# Operational burden

`kaal:entity:operational-burden`

**Status.** derived

This node is assembled mechanically from the 2 claims that carry the concept tag `operational-burden`. It is a roster of what the corpus says under this term. It is **not** an adjudicated definition: no single statement here has been ruled canonical, and no first-appearance call has been made. Read the claims and judge for yourself.

## Every claim under this term

2 claims across 2 works, 2017 to 2021.

**2017**

- [2959730-030](https://wulfkaal.github.io/claims/2959730-030) [failure/argued] *(failure mode)* -- Traditional per transaction fee models failed because settlement and calculation created a prohibitive amount of work that made such operations very difficult to execute; blockchain technology overcomes all of these restrictions.
  > In contrast to the traditional settlement and calculation of fees in a per-transaction model that created a prohibitive amount of work making such operations very difficult to execute, blockchain technology overcomes all of these restrictions.
  Wulf A. Kaal, Blockchain Applications and Fee Structure Developments in Private Investment Funds (2017). SSRN: https://ssrn.com/abstract=2959730

**2021**

- [3936876-023](https://wulfkaal.github.io/claims/3936876-023) [condition/asserted] -- Self management of private keys or passphrases for individual digital assets is too cumbersome for institutional investors, so institutional custody solutions must be as robust as those provided for traditional assets.
  > Private keys or maintaining passphrases for individual digital assets is too cumbersome for institutional investors.
  Wulf A. Kaal, Hayley Howe, Custody of Digital Assets (2021). SSRN: https://ssrn.com/abstract=3936876

## Verify

Every claim above resolves to a record carrying a verbatim source quote, the sha256 of the source PDF, and a preformatted citation. Nothing here asks to be taken on trust.

    curl -s https://wulfkaal.github.io/entities/operational-burden.md | sha256sum

**Canonical form.** This markdown file is the canonical hashed representation of this entity node. Its sha256 is the content hash.