@zipcoinnetwork

zipcoin / zc private payments inspired by snowmoon.

 redshire
zipcoinnetwork.com/
Joined September 2026
  • Tweets26
  • Following3
  • Followers82
3Media
they took inspiration from the book. we took a key from chapter 30 and used its account to create zc on ethereum.
1
2
9
784
from a key in Snowmoon to a contract on Ethereum. zc was created through the book-derived account. deployment: etherscan.io/tx/0x7705d215f7… buy: etherscan.io/tx/0xfec1bfea0a… deposit: etherscan.io/tx/0x7a55dcf9b1…
6
1
14
1,543
The book key supplies a public identity. It does not protect the deposited funds. Spending requires the private note's ZK proof. Verifier contract: etherscan.io/address/0x6118b… Independent project. No Vitalik affiliation or endorsement.

Address: 0x6118bF70...77dc63909 | Etherscan

Contract: Verified | Balance: $0 across 0 Chain | Transactions: 0 | As at Oct-20-2026 06:05:47 PM (UTC)

etherscan.io
2
1
9
749
You can find every single wallet pk right here including ours we deployed from which is the first proxy one. the vision will only become more and more clear.
2
8
647
The thesis is simple. Wallet given by vitalik deployed this zipcoin and the other wallets in the book are part od the entire ZK protocol I build. #zc #zipcoin
1
3
9
738
open chapter 30. find the first proxy’s access key. derive its Ethereum address. then open zc’s deployment transaction. the same address appears as the CREATE2 creator. the connection is in the text and onchain.
2
1
4
607
everyone can read the keys in snowmoon. zc gives them a role: signing relay authorizations that carry zk payment requests. public book keys. private spending secrets.
4
1
10
781
in chapter 30, deluin gives zei network addresses and access keys. the first Redshire proxy’s key became the Ethereum identity that created zc. the exact value is still there in the text.
12
1
12
1,052
Imagine, vitalik gives you loads of pks in his book and someone decides to create a zk protocol using those wallets as custom signers Just imagine.
11
2
10
1,055
Y'all fudded and sold, now we can send it and agree the vision and lore is real.
2
1
4
973
what happens when a key printed in a story becomes a signing key in real software. that’s the connection we built with zc.
5
1
4
898
zc was created by the book wallet using EIP-7702 + CREATE2. our operator submitted the transaction and paid gas, keeping ETH out of a wallet whose key everyone knows. a direct deployment through a private funding bundle was also possible. we chose delegation. Before you fud, learn blockchain.
10
1
17
1,888
open the deployment transaction → Internal Txns → first CREATE2 row. From: the book wallet, 0x9975…01Be5 To: the zc contract, 0x7446…e696 the book wallet created zc via EIP-7702 delegation. our operator paid gas. Check it yourself here etherscan.io/address/0x9975e…

Address: 0x9975e5e1...FC1901Be5 | Etherscan

Address (Authority) | Balance: $0 across 0 Chain | Transactions: 2 | As at Oct-20-2026 08:23:20 AM (UTC)

etherscan.io
4
1
5
1,016
we used the keys published in snowmoon. chapter 30 contains 28 hex values under “Network” and “Proxies”. each derives to an Ethereum wallet when interpreted as a private key. check the original source here vitalik.eth.limo/snowmoon/ht…
2
2
860
more replies
the book keys also sign relay authorizations for zk payments. your own secret proves you can spend the private notes. the public keys carry the request. knowing a book key doesn’t give someone your private balance.
1
198
a public key from the book became our deployment identity. the others became part of the payment flow. PS never fund the book wallets directly..
1
168
snowmoon published the keys. we gave them a role on ethereum. zc uses the book’s wallets to sign relay authorizations for zk payments. your own secret proves the right to spend. public keys. private notes. vitalik.eth.limo/snowmoon/ht…
4
2
1,108
zc was deployed from a wallet whose key is published in snowmoon. the book’s keys also sign our relay authorizations. your own secret authorizes spending through zk proofs. from the pages to ethereum. zipcoinnetwork.com 0x74461dc947b97027bf3bfe58171636d6a5e5e696
4
5
2,441
Load more