Skip to content

Commit

Permalink
updates endpoints for IOTA Mainnet (#1208)
Browse files Browse the repository at this point in the history
  • Loading branch information
@luca-moser
luca-moser authored Oct 3, 2023
1 parent d3f61dc commit fba5377
Show file tree
Hide file tree
Showing 4 changed files with 64 additions and 56 deletions.
99 changes: 51 additions & 48 deletions docs/build/getting-started/networks-endpoints.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -19,39 +19,38 @@ import { AddToMetaMaskButton, EVMNetworks } from '@theme/AddToMetaMaskButton';

This pages gives an overview around the different networks available in the IOTA ecosystem.

:::info
In general, all endpoints are load balanced but are also subject to rate limiting.
If you are developing a production level application for IOTA, consider setting up your own infrastructure in order to
have more control and to not run into any limits.
:::

## IOTA Mainnet

[The IOTA Mainnet](https://explorer.iota.org/mainnet) is the production network within the IOTA ecosystem using the IOTA
token.

<table>
<table style={{ wordBreak: 'break-all', verticalAlign: 'middle' }}>
<tbody>
<tr>
<th>Base Token</th>
<th>Protocol</th>
<th style={{ width: '150px' }}>Base Token</th>
<th style={{ width: '100px' }}>Protocol</th>
<th>HTTP REST API</th>
<th>Event API</th>
<th>Permanode API</th>
<th>Faucet</th>
</tr>
<tr>
<td>IOTA Token</td>
<td>
<a href='/learn/protocols/chrysalis/introduction/'>Chrysalis</a>
<td style={{ textAlign: 'center' }}>IOTA Token</td>
<td style={{ textAlign: 'center' }}>
<a href='/learn/protocols/stardust/introduction/'>Stardust</a>
</td>
<td>
<a href='https://chrysalis-nodes.iota.org/api/v1/info'>
https://chrysalis-nodes.iota.org
<a href='https://api.stardust-mainnet.iotaledger.net/api/v2/info'>
https://api.stardust-mainnet.iotaledger.net
</a>
, <a href='https://chrysalis-nodes.iota.cafe/api/v1/info'>https://chrysalis-nodes.iota.cafe</a>
</td>
<td>wss://chrysalis-nodes.iota.org:443 (MQTT 3.1, /mqtt)</td>
<td>N/A</td>
<td>N/A</td>
<td>wss://api.stardust-mainnet.iotaledger.net:443 (MQTT 3.1, /mqtt)</td>
<td>https://chronicle.stardust-mainnet.iotaledger.net</td>
</tr>
</tbody>
</table>
Expand All @@ -61,18 +60,18 @@ token.
[Shimmer](https://explorer.iota.org/shimmer) is the staging network for new protocol versions before they hit IOTA
Mainnet.

<table>
<table style={{ wordBreak: 'break-all', verticalAlign: 'middle' }}>
<tbody>
<tr>
<th>Base Token</th>
<th>Protocol</th>
<th style={{ width: '150px' }}>Base Token</th>
<th style={{ width: '100px' }}>Protocol</th>
<th>HTTP REST API</th>
<th>Event API</th>
<th>Permanode API</th>
</tr>
<tr>
<td>Shimmer Token</td>
<td>
<td style={{ textAlign: 'center' }}>Shimmer Token</td>
<td style={{ textAlign: 'center' }}>
<a href='/learn/protocols/stardust/introduction/'>Stardust</a>
</td>
<td>
Expand All @@ -92,24 +91,24 @@ Mainnet.

<AddToMetaMaskButton cfg={EVMNetworks['shimmerevm']} />

<table>
<table style={{ wordBreak: 'break-all', verticalAlign: 'middle' }}>
<tbody>
<tr>
<th>Base Token</th>
<th>Protocol</th>
<th style={{ width: '150px' }}>Base Token</th>
<th style={{ width: '120px' }}>Protocol</th>
<th style={{ width: '100px' }}>Chain ID</th>
<th>RPC URL</th>
<th>Chain ID</th>
<th>Explorer</th>
</tr>
<tr>
<td>Shimmer Token</td>
<td>ISC / EVM</td>
<td style={{ textAlign: 'center' }}>Shimmer Token</td>
<td style={{ textAlign: 'center' }}>ISC / EVM</td>
<td style={{ textAlign: 'center' }}>148</td>
<td>
<a href='https://json-rpc.evm.shimmer.network'>
https://json-rpc.evm.shimmer.network
</a>
</td>
<td>148</td>
<td>
<a href='https://explorer.evm.shimmer.network'>
https://explorer.evm.shimmer.network
Expand All @@ -123,19 +122,19 @@ Mainnet.

[The Public Testnet](https://explorer.iota.org/testnet) acts as a test bed for builders without any real world value.

<table>
<table style={{ wordBreak: 'break-all', verticalAlign: 'middle' }}>
<tbody>
<tr>
<th>Base Token</th>
<th>Protocol</th>
<th>HTTP REST API</th>
<th style={{ width: '150px' }}>Base Token</th>
<th style={{ width: '100px' }}>Protocol</th>
<th style={{ width: '200px' }}>HTTP REST API</th>
<th>Event API</th>
<th>Permanode API</th>
<th>Faucet</th>
</tr>
<tr>
<td>Testnet Tokens (no value)</td>
<td>
<td style={{ textAlign: 'center' }}>Testnet Tokens (no value)</td>
<td style={{ textAlign: 'center' }}>
<a href='/learn/protocols/stardust/introduction/'>Stardust</a>
</td>
<td>
Expand Down Expand Up @@ -163,25 +162,25 @@ of the Public Testnet. This network does not run
any IOTA protocol but instead uses ISC to facilitate an Ethereum Virtual Machine and has an enshrined bridge from to
layer 1.

<table>
<table style={{ wordBreak: 'break-all', verticalAlign: 'middle' }}>
<tbody>
<tr>
<th>Base Token</th>
<th>Protocol</th>
<th style={{ width: '150px' }}>Base Token</th>
<th style={{ width: '150px' }}>Protocol</th>
<th style={{ width: '100px' }}>Chain ID</th>
<th>RPC URL</th>
<th>Chain ID</th>
<th>Faucet</th>
<th>Explorer</th>
</tr>
<tr>
<td>Testnet Tokens (no value)</td>
<td>ISC / EVM</td>
<td>1072</td>
<td>
<a href='https://json-rpc.evm.testnet.shimmer.network'>
https://json-rpc.evm.testnet.shimmer.network
</a>
</td>
<td>1072</td>
<td>
<a href='https://evm-faucet.testnet.shimmer.network'>
https://evm-faucet.testnet.shimmer.network
Expand All @@ -198,22 +197,26 @@ layer 1.

## DevNet

[The DevNet](https://explorer.iota.org/legacy-mainnet) is a legacy network running the Chrysalis protocol and is to be
decommissioned once IOTA Mainnet runs under Stardust.
:::caution
This network is going to be decommissioned by the end of 2023,
consider building on the Public Testnet instead.
:::

<table>
[The DevNet](https://explorer.iota.org/legacy-mainnet) is a legacy network running the Chrysalis protocol.

<table style={{ wordBreak: 'break-all', verticalAlign: 'middle' }}>
<tbody>
<tr>
<th>Base Token</th>
<th>Protocol</th>
<th style={{ width: '150px' }}>Base Token</th>
<th style={{ width: '100px' }}>Protocol</th>
<th>HTTP REST API</th>
<th>Event API</th>
<th>Permanode API</th>
<th>Faucet</th>
</tr>
<tr>
<td>Testnet Tokens (no value)</td>
<td>
<td style={{ textAlign: 'center' }}>Testnet Tokens (no value)</td>
<td style={{ textAlign: 'center' }}>
<a href='/learn/protocols/chrysalis/introduction/'>Chrysalis</a>
</td>
<td>
Expand All @@ -235,13 +238,13 @@ decommissioned once IOTA Mainnet runs under Stardust.

## Legacy

The legacy IOTA Mainnet still running for the sole purpose to facilitate token migrations into the IOTA Mainnet.
See following [page](https://chrysalis.iota.org/status) for a status on the token migration.

:::info Migration Only
The legacy IOTA Mainnet only allows the creation of migration transactions and can only be used via FireFly.
:::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.

<table>
<tbody>
<tr>
Expand Down
5 changes: 5 additions & 0 deletions ...ild/introduction-docs/chrysalis/docs/explanations/update/migration_mechanism.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,11 @@ keywords:

# How the IOTA Chrysalis Phase 2 Token Migration Works

:::caution
Since the launch of the Stardust protocol on the IOTA Mainnet, this mechanism is no longer applied, instead
the migrations will be facilitated through an L2 solution.
:::

For the Chrysalis Phase 2 transition, the IOTA Foundation developed a way to migrate funds to the new network. IOTA created this new mechanism because the previous network did not support the WOTS addresses.

Before proceeding into the developed mechanism, below is our reasoning for why other mechanisms were not chosen:
Expand Down
2 changes: 1 addition & 1 deletion docs/get-started/introduction/iota/iota-token.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ the more common denominations used in the DLT space.
On the 4th of October 2023, the IOTA Mainnet was upgraded to run under the Stardust protocol. With the upgrade, a
change in the supply was also executed, where the initial supply of ~2,779,530,283 IOTAs (2,779,530,283,277,761 micros, to be precise) was
increased to 4,600,000,000 IOTAs (4,600,000,000,000,000 micros), where the additional new supply of
~1,820,469,713 IOTAs were distributed under the following allocations and unlock schedules:
~1,820,469,716 IOTAs were distributed under the following allocations and unlock schedules:

| Allocation | Percentage | # IOTA Tokens | Unlock Schedule |
| ---------------------------- | ---------- | ------------- | ---------------------------------------------------- |
Expand Down
14 changes: 7 additions & 7 deletions docs/learn/protocols/introduction.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,10 @@ keywords: [

This page provides an overview around the different protocol versions within the IOTA ecosystem.

| Name | Release Date | Description | Consensus | Features | Networks |
| ------------------------------------------------------------ | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- |
| Legacy Trinary | 2016 | Based on a [probabilistic consensus algorithm using random walks on a DAG](https://assets.ctfassets.net/r1dr6vzfxhev/2t4uxvsIqk0EUau6g2sw0g/45eae33637ca92f85dd9f4a3a218e1ec/iota1_4_3.pdf), the original version of the IOTA protocol | [PoA - Coordinator](/learn/protocols/coordinator) | Bundles, trinary | - |
| [Chrysalis Phase 1](/learn/protocols/chrysalis/introduction) | August 2020 (IOTA Mainnet) | Replaced the heavy probabilistic consensus algorithm to use the [White-Flag approach](/learn/protocols/chrysalis/core-concepts/white-flag-consensus) instead | [PoA - Coordinator](/learn/protocols/coordinator) | White-Flag Confirmation | [Legacy IOTA Mainnet](/build/networks-endpoints#legacy) |
| [Chrysalis Phase 2](/learn/protocols/chrysalis/introduction) | April 2021 (IOTA Mainnet) | Switched from trinary to binary for data representation, changed from an account model to UTXO, removed Winternitz One Time Signatures (WOTS) and introduced EdDSA, dust protection and a complete overhaul of all APIs | [PoA - Coordinator](/learn/protocols/coordinator) | Binary, EdDSA, UTXO, Removal of WOTS | [IOTA Mainnet](/build/networks-endpoints#iota-mainnet), [DevNet](/build/networks-endpoints#devnet) |
| [Stardust](/learn/protocols/stardust/introduction) | September 2022 (Shimmer) | Upgraded the ledger to support multiple assets instead of just the base token, switched the dust protection to a more granular one based on exact byte costs, renamed vertices from "messages" to "blocks", introduced concepts such as `FoundryOutput`, `AliasOutput` and `NFTOutput`. Also added the foundation for ISC anchoring via `AliasOutput`s. | [PoA - Coordinator](/learn/protocols/coordinator) | Multi-Asset Ledger, ISC support, Byte Cost Based Dust Protection, Blocks as vertices, Bech32 addresses | [Shimmer](/build/networks-endpoints#shimmer), [Public Testnet](/build/networks-endpoints#public-testnet) |
| IOTA 2.0 | - | The upcoming version of IOTA running under a PoS scheme with a leaderless consensus algorithm called On-Tangle-Voting. Introduces the concept of mana, which is a resource used to pay for network utilisation. | PoS - OTV | Mana, Staking, PoS, AccountOutput, ICCA | - |
| Name | Release Date | Description | Consensus | Features | Networks |
| ------------------------------------------------------------ | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Legacy Trinary | 2016 | Based on a [probabilistic consensus algorithm using random walks on a DAG](https://assets.ctfassets.net/r1dr6vzfxhev/2t4uxvsIqk0EUau6g2sw0g/45eae33637ca92f85dd9f4a3a218e1ec/iota1_4_3.pdf), the original version of the IOTA protocol | [PoA - Coordinator](/learn/protocols/coordinator) | Bundles, trinary | - |
| [Chrysalis Phase 1](/learn/protocols/chrysalis/introduction) | August 2020 (IOTA Mainnet) | Replaced the heavy probabilistic consensus algorithm to use the [White-Flag approach](/learn/protocols/chrysalis/core-concepts/white-flag-consensus) instead | [PoA - Coordinator](/learn/protocols/coordinator) | White-Flag Confirmation | [Legacy IOTA Mainnet](/build/networks-endpoints#legacy) |
| [Chrysalis Phase 2](/learn/protocols/chrysalis/introduction) | April 2021 (IOTA Mainnet) | Switched from trinary to binary for data representation, changed from an account model to UTXO, removed Winternitz One Time Signatures (WOTS) and introduced EdDSA, dust protection and a complete overhaul of all APIs | [PoA - Coordinator](/learn/protocols/coordinator) | Binary, EdDSA, UTXO, Removal of WOTS | [DevNet](/build/networks-endpoints#devnet) |
| [Stardust](/learn/protocols/stardust/introduction) | September 2022 (Shimmer), October 2023 (IOTA Mainnet) | Upgraded the ledger to support multiple assets instead of just the base token, switched the dust protection to a more granular one based on exact byte costs, renamed vertices from "messages" to "blocks", introduced concepts such as `FoundryOutput`, `AliasOutput` and `NFTOutput`. Also added the foundation for ISC anchoring via `AliasOutput`s. | [PoA - Coordinator](/learn/protocols/coordinator) | Multi-Asset Ledger, ISC support, Byte Cost Based Dust Protection, Blocks as vertices, Bech32 addresses | [IOTA Mainnet](/build/networks-endpoints#iota-mainnet), [Shimmer](/build/networks-endpoints#shimmer), [Public Testnet](/build/networks-endpoints#public-testnet) |
| IOTA 2.0 | - | The upcoming version of IOTA running under a dPoS scheme with a leaderless consensus algorithm called On-Tangle-Voting. Introduces the concept of mana, which is a resource used to pay for network utilisation. | PoS - OTV | Mana, Staking, PoS, AccountOutput, ICCA | - |

0 comments on commit fba5377

Please sign in to comment.