Add version 1.6

Author: Dr-Electron

config/versionedConfig.js

@@ -33,6 +33,10 @@ exports.buildPluginsConfig = [
         label: 'v1.5',
         badges: ['Testnet'],
       },
+      {
+        label: 'v1.6',
+        badges: ['IOTA', 'Shimmer'],
+      },
     ],
   },
   {
@@ -150,6 +154,10 @@ exports.maintainPluginsConfig = [
         label: 'v1.5',
         badges: ['Testnet'],
       },
+      {
+        label: 'v1.6',
+        badges: ['IOTA', 'Shimmer'],
+      },
     ],
   },
   {

docs/build/isc/v1.6/docs/_admonitions/_AgentID.md

@@ -0,0 +1,5 @@
+:::info ISC Agent ID
+
+The `ISCAgentID` represents the identifier of the agent (user or contract) whose NFTs you want to retrieve. You can get the [`AgentID`](../explanations/how-accounts-work.md) from the sender by calling `ISC.sandbox.getSenderAccount()`.
+
+:::

docs/build/isc/v1.6/docs/_admonitions/_ERC721.md

@@ -0,0 +1,5 @@
+:::info ERC721
+
+As your L1 NFT is always registered as [ERC721](https://eips.ethereum.org/EIPS/eip-721), you might want to get the metadata like `tokenURI` from there. Using `getIRC27NFTData` is normally only needed if you need special [IRC27](https://wiki.iota.org/tips/tips/TIP-0027/) metadata.
+
+:::

docs/build/isc/v1.6/docs/_admonitions/_EVM-required-prior-knowledge.md

@@ -0,0 +1,14 @@
+:::note Required Prior Knowledge
+
+This guide assumes you are familiar with the concept
+of [tokens](https://en.wikipedia.org/wiki/Cryptocurrency#Crypto_token)
+in [blockchain](https://en.wikipedia.org/wiki/Blockchain),
+[Ethereum Request for Comments (ERCs)](https://eips.ethereum.org/erc)(also known as Ethereum Improvement Proposals (
+EIP))
+, [NFTs](/learn/protocols/stardust/core-concepts/multi-asset-ledger#non-fungible-tokens-nfts), [Smart Contracts](/learn/smart-contracts/introduction)
+and have already tinkered with [Solidity](https://docs.soliditylang.org/en/v0.8.16/).
+
+You should also have basic knowledge on how to [create](../how-tos/create-a-basic-contract.md) and [deploy](../how-tos/deploy-a-smart-contract.mdx)
+a smart contract.
+
+:::

docs/build/isc/v1.6/docs/_admonitions/_EVM_compatibility.md

@@ -0,0 +1,7 @@
+:::info EVM Compatibility
+
+The ISC EVM layer is also designed to be as compatible as possible with existing Ethereum
+[tools](../getting-started/tools.mdx) and functionalities. However, please make sure you have checked out the current
+[properties and limitations](../getting-started/compatibility.mdx).
+
+:::

docs/build/isc/v1.6/docs/_admonitions/_IRC27.md

@@ -0,0 +1,5 @@
+:::info IRC27NFTMetadata URI
+
+The uri property contains a JSON object which follows the `ERC721` standard. This JSON is also returned by the [`tokenURI`](../reference/magic-contract/ERC721NFTs.md#tokenuri) function from the `ERC721NFTs` contract.
+
+:::

docs/build/isc/v1.6/docs/_admonitions/_about-accounts.md

@@ -0,0 +1,5 @@
+:::info Accounts in ISC
+
+Learn more about the [different types of accounts](../explanations/how-accounts-work.md).
+
+:::

docs/build/isc/v1.6/docs/_admonitions/_create-native-token.md

@@ -0,0 +1,5 @@
+:::tip Create a Native Token 
+
+Create your first native token by following our how to [Create a Native Token Guide](../how-tos/core-contracts/token/create-native-token.md/).
+
+:::

docs/build/isc/v1.6/docs/_admonitions/_deploy_a_smart_contract.md

@@ -0,0 +1,5 @@
+:::tip Deploy a Smart Contract 
+
+Deploy a Solidity Smart Contract following our [how to Deploy a Smart Contract guide](/isc/how-tos/deploy-a-smart-contract#remix).
+
+:::

docs/build/isc/v1.6/docs/_admonitions/_ownership.md

@@ -0,0 +1,7 @@
+:::info Ownership
+
+You might want to look into making the function ownable with, for example,
+[OpenZeppelin](https://docs.openzeppelin.com/contracts/5.x/access-control#ownership-and-ownable)
+so only owners of the contract can call certain functionalities of your contract.
+
+:::