Thanks to everyone for input on Frames features last week! We are working on expanding "mint with Warps" to a more general "pay with Warps" that will support more transaction types.

👇 Below are a couple follow up questions that will help us prioritize.

To use "Pay with Warps," your contract must support some kind of "unauthenticated delegation," i.e. not depend on msg.sender. 

Examples:
- An NFT contract with a mintTo function
- An airdrop claim with a claimFor function
- A dex swap that accepts a to address

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

If your contract doesn't support this today, could/would you change it? 

In some cases, you can use a router contract or multicall to support this use case without directly changing your contracts.

If your contract doesn't support this today, could/would you change it? 

In some cases, you can use a router contract or multicall to support this use case without directly changing your contracts.

https://www.weponder.io/farcaster/surveys/586

To use "Pay with Warps," your contract must support some kind of "unauthenticated delegation," i.e. not depend on msg.sender. 

Examples:
- An NFT contract with a mintTo function
- An airdrop claim with a claimFor function
- A dex swap that accepts a to address

https://www.weponder.io/farcaster/surveys/584

Aspiring mad scientist,
support team @ /rainbow