1. Purpose
This proposal opens a conversation with the Polkadot Technical Fellowship about the governance calls needed to begin onboarding Polkadot App users on Polkadot, and to publish the base apps the Polkadot App relies on.
PCF requests that the Fellowship review and whitelist a single batch of five existing Root calls, to be executed by a Whitelisted Caller referendum on Asset Hub.
No runtime change is requested. All five calls already exist in the runtimes the Fellowship released and in the dotNS release currently live on Polkadot. They only set parameters that are empty today, and without which username registration cannot complete and no .dot app can be published.
We share this ahead of any on-chain submission so the Fellowship can raise concerns, request parameter changes, or indicate a preferred route before a preimage is proposed.
2. Background
When a new user claims a username in the Polkadot App, two things happen on-chain:
- On the People chain, the user is registered as a lite person through
PeopleLite.attest, signed by an attester account. - On Asset Hub, the user’s
.dotname is reserved through the dotNS gateway (DotnsGateway), which forwards the reservation to the dotNS contracts through a dispatcher contract.
PCF operates the onboarding service that performs these steps on behalf of new users. Each attestation consumes one unit of attestation allowance on the respective chain, and governance can grant allowances only.
PCF already runs this service, and has done so on devnet too since devnet launched.
Today, on Polkadot:
- No attestation allowance exists on either the People chain or Asset Hub.
- No dispatcher address is set in the dotNS gateway.
Until both are in place, every registration remains pending, and no user can complete onboarding.
PCF also publishes the base apps of the Polkadot App: Get CASH (getcash.dot), the dotNS app (dotns.dot) and Browse (browse.dot). Publishing an app on Polkadot takes two things:
- A
.dotname. In the dotNS release, names of five characters or fewer are reserved for governance, and names of six to eight characters require proof of personhood. An organisation can only obtain such a name through a grant on the dotNS name whitelist, which is gated on Root. - Storage on the Bulletin chain, where the app bundle is stored. The Bulletin chain only accepts uploads from authorized accounts, and only governance can register an authorizer. Authorizations and stored data expire after 14 days and must be renewed.
Today, on Polkadot, no authorizer is registered on the Bulletin chain, so no app can be published. A fourth app, the contract registry at contracts.dot, uses a name that is open to any account, and is not part of this request.
3. The Request
| Chain | Call | Required origin |
|---|---|---|
| Asset Hub | DotnsGateway.increase_attestation_allowance(attester, count) |
Root or Whitelisted Caller |
| Asset Hub | DotnsGateway.set_dispatcher_address(dispatcher) |
Root or Whitelisted Caller |
| People | PeopleLite.increase_attestation_allowance(attester, count) |
Root |
| Asset Hub | Revive.call(DotnsNameWhitelist, grantNames(names, namesOwner)) |
Root |
| Bulletin | TransactionStorage.add_authorizer(authorizer, budget) |
Root |
The People and Bulletin calls require Root, and so does the name grant, which the dotNS contracts gate on originIsRoot. All five calls are therefore bundled into one utility.batch_all on Asset Hub, dispatched with Root through the whitelist. This ensures that they land together and that no chain is left enabled without the others.
Name grant. grantNames marks each listed name as granted to namesOwner. It does not register anything by itself. PCF then registers each name through registerReserved, which checks the grant against the name’s owner and consumes it. The grant covers exactly the listed names.
Storage authorizer. add_authorizer registers one PCF account as a Bulletin storage authorizer with a fixed budget: a quota of transactions and bytes, and an expiry block. Within that budget, the authorizer can grant and refresh upload authorizations for PCF’s publishing account. Every authorization it issues is debited from the quota and expires no later than the authorizer itself.
4. Parameters
| Parameter | Value |
|---|---|
attester |
15sDLj4T9NnCtT665koDMxBs1PZw3rzDc6wcz9tN9kKTQ2zj |
count |
1,000,000 on each chain. |
dispatcher |
0xA06d1CB1e3FedFF7b5dFa779b4Cc61703F8A46A1 |
names |
getcash, dotns, browse |
namesOwner |
0xA5C4c241985D77A0296a0FB83E0FA5905e9E39De |
authorizer |
1YoKNfXM43vegdG6g4XHCDPK6EGykYgHPNkXfRL6etnma1b |
budget |
5,000 transactions and 10 GiB, valid for one year, with fee-exempt authorization calls. |
On the storage budget: one Get CASH release is about 10 MB. Because stored data expires after 14 days, the budget has to cover regular releases of all three apps and their renewals for a year. The one-year expiry means the budget comes back to governance at least once a year.
5. Mechanism
The operational workflow is designed to keep the Fellowship as the technical filter and DOTDAO as the executing authority:
- PCF publishes the final preimage, its hash, and the attester, dispatcher, names owner and authorizer addresses.
- PCF publishes a dry run of the exact batch against live Polkadot state, showing that all five calls succeed.
- The Fellowship reviews the preimage and, if satisfied, whitelists it through a Fellowship vote.
- PCF opens the Whitelisted Caller referendum on Asset Hub and places the required deposits.
- DOTDAO votes on the referendum. On approval, the batch executes with Root.
The Fellowship vote and the referendum can run in parallel. The referendum can only execute what the Fellowship has whitelisted, so the whitelist must land before the referendum enacts.
Day 0 PCF publishes preimage + hash, Fellowship whitelist vote opens
│ PCF opens the Whitelisted Caller referendum on Asset Hub
│
├── Fellowship whitelist ········· ≤ 7 days ───┐
│ ├──► all five calls execute
└── Whitelisted Caller referendum · ~2–7 days──┘
│
Done ~2–7 days
If the Fellowship prefers not to whitelist, the fallback is a Root-track referendum with the same calls, which takes approximately 25 to 30 days.
6. Structural Independence
This request preserves the structural independence of all parties:
- The Fellowship remains the owner of the runtimes and the technical filter. It verifies exactly what executes, and nothing runs without its whitelist (or a full Root-track referendum).
- DOTDAO retains the final voting power through OpenGov.
- PCF acts as operator and consumer advocate. It proposes the parameters, operates the onboarding service, publishes the base apps, and covers the transaction fees for every onboarding and every publication from its own funds. No Treasury spend is requested.
Governance also keeps full control after enactment. clear_attestation_allowance exists on both pallets under the same origin, and governance can remove the grant at any time. Governance can also replace the dispatcher address. Governance can remove the storage authorizer at any time with remove_authorizer, and the authorizer lapses by itself at the end of its validity. A name grant can be withdrawn with revokeName until PCF registers the name. Administrative control over dotNS name allocation (reserved names, whitelists) remains gated on Root within the contracts them selves. This request uses it once, for the three names listed in section 4, and does not delegate it.
7. Transparency and Verification
To ensure that no part of this request is decided behind closed doors:
- The preimage, its hash, and a decoded breakdown of every call will be published on the Polkadot Forum before submission.
- The dry run against live Polkadot state, together with the scripts used to encode and run it, will be shared so that any Fellow can reproduce the result.
- PCF will publish periodic updates on allowance consumption, onboarding figures and storage budget consumption, so the community can judge whether the grants remain proportionate.
8. Questions for the Fellowship
- Is the Whitelisted Caller route acceptable for this request?
- Which Fellows would be willing to sponsor the whitelist vote, and in what form would the Fellowship like to receive the preimage and dry run?
- Are there further guarantees (custody, reporting cadence, revocation conditions) the Fellowship would expect from PCF as the attester operator?
- Is a storage budget of 5,000 transactions and 10 GiB for one year acceptable, or would the Fellowship prefer a different quota or expiry?