doc: add an umbrella page for CS Filecoin services #5182
Conversation
LesnyRumcajs
force-pushed
the
umbrella-page-fil-services
branch
from
56b2a82 to
3734195
Compare
LesnyRumcajs
force-pushed
the
umbrella-page-fil-services
branch
from
3734195 to
82cb613
Compare
| - [calibnet](https://github.com/ChainSafe/forest/blob/main/build/bootstrap/calibnet) | ||
| - [mainnet](https://github.com/ChainSafe/forest/blob/main/build/bootstrap/mainnet) |
There was a problem hiding this comment.
| - [calibnet](https://github.com/ChainSafe/forest/blob/main/build/bootstrap/calibnet) | |
| - [mainnet](https://github.com/ChainSafe/forest/blob/main/build/bootstrap/mainnet) | |
| #### Mainnet | |
| - `/dns/bootstrap-mainnet-0.chainsafe-fil.io/tcp/34000/p2p/12D3KooWKKkCZbcigsWTEu1cgNetNbZJqeNtysRtFpq7DTqw3eqH` | |
| - `/dns/bootstrap-mainnet-1.chainsafe-fil.io/tcp/34000/p2p/12D3KooWGnkd9GQKo3apkShQDaq1d6cKJJmsVe6KiQkacUk1T8oZ` | |
| - `/dns/bootstrap-mainnet-2.chainsafe-fil.io/tcp/34000/p2p/12D3KooWHQRSDFv4FvAjtU32shQ7znz7oRbLBryXzZ9NMK2feyyH` | |
| #### Calibnet | |
| - `/dns/bootstrap-calibnet-0.chainsafe-fil.io/tcp/34000/p2p/12D3KooWABQ5gTDHPWyvhJM7jPhtNwNJruzTEo32Lo4gcS5ABAMm` | |
| - `/dns/bootstrap-calibnet-1.chainsafe-fil.io/tcp/34000/p2p/12D3KooWS3ZRhMYL67b4bD5XQ6fcpTyVQXnDe8H89LvwrDqaSbiT` | |
| - `/dns/bootstrap-calibnet-2.chainsafe-fil.io/tcp/34000/p2p/12D3KooWEiBN8jBX8EBoM3M47pVRLRWV812gDRUJhMxgyVkUoR48` | |
| - `/dns/bootstrap-archive-calibnet-0.chainsafe-fil.io/tcp/1347/p2p/12D3KooWLcRpEfmUq1fC8vfcLnKc1s161C92rUewEze3ALqCd9yJ` |
There was a problem hiding this comment.
I would avoid embedding copying those entries, as they might change over time and Forest docs should not be a source of truth - the code should.
| ### Bootstrap nodes | ||
|
|
||
| Bootstrap nodes are essential for new peers joining the network. They provide a list of known peers to connect to, allowing the new peer to join the network quickly. ChainSafe provides several bootstrap nodes (both Forest and Lotus-based) for the Filecoin network (the `chainsafe.io` domain): | ||
|
|
There was a problem hiding this comment.
| ChainSafe also operates an **archival bootstrap node** which maintains a full set of historical state to serve to the network. |
We should mention this somewhere/how. This suggestion can probably be expanded/improved.
There was a problem hiding this comment.
@joshdougall Can you provide some details around it?
|
|
||
| ### Storage | ||
|
|
||
| The S3-compatible IPFS/Filecoin gateway is available at [storage.chainsafe.io](https://storage.chainsafe.io). |
There was a problem hiding this comment.
@joshdougall Would be good to include some direction for where to go for support (eg. Fil slack channels)
docs/docs/users/filecoin_services.md
Outdated
|
|
||
| ChainSafe works on various projects in the Filecoin ecosystem. While the Forest team focuses on improving the Forest client and collaborating with other Filecoin implementations to drive the network forward, ChainSafe's Infrastructure team provides a number of services to the Filecoin community. | ||
|
|
||
| ## 🌲Forest |
There was a problem hiding this comment.
I'm not sure it makes sense for Forest to be at the top of this, nor to separate services into forest vs infra. The purpose of this page is to promote the services we operate, shilling Forest should be secondary. Also the distinction of what each team operates is probably not relevant to users (unless they have issues...)
I would suggest mentioning Forest in a callout (ie. admonition, :::info....), collapsing this into a single list, and moving the status page to a callout as well.
There was a problem hiding this comment.
Also the distinction of what each team operates is probably not relevant to users (unless they have issues...)
That's the exact reason for this distinction, given folks were quite often reaching out to Forest team, and the only thing we could do is to forward it to the infra team. It's not a huge hassle, though.
I can de-prioritize Forest in this page.
docs/docs/users/filecoin_services.md
Outdated
| <img src="/img/filecoin_logo.png" alt="Filecoin logo"/> | ||
| </p> | ||
|
|
||
| ChainSafe works on various projects in the Filecoin ecosystem. While the Forest team focuses on improving the Forest client and collaborating with other Filecoin implementations to drive the network forward, ChainSafe's Infrastructure team provides a number of services to the Filecoin community. |
There was a problem hiding this comment.
| ChainSafe works on various projects in the Filecoin ecosystem. While the Forest team focuses on improving the Forest client and collaborating with other Filecoin implementations to drive the network forward, ChainSafe's Infrastructure team provides a number of services to the Filecoin community. | |
| ChainSafe works on various projects in the Filecoin ecosystem. While the Forest team focuses on improving the Forest client and collaborating with other Filecoin implementations to drive the network forward, ChainSafe's Infrastructure team provides a number of services to support the Filecoin community, dogfooding Forest at every possible opportunity. |
Co-authored-by: David Ansermino <[email protected]>
|
@ansermino Changed it a bit to address some of your comments (mainly regarding the page being Forest-centric). |
Summary of changes
Changes introduced in this pull request:
filecoin.chainsafe.ioReference issue to close (if applicable)
Closes
Other information and links
Change checklist