Minter Dev Notifications

Minter Blockchain Important News

On October 19, 2020, the network successfully upgraded to version 1.2. Since then, over 450,000 blocks have been generated. No critical issues have been detected. Thank you to all developers and validators who quickly updated their services!

Some news:

1. Golang security fix
On November 12, the Go language developer team released a vital update that eliminated a couple of vulnerabilities. One of the changes fixed the processing of large numbers that was causing applications to crash: crypto/rsa.VerifyPSS, crypto/rsa.VerifyPKCS1v15, and crypto/dsa.Verify might panic when provided crafted public keys and signatures.

We have re-compiled the v1.2.0 release with the latest version of Go (v1.15.5) so developers and validators can update their nodes. We suggest that you run tests on non-critical services before updating the main ones.

2. 1.2.1 Update
After the nodes moved onto v1.2, we have noticed quick increase in disk space consumption. After investigating, it became evident the problem was with the storage developed by Tendermint. Member of our core team submitted a pull request that was merged shortly afterwards. This fix will be included with Minter Node v1.2.1. To reduce the size of the base, it will be necessary to sync the node from scratch.

Full list of improvements:
- old_coin_symbol and old_coin_id tags added to the RecreateCoin transaction
- Increasing disk space issue resolved
- Minor Console bugs fixed
- Auto-load of minter-mainnet-3 genesis

Release Candidate: https://github.com/MinterTeam/minter-go-node/releases/tag/v1.2.1-rc5
We suggest that you run tests on non-critical services before updating the main ones.

3. Problem with Coin Owners
All coins that had been created using the most recent instructions were assigned an owner in network v1.2. Due to an error in genesis, however, some coins with other parameters (but with 100% of supply on one address) didn’t get an owner. A total of 64 coins have been affected.

We’re aware of the issue and will resolve it in one of the upcoming updates. That will require a simultaneous update of all validators.

Plans:
1. Blockchain security audit. We’ve prepared the node’s code for audit and plan to send out applications to several companies that could run it.
2. 2.0 development. We’re working on Minter 2.0 architecture and functionality and will soon publish a detailed document with description.
3. Minter HUB development. Minter HUB is a cross-chain bridge with smart contracts (between Minter and Ethereum in the first place). The solution is unique in that all operations are made in a single transaction, which can be signed both from within Minter (e.g., exchange of any custom coin for one of the numerous ERC-20 tokens) and Ethereum (e.g., buying BIP for USDT).

🚀

www.tg-me.com/us/Minter Dev Notifications/com.minterdev_en/14

144 viewsNov 15, 2020 at 16:19

Minter Blockchain Important News

On October 19, 2020, the network successfully upgraded to version 1.2. Since then, over 450,000 blocks have been generated. No critical issues have been detected. Thank you to all developers and validators who quickly updated their services!

Some news:

1. Golang security fix
On November 12, the Go language developer team released a vital update that eliminated a couple of vulnerabilities. One of the changes fixed the processing of large numbers that was causing applications to crash: crypto/rsa.VerifyPSS, crypto/rsa.VerifyPKCS1v15, and crypto/dsa.Verify might panic when provided crafted public keys and signatures.

We have re-compiled the v1.2.0 release with the latest version of Go (v1.15.5) so developers and validators can update their nodes. We suggest that you run tests on non-critical services before updating the main ones.

2. 1.2.1 Update
After the nodes moved onto v1.2, we have noticed quick increase in disk space consumption. After investigating, it became evident the problem was with the storage developed by Tendermint. Member of our core team submitted a pull request that was merged shortly afterwards. This fix will be included with Minter Node v1.2.1. To reduce the size of the base, it will be necessary to sync the node from scratch.

Full list of improvements:
- old_coin_symbol and old_coin_id tags added to the RecreateCoin transaction
- Increasing disk space issue resolved
- Minor Console bugs fixed
- Auto-load of minter-mainnet-3 genesis

Release Candidate: https://github.com/MinterTeam/minter-go-node/releases/tag/v1.2.1-rc5
We suggest that you run tests on non-critical services before updating the main ones.

3. Problem with Coin Owners
All coins that had been created using the most recent instructions were assigned an owner in network v1.2. Due to an error in genesis, however, some coins with other parameters (but with 100% of supply on one address) didn’t get an owner. A total of 64 coins have been affected.

We’re aware of the issue and will resolve it in one of the upcoming updates. That will require a simultaneous update of all validators.

Plans:
1. Blockchain security audit. We’ve prepared the node’s code for audit and plan to send out applications to several companies that could run it.
2. 2.0 development. We’re working on Minter 2.0 architecture and functionality and will soon publish a detailed document with description.
3. Minter HUB development. Minter HUB is a cross-chain bridge with smart contracts (between Minter and Ethereum in the first place). The solution is unique in that all operations are made in a single transaction, which can be signed both from within Minter (e.g., exchange of any custom coin for one of the numerous ERC-20 tokens) and Ethereum (e.g., buying BIP for USDT).

🚀

BY Minter Dev Notifications