In some cases, getMultiProof can't get right answer

[CryptoRbtree]

const leaves = ['a', 'b', 'c'].map(x => SHA256(x))
const tree = new MerkleTree(leaves, SHA256)
const root = tree.getRoot().toString('hex')

const proofIndices = [0, 2]
const proofLeaves = proofIndices.map(i => leaves[i])
const multiProof = tree.getMultiProof(proofIndices)
console.log(multiProof)
console.log(tree.verifyMultiProof(root, proofIndices, proofLeaves, leaves.length, multiProof))

[Fraccaman]

I'm having the same problem

[tsudmi]

There is a relevant discussion around that issue in OpenZeppelin/openzeppelin-contracts#3743

[frangio]

Working on this.

[frangio]

#68 will help but not fix this... The complete: true option introduced in that PR should be used for multiproofs. But it does not fix this snippet shared in this issue. We will be releasing a new merkle tree library that can properly generate all multiproofs.

Curious, is the use of SHA256 instead of Keccak256 significant?

[frangio]

We've released a new library that correctly generates multiproofs.

https://github.com/OpenZeppelin/merkle-tree