Skip to content

Conversation

@dkcumming
Copy link
Collaborator

  • Adds the report Stephen wrote that contains:
    • details of Solana
    • details of equivalence proofs
    • hand proofs for equivalence of P-Token and SPL-Token
  • Updates VERIFICATION.md:
    • Assumptions
    • Limitations
    • Shared harnesses
  • Remove old smir script, artefacts, and dot files

- **Production code**: `src/entrypoint.rs` - Used for normal builds
- **Verification code**: `src/entrypoint-runtime-verification.rs` - Used when `runtime-verification` feature is enabled

Both P-Token and SPL token `entrypoint-runtime-verification.rs` have `include!` macros that import the respective prelude and shared

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIRC, the markdown convention is one sentence per line, and I'm not sure whether splitting the sentence into multiple lines would not introduce display issues on some devices. lgtm otherwise!

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should render correctly in browsers. I have cut them shorter since the AWS application Jost and I were asked to introduce more line breaks to make them easier, so this is just the same approach from there.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, ty!

Copy link
Collaborator

@sskeirik sskeirik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I perused the equivalence proofs report itself and it looks good! Thanks!

One minor comment: there is an asymmetry between the P-Token and SPL-Token verification guide files. We have:

  • p-token/test-properties/VERIFICATION_GUIDE.md
  • program/test-properties/README.md

It might be good to synchronize these two files at some point. Maybe they should both be README files, as this provides a better experience on GH?

One last point is that the SPL-Token test-properties README is a bit harder to follow than the corresponding text on the P-Token side. I think some introductory text at the top that describes the what and why could be helpful.

@dkcumming
Copy link
Collaborator Author

@sskeirik Yeah I haven't actually looked at the program/README.md. That will be fixed up at some point but not this PR

@automergerpr-permission-manager automergerpr-permission-manager bot merged commit eeb80a3 into proofs Jan 21, 2026
1 check passed
@jberthold jberthold deleted the dc/docs-for-proofs branch January 22, 2026 03:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants