t3rn Development Update 3

The t3rn development team has been working hard to prepare our product for new integrations, developer adoption and a public testnet release. 

Numerous upgrades have been implemented, such as live data for the XDNS, relayers that allow the circuit to communicate with substrate-based chains, refactoring our Side Effect Protocol, as well as pallet updates.‍

Technical Documentation

A defined onboarding process for developers is being introduced with our new documentation. Our efforts so far have focused on Gateway registration by detailing multiple steps, from installing and importing dependencies to building and submitting transactions. Our documentation will be released in the new year, with topics such as Side Effects, upgrades on Circuit pallets, XDNS and additional features related to integrations all covered.

Pallets update to Polkadot v0.9.12

‍For continuous maintenance and compatibility with forthcoming testnets, we upgraded the Circuit Pallets, i.e. XDNS, Contracts Registry, Execution Delivery.

Relayers for Circuit-Substrate based chains 

The first implementation of relayers that communicate Circuit with Substrate-based chains is ready. The implementation is written in JavaScript. Relayers listen to the Side Effects emitted by the Circuit, form the request by the protocol messages and submit them to the target chains. Next, relayers wait for the events confirmation on the target chain and, alongside the storage proof of the corresponding events, pass the data back to the Circuit.

XDNS now works with live data‍

The XDNS component of the t3rn circuit has been finalized and can be used with live data. This goes hand in hand with the activation of the register gateway extrinsic, which will happen soon, allowing for early developer experimentation. 

The integration of XDNS has been tested with Westend testnet, with which Circuit can communicate by sending transfers and confirming the associated events inclusion in the Westend chain. 

Emitting on-chain Side Effects

Circuit now has the simplified version of Execution Delivery pallet which allows users to submit the side effects directly for execution. The Side Effects Protocol has been refactored to follow the following steps:

1. Validate the arguments of incoming side effects against the target's ABI (address length, value size etc).

2. Create the cross-chain transaction order including the side effects.

3. Wait for relayers to pass the side effects to the target chains and get the required proofs.

4. Implement the API entry for side effects confirmations that checks the execution and inclusion proofs. 

‍

Huge strides are being taken at t3rn and momentum behind the project is growing, 2022 promises to be an incredible year. 
Be sure to watch updates on our social media and blogs.

👉 Subscribe to our newsletter: Join 15,000 subscribers for exclusive monthly updates and insights, directly from Maciej Baj, founder & CTO of t3rn. - no spam, unsubscribe anytime.