GM Wallet

OPEN SOURCE / GM WALLET

Our know-how,your starting point

GM Wallet is opening up the technology, code and solutions built over years of research and real-world practice, so new ideas can start from what already works. Together with developers, we are improving on-chain infrastructure and moving the industry forward.

_> SHARE. BUILD. ADVANCE.

EPUSDT

Multi-chain paymentsfor more real businesses

An open multi-chain payment tool for merchants and developers. It watches for on-chain payments and sends automatic callbacks, bringing payments into your business while it keeps improving through open collaboration.

_> ON_CHAIN_SIGNAL

  1. 01

    Multi-chain checkout

    One merchant payment flow across different networks.

  2. 02

    Automatic monitoring

    Watches on-chain deposits and links payment status to orders.

  3. 03

    Result callbacks

    Calls back on arrival so payment results flow into your business.

7702 Contract

Batch operations,smoother on-chain experiences

An open-source account contract based on EIP-7702. It supports signature-authorized batch calls and sponsored gas, giving accounts more flexible execution and fee settlement.

  1. 01

    Batch signing and execution

    One business signature covers multiple calls. Calls run atomically in order, and if any call fails, the whole transaction reverts.

  2. 02

    Gas abstraction

    A sponsor pays native gas. Fees can be subsidized by the platform or repaid in a designated ERC-20 token.

  3. 03

    Authorization and policy

    Signatures bind calls, fees and expiry. Nonces prevent replays, while allowlists and fee caps constrain sponsorship.

GM Wallet Core

Add wallet capabilitiesto your product with ease

Built in Rust, it opens up the low-level implementation of key management, signing and the data layer, so developers can reuse proven capabilities, focus on product innovation and help improve wallet infrastructure together.

  1. 01

    Security layer

    Manages wallet private keys and account identity at the lowest level, providing keys for account control and transaction signing. It centralizes key operations, draws a clear line between core capabilities and business calls, and spares apps from reimplementing security logic.

  2. 02

    Signing layer

    Builds and signs transaction data, connecting business requests, key capabilities and on-chain execution rules. Signing flows live in one layer, so apps reuse the underlying implementation and integrate transfers and other on-chain interactions with less effort.

  3. 03

    Data layer

    Organizes and provides access to account, asset and transaction information with one consistent data model. Apps build display, queries and state management on shared structures instead of repeatedly adapting to low-level data differences.

Open collaboration, shared progress.

Use, review and improve these projects, share your experience, raise issues and contribute code. Let practices from different teams inspire each other and keep our shared technical foundation improving.

Contribute on GitHub