🐻 Pearl PRL ● backend not configured

Pearl Testnet Faucet

Free tPRL (testnet Pearl) for developers building on the Pearl Proof-of-Useful-Work chain. This page is a static frontend — it sends your request to a faucet backend you configure below.

No backend connected yet. Point the faucet at a running backend (see Run your own) or use the default http://127.0.0.1:8090 when testing locally.

Request tPRL

1 drip / address / 24h

Faucet backend status

Network—
Max drip—
Cooldown—
Daily cap—
Wallet connected—
Backend—

How it works

  1. Paste a testnet Pearl address (tprl1… — bech32m per BIP-350, witness v1+ Taproot/P2MR only, like all Pearl addresses).
  2. The page validates the address locally (bech32m checksum + witness-program rules from node/btcutil/address.go), then POSTs it to the faucet backend.
  3. The backend rate-limits (default: 1 drip per address per 24h, operator-set daily cap) and pays out from its own funded Oyster wallet via the Oyster legacy JSON-RPC sendtoaddress method.
  4. You get back a real transaction id on the Pearl testnet.

Testnet coins have no monetary value. Mainnet PRL addresses (prl1…) are rejected — this faucet is testnet-only by design. Nothing here is custodial: the page never sees private keys, and the backend only ever pays out.

Run your own faucet backend

A zero-dependency Node.js reference backend lives in this repo:

examples/faucet-backend

git clone https://github.com/Kshot3000/Oysters4All.git
cd Oysters4All/examples/faucet-backend
cp .env.example .env   # set OYSTER_RPC_USER / OYSTER_RPC_PASS
node server.js         # listens on http://127.0.0.1:8090

It needs a funded Oyster wallet on testnet (Oyster legacy JSON-RPC defaults: 127.0.0.1:44209 on testnet, 44211 on testnet2) and a pearld testnet node behind it. Without wallet credentials the backend starts but honestly reports walletConfigured: false and refuses drips.