Article guide

Cryptoassets beside a criminal scheme: what technology does and what a person does

Guide contents

A technology name establishes neither crime nor good faith. Record confirmation and commercial basis differ; writing code alone cannot establish knowledge of every use; holding an asset alone cannot establish organising a service for others. Capability, consent and authority differ. Executed conditions are not every human obligation fulfilled; international regulatory recommendations cannot confirm local platform compliance. Later knowledge does not automatically establish earlier awareness. Cessation, control, recovery and legal outcomes differ.

Questions explored

Does a technology name establish crime or good faith?

No conclusion follows from the label. Asset, record, service and person differ; FATF is international framing, local status undetermined. Unknown status does not mean absent duties.

Does a ledger record confirm the whole human history?

No. Record confirmation and commercial grounds differ; visible information is not restored control. Only the NIST2018 abstract was used; particular owner, intent and universal absolute immutability are unestablished.

Does access establish consent and authority?

Not automatically. Capability, consent and authority differ, as do own acts and acting for another. Lawful representation remains possible, but particular ownership/consent are undetermined here; no trial transfer is proposed.

Does code execution fulfil every promise?

No. Program conditions and human obligations differ. Checking one property of code is not proof of the whole project's safety, and contract terminology cannot settle the whole legal regime. Genuine limited examination retains value.

Do receipt, control, recovery and legal outcomes coincide?

No. They differ; none is established as achieved. Cessation does not establish every duty gone, and unresolved matters create no lifelong obedience to a helper.

Key distinctions

Technology names establish neither crime nor good faith; asset, record, service and acting person differ.

  • FATF is international framing, not established local status; user/developer classification is not automatic and unknown status is not absent duties.

Technical record confirmation differs from commercial grounds; visible information and restored control differ.

  • Only official NIST2018 abstract used, not legal review; the article establishes no universal absolute immutability, particular address owner or person's intent.

Writing code alone cannot establish knowledge of every use; holding an asset alone cannot establish organising a service for others; observed status, explanation and added guarantee differ.

  • Roles may overlap/change without automatic crime; the technical label does not prove an act meaningless, and local communication duties are undetermined.

Capability, consent and authority differ; control means cannot automatically establish every permission, and own acts differ from acting for another.

  • Ownership/genuine consent undetermined; lawful representation, incomplete explanation, unknowing use and pressure are possibilities, not self-proving; no trial transfer/control-sharing test.

Execution of program conditions and fulfilment of all human obligations are different results; examined properties, no found error and whole-project safety differ.

  • No particular code assessed and automation not inherently unreliable; contract terminology cannot settle all law, while limited safety knowledge cannot erase genuine useful examination.

Regulatory recommendations cannot confirm platform compliance; remuneration cannot confirm a promise and absence of payment cannot establish absence of a role.

  • Registration/permission/quality undetermined; personal belief and holding cannot prove all assertions or criminal intent.

Pressure and possible participation need joint attention; later knowledge does not automatically establish earlier awareness and a new technical status does not automatically change earlier legal meaning.

  • Manager promises transfer no responsibility automatically; threat help need not await innocence, safe refusal/secrecy/disclosure protection unpromised; correction promises no erasure/immunity/recovery.

Cessation/control/recovery/legal outcomes differ; receipt is not restored control or funds, and limited progress does not itself establish completed recovery.

  • No outcome established as achieved; ended participation does not establish all duties/consequences gone, and unresolved questions create no lifelong obedience.

Limits of interpretation

  • Hypothetical scenes; crime/guilt/law/status/reporting/recovery unestablished. No concealment/bypass/trial transfer/control-sharing experiment, deletion/false dates/agreed histories/covert collection; copying/retention/transmission rights undetermined. Immediate danger gives urgent local help priority. Moral comparison merges no traditions, replaces no law, blames no harmed person and requires no sacrifice; technical status supplies no promised cleansing of history.

Sources

  • Recommendations,June2026:R15;VirtualAsset/VASP glossary — FATF

    R15complete438–449;gloss4766–4778/4794–4799+footnote112 4811–4812read;metareusedSYS187;notIN15/151pages/2026oVASPreports

    Source use: COPYRIGHT_FATF_OECD2012_2026_ALL_RIGHTS_RESERVED

  • IR8202 Blockchain Technology Overview,finalOctober2018 — NIST;DylanYaga;PeterMell;NikRoby;KarenScarfone

    Officialfullabstract74–75/77–78,metadata68/72/history99–101read;fullPDFNOT_READ

    Source use: UNKNOWN

  • DhammapadaXII.165 — Dhammapada;F.MaxMüller

    Complete165at346read;162–166shown;fullXIIcontextreusedSYS186,ebook2017USPDmetadataSYS182;notwholebook

    Source use: US_PUBLIC_DOMAIN_WORLDWIDE_NOT_ASSESSED

  • Matthew7:16 in7:15–20 — Matthew;KJV

    Complete7:15–20 49–58/version64/PublicDomain66read;notchapter

    Source use: PAGE_MARKED_PUBLIC_DOMAIN_WORLDWIDE_NOT_ASSESSED