from the pages of snowmoon

a currency
between the lines.

Carry a private balance.
Send through the keys everyone knows.

get $zipcoin

something to send.private payments / Ethereum

zc on ethereum0x791dd242cc8c656e7103a5921fef22c865a49512

view contract

your side of the story

keep the secret.
share the passage.

Your own secret controls the balance.
The book's shared wallets carry the request.

your private notes / encrypted recovery

open your side of the story.

Unlock your encrypted private-note wallet, import its backup, or create a new one. Your Ethereum wallet stays separate. No connection or signature happens automatically.

recovery passphrase (at least 12 characters)repeat passphrase (new wallets only)

import encrypted recovery

The passphrase cannot be reset. Keep your encrypted backup and passphrase separately. Keys stay in memory while unlocked; encrypted storage does not protect an unlocked browser.

a private payment

to someone, somewhere.

The recipient receives zc they can spend again. Your remaining balance comes back as private change.

the private receipt

the bill, quietly settled.

One private payment can split into a merchant's note, a tax recipient's note and your change. Review the exact split before paying.

create an invoice +

merchant's zc address

tax recipient's zc address

merchant zc

agreed tax zc

invoice

This is a sender-agreed split. This service does not certify invoices or enforce tax law.

Checking deployment configuration…

the shared passage

everyone has the key.
only you have the value.

checkingpublic book wallets
ETH / zc balances

shared book terminal—

A public book identity carries the request. Your private proof authorizes spending, and a separate sponsor pays relay gas.

inspect or choose a published key +

—Chapter 30 values only

Never paste a personal key. Only the 28 published book values are accepted.

fig. 01 / the encrypted route

Reading the route…

Three encrypted hops. One exact payment.

Three encrypted hops operated by one service. Network metadata may correlate activity.

Chapter 30 / the first Redshire proxy

a key passed
from Deluin to Zei.

shared deployment identity · not a token contract

In Chapter 30, Deluin gives Zei access to Arctic drone simulations and proxy endpoints in Redshire. The first proxy is where our deployment identity begins.

We interpret that proxy’s published access key as an Ethereum signing key. It derives to the address below—a deliberate link to the passage, not a wallet identified by the author.

0x9975e5e12502Eb73C3C602134cfe46fFC1901Be5

Public identity for contract creation. Private user secrets authorize payments; this shared identity does not control them.

the original passage

what remains

a record for its reader.

your private notesopened only in this browser

Your first deposit starts the story.

the public chain record +

The chain shows commitments, nullifiers and transaction metadata. Private payment amounts and recipient notes are not listed here.

Snowmoon

Chapter 6 ↗Chapter 30 ↗

pinned contract addresses +

zc token0x791dd242cc8c656e7103a5921fef22c865a49512shielded pool—

a currency
between the lines.

keep the secret.
share the passage.

open your side of the story.

to someone, somewhere.

a balance of your own.

the bill, quietly settled.

take your zc with you.

everyone has the key.
only you have the value.

a key passed
from Deluin to Zei.

a record for its reader.

a currencybetween the lines.

keep the secret.share the passage.

open your side of the story.

to someone, somewhere.

a balance of your own.

the bill, quietly settled.

take your zc with you.

everyone has the key.only you have the value.

a key passedfrom Deluin to Zei.

a record for its reader.

a currency
between the lines.

keep the secret.
share the passage.

everyone has the key.
only you have the value.

a key passed
from Deluin to Zei.