P0: isolate Panopt core from inherited Monero networks and consensus #1

Open
opened 2026-10-19 04:21:31 +00:00 by nmchenry · 0 comments
Owner

Development-only core fork from Monero v0.18.5.3. Keep every item open until code, negative tests, and independent review are linked. Experimental branches are not launch candidates.

  • Replace inherited genesis transactions for main/test/stage with independently generated Panopt genesis and record hashes and issuance vectors.
  • Prove Monero and Panopt transactions, blocks, wallets and peers cannot cross networks.
  • Remove inherited peer seeds, checkpoints, blocklists, update-service trust and height-specific exceptions.
  • Define and test the Panopt fork schedule, monetary cap, founder allocation, lock and vesting rules.
  • Run unit, functional RPC, adversarial P2P/reorg, wallet privacy and monetary-invariant tests.
  • Complete provenance and license review plus independent security audit before a public binary or network launch.

Current development evidence and unresolved failures are in PANOPT_FORK_STATUS.md, the master checklist, and the historical GitHub issue. Forgejo is the active tracker from this point.

Development-only core fork from Monero v0.18.5.3. Keep every item open until code, negative tests, and independent review are linked. Experimental branches are not launch candidates. - [ ] Replace inherited genesis transactions for main/test/stage with independently generated Panopt genesis and record hashes and issuance vectors. - [ ] Prove Monero and Panopt transactions, blocks, wallets and peers cannot cross networks. - [ ] Remove inherited peer seeds, checkpoints, blocklists, update-service trust and height-specific exceptions. - [ ] Define and test the Panopt fork schedule, monetary cap, founder allocation, lock and vesting rules. - [ ] Run unit, functional RPC, adversarial P2P/reorg, wallet privacy and monetary-invariant tests. - [ ] Complete provenance and license review plus independent security audit before a public binary or network launch. Current development evidence and unresolved failures are in [PANOPT_FORK_STATUS.md](https://git.panoptsecurity.com/Panopt/Panopt-Core/src/branch/panopt/dev/PANOPT_FORK_STATUS.md), the [master checklist](https://git.panoptsecurity.com/Panopt/Panopt-Coin/src/branch/main/docs/MASTER_CHECKLIST.md), and the [historical GitHub issue](https://github.com/Nicalicious/Panopt-Core/issues/1). Forgejo is the active tracker from this point.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Panopt/Panopt-Core#1
No description provided.