FAQ
About Fast
What is Fast?
Fast is payment infrastructure for programmatic transactions. It enables agents, APIs, merchants, and services to request, authorize, send, and settle payments — fully programmatically, across both crypto and fiat rails. It processes payments, including agentic payments and micropayments, in a massively parallel manner.
Fast delivers sub-second finality, near-zero fees, and uncapped throughput that scales with the rising agent economy. Fast needs no blocks, no miners, and no consensus protocol. Instead, all transactions are concurrently processed and settled.
Is Fast a blockchain?
No. Fast is fundamentally different from blockchains.
Blockchains serialize all transactions into an ordered chain of blocks, even when those transactions have nothing to do with each other. This creates a bottleneck. Fast observes that most transactions are independent — Alice paying Bob has nothing to do with Carol paying Dave — and processes them in parallel. The result is orders of magnitude more throughput without sacrificing security or decentralization.
How fast is Fast?
Throughput: Acheived 200,000+ transactions per second on standard hardware
Finality: Sub-100ms for a single transaction to be irreversibly settled
These numbers are achieved without specialized hardware. Validators perform only signature operations — all complex computation happens off-network.
How does Fast prevent double-spending without ordering transactions?
Each account has a nonce — a sequence number that increments with every transaction. Validators enforce per-account ordering: they will not sign a second transaction from the same account at the same nonce. This makes double-spending impossible without compromising a quorum of validators. Transactions from different accounts are processed in any order because they are weakly independent — the final state is the same regardless of ordering.
Is Fast decentralized?
Yes, but not at the cost of what a blockchain takes. Because Fast validators do not communicate with each other, adding more validators does not slow down the network. Every validator independently processes transactions and converges to the same state. Anyone can run a validator on commodity hardware.
For Developers
How do I get started?
Install the SDK and send your first payment in under two minutes:
The SDK provides Signer, FastProvider, and TransactionBuilder for building, signing, and submitting transactions. For complete setup instructions and runnable examples, see the Fast SDK on GitHub.
No API keys. No account registration. No configuration files.
What's the learning curve?
For payments — minimal. Use the CLI for quick interactions (fast account create, fast send, fast info balance) or the SDK for programmatic access (Signer, FastProvider, TransactionBuilder). The SDK handles all the complexity of signing and network communication. If you can call a function, you can use Fast. See the CLI README and SDK README for details.
For advanced use cases — custom tokens, cross-network transfers, or direct JSON-RPC access — see the SDK Reference.
How do payments work for AI agents?
An agent uses the SDK or CLI to create a signer, and starts sending and receiving payments immediately. The signer is created locally — no registration, no approval process. Agents can:
Pay other agents for services (data, compute, API access)
Receive payments from other agents or users
Manage balances autonomously
All payments settle in under a second with no fees, making micropayments viable. An agent can make thousands of sub-cent payments per hour without batching or accumulating debt.
Security and Trust
What cryptographic guarantees does Fast provide?
Fast uses Ed25519 digital signatures and a Byzantine fault-tolerant quorum model (3f+1 validators, at most f faulty). Four guarantees hold under this model:
Safety: Only one transaction can be settled per account per nonce — double-spending is impossible
Determinism: The order validators receive messages does not affect the final state
Monotonicity: Once a transaction becomes settleable, it stays settleable
Liveness: If any honest validator makes progress, all honest validators eventually do
How is the protocol verified?
The FastSet protocol has been mathematically proved correct in the FastSet whitepaper.
Last updated
Was this helpful?