Terms

Effective 2026-09-02 · Terminus Veil v0.1

These terms cover this software copy of Terminus Veil: the registry contract sources, the browser console, and these static pages. By using them you agree to the limits below. If you do not agree, do not use the software.

Independent product

Terminus Veil is not affiliated with, endorsed by, or sponsored by Robinhood Markets, Inc. or any Robinhood company. References to Robinhood Chain mean a public chain configuration (RPC, chain id, explorer) that a user or operator may point at. They are not a claim of partnership, listing, or official status.

What you are using

v0.1 is experimental. It is a public title registry. It is not a mixer. It does not hide senders, receivers, or amounts. It does not issue a token, ticker, or sale. It does not take custody of assets. A leaf is a hash you choose to stamp; it is not a warranty that an offchain object exists or that you have legal title to anything.

Your keys, your writes

You are responsible for wallets, seed phrases, RPC endpoints, and network fees. Stamp and transfer are irreversible once included. Losing the owner key means losing the ability to transfer that leaf. Calling ownerOf on a leaf you did not stamp does not give you rights in any offchain property.

Public record

Everything written by the registry is public. Do not stamp personal data, secrets, or anything you are not willing to publish. Operators of RPC nodes, explorers, and wallets may keep their own copies.

No deployment promise

A zero registry address means the contract is not deployed. Status will show OFFLINE / not deployed in that case. A local test node is not a public network. This build does not promise a verified public address or ongoing hosting.

Acceptable use

You may not use Terminus Veil to commit crimes, to launder value, or to mislead others into thinking a public hash is a licensed security, bank deposit, or mixed funds. You may not present this software as a Robinhood product.

No warranty

The software is provided “as is”, without warranties of any kind, including merchantability, fitness for a particular purpose, and non-infringement. Contract bugs, RPC outages, chain reorgs, and browser failures can lose or strand titles. To the extent law allows, authors and hosts are not liable for indirect, incidental, or consequential damages, or for lost profits, data, or titles.

Changes

A later copy may change these terms. The copy you opened is the copy that applies. Source in this repository is MIT-licensed where marked; these terms do not replace that license for the code.