Skip to content
Setrya

How it works

From fee statement to private settlement

Picture a launch studio paying a promoter 20% and a creator 10% of last month's fees. The export shows $1,200 of fees, a $50 refund, and a $20,000 line that is trading volume. Here is what happens to it.

Steps

  1. 1

    Import the real record

    Upload the CSV your launchpad or platform exports. You map its columns, and Setrya flags rows that look wrong: a line labelled fees that reads like trading volume, a duplicate ID, a refund that needs a decision. Nothing is committed until you review every row.

    Each row keeps its raw fields and a hash; the file keeps its SHA-256 fingerprint.

  2. 2

    Apply agreements to the eligible base

    Agreements are versioned terms: 20% of eligible realised fees, a fixed 1 ZEC per period, with caps and refund rules. If a version changes mid-month, the fee base splits by date. Exclusive shares on one pool cannot exceed 100%.

    Amounts are exact decimals. ZEC is integer zatoshis. No floating point anywhere.

    October creator feesIllustrative data — not a real payment
    Source rows
    Creator fees, week 40
    FEE-4401
    		1,200.00 USD
    Trading volume, week 40
    VOL-4402 · Volume is not fees earned
    		20,000.00 USD
    Refund of disputed launch fee
    RFD-4403 · Nets against this period
    		-50.00 USD
    Eligible fee base1,150.00 USD
    • Promoter Ana 20%230.00 USD4.6 ZEC
    • Creator Bo 10%115.00 USD2.3 ZEC
    • Studio Cy 5%57.50 USDHeld: no address
    1. Imported
    2. Calculated
    3. Exception resolved
    4. Frozen
    5. Approved
    6. Shielded payment
    7. Confirmed
    8. Statement
  3. 3

    Decide the exceptions

    An unresolved row holds only the payouts that depend on it. You exclude it, correct it, or hold the payment, with a reason. The inbox previews how totals change before you save.

    Decisions are locked once you freeze; later changes need a new revision.

  4. 4

    Freeze, approve, inspect, sign

    Freezing hashes every input: rows, agreement versions, rates, address versions, payer account. Approval needs your password. The wallet service on your server then builds a FullPrivacy PCZT, and Setrya compares the wallet’s inspection with the approval to the zatoshi before you authorise signing.

    Any transparent output, cross-pool amount or mismatch blocks the send.

  5. 5

    Confirm and issue statements

    Setrya stores the signed transaction before broadcasting it, then watches confirmations. Each partner gets a statement and, if you choose, an encrypted link only they can open.

    No status says paid until the confirmation threshold is reached.

Privacy boundaries

Who can see each step.

The same rules hold at every stage. Read the privacy model.

What the operator can see

Everything in your project, decrypted only while your workspace is unlocked.

What recipients can see

Their own statement: fee base, rule, amount, payment status and txid. Nothing about other partners.

What the public chain can see

That a shielded transaction exists and when it was mined. Not its recipients or amounts.

What Setrya cannot hide

Timing, your server’s network activity, anything readable by your host administrator, and statements a partner forwards.

Close your next period in one sitting.

Start on testnet with a sample project, then point it at your own fee export when the numbers match yours.

Open workspaceExplore the sample