Replies: 13 comments 30 replies
-
Just an update on where I'm at. I'm still stuck. I've been testing with the 0N1 Force collection. It seems if you do a collection offer there are no filters (which makes this easy to test with), therefore I'm assuming a collection offer is just simply "collection-wide" and the merkle tree would consist of all token IDs when built. So, I built a merkle tree with token IDs 1 - 7777 (inclusive), and upon generating proofs for one of the IDs, it seems I can get 4 of them to match, and the other 9 do not match. The root hash also does not match. It's pretty cool that 4 do match, I think that means I'm on the right track, but not there yet. At this point, I think I've exhausted ideas that make sense, and I've just been guessing at what could possibly be different. Why would the tree for a "collection-wide" offer have something other than all tokens in the collection? Perhaps it excludes tokens that are "locked" on OS? |
Beta Was this translation helpful? Give feedback.
-
Hey @shea851, If we're not properly returning the proof that's on us. You shouldn't be expected to generate the proof yourself as we don't give you the list of valid identifiers either. This is something Opensea has to support returning from the REST endpoint. |
Beta Was this translation helpful? Give feedback.
-
Hi, how exactly do you generate merkle tree for a range? say 1-10000? I'm not generating the correct root |
Beta Was this translation helpful? Give feedback.
-
Is it not possible to let us know the range for generating the merkle tree? |
Beta Was this translation helpful? Give feedback.
-
Hey all, are there any updates on this matter? What I've noticed is sometimes the My question is actually what to do when the value is returned as '0'. When I like to fulfil a particular order which is an offer for a collection valid for any trait (hence the What to do in these cases? Is it required to supply a proof ourselves? How does that relate to the signature provided with the order? Can a consideration be extended not only for tipping, but also for modifying the proof? Many head scratching questions are floating... |
Beta Was this translation helpful? Give feedback.
-
No news about the implementation in the endpoint ? |
Beta Was this translation helpful? Give feedback.
-
Why not just provide the information on how to calculate the tree instead of providing an endpoint? |
Beta Was this translation helpful? Give feedback.
-
Anyone here was able to accept a collection based offer using this libary ? |
Beta Was this translation helpful? Give feedback.
-
anything update? |
Beta Was this translation helpful? Give feedback.
-
where is the support wtf |
Beta Was this translation helpful? Give feedback.
-
Same issue for me. After 7 months there is still no update. I can't believe this |
Beta Was this translation helpful? Give feedback.
-
Everything is in their github, you just have to set up the merkle using their criteria code, and everything will work (I did it) |
Beta Was this translation helpful? Give feedback.
-
Hi,
Recently, criteria based offers began to show up from the offers API.
It seems that in order to fulfill an offer, an identifier must be supplied (token ID I'm assuming), as well as merkle proofs that this is a valid leaf in the tree. It also seems we are given the tree root.
I don't believe I can build a tree with just the root. I think the root is given so we can validate that the tree we built is a match.
I am not sure how to obtain these merkle proofs. My guess is that I would need to build a tree. Can you please provide some guidance on this part? Or am I totally missing something and there is an endpoint/contract I can call to get the proofs?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions