BeamPay

We use eip7702 to provide metadata to simple ERC20 token transfer and to safely validate it and provide a trusted event to backends and frontends. Main reason is that ERC20 transfer doesn't have any additional information field, needed to pass data like payment or item id. Basically you need to decode it into value or make more that one transaction. We provide a single-transaction seamless solution both for single-chain and multichain cases. Also eip draft is created for discussion as it may be the part of a new standart

Heyhey! Our main part are smart-contracts. Firstly we tested our conceptual contracts in Huff, and after it became more complex, we made it in Solidity. Our smart-contracts use transient storage to keep track of payment data ("to", amount and payment id) in the one eip7702 batched transaction. Also we forked metamask delegation framework and simplified their delegator contract for our use on Flow and Zircuit (no wallet currently provide eip7702 on these chains). We made our own chrome extension, which is a eip7702 wallet for our payment system. It can develop into separate wallet, or be integrated in current ones (we hope they move forward better eip7702 adoption). Also we added crosschain option with Circle's CCTPv2, still using eip7702 for batching and their hook for transferring information to dest chain