Physical gold.
Managed directly.
macOS · Windows · Linux · v2.4.1 · Open-source
Each Pax Gold (PAXG) token is backed by one fine troy ounce of gold, stored in LBMA-accredited vaults in London. If you own PAXG, you own the underlying physical gold — held in custody by Paxos Trust Company, a regulated US trust under NYDFS oversight.
PAXG Wallet is built around four principles that set physically allocated gold apart from every other form of exposure.
Every token corresponds to individually identified LBMA Good Delivery bars. Enter any address and retrieve bar serial numbers, fineness, and weight — directly from the Paxos allocation API, inside the wallet.
Private keys are generated locally, encrypted with AES-256, and stored only on your device. No server, no account, no cloud sync. Compatible with Ledger and Trezor for hardware-level signing.
Send PAXG to any Ethereum address. Transactions settle on-chain — final, auditable by anyone, anywhere. No T+2, no intermediary, no settlement risk. Verify independently on any block explorer.
PAXG is issued by Paxos Trust Company, chartered under New York State law, regulated by the NYDFS. Monthly attestation reports confirm gold holdings match token supply — published publicly.
Free. No account required. Open-source.
Not all gold exposure is equal. See how PAXG compares to the alternatives.
| PAXG Wallet | Gold ETF | Exchange | Physical bar | |
|---|---|---|---|---|
| Allocated — specific bars | Yes | Varies | Pooled | Yes |
| On-chain ownership | ERC-20 | No | No | No |
| Keys in your control | Always | N/A | Custodied | Physical |
| Settlement | Instant* | T+2 | T+0–1 | Days |
| Bar serial verification | Built-in | No | No | Manual |
| Minimum holding | 0.01 oz | 1 share | Varies | ~400 oz |
| Custody fee | None | 19–40 bps/yr | Varies | 0–10 bps/yr |
On-chain PAXG transfers between Ethereum wallets settle near-instantly. New token issuance from Paxos typically completes same-day; larger orders may settle the next business day.
Read the full documentation, browse the open-source codebase, or open an issue on GitHub.
GitHub →Run shasum -a 256 <file> on macOS/Linux or certutil -hashfile <file> SHA256 on Windows to verify.