The Standing Trust

Policy of the Trustee · clauses 7.3 and 7.4 · adopted 12 August 2026

Things arrive at a public address.

The Trust publishes every wallet address it holds, because the deed requires it and because a register nobody can verify is not a register. The consequence is that anyone can send anything to it. This is what happens when they do.

The short version: property the Trustee has not requested or accepted does not form part of the Trust Fund, is valued at nil, and is never interacted with.

Adopted by the Original Trustee on 12 August 2026 under clauses 7.3 and 7.4 of the Deed of Trust dated 6 August 2026.

Published in the Register. This policy binds the Trustee and may be amended only by a subsequent policy published in the same way, with the reasons recorded.


1. WHY THIS POLICY EXISTS

The Trust publishes the public address of every wallet holding trust property, because clause 7.4(e) requires it and because a register nobody can verify is not a register.

A consequence of publishing an address is that anyone in the world can send things to it, and some will. Most of what arrives unbidden at a public address is worthless, promotional, or hostile. Similar problems arise off-chain: a bank transfer nobody asked for, a parcel in the post, a file sent by email.

The Trustee cannot prevent any of this. What the Trustee can do is decide in advance what happens when it occurs, publish that decision, and follow it — so that the treatment of unsolicited property is a rule applied consistently rather than a judgement made case by case after the fact.

2. WHAT THIS POLICY COVERS

Unsolicited Property means anything of any kind transferred, sent, delivered or made available to the Trust, or to any address, account or premises of the Trust, which the Trustee has not requested, agreed to receive, or accepted under clause 7.3.

It applies to property of every description, including:

  1. digital assets of any kind, including tokens, coins, non-fungible tokens, inscriptions and anything else recorded on a distributed ledger;
  2. money in any currency, including bank transfers and cash;
  3. tangible property, including anything delivered by post or courier;
  4. intangible property, including data, models, model weights, source code, documents and intellectual property; and
  5. anything else capable of being owned.

3. THE GENERAL RULE

Unsolicited Property is not accepted, and does not form part of the Trust Fund, unless and until the Trustee accepts it by a decision recorded in the Register.

Until that decision is made:

  1. it is not an addition to the Trust Fund for the purposes of clause 11A.2(c), which is triggered by the Trust accepting additions, not by receipt;
  2. it is not included in the value of the Trust Fund for any purpose, including clauses 1.5, 6A.2, 11A.2(a), 13A.2(b) and 13A.4;
  3. it is valued at nil in the accounts, and identified separately from trust property; and
  4. it confers nothing on the sender: no interest in the Trust Fund, no entitlement, no right to be consulted, no right to registration as a Participant, and no obligation on the Trustee of any kind.

Receipt is not acceptance. Silence is not acceptance. The passage of time is not acceptance.

4. DIGITAL ASSETS — SPECIFIC RULES

4.1 The Trustee shall not interact with unsolicited digital assets

The Trustee shall not transfer, swap, sell, approve, claim, bridge, or otherwise interact with any unsolicited digital asset, and shall not visit any website, sign any message, or connect any wallet to any application referenced in or by such an asset.

This is not fastidiousness. A substantial proportion of unsolicited tokens exist to provoke exactly that interaction: approving, claiming or attempting to move them executes code that drains the wallet of everything else it holds. The safest action is always no action. An unsolicited token left untouched can do nothing.

Where an asset cannot be hidden from view in the Trust’s wallet interface, it is to be left in place and ignored.

4.2 Returning unsolicited digital assets

The Trustee is under no obligation to return unsolicited digital assets and shall not attempt to do so, because:

  1. the sending address is frequently not controlled by the true sender;
  2. returning costs the Trust Fund a transaction fee, applied for no purpose of the Trust and therefore questionable under clause 4.5; and
  3. the act of returning is itself an interaction of the kind clause 4.1 prohibits.

Where a sender identifies themselves and asks for a return, and the Trustee is satisfied the request is genuine and the asset is safe to move, the Trustee may return it, and shall record the fact and the reasons in the Register.

4.3 Clause 7.4(e) — the correct reading

