Community · Validators
Run a Validator
Falcon PL · Network ID 2300 · Bond 1,000 FPL · Faucet drip 2,000 FPL
Live path is Bond → archive join-snap → residual NeedLedgers → pong at tip. The retired 1001 RPC / docker one-liner is shut down and is not the 2300 product.
Step-by-step
- 01Create a Falcon-512 identityOpen Wallet and create a passkey-secured Falcon PL account. Back up your falcon_secret. Named PL accounts are the live path — not classic r-addresses.
- 02Fund the account (2,000 FPL faucet drip)Use Faucet (or Wallet → Top up). One drip is enough to cover the 1,000 FPL bond plus fees.
- 03Submit Bond (≥ 1,000 FPL)A seat exists only after a Bond is packed. Hello cannot invent a lottery seat. The registry grows through genesis and confirmed Bond transactions.
- 04Start the node with --joinJoin against published seeds. Do not pack while you are behind the mesh tip.
- 05Pull a join-snap if you are far behindIf tip = 0 or lag ≥ 2,048 ledgers, pull a join-snap from an archive (tip state + 128 ledgers). Snapshots are a point-in-time copy, not a live feed.
- 06Close the residual gapApply certified NeedLedgers after the snap. Light validators keep 128 ledgers in memory and then follow gossip.
- 07Pong at the mesh tipOnly then is the seat lottery-eligible. To leave: RequestUnbond → 14-day cooldown → CompleteUnbond. Unbonding exits the lottery immediately; funds stay locked for 14 days.
Requirements
- Falcon-512 identity (passkey wallet) on Falcon PL 2300
- ≥1,000 FPL to Bond (faucet drip covers this on testnet)
- Node started with
--joinagainst published seeds - Archive join-snap available when tip is 0 or lag ≥ 2,048
Protocol notes
- Bond is a slash target and a lottery ticket — not an interest rate.
- Join-snap is served only by nodes that advertise the archive role.
- Live packing still verifies every transaction after residual catch-up.
- Full lifecycle is in the in-app whitepaper (Validator lifecycle).