From a57c4250170a7f3de4dfa9c3c09d73a13499d1c9 Mon Sep 17 00:00:00 2001 From: Yash Jagtap Date: Wed, 8 Jan 2025 22:59:25 +0530 Subject: [PATCH] chore: typos after spellchecker --- .../smart-contracts/contracts/ERC725.md | 2 +- docs/contracts/contracts/ERC725/ERC725.md | 2 +- .../LSP0ERC725Account/LSP0ERC725Account.md | 2 +- .../LSP1UniversalReceiverDelegateUP.md | 2 +- .../LSP1UniversalReceiverDelegateUP.md | 2 +- .../LSP6KeyManager/LSP6KeyManager.md | 4 ++-- .../extensions/LSP7CappedSupply.md | 2 +- .../extensions/LSP8CappedSupply.md | 2 +- .../contracts/LSP9Vault/LSP9Vault.md | 2 +- docs/contracts/contracts/UniversalProfile.md | 2 +- .../UniversalProfile/UniversalProfile.md | 2 +- .../NFT/customise-transfer-behaviour.md | 2 +- docs/faq/lukso/feature-requests.md | 2 +- docs/faq/network/blockchain-architecture.md | 4 ++-- docs/faq/network/staking.md | 2 +- docs/faq/network/validators.md | 2 +- docs/faq/onboarding/lukso-standards.md | 2 +- docs/learn/concepts.md | 2 +- .../metadata-management/read-asset-data.md | 4 ++-- .../nft/create-nft-collection-lsp8.md | 2 +- ...create-nft-collection-with-lsp7-tokenId.md | 6 ++--- .../digital-assets/token/create-lsp7-token.md | 2 +- docs/learn/migrate/migrate-erc20-to-lsp7.md | 6 ++--- .../other-guides/utilize-ipfs-storage.md | 2 +- .../advanced-guides/upgrade-key-manager.md | 2 +- .../accept-reject-assets.md | 4 ++-- docs/learn/vault/interact-with-contracts.md | 2 +- .../access-control/lsp14-ownable-2-step.md | 4 ++-- .../access-control/lsp6-key-manager.md | 4 ++-- .../accounts/lsp1-universal-receiver.md | 2 +- .../accounts/lsp15-transaction-relayer-api.md | 2 +- .../metadata/lsp3-profile-metadata.md | 6 ++--- .../tokens/LSP8-Identifiable-Digital-Asset.md | 2 +- docs/tools/dapps/erc725js/getting-started.md | 4 ++-- docs/tools/dapps/erc725js/methods.md | 22 +++++++++---------- .../lsp-utils/LSP4DigitalAssetMetadata.md | 2 +- docs/tools/dapps/lsp-utils/LSP6KeyManager.md | 2 +- docs/tools/integrations.md | 2 +- 38 files changed, 61 insertions(+), 61 deletions(-) diff --git a/docs/contracts/contracts/@erc725/smart-contracts/contracts/ERC725.md b/docs/contracts/contracts/@erc725/smart-contracts/contracts/ERC725.md index 442380f1f6..3d031dff89 100644 --- a/docs/contracts/contracts/@erc725/smart-contracts/contracts/ERC725.md +++ b/docs/contracts/contracts/@erc725/smart-contracts/contracts/ERC725.md @@ -802,7 +802,7 @@ Emitted when calling an address `target` (EOA or contract) with `value`. | Name | Type | Description | | ----------------------------- | :-------: | ---------------------------------------------------------------------------------------------------- | -| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICALL` or `DELEGATECALL`). | +| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICCALL` or `DELEGATECALL`). | | `target` **`indexed`** | `address` | The address to call. `target` will be unused if a contract is created (operation types 1 and 2). | | `value` | `uint256` | The amount of native tokens transferred along the call (in Wei). | | `selector` **`indexed`** | `bytes4` | The first 4 bytes (= function selector) of the data sent with the call. | diff --git a/docs/contracts/contracts/ERC725/ERC725.md b/docs/contracts/contracts/ERC725/ERC725.md index d0e76e30bf..13ec0f1602 100644 --- a/docs/contracts/contracts/ERC725/ERC725.md +++ b/docs/contracts/contracts/ERC725/ERC725.md @@ -792,7 +792,7 @@ Emitted when calling an address `target` (EOA or contract) with `value`. | Name | Type | Description | | ----------------------------- | :-------: | ---------------------------------------------------------------------------------------------------- | -| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICALL` or `DELEGATECALL`). | +| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICCALL` or `DELEGATECALL`). | | `target` **`indexed`** | `address` | The address to call. `target` will be unused if a contract is created (operation types 1 and 2). | | `value` | `uint256` | The amount of native tokens transferred along the call (in Wei). | | `selector` **`indexed`** | `bytes4` | The first 4 bytes (= function selector) of the data sent with the call. | diff --git a/docs/contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md b/docs/contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md index 4388617865..d5c28325fc 100644 --- a/docs/contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md +++ b/docs/contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md @@ -1370,7 +1370,7 @@ Emitted when calling an address `target` (EOA or contract) with `value`. | Name | Type | Description | | ----------------------------- | :-------: | ---------------------------------------------------------------------------------------------------- | -| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICALL` or `DELEGATECALL`). | +| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICCALL` or `DELEGATECALL`). | | `target` **`indexed`** | `address` | The address to call. `target` will be unused if a contract is created (operation types 1 and 2). | | `value` | `uint256` | The amount of native tokens transferred along the call (in Wei). | | `selector` **`indexed`** | `bytes4` | The first 4 bytes (= function selector) of the data sent with the call. | diff --git a/docs/contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateUP.md b/docs/contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateUP.md index b08ec1df24..3ee0d39f43 100644 --- a/docs/contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateUP.md +++ b/docs/contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateUP.md @@ -103,7 +103,7 @@ See [`IERC165-supportsInterface`](#ierc165-supportsinterface). :::caution Warning -When the data stored in the ERC725Y storage of the LSP0 contract is corrupted (\_e.g: ([LSP-5-ReceivedAssets]'s Array length not 16 bytes long, the token received is already registered in `LSP5ReceivetAssets[]`, the token being sent is not sent as full balance, etc...), the function call will still pass and return (**not revert!**) and not modify any data key on the storage of the [LSP-0-ERC725Account]. +When the data stored in the ERC725Y storage of the LSP0 contract is corrupted (\_e.g: ([LSP-5-ReceivedAssets]'s Array length not 16 bytes long, the token received is already registered in `LSP5ReceivedAssets[]`, the token being sent is not sent as full balance, etc...), the function call will still pass and return (**not revert!**) and not modify any data key on the storage of the [LSP-0-ERC725Account]. ::: diff --git a/docs/contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateUP/LSP1UniversalReceiverDelegateUP.md b/docs/contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateUP/LSP1UniversalReceiverDelegateUP.md index 62b70d1109..be8e2a90b2 100644 --- a/docs/contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateUP/LSP1UniversalReceiverDelegateUP.md +++ b/docs/contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateUP/LSP1UniversalReceiverDelegateUP.md @@ -103,7 +103,7 @@ See [`IERC165-supportsInterface`](#ierc165-supportsinterface). :::caution Warning -When the data stored in the ERC725Y storage of the LSP0 contract is corrupted (\_e.g: ([LSP-5-ReceivedAssets]'s Array length not 16 bytes long, the token received is already registered in `LSP5ReceivetAssets[]`, the token being sent is not sent as full balance, etc...), the function call will still pass and return (**not revert!**) and not modify any data key on the storage of the [LSP-0-ERC725Account]. +When the data stored in the ERC725Y storage of the LSP0 contract is corrupted (\_e.g: ([LSP-5-ReceivedAssets]'s Array length not 16 bytes long, the token received is already registered in `LSP5ReceivedAssets[]`, the token being sent is not sent as full balance, etc...), the function call will still pass and return (**not revert!**) and not modify any data key on the storage of the [LSP-0-ERC725Account]. ::: diff --git a/docs/contracts/contracts/LSP6KeyManager/LSP6KeyManager.md b/docs/contracts/contracts/LSP6KeyManager/LSP6KeyManager.md index cacf6db911..997bde8e24 100644 --- a/docs/contracts/contracts/LSP6KeyManager/LSP6KeyManager.md +++ b/docs/contracts/contracts/LSP6KeyManager/LSP6KeyManager.md @@ -132,7 +132,7 @@ function executeBatch( ) external payable returns (bytes[]); ``` -\*Executing the following batch of payloads and sensind on the linked contract. +\*Executing the following batch of payloads and sending on the linked contract. - payloads: `payloads` @@ -241,7 +241,7 @@ function executeRelayCallBatch( _Executing a batch of relay calls (= meta-transactions)._ -Same as [`executeRelayCall`](#executerelaycall) but execute a batch of signed calldata payloads (abi-encoded function calls) in a single transaction. The `signatures` can be from multiple controllers, not necessarely the same controller, as long as each of these controllers that signed have the right permissions related to the calldata `payload` they signed. +Same as [`executeRelayCall`](#executerelaycall) but execute a batch of signed calldata payloads (abi-encoded function calls) in a single transaction. The `signatures` can be from multiple controllers, not necessarily the same controller, as long as each of these controllers that signed have the right permissions related to the calldata `payload` they signed.
diff --git a/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CappedSupply.md b/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CappedSupply.md index 3aa92fd57d..db297ea27c 100644 --- a/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CappedSupply.md +++ b/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CappedSupply.md @@ -634,7 +634,7 @@ function tokenSupplyCap() external view returns (uint256); _The maximum supply amount of tokens allowed to exist is `_TOKEN_SUPPLY_CAP`._ -Get the maximum number of tokens that can exist to circulate. Once [`totalSupply`](#totalsupply) reaches reaches [`totalSuuplyCap`](#totalsuuplycap), it is not possible to mint more tokens. +Get the maximum number of tokens that can exist to circulate. Once [`totalSupply`](#totalsupply) reaches reaches [`totalSupplyCap`](#totalsuuplycap), it is not possible to mint more tokens. #### Returns diff --git a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CappedSupply.md b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CappedSupply.md index ee12adcddc..4de60b91d4 100644 --- a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CappedSupply.md +++ b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CappedSupply.md @@ -729,7 +729,7 @@ function tokenSupplyCap() external view returns (uint256); _The maximum supply amount of tokens allowed to exist is `_TOKEN_SUPPLY_CAP`._ -Get the maximum number of tokens that can exist to circulate. Once [`totalSupply`](#totalsupply) reaches reaches [`totalSuuplyCap`](#totalsuuplycap), it is not possible to mint more tokens. +Get the maximum number of tokens that can exist to circulate. Once [`totalSupply`](#totalsupply) reaches reaches [`totalSupplyCap`](#totalsuuplycap), it is not possible to mint more tokens. #### Returns diff --git a/docs/contracts/contracts/LSP9Vault/LSP9Vault.md b/docs/contracts/contracts/LSP9Vault/LSP9Vault.md index 7b74a92fb3..6104066500 100644 --- a/docs/contracts/contracts/LSP9Vault/LSP9Vault.md +++ b/docs/contracts/contracts/LSP9Vault/LSP9Vault.md @@ -1280,7 +1280,7 @@ Emitted when calling an address `target` (EOA or contract) with `value`. | Name | Type | Description | | ----------------------------- | :-------: | ---------------------------------------------------------------------------------------------------- | -| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICALL` or `DELEGATECALL`). | +| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICCALL` or `DELEGATECALL`). | | `target` **`indexed`** | `address` | The address to call. `target` will be unused if a contract is created (operation types 1 and 2). | | `value` | `uint256` | The amount of native tokens transferred along the call (in Wei). | | `selector` **`indexed`** | `bytes4` | The first 4 bytes (= function selector) of the data sent with the call. | diff --git a/docs/contracts/contracts/UniversalProfile.md b/docs/contracts/contracts/UniversalProfile.md index 1af69dc7ab..fb3a1c6763 100644 --- a/docs/contracts/contracts/UniversalProfile.md +++ b/docs/contracts/contracts/UniversalProfile.md @@ -1289,7 +1289,7 @@ Emitted when calling an address `target` (EOA or contract) with `value`. | Name | Type | Description | | ----------------------------- | :-------: | ---------------------------------------------------------------------------------------------------- | -| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICALL` or `DELEGATECALL`). | +| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICCALL` or `DELEGATECALL`). | | `target` **`indexed`** | `address` | The address to call. `target` will be unused if a contract is created (operation types 1 and 2). | | `value` | `uint256` | The amount of native tokens transferred along the call (in Wei). | | `selector` **`indexed`** | `bytes4` | The first 4 bytes (= function selector) of the data sent with the call. | diff --git a/docs/contracts/contracts/UniversalProfile/UniversalProfile.md b/docs/contracts/contracts/UniversalProfile/UniversalProfile.md index 4257ec4e56..95d847a686 100644 --- a/docs/contracts/contracts/UniversalProfile/UniversalProfile.md +++ b/docs/contracts/contracts/UniversalProfile/UniversalProfile.md @@ -1299,7 +1299,7 @@ Emitted when calling an address `target` (EOA or contract) with `value`. | Name | Type | Description | | ----------------------------- | :-------: | ---------------------------------------------------------------------------------------------------- | -| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICALL` or `DELEGATECALL`). | +| `operationType` **`indexed`** | `uint256` | The low-level call opcode used to call the `target` address (`CALL`, `STATICCALL` or `DELEGATECALL`). | | `target` **`indexed`** | `address` | The address to call. `target` will be unused if a contract is created (operation types 1 and 2). | | `value` | `uint256` | The amount of native tokens transferred along the call (in Wei). | | `selector` **`indexed`** | `bytes4` | The first 4 bytes (= function selector) of the data sent with the call. | diff --git a/docs/contracts/overview/NFT/customise-transfer-behaviour.md b/docs/contracts/overview/NFT/customise-transfer-behaviour.md index 5ba93b91ea..ead370698b 100644 --- a/docs/contracts/overview/NFT/customise-transfer-behaviour.md +++ b/docs/contracts/overview/NFT/customise-transfer-behaviour.md @@ -5,4 +5,4 @@ sidebar_position: 2 # Customize transfer behaviour -The `LSP8IdenfitiableDigitalAsset` contract implementation includes the `_beforeTokenTransfer` and `_afterTokenTransfer` functions that offer the ability to specify custom logic that can run before or after the token transfer has happen (= before or after the balances in the contract state have been updated). +The `LSP8IdentifiableDigitalAsset` contract implementation includes the `_beforeTokenTransfer` and `_afterTokenTransfer` functions that offer the ability to specify custom logic that can run before or after the token transfer has happen (= before or after the balances in the contract state have been updated). diff --git a/docs/faq/lukso/feature-requests.md b/docs/faq/lukso/feature-requests.md index abeb28ed42..af6c419bce 100644 --- a/docs/faq/lukso/feature-requests.md +++ b/docs/faq/lukso/feature-requests.md @@ -16,7 +16,7 @@ Yes, developers have several options for financial support when building on LUKS ## Will LUKSO be listed on additional exchanges? -At the moment, LUKSO is available on [KuCoin](https://www.kucoin.com/de), [Crypto.com](https://crypto.com/), and [Gate.io](https://www.gate.io/). As the network continues to expand, additionl exchanges may consider joining. It is important to note that this decision is entirely at the discretion of the exchanges. +At the moment, LUKSO is available on [KuCoin](https://www.kucoin.com/de), [Crypto.com](https://crypto.com/), and [Gate.io](https://www.gate.io/). As the network continues to expand, additional exchanges may consider joining. It is important to note that this decision is entirely at the discretion of the exchanges. ## Will there be a Mobile Application for Universal Profiles? diff --git a/docs/faq/network/blockchain-architecture.md b/docs/faq/network/blockchain-architecture.md index f7de66a626..bb1632d485 100644 --- a/docs/faq/network/blockchain-architecture.md +++ b/docs/faq/network/blockchain-architecture.md @@ -43,7 +43,7 @@ The LUKSO Mainnet is up to date with [every Ethereum fork](https://ethereum.org/ Having a variety of clients in a blockchain network and improving our client diversity is critically important. Client diversity refers to utilizing different software clients in a blockchain network developed by various teams and in other programming languages to improve the following: - **Security and Resilience**: Client diversity increases the robustness of the network. If there's a bug in one client, it doesn't bring down the entire network because other clients can continue to operate. This decentralization and redundancy is a fundamental aspect of blockchain security and resilience. -- **Decentralization and Governanc**e: Client diversity promotes decentralization in the development and governance of the Ethereum network. It prevents any team or entity from having too much influence over the network's growth. +- **Decentralization and Governance**: Client diversity promotes decentralization in the development and governance of the Ethereum network. It prevents any team or entity from having too much influence over the network's growth. For Ethereum, **client diversity has proven essential** in maintaining the network's robustness during several incidents. One of the most notable incidents were the [Shanghai DoS Attacks in 2016](https://blog.ethereum.org/2016/09/22/ethereum-network-currently-undergoing-dos-attack), the [OpenEthereum Consensus Bug in 2020](https://www.coindesk.com/tech/2020/08/27/buggy-code-release-knocks-13-of-ethereum-nodes-offline/), and the [Prysm Client Incident in 2023](https://offchain.medium.com/post-mortem-report-ethereum-mainnet-finality-05-11-2023-95e271dfd8b2). You can find an overview of these bugs within the [extended client section](https://docs.luksoverse.io/docs/mainnet/complete-node-guide/blockchain-clients/client-setups) by the community. @@ -87,7 +87,7 @@ An epoch in PoS is a fixed period during which slots occur. It is a larger time Epochs provide several vital functions: - **Validator Shuffling**: At the start of each epoch, a random selection process determines the active validators and assigns them to slots. This is done to ensure that the system remains decentralized and that no single validator can predict far in advance when they will be selected. -- **Rewards and Penaltie**s: At the end of each epoch, rewards and penalties are calculated for validators. Validators that correctly proposed and attested to blocks receive rewards, while those who behaved maliciously or were offline are penalized. +- **Rewards and Penalties**: At the end of each epoch, rewards and penalties are calculated for validators. Validators that correctly proposed and attested to blocks receive rewards, while those who behaved maliciously or were offline are penalized. - **Finality**: An epoch also plays a role in achieving finality. Finality refers to the point at which a block cannot be changed or removed from the blockchain. The finality is achieved in every epoch. ## What are slots? diff --git a/docs/faq/network/staking.md b/docs/faq/network/staking.md index 6afee81fc9..648dd7735a 100644 --- a/docs/faq/network/staking.md +++ b/docs/faq/network/staking.md @@ -40,7 +40,7 @@ No. Rewards are given out for each validator key separately and do not increase ## Are LYX/LYXt locked after they have been deposited? -No, validators are not locked after depositing their stake. The locking **only occurred for genesis deposits** before the Shappella fork went live on the LUKSO mainnet. Please remember that the deposited LYX can only be exited from the network after they have been activated, which may take up to 24h. In addition, the exit process may also **take up to multiple hours** until it is picked up from the consensus. Please also note that it requires setting withdrawal credentials to withdraw your funds to an account. +No, validators are not locked after depositing their stake. The locking **only occurred for genesis deposits** before the Shapella fork went live on the LUKSO mainnet. Please remember that the deposited LYX can only be exited from the network after they have been activated, which may take up to 24h. In addition, the exit process may also **take up to multiple hours** until it is picked up from the consensus. Please also note that it requires setting withdrawal credentials to withdraw your funds to an account. ## Are there different types of withdrawals for validators? diff --git a/docs/faq/network/validators.md b/docs/faq/network/validators.md index 503bf2db25..3478953b0f 100644 --- a/docs/faq/network/validators.md +++ b/docs/faq/network/validators.md @@ -56,7 +56,7 @@ If you plan to become a validator for testnet, please contact `testnet-validator ## What happens when my validator is offline? -In Proof of Stake, validators can be penalized for being offline. The **penalties for an offline validator are dynamically adjusted** based on the total amount of offline validators and their offline duration. You can find rough estemates within the [staking section](./staking.md) of the FAQ. +In Proof of Stake, validators can be penalized for being offline. The **penalties for an offline validator are dynamically adjusted** based on the total amount of offline validators and their offline duration. You can find rough estimates within the [staking section](./staking.md) of the FAQ. This mechanism **incentivizes validators to stay online** and actively participate in the network's consensus process. Validators are expected to be online to propose and attest to blocks. If a validator is offline, they're not fulfilling their role, so their balance slowly leaks over time. The inactivity penalty is proportional to the square of the time the validator has been offline, meaning the penalty accelerates the longer the validator is offline. diff --git a/docs/faq/onboarding/lukso-standards.md b/docs/faq/onboarding/lukso-standards.md index ecd59cd23a..686357fa44 100644 --- a/docs/faq/onboarding/lukso-standards.md +++ b/docs/faq/onboarding/lukso-standards.md @@ -23,7 +23,7 @@ With LSPs, the mission is to have standards that facilitate using tools that abs - Assets can be **anchored** directly to the blockchain **account's storage** using [LSP1](/standards/accounts/lsp1-universal-receiver), abandoning complex data fetching. - Token IDs have an increased size and can map any serial number (for digital or physical products) on-chain, which also allows NFC integration. - Developers and users can safely utilize **events from asset contracts**, regulate allowlists and blocklists, customize UI and app workflows, or create consensus for asset transfers using LSP1 Delegate. -- Assets have **built-in security for sending assets** to accounts without recovery, utiliszing account abstraction with their force parameter in [LSP7](/standards/tokens/LSP7-Digital-Asset) and [LSP8](/standards/tokens/LSP8-Identifiable-Digital-Asset). +- Assets have **built-in security for sending assets** to accounts without recovery, utilizing account abstraction with their force parameter in [LSP7](/standards/tokens/LSP7-Digital-Asset) and [LSP8](/standards/tokens/LSP8-Identifiable-Digital-Asset). - Attached data can always be verified through hash integration in the [LSP2](/standards/metadata/lsp2-json-schema) schema. - Assets can be **organized and managed in vaults** using [LSP9](/standards/accounts/lsp9-vault). Here, multiple services and games can have permissioned access for updating the asset data of user accounts. - For NFTs, individual token IDs from a collection can have **separate metadata**, upgrades, creators, and behaviors, instead of just being limited to the logic of the mint contract. diff --git a/docs/learn/concepts.md b/docs/learn/concepts.md index 022be0400c..e2cc6013c4 100644 --- a/docs/learn/concepts.md +++ b/docs/learn/concepts.md @@ -23,5 +23,5 @@ Highlight any word and click `Ask Cookbook` in the Navbar for its definition. | [ERC725Y](/standards/erc725#erc725x) | ERC725Y is the basic tool that lets you store information, while LSP2 is the set of rules that makes sure everyone stores and retrieves this information in an organized and understandable way. | | [LYXt](../../docs/faq/lukso/general-information.md#whats-the-difference-between-lyxt-lyxe-and-lyx) | LYXt is the token for developers to use on our testnet. It can always be acquired by anyone for free. | | [LYXe](../../docs/faq/lukso/general-information.md#whats-the-difference-between-lyxt-lyxe-and-lyx) | LYXe is the token that was deployed on Ethereum before LUKSO Mainnet was launched. It allowed people to invest in LUKSO pre-launch. | -| [Metadata](/standards/metadata/lsp3-profile-metadata.md) | This typically refers to the additional data that is stored against a token or NFT. The difference on LUKSO is it can be extended.

For example, imagine you've bought a house and have the deed as an NFT on LUKSO. Well now, as rennovations are carried out, they can be continually added to the NFT for history. | +| [Metadata](/standards/metadata/lsp3-profile-metadata.md) | This typically refers to the additional data that is stored against a token or NFT. The difference on LUKSO is it can be extended.

For example, imagine you've bought a house and have the deed as an NFT on LUKSO. Well now, as renovations are carried out, they can be continually added to the NFT for history. | | Account Abstraction | Account abstraction is abstracting away smart contract execution from storing funds. With a smart contract account, you can program it to do all sorts of things. You can set up automatic payments, create multi-signature wallets that require multiple people to approve transactions, or even add security features like daily spending limits. It's like having a customizable, programmable bank account on the blockchain. | diff --git a/docs/learn/digital-assets/metadata-management/read-asset-data.md b/docs/learn/digital-assets/metadata-management/read-asset-data.md index f286b290e5..51872c07d1 100644 --- a/docs/learn/digital-assets/metadata-management/read-asset-data.md +++ b/docs/learn/digital-assets/metadata-management/read-asset-data.md @@ -235,7 +235,7 @@ console.log(tokenSymbol); To fetch the whole JSON file of the asset's metadata, you can use the following 2 functions of the [`erc725js`](../../../tools/dapps/erc725js/getting-started.md) library: - [`fetchData('LSP4Metadata')`](../../../tools/dapps/erc725js/methods.md#fetchdata): This will download and decode the content of `VerifiableURI` as JSON. -- [`getData(LSP4Metadata)`](../../../tools/dapps/erc725js/methods#getdata): This will retrieve the raw data value from the smart contract. You will then need to decode the `VerifiableURI` maunually using [`decodeData(...)`](../../../tools/dapps/erc725js/methods.md#decodedata). +- [`getData(LSP4Metadata)`](../../../tools/dapps/erc725js/methods#getdata): This will retrieve the raw data value from the smart contract. You will then need to decode the `VerifiableURI` manually using [`decodeData(...)`](../../../tools/dapps/erc725js/methods.md#decodedata). ```ts // Download and verify the asset metadata JSON file @@ -386,4 +386,4 @@ Based on the [token type](#detect-the-token-type), the information of the [LSP4 - If your asset is a Token (`tokenType = 0`), individual metadata **can't be set**, due to the lack of token IDs. - If your asset is an NFT (`tokenType = 1`), individual metadata **may be set in addition** to the global token information. -- If your asset is a Collection (`tokenType = 2`), the token ID-specific medatada is **mandatory**. +- If your asset is a Collection (`tokenType = 2`), the token ID-specific metadata is **mandatory**. diff --git a/docs/learn/digital-assets/nft/create-nft-collection-lsp8.md b/docs/learn/digital-assets/nft/create-nft-collection-lsp8.md index 48cb117f75..0ea59f317f 100644 --- a/docs/learn/digital-assets/nft/create-nft-collection-lsp8.md +++ b/docs/learn/digital-assets/nft/create-nft-collection-lsp8.md @@ -33,7 +33,7 @@ When creating smart contracts representing digital assets on LUKSO, you need to - `1` = NFT - `2` = Collection -For this example we will use the `Collection` token type. You can create a custom 🌄 [LSP8 Identfiable Digital Asset Collection](../../../standards/tokens/LSP8-Identifiable-Digital-Asset.md) that extends [LSP8Mintable](../../../contracts/contracts/LSP8IdentifiableDigitalAsset/presets/LSP8Mintable.md) so that new assets can be created within the smart contract. +For this example we will use the `Collection` token type. You can create a custom 🌄 [LSP8 Identifiable Digital Asset Collection](../../../standards/tokens/LSP8-Identifiable-Digital-Asset.md) that extends [LSP8Mintable](../../../contracts/contracts/LSP8IdentifiableDigitalAsset/presets/LSP8Mintable.md) so that new assets can be created within the smart contract. ```solidity title="contracts/BasicNFTCollection.sol" // SPDX-License-Identifier: MIT diff --git a/docs/learn/digital-assets/nft/create-nft-collection-with-lsp7-tokenId.md b/docs/learn/digital-assets/nft/create-nft-collection-with-lsp7-tokenId.md index d420655fa9..d6a8587de0 100644 --- a/docs/learn/digital-assets/nft/create-nft-collection-with-lsp7-tokenId.md +++ b/docs/learn/digital-assets/nft/create-nft-collection-with-lsp7-tokenId.md @@ -24,11 +24,11 @@ If you have been looking at the [LSP8 token standard](../../../standards/tokens/ ## Use Case -Let's take the example of [The Dematerialised](https://thedematerialised.com), and more precisely their KLxENDLESS PHYGITAL COLLECTION. As you can see in the picture below, we have three medalions of different colours.s +Let's take the example of [The Dematerialised](https://thedematerialised.com), and more precisely their KLxENDLESS PHYGITAL COLLECTION. As you can see in the picture below, we have three medallions of different colours. ![KLxENDLESS PHYSITAL COLLECTION](../../../../static/img/learn/klxendless-physital-collection.png) -Each medaillon has a supply limit and each medaillon collection has its own metadata with different attributes. What we will do is create an [LSP8 collection](../../../standards/tokens//LSP8-Identifiable-Digital-Asset.md) that will represent the whole KLxENDLESS PHYSITAL collection and each medaillon will be a sub-collection (purple, blue or gold) will with a limited supply of NFTs [(Non-divisible LSP7 token)](../../../standards/tokens//LSP7-Digital-Asset.md). +Each medallion has a supply limit and each medallion collection has its own metadata with different attributes. What we will do is create an [LSP8 collection](../../../standards/tokens//LSP8-Identifiable-Digital-Asset.md) that will represent the whole KLxENDLESS PHYSITAL collection and each medallion will be a sub-collection (purple, blue or gold) will with a limited supply of NFTs [(Non-divisible LSP7 token)](../../../standards/tokens//LSP7-Digital-Asset.md). ## Create the LSP7 Sub-Collection @@ -581,7 +581,7 @@ We will do the same with the LSP7 Sub-Collection metadata. Let's create a `lsp7S "method": "keccak256(bytes)", "data": "0x88f3d704f3d534267c564019ce2b70a5733d070e71bf2c1f85b5fc487f47a46f" }, - "url": "ifps://QmTDQGR26dSd3c4qJpmFwTh7gNRPnNbBf2Fg3gULypUag3", + "url": "ipfs://QmTDQGR26dSd3c4qJpmFwTh7gNRPnNbBf2Fg3gULypUag3", "fileType": "mp4" } ], diff --git a/docs/learn/digital-assets/token/create-lsp7-token.md b/docs/learn/digital-assets/token/create-lsp7-token.md index 914dde09fc..27896d6659 100644 --- a/docs/learn/digital-assets/token/create-lsp7-token.md +++ b/docs/learn/digital-assets/token/create-lsp7-token.md @@ -155,7 +155,7 @@ module.exports = [ ]; ``` -To verify the deployed token, you can use the **blockscout API properties** set up within the [Getting Started](../../../learn/getting-started.mdx) section. If you configured the API, you will be able to run the verification by specifying the _token address_, _paramter file_, and _network_: +To verify the deployed token, you can use the **blockscout API properties** set up within the [Getting Started](../../../learn/getting-started.mdx) section. If you configured the API, you will be able to run the verification by specifying the _token address_, _parameter file_, and _network_: ```bash npx hardhat verify --constructor-args ./verify/myCustomToken.ts --network luksoTestnet diff --git a/docs/learn/migrate/migrate-erc20-to-lsp7.md b/docs/learn/migrate/migrate-erc20-to-lsp7.md index bd67aecaab..f13489c448 100644 --- a/docs/learn/migrate/migrate-erc20-to-lsp7.md +++ b/docs/learn/migrate/migrate-erc20-to-lsp7.md @@ -325,7 +325,7 @@ const retrievedJsonMetadata = JSON.parse(ethers.toUtf8String(storedMetadata)); { width: 256, height: 256, - url: 'ifps://QmW5cF4r9yWeY1gUCtt7c6v3ve7Fzdg8CKvTS96NU9Uiwr', + url: 'ipfs://QmW5cF4r9yWeY1gUCtt7c6v3ve7Fzdg8CKvTS96NU9Uiwr', verification: { method: 'keccak256(bytes)', data: '0x01299df007997de92a820c6c2ec1cb2d3f5aa5fc1adf294157de563eba39bb6f', @@ -337,7 +337,7 @@ const retrievedJsonMetadata = JSON.parse(ethers.toUtf8String(storedMetadata)); { width: 1024, height: 974, - url: 'ifps://QmW4wM4r9yWeY1gUCtt7c6v3ve7Fzdg8CKvTS96NU9Uiwr', + url: 'ipfs://QmW4wM4r9yWeY1gUCtt7c6v3ve7Fzdg8CKvTS96NU9Uiwr', verification: { method: 'keccak256(bytes)', data: '0xa9399df007997de92a820c6c2ec1cb2d3f5aa5fc1adf294157de563eba39bb6e', @@ -352,7 +352,7 @@ const retrievedJsonMetadata = JSON.parse(ethers.toUtf8String(storedMetadata)); method: 'keccak256(bytes)', data: '0x98fe032f81c43426fbcfb21c780c879667a08e2a65e8ae38027d4d61cdfe6f55', }, - url: 'ifps://QmPJESHbVkPtSaHntNVY5F6JDLW8v69M2d6khXEYGUMn7N', + url: 'ipfs://QmPJESHbVkPtSaHntNVY5F6JDLW8v69M2d6khXEYGUMn7N', fileType: 'fbx' }], attributes: [ diff --git a/docs/learn/other-guides/utilize-ipfs-storage.md b/docs/learn/other-guides/utilize-ipfs-storage.md index 4a96d56952..deaf9e676f 100644 --- a/docs/learn/other-guides/utilize-ipfs-storage.md +++ b/docs/learn/other-guides/utilize-ipfs-storage.md @@ -256,7 +256,7 @@ if (results.length > 0) { **Using Sense** -To upload files via IPFS using Sense Protocol, please setup api key and add thata as environment variables. +To upload files via IPFS using Sense Protocol, please setup api key and add that as environment variables. ```ts import { SenseUploader } from '@lukso/data-provider-sense'; diff --git a/docs/learn/universal-profile/advanced-guides/upgrade-key-manager.md b/docs/learn/universal-profile/advanced-guides/upgrade-key-manager.md index 9fa5732137..f75253569a 100644 --- a/docs/learn/universal-profile/advanced-guides/upgrade-key-manager.md +++ b/docs/learn/universal-profile/advanced-guides/upgrade-key-manager.md @@ -407,7 +407,7 @@ const testLSP6 = async () => { console.log( `The new owner of the Universal Profile is: ${universalProfileOwner}`, ); - console.log(`The old LSP6 Key Manager is at address: ${keyManagerAdderss}`); + console.log(`The old LSP6 Key Manager is at address: ${keyManagerAddress}`); const keyManager = new web3.eth.Contract( LSP6KeyManager.abi, diff --git a/docs/learn/universal-profile/universal-receiver/accept-reject-assets.md b/docs/learn/universal-profile/universal-receiver/accept-reject-assets.md index 8c4932911e..d33f84a9c3 100644 --- a/docs/learn/universal-profile/universal-receiver/accept-reject-assets.md +++ b/docs/learn/universal-profile/universal-receiver/accept-reject-assets.md @@ -44,7 +44,7 @@ A full list of LSP1 TypeIds that can be filtered from the `UniversalReceiver` ev // SPDX-License-Identifier: UNLICENSED pragma solidity ^0.8.0; -// This code is only used for guides puprose, it is working but not verified nor audited. +// This code is only used for guides purpose, it is working but not verified nor audited. // modules import {LSP1UniversalReceiverDelegateUP} from "@lukso/lsp-smart-contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateUP/LSP1UniversalReceiverDelegateUP.sol"; @@ -344,7 +344,7 @@ contract CustomUniversalReceiverDelegate is LSP1UniversalReceiverDelegateUP { /** * @dev Reverts when the asset being transferred is not allowed. If allowed, the address of the asset * will be registered inside the storage, and removed when balance of the asset equal 0, according to - * the LSP5-ReceivedAssers standard. + * the LSP5-ReceivedAssets standard. * * @param caller The address of the asset informing the `universalReceiver(..)` function on the UniversalProfile. * @param value The amount of native tokens sent by the caller to the universalReceiver function on the UniversalProfile. diff --git a/docs/learn/vault/interact-with-contracts.md b/docs/learn/vault/interact-with-contracts.md index 14b0686f0d..1dcd49a027 100644 --- a/docs/learn/vault/interact-with-contracts.md +++ b/docs/learn/vault/interact-with-contracts.md @@ -39,7 +39,7 @@ To complete this mini-guide, we will need: :::info -The chosen EOA needs to have [**CALL Permission**](../../standards/access-control/lsp6-key-manager.md#permissions) together with [**AllowedCalls**](../../standards/access-control/lsp6-key-manager.md#allowed-calls) or [**SUPER_CALL Pemrission**](../../standards/access-control/lsp6-key-manager.md#super-permissions) +The chosen EOA needs to have [**CALL Permission**](../../standards/access-control/lsp6-key-manager.md#permissions) together with [**AllowedCalls**](../../standards/access-control/lsp6-key-manager.md#allowed-calls) or [**SUPER_CALL Permission**](../../standards/access-control/lsp6-key-manager.md#super-permissions) ::: diff --git a/docs/standards/access-control/lsp14-ownable-2-step.md b/docs/standards/access-control/lsp14-ownable-2-step.md index 68265ee753..c5684b7402 100644 --- a/docs/standards/access-control/lsp14-ownable-2-step.md +++ b/docs/standards/access-control/lsp14-ownable-2-step.md @@ -34,7 +34,7 @@ What is needed is a safer mechanism for managing contract ownership. **LSP14 - Ownable2Step** is an extended version of [EIP173 - Contract Ownership Standard](https://eips.ethereum.org/EIPS/eip-173) that uses a 2-step process for transferring and renouncing ownership. -**LSP14 - Ownable2Step** modifies the processes of _tranferring and renouncing ownership_ in the following way: +**LSP14 - Ownable2Step** modifies the processes of _transferring and renouncing ownership_ in the following way: 1. For _transferring ownership_ the method `transferOwnership(...)` is modified in a way so the **address** passed as parameter will not be the owner directly but a pending owner. A new method is introduced, `acceptOwnership()`, which should be called by the **pending owner** in order for the process of _transferring ownership_ to be complete. @@ -77,7 +77,7 @@ Each hook is executed whenever the _new owner confirms the process of transferri ### Renouncing the contract ownership -The control of the contract is refully renounced _once the owner of the contract confirmes the ownership renouncement_. The 2 steps of ownership renouncement are described below: +The control of the contract is refully renounced _once the owner of the contract confirms the ownership renouncement_. The 2 steps of ownership renouncement are described below: 1. The owner initiates the process of ownership renouncement via the ['renounceOwnership()'](../../contracts/contracts/LSP14Ownable2Step/LSP14Ownable2Step.md#renounceownership) function. diff --git a/docs/standards/access-control/lsp6-key-manager.md b/docs/standards/access-control/lsp6-key-manager.md index b34680c8b0..aa8ddcd947 100644 --- a/docs/standards/access-control/lsp6-key-manager.md +++ b/docs/standards/access-control/lsp6-key-manager.md @@ -194,7 +194,7 @@ _Example:_ One of the best uses for this permission is the following scenario: -1. The ERC725Acccount linked to the Key Manager makes an external call to a _contract A_. +1. The ERC725Account linked to the Key Manager makes an external call to a _contract A_. 2. _Contract A_ will make some internal updates using the received data. 3. The _contract A_ will then call back the ERC725Account **(via the Key Manager)** with another payload that will update the account storage. @@ -627,7 +627,7 @@ If you want to have multiple different interactions, you MUST add each of the de
Example 1: allow only to CALL a specific LSP0 at a specific address -To allow a controller to only do `CALL` to any function on a LSP0ERC725Account (interface ID `0x3e89ad98`) deployed at address `0xCA41e4ea94c8fA99889c8EA2c8948768cBaf4bc0`, the following value for the CompactBYytesArray of allowed calls will be used: +To allow a controller to only do `CALL` to any function on a LSP0ERC725Account (interface ID `0x3e89ad98`) deployed at address `0xCA41e4ea94c8fA99889c8EA2c8948768cBaf4bc0`, the following value for the CompactBytesArray of allowed calls will be used: `0x002000000002CA41e4ea94c8fA99889c8EA2c8948768cBaf4bc03e89ad98ffffffff` diff --git a/docs/standards/accounts/lsp1-universal-receiver.md b/docs/standards/accounts/lsp1-universal-receiver.md index 6b21004802..c67295a35b 100644 --- a/docs/standards/accounts/lsp1-universal-receiver.md +++ b/docs/standards/accounts/lsp1-universal-receiver.md @@ -66,7 +66,7 @@ For example, **to notify the recipient that he is about to receive tokens**, dur - bytes32 `typeId`: **Hash**('ERCXXXXTokenReceived') - bytes `data`: **packedData**(amount of token sent, the sender address, the block timestamp) -In this way, instead of **listening to all the events of the token contrats on the network**, and checking which one of these transfers is relative to the recipient, users can listen to the **[UniversalReceiver](../../contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md#universalreceiver-1)** event on the contract implementing the `universalReceiver(..)` and know the token transfer details. +In this way, instead of **listening to all the events of the token contracts on the network**, and checking which one of these transfers is relative to the recipient, users can listen to the **[UniversalReceiver](../../contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md#universalreceiver-1)** event on the contract implementing the `universalReceiver(..)` and know the token transfer details. As well as emitting an event, the `universalReceiver(...)` function can implement **custom logic** to make the contract behave differently based on the data received. Some ideas include: diff --git a/docs/standards/accounts/lsp15-transaction-relayer-api.md b/docs/standards/accounts/lsp15-transaction-relayer-api.md index 7f2f788fd4..0cf75f32b9 100644 --- a/docs/standards/accounts/lsp15-transaction-relayer-api.md +++ b/docs/standards/accounts/lsp15-transaction-relayer-api.md @@ -57,7 +57,7 @@ Executes a signed transaction on behalf of a Universal Profile using [`executeRe Returns the available quota left for a registered Universal Profile. -- `signature` is the message value signed by a controller key with the [`SIGN` permission](../access-control/lsp6-key-manager#permissions) of the Universal Profile. The hash to sign should be calculated as [EIP-712](https://eips.ethereum.org/EIPS/eip-712) hash where the message is `keccack256(address, timestamp)`. Make sure that no matter the language or platform timestamp is of type `int`, `int256`, `uint` or `uint256`. In the backend the message is reconstructed using [soliditysha3()](https://web3js.readthedocs.io/en/v1.7.4/web3-utils.html#soliditysha3) to verify the signature. +- `signature` is the message value signed by a controller key with the [`SIGN` permission](../access-control/lsp6-key-manager#permissions) of the Universal Profile. The hash to sign should be calculated as [EIP-712](https://eips.ethereum.org/EIPS/eip-712) hash where the message is `keccak256(address, timestamp)`. Make sure that no matter the language or platform timestamp is of type `int`, `int256`, `uint` or `uint256`. In the backend the message is reconstructed using [soliditysha3()](https://web3js.readthedocs.io/en/v1.7.4/web3-utils.html#soliditysha3) to verify the signature. [Web3.js](https://web3js.readthedocs.io/en/v1.8.0/web3-eth-accounts.html?#sign) and [ethers.js](https://docs.ethers.io/v5/api/signer/#Signer-signMessage) both automatically hash when using their native sign functions. This may need to be done manually if using a different library. diff --git a/docs/standards/metadata/lsp3-profile-metadata.md b/docs/standards/metadata/lsp3-profile-metadata.md index dea05a792d..370f136462 100644 --- a/docs/standards/metadata/lsp3-profile-metadata.md +++ b/docs/standards/metadata/lsp3-profile-metadata.md @@ -85,7 +85,7 @@ Inside the JSON file, the keys `profileImage` and `backgroundImage` can accept a { "hashFunction": "keccak256(bytes)", "hash": "0x98fe032f81c43426fbcfb21c780c879667a08e2a65e8ae38027d4d61cdfe6f55", - "url": "ifps://QmPJESHbVkPtSaHntNVY5F6JDLW8v69M2d6khXEYGUMn7N", + "url": "ipfs://QmPJESHbVkPtSaHntNVY5F6JDLW8v69M2d6khXEYGUMn7N", "fileType": "fbx" } ], @@ -101,14 +101,14 @@ Inside the JSON file, the keys `profileImage` and `backgroundImage` can accept a "height": 1013, "hashFunction": "keccak256(bytes)", "hash": "0x98fe032f81c43426fbcfb21c780c879667a08e2a65e8ae38027d4d61cdfe6f55", - "url": "ifps://QmPJESHbVkPtSaHntNVY5F6JDLW8v69M2d6khXEYGUMn7N" + "url": "ipfs://QmPJESHbVkPtSaHntNVY5F6JDLW8v69M2d6khXEYGUMn7N" }, { "width": 1024, "height": 576, "hashFunction": "keccak256(bytes)", "hash": "0xfce1c7436a77a009a97e48e4e10c92e89fd95fe1556fc5c62ecef57cea51aa37", - "url": "ifps://QmZc9uMJxyUeUpuowJ7AD6MKoNTaWdVNcBj72iisRyM9Su" + "url": "ipfs://QmZc9uMJxyUeUpuowJ7AD6MKoNTaWdVNcBj72iisRyM9Su" } ] } diff --git a/docs/standards/tokens/LSP8-Identifiable-Digital-Asset.md b/docs/standards/tokens/LSP8-Identifiable-Digital-Asset.md index 41a467de12..02e1223c71 100644 --- a/docs/standards/tokens/LSP8-Identifiable-Digital-Asset.md +++ b/docs/standards/tokens/LSP8-Identifiable-Digital-Asset.md @@ -125,7 +125,7 @@ During an **ERC721 token transfer**, the ownership of the tokenId is changed fro ![ERC721 Transfer](/img/standards/lsp8/erc721-transfer.jpeg) -During an **LSP8 token transfer**, as well as updating the tokenId ownership, both the sender and recipient are informed of the transfer by calling the **[`universalReceiever(...)`](../accounts/lsp1-universal-receiver.md#lsp1---universal-receiver)** function on their profiles. +During an **LSP8 token transfer**, as well as updating the tokenId ownership, both the sender and recipient are informed of the transfer by calling the **[`universalReceiver(...)`](../accounts/lsp1-universal-receiver.md#lsp1---universal-receiver)** function on their profiles. ![LSP8 Transfer](/img/standards/lsp8/lsp8-transfer.jpeg) diff --git a/docs/tools/dapps/erc725js/getting-started.md b/docs/tools/dapps/erc725js/getting-started.md index 809f74721a..375388aeb6 100644 --- a/docs/tools/dapps/erc725js/getting-started.md +++ b/docs/tools/dapps/erc725js/getting-started.md @@ -115,7 +115,7 @@ const reEncodedVerifiableURI = decodeDataSourceWithHash( // verification: { // data: '820464ddfac1bec070cc14a8daf04129871d458f2ca94368aae8391311af6361', // method: 'keccak256(utf8)', -// source: 'ifps://QmYr1VJLwerg6pEoscdhVGugo39pa6rycEZLjtRPDfW84UAx' +// source: 'ipfs://QmYr1VJLwerg6pEoscdhVGugo39pa6rycEZLjtRPDfW84UAx' // }, const verifiableURI = encodeDataSourceWithHash( @@ -123,7 +123,7 @@ const verifiableURI = encodeDataSourceWithHash( method: 'keccak256(utf8)', data: '820464ddfac1bec070cc14a8daf04129871d458f2ca94368aae8391311af6361', }, - 'ifps://QmYr1VJLwerg6pEoscdhVGugo39pa6rycEZLjtRPDfW84UAx', + 'ipfs://QmYr1VJLwerg6pEoscdhVGugo39pa6rycEZLjtRPDfW84UAx', ); // 0x00006f357c6a0020820464ddfac1bec070cc14a8daf04129871d458f2ca94368aae8391311af6361696670733a2f2f516d597231564a4c776572673670456f73636468564775676f3339706136727963455a4c6a7452504466573834554178 ``` diff --git a/docs/tools/dapps/erc725js/methods.md b/docs/tools/dapps/erc725js/methods.md index 2a2d561e58..c7883ade4b 100644 --- a/docs/tools/dapps/erc725js/methods.md +++ b/docs/tools/dapps/erc725js/methods.md @@ -278,7 +278,7 @@ myErc725.encodeData( const schemas = [ { name: 'DynamicKey::', - key: '0xForDynamicKeysThisFieldIsIrrelevantAndWillBeOverwriten', + key: '0xForDynamicKeysThisFieldIsIrrelevantAndWillBeOverwritten', keyType: 'Mapping', valueType: 'bytes', valueContent: 'Address', @@ -982,7 +982,7 @@ myErc725.decodeData( method: 'keccak256(utf8)', data: '0x820464ddfac1bec070cc14a8daf04129871d458f2ca94368aae8391311af6361' }, - url: 'ifps://QmYr1VJLwerg6pEoscdhVGugo39pa6rycEZLjtRPDfW84UAx', + url: 'ipfs://QmYr1VJLwerg6pEoscdhVGugo39pa6rycEZLjtRPDfW84UAx', }, }, ]; @@ -1477,7 +1477,7 @@ The name(s) (or the encoded name(s) as schema key) of the element(s) in the smar ```javascript title="Receiving all keys from the schema" import ERC725 from '@erc725/erc725.js'; -import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.sjon'; +import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.json'; const universalProfileAddress = '0x0F4180da178ed1C71398a57ca8Cb177F69591f1f'; const myErc725 = new ERC725(LSP3Schemas, universalProfileAddress); @@ -1523,7 +1523,7 @@ await myErc725.fetchData(); ```javascript title="Receiving one key from the schema" import ERC725 from '@erc725/erc725.js'; -import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.sjon'; +import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.json'; const universalProfileAddress = '0x0F4180da178ed1C71398a57ca8Cb177F69591f1f'; const myErc725 = new ERC725(LSP3Schemas, universalProfileAddress); @@ -1552,7 +1552,7 @@ await myErc725.fetchData(['LSP1UniversalReceiverDelegate']); ```javascript title="Receiving multiple keys from the schema" import ERC725 from '@erc725/erc725.js'; -import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.sjon'; +import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.json'; const universalProfileAddress = '0x0F4180da178ed1C71398a57ca8Cb177F69591f1f'; const myErc725 = new ERC725(LSP3Schemas, universalProfileAddress); @@ -1642,7 +1642,7 @@ The name(s) (or the encoded name(s) as schema key) of the element(s) in the smar ```javascript title="Receiving all keys from the schema" import ERC725 from '@erc725/erc725.js'; -import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.sjon'; +import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.json'; const universalProfileAddress = '0x0F4180da178ed1C71398a57ca8Cb177F69591f1f'; const myErc725 = new ERC725(LSP3Schemas, universalProfileAddress); @@ -1695,7 +1695,7 @@ await myErc725.getData(); ```javascript title="Receiving one key from the schema" import ERC725 from '@erc725/erc725.js'; -import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.sjon'; +import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.json'; const universalProfileAddress = '0x0F4180da178ed1C71398a57ca8Cb177F69591f1f'; const myErc725 = new ERC725(LSP3Schemas, universalProfileAddress); @@ -1746,7 +1746,7 @@ await myErc725.getData('LSP1UniversalReceiverDelegate'); ```javascript title="Receiving multiple keys from the schema" import ERC725 from '@erc725/erc725.js'; -import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.sjon'; +import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.json'; const universalProfileAddress = '0x0F4180da178ed1C71398a57ca8Cb177F69591f1f'; const myErc725 = new ERC725(LSP3Schemas, universalProfileAddress); @@ -1778,7 +1778,7 @@ await myErc725.getData(['LSP3Profile', 'LSP1UniversalReceiverDelegate']); ```javascript title="Receiving dynamic keys from the schema" import ERC725 from '@erc725/erc725.js'; -import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.sjon'; +import LSP3Schemas from '@erc725/erc725.js/schemas/LSP3ProfileMetadata.json'; const luksoUniversalProfile = '0x8363Cfe6c787218f0ADA0A4aBC289A8d9dfc2453'; const myErc725 = new ERC725(LSP3Schemas, luksoUniversalProfile); @@ -2097,7 +2097,7 @@ const verifiableURI = myErc725.encodeDataSourceWithHash( method: 'keccak256(utf8)', data: '0x820464ddfac1bec070cc14a8daf04129871d458f2ca94368aae8391311af6361', }, - 'ifps://QmYr1VJLwerg6pEoscdhVGugo39pa6rycEZLjtRPDfW84UAx', + 'ipfs://QmYr1VJLwerg6pEoscdhVGugo39pa6rycEZLjtRPDfW84UAx', ); /** 0x00006f357c6a0020820464ddfac1bec070cc14a8daf04129871d458f2ca94368aae8391311af6361696670733a2f2f516d597231564a4c776572673670456f73636468564775676f3339706136727963455a4c6a7452504466573834554178 @@ -2178,7 +2178,7 @@ verification: { data: '820464ddfac1bec070cc14a8daf04129871d458f2ca94368aae8391311af6361', method: 'keccak256(utf8)', } -url: 'ifps://QmYr1VJLwerg6pEoscdhVGugo39pa6rycEZLjtRPDfW84UAx' +url: 'ipfs://QmYr1VJLwerg6pEoscdhVGugo39pa6rycEZLjtRPDfW84UAx' */ ``` diff --git a/docs/tools/dapps/lsp-utils/LSP4DigitalAssetMetadata.md b/docs/tools/dapps/lsp-utils/LSP4DigitalAssetMetadata.md index 0dd19811c1..bb363edf13 100644 --- a/docs/tools/dapps/lsp-utils/LSP4DigitalAssetMetadata.md +++ b/docs/tools/dapps/lsp-utils/LSP4DigitalAssetMetadata.md @@ -13,7 +13,7 @@ Add LSP4 Creators to the digital asset contract that supports ERC725Y. | Name | Type | Description | | :------------- | :----------------------- | :----------------------------------------------------------------------------------- | | `digitalAsset` | `BytesLike` \| `ERC725Y` | - | -| `newCreators` | `Issuer`[] | An array of creators which specifies the address and interface id of each creatotor. | +| `newCreators` | `Issuer`[] | An array of creators which specifies the address and interface id of each creator. | | `signer?` | `Signer` \| `Wallet` | The signer that will send the transaction. | #### Returns diff --git a/docs/tools/dapps/lsp-utils/LSP6KeyManager.md b/docs/tools/dapps/lsp-utils/LSP6KeyManager.md index 9c73ef08fa..15b52bd1a9 100644 --- a/docs/tools/dapps/lsp-utils/LSP6KeyManager.md +++ b/docs/tools/dapps/lsp-utils/LSP6KeyManager.md @@ -308,7 +308,7 @@ v0.0.1 **`Throws`** - When one of `dataKeys[index]` is not hex. -- When one of `dataKeys[index]` has a length of 0 bytes or bigger thsn 32 bytes. +- When one of `dataKeys[index]` has a length of 0 bytes or bigger than 32 bytes. **`See`** diff --git a/docs/tools/integrations.md b/docs/tools/integrations.md index 75bdfb158c..3e2993b014 100644 --- a/docs/tools/integrations.md +++ b/docs/tools/integrations.md @@ -176,7 +176,7 @@ All the RPC URLs are listed under the [**Networks**](../networks/mainnet/paramet - Cookbook provides bundled smart contract libraries that can be directly used within Visual Studio Code, Foundry, Harthat, or Remix. Their webpage also features a ChatGPT integration to help learn and deploy LSPs. + Cookbook provides bundled smart contract libraries that can be directly used within Visual Studio Code, Foundry, Hardhat, or Remix. Their webpage also features a ChatGPT integration to help learn and deploy LSPs.