Proposal: x/wauth module
Native Authorization-Based Transfer Module for the Cosmos SDK Summary This topic proposes `x/wauth` (WAuth => “with authorization”), a new Cosmos SDK module that introduces off-chain-signed, on-chain-settled token transfers. The design is semantically equivalent to Ethereum’s EIP-3009 (`transferWithAuthorization`) but implemented as a first-class Cosmos SDK module with no EVM dependency. A working reference implementation targeting `cosmos/evm` is available and production-ready. Motivation The Cosmos SDK’s transfer model requires the token sender to submit and pay for every transaction. This is the right default, but it makes an entire class of application patterns difficult or impossible to implement cleanly: • Meta-transactions / gas abstraction : end users should not need to hold the native fee token to interact with an application. • Delegated and pull payments : a recipient or relayer should be able to settle a pre-authorized payment without requiring another round-trip to the sender. • Machine-to-machine and API-triggered payments : services built on the x402 pay-per-request standard need to settle blockchain payments in response to HTTP events, not…
Excerpt (1195 of 8872 characters). Read the whole post on the forum ↗
Looks like a profound work, but still some question: I guess the initiator/receiver that will trigger the release needs at least an already initialized wallet (with sequence number). This might turn out a major problem in real environment: The service won’t work out of the box, or at least will be limited to the small batch of current cosmos users. I created a similiar concept using cosmwasm too, that allows usual webapps to hand out Tokens to users. The webapp doesn’t need to run a local signing or broadcasting client in the backend, its just creating the message that will trigger the escrow contract to release the funds mentioned in the tx Here is the schematics: image 1767×760 135 KB mintscan.io Mintscan Interchain block explorer and data analytics for sovereign blockchain networks. WebApp Composes the voucher message and decides the Token amount that shall be sent to the user The ECDSA signature is derived from this execution message body and is being attached below The WebApp holds the ECDSA private key in his .ENV Variable only, no backend client necessary The contract holds the ECDSA public key only -it checks…
Excerpt (1197 of 1513 characters). Read the whole post on the forum ↗
Hi! Thanks for sharing this.
Can I ask what you’re using it for today, or plan to use it for?
Thank you for the interest!
We plan to use it as agentic payment option for Gurufin chain. It is built on top of cosmos/evm repository
@rattadan That is an interesting alternative! Meanwhile, we are working on fixing the PubKey issue on chain for new accounts