From 5474fadffd051445ff49c796804e0434d263db17 Mon Sep 17 00:00:00 2001 From: Hugo Masclet Date: Fri, 10 Nov 2023 08:58:37 +0100 Subject: [PATCH] docs: update links --- docs/classes/lsp7-digital-asset.md | 2 +- docs/classes/lsp8-identifiable-digital-asset.md | 2 +- docs/deployment/digital-asset.md | 12 ++++++------ docs/deployment/universal-profile.md | 2 +- 4 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/classes/lsp7-digital-asset.md b/docs/classes/lsp7-digital-asset.md index 206da7e0..1bf37b0f 100644 --- a/docs/classes/lsp7-digital-asset.md +++ b/docs/classes/lsp7-digital-asset.md @@ -11,7 +11,7 @@ title: LSP7DigitalAsset lspFactory.LSP7DigitalAsset.deploy(digitalAssetProperties [, options]); ``` -Deploys a mintable [LSP7 Digital Asset](../../../standards/nft-2.0/LSP7-Digital-Asset). +Deploys a mintable [LSP7 Digital Asset](../../../standards/tokens/LSP7-Digital-Asset). :::info diff --git a/docs/classes/lsp8-identifiable-digital-asset.md b/docs/classes/lsp8-identifiable-digital-asset.md index 6d050b39..fe33bf5d 100644 --- a/docs/classes/lsp8-identifiable-digital-asset.md +++ b/docs/classes/lsp8-identifiable-digital-asset.md @@ -11,7 +11,7 @@ title: LSP8IdentifiableDigitalAsset lspFactory.LSP8IdentifiableDigitalAsset.deploy(digitalAssetProperties [, options]); ``` -Deploys a mintable [LSP8 Identifiable Digital Asset](../../../standards/nft-2.0/LSP8-Identifiable-Digital-Asset). +Deploys a mintable [LSP8 Identifiable Digital Asset](../../../standards/tokens/LSP8-Identifiable-Digital-Asset). :::info diff --git a/docs/deployment/digital-asset.md b/docs/deployment/digital-asset.md index b14fd76e..c1cf203f 100644 --- a/docs/deployment/digital-asset.md +++ b/docs/deployment/digital-asset.md @@ -113,7 +113,7 @@ Set the address which should own your digital asset contract by passing the `con ### Adding LSP4 Metadata -[LSP7] and [LSP8] both adhere to the [LSP4 Digital Asset Metadata standard](../../../standards/nft-2.0/LSP4-Digital-Asset-Metadata.md). Developers can specify the LSP4Metadata by setting the `name`, `symbol`, `digitalAssetMetadata` and `creators` keys when deploying with LSPFactory. +[LSP7] and [LSP8] both adhere to the [LSP4 Digital Asset Metadata standard](../../../standards/tokens/LSP4-Digital-Asset-Metadata.md). Developers can specify the LSP4Metadata by setting the `name`, `symbol`, `digitalAssetMetadata` and `creators` keys when deploying with LSPFactory. ```javascript await lspFactory.LSP8IdentifiableDigitalAsset.deploy({ @@ -128,9 +128,9 @@ await lspFactory.LSP8IdentifiableDigitalAsset.deploy({ }); ``` -The `name` and `symbol` keys are passed as deployment constructor parameters. These values will set the [`LSP4TokenName`](../../../standards/nft-2.0/LSP4-Digital-Asset-Metadata.md#lsp4tokenname) and [`LSP4TokenSymbol`](../../../standards/nft-2.0/LSP4-Digital-Asset-Metadata.md#lsp4tokensymbol) [ERC725Y] keys directly on the contract during deployment. +The `name` and `symbol` keys are passed as deployment constructor parameters. These values will set the [`LSP4TokenName`](../../../standards/tokens/LSP4-Digital-Asset-Metadata.md#lsp4tokenname) and [`LSP4TokenSymbol`](../../../standards/tokens/LSP4-Digital-Asset-Metadata.md#lsp4tokensymbol) [ERC725Y] keys directly on the contract during deployment. -Addresses passed inside the `creators` array will be set under the [LSP4Creators[]](../../../standards/nft-2.0/LSP4-Digital-Asset-Metadata#lsp4creators) [ERC725Y] key. +Addresses passed inside the `creators` array will be set under the [LSP4Creators[]](../../../standards/tokens/LSP4-Digital-Asset-Metadata#lsp4creators) [ERC725Y] key. :::warning LSPFactory does not set the [LSP3IssuedAssets key](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-3-UniversalProfile-Metadata.md#lsp3issuedassets) on any Universal Profile when deploying a digital asset. This key will have to be updated seperately. @@ -139,7 +139,7 @@ LSPFactory does not set the [LSP3IssuedAssets key](https://github.com/lukso-netw #### Digital Asset Metadata -Further Digital Asset metadata can be added by passing the `digitalAssetMetadata` parameter. This is metadata stored as JSON on a server and referenced from the contract by the [`LSP4Metadata`](../../../standards/nft-2.0/LSP4-Digital-Asset-Metadata.md#lsp4metadata) [ERC725Y] key. +Further Digital Asset metadata can be added by passing the `digitalAssetMetadata` parameter. This is metadata stored as JSON on a server and referenced from the contract by the [`LSP4Metadata`](../../../standards/tokens/LSP4-Digital-Asset-Metadata.md#lsp4metadata) [ERC725Y] key. :::info Info Digital Asset Metadata can be passed as either a JSON object containing the [LSP4Metadata](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-4-DigitalAsset-Metadata.md) you want to upload or a URL of your previously uploaded metadata. @@ -632,7 +632,7 @@ Digital Asset deployment completed ``` -[lsp7]: ../../../standards/nft-2.0/LSP7-Digital-Asset -[lsp8]: ../../../standards/nft-2.0/LSP8-Identifiable-Digital-Asset +[lsp7]: ../../../standards/tokens/LSP7-Digital-Asset +[lsp8]: ../../../standards/tokens/LSP8-Identifiable-Digital-Asset [erc20]: https://eips.ethereum.org/EIPS/eip-20 [erc725y]: ../../../standards/generic-standards/lsp2-json-schema.md diff --git a/docs/deployment/universal-profile.md b/docs/deployment/universal-profile.md index fd9281c2..7b1fe0be 100644 --- a/docs/deployment/universal-profile.md +++ b/docs/deployment/universal-profile.md @@ -39,7 +39,7 @@ Inside the `profileProperties` object, you can set profile configuration options ### Controller Addresses -You can set the addresses which should be able to control your Universal Profile initially by passing in the `controllerAddresses`. The addresses that were passed here will be given all LSP6 KeyManager permissions except `DELEGATECALL` to [prevent accidental misuse](https://solidity-by-example.org/hacks/delegatecall/). If your controller keys require `DELEGATECALL`, you can [change the permission after deployment](../../../guides/key-manager/give-permissions.md). +You can set the addresses which should be able to control your Universal Profile initially by passing in the `controllerAddresses`. The addresses that were passed here will be given all LSP6 KeyManager permissions except `DELEGATECALL` to [prevent accidental misuse](https://solidity-by-example.org/hacks/delegatecall/). If your controller keys require `DELEGATECALL`, you can [change the permission after deployment](../../../learn/expert-guides/key-manager/grant-permissions.md). The property `controllerAddresses` can be filled with addresses of externally owned accounts (EOAs) or another smart contract that can call the `execute(calldata)` function on the KeyManager.