Skip to content

[BUG] pg deploy: service account unfunded — breaks 'prefunded' user promise #261

@ottovlotto

Description

@ottovlotto

Severity: P0
Reported by: DevEx Audit External
Source: DevEx Audit (External), 3 June 2026

Symptom

Deploying #1
Critical UX:
Fund the service account mnemonic via https://faucet.polkadot.io/?parachain=1500
(Account was apparently not funded, breaking user promise )
$pg deploy
Fix as top priority and make it transparent for the user. Ensure the delivery of prefunded accounts.
❌Mac OS X, ❌Linux

pg deploy fails because the service account wasn't funded. The auditor notes this breaks the user promise — Playground was supposed to provide prefunded accounts so deploy "just works".

Per audit screenshots: "Following the steps doesn't fix the issue" — i.e. even after visiting the faucet URL, deploy continues to fail. The bug is bigger than "wrong URL" — the funding mechanism itself isn't reliable.

Note on Bulletin Next: per user memory, Bulletin Next uses TransactionStorage.Authorizations for fees, not native PAS. If the CLI is asking users to fund with PAS, that's the wrong fix and the error path is misleading. Verify whether this is a PAS-funding issue or an Authorization grant issue.

Reproduction

DOT_DEPLOY_VERBOSE=1 DOT_MEMORY_TRACE=1 pg deploy 2> >(tee dot.log >&2)

with a freshly-attested signer. Observe the funding-related error and "Account not funded" / InvalidPayment outcome.

Recommended fix / next steps

Metadata

Metadata

Assignees

No one assigned

    Labels

    P0Blocker — required for V1 shipbugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions