Release - FIO v2.0.0
Blockchain update
A replay is required when updating to this release.
Upgrade required by Friday September 4th
This is a required upgrade to the blockchain code. All FIO API and History Nodes must be upgraded by Friday September 4th. Nodes that are not upgraded by that date will be forked from the updated FIO blockchain.
Enhancements and Updates
These features are included in the current fio release but may not be available until the corresponding features are also released in fio.contracts.
(#217) Add final forking date to apply_context.cpp / chain_plugin
(#73) FIP-2. Add get_fio_domains and get_fio_addresses endpoints with support for paging.
(#95) FIP-3. Add ability to cancel a request for funds.
- Adds a new status for a request for funds, to cancel a request for funds.
- Modifies the get_sent_fio_requests to return cancelled requests along with the rest.
- Modified the record_obt_data so that it no longer allows multiple status records to be associated with a request id.
- Adds a new endpoint and contract action for cancel_funds_request.
- Adds a new get endpoint get_cancelled_fio_requests, returning cancelled fio requests.
(#96) FIP-4. Add ability to remove mapped public addresses. Adds new endpoints and fio.address actions for remove_pub_address remove_all_pub_address.
(#35) Addresses issue #112. EOSIO 1.8.10-1.8.12 upgrade.
(#118 / #119) Create /get_actor endpoint. Adds a new endpoint to the chain plugin called get_actor that takes as input fio public key and returns the actor for the specified public key.
V1 History Updates
A resync is required for nodes running the V1 history plugin when upgrading to this release.
Some of these updates may not be available until the corresponding features are also released in fio.contracts.
(#120) FIO Support for History Plugin. Includes initial import of light history implementation from Greymass for FIO.
(#129) Unlinkauth missing from action mapping. Addresses issue #128.