Here’s what we’ve been working on:
- We completed the implementation of a test CUDOS token faucet in the Dashboard for developers to fully explore the Public Testnet.
- We implemented a quick and easy way for users to view the validators they have delegated to. This will now happen through an additional tab (My Delegations) on the Staking page that will show the user only the validators that they have delegated to.
- We implemented the functionality to Claim and Restake seamlessly with 1 transaction only to compound earnings. With the next Dashboard version, users will be able to Restake the rewards they are claiming from their delegations to the same Validators from which they are receiving the rewards. This will all happen with a toggle option in the Claiming modal that allows users the option to Restake automatically.
- We updated the Staking page number of validators count to change according to the tab selected (Active, Inactive, All, My Delegations). Currently, this amount always shows the total number of validators.
- We have removed the MAX button on depositing for a Proposal modal as it is a very unlikely use case.
- We implemented sorting of the validators on the Staking page, where the user can sort validators based on reliability metrics.
- We extended the CudosJS to accommodate the Cudos Module.
- We went through a brief refactoring of the Cudos Bridge UI and it is now using the CudosJS.
- We implemented an additional modal which will allow users to choose the type of transaction they would like to create – Single Transaction or Multi Transaction (sending 1 transaction with multiple messages to different addresses).
- We created and further improved the UX of creating a Single Transaction workflow. The process is now more straightforward and optimised.
- We worked on improving the sorting of the transaction table and fixed an issue with all of the different classes.
- We created the Wallet Settings update transaction type, which is listed along with the rest of the transactions, but with the transaction type “Settings Update”.
- We worked on creating all required UI elements for the Settings page of the MultiSig. This includes the Settings page itself. The Settings update modal (where the actual changes are applied) along with the Success/Failure modals.
- We completed all implementations required for adding a new “Owner” of the MultiSig wallet. This includes the flow for Adding a new owner (both functionally and frontend), Removing an owner from the wallet, and handling the transaction type for the “Wallet Owner” updates.
- We improved the UX and implemented a visualisation, which provides the reason for a proposal/transaction failure.
- We completed the fetching and display of all types of transaction types. The new additions to the types are:
- Aborted – this transaction status applies for all transactions that have been in the Queue, were expecting more signatures, and Wallet update (any kind of update) took place before the transaction has been executed. This is a final state.
- Expired – This status shows that a certain transaction expired due to not getting the number of needed signatures before the set expiration time.
- Failed – This status implies that a transaction has failed for any reason. This is NOT a final status, and this transaction can be executed again.
- We finalised the dropdown view of the transactions to improve the UX when the user reviews the transactions.
- We completed the Execute transaction modals and finalised the whole transaction execution flow.
- We finalised the Approve and Reject messages and modals for signing a created transaction before its execution.
NFT Minting Portal:
- We implemented the functionality to update a collection. In v0.1.0 it was only possible to create one, and this version (0.3.0) will allow users to add/remove NFTs from the collection.
- We included pagination in “My NFTs” page of the Minting Portal.
- We updated the design based on thefeedback that we received.
- We included an official README file to the NFT Minting UI repository.
- We researchedthe best approach in terms of storage for the Minting Portal. Piñata and multiple other services were researched and decided to go ahead with NFT.storage
- After initial testing of version 0.1.0 we concluded that several file types were not working as expected. We fixed this and all file types are now supported.
- We included caching for the NFT minting portal to improve loading time and UX.
- We included a captcha on the portal.
- We updated the calculation of the circulating supply of the CUDOS token.
- We completed an implementation that will have Docker restart BDJuno if it stops working for a certain period.
- We updated multiple vulnerable packages in CudosJS.
- We will move forward with research and outline the approach we need to take to move from using Docker to a standalone binary for cudos-noded.
- We will aim to accommodate the upgrade of our Private Testnet so that we can proceed with deployments on multiple UIs (MultiSig, Dashboard, NFT Minting Portal).
- We will continue working on improvements around the Dashboard. There are multiple suggestions on how we can optimise the UX further. We are in the ideation phase around improving the Dashboard to accommodate Validator’s needs as well.
- We aim to wrap up version 1.0.0 of the MultiSig wallet.
Build on Cudos!
We’re out to improve blockchain and cloud technology whilst reducing their harmful environmental effects. Our network offers a cheaper, more energy-efficient alternative for dApps, asset ownership, and transfer. Check out our docs and start building on Cudos today!
- Join the Cudos’ Discord server
- Join the Cudos’ Telegram community
- Buy CUDOS tokens
- Become a Cudos ambassador
Come build on our mainnet!
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.