# Wallet Membership Kit — planning brief

Status: planned product; software not released. Version 1.0, 2026-09-29.

Connecting a wallet is often mistaken for logging in. Users get stuck when they cancel signing, change accounts or return to an expired session.

## First workflow

A member connects a supported wallet, signs a clear login challenge and enters the application. The server checks the access rule and shows a useful explanation when membership cannot be confirmed.

## Proposed first release

- [ ] One EVM network and an agreed supported-wallet list
- [ ] Server-verified message signing and application sessions
- [ ] One membership rule with a read-only chain adapter
- [ ] Account-change, signature-cancellation and recovery interfaces

## Extension points

- [ ] Separate wallet identity from application roles and business permissions
- [ ] Swap the membership resolver without replacing the UI
- [ ] Add a second network only after its verification and indexing behavior is scoped

## Acceptance checks

- [ ] Expired or replayed challenges are rejected
- [ ] An account change does not reveal the previous account’s data
- [ ] A failed chain lookup shows an unknown state rather than granting access
- [ ] An operator can explain why access was granted or denied

## Boundaries

Token launches, custody, investment features and audited smart-contract claims are not included. Contract changes and independent review are separately scoped.

## Decisions to fill in

- Business owner:
- Intended users:
- Data sources and retention:
- Existing systems:
- Integrations:
- First release exclusions:
- Deployment owner:
- Acceptance owner and evidence:

## Reuse

You may copy and adapt this planning document for your own or client projects. It contains no software license or promise of implementation.

Discuss a custom build: https://fone.cc/contact/