Clause 7.4(e) provides that no wallet holding trust property may hold any asset not belonging to the Trust. That provision is a prohibition on the Trustee placing assets belonging to others, or to the Trustee personally, in a wallet of the Trust. It is a rule about commingling, and it is directed at conduct within the Trustee’s control.

It is not a warranty that no third party will ever push an asset to a published address, which is not within the Trustee’s control and cannot be prevented by any means consistent with clause 7.4(e)’s own requirement that addresses be published. The presence of unsolicited property in a wallet of the Trust is not a breach of clause 7.4(e), and the Trustee shall not treat it as one.

The distinction between what the Trust holds and what has merely arrived at its addresses remains visible, but it is drawn as section 6.1 describes: the chain shows what arrived, the Register shows what was accepted, and anything in the first and not the second is not the Trust’s.

5. ACCEPTANCE

The Trustee may accept Unsolicited Property, in whole or in part, where satisfied that:

  1. accepting it advances the Purposes;
  2. clause 7.3 does not require it to be declined — in particular, that it is not conditional upon the exercise of any power in a particular way, and would not compromise the independence of the Trust;
  3. it is not property whose acceptance would breach clause 4.5, including property which is unlawful to hold or deal with in any relevant jurisdiction, property which appears to be the proceeds of crime, and property whose acceptance would subordinate the Purposes to the commercial interests of any person;
  4. accepting it would not confer any benefit on the Settlor, any Trustee, the Enforcer, or any person connected with any of them, unless clause 4.6 has been complied with; and
  5. where accepting it would cross an Operating Threshold, the requirements of clause 11A and, while the Founding Enforcer holds office, clause 6.1D(f) have been satisfied.

An acceptance is a decision applying to the Trust Fund. It is recorded in the Register with the reasons for it under clause 10.2B.

6. RECORDING

6.1 Digital assets — the chain is the record

The Trust does not maintain its own log of what arrives at its published addresses, because a better record already exists and is not in the Trustee’s hands.

Every receipt at every address published under clause 7.4(e) is recorded on a public distributed ledger: what arrived, from where, at what time, permanently, and verifiable by anyone without asking the Trustee for anything. That record cannot be edited, omitted from, or backdated by the Trustee. A log kept by the Trustee could be all three.

The Trustee therefore records in the Register only decisions: which assets have been accepted, and the reasons. It follows from section 3 that anything appearing at a published address which does not appear in the Register as accepted is, by the operation of this policy, not part of the Trust Fund and is valued at nil.

Stated as a rule a reader can apply:

What arrived is on the chain. What was accepted is in the Register. Everything in the first and not the second is not the Trust’s.

No further record of unsolicited digital assets is kept or required, however many arrive.

6.2 Property that is not recorded on a ledger

Money received into a bank account, tangible property, data, models, source code, documents and intellectual property leave no public record of the kind described in section 6.1. For property of that kind the Trustee shall record in the Register:

  1. the date of receipt and the manner in which it was received;
  2. a description of what was received;
  3. that it was unsolicited and has not been accepted; and
  4. where the Trustee later accepts or returns it, that decision and the reasons.

Where such property is of trivial value and of a kind that recurs, it may be recorded in aggregate, by number and period.

6.3 Senders

The identity of a sender is recorded only where the sender has identified themselves and the Trustee has decided whether to accept. Nothing in this policy requires or permits the Trustee to attempt to identify a sender who has not identified themselves.

7. WHAT THIS POLICY DOES NOT AFFECT

Nothing in this policy limits:

  1. the Trustee’s power under clause 7.3 to decline any addition, whether solicited or not, including for the purpose of not crossing an Operating Threshold;
  2. the Trustee’s duty under clause 7.3 to decline any addition which is conditional upon the exercise of any power in a particular way or which would compromise the independence of the Trust; or
  3. the requirements of clause 4.6 in respect of any transaction involving the Settlor, a Trustee, the Enforcer or a person connected with any of them.

A donation the Trust has asked for, or agreed in advance to receive, is not Unsolicited Property and this policy does not apply to it.

8. REVIEW

This policy shall be reviewed by the Trustee in each year, and by the Human Council once constituted, and any change published in the Register with the reasons for it.


Published in the Register of The Standing Trust under clause 10.2. https://standingtrust.org