In the world of Web3, users often find themselves juggling multiple addresses across different chains. This creates significant challenges when it comes to making payments and engaging with decentralized applications (Dapps). Users are forced to navigate through bridges repeatedly, create new identities for each chain, potentially purchase different decentralized identifiers (DIDs) on various chains, and manage native tokens on each individual chain. Consequently, even a simple transaction requires users to jump through multiple hoops. Additionally, the absence of a request transaction feature in Web3 currently renders asynchronous payments and recurring payments impossible.