As mentioned in our previous Dev Logs, our current focus remains centered on preparing Picasso and Pablo for launch as we finalize audits and QA, whilst continuing to make strong progress within our Bridging team for both Cosmos and NEAR, and the XCVM demo and developer interface that will be shown at Cosmoverse in September.
Picasso/Pablo
Staking rewards has been the largest pallet focus in recent sprints, with this now completed from a development perspective and ready to be extended to support our latest fNFT pallet. This will allow us to have complete functionality for PICA and PBLO fNFT staking on launch.
With that in mind, our Substrate developers are progressing with the fNFT pallet itself, which marks the final pallet necessary for our complete launch sequence. Once this has been completed, it will be passed to Halborn for audit, along with the staking-rewards pallet.
In the meantime, we are additionally making final tweaks to our gas token support for Picasso, via our bring-your-own-gas pallet. By focusing on this, we will be able to roll out an improved UX that will support EVM assets on Picasso — allowing the choice of gas token to be abstracted away from the user and made as simple as possible.
As mentioned previously, the audits for Pablo and Picasso remain the largest factor before we can proceed with launch. One of the largest pallets — Pablo DEX, has now been completed, as well as DEX router, currency-factory, and assets. This marks 80% of our audits now complete.
Through pre-production validation, we identified UI/UX enhancements that our design and FE team are now working on — preparing Pablo and Picasso for their launch. We are currently estimating our full end-to-end testing to be finalized in mid-Sept, pending audit findings and fixes.
Bridging team
As detailed in our previous longer-form posts, we’re building Picasso and Pablo with cross-chain modularity in mind. Simply put, this means that whilst our chain and DEX will launch without Centauri bridge, they are being built to support and leverage our trustless IBC<>Substrate tech.
Starting with the work to bring IBC to NEAR, we are seeing strong progress after implementing ‘ibc-transfer’ and unit tests for the router, as well as mirroring substrate storage logic and ibc transfer tests.
NEP-364 has been approved, and our team are currently discussing details on the implementation related to gas fees. In addition, we are working on a new proposal to extend the NEAR smart contract standard to be IBC compliant, which we are looking forward to sharing furher details soon.
On the IBC front, ‘ICS20’ within the ibc pallet has undergone bug fixes, and our latest tests have progressed successfully. For ibc-rs, the Beefy light client has been modified to track a single parachain making it more inline with the existing ibc standards. Within ibc-go, we’ve successfully created clients for both chains, and parsed IBC events from ibc-rs. We have created 3 PRs ino cosmos relayer repo for: {Key store, Event Parser, Chain Processor}.
We are migrating code to the new Go relayer implementation, breaking the work into smaller PRs and creating them upstream, focusing on multiple dependencies like go-substrate-rpc library and ibc-go
Our design team continues to develop the UI, with the below screenshot displaying the in-progress development of the initial wireframes. We will continue to display the various iterations before we consider the design final.
XCVM
The XCVM team remains focused on our second demo for Cosmoverse in September, where we additionally reveal our new developer interface and explorer. In the past weeks, we have onboarded a new Senior Frontend Engineer to the XCVM team, who has been working alongside our design team to build these new visualization tools.
The spec for XCVM continues to advance, with the most recent updates pushed here.
Through this, users (with a strong developer focus), have complete, easy, and filtered-enabled access to transaction details on the overview page; and for further visualization, XCVM holds pages for relayer details and an explorer for transactions data. The explorer also includes an innovative transaction visualization feature: a graphic stepper tree where the user can visualize the full orchestration process, no matter how complex the operation is.
Our focus on development continues to be centered on the last details and review around the CosmWasm VM pallet, the frontend and data structure, whilst moving forward to blockchain integration. Our CosmWasm pallet has entered our broader integration and audit pipeline where we prioritize work across all of our product streams — as our core Picasso and Pablo pallets are close to completion, we will proceed with the audit of CosmWasm too.
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
Dev Log #11 was originally published in Composable Finance on Medium, where people are continuing the conversation by highlighting and responding to this story.
