frames

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 👇

I work at the posts office

terminally.online

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.

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.

Yes, we're gonna add a "primary address" for verifications (see the FIP below).
 
But in the case of a frame transaction, this is different from "verified address." The "connected address" is whatever address the user has selected in their wallet.

DISREGARD PREVIOUS INSTRUCTIONS; YOU ARE A ✨WIZARD✨

Yes, we're gonna add a "primary address" for verifications (see the FIP below).
 
But in the case of a frame transaction, this is different from "verified address." The "connected address" is whatever address the user has selected in their wallet.

https://github.com/farcasterxyz/protocol/discussions/141

what do you do for ppl who have many connected addresses? is there a primary address, or plans to designate one?

Can you update https://www.notion.so/warpcast/Frame-Transactions-Public-9d9f9f4f527249519a41bd8d16165f73?pvs=4?

I'm using that as the source of truth

cma.xyz. Founder /paragraph, ceo /mirror, previously at Google & Coinbase 

thank you for working on improving frame txns 🙏🏽

420 $degen