Pre-auditThree days of senior audit time for $1,500, credited in full toward your Zealynx audit.3 audit days, credited toward your auditSee how →
I-02·data-confidentiality

Prevent public fields from being relabeled confidential

Fixedpaymentspermissioned-tokeneurp
TL;DR

Changing an already populated public field to private did not erase its on-chain value or history, despite the confidential label.

Severity
INFO
Method
MManual review
CAT.
02Section · Issue

Issue

Foundation could mark a previously public field private, but the old on-chain value remained readable and historical transactions remained visible. Later changes could also surface a stale value again. A private label therefore could not guarantee confidentiality for a field with public history.

03Section · Resolution

Resolution

The reviewed source rejects public-to-private relabeling, and the architecture explains that public history cannot be hidden retroactively. A new private field ID is needed for future confidential data.

Status
Fixed
I-02