-
Notifications
You must be signed in to change notification settings - Fork 297
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
Update getting datacap instructions #2250
Comments
@dannyob can you suggest someone who might be well placed to update this? |
@galen-mcandrew @willscott would be my first port of call! |
We need to update these, so we can link to them from the various tutorials also. We need a working process for new devs to get datacap, even if it's the old one, some intermediate hack, anything. |
Flagging the homepage of this site (https://filplus.storage/) inaccurately suggests SP's will "get significantly more reward from the network for successful storage," when it should read "SP's who accept Filecoin+ deals will have a higher probability of being selected as the verifier and earning block rewards than their peers who only accept regular deals." Along with other issues found in Filecoin+ documentation, adding to the docs scratchpad. |
"First bad draft" found here: https://docs.google.com/document/d/1Tinyz3MGG0bFhbhjsk7137resxDgyXNDHHZ0xX7D74o/edit |
This work will also need to address the instructions in the lotus tutorial https://lotus.filecoin.io/tutorials/lotus/store-and-retrieve/store-data/ |
This may be waiting on a clearer pathway in the new world of allocators, but I believe the instructions at https://docs.filecoin.io/basics/how-storage-works/filecoin-plus are currently inaccurate. (At the very least, I don't think https://filplus.fil.org/#/ gives a list of entities -- at least it has no SPs and no obvious way to find allocators), and I believe the filplus.storage path doesn't currently work, as it awaits a rewrite.
The text was updated successfully, but these errors were encountered: