PCO Token — User Guide

This guide covers everything a community member can do with the PCO token. Every action here is a community function— administrative functions (opening rounds, granting awards, sweeping the pool, upgrading modules) are never exposed on the website and always require the organization's hardware-held keysets.

1 · Choose your wallet — one active identity

The token page uses one active wallet at a time: claims land there, balances show for it, votes and transfers come from it. Never two identities at once — switching wallets switches everything. Three options:

• EckoWallet — browser extension. Must be on the site's network (see below).
• Zelcore — desktop app. Log in first; the site talks to its local signing API.
• Ledger — hardware, via WebHID (Chrome/Edge/Brave; Kadena app open). The page asks the device to display the transaction so you can check the recipient and amount on the device itself. Leave blind signing off: if the device shows only a hash it cannot tell you what you are approving, and this page will warn you before it continues.

2 · Claim — free, with any wallet

Claiming is the one action whose gas is sponsored by the on-chain gas station, soyou need no KDA to claim. Your wallet signs one thing: permission for the station to pay the fee. It never authorises a transfer of your funds, and the tokens can only land in the account bound to the guard supplied with the claim.

• Pick the open claim round and answer its quest. Quests are published on the PCO channels together with the round id; the answer, normalized to lowercase, is the claim code.
• Claim. The gas station pays the fee; tokens land in your active wallet's account.

On-chain rules that keep this fair: one claim per account per round, a fixed budget per round, and a time window — when a round's budget is exhausted or its window closes, the round is over. Everything beyond claiming is self-paid: your active wallet signs and pays a little KDA gas.

Wallet setup: none needed. PCO is deployed on Kadena mainnet, so any Kadena wallet already points at the right network — just connect. PCO lives in the namespace n_57fcd6f7b72e8949af51a8d6f17fe12cc7719d10, a principal namespace whose name is derived from the governance keyset, so it cannot be impersonated by a look-alike.

3 · What is sponsored and what you pay

• Sponsored (free for you): the claim — the community gas fund exists to onboard newcomers who hold no KDA. It is capped at a fixed daily budget that refills each day, so it stays an onboarding fund.
• Self-paid (ordinary gas from your wallet): transfers, cross-chain transfers, voting, vote-key registration, guard rotation. Fees are tiny fractions of a KDA. (Questions are authored by the organization, not by holders — see below.)

4 · Transfers

• Same-chain: enter a k: recipient and an amount. Transfers are irreversible — check the recipient twice. A not-yet-existing recipient account is created bound to the key in its name; that is what makes k: accounts safe to send to.
• Cross-chain sends are not offered here, on purpose. The token supports them, but a cross-chain move is a two-step transfer: the first step debits the chain you are on, and the credit only lands when someone submits the second step with a proof on the target chain. This page does not do that, so offering it would take your PCO and leave it in a half-finished transfer. Claiming, awards and voting all live on chain 0 in any case, so there is nothing on another chain for PCO to do yet.

5 · Governance — ranked-choice voting on admin-authored questions

• Questions come from the organization; answers come from you. Each on-chain question carries 2–5 named options. The community suggests questions on the public channels (Telegram / X) and the organization puts them on-chain — an accountable public step.
• You vote by ranking the options in order of preference. A partial ranking is fine and costs you nothing — ranking more options can never hurt your favourite.
• The result is head-to-head. For every pair of options the contract records how much voting weight prefers one to the other, and the winner is the option that beats every other. If none does, that is published as a split rather than broken by an arbitrary rule. A Borda points row is shown too, but only as a completeness diagnostic — points reward ranking fewer options, so they are not the result.
• Voting weight is your current hub-chain balance, and re-submitting replaces your ballot. If your balance ever falls below the weight recorded on an open ballot, that ballot is automatically trimmed to what you still hold — so you can never keep voting with tokens you no longer have. A decrease that still leaves you above your recorded weight changes nothing. Received tokens arrive unvoted.
• The organization can close a question early only with a public on-chain reason.

Why can't holders create proposals directly?

With a small global cap on open questions (which bounds gas on every transfer), open proposing is squattable: one threshold-sized bankroll hopping between fresh accounts can fill every slot forever, and defending that requires stake locks plus admin cancel/seizure backstops — at which point admin involvement is structural anyway. v1 takes honest control of question authorship instead, keeps voting and suggesting fully open, and preserves the complete open-proposing design for a future version. Full analysis: GOVERNANCE-DESIGN.md.

6 · The voting key — vote hot, keep your wallet cold

If you hold PCO in a wallet you do not want to take out for routine votes, register a dedicated vote key:

• Register: your MAIN wallet signs one transaction (set-vote-key, scoped to the VOTE-KEY-ADMIN capability). On the token page, one click registers the browser's own key as your vote key.
• After that: the hot key can cast and re-cast votes for your account, paying its own tiny gas. Your main wallet never has to come out to vote.
• Safety, enforced on-chain: the hot key can only vote — transfers, rotation, claiming, and the registration itself all require the main guard; the hot key can never re-point or clear itself; the contract checks the main guard first, so a registration can never lock you out; clear the key any time with one main-wallet transaction.

7 · Rotating an account guard

Named PCO accounts (not k:-prefixed) can rotate to a new guard: connect a wallet satisfying the account's current guard and submit the rotation (scoped ROTATE capability). Protocol note: k: accounts cannot rotate — their guard is permanently bound to the key in their name; that is exactly what makes them safe transfer targets.

8 · Verifying everything yourself

• Contracts: the deployed modules byte-compare against the public repository — its verification guide shows how to run the comparison against any node.
• Activity: every claim, grant (with its public reason), round, vote, vote-key registration, and transfer emits a public on-chain event. Nothing about the program is off-ledger.

9 · Fair play and safety

• Official rounds exist on-chain before they are announced anywhere. We never direct-message claim links, and there is nothing to buy — ever.
• The claim page never asks for a seed phrase or a private key, and never generates one for you. Every signature comes from a wallet you already control. Any page asking you to paste key material is not ours — including one that looks exactly like this.
• Round budgets bound worst-case abuse; one-claim-per-account-per-round is the on-chain rule.

← back to the token page · this guide on the wiki · contracts on GitHub