Here’s what we’ve been working on:

Last week:

Cudos Network

  • We have updated the Tendermint version to 0.34.19, including the Network Halting patch. 
  • We’ve worked on refactoring the Network Upgrade scripts and embedding them into the Cudos-builders repository. The goal is to use these scripts for future network updates.
  • We’ve completed tests on the refactored Network Upgrade scripts and performed a network upgrade on the Private Testnet network. We carried out the upgrade successfully.
  • We’ve fixed an issue with invariants’ query returning an error. 
  • We’ve completed the implementation that prevents validators from registering with an empty moniker.
  • We’ve removed the vesting module from the list of available transactions because we’re replacing it with the cudosMint module and vesting schedules are not available. 

IBC module

  • We have started research on best practices for upgrading the IBC versions. 

Gravity Bridge

  • We have conducted an extensive study on the optimal way to proceed with the Gravity contract upgrade. We need to upgrade it because various modifications have been made (see previous updates). Our findings are as follows:
    • We cannot alter the contract because the data stored on-chain must be in sync with the Gravity Smart Contract.  Doing so would result in data mismatches between the contract and the chain.
    • The only alternative available to us is to erase all Gravity data (during the Hard Fork procedure) and deploy a new contract. As a result, a chain will be created that begins to utilise the Gravity Module.
      • Any past data about ValSetUpdates, Batches, and more will be lost along with ongoing transfers during the upgrade. 
      • This does not present any issue for the network, our testing, or the Gravity bridge.
  • We performed comprehensive testing, transferred tokens to and from Ethereum, and checked module and bridge contract balances.

Explorer Updates

  • We’ve created two full nodes on the Dress Rehearsal network for both explorers. Both explorers were reading from the same node, which put a strain on it. We simulate the production scenario as closely as possible by using two separate full nodes for each explorer.
  • We’ve worked on displaying Smart Contract info on Explorer ver.2.
  • We’ve also worked on displaying Smart Contracts by address in Explorer ver.1.
  • We’ve implemented a new custom Cudos theme for the Explorer ver.2. 
  • We’ve extended the Explorer ver.1 user interface to include all forms of governance proposals (including IBC ones).
  • We’ve worked on reported bugs:
    • Gravity transaction is not triggering balance update in Explorer ver.2.
    • Voting and depositing on passed/rejected proposals should not be possible.

Cudos dashboard

  • We’re working on the main dashboard page, with all the functionalities there.
  • We’re also implementing the staking page (where all validators are presented). 
  • We’ve further allocated jobs to ensure a more efficient division of labour. Our next update will include more details on the Cudos Dashboard’s progress.

Current week:

  • This week, our primary focus is on the Dress Rehearsal network’s hard fork, scheduled for Thursday (21st of April). We’ll be undertaking the following:
    • The creation of the proposal
    • Estimation of the block height for the network upgrade 
    • Communications
  • With the Gravity Module audit, we’re assisting in the process’ commencement.
  • We’re going to support efforts towards the testing and final sign off of the Validator peer connectivity issue (which caused the Network Halt). 
  • The team will continue and finalise the efforts for the IBC module Hermes relayer upgrade and the IBC module upgrade. 
  • We will continue with the improvements on the Explorers, where the emphasis will be on bugs and upgrades to Explorer ver.2.
  • We’ll proceed with preparing the next version of Cudos Blast. 
  • We aim to wrap up the Frontend and functional implementations around the Dashboard and Staking pages of the Cudos Dashboard application.
  • We aim to start working on the Cudos MultiSend DApp during this sprint, starting with the initiation phase.

You can still participate in our Testnet!

For developers, our incentivised Testnet remains open to participation. Perform tasks for the chance to earn rewards. We are currently in the fourth and final phase of the Testnet, with the highly anticipated Mainnet launch set for release next month. Check out some of the outstanding tasks here.

About Cudos

Cudos is powering the metaverse bringing together DeFi, NFTs and gaming experiences to realise the vision of a decentralised Web3, enabling all users to benefit from the growth of the network. We’re an interoperable, open platform launchpad that will provide the infrastructure required to meet the 1000x higher computing needs for the creation of fully immersive, gamified digital realities. Cudos is a Layer 1 blockchain and Layer 2 community-governed compute network, designed to ensure decentralised, permissionless access to high-performance computing at scale. Our native utility token CUDOS is the lifeblood of our network and offers an attractive annual yield and liquidity for stakers and holders.

Learn more: