goshimmer VS bsc

I highly recommend searching for "IOTA 2.0 devnet" - it's a *public* test net running for an year with a new OTV consensus entirely without Coordinator. This is the result of literally years of research (link to research papers: https://www.iota.org/foundation/research-papers ). This is the exact link to the git repo of IOTA 2.0 devnet node software: https://github.com/iotaledger/goshimmer The purpose of Shimmer is to test out these solutions (that already exist) in a real live network - Coordicide will land on Shimmer in a series of modules, which should start happening in the next few months.

Goshinmer: https://wiki.iota.org/goshimmer/welcome

Who cares about discord and twitter. He is working even on weekends. https://github.com/iotaledger/goshimmer/commit/3e27a8cb7f128c67244c3d44914b62c078febbd1

That's exactly what the iota foundation is doing, they have built a network where there are no blocks, no commission fees, no miners, the protocol is leaderless, everyone can write on the ledger with their own node. Essentially the network is not competitive (miners trying to mine the block first) but contributory, like bittorrent. Notable fact about congestion, the network exchanges messages that can be only data or economic transactions, the exchange of messages is so fluid that they had to implement a complete congestion protocol in the node with algorithms similar to the TCP layer and a message scheduler. If you're interested in learning more about the technical side, here's a link to their wiki. https://wiki.iota.org/goshimmer/welcome

GOSHIMMER (Coordicide Testnet)

As far as the IOTA ecosystem as whole, we primarily use Rust. Go is being used for prototyping IOTA 2.0 with the GoShimmer node along with some other projects I believe, but Rust is used in the main ones (e.g. client libraries (iota.rs and wallet.rs), Streams, Identity).

[GoShimmer 0.8](https://github.com/iotaledger/goshimmer/releases/tag/v0.8.0) is now out, which means that a working prototype of the final "OnTangleVoting" consensus mechanism is now running on the DevNet.

-CLI: https://github.com/iotaledger/goshimmer/releases

In 2022, cross-chain between BNB Beacon Chain and BSC was exploited because of Zero Day vulnerabilities in the Cosmos SDK. The hotfixes (1.1.15 and 1.1.16) are implemented with almost zero direct impact on users and dApps.

How is is closed source? https://github.com/bnb-chain/bsc

BNB Smart Chain Mainnet is expected to have a scheduled hardfork upgrade named Gibbs at block height 23,846,001. The current block generation speed forecasts this to occur around 12th Dec. 2022 at 10:00 AM (UTC). The validators and full node operators on Mainnet should switch their software version to  v1.1.18 by 12th Dec.

1. BSC Release v1.1.16 - BSC v1.1.16 is a temporary urgent patch to mitigate the cross-chain infrastructure between Beacon Chain and Smart Chain so that the cross-chain can be re-enabled back.

For more technical information: https://github.com/bnb-chain/bsc/releases/tag/v1.1.16