Releases: boscore/bos.contract-prebuild
BOSCore Contracts v3.0.4 Release Notes
Change Description
- Merge eosio.contracts 1.8.3 for improve the REX logic
- Fix BOS.Oracle clean data logs issues
Documentation Additions
BOSCore Contracts v3.0.3 Release Notes
Upgrades
Merge some critical fix from EOSIO contracts.
#272 fix double-move bug in system_contract::registration - v1.6.x
#261 fix assertion in create_core_token
#382 modify eosio::bidrefund calling authority
BOSCore Contracts v3.0.2 Release Notes
Upgrades
BOSCore has the fastest finality and is the first IBC equipped DPoS blockchain.
Aiming to refactor business scenarios with decentralized technology.
And now, the next significant feature BOS Oracle has finished its first version: BOS Oracle v1.0.
Some Oracle services are designed on the basis of the assumption of a dependable or authoritative data source, which is theoretically too risky to guarantee the authenticity of the data provided by such a data source. Thus, the principle of the BOS Oracle system from the beginning is that:
BOS Oracle does not relying on each oracle provider's 100% credibility of the data they provided.
BOS Oracle treat each oracle provider as a participant in the game, in order to achieve overall credibility in the game.
BOS Oracle advantages:
- Game Completion
- Positive Incentive
- Full scene coverage
BOS Oracle Composition
Documentation Additions
English
中文
BOSCore Contracts v3.0.1 Release Notes
BOSCore Contracts v3.0.0 Release Notes
Upgrades
After v3.0.x, BOSCore will use Batch-PBFT consensus algorithm, this version add function to realize upgrade smoothly.
- upgraded version of system contract used for dpos-pbft (bos)
- decouple setupgrade arg and wast interface param
- comment unnecessary attributes.
- add unittest in build script.
Deployment
- upgrade
eosio.systemcontract - set target upgrade block hight example:
cleos push action eosio eosio setupgrade '{"up":{"target_block_num":1000}}' -p eosio