You could do this yourself.

Six steps you can do alone, for free. Then the one you cannot.

1. Write your declaration

Read the Terms 1.0 and the Directive 1.0, then write your choices and exceptions in one text file. Any format works. If you want our vocabulary, use context.jsonld.

2. Hash it

Canonicalize with RFC 8785, then hash. The command is on the verify page.

shasum -a 256 declaration.canonical.json

3. Timestamp it in Bitcoin

pip install opentimestamps-client
ots stamp declaration.jsonld
# a few hours later
ots upgrade declaration.jsonld.ots
ots verify declaration.jsonld.ots

Free. Public calendar servers batch thousands of hashes into one transaction.

4. Store it permanently

npm i -g arweave-deploy   # or use arkb / bundlr
arweave deploy declaration.jsonld

A few KB costs about a cent. Then save the URL to the Internet Archive and push it to GitHub.

5. Sign it

openssl dgst -sha256 -sign key.pem -out declaration.sig declaration.jsonld

Do not lose the key. It is the only thing that proves you are you in twenty years.

6. Do it again every year

Append one line, "still holds", and repeat steps 2 to 5. That is how a reader knows your will persisted.

What you cannot do alone

The six steps above produce a statement. Ten thousand statements are ten thousand opinions; ten thousand signatures on the same document are one number.

• You cannot issue yourself a government identity check. Personhood has to be verified by someone who is not you.
• Your file will not be aggregated with the files of others who signed the same terms. The sentence "N humans agreed to these terms" only exists in a shared ledger, and only a shared ledger is published as one dataset.

What you cannot do alone is be counted.

That is what the $22 is for. Where it goes is on the costs page.