# Final Steps for DOTDAO to enable User Onboarding via Polkadot App

**URL:** <https://forum.polkadot.network/t/final-steps-for-dotdao-to-enable-user-onboarding-via-polkadot-app/18937>\
**Category:** Governance\
**Created:** [October 8, 2026, 10:58am UTC](https://forum.polkadot.network/t/final-steps-for-dotdao-to-enable-user-onboarding-via-polkadot-app/18937 "2026-10-08T10:58:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![pcf\_network](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/pcf_network/32/11309_2.png) [@pcf\_network](https://forum.polkadot.network/u/pcf_network)\
**Post date:** [October 8, 2026, 10:58am UTC](https://forum.polkadot.network/t/final-steps-for-dotdao-to-enable-user-onboarding-via-polkadot-app/18937/1 "2026-10-08T10:58:25Z")

</div>

## 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](https://github.com/Polkadot-Community-Foundation/dotns/releases/tag/v1.0.0-pcf.1). 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 `.dot` name 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 `.dot` name. 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`](https://github.com/Polkadot-Community-Foundation/dotns/releases/tag/v1.0.0-pcf.1) |
| `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:

1. PCF publishes the final preimage, its hash, and the attester, dispatcher, names owner and authorizer addresses.
2. PCF publishes a dry run of the exact batch against live Polkadot state, showing that all five calls succeed.
3. The Fellowship reviews the preimage and, if satisfied, whitelists it through a Fellowship vote.
4. PCF opens the Whitelisted Caller referendum on Asset Hub and places the required deposits.
5. 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.

```auto
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:

1. The preimage, its hash, and a decoded breakdown of every call will be published on the Polkadot Forum before submission.
2. 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.
3. 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

1. Is the Whitelisted Caller route acceptable for this request?
2. 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?
3. Are there further guarantees (custody, reporting cadence, revocation conditions) the Fellowship would expect from PCF as the attester operator?
4. 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?

---

<div class="post-metadata">

**Author:** ![OliverTY](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/oliverty/32/2986_2.png) [@OliverTY](https://forum.polkadot.network/u/OliverTY)\
**Post date:** [October 8, 2026, 12:51pm UTC](https://forum.polkadot.network/t/final-steps-for-dotdao-to-enable-user-onboarding-via-polkadot-app/18937/2 "2026-10-08T12:51:58Z")

</div>

> [@pcf\_network](#):
>
> […] and in what form would the Fellowship like to receive the preimage and dry run?

It would be useful to have all the reproduction info in one doc. Hackmd or here, does not matter.  
And please note the preimage already, so that it can be tested independently and in parallel.

---

<div class="post-metadata">

**Author:** ![pcf\_network](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/pcf_network/32/11309_2.png) [@pcf\_network](https://forum.polkadot.network/u/pcf_network)\
**Post date:** [October 12, 2026, 2:42pm UTC](https://forum.polkadot.network/t/final-steps-for-dotdao-to-enable-user-onboarding-via-polkadot-app/18937/4 "2026-10-12T14:42:02Z")

</div>

We have updated the proposal and published it with everything needed to review and reproduce it in one place: **[pcf-refs `app-onboarding/v2`](https://github.com/Polkadot-Community-Foundation/pcf-refs/releases/tag/app-onboarding/v2)**.

### What changed

- **Four calls instead of five.** The Bulletin storage authorizer is dropped, together with its budget. PCF can buy Bulletin storage without governance, through paid lite personhood on People (`PeopleLite.register_with_fee`, then `Resources.claim_long_term_storage`).
- **Fixed enactment with a whitelist cutoff**. The referendum does not enact before the fixed block, however early it passes, and the cutoff leaves the Fellowship time to whitelist first.
- **The preimage is noted on Asset Hub** , in [Asset Hub block 21741068](https://assethub-polkadot.subscan.io/extrinsic/21741068-2), so it can be tested independently and in parallel, as @OliverTY asked.

The four remaining calls are unchanged, byte for byte:

| Call | What it grants |
| --- | --- |
| `DotnsGateway.increase_attestation_allowance(attester, 1,000,000)` on Asset Hub | the attester can reserve up to 1,000,000 user names through the gateway |
| `DotnsGateway.set_dispatcher_address(0xA06d…46A1)` on Asset Hub | the gateway forwards reservations, with Root origin, to the dotNS PopController |
| `PeopleLite.increase_attestation_allowance(attester, 1,000,000)` on People, sent from Asset Hub | the attester can register up to 1,000,000 lite people |
| `grantNames([getcash, dotns, browse], 0xA5C4…39De)` on the dotNS name whitelist | the three names become registrable by that account; nothing is registered yet |

### Hashes and ideal timing

| | |
| --- | --- |
| Inner call, to be whitelisted by the Fellowship | `0x90640a174e1d62b5645f31cb053d562e95a63881fd1e0f9197edbbcf83e21fad` (547 bytes) |
| Referendum preimage, noted on Asset Hub in [Asset Hub block 21741068](https://assethub-polkadot.subscan.io/extrinsic/21741068-2) | `0x294b20f9659cfb82c624b9391106bb3533cad0921e595b70389b12ab68e8e54a` (549 bytes) |
| Both referenda submitted by | relay block 33424298, about 2026-10-14 09:00 CEST |
| Whitelist on Asset Hub by (cutoff) | relay block 33525098, about 2026-10-21 09:00 CEST |
| Whitelisted Caller referendum enacts at | relay block 33539498, about 2026-10-22 09:00 CEST |

### Where to find everything

The [release](https://github.com/Polkadot-Community-Foundation/pcf-refs/releases/tag/app-onboarding/v2) carries the call data, a decoded breakdown of every call, and the reports:

- the dry runs of every call against live Polkadot, each with the origin it will have;
- a rehearsal on a fork of live state, which enacts both referenda and checks the exact state change.

The [proposal README](https://github.com/Polkadot-Community-Foundation/pcf-refs/blob/c8884b5f1be45e1a58d1663fe58437eb1f54c3dd/proposals/app-onboarding/README.md) explains each call, what it grants and how each check proves it, and lists the commands to reproduce it all against current state:

```sh
git clone https://github.com/Polkadot-Community-Foundation/pcf-refs && cd pcf-refs && npm ci
npm test && npm run decode && npm run preflight && npm run dry-run && npm run rehearse

```

We would appreciate the Fellowship’s review of the inner call above, and a sponsor for the whitelist referendum.

---

<div class="post-metadata">

**Author:** ![pcf\_network](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/pcf_network/32/11309_2.png) [@pcf\_network](https://forum.polkadot.network/u/pcf_network)\
**Post date:** [October 13, 2026, 5:33pm UTC](https://forum.polkadot.network/t/final-steps-for-dotdao-to-enable-user-onboarding-via-polkadot-app/18937/5 "2026-10-13T17:33:37Z")

</div>

Both referenda are now open.

- Fellowship whitelist: [Fellowship referendum #639](https://collectives.subsquare.io/fellowship/referenda/639)
- Whitelisted Caller: [Referendum #1955](https://polkadot.subsquare.io/referenda/1955), enacting at relay block `33539498` (about 22 October 2026, 09:00 CEST)

Both carry exactly the call data in [pcf-refs `app-onboarding/v2`](https://github.com/Polkadot-Community-Foundation/pcf-refs/releases/tag/app-onboarding/v2).

Questions are welcome here or on the referendum.

---

<div class="post-metadata">

**Author:** ![Northvane](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/northvane/32/11682_2.png) [@Northvane](https://forum.polkadot.network/u/Northvane)\
**Post date:** [October 17, 2026, 5:06pm UTC](https://forum.polkadot.network/t/final-steps-for-dotdao-to-enable-user-onboarding-via-polkadot-app/18937/6 "2026-10-17T17:06:10Z")

</div>

Thanks for putting everything in one place. I checked the call against the forum post and the v2 release: the preimage hash on chain matches the published one, and the four calls do what the post describes. The attester, dispatcher and name owner match, and both contracts exist on chain.

One question: the attester account has no on-chain identity today, while the accounts that submit PCF’s referenda are both identified and judged by a registrar. Since this account will decide who counts as a lite person, up to a million of them, could it be given an identity, or set as a sub-identity of PCF OpenGov, before onboarding starts? Then anyone can see on chain whose account it is.

---

<div class="post-metadata">

**Author:** ![pcf\_network](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/pcf_network/32/11309_2.png) [@pcf\_network](https://forum.polkadot.network/u/pcf_network)\
**Post date:** [October 22, 2026, 7:33pm UTC](https://forum.polkadot.network/t/final-steps-for-dotdao-to-enable-user-onboarding-via-polkadot-app/18937/7 "2026-10-22T19:33:47Z")

</div>

We have published a substitute for the onboarding calls currently proposed in [referendum #1955](https://polkadot.subsquare.io/referenda/1955). The one is [Referendum #1958](https://polkadot.subsquare.io/referenda/1958).

We’re narrowing the proposal to the attestation allowances and the dispatcher. The base app names will come in a separate proposal later, so each decision can be voted on by itself. The three remaining calls are unchanged, byte for byte.

The new Fellowship referendum, #664, removes the #1955 call (`0x90640a174e1d62b5645f31cb053d562e95a63881fd1e0f9197edbbcf83e21fad`) from the whitelist in the same batch that whitelists the substitute. After that, #1955 can only enact without effect.

This is the information relevant to the new referendum:

| Call | What it grants |
| --- | --- |
| `DotnsGateway.increase_attestation_allowance(attester, 1,000,000)` on Asset Hub | the attester can reserve up to 1,000,000 user names through the gateway |
| `DotnsGateway.set_dispatcher_address(0xA06d1CB1e3FedFF7b5dFa779b4Cc61703F8A46A1)` on Asset Hub | the gateway forwards reservations, with Root origin, to the dotNS PopController |
| `PeopleLite.increase_attestation_allowance(attester, 1,000,000)` on People, sent from Asset Hub | the attester can register up to 1,000,000 lite people |

### Hashes

| | |
| --- | --- |
| Inner call, to be whitelisted by the Fellowship | `0x33ed6c42bb4078327a29bf59f8cb34c9df2f93703c3c624e47dc967b4a4af03f` (118 bytes) |
| Referendum preimage, noted on Asset Hub in [Asset Hub extrinsic 22151390-2](https://assethub-polkadot.subscan.io/extrinsic/22151390-2) | `0x681f287489eea7db8bf4a37c03d4f8f861fa69565c313aa5e45dbf1a6ff29325` (120 bytes) |

The [release linked here](https://github.com/Polkadot-Community-Foundation/pcf-refs/releases/tag/app-onboarding/v3) carries the call data, the decoded breakdown, the dry runs against live Polkadot and a rehearsal on a fork of live state. To reproduce it all:

```sh
git clone https://github.com/Polkadot-Community-Foundation/pcf-refs && cd pcf-refs && npm ci
npm test && npm run decode && npm run preflight && npm run dry-run && npm run rehearse

```

Both referenda are now open:

- Fellowship whitelist: [Fellowship referendum #664](https://collectives.subsquare.io/fellowship/referenda/664)
- Whitelisted Caller: [Referendum #1958](https://polkadot.subsquare.io/referenda/1958), which can enact from relay block `33698272` (about 2 November 2026, 09:00 CET)

Both carry exactly the call data in the [release](https://github.com/Polkadot-Community-Foundation/pcf-refs/releases/tag/app-onboarding/v3).
