docs: add Walletbeat compatibility & requirements mapping - #53
Merged
hellno merged 5 commits intoJun 14, 2026
Conversation
Map Deckard against all 27 Walletbeat software-wallet attributes across the five groups (Security, Privacy, Self-sovereignty, Transparency, Ecosystem), with current status, the PASS rule, and the concrete work to pass each. Adds a sequenced action list and the Stage 0/1/2 ladder. Action-oriented companion to the neutral research in docs/research/07-wallet-rankings.md.
Record the 2026-06-14 product decisions in the compatibility map: - Funding: self-funded, no protocol revenue (content for #21 FUNDING.md) - Security audit (#1): decision spike, budget/vendor undecided - Out of scope for v0: social/guardian recovery (#6) and L2 force-withdrawal (#15), documented as deliberate trade-offs No GitHub issues opened (per process decision).
Second decision round (2026-06-14): - Ambition: harvest aligned attributes, do not climb the Stage ladder - Hardware-wallet signing (#4): out of scope (deliberate non-goal) - Browser integration (#25): deferred; MCP agent is the sole connection surface; app isolation (#11) reframed as per-agent/session isolation - Account abstraction (#26): EIP-7702 research spike (on-chain agent policy), batching (#27) contingent on it - Multi-identity (#8/#9): a post-v0 goal with non-correlation UX Rewrites the Stages section as reference-only.
Validate the code-fit layer from a four-cluster read of the actual codebase: per-item crate placement, seam-vs-expansion, size, and risk, plus an EIP-7702 spike brief. Key findings: - deckard-core already has the right seams (multi-account derivation, reserved enclave flag, alloy/7702-ready builder-agnostic broadcast) - Un-gating Send is UI-only (daemon path tested) and the dependency hub - deckard-contract (frozen) is the higher-ceremony expansion point; batch RevokeApproval/Intent::Batch/session-token changes together - Re-tier #13 RPC-before-first-request UP to L (provider spawns with DEFAULT_RPC before the auth gate); re-tier #8/#9 multi-identity DOWN (core already derives accounts) Reworks the sequencing tiers with the measured sizes.
PR #52 resolved the dapp-connectivity exploration and created canonical issues (epic #44, PRD-01..05 #45-50) plus an issues-not-files convention. Reconcile this doc to a rubric + decision record, not a parallel tracker: - Replace the work-item sequencing backlog and the EIP-7702 spike brief (duplicated existing issue #33) with a Tracking & cross-references block - Fix the now-outdated connection-surface framing: #25 browser integration is planned/phased via the owned EIP-6963 bridge (ADR 0001), not 'no dapps'; #11 isolation maps to per-origin permissions (PRD-05 #48), not a wire token - Point #3 clear-signing at PRD-02 #46; note PRD-01 #45 resolver-auth - Update Stages + status notes to match
hellno
force-pushed
the
claude/walletbeat-compatibility-requirements-apyqgr
branch
from
June 14, 2026 11:20
51cb6bb to
316c6f0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
docs/WALLETBEAT-COMPATIBILITY.md— the action-oriented companion to the neutralresearch/07-wallet-rankings.md: attribute-by-attribute, what Deckard must do to be compatible withand pass the Walletbeat rubric, with current self-assessed status and the concrete work for each.
Docs-only. No code, no dependency changes.
Contents
Transparency / Ecosystem) with PASS / PARTIAL / FAIL status and the per-attribute requirement.
oversights: self-funded (no protocol fee), audit as a budget/vendor decision spike, "harvest the
vision-aligned attributes, don't climb the Stage ladder," hardware signing out of scope,
multi-identity as a post-v0 goal.
item, which crate it lands in, whether the seam already exists or
deckard-core/deckard-contractmust be expanded, rough size, and risk. Headline: the core already has the right seams (multi-account
derivation, reserved enclave flag, alloy/7702-ready builder-agnostic broadcast); most items need new
typed surfaces, not new crypto. Un-gating Send is UI-only and the dependency hub.
Reconciled with ADR 0001 / #52
The dapp-connectivity exploration this doc had deferred to has landed, so the doc now defers to the
issues #52 created rather than duplicating them, and follows the new issues-not-files convention (work
items as issues; decisions + research in
docs/):Removed the duplicated EIP-7702 spike brief (subsumed by #33) and the work-item sequencing backlog;
fixed the now-outdated "agent-only, no dapps" framing to match the phased owned-bridge decision.
https://claude.ai/code/session_01Mayw4s85gcgHxi38UiybaA