Skip to content

Get TestNet Tokens

Beginner

To build and test, your account needs two things on TestNet: a balance of PAS (the Paseo TestNet token, which pays transaction fees) and per-service allowances for the infrastructure your Product uses.

Prerequisites

Before getting started, ensure you have:

Get Tokens

The Polkadot Faucet distributes free PAS tokens to developers.

  1. Open the Polkadot Faucet for parachain 1500. Paseo Next v2's Asset Hub is parachain 1500, so use this link rather than picking a network by hand.

    Polkadot TestNet Faucet showing the Network and Chain dropdowns, the Paseo Address input, the reCAPTCHA check, and the Get some PASs button.

  2. Paste the address of the account paired with Polkadot Desktop into the address field.

  3. Click Get Some PASs to request tokens. They arrive in your account shortly after the request is processed.

Pick parachain 1500, not the public Paseo Asset Hub

The faucet's default selection drips to the public Paseo Asset Hub (parachain 1000), which is a different chain from the one Polkadot Desktop and the playground CLI target. Funding that chain leaves your Paseo Next v2 balance at zero, with no error to tell you why. The ?parachain=1500 link above is the same one the playground CLI uses.

Or top up from the CLI

If you have paired the playground CLI, pg drip funds your product account directly, no browser or captcha involved. It sends 1 PAS per run up to a 10 PAS cap, drawn from a shared dev funder rather than the public faucet. Run pg status afterward to confirm the balance landed on the account you expect.

Service Allowances

Some Polkadot infrastructure services use a separate allowance-based access model. These allowances are independent of your token balance; even with enough PAS to cover fees, a missing allowance will cause the service to reject your request. Allowances are granted per account, so a missing or misdirected one surfaces as no allowance set for account or rejected uploads; see Accounts and Signing for granting them to the account that actually signs.

Service Allowances: Bulletin Chain Storage

The Bulletin Chain has no token balance for storage. Every account needs an explicit authorization that grants a quota of transactions and bytes before it can store data on-chain. Without authorization, storage extrinsics are rejected.

On TestNet, request your storage authorization directly from the Bulletin Chain authorization page. This is required before submitting any store extrinsic from your Product.

After your authorization request is confirmed, you can verify the allocation on-chain by querying the Authorizations storage map of the transaction-storage pallet for your account.

Service Allowances: Statement Store

The Statement Store lets accounts publish off-chain statements that are gossiped and persisted by the network. Access is controlled by an on-chain StatementAllowance record that specifies two limits per account: max_count (the maximum number of statements the account can publish) and max_size (the maximum total bytes across those statements).

Provisional

The process for obtaining a Statement Store allowance on TestNet is not yet documented. Check back for updates, or ask in the developer community for available access paths.

Service Allowances: dotNS Names

dotNS (.dot name registration) uses a hybrid model. Open names (those that anyone can register) require a deposit paid in PAS. Names reserved for accounts with Proof of Personhood Full or PoP Lite status are free to register for eligible accounts, with no deposit required.

See the dotNS PopRules pricing reference for full pricing and tier details.

Where to Go Next

  • Guide Build Your Product

    Set up a local project, load it in Polkadot Desktop via the localhost bypass, and add capabilities guide by guide.

    Set Up Your Project

Last update: September 2, 2026
| Created: June 16, 2026