Skip to content

Faucet

View as Markdown

Both withdrawals go through Thru Developers. Sign in once, then fund an account on Alphanet or Betanet:

Terminal window
thru auth login
thru --network betanet faucet withdraw thrusd ta... 100
thru --network betanet faucet withdraw thru ta... 10000

Omitting --network uses your configured network. Custom RPC endpoints are unsupported. Neither command creates the recipient account; it must already exist on the selected network.

For automation, configure a Developers API key instead of logging in. The key works for both withdrawals.

Limits

Section titled “Limits”

Each Developers account shares 5 requests per rolling 60 seconds across the browser faucet, CLI installations, API keys, assets, networks, and destinations. Admitted attempts consume quota even if funding fails. Wait for Retry-After on HTTP 429. The CLI never retries funding automatically; check your balance after an uncertain result.

Test THRUSD

Section titled “Test THRUSD”
Terminal window
thru --network betanet faucet withdraw thrusd ta... 100

Replace ta... with an existing THRUSD token-account address, not a wallet address or key name. Amounts are decimal tokens.

THRU

Section titled “THRU”
Terminal window
thru --network betanet faucet withdraw thru ta... 10000

The recipient can be a configured key name, a ta... address, or a hex public key. A key name only resolves the address; nothing is signed locally, so no funded local key is needed.

Amounts are raw balance units, from 1 to 10,000 per request. The recipient must be a wallet (EOA) account or an account that has opted into receiving THRU. Token accounts cannot receive THRU; requests to them fail with RECIPIENT_CANNOT_RECEIVE_NATIVE.

You can also request THRU in the browser: open the Developers faucet and select THRU.

Changes from earlier CLI versions

Section titled “Changes from earlier CLI versions”

Earlier versions named this command faucet withdraw native, signed withdrawals locally, and used an on-chain rate-limit policy. Current versions:

  • name the command faucet withdraw thru; native still works as an alias
  • require thru auth login or THRU_DEVELOPERS_API_KEY
  • no longer accept --fee-payer on THRU withdrawals
  • print THRU results in the same faucet_fund JSON object as THRUSD, with asset, network, account, amount, and result fields

Earlier CLI versions cannot withdraw THRU from the current faucet program. Upgrade the CLI.

Deposit THRU

Section titled “Deposit THRU”
Terminal window
thru faucet deposit default 1000

Deposit replenishes the faucet from a local key. It signs locally, accepts --fee-payer, and takes raw balance units. The depositor must match the fee payer. Accounts accept configured key names, ta... addresses, or hex public keys.