Severity: P0
Reported by: DevEx Audit External
Source: DevEx Audit (External), 3 June 2026
Symptom
Deploying #1
Critical UX: Unable to deploy rpsclonetest.dot requires ProofOfPersonhoodFull, but this signer is NoStatus.
$ pg deploy
Fix as top priority and make it transparent for the user.
❌Mac OS X, ❌Ubuntu 26.04 LTS
pg deploy fails with requires ProofOfPersonhoodFull, but this signer is NoStatus. The signer the user is deploying with doesn't have full PoP status, so the deploy is rejected. The CLI surfaces this raw upstream error without any guidance on how to fix it.
Cross-ref existing playground-cli issues:
This is the same class of bug — auditor's report is a fresh confirmation.
Reproduction
DOT_DEPLOY_VERBOSE=1 DOT_MEMORY_TRACE=1 pg deploy 2> >(tee dot.log >&2)
With a fresh service-account signer that isn't ProofOfPersonhoodFull. Observe:
Unable to deploy rpsclonetest.dot requires ProofOfPersonhoodFull, but this signer is NoStatus.
Recommended fix / next steps
- Make the error transparent and actionable: tell the user how to get to ProofOfPersonhoodFull (via Polkadot mobile attestation), with a one-line CTA.
- See memory note: "Funder PoP bootstrap recipe" — manual steps to get e2e funder to ProofOfPersonhoodFull via personhood-faucet + dotns-bootstrap sudo endpoints. The CLI shouldn't expose those raw URLs to users (separate issue).
- Cross-ref upstream bulletin-deploy#376 (reads PoP from precompile).
Severity: P0
Reported by: DevEx Audit External
Source: DevEx Audit (External), 3 June 2026
Symptom
pg deployfails withrequires ProofOfPersonhoodFull, but this signer is NoStatus. The signer the user is deploying with doesn't have full PoP status, so the deploy is rejected. The CLI surfaces this raw upstream error without any guidance on how to fix it.Cross-ref existing playground-cli issues:
This is the same class of bug — auditor's report is a fresh confirmation.
Reproduction
With a fresh service-account signer that isn't ProofOfPersonhoodFull. Observe:
Recommended fix / next steps