You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At 1000 entries in a claim chain the entire block is about 1MB in size. A proof of inclusion for a single email address is <2kB. So for a message with 10 recipients we increase the message size either by 20kB or by 1MB.
The choice seems obvious from that perspective. However if one only has proofs of inclusion for a new block one cannot verify that previous claims about others are included unchanged. So this also relates to the question of mitigating equivocation between blocks.
The text was updated successfully, but these errors were encountered:
For now we are looking at online claim chains. In this case downloading the entire chain should not be much of an issue. Once we notice we need to reduce bandwidth requirements or move to an in band scenario switching to proofs of inclusions might become an option again.
For now i close this issue.
At 1000 entries in a claim chain the entire block is about 1MB in size. A proof of inclusion for a single email address is <2kB. So for a message with 10 recipients we increase the message size either by 20kB or by 1MB.
The choice seems obvious from that perspective. However if one only has proofs of inclusion for a new block one cannot verify that previous claims about others are included unchanged. So this also relates to the question of mitigating equivocation between blocks.
The text was updated successfully, but these errors were encountered: