

Shurli
19 posts

@ShurliNet
AI-native P2P infrastructure for the Zero-Human Network. Connect devices and agents directly. No accounts, no cloud, no middleman. https://t.co/Bj5DzjSh3T




Alright, imagine a small town with 10 restaurants. Every restaurant employs local people - cooks, servers, dishwashers. Those employees eat out at each other's restaurants on their days off. The whole town's dining economy is basically a circle: restaurants pay workers, workers eat at restaurants. Now a magical cooking robot arrives. It costs half what a human cook costs and never calls in sick. Restaurant owner Maria looks at the numbers. If she replaces her three cooks with robots, she saves a fortune on wages. Yes, those three fired cooks will stop eating out around town, but that lost spending gets spread across all 10 restaurants. Maria's place only loses a tenth of it. The savings massively outweigh her tiny slice of the demand hit. So she buys the robots. Every other owner does the exact same calculation and reaches the exact same conclusion. They can all see what's coming. They even talk about it at the chamber of commerce meeting. "If we all do this, we'll have no customers left." Everyone nods gravely. Then they all go home and buy the robots anyway, because any single owner who holds back just eats the demand loss from everyone else's layoffs while also paying higher wages. You'd be the expensive restaurant in a town of unemployed people. Six months later, the town is full of incredibly efficient robot-staffed restaurants with almost nobody coming through the doors. Every owner is making *less* money than before they automated. The workers are obviously worse off too. The surplus didn't transfer from workers to owners - it just evaporated. Now the town council meets to figure out what to do. Someone suggests giving everyone a basic stipend (UBI). That helps people eat, but it doesn't change the math any restaurant owner faces. The robots are still cheaper than humans, and the demand loss from firing one more worker still gets spread across 10 restaurants. Owners keep automating at the same rate. Someone suggests taxing restaurant profits and redistributing the money. Same problem. You're taxing 30% of profits instead of 0%, but 70% of a higher number is still better than 100% of a lower number. The incentive to automate doesn't budge. Someone suggests the owners just agree to limit automation. They shake hands on it. Then Maria thinks, "If the other nine stick to the deal but I quietly add one more robot, I pocket the savings and the demand hit is negligible." Everyone thinks this simultaneously. The deal falls apart by Tuesday. Someone suggests giving workers ownership stakes in the restaurants. This helps - workers who own shares spend their dividends at other restaurants, recycling some money back. But it can't fully close the gap because workers only spend a fraction of their dividends on dining out. Some leaks away to rent and groceries and everything else. Finally, the town accountant proposes something different: a per-robot tax set exactly equal to the demand damage each robot imposes on the *other nine restaurants*. Now when Maria considers adding one more robot, the tax forces her to pay for the full demand destruction, not just her one-tenth share. The math flips. She only automates up to the point where it's genuinely efficient for the whole town. And here's the elegant part - the tax revenue funds retraining programs that help fired cooks become, say, robot maintenance technicians who earn comparable wages. As those retrained workers start spending in town again, the demand problem shrinks, which means the tax can shrink too. Eventually, if retraining works well enough, the tax approaches zero on its own. That's the whole paper. The trap is that every owner's individually rational decision is collectively suicidal, and most of the obvious policy fixes operate on the wrong part of the equation.


Just published the Shurli whitepaper: Distributed Social Proof for P2P Trust Without Blockchain It outlines how trust can emerge from overlapping behavioral observations by independent agents - no ledger, no tokens, no central authority. shurli.io/shurli.pdf












What Shurli actually does (and why nothing else does all of it) Everything here is shipped code. Not a roadmap. Not a pitch. Tested on physical hardware across satellite, cellular, terrestrial WiFi, and USB LAN networks. Shurli is a single Go binary that gives you a private P2P network with: - Automatic NAT/CGNAT traversal and path selection - Cryptographic identity and authorization (Ed25519 + macaroon capability tokens) - Zero-knowledge anonymous authentication - Private reputation proofs - Unified BIP39 seed identity (one 24-word phrase recovers everything) - Full Prometheus observability (40 metrics, pre-built Grafana dashboard) - Zero cloud accounts. Zero third-party services. THE NETWORKING When two peers connect, Shurli finds the best path automatically: 1. LAN (mDNS) - same local network 2. Direct IPv6 - path probing confirms reachability 3. Direct IPv4 (STUN) - hole punch 4. Relay - fallback Switch from cellular to WiFi to hotspot? Shurli re-evaluates and transitions. No reconnection. No config changes. THE AUTH Four layers, each enforced by math, not policy: - Identity: Ed25519 keypair, encrypted at rest - Allowlisting: peer ID whitelist, rejected before any data flows - Capability tokens: HMAC-SHA256 chains that can only be made stricter, never looser. Mathematical guarantee. - Roles: admin/member with configurable invite policy THE ZERO-KNOWLEDGE PART This is where Shurli diverges from everything in this category. Standard auth reveals your identity on every connection. Shurli's ZK auth proves "I have a key in the authorized set" without revealing which key. The relay learns one fact: an authorized peer connected. It never learns which one. PLONK on BN254. Poseidon2 hash. Same construction Ethereum L2 rollups use for transaction validity. - 520-byte proofs - 1.8s to generate - 2-3ms to verify - Scales to 1M+ peers Reputation range proofs: prove "my score is above X" without revealing the number. Score is committed in the Merkle tree, binding, not self-reported. ONE SEED, EVERYTHING 24-word BIP39 mnemonic derives your identity key, vault encryption key, and ZKP circuit keys. Same phrase on any device = same identity. shurli init to generate, shurli recover on any machine. THE NUMBERS 37 MB binary. 884 tests across 20 packages. 11 custom P2P protocols. 42 admin API endpoints. 24 subcommands. Zero cloud accounts required. Zero subscriptions. Runs on a $5/month VPS. WHO THIS IS FOR People who want a private network they fully control. Not "we promise not to look" private. Mathematically private. Inspired by operators who chose to shut down rather than compromise their users. Full post with diagrams: shurli.io/blog/the-shurl…

