The Frame Transactions spec is ready for feedback! 

Please share your thoughts in replies, comments or DMs. Your feedback is very important to help us get the design right.

The Frame Transactions spec is ready for feedback! 

Please share your thoughts in replies, comments or DMs. Your feedback is very important to help us get the design right.

https://www.notion.so/warpcast/Frames-Transactions-Public-Draft-c2e0d3210d684b4cb7803de1810db36d?pm=c

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

my hot take is that transaction urls should not be in the spec. adds a lot of complexity to what should be relatively straightforward tool for frames to use and is a centralizing force

only domain attribution and who shared the frame should be presented to the user in client - no tx simulation, wallets already to this

cypherpunk wannabe, engineer working on @frames /open-frames /opencast
https://stephancill.co.za create stories at https://stories.steer.fun

- i'd be curious to see what the process and criteria to get onto the trusted contracts list is. ofc this is warpcast specific but if it's public i expect the list to be used by most clients so it's going to be an important precedent to set

- client confirmation screen is information overload and tx sim is redundant

What’s being centralized here? 

There’s no restriction on what domains can serve transactions. 


Tx simulation is encouraged not required. Up to clients to decide.