Currently the signed votes included require a merkle proof for voters verify the inclusion of their vote.
With use of SparseMerkleTree, the root starts with all accounts on a default value.
The use of SparseMerkleTree could replace the use of array of smaller merkle trees (which can contain repeated or conflicting vote signatures)
However the use of SparseMerkleTree could significantly increase the cost of vote inclusion, in other hand it can potentially cheaper the tabulation cost - because is necessary to preverify the signatures when they are included by the volunteer.
The use of SparseMerkleTree should be tested to see if the total net gas used by proposal is reduced or increased by this technique.
This is an implementation of SparseMerkleTree in solidity that we can use:
https://github.com/loomnetwork/plasma-cash/blob/master/server/contracts/Core/SparseMerkleTree.sol
Currently the signed votes included require a merkle proof for voters verify the inclusion of their vote.
With use of SparseMerkleTree, the root starts with all accounts on a default value.
The use of SparseMerkleTree could replace the use of array of smaller merkle trees (which can contain repeated or conflicting vote signatures)
However the use of SparseMerkleTree could significantly increase the cost of vote inclusion, in other hand it can potentially cheaper the tabulation cost - because is necessary to preverify the signatures when they are included by the volunteer.
The use of SparseMerkleTree should be tested to see if the total net gas used by proposal is reduced or increased by this technique.
This is an implementation of SparseMerkleTree in solidity that we can use:
https://github.com/loomnetwork/plasma-cash/blob/master/server/contracts/Core/SparseMerkleTree.sol