A private team fund on NEAR · OutLayer TEE · Sputnik DAO

SODALIS

Prove you belong. Never say who you are.

A team fund you can ask for help without your email address ever being published. Prove you belong with your email; the chain records the rules, the decisions and the payments, never the address.

scroll

The problem

Asking for help shouldn't cost you your privacy.

An illustration. Maya's car breaks down three days before payday. Her team keeps a small fund for exactly this. But asking means telling the colleagues who run it that she's short this month. So she doesn't ask.

Every team fund, mutual-aid pool and community grant faces the same choice today, and every option fails someone.

01

Ask openly, and be known

The people who run the fund learn who is struggling. Some would rather go without.

02

Stay anonymous, and get farmed

One person, ten wallets, ten votes. The treasury pays whoever made the most accounts.

03

Trust a gatekeeper

Someone checks the emails by hand. Now that someone can be bribed, breached or subpoenaed.

The mechanism

A sealed letter, opened only inside an enclave.

I · Challenge

A subject line that names no one

Your fresh wallet gets a one-line subject: a hash of the guild, your wallet and a random salt, plus an expiry. It points at your wallet without saying so.

II · Signed email

Your mail host vouches for you

You send that subject from your work mailbox to any other address. Your company's mail server signs it with DKIM, the same signature that fights spoofing everywhere.

III · Sealed

Encrypted in your browser

The page drops every unsigned header and seals the email to the guild's inbox key. The key was derived inside the enclave; nobody outside it can open the letter.

IV · Enclave

Checked where no one can watch

The guild contract asks OutLayer to run its pinned verifier in an Intel TDX enclave. It checks the signature against a key the DAO approved, the domain, the subject and the expiry, and returns one thing: a fingerprint of the mailbox under a secret nobody has seen.

V · Seat

One mailbox, one seat, same transaction

If the fingerprint is new, the guild seats your wallet in the DAO tier for your domain: staff may approve payouts, public may ask for them. A second wallet from the same mailbox is refused.

Live, from testnet

Read off the chain as you load this page.

—
seats held
—
approved domains
—
attacks refused on chain
0
email addresses in the admission record, by design

Why NEAR

Remove any piece and the guild stops working.

OutLayer · yield and resume

The contract itself calls the enclave and acts on its answer in the same transaction. No backend sits between the proof and the seat.

OutLayer · attested secrets

The guild's master secret was generated inside the keystore and is released only to one verifier build, only on runs the guild requests. The guild account owns it.

Sputnik DAO · roles

Tiers are DAO roles. The guild holds a gatekeeper role that can only add or remove members; spending stays with the DAO's own rules.

NEP-366 · meta-transactions

The member is whoever calls join, not whoever pays gas, so a relayer can sponsor a brand-new wallet with no funding trail of its own. Tested; the live Join page uses a visible drip instead.