Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If i publish a messages in calibnet, how do I retrieve it through lassie? #412

Closed
i-Lucifer opened this issue Sep 11, 2023 · 4 comments
Closed

Comments

@i-Lucifer
Copy link

Hello, I post a massage in calibnet through 'lotus-miner index announce bafyreiexy7a2hl7s6i2phlmaw6bt7gxxsoudih5evwtvvnwo4yvtfijh4u', however, I cannot retrieve it by using lassie tool or https://cid.contact. May I ask how to configure lassie to retrieve data published by calibnet?

@LexLuthr
Copy link

@i-Lucifer cid.contact does not listen to calibnet miner by default. It is configured for mainnet. Can you please explain your use case for publishing from calibnet to cid.contact? Are you testing the retrievals flows?

@i-Lucifer
Copy link
Author

i-Lucifer commented Sep 12, 2023

@LexLuthr I'm testing retrievals flows and I'm not sure I successfully published to cid.contact.
steps:
1、run ./bin/lotus-miner index announce bafyreiexy7a2hl7s6i2phlmaw6bt7gxxsoudih5evwtvvnwo4yvtfijh4u on calibnet
2、run lassie fetch -p bafyreiexy7a2hl7s6i2phlmaw6bt7gxxsoudih5evwtvvnwo4yvtfijh4u
If calibnet does not publish to cid.contact,How do I retrieve calibnet's piece-cid using lassie?

@LexLuthr
Copy link

@i-Lucifer The market components within Lotus are deprecated. You should not be testing with lotus-miner index as it is deprecated as well as not supported anymore. Please switch to Boost for market integration.

  1. cid.contact does not listen to calibnet gossipsub topic. Any announcements published there will not be picked up by cid.contact.
  2. To check retrievals, you have 2 options
    • Skip indexer check from Lassie and use --provider flag to directly fetch from your miner
    • If indexer is a must then
      • We update either cid.contact with your miner (requires Boost and HTTP announcements)
      • You can deploy your own indexer node listening just to your miner. We can update Lassie to use this indexer to resolve the CIDs.

Let me know which method suits your testing purposes and I can get you the step to configure the stack.

@i-Lucifer
Copy link
Author

@LexLuthr Thanks for your answer.
I will try using --provider and try deploying privatized lassie.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants