Content
@
0 reply
0 recast
2 reactions
Dan Romero
@dwr.eth
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
9 replies
3 recasts
26 reactions
sean
@swabbie.eth
Is this 4337 (you're acting as bundler), or standard relay?
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
EOA + basic Warpcast backend service with an Ethereum hot wallet in AWS (we top up the wallet occasionally)
2 replies
0 recast
1 reaction
sean
@swabbie.eth
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?
2 replies
0 recast
0 reaction
Royal
@royalaid.eth
Super curious about that hot wallet management 👀. I'm always paranoid that as soon as I have a private key in memory that I have control over its comprised 🤣
0 reply
0 recast
0 reaction