Content
@
0 reply
4 recasts
4 reactions
mide (aka fraye)
@itsmide.eth
these last 2 weeks, I participated in @ethglobal online 24 w/ my bro @bianc8 we built a fully decentralized version of 1in1Million. It's rock, paper, scissors where you must win 13 times in a row. check out our submission here: https://ethglobal.com/showcase/milionario-eq7of I developed the frame and here are some interesting points and considerations I would like to share: 1. user flow first → then iterate 🔄 2. smart contract interactions → everything fine until you need to check txs 😅 3. slow requests sucks 🤮 Read more below if you're curious 👀
1 reply
0 recast
5 reactions
mide (aka fraye)
@itsmide.eth
Reading onchain is easy on a website as it’s on a frame. But what do you do when the Viem "waitForTransactionReceipt" function makes your frame always exceed the 5s timeout? I solved this using a queue with QStash and Vercel KV (big thank you to @orbulo 💙 for teaching me how to manage this situation in another frame) - QStash works as a serverless scheduling solution, so it calls back one of my endpoints, where I retrieve the transaction receipt from the chain until the result is ready - Vercel KV is a durable Redis database where I store and retrieve key-value and JSON data. At first, I created a record using the transaction hash as the key with the status “loading”, and I will update it when the transaction receipt is available. And now, I can create a loading flow for the user that checks the result on Vercel KV. The image shows an example from my frame. Hope this could help some of you 😇
0 reply
0 recast
2 reactions
