Live now
Frost is not a proposal. A public testnet is running today, with the services you need to use it.
Endpoints
Section titled “Endpoints”- RPChttps://rpc.frostfi.net
- Chain ID8141
- Explorerhttps://explorer.frostfi.net
- Faucethttps://faucet.frostfi.net
- Swaphttps://swap.frostfi.net
Try it in a few minutes
Section titled “Try it in a few minutes”-
Create a post-quantum account. Generate an ML-DSA-65 key with one of the SDKs or the
frametxCLI. The address is derived offline, so you have one before anything exists on chain. Create a wallet walks through it. -
Fund it from the faucet. Paste the address; the funds arrive at an address with no code, which is normal. The account does not exist yet and does not need to.
-
Send a transaction. The first send carries a deploy frame that creates the account and pays for that out of the faucet funds — no sponsor, no activation step. Send a transaction covers transfers and contract calls.
-
Watch it land in Frostscan. The receipt shows the VERIFY frame that checked your signature and the SENDER frame that did the work, each with its own status and gas.
-
Trade on FrostSwap. A real Uniswap v3 deployment, driven from an account whose signatures are post-quantum. From the pool contracts’ point of view you are an ordinary address.
The Quickstart does the first three steps end to end, in TypeScript or Python.
MetaMask, ethers, and stock viem can read Frost like any EVM chain but cannot sign for a post-quantum account — they cannot produce an ML-DSA signature. That is a property of the cryptography, not a missing integration, and it is why the SDKs exist. Two native wallets, for iOS/macOS and as a browser extension, are listed on the Ecosystem page.
It is a testnet
Section titled “It is a testnet”FROST on this network has no value, and the faucet hands it out for free. Use it to build, integrate, and break things. Every contract on the Ecosystem page — the DEX, the token suite, the predeploys — is deployed and source-verified on the chain you connect to above.
Written against the chain as deployed
Section titled “Written against the chain as deployed”The second sentence of the home-page card is a commitment about these documents, not the chain, and most of it is enforced mechanically.
Every consensus-critical value the site states — the verifier prices, the
frame-transaction validity caps, the precompile addresses, the FIPS 204
encoding sizes — lives in the site’s data files, and the pages render from
them rather than restating the numbers. On every change, and daily whether or
not anyone is editing, a check asserts those values against the chain’s source
repository and against the live RPC endpoint: the chain ID, that
eth_maxPriorityFeePerGas is zero, that the predeploys have the code the docs
say they have, and that the precompiles fail the way the docs say they fail.
When the chain and the docs disagree, the check fails and the change cannot
merge. Code examples are written against the SDK sources checked out alongside
the site, and every API name in them is checked by hand against those sources.
The editorial rule is the same in spirit: the site documents the chain as it is, not how it got there. Retired implementations, superseded designs, and alternatives that were considered but not deployed are left out, so that every page can be trusted to describe something currently true. The Design section explains why the chain is the way it is; nothing here describes something it used to be.
Found a mismatch? Tell the team, and it will be fixed at the source rather than on the page.
- Quickstart — from nothing to a funded post-quantum account that has sent a transaction.
- Connect to Frost — network parameters and exactly what the public endpoint serves.
- Ecosystem — everything deployed on Frost today.