Merkle tree

The N-O-O-N-I-F-I-C-A-T-I-O-N.

How to Implement a Merkle Tree in Solidity.

October 23, 2023.

October 23, 2023.

The H-A-C-K-E-R-N-O-O-N newsletter.

Your career is not your personality.

sorry april 21st 2025 april 21st 2025 top 5 stories on the hacker noon homepage 199 the n-o-o-n-i-f-i-c-a-t-i-o-n how to implement a merkle tree in solidity the 12th of november 2023 the 12th of november 2023 top 5 stories on the hacker noon homepage 200 The N-O-O-N-I-F-I-C-A-T-I-O-N.

How to build products people love in 2024 and beyond.

73.

Sparse Merkle Trees.

The new state model for LISC's interoperability this blog post is part of the interoperability blog post series taking a closer look at various aspects of the LISC interoperability solution.

74.

So you can see those activities actually on-chain.

And then for our users, they can do Merkle Tree Proof Reserve on their own funds and know that their own funds are still part of the Merkle Tree.

And we've also published another special round of the Merkle Tree Proof Reserve right after the incident so that users feel more comfortable in knowing what's your proof of reserve rate, which I think is 131%.

at that time.

While we obviously publish proof of reserve on a monthly basis after FTX collapsed, and we've been doing that for almost four consecutive years.

3.

How to implement a Merkle tree in Solidity without Merkle trees, blockchains would be too cumbersome, and Merkle proofsolo for cost-effective verification of data authenticity.

Solidity now.

4.

You can see there's a whole transaction tree that's embedded in the block, in the block header.

This, this is what's called, this tree here is what's called a Merkle tree.

which means that essentially all of these transactions that represent the block, and we'll talk about transactions in just a minute, essentially they are sort of committed to in the block header.

Yeah, so this value here is a hash value that commits to all the transactions that are embedded in this particular block.

So I think that if you started to see those moving to non-quantum vulnerable address types, like what you now see as standard practice in Bitcoin wallets, you could kind of surmise that people are moving.

But also from a preparedness perspective, I think it's also important to point out that on the Bitcoin side, we have BIP360, which is paid at Merkle Root, which actually removes one of the quantum vulnerable spend paths on Taproot.

It's just like the non-technically engaged essentially means that there's this upgrade on Bitcoin called Taproot.

One of the ways to spend coins using a taproot address exposed to the public key.