All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.
As this project is pre 1.0, breaking changes may happen for minor version bumps. A breaking change will get clearly notified in this log.
0.22.0 - 2020-03-26
- Add TransactionBuilder (#54)
0.21.0 - 2019-10-04
- Stellar Protocol 12 compatibility.
- XDR changes for path payment
- constant renames, which may cause breaking changes if referred to directly
0.20.0 - 2019-05-22
- Stellar Protocol 11 compatibility (#48)
- XDR changes for CAP-0006 Buy Offers
- XDR changes for CAP-0020 Bucket Initial Entries
- Add
manage_buy_offer
,manage_sell_offer
andcreate_passive_sell_offer
factory methods toStellar::Transaction
andStellar::Operation
- Deprecate
manage_offer
andcreate_passive_offer
factory methods inStellar::Transaction
andStellar::Operation
- Add an option to pass the exact stellar-core revision into
xdr:update
Rake task
- Loosen ActiveSupport to >= 5.0.0
- Update XDR definitions for stellar-core v10.0.0 (introduces Liabilities and other changes to support asset-backed offers as per CAP-0003 Specification)
- Add factories for ledger, transaction, operation.
- Use rbnacl instead of rbnacl-libsodium (the latter has been deprecated)
- Rename
Stellar::SignerKey#onetime_signer
helper toStellar::SignerKey#hash_x
, add preimage validations
- Create co-signers conveniently using helpers
ed25519(keypair)
,preauthorized_transaction(tx)
andonetime_signer(preimage)
fromStellar::SignerKey
module - Merge two transactions with
Stellar::TransactionEnvelope#merge
- Source account overriding in Stellar::Transaction#to_operations
Stellar::Operation.change_trust
can acceptStellar::Asset
instance forline
- Protect
Stellar::Operation.change_trust
against malicious arguments, in the event that developers pass this argument directly from user input
- We now support the bump sequence operation with
Operation.bump_sequence
.
- Update XDR definitions for stellar-core 0.10.0 support
Operation.change_trust
learned how to use a default for the:limit
parameterStrKey
learned about new version bytespre_auth_tx
andhash_x
- Update XDR definitions for stellar-core 0.9.1 support
- Added
#signer_key
helper toKeyPair
- Avoid modifying $LOAD_PATH to fix load order issues
- Update XDR definitions for stellar-core 0.6 support
- BREAKING CHANGE: Removed support for JRuby.
- Added support for
manage_data
operations
Stellar::Transaction#to_envelope
can now be used without arguments, returning aStellar::TransactionEnvelope
with zero signatures.
- Added memo helpers to
Stellar::Transaction.for_account
, allowing any operation builder (such asStellar::Transaction.payment) to provide a custom memo using the
:memo` attribute.
- XDR Definitions have been updated to stellar-core commit eed89649c2060b8e9dacffe2cec4e8b258b32416
- BREAKING CHANGE: The default network for this library is now the stellar test network.
To enable this library for the production network use
Stellar.default_network = Stellar::Networks::PUBLIC
at the head of your script or in your configuration function.
- Bump xdr dependency to 1.0.0
- Update default fee for transactions to new minimum of 100 stroops
- Update to latest xdr (stellar-core commit ad22bccafbbc14a358f05a989f7b95714dc9d4c6)
- Update to latest xdr
- BREAKING CHANGE: "Amounts", that is, input parameters that represent a
certain amount of a given asset, such as the
:starting_balance
option forOperation.create_account
are now interpreted using the convention of 7 fixed-decimal places. For example, specifying a payment where the amount is50
will result in a transaction with an amount set to500000000
.