Evidence collection
Release notes
Release v2.0.4
Evidence collection
Release notes
Recommended update. Makes all the calls to RPC nodes faster.
Replaces the old-style calls with appbase style calls and uses broadcast_transaction
instead of broadcast_transaction_synchronous
.
From this version, broadcasting transactions won't return block_num and will only return transaction id. You can use hive.api.findTransaction(transaction_id, expiration)
to get block number when the transaction gets included in a block.
Evidence collection
Release notes
It's highly recommended to update.
rebranded_api
and updateOperations()
which were introduced before hf24 are now deprecated. You can remove both from your code safely. Also, one API call is removed which was used before hf24 to update the chain_id
on broadcasting every transaction.
Release notes
Summary:
- Rebranded everything to Hive
- Added new config
rebranded_api
with defaultfalse
- Setting the new config to
true
will change all the "steem/sbd" in the operations and variables to "hive/hbd". - Added a helper function
autoDetectApiVersion()
to get api version and update the confing. - Deprecated but still working:
- vestingSteem() replace with: vestingHive()
- pricePerSteem() replace with: pricePerHive()
- vesting_steem variable input in estimateAccountValue() replace with: vesting_hive
Important: After updating the config variable rebranded_api
inside the app (e.g. hive.config.set('rebranded_api', true)
) another function (hive.broadcast.updateOperations()
) MUST be called manually before broadcasting any transaction.
updateOperations()
is necessary to update the list of operations according to the changed configuration. It's also needed after autoDetectApiVersion()
!
For technical reasons, we can not run updateOperations()
automatically after config change.
The ideal and recommended option is to change the 'rebranded_api' inside the config.json
file before using hive-js
.
Release notes
Hive HF24 chain_id swap. Smooth transition from HF23 to HF24.