Varun Srinivasan on Warpcast

Content pfp

0 reply

20 recasts

20 reactions

Varun Srinivasan pfp

Varun Srinivasan

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

61 replies

77 recasts

352 reactions

Varun Srinivasan pfp

Varun Srinivasan

Our goal is to collect feedback over the next 24-48 hours and then finalize a spec before the developer call on Thursday. h/t @horsefacts.eth for the heavy lifting and @deodad @gt and @sanjay for design input.

0 reply

1 recast

26 reactions

Cameron Armstrong pfp

Cameron Armstrong

actually quick question - before going live can y'all make a hidden/dev page in the warpcast mobile app that acts as a playground for testing transactions/how things appear/etc Feels more important now that the stakes are higher than just raw frames

2 replies

0 recast

20 reactions

Salvino Armati ↑ pfp

Salvino Armati ↑

built different

0 reply

1 recast

19 reactions

six pfp

So on mobile, users need to have the Coinbase Wallet app for it to work?

2 replies

0 recast

4 reactions

Henri Stern Ꙫ pfp

Henri Stern Ꙫ

Left some notes around transaction format and CAIP 10 as well as how to set up UI standards that can work across FC clients so detecting malicious frames becomes easier for users. In general would be very useful to have a Frames reporting site to quickly flag malicious ones

0 reply

0 recast

5 reactions

Henri Stern Ꙫ pfp

Henri Stern Ꙫ

Your excalidraw game is on another level @v !

1 reply

0 recast

2 reactions

JB Rubinovitz ⌐◨-◨ pfp

JB Rubinovitz ⌐◨-◨

We should have an redteam contest for this on Farcaster

0 reply

0 recast

4 reactions

David Furlong pfp

Not a fan of this proposal. It adds a lot complexity to the spec and doesn't meaningfully improve over the current problems of crypto UX: speed, safety, simplicity. The flow has significant friction and low conversion for the most common txs in social: small mints/fees, so those txs will find other ways to convert.

1 reply

0 recast

3 reactions

Stephan pfp

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

1 reply

0 recast

1 reaction

jacopo pfp

since trusted domains can unknowingly allow malicious transactions, doesn’t it defeat the purpose of maintaining a list?

1 reply

0 recast

1 reaction

David Furlong pfp

I'm betting less than 10% of transactions in frames clients will happen via this method in a 6 months. Too many steps, too slow, too unsafe (still has risk beyond the cost of the current transaction). 95% of transactions will be < $10 and users just want to press a button and pay the $ and get the thing, no risk.

0 reply

0 recast

1 reaction

albert pfp

wait this spoof scenario seems pretty bad? > The figure below shows a malicious frame attempting to spoof the information in Figure 1, using an unrelated but legitimate token contract with a higher mint price. this means i'd be minting a rug pull token right?

1 reply

0 recast

1 reaction

Linda Xie pfp

@pirosb3 get in there :D

0 reply

0 recast

1 reaction

albert pfp

0 reply

0 recast

1 reaction

rafa pfp

Does this mean you need to go through the whole tx confirmation in an external wallet? Seems wayyyyy too high friction for 95% of micro-economy payments. There needs to be a better way to manage this within app without leaving

0 reply

0 recast

0 reaction

Manuel pfp

@manuelmaccou.eth

Thanks for sharing this early! Does this spec mean that only approved apps can initiate transactions? Or since it mentions approved contracts, I’m assuming that a library of contracts could preapproved like certain OpenZeppelin or thirdweb contracts? Trying better understand the whitelist part

0 reply

0 recast

0 reaction

Vladyslav Dalechyn pfp

Vladyslav Dalechyn

What if a user could pay for anything with Warps? Have Frame Devs to deploy a contract that would implement a specific interface that would have "receiveUSDC(uint256 amount)" that Warpcast client would call itself and have a developer to implement anything on-chain related in the contract itself? 1/n

1 reply

0 recast

0 reaction

Samuel pfp

@samuellhuber.eth

the storage renting example is neat, if one wanted to add a tipp say for caststorage.com or so to get referral revenue then one would need to host the tx themselves and include both the rent storage + tip I assume?

0 reply

0 recast

0 reaction

Noah Bragg 🔥 pfp

Noah Bragg 🔥

Looking great! Very thoughtful with all the safety measures.

0 reply

0 recast

0 reaction