Sevrin

Public terms. Private recipients.

Issue verifiable token allocations on Starknet without publishing who received them or which wallet eventually claims.

Create an allocationSee the privacy boundary

One claim link · two visibility zones

The server can route

sevrin.app/claim/7cN2mQ…

Only the recipient can decrypt

#N0p7Qv…private-decryption-key

Public

Allocation totals
Unlock schedule
Credential root

Private

Recipient identity
Wallet mapping
Claim secret

From allocation to private balance.

The public supply remains auditable while delivery and destination stay outside the public graph.

  1. 01

    Issue

    Label recipients, choose the amount and unlock date, then generate one encrypted link per allocation.

  2. 02

    Commit

    Fund and finalize the aggregate allocation on Starknet in one atomic wallet transaction.

  3. 03

    Deliver

    Send each recipient their individual private link through a channel you trust.

  4. 04

    Claim

    The recipient decrypts locally and settles into a STRK20 private balance.

Privacy with an honest boundary.

Sevrin does not hide allocation amounts or unlock timing in V1. It hides the relationship between a beneficiary, their one-time credential, and the wallet receiving the private balance.

The API stores encrypted claim envelopes and hashed lookup tokens. The decryption key remains in the URL fragment, which browsers do not send to the server.

Start issuing