Add private network info to create wiki page
@@ -16,14 +16,7 @@ import create_did_node from "!!raw-loader!../../../../bindings/wasm/examples/src
When someone or something wants to benefit from Self-Sovereign Identity, they must first create a Decentralized Identity. This identity consists of many parts that have different functions. This page will cover both the basics and the details about identity creation and publishing.
-
-## Creating an Identity Using the Account
-
-:::tip Using Replit
-
-Select your programming language of choice and press the green play button to execute the example.
-
-:::
+## Creating an Identity
<CodeSnippet
nodeContent={create_did_node}
@@ -32,13 +25,12 @@ Select your programming language of choice and press the green play button to ex
rustGithubLink = "https://github.com/iotaledger/identity.rs/blob/dev/examples/0_basic/0_create_did.rs"
/>
-This examples creates a new address with funds using the faucet on the testnet. Next, it creates a new DID Document with a verification method. This DID Document is then published in an Alias Output making the DID available in the ledger state and resolvable by any node.
+This examples creates a new address with funds using the faucet on a private network. Next, it creates a new DID Document with a verification method. This DID Document is then published in an Alias Output making the DID available in the ledger state and resolvable by any node.
-Note that using the faucet is only possible on the testnet. Once the Stardust update is released on the Shimmer network or the IOTA network, an output with funds is required to create a new Alias Output that represents a DID.
+Note that using the faucet is only possible on private networks or public testnets. Once the Stardust update is released on the Shimmer network or the IOTA network, an output with actual Shimmer or IOTA funds is required to create a new Alias Output that represents a DID.
Updating the identity is also possible, which will be discussed in the next section, but all previous states of the DID Document will still be stored in permanodes or any third party recording the network activity.
-
### Identity Generation Process
In order to create a Alias Output, an existing output is required to make a transaction. For that a new Address is generated and a Basic Output controlled by this address is created using the faucet.
@@ -50,3 +42,9 @@ An Alias Output is created which contains an encoded version of the DID Document
The byte cost for the document is then automatically calculated and a new transaction is published that includes the Basic Output as input and the newly generated Alias Output as output as well as a Basic Output which contains the remaining IOTA coins.
Once the transaction is confirmed, the `Alias ID` would be assigned and the DID can be derived from it. Now The DID Document is stored on the ledger and can be resolved using any node. See the further examples for [updating](./update) and [resolving](./resolve) DID.
+
+## Running a private network
+
+In order to run the examples, a private network (sometimes also called a private Tangle) needs to run locally. You can refer to [Hornet wiki](https://wiki.iota.org/hornet/develop/how_tos/private_tangle) for instructions on how to run a private network.
+
+If your local private network uses different ports than Hornet, modify the API and faucet endpoints in the examples to match your local setup.
