Bancor has made some important updates to the Bancor Protocol. Effective immediately, these changes remove code redundancy from the Protocol and are also designed to ensure that transactions submitted to the Bancor Network are executed in the correct and valid order.

** Bancor now limits all transactions to use the quickConvert function. Bancor will no longer support use of the Buy or Sell functions. This update removes code redundancy and ensures all transactions use the same entry point. More info on Bancor’s quickConvert function.

** Bancor now prioritizes transactions submitted to the Bancor Network in order to ensure that they are executed in the correct and valid order. This is NOT a breaking change, meaning the current process will continue to work as it used to. Read more in Bancor’s Knowledge Base.

** As an added layer of protection to ensure transactions are executed in the correct and valid order, Bancor will now hash several values into each transaction that cannot be changed. Any change to the following hashed values will cause the transaction to fail:

Block number — transactions are initiated with a lifespan of X blocks (at the time of writing — 12 blocks). Meaning, from the moment you create the transaction you have X amount of blocks to execute it. Executing it after the transaction lifespan will cause the transaction to fail. A specific API to query transaction lifespan on the Bancor Network will be available in the near future.

Gas price — the gas price received is part of the transaction’s hard coded values. Changing the gas price will cause the transaction to fail.

User address — transaction is limited to a specific user.

Nonce — transaction is limited to a specific nonce.

Read more about building transactions using Bancor’s Convert API.

We are constantly working to improve the experience of interacting with Bancor for both users and developers. As always, we would love to hear your thoughts and feedback on these or any aspects of the Bancor Protocol.