● Set up · Your responsibilities

Compliance
what you distribute is yours.

SLUICE is software that reads a chain, divides an amount and prepares unsigned transactions. What a project distributes, to whom and how it describes it is the project's and the operator's decision and responsibility, in their jurisdictions. Nothing on this page is legal, tax or financial advice.

01The legal character is yours

Paying token holders a share of something can, depending on the facts and the jurisdiction, be treated as a regulated activity, for example as an investment contract. SLUICE does not make that determination, and using it does not make a distribution lawful or exempt from any rule. Check with counsel in your jurisdiction, and in every market you serve, before you run rounds for a project.

02The words are yours too

Rewards, distribution, revenue share, dividend and yield all ship as presets, and a custom preset lets you write your own. The preset changes no number. Which word is appropriate for a given project is a legal question for that project, and the choice is the operator's and the project's.

03No number in the future tense

SLUICE is designed to display only what has been measured: figures with a signature, a slot or a published hash behind them.

Shown, because it is measured	Not built, because nobody can know it
Total paid to date, from verified signatures The last round and its date A realised rate over a past window, printed with the window and the round count, never annualised	A projected rate of any kind An expected-amount preview A "what holders would get" calculator Any figure based on a guess about future income

Every dry-run figure carries an evidence record, and there is no evidence type for a projection; test/report/measured_only_test.dart checks that. When the asset sent is not the snapshot token, SLUICE states units paid per whole token held rather than a percentage, because a percentage would need a historical price it does not have. How you present these figures to holders remains your responsibility.

04Keys and signing

SLUICE holds no key, derives none and has no method that produces a signature; its RPC client has no sendTransaction. It has no server, so it relays or submits nothing on anyone's behalf. The project's own wallet funds and signs every batch. These are technical facts about the software; they do not by themselves settle how any law applies to the operator or the project. If you add a server that coordinates or submits transactions, the legal analysis may change: check with counsel first.

05Privacy

SLUICE stores addresses and amounts. It has no concept of a user, an account, an e-mail or a referral code, and it does not map a wallet to a person. Exports contain addresses and amounts, which is what makes a round auditable; where you publish them, and whether that is permitted where you operate, is your decision.

06Before the first round

You have advice from counsel in your jurisdiction on what the project is distributing and how it may be described.
The project knows the snapshot method (current slot or time-weighted), the exclusions and the distribution rule before it funds.
Your fee is disclosed to the project; the dry run shows it before anything moves.

Compliancewhat you distribute is yours.