Cowrie Research

aopp-primary-sources-2026-05-03

3 min read

Address Ownership Proof Protocol (AOPP) primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone AOPP whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official GitLab specification and README, supplemented by first-party wallet-support documentation and compliance explainers.
  • The materials consistently frame AOPP as a reusable verification handshake for self-hosted-wallet ownership proofs rather than as a product owned by a single wallet or compliance vendor.

Primary-source snapshots

1) Canonical specification / README

  • URL: https://gitlab.com/aopp/address-ownership-proof-protocol/-/raw/master/README.md
  • Key excerpt:
    • The README says AOPP “streamlines and automates address ownership proofs” required between self-hosted wallets and VASPs.
    • It defines an aopp: URI with v, msg, asset, format, and callback parameters plus optional xpub_required.
    • It also defines the wallet response as a JSON POST containing version, address, signature, and optionally xpub.

2) 21 Analytics explainer

  • URL: https://www.21analytics.co/what-is-aopp/
  • Key excerpt:
    • The page says AOPP allows cryptocurrency owners to prove that their self-hosted wallet belongs to them in an easy, fast, and private way.
    • It says both the self-hosted wallet and the VASP need to support AOPP for the signed-message exchange to work.
    • It also ties AOPP directly to Travel Rule and AML compliance, especially in jurisdictions where self-hosted-wallet ownership must be verified.

3) BitBox support article

  • URL: https://support.bitbox.swiss/en_US/1-other/what-is-aopp-crypto-ownership-proof
  • Key excerpt:
    • The article positions AOPP as a secure and automated method for proving control of a specific self-hosted-wallet address.
    • It explains the common single-address verification flow and separately describes an optional xpub-sharing mode for account-level verification.
    • The article also emphasizes that AOPP is open source and collaborative rather than a proprietary BitBox-only feature.

4) Trezor removal note

  • URL: https://blog.trezor.io/a-decision-on-aopp-789540c2930b
  • Key excerpt:
    • Trezor says it removed AOPP from Trezor Suite after community pushback, even though the feature had been intended to improve usability for users dealing with strict withdrawal rules.
    • The post says everything AOPP did could still be done through ordinary sign-and-verify flows, which clarifies that AOPP is an automation and interoperability layer over existing signing primitives.
    • This source is useful mainly as evidence that the protocol mattered enough to wallet UX and regulatory workflows to become publicly controversial.

Working conclusion

AOPP is best cataloged as self-hosted-wallet verification and compliance interoperability infrastructure. The deciding evidence in this pass was the concrete aopp: URI spec, the signed-message callback flow, the optional xpub path, and repeated first-party descriptions of AOPP as a way to automate Travel Rule-driven ownership proofs without relying on screenshots or ad hoc manual signing.

Graph View