Merge branch 'main' into contracts-docs-sync

lukso-network · Nov 1, 2023 · 88a3b2e · 88a3b2e
2 parents 847cc8d + 0f0cb6e
commit 88a3b2e
Show file tree

Hide file tree

Showing 9 changed files with 44 additions and 26 deletions.
diff --git a/docs/networks/advanced-guides/switch-consensus-clients.md b/docs/networks/advanced-guides/switch-consensus-clients.md
@@ -157,9 +157,9 @@ If you are setting up a node for the testnet, add the `--testnet` flag to the st
 
 :::
 
-:::note
+:::info
 
-You will need the LUKSO CLI Version 0.8.0 or above in order to use the `--checkpoint-sync` command. If you are using an older version, please pass down the checkpoint flag as described in the [LUKSO CLI Documentation](https://github.com/lukso-network/tools-lukso-cli/tree/main#using-checkpoint-syncing).
+You will need the LUKSO CLI Version 0.8.0 or above in order to use the `--checkpoint-sync` command. If you are using an older version or run into issues, please pass down the checkpoint flag manually, as described in the [LUKSO CLI Checkpoint Documentation](https://github.com/lukso-network/tools-lukso-cli/tree/main#using-checkpoint-syncing).
 
 :::
 

diff --git a/docs/networks/advanced-guides/update-clients.md b/docs/networks/advanced-guides/update-clients.md
@@ -91,6 +91,12 @@ If you are setting up a node for the testnet, add the `--testnet` flag to the st
 
 :::
 
+:::info
+
+You will need the LUKSO CLI Version 0.8.0 or above in order to use the `--checkpoint-sync` command. If you are using an older version or run into issues, please pass down the checkpoint flag manually, as described in the [LUKSO CLI Checkpoint Documentation](https://github.com/lukso-network/tools-lukso-cli/tree/main#using-checkpoint-syncing).
+
+:::
+
 ```sh
 # Starting the Mainnet Node
 lukso start --checkpoint-sync

diff --git a/docs/networks/advanced-guides/update-the-node.md b/docs/networks/advanced-guides/update-the-node.md
@@ -299,6 +299,12 @@ If you are setting up a node for the testnet, add the `--testnet` flag to the st
 
 :::
 
+:::info
+
+You will need the LUKSO CLI Version 0.8.0 or above in order to use the `--checkpoint-sync` command. If you are using an older version or run into issues, please pass down the checkpoint flag manually, as described in the [LUKSO CLI Checkpoint Documentation](https://github.com/lukso-network/tools-lukso-cli/tree/main#using-checkpoint-syncing).
+
+:::
+
 ```sh
 # Starting the Mainnet Node
 lukso start --checkpoint-sync

diff --git a/docs/networks/advanced-guides/withdrawal-update.md b/docs/networks/advanced-guides/withdrawal-update.md
@@ -246,7 +246,7 @@ A maximum of 16 validator keys can update their withdrawal credentials per block
 :::
 
 1. Open the Validator Withdrawal Page of the related network:
-   - [LUKSO Mainnet Validator Withdrawals](https://explorer.consensus.mainnet.lukso.network/tools/broadcast)
-   - [LUKSO Testnet Validator Withdrawals](https://explorer.consensus.testnet.lukso.network/tools/broadcast)
+   - [LUKSO Mainnet Validator Withdrawals](https://explorer.consensus.mainnet.lukso.network/validators/withdrawals)
+   - [LUKSO Testnet Validator Withdrawals](https://explorer.consensus.testnet.lukso.network/validators/withdrawals)
 2. Scroll down to the list of **Address Changes**.
 3. Your Validator indices should show up as some of the latest entries.
diff --git a/docs/networks/mainnet/become-a-validator.md b/docs/networks/mainnet/become-a-validator.md
@@ -107,9 +107,9 @@ If you are setting up a node for the testnet, add the `--testnet` flag to the st
 
 :::
 
-:::note
+:::info
 
-You will need the LUKSO CLI Version 0.8.0 or above in order to use the `--checkpoint-sync` command. If you are using an older version, please pass down the checkpoint flag as described in the [LUKSO CLI Documentation](https://github.com/lukso-network/tools-lukso-cli/tree/main#using-checkpoint-syncing).
+You will need the LUKSO CLI Version 0.8.0 or above in order to use the `--checkpoint-sync` command. If you are using an older version or run into issues, please pass down the checkpoint flag manually, as described in the [LUKSO CLI Checkpoint Documentation](https://github.com/lukso-network/tools-lukso-cli/tree/main#using-checkpoint-syncing).
 
 :::
 

diff --git a/docs/networks/mainnet/running-a-node.md b/docs/networks/mainnet/running-a-node.md
@@ -105,19 +105,6 @@ If you want more convenience and your validator to operate quickly, you can also
 > After the synchronization is finalized, you will end up with the equal blockchain data. You can use the flag on every startup. However, it shows the most significant effect when synchronizing from scratch or after an extended downtime. The shortcut is ideal for fresh installations, validator migration, or recovery.
 
 <Tabs>
-  <TabItem value="regular-sync" label="Regular Synchronization">
-
-:::info
-
-The synchronization process will take multiple hours for the node to finalize.
-
-:::
-
-```sh
-lukso start
-```
-
-  </TabItem>  
   <TabItem value="checkpoint-sync" label="Checkpoint Synchronization">
 
 :::tip
@@ -126,9 +113,9 @@ The shortcut is ideal for making installation, validator migration, or recovery
 
 :::
 
-:::note
+:::info
 
-You will need the LUKSO CLI Version 0.8.0 or above in order to use the `--checkpoint-sync` command. If you are using an older version, please pass down the checkpoint flag as described in the [LUKSO CLI Documentation](https://github.com/lukso-network/tools-lukso-cli/tree/main#using-checkpoint-syncing).
+You will need the LUKSO CLI Version 0.8.0 or above in order to use the `--checkpoint-sync` command. If you are using an older version or run into issues, please pass down the checkpoint flag manually, as described in the [LUKSO CLI Checkpoint Documentation](https://github.com/lukso-network/tools-lukso-cli/tree/main#using-checkpoint-syncing).
 
 :::
 
@@ -137,6 +124,19 @@ lukso start --checkpoint-sync
 ```
 
   </TabItem>
+  <TabItem value="regular-sync" label="Regular Synchronization">
+
+:::info
+
+The synchronization process will take multiple hours for the node to finalize.
+
+:::
+
+```sh
+lukso start
+```
+
+  </TabItem>  
 </Tabs>
 
 :::info

diff --git a/docs/tools/erc725js/classes/ERC725.md b/docs/tools/erc725js/classes/ERC725.md
@@ -187,8 +187,7 @@ myErc725.decodeData([
     value: [
       {
         key: '0x7c8c3416d6cda87cd42c71ea1843df28ac4850354f988d55ee2eaa47b6dc05cd',
-        value:
-          '0x0000000000000000000000000000000000000000000000000000000000000002',
+        value: '0x00000000000000000000000000000002',
       },
       {
         key: '0x7c8c3416d6cda87cd42c71ea1843df2800000000000000000000000000000000',
@@ -593,7 +592,7 @@ myErc725.encodeData([
   ],
   values: [
     '0x6f357c6a820464ddfac1bec070cc14a8daf04129871d458f2ca94368aae8391311af6361696670733a2f2f516d597231564a4c776572673670456f73636468564775676f3339706136727963455a4c6a7452504466573834554178',
-    '0x0000000000000000000000000000000000000000000000000000000000000002',
+    '0x00000000000000000000000000000002',
     '0xd94353d9b005b3c0a9da169b768a31c57844e490',
     '0xdaea594e385fc724449e3118b2db7e86dfba1826',
     '0x1183790f29be3cdfd0a102862fea1a4a30b3adab',
@@ -704,6 +703,7 @@ ERC725.decodeMappingKey(
   '0x35e6950bc8d21a1699e50000cafecafecafecafecafecafecafecafecafecafe',
   'MyKeyName:<address>',
 );
+// Decoding will checksum addresses
 // [{
 //   type: 'address',
 //   value: '0xCAfEcAfeCAfECaFeCaFecaFecaFECafECafeCaFe'
@@ -806,6 +806,7 @@ ERC725.encodePermissions({
   ENCRYPT: false,
   DECRYPT: false,
   SIGN: false,
+  EXECUTE_RELAY_CALL: false
 }),
 // '0x0000000000000000000000000000000000000000000000000000000000000110'
 

diff --git a/docs/tools/erc725js/providers.md b/docs/tools/erc725js/providers.md
@@ -30,9 +30,9 @@ const ethereumProvider = window.ethereum;
 const erc725 = new ERC725([], '0x...', ethereumProvider);
 ```
 
-## Web3
+## Web3 (deprecated)
 
-The following code snippet will use the web3 provider available at web3.providers from the corresponding `web3` library.
+The following code snippet will use the web3 provider available at `web3.providers` from the corresponding `web3` library.
 
 :::caution Warning
 

diff --git a/docs/tools/erc725js/schemas.md b/docs/tools/erc725js/schemas.md
@@ -31,9 +31,11 @@ LSP4DigitalAssetLegacy.json
 LSP4DigitalAsset.json
 LSP5ReceivedAssets.json
 LSP6KeyManager.json
+LSP8IdentifiableDigitalAsset.json
 LSP9Vault.json
 LSP10ReceivedVaults.json
 LSP12IssuedAssets.json
+LSP17ContractExtension.json
 ```
 
 You can import them from:
@@ -45,4 +47,7 @@ import LSP5 from '@erc725/erc725.js/schemas/LSP5ReceivedAssets.json';
 
 // Later use them on instantiation
 const myErc725Contract = new ERC725js(LSP3, address, web3.currentProvider);
+
+// You can retrieve the current loaded schema via
+myErc725Contract.options.schemas;
 ```
-Original file line number
+Diff line change
@@ Expand Up @@
     :::
-    :::note
+    :::info
-    You will need the LUKSO CLI Version 0.8.0 or above in order to use the `--checkpoint-sync` command. If you are using an older version, please pass down the checkpoint flag as described in the [LUKSO CLI Documentation](https://github.com/lukso-network/tools-lukso-cli/tree/main#using-checkpoint-syncing).
+    You will need the LUKSO CLI Version 0.8.0 or above in order to use the `--checkpoint-sync` command. If you are using an older version or run into issues, please pass down the checkpoint flag manually, as described in the [LUKSO CLI Checkpoint Documentation](https://github.com/lukso-network/tools-lukso-cli/tree/main#using-checkpoint-syncing).
     :::
@@ Expand Down @@