Implement the GuildPass V2 access-control engine

[Lakes41]

Difficulty

Hard

Type

Feature / Security

Background

Access evaluation is one of the core capabilities of GuildPass. It must produce predictable decisions based on membership, roles, Pass ownership, and configured policies.

Problem

There is currently no V2 access-control engine with a stable request and decision model.

Expected Outcome

Core exposes deterministic access evaluation with explainable results that can be consumed through the SDK and integrations.

Suggested Implementation

Define an access request similar to:

{
  guildId,
  account,
  resource?,
  action?
}

Define a deterministic result similar to:

{
  allowed: boolean,
  reason: string
}

Implement initial policy evaluation for:

• Guild membership.
• Member roles.
• Pass ownership/eligibility abstraction.
• Combined policy requirements.

Keep blockchain ownership resolution behind an interface so the engine can initially be tested without Soroban.

Acceptance Criteria

• Canonical access request and result types exist.
• Membership-based rules are supported.
• Role-based rules are supported.
• Pass-based rules have an implementation-independent evaluation boundary.
• Combined conditions are deterministic.
• Every decision includes an explainable reason/code.
• Deny behaviour is explicit and tested.
• Unit tests cover positive, negative, boundary, and conflicting-policy cases.

Likely Affected Files/Directories

• src/access/
• src/services/access/
• src/domain/
• src/errors/
• test/

[abojeEdwin]

Hi maintainer, I've gone through the issue and I have a clear understanding of the fix for this issue. I'd love to be assigned to this issue. Thank you

[Okorie2000-code]

The issue description is crystal clear, and I’d be glad to work on it. I’ll ensure the implementation is clean, tested, and submit a clean PR. Kindly assign it to me. 🙏

[guptakumarranjeet150]

Hi everyone,

I can tackle Implement the GuildPass V2 access-control engine. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in Adamantine-guild/guildpass-core
• Core Implementation: Build Implement the GuildPass V2 access-control engine with responsive React/Next.js components and clean state management.
• Quality Assurance: Add component unit tests verifying user interactions and rendering states.

Happy to pick this up today—please assign to me!