Content
@
https://warpcast.com/~/channel/frames
0 reply
4 recasts
4 reactions
horsefacts 🚂
@horsefacts.eth
Frame tx requests now receive the user's connected wallet address! 🎉 Warpcast now includes an "address" field in the frame message for requests to load transaction calldata. This is the *currently connected wallet address* at request time (the same one we use for simulation). More details 👇
8 replies
4 recasts
82 reactions
horsefacts 🚂
@horsefacts.eth
1️⃣ Address is only present in requests to the tx action "target", not other request types. 2️⃣ We are NOT including address in the post-tx callback. If you need to check this, use the transactionId to look up the from address. 3️⃣ Upgrade to Hubble 1.10.11 to read the address from frame messages.
1 reply
0 recast
5 reactions
0xfeatr
@featr
btw, wondering why is the address not included in the post-tx callback? Using the txId could present issues, as it usually takes some time for a tx to be included in block explorers/etc. Having some "fabricated" (say 3s) timeout before fetching for the tx solves that, but the 5 second limit makes this not reliable.
0 reply
0 recast
0 reaction
