Merge remote-tracking branch 'origin/master' into testnet/3
This commit is contained in:
commit
be439d3b13
@ -109,7 +109,7 @@ func GetAPIInfo(ctx *cli.Context, t repo.RepoType) (APIInfo, error) {
|
|||||||
|
|
||||||
p, err := homedir.Expand(ctx.String(repoFlag))
|
p, err := homedir.Expand(ctx.String(repoFlag))
|
||||||
if err != nil {
|
if err != nil {
|
||||||
return APIInfo{}, xerrors.Errorf("cound not exand home dir (%s): %w", repoFlag, err)
|
return APIInfo{}, xerrors.Errorf("cound not expand home dir (%s): %w", repoFlag, err)
|
||||||
}
|
}
|
||||||
|
|
||||||
r, err := repo.NewFS(p)
|
r, err := repo.NewFS(p)
|
||||||
@ -119,7 +119,7 @@ func GetAPIInfo(ctx *cli.Context, t repo.RepoType) (APIInfo, error) {
|
|||||||
|
|
||||||
ma, err := r.APIEndpoint()
|
ma, err := r.APIEndpoint()
|
||||||
if err != nil {
|
if err != nil {
|
||||||
return APIInfo{}, xerrors.Errorf("could not get api enpoint: %w", err)
|
return APIInfo{}, xerrors.Errorf("could not get api endpoint: %w", err)
|
||||||
}
|
}
|
||||||
|
|
||||||
token, err := r.APIToken()
|
token, err := r.APIToken()
|
||||||
|
@ -101,6 +101,12 @@
|
|||||||
"slug": "en+storing-data-troubleshooting",
|
"slug": "en+storing-data-troubleshooting",
|
||||||
"github": "en/storing-data-troubleshooting.md",
|
"github": "en/storing-data-troubleshooting.md",
|
||||||
"value": null
|
"value": null
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"title": "Information for Miners",
|
||||||
|
"slug": "en+info-for-miners",
|
||||||
|
"github": "en/miner-deals.md",
|
||||||
|
"value": null
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
},
|
},
|
||||||
|
@ -117,6 +117,11 @@ Note that these might NOT be the minimum requirements for mining on Mainnet.
|
|||||||
|
|
||||||
A list of benchmarked GPUs can be found [here](https://lotu.sh/en+hardware-mining#benchmarked-gpus-7393).
|
A list of benchmarked GPUs can be found [here](https://lotu.sh/en+hardware-mining#benchmarked-gpus-7393).
|
||||||
|
|
||||||
|
### Why is my GPU not being used when sealing a sector?
|
||||||
|
|
||||||
|
Sealing a sector does not involve constant GPU operations. It's possible
|
||||||
|
that your GPU simply isn't necessary at the moment you checked.
|
||||||
|
|
||||||
## Advanced questions
|
## Advanced questions
|
||||||
|
|
||||||
### Is there a Docker image for lotus?
|
### Is there a Docker image for lotus?
|
||||||
|
41
documentation/en/miner-deals.md
Normal file
41
documentation/en/miner-deals.md
Normal file
@ -0,0 +1,41 @@
|
|||||||
|
# Information for Miners
|
||||||
|
|
||||||
|
Here is how a miner can get set up to accept storage deals. The first step is
|
||||||
|
to install a Lotus node and sync to the top of the chain.
|
||||||
|
|
||||||
|
## Set up an ask
|
||||||
|
|
||||||
|
```
|
||||||
|
lotus-storage-miner set-price <price>
|
||||||
|
```
|
||||||
|
|
||||||
|
This command will set up your miner to accept deal proposals that meet the input price.
|
||||||
|
The price is inputted in FIL per GiB per epoch, and the default is 0.0000000005.
|
||||||
|
|
||||||
|
<!-- TODO: Add info about setting min piece size, max piece size, duration -->
|
||||||
|
|
||||||
|
## Ensure you can be discovered
|
||||||
|
|
||||||
|
Clients need to be able to find you in order to make storage deals with you.
|
||||||
|
While there isn't necessarily anything you need to do to become discoverable, here are some things you can
|
||||||
|
try to check that people can connect to you.
|
||||||
|
|
||||||
|
To start off, make sure you are connected to at least some peers, and your port is
|
||||||
|
open and working.
|
||||||
|
|
||||||
|
### Connect to your own node
|
||||||
|
|
||||||
|
If you are in contact with someone else running Lotus, you can ask them to try connecting
|
||||||
|
to your node. To do so, provide them your peer ID, which you can get by running `lotus net id` on
|
||||||
|
your node.
|
||||||
|
|
||||||
|
They can then try running `lotus net findpeer <peerID>` to get your address(es), and can then
|
||||||
|
run `lotus net connect <address>` to connect to you. If successful, your node will now
|
||||||
|
appear on their peers list (run `lotus net peers` to check).
|
||||||
|
|
||||||
|
You can also check this by running a second instance of Lotus yourself.
|
||||||
|
|
||||||
|
### Query your own ask
|
||||||
|
|
||||||
|
A client should be able to find your ask by running `lotus client query-ask <minerID>`. If
|
||||||
|
someone is not able to retrieve your ask by doing so, then there is an issue with your node.
|
@ -65,7 +65,8 @@ func (s *RPCServer) handleWS(ctx context.Context, w http.ResponseWriter, r *http
|
|||||||
func (s *RPCServer) ServeHTTP(w http.ResponseWriter, r *http.Request) {
|
func (s *RPCServer) ServeHTTP(w http.ResponseWriter, r *http.Request) {
|
||||||
ctx := r.Context()
|
ctx := r.Context()
|
||||||
|
|
||||||
if strings.Contains(r.Header.Get("Connection"), "Upgrade") {
|
h := strings.ToLower(r.Header.Get("Connection"))
|
||||||
|
if strings.Contains(h, "upgrade") {
|
||||||
s.handleWS(ctx, w, r)
|
s.handleWS(ctx, w, r)
|
||||||
return
|
return
|
||||||
}
|
}
|
||||||
|
Loading…
Reference in New Issue
Block a user