AccessVerdict

DISCORD PILOT

Token-gated Discord roles without rebuilding onchain verification.

AccessVerdict for Discord is a focused adapter over the existing AccessVerdict core: run /verify, sign with a wallet, evaluate the configured policy, and assign a Discord role only when the result is allowed.

01

FLOW

From /verify to role assignment

A member runs /verify in the configured Discord server and receives a short-lived verification link.

The member signs a message with an EVM wallet. AccessVerdict evaluates the existing policy and the adapter assigns the configured role only for an allowed decision.

/verify
  -> signed verification link
  -> wallet signature
  -> AccessVerdict policy
  -> allowed | denied | error
  -> role assigned only on allowed
02

CORE UNCHANGED

The Discord adapter does not fork the authorization engine

The same wallet allowlist, ERC-20, ERC-721, ERC-1155 and deterministic AND/OR policy engine stays in place.

Discord is only a new delivery surface. This keeps product behavior consistent with API, SDK, CLI and route-guard integrations.

03

FAIL CLOSED

A provider failure is not a non-holder result

Denied and verification error remain separate. If onchain verification is unavailable, the adapter does not pretend the wallet failed the policy and does not grant a role.

This makes Discord re-verification safer than helpers that collapse RPC failure into false or zero.

04

PILOT SCOPE

Start with one server and one authorization boundary

The first pilot intentionally supports a single configured server, policy and role. That keeps the test small enough to validate real demand before adding multi-server administration.

If the pilot produces real installs, the next layer is server onboarding, policy selection, scheduled rechecks and Discord Linked Roles.