v0.0.31

Breaking changes

• id parameter is now required when sending payments using Compliance Protocol.

Changes

• nonce value does not change when repeating Auth Request after receiving pending status.
• Support for sending XLM using Compliance Protocol.
• Fix for #109

Please migrate your compliance DB before running a new version using: compliance --migrate-db.

v0.0.30

• Support for "Forward federation" destinations.

v0.0.29

• Improved transaction submission code:
  • High rate transaction submission using /payment endpoint should work better.
  • Added id parameter to /payment request: payments with id set, when resubmitted, are using previously created transaction envelope stored in a DB instead of recreating a transaction with a new sequence number. This can prevent accidental double-spends.
• Fix for a bug in /builder endpoint: sequence number is now incremented when loaded from Horizon server (#86).
• Payment listener is now also sending account_merge operations and, for each operation, a new parameter: transaction_id.
• Updated github.com/BurntSushi/toml dependency.

Read README file for more information about new features.

Please migrate your bridge DB before running a new version using: bridge --migrate-db

v0.0.28

• Added error messages to Compliance protocol (SEP-0003)

v0.0.27

• Admin Panel (/admin endpoint in bridge server).
• /tx_status endpoint More info.
• Sequence number in automatically loaded if it's not set in /builder.
• Fixed log levels in PaymentListener (#73).
• Fixed AllowedFI table name under Windows (#72).
• New -v parameter to print app version.

v0.0.26

• Fix log level in PaymentListener.

v0.0.25

• XLM (lumen) payments can be now used in PaymentListener.
• Fixed a loop in PaymentListener occurring when multiple payments fail.

v0.0.24

• Better responses.
• Use http.Client with Timeout.

v0.0.23

Fix a bug in protocols.Asset.String. Add more_info field to invalid_parameter errors.

v0.0.22

Ability to reprocess received payments.