Joining and role access
Require a human, account, organization, or role proof before entry or elevated permissions.
Communities and memberships
Make membership portable without making identity public.
Confirm the human, role, account, domain, wallet, or asset behind a member and issue a reusable proof. Receipts stay private by default, while connected communities can request the current decision they need.
01Decisions that matter
One proof path across the highest-value gates.
Human checks, verified roles, token or account ownership, member access, and portable eligibility.
Communities and memberships gates
Ready
- Human checkPassed
- Role accessCurrent
- OwnershipConfirmed
Ownership-based membership
Check current domain, social account, wallet, or supported asset ownership before access.
Rewards and renewals
Recheck eligibility, scope, and expiration before rewards or continued member access.
02How it works
From trust decision to reusable proof in four steps.
- 01
Choose the membership rule
Define the human, role, account, or ownership proof the community accepts.
- 02
Let the member prove it
Use a hosted check instead of collecting the same evidence in every community.
- 03
Keep the proof private
Store the accepted decision privately until the member chooses where to use it.
- 04
Check on entry and renewal
Require current status before access, rewards, or role changes.
How it works
CHECK → RECEIPT
- 01Verify onceComplete a supported check
- 02Get a receiptResult becomes a reusable record
- 03Check at the gateApps confirm before action
- 04Share lessPresent the result, not the file
03Recommended paths
Start with the decision you already repeat.
Add one current proof to one valuable gate. Expand only when another product can reuse the same decision.
Trust receipt
Current
One check. Reusable everywhere it is accepted.
SubjectAcme Ops · org
CheckOrganization
ScopeAccess · payout
StatusActive
Expires2026-12-01
Connected apps confirm status before access — without the full source file.
Recommended NEUS paths
Pick the product that matches your gate.
Add one trusted decision to your next gate.
Start with a supported check, issue the reusable proof, and require current status where it matters.