You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: nodes/full-nodes/basic-setup.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,13 @@ To install Lotus on your computer, follow these steps:
12
12
2. Once you have downloaded the binary file, extract the contents to a directory of your choice. For example, if you are using Linux, you can extract the contents to the `/usr/local/bin directory` by running the command:
13
13
14
14
```sh
15
-
sudo tar -C /usr/local/bin -xzf lotus-1.33.0-linux-amd64.tar.gz
15
+
sudo tar -C /usr/local/bin -xzf lotus-1.33.1-linux-amd64.tar.gz
16
16
```
17
17
18
18
3. After extracting the contents, navigate to the `lotus` directory in your terminal. For example, if you extracted the contents to `/usr/local/bin`, you can navigate to the lotus directory by running the command:
19
19
20
20
```sh
21
-
cd /usr/local/bin/lotus-1.33.0
21
+
cd /usr/local/bin/lotus-1.33.1
22
22
```
23
23
24
24
4. Run the `lotus` binary file to start the Lotus daemon. You can do this by running the command:
Copy file name to clipboardExpand all lines: nodes/lite-nodes/spin-up-a-lite-node.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,12 +73,12 @@ Before we can build the Lotus binaries, we need to follow a few pre-build steps.
73
73
This should output something like:
74
74
75
75
```output
76
-
v1.33.0
76
+
v1.33.1
77
77
```
78
78
3. Using the value returned from the previous command, checkout to the latest release branch:
79
79
80
80
```shell
81
-
git checkout v1.33.0
81
+
git checkout v1.33.1
82
82
```
83
83
4. Done! You can move on to the [Build](https://docs.filecoin.io/nodes/lite-nodes/spin-up-a-lite-node/#build-the-binary) section.
84
84
{% endtab %}
@@ -99,12 +99,12 @@ Before we can build the Lotus binaries, we need to follow a few pre-build steps.
99
99
This should output something like:
100
100
101
101
```output
102
-
v1.33.0
102
+
v1.33.1
103
103
```
104
104
3. Using the value returned from the previous command, checkout to the latest release branch:
105
105
106
106
```shell
107
-
git checkout v1.33.0
107
+
git checkout v1.33.1
108
108
```
109
109
4. Create the necessary environment variables to allow Lotus to run on M1 architecture:
110
110
@@ -132,12 +132,12 @@ Before we can build the Lotus binaries, we need to follow a few pre-build steps.
132
132
This should output something like:
133
133
134
134
```output
135
-
v1.33.0
135
+
v1.33.1
136
136
```
137
137
3. Using the value returned from the previous command, checkout to the latest release branch:
138
138
139
139
```shell
140
-
git checkout v1.33.0
140
+
git checkout v1.33.1
141
141
```
142
142
4. If your processor was released later than an AMD Zen or Intel Ice Lake CPU, enable SHA extensions by adding these two environment variables. If in doubt, ignore this command and move on to [the next section](https://docs.filecoin.io/nodes/lite-nodes/spin-up-a-lite-node/#build-the-binary).
143
143
@@ -175,7 +175,7 @@ The last thing we need to do to get our node setup is to build the package. The
175
175
This will output something like:
176
176
177
177
```plaintext
178
-
lotus version 1.33.0+mainnet+git.1ff3b360b
178
+
lotus version 1.33.1+mainnet+git.1ff3b360b
179
179
```
180
180
{% endtab %}
181
181
@@ -200,7 +200,7 @@ The last thing we need to do to get our node setup is to build the package. The
Copy file name to clipboardExpand all lines: reference/general/README.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,17 +81,17 @@ Developer tools, API clients & storage services that developers can use to build
81
81
*[Fleek’s tools](https://fleek.xyz/) - provides access to Fleek’s hosted services using IPFS, Filecoin, Ethereum, etc.
82
82
*[Akave](https://www.akave.ai/) is "revolutionizing data management with a decentralized, modular solution that combines the robust storage of Filecoin with cutting-edge encryption and easy-to-use interfaces."
83
83
84
+
### JavaScript tools
84
85
85
-
### Message signing tools
86
+
*[iso-filecoin](https://github.com/hugomrdias/filecoin/tree/main/packages/iso-filecoin) - Filecoin Javascript Standard Library. Used by the [Metamask Filecoin Wallet](https://github.com/filecoin-project/filsnap) and [Ledger Live Filecoin app](https://www.ledger.com/coin/wallet/filecoin).
87
+
*[iso-filecoin-react](https://github.com/hugomrdias/filecoin/tree/main/packages/iso-filecoin-react) - React hooks and context to easily integrate Filecoin wallet interactions into your React applications. It works seamlessly with the wallet adapters from iso-filecoin-wallets.
86
88
87
-
*[Filecoin Signing Tools](../built-in-actors/) - _**Recommended**_ a pure JS or Rust / WASM / JSONRPC library for creating signed messages apart from a Filecoin node.
88
-
* For an open source example of how to use it see the [Glif web wallet](https://github.com/glifio/wallet) on GitHub.
89
-
*[Filecoin JS Signer](https://github.com/blitslabs/filecoin-js-signer) - \[_last update: June 2021_] pure TS / JS library for creating signed messages and interacting with Filecoin’s built-in Actors (like Payment Channel and Multisig), used by the [Filecoin Loans grant project](https://github.com/blitslabs/filecoin.loans-monorepo).
90
-
* On npm at [`@blitslabs/filecoin-js-signer`](https://www.npmjs.com/package/@blitslabs/filecoin-js-signer)
89
+
Check out the [documentation website](https://filecoin.hugomrdias.dev/) for more information.
91
90
92
91
### Wallet-related tools
93
92
94
-
*[FilSnap MetaMask Plugin](https://metamask.io/flask/) - MetaMask has a new plugin system currently still in beta that developers can try out. The MM UI will not change but Filecoin keys are in the MM vault.
93
+
*[Metamask Filecoin Wallet](https://github.com/filecoin-project/filsnap) - A MetaMask [Snap](https://snaps.metamask.io/snap/npm/filsnap/) to add Filecoin support to the MetaMask extension. Check out [filsnap.dev](https://filsnap.dev/) built with the [iso-filecoin](https://github.com/hugomrdias/filecoin/tree/main/packages/iso-filecoin) and [filsnap](https://github.com/filecoin-project/filsnap) libraries.
94
+
*[iso-filecoin-wallets](https://github.com/hugomrdias/filecoin/tree/main/packages/iso-filecoin-wallets) - Filecoin wallet adapters to interact with different types of Filecoin wallets through a common interface. Supports Ledger, MetaMask Filecoin Wallet, and more.
95
95
96
96
### Node Infrastructure & APIs
97
97
@@ -110,9 +110,7 @@ For running a node cluster of load balanced Lotus JSON RPC API endpoints.
110
110
111
111
**Filecoin API clients**
112
112
113
-
*[`Filecoin.js`](https://github.com/filecoin-shipyard/filecoin.js) (outdated) - higher-level JS library for interacting with Lotus via JSON-RPC API.
114
-
*[`js-lotus-client`](https://github.com/filecoin-shipyard/js-lotus-client) - lower-level JS wrapper for basic parsing of the Lotus JSON RPC API.
115
-
*[`lotus-json-rpc-provider`](https://www.npmjs.com/package/@coinsummer/lotus-jsonrpc-provider) (outdated) - wraps the Lotus API in TypeScript.
113
+
*[iso-filecoin](https://github.com/hugomrdias/filecoin/tree/main/packages/iso-filecoin) - Filecoin Javascript Standard Library includes an API client for the Lotus JSON-RPC API.
Copy file name to clipboardExpand all lines: reference/general/tools.md
+41-6Lines changed: 41 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,15 +10,50 @@ description: >-
10
10
11
11
These infrastructure libraries and tools exist to speed up the development of software on top of the Filecoin network.
12
12
13
-
#### Filecoin signing tools
13
+
#### Filecoin Javascript Standard Library
14
14
15
-
The [Filecoin signing tools](./) provide basic functionality for signing Filecoin transactions in pure JavaScript, WASM and Rust. Currently, the Rust and WASM implementations support:
15
+
> Connect apps to the Filecoin blockchain with iso-filecoin.
16
16
17
-
* Secp256k1
18
-
* BLS
19
-
* CBOR-JSON serialization of transactions
17
+
##### Features
20
18
21
-
Support for multisignature transaction signing is currently in progress, and the pure JavaScript implementation is less complete than the Rust and WASM implementations.
19
+
- Lightweight, performant and type-safe
20
+
- Support for RPC, Signature, Address, Token, Chain, Wallet and more.
21
+
- React hooks and context to easily integrate Filecoin wallets
22
+
- Wallet adapters for Ledger Filecoin App, MetaMask Filecoin Wallet, and more.
-[filsnap](https://github.com/filecoin-project/filsnap/tree/master/packages/snap) - Filecoin snap for Metamask
55
+
-[filsnap-adapter](https://github.com/filecoin-project/filsnap/tree/master/packages/adapter) - Adapter to interact with Filsnap from a dapp
56
+
-[filsnap-adapter-react](https://github.com/filecoin-project/filsnap/tree/master/packages/adapter-react) - React hooks to interact with Filsnap from a dapp
Copy file name to clipboardExpand all lines: storage-providers/skills/linux.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ sudo sysctl -p
57
57
58
58
Diagnosing performance bottlenecks on a system is vital to keeping a well balanced [sealing pipeline](../architecture/sealing-pipeline.md).
59
59
60
-
There are many good resources to check out when it comes to Linux performance troubleshooting. Brendan Gregg’s [Linux performance analysis in 60 seconds](https://netflixtechblog.com/linux-performance-analysis-in-60-000-milliseconds-accc10403c55) is an excellent introduction. Each one of these commands deserves a chapter on its own but can be further researched in their man pages.
60
+
There are many good resources to check out when it comes to Linux performance troubleshooting. Brendan Gregg’s [Linux performance analysis in 60 seconds](https://www.brendangregg.com/blog/2015-12-03/linux-perf-60s-video.html) is an excellent introduction. Each one of these commands deserves a chapter on its own but can be further researched in their man pages.
0 commit comments