Intmax pfp
Intmax
@intmax
Nethermind researcher discussed our whitepaper at #DefiSecuritySummit which covers how we’re building a scaling solution for #Ethereum which privately facilitates asset transfers. This creates a more efficient L2 #stateless infrastructure that is designed to support the global demand for privacy on #Ethereum. Tackling the Data Availability Problem One of the biggest challenges for blockchains and #rollups ensure data availability. For anyone hoping to verify the current state of a blockchain, the underlying transaction data must be accessible. In traditional Layer 1 blockchains, all transaction data is publicly available. Rollups, on the other hand, rely on the underlying blockchain’s data availability, verifying all transaction data on Layer 1 before generating a new block. But since this global data must be updated across numerous nodes, it significantly limits the number of transactions per second that the blockchain or rollup can handle.
1 reply
2 recasts
2 reactions
Intmax pfp
Intmax
@intmax
At INTMAX, we’ve taken a different approach. Instead of storing all transaction data on-chain, we provide a commitment to the set of transactions in a block (a Merkle tree root) and signatures from senders confirming they’ve received inclusion proofs. With this design, users can generate zero-knowledge proofs (ZK-proofs) of their balances by combining proofs of their sent transactions with proofs of the transactions they’ve received.Moreover, we use ‘Cyclic Recursive Zero-Knowledge Proofs’ to validate entire transaction chains efficiently. By proving only the most recent transaction, the system inherently validates the entire history, drastically reducing L2 costs while maintaining integrity. Users also receive asset proofs directly from block producers, eliminating the need for full database reconstruction, which is a major cost factor in traditional rollups. Our Three Block Types To handle deposits, transfers, and withdrawals efficiently, we use three specialized block types:
1 reply
0 recast
0 reaction
Intmax pfp
Intmax
@intmax
Deposit Blocks: Layer 1 users deposit funds into Layer 2 via a rollup contract, creating a deposit block with the recipient and amount. This block gets added to the list of blocks stored in the contract. Transfer Blocks: Aggregators build Merkle trees from transaction batches, collect signatures, and submit transfer blocks to the rollup contract. These blocks allow senders to move funds within Layer 2 by validating each transaction’s inclusion in the batch through Merkle proofs. Withdrawal Blocks: If you want to withdraw funds from Layer 2 to Layer 1, you first transfer the funds to your L1 account using the transfer protocol. A balance proof is then submitted to the rollup contract, which verifies it, creates a withdrawal block, adds it to storage, and completes the withdrawal.
1 reply
0 recast
0 reaction
Intmax pfp
Intmax
@intmax
Why This Matters As a result of these three types of blocks, we’ve reduced the amount of data stored on-chain (Only 5 bytes), improving scalability and privacy for users. Our #permissionless #stateless design eliminates the need for leader elections or coordination between block builders, simplifying rollup operations and increasing resistance to censorship. Additionally, peer-to-peer interactions allow users to update #ZK proofs and seamlessly continue transactions without adding extra data costs, making transfers more flexible and efficient. By combining Cyclic Recursive #ZKProofs, stateless infrastructure, and decentralized block production, we’ve created a rollup ecosystem that balances efficiency, decentralization, and, of course, privacy. We believe these innovations are key to fulfilling our mission at INTMAX: enabling private, scalable asset transfers for everyone.
0 reply
0 recast
0 reaction