jrcrypto.dev + 130 dapps created (@jrcrypto_dev) header
jrcrypto.dev + 130 dapps created (@jrcrypto_dev) profile picture

Dapp maker

Joined March 2023
Photo by jrcrypto.dev + 130 dapps created (@jrcrypto_dev)Photo by jrcrypto.dev + 130 dapps created (@jrcrypto_dev)Photo by jrcrypto.dev + 130 dapps created (@jrcrypto_dev)Photo by jrcrypto.dev + 130 dapps created (@jrcrypto_dev)Photo by jrcrypto.dev + 130 dapps created (@jrcrypto_dev)Photo by jrcrypto.dev + 130 dapps created (@jrcrypto_dev)Photo by jrcrypto.dev + 130 dapps created (@jrcrypto_dev)Photo by jrcrypto.dev + 130 dapps created (@jrcrypto_dev)Photo by jrcrypto.dev + 130 dapps created (@jrcrypto_dev)
jrcrypto.dev + 130 dapps created retweeted
💸 Today I invested in a new thing: Ethereum is essentially a public spreadsheet with every transaction being visible for everyone forever But that makes it impossible to use for banks because it's not private. Imagine you buy something and everyone in the entire world can see it? That'd be never be accepted So my friend @oskarth has been working on a new thing called @eth_systems that lets banks use Ethereum but while keeping transactions private Before this he was working for 10 years on stuff like zk-SNARK (math tricks that let you prove something is true without revealing the details) and advising the Ethereum Foundation, he's the most high IQ person I know, so when he started something that's for-profit (after lots of non-profit work) I asked to invest immediately YC always taught me to invest in people not companies, the companies (and product) can change (and should) and it can pivot into lots of other things, but if you trust the person you can estimate a higher likelihood of it (and your investment) working out If you like to see what they will make, follow @eth_systems 😊😊😊
Yesterday was my last day at the Ethereum Foundation. Today we are launching EthSystems. We build confidential systems for institutional Ethereum. I've spent close to a decade building privacy infrastructure in crypto: p2p messaging at @ethstatus, developing Waku protocols at Vac (both now part of @logos_network), mobile proving tooling with @zkmopro, teaching zero-knowledge proofs with my zkintro primer, and advising @ethereumfndn on privacy and access layer strategy. Most of that was aimed at individuals. The past year at EF's Institutional Privacy Task Force (IPTF) we've been looking at privacy for institutions. On the surface this might seem different, but there are a lot of similarities. There's also a very strong market need for it, and the timing is right. I've written in the past about the tension and overlap between cypherpunks and institutions. Twitter is not exactly the best medium for nuance, but right now we are at a sensitive point in time: the defaults for the next generation of financial infrastructure are being set, with or without us. I believe we need cypherpunks in the room when that happens. Excited to start @eth_systems together with my co-founder @motypes and @_rymnc as part of the founding team. See quoted announcement thread for more details. nitter.gq/eth_systems/status/207…
262
121
42
2,770
607,843
jrcrypto.dev + 130 dapps created retweeted
EIP-7503 Deep Analysis 1. What is EIP-7503? EIP-7503, also known as Zero-Knowledge Wormholes, is a proposal for Ethereum protocol-level privacy. It introduces a revolutionary protocol-level privacy solution that uses a "Private Proof-of-Burn (PPoB)" mechanism and zero-knowledge proofs to enable anonymous ETH transfers. The project leverages SHA256 to generate unspendable addresses, allowing users to prove control over burnt ETH without revealing the specific burn address, thereby creating a massive anonymity pool of millions of addresses. Compared to application-layer mixers like Tornado Cash, EIP-7503 offers stronger compliance, a larger anonymity set, and protocol-level resistance to censorship. 2. How is it Implemented? The core idea of EIP-7503 is a "Burn and Remint" model. This model breaks down the privacy process of a transaction into two separate and seemingly unrelated steps, aiming to break the on-chain traceability between the sender and receiver. 1️⃣Private Burn: A user first transfers a specific amount of ETH to a special "unspendable address." This is a regular transaction on-chain. Since this address has no associated private key, once the ETH is transferred, it cannot be retrieved by anyone, effectively "burning" the tokens. On-chain, this transfer cannot be directly identified as part of a privacy protocol; it can be interpreted as a transfer to a wrong address or a permanent donation, which is key to the mechanism's "plausible deniability." 2️⃣Private Proof: After the first step, the user generates a zero-knowledge proof (ZK-SNARK) off-chain. This proof does not disclose any sensitive information to the outside world, such as the original sender's address, the secret value of the burn address, or specific transaction details. Instead, it cryptographically verifies that the user did indeed transfer a specific amount of ETH to an unspendable address. 3️⃣On-chain Remint: The user then uses a new, unlinked address to submit the zero-knowledge proof generated in the previous step, along with the recipient address and a nullifier to prevent double-spending, to an on-chain verification contract. Once the proof is validated, the contract mints an equivalent amount of ETH to the new address, completing the fund transfer while severing any traceable link in the fund flow. 4️⃣Smart Change Management: The system includes an intelligent "change" feature, similar to getting change when paying with cash. When you remint your ETH, you don't have to withdraw the entire burned amount at once. For example, if you burned 20 ETH but only need to send 12 ETH to someone, the system automatically creates a hidden "change deposit" of 8 ETH that remains available for future use. This change amount is cryptographically protected - even though it exists on-chain, no one can see its actual value or link it back to your original 20 ETH deposit. This prevents attackers from using simple math (like noticing that 12 + 8 = 20) to trace your transactions. Think of it like breaking a $20 bill: the cashier doesn't know if that $20 came from your wallet or the ATM, and when you get $8 change, it's just another anonymous $8 bill. 3. Core Difference Analysis (EIP-7503 vs. Tornado Cash) 4. Security 1️⃣Known Attack Vectors and Mitigation • Hash Collision Attack: ▶️Risk: A Create2 address might collide with a burn address. ▶️Mitigation: An integrated PoW (Proof-of-Work) requirement and a 32 ETH limit. ▶️Difficulty: It would require approximately ~2^92 hash attempts, which is economically infeasible rather than theoretically impossible. For comparison, Bitcoin block mining requires approximately 2^79 hash attempts, making attacking EIP-7503 less profitable than mining Bitcoin. • Double-Spend Attack: ▶️Protection: A Nullifier mechanism prevents the reuse of the same burnt ETH. ▶️Implementation: An on-chain nullifier registry is used to track used nullifiers. ▶️Verification: The zero-knowledge circuit enforces a unique nullifier. • Circuit Implementation Vulnerability: ▶️Risk: A flaw in the ZK circuit could allow for the infinite minting of ETH. ▶️ Impact: This would be catastrophic and could lead to a collapse in the price of ETH. ▶️Mitigation: Requires extensive audits and formal verification to ensure security. 2️⃣Security Considerations for PoW Mechanism and 32 ETH Limit The 32 ETH limit in the proposal is based on multiple security considerations: ▶️ Prevents Large-Scale Attacks: Limits the potential loss in a single transaction. ▶️Limits Potential Economic Damage: In the event of a vulnerability, the loss is contained. ▶️Maintains Reasonable Transaction Cost: Ensures proof generation time remains acceptable. ▶️Balances Privacy and Utility: Provides privacy while considering the overall health and security of the network. Summary: When using any product that implements this protocol, one should carefully analyze its security and potential vulnerabilities by considering each of these risk points. 5. Fisrt Project Introduction 1️⃣@EIP7503 implemented a dual-token system based on the principles of EIP-7503. ▶️BETH: A private burn receipt token (1:1 with burnt ETH). ▶️WORM: A scarce terminal asset minted by consuming BETH. •Technical Stack ▶️ZK Framework: Circom & SnarkJS. ▶️Hash Function: Poseidon (a ZK-friendly hash function). ▶️Proving System: Groth16. • Smart Contracts: Solidity + OpenZeppelin. •Sepolia Testnet Contract Addresses: ▶️WORM: 0x78eFE1D19d5F5e9AED2C1219401b00f74166A1d9 ◦ ▶️BETH: 0x1b218670EcaDA5B15e2cE1879074e5D903b55334 2️⃣Degree of Adherence to EIP-7503 Standard •Areas of Full Adherence ▶️Private Proof-of-Burn Mechanism: Implements the core idea of EIP-7503. ▶️Zero-Knowledge Verification System: Uses ZK proofs to verify the burning action. ▶️Unspendable Address Generation: Follows the burn address generation standard (sha256(MAGIC_ADDRESS + secret)[12:]). ▶️Nullifier Double-Spend Protection: Prevents double-spending through the nullifier mechanism. •Custom Extensions ▶️WORM Token: Introduces a scarcity mechanism by linking the burning action to the minting of a new asset. ▶️Competitive Minting: WORM is allocated proportionally based on burn participation. ▶️Hard Emission Cap: A maximum of 100 WORM can be minted per block. ▶️Zero Pre-mine: A pure "burn-to-earn" economic model. •Implementation Progress and Current Status The worm.cx project has completed the following milestones: ✅ ZK circuit development ✅ Smart contract deployment (on Sepolia) ✅ Web front-end interface ✅ Sepolia real-time data tracking •Technical Performance Metrics: ▶️Proof generation time: Approximately 2 minutes on consumer-grade hardware. ▶️Circuit constraints: Optimized through proof decomposition. •Current Limitations: ▶️The project is currently limited to the Sepolia testnet. ▶️The proof-of-burn mechanism is still in development. 6. How to Participate in WORM 1️⃣Participate Through Official Channels You can visit the official website at worm.cx to join the second phase of Sepolia testnet mining. 2️⃣Participate Through AlphaLabs' Automation Tool Due to the long mining cycles, AlphaLabs has developed an automated tool based on the official code. This tool can perform: ▶️Fully automated burn ETH → bETH ▶️Fully automated participation ▶️Fully automated claim ⚠️ Warning: Since the automation requires sending transactions, you need to enter your private key into the AlphaLabs tool website. The tool will not save your private key; it is stored locally on your device. It is highly recommended to use a new, dedicated private key when experimenting with the Worm protocol to prevent loss of assets.
13
8
2
50
3,754
jrcrypto.dev + 130 dapps created retweeted
Build, Fight, Earn? Our servers are back online! come play minecraft with us and start earning basedmc on @base
4
5
29
695
jrcrypto.dev + 130 dapps created retweeted
Thanks for the talk my friend! @jrcrypto_dev already cooked with Cartesi and had fun with our @cartesiproject game night and ours and @EspressoSys back to the future! ETH Denver 2025 is over, but I can’t wait for the next one! Btw bubblewars is such a fun game!
1
3
11
329
jrcrypto.dev + 130 dapps created retweeted
1/ Updates from the last couple of weeks in the Ethereum ecosystem, a thread by @sassal0x. There’s so much happening in the Ethereum ecosystem that keeping up with it all can feel overwhelming, but allow me to give you the highlights. Let’s get into it 🧵👇
296
849
175
4,594
801,130
jrcrypto.dev + 130 dapps created retweeted
huh
1
24
jrcrypto.dev + 130 dapps created retweeted
Replying to @crypto_bitlord7
or your bills can handle $tip bots at erc20 pools go check usdc printer goes brrr tipsterxbets.com
2
7
95
jrcrypto.dev + 130 dapps created retweeted
GM Frens, grab a $TIP baaag, hold and be proud to be part of a decentralized betting platform that valued transparency, security, and user empowerment. tipsterxbets.com
3
5
7
204
jrcrypto.dev + 130 dapps created retweeted
Replying to @gainzy222
do you have time to check tipsterxbets.com Bet with $TIP with tg bot, premium services unlock with 5mil tokens. Dip from 200k to 100k, perfect entry.
3
4
7
69
jrcrypto.dev + 130 dapps created retweeted
Check out $TIP. A betting platform with its own working telegram bot for a better betting experience.
3
4
29