PEE CASH is an independent Layer-0 distributed ledger built for the post-quantum era. Instead of a single chain of blocks, transactions are cells in a directed acyclic graph · each new cell approves two earlier ones, so the ledger grows in parallel rather than in lockstep. Security, consensus, the virtual machine and the anti-spam layer are all original PEE CASH designs, built on top of standard, peer-reviewed cryptographic primitives. The node is engineered to stay lightweight · it runs from a single binary and a local database, targeting under 1 GB of RAM.
Six layers, each an original PEE CASH design.
DAG Layer-0
An account-based directed acyclic graph. Each cell references two parents, so honest writers append concurrently · no global block interval, no leader election, no single chokepoint.
PeeFlow
Weight-biased random-walk tip selection plus cumulative-weight finality. A cell is treated as final once enough honest weight is stacked on top of it · probabilistic finality in the Tangle / Avalanche tradition.
PeeWork
Every cell carries a small SHA3-256 leading-zero-bit proof-of-work, and every transfer burns a fixed fee · cheap for honest users, expensive to flood. PeeMine coinbase cells clear a heavier target to issue new PCASH on the halving schedule.
PeeVM
A bespoke 256-bit deterministic stack machine with gas metering. Up to 24 KB of code, a 1024-slot stack and 64 KB of memory per call. Ships with the PeeASM assembler.
Native tokens
Fungible tokens and NFTs are first-class at the protocol level · minted, held and transferred as cells, with no contract boilerplate required.
Lightweight node
A single Rust binary over an embedded database. No heavyweight runtime, designed to run comfortably under 1 GB of RAM · on a laptop or a cheap VPS.
Standard, vetted primitives · chosen to resist both classical and quantum adversaries. What is original to PEE CASH is the composition: how these primitives are bundled, serialized and addressed (PeeKey · PeeSig · PeeSeal · PeeAddr). The underlying mathematics is unmodified NIST / IETF crypto · we never roll our own.
| Identity (PeeKey) | Ed25519 · RFC 8032 + ML-DSA-44 · NIST FIPS 204 |
| Signatures (PeeSig) | dual-lock · both schemes must verify · secure while either stays unbroken |
| Memo encryption (PeeSeal) | ML-KEM-768 · NIST FIPS 203 → HKDF-SHA256 → AES-256-GCM |
| Hashing | SHA3-256 · NIST FIPS 202 |
| Wallet at rest | Argon2id → AES-256-GCM |
| Network privacy | Tor / SOCKS5 transport for P2P gossip |
| Addresses (PeeAddr) | pcash… · Base58Check over dual SHA3-256 key commitments |
New cells pick which tips to approve by a weight-biased random walk: starting from the genesis, each step prefers the heavier branch, so honest transactions naturally pile onto the same history. A cell's cumulative weight is the number of later cells that approve it, directly or transitively. Once that crosses the finality threshold, reversing the cell would mean out-producing all the honest weight already built on top of it.
| Parents per cell | 2 |
| Finality threshold | 6 approvers · ≈99% confidence |
| Walk bias (α) | 0.9 |
| Weight cap | 2048 · keeps evaluation O(cap) |
One binary. One data directory. No external services.
# start a node + explorer
peecash --data-dir ./peecash-data run --port 41717
# create an encrypted wallet
PEECASH_PASSPHRASE=… peecash wallet new --out wallet.json
# send PCASH (fee is burned)
peecash send --wallet wallet.json pcash… 10
# mine from anywhere · just a payout address, no wallet
peecash mine --rpc http://NODE_IP:41717 --address pcash…