{leadingElement}
@@ -203,11 +236,16 @@ export function TableCell(props: TableCellProps): JSX.Element {
href={to}
target={isExternal ? '_blank' : '_self'}
rel="noopener noreferrer"
- className={cx('text-primary-30 dark:text-primary-80', textSizeClass)}
+ className={cx('text-primary-30 dark:text-primary-80', textSizeClass, {
+ 'whitespace-nowrap': noWrap,
+ })}
>
{label}
);
+ case TableCellType.Children:
+ const { children } = props;
+ return children;
default:
return null;
}
diff --git a/apps/ui-kit/src/lib/components/molecules/table-cell/table-cell.enums.ts b/apps/ui-kit/src/lib/components/molecules/table-cell/table-cell.enums.ts
index 856dcf3f30e..c89759317d8 100644
--- a/apps/ui-kit/src/lib/components/molecules/table-cell/table-cell.enums.ts
+++ b/apps/ui-kit/src/lib/components/molecules/table-cell/table-cell.enums.ts
@@ -9,4 +9,10 @@ export enum TableCellType {
Checkbox = 'checkbox',
Placeholder = 'placeholder',
Link = 'link',
+ Children = 'children',
+}
+
+export enum TableCellTextColor {
+ Default = 'text-neutral-40 dark:text-neutral-60',
+ Dark = 'text-neutral-10 dark:text-neutral-92',
}
diff --git a/apps/ui-kit/src/lib/components/molecules/table-header-cell/TableHeaderCell.tsx b/apps/ui-kit/src/lib/components/molecules/table-header-cell/TableHeaderCell.tsx
index 722e3235b95..84beb087ecb 100644
--- a/apps/ui-kit/src/lib/components/molecules/table-header-cell/TableHeaderCell.tsx
+++ b/apps/ui-kit/src/lib/components/molecules/table-header-cell/TableHeaderCell.tsx
@@ -105,7 +105,13 @@ export function TableHeaderCell({
onCheckedChange={onCheckboxChange}
/>
) : (
- {label}
+
+ {label}
+
)}
{hasSort && sortOrder === TableHeaderCellSortOrder.Asc && (
diff --git a/apps/ui-kit/src/lib/tailwind/constants/colors.constants.ts b/apps/ui-kit/src/lib/constants/colors.constants.ts
similarity index 100%
rename from apps/ui-kit/src/lib/tailwind/constants/colors.constants.ts
rename to apps/ui-kit/src/lib/constants/colors.constants.ts
diff --git a/apps/ui-kit/src/lib/constants/index.ts b/apps/ui-kit/src/lib/constants/index.ts
new file mode 100644
index 00000000000..8b691fd8ff1
--- /dev/null
+++ b/apps/ui-kit/src/lib/constants/index.ts
@@ -0,0 +1,4 @@
+// Copyright (c) 2024 IOTA Stiftung
+// SPDX-License-Identifier: Apache-2.0
+
+export * from './colors.constants';
diff --git a/apps/ui-kit/src/lib/index.ts b/apps/ui-kit/src/lib/index.ts
index 0e37afefc94..4457ead55fc 100644
--- a/apps/ui-kit/src/lib/index.ts
+++ b/apps/ui-kit/src/lib/index.ts
@@ -3,4 +3,5 @@
export * from './tailwind';
export * from './components';
+export * from './constants';
export * from './enums';
diff --git a/apps/ui-kit/src/lib/tailwind/base.preset.ts b/apps/ui-kit/src/lib/tailwind/base.preset.ts
index 9608070bda8..f7ee5e37a5e 100644
--- a/apps/ui-kit/src/lib/tailwind/base.preset.ts
+++ b/apps/ui-kit/src/lib/tailwind/base.preset.ts
@@ -2,7 +2,7 @@
// SPDX-License-Identifier: Apache-2.0
import { Config } from 'tailwindcss';
-import { IOTA_PRIMITIVES_COLOR_PALETTE, SHADER_COLOR_PALETTE } from './constants/colors.constants';
+import { IOTA_PRIMITIVES_COLOR_PALETTE, SHADER_COLOR_PALETTE } from '../constants/colors.constants';
import {
CUSTOM_FONT_SIZES,
BORDER_RADIUS,
diff --git a/apps/ui-kit/src/lib/tailwind/constants/index.ts b/apps/ui-kit/src/lib/tailwind/constants/index.ts
index a481235f30c..2adc80fcca0 100644
--- a/apps/ui-kit/src/lib/tailwind/constants/index.ts
+++ b/apps/ui-kit/src/lib/tailwind/constants/index.ts
@@ -1,7 +1,6 @@
// Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-export * from './colors.constants';
export * from './scaling.constants';
export * from './fontSizes.constants';
export * from './variable-spacing.constants';
diff --git a/apps/ui-kit/src/storybook/stories/atoms/LabelText.stories.tsx b/apps/ui-kit/src/storybook/stories/atoms/LabelText.stories.tsx
index f94d22039e5..d9c99286cdc 100644
--- a/apps/ui-kit/src/storybook/stories/atoms/LabelText.stories.tsx
+++ b/apps/ui-kit/src/storybook/stories/atoms/LabelText.stories.tsx
@@ -22,7 +22,6 @@ export const Default: Story = {
text: '12,000.00',
label: 'Label',
size: LabelTextSize.Medium,
- showSupportingLabel: true,
supportingLabel: 'IOTA',
isCentered: false,
},
@@ -40,9 +39,6 @@ export const Default: Story = {
supportingLabel: {
control: 'text',
},
- showSupportingLabel: {
- control: 'boolean',
- },
text: {
control: 'text',
},
diff --git a/apps/ui-kit/src/storybook/stories/design-tokens/colors.stories.mdx b/apps/ui-kit/src/storybook/stories/design-tokens/colors.stories.mdx
index 18afbd591fe..94f3f51adaf 100644
--- a/apps/ui-kit/src/storybook/stories/design-tokens/colors.stories.mdx
+++ b/apps/ui-kit/src/storybook/stories/design-tokens/colors.stories.mdx
@@ -2,7 +2,7 @@ import { Meta, ColorPalette, ColorItem } from '@storybook/blocks';
import {
IOTA_PRIMITIVES_COLOR_PALETTE,
SHADER_COLOR_PALETTE,
-} from '../../../lib/tailwind/constants/colors.constants';
+} from '../../../lib/constants/colors.constants';
diff --git a/apps/wallet-dashboard/package.json b/apps/wallet-dashboard/package.json
index 3e79a7a28fa..71591c967e1 100644
--- a/apps/wallet-dashboard/package.json
+++ b/apps/wallet-dashboard/package.json
@@ -21,7 +21,7 @@
"@iota/iota-sdk": "workspace:*",
"@tanstack/react-query": "^5.0.0",
"@tanstack/react-virtual": "^3.5.0",
- "next": "14.2.3",
+ "next": "14.2.10",
"react": "^18.3.1",
"zustand": "^4.4.1"
},
diff --git a/docker/fullnode/README.md b/docker/fullnode/README.md
index 36f03c63b2a..eea6c38606f 100644
--- a/docker/fullnode/README.md
+++ b/docker/fullnode/README.md
@@ -10,21 +10,25 @@ Follow the steps in this Readme to install and configure a Iota Full node for te
- [Install Docker](https://docs.docker.com/get-docker/)
- [Install Docker Compose](https://docs.docker.com/compose/install/)
-- Download the Full node [docker-compose.yaml](https://github.com/iotaledger/iota/blob/main/docker/fullnode/docker-compose.yaml) file.
+- Download the Full node [docker-compose.yaml](https://github.com/iotaledger/iota/blob/develop/docker/fullnode/docker-compose.yaml) file.
## Configure Iota Full node
-Download the latest version of the Iota Full node configuration file [fullnode-template.yaml](https://github.com/iotaledger/iota/raw/main/crates/iota-config/data/fullnode-template.yaml). Use the following command to download the file:
+Download the latest version of the Iota Full node configuration file [fullnode-template.yaml](https://github.com/iotaledger/iota/raw/develop/crates/iota-config/data/fullnode-template.yaml). Use the following command to download the file:
```shell
-wget https://github.com/iotaledger/iota/raw/main/crates/iota-config/data/fullnode-template.yaml
+wget https://github.com/iotaledger/iota/raw/develop/crates/iota-config/data/fullnode-template.yaml
```
+To ensure you add the appropriate peers for your full node, please refer to the instructions provided at the following link:
+https://docs.iota.org/operator/iota-full-node#set-up-from-source and proceed with step 4.
+
### Download the Iota genesis blob
-The genesis blob contains the information that defined the Iota network configuration. Before you can start the Full node, you need to download the most recent file to ensure compatibility with the version of Iota you use. Use the following command to download the [genesis.blob](https://github.com/iotaledger/iota-genesis/raw/main/devnet/genesis.blob) from the `devnet` branch of the Iota repository:
+The genesis blob contains the information that defined the Iota network configuration. Before you can start the Full node, you need to download the most recent file to ensure compatibility with the version of Iota you use.
-`wget https://github.com/iotaledger/iota-genesis/raw/main/devnet/genesis.blob`
+To download the appropriate genesis.blob file, please refer to the instructions provided at the following link:
+https://docs.iota.org/operator/iota-full-node#set-up-from-source. and proceed with step 3.
## Start your Iota Full node
@@ -42,7 +46,7 @@ After the Full node starts you can test the JSON-RPC interfaces.
## View activity on your local Full node with Iota Explorer
-Iota Explorer supports connecting to a local network. To view activity on your local Full node, open the URL: [https://explorer.iota.io/?network=local](https://explorer.iota.io/?network=local).
+Iota Explorer supports connecting to a local network. To view activity on your local Full node, open the URL: [https://explorer.iota.org/?network=local](https://explorer.iota.org/?network=local).
You can also change the network that Iota Explorer connects to by select it in the Iota Explorer interface.
diff --git a/docs/content/about-iota/iota-architecture/iota-architecture.mdx b/docs/content/about-iota/iota-architecture/iota-architecture.mdx
index 6fffb07ff89..540a16fa536 100644
--- a/docs/content/about-iota/iota-architecture/iota-architecture.mdx
+++ b/docs/content/about-iota/iota-architecture/iota-architecture.mdx
@@ -34,7 +34,7 @@ The following diagram describes the architectural structure for IOTA's solution.
The core components are:
-- [Execution Layer](../execution-architecture/execution-layer.mdx)
+- [Execution Layer](../../references/execution-architecture/execution-layer.mdx)
- [IOTA Node](../../operator/iota-full-node.mdx)
- [IOTA RPC](../../references/iota-api)
- [IOTA CLI](../../references/cli)
diff --git a/docs/content/developer/cryptography/on-chain/ecvrf.mdx b/docs/content/developer/cryptography/on-chain/ecvrf.mdx
index ac1c28bf760..308dedaf339 100644
--- a/docs/content/developer/cryptography/on-chain/ecvrf.mdx
+++ b/docs/content/developer/cryptography/on-chain/ecvrf.mdx
@@ -52,7 +52,7 @@ module math::ecvrf_test {
use iota::event;
/// Event on whether the output is verified
- struct VerifiedEvent has copy, drop {
+ public struct VerifiedEvent has copy, drop {
is_verified: bool,
}
diff --git a/docs/content/developer/cryptography/on-chain/hashing.mdx b/docs/content/developer/cryptography/on-chain/hashing.mdx
index 3828658c8be..ed63b7d95eb 100644
--- a/docs/content/developer/cryptography/on-chain/hashing.mdx
+++ b/docs/content/developer/cryptography/on-chain/hashing.mdx
@@ -22,10 +22,9 @@ module test::hashing_std {
use iota::object::{Self, UID};
use iota::tx_context::TxContext;
use iota::transfer;
- use std::vector;
/// Object that holds the output hash value.
- struct Output has key, store {
+ public struct Output has key, store {
id: UID,
value: vector
}
@@ -49,10 +48,9 @@ module test::hashing_iota {
use iota::object::{Self, UID};
use iota::tx_context::TxContext;
use iota::transfer;
- use std::vector;
/// Object that holds the output hash value.
- struct Output has key, store {
+ public struct Output has key, store {
id: UID,
value: vector
}
diff --git a/docs/content/developer/developer.mdx b/docs/content/developer/developer.mdx
index 10774af912b..aa7aca661d6 100644
--- a/docs/content/developer/developer.mdx
+++ b/docs/content/developer/developer.mdx
@@ -5,24 +5,24 @@ description: Guides and documents for developers on the IOTA network. Whether yo
The developer section is meant to introduce you to the Move programming language and its implementation on the IOTA network through examples, tasks, and conceptual content. This contains everything a developer needs to get started developing on top of the IOTA network.
-## Getting started
+## Getting Started
-If you are completely new to Move, you should start with the aptly named Getting Started section. Topics in that section introduce you to the IOTA monorepo, guide you through installing IOTA binaries, and introduce you to some key core concepts of blockchain technology, particularly how they relate to IOTA.
+If you are completely new to Move, you should start with the aptly named Getting Started section. Topics in that section introduce you to the IOTA monorepo, guide you through installing IOTA binaries, and introduce you to some key core concepts of blockchain technology, particularly how they relate to IOTA. This sections contains everything you need to get your first dApp built and deployed.
Go to [Getting Started](getting-started/getting-started.mdx).
-## Your first dApp
-
-If you prefer to jump right in to coding (after installing IOTA, of course), then the Your First dApp is the place for you. These topics show you how to work with Move packages and get them published on-chain.
-
-Go to [Your First IOTA dApp](getting-started/create-a-package.mdx).
-
## IOTA 101
The IOTA 101 section introduces the basics of IOTA that help you create smart contracts. These topics assume you are familiar with Move and the IOTA blockchain.
Go to [IOTA 101](iota-101.mdx).
+## Standards
+
+Utilizing standards while developing applications is very important for composability. In this section you can find out all about the standards within the IOTA Move ecosystem for dealing with tokens, NFT like objects, and wallets.
+
+Go to the [Standards](/developer/standards).
+
## IOTA compared to EVM
If you are familiar with EVM/Solidity and want to work with IOTA and Move this section is for you. These topics describe the differences between a traditional EVM chain and way of working compared to IOTA Move based smart contracts. Together with some common implementation examples the nuances between the different ways of working are explained.
@@ -35,19 +35,25 @@ The Cryptography section demonstrates how to secure your smart contracts with cr
Go to [Cryptography](cryptography.mdx).
-## Standards
-
-Utilizing standards while developing applications is very important for composability. In this section you can find out all about the standards within the IOTA Move ecosystem for dealing with tokens, NFT like objects, and wallets.
-
-Go to the [Standards](/developer/standards).
-
## Advanced Topics
The Advanced Topics section includes guides for advanced solutions (like asset tokenization). These topics assume you are familiar with Move and the IOTA blockchain.
Go to the [Advanced Topics](advanced.mdx).
-## Developer cheat sheet
+## Migrating from IOTA/Shimmer Stardust
+
+IOTA Stardust becomes IOTA Rebased, and with it a lot of changes. Most assets are just available on the IOTA Rebased chain once it's available without any manual work but for integrations and in some situations you might need to migrate. This section covers the details of the migration and how you can prepare your integration to be IOTA Rebased compatible.
+
+Go to [Migrating from IOTA/Shimmer Stardust](stardust/stardust-migration.mdx).
+
+## Exchange Integration
+
+This section contains the technical details needed to integrate IOTA on a exchange.
+
+Go to [Exchange integration](exchange-integration/exchange-integration.mdx).
+
+## Developer Cheat Sheet
The cheat sheet is a compact overview of solutions for common problems and contains information on how to avoid common pitfalls for IOTA Move developers. This page contains important information that might get lost in the quantity of content available. Use this often-updated page to see around corners when starting a Move project or to refresh your memory on important concepts to be mindful of.
@@ -59,14 +65,9 @@ Everything you need to know about our Layer 2 EVM Support, including working wit
Go to [EVM Smart Contracts](iota-evm/introduction.mdx).
-## Migrating from IOTA/Shimmer Stardust
-
-IOTA Stardust becomes IOTA Rebased, and with it a lot of changes. Most assets are just available on the IOTA Rebased chain once it's available without any manual work but for integrations and in some situations you might need to migrate. This section covers the details of the migration and how you can prepare your integration to be IOTA Rebased compatible.
-
-Go to [Migrating from IOTA/Shimmer Stardust](stardust/stardust-migration.mdx).
+## Decentralized Identity
-## Exchange integration
+IOTA also offers a Decentralized Identity framework which can be utilized to provide and use digital decentralized identities for People, Organizations, Things and Objects.
-This section contains the technical details needed to integrate IOTA on a exchange.
+Go to the [IOTA Identity Framework](iota-identity/welcome.mdx) section.
-Go to [Exchange integration](exchange-integration/exchange-integration.mdx).
diff --git a/docs/content/developer/evm-to-move/creating-token.mdx b/docs/content/developer/evm-to-move/creating-token.mdx
index f3c8dbf6797..f8597fd1903 100644
--- a/docs/content/developer/evm-to-move/creating-token.mdx
+++ b/docs/content/developer/evm-to-move/creating-token.mdx
@@ -36,13 +36,12 @@ The initial creation of `Coin` takes place by minting these coins. This is usual
```move title="examples/Exampletoken.move"
module examples::exampletoken {
- use std::option;
use iota::coin;
use iota::transfer;
use iota::tx_context::{Self, TxContext};
/// One-Time-Witness of kind: `Coin`
- struct EXAMPLETOKEN has drop {}
+ public struct EXAMPLETOKEN has drop {}
fun init(witness: EXAMPLETOKEN, ctx: &mut TxContext) {
let (treasurycap, metadata) = coin::create_currency(
@@ -71,7 +70,7 @@ A `module` is defined (`exampletoken`) as part of the `examples` package (module
After the aliases, we see an empty struct defined:
```move
-struct EXAMPLETOKEN has drop {}
+public struct EXAMPLETOKEN has drop {}
```
This is the definition of the so-called [One-Time-Witness](../iota-101/move-overview/one-time-witness.mdx). Together with the `init` function definition, this ensures that this `Coin` will only be created once and never more on this chain.
diff --git a/docs/content/developer/getting-started/connect.mdx b/docs/content/developer/getting-started/connect.mdx
index d897fdc7ced..ee23e1c8e02 100644
--- a/docs/content/developer/getting-started/connect.mdx
+++ b/docs/content/developer/getting-started/connect.mdx
@@ -10,11 +10,13 @@ import AlphaNet from "../../_snippets/alphanet.mdx";
## IOTA CLI
-IOTA provides [IOTA command line interface (CLI)](/references/cli/client.mdx) to interact with [IOTA networks](#iota-networks):
+IOTA provides the [IOTA command line interface (CLI)](/references/cli/client.mdx) to interact with [IOTA networks](#iota-networks), it does the following and more:
- Create and manage your private keys
-- Create example NFTs
- Call and publish Move modules
+- Compile and test Move modules
+- Create and execute programmable transaction blocks ([PTBs](/references/cli/ptb.mdx))
+- Interact with testnet/devnet faucets
You can use the [CLI](iota-environment.mdx#iota-cli) or [SDKs](iota-environment.mdx#iota-sdks) to send transactions and
read requests from using the [JSON-RPC](../../references/iota-api/json-rpc-format.mdx) and the following
@@ -90,6 +92,12 @@ Select key scheme to generate keypair (0 for ed25519, 1 for secp256k1, 2: for se
Finally, you will be prompted to select the key scheme you want to use. After this, you will receive a message that
states the selected key-scheme, the generated address and your secret recovery phrase.
+:::tip Signature scheme selection
+
+If you are unsure which scheme to use just go with the default ed25519 scheme (option 0).
+
+:::
+
```bash
Generated new keypair for address with scheme "ed25519" [0xb9c83a8b40d3263c9ba40d551514fbac1f8c12e98a4005a0dac072d3549c2442]
Secret Recovery Phrase : [hat become demise beyond history wood stage add nice list jaguar legend]
diff --git a/docs/content/developer/getting-started/create-a-package.mdx b/docs/content/developer/getting-started/create-a-package.mdx
index 7c9b61b791b..653e2ce44af 100644
--- a/docs/content/developer/getting-started/create-a-package.mdx
+++ b/docs/content/developer/getting-started/create-a-package.mdx
@@ -31,7 +31,7 @@ In `.toml` files, use the hash mark (`#`) to denote a comment.
```toml title="my_first_package/Move.toml"
[package]
name = "my_first_package"
-edition = "2024.beta" # edition = "legacy" to use legacy (pre-2024) Move
+edition = "2024.beta" # edition
# license = "" # e.g., "MIT", "GPL", "Apache 2.0"
# authors = ["..."] # e.g., ["Joe Smith (joesmith@noemail.com)", "John Snow (johnsnow@noemail.com)"]
@@ -43,7 +43,7 @@ Iota = { git = "https://github.com/iotaledger/iota.git", subdir = "crates/iota-f
# MyRemotePackage = { git = "https://some.remote/host.git", subdir = "remote/path", rev = "main" }
# For local dependencies use `local = path`. Path is relative to the package root
-# Local = { local = "../path/to" }
+# Iota = { local = "../path/to/iota/crates/iota-framework/packages/iota-framework" }
# To resolve a version conflict and force a specific version for dependency
# override use `override = true`
@@ -67,6 +67,12 @@ my_first_package = "0x0"
# alice = "0xB0B"
```
+:::tip Using a local version of IOTA
+
+For local testnet development and testing it is recommended to use the local dependency of the `Iota` framework for faster and more reliable builds. See the commented line in the example above as an example pointing towards your local checkout of the `iota` repository.
+
+:::
+
### Package
The `[package]` section describes the package. By default, the `iota move new` command populates only the `name` value
@@ -83,13 +89,13 @@ repository URL or a path to the local directory.
```rust
# git repository
-iota = { git = "https://github.com/iotaledger/iota.git", subdir = "crates/iota-framework/packages/iota-framework", rev = "framework/testnet" }
+Iota = { git = "https://github.com/iotaledger/iota.git", subdir = "crates/iota-framework/packages/iota-framework", rev = "framework/testnet" }
# local directory
MyPackage = { local = "../my-package" }
```
-Packages also import addresses from other packages. For example, the IOTA dependency adds the `std` and `iota` addresses
+Packages also import addresses from other packages. For example, the `Iota` dependency adds the `std` and `iota` addresses
to the project. These addresses can be used in the code as aliases for the addresses.
### Resolving Version Conflicts with `override`
@@ -100,7 +106,7 @@ the `[dependencies]` section will be used instead of the one specified in the de
```rust
[dependencies]
-iota = { override = true, git = "https://github.com/iotaledger/iota.git", subdir = "crates/iota-framework/packages/iota-framework", rev = "framework/testnet" }
+Iota = { override = true, git = "https://github.com/iotaledger/iota.git", subdir = "crates/iota-framework/packages/iota-framework", rev = "framework/testnet" }
```
### Dev-dependencies
diff --git a/docs/content/developer/getting-started/get-address.mdx b/docs/content/developer/getting-started/get-address.mdx
index b88e4b57fe2..8aa74e7d322 100644
--- a/docs/content/developer/getting-started/get-address.mdx
+++ b/docs/content/developer/getting-started/get-address.mdx
@@ -67,7 +67,7 @@ IOTA provides multiple ways to obtain an IOTA address. The following are the two
:::note Supported Address Types
-IOTA supports multiple cryptographic algorithms for account generation. The two supported curves
+IOTA supports multiple signature schemes for account generation. The currently supported curves
are `ed25519`, `secp256k1`, and `secp256r1`.
:::
diff --git a/docs/content/developer/getting-started/iota-install.mdx b/docs/content/developer/getting-started/iota-install.mdx
index d069f0d9591..2c5d905d88e 100644
--- a/docs/content/developer/getting-started/iota-install.mdx
+++ b/docs/content/developer/getting-started/iota-install.mdx
@@ -24,9 +24,9 @@ always [build the binaries yourself from source](#install-from-source).
IOTA supports the following operating systems:
-- Linux - Ubuntu version 20.04 (Bionic Beaver)
-- macOS - macOS Monterey
-- Microsoft Windows - Windows 10 and 11
+- Linux (Ubuntu/Debian recommended)
+- macOS
+- Microsoft Windows (10+)
{/* TODO: Re-enable and check if we have packages published */}
{/*
@@ -76,7 +76,7 @@ install the necessary binaries. You should start with the main IOTA binary.
2. iota-faucet-``-``: Local faucet to mint coins on a local network.
3. iota-indexer-``-``: An indexer for a local IOTA network.
4. iota-node-``-``: Run a local node.
-5. iota-test-validator-``-``: Run test validators on a local network for development.
+5. iota-test-validator-``-``: Run test validators on a local network for development, including indexer and faucet.
6. iota-tool-``-``: Provides utilities for IOTA.
:::note
diff --git a/docs/content/developer/getting-started/local-network.mdx b/docs/content/developer/getting-started/local-network.mdx
index 6c74dae57d9..df113e650b9 100644
--- a/docs/content/developer/getting-started/local-network.mdx
+++ b/docs/content/developer/getting-started/local-network.mdx
@@ -5,12 +5,12 @@ tags: [ how-to, install, setup, cli, typescript, sdk, testing ]
# Local Development
You can create a local IOTA network to develop and test your dApps with the latest changes in the IOTA repository. You
-can set it up using the `iota-test-validator` binary, which will start a local IOTA Full node, an IOTA validator, and a
+can set it up using the `iota-test-validator` binary, which will start a local IOTA network consisting of 4 IOTA validators with indexer and a
test token faucet.
## Prerequisites
-You should [install IOTA](iota-install.mdx) to interact with the local node.
+You should [install the IOTA CLI tool](iota-install.mdx) to interact with the local node.
## Start a Local Network
@@ -165,7 +165,7 @@ The response resembles the following, but with different IDs:
### Prerequisites
-* [pnpm](https://pnpm.io/installation).
+* [pnpm](https://pnpm.io/installation)
### Install Dependencies
diff --git a/docs/content/operator/iota-full-node.mdx b/docs/content/operator/iota-full-node.mdx
index 7502a475929..ecafd65f858 100644
--- a/docs/content/operator/iota-full-node.mdx
+++ b/docs/content/operator/iota-full-node.mdx
@@ -13,13 +13,13 @@ IOTA Full nodes validate blockchain activities, including transactions, checkpoi
This role enables validators to focus on servicing and processing transactions. When a validator commits a new set of transactions (or a block of transactions), the validator pushes that block to all connected Full nodes that then service the queries from clients.
-## Features
+## Features
IOTA Full nodes:
- Track and verify the state of the blockchain, independently and locally.
- Serve read requests from clients.
-## State synchronization
+## State synchronization
IOTA Full nodes sync with validators to receive new transactions on the network.
A transaction requires a few round trips to 2f+1 validators to form a transaction certificate (TxCert).
@@ -32,7 +32,7 @@ This synchronization process includes:
This synchronization process requires listening to at a minimum 2f+1 validators to ensure that a Full node has properly processed all new transactions. IOTA will improve the synchronization process with the introduction of checkpoints and the ability to synchronize with other Full nodes.
-## Architecture
+## Architecture
An IOTA Full node is essentially a read-only view of the network state. Unlike validator nodes, Full nodes cannot sign transactions, although they can validate the integrity of the chain by re-executing transactions that a quorum of validators previously committed.
@@ -40,11 +40,11 @@ Today, an IOTA Full node maintains the full history of the chain.
Validator nodes store only the latest transactions on the frontier of the object graph (for example, transactions with >0 unspent output objects).
-## Full node setup
+## Full node setup
Follow the instructions here to run your own IOTA Full node.
-### Hardware requirements
+### Hardware requirements
Suggested minimum hardware to run an IOTA Full node:
@@ -52,7 +52,7 @@ Suggested minimum hardware to run an IOTA Full node:
- RAM: 128 GB
- Storage (SSD): 4 TB NVMe drive
-### Software requirements
+### Software requirements
IOTA recommends running IOTA Full nodes on Linux. IOTA supports the Ubuntu and Debian distributions. You can also run an IOTA Full node on macOS.
@@ -78,15 +78,15 @@ clang \
cmake
```
-## Configure a Full node
+## Configure a Full node
You can configure an IOTA Full node either using Docker or by building from source.
-### Using Docker Compose
+### Using Docker Compose
Follow the instructions in the [Full node Docker Readme](https://github.com/iotaledger/iota/tree/develop/docker/fullnode#readme) to run an IOTA Full node using Docker, including [resetting the environment](https://github.com/iotaledger/iota/tree/develop/docker/fullnode#reset-the-environment).
-### Setting up a local IOTA repository
+### Setting up a local IOTA repository
You must get the latest source files from the IOTA GitHub repository.
1. Set up your fork of the IOTA repository:
@@ -109,23 +109,23 @@ Open a terminal or console to the `iota` directory you downloaded in the previou
1. Make a copy of the [Full node YAML template](https://github.com/iotaledger/iota/blob/develop/crates/iota-config/data/fullnode-template.yaml):
`cp crates/iota-config/data/fullnode-template.yaml fullnode.yaml`
1. Download the genesis blob for the network to use:
- - [Devnet genesis blob](https://github.com/iotaledger/iota/TODO):
- `curl -fLJO TODO`
+ - [Alphanet genesis blob](https://dbfiles.iota-rebased-alphanet.iota.cafe/genesis.blob):
+ `curl -fLJO https://dbfiles.iota-rebased-alphanet.iota.cafe/genesis.blob`
- [Testnet genesis blob](https://github.com/iotaledger/iota/TODO):
`curl -fLJO TODO`
- [Mainnet genesis blob](https://github.com/iotaledger/iota/TODO):
`curl -fLJO TODO`
-1. For Testnet or Mainnet: Edit the `fullnode.yaml` file to include peer nodes for state synchronization. Append the following to the end of the current configuration:
+1. For Alphanet or Testnet: Edit the `fullnode.yaml` file to include peer nodes for state synchronization. Append the following to the end of the current configuration:
-
+
```yaml
p2p-config:
seed-peers:
- - address: TODO # Example: /dns/mel-00.mainnet.iota.io/udp/8084
- peer-id: TODO # Example: d32b55bdf1737ec415df8c88b3bf91e194b59ee3127e3f38ea46fd88ba2e7849
+ - address: /dns/access-0.r.iota-rebased-alphanet.iota.cafe/udp/8084
+ peer-id: 10cbea76ea5ec3f7ee827f0c11f612f0059949127876dd964b09304bf8808d18
```
@@ -141,7 +141,7 @@ Open a terminal or console to the `iota` directory you downloaded in the previou
-
+
1. Optional: Skip this step to accept the default paths to resources. Edit the fullnode.yaml file to use custom paths.
1. Update the `db-path` field with the path to the Full node database.
`db-path: "/db-files/iota-fullnode"`
@@ -159,7 +159,7 @@ Run the following command to compile the `iota-node`.
cargo run --release --bin iota-node
```
-### Starting services
+### Starting services
At this point, your IOTA Full node is ready to connect to the IOTA network.
@@ -172,7 +172,7 @@ If your setup is successful, your IOTA Full node is now connected to the appropr
Your Full node serves the read endpoints of the IOTA JSON-RPC API at: `http://127.0.0.1:9000`.
-### Troubleshooting
+### Troubleshooting
If, during the compilation step, you receive a `cannot find -lpq` error, you are missing the `libpq` library. Use `sudo apt-get install libpq-dev` to install on Linux, or `brew install libpq` on MacOS. After you install on MacOS, create a Homebrew link using `brew link --force libpq`. For further context, reference the [issue on Stack Overflow](https://stackoverflow.com/questions/70313347/ld-library-not-found-for-lpq-when-build-rust-in-macos?rq=1).
If you receive the following error:
@@ -187,17 +187,17 @@ Then update the metrics address in your fullnode.yaml file to use port `9180`.
metrics-address: "0.0.0.0:9180"
```
-## Monitoring
+## Monitoring
Monitor your Full node using the instructions in the _Node Monitoring and Metrics_ section.
The default metrics port is `9184`. To change the port, edit your `fullnode.yaml` file.
-## Update your Full node
+## Update your Full node
Whenever IOTA releases a new version, you must update your Full node with the release to ensure compatibility with the network it connects to. For example, if you use IOTA Testnet you should install the version of IOTA running on IOTA Testnet.
-### Update with Docker Compose
+### Update with Docker Compose
Follow the instructions to [reset the environment](https://github.com/iotaledger/iota/tree/develop/docker/fullnode#reset-the-environment), namely by running the command:
@@ -205,7 +205,7 @@ Follow the instructions to [reset the environment](https://github.com/iotaledger
docker-compose down --volumes
```
-### Update from source
+### Update from source
If you followed the instructions for Building from Source, use the following steps to update your Full node:
@@ -241,13 +241,13 @@ If you followed the instructions for Building from Source, use the following ste
```shell
./target/release/iota-node --config-path fullnode.yaml
```
-
+
Your Full node starts on: http://127.0.0.1:9000.
## Object pruning {#object-pruning}
-IOTA adds new object versions to the database as part of transaction execution. This makes previous versions ready for
-garbage collection. However, without pruning, this can result in database performance degradation and requires large
+IOTA adds new object versions to the database as part of transaction execution. This makes previous versions ready for
+garbage collection. However, without pruning, this can result in database performance degradation and requires large
amounts of storage space. IOTA identifies the objects that are eligible for pruning in each checkpoint, and then performs
the pruning in the background.
@@ -255,7 +255,7 @@ You can enable pruning for an IOTA node by adding the `authority-store-pruning-c
```yaml
authority-store-pruning-config:
- # Number of epoch dbs to keep
+ # Number of epoch dbs to keep
# Not relevant for object pruning
num-latest-epoch-dbs-to-retain: 3
# The amount of time, in seconds, between running the object pruning task.
@@ -264,16 +264,16 @@ authority-store-pruning-config:
# Number of epochs to wait before performing object pruning.
# When set to 0, IOTA prunes old object versions as soon
# as possible. This is also called *aggressive pruning*, and results in the most effective
- # garbage collection method with the lowest disk usage possible.
+ # garbage collection method with the lowest disk usage possible.
# This is the recommended setting for IOTA Validator nodes since older object versions aren't
# necessary to execute transactions.
# When set to 1, IOTA prunes only object versions from transaction checkpoints
- # previous to the current epoch. In general, when set to N (where N >= 1), IOTA prunes
- # only object versions from checkpoints up to `current - N` epoch.
- # It is therefore possible to have multiple versions of an object present
- # in the database. This setting is recommended for IOTA Full nodes as they might need to serve
+ # previous to the current epoch. In general, when set to N (where N >= 1), IOTA prunes
+ # only object versions from checkpoints up to `current - N` epoch.
+ # It is therefore possible to have multiple versions of an object present
+ # in the database. This setting is recommended for IOTA Full nodes as they might need to serve
# RPC requests that require looking up objects by ID and Version (rather than just the latest
- # version). However, if your Full node does not serve RPC requests you should then also enable
+ # version). However, if your Full node does not serve RPC requests you should then also enable
# aggressive pruning.
num-epochs-to-retain: 0
# Advanced setting: Maximum number of checkpoints to prune in a batch. The default
@@ -301,9 +301,9 @@ authority-store-pruning-config:
max-checkpoints-in-batch: 10
max-transactions-in-batch: 1000
# Number of epochs to wait before performing transaction pruning.
- # When this is N (where N >= 2), IOTA prunes transactions and effects from
+ # When this is N (where N >= 2), IOTA prunes transactions and effects from
# checkpoints up to the `current - N` epoch. IOTA never prunes transactions and effects from the current and
- # immediately prior epoch. N = 2 is a recommended setting for IOTA Validator nodes and IOTA Full nodes that don't
+ # immediately prior epoch. N = 2 is a recommended setting for IOTA Validator nodes and IOTA Full nodes that don't
# serve RPC requests.
num-epochs-to-retain-for-checkpoints: 2
# Ensures that individual database files periodically go through the compaction process.
diff --git a/docs/content/references/contribute/contribute-to-iota-repos.mdx b/docs/content/references/contribute/contribute-to-iota-repos.mdx
index 134e31484b6..9c4a678c7f8 100644
--- a/docs/content/references/contribute/contribute-to-iota-repos.mdx
+++ b/docs/content/references/contribute/contribute-to-iota-repos.mdx
@@ -18,8 +18,3 @@ To report an issue with IOTA, [create an issue](https://github.com/iotaledger/io
To contribute to IOTA source code or documentation, you need only a GitHub account. You can commit updates and then submit a PR directly from the Github website, or create a fork of the repo to your local environment and use your favorite tools to make changes. Always submit PRs to the `main` branch.
See [IOTA Environment Setup](/developer/getting-started/iota-environment.mdx) for instructions on forking the IOTA repository, if necessary.
-
-## Contribute via the IOTA Improvement Proposal (SIP) process {#SIP}
-
-The IOTA Network is an open-source, decentralized, and permissionless protocol that welcomes community contributions. If you have an idea regarding a core protocol upgrade, the best way to make your voice heard is via submitting a IOTA Improvement Proposal (SIP). For more information on SIPs, see [Contribute to IOTA through SIPs](https://blog.iota.io/iota-improvement-proposals-sips/).
-
diff --git a/docs/content/references/contribute/localize-iota-docs.mdx b/docs/content/references/contribute/localize-iota-docs.mdx
deleted file mode 100644
index 3827502075e..00000000000
--- a/docs/content/references/contribute/localize-iota-docs.mdx
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Localize IOTA Documentation
-slug: /localize-iota-docs
----
-
-The IOTA documentation can be localized (translated) into any language of your choosing. The localization platform utilized is Crowdin. For more information regarding the localization process please see [here](https://support.crowdin.com/crowdin-intro/).
diff --git a/docs/content/about-iota/execution-architecture/adapter.mdx b/docs/content/references/execution-architecture/adapter.mdx
similarity index 100%
rename from docs/content/about-iota/execution-architecture/adapter.mdx
rename to docs/content/references/execution-architecture/adapter.mdx
diff --git a/docs/content/about-iota/execution-architecture/execution-layer.mdx b/docs/content/references/execution-architecture/execution-layer.mdx
similarity index 87%
rename from docs/content/about-iota/execution-architecture/execution-layer.mdx
rename to docs/content/references/execution-architecture/execution-layer.mdx
index 7d5a5782bfd..c0f04f857b3 100644
--- a/docs/content/about-iota/execution-architecture/execution-layer.mdx
+++ b/docs/content/references/execution-architecture/execution-layer.mdx
@@ -9,4 +9,4 @@ It includes:
- The [IOTA Execution Crate](iota-execution.mdx).
- The [Adapter](adapter.mdx) and the [MoveVM](adapter.mdx#move-vm).
- The [Native Functions & Object Runtime](natives.mdx).
-- The [IOTA Framework](../../references/framework.mdx).
\ No newline at end of file
+- The [IOTA Framework](../framework.mdx).
\ No newline at end of file
diff --git a/docs/content/about-iota/execution-architecture/iota-execution.mdx b/docs/content/references/execution-architecture/iota-execution.mdx
similarity index 100%
rename from docs/content/about-iota/execution-architecture/iota-execution.mdx
rename to docs/content/references/execution-architecture/iota-execution.mdx
diff --git a/docs/content/about-iota/execution-architecture/natives.mdx b/docs/content/references/execution-architecture/natives.mdx
similarity index 100%
rename from docs/content/about-iota/execution-architecture/natives.mdx
rename to docs/content/references/execution-architecture/natives.mdx
diff --git a/docs/content/references/iota-glossary.mdx b/docs/content/references/iota-glossary.mdx
index 75929f62875..f39220836b4 100644
--- a/docs/content/references/iota-glossary.mdx
+++ b/docs/content/references/iota-glossary.mdx
@@ -75,11 +75,7 @@ A [smart contract](https://en.wikipedia.org/wiki/Smart_contract) is an agreement
### IOTA {#iota}
-IOTA refers to the IOTA blockchain, and the [IOTA open source project](https://github.com/iotaledger/iota/) as a whole.
-
-### IOTA {#iota-1}
-
-IOTA is the native token to the IOTA network.
+IOTA refers to the IOTA blockchain, and the [IOTA open source project](https://github.com/iotaledger/iota/) as a whole, or the native token to the IOTA network.
### Total order {#total-order}
diff --git a/docs/content/sidebars/about-iota.js b/docs/content/sidebars/about-iota.js
index 4f61f32d80c..f618bc0d3e9 100644
--- a/docs/content/sidebars/about-iota.js
+++ b/docs/content/sidebars/about-iota.js
@@ -39,24 +39,5 @@ const aboutIota = [
'about-iota/tokenomics/gas-pricing',
],
},
- {
- type: 'category',
- label: 'Expert topics',
- items: [
- {
- type: 'category',
- label: 'Execution Architecture',
- link: {
- type: 'doc',
- id: 'about-iota/execution-architecture/execution-layer',
- },
- items: [
- 'about-iota/execution-architecture/iota-execution',
- 'about-iota/execution-architecture/adapter',
- 'about-iota/execution-architecture/natives',
- ],
- },
- ],
- },
];
module.exports = aboutIota;
diff --git a/docs/content/sidebars/references.js b/docs/content/sidebars/references.js
index fcac9fa935f..dd1d40015fd 100644
--- a/docs/content/sidebars/references.js
+++ b/docs/content/sidebars/references.js
@@ -323,6 +323,25 @@ const references = [
},
],
},
+ {
+ type: 'category',
+ label: 'Expert topics',
+ items: [
+ {
+ type: 'category',
+ label: 'Execution Architecture',
+ link: {
+ type: 'doc',
+ id: 'references/execution-architecture/execution-layer',
+ },
+ items: [
+ 'references/execution-architecture/iota-execution',
+ 'references/execution-architecture/adapter',
+ 'references/execution-architecture/natives',
+ ],
+ },
+ ],
+ },
'references/research-papers',
'references/iota-glossary',
{
@@ -334,13 +353,6 @@ const references = [
},
items: [
'references/contribute/contribution-process',
- 'references/contribute/contribute-to-iota-repos',
- {
- type: 'link',
- label: 'Submit a SIP',
- href: 'https://sips.iota.io',
- },
- 'references/contribute/localize-iota-docs',
'references/contribute/code-of-conduct',
'references/contribute/style-guide',
],
diff --git a/nre/validator_tool.md b/nre/validator_tool.md
index ed512653a2e..cbeb008c435 100644
--- a/nre/validator_tool.md
+++ b/nre/validator_tool.md
@@ -169,6 +169,8 @@ At this point you are validator candidate and can start to accept self staking a
**If you haven't, start a fullnode now to catch up with the network. When you officially join the committee but is not fully up-to-date, you cannot make meaningful contribution to the network and may be subject to peer reporting hence face the risk of reduced staking rewards for you and your delegators.**
+Add stake to a validator's staking pool: https://docs.iota.org/references/framework/iota-system/iota_system#function-request_add_stake
+
Once you collect enough staking amount, run
```bash
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 3dd5c2e8653..68b72efaa3b 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -1107,8 +1107,8 @@ importers:
specifier: ^3.5.0
version: 3.5.0(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
next:
- specifier: 14.2.3
- version: 14.2.3(@babel/core@7.23.9)(@playwright/test@1.46.1)(babel-plugin-macros@3.1.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(sass@1.63.6)
+ specifier: 14.2.10
+ version: 14.2.10(@babel/core@7.23.9)(@playwright/test@1.46.1)(babel-plugin-macros@3.1.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(sass@1.63.6)
react:
specifier: ^18.3.1
version: 18.3.1
@@ -5254,62 +5254,62 @@ packages:
'@nestjs/platform-express':
optional: true
- '@next/env@14.2.3':
- resolution: {integrity: sha512-W7fd7IbkfmeeY2gXrzJYDx8D2lWKbVoTIj1o1ScPHNzvp30s1AuoEFSdr39bC5sjxJaxTtq3OTCZboNp0lNWHA==}
+ '@next/env@14.2.10':
+ resolution: {integrity: sha512-dZIu93Bf5LUtluBXIv4woQw2cZVZ2DJTjax5/5DOs3lzEOeKLy7GxRSr4caK9/SCPdaW6bCgpye6+n4Dh9oJPw==}
'@next/eslint-plugin-next@14.2.3':
resolution: {integrity: sha512-L3oDricIIjgj1AVnRdRor21gI7mShlSwU/1ZGHmqM3LzHhXXhdkrfeNY5zif25Bi5Dd7fiJHsbhoZCHfXYvlAw==}
- '@next/swc-darwin-arm64@14.2.3':
- resolution: {integrity: sha512-3pEYo/RaGqPP0YzwnlmPN2puaF2WMLM3apt5jLW2fFdXD9+pqcoTzRk+iZsf8ta7+quAe4Q6Ms0nR0SFGFdS1A==}
+ '@next/swc-darwin-arm64@14.2.10':
+ resolution: {integrity: sha512-V3z10NV+cvMAfxQUMhKgfQnPbjw+Ew3cnr64b0lr8MDiBJs3eLnM6RpGC46nhfMZsiXgQngCJKWGTC/yDcgrDQ==}
engines: {node: '>= 10'}
cpu: [arm64]
os: [darwin]
- '@next/swc-darwin-x64@14.2.3':
- resolution: {integrity: sha512-6adp7waE6P1TYFSXpY366xwsOnEXM+y1kgRpjSRVI2CBDOcbRjsJ67Z6EgKIqWIue52d2q/Mx8g9MszARj8IEA==}
+ '@next/swc-darwin-x64@14.2.10':
+ resolution: {integrity: sha512-Y0TC+FXbFUQ2MQgimJ/7Ina2mXIKhE7F+GUe1SgnzRmwFY3hX2z8nyVCxE82I2RicspdkZnSWMn4oTjIKz4uzA==}
engines: {node: '>= 10'}
cpu: [x64]
os: [darwin]
- '@next/swc-linux-arm64-gnu@14.2.3':
- resolution: {integrity: sha512-cuzCE/1G0ZSnTAHJPUT1rPgQx1w5tzSX7POXSLaS7w2nIUJUD+e25QoXD/hMfxbsT9rslEXugWypJMILBj/QsA==}
+ '@next/swc-linux-arm64-gnu@14.2.10':
+ resolution: {integrity: sha512-ZfQ7yOy5zyskSj9rFpa0Yd7gkrBnJTkYVSya95hX3zeBG9E55Z6OTNPn1j2BTFWvOVVj65C3T+qsjOyVI9DQpA==}
engines: {node: '>= 10'}
cpu: [arm64]
os: [linux]
- '@next/swc-linux-arm64-musl@14.2.3':
- resolution: {integrity: sha512-0D4/oMM2Y9Ta3nGuCcQN8jjJjmDPYpHX9OJzqk42NZGJocU2MqhBq5tWkJrUQOQY9N+In9xOdymzapM09GeiZw==}
+ '@next/swc-linux-arm64-musl@14.2.10':
+ resolution: {integrity: sha512-n2i5o3y2jpBfXFRxDREr342BGIQCJbdAUi/K4q6Env3aSx8erM9VuKXHw5KNROK9ejFSPf0LhoSkU/ZiNdacpQ==}
engines: {node: '>= 10'}
cpu: [arm64]
os: [linux]
- '@next/swc-linux-x64-gnu@14.2.3':
- resolution: {integrity: sha512-ENPiNnBNDInBLyUU5ii8PMQh+4XLr4pG51tOp6aJ9xqFQ2iRI6IH0Ds2yJkAzNV1CfyagcyzPfROMViS2wOZ9w==}
+ '@next/swc-linux-x64-gnu@14.2.10':
+ resolution: {integrity: sha512-GXvajAWh2woTT0GKEDlkVhFNxhJS/XdDmrVHrPOA83pLzlGPQnixqxD8u3bBB9oATBKB//5e4vpACnx5Vaxdqg==}
engines: {node: '>= 10'}
cpu: [x64]
os: [linux]
- '@next/swc-linux-x64-musl@14.2.3':
- resolution: {integrity: sha512-BTAbq0LnCbF5MtoM7I/9UeUu/8ZBY0i8SFjUMCbPDOLv+un67e2JgyN4pmgfXBwy/I+RHu8q+k+MCkDN6P9ViQ==}
+ '@next/swc-linux-x64-musl@14.2.10':
+ resolution: {integrity: sha512-opFFN5B0SnO+HTz4Wq4HaylXGFV+iHrVxd3YvREUX9K+xfc4ePbRrxqOuPOFjtSuiVouwe6uLeDtabjEIbkmDA==}
engines: {node: '>= 10'}
cpu: [x64]
os: [linux]
- '@next/swc-win32-arm64-msvc@14.2.3':
- resolution: {integrity: sha512-AEHIw/dhAMLNFJFJIJIyOFDzrzI5bAjI9J26gbO5xhAKHYTZ9Or04BesFPXiAYXDNdrwTP2dQceYA4dL1geu8A==}
+ '@next/swc-win32-arm64-msvc@14.2.10':
+ resolution: {integrity: sha512-9NUzZuR8WiXTvv+EiU/MXdcQ1XUvFixbLIMNQiVHuzs7ZIFrJDLJDaOF1KaqttoTujpcxljM/RNAOmw1GhPPQQ==}
engines: {node: '>= 10'}
cpu: [arm64]
os: [win32]
- '@next/swc-win32-ia32-msvc@14.2.3':
- resolution: {integrity: sha512-vga40n1q6aYb0CLrM+eEmisfKCR45ixQYXuBXxOOmmoV8sYST9k7E3US32FsY+CkkF7NtzdcebiFT4CHuMSyZw==}
+ '@next/swc-win32-ia32-msvc@14.2.10':
+ resolution: {integrity: sha512-fr3aEbSd1GeW3YUMBkWAu4hcdjZ6g4NBl1uku4gAn661tcxd1bHs1THWYzdsbTRLcCKLjrDZlNp6j2HTfrw+Bg==}
engines: {node: '>= 10'}
cpu: [ia32]
os: [win32]
- '@next/swc-win32-x64-msvc@14.2.3':
- resolution: {integrity: sha512-Q1/zm43RWynxrO7lW4ehciQVj+5ePBhOK+/K2P7pLFX3JaJ/IZVC69SHidrmZSOkqz7ECIOhhy7XhAFG4JYyHA==}
+ '@next/swc-win32-x64-msvc@14.2.10':
+ resolution: {integrity: sha512-UjeVoRGKNL2zfbcQ6fscmgjBAS/inHBh63mjIlfPg/NG8Yn2ztqylXt5qilYb6hoHIwaU2ogHknHWWmahJjgZQ==}
engines: {node: '>= 10'}
cpu: [x64]
os: [win32]
@@ -8975,9 +8975,6 @@ packages:
caniuse-lite@1.0.30001520:
resolution: {integrity: sha512-tahF5O9EiiTzwTUqAeFjIZbn4Dnqxzz7ktrgGlMYNLH43Ul26IgTMH/zvL3DG0lZxBYnlT04axvInszUsZULdA==}
- caniuse-lite@1.0.30001585:
- resolution: {integrity: sha512-yr2BWR1yLXQ8fMpdS/4ZZXpseBgE7o4g41x3a6AJOqZuOi+iE/WdJYAuZ6Y95i4Ohd2Y+9MzIWRR+uGABH4s3Q==}
-
caniuse-lite@1.0.30001636:
resolution: {integrity: sha512-bMg2vmr8XBsbL6Lr0UHXy/21m84FTxDLWn2FSqMd5PrlbMxwJlQnC2YWYxVgp66PZE+BBNF2jYQUBKCo1FDeZg==}
@@ -13461,8 +13458,8 @@ packages:
neo-async@2.6.2:
resolution: {integrity: sha512-Yd3UES5mWCSqR+qNT93S3UoYUkqAZ9lLg8a7g9rimsWmYGK8cVToA4/sF3RrshdyV3sAGMXVUmpMYOw+dLpOuw==}
- next@14.2.3:
- resolution: {integrity: sha512-dowFkFTR8v79NPJO4QsBUtxv0g9BrS/phluVpMAt2ku7H+cbcBJlopXjkWlwxrk/xGqMemr7JkGPGemPrLLX7A==}
+ next@14.2.10:
+ resolution: {integrity: sha512-sDDExXnh33cY3RkS9JuFEKaS4HmlWmDKP1VJioucCG6z5KuA008DPsDZOzi8UfqEk3Ii+2NCQSJrfbEWtZZfww==}
engines: {node: '>=18.17.0'}
hasBin: true
peerDependencies:
@@ -22898,37 +22895,37 @@ snapshots:
optionalDependencies:
'@nestjs/platform-express': 10.3.8(@nestjs/common@10.3.8(reflect-metadata@0.2.2)(rxjs@7.8.1))(@nestjs/core@10.3.8)
- '@next/env@14.2.3': {}
+ '@next/env@14.2.10': {}
'@next/eslint-plugin-next@14.2.3':
dependencies:
glob: 10.3.10
- '@next/swc-darwin-arm64@14.2.3':
+ '@next/swc-darwin-arm64@14.2.10':
optional: true
- '@next/swc-darwin-x64@14.2.3':
+ '@next/swc-darwin-x64@14.2.10':
optional: true
- '@next/swc-linux-arm64-gnu@14.2.3':
+ '@next/swc-linux-arm64-gnu@14.2.10':
optional: true
- '@next/swc-linux-arm64-musl@14.2.3':
+ '@next/swc-linux-arm64-musl@14.2.10':
optional: true
- '@next/swc-linux-x64-gnu@14.2.3':
+ '@next/swc-linux-x64-gnu@14.2.10':
optional: true
- '@next/swc-linux-x64-musl@14.2.3':
+ '@next/swc-linux-x64-musl@14.2.10':
optional: true
- '@next/swc-win32-arm64-msvc@14.2.3':
+ '@next/swc-win32-arm64-msvc@14.2.10':
optional: true
- '@next/swc-win32-ia32-msvc@14.2.3':
+ '@next/swc-win32-ia32-msvc@14.2.10':
optional: true
- '@next/swc-win32-x64-msvc@14.2.3':
+ '@next/swc-win32-x64-msvc@14.2.10':
optional: true
'@nicolo-ribaudo/semver-v6@6.3.3': {}
@@ -28140,8 +28137,6 @@ snapshots:
caniuse-lite@1.0.30001520: {}
- caniuse-lite@1.0.30001585: {}
-
caniuse-lite@1.0.30001636: {}
capital-case@1.0.4:
@@ -34367,27 +34362,27 @@ snapshots:
neo-async@2.6.2: {}
- next@14.2.3(@babel/core@7.23.9)(@playwright/test@1.46.1)(babel-plugin-macros@3.1.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(sass@1.63.6):
+ next@14.2.10(@babel/core@7.23.9)(@playwright/test@1.46.1)(babel-plugin-macros@3.1.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(sass@1.63.6):
dependencies:
- '@next/env': 14.2.3
+ '@next/env': 14.2.10
'@swc/helpers': 0.5.5
busboy: 1.6.0
- caniuse-lite: 1.0.30001585
+ caniuse-lite: 1.0.30001636
graceful-fs: 4.2.11
postcss: 8.4.31
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
styled-jsx: 5.1.1(@babel/core@7.23.9)(babel-plugin-macros@3.1.0)(react@18.3.1)
optionalDependencies:
- '@next/swc-darwin-arm64': 14.2.3
- '@next/swc-darwin-x64': 14.2.3
- '@next/swc-linux-arm64-gnu': 14.2.3
- '@next/swc-linux-arm64-musl': 14.2.3
- '@next/swc-linux-x64-gnu': 14.2.3
- '@next/swc-linux-x64-musl': 14.2.3
- '@next/swc-win32-arm64-msvc': 14.2.3
- '@next/swc-win32-ia32-msvc': 14.2.3
- '@next/swc-win32-x64-msvc': 14.2.3
+ '@next/swc-darwin-arm64': 14.2.10
+ '@next/swc-darwin-x64': 14.2.10
+ '@next/swc-linux-arm64-gnu': 14.2.10
+ '@next/swc-linux-arm64-musl': 14.2.10
+ '@next/swc-linux-x64-gnu': 14.2.10
+ '@next/swc-linux-x64-musl': 14.2.10
+ '@next/swc-win32-arm64-msvc': 14.2.10
+ '@next/swc-win32-ia32-msvc': 14.2.10
+ '@next/swc-win32-x64-msvc': 14.2.10
'@playwright/test': 1.46.1
sass: 1.63.6
transitivePeerDependencies: