A place for developers to talk about building on Farcaster.

/dev

How this works

- Standard App Store IAP APIs—including the 30% fee

- Warpcast app generates a transaction( since the user has their Farcaster mnemonic loaded)

- Once IAP is confirmed, we use a Warpcast backend service that has some ETH in wallet to pay for the txn

How this works

- Standard App Store IAP APIs—including the 30% fee

- Warpcast app generates a transaction( since the user has their Farcaster mnemonic loaded)

- Once IAP is confirmed, we use a Warpcast backend service that has some ETH in wallet to pay for the txn

https://warpcast.com/dwr.eth/0x247ccf

Is this 4337 (you're acting as bundler), or standard relay?

/bettik founder /outercorps stalwart | ex-binance, ex-celsiusX

Sounds like relayed metatransaction, so since the user isn't msg.sender, you're mostly limited to your own contracts or ERC-2771 compatible contracts?

point being - you aren't able to simply allow us to call Uniswap, etc?

Perhaps you can use the EOAs as owners on a 4337 wallet & WC sends signed UserOps to a bundler?

EOA + basic Warpcast backend service with an Ethereum hot wallet in AWS (we top up the wallet occasionally)