Skip to content

Define and test a cross-contract authorization context for nested calls #1794

Closed

Description

@Jagadeeshftw

Problem

Nested calls currently rely on independently reconstructed authorization information, which makes cross-contract permission checks difficult to audit.

Scope

Define a compact authorization context for nested contract calls, including caller, original actor, scope, and replay information. Propagate it consistently through the facade and adapters.

Acceptance criteria

  • Nested calls cannot replace the original actor without an explicit authorized transition.
  • Context fields are validated and bounded.
  • Cross-contract tests cover allowed and denied call chains.

Validation

Add security tests for forged, missing, and mismatched contexts.

Activity

  1. Jagadeeshftw commented on Sep 24, 2026

    @Jagadeeshftw
    OwnerAuthor

    Closing as part of a backlog reset.

    The open issue set in this repository is being replaced with a refreshed, more focused batch. This is not a judgement on this issue's validity — where the underlying problem still stands, it will reappear in the new set.

    Thanks to everyone who picked one of these up. Please take a look at the refreshed backlog for something to work on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions