Releases: ShareRing/Shareledger
v2.0.0
Change summary
- Add module distributionX to change fee distribution. Config devpool account:shareledger1qda5j5mgvmesceg8h68przllcxhz5lzvwz38v5
- Add globalfee config to gentlemint
- Fixed fee apply only for Shareledger custom modules.
- Upgrade library version: Cosmos-sdk 0.47, upgrade ibc-go, wasmd...
- Clean junk data in module ID
- Refactor code in Shareledger
- Add e2e test in Shareledger
- Migrade from Tendermint consensus to CometBFT, a forked version that offers enhanced features and improvements.
Full Changelog: v0.1.6...v2.0.0
v2.0.1
Change summary
- Add module distributionX to change fee distribution. Config devpool account:shareledger1qda5j5mgvmesceg8h68przllcxhz5lzvwz38v5
- Add globalfee config to gentlemint
- Fixed fee apply only for Shareledger custom modules.
- Upgrade library version: Cosmos-sdk 0.46, upgrade ibc-go, wasmd...
- Clean junk data in module ID
- Refactor code in Shareledger
- Add e2e test in Shareledger
Full Changelog: v0.1.6...v2.0.1
v1.4.1
Change summary
We will be upgrading the ShareLedger binary to apply the urgent HotFix that the CosmosSDK team issued recently. For more information about this fix please see here: https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349
We have also made some minor updates to the ShareLedger Swap/Bridge functionality.
v1.4.0
Change summary
CosmWasm is a RUST based smart contract protocol, built for the Cosmos ecosystem. ShareRing are pleased to be adding CowmWasm to ShareLedger to accelerate the opportunities for external developers to leverage our verifiable credentials and NFT infrastructure to build smart contracts onto ShareLedger (Dapps)
We will deploying CosmWasm module onto ShareLedger via our new governance proposal mechanism.
v1.3.1 (Internal use)
Fix electoral query for relayer
This version we fix the bug when query the list of relayer
v1.3.0
This on-chain upgrade governance proposal is to adopt ShareLedger v1.3.0, which includes the new ShareLedger Swapping module, as well as a number of other fixes. By voting YES to this proposal, you approve to add these.
Background
Since the last ShareLedger upgrade, there have been a number of fixes. Additionally, the team have created some significant improvements to the ERC20/SLP3 swapping process and fees by incorporating it into the ShareLedger blockchain as a native Web3 function. The new swapping module also creates the ability to perform swaps between BEP20 (BNB Smart Chain) and SLP3 (ShareLedger).
More detail on the changes are as follows:
Cosmos SDK upgraded to v0.45.3
Full changlog here: cosmos-sdk/CHANGELOG.md at v0.45.3 · cosmos/cosmos-sdk
Tendermint upgraded to v0.34.19
Full changelog here: tendermint/CHANGELOG.md at v0.34.19 · tendermint/tendermint
Cosmos IBC upgraded to v3.0.0
Full changelog here: ibc-go/CHANGELOG.md at v3.0.0 · cosmos/ibc-go
Swap module on Shareledger
-
All swap requests are now kept track by transactions on Shareledger
-
Increase transaction volume on Shareledger
-
Reduce swapping cost (instead of making multiple transactions to Ethereum, now most of transactions are done on Shareledger)
-
Relayer role to process approved swap requests
-
Support both Ethereum (ERC20) and Binance smart chain (BEP20)
-
Use EIP712 to sign and verify the approvals on smart contract side
-
Reduce use of centralized database for keeping transactional data
-
Overall performance improvement
On-Chain Upgrade Process
When the network reaches the halt height (as published in this proposal), the state machine program of the ShareLedger chain will be halted. The current method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary, then restart the binary. You can use the following script to upgrade your ShareLedger:
wget https://github.com/ShareRing/Shareledger/releases/download/v1.3.0/proposal_upgrade.sh
chmod +x proposal_upgrade.sh
sudo ./proposal_upgrade.sh
Reminder: you can use the above upgrade script only if the following message appears in ShareLedger log
UPGRADE "v1.3.0-shareledger" NEEDED at height: ...
Potential Risk Factors
Although very extensive testing and simulation has taken place there always still exists a risk that ShareLedger might experience problems due to potential bugs or errors from the new features. In the case of serious problems, validators should stop operating the network immediately, allow the ShareRing team to execute a contingency plan. and await further instructions via the Masternode Slack channel.
v1.2.0
Improvements
- ADR-028 Addresses: a new specification for deriving addresses for all kinds of addressable accounts to cover a security risk due to address space collisions.
- Better support for multisig transactions.
- Transaction fees are now saved on-chain and configurable. We can adjust the transaction fee whenever necessary without having to update the binary.
- Better modularization on some of our modules. gentlemint module will now only take care of token-related tasks like load tokens, burn tokens or fee handling, etc. electoral module takes care of authorization.
- Transaction fee will be automatically calculated base on the on-chain values if not supplied. Clients can still submit higher fee if they want to.
- Automatically load SHR by SHRP when balance is not enough for transaction fee.
- Backports improvements to state synchronization and ABCI performance under concurrent load, and the PostgreSQL event indexer.
- Allow state sync fetchers and request timeout to be configurable.
- Retry requests for snapshots and add a minimum discovery time (5s) for new snapshots.
Bug fixes
- Sometimes user input fee gets overridden by application default fee, unexpectedly.
- Transfer tokens accidentally minted the same amount of tokens to module’s balance (each module has its own address), causing inconsistent total supply values.
- When balance is equal to transaction fee, the transaction is rejected. We now allow spending ALL available balance, making it zero.
- There is a substantial bug in evidence handling where evidence could sometimes be broadcast before the block containing that evidence was fully committed, resulting in some nodes panicking when trying to verify said evidence.
- Sometimes peers (nodes) try to send messages on incorrect channels causing error which could terminate the process.
- A bug with incorrectly handling contexts that would occasionally freeze state sync.
- A memory leak in the evidence reactor.
- And many many more from Cosmos SDK and Tendermint altogether.
Those are some major features, improvements and bug fixes we both made and picked up from a huge list with tons of others. More can be found at Cosmos SDK and Tendermint official github pages.
Instruction
For this release, depending on your current validator situation only run ONE of the two scripts. DO NOT RUN BOTH.
Do not run these instructions until notified by ShareRing
1. For Nodes currently running shareledger
# download the hard_fork_v1.2.0.sh script
curl -LJ https://github.com/ShareRing/Shareledger/releases/download/v1.2.0/hard_fork_v1.2.0.sh > hard_fork_v1.2.0.sh
# give exec permission
chmod +x hard_fork_v1.2.0.sh
# run the script with sudo privilege
sudo ./hard_fork_v1.2.0.sh
2. For Nodes that have not installed shareledger before
This is for new builds
# download the new_validator_v1.2.0.sh script
curl -LJ https://github.com/ShareRing/Shareledger/releases/download/v1.2.0/new_validator_v1.2.0.sh > new_validator_v1.2.0.sh
# give exec permission
chmod +x new_validator_v1.2.0.sh
# run the script with sudo privilege
sudo ./new_validator_v1.2.0.sh
v1.1.1
Added in this release
Fix staking problem of jailed validator
Instruction
For this release, depending on your current validator situation only run ONE of the two scripts. DO NOT RUN BOTH.
Do not run these instructions until notified by ShareRing , message will be sent after 4pm Australia Eastern Time (GMT+10) today (05/31/2021)
1. For Nodes currently running shareledger
# download the hard_fork_v1.1.1.sh script
curl -LJ https://github.com/ShareRing/Shareledger/releases/download/v1.1.1/hard_fork_v1.1.1.sh > hard_fork_v1.1.1.sh
# give exec permission
chmod +x hard_fork_v1.1.1.sh
# run the script with sudo privilege
sudo sh hard_fork_v1.1.1.sh
2. For Nodes that have not installed shareledger before
This is for new builds
# download the new_validator_v1.1.1.sh script
curl -LJ https://github.com/ShareRing/Shareledger/releases/download/v1.1.1/new_validator_v1.1.1.sh > new_validator_v1.1.1.sh
# give exec permission
chmod +x new_validator_v1.1.1.sh
# run the script with sudo privilege
sudo sh new_validator_v1.1.1.sh
v1.1.0
v1.02
New release of ShareLedger