Voodoo (@zkVoodoo) header
Voodoo (@zkVoodoo) profile picture

Money hasn't been real since we got off the gold standard.

Joined August 2020
Photo by Voodoo (@zkVoodoo)Photo by Voodoo (@zkVoodoo)Photo by Voodoo (@zkVoodoo)Photo by Voodoo (@zkVoodoo)Photo by Voodoo (@zkVoodoo)Photo by Voodoo (@zkVoodoo)Photo by Voodoo (@zkVoodoo)Photo by Voodoo (@zkVoodoo)Photo by Voodoo (@zkVoodoo)
Why is ZEC important right now? Because financial privacy has never mattered more. As surveillance continues to grow, Zcash gives people the freedom to protect their transactions while choosing the level of privacy they want.
15
14
2
150
16,697
Zcash is the most thrilling story you will share with your grandchildren.
2
1
14
223
I've been there, and everything went into RESET mode. Money could fade, but knowledge never does. So it's my second time, but this time will be x10 faster than before. Lesson learned.🤌
imagine nobody believing in you then boom, you're a millionaire bro
26
Bruh, this world is so fucked up😂
This quoted post is unavailable.
21
whole 20s and more. Priceless, right? :)
wasted half my twenties in the cesspool called crypto
29
Voodoo retweeted
Replying to @VitalikButerin
bro wants a 401k for degens. i'm listening :)))
2
1
8
1,080
They will try every possible way to force you to panic-sell.
49
There's a lot of skepticism around quantum-resistant cryptography, but it's one of the more urgent infrastructure upgrades we actually need. Quantum computers don't exist at scale yet, but the threat model is already real because of "harvest now, decrypt later" attacks. At the same time, AI is accelerating research across the board, including in quantum computing. Waiting until the threat is fully mature isn't a viable option.
1
64
Vitalik just flipped to total bull on leanPCS and the whole 8288 setup. Basically saying STARKs can scale way harder and faster than people thought, especially once we go post-quantum. @Starknet has been running this exact stack in production for years.
Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull. So let me explain some of these buzzwords in more detail. At the core, 8288 is about hyper-scaling data and execution for any computation that needs to get performed on a piece of data once, the chain learns the answer, and then we never need to see that data again. This sounds very specific, but it includes most "heavy" things happening on Ethereum: * Signatures * STARKs * Merkle branches * FHE computation * ... Really the first two are the most important. Once we go quantum-safe, signatures get bigger (65 bytes ECDSA -> 1-6 kB WOTS/SPHINCS depending on params) and ZKPs get much bigger (200-1000 bytes with groth16, PLONK, etc -> 128 kB with STARKs). This is unsustainable to put on chain, and 8288 fixes this. 8288 works by aggregating STARKs in the mempool. First, you as a user generate the STARK or SPHINCS signature or PCS opening (more on that last one later), and publish it. Then, each node listens. Each tick, each node takes all of the new objects that it has seen, and generates a STARK containing a list of "claims": "pubkey P has signed message M" "program X run on data D has output Y" "p(X) = Y for some polynomial P whose hash is H" and a proof that it has seen a signature, STARK or PCS opening verifying those claims. So the only information getting re-broadcasted is: (i) hashes of inputs and outputs (~64-96 bytes per claim) (ii) a single STARK proof per tick These aggregate proofs themselves get re-aggregated, and eventually you get to a single "master proof" in the block, that verifies that all of those statements are true. And so the only other data that has to actually go on chain is the statements (the (P, M), (X, D, Y), (X, Y, H) tuples I described above), not the actual signatures or proofs. This gets put into a specialized frame type. Now, let's get into the leanSPHINCS vs leanSTARK vs leanPCS part. The core distinction is: *what is the underlying object that the user is creating?* In leanSPHINCS, it's a signature, and specifically this particular type of purely-hash-based signature: ethresear.ch/t/sphincs-minus… If we add leanSPHINCS, then users will be able to make quantum-safe accounts, and pay only a little bit of gas (4096 for the 64 bytes) for each signature. So we get scalable quantum-safety for regular accounts, multisigs, etc. But it's only one specific signature scheme, you can't do anything else. In leanSTARK, it's a STARK. This means it's fully general: the user runs whatever computation they want, and publish a STARK of it. So you can use it for: * Any signature scheme (including eg. lattice-based ones if you like those) * A multisig that hides its internal logic * Privacy protocols * Private account abstraction: authorization logic that depends on some value hidden elsewhere in the state, so you can have one key that controls all your accounts without publicly linking them to each other Basically, it's a free for all, in the same way the EVM is a free for all. But leanSTARK has a practical downside. The protocol would have to specify the language in which users write their programs (we call this the "ISA"). So we would have to agree on that language. This is a really big deal - it's the first big case of "Ethereum moving beyond the EVM" - and so it's likely to take time to agree on the details of it, especially since the ISA would be hard to upgrade. There are benefits to taking longer on this, figuring out the ideal ISA, and then even giving access to it inside regular contracts. LeanPCS is the third option. PCS stands for "polynomial commitment scheme": a proof that P(x) = y. The most important thing to know about PCSes is that they are by far the most important "hard" component of a STARK (see here: vitalik.eth.limo/general/202… ). If you have a "magic PCS oracle" (which from the EVM's point of view, 8288 is), you can verify a STARK in ~20-40k gas. The most important gain with PCS is that there is far less that we need to choose. Specifying a PCS only requires specifying a field, and there is a natural option: the 128 bit binary field (technically, we can go more general than that, and say the 2^k-bit binary recursive tower field, going up to 256) LeanPCS is less efficient than leanSTARK onchain, because you would have to put multiple claims to prove one thing. But it's arguably more efficient offchain, because you have much more flexibility to choose proof systems. But most importantly, leanPCS gives you the same generality as leanSTARK, in a way that could potentially be implemented very quickly. And once we figure out the ISA, we can add leanSTARK later. So there is a route to getting "the cryptographic proof singularity" much faster than any of us expected, and that route runs through 8288 with leanPCS. firefly.social/post/x/212092…
1
62
Things are moving so fast that exchanges may soon need to know their agents (KYA) as much as they need to know their customers (KYC).
1
72
One of the things that changed is UX. Privacy always had a trade off with UX. Once UX improved, the cost for privacy wasn't so high. Another thing is simply awareness. It takes time for people to realize just how much is out there and what people might do with that information.
1
2
7
160
When Starknet book? @EliBenSasson
Crypto protocol whitepapers as books. $BTC $ETH $XRP $SOL $LINK $ZEC $HYPE $AVAX $SUI
1
3
77
7 AM and my brain is already deep-diving into MimbleWimble cut-through vs zk-SNARK trusted setups.
2
55
The road may be steep, but you’re already here
2
87
Remember these days well to remind yourself that creating wealth isn't an easy path.
4
132
Good morning! Fuck you, Trump.
2
107
Replying to @Cointelegraph
A glitch that jams up North Korea's laundering is the best bug I've heard of all year
1
41
3,742
Starknet is built to adapt ethereum:0xca14007eff0db1f8135f4c25b34de49ab0d42766
3
5
50
767
Bill Gates is a slimy, dirty, rotten, deep state, Epstein class POS!!
1
10
93
3,738
😂😂😂🥁
4
107
Freedom will win. Don't give up, my friend.
1
3
99