Skip to content

Commit 81b89cb

Browse files
Add Phase C6-B wallet conformance criteria (non-normative)
1 parent a857b0b commit 81b89cb

File tree

1 file changed

+61
-0
lines changed

1 file changed

+61
-0
lines changed
Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
# Phase C6-B Wallet Conformance Criteria — XSTRP
2+
3+
## Status
4+
NON-NORMATIVE — GOVERNANCE ONLY
5+
6+
## Purpose
7+
8+
This document defines non-normative conformance criteria for wallet and
9+
user interface surfaces that claim compatibility with XSTRP, without
10+
imposing implementation requirements or assuming authority over keys,
11+
signing, or transaction submission.
12+
13+
## Conformance Scope
14+
15+
These criteria apply only to how wallets and interfaces present,
16+
confirm, and relay XSTRP intent information to human participants.
17+
18+
They do not apply to ledger interaction, cryptographic validation, or
19+
economic enforcement.
20+
21+
## Minimum Conformance Expectations
22+
23+
A wallet or interface claiming XSTRP compatibility should:
24+
25+
- Surface all relevant intent information accurately and without omission.
26+
- Require explicit, intentional human confirmation before any signing action.
27+
- Avoid implicit, automatic, or time-based consent mechanisms.
28+
- Clearly represent failure, expiration, and abort conditions.
29+
- Preserve user agency by allowing safe cancellation prior to signing.
30+
31+
## Prohibited Behaviors
32+
33+
A wallet or interface claiming XSTRP compatibility must not:
34+
35+
- Infer or predict protocol outcomes.
36+
- Auto-approve, batch, or suppress confirmations.
37+
- Modify, reinterpret, or obscure intent semantics.
38+
- Represent unsigned or unverified states as final.
39+
- Assume authority beyond presentation and confirmation.
40+
41+
## Hardware Wallet Alignment
42+
43+
When used with hardware wallets, interfaces should:
44+
45+
- Treat hardware devices as the final authority on signing approval.
46+
- Avoid bypassing or abstracting explicit device confirmation.
47+
- Preserve clear user understanding of what is being signed.
48+
49+
## Failure Transparency
50+
51+
Interfaces should present protocol failure states truthfully and without
52+
ambiguity, including refund eligibility and non-completion outcomes.
53+
54+
Partial or speculative states must not be represented as success.
55+
56+
## Non-Authorization Clause
57+
58+
This document does not authorize implementation, certification,
59+
endorsement, or enforcement.
60+
61+
It exists solely to define governance expectations.

0 commit comments

Comments
 (0)