@levelsio Don't forget about things like "tropenrooster" - where schools without AC decide to end the day early, so all working parents have to ruin their own working days to accommodate.
New EIP!
pERC20 - Privacy-Native Fungible Tokens
🔗 https://t.co/DBDudAF6I7
Highlights:
- Not ERC-20 compatible by design: pERC20 removes public balance/allowance concepts (no balanceOf/approve/allowance/transferFrom) and replaces transfers with a ZK note-based interface (transfer(PrivacyCall)), because public balances would defeat the privacy goal.
- Privacy-native from issuance: tokens are always represented as encrypted ZK-UTXO notes (Orchard-style actions with Groth16 proofs); there is no “public-to-private shielding” step—transfers are note→note and amounts/participants are private by default.
- Public, on-chain verifiable supply: totalSupply remains public and is updated only through controlled mint(amount, ...) and burn(amount, ...); transfers must conserve value (valueBalance == 0), enabling “no invisible inflation” while keeping balances private.
- Built-in compliance via frozen-root binding: every action commits to the contract’s cmxFrozenRoot, and the ZK circuit must prove the spent note commitment is NOT in the blacklist SMT. Admin can update the root (setFrozenRoot) to freeze/unfreeze specific notes without revealing normal users’ balances.
- Security-critical invariants and checks: implementations must prevent double-spends with nullifiers and must range-check each public field (< Fr) to avoid nf + Fr-style bypasses; the core bundle execution must not be publicly callable to prevent unaccounted supply changes; signature points must be curve/field validated and replay protection must bind chainId + contract + note data.
ELI5:
This EIP proposes a new kind of token standard for Ethereum where people’s token amounts and who they pay are hidden by default. Instead of keeping a public “balance” per account like ERC-20, the token exists as many encrypted “notes” (like digital cash bills) that can be spent with zero-knowledge proofs. Everyone can still see the total number of tokens that exist (totalSupply) so the issuer can’t secretly create extra tokens. It also adds an optional-but-built-in “freeze list” mechanism: the token contract keeps a public fingerprint (root) of a blacklist, and the zero-knowledge proof must show you are not spending a frozen note.
You start reading weird books.
You buy “The Bitcoin Standard” and then “The Fiat Standard” and then you accidentally end up reading Murray Rothbard, and then somehow you’re reading Mises, and then it’s 11:47 PM on a Tuesday and you’re 340 pages into “Human Action” and you’re highlighting passages about praxeology and your wife comes downstairs and asks if you’re coming to bed and you say “in a minute” but you don’t come to bed for two hours because you have just discovered that everything you were taught about economics in college was wrong, all of it, every single sentence, and now you can’t go back, you can never go back, you have been orange-pilled in a way that goes deeper than money, you have been epistemologically orange-pilled, you now believe that John Maynard Keynes was a charlatan and the gold standard was actually fine and the income tax is theft and you can never say any of this out loud at a dinner party ever again.
Today I became convinced that agentic engineering means left-curving everything: keep the stack, architecture, and product as simple as possible
Trad-engineering made everything way too complex. With LLMs, the simpler the system, the faster you can build, debug, and iterate
I just spun up the @levelsio stack: simple VPS, PHP, SQLite, and plain HTML/CSS/JS
I’m afraid he's right bois: LLM'ing is much easier with such a simple stack