docs: incident recovery evidence, ownership adjudication and defense backlog #13
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
code/cw20-mintable!13
Loading…
Reference in a new issue
No description provided.
Delete branch "bb/incident-review-recovered-funds-and-ownership-ve-thr_q67g8guhi6"
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?
Unauthorized accepted signatures in the October incident require recovery to distinguish identity, current key control, historic entitlement and consent. This report records exact dated recovery/compensation evidence, compares current official CEX/bank/NIST/Safe/Argent sources, and proposes independent private adjudication with >=30-day contest, destination consent and reservation-safe disputes/rotation.
Research issue: #8; epic: #3. Six additional-defense issues are linked in the report and epic, separately from original production acceptance. Only README/documentation changes; no contract implementation, chain broadcasts or merges.
Validation: fourteen archived inputs match pinned DEX committed bytes; bounded ledger/selected-capture checks verify exact recovery units, reserve transfer endpoints, NFT ownership and unused nonce153. Official sources checked 2026-10-31; independent research review corrections incorporated. Local links and git diff whitespace check pass. No software test suite/build/archive-wide verifier was run for documentation.
Limits: signing mechanism/device involvement/actor attribution unresolved; no current loss valuation or final victim delivery established. Recommendations, issue creation and source publication do not establish implemented or deployed production controls.
Publication correction: the original local base included inherited GitHub minter changes absent from Forgejo main. Rebased only the two patch-identical research commits onto Forgejo
origin/main2f8438b; new headae012b7e75b022ea99617276aca2e1b46f55a9c3. Git merge-base diff and the PR files API both confirm exactly README plus four docs files, with no contract/schema/Cargo changes. The prior per-commit docs-only check was insufficient; aggregate PR scope is now verified. No merge or issue closure performed.20d76b3315toae012b7e75Coordinator reviewed corrected research head
ae012b7e75b022ea99617276aca2e1b46f55a9c3: aggregate PR diff is README plus four docs files only; report content is unchanged from reviewed patches. Integration attempted with exact head guard and refused HTTP405:Not all required status checks successful. Existing main protection requiresci/woodpecker/pr/woodpecker; this head has no statuses. Woodpecker repository26 (code/cw20-mintable) is active but has no pipeline history/config. Contract/rollout leadthr_n4vtxxfcb7owns bounded functional CI setup under #7, retaining branch protection and publishing actual run evidence. No check was bypassed or success status invented. Research issue remains open only pending integration; production criteria remain separately open.ae012b7e75to5cd743bb6a