Nicolas Ramsrud (@Nicram) header
Nicolas Ramsrud (@Nicram) profile picture

Co-founder CEO @LurkLab

Seattle, WA
Joined October 2021
Photo by Nicolas Ramsrud (@Nicram)Photo by Nicolas Ramsrud (@Nicram)Photo by Nicolas Ramsrud (@Nicram)Photo by Nicolas Ramsrud (@Nicram)Photo by Nicolas Ramsrud (@Nicram)Photo by Nicolas Ramsrud (@Nicram)Photo by Nicolas Ramsrud (@Nicram)Photo by Nicolas Ramsrud (@Nicram)Photo by Nicolas Ramsrud (@Nicram)Photo by Nicolas Ramsrud (@Nicram)
Nicolas Ramsrud retweeted
Lurk (a LISP dialects that compiles into a flat ZKP-friendly circuit) is one of the coolest projects I've worked on in the blockchain space
3
4
40
1,725
Nicolas Ramsrud retweeted
Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the Government for a redress of grievances.
Tim Walz: “There’s no guarantee to free speech on misinformation or hate speech and especially around our democracy”
202
1,285
62
9,114
562,717
Nicolas Ramsrud retweeted
Replying to @Nicram
The early-grey-bald are the thrice-blessed.
1
1
1
337
Nicolas Ramsrud retweeted
This ZK timeline feels like the 80s chip wars: Intel vs. Arm vs. Texas Instruments. And yes, someone likely gets relegated to calculators and another misses client-side compute entirely. The story is not who wins, but what internet-equivalent fast, commoditized ZK enables.
ZK proofs have become critical to blockchain privacy and scaling.
6
12
75
6,252
One thing I've learned is that a *lot* of people consider phones to be inherently insecure and they go to some effort to sequester their high-value stuff onto their desktop and keep it off of their phone. That's backwards! Phones are secure. Desktops are not.
1
11
8
87
19,668
Nicolas Ramsrud retweeted
It is absolutely possible to write DeFi protocols (and much more) while relying on ZKPs for privacy - this is exactly what Miden was designed to do. The main trick is to reimagine how the state works and instead of using a monolithic state adapt the Actor Model (something used in distributed systems for decades). Then we can have private actors that can interact with public actors which control the shared state. Or we could have semi-private actors (the state is known to some set of users, but not to the entire network) and these can also interact both with fully private actor or public actors. This is a very powerful model that covers a large number of DeFi use cases - from anonymous AMMs and CLBOs, to private compliant stablecoins. And one other nice thing: to write these DeFi protocol, we don't need engineers who understand ZKPs - you can write everything in Rust. I do like FHE - really cool technology and it does enable a few use cases which ZKPs cannot address (i.e., having truly private shared state) - but it also comes with huge performance overhead for the network. The beauty of ZKPs is that they actually reduce the network load - a transaction proven locally does not need to be executed by the network (verifying ZK proofs is very cheap) - we call this concept the Edge blockchain. While with FHE, every transaction becomes 100x (or 1000x) more expensive for the network. ASICs will help here for sure, but this also means that every validating node will need to run these ASICs or otherwise they won't be able to follow the network. And requiring every node to have an ASIC is kind of like requiring every Bitcoin node to be a miner.
Replying to @KyleSamani
6/ b) is the most subtle and hardest to understand. This is where ZK fails To understand why, let's consider the simplest privacy app: zcash (no defi). When you submit a shielded zcash transaction, you produce a proof that says, roughly "I am sending coins such that my balance remains >0 after this transaction." Well, if you aggregate 1000 of those transactions and then look at the state of the chain as an outsider, what do you know about the state? Nothing Now imagine trying to do DeFi on top of that. How do you do DeFi if your transaction literally cannot see or interact with anyone else's assets A bunch of teams have been trying to address this over the last decade, including Aztec, Aleo, and probably quite a few more that I cannot recall atm. The fundamental challenge each of these teams has to contend with is the challenge described above. Basically, how do you design ZKPs to allow for selective information to be seen by the outside world (eg how much collateral is backing a loan) Now consider being a DeFi developer. You have to not only design your DeFi protocol, you have to do so 1) in a partially hamstrung way, and 2) you have to understand how ZKPs work. Who wants to be the developer building a DeFi system that has 9 or 10-figures in it with all of these additional risks. This is scary stuff Many of the zk DeFi teams have been working to try to make this stuff more understandable, but the underlying reality is just extremely difficult to contend with. Moreover, this requires rebuilding every DeFi primitive from the ground up. The fundamental challenge here is that DeFi as we currently know it *requires the ability to reason about globally shared state.* Perhaps there is a way to rebuild DeFi from the ground up with selective reasoning, but I am extremely skeptical of that claim. And demonstrating that claim to the world at large in a way that everyone else will believe it will be a decade long endeavor given how much technical risk is there with dozens of bespoke zk circuits. So what is FHE? FHE allows you compute over encrypted data. This has been considered the holy grail of cryptography for decades. Thinking about private DeFi using FHE as the primary cryptographic construction is actually quite simple. You think about it the same as if it was transparent! It's just that magically, everything is not transparent, but you can still compute over it anyways Yes, this is magic
10
11
3
83
10,616
I love this thread about the huge positive impact from network effects of open standards. My one quibble is I suspect Christian might be thinking of national-government-issued currencies as being the open standard everyone can agree on, and I don't believe that. :-) But read it:
1/ "Open always, eventually wins." Money is the last closed network. The next step is neutral, permissionless rails anyone can build on. Full talk ⬇️
2
8
90
9,418
finally trending!
582
119
62
3,177
240,697
We are entering a phase where Crypto in large entreprises shouldn't be a product vertical but a horizontal function across teams. Beyond speculation, crypto isn't a product—it's infrastructure, invisible to users yet that empowers other products.
22
10
4
154
14,588
Nicolas Ramsrud retweeted
The dollar will debase due to debt. The Fed must print more to pay obligations. Bitcoin will attract capital as a scarce asset, a fiat hedge. Zcash will attract even more as an encrypted scarce asset. Free from debasement. Free from censorship. Bitcoin, but encrypted.
Bitcoin is insurance against fiat. ZCash is insurance against Bitcoin.
25
51
6
406
48,257
Nicolas Ramsrud retweeted
Congrats to @nicram and team on their continued progress. Since Day 1, they've used Succinct to build infrastructure for private and provable apps. Succinct will power a universe of private applications 🔜
This quoted post is unavailable.
18
5
96
11,315
Nicolas Ramsrud retweeted
Appreciation of privacy has always required mainstream adoption of transparent blockchains, creating enough problems from unnecessary oversharing, for “privacy on permissionless blockchains” to be valued. One of those things where it’ll be slowly… slowly… then all at once.
62
43
19
348
130,109
Nicolas Ramsrud retweeted
Thank you for such kind words, Nicolas! I love Lurk, and if I could start Miden from scratch, it would share even more similarities with Lurk (or maybe even be identical to it)
This quoted post is unavailable.
1
2
16
1,651
Before working at a venture fund, I believed privacy both online and in crypto was important for obvious moral and commercial reasons. Now I believe the lack of privacy onchain is one of the biggest sources of friction, if not a dealbreaker, for many institutions. It's critical.
72
30
21
313
69,174
Nicolas Ramsrud retweeted
🚨 There’s a large-scale supply chain attack in progress: the NPM account of a reputable developer has been compromised. The affected packages have already been downloaded over 1 billion times, meaning the entire JavaScript ecosystem may be at risk. The malicious payload works by silently swapping crypto addresses on the fly to steal funds. If you use a hardware wallet, pay attention to every transaction before signing and you're safe. If you don’t use a hardware wallet, refrain from making any on-chain transactions for now. It’s still unclear whether the attacker is also stealing seeds from software wallets directly at this stage. Excellent report here: jdstaerk.substack.com/p/we-j…
2,882
6,728
4,409
18,058
9,955,696
Nicolas Ramsrud retweeted
Given zk do you need more than one permissionless settlement layer
4
6
11
8,242
Zcash is now the fundamental privacy layer for all of crypto. There’s just one thing you need to understand: Acquire and hold shielded Zcash *today* and you’ll get strong privacy with any chain when you spend tomorrow. But if you wait until you want to spend, you won’t.
🚨 #Zcash just became crypto’s privacy anchor ⚓️🔐. With @zashi_app's shielded off-ramp, it solves the “fresh address” (aka gasless withdrawal) problem! Not just for ZEC, but for any supported chain. This is big! 👉 teapaw.org/zashi_app/status/19610… What’s the “fresh address” problem? After a mixer deposit, you want to withdraw to a new address B. However, B has no gas to claim. If you top it up from a known wallet/CEX, you link yourself. One funding tx can kill anonymity. How Tornado Cash handled it: relayers. You make a zk-proof; a relayer submits the withdrawal and pays gas, the contract pays B and the relayer fee. On-chain, A ↛ B remains unlinkable. But there’s a catch… Relayer trade-offs: they see B, plus timing/IP metadata; you rely on them to stay online, act honestly, and avoid censorship. Even if the ZK holds, privacy now depends on a semi-trusted off-chain actor. More coordination, cost, centralization. Zcash + Zashi: buy/receive ZEC → shield it → in Zashi, swap shielded ZEC into a “fresh address” on the chain you care about (uses NEAR Intents/@NEARProtocol). Use that address to withdraw from the mixer! No relayers needed. This solves the “fresh address”bootstrap for the rest of crypto. You can spin up funded fresh addresses on supported chains privately. Use mixers/privacy pools elsewhere without relayers. Shields up. 🛡️
4
44
15
169
56,548
Nicolas Ramsrud retweeted
4chan is suing the UK government over their speech laws. The opening is quite something.
929
4,373
713
47,846
2,642,984
Nicolas Ramsrud retweeted
The head of DOJ's Criminal Division says there will be no Section 1960(b)(1)(C) charges against developers who lack custody and control over user assets. Roman Storm was just convicted on this exact charge under this exact circumstance. Justice for Roman means dropping the case.
Replying to @iampaulgrewal
Where “software is truly decentralized and solely automates peer-to-peer transactions, and where a third-party does not have custody and control over user assets, new 1960(b)(1)(C) charges against the third-party will not be approved.”
51
82
4
394
46,983