1 reply
2 recasts
2 reactions
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