Content
@
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
87 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.
2 replies
0 recast
5 reactions
grin
@grin
what do you do for ppl who have many connected addresses? is there a primary address, or plans to designate one?
1 reply
0 recast
1 reaction
Colin
@colin
Can you update https://www.notion.so/warpcast/Frame-Transactions-Public-9d9f9f4f527249519a41bd8d16165f73?pvs=4? I'm using that as the source of truth
1 reply
0 recast
0 reaction
⚪️ cooper 🎩 ↑
@cooperray
thank you for working on improving frame txns 🙏🏽 420 $degen
0 reply
0 recast
1 reaction
agusti
@bleu.eth
can u guys make token gated chats make an api call that's not to OpenSea? now if you have an NFT as Hidden on opensea, the token gating feature is nerfed. and won't let you in.
1 reply
0 recast
0 reaction
patxol 🔷 anser.social
@patxol.eth
420 $DEGEN
0 reply
0 recast
0 reaction
Franklyn 🎩Ⓜ️🟣
@franklynr
Great!!! 777 $DEGEN
0 reply
0 recast
0 reaction
0xHashbrown🎩🍖✋
@0xhashbrown
1111 $DEGEN 🖼️
0 reply
0 recast
0 reaction
