Presenting the recording of our recent Digitalsocial.id AMA featuring Simon Molitor, CEO of Digitalsocial.id and Kåre Kjelstrøm, CTO of Concordium. Feel free to listen to the session if you couldn't attend.

Remember to join the AMA with our CTO @kaarekjelstroem today!

🚀 Exciting news! Concordium's groundbreaking consensus protocol, ConcordiumBFT, is will be soon live on testnet! This implementation achieves an ideal balance of speed, capacity, and security, catering to diverse use cases in the Concordium ecosystem. 🔑 🔗 This milestone is a game-changer for self-sovereign identity, leveraging verifiable credentials to unlock tremendous business potential within Concordium's innovative infrastructure. Stay ahead with Concordium! 🌐 📢 Mark your calendars for August 21 as the protocol update takes effect on testnet. Get ready for protocol version 6, featuring the powerful Concordium BFT consensus protocol and expanded smart contract capabilities. Enhanced support for sponsored transactions is a game-changer. ⏰ ⚙️ Node runners, ensure seamless service by upgrading to version 6.0.4. before the big day. Keep track of the journey on our testnet status page. Stay connected! 📡 🌐 Stay tuned for upcoming releases of concordium-client, cargo-concordium, smart contract libraries, and wallets. Exciting times lie ahead! The mainnet node release and protocol update are on the horizon—September 11 and 25 are the dates to remember. 🗓️ Release Note:

t.co

Protocol Update 6 Proposal:

t.co

Testnet Status Page:

t.co

Baker Documentation:

t.co

Concordium Client 6.0.1 is released. It adds support for the upcoming protocol version 6. Note that this version of Concordium-Client requires at least node version 5.4. 🔘 Discourse announcement 🔘 Release notes 🔘 Download

Benefits of the Hotstuff-Based New Ecosystem for Concordium 🚀 Exciting news! Concordium's innovative consensus protocol, ConcordiumBFT, is now live on testnet, offering a balanced blend of speed, capacity, and security for various uses. 🔗 This is a game-changer for self-sovereign identity, using verifiable credentials to unlock business potential in Concordium's infrastructure. 📢 Save the date: August 21 for the protocol update on testnet. Protocol version 6 introduces Concordium BFT consensus, enhanced smart contracts, and sponsored transactions. ⚙️ Node runners, upgrade to version 6.0.4. before August 21. Check our testnet status page for updates. 🌐 Watch out for concordium-client, cargo-concordium, smart contract libraries, and wallet releases. Mainnet node and protocol updates are coming on September 11 and 25. 🔘 Release Note 🔘 Protocol Update 6 Proposal 🔘 Testnet Status Page 🔘 Baker Documentation

Concordium Node has been released for testnet in version 6.0.4. This is a major release that contains support for protocol version 6. The main update in protocol 6 is the new Concordium BFT consensus protocol. The new protocol also extends smart contract functionality, with the main usability improvement being better support for sponsored transactions. For more details on changes and effects of the protocol update, please see concordium-update-proposals and our updated baker documentation. The protocol update will be effective on testnet on August 21. Node runners must upgrade to version 6.0.4. before the protocol update to ensure that their nodes do not shut down. You can follow the status of the protocol update on our testnet status page. New versions of concordium-client, cargo-concordium, smart contract libraries and wallets will be released as well. The node release and protocol update on testnet are in preparation of a similar node release and protocol update on mainnet, which are planned for September 11 and 25, respectively. Also, gRPC v1 is NOT enabled in any of the node distributions. gRPC v2 should be used. As a consequence of this the configuration option no-rpc-server and environment variable CONCORDIUM_NODE_DISABLE_RPC_SERVER, as well as default values of rpc-server-port (CONCORDIUM_NODE_RPC_SERVER_PORT) and rpc-server-addr (CONCORDIUM_NODE_RPC_SERVER_ADDR), have been removed. The V1 gRPC server is only started if both of these options are supplied. For information on additional features and improvements included in this node release, please see our release note. 🔘 Discourse announcement 🔘 Download 🔘 Release note