Skip to content

Conversation

@dkcumming
Copy link
Collaborator

@dkcumming dkcumming commented Jan 10, 2026

Adds guard on postcondition check for owner, lamports, and data_len behind a feature flag, specifically target_os = "solana" and target_arch = "bpf". This means that CloseAccount now passes for non-multisig.

However this proof passing is slightly limited in strength since it does not check that the data, lamports, and owner field are zeroed when close_unchecked is called in the implementation.

dkcumming and others added 4 commits January 10, 2026 22:51
…dition

These assertions are checking the effects of `close_unchecked` which
calls a syscall `sol_memset_`. Currently our target is not `solana` so
we are not compiling these syscalls calls, nor their bodies.
@dkcumming dkcumming marked this pull request as ready for review January 13, 2026 11:02
Copy link

@Stevengre Stevengre left a comment

Choose a reason for hiding this comment

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

LGTM!

@dkcumming dkcumming merged commit c7a8a69 into proofs Jan 14, 2026
1 check passed
dkcumming added a commit that referenced this pull request Jan 21, 2026
Adds guard on postcondition check for `owner`, `lamports`, and
`data_len` behind a feature flag, specifically `target_os = "solana"`
and `target_arch = "bpf"`. This means that `CloseAccount` now passes for
non-multisig.

However this proof passing is slightly limited in strength since it does
not check that the `data`, `lamports`, and `owner` field are zeroed when
`close_unchecked` is called in the implementation.
@jberthold jberthold deleted the dc/close-account-correction branch January 22, 2026 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants