Such a mess. So much blood

.github/_CODEOWNERS

@@ -1,15 +1,9 @@
-# clients
-**/iota.rs @thibault-martinez
-**/wallet.rs @thibault-martinez
+# sdk
 **/iota-sdk @thibault-martinez
-**/iota.js @thibault-martinez
 
 # chronicle
 **/chronicle @Alexandcoats
 
-# goshimmer
-**/goshimmer @karimodm
-
 # hornet and inx plugins
 **/hornet @muXxer
 **/inx-api-core-v0 @alexsporn
@@ -30,8 +24,5 @@
 # protocol - introduction-docs
 **/introduction-docs @luca-moser
 
-# research
-**/iota-2.0-research-specifications @darcy-camargo
-
 # WASP - ISC
 **/wasp @fijter

articleRedirects.js

@@ -123,7 +123,7 @@ exports.articleRedirects = [
   },
   {
     from: '/learn/about-iota/energy-efficiency',
-    to: '/learn/protocols/chrysalis/introduction',
+    to: '/learn/protocols/stardust/introduction',
   },
   {
     from: '/learn/about-iota/messages',

docs/build/apis/sidebars.js

@@ -37,17 +37,11 @@ const categories = [
       type: 'generated-index',
       title: 'Core API',
       description:
-        'The core API is the main API for interacting with the Tangle. V1 is meant for the IOTA network and V2 for the Shimmer staging network.',
+        'The core API is the main API for interacting with the Tangle. V2 is now used for both IOTA and the Shimmer staging network.',
       slug: '/api/core',
     },
     collapsed: true,
     items: [
-      {
-        type: 'category',
-        label: 'V1',
-        collapsed: true,
-        items: './docs/core/v1/sidebar',
-      },
       {
         type: 'category',
         label: 'V2',

docs/build/getting-started/networks-endpoints.mdx

@@ -3,7 +3,6 @@ description: Networks and endpoints in the IOTA ecosystem.
 keywords:
   - mainnet
   - shimmer
-  - devnet
   - public testnet
   - MQTT
   - REST API
@@ -88,29 +87,3 @@ This network is subject to occasional resets (no data retention) which are usual
 | Base Token                | Protocol  | Chain ID | RPC URL                                      | Faucet                                     | Explorer                                     |
 | ------------------------- | --------- | -------- | -------------------------------------------- | ------------------------------------------ | -------------------------------------------- |
 | Testnet Tokens (no value) | ISC / EVM | <ChainId url='https://json-rpc.evm.testnet.shimmer.network'/> | https://json-rpc.evm.testnet.shimmer.network | https://evm-faucet.testnet.shimmer.network | https://explorer.evm.testnet.shimmer.network |
-
-## DevNet
-
-:::caution
-This network is going to be decommissioned by the end of 2023,
-consider building on the Public Testnet instead.
-:::
-
-[The DevNet](https://explorer.iota.org/legacy-mainnet) is a legacy network running the Chrysalis protocol.
-
-| Base Token                | Protocol  | HTTP REST API                                                                                         | Event API                                                         | Permanode API                             | Faucet                                 |
-| ------------------------- | --------- | ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | ----------------------------------------- | -------------------------------------- |
-| Testnet Tokens (no value) | Chrysalis | https://api.lb-0.h.chrysalis-devnet.iota.cafe , https://api.lb-1.h.chrysalis-devnet.iota.cafe | wss://api.lb-0.h.chrysalis-devnet.iota.cafe:443 (MQTT 3.1, /mqtt) | https://chronicle.testnet.shimmer.network | https://faucet.testnet.shimmer.network |
-
-## Legacy
-
-:::caution
-With the upgrade of the IOTA Mainnet to the Stardust protocol, migrations have been stopped and will re-commence
-once a new mechanism via an L2 chain is set up.
-:::
-
-The legacy IOTA Mainnet was running for the sole purpose to facilitate token migrations into the IOTA Mainnet.
-
-| Base Token              | Protocol                | HTTP REST API                     |
-| ----------------------- | ----------------------- | --------------------------------- |
-| IOTA Token (Unmigrated) | Legacy Trinary Protocol | https://api-legacy.iotaledger.net |

docs/build/identity.rs/1.0/docs/explanations/about-alias-outputs.mdx

@@ -26,7 +26,7 @@ and which can be transferred through transactions to update DID Documents.
 :::
 
 
-The IOTA DID method uses the IOTA ledger, which is baed on the [unspent transaction output (_UTXO_) model](/learn/protocols/chrysalis/core-concepts/switch-to-UTXO/),
+The IOTA DID method uses the IOTA ledger, which is baed on the unspent transaction output (_UTXO_) model,
 as well as the features of the [Stardust](/introduction/stardust/explanations/what_is_stardust) upgrade,
 which are fundamental to the IOTA DID method.
 
@@ -38,7 +38,7 @@ A state controller can execute a state transition which allows updating the data
 
 The governor, on the contrary, can't update the `State Metadata` but can change both controllers and destroy the Alias Output.
 
-A controller can be either [Ed25519 Address](/learn/protocols/chrysalis/core-concepts/switch-to-UTXO/), [Alias Address or an _NFT_ Address](/learn/protocols/stardust/core-concepts/multi-asset-ledger/)
+A controller can be either Ed25519 Address, [Alias Address or an _NFT_ Address](/learn/protocols/stardust/core-concepts/multi-asset-ledger/)
 and at most one of each can be set for an Alias Output.
 
 In order to create a new Alias Output, a transaction must be made that includes another Output, for example,

docs/build/identity.rs/1.0/docs/how-tos/decentralized-identifiers/create.mdx

@@ -96,7 +96,7 @@ https://github.com/iotaledger/identity.rs/blob/main/bindings/wasm/examples/src/0
 Next, you need to construct a new [Alias Output](../../explanations/about-alias-outputs.mdx) that includes the
 DID Document in the [State Metadata](../../explanations/about-alias-outputs.mdx).
 The created Alias Output contains an encoded version of the DID Document in its `State Metadata`, and has the state
-controller and the governor set to the generated [Ed25519](/learn/protocols/chrysalis/core-concepts/EdDSA-support/) address.
+controller and the governor set to the generated Ed25519 address.
 
 Note that controllers don't need to be Ed25519 addresses, they can be any type of output.
 However, they must be unlocked in order perform a state or governance transition when the DID Document is updated or destroyed.

docs/build/identity.rs/1.0/docs/references/specifications/iota-did-method-spec.mdx

@@ -18,7 +18,7 @@ keywords:
 
 ## Abstract
 
-The IOTA DID Method Specification describes a method of implementing the [Decentralized Identifiers](https://www.w3.org/TR/did-core/) (DID) standard on [IOTA](https://iota.org), a Distributed Ledger Technology (DLT). It conforms to the [DID specification v1.0](https://www.w3.org/TR/did-core/) and describes how to perform Create, Read, Update and Delete (CRUD) operations for IOTA DID Documents using unspent transaction outputs ([_UTXO_](/introduction/reference/details#unspent-transaction-output-utxo)) on the IOTA and [Shimmer](https://shimmer.network/) networks, introduced with the [Stardust upgrade](https://blog.shimmer.network/stardust-upgrade-in-a-nutshell/).
+The IOTA DID Method Specification describes a method of implementing the [Decentralized Identifiers](https://www.w3.org/TR/did-core/) (DID) standard on [IOTA](https://iota.org), a Distributed Ledger Technology (DLT). It conforms to the [DID specification v1.0](https://www.w3.org/TR/did-core/) and describes how to perform Create, Read, Update and Delete (CRUD) operations for IOTA DID Documents using unspent transaction outputs (_UTXO_) on the IOTA and [Shimmer](https://shimmer.network/) networks, introduced with the [Stardust upgrade](https://blog.shimmer.network/stardust-upgrade-in-a-nutshell/).
 
 ## Data Types & Subschema Notation
 

docs/build/introduction-docs/stardust/docs/explanations/libraries/overview.md

@@ -24,12 +24,11 @@ The IOTA client libraries have been deprecated and replaced by the [IOTA SDK](/i
 
 The official IOTA libraries serve as `one-source-code-of-truth` to IOTA users and provide binding to other programming languages. Below is a list of the IOTA libraries. You can also check out the [IOTA client libraries blog post](https://blog.iota.org/the-new-iota-client-libraries-harder-better-faster-stronger/), to learn about the libraries' core principles.
 
-- [IOTA SDK](/iota-sdk/welcome): The IOTA SDK replaces `iota.rs`, `iota.js` and `wallet.rs` with a convenient development kit, written
+- [IOTA SDK](/iota-sdk/welcome): A convenient development kit, written
   in [Rust](/iota-sdk/getting-started/rust), with bindings for
   [Node.js](/iota-sdk/getting-started/nodejs),
   [Python](/iota-sdk/getting-started/python), and [Wasm](/iota-sdk/getting-started/wasm).
 - [iota.go](https://github.com/iotaledger/iota.go/tree/v3): an IOTA client library in Golang.
-- [iota.c](https://github.com/iotaledger/iota.c/tree/develop): a special-purpose library in C for embedded devices (with microcontrollers) covering a basic features of `client-lib` or `wallet-lib.`
 
 <div class="iframe-wrapper">
 <iframe src="https://www.youtube.com/embed/N2VW3zJQmso" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

docs/build/introduction-docs/stardust/docs/welcome.md

@@ -9,7 +9,7 @@ image: /img/logo/preview.png
 
 # Welcome
 
-Stardust protocol is the successor to IOTA 1.5, also known as [Chrysalis](/introduction/welcome), that transforms IOTA into a multi-asset ledger and enables the operation of [IOTA Smart Contracts](/learn/smart-contracts/introduction/). This page outlines the new concepts
+Stardust protocol is the successor to IOTA 1.5, also known as _Chrysalis_, that transforms IOTA into a multi-asset ledger and enables the operation of [IOTA Smart Contracts](/learn/smart-contracts/introduction/). This page outlines the new concepts
 and differences compared to Chrysalis, furthermore gives an overview of different components of the IOTA technology stack.
 
 Stardust debuts on [Shimmer](https://shimmer.network/), the new staging network for IOTA, before being fully supported on the IOTA Mainnet.

docs/build/introduction-docs/stardust/sidebars.js

@@ -110,16 +110,6 @@ module.exports = {
               id: 'explanations/libraries/overview',
               label: 'Overview',
             },
-            {
-              type: 'doc',
-              id: 'explanations/libraries/client',
-              label: 'Client Lib',
-            },
-            {
-              type: 'doc',
-              id: 'explanations/libraries/wallet',
-              label: 'Wallet Lib',
-            },
           ],
         },
         {

docs/build/iota-sdk/1.0/docs/_admonitions/_warning-password-storage.md

@@ -1,7 +1,7 @@
 :::warning Safe Password Storage
 
 In a production setup, do not store passwords in the host's environment variables or in the source code. See
-our [backup and security recommendations](/introduction/how_tos/backup_security) for
+our [backup and security recommendations](/introduction/stardust/how_tos/backup_security) for
 production setups.
 
 :::

docs/build/iota-sdk/1.0/docs/how-tos/exchange-guide.mdx

@@ -78,16 +78,16 @@ Most of the APIs are the same and the changes are fairly minimal, here are some
 
 - The npm package changes from [`@iota/wallet`](https://www.npmjs.com/package/@iota/wallet) to
   [`@iota/sdk`](https://www.npmjs.com/package/@iota/sdk).
-- [`AccountManager`](/wallet.rs/1.0-rc.6/references/nodejs/classes/AccountManager)
+- `AccountManager`
   becomes
   [`Wallet`](../references/nodejs/classes/Wallet.md).
-- [`manager.generateMnemonic()`](/wallet.rs/1.0-rc.6/references/nodejs/classes/AccountManager#generatemnemonic)
+- `manager.generateMnemonic()`
   becomes
   [`Utils.generateMnemonic()`](../references/nodejs/classes/Utils.md#generatemnemonic).
-- [`AccountManager.generateAddress`](/wallet.rs/1.0-rc.6/references/nodejs/classes/AccountManager#generateaddress)
+- `AccountManager.generateAddress`
   becomes
   [`Wallet.generateEd25519Addresses`](../references/nodejs/classes/Wallet.md#generateed25519address).
-- [`Account.sendAmount`](/wallet.rs/1.0-rc.6/references/nodejs/classes/Account) becomes
+- `Account.sendAmount` becomes
   [`send`](../references/nodejs/classes/Account.md#send).
 - The callbacks to `listen` now provide a properly typed
   [`Event`](../references/nodejs/classes/Event.md).
@@ -96,13 +96,13 @@ Most of the APIs are the same and the changes are fairly minimal, here are some
 <TabItem value="python" label="Python">
 
 - The pip package changes from `iota-wallet` to [`iota-sdk`](https://pypi.org/project/iota-sdk.md).
-- [`wallet.generate_mnemonic()`](/wallet.rs/1.0-rc.6/references/python/iota_wallet/wallet#generate_mnemonic)
+- `wallet.generate_mnemonic()`
   becomes
   [`utils.generate_mnemonic()`](../references/python/iota_sdk/utils.md#generate_mnemonic).
-- [`wallet.generate_address()`](/wallet.rs/1.0-rc.6/references/python/iota_wallet/wallet#generate_address)
+- `wallet.generate_address()`
   becomes
   [`wallet.generate_ed25519_addresses()`](../references/python/iota_sdk/wallet/wallet.md#generate_ed25519_address).
-- [`account.send_amount`](/wallet.rs/1.0-rc.6/references/python/iota_wallet/account#send_amount)
+- `account.send_amount`
   becomes
   [`account.send`](../references/python/iota_sdk/wallet/account.md#send).
 - The callbacks to `listen` now provide a properly typed
@@ -120,7 +120,7 @@ Most of the APIs are the same and the changes are fairly minimal, here are some
 First, you should install the components needed to use the IOTA SDK and the binding of your choice; it may vary a bit
 from language to language.
 
-You can read more about [backup and security in this guide](/introduction/how_tos/backup_security).
+You can read more about [backup and security in this guide](/introduction/stardust/how_tos/backup_security).
 
 <Tabs groupId="language" queryString>