The experience design when interacting on the Miden network is very interesting. Executing transactions locally is like using a phone as a controller to play games, with response speeds that are off the charts. But here's the problem — after the transaction is completed, a super high-definition complete proof video needs to be generated immediately as an on-chain certificate, which is the process of generating a ZK proof. Using mobile Computing Power to handle it? Basically unrealistic, either it lags or it crashes directly.
The bottleneck lies in the computing power. The solution is actually very clear: introduce the concept of cloud rendering farms. Networks like Gateway act in this role, specifically responsible for handling heavy computation tasks. Local quick interaction + on-chain parallel proof generation not only ensures the real-time nature of user experience but also alleviates the resource pressure of ZK proof computation. This architecture allows for a good separation between light clients and heavy computation tasks.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
7 Likes
Reward
7
4
Repost
Share
Comment
0/400
AirdropHunterWang
· 12-23 05:50
Running ZK proofs on a mobile phone? Haha, what are you thinking? Just explode it!
View OriginalReply0
CounterIndicator
· 12-23 05:42
The local quick interaction on the phone is indeed enjoyable, but to prove the generation, we have to rely on Cloud Mining to save the day. This architectural approach is quite practical.
View OriginalReply0
AirdropNinja
· 12-23 05:35
Local quick + cloud rework, this idea is indeed brilliant, finally someone has figured this out.
View OriginalReply0
Layer2Arbitrageur
· 12-23 05:32
yo this gateway offloading actually makes sense from a gas optimization angle... but ngl the real question is MEV extraction during proof generation. who's verifying the validators aren't sandwiching txs in that cloud compute gap? 🤔
The experience design when interacting on the Miden network is very interesting. Executing transactions locally is like using a phone as a controller to play games, with response speeds that are off the charts. But here's the problem — after the transaction is completed, a super high-definition complete proof video needs to be generated immediately as an on-chain certificate, which is the process of generating a ZK proof. Using mobile Computing Power to handle it? Basically unrealistic, either it lags or it crashes directly.
The bottleneck lies in the computing power. The solution is actually very clear: introduce the concept of cloud rendering farms. Networks like Gateway act in this role, specifically responsible for handling heavy computation tasks. Local quick interaction + on-chain parallel proof generation not only ensures the real-time nature of user experience but also alleviates the resource pressure of ZK proof computation. This architecture allows for a good separation between light clients and heavy computation tasks.