GRCLibrary.ai

Crypto-asset governance

Do we govern our crypto-asset and blockchain activity before it starts?

3 leadership pages, 9 governing documents. Can we prove we are in control?

Crypto-asset activity concentrates several exposures at once: assets that can be irreversibly lost if keys are mishandled, and stable-value tokens whose holders rely on a backing the organization must actually hold. It also brings disclosures that carry legal liability, and third-party providers and smart-contract code the organization does not fully control.

Note

Adopting a page here decides nothing for you. The leadership pages linked here are explanatory and advisory; they establish no requirement and prove nothing about your organization. Every claim in them resolves to the governing reference documents in the corpus, and it is those documents that govern.

Leadership

The leadership pages

Pages from the executive layer mapped to this concern, generated from the narrative registry. They explain and advise; the documents below govern.

Documents

The governing documents

The evidence shelf: the corpus documents the pages above resolve to, joined to the library's registries at build time. These are the documents that govern, and the evidence to ask for starts here.

Frameworks

Frameworks touched

The external frameworks the shelf above maps, from the corpus registry. The documents' framework spellings are normalized against the crosswalk's committed alias maps: every spelling that names a crosswalk instrument, whole or by a clause, appears once as the instrument's short label and links its instrument page; a cited text that names no instrument is shown as plain text.

  • CRR
  • Directive (EU) 2015/849 (AMLD)
  • Directive 2009/110/EC (EMD2)
  • DORA
  • EMD2
  • Financial Collateral Directive
  • ISO/IEC 27001
  • MiCA
  • MiCA liquidity RTS
  • MiCA RTS and ITS
  • Money Market Funds Regulation

Go deeper

The domains behind it