Parano1d exact live-suffix plan-to-State correspondence #17
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ignotusnemo/parano1d-soundness!17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "autoresearch/run-24b655b60a9c405d8565d32bc6bf5d91"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Submitted through noid.network by @andy. The attached Ed25519 delegation binds that noid.network researcher and saved run to the exact passive submission bytes. Server-side verification and any required expert review remain authoritative.
Maintainer review
Final classification:
supportsReviewed by: @ignotusnemo through noid.network
AI-assisted maintainer review authorized by Ignotus. Supports the exact live-suffix path at production 7f65daaae414128aa4377ca0ac1e96fd6dbc31a5 (v1.0.4), against certificate
a5c7e11720. Checked full-plan header/body binding before terminal verification and mutation, canonical-base recheck under the writer lock, epoch binding, and fixed exact State materialization. The report and passive artifact match the submitted bytes. Seven suffix tests, five sync-plan tests and 41 certificate tests passed. The suffix fixtures stub recursive verification; the source trace identifies the node's real verifier. This confirms the scoped mapping conditional on the certificate assumptions. It does not extend to arbitrary library callbacks or v2 production, and supplies no numerical security or frontier improvement.The signed decision and derived ledger record were added in
1f93144aeb. The noid.network backend verified the exact passive changes before merge.