docs: storage audit — no PII in contract storage#3
Open
devSoniia wants to merge 1 commit into
Open
Conversation
Audits all DataKey and TokenDataKey variants across both contracts. No PII found. Documents methodology, findings, and recommendations. Closes Vera3289#67
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Completes the storage audit required by Vera3289#67.
What was audited
Every
DataKeyvariant incontracts/stream/src/types.rsand everyTokenDataKeyvariant incontracts/token/src/types.rs, across all three Soroban storage tiers (persistent, instance, temporary).Findings
No PII or sensitive off-chain data found. All stored values are cryptographic addresses, numeric amounts, boolean flags, or enumerations.
Full findings documented in
docs/security/storage-audit.md.Checklist
docs/security/storage-audit.mdCloses Vera3289#67