# Domicile

`kaal:entity:domicile`

**Status.** derived

This node is assembled mechanically from the 2 claims that carry the concept tag `domicile`. 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 2019.

**2017**

- [2998033-011](https://wulfkaal.github.io/claims/2998033-011) [failure/argued] *(failure mode)* -- Managers of funds that exist only as smart contracts in cyberspace, with no foreign or domestic domicile, cannot assume they are judgment proof; the more likely outcome is that they must comply with more regulations, not fewer, because every node location can trigger a jurisdiction.
  > However, managers cannot assume that they are judgment-proof. Instead, fund managers may be required to comply with more regulations not fewer.
  Wulf A. Kaal, Blockchain Innovation for Private Investment Funds (2017). SSRN: https://ssrn.com/abstract=2998033

**2019**

- [3409548-021](https://wulfkaal.github.io/claims/3409548-021) [failure/argued] *(failure mode)* -- A fund constituted purely through smart contracts on the Ethereum blockchain may have no domicile, foreign or domestic, which makes jurisdiction over blockchain transactions a genuine problem for the funds that use the technology.
  > Some private investment funds may exist through the combination of smart contracts on the Ethereum blockchain.85 Such funds may not have a domicile either foreign or domestic.
  Kaal, Financial Technology and Hedge Funds (2019). SSRN: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3409548

## 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/domicile.md | sha256sum

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