Skip to content

[EAN-Issue-2520] Added logic to validate txn caller address#10

Merged
aregng merged 1 commit intotask/issue-2529from
task/issue-2520
Jan 22, 2026
Merged

[EAN-Issue-2520] Added logic to validate txn caller address#10
aregng merged 1 commit intotask/issue-2529from
task/issue-2520

Conversation

@aregng
Copy link
Copy Markdown

@aregng aregng commented Dec 29, 2025

  • Introduced ExecutionMode describing the context of the vm for the transaction being executed

  • Extended Handler with validate_caller() which validates caller address based on the transaction execution mode.

    • System transaction caller is expected to be VM_SIGNER reserved address
    • All User/Automated transactions having any of the supra reserved as caller will fail validation

- Introduced ExecutionMode describing the context of the vm for the
  transaction being executed

- Extended Handler with validate_caller() which validates caller address
  based on the transaction execution mode.
    - System transaction caller is expected to be VM_SIGNER reserved address
    - All User/Automated transactions having any of the supra reserved as
      caller will fail validation
Comment thread crates/context/src/cfg.rs
/// Create new `CfgEnv` with default values and specified spec.
pub fn new_with_spec(spec: SPEC) -> Self {
Self {
chain_id: 1,
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

should chain_id be 1? Is this consistent with chain_id of Move VM?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

@aregng aregng merged commit 38279cf into task/issue-2529 Jan 22, 2026
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.

2 participants