Dev Log no.6
Disclaimer: Information as of Jun 3, 2022. For the most recent updates, dive into our comprehensive documentation here
Presenting our Dev Log #6, bringing you updates from our tech and product teams. A significant amount of progress has been made as we continue to build out the Composable tech stack. In our past sprint; the Mosaic relayer build for the job producer and executor is near completion, defined features and rewards in Pablo staking, and completed a PR on implementation of the IBC protocol for Substrate, which brings us closer to the implementation of Centauri.
Mosaic
We kicked off relayer refactoring a month ago to enhance the security of cross-chain transfers. Adopting an agile approach, teams from front end, back end, integrations, testing, and QA have daily discussions which allow us to identify and address blockers early. Our community will be happy to note that the build for job producer and executor is near completion. The job producer and the executor make up the bulk of the relayer; they are responsible for listening to transfer/ withdrawal requests, schedule jobs, validate them, and execute the transfer/withdrawal as requested. We are deploying them in a pre-production environment to test how they interact with each other. The completion of QA will be an important milestone in our relayer refactoring, which we are working to close off shortly.
Simultaneously,, we are extending the job producer to support Polkadot.js as well as EVM by enabling the job producer to listen to Substrate events. This involves adapting the event listener and blocker processor. Once the job producer is connected to Substrate chains, users will be able to transfer tokens from EVM chains to Picasso and vice versa.
Top-level highlights:
- Kicked off relayer refactoring
- Cross department efforts for identifying blockers
- Build job for producer and executor is near completion
- Ready to deploy and start testing how they interact with each other
- Extending the job producer to support Polkadot.js and EVM
Picasso
We have updated the approach to fee distribution and staking rewards on the Pablo DEX, including the fee distribution for LPs, stakers, and Pablo governance. The documentation is near completion (you can find the PR here). The next steps will be to blockchain integration and testing it on the Dali testnet. We have started refactoring existing pallets to enable the use of fNFT in governance. fNFTs play a similar role like veCRV in Curve Finance. They allow holders to decide on adding new assets, and allocating liquidity incentives, but with greater flexibility in renewing and splitting the fNFTs. We are positioning the fNFT to become a yield-bearing, governance NFT in the Picasso ecosystem, the first of its kind.
Most of the Picasso and Pablo pages, such as the overview, interface for swaps, bonding, LBP in Pablo, etc., are under integration, where we ensure that the pallet and the front-end are connected in ways that are consistent with the product design. As a result of changes to the fNFT, Pablo fee distribution, staking rewards pallets, we are updating the integrations as well. In this process, we are also refining the APIs using Subsquid to avoid calculations on the front-end, for example the initial balance, tokens sold and tokens raised, etc. We have chosen to handle calculations with RPCs rather than at front-end for greater security.
The Apollo oracle is one of the core pallets Composable is developing. Apollo will provide price feeds to the Pablo DEX and Angular, a cross-chain money market. Apollo has a permissionless set-up, anyone following the instructions can set up their own oracle and get rewarded/slashed according to their contribution. This week we have validated the permissionless set-up, which worked successfully.
Top-level highlights:
- Updated the approach to fee distribution and staking rewards on the Pablo DEX
- Preparing for blockchain integration and testing it on the Dali testnet.
- Started refactoring existing pallets to enable the use of fNFT in governance
- Refining APIs using Subsquid
- We are using RPCs for error handling and improved security during calculation
Trustless bridging
Our bridging team continues to pioneer the exploration of trustless bridging through light clients, which has stronger security protection through finality proofs, compared to the commonly used lock-and-release mechanism. We are excited to report that this week we have completed the PR that enables the implementation of the IBC protocol on Substrate, which is the gateway for cross-chain communications via IBC.
It is an important on-chain and trustless mechanism for developers to:
- Connect with any chains that have a light client protocol
- Continuously verify the state of that chain
- Suspend the connection if any misbehaviour is detected
As a result of the implementation of the IBC-protocol in this pallet, users can verify and get proofs of the shared state of cross-chain apps on connected chains at all times. The module router allows cross-chain applications to make changes to their state on different chains, while still ensuring that the state on each chain is valid.
Top-level highlights:
- Completed PR that enables implementation of the IBC on Substrate
We are excited to share this important milestone and contribute to an interoperable future.
Thank you to the community for their ongoing support as we gear closer to launching our full tech stack in the coming months.
If you have any questions or comments on the PR, please reach out to us on Discord where our team is on hand to answer your queries, comments and suggestions.
For more information about Composable and how it is architecting the unified DeFi landscape of the future, check out our socials:
Twitter | Telegram | Discord | Website | GitHub | LinkedIn | Youtube
