Release 3.6.1

Changes

• Improved the format of a panic message by extending it with nonces from an account and a transaction
  by [@aleksuss]. (#898)

Release 3.6.0

Fixes

• Fixed underflow in the modexp gas calculation by [@guidovranken]. (#883)
• Prevented subtraction underflow in th xcc module by [@guidovranken]. (#888)
• Fixed balance and gas overflows in the xcc module by [@guidovranken]. (#889)

Changes

• CI was updated by changing self-hosted runner to the GitHub heavy by [@aleksuss]. (#881)
• Removed a logic of fee calculation in the eth-connector by [@karim-en]. (#882)
• Version of the rust nightly was updated to 2023-12-15 by [@RomanHodulak]. (#885)

Release 3.5.0

Additions

• Added a new transaction upgrade which allows upgrading the contract and invoking the state_migration callback
  with one call by [@aleksuss]. (#878)

Fixes

• Updated the logic of upgrading XCC router which works properly on both mainnet and testnet by [@birchmd]. (#877)

Release 3.4.0

Additions

• Added a possibility to pass initialize arguments in json format to the new transaction by [@aleksuss]. (#871)
• The SubmitResult was made available for ft_on_transfer transactions in the standalone engine by [@birchmd]. (#869)
• The order of producing the exit precompile and XCC promises has been changed to sequential by [@birchmd]. (#868)

Changes

• Removed the code hidden behind the feature that isn't used anymore by [@joshuajbouw]. (#870)
• The logic of unwrapping wNEAR has been changed to the Bridge's native by [@birchmd]. (#867)
• Bumped the near-workspaces to 0.9 by [@aleksuss]. (#862)

Fixes

• Add a method for upgrading XCC router contract by [@birchmd]. (#866)
• Fixed a potential panic in the ExitToNear precompile by [@guidovranken]. (#865)
• Fixed a behaviour when the ft_transfer could occur before the near_withdraw by [@birchmd]. (#864)
• Fixed correctness of reproducing the NEAR runtime random value in the standalone engine by [@birchmd]. (#863)

Release 3.3.1

Fixes

• The smart contract owner whose account id is not the same as the contract account id can set ERC-20 metadata by [@aleksuss]. ([#858])

Release 3.3.0

Changes

• Changed the logic of cost calculation in Silo mode. Specifically, the fixed cost has been replaced with
  a fixed amount of gas per transaction by [@aleksuss]. ([#854])

• near-workspaces-rs has been updated to 0.8.0 by [@aleksuss]. ([#855])

Release 3.2.0

Changes

• Changed structure SetEthConnectorContractAccountArgs for setting eth connector account. It was extended with
  additional field: withdraw_serialize_type for defining serialization type for withdraw arguments by [@aleksuss]. (#834)

• Updated rocksdb up to 0.21.0 by [@aleksuss]. (#840)

Additions

• Added a possibility of mirroring deployed ERC-20 contracts in the main Aurora contract in Silo mode by [@aleksuss]. ([#845])

• Allow to initialize hashchain directly with the new method by [@birchmd]. (#846)

• Added a silo logic which allows to set fixed gas costs per transaction by [@aleksuss]. (#746)

• Added a new type of transaction which allows to add full access key into account of the smart contract by [@aleksuss]. (#847)

Release 3.1.0

Additions

• Added the possibility to use native NEAR instead of wNEAR on Aurora by @karim-en. #750

• Added hashchain integration by @birchmd. #831

• Added functions for setting and getting metadata of ERC-20 contracts deployed with deploy_erc20_token transaction by @aleksuss. #837

Aurora SILO 3.0.0

chore: update release notes in develop branch (#829)

## Description

The PR just updates release notes in the develop branch and bumps
`aurora-engine` version.

Release 3.0.0

Fixes

• Updated SputnikVM dependency with bugfix in the returndatacopy
  implementation and a performance improvement in accessing EVM memory by @birchmd. #826

Changes

• BREAKING: engine-standalone-storage no longer automatically writes to the DB when consume_message is called.
  It is up to downstream users of the library to commit the diff (after doing any validation for correctness) by @birchmd. #825

Additions

• New crate for the so-called "hashchain" implementation. It will enable verification of Aurora blocks by light clients
  in the future by @birchmd. #816