Show the evidence behind the sentence.
A field note begins with a concrete product question, then separates observed behaviour, protocol documentation and hypothetical design choices.
Source order
- Use official protocol or standards documentation for technical behaviour.
- Use the selected wallet or adapter’s own documentation for its integration surface.
- Use a protocol’s own material only for claims about that protocol; do not turn it into a universal protocol guarantee.
- Mark hypothetical product flows clearly and avoid fictional testimonials, customer numbers or integration claims.
What a source does not prove
A reference documents the behaviour described in its scope. It does not prove that a hypothetical product implemented that behaviour, that a particular RPC provider is reliable, or that an observed state will remain unchanged. Notes should include a review date, identify assumptions, and distinguish signatures, submissions, confirmations and account reads.
Design and accessibility
Diagrams are original, have text equivalents and are labelled illustrative. Pages are HTML-first, responsive and usable without animation. Keyboard focus is visible, the site honours reduced-motion preferences, and the blank canvas is a real downloadable SVG. The prototype uses no live product data.
Limitations
These case notes are educational examples, not production integration audits, security reviews, financial recommendations or legal opinions. Technical sources were checked on 26 October 2026; they may change. Re-check them before publication and before relying on them in an implementation.
See the Wallet signing and staking status and Corrections.