Replies: 1 comment 2 replies
-
This is not a concern because the leaves of the merkle tree are 32-byte blocks of the replica itself. So the vanilla inclusion proofs actually contain the real (replicated) data, not only a hash of it. We did it that way specifically to prevent the issue you mention. I or someone else can point you to the best place to confirm this yourself in the code, but that's the short answer. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
Not sure if it's the right place to ask this question, please advise.
I'm new to FileCoin, though I read most of the docs.filecoin.io and proto.school/verifying-storage-on-filecoin, but I can't find how exactly the PoST works.
My main doubt is about the merkle inclusion proofs on which PoST is apparently based. If I understand it correctly, you don't need to have the actual data, just the hashes, in order to complete the proof. If this is true, what prevents the storage provider to pre-calculate in advance all the needed hashes and then just drop the data?
If this is something trivial, please advice where to find the details to understand it better.
Beta Was this translation helpful? Give feedback.
All reactions