[Bug]: pop status --json silently dropped the whitelisted field in 0.9.0
Nobody has claimed this yet.
- Dominant language
- Solidity
- Stars
- 4
- Forks
- 2
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 24
Description
Component
Other
Priority
P3
What happened?
pop status --json in 0.9.0 emits {substrate, evm, status, statusCode, pendingClaims} — the whitelisted key that 0.8.x emitted is gone (its backing contract function was removed in the v0.6.0 contracts). Any script reading that key gets undefined with no signal.
Expected behavior
Document the breaking change in the release notes, and consider emitting the name-grant equivalent (account grant) or an explicit whitelisted: null for one deprecation cycle.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the 0.9.0 release notes and the pop status --json output described in the issue. Confirm how the removed whitelisted field differs from the current account-grant behavior, then document the breaking change and record the chosen deprecation or null-field outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 50/100