Author: Weilin, PANews
A few days ago, Skate co-founder and CEO Siddharth Lalwani demonstrated the latest achievements of the project at X: participating in the prediction market Polymarket betting on Telegram without switching chains or transferring assets across chains.
According to the official introduction, Skate is a universal application layer that enables applications to run on thousands of chains through a single state. Skate monitors the state of each network, and when a user wants to participate in a certain cross-chain operation, the user signs an "intention". These intentions are monitored by executors, who execute them in real time. For example, if a user wants to transfer $10,000 across chains, the executor will seek to obtain liquidity from all available networks, thereby facilitating the transaction and actually unifying liquidity.
This relies on a hub-and-spoke architecture and leverages the EigenLayer to achieve fast finality. This also means that any network can be easily integrated because Skate monitors their state and then connects them to the entire network.
In this article, PANews has compiled a graphic and text compilation of Siddharth Lalwani’s latest workflow for connecting Telegram and Polymarket so that readers can better understand this innovation.
Siddharth Lalwani, co-founder and CEO of Skate:
We are building a test application internally to enable Polymarket prediction markets on TON. A user can interact with Polymarket directly within Telegram, through a Telegram mini-app. He can express his intention, such as he wants to bet $10 that Trump will win the US presidential election, and the whole process will be automatically executed for him. He does not need to switch chains or bridge assets across chains.
Test application introduction:
For the user, he is still inside Telegram, interacting through the mini-app. His assets are still on TON, he just needs to express his intention to bet that Trump will win the election. The assets will enter an intermediate stage and be in the periphery contract of the TON blockchain.
In general, the kernel represents the core application logic and application state, while the periphery represents the user interaction logic. A periphery is deployed for each chain that the user interacts with, but for the same application, there is only one kernel application, which is why there is a single application state. Users express their intentions within the Telegram mini-app on TON, and this intention is picked up by the executor and executed on the kernel deployed on Skate. This kernel currently basically stores the mapping of the proxy contracts, multi-signature wallets and their TON addresses deployed by users on Polygon, and enables all callbacks from TON to Polygon.
Once a callback is needed, such as when a user places a bet, the callback goes through EigenLayer, and using the high economic trust obtained from pre-confirmed AVS, the callback creates a proxy contract for the user and places a bet on Polymarket.
Now, let's say I'm inside Telegram, interacting with it through the test app we developed, and I'm betting that Michelle Obama will win the US presidential election. I don't think she's in the running, but I'll show you real quick. We're going to connect our Tonkeeper wallet to the app, which is a wallet I created with some USDT and TON for gas. Let's say we bet 0.1 USDT that Michelle Obama will win the election. This will generate a bet graph. That's all you need to do as a user.
The entire user process is executed in the background:
Now, I will quickly demonstrate what is actually happening in the background, using the blockchain explorer. I just interacted with the user's wallet and quickly opened the TON blockchain explorer to view the transaction.
Here it shows 0.1 USDT transferred to the contract. This is the intermediate stage, now the intent to bet on Polymarket is generated for the user. The executor picks up this intent and executes it on the contract containing the core logic.
This is the core contract on the Skate chain. This core contract is responsible for maintaining the status of users interacting with Polymarket, which is accomplished through the Skate stateless application model.
You can see that 47 seconds ago, the kernel part of the process intent was called. For each callback from the Skate chain to any chain, a task is created and the task ID is associated. The AVS operator checks the task ID and makes a proof. Once enough proofs are received, the callback is executed on the target chain, in this case Polygon.
So let's take a quick look at the gateway contract on Polygon, all the interactions from the EigenLayer AVS, the pre-confirmations, will happen on any stateless application perimeter deployed here. Do a quick refresh. You can see that 1 minute ago, a transaction was executed for the user. This time 0.1 USDT was bet on behalf of the user. Let me quickly explain what actually happened here.
First, a multi-signature wallet is created for the user. We automatically generate this address and store it in the SkateChain mapping so that agents can create on behalf of users and update their TON addresses in the mapping.
Once the proxy is created, the next data calls that are performed are the different approvals that you have to give to the Polymarket contract. In this case, it is the approval that must be given to the CTF contract and some other interactions on Polymarket. Once the approval is completed, what happens next is that we first remove the ownership from the UA (User agent) of the wallet that created the multi-signature, and then transfer the ownership of the multi-signature to the EigenLayer AVS. I think this is the most elegant part of our design.
Now, basically, all the proxies that are interacting on behalf of users on different chains are owned by pre-confirmed AVS. If we have a baseline economic trust of $5 billion when we go live in production, that basically determines the cost of moving any asset. So, if you want to attack the system, the economic cost is this.
Therefore, any movement of assets will occur after more than $5 billion worth of collateral is secured. Then, order matching on Polymarket will be completed.
I can quickly show you what's happening on a multi-signature contract. This is the multi-signature contract that was created for this TON user. First, a provider provides him with some assets for settlement. The provider can basically keep rebalancing between their inventory to get TON assets, and eventually they will get assets on Polygon. You can see that the order matching has been executed, basically placing a bet on Polymarket on behalf of the user.
After that, the callback happens on TON and the user settles there. The whole process is completely seamless and all custody is taken care of by AVS, which provides us with a very high economic trust and I would say makes the whole system trustless. I just want to quickly record it and help you understand what this stateless user experience looks like.
Now, basically, in this way, we can enable these applications on any blue chip EVM application or non-EVM chain like TON, Solana. More importantly, we can enable this new asynchronous application design pattern, with a single application state. It feels like you are running the same application on all chains, but at the user level, he doesn't need to worry about switching chains. Even at the application developer level, they don't need to worry. I'm on this particular chain, but now there is a new chain offering airdrop incentives, and I want to migrate all my users over. Now you can run your application on all chains and get the network effects of all ecosystems.
“We’re really excited to make these apps available to you and look forward to your interaction with them. I think we still have a few details to work out. We’d love to hear your feedback and get in touch with any teams that are interested in building in this new design space. We’re really excited to share this with you and look forward to the community’s feedback,” said Siddharth Lalwani.
