diff --git a/.github/workflows/_rust_tests.yml b/.github/workflows/_rust_tests.yml
index 9aeccdffe2d..99df4384185 100644
--- a/.github/workflows/_rust_tests.yml
+++ b/.github/workflows/_rust_tests.yml
@@ -204,6 +204,6 @@ jobs:
cargo nextest run --no-fail-fast --test-threads 8 --package iota-graphql-e2e-tests --features pg_integration
cargo nextest run --no-fail-fast --test-threads 1 --package iota-cluster-test --test local_cluster_test --features pg_integration
cargo nextest run --no-fail-fast --test-threads 1 --package iota-indexer --test ingestion_tests --features pg_integration
- # Iota-indexer's RPC tests, which depend on a shared runtime, are incompatible with nextest due to its process-per-test execution model.
+ # iota-indexer's RPC tests, which depend on a shared runtime, are incompatible with nextest due to its process-per-test execution model.
# cargo test, on the other hand, allows tests to share state and resources by default.
cargo test --profile simulator --package iota-indexer --test rpc-tests --features shared_test_runtime
diff --git a/Cargo.lock b/Cargo.lock
index 1eab542687f..6187ede5b47 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -7895,7 +7895,7 @@ dependencies = [
[[package]]
name = "iota-rust-sdk"
version = "0.0.0"
-source = "git+https://github.com/iotaledger/iota-rust-sdk.git?rev=d605da95029e74376f0f39a95526bb1a5c0ebd7a#d605da95029e74376f0f39a95526bb1a5c0ebd7a"
+source = "git+https://github.com/iotaledger/iota-rust-sdk.git?rev=2ba6b293bdede769a1d9b4d1aecaede2ff7682dd#2ba6b293bdede769a1d9b4d1aecaede2ff7682dd"
dependencies = [
"base64ct",
"bcs",
@@ -9159,7 +9159,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4979f22fdb869068da03c9f7528f8297c6fd2606bc3a4affe42e6a823fdb8da4"
dependencies = [
"cfg-if",
- "windows-targets 0.52.6",
+ "windows-targets 0.48.5",
]
[[package]]
diff --git a/Cargo.toml b/Cargo.toml
index bc6279194b4..be2b62e55c7 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -414,7 +414,7 @@ iota-rosetta = { path = "crates/iota-rosetta" }
iota-rpc-loadgen = { path = "crates/iota-rpc-loadgen" }
iota-sdk = { path = "crates/iota-sdk" }
# core-types with json format for REST API
-iota-sdk2 = { package = "iota-rust-sdk", git = "https://github.com/iotaledger/iota-rust-sdk.git", rev = "d605da95029e74376f0f39a95526bb1a5c0ebd7a", features = ["hash", "serde", "schemars"] }
+iota-sdk2 = { package = "iota-rust-sdk", git = "https://github.com/iotaledger/iota-rust-sdk.git", rev = "2ba6b293bdede769a1d9b4d1aecaede2ff7682dd", features = ["hash", "serde", "schemars"] }
iota-simulator = { path = "crates/iota-simulator" }
iota-snapshot = { path = "crates/iota-snapshot" }
iota-source-validation = { path = "crates/iota-source-validation" }
diff --git a/apps/explorer/src/components/validator/ValidatorStats.tsx b/apps/explorer/src/components/validator/ValidatorStats.tsx
index a39b65a7eec..06992a863a1 100644
--- a/apps/explorer/src/components/validator/ValidatorStats.tsx
+++ b/apps/explorer/src/components/validator/ValidatorStats.tsx
@@ -149,7 +149,7 @@ export function ValidatorStats({
tooltipText={
!tallyingScore
? 'Coming soon'
- : 'A score created by validators to assess each other’s performance during Iota’s standard operations.'
+ : 'A score created by validators to assess each other’s performance during IOTA’s standard operations.'
}
tooltipPosition={TooltipPosition.Right}
/>
diff --git a/apps/wallet/src/ui/app/components/transactions-card/index.tsx b/apps/wallet/src/ui/app/components/transactions-card/index.tsx
index 3876a731649..1c1d8f47226 100644
--- a/apps/wallet/src/ui/app/components/transactions-card/index.tsx
+++ b/apps/wallet/src/ui/app/components/transactions-card/index.tsx
@@ -40,7 +40,7 @@ export function TransactionCard({ txn, address }: TransactionCardProps) {
recognizedPackagesList,
});
- // we only show IOTA Transfer amount or the first non-Iota transfer amount
+ // we only show IOTA Transfer amount or the first non-IOTA transfer amount
// Get the balance changes for the transaction and the amount
const balanceChanges = getBalanceChangeSummary(txn, recognizedPackagesList);
const [formatAmount, symbol] = useFormatCoin(
diff --git a/bridge/evm/contracts/BridgeConfig.sol b/bridge/evm/contracts/BridgeConfig.sol
index d9a9069976b..4a10ee5e3c5 100644
--- a/bridge/evm/contracts/BridgeConfig.sol
+++ b/bridge/evm/contracts/BridgeConfig.sol
@@ -8,7 +8,7 @@ import "./interfaces/IBridgeConfig.sol";
/// @title BridgeConfig
/// @notice This contract manages a registry of supported tokens and supported chain IDs for the IotaBridge.
-/// It also provides functions to convert token amounts to Iota decimal adjusted amounts and vice versa.
+/// It also provides functions to convert token amounts to IOTA decimal adjusted amounts and vice versa.
contract BridgeConfig is IBridgeConfig, CommitteeUpgradeable {
/* ========== STATE VARIABLES ========== */
@@ -166,11 +166,11 @@ contract BridgeConfig is IBridgeConfig, CommitteeUpgradeable {
bool native
) private {
require(tokenAddress != address(0), "BridgeConfig: Invalid token address");
- require(iotaDecimal > 0, "BridgeConfig: Invalid Iota decimal");
+ require(iotaDecimal > 0, "BridgeConfig: Invalid IOTA decimal");
require(tokenPrice > 0, "BridgeConfig: Invalid token price");
uint8 erc20Decimals = IERC20Metadata(tokenAddress).decimals();
- require(erc20Decimals >= iotaDecimal, "BridgeConfig: Invalid Iota decimal");
+ require(erc20Decimals >= iotaDecimal, "BridgeConfig: Invalid IOTA decimal");
supportedTokens[tokenID] = Token(tokenAddress, iotaDecimal, native);
tokenPrices[tokenID] = tokenPrice;
diff --git a/bridge/evm/contracts/IotaBridge.sol b/bridge/evm/contracts/IotaBridge.sol
index cd4362d0765..dc1fe6351e0 100644
--- a/bridge/evm/contracts/IotaBridge.sol
+++ b/bridge/evm/contracts/IotaBridge.sol
@@ -16,7 +16,7 @@ import "./interfaces/IWETH9.sol";
/// @title IotaBridge
/// @notice This contract implements a token bridge that enables users to deposit and withdraw
/// supported tokens to and from other chains. The bridge supports the transfer of Ethereum and ERC20
-/// tokens. Bridge operations are managed by a committee of Iota validators that are responsible
+/// tokens. Bridge operations are managed by a committee of IOTA validators that are responsible
/// for verifying and processing bridge messages. The bridge is designed to be upgradeable and
/// can be paused in case of an emergency. The bridge also enforces limits on the amount of
/// assets that can be withdrawn to prevent abuse.
@@ -131,7 +131,7 @@ contract IotaBridge is IIotaBridge, CommitteeUpgradeable, PausableUpgradeable {
/// have approved this contract to transfer the given token.
/// @param tokenID The ID of the token to be bridged.
/// @param amount The amount of tokens to be bridged.
- /// @param recipientAddress The address on the Iota chain where the tokens will be sent.
+ /// @param recipientAddress The address on the IOTA chain where the tokens will be sent.
/// @param destinationChainID The ID of the destination chain.
function bridgeERC20(
uint8 tokenID,
diff --git a/bridge/evm/contracts/interfaces/IIotaBridge.sol b/bridge/evm/contracts/interfaces/IIotaBridge.sol
index f7f70a307f6..ad874d85ee7 100644
--- a/bridge/evm/contracts/interfaces/IIotaBridge.sol
+++ b/bridge/evm/contracts/interfaces/IIotaBridge.sol
@@ -3,14 +3,14 @@
pragma solidity ^0.8.20;
/// @title IIotaBridge
-/// @dev Interface for the Iota Bridge contract.
+/// @dev Interface for the IOTA Bridge contract.
interface IIotaBridge {
/// @notice Emitted when tokens are deposited to be bridged.
/// @param sourceChainID The ID of the source chain (this chain).
/// @param nonce The nonce of the transaction on source chain.
/// @param destinationChainID The ID of the destination chain.
/// @param tokenID The code of the token.
- /// @param iotaAdjustedAmount The amount of tokens to transfer, adjusted for Iota decimals.
+ /// @param iotaAdjustedAmount The amount of tokens to transfer, adjusted for IOTA decimals.
/// @param senderAddress The address of the sender.
/// @param recipientAddress The address of the sender.
event TokensDeposited(
diff --git a/bridge/evm/contracts/utils/BridgeUtils.sol b/bridge/evm/contracts/utils/BridgeUtils.sol
index 0d9f501a0d9..9db8093cc02 100644
--- a/bridge/evm/contracts/utils/BridgeUtils.sol
+++ b/bridge/evm/contracts/utils/BridgeUtils.sol
@@ -3,7 +3,7 @@
pragma solidity ^0.8.20;
/// @title BridgeUtils
-/// @notice This library defines the message format and constants for the Iota native bridge. It also
+/// @notice This library defines the message format and constants for the IOTA native bridge. It also
/// provides functions to encode and decode bridge messages and their payloads.
/// @dev This library only utilizes internal functions to enable upgradeability via the OpenZeppelin
/// UUPS proxy pattern (external libraries are not supported).
@@ -118,11 +118,11 @@ library BridgeUtils {
}
}
- /// @notice Converts the provided token amount to the Iota decimal adjusted amount.
+ /// @notice Converts the provided token amount to the IOTA decimal adjusted amount.
/// @param erc20Decimal The erc20 decimal value for the token.
/// @param iotaDecimal The iota decimal value for the token.
- /// @param amount The ERC20 amount of the tokens to convert to Iota.
- /// @return Iota converted amount.
+ /// @param amount The ERC20 amount of the tokens to convert to IOTA.
+ /// @return IOTA converted amount.
function convertERC20ToIotaDecimal(uint8 erc20Decimal, uint8 iotaDecimal, uint256 amount)
internal
pure
@@ -136,7 +136,7 @@ library BridgeUtils {
return uint64(amount);
}
- require(erc20Decimal > iotaDecimal, "BridgeUtils: Invalid Iota decimal");
+ require(erc20Decimal > iotaDecimal, "BridgeUtils: Invalid IOTA decimal");
// Difference in decimal places
uint256 factor = 10 ** (erc20Decimal - iotaDecimal);
@@ -151,10 +151,10 @@ library BridgeUtils {
return uint64(amount);
}
- /// @notice Converts the provided Iota decimal adjusted amount to the ERC20 token amount.
+ /// @notice Converts the provided IOTA decimal adjusted amount to the ERC20 token amount.
/// @param erc20Decimal The erc20 decimal value for the token.
/// @param iotaDecimal The iota decimal value for the token.
- /// @param amount The Iota amount of the tokens to convert to ERC20.
+ /// @param amount The IOTA amount of the tokens to convert to ERC20.
/// @return ERC20 converted amount.
function convertIotaToERC20Decimal(uint8 erc20Decimal, uint8 iotaDecimal, uint64 amount)
internal
@@ -165,7 +165,7 @@ library BridgeUtils {
return uint256(amount);
}
- require(erc20Decimal > iotaDecimal, "BridgeUtils: Invalid Iota decimal");
+ require(erc20Decimal > iotaDecimal, "BridgeUtils: Invalid IOTA decimal");
// Difference in decimal places
uint256 factor = 10 ** (erc20Decimal - iotaDecimal);
@@ -176,7 +176,7 @@ library BridgeUtils {
/// @dev The function will revert if the payload length is invalid.
/// TokenTransfer payload is 64 bytes.
/// byte 0 : sender address length
- /// bytes 1-32 : sender address (as we only support Iota now, it has to be 32 bytes long)
+ /// bytes 1-32 : sender address (as we only support IOTA now, it has to be 32 bytes long)
/// bytes 33 : target chain id
/// byte 34 : target address length
/// bytes 35-54 : target address
@@ -195,7 +195,7 @@ library BridgeUtils {
require(
senderAddressLength == 32,
- "BridgeUtils: Invalid sender address length, Iota address must be 32 bytes"
+ "BridgeUtils: Invalid sender address length, IOTA address must be 32 bytes"
);
// used to offset already read bytes
@@ -391,7 +391,7 @@ library BridgeUtils {
/// @return native whether the token is native to the chain.
/// @return tokenIDs the token ID to be added.
/// @return tokenAddresses the address of the token to be added.
- /// @return iotaDecimals the Iota decimal places of the tokens to be added.
+ /// @return iotaDecimals the IOTA decimal places of the tokens to be added.
/// @return tokenPrices the price of the tokens to be added.
function decodeAddTokensPayload(bytes memory _payload)
internal
diff --git a/bridge/evm/script/deploy_bridge.s.sol b/bridge/evm/script/deploy_bridge.s.sol
index 5f15f006d00..5397073c3e8 100644
--- a/bridge/evm/script/deploy_bridge.s.sol
+++ b/bridge/evm/script/deploy_bridge.s.sol
@@ -68,7 +68,7 @@ contract DeployBridge is Script {
}
// deploy bridge config
- // price of Iota (id = 0) should not be included in tokenPrices
+ // price of IOTA (id = 0) should not be included in tokenPrices
require(
deployConfig.supportedTokens.length == deployConfig.tokenPrices.length,
"supportedTokens.length + 1 != tokenPrices.length"
@@ -149,7 +149,7 @@ contract DeployBridge is Script {
uint8[] memory _destinationChains = new uint8[](1);
_destinationChains[0] = 1;
- // deploy Iota Bridge ========================================================================
+ // deploy IOTA Bridge ========================================================================
address iotaBridge = Upgrades.deployUUPSProxy(
"IotaBridge.sol",
diff --git a/bridge/evm/test/BridgeConfigTest.t.sol b/bridge/evm/test/BridgeConfigTest.t.sol
index 32eceea61fb..f87d64c5c76 100644
--- a/bridge/evm/test/BridgeConfigTest.t.sol
+++ b/bridge/evm/test/BridgeConfigTest.t.sol
@@ -195,7 +195,7 @@ contract BridgeConfigTest is BridgeBaseTest {
signatures[3] = getSignature(messageHash, committeeMemberPkD);
// add token should fail because the iota decimal is greater than the eth decimal
- vm.expectRevert(bytes("BridgeConfig: Invalid Iota decimal"));
+ vm.expectRevert(bytes("BridgeConfig: Invalid IOTA decimal"));
config.addTokensWithSignatures(signatures, message);
}
diff --git a/bridge/evm/test/BridgeUtilsTest.t.sol b/bridge/evm/test/BridgeUtilsTest.t.sol
index c9e93074d32..8a16fd71d46 100644
--- a/bridge/evm/test/BridgeUtilsTest.t.sol
+++ b/bridge/evm/test/BridgeUtilsTest.t.sol
@@ -17,12 +17,12 @@ contract BridgeUtilsTest is BridgeBaseTest {
}
function testConvertERC20ToIotaDecimalInvalidIotaDecimal() public {
- vm.expectRevert(bytes("BridgeUtils: Invalid Iota decimal"));
+ vm.expectRevert(bytes("BridgeUtils: Invalid IOTA decimal"));
BridgeUtils.convertERC20ToIotaDecimal(10, 11, 100);
}
function testconvertIotaToERC20DecimalInvalidIotaDecimal() public {
- vm.expectRevert(bytes("BridgeUtils: Invalid Iota decimal"));
+ vm.expectRevert(bytes("BridgeUtils: Invalid IOTA decimal"));
BridgeUtils.convertIotaToERC20Decimal(10, 11, 100);
}
diff --git a/bridge/evm/test/IotaBridgeTest.t.sol b/bridge/evm/test/IotaBridgeTest.t.sol
index f21a8ff7969..11e26000e37 100644
--- a/bridge/evm/test/IotaBridgeTest.t.sol
+++ b/bridge/evm/test/IotaBridgeTest.t.sol
@@ -103,7 +103,7 @@ contract IotaBridgeTest is BridgeBaseTest, IIotaBridge {
recipientAddressLength: 0,
recipientAddress: bridgerA,
tokenID: BridgeUtils.ETH,
- // This is Iota amount (eth decimal 8)
+ // This is IOTA amount (eth decimal 8)
amount: 100_000_000
});
BridgeUtils.Message memory message = BridgeUtils.Message({
@@ -131,7 +131,7 @@ contract IotaBridgeTest is BridgeBaseTest, IIotaBridge {
recipientAddressLength: 0,
recipientAddress: bridgerA,
tokenID: BridgeUtils.ETH,
- // This is Iota amount (eth decimal 8)
+ // This is IOTA amount (eth decimal 8)
amount: 100_000_000
});
BridgeUtils.Message memory message = BridgeUtils.Message({
diff --git a/chocolatey/iota.nuspec b/chocolatey/iota.nuspec
index 26d9153b6bd..c547358e932 100644
--- a/chocolatey/iota.nuspec
+++ b/chocolatey/iota.nuspec
@@ -6,7 +6,7 @@ enclosed in quotation marks, you should use an editor that supports UTF-8, not t
iota$version$iota
- Main Iota Binary
+ Main IOTA Binaryiotahttps://iota.org/https://github.com/iotaledger/iota/blob/develop/LICENSE
@@ -16,7 +16,7 @@ enclosed in quotation marks, you should use an editor that supports UTF-8, not t
iotahttps://community.chocolatey.org/packages/iota.portableRun a local iota binary
- Iota is the first internet-scale programmable blockchain platform
+ IOTA is the first internet-scale programmable blockchain platformhttps://github.com/iotaledger/iota/releases/tag/mainnet-v$version$
diff --git a/consensus/config/src/committee.rs b/consensus/config/src/committee.rs
index dcfa2aed87f..0793d9d8b8b 100644
--- a/consensus/config/src/committee.rs
+++ b/consensus/config/src/committee.rs
@@ -16,7 +16,7 @@ use crate::{AuthorityPublicKey, NetworkPublicKey, ProtocolPublicKey};
pub type Epoch = u64;
/// Voting power of an authority, roughly proportional to the actual amount of
-/// Iota staked by the authority.
+/// IOTA staked by the authority.
/// Total stake / voting power of all authorities should sum to 10,000.
pub type Stake = u64;
diff --git a/consensus/config/src/parameters.rs b/consensus/config/src/parameters.rs
index 61d2b3eba7f..be777fbbd27 100644
--- a/consensus/config/src/parameters.rs
+++ b/consensus/config/src/parameters.rs
@@ -9,7 +9,7 @@ use serde::{Deserialize, Serialize};
/// Operational configurations of a consensus authority.
///
/// All fields should tolerate inconsistencies among authorities, without
-/// affecting safety of the protocol. Otherwise, they need to be part of Iota
+/// affecting safety of the protocol. Otherwise, they need to be part of IOTA
/// protocol config or epoch state on-chain.
///
/// NOTE: fields with default values are specified in the serde default
diff --git a/consensus/core/src/authority_node.rs b/consensus/core/src/authority_node.rs
index 70f81c271fb..ee618b2b256 100644
--- a/consensus/core/src/authority_node.rs
+++ b/consensus/core/src/authority_node.rs
@@ -33,7 +33,7 @@ use crate::{
transaction::{TransactionClient, TransactionConsumer, TransactionVerifier},
};
-/// ConsensusAuthority is used by Iota to manage the lifetime of AuthorityNode.
+/// ConsensusAuthority is used by IOTA to manage the lifetime of AuthorityNode.
/// It hides the details of the implementation from the caller,
/// MysticetiManager.
pub enum ConsensusAuthority {
diff --git a/consensus/core/src/block.rs b/consensus/core/src/block.rs
index c08bcce1f46..fbe1ae2fb9c 100644
--- a/consensus/core/src/block.rs
+++ b/consensus/core/src/block.rs
@@ -34,7 +34,7 @@ pub(crate) const GENESIS_ROUND: Round = 0;
/// Block proposal as epoch UNIX timestamp in milliseconds.
pub type BlockTimestampMs = u64;
-/// Iota transaction in serialised bytes
+/// IOTA transaction in serialised bytes
#[derive(Clone, Eq, PartialEq, Serialize, Deserialize, Default, Debug)]
pub struct Transaction {
data: Bytes,
diff --git a/consensus/core/src/commit.rs b/consensus/core/src/commit.rs
index fc2221a84b0..36735cfd771 100644
--- a/consensus/core/src/commit.rs
+++ b/consensus/core/src/commit.rs
@@ -308,7 +308,7 @@ pub struct CommittedSubDag {
/// a index incremented by 1.
pub commit_ref: CommitRef,
/// Optional scores that are provided as part of the consensus output to
- /// Iota that can then be used by Iota for future submission to
+ /// IOTA that can then be used by IOTA for future submission to
/// consensus.
pub reputation_scores_desc: Vec<(AuthorityIndex, u64)>,
}
diff --git a/consensus/core/src/commit_syncer.rs b/consensus/core/src/commit_syncer.rs
index ef6ce101cb3..8dec50c2a83 100644
--- a/consensus/core/src/commit_syncer.rs
+++ b/consensus/core/src/commit_syncer.rs
@@ -15,7 +15,7 @@
//! when blocks are included in commits with >= 2f+1 certifiers by stake, these
//! blocks must have passed verifications on some honest validators, so
//! re-verifying them is unnecessary. In fact, the quorum certified commits
-//! themselves can be trusted to be sent to Iota directly, but for simplicity
+//! themselves can be trusted to be sent to IOTA directly, but for simplicity
//! this is not done. Blocks from trusted commits still go through Core and
//! committer.
//!
diff --git a/consensus/core/src/linearizer.rs b/consensus/core/src/linearizer.rs
index 54f20e7f537..7ebfba9cc8d 100644
--- a/consensus/core/src/linearizer.rs
+++ b/consensus/core/src/linearizer.rs
@@ -158,7 +158,7 @@ impl Linearizer {
committed_sub_dags.push(sub_dag);
}
- // Committed blocks must be persisted to storage before sending them to Iota and
+ // Committed blocks must be persisted to storage before sending them to IOTA and
// executing their transactions.
// Commit metadata can be persisted more lazily because they are recoverable.
// Uncommitted blocks can wait to persist too.
diff --git a/consensus/core/src/transaction.rs b/consensus/core/src/transaction.rs
index f22eeeba635..fb8dbb8c99f 100644
--- a/consensus/core/src/transaction.rs
+++ b/consensus/core/src/transaction.rs
@@ -226,7 +226,7 @@ impl TransactionClient {
}
}
-/// `TransactionVerifier` implementation is supplied by Iota to validate
+/// `TransactionVerifier` implementation is supplied by IOTA to validate
/// transactions in a block, before acceptance of the block.
pub trait TransactionVerifier: Send + Sync + 'static {
/// Determines if this batch can be voted on
diff --git a/crates/iota-adapter-transactional-tests/Cargo.toml b/crates/iota-adapter-transactional-tests/Cargo.toml
index cbbf533c426..1112a3474de 100644
--- a/crates/iota-adapter-transactional-tests/Cargo.toml
+++ b/crates/iota-adapter-transactional-tests/Cargo.toml
@@ -5,7 +5,7 @@ authors = ["IOTA Foundation "]
edition = "2021"
license = "Apache-2.0"
publish = false
-description = "Transactional tests for Iota Adapter"
+description = "Transactional tests for IOTA Adapter"
[dev-dependencies]
# external dependencies
diff --git a/crates/iota-adapter-transactional-tests/tests/entry_points/generic_by_ref_invalid.exp b/crates/iota-adapter-transactional-tests/tests/entry_points/generic_by_ref_invalid.exp
index 82813a5d23d..af712cd7028 100644
--- a/crates/iota-adapter-transactional-tests/tests/entry_points/generic_by_ref_invalid.exp
+++ b/crates/iota-adapter-transactional-tests/tests/entry_points/generic_by_ref_invalid.exp
@@ -5,20 +5,20 @@ A: object(0,0)
task 1, lines 9-12:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: &T0"), command: Some(0) } }
task 2, lines 14-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: &mut T0"), command: Some(0) } }
task 3, lines 19-22:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: &T0"), command: Some(0) } }
task 4, lines 24-27:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: &mut T0"), command: Some(0) } }
diff --git a/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_only.exp b/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_only.exp
index 10c7961e704..e676ae72cd3 100644
--- a/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_only.exp
+++ b/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_only.exp
@@ -2,7 +2,7 @@ processed 6 tasks
task 1, lines 7-38:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Enum X cannot have the 'key' ability. Enums cannot have the 'key' ability."), command: Some(0) } }
task 2, line 40:
diff --git a/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_only_uid_field.exp b/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_only_uid_field.exp
index 1bf0ae5713c..3289f2895a1 100644
--- a/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_only_uid_field.exp
+++ b/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_only_uid_field.exp
@@ -2,7 +2,7 @@ processed 6 tasks
task 1, lines 7-46:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Enum X cannot have the 'key' ability. Enums cannot have the 'key' ability."), command: Some(0) } }
task 2, line 48:
diff --git a/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_store.exp b/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_store.exp
index d35bae25d13..94035a4ef9d 100644
--- a/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_store.exp
+++ b/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_store.exp
@@ -2,7 +2,7 @@ processed 11 tasks
task 1, lines 7-89:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Enum X cannot have the 'key' ability. Enums cannot have the 'key' ability."), command: Some(0) } }
task 2, line 91:
diff --git a/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_store_uid_field.exp b/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_store_uid_field.exp
index 01175813bf2..c8fc8b16efb 100644
--- a/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_store_uid_field.exp
+++ b/crates/iota-adapter-transactional-tests/tests/enums/enum_with_key_store_uid_field.exp
@@ -2,7 +2,7 @@ processed 11 tasks
task 1, lines 7-105:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Enum X cannot have the 'key' ability. Enums cannot have the 'key' ability."), command: Some(0) } }
task 2, line 107:
diff --git a/crates/iota-adapter-transactional-tests/tests/init/entry_new.exp b/crates/iota-adapter-transactional-tests/tests/init/entry_new.exp
index 7a6336cfa87..e15ba170bd5 100644
--- a/crates/iota-adapter-transactional-tests/tests/init/entry_new.exp
+++ b/crates/iota-adapter-transactional-tests/tests/init/entry_new.exp
@@ -2,7 +2,7 @@ processed 3 tasks
task 1, lines 9-18:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m. 'init' cannot be 'entry'"), command: Some(0) } }
task 2, line 19:
diff --git a/crates/iota-adapter-transactional-tests/tests/publish/init_param.exp b/crates/iota-adapter-transactional-tests/tests/publish/init_param.exp
index 3e7498ef22e..056f62ab500 100644
--- a/crates/iota-adapter-transactional-tests/tests/publish/init_param.exp
+++ b/crates/iota-adapter-transactional-tests/tests/publish/init_param.exp
@@ -2,5 +2,5 @@ processed 2 tasks
task 1, lines 6-28:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last parameter for _::M1::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext, but found &mut iota::tx_context::TxContext"), command: Some(0) } }
diff --git a/crates/iota-adapter-transactional-tests/tests/publish/init_public.exp b/crates/iota-adapter-transactional-tests/tests/publish/init_public.exp
index bf37defa5ed..2d9e59a6aee 100644
--- a/crates/iota-adapter-transactional-tests/tests/publish/init_public.exp
+++ b/crates/iota-adapter-transactional-tests/tests/publish/init_public.exp
@@ -2,5 +2,5 @@ processed 2 tasks
task 1, lines 6-28:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::M1. 'init' function must be private"), command: Some(0) } }
diff --git a/crates/iota-adapter-transactional-tests/tests/publish/init_ret.exp b/crates/iota-adapter-transactional-tests/tests/publish/init_ret.exp
index 76c2847072f..efea232dc2f 100644
--- a/crates/iota-adapter-transactional-tests/tests/publish/init_ret.exp
+++ b/crates/iota-adapter-transactional-tests/tests/publish/init_ret.exp
@@ -2,5 +2,5 @@ processed 2 tasks
task 1, lines 6-28:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::M1, 'init' function cannot have return values"), command: Some(0) } }
diff --git a/crates/iota-adapter-transactional-tests/tests/transfer_object/transfer_coin.move b/crates/iota-adapter-transactional-tests/tests/transfer_object/transfer_coin.move
index 75b2057f9a8..3a5b6316760 100644
--- a/crates/iota-adapter-transactional-tests/tests/transfer_object/transfer_coin.move
+++ b/crates/iota-adapter-transactional-tests/tests/transfer_object/transfer_coin.move
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-// tests TransferObject with a IOTA coin
+// tests TransferObject with an IOTA coin
//# init --accounts A B C
diff --git a/crates/iota-adapter-transactional-tests/tests/upgrade/add_ability_during_upgrade.exp b/crates/iota-adapter-transactional-tests/tests/upgrade/add_ability_during_upgrade.exp
index 95e29002e95..72f21648323 100644
--- a/crates/iota-adapter-transactional-tests/tests/upgrade/add_ability_during_upgrade.exp
+++ b/crates/iota-adapter-transactional-tests/tests/upgrade/add_ability_during_upgrade.exp
@@ -41,7 +41,7 @@ Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { k
task 8, lines 46-49:
//# upgrade --package Test_V0 --upgrade-capability 1,1 --sender A
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("First field of struct Foo must be 'id', dummy_field found"), command: Some(1) } }
task 9, lines 51-57:
diff --git a/crates/iota-analytics-indexer/src/lib.rs b/crates/iota-analytics-indexer/src/lib.rs
index eaef0cbd712..b46ce94d72a 100644
--- a/crates/iota-analytics-indexer/src/lib.rs
+++ b/crates/iota-analytics-indexer/src/lib.rs
@@ -66,7 +66,7 @@ const WRAPPED_OBJECT_PREFIX: &str = "wrapped_object";
#[derive(Parser, Clone, Debug)]
#[clap(
- name = "Iota Analytics Indexer",
+ name = "IOTA Analytics Indexer",
about = "Indexer service to upload data for the analytics pipeline.",
rename_all = "kebab-case"
)]
diff --git a/crates/iota-aws-orchestrator/assets/plot.py b/crates/iota-aws-orchestrator/assets/plot.py
index a30f6f08511..17817417b5f 100644
--- a/crates/iota-aws-orchestrator/assets/plot.py
+++ b/crates/iota-aws-orchestrator/assets/plot.py
@@ -419,7 +419,7 @@ def plot_duration(self, file, precision):
if __name__ == "__main__":
parser = argparse.ArgumentParser(
- prog='Iota Plotter',
+ prog='IOTA Plotter',
description='Simple script to plot measurement data'
)
parser.add_argument(
diff --git a/crates/iota-aws-orchestrator/src/protocol/iota.rs b/crates/iota-aws-orchestrator/src/protocol/iota.rs
index 8eaf3931f43..ac3d3e88c3d 100644
--- a/crates/iota-aws-orchestrator/src/protocol/iota.rs
+++ b/crates/iota-aws-orchestrator/src/protocol/iota.rs
@@ -50,7 +50,7 @@ impl FromStr for IotaBenchmarkType {
impl BenchmarkType for IotaBenchmarkType {}
-/// All configurations information to run a Iota client or validator.
+/// All configurations information to run an IOTA client or validator.
pub struct IotaProtocol {
working_dir: PathBuf,
}
@@ -60,7 +60,7 @@ impl ProtocolCommands for IotaProtocol {
vec![
// Install typical iota dependencies.
"sudo apt-get -y install curl git-all clang cmake gcc libssl-dev pkg-config libclang-dev",
- // This dependency is missing from the Iota docs.
+ // This dependency is missing from the IOTA docs.
"sudo apt-get -y install libpq-dev",
]
}
@@ -214,7 +214,7 @@ impl ProtocolCommands for IotaProtocol {
impl IotaProtocol {
const CLIENT_METRICS_PORT: u16 = GenesisConfig::BENCHMARKS_PORT_OFFSET + 2000;
- /// Make a new instance of the Iota protocol commands generator.
+ /// Make a new instance of the IOTA protocol commands generator.
pub fn new(settings: &Settings) -> Self {
Self {
working_dir: [&settings.working_dir, &iota_config::IOTA_CONFIG_DIR.into()]
diff --git a/crates/iota-benchmark/src/in_memory_wallet.rs b/crates/iota-benchmark/src/in_memory_wallet.rs
index 62cffdfb7b7..40273a31e14 100644
--- a/crates/iota-benchmark/src/in_memory_wallet.rs
+++ b/crates/iota-benchmark/src/in_memory_wallet.rs
@@ -18,7 +18,7 @@ use crate::{
workloads::Gas,
};
-/// A Iota account and all of the objects it owns
+/// An IOTA account and all of the objects it owns
#[derive(Debug)]
pub struct IotaAccount {
key: Arc,
diff --git a/crates/iota-benchmark/src/options.rs b/crates/iota-benchmark/src/options.rs
index 7b7c36c92b3..995b262872b 100644
--- a/crates/iota-benchmark/src/options.rs
+++ b/crates/iota-benchmark/src/options.rs
@@ -12,7 +12,7 @@ use crate::drivers::Interval;
#[derive(Parser)]
#[clap(name = "Stress Testing Framework")]
pub struct Opts {
- /// Size of the Iota committee.
+ /// Size of the IOTA committee.
#[clap(long, default_value = "4", global = true)]
pub committee_size: u64,
/// Num of accounts to use for transfer objects
diff --git a/crates/iota-bridge-cli/src/lib.rs b/crates/iota-bridge-cli/src/lib.rs
index 74392f8977c..67a2706c776 100644
--- a/crates/iota-bridge-cli/src/lib.rs
+++ b/crates/iota-bridge-cli/src/lib.rs
@@ -113,7 +113,7 @@ pub enum BridgeCommand {
#[clap(long = "iota-rpc-url")]
iota_rpc_url: String,
},
- /// View current status of Iota bridge
+ /// View current status of IOTA bridge
#[clap(name = "view-iota-bridge")]
ViewIotaBridge {
#[clap(long = "iota-rpc-url")]
@@ -379,7 +379,7 @@ pub fn select_contract_address(
#[derive(Clone, Debug, Deserialize, Serialize)]
#[serde(rename_all = "kebab-case")]
pub struct BridgeCliConfig {
- /// Rpc url for Iota fullnode, used for query stuff and submit transactions.
+ /// Rpc url for IOTA fullnode, used for query stuff and submit transactions.
pub iota_rpc_url: String,
/// Rpc url for Eth fullnode, used for query stuff.
pub eth_rpc_url: String,
@@ -391,7 +391,7 @@ pub struct BridgeCliConfig {
/// - Base64 encoded `privkey` for Raw key
/// - Hex encoded `privkey` for Raw key
/// At least one of `iota_key_path` or `eth_key_path` must be provided.
- /// If only one is provided, it will be used for both Iota and Eth.
+ /// If only one is provided, it will be used for both IOTA and Eth.
pub iota_key_path: Option,
/// See `iota_key_path`. Must be Secp256k1 key.
pub eth_key_path: Option,
@@ -400,7 +400,7 @@ pub struct BridgeCliConfig {
impl Config for BridgeCliConfig {}
pub struct LoadedBridgeCliConfig {
- /// Rpc url for Iota fullnode, used for query stuff and submit transactions.
+ /// Rpc url for IOTA fullnode, used for query stuff and submit transactions.
pub iota_rpc_url: String,
/// Rpc url for Eth fullnode, used for query stuff.
pub eth_rpc_url: String,
@@ -412,7 +412,7 @@ pub struct LoadedBridgeCliConfig {
pub eth_bridge_config_proxy_address: EthAddress,
/// Proxy address for BridgeLimiter deployed on Eth
pub eth_bridge_limiter_proxy_address: EthAddress,
- /// Key pair for Iota operations
+ /// Key pair for IOTA operations
iota_key: IotaKeyPair,
/// Key pair for Eth operations, must be Secp256k1 key
eth_signer: EthSigner,
@@ -469,7 +469,7 @@ impl LoadedBridgeCliConfig {
let eth_address = eth_signer.address();
let eth_chain_id = provider.get_chainid().await?;
let iota_address = IotaAddress::from(&iota_key.public());
- println!("Using Iota address: {:?}", iota_address);
+ println!("Using IOTA address: {:?}", iota_address);
println!("Using Eth address: {:?}", eth_address);
println!("Using Eth chain: {:?}", eth_chain_id);
@@ -504,7 +504,7 @@ impl LoadedBridgeCliConfig {
.get_coins(iota_client_address, None, None, None)
.await?
.data;
- // TODO: is 5 Iota a good number?
+ // TODO: is 5 IOTA a good number?
let gas = gases
.into_iter()
.find(|coin| coin.balance >= 5_000_000_000)
@@ -665,7 +665,7 @@ async fn deposit_on_iota(
);
let signed_tx = Transaction::from_data(tx_data, vec![sig]);
let tx_digest = *signed_tx.digest();
- info!(?tx_digest, "Sending deposit transction to Iota.");
+ info!(?tx_digest, "Sending deposit transction to IOTA.");
let resp = iota_bridge_client
.execute_transaction_block_with_effects(signed_tx)
.await
@@ -715,7 +715,7 @@ async fn claim_on_eth(
let message = eth_iota_bridge::Message::from(parsed_message);
let tx = eth_iota_bridge.transfer_bridged_tokens_with_signatures(signatures, message);
let _eth_claim_tx_receipt = tx.send().await.unwrap().await.unwrap().unwrap();
- info!("Iota to Eth bridge transfer claimed");
+ info!("IOTA to Eth bridge transfer claimed");
Ok(())
}
diff --git a/crates/iota-bridge-cli/src/main.rs b/crates/iota-bridge-cli/src/main.rs
index ed90c1d7c2e..0a4f1b44304 100644
--- a/crates/iota-bridge-cli/src/main.rs
+++ b/crates/iota-bridge-cli/src/main.rs
@@ -99,7 +99,7 @@ async fn main() -> anyhow::Result<()> {
);
let agg = BridgeAuthorityAggregator::new(bridge_committee);
- // Handle Iota Side
+ // Handle IOTA Side
if chain_id.is_iota_chain() {
let iota_chain_id = BridgeChainId::try_from(bridge_summary.chain_id).unwrap();
assert_eq!(
@@ -109,7 +109,7 @@ async fn main() -> anyhow::Result<()> {
);
// Create BridgeAction
let iota_action = make_action(iota_chain_id, &cmd);
- println!("Action to execute on Iota: {:?}", iota_action);
+ println!("Action to execute on IOTA: {:?}", iota_action);
let certified_action = agg
.request_committee_signatures(iota_action)
.await
@@ -144,10 +144,10 @@ async fn main() -> anyhow::Result<()> {
.await
.expect("Failed to execute transaction block with effects");
if resp.status_ok().unwrap() {
- println!("Iota Transaction succeeded: {:?}", resp.digest);
+ println!("IOTA Transaction succeeded: {:?}", resp.digest);
} else {
println!(
- "Iota Transaction failed: {:?}. Effects: {:?}",
+ "IOTA Transaction failed: {:?}. Effects: {:?}",
resp.digest, resp.effects
);
}
diff --git a/crates/iota-bridge-indexer/config.yaml b/crates/iota-bridge-indexer/config.yaml
index 5ce78b55a94..2363925284f 100644
--- a/crates/iota-bridge-indexer/config.yaml
+++ b/crates/iota-bridge-indexer/config.yaml
@@ -12,7 +12,7 @@
# concurrency: 1
# Bridge genesis checkpoint in IOTA, for testnet = 43917829
# bridge_genesis_checkpoint:
-# Ethereum to Iota bridge contract address
+# Ethereum to IOTA bridge contract address
# eth_iota_bridge_contract_address:
# Starting block number
# start_block:
@@ -23,4 +23,4 @@
# checkpoint size of each backfill worker, use 432000 for 1 worker per day, assume 5 checkpoint per second
# back_fill_lot_size:
# Optional starting checkpoint for realtime ingestion task
-# resume_from_checkpoint:
+# resume_from_checkpoint:
diff --git a/crates/iota-bridge-indexer/src/iota_bridge_indexer.rs b/crates/iota-bridge-indexer/src/iota_bridge_indexer.rs
index a1f6be3d743..82673332753 100644
--- a/crates/iota-bridge-indexer/src/iota_bridge_indexer.rs
+++ b/crates/iota-bridge-indexer/src/iota_bridge_indexer.rs
@@ -234,7 +234,7 @@ fn process_iota_event(
Ok(if ev.type_.address == BRIDGE_ADDRESS {
match ev.type_.name.as_str() {
"TokenDepositedEvent" => {
- info!("Observed Iota Deposit {:?}", ev);
+ info!("Observed IOTA Deposit {:?}", ev);
// todo: metrics.total_iota_token_deposited.inc();
let move_event: MoveTokenDepositedEvent = bcs::from_bytes(&ev.contents)?;
Some(ProcessedTxnData::TokenTransfer(TokenTransfer {
@@ -257,7 +257,7 @@ fn process_iota_event(
}))
}
"TokenTransferApproved" => {
- info!("Observed Iota Approval {:?}", ev);
+ info!("Observed IOTA Approval {:?}", ev);
// todo: metrics.total_iota_token_transfer_approved.inc();
let event: MoveTokenTransferApproved = bcs::from_bytes(&ev.contents)?;
Some(ProcessedTxnData::TokenTransfer(TokenTransfer {
@@ -274,7 +274,7 @@ fn process_iota_event(
}))
}
"TokenTransferClaimed" => {
- info!("Observed Iota Claim {:?}", ev);
+ info!("Observed IOTA Claim {:?}", ev);
// todo: metrics.total_iota_token_transfer_claimed.inc();
let event: MoveTokenTransferClaimed = bcs::from_bytes(&ev.contents)?;
Some(ProcessedTxnData::TokenTransfer(TokenTransfer {
diff --git a/crates/iota-bridge-indexer/src/iota_transaction_handler.rs b/crates/iota-bridge-indexer/src/iota_transaction_handler.rs
index 5317677a84c..30d88b05c17 100644
--- a/crates/iota-bridge-indexer/src/iota_transaction_handler.rs
+++ b/crates/iota-bridge-indexer/src/iota_transaction_handler.rs
@@ -92,7 +92,7 @@ pub fn into_token_transfers(
}
match ev.type_.name.as_str() {
"TokenDepositedEvent" => {
- info!("Observed Iota Deposit {:?}", ev);
+ info!("Observed IOTA Deposit {:?}", ev);
metrics.total_iota_token_deposited.inc();
let move_event: MoveTokenDepositedEvent = bcs::from_bytes(&ev.bcs)?;
transfers.push(ProcessedTxnData::TokenTransfer(TokenTransfer {
@@ -115,7 +115,7 @@ pub fn into_token_transfers(
}));
}
"TokenTransferApproved" => {
- info!("Observed Iota Approval {:?}", ev);
+ info!("Observed IOTA Approval {:?}", ev);
metrics.total_iota_token_transfer_approved.inc();
let event: MoveTokenTransferApproved = bcs::from_bytes(&ev.bcs)?;
transfers.push(ProcessedTxnData::TokenTransfer(TokenTransfer {
@@ -132,7 +132,7 @@ pub fn into_token_transfers(
}));
}
"TokenTransferClaimed" => {
- info!("Observed Iota Claim {:?}", ev);
+ info!("Observed IOTA Claim {:?}", ev);
metrics.total_iota_token_transfer_claimed.inc();
let event: MoveTokenTransferClaimed = bcs::from_bytes(&ev.bcs)?;
transfers.push(ProcessedTxnData::TokenTransfer(TokenTransfer {
diff --git a/crates/iota-bridge/src/action_executor.rs b/crates/iota-bridge/src/action_executor.rs
index a1070ae3aab..75b6e1a268d 100644
--- a/crates/iota-bridge/src/action_executor.rs
+++ b/crates/iota-bridge/src/action_executor.rs
@@ -485,7 +485,7 @@ where
return;
}
- info!("Building Iota transaction");
+ info!("Building IOTA transaction");
let rgp = iota_client.get_reference_gas_price_until_success().await;
let tx_data = match build_iota_transaction(
*iota_address,
@@ -527,7 +527,7 @@ where
return;
}
- info!(?tx_digest, ?gas_object_ref, "Sending transaction to Iota");
+ info!(?tx_digest, ?gas_object_ref, "Sending transaction to IOTA");
match iota_client
.execute_transaction_block_with_effects(signed_tx)
.await
@@ -541,7 +541,7 @@ where
error!(
?action_key,
?tx_digest,
- "Iota transaction failed at signing: {err:?}"
+ "IOTA transaction failed at signing: {err:?}"
);
metrics.err_iota_transaction_submission.inc();
let metrics_clone = metrics.clone();
@@ -599,7 +599,7 @@ where
"Expected TokenTransferAlreadyClaimed, TokenTransferClaimed, TokenTransferApproved or TokenTransferAlreadyApproved event but got: {:?}",
events,
);
- info!(?tx_digest, "Iota transaction executed successfully");
+ info!(?tx_digest, "IOTA transaction executed successfully");
store
.remove_pending_actions(&[action.digest()])
.unwrap_or_else(|e| {
@@ -617,7 +617,7 @@ where
metrics.err_iota_transaction_execution.inc();
error!(
?tx_digest,
- "Manual intervention is needed. Iota transaction executed and failed with error: {error:?}"
+ "Manual intervention is needed. IOTA transaction executed and failed with error: {error:?}"
);
}
}
diff --git a/crates/iota-bridge/src/config.rs b/crates/iota-bridge/src/config.rs
index 1714fe4270a..f1f37a81419 100644
--- a/crates/iota-bridge/src/config.rs
+++ b/crates/iota-bridge/src/config.rs
@@ -67,9 +67,9 @@ pub struct EthConfig {
#[derive(Clone, Debug, Deserialize, Serialize)]
#[serde(rename_all = "kebab-case")]
pub struct IotaConfig {
- /// Rpc url for Iota fullnode, used for query stuff and submit transactions.
+ /// Rpc url for IOTA fullnode, used for query stuff and submit transactions.
pub iota_rpc_url: String,
- /// The expected BridgeChainId on Iota side.
+ /// The expected BridgeChainId on IOTA side.
pub iota_bridge_chain_id: u8,
/// Path of the file where bridge client key (any IotaKeyPair) is stored.
/// If `run_client` is true, and this is None, then use
@@ -114,7 +114,7 @@ pub struct BridgeNodeConfig {
/// A list of approved governance actions. Action in this list will be
/// signed when requested by client.
pub approved_governance_actions: Vec,
- /// Iota configuration
+ /// IOTA configuration
pub iota: IotaConfig,
/// Eth configuration
pub eth: EthConfig,
@@ -132,7 +132,7 @@ impl BridgeNodeConfig {
BridgeChainId::try_from(self.eth.eth_bridge_chain_id)?,
) {
return Err(anyhow!(
- "Route between Iota chain id {} and Eth chain id {} is not valid",
+ "Route between IOTA chain id {} and Eth chain id {} is not valid",
self.iota.iota_bridge_chain_id,
self.eth.eth_bridge_chain_id,
));
@@ -308,12 +308,12 @@ impl BridgeNodeConfig {
Some(path) => read_key(path, false),
}?;
- // If bridge chain id is Iota Mainent or Testnet, we expect to see chain
+ // If bridge chain id is IOTA Mainent or Testnet, we expect to see chain
// identifier to match accordingly.
let iota_identifier = iota_client
.get_chain_identifier()
.await
- .map_err(|e| anyhow!("Error getting chain identifier from Iota: {:?}", e))?;
+ .map_err(|e| anyhow!("Error getting chain identifier from IOTA: {:?}", e))?;
if self.iota.iota_bridge_chain_id == BridgeChainId::IotaMainnet as u8
&& iota_identifier != get_mainnet_chain_identifier().to_string()
{
@@ -333,7 +333,7 @@ impl BridgeNodeConfig {
);
}
info!(
- "Connected to Iota chain: {}, Bridge chain id: {}",
+ "Connected to IOTA chain: {}, Bridge chain id: {}",
iota_identifier, self.iota.iota_bridge_chain_id,
);
@@ -428,11 +428,11 @@ pub async fn pick_highest_balance_coin(
})
.await;
if highest_balance_coin.is_none() {
- return Err(anyhow!("No Iota coins found for address {:?}", address));
+ return Err(anyhow!("No IOTA coins found for address {:?}", address));
}
if highest_balance < minimal_amount {
return Err(anyhow!(
- "Found no single coin that has >= {} balance Iota for address {:?}",
+ "Found no single coin that has >= {} balance IOTA for address {:?}",
minimal_amount,
address,
));
diff --git a/crates/iota-bridge/src/e2e_tests/basic.rs b/crates/iota-bridge/src/e2e_tests/basic.rs
index d752a8322f1..3b4e3ebe738 100644
--- a/crates/iota-bridge/src/e2e_tests/basic.rs
+++ b/crates/iota-bridge/src/e2e_tests/basic.rs
@@ -152,7 +152,7 @@ async fn test_bridge_from_eth_to_iota_to_eth() {
let call = eth_iota_bridge.transfer_bridged_tokens_with_signatures(signatures, message);
let eth_claim_tx_receipt = send_eth_tx_and_get_tx_receipt(call).await;
assert_eq!(eth_claim_tx_receipt.status.unwrap().as_u64(), 1);
- info!("Iota to Eth bridge transfer claimed");
+ info!("IOTA to Eth bridge transfer claimed");
// Assert eth_address_1 has received ETH
assert_eq!(
eth_signer.get_balance(eth_address_1, None).await.unwrap(),
@@ -160,7 +160,7 @@ async fn test_bridge_from_eth_to_iota_to_eth() {
);
}
-// Test add new coins on both Iota and Eth
+// Test add new coins on both IOTA and Eth
// Also test bridge node handling `NewTokenEvent``
#[tokio::test(flavor = "multi_thread", worker_threads = 8)]
#[ignore = "https://github.com/iotaledger/iota/issues/3224"]
@@ -175,7 +175,7 @@ async fn test_add_new_coins_on_iota_and_eth() {
let bridge_arg = bridge_test_cluster.get_mut_bridge_arg().await.unwrap();
- // Register tokens on Iota
+ // Register tokens on IOTA
let token_id = 5;
let token_iota_decimal = 9; // this needs to match ka.move
let token_price = 10000;
@@ -258,7 +258,7 @@ async fn test_add_new_coins_on_iota_and_eth() {
_ => false,
}
}));
- info!("Approved new token on Iota");
+ info!("Approved new token on IOTA");
// Assert new token is correctly added
let treasury_summary = bridge_test_cluster
@@ -456,7 +456,7 @@ pub async fn initiate_bridge_erc20_to_iota(
.tap_ok(|_| {
info!(
nonce,
- token_id, amount_u64, "Eth to Iota bridge transfer claimed"
+ token_id, amount_u64, "Eth to IOTA bridge transfer claimed"
);
})
}
@@ -477,7 +477,7 @@ pub async fn initiate_bridge_eth_to_iota(
let eth_chain_id = bridge_test_cluster.eth_chain_id();
let token_id = TOKEN_ID_ETH;
- let iota_amount = (U256::from(amount) * U256::exp10(8)).as_u64(); // DP for Ether on Iota
+ let iota_amount = (U256::from(amount) * U256::exp10(8)).as_u64(); // DP for Ether on IOTA
let eth_tx = deposit_native_eth_to_sol_contract(
ð_signer,
@@ -517,7 +517,7 @@ pub async fn initiate_bridge_eth_to_iota(
)
.await
.tap_ok(|_| {
- info!("Eth to Iota bridge transfer claimed");
+ info!("Eth to IOTA bridge transfer claimed");
})
}
@@ -554,7 +554,7 @@ pub async fn initiate_bridge_iota_to_eth(
{
Ok(resp) => {
if !resp.status_ok().unwrap() {
- return Err(anyhow!("Iota TX error"));
+ return Err(anyhow!("IOTA TX error"));
} else {
resp
}
@@ -604,7 +604,7 @@ pub async fn initiate_bridge_iota_to_eth(
)
.await
.unwrap();
- info!("Iota to Eth bridge transfer approved.");
+ info!("IOTA to Eth bridge transfer approved.");
Ok(bridge_event)
}
diff --git a/crates/iota-bridge/src/e2e_tests/complex.rs b/crates/iota-bridge/src/e2e_tests/complex.rs
index c258002c824..76ab551688c 100644
--- a/crates/iota-bridge/src/e2e_tests/complex.rs
+++ b/crates/iota-bridge/src/e2e_tests/complex.rs
@@ -62,7 +62,7 @@ async fn test_iota_bridge_paused() {
initiate_bridge_eth_to_iota(&bridge_test_cluster, 10, 0)
.await
.unwrap();
- // verify Eth was transferred to Iota address
+ // verify Eth was transferred to IOTA address
let eth_coin_type = iota_token_type_tags.get(&TOKEN_ID_ETH).unwrap();
let eth_coin = bridge_client
.iota_client()
@@ -111,10 +111,10 @@ async fn test_iota_bridge_paused() {
// verify bridge paused
assert!(bridge_client.get_bridge_summary().await.unwrap().is_frozen);
- // Transfer from eth to iota should fail on Iota
+ // Transfer from eth to iota should fail on IOTA
let eth_to_iota_bridge_action = initiate_bridge_eth_to_iota(&bridge_test_cluster, 10, 1).await;
assert!(eth_to_iota_bridge_action.is_err());
- // message should not be recorded on Iota when the bridge is paused
+ // message should not be recorded on IOTA when the bridge is paused
let res = bridge_test_cluster
.bridge_client()
.get_token_transfer_action_onchain_status_until_success(
@@ -123,7 +123,7 @@ async fn test_iota_bridge_paused() {
)
.await;
assert_eq!(BridgeActionStatus::NotFound, res);
- // Transfer from Iota to eth should fail
+ // Transfer from IOTA to eth should fail
let iota_to_eth_bridge_action = initiate_bridge_iota_to_eth(
&bridge_test_cluster,
EthAddress::random(),
diff --git a/crates/iota-bridge/src/error.rs b/crates/iota-bridge/src/error.rs
index de290334a58..cd344de337c 100644
--- a/crates/iota-bridge/src/error.rs
+++ b/crates/iota-bridge/src/error.rs
@@ -18,7 +18,7 @@ pub enum BridgeError {
NoBridgeEventsInTxPosition,
// Found a bridge event but not in a recognized Eth bridge contract
BridgeEventInUnrecognizedEthContract,
- // Found a bridge event but not in a recognized Iota bridge package
+ // Found a bridge event but not in a recognized IOTA bridge package
BridgeEventInUnrecognizedIotaPackage,
// Found BridgeEvent but not BridgeAction
BridgeEventNotActionable,
@@ -60,7 +60,7 @@ pub enum BridgeError {
AuthorityUrlInvalid,
// Action is not token transfer
ActionIsNotTokenTransferAction,
- // Iota transaction failure due to generic error
+ // IOTA transaction failure due to generic error
IotaTxFailureGeneric(String),
// Zero value bridge transfer should not be allowed
ZeroValueBridgeTransfer(String),
diff --git a/crates/iota-bridge/src/events.rs b/crates/iota-bridge/src/events.rs
index 101db3aca1c..7d6ae66f936 100644
--- a/crates/iota-bridge/src/events.rs
+++ b/crates/iota-bridge/src/events.rs
@@ -221,7 +221,7 @@ pub struct EmittedIotaToEthTokenBridgeV1 {
pub iota_address: IotaAddress,
pub eth_address: EthAddress,
pub token_id: u8,
- // The amount of tokens deposited with decimal points on Iota side
+ // The amount of tokens deposited with decimal points on IOTA side
pub amount_iota_adjusted: u64,
}
diff --git a/crates/iota-bridge/src/iota_client.rs b/crates/iota-bridge/src/iota_client.rs
index 63da0c725c8..3d7ed87baf3 100644
--- a/crates/iota-bridge/src/iota_client.rs
+++ b/crates/iota-bridge/src/iota_client.rs
@@ -58,7 +58,7 @@ impl IotaBridgeClient {
.build(rpc_url)
.await
.map_err(|e| {
- anyhow!("Can't establish connection with Iota Rpc {rpc_url}. Error: {e}")
+ anyhow!("Can't establish connection with IOTA Rpc {rpc_url}. Error: {e}")
})?;
let self_ = Self { inner };
self_.describe().await?;
@@ -132,7 +132,7 @@ where
Ok(events)
}
- /// Returns BridgeAction from a Iota Transaction with transaction hash
+ /// Returns BridgeAction from an IOTA Transaction with transaction hash
/// and the event index. If event is declared in an unrecognized
/// package, return error.
pub async fn get_bridge_action_by_tx_digest_and_event_idx_maybe(
@@ -792,7 +792,7 @@ mod tests {
.await;
let id_token_map = iota_client.get_token_id_map().await.unwrap();
- // 1. Create a Eth -> Iota Transfer (recipient is sender address), approve with
+ // 1. Create a Eth -> IOTA Transfer (recipient is sender address), approve with
// validator secrets and assert its status to be Claimed
let action =
get_test_eth_to_iota_bridge_action(None, Some(usdc_amount), Some(sender), None);
@@ -818,7 +818,7 @@ mod tests {
.unwrap();
assert_eq!(status, BridgeActionStatus::Claimed);
- // 2. Create a Iota -> Eth Transfer, approve with validator secrets and assert
+ // 2. Create an IOTA -> Eth Transfer, approve with validator secrets and assert
// its status to be Approved
// We need to actually send tokens to bridge to initialize the record.
let eth_recv_address = EthAddress::random();
diff --git a/crates/iota-bridge/src/iota_mock_client.rs b/crates/iota-bridge/src/iota_mock_client.rs
index acf4fa4fd27..c7738276cda 100644
--- a/crates/iota-bridge/src/iota_mock_client.rs
+++ b/crates/iota-bridge/src/iota_mock_client.rs
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-//! A mock implementation of Iota JSON-RPC client.
+//! A mock implementation of IOTA JSON-RPC client.
use std::{
collections::{HashMap, VecDeque},
diff --git a/crates/iota-bridge/src/iota_syncer.rs b/crates/iota-bridge/src/iota_syncer.rs
index dfc7a40cb85..fbfaa506cdf 100644
--- a/crates/iota-bridge/src/iota_syncer.rs
+++ b/crates/iota-bridge/src/iota_syncer.rs
@@ -3,7 +3,7 @@
// SPDX-License-Identifier: Apache-2.0
//! The IotaSyncer module is responsible for synchronizing Events emitted
-//! on Iota blockchain from concerned modules of bridge package 0x9.
+//! on IOTA blockchain from concerned modules of bridge package 0x9.
use std::{collections::HashMap, sync::Arc};
@@ -106,11 +106,11 @@ where
events_sender
.send((module.clone(), events.data))
.await
- .expect("All Iota event channel receivers are closed");
+ .expect("All IOTA event channel receivers are closed");
if let Some(next) = events.next_cursor {
cursor = Some(next);
}
- tracing::info!(?module, ?cursor, "Observed {len} new Iota events");
+ tracing::info!(?module, ?cursor, "Observed {len} new IOTA events");
}
}
}
diff --git a/crates/iota-bridge/src/iota_transaction_builder.rs b/crates/iota-bridge/src/iota_transaction_builder.rs
index 550f5d83d74..c39891ab2fc 100644
--- a/crates/iota-bridge/src/iota_transaction_builder.rs
+++ b/crates/iota-bridge/src/iota_transaction_builder.rs
@@ -80,7 +80,7 @@ pub fn build_iota_transaction(
rgp,
),
BridgeAction::EvmContractUpgradeAction(_) => {
- // It does not need a Iota tranaction to execute EVM contract upgrade
+ // It does not need an IOTA tranaction to execute EVM contract upgrade
unreachable!()
}
BridgeAction::AddTokensOnIotaAction(_) => build_add_tokens_on_iota_transaction(
@@ -91,7 +91,7 @@ pub fn build_iota_transaction(
rgp,
),
BridgeAction::AddTokensOnEvmAction(_) => {
- // It does not need a Iota tranaction to add tokens on EVM
+ // It does not need an IOTA tranaction to add tokens on EVM
unreachable!()
}
}
@@ -672,7 +672,7 @@ mod tests {
.await;
let id_token_map = iota_client.get_token_id_map().await.unwrap();
- // 1. Test Eth -> Iota Transfer approval
+ // 1. Test Eth -> IOTA Transfer approval
let action =
get_test_eth_to_iota_bridge_action(None, Some(usdc_amount), Some(sender), None);
// `approve_action_with_validator_secrets` covers transaction building
@@ -687,7 +687,7 @@ mod tests {
.await
.unwrap();
- // 2. Test Iota -> Eth Transfer approval
+ // 2. Test IOTA -> Eth Transfer approval
let bridge_event = bridge_token(
context,
EthAddress::random(),
diff --git a/crates/iota-bridge/src/orchestrator.rs b/crates/iota-bridge/src/orchestrator.rs
index 8604d0fe28d..c44e162f5bb 100644
--- a/crates/iota-bridge/src/orchestrator.rs
+++ b/crates/iota-bridge/src/orchestrator.rs
@@ -3,7 +3,7 @@
// SPDX-License-Identifier: Apache-2.0
//! `BridgeOrchestrator` is the component that:
-//! 1. monitors Iota and Ethereum events with the help of `IotaSyncer` and
+//! 1. monitors IOTA and Ethereum events with the help of `IotaSyncer` and
//! `EthSyncer`
//! 2. updates WAL table and cursor tables
//! 2. hands actions to `BridgeExecutor` for execution
@@ -117,7 +117,7 @@ where
if events.is_empty() {
continue;
}
- info!("Received {} Iota events: {:?}", events.len(), events);
+ info!("Received {} IOTA events: {:?}", events.len(), events);
metrics
.iota_watcher_received_events
.inc_by(events.len() as u64);
@@ -134,7 +134,7 @@ where
}
Err(e) => {
panic!(
- "Iota Event could not be deserialzed to IotaBridgeEvent: {:?}",
+ "IOTA Event could not be deserialzed to IotaBridgeEvent: {:?}",
e
);
}
@@ -147,12 +147,12 @@ where
if opt_bridge_event.is_none() {
// TODO: we probably should not miss any events, log for now.
metrics.iota_watcher_unrecognized_events.inc();
- error!("Iota event not recognized: {:?}", iota_event);
+ error!("IOTA event not recognized: {:?}", iota_event);
continue;
}
// Unwrap safe: checked above
let bridge_event: IotaBridgeEvent = opt_bridge_event.unwrap();
- info!("Observed Iota bridge event: {:?}", bridge_event);
+ info!("Observed IOTA bridge event: {:?}", bridge_event);
// Send event to monitor
monitor_tx
@@ -169,7 +169,7 @@ where
if !actions.is_empty() {
info!(
- "Received {} actions from Iota: {:?}",
+ "Received {} actions from IOTA: {:?}",
actions.len(),
actions
);
@@ -193,7 +193,7 @@ where
.update_iota_event_cursor(identifier, cursor)
.expect("Store operation should not fail");
}
- panic!("Iota event channel was closed unexpectedly");
+ panic!("IOTA event channel was closed unexpectedly");
}
async fn run_eth_watcher(
diff --git a/crates/iota-bridge/src/server/handler.rs b/crates/iota-bridge/src/server/handler.rs
index 951a6869b73..b1292bf3e44 100644
--- a/crates/iota-bridge/src/server/handler.rs
+++ b/crates/iota-bridge/src/server/handler.rs
@@ -28,7 +28,7 @@ use crate::{
#[async_trait]
pub trait BridgeRequestHandlerTrait {
/// Handles a request to sign a BridgeAction that bridges assets
- /// from Ethereum to Iota. The inputs are a transaction hash on Ethereum
+ /// from Ethereum to IOTA. The inputs are a transaction hash on Ethereum
/// that emitted the bridge event and the Event index in that transaction
async fn handle_eth_tx_hash(
&self,
@@ -36,7 +36,7 @@ pub trait BridgeRequestHandlerTrait {
event_idx: u16,
) -> Result, BridgeError>;
/// Handles a request to sign a BridgeAction that bridges assets
- /// from Iota to Ethereum. The inputs are a transaction digest on Iota
+ /// from IOTA to Ethereum. The inputs are a transaction digest on IOTA
/// that emitted the bridge event and the Event index in that transaction
async fn handle_iota_tx_digest(
&self,
@@ -80,7 +80,7 @@ where
self.iota_client
.get_bridge_action_by_tx_digest_and_event_idx_maybe(&tx_digest, event_idx)
.await
- .tap_ok(|action| info!("Iota action found: {:?}", action))
+ .tap_ok(|action| info!("IOTA action found: {:?}", action))
}
}
diff --git a/crates/iota-bridge/src/server/mod.rs b/crates/iota-bridge/src/server/mod.rs
index 2085b4cc19e..a6affca3caf 100644
--- a/crates/iota-bridge/src/server/mod.rs
+++ b/crates/iota-bridge/src/server/mod.rs
@@ -424,7 +424,7 @@ async fn handle_add_tokens_on_iota(
if !chain_id.is_iota_chain() {
return Err(BridgeError::InvalidBridgeClientRequest(
- "handle_add_tokens_on_iota only expects Iota chain id".to_string(),
+ "handle_add_tokens_on_iota only expects IOTA chain id".to_string(),
));
}
@@ -505,7 +505,7 @@ async fn handle_add_tokens_on_evm(
})?;
if chain_id.is_iota_chain() {
return Err(BridgeError::InvalidBridgeClientRequest(
- "handle_add_tokens_on_evm does not expect Iota chain id".to_string(),
+ "handle_add_tokens_on_evm does not expect IOTA chain id".to_string(),
));
}
diff --git a/crates/iota-bridge/src/test_utils.rs b/crates/iota-bridge/src/test_utils.rs
index 5a4bda4f769..00a02d95d64 100644
--- a/crates/iota-bridge/src/test_utils.rs
+++ b/crates/iota-bridge/src/test_utils.rs
@@ -336,7 +336,7 @@ pub fn get_certified_action_with_validator_secrets(
/// Approve a bridge action with the given validator secrets. Return the
/// newly created token object reference if `expected_token_receiver` is Some
-/// (only relevant when the action is eth -> Iota transfer),
+/// (only relevant when the action is eth -> IOTA transfer),
/// Otherwise return None.
/// Note: for iota -> eth transfers, the actual deposit needs to be recorded.
/// Use `bridge_token` to do it.
diff --git a/crates/iota-bridge/src/types.rs b/crates/iota-bridge/src/types.rs
index 334a679ef02..2b1e669a1b1 100644
--- a/crates/iota-bridge/src/types.rs
+++ b/crates/iota-bridge/src/types.rs
@@ -343,7 +343,7 @@ pub struct AddTokensOnEvmAction {
#[derive(Debug, Clone, Serialize, Deserialize, PartialEq, Eq, Hash)]
#[enum_dispatch(BridgeMessageEncoding)]
pub enum BridgeAction {
- /// Iota to Eth bridge action
+ /// IOTA to Eth bridge action
IotaToEthBridgeAction(IotaToEthBridgeAction),
/// Eth to iota bridge action
EthToIotaBridgeAction(EthToIotaBridgeAction),
diff --git a/crates/iota-bridge/src/utils.rs b/crates/iota-bridge/src/utils.rs
index 91b9549ddfe..4f342e6c4ff 100644
--- a/crates/iota-bridge/src/utils.rs
+++ b/crates/iota-bridge/src/utils.rs
@@ -67,7 +67,7 @@ pub fn generate_bridge_authority_key_and_write_to_file(
);
let iota_address = IotaAddress::from(&kp.public);
println!(
- "Corresponding Iota address by this ecdsa key: {:?}",
+ "Corresponding IOTA address by this ecdsa key: {:?}",
iota_address
);
let base64_encoded = kp.encode_base64();
@@ -94,7 +94,7 @@ pub fn generate_bridge_client_key_and_write_to_file(
IotaKeyPair::from(kp)
};
let iota_address = IotaAddress::from(&kp.public());
- println!("Corresponding Iota address by this key: {:?}", iota_address);
+ println!("Corresponding IOTA address by this key: {:?}", iota_address);
let contents = kp.encode_base64();
std::fs::write(path, contents)
@@ -168,7 +168,7 @@ pub fn examine_key(path: &PathBuf, is_validator_key: bool) -> Result<(), anyhow:
kp.public().as_bytes().to_vec()
}
};
- println!("Corresponding Iota address: {:?}", iota_address);
+ println!("Corresponding IOTA address: {:?}", iota_address);
println!("Corresponding PublicKey: {:?}", Hex::encode(pubkey));
Ok(())
}
diff --git a/crates/iota-cluster-test/src/cluster.rs b/crates/iota-cluster-test/src/cluster.rs
index edf61868092..14375a8ae6c 100644
--- a/crates/iota-cluster-test/src/cluster.rs
+++ b/crates/iota-cluster-test/src/cluster.rs
@@ -177,7 +177,7 @@ impl Cluster for LocalNewCluster {
// Check if we already have a config directory that is passed
if let Some(config_dir) = options.config_dir.clone() {
assert!(options.epoch_duration_ms.is_none());
- // Load the config of the Iota authority.
+ // Load the config of the IOTA authority.
let network_config_path = config_dir.join(IOTA_NETWORK_CONFIG);
let NetworkConfigLight {
validator_configs,
@@ -185,7 +185,7 @@ impl Cluster for LocalNewCluster {
committee_with_network: _,
} = PersistedConfig::read(&network_config_path).map_err(|err| {
err.context(format!(
- "Cannot open Iota network config file at {:?}",
+ "Cannot open IOTA network config file at {:?}",
network_config_path
))
})?;
diff --git a/crates/iota-cluster-test/src/helper.rs b/crates/iota-cluster-test/src/helper.rs
index c25a6854e8e..2d60b4683f3 100644
--- a/crates/iota-cluster-test/src/helper.rs
+++ b/crates/iota-cluster-test/src/helper.rs
@@ -12,7 +12,7 @@ use iota_types::{
use move_core_types::language_storage::TypeTag;
use tracing::{debug, trace};
-/// A util struct that helps verify Iota Object.
+/// A util struct that helps verify IOTA Object.
/// Use builder style to construct the conditions.
/// When optionals fields are not set, related checks are omitted.
/// Consuming functions such as `check` perform the check and panics if
diff --git a/crates/iota-cluster-test/src/lib.rs b/crates/iota-cluster-test/src/lib.rs
index 855ab846157..89a55318af0 100644
--- a/crates/iota-cluster-test/src/lib.rs
+++ b/crates/iota-cluster-test/src/lib.rs
@@ -79,7 +79,7 @@ impl TestContext {
if gas_coins.len() < minimum_coins {
panic!(
- "Expect to get at least {minimum_coins} Iota Coins for address {addr}, but only got {}",
+ "Expect to get at least {minimum_coins} IOTA Coins for address {addr}, but only got {}",
gas_coins.len()
)
}
diff --git a/crates/iota-common/src/sync/mod.rs b/crates/iota-common/src/sync/mod.rs
index b474955f390..a5a1ba10fb2 100644
--- a/crates/iota-common/src/sync/mod.rs
+++ b/crates/iota-common/src/sync/mod.rs
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-/// Low level utilities shared across Iota.
+/// Low level utilities shared across IOTA.
pub mod async_once_cell;
pub mod notify_once;
pub mod notify_read;
diff --git a/crates/iota-config/data/fullnode-template-with-path.yaml b/crates/iota-config/data/fullnode-template-with-path.yaml
index 12854a33135..dc95921b7c9 100644
--- a/crates/iota-config/data/fullnode-template-with-path.yaml
+++ b/crates/iota-config/data/fullnode-template-with-path.yaml
@@ -1,4 +1,4 @@
-# Update this value to the location you want Iota to store its database
+# Update this value to the location you want IOTA to store its database
db-path: "iotadb"
# For ipv4, update this to "/ipv4/X.X.X.X/tcp/8080/http"
diff --git a/crates/iota-config/data/fullnode-template.yaml b/crates/iota-config/data/fullnode-template.yaml
index b161d62372b..9aa48c4e7ba 100644
--- a/crates/iota-config/data/fullnode-template.yaml
+++ b/crates/iota-config/data/fullnode-template.yaml
@@ -1,4 +1,4 @@
-# Update this value to the location you want Iota to store its database
+# Update this value to the location you want IOTA to store its database
db-path: "/opt/iota/db"
# For ipv4, update this to "/ipv4/X.X.X.X/tcp/8080/http"
diff --git a/crates/iota-config/src/genesis.rs b/crates/iota-config/src/genesis.rs
index 7e95ac0a148..5be816f64ce 100644
--- a/crates/iota-config/src/genesis.rs
+++ b/crates/iota-config/src/genesis.rs
@@ -159,7 +159,7 @@ impl Genesis {
pub fn iota_system_wrapper_object(&self) -> IotaSystemStateWrapper {
get_iota_system_state_wrapper(&self.objects())
- .expect("Iota System State Wrapper object must always exist")
+ .expect("IOTA System State Wrapper object must always exist")
}
pub fn contains_migrations(&self) -> bool {
@@ -167,7 +167,7 @@ impl Genesis {
}
pub fn iota_system_object(&self) -> IotaSystemState {
- get_iota_system_state(&self.objects()).expect("Iota System State object must always exist")
+ get_iota_system_state(&self.objects()).expect("IOTA System State object must always exist")
}
pub fn clock(&self) -> Clock {
@@ -321,11 +321,11 @@ impl UnsignedGenesis {
pub fn iota_system_wrapper_object(&self) -> IotaSystemStateWrapper {
get_iota_system_state_wrapper(&self.objects())
- .expect("Iota System State Wrapper object must always exist")
+ .expect("IOTA System State Wrapper object must always exist")
}
pub fn iota_system_object(&self) -> IotaSystemState {
- get_iota_system_state(&self.objects()).expect("Iota System State object must always exist")
+ get_iota_system_state(&self.objects()).expect("IOTA System State object must always exist")
}
pub fn authenticator_state_object(&self) -> Option {
diff --git a/crates/iota-core/src/authority_aggregator.rs b/crates/iota-core/src/authority_aggregator.rs
index 3ad3c4f0089..42934a53e1b 100644
--- a/crates/iota-core/src/authority_aggregator.rs
+++ b/crates/iota-core/src/authority_aggregator.rs
@@ -516,7 +516,7 @@ impl ProcessTransactionResult {
/// the validators and determining the final state of the transaction.
#[derive(Clone)]
pub struct AuthorityAggregator {
- /// Our Iota committee.
+ /// Our IOTA committee.
pub committee: Arc,
/// For more human readable metrics reporting.
/// It's OK for this map to be empty or missing validators, it then defaults
@@ -1901,7 +1901,7 @@ where
}
/// `AuthorityAggregatorBuilder` is used to build an `AuthorityAggregator` with
-/// customizable configurations for the Iota network.
+/// customizable configurations for the IOTA network.
#[derive(Default)]
pub struct AuthorityAggregatorBuilder<'a> {
network_config: Option<&'a NetworkConfig>,
diff --git a/crates/iota-core/src/consensus_adapter.rs b/crates/iota-core/src/consensus_adapter.rs
index eb25d7b5137..5e68b3db330 100644
--- a/crates/iota-core/src/consensus_adapter.rs
+++ b/crates/iota-core/src/consensus_adapter.rs
@@ -186,7 +186,7 @@ pub trait SubmitToConsensus: Sync + Send + 'static {
) -> IotaResult;
}
-/// Submit Iota certificates to the consensus.
+/// Submit IOTA certificates to the consensus.
pub struct ConsensusAdapter {
/// The network client connecting to the consensus node of this authority.
consensus_client: Arc,
diff --git a/crates/iota-core/src/consensus_manager/mod.rs b/crates/iota-core/src/consensus_manager/mod.rs
index 2e2c7a7d521..d77f2c6eafa 100644
--- a/crates/iota-core/src/consensus_manager/mod.rs
+++ b/crates/iota-core/src/consensus_manager/mod.rs
@@ -81,7 +81,7 @@ impl ProtocolManager {
}
}
-/// Used by Iota validator to start consensus protocol for each epoch.
+/// Used by IOTA validator to start consensus protocol for each epoch.
pub struct ConsensusManager {
consensus_config: ConsensusConfig,
mysticeti_manager: ProtocolManager,
diff --git a/crates/iota-core/src/generate_format.rs b/crates/iota-core/src/generate_format.rs
index 1f0ff6e1ee5..559d9938812 100644
--- a/crates/iota-core/src/generate_format.rs
+++ b/crates/iota-core/src/generate_format.rs
@@ -197,8 +197,8 @@ enum Action {
#[derive(Debug, Parser)]
#[clap(
- name = "Iota format generator",
- about = "Trace serde (de)serialization to generate format descriptions for Iota types"
+ name = "IOTA format generator",
+ about = "Trace serde (de)serialization to generate format descriptions for IOTA types"
)]
struct Options {
#[clap(value_enum, default_value = "Print", ignore_case = true)]
diff --git a/crates/iota-core/src/overload_monitor.rs b/crates/iota-core/src/overload_monitor.rs
index c4e921d15cf..47c686a28e6 100644
--- a/crates/iota-core/src/overload_monitor.rs
+++ b/crates/iota-core/src/overload_monitor.rs
@@ -255,7 +255,7 @@ pub fn overload_monitor_accept_tx(
// all validators makes the same decision.
let temporal_seed = SystemTime::now()
.duration_since(UNIX_EPOCH)
- .expect("Iota did not exist prior to 1970")
+ .expect("IOTA did not exist prior to 1970")
.as_secs()
/ SEED_UPDATE_DURATION_SECS;
diff --git a/crates/iota-core/src/safe_client.rs b/crates/iota-core/src/safe_client.rs
index ebf73e0daae..85744b91bc1 100644
--- a/crates/iota-core/src/safe_client.rs
+++ b/crates/iota-core/src/safe_client.rs
@@ -305,7 +305,7 @@ impl SafeClient
where
C: AuthorityAPI + Send + Sync + Clone + 'static,
{
- /// Initiate a new transfer to a Iota or Primary account.
+ /// Initiate a new transfer to an IOTA or Primary account.
pub async fn handle_transaction(
&self,
transaction: Transaction,
diff --git a/crates/iota-core/src/scoring_decision.rs b/crates/iota-core/src/scoring_decision.rs
index 631c8238e3a..e3ae21cede5 100644
--- a/crates/iota-core/src/scoring_decision.rs
+++ b/crates/iota-core/src/scoring_decision.rs
@@ -174,7 +174,7 @@ mod tests {
);
}
- /// Generate a pair of Iota and consensus committees for the given size.
+ /// Generate a pair of IOTA and consensus committees for the given size.
fn generate_committees(committee_size: usize) -> (Committee, ConsensusCommittee) {
let (consensus_committee, _) = local_committee_and_keys(0, vec![1; committee_size]);
diff --git a/crates/iota-core/src/test_authority_clients.rs b/crates/iota-core/src/test_authority_clients.rs
index bc17d9d2754..91e7d533cc2 100644
--- a/crates/iota-core/src/test_authority_clients.rs
+++ b/crates/iota-core/src/test_authority_clients.rs
@@ -250,7 +250,7 @@ impl MockAuthorityApi {
#[async_trait]
impl AuthorityAPI for MockAuthorityApi {
- /// Initiate a new transaction to a Iota or Primary account.
+ /// Initiate a new transaction to an IOTA or Primary account.
async fn handle_transaction(
&self,
_transaction: Transaction,
diff --git a/crates/iota-cost/tests/empirical_transaction_cost.rs b/crates/iota-cost/tests/empirical_transaction_cost.rs
index da6183eadc6..650908f40a2 100644
--- a/crates/iota-cost/tests/empirical_transaction_cost.rs
+++ b/crates/iota-cost/tests/empirical_transaction_cost.rs
@@ -115,7 +115,7 @@ async fn create_txes(
.build();
ret.insert(CommonTransactionCosts::Publish, publish_tx);
- // Transfer Whole Iota Coin and Transfer Portion of Iota Coin
+ // Transfer Whole IOTA Coin and Transfer Portion of IOTA Coin
//
let whole_iota_coin_tx =
TestTransactionBuilder::new(sender, gas_objects.pop().unwrap(), gas_price)
diff --git a/crates/iota-cost/troubleshooting.md b/crates/iota-cost/troubleshooting.md
index 9d37cba8362..5e739ee78a9 100644
--- a/crates/iota-cost/troubleshooting.md
+++ b/crates/iota-cost/troubleshooting.md
@@ -1,8 +1,8 @@
# Troubleshooting
-## Iota Framework change
+## IOTA Framework change
-If Iota framework code got updated, the expectations need to be changed. Follow these steps:
+If IOTA framework code got updated, the expectations need to be changed. Follow these steps:
```bash
# required; can be omitted if cargo-insta is installed
diff --git a/crates/iota-e2e-tests/tests/framework_upgrades/mock_iota_systems/base/README.txt b/crates/iota-e2e-tests/tests/framework_upgrades/mock_iota_systems/base/README.txt
index c40cfc5d190..db148aa9e7d 100644
--- a/crates/iota-e2e-tests/tests/framework_upgrades/mock_iota_systems/base/README.txt
+++ b/crates/iota-e2e-tests/tests/framework_upgrades/mock_iota_systems/base/README.txt
@@ -1,5 +1,5 @@
This directory contains a mock version of the 0x3 package (iota-system).
-The idea is to introduce a minimum version of the iota-system that we can use to start Iota.
+The idea is to introduce a minimum version of the iota-system that we can use to start IOTA.
We can then use this mock version as the base package to test various things such as iota system state upgrades.
This allows us to decouple from the complicated code in the original iota-system under iota-framework.
We only need to update code here and in other mock versions when the core protocol changes. This includes:
diff --git a/crates/iota-e2e-tests/tests/protocol_version_tests.rs b/crates/iota-e2e-tests/tests/protocol_version_tests.rs
index 4d34b9a39bc..773504aeaee 100644
--- a/crates/iota-e2e-tests/tests/protocol_version_tests.rs
+++ b/crates/iota-e2e-tests/tests/protocol_version_tests.rs
@@ -996,7 +996,7 @@ mod sim_only_tests {
framework_injection::set_override_cb(IOTA_SYSTEM_PACKAGE_ID, f)
}
- /// Get compiled modules for Iota System, built from fixture `fixture` in
+ /// Get compiled modules for IOTA System, built from fixture `fixture` in
/// the `framework_upgrades` directory.
fn iota_system_modules(fixture: &str) -> Vec {
fixture_package(fixture)
diff --git a/crates/iota-e2e-tests/tests/shared_objects_tests.rs b/crates/iota-e2e-tests/tests/shared_objects_tests.rs
index cbabd65cf64..663e81dabd0 100644
--- a/crates/iota-e2e-tests/tests/shared_objects_tests.rs
+++ b/crates/iota-e2e-tests/tests/shared_objects_tests.rs
@@ -28,7 +28,7 @@ use rand::distributions::Distribution;
use test_cluster::TestClusterBuilder;
use tokio::time::sleep;
-/// Send a simple shared object transaction to Iota and ensures the client gets
+/// Send a simple shared object transaction to IOTA and ensures the client gets
/// back a response.
#[sim_test]
async fn shared_object_transaction() {
@@ -319,8 +319,8 @@ async fn shared_object_deletion_multi_certs() {
.unwrap();
}
-/// End-to-end shared transaction test for a Iota validator. It does not test
-/// the client or wallet, but tests the end-to-end flow from Iota to consensus.
+/// End-to-end shared transaction test for an IOTA validator. It does not test
+/// the client or wallet, but tests the end-to-end flow from IOTA to consensus.
#[sim_test]
async fn call_shared_object_contract() {
let test_cluster = TestClusterBuilder::new().build().await;
@@ -635,7 +635,7 @@ async fn shared_object_sync() {
assert!(effects.status().is_ok());
}
-/// Send a simple shared object transaction to Iota and ensures the client gets
+/// Send a simple shared object transaction to IOTA and ensures the client gets
/// back a response.
#[sim_test]
async fn replay_shared_object_transaction() {
diff --git a/crates/iota-faucet/src/faucet/mod.rs b/crates/iota-faucet/src/faucet/mod.rs
index 0461473841b..a3e6e471eb7 100644
--- a/crates/iota-faucet/src/faucet/mod.rs
+++ b/crates/iota-faucet/src/faucet/mod.rs
@@ -87,8 +87,8 @@ pub const DEFAULT_NUM_OF_COINS: usize = 1;
#[derive(Parser, Clone)]
#[clap(
- name = "Iota Faucet",
- about = "Faucet for requesting test tokens on Iota",
+ name = "IOTA Faucet",
+ about = "Faucet for requesting test tokens on IOTA",
rename_all = "kebab-case"
)]
pub struct FaucetConfig {
diff --git a/crates/iota-framework-snapshot/tests/compatibility_tests.rs b/crates/iota-framework-snapshot/tests/compatibility_tests.rs
index 9fe13cf62da..01cfcc51bad 100644
--- a/crates/iota-framework-snapshot/tests/compatibility_tests.rs
+++ b/crates/iota-framework-snapshot/tests/compatibility_tests.rs
@@ -35,7 +35,7 @@ mod compatibility_tests {
.is_none()
{
panic!(
- "The current Iota framework {:?} is not compatible with version {:?}",
+ "The current IOTA framework {:?} is not compatible with version {:?}",
cur_package.id(),
version
);
diff --git a/crates/iota-framework/CONTRIBUTING.md b/crates/iota-framework/CONTRIBUTING.md
index 511dff52b67..ab52bea50e6 100644
--- a/crates/iota-framework/CONTRIBUTING.md
+++ b/crates/iota-framework/CONTRIBUTING.md
@@ -6,11 +6,11 @@ If changes need to be made to the framework's Move code, additional actions need
### Snapshot tests update
-Run the following commands in Iota's [root directory](../../) and accept the changes, if any (if you do not have `cargo-insta` command installed, please run the `cargo install cargo-insta` command first):
+Run the following commands in IOTA's [root directory](../../) and accept the changes, if any (if you do not have `cargo-insta` command installed, please run the `cargo install cargo-insta` command first):
```bash
cargo insta test -p iota-cost --review
cargo insta test -p iota-config --review
```
-Please use your best judgment to decide if the changes between old and new versions of the snapshots look "reasonable" (e.g., a minor change in gas costs). When in doubt, please reach out to a member of Iota core team.
+Please use your best judgment to decide if the changes between old and new versions of the snapshots look "reasonable" (e.g., a minor change in gas costs). When in doubt, please reach out to a member of IOTA core team.
diff --git a/crates/iota-framework/packages/bridge/sources/bridge.move b/crates/iota-framework/packages/bridge/sources/bridge.move
index 84c6e794068..dedc2870cc6 100644
--- a/crates/iota-framework/packages/bridge/sources/bridge.move
+++ b/crates/iota-framework/packages/bridge/sources/bridge.move
@@ -254,7 +254,7 @@ module bridge::bridge {
);
}
- // Record bridge message approvals in Iota, called by the bridge client
+ // Record bridge message approvals in IOTA, called by the bridge client
// If already approved, return early instead of aborting.
public fun approve_token_transfer(
bridge: &mut Bridge,
@@ -276,7 +276,7 @@ module bridge::bridge {
);
let message_key = message.key();
- // retrieve pending message if source chain is Iota, the initial message
+ // retrieve pending message if source chain is IOTA, the initial message
// must exist on chain
if (message.source_chain() == inner.chain_id) {
let record = &mut inner.token_transfer_records[message_key];
diff --git a/crates/iota-framework/packages/bridge/sources/committee.move b/crates/iota-framework/packages/bridge/sources/committee.move
index 1b0e49b14b0..c1383fcfbc5 100644
--- a/crates/iota-framework/packages/bridge/sources/committee.move
+++ b/crates/iota-framework/packages/bridge/sources/committee.move
@@ -60,7 +60,7 @@ module bridge::committee {
}
public struct CommitteeMember has copy, drop, store {
- /// The Iota Address of the validator
+ /// The IOTA Address of the validator
iota_address: address,
/// The public key bytes of the bridge key
bridge_pubkey_bytes: vector,
@@ -74,7 +74,7 @@ module bridge::committee {
}
public struct CommitteeMemberRegistration has copy, drop, store {
- /// The Iota Address of the validator
+ /// The IOTA Address of the validator
iota_address: address,
/// The public key bytes of the bridge key
bridge_pubkey_bytes: vector,
diff --git a/crates/iota-framework/packages/bridge/sources/limiter.move b/crates/iota-framework/packages/bridge/sources/limiter.move
index b4d11d4d5f8..3063226ca34 100644
--- a/crates/iota-framework/packages/bridge/sources/limiter.move
+++ b/crates/iota-framework/packages/bridge/sources/limiter.move
@@ -177,10 +177,10 @@ module bridge::limiter {
// It's tedious to list every pair, but it's safer to do so so we don't
// accidentally turn off limiter for a new production route in the future.
// Note limiter only takes effects on the receiving chain, so we only need to
- // specify routes from Ethereum to Iota.
+ // specify routes from Ethereum to IOTA.
fun initial_transfer_limits(): VecMap {
let mut transfer_limits = vec_map::empty();
- // 5M limit on Iota -> Ethereum mainnet
+ // 5M limit on IOTA -> Ethereum mainnet
transfer_limits.insert(
chain_ids::get_route(chain_ids::eth_mainnet(), chain_ids::iota_mainnet()),
5_000_000 * USD_VALUE_MULTIPLIER
diff --git a/crates/iota-framework/packages/bridge/sources/message.move b/crates/iota-framework/packages/bridge/sources/message.move
index f3b2ade6055..c4a04a8b947 100644
--- a/crates/iota-framework/packages/bridge/sources/message.move
+++ b/crates/iota-framework/packages/bridge/sources/message.move
@@ -385,7 +385,7 @@ module bridge::message {
}
}
- /// Update Iota token message
+ /// Update IOTA token message
/// [message_type:u8]
/// [version:u8]
/// [nonce:u64]
diff --git a/crates/iota-framework/packages/iota-framework/sources/address.move b/crates/iota-framework/packages/iota-framework/sources/address.move
index 7dc2aed0873..b9354e96df3 100644
--- a/crates/iota-framework/packages/iota-framework/sources/address.move
+++ b/crates/iota-framework/packages/iota-framework/sources/address.move
@@ -75,7 +75,7 @@ module iota::address {
else abort EAddressParseError
}
- /// Length of a Iota address in bytes
+ /// Length of an IOTA address in bytes
public fun length(): u64 {
LENGTH
}
diff --git a/crates/iota-framework/packages/iota-framework/sources/bag.move b/crates/iota-framework/packages/iota-framework/sources/bag.move
index e672c30b4ab..4adadc8f110 100644
--- a/crates/iota-framework/packages/iota-framework/sources/bag.move
+++ b/crates/iota-framework/packages/iota-framework/sources/bag.move
@@ -3,7 +3,7 @@
// SPDX-License-Identifier: Apache-2.0
/// A bag is a heterogeneous map-like collection. The collection is similar to `iota::table` in that
-/// its keys and values are not stored within the `Bag` value, but instead are stored using Iota's
+/// its keys and values are not stored within the `Bag` value, but instead are stored using IOTA's
/// object system. The `Bag` struct acts only as a handle into the object system to retrieve those
/// keys and values.
/// Note that this means that `Bag` values with exactly the same key-value mapping will not be
diff --git a/crates/iota-framework/packages/iota-framework/sources/display.move b/crates/iota-framework/packages/iota-framework/sources/display.move
index bf6cc92765a..c557f469f7b 100644
--- a/crates/iota-framework/packages/iota-framework/sources/display.move
+++ b/crates/iota-framework/packages/iota-framework/sources/display.move
@@ -58,7 +58,7 @@ module iota::display {
/// Type signature of the event corresponds to the type while id serves for
/// the discovery.
///
- /// Since Iota RPC supports querying events by type, finding a Display for the T
+ /// Since IOTA RPC supports querying events by type, finding a Display for the T
/// would be as simple as looking for the first event with `Display`.
public struct DisplayCreated has copy, drop {
id: ID
diff --git a/crates/iota-framework/packages/iota-framework/sources/dynamic_field.move b/crates/iota-framework/packages/iota-framework/sources/dynamic_field.move
index 4daaba11071..5a71552837e 100644
--- a/crates/iota-framework/packages/iota-framework/sources/dynamic_field.move
+++ b/crates/iota-framework/packages/iota-framework/sources/dynamic_field.move
@@ -3,11 +3,11 @@
// SPDX-License-Identifier: Apache-2.0
#[allow(unused_const)]
-/// In addition to the fields declared in its type definition, a Iota object can have dynamic fields
+/// In addition to the fields declared in its type definition, an IOTA object can have dynamic fields
/// that can be added after the object has been constructed. Unlike ordinary field names
/// (which are always statically declared identifiers) a dynamic field name can be any value with
/// the `copy`, `drop`, and `store` abilities, e.g. an integer, a boolean, or a string.
-/// This gives Iota programmers the flexibility to extend objects on-the-fly, and it also serves as a
+/// This gives IOTA programmers the flexibility to extend objects on-the-fly, and it also serves as a
/// building block for core collection types
module iota::dynamic_field {
diff --git a/crates/iota-framework/packages/iota-framework/sources/object.move b/crates/iota-framework/packages/iota-framework/sources/object.move
index aff3fbbf9f0..ba66ccb9f3c 100644
--- a/crates/iota-framework/packages/iota-framework/sources/object.move
+++ b/crates/iota-framework/packages/iota-framework/sources/object.move
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-/// Iota object identifiers
+/// IOTA object identifiers
module iota::object {
use std::bcs;
use iota::address;
@@ -25,7 +25,7 @@ module iota::object {
/// Allows calling `.to_bytes` on a `UID` to get a `vector`.
public use fun uid_to_bytes as UID.to_bytes;
- /// The hardcoded ID for the singleton Iota System State Object.
+ /// The hardcoded ID for the singleton IOTA System State Object.
const IOTA_SYSTEM_STATE_OBJECT_ID: address = @0x5;
/// The hardcoded ID for the singleton Clock Object.
@@ -46,7 +46,7 @@ module iota::object {
/// Sender is not @0x0 the system address.
const ENotSystemAddress: u64 = 0;
- /// An object ID. This is used to reference Iota Objects.
+ /// An object ID. This is used to reference IOTA Objects.
/// This is *not* guaranteed to be globally unique--anyone can create an `ID` from a `UID` or
/// from an object, and ID's can be freely copied and dropped.
/// Here, the values are not globally unique because there can be multiple values of type `ID`
@@ -60,7 +60,7 @@ module iota::object {
bytes: address
}
- /// Globally unique IDs that define an object's ID in storage. Any Iota Object, that is a struct
+ /// Globally unique IDs that define an object's ID in storage. Any IOTA Object, that is a struct
/// with the `key` ability, must have `id: UID` as its first field.
/// These are globally unique in the sense that no two values of type `UID` are ever equal, in
/// other words for any two values `id1: UID` and `id2: UID`, `id1` != `id2`.
@@ -167,7 +167,7 @@ module iota::object {
// === any object ===
- /// Create a new object. Returns the `UID` that must be stored in a Iota object.
+ /// Create a new object. Returns the `UID` that must be stored in an IOTA object.
/// This is the only way to create `UID`s.
public fun new(ctx: &mut TxContext): UID {
UID {
@@ -176,10 +176,10 @@ module iota::object {
}
/// Delete the object and it's `UID`. This is the only way to eliminate a `UID`.
- // This exists to inform Iota of object deletions. When an object
+ // This exists to inform IOTA of object deletions. When an object
// gets unpacked, the programmer will have to do something with its
// `UID`. The implementation of this function emits a deleted
- // system event so Iota knows to process the object deletion
+ // system event so IOTA knows to process the object deletion
public fun delete(id: UID) {
let UID { id: ID { bytes } } = id;
delete_impl(bytes)
@@ -206,7 +206,7 @@ module iota::object {
}
/// Get the `UID` for `obj`.
- /// Safe because Iota has an extra bytecode verifier pass that forces every struct with
+ /// Safe because IOTA has an extra bytecode verifier pass that forces every struct with
/// the `key` ability to have a distinguished `UID` field.
/// Cannot be made public as the access to `UID` for a given object must be privileged, and
/// restrictable in the object's module.
diff --git a/crates/iota-framework/packages/iota-framework/sources/table.move b/crates/iota-framework/packages/iota-framework/sources/table.move
index 944da32a0e4..15a26dbce92 100644
--- a/crates/iota-framework/packages/iota-framework/sources/table.move
+++ b/crates/iota-framework/packages/iota-framework/sources/table.move
@@ -3,7 +3,7 @@
// SPDX-License-Identifier: Apache-2.0
/// A table is a map-like collection. But unlike a traditional collection, it's keys and values are
-/// not stored within the `Table` value, but instead are stored using Iota's object system. The
+/// not stored within the `Table` value, but instead are stored using IOTA's object system. The
/// `Table` struct acts only as a handle into the object system to retrieve those keys and values.
/// Note that this means that `Table` values with exactly the same key-value mapping will not be
/// equal, with `==`, at runtime. For example
diff --git a/crates/iota-framework/packages/iota-framework/sources/test/test_scenario.move b/crates/iota-framework/packages/iota-framework/sources/test/test_scenario.move
index da316004a5d..ea484de915e 100644
--- a/crates/iota-framework/packages/iota-framework/sources/test/test_scenario.move
+++ b/crates/iota-framework/packages/iota-framework/sources/test/test_scenario.move
@@ -41,7 +41,7 @@ module iota::test_scenario {
/// Unable to deallocate the receiving ticket
const EUnableToDeallocateReceivingTicket: u64 = 7;
- /// Utility for mocking a multi-transaction Iota execution in a single Move procedure.
+ /// Utility for mocking a multi-transaction IOTA execution in a single Move procedure.
/// A `Scenario` maintains a view of the global object pool built up by the execution.
/// These objects can be accessed via functions like `take_from_sender`, which gives the
/// transaction sender access to objects in (only) their inventory.
diff --git a/crates/iota-framework/packages/iota-framework/sources/transfer.move b/crates/iota-framework/packages/iota-framework/sources/transfer.move
index 0a941f651a2..884e38ca845 100644
--- a/crates/iota-framework/packages/iota-framework/sources/transfer.move
+++ b/crates/iota-framework/packages/iota-framework/sources/transfer.move
@@ -43,7 +43,7 @@ module iota::transfer {
/// which (in turn) ensures that `obj` has a globally unique ID. Note that if the recipient
/// address represents an object ID, the `obj` sent will be inaccessible after the transfer
/// (though they will be retrievable at a future date once new features are added).
- /// This function has custom rules performed by the Iota Move bytecode verifier that ensures
+ /// This function has custom rules performed by the IOTA Move bytecode verifier that ensures
/// that `T` is an object defined in the module where `transfer` is invoked. Use
/// `public_transfer` to transfer an object with `store` outside of its module.
public fun transfer(obj: T, recipient: address) {
@@ -61,7 +61,7 @@ module iota::transfer {
/// Freeze `obj`. After freezing `obj` becomes immutable and can no longer be transferred or
/// mutated.
- /// This function has custom rules performed by the Iota Move bytecode verifier that ensures
+ /// This function has custom rules performed by the IOTA Move bytecode verifier that ensures
/// that `T` is an object defined in the module where `freeze_object` is invoked. Use
/// `public_freeze_object` to freeze an object with `store` outside of its module.
public fun freeze_object(obj: T) {
@@ -79,7 +79,7 @@ module iota::transfer {
/// This is irreversible, i.e. once an object is shared, it will stay shared forever.
/// Aborts with `ESharedNonNewObject` of the object being shared was not created in this
/// transaction. This restriction may be relaxed in the future.
- /// This function has custom rules performed by the Iota Move bytecode verifier that ensures
+ /// This function has custom rules performed by the IOTA Move bytecode verifier that ensures
/// that `T` is an object defined in the module where `share_object` is invoked. Use
/// `public_share_object` to share an object with `store` outside of its module.
public fun share_object(obj: T) {
@@ -98,7 +98,7 @@ module iota::transfer {
/// Given mutable (i.e., locked) access to the `parent` and a `Receiving` argument
/// referencing an object of type `T` owned by `parent` use the `to_receive`
/// argument to receive and return the referenced owned object of type `T`.
- /// This function has custom rules performed by the Iota Move bytecode verifier that ensures
+ /// This function has custom rules performed by the IOTA Move bytecode verifier that ensures
/// that `T` is an object defined in the module where `receive` is invoked. Use
/// `public_receive` to receivne an object with `store` outside of its module.
public fun receive(parent: &mut UID, to_receive: Receiving): T {
diff --git a/crates/iota-framework/packages/iota-framework/sources/types.move b/crates/iota-framework/packages/iota-framework/sources/types.move
index 4edc5dd3909..dd37f1865e9 100644
--- a/crates/iota-framework/packages/iota-framework/sources/types.move
+++ b/crates/iota-framework/packages/iota-framework/sources/types.move
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-/// Iota types helpers and utilities
+/// IOTA types helpers and utilities
module iota::types {
// === one-time witness ===
diff --git a/crates/iota-framework/packages/iota-framework/tests/kiosk/kiosk_test_utils.move b/crates/iota-framework/packages/iota-framework/tests/kiosk/kiosk_test_utils.move
index 9db936952b8..2ceeb57f23b 100644
--- a/crates/iota-framework/packages/iota-framework/tests/kiosk/kiosk_test_utils.move
+++ b/crates/iota-framework/packages/iota-framework/tests/kiosk/kiosk_test_utils.move
@@ -33,7 +33,7 @@ module iota::kiosk_test_utils {
(policy, cap)
}
- /// Prepare: Get Iota
+ /// Prepare: Get IOTA
public fun get_iota(amount: u64, ctx: &mut TxContext): Coin {
coin::mint_for_testing(amount, ctx)
}
diff --git a/crates/iota-framework/packages/iota-framework/tests/verifier_tests.move b/crates/iota-framework/packages/iota-framework/tests/verifier_tests.move
index 9200fad14b1..10eb0fc2b91 100644
--- a/crates/iota-framework/packages/iota-framework/tests/verifier_tests.move
+++ b/crates/iota-framework/packages/iota-framework/tests/verifier_tests.move
@@ -3,7 +3,7 @@
// SPDX-License-Identifier: Apache-2.0
#[test_only]
-/// Tests if normally illegal (in terms of Iota bytecode verification) code is allowed in tests.
+/// Tests if normally illegal (in terms of IOTA bytecode verification) code is allowed in tests.
module iota::verifier_tests {
public struct VERIFIER_TESTS has drop {}
diff --git a/crates/iota-framework/packages/iota-system/sources/iota_system.move b/crates/iota-framework/packages/iota-system/sources/iota_system.move
index 573ffddb165..81876d03abd 100644
--- a/crates/iota-framework/packages/iota-system/sources/iota_system.move
+++ b/crates/iota-framework/packages/iota-system/sources/iota_system.move
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-/// Iota System State Type Upgrade Guide
+/// IOTA System State Type Upgrade Guide
/// `IotaSystemState` is a thin wrapper around `IotaSystemStateV1` that provides a versioned interface.
/// The `IotaSystemState` object has a fixed ID 0x5, and the `IotaSystemStateV1` object is stored as a dynamic field.
/// There are a few different ways to upgrade the `IotaSystemStateV1` type:
diff --git a/crates/iota-framework/packages/iota-system/sources/iota_system_state_inner.move b/crates/iota-framework/packages/iota-system/sources/iota_system_state_inner.move
index 2097871e915..b4840789b09 100644
--- a/crates/iota-framework/packages/iota-system/sources/iota_system_state_inner.move
+++ b/crates/iota-framework/packages/iota-system/sources/iota_system_state_inner.move
@@ -58,7 +58,7 @@ module iota_system::iota_system_state_inner {
extra_fields: Bag,
}
- /// The top-level object containing all information of the Iota system.
+ /// The top-level object containing all information of the IOTA system.
public struct IotaSystemStateV1 has store {
/// The current epoch ID, starting from 0.
epoch: u64,
diff --git a/crates/iota-framework/packages/iota-system/sources/validator.move b/crates/iota-framework/packages/iota-system/sources/validator.move
index 3e19f8fddf8..cbba81c6c0a 100644
--- a/crates/iota-framework/packages/iota-system/sources/validator.move
+++ b/crates/iota-framework/packages/iota-system/sources/validator.move
@@ -72,7 +72,7 @@ module iota_system::validator {
const MAX_VALIDATOR_GAS_PRICE: u64 = 100_000;
public struct ValidatorMetadataV1 has store {
- /// The Iota Address of the validator. This is the sender that created the ValidatorV1 object,
+ /// The IOTA Address of the validator. This is the sender that created the ValidatorV1 object,
/// and also the address to send validator/coins to during withdraws.
iota_address: address,
/// The public key bytes corresponding to the private key that the validator
diff --git a/crates/iota-framework/packages/move-stdlib/sources/address.move b/crates/iota-framework/packages/move-stdlib/sources/address.move
index 924a1d939dd..79e0c960c42 100644
--- a/crates/iota-framework/packages/move-stdlib/sources/address.move
+++ b/crates/iota-framework/packages/move-stdlib/sources/address.move
@@ -6,7 +6,7 @@
/// platform-specific parameter.
module std::address {
/// Should be converted to a native function.
- /// Current implementation only works for Iota.
+ /// Current implementation only works for IOTA.
public fun length(): u64 {
32
}
diff --git a/crates/iota-framework/packages/stardust/sources/basic/basic_output.move b/crates/iota-framework/packages/stardust/sources/basic/basic_output.move
index 10e3dad75d7..e322baadf41 100644
--- a/crates/iota-framework/packages/stardust/sources/basic/basic_output.move
+++ b/crates/iota-framework/packages/stardust/sources/basic/basic_output.move
@@ -4,7 +4,7 @@
module stardust::basic_output {
// === Imports ===
- // Iota imports.
+ // IOTA imports.
use iota::bag::Bag;
use iota::balance::Balance;
use iota::transfer::Receiving;
diff --git a/crates/iota-framework/packages/stardust/sources/nft/nft.move b/crates/iota-framework/packages/stardust/sources/nft/nft.move
index 5ffbd7677d1..a257dd7dcd8 100644
--- a/crates/iota-framework/packages/stardust/sources/nft/nft.move
+++ b/crates/iota-framework/packages/stardust/sources/nft/nft.move
@@ -39,7 +39,7 @@ module stardust::nft {
// Build a `Display` object.
let keys = vector[
- // The Iota standard fields.
+ // The IOTA standard fields.
string::utf8(b"name"),
string::utf8(b"image_url"),
string::utf8(b"description"),
@@ -55,7 +55,7 @@ module stardust::nft {
];
let values = vector[
- // The Iota standard fields.
+ // The IOTA standard fields.
string::utf8(b"{immutable_metadata.name}"),
string::utf8(b"{immutable_metadata.uri}"),
string::utf8(b"{immutable_metadata.description}"),
diff --git a/crates/iota-genesis-builder/examples/snapshot_add_test_outputs.rs b/crates/iota-genesis-builder/examples/snapshot_add_test_outputs.rs
index 3600e31afea..e5b8398784f 100644
--- a/crates/iota-genesis-builder/examples/snapshot_add_test_outputs.rs
+++ b/crates/iota-genesis-builder/examples/snapshot_add_test_outputs.rs
@@ -13,7 +13,7 @@ use iota_genesis_builder::stardust::{
use iota_types::{gas_coin::STARDUST_TOTAL_SUPPLY_IOTA, stardust::coin_type::CoinType};
#[derive(Parser, Debug)]
-#[clap(about = "Tool for adding test data to Iota Hornet full-snapshot")]
+#[clap(about = "Tool for adding test data to IOTA Hornet full-snapshot")]
struct Cli {
#[clap(subcommand)]
snapshot: Snapshot,
@@ -21,9 +21,9 @@ struct Cli {
#[derive(Subcommand, Debug)]
enum Snapshot {
- #[clap(about = "Parse an Iota Hornet full-snapshot file")]
+ #[clap(about = "Parse an IOTA Hornet full-snapshot file")]
Iota {
- #[clap(long, help = "Path to the Iota Hornet full-snapshot file")]
+ #[clap(long, help = "Path to the IOTA Hornet full-snapshot file")]
snapshot_path: String,
},
}
diff --git a/crates/iota-genesis-builder/examples/snapshot_only_test_outputs.rs b/crates/iota-genesis-builder/examples/snapshot_only_test_outputs.rs
index d56d1b53716..1051e28a5cd 100644
--- a/crates/iota-genesis-builder/examples/snapshot_only_test_outputs.rs
+++ b/crates/iota-genesis-builder/examples/snapshot_only_test_outputs.rs
@@ -19,7 +19,7 @@ use iota_types::{
const WITH_SAMPLING: bool = false;
#[derive(Parser, Debug)]
-#[clap(about = "Tool for generating Iota Hornet full-snapshot file with test data")]
+#[clap(about = "Tool for generating IOTA Hornet full-snapshot file with test data")]
struct Cli {
#[clap(subcommand)]
snapshot: Snapshot,
@@ -27,9 +27,9 @@ struct Cli {
#[derive(Subcommand, Debug)]
enum Snapshot {
- #[clap(about = "Parse an Iota Hornet full-snapshot file")]
+ #[clap(about = "Parse an IOTA Hornet full-snapshot file")]
Iota {
- #[clap(long, help = "Path to the Iota Hornet full-snapshot file")]
+ #[clap(long, help = "Path to the IOTA Hornet full-snapshot file")]
snapshot_path: String,
#[clap(long, help = "Specify the delegator address")]
delegator: IotaAddress,
diff --git a/crates/iota-genesis-builder/src/lib.rs b/crates/iota-genesis-builder/src/lib.rs
index bbde092580a..69de4c1e0be 100644
--- a/crates/iota-genesis-builder/src/lib.rs
+++ b/crates/iota-genesis-builder/src/lib.rs
@@ -408,7 +408,7 @@ impl Builder {
fn committee(objects: &[Object]) -> Committee {
let iota_system_object =
- get_iota_system_state(&objects).expect("Iota System State object must always exist");
+ get_iota_system_state(&objects).expect("IOTA System State object must always exist");
iota_system_object
.get_current_epoch_committee()
.committee()
@@ -1770,7 +1770,7 @@ impl From for SnapshotSource {
}
}
-/// The URLs to download Iota object snapshot.
+/// The URLs to download IOTA object snapshot.
#[derive(Debug, Clone, Deserialize, Serialize)]
pub enum SnapshotUrl {
Iota,
@@ -1802,7 +1802,7 @@ impl FromStr for SnapshotUrl {
}
impl SnapshotUrl {
- /// Returns the Iota object snapshot download URL.
+ /// Returns the IOTA object snapshot download URL.
pub fn to_url(&self) -> Url {
match self {
Self::Iota => Url::parse(IOTA_OBJECT_SNAPSHOT_URL).expect("should be valid URL"),
diff --git a/crates/iota-genesis-builder/src/main.rs b/crates/iota-genesis-builder/src/main.rs
index b85c4358fee..7b7e9c1c4fb 100644
--- a/crates/iota-genesis-builder/src/main.rs
+++ b/crates/iota-genesis-builder/src/main.rs
@@ -22,7 +22,7 @@ use tracing::Level;
use tracing_subscriber::FmtSubscriber;
#[derive(Parser, Debug)]
-#[clap(about = "Tool for migrating Iota Hornet full-snapshot file")]
+#[clap(about = "Tool for migrating IOTA Hornet full-snapshot file")]
struct Cli {
#[clap(subcommand)]
snapshot: Snapshot,
@@ -32,9 +32,9 @@ struct Cli {
#[derive(Subcommand, Debug)]
enum Snapshot {
- #[clap(about = "Migrate an Iota Hornet full-snapshot file")]
+ #[clap(about = "Migrate an IOTA Hornet full-snapshot file")]
Iota {
- #[clap(long, help = "Path to the Iota Hornet full-snapshot file")]
+ #[clap(long, help = "Path to the IOTA Hornet full-snapshot file")]
snapshot_path: String,
#[clap(
long,
diff --git a/crates/iota-genesis-builder/src/stake.rs b/crates/iota-genesis-builder/src/stake.rs
index 81cab76653e..10e70abfa89 100644
--- a/crates/iota-genesis-builder/src/stake.rs
+++ b/crates/iota-genesis-builder/src/stake.rs
@@ -80,7 +80,7 @@ impl GenesisStake {
/// inner token allocations.
///
/// The resulting schedule is guaranteed to contain allocations
- /// that sum up the initial total supply of Iota in nanos.
+ /// that sum up the initial total supply of IOTA in nanos.
///
/// ## Errors
///
diff --git a/crates/iota-graphql-e2e-tests/Cargo.toml b/crates/iota-graphql-e2e-tests/Cargo.toml
index de5796645cb..e912872c3ec 100644
--- a/crates/iota-graphql-e2e-tests/Cargo.toml
+++ b/crates/iota-graphql-e2e-tests/Cargo.toml
@@ -5,7 +5,7 @@ authors = ["IOTA Foundation "]
edition = "2021"
license = "Apache-2.0"
publish = false
-description = "End to end tests for Iota GraphQL"
+description = "End to end tests for IOTA GraphQL"
[lints]
workspace = true
diff --git a/crates/iota-graphql-rpc/schema.graphql b/crates/iota-graphql-rpc/schema.graphql
index 8821213b8ef..ec5f1a351d7 100644
--- a/crates/iota-graphql-rpc/schema.graphql
+++ b/crates/iota-graphql-rpc/schema.graphql
@@ -951,7 +951,7 @@ of dynamic fields:
an object stored in this kind of field will be considered wrapped and
will not be accessible directly via its ID by external tools (explorers,
wallets, etc) accessing storage.
-2) Dynamic Object Fields values must be Iota objects (have the `key` and
+2) Dynamic Object Fields values must be IOTA objects (have the `key` and
`store` abilities, and id: UID as the first field), but will still be
directly accessible off-chain via their object ID after being attached.
"""
@@ -1061,7 +1061,7 @@ type EndOfEpochTransactionKindEdge {
}
"""
-Operation of the Iota network is temporally partitioned into non-overlapping
+Operation of the IOTA network is temporally partitioned into non-overlapping
epochs, and the network aims to keep epochs roughly the same duration as
each other. During a particular epoch the following data is fixed:
@@ -1664,7 +1664,7 @@ type MergeCoinsTransaction {
}
"""
-Abilities are keywords in Iota Move that define how types behave at the
+Abilities are keywords in IOTA Move that define how types behave at the
compiler level.
"""
enum MoveAbility {
@@ -2610,7 +2610,7 @@ enum MoveVisibility {
}
"""
-Mutations are used to write to the Iota network.
+Mutations are used to write to the IOTA network.
"""
type Mutation {
"""
@@ -2638,7 +2638,7 @@ type Mutation {
}
"""
-An object in Iota is a package (set of Move bytecode modules) or object
+An object in IOTA is a package (set of Move bytecode modules) or object
(typed data structure with fields) with additional metadata detailing its
id, version, transaction digest, owner field indicating how this object can
be accessed.
@@ -3279,7 +3279,7 @@ type Query {
field when its parent was at `rootVersion`.
If `rootVersion` is omitted, dynamic fields will be from a consistent
- snapshot of the Iota state at the latest checkpoint known to the
+ snapshot of the IOTA state at the latest checkpoint known to the
GraphQL RPC. Similarly, `Owner.asObject` will return the object's
version at the latest checkpoint.
"""
diff --git a/crates/iota-graphql-rpc/src/commands.rs b/crates/iota-graphql-rpc/src/commands.rs
index 0a3c4317242..00585243954 100644
--- a/crates/iota-graphql-rpc/src/commands.rs
+++ b/crates/iota-graphql-rpc/src/commands.rs
@@ -9,7 +9,7 @@ use clap::*;
#[derive(Parser)]
#[clap(
name = "iota-graphql-rpc",
- about = "Iota GraphQL RPC",
+ about = "IOTA GraphQL RPC",
rename_all = "kebab-case",
author,
version
diff --git a/crates/iota-graphql-rpc/src/config.rs b/crates/iota-graphql-rpc/src/config.rs
index 550482e4d9d..70e30f59370 100644
--- a/crates/iota-graphql-rpc/src/config.rs
+++ b/crates/iota-graphql-rpc/src/config.rs
@@ -439,7 +439,7 @@ impl Default for Versions {
impl Default for Ide {
fn default() -> Self {
Self {
- ide_title: "Iota GraphQL IDE".to_string(),
+ ide_title: "IOTA GraphQL IDE".to_string(),
}
}
}
diff --git a/crates/iota-graphql-rpc/src/mutation.rs b/crates/iota-graphql-rpc/src/mutation.rs
index b236b6824a4..0cc7cfaadda 100644
--- a/crates/iota-graphql-rpc/src/mutation.rs
+++ b/crates/iota-graphql-rpc/src/mutation.rs
@@ -26,7 +26,7 @@ use crate::{
};
pub struct Mutation;
-/// Mutations are used to write to the Iota network.
+/// Mutations are used to write to the IOTA network.
#[Object]
impl Mutation {
/// Execute a transaction, committing its effects on chain.
@@ -56,11 +56,11 @@ impl Mutation {
) -> Result {
let iota_sdk_client: &Option = ctx
.data()
- .map_err(|_| Error::Internal("Unable to fetch Iota SDK client".to_string()))
+ .map_err(|_| Error::Internal("Unable to fetch IOTA SDK client".to_string()))
.extend()?;
let iota_sdk_client = iota_sdk_client
.as_ref()
- .ok_or_else(|| Error::Internal("Iota SDK client not initialized".to_string()))
+ .ok_or_else(|| Error::Internal("IOTA SDK client not initialized".to_string()))
.extend()?;
let tx_data = bcs::from_bytes(
&Base64::decode(&tx_bytes)
diff --git a/crates/iota-graphql-rpc/src/server/exchange_rates_task.rs b/crates/iota-graphql-rpc/src/server/exchange_rates_task.rs
index d39d8f3597c..e2d9b91f297 100644
--- a/crates/iota-graphql-rpc/src/server/exchange_rates_task.rs
+++ b/crates/iota-graphql-rpc/src/server/exchange_rates_task.rs
@@ -43,7 +43,7 @@ impl TriggerExchangeRatesTask {
info!("Detected epoch boundary, triggering call to exchange rates");
let latest_iota_system_state = self.db.inner.spawn_blocking(move |this|
this.get_latest_iota_system_state()
- ).await.map_err(|_| error!("Failed to fetch latest Iota system state"));
+ ).await.map_err(|_| error!("Failed to fetch latest IOTA system state"));
if let Ok(latest_iota_system_state) = latest_iota_system_state {
let db = self.db.clone();
diff --git a/crates/iota-graphql-rpc/src/test_infra/cluster.rs b/crates/iota-graphql-rpc/src/test_infra/cluster.rs
index 36aff4343d1..f6a0aeede83 100644
--- a/crates/iota-graphql-rpc/src/test_infra/cluster.rs
+++ b/crates/iota-graphql-rpc/src/test_infra/cluster.rs
@@ -105,9 +105,9 @@ pub async fn start_cluster(
}
}
-/// Takes in a simulated instantiation of a Iota blockchain and builds a cluster
-/// around it. This cluster is typically used in e2e tests to emulate and test
-/// behaviors.
+/// Takes in a simulated instantiation of an IOTA blockchain and builds a
+/// cluster around it. This cluster is typically used in e2e tests to emulate
+/// and test behaviors.
pub async fn serve_executor(
graphql_connection_config: ConnectionConfig,
internal_data_source_rpc_port: u16,
diff --git a/crates/iota-graphql-rpc/src/types/dynamic_field.rs b/crates/iota-graphql-rpc/src/types/dynamic_field.rs
index 612e3ab84ac..c63634adfa2 100644
--- a/crates/iota-graphql-rpc/src/types/dynamic_field.rs
+++ b/crates/iota-graphql-rpc/src/types/dynamic_field.rs
@@ -58,7 +58,7 @@ pub(crate) struct DynamicFieldName {
/// an object stored in this kind of field will be considered wrapped and
/// will not be accessible directly via its ID by external tools (explorers,
/// wallets, etc) accessing storage.
-/// 2) Dynamic Object Fields values must be Iota objects (have the `key` and
+/// 2) Dynamic Object Fields values must be IOTA objects (have the `key` and
/// `store` abilities, and id: UID as the first field), but will still be
/// directly accessible off-chain via their object ID after being attached.
#[Object]
diff --git a/crates/iota-graphql-rpc/src/types/epoch.rs b/crates/iota-graphql-rpc/src/types/epoch.rs
index bbb9607c294..696ebdfe0fd 100644
--- a/crates/iota-graphql-rpc/src/types/epoch.rs
+++ b/crates/iota-graphql-rpc/src/types/epoch.rs
@@ -43,7 +43,7 @@ struct EpochKey {
pub checkpoint_viewed_at: u64,
}
-/// Operation of the Iota network is temporally partitioned into non-overlapping
+/// Operation of the IOTA network is temporally partitioned into non-overlapping
/// epochs, and the network aims to keep epochs roughly the same duration as
/// each other. During a particular epoch the following data is fixed:
///
diff --git a/crates/iota-graphql-rpc/src/types/event/mod.rs b/crates/iota-graphql-rpc/src/types/event/mod.rs
index 633e9771184..cfe77f3cb45 100644
--- a/crates/iota-graphql-rpc/src/types/event/mod.rs
+++ b/crates/iota-graphql-rpc/src/types/event/mod.rs
@@ -42,7 +42,7 @@ mod lookups;
pub(crate) use cursor::Cursor;
pub(crate) use filter::EventFilter;
-/// A Iota node emits one of the following events:
+/// An IOTA node emits one of the following events:
/// Move event
/// Publish event
/// Transfer object event
diff --git a/crates/iota-graphql-rpc/src/types/move_type.rs b/crates/iota-graphql-rpc/src/types/move_type.rs
index 44227f90de5..880d84985ca 100644
--- a/crates/iota-graphql-rpc/src/types/move_type.rs
+++ b/crates/iota-graphql-rpc/src/types/move_type.rs
@@ -316,7 +316,7 @@ impl TryFrom for MoveFieldLayout {
}
/// Error from seeing a `signer` value or type, which shouldn't be possible in
-/// Iota Move.
+/// IOTA Move.
pub(crate) fn unexpected_signer_error() -> Error {
Error::Internal("Unexpected value of type: signer.".to_string())
}
diff --git a/crates/iota-graphql-rpc/src/types/move_value.rs b/crates/iota-graphql-rpc/src/types/move_value.rs
index d0e31fe47e4..32a3080db8a 100644
--- a/crates/iota-graphql-rpc/src/types/move_value.rs
+++ b/crates/iota-graphql-rpc/src/types/move_value.rs
@@ -230,7 +230,7 @@ impl TryFrom for MoveData {
})
}
- // Iota does not support `signer` as a type.
+ // IOTA does not support `signer` as a type.
V::Signer(_) => return Err(unexpected_signer_error()),
})
}
@@ -318,7 +318,7 @@ fn try_to_json_value(value: A::MoveValue) -> Result {
.collect(),
)
}
- // Iota does not support `signer` as a type.
+ // IOTA does not support `signer` as a type.
V::Signer(_) => return Err(unexpected_signer_error()),
})
}
diff --git a/crates/iota-graphql-rpc/src/types/object.rs b/crates/iota-graphql-rpc/src/types/object.rs
index ae2d53767f3..d6211443f8a 100644
--- a/crates/iota-graphql-rpc/src/types/object.rs
+++ b/crates/iota-graphql-rpc/src/types/object.rs
@@ -334,7 +334,7 @@ struct LatestAtKey {
checkpoint_viewed_at: u64,
}
-/// An object in Iota is a package (set of Move bytecode modules) or object
+/// An object in IOTA is a package (set of Move bytecode modules) or object
/// (typed data structure with fields) with additional metadata detailing its
/// id, version, transaction digest, owner field indicating how this object can
/// be accessed.
diff --git a/crates/iota-graphql-rpc/src/types/open_move_type.rs b/crates/iota-graphql-rpc/src/types/open_move_type.rs
index b88944de9f0..bf3c4e79126 100644
--- a/crates/iota-graphql-rpc/src/types/open_move_type.rs
+++ b/crates/iota-graphql-rpc/src/types/open_move_type.rs
@@ -13,7 +13,7 @@ pub(crate) struct OpenMoveType {
signature: OpenMoveTypeSignature,
}
-/// Abilities are keywords in Iota Move that define how types behave at the
+/// Abilities are keywords in IOTA Move that define how types behave at the
/// compiler level.
#[derive(Enum, Copy, Clone, Eq, PartialEq)]
pub(crate) enum MoveAbility {
diff --git a/crates/iota-graphql-rpc/src/types/query.rs b/crates/iota-graphql-rpc/src/types/query.rs
index 91de38b2f8e..6786b84501c 100644
--- a/crates/iota-graphql-rpc/src/types/query.rs
+++ b/crates/iota-graphql-rpc/src/types/query.rs
@@ -110,11 +110,11 @@ impl Query {
let iota_sdk_client: &Option = ctx
.data()
- .map_err(|_| Error::Internal("Unable to fetch Iota SDK client".to_string()))
+ .map_err(|_| Error::Internal("Unable to fetch IOTA SDK client".to_string()))
.extend()?;
let iota_sdk_client = iota_sdk_client
.as_ref()
- .ok_or_else(|| Error::Internal("Iota SDK client not initialized".to_string()))
+ .ok_or_else(|| Error::Internal("IOTA SDK client not initialized".to_string()))
.extend()?;
let (sender_address, tx_kind, gas_price, gas_sponsor, gas_budget, gas_objects) =
@@ -200,7 +200,7 @@ impl Query {
/// field when its parent was at `rootVersion`.
///
/// If `rootVersion` is omitted, dynamic fields will be from a consistent
- /// snapshot of the Iota state at the latest checkpoint known to the
+ /// snapshot of the IOTA state at the latest checkpoint known to the
/// GraphQL RPC. Similarly, `Owner.asObject` will return the object's
/// version at the latest checkpoint.
async fn owner(
diff --git a/crates/iota-graphql-rpc/src/types/validator.rs b/crates/iota-graphql-rpc/src/types/validator.rs
index 7d70342693f..4f9b3cfb87a 100644
--- a/crates/iota-graphql-rpc/src/types/validator.rs
+++ b/crates/iota-graphql-rpc/src/types/validator.rs
@@ -74,7 +74,7 @@ impl Loader for Db {
.inner
.spawn_blocking(move |this| this.get_latest_iota_system_state())
.await
- .map_err(|_| Error::Internal("Failed to fetch latest Iota system state".to_string()))?;
+ .map_err(|_| Error::Internal("Failed to fetch latest IOTA system state".to_string()))?;
let governance_api = GovernanceReadApi::new(self.inner.clone());
let (candidate_rates, pending_rates) = tokio::try_join!(
diff --git a/crates/iota-graphql-rpc/tests/snapshots/snapshot_tests__schema_sdl_export.snap b/crates/iota-graphql-rpc/tests/snapshots/snapshot_tests__schema_sdl_export.snap
index b1c9a00a5ac..f9ff85e3efb 100644
--- a/crates/iota-graphql-rpc/tests/snapshots/snapshot_tests__schema_sdl_export.snap
+++ b/crates/iota-graphql-rpc/tests/snapshots/snapshot_tests__schema_sdl_export.snap
@@ -955,7 +955,7 @@ of dynamic fields:
an object stored in this kind of field will be considered wrapped and
will not be accessible directly via its ID by external tools (explorers,
wallets, etc) accessing storage.
-2) Dynamic Object Fields values must be Iota objects (have the `key` and
+2) Dynamic Object Fields values must be IOTA objects (have the `key` and
`store` abilities, and id: UID as the first field), but will still be
directly accessible off-chain via their object ID after being attached.
"""
@@ -1065,7 +1065,7 @@ type EndOfEpochTransactionKindEdge {
}
"""
-Operation of the Iota network is temporally partitioned into non-overlapping
+Operation of the IOTA network is temporally partitioned into non-overlapping
epochs, and the network aims to keep epochs roughly the same duration as
each other. During a particular epoch the following data is fixed:
@@ -1668,7 +1668,7 @@ type MergeCoinsTransaction {
}
"""
-Abilities are keywords in Iota Move that define how types behave at the
+Abilities are keywords in IOTA Move that define how types behave at the
compiler level.
"""
enum MoveAbility {
@@ -2614,7 +2614,7 @@ enum MoveVisibility {
}
"""
-Mutations are used to write to the Iota network.
+Mutations are used to write to the IOTA network.
"""
type Mutation {
"""
@@ -2642,7 +2642,7 @@ type Mutation {
}
"""
-An object in Iota is a package (set of Move bytecode modules) or object
+An object in IOTA is a package (set of Move bytecode modules) or object
(typed data structure with fields) with additional metadata detailing its
id, version, transaction digest, owner field indicating how this object can
be accessed.
@@ -3283,7 +3283,7 @@ type Query {
field when its parent was at `rootVersion`.
If `rootVersion` is omitted, dynamic fields will be from a consistent
- snapshot of the Iota state at the latest checkpoint known to the
+ snapshot of the IOTA state at the latest checkpoint known to the
GraphQL RPC. Similarly, `Owner.asObject` will return the object's
version at the latest checkpoint.
"""
diff --git a/crates/iota-indexer/examples/index_genesis_transaction.rs b/crates/iota-indexer/examples/index_genesis_transaction.rs
index cc2de930778..59ec702bde4 100644
--- a/crates/iota-indexer/examples/index_genesis_transaction.rs
+++ b/crates/iota-indexer/examples/index_genesis_transaction.rs
@@ -33,7 +33,7 @@ struct Args {
const DEFAULT_DB_URL: &str = "postgres://postgres:postgrespw@localhost:5432/iota_indexer";
-// Build genesis with `Iota` stardust snapshot
+// Build genesis with `IOTA` stardust snapshot
fn genesis_builder(migration_sources: Vec) -> GenesisBuilder {
// Create the builder
let mut builder = GenesisBuilder::new();
diff --git a/crates/iota-indexer/src/indexer.rs b/crates/iota-indexer/src/indexer.rs
index 3f71000b7f8..b9c16356971 100644
--- a/crates/iota-indexer/src/indexer.rs
+++ b/crates/iota-indexer/src/indexer.rs
@@ -70,7 +70,7 @@ impl Indexer {
cancel: CancellationToken,
) -> Result<(), IndexerError> {
info!(
- "Iota Indexer Writer (version {:?}) started...",
+ "IOTA Indexer Writer (version {:?}) started...",
env!("CARGO_PKG_VERSION")
);
@@ -173,7 +173,7 @@ impl Indexer {
db_url: String,
) -> Result<(), IndexerError> {
info!(
- "Iota Indexer Reader (version {:?}) started...",
+ "IOTA Indexer Reader (version {:?}) started...",
env!("CARGO_PKG_VERSION")
);
let indexer_reader = IndexerReader::::new(db_url)?;
@@ -193,7 +193,7 @@ impl Indexer {
metrics: IndexerMetrics,
) -> Result<(), IndexerError> {
info!(
- "Iota Indexer Analytical Worker (version {:?}) started...",
+ "IOTA Indexer Analytical Worker (version {:?}) started...",
env!("CARGO_PKG_VERSION")
);
let mut processor_orchestrator = ProcessorOrchestrator::new(store, metrics);
diff --git a/crates/iota-indexer/src/lib.rs b/crates/iota-indexer/src/lib.rs
index 76d1696c44d..22c911f6664 100644
--- a/crates/iota-indexer/src/lib.rs
+++ b/crates/iota-indexer/src/lib.rs
@@ -48,8 +48,8 @@ pub mod types;
#[derive(Parser, Clone, Debug)]
#[clap(
- name = "Iota indexer",
- about = "An off-fullnode service serving data from Iota protocol",
+ name = "IOTA indexer",
+ about = "An off-fullnode service serving data from IOTA protocol",
rename_all = "kebab-case"
)]
pub struct IndexerConfig {
diff --git a/crates/iota-indexer/src/main.rs b/crates/iota-indexer/src/main.rs
index 791b16a5469..11c04da67b3 100644
--- a/crates/iota-indexer/src/main.rs
+++ b/crates/iota-indexer/src/main.rs
@@ -13,7 +13,7 @@ async fn main() -> Result<(), IndexerError> {
.with_env()
.init();
warn!(
- "WARNING: Iota indexer is still experimental and we expect occasional breaking changes that require backfills."
+ "WARNING: IOTA indexer is still experimental and we expect occasional breaking changes that require backfills."
);
let mut indexer_config = IndexerConfig::parse();
diff --git a/crates/iota-json-rpc-api/Cargo.toml b/crates/iota-json-rpc-api/Cargo.toml
index 7bec4ba6e6c..2d1478439ac 100644
--- a/crates/iota-json-rpc-api/Cargo.toml
+++ b/crates/iota-json-rpc-api/Cargo.toml
@@ -24,7 +24,7 @@ iota-open-rpc.workspace = true
iota-open-rpc-macros.workspace = true
iota-types.workspace = true
# NOTE: It's important to keep the above dependency list short.
-# This and the iota-sdk crate are widely used to develop on Iota and it's valuable
+# This and the iota-sdk crate are widely used to develop on IOTA and it's valuable
# to not have to pull in the entire iota repo for it.
[dev-dependencies]
diff --git a/crates/iota-json-rpc-api/src/coin.rs b/crates/iota-json-rpc-api/src/coin.rs
index f3201e4ec64..23d63eee1de 100644
--- a/crates/iota-json-rpc-api/src/coin.rs
+++ b/crates/iota-json-rpc-api/src/coin.rs
@@ -20,7 +20,7 @@ pub trait CoinReadApi {
#[method(name = "getCoins")]
async fn get_coins(
&self,
- /// the owner's Iota address
+ /// the owner's IOTA address
owner: IotaAddress,
/// optional type name for the coin (e.g., 0x168da5bf1f48dafc111b0a488fa454aca95e0b5e::usdc::USDC), default to 0x2::iota::IOTA if not specified.
coin_type: Option,
@@ -35,7 +35,7 @@ pub trait CoinReadApi {
#[method(name = "getAllCoins")]
async fn get_all_coins(
&self,
- /// the owner's Iota address
+ /// the owner's IOTA address
owner: IotaAddress,
/// optional paging cursor
cursor: Option,
@@ -48,7 +48,7 @@ pub trait CoinReadApi {
#[method(name = "getBalance")]
async fn get_balance(
&self,
- /// the owner's Iota address
+ /// the owner's IOTA address
owner: IotaAddress,
/// optional type names for the coin (e.g., 0x168da5bf1f48dafc111b0a488fa454aca95e0b5e::usdc::USDC), default to 0x2::iota::IOTA if not specified.
coin_type: Option,
@@ -59,7 +59,7 @@ pub trait CoinReadApi {
#[method(name = "getAllBalances")]
async fn get_all_balances(
&self,
- /// the owner's Iota address
+ /// the owner's IOTA address
owner: IotaAddress,
) -> RpcResult>;
diff --git a/crates/iota-json-rpc-api/src/indexer.rs b/crates/iota-json-rpc-api/src/indexer.rs
index b77ab45d2d6..e25363c265d 100644
--- a/crates/iota-json-rpc-api/src/indexer.rs
+++ b/crates/iota-json-rpc-api/src/indexer.rs
@@ -33,7 +33,7 @@ pub trait IndexerApi {
#[method(name = "getOwnedObjects")]
async fn get_owned_objects(
&self,
- /// the owner's Iota address
+ /// the owner's IOTA address
address: IotaAddress,
/// the objects query criteria.
query: Option,
@@ -73,7 +73,7 @@ pub trait IndexerApi {
descending_order: Option,
) -> RpcResult;
- /// Subscribe to a stream of Iota event
+ /// Subscribe to a stream of IOTA event
#[rustfmt::skip]
#[subscription(name = "subscribeEvent", item = IotaEvent)]
fn subscribe_event(
@@ -82,7 +82,7 @@ pub trait IndexerApi {
filter: EventFilter,
) -> SubscriptionResult;
- /// Subscribe to a stream of Iota transaction effects
+ /// Subscribe to a stream of IOTA transaction effects
#[subscription(name = "subscribeTransaction", item = IotaTransactionBlockEffects)]
fn subscribe_transaction(&self, filter: TransactionFilter) -> SubscriptionResult;
diff --git a/crates/iota-json-rpc-api/src/transaction_builder.rs b/crates/iota-json-rpc-api/src/transaction_builder.rs
index eb2019ae1d9..c8fd2d80b8a 100644
--- a/crates/iota-json-rpc-api/src/transaction_builder.rs
+++ b/crates/iota-json-rpc-api/src/transaction_builder.rs
@@ -26,7 +26,7 @@ pub trait TransactionBuilder {
#[method(name = "transferObject")]
async fn transfer_object(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
/// the ID of the object to be transferred
object_id: ObjectID,
@@ -34,22 +34,22 @@ pub trait TransactionBuilder {
gas: Option,
/// the gas budget, the transaction will fail if the gas cost exceed the budget
gas_budget: BigInt,
- /// the recipient's Iota address
+ /// the recipient's IOTA address
recipient: IotaAddress,
) -> RpcResult;
- /// Create an unsigned transaction to send IOTA coin object to a Iota address. The IOTA object is also used as the gas object.
+ /// Create an unsigned transaction to send IOTA coin object to an IOTA address. The IOTA object is also used as the gas object.
#[rustfmt::skip]
#[method(name = "transferIota")]
async fn transfer_iota(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
- /// the Iota coin object to be used in this transaction
+ /// the IOTA coin object to be used in this transaction
iota_object_id: ObjectID,
/// the gas budget, the transaction will fail if the gas cost exceed the budget
gas_budget: BigInt,
- /// the recipient's Iota address
+ /// the recipient's IOTA address
recipient: IotaAddress,
/// the amount to be split out and transferred
amount: Option>,
@@ -63,9 +63,9 @@ pub trait TransactionBuilder {
#[method(name = "pay")]
async fn pay(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
- /// the Iota coins to be used in this transaction
+ /// the IOTA coins to be used in this transaction
input_coins: Vec,
/// the recipients' addresses, the length of this vector must be the same as amounts.
recipients: Vec,
@@ -90,9 +90,9 @@ pub trait TransactionBuilder {
#[method(name = "payIota")]
async fn pay_iota(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
- /// the Iota coins to be used in this transaction, including the coin for gas payment.
+ /// the IOTA coins to be used in this transaction, including the coin for gas payment.
input_coins: Vec,
/// the recipients' addresses, the length of this vector must be the same as amounts.
recipients: Vec,
@@ -113,9 +113,9 @@ pub trait TransactionBuilder {
#[method(name = "payAllIota")]
async fn pay_all_iota(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
- /// the Iota coins to be used in this transaction, including the coin for gas payment.
+ /// the IOTA coins to be used in this transaction, including the coin for gas payment.
input_coins: Vec,
/// the recipient address,
recipient: IotaAddress,
@@ -128,7 +128,7 @@ pub trait TransactionBuilder {
#[method(name = "moveCall")]
async fn move_call(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
/// the Move package ID, e.g. `0x2`
package_object_id: ObjectID,
@@ -153,7 +153,7 @@ pub trait TransactionBuilder {
#[method(name = "publish")]
async fn publish(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
sender: IotaAddress,
/// the compiled bytes of a Move package
compiled_modules: Vec,
@@ -171,7 +171,7 @@ pub trait TransactionBuilder {
#[method(name = "splitCoin")]
async fn split_coin(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
/// the coin object to be spilt
coin_object_id: ObjectID,
@@ -188,7 +188,7 @@ pub trait TransactionBuilder {
#[method(name = "splitCoinEqual")]
async fn split_coin_equal(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
/// the coin object to be spilt
coin_object_id: ObjectID,
@@ -205,7 +205,7 @@ pub trait TransactionBuilder {
#[method(name = "mergeCoins")]
async fn merge_coin(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
/// the coin object to merge into, this coin will remain after the transaction
primary_coin: ObjectID,
@@ -222,7 +222,7 @@ pub trait TransactionBuilder {
#[method(name = "batchTransaction")]
async fn batch_transaction(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
/// list of transaction request parameters
single_transaction_params: Vec,
@@ -239,13 +239,13 @@ pub trait TransactionBuilder {
#[method(name = "requestAddStake")]
async fn request_add_stake(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
/// Coin object to stake
coins: Vec,
/// stake amount
amount: Option>,
- /// the validator's Iota address
+ /// the validator's IOTA address
validator: IotaAddress,
/// gas object to be used in this transaction, node will pick one from the signer's possession if not provided
gas: Option,
@@ -258,7 +258,7 @@ pub trait TransactionBuilder {
#[method(name = "requestWithdrawStake")]
async fn request_withdraw_stake(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
/// StakedIota object ID
staked_iota: ObjectID,
@@ -273,11 +273,11 @@ pub trait TransactionBuilder {
#[method(name = "requestAddTimelockedStake")]
async fn request_add_timelocked_stake(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
/// TimeLock> object to stake
locked_balance: ObjectID,
- /// the validator's Iota address
+ /// the validator's IOTA address
validator: IotaAddress,
/// gas object to be used in this transaction
gas: ObjectID,
@@ -290,7 +290,7 @@ pub trait TransactionBuilder {
#[method(name = "requestWithdrawTimelockedStake")]
async fn request_withdraw_timelocked_stake(
&self,
- /// the transaction signer's Iota address
+ /// the transaction signer's IOTA address
signer: IotaAddress,
/// TimelockedStakedIota object ID
timelocked_staked_iota: ObjectID,
diff --git a/crates/iota-json-rpc-types/src/iota_event.rs b/crates/iota-json-rpc-types/src/iota_event.rs
index 80ed4023f0d..828ddb8450f 100644
--- a/crates/iota-json-rpc-types/src/iota_event.rs
+++ b/crates/iota-json-rpc-types/src/iota_event.rs
@@ -44,7 +44,7 @@ pub struct IotaEvent {
#[serde_as(as = "DisplayFromStr")]
/// Move module where this event was emitted.
pub transaction_module: Identifier,
- /// Sender's Iota address.
+ /// Sender's IOTA address.
pub sender: IotaAddress,
#[schemars(with = "String")]
#[serde_as(as = "IotaStructTag")]
diff --git a/crates/iota-json-rpc-types/src/iota_move.rs b/crates/iota-json-rpc-types/src/iota_move.rs
index 239afb24a09..feb3ce0264d 100644
--- a/crates/iota-json-rpc-types/src/iota_move.rs
+++ b/crates/iota-json-rpc-types/src/iota_move.rs
@@ -376,7 +376,7 @@ impl From for IotaMoveValue {
IotaMoveValue::Vector(values.into_iter().map(|value| value.into()).collect())
}
MoveValue::Struct(value) => {
- // Best effort Iota core type conversion
+ // Best effort IOTA core type conversion
let MoveStruct { type_, fields } = &value;
if let Some(value) = try_convert_type(type_, fields) {
return value;
diff --git a/crates/iota-json-rpc-types/src/iota_transaction.rs b/crates/iota-json-rpc-types/src/iota_transaction.rs
index 23e4cdfc8c0..1c044f64ab2 100644
--- a/crates/iota-json-rpc-types/src/iota_transaction.rs
+++ b/crates/iota-json-rpc-types/src/iota_transaction.rs
@@ -1249,7 +1249,7 @@ impl DevInspectResults {
#[derive(Eq, PartialEq, Clone, Debug, Serialize, Deserialize, JsonSchema)]
pub enum IotaTransactionBlockBuilderMode {
- /// Regular Iota Transactions that are committed on chain
+ /// Regular IOTA Transactions that are committed on chain
Commit,
/// Simulated transaction that allows calling any Move function with
/// arbitrary values.
diff --git a/crates/iota-json-rpc/src/lib.rs b/crates/iota-json-rpc/src/lib.rs
index 26db25d957a..97bf87e233b 100644
--- a/crates/iota-json-rpc/src/lib.rs
+++ b/crates/iota-json-rpc/src/lib.rs
@@ -71,7 +71,7 @@ pub fn iota_rpc_doc(version: &str) -> Project {
Project::new(
version,
"IOTA JSON-RPC",
- "IOTA JSON-RPC API for interaction with Iota Full node. Make RPC calls using https://api.NETWORK.iota.cafe:443, where NETWORK is the network you want to use (testnet, devnet, mainnet). By default, local networks use port 9000.",
+ "IOTA JSON-RPC API for interaction with IOTA Full node. Make RPC calls using https://api.NETWORK.iota.cafe:443, where NETWORK is the network you want to use (testnet, devnet, mainnet). By default, local networks use port 9000.",
"IOTA Foundation",
"https://iota.org",
"info@iota.org",
@@ -257,7 +257,7 @@ impl JsonRpcServerBuilder {
let handle = ServerHandle {
handle: ServerHandleInner::Axum(handle),
};
- info!(local_addr =? addr, "Iota JSON-RPC server listening on {addr}");
+ info!(local_addr =? addr, "IOTA JSON-RPC server listening on {addr}");
Ok(handle)
}
}
diff --git a/crates/iota-keys/src/keypair_file.rs b/crates/iota-keys/src/keypair_file.rs
index 1a2c9dffaf4..21bf12f6f7f 100644
--- a/crates/iota-keys/src/keypair_file.rs
+++ b/crates/iota-keys/src/keypair_file.rs
@@ -88,7 +88,7 @@ pub fn read_key(path: &PathBuf, require_secp256k1: bool) -> Result Result<(), anyhow::Error> {
let phrase = "result crisp session latin must fruit genuine question prevent start coconut brave speak student dismiss";
diff --git a/crates/iota-light-client/README.md b/crates/iota-light-client/README.md
index 4564de9edb5..381e459ac4b 100644
--- a/crates/iota-light-client/README.md
+++ b/crates/iota-light-client/README.md
@@ -1,4 +1,4 @@
-This crate contains a Command Line Interface light client for Iota.
+This crate contains a Command Line Interface light client for IOTA.
# What is a light client?
@@ -6,7 +6,7 @@ A light client allows checking the authenticity and validity of on-chain state,
Running a _full node_ requires downloading the full sequence of all transaction and re-executing them. Then the full state of the blockchain is available locally to serve reads. This is however an expensive process in terms of network bandwidth needed to download the full sequence of transactions, as well as CPU to re-execute it, and storage to store the full state of the blockchain.
-Alternatively, a _light client_ only needs to download minimal information to authenticate blockchain state. Specifically in Iota, the light client needs to _sync_ all end-of-epoch checkpoints that contain information about the committee in the next epoch. Sync involves downloading the checkpoints and checking their validity by checking their certificate.
+Alternatively, a _light client_ only needs to download minimal information to authenticate blockchain state. Specifically in IOTA, the light client needs to _sync_ all end-of-epoch checkpoints that contain information about the committee in the next epoch. Sync involves downloading the checkpoints and checking their validity by checking their certificate.
Once all end-of-epoch checkpoints are downloaded and checked, any event or current object can be checked for its validity. To do that the light client downloads the checkpoint in which the transaction was executed, and the effects structure that summarizes its effects on the system, including events emitted and objects created. The chain of validity from the checkpoint to the effects and its contents is checked via the certificate on the checkpoint and the hashes of all structures.
@@ -20,7 +20,7 @@ The light client requires a config file and a directory to cache checkpoints, an
## Setup
-The config file for the light client takes a URL for a full node, a directory (that must exist) and within the directory to name of the genesis blob for the Iota network.
+The config file for the light client takes a URL for a full node, a directory (that must exist) and within the directory to name of the genesis blob for the IOTA network.
```
full_node_url: "https://api.testnet.iota.cafe:443"
@@ -28,7 +28,7 @@ checkpoint_summary_dir: "checkpoints_dir"
genesis_filename: "genesis.blob"
```
-The genesis blob for the Iota mainnet can be found here: https://github.com/iotaledger/iota-genesis/blob/main/mainnet/genesis.blob
+The genesis blob for the IOTA mainnet can be found here: https://github.com/iotaledger/iota-genesis/blob/main/mainnet/genesis.blob
## Sync
diff --git a/crates/iota-light-client/src/bin/light_client.rs b/crates/iota-light-client/src/bin/light_client.rs
index 1db8daab15f..e99ef02494c 100644
--- a/crates/iota-light-client/src/bin/light_client.rs
+++ b/crates/iota-light-client/src/bin/light_client.rs
@@ -13,7 +13,7 @@ use iota_light_client::utils::{
use iota_package_resolver::Resolver;
use iota_types::{base_types::ObjectID, digests::TransactionDigest, object::Data};
-/// A light client for the Iota blockchain
+/// A light client for the IOTA blockchain
#[derive(Parser, Debug)]
#[command(author, version, about, long_about = None)]
struct Args {
diff --git a/crates/iota-light-client/src/proof.rs b/crates/iota-light-client/src/proof.rs
index 36d2ee30a6f..96058205b7f 100644
--- a/crates/iota-light-client/src/proof.rs
+++ b/crates/iota-light-client/src/proof.rs
@@ -13,7 +13,7 @@ use iota_types::{
transaction::Transaction,
};
-/// Define aspect of Iota state that needs to be certified in a proof
+/// Define aspect of IOTA state that needs to be certified in a proof
#[derive(Default)]
pub struct ProofTarget {
/// Objects that need to be certified.
diff --git a/crates/iota-move-build/Cargo.toml b/crates/iota-move-build/Cargo.toml
index 5ddcd6b91f3..5d4a7e73622 100644
--- a/crates/iota-move-build/Cargo.toml
+++ b/crates/iota-move-build/Cargo.toml
@@ -5,7 +5,7 @@ authors = ["IOTA Foundation "]
edition = "2021"
license = "Apache-2.0"
publish = false
-description = "Logic for building Iota Move Packages"
+description = "Logic for building IOTA Move Packages"
[dependencies]
# external dependencies
diff --git a/crates/iota-move-build/src/lib.rs b/crates/iota-move-build/src/lib.rs
index 309885fcbf1..d3215b3b1ef 100644
--- a/crates/iota-move-build/src/lib.rs
+++ b/crates/iota-move-build/src/lib.rs
@@ -54,7 +54,7 @@ use serde_reflection::Registry;
#[path = "unit_tests/build_tests.rs"]
mod build_tests;
-/// Wrapper around the core Move `CompiledPackage` with some Iota-specific
+/// Wrapper around the core Move `CompiledPackage` with some IOTA-specific
/// traits and info
#[derive(Debug, Clone)]
pub struct CompiledPackage {
@@ -65,7 +65,7 @@ pub struct CompiledPackage {
pub dependency_ids: PackageDependencies,
}
-/// Wrapper around the core Move `BuildConfig` with some Iota-specific info
+/// Wrapper around the core Move `BuildConfig` with some IOTA-specific info
#[derive(Clone)]
pub struct BuildConfig {
pub config: MoveBuildConfig,
@@ -156,7 +156,7 @@ impl BuildConfig {
}
/// Given a `path` and a `build_config`, build the package in that path,
- /// including its dependencies. If we are building the Iota framework,
+ /// including its dependencies. If we are building the IOTA framework,
/// we skip the check that the addresses should be 0
pub fn build(self, path: &Path) -> IotaResult {
let print_diags_to_stderr = self.print_diags_to_stderr;
@@ -337,7 +337,7 @@ impl CompiledPackage {
} else {
// Collect all module IDs from the current package to be published (module names
// are not sufficient as we may have modules with the same names in
- // user code and in Iota framework which would result in the latter
+ // user code and in IOTA framework which would result in the latter
// being pulled into a set of modules to be published).
let self_modules: HashSet<_> = self
.package
@@ -396,13 +396,13 @@ impl CompiledPackage {
.filter(|m| *m.self_id().address() == BRIDGE_ADDRESS)
}
- /// Get bytecode modules from the Iota System that are used by this package
+ /// Get bytecode modules from the IOTA System that are used by this package
pub fn get_iota_system_modules(&self) -> impl Iterator {
self.get_modules_and_deps()
.filter(|m| *m.self_id().address() == IOTA_SYSTEM_ADDRESS)
}
- /// Get bytecode modules from the Iota Framework that are used by this
+ /// Get bytecode modules from the IOTA Framework that are used by this
/// package
pub fn get_iota_framework_modules(&self) -> impl Iterator {
self.get_modules_and_deps()
diff --git a/crates/iota-move-build/src/unit_tests/build_tests.rs b/crates/iota-move-build/src/unit_tests/build_tests.rs
index 992a1095bee..e32e4bf0fef 100644
--- a/crates/iota-move-build/src/unit_tests/build_tests.rs
+++ b/crates/iota-move-build/src/unit_tests/build_tests.rs
@@ -8,7 +8,7 @@ use crate::BuildConfig;
#[test]
fn generate_struct_layouts() {
- // build the Iota framework and generate struct layouts to make sure nothing
+ // build the IOTA framework and generate struct layouts to make sure nothing
// crashes
let path = Path::new(env!("CARGO_MANIFEST_DIR"))
.parent()
diff --git a/crates/iota-move/src/iota-natives.bpl b/crates/iota-move/src/iota-natives.bpl
index f9825430840..845c461720a 100644
--- a/crates/iota-move/src/iota-natives.bpl
+++ b/crates/iota-move/src/iota-natives.bpl
@@ -53,7 +53,7 @@ procedure {:inline 1} $2_tx_context_derive_id(tx_hash: Vec (int), ids_created: i
{%- set T = instance.name -%}
// ----------------------------------------------------------------------------------
-// Native Iota event implementation for object type `{{instance.suffix}}`
+// Native IOTA event implementation for object type `{{instance.suffix}}`
procedure {:inline 1} $2_event_emit{{S}}(event: {{T}});
@@ -69,7 +69,7 @@ procedure {:inline 1} $2_event_emit{{S}}(event: {{T}});
{%- set T = instance.name -%}
// ----------------------------------------------------------------------------------
-// Native Iota types implementation for object type `{{instance.suffix}}`
+// Native IOTA types implementation for object type `{{instance.suffix}}`
procedure {:inline 1} $2_types_is_one_time_witness{{S}}(_: {{T}}) returns (res: bool);
@@ -112,7 +112,7 @@ procedure {:inline 1} $2_dynamic_field_has_child_object_with_ty{{S}}(parent: int
{%- set T = instance.name -%}
// ----------------------------------------------------------------------------------
-// Native Iota prover implementation for object type `{{instance.suffix}}`
+// Native IOTA prover implementation for object type `{{instance.suffix}}`
function $2_prover_vec_remove{{S}}(v: Vec ({{T}}), elem_idx: int): Vec ({{T}}) {
RemoveAtVec(v, elem_idx)
diff --git a/crates/iota-move/src/main.rs b/crates/iota-move/src/main.rs
index d18514582a3..17933267102 100644
--- a/crates/iota-move/src/main.rs
+++ b/crates/iota-move/src/main.rs
@@ -17,7 +17,7 @@ bin_version::bin_version!();
#[derive(Parser)]
#[clap(
name = env!("CARGO_BIN_NAME"),
- about = "Iota-Move CLI",
+ about = "IOTA Move CLI",
rename_all = "kebab-case",
author,
version = VERSION,
@@ -64,7 +64,7 @@ async fn main() {
.with_log_file(&format!("{bin_name}.log"))
.with_env()
.init();
- debug!("Iota-Move CLI version: {VERSION}");
+ debug!("IOTA Move CLI version: {VERSION}");
exit_main!(execute_move_command(
args.package_path.as_deref(),
diff --git a/crates/iota-move/src/unit_test.rs b/crates/iota-move/src/unit_test.rs
index f85d7689d7d..39a7855ca2b 100644
--- a/crates/iota-move/src/unit_test.rs
+++ b/crates/iota-move/src/unit_test.rs
@@ -47,7 +47,7 @@ impl Test {
let compute_coverage = self.test.compute_coverage;
if !cfg!(debug_assertions) && compute_coverage {
return Err(anyhow::anyhow!(
- "The --coverage flag is currently supported only in debug builds. Please build the Iota CLI from source in debug mode."
+ "The --coverage flag is currently supported only in debug builds. Please build the IOTA CLI from source in debug mode."
));
}
// find manifest file directory from a given path or (if missing) from current
diff --git a/crates/iota-node/src/lib.rs b/crates/iota-node/src/lib.rs
index b03875abfdd..9469e669aa1 100644
--- a/crates/iota-node/src/lib.rs
+++ b/crates/iota-node/src/lib.rs
@@ -1575,7 +1575,7 @@ impl IotaNode {
.state
.get_object_cache_reader()
.get_iota_system_state_object_unsafe()
- .expect("Read Iota System State object cannot fail");
+ .expect("Read IOTA System State object cannot fail");
#[cfg(msim)]
if !self
@@ -2082,7 +2082,7 @@ pub async fn build_http_server(
.unwrap()
});
- info!(local_addr =? addr, "Iota JSON-RPC server listening on {addr}");
+ info!(local_addr =? addr, "IOTA JSON-RPC server listening on {addr}");
Ok(Some(handle))
}
diff --git a/crates/iota-node/src/main.rs b/crates/iota-node/src/main.rs
index debd3a54968..995b03d366e 100644
--- a/crates/iota-node/src/main.rs
+++ b/crates/iota-node/src/main.rs
@@ -149,7 +149,7 @@ fn main() {
None => "unknown".to_string(),
};
- info!("Iota chain identifier: {chain_identifier}");
+ info!("IOTA chain identifier: {chain_identifier}");
prometheus_registry
.register(iota_metrics::uptime_metric(
if is_validator {
diff --git a/crates/iota-open-rpc-macros/src/lib.rs b/crates/iota-open-rpc-macros/src/lib.rs
index cddbf557130..78e15b0eadc 100644
--- a/crates/iota-open-rpc-macros/src/lib.rs
+++ b/crates/iota-open-rpc-macros/src/lib.rs
@@ -261,7 +261,7 @@ fn parse_rpc_method(trait_data: &mut syn::ItemTrait) -> Result TokenStream2 {
let attrs = attributes
.attrs
diff --git a/crates/iota-open-rpc/spec/openrpc.json b/crates/iota-open-rpc/spec/openrpc.json
index f8a243fbc9c..3ce7d818f3c 100644
--- a/crates/iota-open-rpc/spec/openrpc.json
+++ b/crates/iota-open-rpc/spec/openrpc.json
@@ -2,7 +2,7 @@
"openrpc": "1.2.6",
"info": {
"title": "IOTA JSON-RPC",
- "description": "IOTA JSON-RPC API for interaction with Iota Full node. Make RPC calls using https://api.NETWORK.iota.cafe:443, where NETWORK is the network you want to use (testnet, devnet, mainnet). By default, local networks use port 9000.",
+ "description": "IOTA JSON-RPC API for interaction with IOTA Full node. Make RPC calls using https://api.NETWORK.iota.cafe:443, where NETWORK is the network you want to use (testnet, devnet, mainnet). By default, local networks use port 9000.",
"contact": {
"name": "IOTA Foundation",
"url": "https://iota.org",
@@ -3164,7 +3164,7 @@
"params": [
{
"name": "owner",
- "description": "the owner's Iota address",
+ "description": "the owner's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -3214,7 +3214,7 @@
"params": [
{
"name": "owner",
- "description": "the owner's Iota address",
+ "description": "the owner's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -3334,7 +3334,7 @@
"params": [
{
"name": "owner",
- "description": "the owner's Iota address",
+ "description": "the owner's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -3463,7 +3463,7 @@
"params": [
{
"name": "owner",
- "description": "the owner's Iota address",
+ "description": "the owner's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -3984,7 +3984,7 @@
"params": [
{
"name": "address",
- "description": "the owner's Iota address",
+ "description": "the owner's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -4702,7 +4702,7 @@
"name": "PubSub"
}
],
- "description": "Subscribe to a stream of Iota event",
+ "description": "Subscribe to a stream of IOTA event",
"params": [
{
"name": "filter",
@@ -4734,7 +4734,7 @@
"name": "PubSub"
}
],
- "description": "Subscribe to a stream of Iota transaction effects",
+ "description": "Subscribe to a stream of IOTA transaction effects",
"params": [
{
"name": "filter",
@@ -4763,7 +4763,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -4822,7 +4822,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -4879,7 +4879,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -4973,7 +4973,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -4981,7 +4981,7 @@
},
{
"name": "input_coins",
- "description": "the Iota coins to be used in this transaction",
+ "description": "the IOTA coins to be used in this transaction",
"required": true,
"schema": {
"type": "array",
@@ -5047,7 +5047,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5055,7 +5055,7 @@
},
{
"name": "input_coins",
- "description": "the Iota coins to be used in this transaction, including the coin for gas payment.",
+ "description": "the IOTA coins to be used in this transaction, including the coin for gas payment.",
"required": true,
"schema": {
"type": "array",
@@ -5100,7 +5100,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5108,7 +5108,7 @@
},
{
"name": "input_coins",
- "description": "the Iota coins to be used in this transaction, including the coin for gas payment.",
+ "description": "the IOTA coins to be used in this transaction, including the coin for gas payment.",
"required": true,
"schema": {
"type": "array",
@@ -5167,7 +5167,7 @@
"params": [
{
"name": "sender",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5230,7 +5230,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5256,7 +5256,7 @@
},
{
"name": "validator",
- "description": "the validator's Iota address",
+ "description": "the validator's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5297,7 +5297,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5313,7 +5313,7 @@
},
{
"name": "validator",
- "description": "the validator's Iota address",
+ "description": "the validator's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5355,7 +5355,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5404,7 +5404,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5454,7 +5454,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5514,7 +5514,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5567,11 +5567,11 @@
"name": "Transaction Builder API"
}
],
- "description": "Create an unsigned transaction to send IOTA coin object to a Iota address. The IOTA object is also used as the gas object.",
+ "description": "Create an unsigned transaction to send IOTA coin object to an IOTA address. The IOTA object is also used as the gas object.",
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5579,7 +5579,7 @@
},
{
"name": "iota_object_id",
- "description": "the Iota coin object to be used in this transaction",
+ "description": "the IOTA coin object to be used in this transaction",
"required": true,
"schema": {
"$ref": "#/components/schemas/ObjectID"
@@ -5595,7 +5595,7 @@
},
{
"name": "recipient",
- "description": "the recipient's Iota address",
+ "description": "the recipient's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5628,7 +5628,7 @@
"params": [
{
"name": "signer",
- "description": "the transaction signer's Iota address",
+ "description": "the transaction signer's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5659,7 +5659,7 @@
},
{
"name": "recipient",
- "description": "the recipient's Iota address",
+ "description": "the recipient's IOTA address",
"required": true,
"schema": {
"$ref": "#/components/schemas/IotaAddress"
@@ -5728,7 +5728,7 @@
}
},
"AuthorityPublicKeyBytes": {
- "description": "Defines the compressed version of the public key that we pass around in Iota",
+ "description": "Defines the compressed version of the public key that we pass around in IOTA.",
"allOf": [
{
"$ref": "#/components/schemas/Base64"
@@ -6773,7 +6773,7 @@
"description": "Parsed json value of the event"
},
"sender": {
- "description": "Sender's Iota address.",
+ "description": "Sender's IOTA address.",
"allOf": [
{
"$ref": "#/components/schemas/IotaAddress"
@@ -7051,7 +7051,7 @@
]
},
"EventID": {
- "description": "Unique ID of a Iota Event, the ID is a combination of tx seq number and event seq number, the ID is local to this particular fullnode and will be different from other fullnode.",
+ "description": "Unique ID of an IOTA Event, the ID is a combination of tx seq number and event seq number, the ID is local to this particular fullnode and will be different from other fullnode.",
"type": "object",
"required": [
"eventSeq",
@@ -8793,7 +8793,7 @@
"IotaTransactionBlockBuilderMode": {
"oneOf": [
{
- "description": "Regular Iota Transactions that are committed on chain",
+ "description": "Regular IOTA Transactions that are committed on chain",
"type": "string",
"enum": [
"Commit"
diff --git a/crates/iota-open-rpc/src/generate_json_rpc_spec.rs b/crates/iota-open-rpc/src/generate_json_rpc_spec.rs
index 6f15290df3c..80dce7b85bc 100644
--- a/crates/iota-open-rpc/src/generate_json_rpc_spec.rs
+++ b/crates/iota-open-rpc/src/generate_json_rpc_spec.rs
@@ -29,8 +29,8 @@ enum Action {
#[derive(Debug, Parser)]
#[clap(
- name = "Iota format generator",
- about = "Trace serde (de)serialization to generate format descriptions for Iota types"
+ name = "IOTA format generator",
+ about = "Trace serde (de)serialization to generate format descriptions for IOTA types"
)]
struct Options {
#[clap(value_enum, default_value = "Record", ignore_case = true)]
diff --git a/crates/iota-open-rpc/src/lib.rs b/crates/iota-open-rpc/src/lib.rs
index 829f2c0d19c..e3ced320aa9 100644
--- a/crates/iota-open-rpc/src/lib.rs
+++ b/crates/iota-open-rpc/src/lib.rs
@@ -17,7 +17,7 @@ use versions::Versioning;
/// OPEN-RPC documentation following the OpenRPC specification
/// The implementation is partial, only required fields and subset of optional
-/// fields in the specification are implemented catered to Iota's need.
+/// fields in the specification are implemented catered to IOTA's need.
#[derive(Serialize, Deserialize, Clone)]
pub struct Project {
openrpc: String,
diff --git a/crates/iota-package-dump/src/client.rs b/crates/iota-package-dump/src/client.rs
index ee96573c704..fdd1afc50e1 100644
--- a/crates/iota-package-dump/src/client.rs
+++ b/crates/iota-package-dump/src/client.rs
@@ -13,7 +13,8 @@ pub(crate) struct Client {
}
impl Client {
- /// Create a new GraphQL client, talking to a Iota GraphQL service at `url`.
+ /// Create a new GraphQL client, talking to an IOTA GraphQL service at
+ /// `url`.
pub(crate) fn new(url: impl IntoUrl) -> Result {
Ok(Self {
inner: reqwest::Client::builder()
diff --git a/crates/iota-protocol-config/src/lib.rs b/crates/iota-protocol-config/src/lib.rs
index 829eaddfab2..b87e01cc899 100644
--- a/crates/iota-protocol-config/src/lib.rs
+++ b/crates/iota-protocol-config/src/lib.rs
@@ -309,12 +309,12 @@ pub struct ProtocolConfig {
max_input_objects: Option,
/// Max size of objects a transaction can write to disk after completion.
- /// Enforce by the Iota adapter. This is the sum of the serialized size
+ /// Enforce by the IOTA adapter. This is the sum of the serialized size
/// of all objects written to disk. The max size of individual objects
/// on the other hand is `max_move_object_size`.
max_size_written_objects: Option,
/// Max size of objects a system transaction can write to disk after
- /// completion. Enforce by the Iota adapter. Similar to
+ /// completion. Enforce by the IOTA adapter. Similar to
/// `max_size_written_objects` but for system transactions.
max_size_written_objects_system_tx: Option,
@@ -378,12 +378,12 @@ pub struct ProtocolConfig {
binary_variant_instantiation_handles: Option,
/// Maximum size of the `contents` part of an object, in bytes. Enforced by
- /// the Iota adapter when effects are produced.
+ /// the IOTA adapter when effects are produced.
max_move_object_size: Option,
// TODO: Option 500 KB exceeds the max
// computation gas cost
- /// Maximum size of a Move package object, in bytes. Enforced by the Iota
+ /// Maximum size of a Move package object, in bytes. Enforced by the IOTA
/// adapter at the end of a publish transaction.
max_move_package_size: Option,
@@ -540,7 +540,7 @@ pub struct ProtocolConfig {
// === Execution gas costs ====
//
- /// Base cost for any Iota transaction
+ /// Base cost for any IOTA transaction
base_tx_cost_fixed: Option,
/// Additional cost for a transaction that publishes a package
@@ -585,11 +585,11 @@ pub struct ProtocolConfig {
// === Storage gas costs ===
//
- /// Per-byte cost of storing an object in the Iota global object store. Some
+ /// Per-byte cost of storing an object in the IOTA global object store. Some
/// of this cost may be refundable if the object is later freed
obj_data_cost_refundable: Option,
- // Per-byte cost of storing an object in the Iota transaction log (e.g., in
+ // Per-byte cost of storing an object in the IOTA transaction log (e.g., in
// CertifiedTransactionEffects) This depends on the size of various fields including the
// effects TODO: Option,
diff --git a/crates/iota-rest-api/openapi/openapi.json b/crates/iota-rest-api/openapi/openapi.json
index 3b39f531479..7213f28e1f5 100644
--- a/crates/iota-rest-api/openapi/openapi.json
+++ b/crates/iota-rest-api/openapi/openapi.json
@@ -858,7 +858,7 @@
},
"Address": {
"title": "Address",
- "description": "A 32-byte Iota address, encoded as a hex string.",
+ "description": "A 32-byte IOTA address, encoded as a hex string.",
"examples": [
"0x0000000000000000000000000000000000000000000000000000000000000002"
],
@@ -2213,7 +2213,7 @@
}
},
{
- "description": "Iota Move Bytecode Verification Error.",
+ "description": "IOTA Move Bytecode Verification Error.",
"type": "object",
"required": [
"error"
@@ -2593,7 +2593,7 @@
}
},
{
- "description": "Iota Move Bytecode verification timed out.",
+ "description": "IOTA Move Bytecode verification timed out.",
"type": "object",
"required": [
"error"
diff --git a/crates/iota-rosetta/README.md b/crates/iota-rosetta/README.md
index d5d9a86af67..1f618ff682a 100644
--- a/crates/iota-rosetta/README.md
+++ b/crates/iota-rosetta/README.md
@@ -6,14 +6,14 @@ integration.
## Overview
-Iota-Rosetta is an implementation of the Rosetta API for the Iota network, the Iota-Rosetta server uses the IOTA fullnode to
-read and write transactions to the Iota network.
+`iota-rosetta` is an implementation of the Rosetta API for the IOTA network, the `iota-rosetta` server uses the IOTA fullnode to
+read and write transactions to the IOTA network.
## Local network quick start
### Build from source
-#### 0. Checkout and build Iota
+#### 0. Checkout and build IOTA
Checkout the [IOTA source code](https://github.com/iotaledger/iota) and compile using `cargo build --release`, the binaries will be located in `target/release` directory.
@@ -94,27 +94,27 @@ docker run iotaledger/iota-rosetta-devnet iota-rosetta start-offline-server
### Account
-| Method | Endpoint | Description | Iota Supported? | Server Type |
+| Method | Endpoint | Description | IOTA Supported? | Server Type |
| ------ | ---------------- | ------------------------------ | :-------------: | :---------: |
| POST | /account/balance | Get an Account's Balance | Yes | Online |
| POST | /account/coins | Get an Account's Unspent Coins | Yes | Online |
### Block
-| Method | Endpoint | Description | Iota Supported? | Server Type |
+| Method | Endpoint | Description | IOTA Supported? | Server Type |
| ------ | ------------------ | ----------------------- | :----------------------------------------------------------------------------------------: | :---------: |
-| POST | /block | Get a Block | Yes (One transaction per block in phase 1, will be replaced by Iota checkpoint in phase 2) | Online |
+| POST | /block | Get a Block | Yes (One transaction per block in phase 1, will be replaced by IOTA checkpoint in phase 2) | Online |
| POST | /block/transaction | Get a Block Transaction | Yes | Online |
### Call
-| Method | Endpoint | Description | Iota Supported? | Server Type |
+| Method | Endpoint | Description | IOTA Supported? | Server Type |
| ------ | -------- | -------------------------------------- | :-------------: | :---------: |
| POST | /call | Make a Network-Specific Procedure Call | No | -- |
### Construction
-| Method | Endpoint | Description | Iota Supported? | Server Type |
+| Method | Endpoint | Description | IOTA Supported? | Server Type |
| ------ | ------------------------ | ----------------------------------------------------- | :-------------: | :---------: |
| POST | /construction/combine | Create Network Transaction from Signatures | Yes | Offline |
| POST | /construction/derive | Derive an AccountIdentifier from a PublicKey | Yes | Offline |
@@ -127,20 +127,20 @@ docker run iotaledger/iota-rosetta-devnet iota-rosetta start-offline-server
### Events
-| Method | Endpoint | Description | Iota Supported? | Server Type |
+| Method | Endpoint | Description | IOTA Supported? | Server Type |
| ------ | -------------- | ------------------------------------ | :-------------: | :---------: |
| POST | /events/blocks | [INDEXER] Get a range of BlockEvents | No | -- |
### Mempool
-| Method | Endpoint | Description | Iota Supported? | Server Type |
+| Method | Endpoint | Description | IOTA Supported? | Server Type |
| ------ | -------------------- | ---------------------------- | :-------------: | :---------: |
| POST | /mempool | Get All Mempool Transactions | No | -- |
| POST | /mempool/transaction | Get a Mempool Transaction | No | -- |
### Network
-| Method | Endpoint | Description | Iota Supported? | Server Type |
+| Method | Endpoint | Description | IOTA Supported? | Server Type |
| ------ | ---------------- | ------------------------------ | :-------------: | :------------: |
| POST | /network/list | Get List of Available Networks | Yes | Online/Offline |
| POST | /network/options | Get Network Options | Yes | Online/Offline |
@@ -148,13 +148,13 @@ docker run iotaledger/iota-rosetta-devnet iota-rosetta start-offline-server
### Search
-| Method | Endpoint | Description | Iota Supported? | Server Type |
+| Method | Endpoint | Description | IOTA Supported? | Server Type |
| ------ | -------------------- | --------------------------------- | :-------------: | :---------: |
| POST | /search/transactions | [INDEXER] Search for Transactions | No | -- |
-## Iota transaction <> Rosetta Operation conversion explained
+## IOTA transaction <> Rosetta Operation conversion explained
-There are 2 places we convert Iota's transaction to Rosetta's operations,
+There are 2 places we convert IOTA's transaction to Rosetta's operations,
one is in the `/construction/parse` endpoint and another one in `/block/transaction endpoint`.
`/operation/parse` uses `Operation::from_data` to create the "intent" operations and `/block/transaction` uses `Operation::from_data_and_effect` to create the "confirmed" operations.
the `/construction/parse` endpoint is used for checking transaction correctness during transaction construction, in our case we only support `TransferIota` for now, the operations created looks like this (negative amount indicate sender):
diff --git a/crates/iota-rosetta/src/construction.rs b/crates/iota-rosetta/src/construction.rs
index d7fe9e365da..c9d3ead2a93 100644
--- a/crates/iota-rosetta/src/construction.rs
+++ b/crates/iota-rosetta/src/construction.rs
@@ -235,7 +235,7 @@ pub async fn hash(
}
/// Get any information required to construct a transaction for a specific
-/// network. For Iota, we are returning the latest object refs for all the input
+/// network. For IOTA, we are returning the latest object refs for all the input
/// objects, which will be used in transaction construction.
///
/// [Rosetta API Spec](https://www.rosetta-api.org/docs/ConstructionApi.html#constructionmetadata)
diff --git a/crates/iota-rosetta/src/errors.rs b/crates/iota-rosetta/src/errors.rs
index 854be4f1967..943048a4659 100644
--- a/crates/iota-rosetta/src/errors.rs
+++ b/crates/iota-rosetta/src/errors.rs
@@ -21,7 +21,7 @@ use typed_store::TypedStoreError;
use crate::types::{BlockHash, IotaEnv, OperationType, PublicKey};
-/// Iota-Rosetta specific error types.
+/// IOTA Rosetta specific error types.
/// This contains all the errors returns by the iota-rosetta server.
#[derive(Debug, Error, EnumDiscriminants, EnumProperty)]
#[strum_discriminants(
diff --git a/crates/iota-rosetta/src/lib.rs b/crates/iota-rosetta/src/lib.rs
index 074d37ece34..16b7e829f7a 100644
--- a/crates/iota-rosetta/src/lib.rs
+++ b/crates/iota-rosetta/src/lib.rs
@@ -62,7 +62,7 @@ impl RosettaOnlineServer {
let listener = tokio::net::TcpListener::bind(&addr).await.unwrap();
info!(
- "Iota Rosetta online server listening on {}",
+ "IOTA Rosetta online server listening on {}",
listener.local_addr().unwrap()
);
axum::serve(listener, app).await.unwrap();
@@ -93,7 +93,7 @@ impl RosettaOfflineServer {
let listener = tokio::net::TcpListener::bind(&addr).await.unwrap();
info!(
- "Iota Rosetta offline server listening on {}",
+ "IOTA Rosetta offline server listening on {}",
listener.local_addr().unwrap()
);
axum::serve(listener, app).await.unwrap();
diff --git a/crates/iota-rosetta/src/main.rs b/crates/iota-rosetta/src/main.rs
index 0d8405d576e..1f17a61a950 100644
--- a/crates/iota-rosetta/src/main.rs
+++ b/crates/iota-rosetta/src/main.rs
@@ -87,7 +87,7 @@ impl RosettaServerCommand {
let prefunded_accounts = read_prefunded_account(&path)?;
info!(
- "Retrieved {} Iota address from keystore file {:?}",
+ "Retrieved {} IOTA address from keystore file {:?}",
prefunded_accounts.len(),
&path
);
@@ -145,7 +145,7 @@ impl RosettaServerCommand {
data_path,
} => {
info!(
- "Starting Rosetta Online Server with remove Iota full node [{full_node_url}]."
+ "Starting Rosetta Online Server with remove IOTA full node [{full_node_url}]."
);
let iota_client = wait_for_iota_client(full_node_url).await;
let rosetta_path = data_path.join("rosetta_db");
@@ -160,7 +160,7 @@ impl RosettaServerCommand {
node_config,
data_path,
} => {
- info!("Starting Rosetta Online Server with embedded Iota full node.");
+ info!("Starting Rosetta Online Server with embedded IOTA full node.");
info!("Data directory path: {data_path:?}");
let node_config = node_config.unwrap_or_else(|| {
@@ -171,7 +171,7 @@ impl RosettaServerCommand {
let mut config = NodeConfig::load(&node_config)?;
config.db_path = data_path.join("iota_db");
- info!("Overriding Iota db path to : {:?}", config.db_path);
+ info!("Overriding IOTA db path to : {:?}", config.db_path);
let registry_service =
iota_metrics::start_prometheus_server(config.metrics_address);
@@ -201,7 +201,7 @@ async fn wait_for_iota_client(rpc_address: String) -> IotaClient {
Ok(client) => return client,
Err(e) => {
warn!(
- "Error connecting to Iota RPC server [{rpc_address}]: {e}, retrying in 5 seconds."
+ "Error connecting to IOTA RPC server [{rpc_address}]: {e}, retrying in 5 seconds."
);
tokio::time::sleep(Duration::from_millis(5000)).await;
}
@@ -209,7 +209,7 @@ async fn wait_for_iota_client(rpc_address: String) -> IotaClient {
}
}
-/// This method reads the keypairs from the Iota keystore to create the
+/// This method reads the keypairs from the IOTA keystore to create the
/// PrefundedAccount objects, PrefundedAccount will be written to the
/// rosetta-cli config file for testing.
fn read_prefunded_account(path: &Path) -> Result, anyhow::Error> {
diff --git a/crates/iota-rosetta/src/operations.rs b/crates/iota-rosetta/src/operations.rs
index e2810e19b79..e2a990b65ff 100644
--- a/crates/iota-rosetta/src/operations.rs
+++ b/crates/iota-rosetta/src/operations.rs
@@ -280,7 +280,7 @@ impl Operations {
let KnownValue::GasCoin(_) = resolve_result(known_results, i, j)?;
}
IotaArgument::GasCoin => (),
- // Might not be a IOTA coin
+ // Might not be an IOTA coin
IotaArgument::Input(_) => return None,
};
let amounts = amounts
diff --git a/crates/iota-rosetta/src/types.rs b/crates/iota-rosetta/src/types.rs
index eadf326efdd..0962a2fb7a0 100644
--- a/crates/iota-rosetta/src/types.rs
+++ b/crates/iota-rosetta/src/types.rs
@@ -411,7 +411,7 @@ pub enum OperationType {
PayIota,
Stake,
WithdrawStake,
- // All other Iota transaction types, readonly
+ // All other IOTA transaction types, readonly
EpochChange,
Genesis,
ConsensusCommitPrologue,
diff --git a/crates/iota-rosetta/src/unit_tests/balance_changing_tx_tests.rs b/crates/iota-rosetta/src/unit_tests/balance_changing_tx_tests.rs
index 88c4cb16308..1bfadedb519 100644
--- a/crates/iota-rosetta/src/unit_tests/balance_changing_tx_tests.rs
+++ b/crates/iota-rosetta/src/unit_tests/balance_changing_tx_tests.rs
@@ -55,7 +55,7 @@ async fn test_transfer_iota() {
let keystore = network.wallet.config().keystore();
let rgp = network.get_reference_gas_price().await;
- // Test Transfer Iota
+ // Test Transfer IOTA
let addresses = network.get_addresses();
let sender = get_random_address(&addresses, vec![]);
let recipient = get_random_address(&addresses, vec![sender]);
@@ -417,7 +417,7 @@ async fn test_pay_iota() {
let keystore = network.wallet.config().keystore();
let rgp = network.get_reference_gas_price().await;
- // Test Pay Iota
+ // Test Pay IOTA
let addresses = network.get_addresses();
let sender = get_random_address(&addresses, vec![]);
let recipient1 = get_random_address(&addresses, vec![sender]);
@@ -452,7 +452,7 @@ async fn test_failed_pay_iota() {
let keystore = network.wallet.config().keystore();
let rgp = network.get_reference_gas_price().await;
- // Test failed Pay Iota
+ // Test failed Pay IOTA
let addresses = network.get_addresses();
let sender = get_random_address(&addresses, vec![]);
let recipient1 = get_random_address(&addresses, vec![sender]);
@@ -487,7 +487,7 @@ async fn test_stake_iota() {
let keystore = network.wallet.config().keystore();
let rgp = network.get_reference_gas_price().await;
- // Test Delegate Iota
+ // Test Delegate IOTA
let sender = get_random_address(&network.get_addresses(), vec![]);
let coin1 = get_random_iota(&client, sender, vec![]).await;
let coin2 = get_random_iota(&client, sender, vec![coin1.0]).await;
@@ -535,7 +535,7 @@ async fn test_stake_iota_with_none_amount() {
let keystore = network.wallet.config().keystore();
let rgp = network.get_reference_gas_price().await;
- // Test Staking Iota
+ // Test Staking IOTA
let sender = get_random_address(&network.get_addresses(), vec![]);
let coin1 = get_random_iota(&client, sender, vec![]).await;
let coin2 = get_random_iota(&client, sender, vec![coin1.0]).await;
@@ -583,7 +583,7 @@ async fn test_pay_all_iota() {
let keystore = network.wallet.config().keystore();
let rgp = network.get_reference_gas_price().await;
- // Test Pay All Iota
+ // Test Pay All IOTA
let addresses = network.get_addresses();
let sender = get_random_address(&addresses, vec![]);
let recipient = get_random_address(&addresses, vec![sender]);
@@ -682,7 +682,7 @@ fn find_module_object(
results.pop().unwrap()
}
-// Record current Iota balance of an address then execute the transaction,
+// Record current IOTA balance of an address then execute the transaction,
// and compare the balance change reported by the event against the actual
// balance change.
async fn test_transaction(
diff --git a/crates/iota-rosetta/tests/end_to_end_tests.rs b/crates/iota-rosetta/tests/end_to_end_tests.rs
index 4a933bf29b8..542d3f5f9ef 100644
--- a/crates/iota-rosetta/tests/end_to_end_tests.rs
+++ b/crates/iota-rosetta/tests/end_to_end_tests.rs
@@ -170,7 +170,7 @@ async fn test_stake() {
.await
.unwrap();
- println!("Iota TX: {tx:?}");
+ println!("IOTA TX: {tx:?}");
assert_eq!(
&IotaExecutionStatus::Success,
@@ -230,7 +230,7 @@ async fn test_stake_all() {
.await
.unwrap();
- println!("Iota TX: {tx:?}");
+ println!("IOTA TX: {tx:?}");
assert_eq!(
&IotaExecutionStatus::Success,
@@ -297,7 +297,7 @@ async fn test_withdraw_stake() {
.await
.unwrap();
- println!("Iota TX: {tx:?}");
+ println!("IOTA TX: {tx:?}");
assert_eq!(
&IotaExecutionStatus::Success,
@@ -351,7 +351,7 @@ async fn test_withdraw_stake() {
&IotaExecutionStatus::Success,
tx.effects.as_ref().unwrap().status()
);
- println!("Iota TX: {tx:?}");
+ println!("IOTA TX: {tx:?}");
let ops2 = Operations::try_from(tx).unwrap();
assert!(
@@ -420,7 +420,7 @@ async fn test_pay_iota() {
&IotaExecutionStatus::Success,
tx.effects.as_ref().unwrap().status()
);
- println!("Iota TX: {tx:?}");
+ println!("IOTA TX: {tx:?}");
let ops2 = Operations::try_from(tx).unwrap();
assert!(
@@ -475,7 +475,7 @@ async fn test_pay_iota_multiple_times() {
)
.await
.unwrap();
- println!("Iota TX: {tx:?}");
+ println!("IOTA TX: {tx:?}");
assert_eq!(
&IotaExecutionStatus::Success,
tx.effects.as_ref().unwrap().status()
diff --git a/crates/iota-rpc-loadgen/README.md b/crates/iota-rpc-loadgen/README.md
index 3ed2fa0740c..10214de6fe4 100644
--- a/crates/iota-rpc-loadgen/README.md
+++ b/crates/iota-rpc-loadgen/README.md
@@ -1,6 +1,6 @@
# iota-rpc-loadgen: Load Generator for IOTA RPC Servers
-`iota-rpc-loadgen` is a utility that facilitates the generation of read and write loads on single or multiple Iota RPC servers. Its primary functions include performance testing and data correctness verification.
+`iota-rpc-loadgen` is a utility that facilitates the generation of read and write loads on single or multiple IOTA RPC servers. Its primary functions include performance testing and data correctness verification.
## Features
diff --git a/crates/iota-rpc-loadgen/src/main.rs b/crates/iota-rpc-loadgen/src/main.rs
index 757e2492c4e..a35042865c1 100644
--- a/crates/iota-rpc-loadgen/src/main.rs
+++ b/crates/iota-rpc-loadgen/src/main.rs
@@ -28,9 +28,9 @@ use crate::{
#[derive(Parser)]
#[clap(
- name = "Iota RPC Load Generator",
+ name = "IOTA RPC Load Generator",
version = "0.1",
- about = "A load test application for Iota RPC"
+ about = "A load test application for IOTA RPC"
)]
struct Opts {
// TODO(chris): support running multiple commands at once
diff --git a/crates/iota-rpc-loadgen/src/payload/pay_iota.rs b/crates/iota-rpc-loadgen/src/payload/pay_iota.rs
index 486c5c01e95..d3ab83a3123 100644
--- a/crates/iota-rpc-loadgen/src/payload/pay_iota.rs
+++ b/crates/iota-rpc-loadgen/src/payload/pay_iota.rs
@@ -39,7 +39,7 @@ impl<'a> ProcessPayload<'a, &'a PayIota> for RpcCommandProcessor {
IotaKeyPair::decode_base64(&encoded_keypair).expect("Decoding keypair should not fail");
debug!(
- "Transfer Iota {} time to {recipient} with {amount} NANOS with {gas_payments:?}",
+ "Transfer IOTA {} time to {recipient} with {amount} NANOS with {gas_payments:?}",
gas_payments.len()
);
diff --git a/crates/iota-sdk/Cargo.toml b/crates/iota-sdk/Cargo.toml
index f65de0938da..35fe2bf9232 100644
--- a/crates/iota-sdk/Cargo.toml
+++ b/crates/iota-sdk/Cargo.toml
@@ -39,7 +39,7 @@ iota-types.workspace = true
move-core-types.workspace = true
shared-crypto.workspace = true
# NOTE: It's important to keep the above dependency list short.
-# This and the iota-json-rpc-api crate are widely used to develop on Iota and it's valuable
+# This and the iota-json-rpc-api crate are widely used to develop on IOTA and it's valuable
# to not have to pull in the entire iota repo for it.
[dev-dependencies]
diff --git a/crates/iota-sdk/README.md b/crates/iota-sdk/README.md
index abe850783e3..0cddd1793e8 100644
--- a/crates/iota-sdk/README.md
+++ b/crates/iota-sdk/README.md
@@ -10,7 +10,7 @@ tokio = { version = "1.2", features = ["full"] }
anyhow = "1.0"
```
-The main building block for the IOTA Rust SDK is the `IotaClientBuilder`, which provides a simple and straightforward way of connecting to a IOTA network and having access to the different available APIs.
+The main building block for the IOTA Rust SDK is the `IotaClientBuilder`, which provides a simple and straightforward way of connecting to an IOTA network and having access to the different available APIs.
In the following example, the application connects to the IOTA `testnet` and `devnet` networks and prints out their respective RPC API versions.
@@ -63,7 +63,7 @@ Unless otherwise specified, most of these examples assume `Rust` and `cargo` are
In the root folder of the `iota` repository (or in the `iota-sdk` crate folder), you can individually run examples using the command `cargo run --example filename` (without `.rs` extension). For example:
-- `cargo run --example iota_client` -- this one requires a local Iota network running (see [#Connecting to Iota Network](https://docs.iota.org/developer/getting-started/local-network#start-the-local-network). If you do not have a local Iota network running, please skip this example.
+- `cargo run --example iota_client` -- this one requires a local IOTA network running (see [#Connecting to IOTA Network](https://docs.iota.org/developer/getting-started/local-network#start-the-local-network). If you do not have a local IOTA network running, please skip this example.
- `cargo run --example coin_read_api`
- `cargo run --example event_api` -- note that this will subscribe to a stream and thus the program will not terminate unless forced (Ctrl+C)
- `cargo run --example governance_api`
diff --git a/crates/iota-sdk/examples/coin_read_api.rs b/crates/iota-sdk/examples/coin_read_api.rs
index f82c975af69..2546899c14b 100644
--- a/crates/iota-sdk/examples/coin_read_api.rs
+++ b/crates/iota-sdk/examples/coin_read_api.rs
@@ -62,7 +62,7 @@ async fn main() -> Result<(), anyhow::Error> {
println!(" *** Coins Stream ***\n");
// Select coins based on the provided coin type (IOTA in this example). Use
- // `None` for the default Iota coin
+ // `None` for the default IOTA coin
let select_coins = client
.coin_read_api()
.select_coins(active_address, coin_type.clone(), 1, vec![])
diff --git a/crates/iota-sdk/examples/event_api.rs b/crates/iota-sdk/examples/event_api.rs
index b843ec0b101..19876789cbf 100644
--- a/crates/iota-sdk/examples/event_api.rs
+++ b/crates/iota-sdk/examples/event_api.rs
@@ -3,7 +3,7 @@
// SPDX-License-Identifier: Apache-2.0
//! This example showcases how to use the Event API.
-//! At the end of the program it subscribes to the events on the Iota testnet
+//! At the end of the program it subscribes to the events on the IOTA testnet
//! and prints every incoming event to the console. The program will loop until
//! it is force stopped.
//!
diff --git a/crates/iota-sdk/examples/governance_api.rs b/crates/iota-sdk/examples/governance_api.rs
index 82b41ddb1a2..98a1e1221dc 100644
--- a/crates/iota-sdk/examples/governance_api.rs
+++ b/crates/iota-sdk/examples/governance_api.rs
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-//! This example connects to the Iota testnet and collects information about the
+//! This example connects to the IOTA testnet and collects information about the
//! stakes in the network, the committee information, lists all the validators'
//! name, description, and iota address, and prints the reference gas price.
//!
@@ -30,15 +30,15 @@ async fn main() -> Result<(), anyhow::Error> {
println!("{:?}", committee);
println!(" *** Committee Info ***\n");
- // Latest Iota System State
+ // Latest IOTA System State
let iota_system_state = client
.governance_api()
.get_latest_iota_system_state()
.await?;
- println!(" *** Iota System State ***");
+ println!(" *** IOTA System State ***");
println!("{:?}", iota_system_state);
- println!(" *** Iota System State ***\n");
+ println!(" *** IOTA System State ***\n");
// List all active validators
diff --git a/crates/iota-sdk/examples/read_api/transaction_subscription.rs b/crates/iota-sdk/examples/read_api/transaction_subscription.rs
index 44bdadcfe2b..ee9763c9854 100644
--- a/crates/iota-sdk/examples/read_api/transaction_subscription.rs
+++ b/crates/iota-sdk/examples/read_api/transaction_subscription.rs
@@ -3,7 +3,7 @@
// SPDX-License-Identifier: Apache-2.0
//! This example showcases how to use the Read API to listen for transactions.
-//! It subscribes to the transactions that transfer IOTA on the Iota testnet and
+//! It subscribes to the transactions that transfer IOTA on the IOTA testnet and
//! prints every incoming transaction to the console. The program will loop
//! until it is force stopped.
//!
diff --git a/crates/iota-sdk/examples/transaction_builder/function_move_call.rs b/crates/iota-sdk/examples/transaction_builder/function_move_call.rs
index f26d326828e..becb4ad9490 100644
--- a/crates/iota-sdk/examples/transaction_builder/function_move_call.rs
+++ b/crates/iota-sdk/examples/transaction_builder/function_move_call.rs
@@ -24,20 +24,20 @@ use utils::setup_for_write;
// This example shows how to use programmable transactions to chain multiple
// commands into one transaction, and specifically how to call a function from a
// move package These are the following steps:
-// 1) finds a coin from the active address that has Iota,
+// 1) finds a coin from the active address that has IOTA,
// 2) creates a PTB and adds an input to it,
// 3) adds a move call to the PTB,
// 4) signs the transaction,
// 5) executes it.
// For some of these actions it prints some output.
// Finally, at the end of the program it prints the number of coins for the
-// Iota address that received the coin.
+// IOTA address that received the coin.
// If you run this program several times, you should see the number of coins
// for the recipient address increases.
#[tokio::main]
async fn main() -> Result<(), anyhow::Error> {
- // 1) get the Iota client, the sender and recipient that we will use
+ // 1) get the IOTA client, the sender and recipient that we will use
// for the transaction, and find the coin we use as gas
let (iota, sender, _recipient) = setup_for_write().await?;
diff --git a/crates/iota-sdk/examples/transaction_builder/pay_iota.rs b/crates/iota-sdk/examples/transaction_builder/pay_iota.rs
index 551c8feddfc..78cad34df74 100644
--- a/crates/iota-sdk/examples/transaction_builder/pay_iota.rs
+++ b/crates/iota-sdk/examples/transaction_builder/pay_iota.rs
@@ -19,7 +19,7 @@ use utils::setup_for_write;
#[tokio::main]
async fn main() -> Result<(), anyhow::Error> {
- // 1) Get the Iota client, the sender and recipient that we will use
+ // 1) Get the IOTA client, the sender and recipient that we will use
// for the transaction
let (client, sender, recipient) = setup_for_write().await?;
diff --git a/crates/iota-sdk/examples/transaction_builder/programmable_transactions_api.rs b/crates/iota-sdk/examples/transaction_builder/programmable_transactions_api.rs
index 6b487128323..9b65aa6c2c3 100644
--- a/crates/iota-sdk/examples/transaction_builder/programmable_transactions_api.rs
+++ b/crates/iota-sdk/examples/transaction_builder/programmable_transactions_api.rs
@@ -5,14 +5,14 @@
//! This example shows how to use programmable transactions to chain multiple
//! actions into one transaction. Specifically, the example retrieves two
//! addresses from the local wallet, and then
-//! 1) finds a coin from the active address that has Iota,
+//! 1) finds a coin from the active address that has IOTA,
//! 2) splits the coin into one coin of 1000 NANOS and the rest,
-//! 3) transfers the split coin to second Iota address,
+//! 3) transfers the split coin to second IOTA address,
//! 4) signs and executes the transaction.
//!
//! For some of these actions it prints some output.
//! Finally, at the end of the program it prints the number of coins for the
-//! Iota address that received the coin. If you run this program several times,
+//! IOTA address that received the coin. If you run this program several times,
//! you should see the number of coins for the recipient address increases.
//!
//! cargo run --example programmable_transactions_api
@@ -28,7 +28,7 @@ use utils::{setup_for_write, sign_and_execute_transaction};
#[tokio::main]
async fn main() -> Result<(), anyhow::Error> {
- // 1) Get the Iota client, the sender and recipient that we will use
+ // 1) Get the IOTA client, the sender and recipient that we will use
// for the transaction
let (client, sender, recipient) = setup_for_write().await?;
diff --git a/crates/iota-sdk/examples/transaction_builder/sign_tx_guide.rs b/crates/iota-sdk/examples/transaction_builder/sign_tx_guide.rs
index 75a423f9509..3eeb5cd5329 100644
--- a/crates/iota-sdk/examples/transaction_builder/sign_tx_guide.rs
+++ b/crates/iota-sdk/examples/transaction_builder/sign_tx_guide.rs
@@ -83,7 +83,7 @@ async fn main() -> Result<(), anyhow::Error> {
.map_err(|_| anyhow!("Invalid base64"))?;
// import a keypair from a Bech32 encoded 33-byte `flag || private key`.
- // this is the format of a private key exported from Iota Wallet or
+ // this is the format of a private key exported from IOTA Wallet or
// iota.keystore.
let _ikp_import_with_flag_0 = IotaKeyPair::decode(
"iotaprivkey1qzdlfxn2qa2lj5uprl8pyhexs02sg2wrhdy7qaq50cqgnffw4c247zslwv6",
@@ -146,7 +146,7 @@ async fn main() -> Result<(), anyhow::Error> {
// if you would like to verify the signature locally before submission, use this
// function. if it fails to verify locally, the transaction will fail to
- // execute in Iota.
+ // execute in IOTA.
let res = iota_sig.verify_secure(
&intent_msg,
sender,
diff --git a/crates/iota-sdk/examples/transaction_builder/stake.rs b/crates/iota-sdk/examples/transaction_builder/stake.rs
index 98df0109bff..ddf939cffe1 100644
--- a/crates/iota-sdk/examples/transaction_builder/stake.rs
+++ b/crates/iota-sdk/examples/transaction_builder/stake.rs
@@ -15,7 +15,7 @@ use utils::{setup_for_write, sign_and_execute_transaction};
#[tokio::main]
async fn main() -> Result<(), anyhow::Error> {
- // Get the Iota client, the sender and recipient that we will use
+ // Get the IOTA client, the sender and recipient that we will use
// for the transaction
let (client, sender, _) = setup_for_write().await?;
diff --git a/crates/iota-sdk/examples/utils.rs b/crates/iota-sdk/examples/utils.rs
index d9de6f91187..103715fddc1 100644
--- a/crates/iota-sdk/examples/utils.rs
+++ b/crates/iota-sdk/examples/utils.rs
@@ -82,7 +82,7 @@ pub async fn setup_for_write() -> Result<(IotaClient, IotaAddress, IotaAddress),
/// IOTA from the faucet.
pub async fn setup_for_read() -> Result<(IotaClient, IotaAddress), anyhow::Error> {
let client = IotaClientBuilder::default().build_testnet().await?;
- println!("Iota testnet version is: {}", client.api_version());
+ println!("IOTA testnet version is: {}", client.api_version());
let mut wallet = retrieve_wallet()?;
assert!(wallet.get_addresses().len() >= 2);
let active_address = wallet.active_address()?;
diff --git a/crates/iota-sdk/src/apis/event.rs b/crates/iota-sdk/src/apis/event.rs
index 97ba5e01294..a92612aab90 100644
--- a/crates/iota-sdk/src/apis/event.rs
+++ b/crates/iota-sdk/src/apis/event.rs
@@ -16,7 +16,7 @@ use crate::{
error::{Error, IotaRpcResult},
};
-/// Defines methods to fetch, query, or subscribe to events on the Iota network.
+/// Defines methods to fetch, query, or subscribe to events on the IOTA network.
#[derive(Clone)]
pub struct EventApi {
api: Arc,
diff --git a/crates/iota-sdk/src/json_rpc_error.rs b/crates/iota-sdk/src/json_rpc_error.rs
index 4fb8aa49a37..c7aad677544 100644
--- a/crates/iota-sdk/src/json_rpc_error.rs
+++ b/crates/iota-sdk/src/json_rpc_error.rs
@@ -11,7 +11,7 @@ use thiserror::Error;
pub struct Error {
pub code: i32,
pub message: String,
- // TODO: as this SDK is specialized for the Iota JSON RPC implementation, we should define
+ // TODO: as this SDK is specialized for the IOTA JSON RPC implementation, we should define
// structured representation for the data field if applicable
pub data: Option,
}
diff --git a/crates/iota-sdk/src/lib.rs b/crates/iota-sdk/src/lib.rs
index d872a02aac8..228c216c133 100644
--- a/crates/iota-sdk/src/lib.rs
+++ b/crates/iota-sdk/src/lib.rs
@@ -33,11 +33,11 @@
//! Add the Rust SDK to the project by running `cargo add iota-sdk` in the root
//! folder of your Rust project.
//!
-//! The main building block for the Iota Rust SDK is the [IotaClientBuilder],
-//! which provides a simple and straightforward way of connecting to an Iota
+//! The main building block for the IOTA Rust SDK is the [IotaClientBuilder],
+//! which provides a simple and straightforward way of connecting to an IOTA
//! network and having access to the different available APIs.
//!
-//! Below is a simple example which connects to a running Iota local network,
+//! Below is a simple example which connects to a running IOTA local network,
//! devnet, and testnet.
//! To successfully run this program, make sure to spin up a local
//! network with a local validator, a fullnode, and a faucet server
@@ -49,21 +49,21 @@
//! #[tokio::main]
//! async fn main() -> Result<(), anyhow::Error> {
//! let iota = IotaClientBuilder::default()
-//! .build("http://127.0.0.1:9000") // provide the Iota network URL
+//! .build("http://127.0.0.1:9000") // provide the IOTA network URL
//! .await?;
-//! println!("Iota local network version: {:?}", iota.api_version());
+//! println!("IOTA local network version: {:?}", iota.api_version());
//!
-//! // local Iota network, same result as above except using the dedicated function
+//! // local IOTA network, same result as above except using the dedicated function
//! let iota_local = IotaClientBuilder::default().build_localnet().await?;
-//! println!("Iota local network version: {:?}", iota_local.api_version());
+//! println!("IOTA local network version: {:?}", iota_local.api_version());
//!
-//! // Iota devnet running at `https://fullnode.devnet.io:443`
+//! // IOTA devnet running at `https://fullnode.devnet.io:443`
//! let iota_devnet = IotaClientBuilder::default().build_devnet().await?;
-//! println!("Iota devnet version: {:?}", iota_devnet.api_version());
+//! println!("IOTA devnet version: {:?}", iota_devnet.api_version());
//!
-//! // Iota testnet running at `https://testnet.devnet.io:443`
+//! // IOTA testnet running at `https://testnet.devnet.io:443`
//! let iota_testnet = IotaClientBuilder::default().build_testnet().await?;
-//! println!("Iota testnet version: {:?}", iota_testnet.api_version());
+//! println!("IOTA testnet version: {:?}", iota_testnet.api_version());
//! Ok(())
//! }
//! ```
@@ -124,7 +124,7 @@ pub const IOTA_TESTNET_URL: &str = "https://api.testnet.iota.cafe";
pub const IOTA_TESTNET_GAS_URL: &str = "https://faucet.testnet.iota.cafe/v1/gas";
pub const IOTA_MAINNET_URL: &str = "https://api.mainnet.iota.cafe";
-/// Builder for creating an [IotaClient] for connecting to the Iota network.
+/// Builder for creating an [IotaClient] for connecting to the IOTA network.
///
/// By default `maximum concurrent requests` is set to 256 and `request timeout`
/// is set to 60 seconds. These can be adjusted using
@@ -143,7 +143,7 @@ pub const IOTA_MAINNET_URL: &str = "https://api.mainnet.iota.cafe";
/// .build("http://127.0.0.1:9000")
/// .await?;
///
-/// println!("Iota local network version: {:?}", iota.api_version());
+/// println!("IOTA local network version: {:?}", iota.api_version());
/// Ok(())
/// }
/// ```
@@ -180,7 +180,7 @@ impl IotaClientBuilder {
self
}
- /// Set the WebSocket URL for the Iota network.
+ /// Set the WebSocket URL for the IOTA network.
pub fn ws_url(mut self, url: impl AsRef) -> Self {
self.ws_url = Some(url.as_ref().to_string());
self
@@ -198,7 +198,7 @@ impl IotaClientBuilder {
self
}
- /// Return an [IotaClient] object connected to the Iota network accessible
+ /// Return an [IotaClient] object connected to the IOTA network accessible
/// via the provided URI.
///
/// # Examples
@@ -212,7 +212,7 @@ impl IotaClientBuilder {
/// .build("http://127.0.0.1:9000")
/// .await?;
///
- /// println!("Iota local version: {:?}", iota.api_version());
+ /// println!("IOTA local version: {:?}", iota.api_version());
/// Ok(())
/// }
/// ```
@@ -289,7 +289,7 @@ impl IotaClientBuilder {
}
/// Return an [IotaClient] object that is ready to interact with the local
- /// development network (by default it expects the Iota network to be up
+ /// development network (by default it expects the IOTA network to be up
/// and running at `127.0.0.1:9000`).
///
/// For connecting to a custom URI, use the `build` function instead.
@@ -303,7 +303,7 @@ impl IotaClientBuilder {
/// async fn main() -> Result<(), anyhow::Error> {
/// let iota = IotaClientBuilder::default().build_localnet().await?;
///
- /// println!("Iota local version: {:?}", iota.api_version());
+ /// println!("IOTA local version: {:?}", iota.api_version());
/// Ok(())
/// }
/// ```
@@ -311,7 +311,7 @@ impl IotaClientBuilder {
self.build(IOTA_LOCAL_NETWORK_URL).await
}
- /// Return an [IotaClient] object that is ready to interact with the Iota
+ /// Return an [IotaClient] object that is ready to interact with the IOTA
/// devnet.
///
/// For connecting to a custom URI, use the `build` function instead.
@@ -333,7 +333,7 @@ impl IotaClientBuilder {
self.build(IOTA_DEVNET_URL).await
}
- /// Return an [IotaClient] object that is ready to interact with the Iota
+ /// Return an [IotaClient] object that is ready to interact with the IOTA
/// testnet.
///
/// For connecting to a custom URI, use the `build` function instead.
@@ -424,7 +424,7 @@ impl IotaClientBuilder {
}
}
-/// Provides all the necessary abstractions for interacting with the Iota
+/// Provides all the necessary abstractions for interacting with the IOTA
/// network.
///
/// # Usage
diff --git a/crates/iota-simulator/README.md b/crates/iota-simulator/README.md
index 613ebca9769..6b10a1994d7 100644
--- a/crates/iota-simulator/README.md
+++ b/crates/iota-simulator/README.md
@@ -1,4 +1,4 @@
-# Iota Simulation Testing
+# IOTA Simulation Testing
This document outlines what the simulator used by `cargo simtest` enables, how it works, how to write sim tests,
and outlines some future work.
@@ -7,7 +7,7 @@ and outlines some future work.
Currently, the simulator:
-- Provides deterministic, randomized execution of an entire Iota network in a single process.
+- Provides deterministic, randomized execution of an entire IOTA network in a single process.
- Simulates network latency and packet loss as desired.
This allows us to:
diff --git a/crates/iota-single-node-benchmark/README.md b/crates/iota-single-node-benchmark/README.md
index 94500b283a2..da4976d00cd 100644
--- a/crates/iota-single-node-benchmark/README.md
+++ b/crates/iota-single-node-benchmark/README.md
@@ -1,4 +1,4 @@
-# Iota Single Node Benchmark
+# IOTA Single Node Benchmark
This crate contains a binary for performance benchmarking a single IOTA node.
Upon running the binary, the node will instantiate a standalone `AuthorityState`, and submit
@@ -50,4 +50,4 @@ The benchmark supports various component:
### Profiling
-If you are interested in profiling Iota, you can start the benchmark, wait for it to print out "Started execution...", and then attach a profiler to the process.
+If you are interested in profiling IOTA, you can start the benchmark, wait for it to print out "Started execution...", and then attach a profiler to the process.
diff --git a/crates/iota-source-validation-service/README.md b/crates/iota-source-validation-service/README.md
index b316bb2ad91..12be09e03ad 100644
--- a/crates/iota-source-validation-service/README.md
+++ b/crates/iota-source-validation-service/README.md
@@ -1,10 +1,10 @@
-# Iota Source Validation Service
+# IOTA Source Validation Service
-This document describes the Iota Source Validation Service. It is engineering documentation primarily for engineers who may want to build, extend, configure, or understand the service.
+This document describes the IOTA Source Validation Service. It is engineering documentation primarily for engineers who may want to build, extend, configure, or understand the service.
The Source Validation Service is a server that returns Move source code associated with on-chain Move bytecode. It fetches and builds Move source code for a repository, and then verifies that the built artifact matches the on-chain bytecode.
-The default configuration limits scope to Iota framework packages in `crates/iota-framework/packages`:
+The default configuration limits scope to IOTA framework packages in `crates/iota-framework/packages`:
- `move-stdlib` — [address `0x1`](https://explorer.iota.org/object/0x1)
- `iota-framework` — [address `0x2`](https://explorer.iota.org/object/0x2)
@@ -41,7 +41,7 @@ packages = [
It specifies the `repository` and `branch` for one or more move `packages`. `network` specifies the on-chain network to verify the source against. It can be one of `mainnet`, `testnet`, `devnet`, or `localnet`.
A package `path` specifies the path of the package in the repository (where the `Move.toml` is).
-The `watch` field is optional, and specifies the address of an object that the server should monitor for on-chain changes if a package is upgraded. For example, Iota framework packages mutate their on-chain address when upgraded.
+The `watch` field is optional, and specifies the address of an object that the server should monitor for on-chain changes if a package is upgraded. For example, IOTA framework packages mutate their on-chain address when upgraded.
Non-framework packages may mutate an `UpgradeCap` or an object wrapping the `UpgradeCap` (in which case, `watch` should be set to the `UpgradeCap` object ID or wrapped object ID respectively).
Currently the `watch` field intends only to invalidate and evict the source code if on-chain code changes via upgrades. Due to current limitations, it does not automatically attempt to find and reprocess the latest source code. To reprocess the latest source code, restart the server, which will download and verify the source code afresh.
@@ -79,11 +79,11 @@ On occasion `https://source.iota.org` may return a `502` response or experience
The source service may experience transient downtime for at least the following reasons:
-- RPC event subscription disconnection or instability. The IOTA source service actively monitors on-chain upgrade events to ensure it always reports accurate verified source. If RPC subscription is lost, the service will attempt to regain the connection. During the time of disconnection the service will not respond with verified source in order to preserve integrity. This behavior is especially important for Iota framework packages that are upgraded _in-place_ (e.g., `0x1`, `0x2`, and `0x3`) to ensure integrity. This is usually a transient issue.
+- RPC event subscription disconnection or instability. The IOTA source service actively monitors on-chain upgrade events to ensure it always reports accurate verified source. If RPC subscription is lost, the service will attempt to regain the connection. During the time of disconnection the service will not respond with verified source in order to preserve integrity. This behavior is especially important for IOTA framework packages that are upgraded _in-place_ (e.g., `0x1`, `0x2`, and `0x3`) to ensure integrity. This is usually a transient issue.
- The on-chain package content has changed (e.g., due to a protocol upgrade) and the source repository does not yet reflect the new on-chain bytecode.
- - This can happen when the branch containing we track for the source-to-be-verified as diverged from on-chain bytecode, or does not yet correspond to the new on-chain bytecode. This is especially the case for Iota framework packages that are upgraded _in-place_ at protocol upgrades (e.g., `0x1`, `0x2`, and `0x3`).
- - While usually transient, there may be extended periods of mismatched source and bytecode due to Iota's release process.
+ - This can happen when the branch containing we track for the source-to-be-verified as diverged from on-chain bytecode, or does not yet correspond to the new on-chain bytecode. This is especially the case for IOTA framework packages that are upgraded _in-place_ at protocol upgrades (e.g., `0x1`, `0x2`, and `0x3`).
+ - While usually transient, there may be extended periods of mismatched source and bytecode due to IOTA's release process.
- A new version of Move compiler is released, requiring service redeployment.
- For example, when framework packages are upgraded and require a more recent compiler version, the IOTA source service will need to be redeployed and will experience transient downtime.
diff --git a/crates/iota-source-validation/src/error.rs b/crates/iota-source-validation/src/error.rs
index c9060245b5e..f418c1d9685 100644
--- a/crates/iota-source-validation/src/error.rs
+++ b/crates/iota-source-validation/src/error.rs
@@ -49,7 +49,7 @@ pub enum Error {
module: Symbol,
},
- #[error("Dependency ID contains a Iota object, not a Move package: {}", .0.0)]
+ #[error("Dependency ID contains an IOTA object, not a Move package: {}", .0.0)]
ObjectFoundWhenPackageExpected(Box<(ObjectID, IotaRawMoveObject)>),
#[error("Could not deserialize on-chain dependency {address}::{module}.")]
diff --git a/crates/iota-source-validation/src/lib.rs b/crates/iota-source-validation/src/lib.rs
index 18a3942c7cc..80bcf7d52d6 100644
--- a/crates/iota-source-validation/src/lib.rs
+++ b/crates/iota-source-validation/src/lib.rs
@@ -392,7 +392,7 @@ impl<'a> BytecodeSourceVerifier<'a> {
// fetched from a iota network via iota_getObject, which takes an object ID
let obj_id = ObjectID::from(addr);
- // fetch the Iota object at the address specified for the package in the local
+ // fetch the IOTA object at the address specified for the package in the local
// resolution table if future packages with a large set of dependency
// packages prove too slow to verify, batched object fetching should be
// added to the ReadApi & used here
diff --git a/crates/iota-source-validation/src/tests.rs b/crates/iota-source-validation/src/tests.rs
index 3fb2169b47f..c8b4d4677ca 100644
--- a/crates/iota-source-validation/src/tests.rs
+++ b/crates/iota-source-validation/src/tests.rs
@@ -373,7 +373,7 @@ async fn dependency_is_an_object() -> anyhow::Result<()> {
let client = context.get_client().await?;
let expected = expect![
- "Dependency ID contains a Iota object, not a Move package: 0x0000000000000000000000000000000000000000000000000000000000000005"
+ "Dependency ID contains an IOTA object, not a Move package: 0x0000000000000000000000000000000000000000000000000000000000000005"
];
expected.assert_eq(
&BytecodeSourceVerifier::new(client.read_api())
diff --git a/crates/iota-swarm-config/tests/snapshot_tests.rs b/crates/iota-swarm-config/tests/snapshot_tests.rs
index 2994f8d0ad1..c0611145a18 100644
--- a/crates/iota-swarm-config/tests/snapshot_tests.rs
+++ b/crates/iota-swarm-config/tests/snapshot_tests.rs
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-// This file contains tests that detect changes in Iota configs.
+// This file contains tests that detect changes in IOTA configs.
// If a PR breaks one or more tests here, the PR probably has a real impact
// on a production configuration file. When test failure happens, the PR should
// be marked as a breaking change and reviewers should be aware of this.
diff --git a/crates/iota-swarm/README.md b/crates/iota-swarm/README.md
index 7e3464b1d5d..2363a54a927 100644
--- a/crates/iota-swarm/README.md
+++ b/crates/iota-swarm/README.md
@@ -1,6 +1,6 @@
# iota-swarm
-This crate contains a collection of utilities for managing complete Iota
+This crate contains a collection of utilities for managing complete IOTA
networks. The intended use for these utilities is for performing end-to-end
testing and benchmarking. In the future, the expectation is that we'll have
support for a number of different "backends" for how the network is operated.
@@ -11,7 +11,7 @@ we should be able to support a multi-process and even a Kubernetes (k8s) backend
### memory
-An `in-memory`, or rather `in-process`, backend for building and managing Iota
+An `in-memory`, or rather `in-process`, backend for building and managing IOTA
networks that all run inside the same process. Nodes are isolated from one
another by each being run on their own separate thread within their own `tokio`
runtime. This enables the ability to properly shut down a single node and
diff --git a/crates/iota-swarm/src/memory/mod.rs b/crates/iota-swarm/src/memory/mod.rs
index 9ae6f422811..fdb52e003aa 100644
--- a/crates/iota-swarm/src/memory/mod.rs
+++ b/crates/iota-swarm/src/memory/mod.rs
@@ -3,7 +3,7 @@
// SPDX-License-Identifier: Apache-2.0
//! An `in-memory`, or rather `in-process`, backend for building and managing
-//! Iota Networks that all run inside the same process. Nodes are isolated from
+//! IOTA Networks that all run inside the same process. Nodes are isolated from
//! one another by each being run on their own separate thread within their own
//! `tokio` runtime. This enables the ability to properly shut down a single
//! node and ensure that all of its running tasks are also shut down, something
diff --git a/crates/iota-swarm/src/memory/node.rs b/crates/iota-swarm/src/memory/node.rs
index fbc9b0d6912..5a0db2dab40 100644
--- a/crates/iota-swarm/src/memory/node.rs
+++ b/crates/iota-swarm/src/memory/node.rs
@@ -13,7 +13,7 @@ use tracing::{error, info};
use super::container::Container;
-/// A handle to an in-memory Iota Node.
+/// A handle to an in-memory IOTA Node.
///
/// Each Node is attempted to run in isolation from each other by running them
/// in their own tokio runtime in a separate thread. By doing this we can ensure
diff --git a/crates/iota-swarm/src/memory/swarm.rs b/crates/iota-swarm/src/memory/swarm.rs
index 11d20ab51c2..126bedc2dcc 100644
--- a/crates/iota-swarm/src/memory/swarm.rs
+++ b/crates/iota-swarm/src/memory/swarm.rs
@@ -433,7 +433,7 @@ impl SwarmBuilder {
}
}
-/// A handle to an in-memory Iota Network.
+/// A handle to an in-memory IOTA Network.
#[derive(Debug)]
pub struct Swarm {
dir: SwarmDirectory,
diff --git a/crates/iota-tool/README.md b/crates/iota-tool/README.md
index 7076016c490..ee203100bb8 100644
--- a/crates/iota-tool/README.md
+++ b/crates/iota-tool/README.md
@@ -1,6 +1,6 @@
# iota-tool
-`iota-tool` contains assorted debugging utilities for Iota.
+`iota-tool` contains assorted debugging utilities for IOTA.
You can build and run `iota-tool` from source with:
@@ -14,7 +14,7 @@ You can use the anemo CLI tools to ping or call an RPC on an Anemo server. Note
Anemo networks are identified by a "server name" that the client must match. Server names you may want to use:
-- Iota discovery and state sync: `iota`
+- IOTA discovery and state sync: `iota`
### ping
@@ -30,7 +30,7 @@ cargo run --bin iota-tool -- anemo ping --server-name "$SERVER_NAME" "$ADDRESS"
`iota-tool` has been preconfigured to support RPC calls using [RON (Rusty Object Notation)](https://crates.io/crates/ron) for the following servivces:
-- Iota: `Discovery` and `StateSync`
+- IOTA: `Discovery` and `StateSync`
Example command to send an RPC:
diff --git a/crates/iota-tool/src/lib.rs b/crates/iota-tool/src/lib.rs
index da8e0de6d03..9c5cf8c93c8 100644
--- a/crates/iota-tool/src/lib.rs
+++ b/crates/iota-tool/src/lib.rs
@@ -500,7 +500,7 @@ pub(crate) fn make_anemo_config() -> anemo_cli::Config {
// TODO: implement `ServiceInfo` generation in anemo-build and use here.
anemo_cli::Config::new()
- // Iota discovery
+ // IOTA discovery
.add_service(
"Discovery",
anemo_cli::ServiceInfo::new().add_method(
@@ -508,7 +508,7 @@ pub(crate) fn make_anemo_config() -> anemo_cli::Config {
anemo_cli::ron_method!(DiscoveryClient, get_known_peers, ()),
),
)
- // Iota state sync
+ // IOTA state sync
.add_service(
"StateSync",
anemo_cli::ServiceInfo::new()
diff --git a/crates/iota-transactional-test-runner/Cargo.toml b/crates/iota-transactional-test-runner/Cargo.toml
index a4ca6024125..df60d2db176 100644
--- a/crates/iota-transactional-test-runner/Cargo.toml
+++ b/crates/iota-transactional-test-runner/Cargo.toml
@@ -5,7 +5,7 @@ authors = ["IOTA Foundation "]
edition = "2021"
license = "Apache-2.0"
publish = false
-description = "Move framework for Iota platform"
+description = "Move framework for IOTA platform"
[lints]
workspace = true
diff --git a/crates/iota-transactional-test-runner/src/args.rs b/crates/iota-transactional-test-runner/src/args.rs
index 2379237cc51..82ff6ecc97f 100644
--- a/crates/iota-transactional-test-runner/src/args.rs
+++ b/crates/iota-transactional-test-runner/src/args.rs
@@ -413,11 +413,11 @@ impl IotaValue {
fn assert_move_value(self) -> MoveValue {
match self {
IotaValue::MoveValue(v) => v,
- IotaValue::Object(_, _) => panic!("unexpected nested Iota object in args"),
- IotaValue::ObjVec(_) => panic!("unexpected nested Iota object vector in args"),
- IotaValue::Digest(_) => panic!("unexpected nested Iota package digest in args"),
- IotaValue::Receiving(_, _) => panic!("unexpected nested Iota receiving object in args"),
- IotaValue::ImmShared(_, _) => panic!("unexpected nested Iota shared object in args"),
+ IotaValue::Object(_, _) => panic!("unexpected nested IOTA object in args"),
+ IotaValue::ObjVec(_) => panic!("unexpected nested IOTA object vector in args"),
+ IotaValue::Digest(_) => panic!("unexpected nested IOTA package digest in args"),
+ IotaValue::Receiving(_, _) => panic!("unexpected nested IOTA receiving object in args"),
+ IotaValue::ImmShared(_, _) => panic!("unexpected nested IOTA shared object in args"),
}
}
@@ -425,10 +425,10 @@ impl IotaValue {
match self {
IotaValue::MoveValue(_) => panic!("unexpected nested non-object value in args"),
IotaValue::Object(id, version) => (id, version),
- IotaValue::ObjVec(_) => panic!("unexpected nested Iota object vector in args"),
- IotaValue::Digest(_) => panic!("unexpected nested Iota package digest in args"),
- IotaValue::Receiving(_, _) => panic!("unexpected nested Iota receiving object in args"),
- IotaValue::ImmShared(_, _) => panic!("unexpected nested Iota shared object in args"),
+ IotaValue::ObjVec(_) => panic!("unexpected nested IOTA object vector in args"),
+ IotaValue::Digest(_) => panic!("unexpected nested IOTA package digest in args"),
+ IotaValue::Receiving(_, _) => panic!("unexpected nested IOTA receiving object in args"),
+ IotaValue::ImmShared(_, _) => panic!("unexpected nested IOTA shared object in args"),
}
}
diff --git a/crates/iota-transactional-test-runner/src/lib.rs b/crates/iota-transactional-test-runner/src/lib.rs
index b0527d3b9bf..91ef468647f 100644
--- a/crates/iota-transactional-test-runner/src/lib.rs
+++ b/crates/iota-transactional-test-runner/src/lib.rs
@@ -3,7 +3,7 @@
// SPDX-License-Identifier: Apache-2.0
//! This module contains the transactional test runner instantiation for the
-//! Iota adapter
+//! IOTA adapter
pub mod args;
pub mod programmable_transaction_test_parser;
diff --git a/crates/iota-transactional-test-runner/src/test_adapter.rs b/crates/iota-transactional-test-runner/src/test_adapter.rs
index 268fe616239..bc36c5b0ff1 100644
--- a/crates/iota-transactional-test-runner/src/test_adapter.rs
+++ b/crates/iota-transactional-test-runner/src/test_adapter.rs
@@ -3,7 +3,7 @@
// SPDX-License-Identifier: Apache-2.0
//! This module contains the transactional test runner instantiation for the
-//! Iota adapter
+//! IOTA adapter
use std::{
collections::{BTreeMap, BTreeSet},
@@ -234,7 +234,7 @@ impl MoveTestAdapter<'_> for IotaTestAdapter {
let rng = StdRng::from_seed(RNG_SEED);
assert!(
pre_compiled_deps.is_some(),
- "Must populate 'pre_compiled_deps' with Iota framework"
+ "Must populate 'pre_compiled_deps' with IOTA framework"
);
// Unpack the init arguments
@@ -439,7 +439,7 @@ impl MoveTestAdapter<'_> for IotaTestAdapter {
})
.collect::>()?;
let gas_price = gas_price.unwrap_or(self.gas_price);
- // we are assuming that all packages depend on Move Stdlib and Iota Framework,
+ // we are assuming that all packages depend on Move Stdlib and IOTA Framework,
// so these don't have to be provided explicitly as parameters
dependencies.extend([MOVE_STDLIB_PACKAGE_ID, IOTA_FRAMEWORK_PACKAGE_ID]);
let data = |sender, gas| {
@@ -1842,7 +1842,7 @@ impl<'a> IotaTestAdapter {
Ok(id)
})
.collect::>()?;
- // we are assuming that all packages depend on Move Stdlib and Iota Framework,
+ // we are assuming that all packages depend on Move Stdlib and IOTA Framework,
// so these don't have to be provided explicitly as parameters
if include_std {
dependencies.extend([MOVE_STDLIB_PACKAGE_ID, IOTA_FRAMEWORK_PACKAGE_ID]);
@@ -1881,7 +1881,7 @@ impl fmt::Display for FakeID {
static NAMED_ADDRESSES: Lazy> = Lazy::new(|| {
let mut map = move_stdlib::move_stdlib_named_addresses();
assert!(map.get("std").unwrap().into_inner() == MOVE_STDLIB_ADDRESS);
- // TODO fix Iota framework constants
+ // TODO fix IOTA framework constants
map.insert(
"iota".to_string(),
NumericalAddress::new(
@@ -1956,7 +1956,7 @@ pub static PRE_COMPILED: Lazy = Lazy::new(|| {
.unwrap();
match fully_compiled_res {
Err((files, diags)) => {
- eprintln!("!!!Iota framework failed to compile!!!");
+ eprintln!("!!!IOTA framework failed to compile!!!");
move_compiler::diagnostics::report_diagnostics(&files, diags)
}
Ok(res) => res,
@@ -2039,7 +2039,7 @@ async fn init_val_fullnode_executor(
test_account
};
- // For each named Iota account without an address value, create an account with
+ // For each named IOTA account without an address value, create an account with
// an address and a gas object
for n in account_names {
let test_account = mk_account();
@@ -2095,7 +2095,7 @@ async fn init_sim_executor(
let mut accounts = BTreeMap::new();
let mut objects = vec![];
- // For each named Iota account without an address value, create a key pair
+ // For each named IOTA account without an address value, create a key pair
for n in account_names {
let test_account = get_key_pair_from_rng(&mut rng);
account_kps.insert(n, test_account);
diff --git a/crates/iota-types/src/README.md b/crates/iota-types/src/README.md
index 2ed1f4446db..3b0532b87cb 100644
--- a/crates/iota-types/src/README.md
+++ b/crates/iota-types/src/README.md
@@ -3,7 +3,7 @@
Note: this README file currently covers cryptography-related structs and methods.
Currently, three files are equipped with signature and hashing functionality (`crypto.rs`, `signature_seed` and
-`messages.rs`). See [Iota Signatures](https://github.com/iotaledger/iota/blob/develop/docs/content/concepts/cryptography/transaction-auth/signatures.mdx) for supported signature schemes and its requirments for user and authority signatures. See [fastcrypto](https://github.com/MystenLabs/fastcrypto) for concrete implementation of various cryptography libraries.
+`messages.rs`). See [IOTA Signatures](https://github.com/iotaledger/iota/blob/develop/docs/content/concepts/cryptography/transaction-auth/signatures.mdx) for supported signature schemes and its requirments for user and authority signatures. See [fastcrypto](https://github.com/MystenLabs/fastcrypto) for concrete implementation of various cryptography libraries.
## Quick links
diff --git a/crates/iota-types/src/base_types.rs b/crates/iota-types/src/base_types.rs
index b28eafbdcd0..4b156f96912 100644
--- a/crates/iota-types/src/base_types.rs
+++ b/crates/iota-types/src/base_types.rs
@@ -173,7 +173,7 @@ pub struct MoveObjectType(MoveObjectType_);
pub enum MoveObjectType_ {
/// A type that is not `0x2::coin::Coin`
Other(StructTag),
- /// A IOTA coin (i.e., `0x2::coin::Coin<0x2::iota::IOTA>`)
+ /// An IOTA coin (i.e., `0x2::coin::Coin<0x2::iota::IOTA>`)
GasCoin,
/// A record of a staked IOTA coin (i.e., `0x3::staking_pool::StakedIota`)
StakedIota,
@@ -491,7 +491,7 @@ pub fn is_primitive_type_tag(t: &TypeTag) -> bool {
}
}
-/// Type of a Iota object
+/// Type of an IOTA object
#[derive(Clone, Serialize, Deserialize, Ord, PartialOrd, Eq, PartialEq, Debug)]
pub enum ObjectType {
/// Move package containing one or more bytecode modules
@@ -775,7 +775,7 @@ impl From<&MultiSigPublicKey> for IotaAddress {
}
}
-/// Iota address for [struct ZkLoginAuthenticator] is defined as the black2b
+/// IOTA address for [struct ZkLoginAuthenticator] is defined as the black2b
/// hash of [zklogin_flag || iss_bytes_length || iss_bytes ||
/// unpadded_address_seed_in_bytes].
impl TryFrom<&ZkLoginAuthenticator> for IotaAddress {
@@ -787,7 +787,7 @@ impl TryFrom<&ZkLoginAuthenticator> for IotaAddress {
impl TryFrom<&GenericSignature> for IotaAddress {
type Error = IotaError;
- /// Derive a IotaAddress from a serialized signature in Iota
+ /// Derive a IotaAddress from a serialized signature in IOTA
/// [GenericSignature].
fn try_from(sig: &GenericSignature) -> IotaResult {
match sig {
diff --git a/crates/iota-types/src/crypto.rs b/crates/iota-types/src/crypto.rs
index c4f0d0b8af4..69dd0f81abf 100644
--- a/crates/iota-types/src/crypto.rs
+++ b/crates/iota-types/src/crypto.rs
@@ -409,7 +409,7 @@ impl PublicKey {
}
/// Defines the compressed version of the public key that we pass around
-/// in Iota
+/// in IOTA.
#[serde_as]
#[derive(
Copy,
diff --git a/crates/iota-types/src/event.rs b/crates/iota-types/src/event.rs
index f879bc64d2e..7e63e7dd960 100755
--- a/crates/iota-types/src/event.rs
+++ b/crates/iota-types/src/event.rs
@@ -25,7 +25,7 @@ use crate::{
object::bounded_visitor::BoundedVisitor,
};
-/// A universal Iota event type encapsulating different types of events
+/// A universal IOTA event type encapsulating different types of events
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct EventEnvelope {
/// UTC timestamp in milliseconds since epoch (1/1/1970)
@@ -39,7 +39,7 @@ pub struct EventEnvelope {
/// Move event's json value
pub parsed_json: Value,
}
-/// Unique ID of a Iota Event, the ID is a combination of tx seq number and
+/// Unique ID of an IOTA Event, the ID is a combination of tx seq number and
/// event seq number, the ID is local to this particular fullnode and will be
/// different from other fullnode.
#[serde_as]
diff --git a/crates/iota-types/src/execution_status.rs b/crates/iota-types/src/execution_status.rs
index 22a23be2188..00b9a1740b0 100644
--- a/crates/iota-types/src/execution_status.rs
+++ b/crates/iota-types/src/execution_status.rs
@@ -45,7 +45,7 @@ pub enum ExecutionFailureStatus {
// General transaction errors
#[error("Insufficient Gas.")]
InsufficientGas,
- #[error("Invalid Gas Object. Possibly not address-owned or possibly not a IOTA coin.")]
+ #[error("Invalid Gas Object. Possibly not address-owned or possibly not an IOTA coin.")]
InvalidGasObject,
#[error("INVARIANT VIOLATION.")]
InvariantViolation,
@@ -84,8 +84,8 @@ pub enum ExecutionFailureStatus {
PublishErrorNonZeroAddress,
#[error(
- "Iota Move Bytecode Verification Error. \
- Please run the Iota Move Verifier for more information."
+ "IOTA Move Bytecode Verification Error. \
+ Please run the IOTA Move Verifier for more information."
)]
IotaMoveVerificationError,
@@ -183,8 +183,8 @@ pub enum ExecutionFailureStatus {
CertificateDenied,
#[error(
- "Iota Move Bytecode Verification Timeout. \
- Please run the Iota Move Verifier for more information."
+ "IOTA Move Bytecode Verification Timeout. \
+ Please run the IOTA Move Verifier for more information."
)]
IotaMoveVerificationTimeout,
diff --git a/crates/iota-types/src/gas_coin.rs b/crates/iota-types/src/gas_coin.rs
index 103ef6c2c59..53bec008e32 100644
--- a/crates/iota-types/src/gas_coin.rs
+++ b/crates/iota-types/src/gas_coin.rs
@@ -25,7 +25,7 @@ use crate::{
object::{Data, MoveObject, Object},
};
-/// The number of Nanos per Iota token
+/// The number of Nanos per IOTA token
pub const NANOS_PER_IOTA: u64 = 1_000_000_000;
/// Total supply in IOTA at genesis, after the migration from a Stardust ledger,
diff --git a/crates/iota-types/src/gas_model/gas_v1.rs b/crates/iota-types/src/gas_model/gas_v1.rs
index f173d7f7425..c9843f970d7 100644
--- a/crates/iota-types/src/gas_model/gas_v1.rs
+++ b/crates/iota-types/src/gas_model/gas_v1.rs
@@ -84,7 +84,7 @@ mod checked {
/ BASIS_POINTS) as u64
}
- /// A list of constant costs of various operations in Iota.
+ /// A list of constant costs of various operations in IOTA.
pub struct IotaCostTable {
/// A flat fee charged for every transaction. This is also the minimum
/// amount of gas charged for a transaction.
@@ -157,9 +157,9 @@ mod checked {
/// It has been multiplied by the storage gas price. This is the new
/// storage rebate.
pub storage_cost: u64,
- /// storage_rebate is the storage rebate (in Iota) for in this object.
+ /// storage_rebate is the storage rebate (in IOTA) for in this object.
/// This is computed at the end of execution while determining storage
- /// charges. The value is in Iota.
+ /// charges. The value is in IOTA.
pub storage_rebate: u64,
/// The object size post-transaction in bytes
pub new_size: u64,
diff --git a/crates/iota-types/src/iota_system_state/epoch_start_iota_system_state.rs b/crates/iota-types/src/iota_system_state/epoch_start_iota_system_state.rs
index 45d800b9293..3ea1e20af44 100644
--- a/crates/iota-types/src/iota_system_state/epoch_start_iota_system_state.rs
+++ b/crates/iota-types/src/iota_system_state/epoch_start_iota_system_state.rs
@@ -202,7 +202,7 @@ impl EpochStartSystemStateTrait for EpochStartSystemStateV1 {
}
// Sort the authorities by their authority (public) key in ascending order, same
- // as the order in the Iota committee returned from get_iota_committee().
+ // as the order in the IOTA committee returned from get_iota_committee().
authorities.sort_by(|a1, a2| a1.authority_key.cmp(&a2.authority_key));
for ((i, mysticeti_authority), iota_authority_name) in authorities
@@ -212,7 +212,7 @@ impl EpochStartSystemStateTrait for EpochStartSystemStateV1 {
{
if iota_authority_name.0 != mysticeti_authority.authority_key.to_bytes() {
error!(
- "Mismatched authority order between Iota and Mysticeti! Index {}, Mysticeti authority {:?}\nIota authority name {}",
+ "Mismatched authority order between IOTA and Mysticeti! Index {}, Mysticeti authority {:?}\nIota authority name {}",
i, mysticeti_authority, iota_authority_name
);
}
diff --git a/crates/iota-types/src/iota_system_state/mod.rs b/crates/iota-types/src/iota_system_state/mod.rs
index 18f4fec702d..ab8c4545a5a 100644
--- a/crates/iota-types/src/iota_system_state/mod.rs
+++ b/crates/iota-types/src/iota_system_state/mod.rs
@@ -399,7 +399,7 @@ pub struct PoolTokenExchangeRate {
}
impl PoolTokenExchangeRate {
- /// Rate of the staking pool, pool token amount : Iota amount
+ /// Rate of the staking pool, pool token amount : IOTA amount
pub fn rate(&self) -> f64 {
if self.iota_amount == 0 {
1_f64
diff --git a/crates/iota-types/src/messages_consensus.rs b/crates/iota-types/src/messages_consensus.rs
index a87ede12052..46def77b51f 100644
--- a/crates/iota-types/src/messages_consensus.rs
+++ b/crates/iota-types/src/messages_consensus.rs
@@ -69,7 +69,7 @@ pub fn check_total_jwk_size(id: &JwkId, jwk: &JWK) -> bool {
#[derive(Serialize, Deserialize, Clone, Debug)]
pub struct ConsensusTransaction {
/// Encodes an u64 unique tracking id to allow us trace a message between
- /// Iota and consensus. Use an byte array instead of u64 to ensure stable
+ /// IOTA and consensus. Use an byte array instead of u64 to ensure stable
/// serialization.
pub tracking_id: [u8; 8],
pub kind: ConsensusTransactionKind,
@@ -170,7 +170,7 @@ impl AuthorityCapabilitiesV1 {
) -> Self {
let generation = SystemTime::now()
.duration_since(UNIX_EPOCH)
- .expect("Iota did not exist prior to 1970")
+ .expect("IOTA did not exist prior to 1970")
.as_millis()
.try_into()
.expect("This build of iota is not supported in the year 500,000,000");
diff --git a/crates/iota-types/src/object.rs b/crates/iota-types/src/object.rs
index 63ef7c06824..706f8c836f2 100644
--- a/crates/iota-types/src/object.rs
+++ b/crates/iota-types/src/object.rs
@@ -380,7 +380,7 @@ pub enum Data {
Move(MoveObject),
/// Map from each module name to raw serialized Move module bytes
Package(MovePackage),
- // ... Iota "native" types go here
+ // ... IOTA "native" types go here
}
impl Data {
diff --git a/crates/iota-types/src/stardust/address.rs b/crates/iota-types/src/stardust/address.rs
index 40758c09d87..d31ea6b1513 100644
--- a/crates/iota-types/src/stardust/address.rs
+++ b/crates/iota-types/src/stardust/address.rs
@@ -7,7 +7,7 @@ use crate::{base_types::IotaAddress, object::Owner};
/// Converts a ["Stardust" `Address`](Address) to a [`IotaAddress`].
///
-/// This is intended as the only conversion function to go from Stardust to Iota
+/// This is intended as the only conversion function to go from Stardust to IOTA
/// addresses, so there is only one place to potentially update it if we decide
/// to change it later.
pub fn stardust_to_iota_address(
diff --git a/crates/iota-verifier-transactional-tests/Cargo.toml b/crates/iota-verifier-transactional-tests/Cargo.toml
index 767e3f1e938..a67e253ec0e 100644
--- a/crates/iota-verifier-transactional-tests/Cargo.toml
+++ b/crates/iota-verifier-transactional-tests/Cargo.toml
@@ -5,7 +5,7 @@ authors = ["IOTA Foundation "]
edition = "2021"
license = "Apache-2.0"
publish = false
-description = "Transactional tests for Iota Verifier"
+description = "Transactional tests for IOTA Verifier"
[dev-dependencies]
# external dependencies
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/clock_mut.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/clock_mut.exp
index a4492d10dfe..239c311258b 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/clock_mut.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/clock_mut.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-15:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Clock must be passed by immutable reference. got: &mut iota::clock::Clock"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/clock_val.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/clock_val.exp
index e0d116b31b4..1be9cf564b8 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/clock_val.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/clock_val.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-15:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Clock must be passed by immutable reference. got: iota::clock::Clock"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/generic_obj_mut_ref_vector.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/generic_obj_mut_ref_vector.exp
index 2840abcd950..809f1caaee8 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/generic_obj_mut_ref_vector.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/generic_obj_mut_ref_vector.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-16:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: &mut vector"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/generic_obj_ref_vector.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/generic_obj_ref_vector.exp
index be3291d02da..19873e95822 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/generic_obj_ref_vector.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/generic_obj_ref_vector.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-16:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: &vector"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/generic_with_key_invalid.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/generic_with_key_invalid.exp
index 0a1908d41e6..c7f460ed13d 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/generic_with_key_invalid.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/generic_with_key_invalid.exp
@@ -2,10 +2,10 @@ processed 2 tasks
task 0, lines 7-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: std::option::Option"), command: Some(0) } }
task 1, lines 19-29:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: vector>"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/nested_key_generic_vector_param.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/nested_key_generic_vector_param.exp
index c739ae04a41..df34bb64271 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/nested_key_generic_vector_param.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/nested_key_generic_vector_param.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-14:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: vector>"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct.exp
index 977a95bd36e..da6d0c0b57c 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-18:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: _::m::S"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct_generic.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct_generic.exp
index 1455cc7a103..6da4b2c9863 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct_generic.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct_generic.exp
@@ -2,10 +2,10 @@ processed 2 tasks
task 0, lines 7-22:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: _::m::Obj<_::m::NoStore>"), command: Some(0) } }
task 1, lines 24-36:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: _::m::Obj"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct_vector.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct_vector.exp
index 875ff1a8c5d..8f9d1b26fec 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct_vector.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/non_key_struct_vector.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-18:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: vector<_::m::S>"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/obj_mut_ref_vector.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/obj_mut_ref_vector.exp
index 7574c578c69..d5f67ca8fa9 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/obj_mut_ref_vector.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/obj_mut_ref_vector.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-19:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: &mut vector<_::m::S>"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/obj_ref_vector.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/obj_ref_vector.exp
index df8bd816d84..a7d5bebb8b8 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/obj_ref_vector.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/obj_ref_vector.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-19:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Expected primitive or object type. Got: &vector<_::m::S>"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/random_mut.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/random_mut.exp
index 2a51f91d8d8..fd4c0ba8aa0 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/random_mut.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/random_mut.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-15:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Random must be passed by immutable reference. got: &mut iota::random::Random"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/random_val.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/random_val.exp
index 3c53406e5be..4fdc537799b 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/random_val.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/random_val.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-15:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point parameter type. Random must be passed by immutable reference. got: iota::random::Random"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/entry_points/return_values_invalid.exp b/crates/iota-verifier-transactional-tests/tests/entry_points/return_values_invalid.exp
index 44e7c39a4eb..ab1e932508b 100644
--- a/crates/iota-verifier-transactional-tests/tests/entry_points/return_values_invalid.exp
+++ b/crates/iota-verifier-transactional-tests/tests/entry_points/return_values_invalid.exp
@@ -2,30 +2,30 @@ processed 6 tasks
task 0, lines 7-14:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point return type. Expected a non reference type."), command: Some(0) } }
task 1, lines 16-23:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point return type. Expected a non reference type."), command: Some(0) } }
task 2, lines 25-32:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point return type. Expected a non reference type."), command: Some(0) } }
task 3, lines 34-42:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point return type. The specified return type does not have the 'drop' ability: _::m::Copyable"), command: Some(0) } }
task 4, lines 44-53:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point return type. The specified return type does not have the 'drop' ability: _::m::Obj"), command: Some(0) } }
task 5, lines 55-64:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Invalid entry point return type. The specified return type does not have the 'drop' ability: vector<_::m::Obj>"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_only.exp b/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_only.exp
index 32b55156b81..4cb8524f57a 100644
--- a/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_only.exp
+++ b/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_only.exp
@@ -2,5 +2,5 @@ processed 2 tasks
task 1, lines 7-12:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Enum X cannot have the 'key' ability. Enums cannot have the 'key' ability."), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_only_uid_field.exp b/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_only_uid_field.exp
index e34d4b330b7..800ff642f3f 100644
--- a/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_only_uid_field.exp
+++ b/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_only_uid_field.exp
@@ -2,5 +2,5 @@ processed 2 tasks
task 1, lines 7-14:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Enum X cannot have the 'key' ability. Enums cannot have the 'key' ability."), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_store.exp b/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_store.exp
index 40adcd44315..94d672b9f7e 100644
--- a/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_store.exp
+++ b/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_store.exp
@@ -2,5 +2,5 @@ processed 2 tasks
task 1, lines 7-12:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Enum X cannot have the 'key' ability. Enums cannot have the 'key' ability."), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_store_uid_field.exp b/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_store_uid_field.exp
index e34d4b330b7..800ff642f3f 100644
--- a/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_store_uid_field.exp
+++ b/crates/iota-verifier-transactional-tests/tests/enums/enum_with_key_store_uid_field.exp
@@ -2,5 +2,5 @@ processed 2 tasks
task 1, lines 7-14:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Enum X cannot have the 'key' ability. Enums cannot have the 'key' ability."), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/id_leak/indirect_leak_through_call.exp b/crates/iota-verifier-transactional-tests/tests/id_leak/indirect_leak_through_call.exp
index addb3329cd5..a8c3a69e9f5 100644
--- a/crates/iota-verifier-transactional-tests/tests/id_leak/indirect_leak_through_call.exp
+++ b/crates/iota-verifier-transactional-tests/tests/id_leak/indirect_leak_through_call.exp
@@ -2,7 +2,7 @@ processed 2 tasks
task 0, lines 5-27:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("PartialVMError with status UNKNOWN_VERIFICATION_ERROR with sub status 1 and message Invalid object creation in _::m::foo. Object created without a newly created UID. The UID must come directly from iota::object::new. Or for tests, it can come from iota::test_scenario::new_object"), command: Some(0) } }
task 1, lines 29-51:
diff --git a/crates/iota-verifier-transactional-tests/tests/id_leak/through_call_with_borrow_field.exp b/crates/iota-verifier-transactional-tests/tests/id_leak/through_call_with_borrow_field.exp
index 8b26a3ad601..0e54f7b12af 100644
--- a/crates/iota-verifier-transactional-tests/tests/id_leak/through_call_with_borrow_field.exp
+++ b/crates/iota-verifier-transactional-tests/tests/id_leak/through_call_with_borrow_field.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-35:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("PartialVMError with status UNKNOWN_VERIFICATION_ERROR with sub status 1 and message Invalid object creation in _::m::new. Object created without a newly created UID. The UID must come directly from iota::object::new. Or for tests, it can come from iota::test_scenario::new_object"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/id_leak/through_indirect_return.exp b/crates/iota-verifier-transactional-tests/tests/id_leak/through_indirect_return.exp
index 53227a2c2da..326f8a498ea 100644
--- a/crates/iota-verifier-transactional-tests/tests/id_leak/through_indirect_return.exp
+++ b/crates/iota-verifier-transactional-tests/tests/id_leak/through_indirect_return.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-21:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("PartialVMError with status UNKNOWN_VERIFICATION_ERROR with sub status 1 and message Invalid object creation in _::m::foo. Object created without a newly created UID. The UID must come directly from iota::object::new. Or for tests, it can come from iota::test_scenario::new_object"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/id_leak/through_pack.exp b/crates/iota-verifier-transactional-tests/tests/id_leak/through_pack.exp
index 448a15d26c1..43e45552ee7 100644
--- a/crates/iota-verifier-transactional-tests/tests/id_leak/through_pack.exp
+++ b/crates/iota-verifier-transactional-tests/tests/id_leak/through_pack.exp
@@ -2,7 +2,7 @@ processed 2 tasks
task 0, lines 5-38:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("PartialVMError with status UNKNOWN_VERIFICATION_ERROR with sub status 1 and message Invalid object creation in _::test::test. Object created without a newly created UID. The UID must come directly from iota::object::new. Or for tests, it can come from iota::test_scenario::new_object"), command: Some(0) } }
task 1, lines 40-63:
diff --git a/crates/iota-verifier-transactional-tests/tests/id_leak/transmute.exp b/crates/iota-verifier-transactional-tests/tests/id_leak/transmute.exp
index 932699d0326..c15f87691b8 100644
--- a/crates/iota-verifier-transactional-tests/tests/id_leak/transmute.exp
+++ b/crates/iota-verifier-transactional-tests/tests/id_leak/transmute.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-29:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("PartialVMError with status UNKNOWN_VERIFICATION_ERROR with sub status 1 and message Invalid object creation in _::m::transmute. Object created without a newly created UID. The UID must come directly from iota::object::new. Or for tests, it can come from iota::test_scenario::new_object"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/init/cannot_call_init.exp b/crates/iota-verifier-transactional-tests/tests/init/cannot_call_init.exp
index a7382a30ac6..6b41a27d0e0 100644
--- a/crates/iota-verifier-transactional-tests/tests/init/cannot_call_init.exp
+++ b/crates/iota-verifier-transactional-tests/tests/init/cannot_call_init.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-18:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::init at offset 1. Cannot call a module's 'init' function from another Move function"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/init/must_have_txn_context.exp b/crates/iota-verifier-transactional-tests/tests/init/must_have_txn_context.exp
index 66867e9543d..4e8a74e15bd 100644
--- a/crates/iota-verifier-transactional-tests/tests/init/must_have_txn_context.exp
+++ b/crates/iota-verifier-transactional-tests/tests/init/must_have_txn_context.exp
@@ -2,10 +2,10 @@ processed 2 tasks
task 0, lines 5-12:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected at least one and at most two parameters for _::m::init"), command: Some(0) } }
task 1, lines 15-22:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last (and at most second) parameter for _::m::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext; optional first parameter must be of one-time witness type whose name is the same as the capitalized module name (_::m::M) and which has no fields or a single field of type bool"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/init/not_generic.exp b/crates/iota-verifier-transactional-tests/tests/init/not_generic.exp
index 9623e9d1a8c..3460c2bc6fd 100644
--- a/crates/iota-verifier-transactional-tests/tests/init/not_generic.exp
+++ b/crates/iota-verifier-transactional-tests/tests/init/not_generic.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-12:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m. 'init' function cannot have type parameters"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/init/not_private.exp b/crates/iota-verifier-transactional-tests/tests/init/not_private.exp
index f75ce843fa3..2b37fc3d322 100644
--- a/crates/iota-verifier-transactional-tests/tests/init/not_private.exp
+++ b/crates/iota-verifier-transactional-tests/tests/init/not_private.exp
@@ -2,15 +2,15 @@ processed 3 tasks
task 0, lines 5-12:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m. 'init' function must be private"), command: Some(0) } }
task 1, lines 14-21:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m. 'init' function must be private"), command: Some(0) } }
task 2, lines 23-30:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m. 'init' function must be private"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/init/not_txn_context.exp b/crates/iota-verifier-transactional-tests/tests/init/not_txn_context.exp
index 8af04d0c625..7833f1f154b 100644
--- a/crates/iota-verifier-transactional-tests/tests/init/not_txn_context.exp
+++ b/crates/iota-verifier-transactional-tests/tests/init/not_txn_context.exp
@@ -2,15 +2,15 @@ processed 3 tasks
task 0, lines 5-12:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last parameter for _::m::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext, but found u64"), command: Some(0) } }
task 1, lines 14-21:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last parameter for _::tx_context::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext, but found _::tx_context::TxContext"), command: Some(0) } }
task 2, lines 23-30:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last parameter for _::m::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext, but found iota::tx_context::TxContext"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/init/return_values.exp b/crates/iota-verifier-transactional-tests/tests/init/return_values.exp
index 615b4c12e98..d4696af14a1 100644
--- a/crates/iota-verifier-transactional-tests/tests/init/return_values.exp
+++ b/crates/iota-verifier-transactional-tests/tests/init/return_values.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-12:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m, 'init' function cannot have return values"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_no_drop.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_no_drop.exp
index e4c071ffd2e..ec8268f6348 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_no_drop.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_no_drop.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-20:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last (and at most second) parameter for _::m::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext; optional first parameter must be of one-time witness type whose name is the same as the capitalized module name (_::m::M) and which has no fields or a single field of type bool"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_single_variant_bool_field.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_single_variant_bool_field.exp
index c0bae74de0a..cb53356e651 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_single_variant_bool_field.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_single_variant_bool_field.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-19:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last (and at most second) parameter for _::m::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext; optional first parameter must be of one-time witness type whose name is the same as the capitalized module name (_::m::M) and which has no fields or a single field of type bool"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_single_variant_no_field.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_single_variant_no_field.exp
index c0bae74de0a..cb53356e651 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_single_variant_no_field.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_single_variant_no_field.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-19:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last (and at most second) parameter for _::m::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext; optional first parameter must be of one-time witness type whose name is the same as the capitalized module name (_::m::M) and which has no fields or a single field of type bool"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_wrong_name.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_wrong_name.exp
index c0bae74de0a..cb53356e651 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_wrong_name.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/enum_wrong_name.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-19:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last (and at most second) parameter for _::m::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext; optional first parameter must be of one-time witness type whose name is the same as the capitalized module name (_::m::M) and which has no fields or a single field of type bool"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/instantiate.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/instantiate.exp
index 3eb93fc2e2f..8b0b1e79500 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/instantiate.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/instantiate.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-25:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("one-time witness type _::m::M is instantiated in the _::m::pack function and must never be"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/many_fields_invalid.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/many_fields_invalid.exp
index f1311b65f17..0431d21d4e4 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/many_fields_invalid.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/many_fields_invalid.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last (and at most second) parameter for _::m::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext; optional first parameter must be of one-time witness type whose name is the same as the capitalized module name (_::m::M) and which has no fields or a single field of type bool"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/more_abilities.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/more_abilities.exp
index f9ad125643a..7017dc97e19 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/more_abilities.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/more_abilities.exp
@@ -2,15 +2,15 @@ processed 4 tasks
task 1, lines 9-20:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("one-time witness type candidate _::m::M must have a single ability: drop"), command: Some(0) } }
task 2, lines 22-33:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("one-time witness type candidate _::m::M must have a single ability: drop"), command: Some(0) } }
task 3, lines 35-46:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("one-time witness type candidate _::m::M must have a single ability: drop"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/no_drop.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/no_drop.exp
index 46109963c25..9d34b48817b 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/no_drop.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/no_drop.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-19:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("one-time witness type candidate _::m::M must have a single ability: drop"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/no_init_arg.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/no_init_arg.exp
index 969e3571f84..2f730a0c4b4 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/no_init_arg.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/no_init_arg.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("init function of a module containing one-time witness type candidate must have _::m::M as the first parameter (a struct which has no fields or a single field of type bool)"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/other_mod_def.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/other_mod_def.exp
index c7f962e4667..93cc50f1c1b 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/other_mod_def.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/other_mod_def.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last (and at most second) parameter for _::n::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext; optional first parameter must be of one-time witness type whose name is the same as the capitalized module name (_::n::N) and which has no fields or a single field of type bool"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/type_param.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/type_param.exp
index ba9b05b2181..6a78b3be337 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/type_param.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/type_param.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m. 'init' function cannot have type parameters"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_field_type_with_init.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_field_type_with_init.exp
index f1311b65f17..0431d21d4e4 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_field_type_with_init.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_field_type_with_init.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last (and at most second) parameter for _::m::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext; optional first parameter must be of one-time witness type whose name is the same as the capitalized module name (_::m::M) and which has no fields or a single field of type bool"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_init_type.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_init_type.exp
index 28a67527e37..997b75451fb 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_init_type.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_init_type.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-18:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("init function of a module containing one-time witness type candidate must have _::m::M as the first parameter (a struct which has no fields or a single field of type bool)"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_name.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_name.exp
index f1311b65f17..0431d21d4e4 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_name.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_name.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last (and at most second) parameter for _::m::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext; optional first parameter must be of one-time witness type whose name is the same as the capitalized module name (_::m::M) and which has no fields or a single field of type bool"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_name_format.exp b/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_name_format.exp
index 8bfc186de21..2a8b60ea6aa 100644
--- a/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_name_format.exp
+++ b/crates/iota-verifier-transactional-tests/tests/one_time_witness/wrong_name_format.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 7-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Expected last (and at most second) parameter for _::mod::init to be &mut iota::tx_context::TxContext or &iota::tx_context::TxContext; optional first parameter must be of one-time witness type whose name is the same as the capitalized module name (_::mod::MOD) and which has no fields or a single field of type bool"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer.exp b/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer.exp
index 12052bcbcad..c9ef4f3bfeb 100644
--- a/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer.exp
+++ b/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer.exp
@@ -2,20 +2,20 @@ processed 4 tasks
task 0, lines 7-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::transfer' on an object of type 'iota::coin::Coin'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_transfer'"), command: Some(0) } }
task 1, lines 19-29:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::freeze_object' on an object of type 'iota::coin::Coin'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_freeze_object'"), command: Some(0) } }
task 2, lines 31-41:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::share_object' on an object of type 'iota::coin::Coin'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_share_object'"), command: Some(0) } }
task 3, lines 43-55:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::receive' on an object of type 'iota::coin::Coin'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_receive'"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_explicit.exp b/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_explicit.exp
index f227e1b7b2d..d4435f83e9e 100644
--- a/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_explicit.exp
+++ b/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_explicit.exp
@@ -8,47 +8,47 @@ gas summary: computation_cost: 1000000, computation_cost_burned: 1000000, storag
task 3, lines 31-40:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("Enum StoreEnum cannot have the 'key' ability. Enums cannot have the 'key' ability."), command: Some(0) } }
task 4, lines 42-52:
//# publish --dependencies test
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::u::f. Invalid call to 'iota::transfer::transfer' on an object of type 'test::m::KeyStruct'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_transfer'"), command: Some(0) } }
task 5, lines 54-64:
//# publish --dependencies test
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::u::f. Invalid call to 'iota::transfer::freeze_object' on an object of type 'test::m::KeyStruct'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_freeze_object'"), command: Some(0) } }
task 6, lines 66-76:
//# publish --dependencies test
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::u::f. Invalid call to 'iota::transfer::share_object' on an object of type 'test::m::KeyStruct'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_share_object'"), command: Some(0) } }
task 7, lines 78-92:
//# publish --dependencies test
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::u::f. Invalid call to 'iota::transfer::receive' on an object of type 'test::m::KeyStruct'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_receive'"), command: Some(0) } }
task 8, lines 94-104:
//# publish --dependencies test
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::u::f. Invalid call to 'iota::transfer::transfer' on an object of type 'test::m::KeyStoreStruct'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_transfer'"), command: Some(0) } }
task 9, lines 106-116:
//# publish --dependencies test
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::u::f. Invalid call to 'iota::transfer::freeze_object' on an object of type 'test::m::KeyStoreStruct'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_freeze_object'"), command: Some(0) } }
task 10, lines 118-128:
//# publish --dependencies test
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::u::f. Invalid call to 'iota::transfer::share_object' on an object of type 'test::m::KeyStoreStruct'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_share_object'"), command: Some(0) } }
task 11, lines 130-144:
//# publish --dependencies test
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::u::f. Invalid call to 'iota::transfer::receive' on an object of type 'test::m::KeyStoreStruct'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_receive'"), command: Some(0) } }
task 12, lines 146-156:
diff --git a/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_generic.exp b/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_generic.exp
index 4746b7e67ef..70c43fe50f7 100644
--- a/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_generic.exp
+++ b/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_generic.exp
@@ -2,20 +2,20 @@ processed 4 tasks
task 0, lines 9-18:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::transfer' on an object of type 'T0'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_transfer'"), command: Some(0) } }
task 1, lines 20-29:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::freeze_object' on an object of type 'T0'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_freeze_object'"), command: Some(0) } }
task 2, lines 31-40:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::share_object' on an object of type 'T0'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_share_object'"), command: Some(0) } }
task 3, lines 42-53:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::receive' on an object of type 'T0'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_receive'"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_store.exp b/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_store.exp
index 12052bcbcad..c9ef4f3bfeb 100644
--- a/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_store.exp
+++ b/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_store.exp
@@ -2,20 +2,20 @@ processed 4 tasks
task 0, lines 7-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::transfer' on an object of type 'iota::coin::Coin'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_transfer'"), command: Some(0) } }
task 1, lines 19-29:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::freeze_object' on an object of type 'iota::coin::Coin'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_freeze_object'"), command: Some(0) } }
task 2, lines 31-41:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::share_object' on an object of type 'iota::coin::Coin'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_share_object'"), command: Some(0) } }
task 3, lines 43-55:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::receive' on an object of type 'iota::coin::Coin'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_receive'"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_store_generic.exp b/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_store_generic.exp
index b9aa3b43aaf..716d6fb4e1e 100644
--- a/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_store_generic.exp
+++ b/crates/iota-verifier-transactional-tests/tests/private_generics/no_public_transfer_store_generic.exp
@@ -2,20 +2,20 @@ processed 5 tasks
task 1, lines 11-20:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::transfer' on an object of type 'T0'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_transfer'"), command: Some(0) } }
task 2, lines 22-31:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::freeze_object' on an object of type 'T0'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_freeze_object'"), command: Some(0) } }
task 3, lines 33-42:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::share_object' on an object of type 'T0'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_share_object'"), command: Some(0) } }
task 4, lines 44-55:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::receive' on an object of type 'T0'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_receive'"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/private_generics/private_event_emit.exp b/crates/iota-verifier-transactional-tests/tests/private_generics/private_event_emit.exp
index a85e79543d0..c58fcf4f862 100644
--- a/crates/iota-verifier-transactional-tests/tests/private_generics/private_event_emit.exp
+++ b/crates/iota-verifier-transactional-tests/tests/private_generics/private_event_emit.exp
@@ -2,22 +2,22 @@ processed 9 tasks
task 1, lines 9-18:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::event::emit' with an event type 'T0'. The event's type must be defined in the current module"), command: Some(0) } }
task 2, lines 20-29:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::event::emit' with an event type 'u64'. The event's type must be defined in the current module"), command: Some(0) } }
task 3, lines 31-44:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::event::emit' with an event type 'vector<_::m::X>'. The event's type must be defined in the current module"), command: Some(0) } }
task 4, lines 46-59:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::event::emit' with an event type 'vector<_::m::X>'. The event's type must be defined in the current module"), command: Some(0) } }
task 5, lines 61-70:
@@ -28,10 +28,10 @@ gas summary: computation_cost: 1000000, computation_cost_burned: 1000000, storag
task 7, lines 74-84:
//# publish --dependencies test
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::t::t. Invalid call to 'iota::event::emit' with an event type 'test::m::X'. The event's type must be defined in the current module"), command: Some(0) } }
task 8, lines 86-96:
//# publish --dependencies test
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::t::t. Invalid call to 'iota::event::emit' with an event type 'test::m::Y'. The event's type must be defined in the current module"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/private_generics/receive_with_and_without_store.exp b/crates/iota-verifier-transactional-tests/tests/private_generics/receive_with_and_without_store.exp
index dba2c2207a4..99e2adaff60 100644
--- a/crates/iota-verifier-transactional-tests/tests/private_generics/receive_with_and_without_store.exp
+++ b/crates/iota-verifier-transactional-tests/tests/private_generics/receive_with_and_without_store.exp
@@ -2,12 +2,12 @@ processed 4 tasks
task 0, lines 1-12:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::receive_bad. Invalid call to 'iota::transfer::receive' on an object of type 'T0'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_receive'"), command: Some(0) } }
task 1, lines 14-25:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m1::receive_bad. Invalid call to 'iota::transfer::receive' on an object of type 'T0'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_receive'"), command: Some(0) } }
task 2, lines 27-41:
diff --git a/crates/iota-verifier-transactional-tests/tests/private_transfer/transfer_invalid.exp b/crates/iota-verifier-transactional-tests/tests/private_transfer/transfer_invalid.exp
index 0bc81b15eca..307ff561bfd 100644
--- a/crates/iota-verifier-transactional-tests/tests/private_transfer/transfer_invalid.exp
+++ b/crates/iota-verifier-transactional-tests/tests/private_transfer/transfer_invalid.exp
@@ -2,20 +2,20 @@ processed 4 tasks
task 0, lines 7-17:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::transfer' on an object of type 'iota::clock::Clock'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_transfer'"), command: Some(0) } }
task 1, lines 19-29:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::share_object' on an object of type 'iota::clock::Clock'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_share_object'"), command: Some(0) } }
task 2, lines 31-41:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::freeze_object' on an object of type 'iota::clock::Clock'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_freeze_object'"), command: Some(0) } }
task 3, lines 43-55:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("_::m::t. Invalid call to 'iota::transfer::receive' on an object of type 'iota::clock::Clock'. The transferred object's type must be defined in the current module. If the object has the 'store' type ability, you can use the non-internal variant instead, i.e. 'iota::transfer::public_receive'"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_first_field_not_id.exp b/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_first_field_not_id.exp
index e8b016b7fc3..2a91386eccf 100644
--- a/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_first_field_not_id.exp
+++ b/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_first_field_not_id.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-11:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("First field of struct S must be 'id', flag found"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_struct_address.exp b/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_struct_address.exp
index 3a90c0c63a1..dcfef40e505 100644
--- a/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_struct_address.exp
+++ b/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_struct_address.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-12:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("First field of struct S must be of type iota::object::UID, _::object::UID type found"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_struct_name.exp b/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_struct_name.exp
index 37209ac818d..bdbc62c9c35 100644
--- a/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_struct_name.exp
+++ b/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_struct_name.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-11:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("First field of struct S must be of type iota::object::UID, iota::object::ID type found"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_type.exp b/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_type.exp
index 3c7d3d9faad..6cda4e0910b 100644
--- a/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_type.exp
+++ b/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_id_field_incorrect_type.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-11:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("First field of struct S must be of type iota::object::UID, Bool type found"), command: Some(0) } }
diff --git a/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_second_field_id.exp b/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_second_field_id.exp
index 4d08f97247a..caf0a7b911f 100644
--- a/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_second_field_id.exp
+++ b/crates/iota-verifier-transactional-tests/tests/struct_with_key/key_struct_second_field_id.exp
@@ -2,5 +2,5 @@ processed 1 task
task 0, lines 5-12:
//# publish
-Error: Transaction Effects Status: Iota Move Bytecode Verification Error. Please run the Iota Move Verifier for more information.
+Error: Transaction Effects Status: IOTA Move Bytecode Verification Error. Please run the IOTA Move Verifier for more information.
Execution Error: ExecutionError: ExecutionError { inner: ExecutionErrorInner { kind: IotaMoveVerificationError, source: Some("First field of struct S must be 'id', flag found"), command: Some(0) } }
diff --git a/crates/iota/genesis.md b/crates/iota/genesis.md
index f76dd67fc4b..1f4b5a91744 100644
--- a/crates/iota/genesis.md
+++ b/crates/iota/genesis.md
@@ -8,7 +8,7 @@ Each validator participating in the ceremony will need the following:
- BLS12381 Public key
- Ed25519 Public key(s)
-- Iota network address
+- IOTA network address
- p2p_address network address
- primary_address network address
diff --git a/crates/iota/src/clever_error_rendering.rs b/crates/iota/src/clever_error_rendering.rs
index 0243a51ef04..a631cc0ed42 100644
--- a/crates/iota/src/clever_error_rendering.rs
+++ b/crates/iota/src/clever_error_rendering.rs
@@ -34,7 +34,7 @@ use move_core_types::account_address::AccountAddress;
/// Clever Error encoding in the abort code.
///
/// This function is used to render Clever Errors for on-chain errors only
-/// within the Iota CLI. This function is _not_ used at all for off-chain errors
+/// within the IOTA CLI. This function is _not_ used at all for off-chain errors
/// or Move unit tests. You should only use this function within this crate.
pub(crate) async fn render_clever_error_opt(
error_string: &str,
diff --git a/crates/iota/src/client_commands.rs b/crates/iota/src/client_commands.rs
index 063a51328e9..b3bd252de87 100644
--- a/crates/iota/src/client_commands.rs
+++ b/crates/iota/src/client_commands.rs
@@ -2111,7 +2111,7 @@ impl Display for IotaClientCommandResult {
write!(writer, "{}", env.as_deref().unwrap_or("None"))?;
}
IotaClientCommandResult::NewEnv(env) => {
- writeln!(writer, "Added new Iota env [{}] to config.", env.alias())?;
+ writeln!(writer, "Added new IOTA env [{}] to config.", env.alias())?;
}
IotaClientCommandResult::Envs(envs, active) => {
let mut builder = TableBuilder::default();
diff --git a/crates/iota/src/console.rs b/crates/iota/src/console.rs
index 990ed73a30c..f40cdb7a51f 100644
--- a/crates/iota/src/console.rs
+++ b/crates/iota/src/console.rs
@@ -157,7 +157,7 @@ async fn handle_command(
result,
IotaClientCommandResult::Switch(SwitchResponse { env: Some(_), .. })
) {
- println!("Iota environment switch completed, please restart Iota console.");
+ println!("IOTA environment switch completed, please restart IOTA console.");
return Ok(true);
}
Ok(false)
diff --git a/crates/iota/src/fire_drill.rs b/crates/iota/src/fire_drill.rs
index 787ca8d05e7..eb27a382853 100644
--- a/crates/iota/src/fire_drill.rs
+++ b/crates/iota/src/fire_drill.rs
@@ -121,7 +121,7 @@ pub async fn get_gas_obj_ref(
.data;
let gas_obj = coins.iter().find(|c| c.balance >= minimal_gas_balance);
if gas_obj.is_none() {
- bail!("Validator doesn't have enough Iota coins to cover transaction fees.");
+ bail!("Validator doesn't have enough IOTA coins to cover transaction fees.");
}
Ok(gas_obj.unwrap().object_ref())
}
diff --git a/crates/iota/src/genesis_inspector.rs b/crates/iota/src/genesis_inspector.rs
index 5ebfacb50f1..dc8e049ec87 100644
--- a/crates/iota/src/genesis_inspector.rs
+++ b/crates/iota/src/genesis_inspector.rs
@@ -23,7 +23,7 @@ const STR_STAKED_IOTA: &str = "StakedIota";
const STR_PACKAGE: &str = "Package";
const STR_COIN_METADATA: &str = "CoinMetadata";
const STR_OTHER: &str = "Other";
-const STR_IOTA_DISTRIBUTION: &str = "Iota Distribution";
+const STR_IOTA_DISTRIBUTION: &str = "IOTA Distribution";
const STR_OBJECTS: &str = "Objects";
const STR_VALIDATORS: &str = "Validators";
@@ -47,10 +47,10 @@ pub(crate) fn examine_genesis_checkpoint(genesis: UnsignedGenesis) {
validator_options.extend_from_slice(&[STR_ALL, STR_EXIT]);
println!("Total Number of Validators: {}", validator_set.len());
- // Prepare Iota distribution info
+ // Prepare IOTA distribution info
let mut iota_distribution = BTreeMap::new();
let entry = iota_distribution
- .entry("Iota System".to_string())
+ .entry("IOTA System".to_string())
.or_insert_with(BTreeMap::new);
entry.insert(
"Storage Fund".to_string(),
@@ -280,7 +280,7 @@ fn examine_total_supply(
total_staked_iota / NANOS_PER_IOTA
);
if print {
- print_divider("Iota Distribution");
+ print_divider("IOTA Distribution");
}
}
@@ -307,7 +307,7 @@ fn display_validator(validator: &IotaValidatorGenesis) {
validator.staking_pool.deactivation_epoch
);
println!(
- "Staking Pool Iota Balance: {:?}",
+ "Staking Pool IOTA Balance: {:?}",
validator.staking_pool.iota_balance
);
println!(
@@ -323,7 +323,7 @@ fn display_validator(validator: &IotaValidatorGenesis) {
validator.staking_pool.pending_stake
);
println!(
- "Pending Total Iota Withdraw: {}",
+ "Pending Total IOTA Withdraw: {}",
validator.staking_pool.pending_total_iota_withdraw
);
println!(
diff --git a/crates/iota/src/iota_commands.rs b/crates/iota/src/iota_commands.rs
index ab0c9387a74..b961a74507d 100644
--- a/crates/iota/src/iota_commands.rs
+++ b/crates/iota/src/iota_commands.rs
@@ -154,7 +154,7 @@ pub enum IotaCommand {
/// description.
///
/// By default, iota start will start a local network from the genesis blob
- /// that exists in the Iota config default dir or in the config_dir that
+ /// that exists in the IOTA config default dir or in the config_dir that
/// was passed. If the default directory does not exist and the
/// config_dir is not passed, it will generate a new default directory,
/// generate the genesis blob, and start the network.
@@ -280,7 +280,7 @@ pub enum IotaCommand {
},
/// Create an IOTA Genesis Ceremony with multiple remote validators.
GenesisCeremony(Ceremony),
- /// Iota keystore tool.
+ /// IOTA keystore tool.
#[clap(name = "keytool")]
KeyTool {
#[clap(long)]
@@ -292,7 +292,7 @@ pub enum IotaCommand {
#[clap(subcommand)]
cmd: KeyToolCommand,
},
- /// Start Iota interactive console.
+ /// Start IOTA interactive console.
#[clap(name = "console")]
Console {
/// Sets the file storing the state of our user accounts (an empty one
@@ -364,7 +364,7 @@ pub enum IotaCommand {
#[clap(subcommand)]
fire_drill: FireDrill,
},
- /// Invoke Iota's move-analyzer via CLI
+ /// Invoke IOTA's move-analyzer via CLI
#[clap(name = "analyzer", hide = true)]
Analyzer,
/// Generate completion files for various shells
@@ -530,14 +530,14 @@ impl IotaCommand {
client_config,
bridge_committee_config_path,
} => {
- // Load the config of the Iota authority.
+ // Load the config of the IOTA authority.
let network_config_path = network_config
.clone()
.unwrap_or(iota_config_dir()?.join(IOTA_NETWORK_CONFIG));
let network_config: NetworkConfig = PersistedConfig::read(&network_config_path)
.map_err(|err| {
err.context(format!(
- "Cannot open Iota network config file at {:?}",
+ "Cannot open IOTA network config file at {:?}",
network_config_path
))
})?;
@@ -664,7 +664,7 @@ async fn start(
if epoch_duration_ms.is_some() && genesis_blob_exists(config_dir.clone()) && !force_regenesis {
bail!(
"epoch duration can only be set when passing the `--force-regenesis` flag, or when \
- there is no genesis configuration in the default Iota configuration folder or the given \
+ there is no genesis configuration in the default IOTA configuration folder or the given \
network.config argument.",
);
}
@@ -727,7 +727,7 @@ async fn start(
..
} = PersistedConfig::read(&network_config_path).map_err(|err| {
err.context(format!(
- "Cannot open Iota network config file at {:?}",
+ "Cannot open IOTA network config file at {:?}",
network_config_path
))
})?;
@@ -926,7 +926,7 @@ async fn genesis(
// if a directory is specified, it must exist (it
// will not be created)
Some(v) => v,
- // create default Iota config dir if not specified
+ // create default IOTA config dir if not specified
// on the command line and if it does not exist
// yet
None => {
@@ -936,11 +936,11 @@ async fn genesis(
}
};
- // if Iota config dir is not empty then either clean it
+ // if IOTA config dir is not empty then either clean it
// up (if --force/-f option was specified or report an
// error
let dir = iota_config_dir.read_dir().map_err(|err| {
- anyhow!(err).context(format!("Cannot open Iota config dir {:?}", iota_config_dir))
+ anyhow!(err).context(format!("Cannot open IOTA config dir {:?}", iota_config_dir))
})?;
let files = dir.collect::, _>>()?;
@@ -970,20 +970,20 @@ async fn genesis(
} else {
fs::remove_dir_all(iota_config_dir).map_err(|err| {
anyhow!(err).context(format!(
- "Cannot remove Iota config dir {:?}",
+ "Cannot remove IOTA config dir {:?}",
iota_config_dir
))
})?;
fs::create_dir(iota_config_dir).map_err(|err| {
anyhow!(err).context(format!(
- "Cannot create Iota config dir {:?}",
+ "Cannot create IOTA config dir {:?}",
iota_config_dir
))
})?;
}
} else if files.len() != 2 || !client_path.exists() || !keystore_path.exists() {
bail!(
- "cannot run genesis with non-empty Iota config directory {}, please use the --force/-f option to remove the existing configuration",
+ "cannot run genesis with non-empty IOTA config directory {}, please use the --force/-f option to remove the existing configuration",
iota_config_dir.to_str().unwrap()
);
}
@@ -1207,7 +1207,7 @@ async fn prompt_if_no_config(
);
} else {
print!(
- "Config file [{:?}] doesn't exist, do you want to connect to a Iota Full node server [y/N]?",
+ "Config file [{:?}] doesn't exist, do you want to connect to an IOTA Full node server [y/N]?",
wallet_conf_path
);
}
@@ -1218,7 +1218,7 @@ async fn prompt_if_no_config(
String::new()
} else {
print!(
- "Iota Full node server URL (Defaults to Iota Testnet if not specified) : "
+ "IOTA Full node server URL (Defaults to IOTA Testnet if not specified) : "
);
read_line()?
};
diff --git a/crates/iota/src/keytool.rs b/crates/iota/src/keytool.rs
index 716548db44d..13b6084b46e 100644
--- a/crates/iota/src/keytool.rs
+++ b/crates/iota/src/keytool.rs
@@ -74,8 +74,8 @@ pub enum KeyToolCommand {
/// Convert private key in Hex or Base64 to new format (Bech32
/// encoded 33 byte flag || private key starting with "iotaprivkey").
/// Hex private key format import and export are both deprecated in
- /// Iota Wallet and Iota CLI Keystore. Use `iota keytool import` if you
- /// wish to import a key to Iota Keystore.
+ /// IOTA Wallet and IOTA CLI Keystore. Use `iota keytool import` if you
+ /// wish to import a key to IOTA Keystore.
Convert { value: String },
/// Given a Base64 encoded transaction bytes, decode its components. If a
/// signature is provided, verify the signature against the transaction
@@ -117,7 +117,7 @@ pub enum KeyToolCommand {
derivation_path: Option,
word_length: Option,
},
- /// Add a new key to Iota CLI Keystore using either the input mnemonic
+ /// Add a new key to IOTA CLI Keystore using either the input mnemonic
/// phrase, a Bech32 encoded 33-byte `flag || privkey` starting with
/// "iotaprivkey" or a seed, the key scheme flag {ed25519 | secp256k1 |
/// secp256r1} and an optional derivation path, default to
@@ -136,20 +136,20 @@ pub enum KeyToolCommand {
key_scheme: SignatureScheme,
derivation_path: Option,
},
- /// Output the private key of the given key identity in Iota CLI Keystore as
+ /// Output the private key of the given key identity in IOTA CLI Keystore as
/// Bech32 encoded string starting with `iotaprivkey`.
Export {
#[clap(long)]
key_identity: KeyIdentity,
},
- /// List all keys by its Iota address, Base64 encoded public key, key scheme
+ /// List all keys by its IOTA address, Base64 encoded public key, key scheme
/// name in iota.keystore.
List {
/// Sort by alias
#[clap(long, short = 's')]
sort_by_alias: bool,
},
- /// To MultiSig Iota Address. Pass in a list of all public keys `flag || pk`
+ /// To MultiSig IOTA Address. Pass in a list of all public keys `flag || pk`
/// in Base64. See `keytool list` for example public keys.
MultiSigAddress {
#[clap(long)]
@@ -370,8 +370,8 @@ pub struct MultiSigOutput {
#[derive(Serialize)]
#[serde(rename_all = "camelCase")]
pub struct ConvertOutput {
- bech32_with_flag: String, // latest Iota Keystore and Iota Wallet import/export format
- base64_with_flag: String, // Iota Keystore storage format
+ bech32_with_flag: String, // latest IOTA Keystore and IOTA Wallet import/export format
+ base64_with_flag: String, // IOTA Keystore storage format
scheme: String,
}
@@ -395,7 +395,7 @@ pub struct SignData {
// Base64 encoded blake2b hash of the intent message, this is what the signature commits to.
digest: String,
// Base64 encoded `flag || signature || pubkey` for a complete
- // serialized Iota signature to be send for executing the transaction.
+ // serialized IOTA signature to be send for executing the transaction.
iota_signature: String,
}
diff --git a/crates/iota/src/main.rs b/crates/iota/src/main.rs
index bb33fdb8577..6634655c269 100644
--- a/crates/iota/src/main.rs
+++ b/crates/iota/src/main.rs
@@ -84,6 +84,6 @@ async fn main() {
.with_env()
.init(),
};
- debug!("Iota CLI version: {VERSION}");
+ debug!("IOTA CLI version: {VERSION}");
exit_main!(args.command.execute().await);
}
diff --git a/crates/iota/src/unit_tests/keytool_tests.rs b/crates/iota/src/unit_tests/keytool_tests.rs
index 5d56996807f..b36c1559f36 100644
--- a/crates/iota/src/unit_tests/keytool_tests.rs
+++ b/crates/iota/src/unit_tests/keytool_tests.rs
@@ -207,7 +207,7 @@ async fn test_load_keystore_err() {
#[test]
async fn test_private_keys_import_export() -> Result<(), anyhow::Error> {
// private key in Bech32, private key in Hex, private key in Base64, derived
- // Iota address in Hex
+ // IOTA address in Hex
const TEST_CASES: &[(&str, &str, &str, &str)] = &[
(
"iotaprivkey1qzwant3kaegmjy4qxex93s0jzvemekkjmyv3r2sjwgnv2y479pgsyj3mjxj",
diff --git a/crates/iota/src/validator_commands.rs b/crates/iota/src/validator_commands.rs
index fedf9aed68f..0a38394d04a 100644
--- a/crates/iota/src/validator_commands.rs
+++ b/crates/iota/src/validator_commands.rs
@@ -148,7 +148,7 @@ pub enum IotaValidatorCommand {
/// by using the `display-metadata` subcommand.
#[clap(name = "operation-cap-id", long)]
operation_cap_id: Option,
- /// The Iota Address of the validator is being reported or un-reported
+ /// The IOTA Address of the validator is being reported or un-reported
#[clap(name = "reportee-address")]
reportee_address: IotaAddress,
/// If true, undo an existing report.
@@ -562,7 +562,7 @@ impl IotaValidatorCommand {
bail!("Address {} is not in the committee", address);
}
println!(
- "Starting bridge committee registration for Iota validator: {address}, with bridge public key: {} and url: {}",
+ "Starting bridge committee registration for IOTA validator: {address}, with bridge public key: {} and url: {}",
ecdsa_keypair.public, bridge_authority_url
);
let iota_rpc_url = context.config().get_active_env().unwrap().rpc();
@@ -641,7 +641,7 @@ impl IotaValidatorCommand {
bail!("Address {} is not in the committee", address);
}
println!(
- "Updating bridge committee node URL for Iota validator: {address}, url: {}",
+ "Updating bridge committee node URL for IOTA validator: {address}, url: {}",
bridge_authority_url
);
diff --git a/crates/iota/src/zklogin_commands_util.rs b/crates/iota/src/zklogin_commands_util.rs
index 5465734e205..49a97926c4b 100644
--- a/crates/iota/src/zklogin_commands_util.rs
+++ b/crates/iota/src/zklogin_commands_util.rs
@@ -137,7 +137,7 @@ pub async fn perform_zk_login_test_tx(
.await?;
if response.data.len() != 2 {
- panic!("Faucet did not work correctly and the provided Iota address has no coins")
+ panic!("Faucet did not work correctly and the provided IOTA address has no coins")
}
let transfer_coin = response.data[0].coin_object_id;
diff --git a/crates/shared-crypto/src/intent.rs b/crates/shared-crypto/src/intent.rs
index 9bbd9234232..91ca544726b 100644
--- a/crates/shared-crypto/src/intent.rs
+++ b/crates/shared-crypto/src/intent.rs
@@ -28,7 +28,7 @@ impl TryFrom for IntentVersion {
}
/// This enums specifies the application ID. Two intents in two different
-/// applications (i.e., Iota, Ethereum etc) should never collide, so
+/// applications (i.e., IOTA, Ethereum etc) should never collide, so
/// that even when a signing key is reused, nobody can take a signature
/// designated for app_1 and present it as a valid signature for an (any) intent
/// in app_2.
@@ -152,7 +152,7 @@ impl Intent {
}
/// Intent Message is a wrapper around a message with its intent. The message
-/// can be any type that implements [trait Serialize]. *ALL* signatures in Iota
+/// can be any type that implements [trait Serialize]. *ALL* signatures in IOTA
/// must commits to the intent message, not the message itself. This guarantees
/// any intent message signed in the system cannot collide with another since
/// they are domain separated by intent.
@@ -186,7 +186,7 @@ pub(crate) mod private {
impl SealedIntent for IntentMessage {}
}
-/// A 1-byte domain separator for hashing Object ID in Iota. It is starting from
+/// A 1-byte domain separator for hashing Object ID in IOTA. It is starting from
/// 0xf0 to ensure no hashing collision for any ObjectID vs IotaAddress which is
/// derived as the hash of `flag || pubkey`. See
/// `iota_types::crypto::SignatureScheme::flag()`.
diff --git a/crates/simulacrum/src/lib.rs b/crates/simulacrum/src/lib.rs
index 2165600de93..efeef0da5e4 100644
--- a/crates/simulacrum/src/lib.rs
+++ b/crates/simulacrum/src/lib.rs
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-//! A `Simulacrum` of Iota.
+//! A `Simulacrum` of IOTA.
//!
//! The word simulacrum is latin for "likeness, semblance", it is also a spell
//! in D&D which creates a copy of a creature which then follows the player's
@@ -55,9 +55,9 @@ use rand::rngs::OsRng;
pub use self::store::{SimulatorStore, in_mem_store::InMemoryStore};
use self::{epoch_state::EpochState, store::in_mem_store::KeyStore};
-/// A `Simulacrum` of Iota.
+/// A `Simulacrum` of IOTA.
///
-/// This type represents a simulated instantiation of a Iota blockchain that
+/// This type represents a simulated instantiation of an IOTA blockchain that
/// needs to be driven manually, that is time doesn't advance and checkpoints
/// are not formed unless explicitly requested.
///
diff --git a/crates/typed-store/src/rocks/mod.rs b/crates/typed-store/src/rocks/mod.rs
index 3787e540cfd..69bce623695 100644
--- a/crates/typed-store/src/rocks/mod.rs
+++ b/crates/typed-store/src/rocks/mod.rs
@@ -2526,7 +2526,7 @@ pub fn default_db_options() -> DBOptions {
opt.set_bottommost_compression_type(rocksdb::DBCompressionType::Zstd);
opt.set_bottommost_zstd_max_train_bytes(1024 * 1024, true);
- // Iota uses multiple RocksDB in a node, so total sizes of write buffers and WAL
+ // IOTA uses multiple RocksDB in a node, so total sizes of write buffers and WAL
// can be higher than the limits below.
//
// RocksDB also exposes the option to configure total write buffer size across
diff --git a/dapps/kiosk/src/components/Kiosk/FindKiosk.tsx b/dapps/kiosk/src/components/Kiosk/FindKiosk.tsx
index fe5d516dd69..9469d3519ce 100644
--- a/dapps/kiosk/src/components/Kiosk/FindKiosk.tsx
+++ b/dapps/kiosk/src/components/Kiosk/FindKiosk.tsx
@@ -44,7 +44,7 @@ export default function FindKiosk() {
className="bg-gray-100 border lg:min-w-[600px] text-gray-900 placeholder:text-gray-500 text-sm rounded rounded-r-none
focus:ring-transparent
focus:border-primary block w-full p-2.5 outline-primary"
- placeholder="Enter an address or a IOTA Kiosk ID to search for a kiosk..."
+ placeholder="Enter an address or an IOTA Kiosk ID to search for a kiosk..."
required
/>
diff --git a/dapps/kiosk/src/components/Kiosk/KioskCreation.tsx b/dapps/kiosk/src/components/Kiosk/KioskCreation.tsx
index f90b06c5d02..dcafab02a49 100644
--- a/dapps/kiosk/src/components/Kiosk/KioskCreation.tsx
+++ b/dapps/kiosk/src/components/Kiosk/KioskCreation.tsx
@@ -18,7 +18,7 @@ export function KioskCreation({ onCreate }: { onCreate: () => void }) {
return (
-
Create a IOTA Kiosk
+
Create an IOTA Kiosk
There’s no kiosk for your address yet. Create a kiosk to store
your digital assets and list them for sale on the IOTA network. Anyone can view
diff --git a/deny.toml b/deny.toml
index 04e8c2cb6f6..0a25c9f4e5c 100644
--- a/deny.toml
+++ b/deny.toml
@@ -42,7 +42,7 @@ yanked = "warn"
# A list of advisory IDs to ignore. Note that ignored advisories will still
# output a note when they are encountered.
ignore = [
- # we don't do RSA signing on Iota (only verifying for zklogin)
+ # we don't do RSA signing on IOTA (only verifying for zklogin)
"RUSTSEC-2023-0071",
# Cannot remove `proc-macro-error` until we can update `tabled`
"RUSTSEC-2024-0370",
diff --git a/docker/deterministic-canary/Dockerfile b/docker/deterministic-canary/Dockerfile
index d11fe698ef6..517f952272c 100644
--- a/docker/deterministic-canary/Dockerfile
+++ b/docker/deterministic-canary/Dockerfile
@@ -51,7 +51,7 @@ COPY --from=llvm . /
COPY --from=make . /
COPY --from=musl . /
-# Iota build deps
+# IOTA build deps
COPY --from=clang . /
COPY --from=linux-headers . /
diff --git a/docker/grafana-local/dashboards/validator-dashboard.json b/docker/grafana-local/dashboards/validator-dashboard.json
index 0e79a79ba98..520c4d374b9 100644
--- a/docker/grafana-local/dashboards/validator-dashboard.json
+++ b/docker/grafana-local/dashboards/validator-dashboard.json
@@ -3534,7 +3534,7 @@
},
"timepicker": {},
"timezone": "",
- "title": "Iota Validators - low level metrics",
+ "title": "IOTA Validators - low level metrics",
"uid": "BpwTlGCnx",
"version": 4,
"weekStart": ""
diff --git a/docker/iota-network/README.md b/docker/iota-network/README.md
index e97d7bedb59..0cccfdf8cb6 100644
--- a/docker/iota-network/README.md
+++ b/docker/iota-network/README.md
@@ -1,4 +1,4 @@
-# Iota Network Docker Compose
+# IOTA Network Docker Compose
This was tested using MacOS 14.3.1, Docker Compose: v2.13.0.
diff --git a/docker/iota-node-deterministic/Dockerfile b/docker/iota-node-deterministic/Dockerfile
index ec48977018e..60ed6a8cc43 100644
--- a/docker/iota-node-deterministic/Dockerfile
+++ b/docker/iota-node-deterministic/Dockerfile
@@ -51,7 +51,7 @@ COPY --from=llvm . /
COPY --from=make . /
COPY --from=musl . /
-# Iota build deps
+# IOTA build deps
COPY --from=clang . /
COPY --from=linux-headers . /
diff --git a/docker/pg-services-local/docker-compose.yaml b/docker/pg-services-local/docker-compose.yaml
index 3c8b78ad929..06d1301780d 100644
--- a/docker/pg-services-local/docker-compose.yaml
+++ b/docker/pg-services-local/docker-compose.yaml
@@ -143,7 +143,7 @@ services:
- --prom-host=0.0.0.0
- --prom-port=9181
- --node-rpc-url=http://local-network:9000
- - --ide-title="Iota GraphQL Service"
+ - --ide-title="IOTA GraphQL Service"
ports:
- "127.0.0.1:8000:8000/tcp"
- "127.0.0.1:9183:9181/tcp"
diff --git a/docs/README.md b/docs/README.md
index 7bf8398b94f..5b0e2025fe8 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -30,7 +30,7 @@ IOTA Foundation is not able to provide support for building the documentation si
## Pull requests
-IOTA uses Vercel to host its documentation site. Vercel builds a preview of the documentation for every pull request submitted to the Iota repo. You can find a link to this preview in the PR comment section from the Vercel bot. Click the **Visit Preview** link for the **iota-core** project to verify your changes behave as you expect.
+IOTA uses Vercel to host its documentation site. Vercel builds a preview of the documentation for every pull request submitted to the IOTA repo. You can find a link to this preview in the PR comment section from the Vercel bot. Click the **Visit Preview** link for the **iota-core** project to verify your changes behave as you expect.
If you'd like to view the Vercel preview before your changes are ready for review, then [mark your PR as a draft](https://github.blog/2019-02-14-introducing-draft-pull-requests/).
@@ -45,4 +45,4 @@ IOTA is for the community. Contribute for the benefit of all.
## License
-The Iota Documentation is distributed under the [LICENSE](CC BY 4.0 license).
+The IOTA Documentation is distributed under the [LICENSE](CC BY 4.0 license).
diff --git a/docs/content/_snippets/initialize-iota-client-cli.mdx b/docs/content/_snippets/initialize-iota-client-cli.mdx
index 7a0375b7eef..c1f8208dca2 100644
--- a/docs/content/_snippets/initialize-iota-client-cli.mdx
+++ b/docs/content/_snippets/initialize-iota-client-cli.mdx
@@ -7,7 +7,7 @@ See [Publish a Package](../developer/getting-started/publish.mdx) for a more det
Before publishing your code, you must first initialize the IOTA Client CLI, if you haven't already. To do so, in a terminal or console at the root directory of the project enter `iota client`. If you receive the following response, complete the remaining instructions:
```
-Config file ["/.iota/iota_config/client.yaml"] doesn't exist, do you want to connect to a IOTA full node server [y/N]?
+Config file ["/.iota/iota_config/client.yaml"] doesn't exist, do you want to connect to an IOTA full node server [y/N]?
```
Enter `y` to proceed. You receive the following response:
@@ -22,5 +22,5 @@ Leave this blank (press Enter). You receive the following response:
Select key scheme to generate keypair (0 for ed25519, 1 for secp256k1, 2: for secp256r1):
```
-Select `0`. Now you should have a IOTA address set up.
+Select `0`. Now you should have an IOTA address set up.
diff --git a/docs/content/developer/advanced/asset-tokenization.mdx b/docs/content/developer/advanced/asset-tokenization.mdx
index bc897ad67f9..b4098c60e2c 100644
--- a/docs/content/developer/advanced/asset-tokenization.mdx
+++ b/docs/content/developer/advanced/asset-tokenization.mdx
@@ -952,7 +952,7 @@ In a terminal or console within the project's setup directory, utilize the follo
After executing the command, the console displays the effects of the transaction.
- By searching the transaction digest on a IOTA network explorer, you can locate the created objects. Subsequently, select and save the `TransferPolicy ID` and the `ProtectedTP ID` from these objects into the respective fields within your .env file.
+ By searching the transaction digest on an IOTA network explorer, you can locate the created objects. Subsequently, select and save the `TransferPolicy ID` and the `ProtectedTP ID` from these objects into the respective fields within your .env file.
- **Add Rules**
diff --git a/docs/content/developer/advanced/create-review-rating-dao-with-multisig.mdx b/docs/content/developer/advanced/create-review-rating-dao-with-multisig.mdx
index 5d87995c99b..71e976dc208 100644
--- a/docs/content/developer/advanced/create-review-rating-dao-with-multisig.mdx
+++ b/docs/content/developer/advanced/create-review-rating-dao-with-multisig.mdx
@@ -414,7 +414,7 @@ The deployment of the contract is done by the admin, which is a [multi-sig](/dev
You need to create a `.env` file that contains important environment variables required for the deployment. Here's an example of what the .env file should look like:
```env
-# Add Iota network url
+# Add IOTA network url
IOTA_NETWORK="iota-network-url"
# Add faucet link
diff --git a/docs/content/developer/cryptography/checkpoint-verification.mdx b/docs/content/developer/cryptography/checkpoint-verification.mdx
index a1689035dcf..f893349f684 100644
--- a/docs/content/developer/cryptography/checkpoint-verification.mdx
+++ b/docs/content/developer/cryptography/checkpoint-verification.mdx
@@ -29,7 +29,7 @@ Checkpoint verification requires two interdependent pieces:
1. By validating checkpoints, the client can determine the make-up of the committee, because the final checkpoint of each epoch contains the validator committee (including the public keys) of the next epoch.
-These pieces seem to create a circular dependency issue. The client needs to know the committee to verify checkpoints, which in turn allows it to learn what the committee is for each epoch. To solve this problem, the process is bootstrapped by starting from the genesis checkpoint, which is the earliest checkpoint in a IOTA network. The genesis checkpoint contains the initial validator committee, which allows a client to verify all checkpoints in the history by using the following process:
+These pieces seem to create a circular dependency issue. The client needs to know the committee to verify checkpoints, which in turn allows it to learn what the committee is for each epoch. To solve this problem, the process is bootstrapped by starting from the genesis checkpoint, which is the earliest checkpoint in an IOTA network. The genesis checkpoint contains the initial validator committee, which allows a client to verify all checkpoints in the history by using the following process:
1. The client obtains the genesis checkpoint from some trusted source.
1. The client loads the initial committee from the genesis checkpoint.
diff --git a/docs/content/developer/cryptography/transaction-auth.mdx b/docs/content/developer/cryptography/transaction-auth.mdx
index 6cf3c7478ad..818c31abacb 100644
--- a/docs/content/developer/cryptography/transaction-auth.mdx
+++ b/docs/content/developer/cryptography/transaction-auth.mdx
@@ -25,7 +25,7 @@ Go to [Multisig](transaction-auth/multisig.mdx).
## Offline Signing
-IOTA supports offline signing, which is signing transactions using a device not connected to a IOTA network, or in a wallet implemented in a different programming language without relying on the IOTA key store.
+IOTA supports offline signing, which is signing transactions using a device not connected to an IOTA network, or in a wallet implemented in a different programming language without relying on the IOTA key store.
Go to [Offline Signing](transaction-auth/offline-signing.mdx).
diff --git a/docs/content/developer/cryptography/transaction-auth/multisig.mdx b/docs/content/developer/cryptography/transaction-auth/multisig.mdx
index eb27374755a..031f6b5242e 100644
--- a/docs/content/developer/cryptography/transaction-auth/multisig.mdx
+++ b/docs/content/developer/cryptography/transaction-auth/multisig.mdx
@@ -36,7 +36,7 @@ The following steps demonstrate how to create a multisig transaction and then su
### Step 1: Create keys
-Use the following command to generate a IOTA address and key for each supported key scheme and add it to the `iota.keystore`, then list the keys.
+Use the following command to generate an IOTA address and key for each supported key scheme and add it to the `iota.keystore`, then list the keys.
Use `iota client` to create IOTA addresses of different key schemes.
diff --git a/docs/content/developer/cryptography/transaction-auth/offline-signing.mdx b/docs/content/developer/cryptography/transaction-auth/offline-signing.mdx
index fc3058f20d1..6510d3bdcc7 100644
--- a/docs/content/developer/cryptography/transaction-auth/offline-signing.mdx
+++ b/docs/content/developer/cryptography/transaction-auth/offline-signing.mdx
@@ -5,7 +5,7 @@ title: Offline Signing
import Quiz from '@site/src/components/Quiz';
import questions from '/json/developer/cryptography/offline-signing.json';
-IOTA supports offline signing, which is signing transactions using a device not connected to a IOTA network, or in a wallet implemented in a different programming language without relying on the IOTA key store. The steps to implement offline signing include:
+IOTA supports offline signing, which is signing transactions using a device not connected to an IOTA network, or in a wallet implemented in a different programming language without relying on the IOTA key store. The steps to implement offline signing include:
1. Serialize the data for signing.
1. Sign the serialized data. Put the serialized data in a location to sign (such as the wallet of your choice, or tools in other programming languages) and to produce a signature with the corresponding public key.
diff --git a/docs/content/developer/exchange-integration/exchange-integration.mdx b/docs/content/developer/exchange-integration/exchange-integration.mdx
index 29d50b7477b..c7a43faf988 100644
--- a/docs/content/developer/exchange-integration/exchange-integration.mdx
+++ b/docs/content/developer/exchange-integration/exchange-integration.mdx
@@ -8,11 +8,11 @@ import questions from '/json/developer/exchange-intergration/exchange-integratio
This topic describes how to integrate IOTA, the token native to the IOTA network, into a cryptocurrency exchange. The specific requirements and processes to implement an integration vary between exchanges. Rather than provide a step-by-step guide, this topic provides information about the primary tasks necessary to complete an integration. After the guidance about how to configure an integration, you can also find information and code samples related to staking on the IOTA network.
-## Requirements to configure a IOTA integration
+## Requirements to configure an IOTA integration
-The requirements to configure a IOTA integration include:
- - A IOTA full node. You can operate your own IOTA full node or use a full node from a node operator.
- - Suggested hardware requirements to run a IOTA full node:
+The requirements to configure an IOTA integration include:
+ - An IOTA full node. You can operate your own IOTA full node or use a full node from a node operator.
+ - Suggested hardware requirements to run an IOTA full node:
- CPU: 8 physical cores / 16 vCPUs
- RAM: 128 GB
- Storage (SSD): 4 TB NVMe drive
@@ -23,7 +23,7 @@ For best results, run IOTA full nodes on Linux. IOTA supports the Ubuntu and Deb
You can develop and test your integration using a local development server. It will spin up a local network with some test nodes, an indexer, and a faucet. You can find detailed instructions in the [local development guide](../getting-started/local-network.mdx).
-## Configure a IOTA Full node
+## Configure an IOTA Full node
You can set up and configure a [IOTA full node](../../operator/iota-full-node/overview.mdx) using Docker or directly from source code in the IOTA GitHub repository.
@@ -184,9 +184,9 @@ IOTA Checkpoint API operations include:
To transfer a specific amount of IOTA between addresses, you need an IOTA token object with that specific value. In IOTA, everything is an object, including IOTA tokens. The amount of IOTA in each IOTA token object varies. For example, an address could own 3 IOTA tokens with different values: one of 0.1 IOTA, a second of 1.0 IOTA, and a third with 0.005 IOTA. The total balance for the address equals the sum of the values of the individual IOTA token objects, in this case, 1.105 IOTA.
-You can merge and split IOTA token objects to create token objects with specific values. To create a IOTA token worth .6 IOTA, split the token worth 1 IOTA into two token objects worth .6 IOTA and .4 IOTA.
+You can merge and split IOTA token objects to create token objects with specific values. To create an IOTA token worth .6 IOTA, split the token worth 1 IOTA into two token objects worth .6 IOTA and .4 IOTA.
-To transfer a specific amount of IOTA, you need a IOTA token worth that specific amount. To get a IOTA token with that specific value, you might need to split or merge existing IOTA tokens. IOTA supports several methods to accomplish this, including some that do not require you to manually split or merge coins.
+To transfer a specific amount of IOTA, you need an IOTA token worth that specific amount. To get an IOTA token with that specific value, you might need to split or merge existing IOTA tokens. IOTA supports several methods to accomplish this, including some that do not require you to manually split or merge coins.
Keep in mind that to execute a transaction, including a normal transfer, you need to provide some IOTA for gas as well. This can not be the same IOTA object as the one you are trying to transfer. The [SDKs](../../references/iota-sdks.mdx) can automatically find another owned IOTA Coin object to use for gas if you don't manually select one. If you only have a single IOTA coin object, you might need to split some off first to have an object to transfer and an object to pay for gas (these can not be the same).
@@ -218,7 +218,7 @@ IOTA supports the following API operations related to transferring IOTA between
The benefits of this method include: no gas fees for merging or splitting tokens, and the abstracted token merge and split. The `unsafe_payIota` operation is a native function, so the merge and split operations are not considered IOTA transactions. The gas fees for them match typical transactions on IOTA. You can use this operation to split coins in your own address by setting the recipient as your own address. Note that the total value of the input coins must be greater than the total value of the amounts to send.
- [unsafe_pay](/iota-api-ref#unsafe_pay)
- This method is similar to `unsafe_payIota`, but it accepts any kind of coin or token instead of only IOTA. You must include a IOTA gas token, and all of the coins or tokens must be the same type.
+ This method is similar to `unsafe_payIota`, but it accepts any kind of coin or token instead of only IOTA. You must include an IOTA gas token, and all of the coins or tokens must be the same type.
- [unsafe_transferIota](/iota-api-ref#unsafe_transferiota)
This method accepts only one IOTA token object and an amount to send to the recipient. It uses the same token for gas fees, so the amount to transfer must be strictly less than the value of the IOTA token used.
diff --git a/docs/content/developer/getting-started/coffee-example.mdx b/docs/content/developer/getting-started/coffee-example.mdx
index f5c5980e71f..488806c6525 100644
--- a/docs/content/developer/getting-started/coffee-example.mdx
+++ b/docs/content/developer/getting-started/coffee-example.mdx
@@ -23,7 +23,7 @@ Welcome to this beginner-friendly tutorial on [Move](../iota-101/move-overview/m
- Basic understanding of blockchain concepts like [tokens](../../references/framework/iota-framework/token.mdx) and [transactions](https://www.scalingparrots.com/en/what-is-a-blockchain-transaction/).
- Basic understanding of the [Move](../iota-101/move-overview/move-overview.mdx)
-- [Install Iota CLI](install-iota.mdx)
+- [Install IOTA CLI](install-iota.mdx)
## 1. Create an IOTA Move Package
diff --git a/docs/content/developer/getting-started/connect.mdx b/docs/content/developer/getting-started/connect.mdx
index 5404cbe59df..3a3837ef8c7 100644
--- a/docs/content/developer/getting-started/connect.mdx
+++ b/docs/content/developer/getting-started/connect.mdx
@@ -67,7 +67,7 @@ If this is the first time you run the command, you will be prompted to configure
#### 1. Create `client.yaml`
```
-Config file ["/.iota/iota_config/client.yaml"] doesn't exist, do you want to connect to a IOTA Full node server [y/N]?
+Config file ["/.iota/iota_config/client.yaml"] doesn't exist, do you want to connect to an IOTA Full node server [y/N]?
```
Enter `y` to proceed. You receive the following response:
diff --git a/docs/content/developer/iota-101/create-coin/migrate-to-coin-manager.mdx b/docs/content/developer/iota-101/create-coin/migrate-to-coin-manager.mdx
index 58e8c33b70a..1c87074d28e 100644
--- a/docs/content/developer/iota-101/create-coin/migrate-to-coin-manager.mdx
+++ b/docs/content/developer/iota-101/create-coin/migrate-to-coin-manager.mdx
@@ -9,7 +9,7 @@ This article will show how an existing `Coin` object can be migrated to [`CoinMa
### Pre-requisites
-- [Installed Iota CLI](../../getting-started/install-iota.mdx)
+- [Installed IOTA CLI](../../getting-started/install-iota.mdx)
- [Created an address and received Testnet funds](../../getting-started/get-coins.mdx)
### 1. Create a Simple Coin
@@ -204,7 +204,7 @@ fun init(witness: EXCLUSIVE_COIN, ctx: &mut TxContext) {
However, since you are migrating from a `Coin`, you will use another constructor for `CoinManager`: [`CoinManager::new_with_immutable_metadata(cap,meta,ctx)`](../../../references/framework/iota-framework/coin_manager.mdx#0x2_coin_manager_new_with_immutable_metadata) if the metadata is already frozen, and [`CoinManager::new(cap,meta,ctx)`](../../../references/framework/iota-framework/coin_manager.mdx#0x2_coin_manager_new) if the metadata is mutable.
-In that case, `init` would have to take two extra parameters: the [`Coin`'s `CoinMetadata`](../../../references/framework/iota-framework/coin.mdx#0x2_coin_CoinMetadata) object and the [`TreasuryCap`](../../../references/framework/iota-framework/coin.mdx#resource-treasurycap) object. Iota's Move only allows `TxContext` and an optional Witness. There is no means to pass in the extra argument.
+In that case, `init` would have to take two extra parameters: the [`Coin`'s `CoinMetadata`](../../../references/framework/iota-framework/coin.mdx#0x2_coin_CoinMetadata) object and the [`TreasuryCap`](../../../references/framework/iota-framework/coin.mdx#resource-treasurycap) object. IOTA's Move only allows `TxContext` and an optional Witness. There is no means to pass in the extra argument.
You can use the [`One Time Witness Pattern`](../../iota-101/move-overview/one-time-witness.mdx) to resolve this.
diff --git a/docs/content/developer/standards/kiosk-apps.mdx b/docs/content/developer/standards/kiosk-apps.mdx
index cb88f6eab24..de64737eaa9 100644
--- a/docs/content/developer/standards/kiosk-apps.mdx
+++ b/docs/content/developer/standards/kiosk-apps.mdx
@@ -85,7 +85,7 @@ module example::my_extension {
## App lifecycle
-These are the key points in the lifecycle of a IOTA Kiosk app:
+These are the key points in the lifecycle of an IOTA Kiosk app:
- You can only install an app with an explicit call in the `kiosk_extension` module.
- A kiosk owner can revoke permissions of an app at any time by calling the `disable` function.
diff --git a/docs/content/developer/standards/kiosk.mdx b/docs/content/developer/standards/kiosk.mdx
index 4d5630e6218..7e7856f6bc6 100644
--- a/docs/content/developer/standards/kiosk.mdx
+++ b/docs/content/developer/standards/kiosk.mdx
@@ -126,7 +126,7 @@ iota client call \
For more advanced use cases, when you want to choose the storage model or perform an action right away, you can use the programmable transaction block (PTB) friendly function `kiosk::new`.
Kiosk is designed to be shared. If you choose a different storage model, such as owned, your kiosk might not function as intended or not be accessible to other users. You can make sure your Kiosk works by testing it on IOTA Testnet.
-### Create an Iota Kiosk With Advanced Options Using Programmable Transaction Blocks
+### Create an IOTA Kiosk With Advanced Options Using Programmable Transaction Blocks
```javascript
let tx = new Transaction();
diff --git a/docs/content/developer/stardust/claiming.mdx b/docs/content/developer/stardust/claiming.mdx
index 471298bb3e1..817d2640612 100644
--- a/docs/content/developer/stardust/claiming.mdx
+++ b/docs/content/developer/stardust/claiming.mdx
@@ -44,10 +44,10 @@ Go to [Foundry Output](claiming/foundry.mdx).
Go to [Output Unlockable by an Alias/Nft Address](claiming/address-unlock-condition.mdx).
-## Sponsoring Your Iota Claiming
+## Sponsoring Your IOTA Claiming
-If some assets are owned by an Iota address that holds no IOTA tokens (needed to pay for gas),
+If some assets are owned by an IOTA address that holds no IOTA tokens (needed to pay for gas),
the claiming process can benefit from self-sponsorship.
-This means that an address owning IOTA tokens can be used by the same user to sponsor a transaction claiming Iota assets.
+This means that an address owning IOTA tokens can be used by the same user to sponsor a transaction claiming IOTA assets.
-Go to [Self-sponsor Iota Claims](claiming/self-sponsor.mdx).
+Go to [Self-sponsor IOTA Claims](claiming/self-sponsor.mdx).
diff --git a/docs/content/developer/stardust/claiming/self-sponsor.mdx b/docs/content/developer/stardust/claiming/self-sponsor.mdx
index 2d473fb1141..f074881a53b 100644
--- a/docs/content/developer/stardust/claiming/self-sponsor.mdx
+++ b/docs/content/developer/stardust/claiming/self-sponsor.mdx
@@ -1,19 +1,19 @@
---
-description: A guide to claiming Iota assets using self-sponsorship when the address lacks IOTA coins for transaction fees.
+description: A guide to claiming IOTA assets using self-sponsorship when the address lacks IOTA coins for transaction fees.
---
import MigrationWarning from '../../../_snippets/migration-warning.mdx';
-# Self-Sponsoring Iota Assets Claims
+# Self-Sponsoring IOTA Assets Claims
-If you own Iota assets but don't have any IOTA coins to cover transaction fees,
+If you own IOTA assets but don't have any IOTA coins to cover transaction fees,
self-sponsorship can help you claim those assets.
In this process, a sponsor (an IOTA address) pays the transaction gas fees for another address (the user).
When claiming assets, a sponsor can cover the gas fees required for the transaction.
-## Claim an Iota Basic Output with Self-Sponsorship
+## Claim an IOTA Basic Output with Self-Sponsorship
### 1. Identify the Self-Sponsoring Address
@@ -37,7 +37,7 @@ Use the IOTA `coin_type` to derive the sponsor and sender addresses.
### 2. Create the PTB for Claiming
Next, create a [Programmable Transaction Block (PTB)](../../iota-101/transactions/ptb/building-programmable-transaction-blocks-ts-sdk.mdx)
-to claim a `BasicOutput` owned by the derived Iota address.
+to claim a `BasicOutput` owned by the derived IOTA address.
This process is similar to the one outlined in the [Basic Output](basic.mdx) guide.
diff --git a/docs/content/iota-identity/explanations/decentralized-identifiers.mdx b/docs/content/iota-identity/explanations/decentralized-identifiers.mdx
index 30e7b38f7db..e9cdaac7ac7 100644
--- a/docs/content/iota-identity/explanations/decentralized-identifiers.mdx
+++ b/docs/content/iota-identity/explanations/decentralized-identifiers.mdx
@@ -109,7 +109,7 @@ Instead, they can verify the issuer's signature by checking the issuer's DID Doc
This puts Holders back in control over their own data,
while making the data much more trustworthy as it has become verifiable.
-## Why Use Iota Identity Over Other Implementations?
+## Why Use IOTA Identity Over Other Implementations?
IOTA Identity is a framework to implement Self-Sovereign Identities on IOTA.
Inherently, IOTA provides some unique features that have a major impact on the usability of the framework.
diff --git a/docs/content/iota-identity/how-tos/decentralized-identifiers/create.mdx b/docs/content/iota-identity/how-tos/decentralized-identifiers/create.mdx
index 11333042bb4..31d564cb870 100644
--- a/docs/content/iota-identity/how-tos/decentralized-identifiers/create.mdx
+++ b/docs/content/iota-identity/how-tos/decentralized-identifiers/create.mdx
@@ -16,7 +16,7 @@ This identity consists of many parts that have different functions.
:::note DID method Specification
-Note that the Iota Identity Framework follows [IOTA DID Method Specification](../../../references/iota-identity/iota-did-method-spec.mdx).
+Note that the IOTA Identity Framework follows [IOTA DID Method Specification](../../../references/iota-identity/iota-did-method-spec.mdx).
:::
diff --git a/docs/content/references/cli/cheatsheet.mdx b/docs/content/references/cli/cheatsheet.mdx
index c8722bb12ea..852790b6955 100644
--- a/docs/content/references/cli/cheatsheet.mdx
+++ b/docs/content/references/cli/cheatsheet.mdx
@@ -71,15 +71,15 @@ The cheat sheet highlights common IOTA CLI commands.
`iota client faucet`
-
Get a IOTA coin from the faucet associated with the active network
+
Get an IOTA coin from the faucet associated with the active network
`iota client faucet --address ADDRESS`
-
Get a IOTA coin for the address (accepts also an alias)
+
Get an IOTA coin for the address (accepts also an alias)
`iota client faucet --url CUSTOM_FAUCET_URL`
-
Get a IOTA coin from custom faucet
+
Get an IOTA coin from custom faucet
`iota client gas`
diff --git a/docs/content/references/cli/client.mdx b/docs/content/references/cli/client.mdx
index 0ede2dd071b..ae33ea7da32 100644
--- a/docs/content/references/cli/client.mdx
+++ b/docs/content/references/cli/client.mdx
@@ -106,14 +106,14 @@ If you run `iota client envs` after this command, you see the asterisk in the `a
### Get current active address
-Use the `iota client active-address` command to reveal the current address. The CLI uses the current active address to execute address-specific CLI commands (like `iota client objects`) when you don't provide them with a IOTA address value.
+Use the `iota client active-address` command to reveal the current address. The CLI uses the current active address to execute address-specific CLI commands (like `iota client objects`) when you don't provide them with an IOTA address value.
```shell
iota client active-address
0x514692f08249c3e9951234ce29074695840422564bff85e424b56de462913e0d
```
-### Request a IOTA coin from faucet
+### Request an IOTA coin from faucet
If you use one of the standard public RPCs (for example, `api.testnet.iota.cafe:443`), you can use the `faucet` command to request gas coins. If you use a custom faucet service, then pass in the URL to the faucet using the `--url` option.
@@ -124,7 +124,7 @@ Request successful. It can take up to 1 minute to get the coin. Run iota client
### Get objects owned by an address
-Use `iota client objects` to list summary information about the objects the current active address owns. You can provide a IOTA address value to the command to list objects for a particular address. This example lists objects for the current active address.
+Use `iota client objects` to list summary information about the objects the current active address owns. You can provide an IOTA address value to the command to list objects for a particular address. This example lists objects for the current active address.
```
$ iota client objects 0x36df11369cf00ecf0be68d6ba965b0abe2e883bc5245911e3a29ebfa0aaf6b69
@@ -204,7 +204,7 @@ In this example, let's see how to transfer IOTA or transfer an object from one a
The `pay` command has two related commands: `pay-iota`, `pay-all-iota`.
The differences between these commands are:
-- commands that end in `-iota` deal with Iota's native coin, and they use the input coints to pay for gas and for transferring IOTA or the object.
+- commands that end in `-iota` deal with IOTA's native coin, and they use the input coints to pay for gas and for transferring IOTA or the object.
- `pay-` commands typically deal with coins and handle (coin merging)[../../developer/iota-101/transactions/ptb/optimizing-gas-with-coin-merging.mdx] for you, whereas `transfer` commands can handle the transfer of any object that has public transfer, meaning any object that has the `store` ability.
- `pay` commands allow you to send coins to multiple recipients, whereas `transfer` commands only accept one recipient.
- `pay-all-iota` is a special case of `pay-iota` that offers a way to transfer the entire balance after smashing.
diff --git a/docs/content/references/cli/keytool.mdx b/docs/content/references/cli/keytool.mdx
index 8b59b0f9e8c..209091caf38 100644
--- a/docs/content/references/cli/keytool.mdx
+++ b/docs/content/references/cli/keytool.mdx
@@ -17,19 +17,19 @@ Usage: iota keytool [OPTIONS]
Commands:
update-alias Update an old alias to a new one. If a new alias is not provided, a random one will be generated
convert Convert private key in Hex or Base64 to new format (Bech32 encoded 33 byte flag || private key starting with "iotaprivkey"). Hex private key format import and
- export are both deprecated in Iota Wallet and Iota CLI Keystore. Use `iota keytool import` if you wish to import a key to Iota Keystore
+ export are both deprecated in IOTA Wallet and IOTA CLI Keystore. Use `iota keytool import` if you wish to import a key to IOTA Keystore
decode-or-verify-tx Given a Base64 encoded transaction bytes, decode its components. If a signature is provided, verify the signature against the transaction and output the result
decode-multi-sig Given a Base64 encoded MultiSig signature, decode its components. If tx_bytes is passed in, verify the multisig
generate Generate a new keypair with key scheme flag {ed25519 | secp256k1 | secp256r1} with optional derivation path, default to m/44'/4218'/0'/0'/0' for ed25519 or
m/54'/4218'/0'/0/0 for secp256k1 or m/74'/4218'/0'/0/0 for secp256r1. Word length can be { word12 | word15 | word18 | word21 | word24} default to word12 if not
specified
- import Add a new key to Iota CLI Keystore using either the input mnemonic phrase or a Bech32 encoded 33-byte `flag || privkey` starting with "iotaprivkey", the key
+ import Add a new key to IOTA CLI Keystore using either the input mnemonic phrase or a Bech32 encoded 33-byte `flag || privkey` starting with "iotaprivkey", the key
scheme flag {ed25519 | secp256k1 | secp256r1} and an optional derivation path, default to m/44'/4218'/0'/0'/0' for ed25519 or m/54'/4218'/0'/0/0 for secp256k1
or m/74'/4218'/0'/0/0 for secp256r1. Supports mnemonic phrase of word length 12, 15, 18, 21, 24. Set an alias for the key with the --alias flag. If no alias is
provided, the tool will automatically generate one
- export Output the private key of the given key identity in Iota CLI Keystore as Bech32 encoded string starting with `iotaprivkey`
- list List all keys by its Iota address, Base64 encoded public key, key scheme name in iota.keystore
- multi-sig-address To MultiSig Iota Address. Pass in a list of all public keys `flag || pk` in Base64. See `keytool list` for example public keys
+ export Output the private key of the given key identity in IOTA CLI Keystore as Bech32 encoded string starting with `iotaprivkey`
+ list List all keys by its IOTA address, Base64 encoded public key, key scheme name in iota.keystore
+ multi-sig-address To MultiSig IOTA Address. Pass in a list of all public keys `flag || pk` in Base64. See `keytool list` for example public keys
multi-sig-combine-partial-sig Provides a list of participating signatures (`flag || sig || pk` encoded in Base64), threshold, a list of all public keys and a list of their weights that
define the MultiSig address. Returns a valid MultiSig signature and its sender address. The result can be used as signature field for `iota client
execute-signed-tx`. The sum of weights of all signatures must be >= the threshold
diff --git a/docs/content/references/contribute/style-guide.mdx b/docs/content/references/contribute/style-guide.mdx
index ab4a8b6ad80..27efe324a2c 100644
--- a/docs/content/references/contribute/style-guide.mdx
+++ b/docs/content/references/contribute/style-guide.mdx
@@ -238,8 +238,8 @@ Use imperative verbs for tasks, procedures, and instructions.
**Example**
- **Indicative –** IOTA network explorers display transactions on the network.
-- **Imperative –** Open a IOTA network explorer to view transactions on the network.
-- **Subjunctive –** We suggest that you view your transaction in a IOTA network explorer after you complete a transfer.
+- **Imperative –** Open an IOTA network explorer to view transactions on the network.
+- **Subjunctive –** We suggest that you view your transaction in an IOTA network explorer after you complete a transfer.
### Person
@@ -291,7 +291,7 @@ Do use serial commas.
**Example**
-> You must install Cargo, Rust, Docker, and the IOTA CLI to create a IOTA node.
+> You must install Cargo, Rust, Docker, and the IOTA CLI to create an IOTA node.
## Headings and titles
@@ -305,7 +305,7 @@ Use enough words in headings and titles to make it easy to know which link to cl
Users search for information to complete a specific task, so help them identify the topic that helps them by using descriptive titles. For example, _Get Started_. Get started with what? If there are multiple products or programs available it could be anything.
-_Get Started with IOTA_ is better, but users want to get started with a specific task or user journey with IOTA. Instead of _Get Started with IOTA_, describe the specific task or journey, such as _Create a IOTA Full Node_ or _IOTA Validator Guide_. Use Get Started as a heading on the Documentation landing page to categorize tasks for new users.
+_Get Started with IOTA_ is better, but users want to get started with a specific task or user journey with IOTA. Instead of _Get Started with IOTA_, describe the specific task or journey, such as _Create an IOTA Full Node_ or _IOTA Validator Guide_. Use Get Started as a heading on the Documentation landing page to categorize tasks for new users.
@@ -632,7 +632,7 @@ Proper nouns include:
## Product names
-Product names are proper nouns. Capitalize all words of a product name. When referring to a product, use only the product name without “the”. When referring specifically to a IOTA wallet, use IOTA Wallet or Ethos Wallet and not just wallet. Users likely have multiple wallets, and we want to make it clear which wallet. Use wallet generically when referring to the concept of a wallet.
+Product names are proper nouns. Capitalize all words of a product name. When referring to a product, use only the product name without “the”. When referring specifically to an IOTA wallet, use IOTA Wallet or Ethos Wallet and not just wallet. Users likely have multiple wallets, and we want to make it clear which wallet. Use wallet generically when referring to the concept of a wallet.
**Example**
diff --git a/docs/content/references/event-query-and-subscription.mdx b/docs/content/references/event-query-and-subscription.mdx
index b4ffdd40869..b6cdf59746e 100644
--- a/docs/content/references/event-query-and-subscription.mdx
+++ b/docs/content/references/event-query-and-subscription.mdx
@@ -8,7 +8,7 @@ The client provides an [event filter](#event-filters) to limit the scope of even
## Event types
-A IOTA node emits the following types of events:
+An IOTA node emits the following types of events:
- [Move event](#move-event)
- [Publish event](#publish-event)
@@ -195,7 +195,7 @@ None, Checkpoint events do not have any attributes. The event includes the Check
## IOTA event query criteria
-You can use the `EventQuery` criteria object to query a IOTA node and retrieve events that match query criteria.
+You can use the `EventQuery` criteria object to query an IOTA node and retrieve events that match query criteria.
| Query | Description | JSON-RPC Parameter Example |
| ----------- | --------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
diff --git a/docs/content/references/exchange-integration-guide.mdx b/docs/content/references/exchange-integration-guide.mdx
index 4b39392f9a2..8d7784b4502 100644
--- a/docs/content/references/exchange-integration-guide.mdx
+++ b/docs/content/references/exchange-integration-guide.mdx
@@ -6,23 +6,23 @@ slug: /exchange-integration-guide
This topic describes how to integrate IOTA, the token native to the IOTA network, into a cryptocurrency exchange. The specific requirements and processes to implement an integration vary between exchanges. Rather than provide a step-by-step guide, this topic provides information about the primary tasks necessary to complete an integration. After the guidance about how to configure an integration, you can also find information and code samples related to staking on the IOTA network.
-## Requirements to configure a IOTA integration
+## Requirements to configure an IOTA integration
-The requirements to configure a IOTA integration include:
+The requirements to configure an IOTA integration include:
-- A IOTA full node. You can operate your own IOTA full node or use a full node from a node operator.
-- Suggested minimum hardware to run a IOTA full node:
+- An IOTA full node. You can operate your own IOTA full node or use a full node from a node operator.
+- Suggested minimum hardware to run an IOTA full node:
- CPUs: 8 physical cores / 16 vCPUs
- RAM: 128 GB
- Storage (SSD): 4 TB NVMe drive
For best results, run IOTA full nodes on Linux. IOTA supports the Ubuntu and Debian distributions. You can also fun a full node on macOS.
-## Configure a IOTA full node
+## Configure an IOTA full node
-You can set up and configure a IOTA full node using Docker or directly from source code in the IOTA GitHub repository.
+You can set up and configure an IOTA full node using Docker or directly from source code in the IOTA GitHub repository.
-### Install a IOTA full node using Docker
+### Install an IOTA full node using Docker
Run the command in this section using the same branch of the repository for each. Replace `branch-name` with the branch you use. For example, use `devnet` to use the IOTA Devnet network, or use `testnet` to use the IOTA Testnet network. You must download all files to, and run all commands from, the same folder location.
@@ -54,9 +54,9 @@ Run the command in this section using the same branch of the repository for each
docker-compose up -d
```
-## Install a IOTA full node from source
+## Install an IOTA full node from source
-Use the steps in this section to install and configure a IOTA full node directly from the IOTA GitHub repository. These steps use [Cargo](https://doc.rust-lang.org/cargo/), the Rust package manager.
+Use the steps in this section to install and configure an IOTA full node directly from the IOTA GitHub repository. These steps use [Cargo](https://doc.rust-lang.org/cargo/), the Rust package manager.
1. Install prerequisites for IOTA.
1. Clone the IOTA repository:
@@ -91,7 +91,7 @@ IOTA addresses do not require on-chain initialization, you can spend from an add
Currently, IOTA address supports these signature schemes: pure Ed25519, Secp256k1, Secp256r1 and Multisig. The corresponding flag bytes are 0x00, 0x01, 0x02, 0x03 respectively.
-The following code sample demonstrates how to derive a IOTA address in Rust:
+The following code sample demonstrates how to derive an IOTA address in Rust:
```rust
let flag = 0x00; // 0x00 = ED25519, 0x01 = Secp256k1, 0x02 = Secp256r1, 0x03 = MultiSig
@@ -203,11 +203,11 @@ IOTA Checkpoint API operations include:
## IOTA Balance transfer
-To transfer a specific amount of IOTA between addresses, you need a IOTA token object with that specific value. In IOTA, everything is an object, including IOTA tokens. The amount of IOTA in each IOTA token object varies. For example, an address could own 3 IOTA tokens with different values: one of 0.1 IOTA, a second of 1.0 IOTA, and a third with 0.005 IOTA. The total balance for the address equals the sum of the values of the individual IOTA token objects, in this case, 1.105 IOTA.
+To transfer a specific amount of IOTA between addresses, you need an IOTA token object with that specific value. In IOTA, everything is an object, including IOTA tokens. The amount of IOTA in each IOTA token object varies. For example, an address could own 3 IOTA tokens with different values: one of 0.1 IOTA, a second of 1.0 IOTA, and a third with 0.005 IOTA. The total balance for the address equals the sum of the values of the individual IOTA token objects, in this case, 1.105 IOTA.
-You can merge and split IOTA token objects to create token objects with specific values. To create a IOTA token worth .6 IOTA, split the token worth 1 IOTA into two token objects worth .6 IOTA and .4 IOTA.
+You can merge and split IOTA token objects to create token objects with specific values. To create an IOTA token worth .6 IOTA, split the token worth 1 IOTA into two token objects worth .6 IOTA and .4 IOTA.
-To transfer a specific amount of IOTA, you need a IOTA token worth that specific amount. To get a IOTA token with that specific value, you might need to split or merge existing IOTA tokens. IOTA supports several methods to accomplish this, including some that do not require you to manually split or merge coins.
+To transfer a specific amount of IOTA, you need an IOTA token worth that specific amount. To get an IOTA token with that specific value, you might need to split or merge existing IOTA tokens. IOTA supports several methods to accomplish this, including some that do not require you to manually split or merge coins.
## IOTA API operations for transfers
diff --git a/docs/content/references/iota-compared.mdx b/docs/content/references/iota-compared.mdx
index 0126c647a66..de959f8a2ce 100644
--- a/docs/content/references/iota-compared.mdx
+++ b/docs/content/references/iota-compared.mdx
@@ -49,7 +49,7 @@ Because IOTA focuses on managing specific objects rather than a single aggregate
- Every object in IOTA has a unique version number.
- Every new version is created from a transaction that may involve several dependencies, themselves versioned objects.
-As a consequence, a IOTA Validator can exhibit a _causal history_ of an object, showing its history since genesis. IOTA explicitly makes the bet that in many cases, the ordering of that _causal history_ with the _causal history_ of another object is irrelevant; and in the few cases where this information is relevant, IOTA makes this relationship explicit in the data.
+As a consequence, an IOTA Validator can exhibit a _causal history_ of an object, showing its history since genesis. IOTA explicitly makes the bet that in many cases, the ordering of that _causal history_ with the _causal history_ of another object is irrelevant; and in the few cases where this information is relevant, IOTA makes this relationship explicit in the data.
## Causal order vs. total order
@@ -68,7 +68,7 @@ This section summarizes the main advantages of IOTA with respect to traditional
IOTA's main selling point is its unprecedented performance. The following bullet points summarize the main performance benefits of IOTA with respect to traditional blockchains:
- IOTA forgoes consensus for many transactions while other blockchains always totally order them. Causally ordering transactions allows IOTA to massively parallelize the execution of many transactions; this reduces latency and allows validators to take advantage of all their CPU cores.
-- IOTA pushes the complexity at the edges: the client is involved in a number of protocol steps. This minimizes the interactions between validators and keeps their code simpler and more efficient. IOTA always gives the possibility to offload most of the client's workload to a IOTA Gateway service for better user experience. In contrast, traditional blockchains follow a fire-and-forget model where clients monitor the blockchain state to assess the success of their transaction submission.
+- IOTA pushes the complexity at the edges: the client is involved in a number of protocol steps. This minimizes the interactions between validators and keeps their code simpler and more efficient. IOTA always gives the possibility to offload most of the client's workload to an IOTA Gateway service for better user experience. In contrast, traditional blockchains follow a fire-and-forget model where clients monitor the blockchain state to assess the success of their transaction submission.
- IOTA operates at network speed without waiting for system timeouts between protocol steps. This significantly reduces latency when the network is good and not under attack. In contrast, the security of a number of traditional blockchains (including most proof-of-work based blockchains) need to wait for predefined timeouts before committing transactions.
- IOTA can take advantage of more machines per validator to increase its performance. Traditional blockchains are often designed to run on a single machine per validator (or even on a single CPU).
@@ -102,7 +102,7 @@ This section presents the main disadvantages of IOTA with respect to traditional
While traditional blockchains require implementing only a single consensus protocol, IOTA requires two protocols: (i) a protocol based on Byzantine Consistent Broadcast to handle simple transactions, and (ii) a consensus protocol to handle transactions with shared objects. This means the IOTA team needs to maintain a much larger codebase.
-Transactions involving shared objects require a little overhead (adding two extra round trips - 200ms for well-connected clients using a IOTA Gateway service) before submitting it to the consensus protocol. This overhead is required to securely compose the two protocols described above. Other blockchains can instead directly submit the transaction to the consensus protocol. Note the finality for shared object transactions is still in the 2-3 second range even with this overhead.
+Transactions involving shared objects require a little overhead (adding two extra round trips - 200ms for well-connected clients using an IOTA Gateway service) before submitting it to the consensus protocol. This overhead is required to securely compose the two protocols described above. Other blockchains can instead directly submit the transaction to the consensus protocol. Note the finality for shared object transactions is still in the 2-3 second range even with this overhead.
Building an efficient synchronizer is harder in IOTA than in traditional blockchains. The synchronizer sub-protocol allows validators to update each other by sharing data, and it allows slow validators to catch up. Building an efficient synchronizer for traditional blockchains is no easy task, but still simpler than in IOTA.
diff --git a/docs/content/references/references.mdx b/docs/content/references/references.mdx
index e35a506b465..baf20002d45 100644
--- a/docs/content/references/references.mdx
+++ b/docs/content/references/references.mdx
@@ -33,7 +33,7 @@ Interact directly with IOTA networks and its features using the IOTA command lin
-Create a client on a IOTA network to generate addresses, access networks, and more with the IOTA Client CLI.
+Create a client on an IOTA network to generate addresses, access networks, and more with the IOTA Client CLI.
Build, preview, and execute programmable transaction blocks directly from your terminal with the IOTA Client PTB CLI.
diff --git a/docs/content/sidebars/developer.js b/docs/content/sidebars/developer.js
index 59e601c93ff..5cf53de9dc2 100644
--- a/docs/content/sidebars/developer.js
+++ b/docs/content/sidebars/developer.js
@@ -394,7 +394,7 @@ const developer = [
},
{
type: 'doc',
- label: 'Self-sponsor Iota Claiming',
+ label: 'Self-sponsor IOTA Claiming',
id: 'developer/stardust/claiming/self-sponsor',
},
],
diff --git a/docs/content/ts-sdk/api/client/classes/IotaClient.md b/docs/content/ts-sdk/api/client/classes/IotaClient.md
index caae17a3f8c..11b535deb8f 100644
--- a/docs/content/ts-sdk/api/client/classes/IotaClient.md
+++ b/docs/content/ts-sdk/api/client/classes/IotaClient.md
@@ -6,7 +6,7 @@
> **new IotaClient**(`options`): [`IotaClient`](IotaClient.md)
-Establish a connection to a IOTA RPC endpoint
+Establish a connection to an IOTA RPC endpoint
#### Parameters
diff --git a/docs/content/ts-sdk/api/client/interfaces/EventId.md b/docs/content/ts-sdk/api/client/interfaces/EventId.md
index 6b7f7ccebcc..8e937a94b89 100644
--- a/docs/content/ts-sdk/api/client/interfaces/EventId.md
+++ b/docs/content/ts-sdk/api/client/interfaces/EventId.md
@@ -1,6 +1,6 @@
# Interface: EventId
-Unique ID of a Iota Event, the ID is a combination of tx seq number and event seq number, the ID is
+Unique ID of an IOTA Event, the ID is a combination of tx seq number and event seq number, the ID is
local to this particular fullnode and will be different from other fullnode.
## Properties
diff --git a/docs/content/ts-sdk/api/client/interfaces/GetAllBalancesParams.md b/docs/content/ts-sdk/api/client/interfaces/GetAllBalancesParams.md
index 0f97cbbd409..3b542772fc5 100644
--- a/docs/content/ts-sdk/api/client/interfaces/GetAllBalancesParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/GetAllBalancesParams.md
@@ -8,4 +8,4 @@ Return the total coin balance for all coin type, owned by the address owner.
> **owner**: `string`
-the owner's Iota address
+the owner's IOTA address
diff --git a/docs/content/ts-sdk/api/client/interfaces/GetAllCoinsParams.md b/docs/content/ts-sdk/api/client/interfaces/GetAllCoinsParams.md
index c378282f13b..8b5c917631b 100644
--- a/docs/content/ts-sdk/api/client/interfaces/GetAllCoinsParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/GetAllCoinsParams.md
@@ -8,7 +8,7 @@ Return all Coin objects owned by an address.
> **owner**: `string`
-the owner's Iota address
+the owner's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/GetBalanceParams.md b/docs/content/ts-sdk/api/client/interfaces/GetBalanceParams.md
index 89d78b0fbdb..dec01139716 100644
--- a/docs/content/ts-sdk/api/client/interfaces/GetBalanceParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/GetBalanceParams.md
@@ -8,7 +8,7 @@ Return the total coin balance for one coin type, owned by the address owner.
> **owner**: `string`
-the owner's Iota address
+the owner's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/GetCoinsParams.md b/docs/content/ts-sdk/api/client/interfaces/GetCoinsParams.md
index f5870cd1bd3..c21e768bfb5 100644
--- a/docs/content/ts-sdk/api/client/interfaces/GetCoinsParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/GetCoinsParams.md
@@ -8,7 +8,7 @@ Return all Coin<`coin_type`> objects owned by an address.
> **owner**: `string`
-the owner's Iota address
+the owner's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/IotaEvent.md b/docs/content/ts-sdk/api/client/interfaces/IotaEvent.md
index 40a03ed7c99..1d577e2af99 100644
--- a/docs/content/ts-sdk/api/client/interfaces/IotaEvent.md
+++ b/docs/content/ts-sdk/api/client/interfaces/IotaEvent.md
@@ -40,7 +40,7 @@ Parsed json value of the event
> **sender**: `string`
-Sender's Iota address.
+Sender's IOTA address.
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/SubscribeEventParams.md b/docs/content/ts-sdk/api/client/interfaces/SubscribeEventParams.md
index 448b21e9591..723b48cfbe2 100644
--- a/docs/content/ts-sdk/api/client/interfaces/SubscribeEventParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/SubscribeEventParams.md
@@ -1,6 +1,6 @@
# Interface: SubscribeEventParams
-Subscribe to a stream of Iota event
+Subscribe to a stream of IOTA event
## Properties
diff --git a/docs/content/ts-sdk/api/client/interfaces/SubscribeTransactionParams.md b/docs/content/ts-sdk/api/client/interfaces/SubscribeTransactionParams.md
index 080041b1f59..3052c615e28 100644
--- a/docs/content/ts-sdk/api/client/interfaces/SubscribeTransactionParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/SubscribeTransactionParams.md
@@ -1,6 +1,6 @@
# Interface: SubscribeTransactionParams
-Subscribe to a stream of Iota transaction effects
+Subscribe to a stream of IOTA transaction effects
## Properties
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafeBatchTransactionParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafeBatchTransactionParams.md
index a6288e19ef6..d3bafbb8cec 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafeBatchTransactionParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafeBatchTransactionParams.md
@@ -8,7 +8,7 @@ Create an unsigned batched transaction.
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafeMergeCoinsParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafeMergeCoinsParams.md
index 14c57e62319..20edde0b753 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafeMergeCoinsParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafeMergeCoinsParams.md
@@ -8,7 +8,7 @@ Create an unsigned transaction to merge multiple coins into one coin.
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafeMoveCallParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafeMoveCallParams.md
index 8033a1b9ef2..86f81c33b76 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafeMoveCallParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafeMoveCallParams.md
@@ -9,7 +9,7 @@ function in the module of a given package.
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafePayAllIotaParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafePayAllIotaParams.md
index 8ef301e08cf..de8d477ae04 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafePayAllIotaParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafePayAllIotaParams.md
@@ -12,7 +12,7 @@ sum(input_coins) - actual_gas_cost. 4. all other input coins other than the firs
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
@@ -20,7 +20,7 @@ the transaction signer's Iota address
> **inputCoins**: `string`[]
-the Iota coins to be used in this transaction, including the coin for gas payment.
+the IOTA coins to be used in this transaction, including the coin for gas payment.
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafePayIotaParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafePayIotaParams.md
index 9a99d4b1006..0ba165f3954 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafePayIotaParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafePayIotaParams.md
@@ -14,7 +14,7 @@ than the first one are deleted.
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
@@ -22,7 +22,7 @@ the transaction signer's Iota address
> **inputCoins**: `string`[]
-the Iota coins to be used in this transaction, including the coin for gas payment.
+the IOTA coins to be used in this transaction, including the coin for gas payment.
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafePayParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafePayParams.md
index 4ad4bb50cc5..e6c98218842 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafePayParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafePayParams.md
@@ -11,7 +11,7 @@ auto-select one.
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
@@ -19,7 +19,7 @@ the transaction signer's Iota address
> **inputCoins**: `string`[]
-the Iota coins to be used in this transaction
+the IOTA coins to be used in this transaction
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafePublishParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafePublishParams.md
index f71ddfc0c58..46b14042a65 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafePublishParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafePublishParams.md
@@ -8,7 +8,7 @@ Create an unsigned transaction to publish a Move package.
> **sender**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestAddStakeParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestAddStakeParams.md
index ff4ff0f0d84..7b160ac581d 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestAddStakeParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestAddStakeParams.md
@@ -8,7 +8,7 @@ Add stake to a validator's staking pool using multiple coins and amount.
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
@@ -32,7 +32,7 @@ stake amount
> **validator**: `string`
-the validator's Iota address
+the validator's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestAddTimelockedStakeParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestAddTimelockedStakeParams.md
index b012505ed4a..130fa86c2ec 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestAddTimelockedStakeParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestAddTimelockedStakeParams.md
@@ -8,7 +8,7 @@ Add timelocked stake to a validator's staking pool using multiple balances and a
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
@@ -24,7 +24,7 @@ TimeLock> object to stake
> **validator**: `string`
-the validator's Iota address
+the validator's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestWithdrawStakeParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestWithdrawStakeParams.md
index fd1f21c21ba..44e248a901d 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestWithdrawStakeParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestWithdrawStakeParams.md
@@ -8,7 +8,7 @@ Withdraw stake from a validator's staking pool.
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestWithdrawTimelockedStakeParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestWithdrawTimelockedStakeParams.md
index c3ed583dd1c..f9b6bc370dd 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestWithdrawTimelockedStakeParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafeRequestWithdrawTimelockedStakeParams.md
@@ -8,7 +8,7 @@ Withdraw timelocked stake from a validator's staking pool.
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafeSplitCoinEqualParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafeSplitCoinEqualParams.md
index cb19a46b51e..b6166ab75f3 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafeSplitCoinEqualParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafeSplitCoinEqualParams.md
@@ -8,7 +8,7 @@ Create an unsigned transaction to split a coin object into multiple equal-size c
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafeSplitCoinParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafeSplitCoinParams.md
index 59c93b78247..e5d146ef17e 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafeSplitCoinParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafeSplitCoinParams.md
@@ -8,7 +8,7 @@ Create an unsigned transaction to split a coin object into multiple coins.
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafeTransferIotaParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafeTransferIotaParams.md
index 6c1333e2eee..a8288bb8426 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafeTransferIotaParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafeTransferIotaParams.md
@@ -1,6 +1,6 @@
# Interface: UnsafeTransferIotaParams
-Create an unsigned transaction to send IOTA coin object to a Iota address. The IOTA object is also
+Create an unsigned transaction to send IOTA coin object to an IOTA address. The IOTA object is also
used as the gas object.
## Properties
@@ -9,7 +9,7 @@ used as the gas object.
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
@@ -17,7 +17,7 @@ the transaction signer's Iota address
> **iotaObjectId**: `string`
-the Iota coin object to be used in this transaction
+the IOTA coin object to be used in this transaction
---
@@ -33,7 +33,7 @@ the gas budget, the transaction will fail if the gas cost exceed the budget
> **recipient**: `string`
-the recipient's Iota address
+the recipient's IOTA address
---
diff --git a/docs/content/ts-sdk/api/client/interfaces/UnsafeTransferObjectParams.md b/docs/content/ts-sdk/api/client/interfaces/UnsafeTransferObjectParams.md
index 282b0735111..03dfcf1c5f4 100644
--- a/docs/content/ts-sdk/api/client/interfaces/UnsafeTransferObjectParams.md
+++ b/docs/content/ts-sdk/api/client/interfaces/UnsafeTransferObjectParams.md
@@ -9,7 +9,7 @@ must allow public transfers
> **signer**: `string`
-the transaction signer's Iota address
+the transaction signer's IOTA address
---
@@ -42,4 +42,4 @@ the gas budget, the transaction will fail if the gas cost exceed the budget
> **recipient**: `string`
-the recipient's Iota address
+the recipient's IOTA address
diff --git a/docs/content/ts-sdk/api/client/type-aliases/GetOwnedObjectsParams.md b/docs/content/ts-sdk/api/client/type-aliases/GetOwnedObjectsParams.md
index cb5aaab254e..9eb08d9e563 100644
--- a/docs/content/ts-sdk/api/client/type-aliases/GetOwnedObjectsParams.md
+++ b/docs/content/ts-sdk/api/client/type-aliases/GetOwnedObjectsParams.md
@@ -12,7 +12,7 @@ been updated when the next page is fetched. Please use iotax_queryObjects if thi
> **owner**: `string`
-the owner's Iota address
+the owner's IOTA address
### cursor?
diff --git a/docs/content/ts-sdk/api/cryptography/classes/PublicKey.md b/docs/content/ts-sdk/api/cryptography/classes/PublicKey.md
index 3793a8aab8d..b54b2bbb9a7 100644
--- a/docs/content/ts-sdk/api/cryptography/classes/PublicKey.md
+++ b/docs/content/ts-sdk/api/cryptography/classes/PublicKey.md
@@ -63,7 +63,7 @@ Return the base-64 representation of the public key
> **toIotaPublicKey**(): `string`
Return the IOTA representation of the public key encoded in
-base-64. A IOTA public key is formed by the concatenation
+base-64. An IOTA public key is formed by the concatenation
of the scheme flag with the raw bytes of the public key
#### Returns
diff --git a/docs/content/ts-sdk/api/keypairs/ed25519/classes/Ed25519PublicKey.md b/docs/content/ts-sdk/api/keypairs/ed25519/classes/Ed25519PublicKey.md
index 1762dc9142e..01ad0dd18ab 100644
--- a/docs/content/ts-sdk/api/keypairs/ed25519/classes/Ed25519PublicKey.md
+++ b/docs/content/ts-sdk/api/keypairs/ed25519/classes/Ed25519PublicKey.md
@@ -71,7 +71,7 @@ Return the base-64 representation of the public key
> **toIotaPublicKey**(): `string`
Return the IOTA representation of the public key encoded in
-base-64. A IOTA public key is formed by the concatenation
+base-64. An IOTA public key is formed by the concatenation
of the scheme flag with the raw bytes of the public key
#### Returns
diff --git a/docs/content/ts-sdk/api/keypairs/secp256k1/classes/Secp256k1PublicKey.md b/docs/content/ts-sdk/api/keypairs/secp256k1/classes/Secp256k1PublicKey.md
index d7ee0719526..0d446b57fa8 100644
--- a/docs/content/ts-sdk/api/keypairs/secp256k1/classes/Secp256k1PublicKey.md
+++ b/docs/content/ts-sdk/api/keypairs/secp256k1/classes/Secp256k1PublicKey.md
@@ -71,7 +71,7 @@ Return the base-64 representation of the public key
> **toIotaPublicKey**(): `string`
Return the IOTA representation of the public key encoded in
-base-64. A IOTA public key is formed by the concatenation
+base-64. An IOTA public key is formed by the concatenation
of the scheme flag with the raw bytes of the public key
#### Returns
diff --git a/docs/content/ts-sdk/api/multisig/classes/MultiSigPublicKey.md b/docs/content/ts-sdk/api/multisig/classes/MultiSigPublicKey.md
index 2a2439369c5..0428fb1aa22 100644
--- a/docs/content/ts-sdk/api/multisig/classes/MultiSigPublicKey.md
+++ b/docs/content/ts-sdk/api/multisig/classes/MultiSigPublicKey.md
@@ -65,7 +65,7 @@ Return the base-64 representation of the public key
> **toIotaPublicKey**(): `string`
Return the IOTA representation of the public key encoded in
-base-64. A IOTA public key is formed by the concatenation
+base-64. An IOTA public key is formed by the concatenation
of the scheme flag with the raw bytes of the public key
#### Returns
diff --git a/docs/content/ts-sdk/dapp-kit/index.mdx b/docs/content/ts-sdk/dapp-kit/index.mdx
index bb1deb750f2..fb48350252e 100644
--- a/docs/content/ts-sdk/dapp-kit/index.mdx
+++ b/docs/content/ts-sdk/dapp-kit/index.mdx
@@ -1,8 +1,8 @@
-# Iota dApp Kit
+# IOTA dApp Kit
-The Iota dApp Kit is a set of React components, hooks, and utilities to help you build a dApp for the
-Iota ecosystem. Its hooks and components provide an interface for querying data from the Iota
-blockchain and connecting to Iota wallets.
+The IOTA dApp Kit is a set of React components, hooks, and utilities to help you build a dApp for the
+IOTA ecosystem. Its hooks and components provide an interface for querying data from the IOTA
+blockchain and connecting to IOTA wallets.
### Core Features
@@ -10,13 +10,13 @@ Some of the core features of the dApp Kit include:
- Query hooks to get the information your dApp needs
- Automatic wallet state management
-- Support for all Iota wallets
+- Support for all IOTA wallets
- Pre-built React components
- Lower level hooks for custom components
## Install
-To use the Iota dApp Kit in your project, run the following command in your project root:
+To use the IOTA dApp Kit in your project, run the following command in your project root:
```sh npm2yarn
npm i --save @iota/dapp-kit @iota/iota-sdk @tanstack/react-query
@@ -70,7 +70,7 @@ import '@iota/dapp-kit/dist/index.css';
## Using hooks to make RPC calls
-The dApp Kit provides a set of hooks for making RPC calls to the Iota blockchain. The hooks are thin
+The dApp Kit provides a set of hooks for making RPC calls to the IOTA blockchain. The hooks are thin
wrappers around `useQuery` from `@tanstack/react-query`. For more comprehensive documentation on how
to use these query hooks, check out the
[react-query documentation](https://tanstack.com/query/latest/docs/react/overview).
diff --git a/docs/content/ts-sdk/dapp-kit/rpc-hooks.mdx b/docs/content/ts-sdk/dapp-kit/rpc-hooks.mdx
index 471a09e36eb..53446b3dafc 100644
--- a/docs/content/ts-sdk/dapp-kit/rpc-hooks.mdx
+++ b/docs/content/ts-sdk/dapp-kit/rpc-hooks.mdx
@@ -5,7 +5,7 @@ IOTA dApp Kit ships with hooks for each of the RPC methods defined in the
## useIotaClientQuery
-Load data from the Iota RPC using the `useIotaClientQuery` hook. This hook is a wrapper around the
+Load data from the IOTA RPC using the `useIotaClientQuery` hook. This hook is a wrapper around the
[useQuery](https://tanstack.com/query/latest/docs/react/guides/queries) hook from
@tanstack/react-query.
@@ -40,7 +40,7 @@ function MyComponent() {
## useIotaClientQueries
-You can fetch a variable number of Iota RPC queries using the `useIotaClientQueries` hook. This hook
+You can fetch a variable number of IOTA RPC queries using the `useIotaClientQueries` hook. This hook
is a wrapper around the
[useQueries](https://tanstack.com/query/latest/docs/react/reference/useQueries) hook from
@tanstack/react-query.
diff --git a/docs/content/ts-sdk/kiosk/kiosk-client/introduction.mdx b/docs/content/ts-sdk/kiosk/kiosk-client/introduction.mdx
index e52f56bc105..75730a53e73 100644
--- a/docs/content/ts-sdk/kiosk/kiosk-client/introduction.mdx
+++ b/docs/content/ts-sdk/kiosk/kiosk-client/introduction.mdx
@@ -13,7 +13,7 @@ You can follow the example to create a `KioskClient`. View next section for usag
import { KioskClient } from '@iota/kiosk';
import { getFullnodeUrl, IotaClient, Network } from '@iota/iota-sdk/client';
-// We need a IOTA Client. You can re-use the IotaClient of your project
+// We need an IOTA Client. You can re-use the IotaClient of your project
// (it's not recommended to create a new one).
const client = new IotaClient({ url: getFullnodeUrl(Network.Testnet) });
diff --git a/docs/content/ts-sdk/typescript/cryptography/keypairs.mdx b/docs/content/ts-sdk/typescript/cryptography/keypairs.mdx
index 5a2d1af1bea..a4af80f2b50 100644
--- a/docs/content/ts-sdk/typescript/cryptography/keypairs.mdx
+++ b/docs/content/ts-sdk/typescript/cryptography/keypairs.mdx
@@ -1,7 +1,7 @@
# Key pairs
The IOTA TypeScript SDK provides `Keypair` classes that handle logic for signing and verification
-using the cryptographic key pairs associated with a IOTA address.
+using the cryptographic key pairs associated with an IOTA address.
The IOTA TypeScript SDK supports three signing schemes:
@@ -22,7 +22,7 @@ example, to use the Ed25519 scheme, import the `Ed25519Keypair` class from
import { Ed25519Keypair } from '@iota/iota-sdk/keypairs/ed25519';
```
-To create a random key pair (which identifies a IOTA address), instantiate a new `Keypair` class. To
+To create a random key pair (which identifies an IOTA address), instantiate a new `Keypair` class. To
reference a key pair from an existing secret key, pass the secret to the `fromSecretKey` function.
```typescript
diff --git a/docs/content/ts-sdk/typescript/graphql.mdx b/docs/content/ts-sdk/typescript/graphql.mdx
index 6aae5cdac25..9f38ff2df8b 100644
--- a/docs/content/ts-sdk/typescript/graphql.mdx
+++ b/docs/content/ts-sdk/typescript/graphql.mdx
@@ -7,7 +7,7 @@ IotaGraphQLClient is still in development and may change rapidly as it is being
:::
To support GraphQL Queries, the Typescript SDK includes the `IotaGraphQLClient` which can help you
-write and execute GraphQL queries against the Iota GraphQL API that are type-safe and easy to use.
+write and execute GraphQL queries against the IOTA GraphQL API that are type-safe and easy to use.
## Writing your first query
diff --git a/docs/content/ts-sdk/typescript/hello-iota.mdx b/docs/content/ts-sdk/typescript/hello-iota.mdx
index 942eb463727..1189aa0b141 100644
--- a/docs/content/ts-sdk/typescript/hello-iota.mdx
+++ b/docs/content/ts-sdk/typescript/hello-iota.mdx
@@ -2,14 +2,14 @@ import Faucet from '@site/../content/_snippets/faucet.mdx';
# Hello IOTA
-This basic example introduces you to the IOTA TypeScript SDK. The Node.js example mints IOTA on a IOTA
+This basic example introduces you to the IOTA TypeScript SDK. The Node.js example mints IOTA on an IOTA
network and then queries the address to get a sum for the owned IOTA. You don't need to use an IDE to
complete the example, but one like Microsoft Visual Studio Code helps centralize more advanced
projects.
## Before you begin
-You need an address on a IOTA development network (Devnet, Testnet, local). If you don't already have
+You need an address on an IOTA development network (Devnet, Testnet, local). If you don't already have
an address, use the [IOTA Client CLI](../../references/cli/client.mdx) or the
IOTA Wallet browser extension to create one.
@@ -106,4 +106,4 @@ the faucet. You can check the total IOTA for your address using the IOTA Wallet
You can also use the [IOTA Client CLI](../../references/cli/client.mdx) to perform client
-calls on a IOTA network.
\ No newline at end of file
+calls on an IOTA network.
\ No newline at end of file
diff --git a/docs/content/ts-sdk/typescript/index.mdx b/docs/content/ts-sdk/typescript/index.mdx
index ca0b3a75128..ec5d35db951 100644
--- a/docs/content/ts-sdk/typescript/index.mdx
+++ b/docs/content/ts-sdk/typescript/index.mdx
@@ -5,7 +5,7 @@ import HighTrafficRpcs from "@site/../content/_snippets/info-high-traffic.mdx";
# IOTA TypeScript SDK Quick Start
The IOTA TypeScript SDK is a modular library of tools for interacting with the IOTA blockchain. Use it
-to send queries to RPC nodes, build and sign transactions, and interact with a IOTA or local network.
+to send queries to RPC nodes, build and sign transactions, and interact with an IOTA or local network.
## Installation
diff --git a/docs/content/ts-sdk/typescript/transaction-building/intents.mdx b/docs/content/ts-sdk/typescript/transaction-building/intents.mdx
index 41466e13796..a0eecc48dcd 100644
--- a/docs/content/ts-sdk/typescript/transaction-building/intents.mdx
+++ b/docs/content/ts-sdk/typescript/transaction-building/intents.mdx
@@ -31,7 +31,7 @@ tx.setSender(keypair.toIotaAddress());
tx.transferObjects(
[
- // Create a IOTA coin (balance is in NANOS)
+ // Create an IOTA coin (balance is in NANOS)
coinWithBalance({ balance: 100 }),
// Create a coin of another type
coinWithBalance({ balance: 100, type: '0x123::foo:Bar' }),
diff --git a/docs/content/ts-sdk/typescript/utils.mdx b/docs/content/ts-sdk/typescript/utils.mdx
index 02e36b5638b..36360e2f883 100644
--- a/docs/content/ts-sdk/typescript/utils.mdx
+++ b/docs/content/ts-sdk/typescript/utils.mdx
@@ -9,7 +9,7 @@ A set of constants exported for common uses cases:
- `NANOS_PER_IOTA`: The conversion rate for NANOS to IOTA (1,000,000,000)
- `IOTA_DECIMALS`: the number of decimals you must shift a NANOS value to convert it to IOTA (`9`)
-- `IOTA_ADDRESS_LENGTH`: The number of bytes in a IOTA address (32)
+- `IOTA_ADDRESS_LENGTH`: The number of bytes in an IOTA address (32)
- `MOVE_STDLIB_ADDRESS`: The address for the IOTA Move standard library
- `IOTA_FRAMEWORK_ADDRESS`: The address for the IOTA Framework
- `IOTA_SYSTEM_ADDRESS`: The address for the IOTA System module
diff --git a/docs/examples/rust/stardust/iota-self-sponsor.rs b/docs/examples/rust/stardust/iota-self-sponsor.rs
index f2acf11c92e..0e8250ee65a 100644
--- a/docs/examples/rust/stardust/iota-self-sponsor.rs
+++ b/docs/examples/rust/stardust/iota-self-sponsor.rs
@@ -1,7 +1,7 @@
// Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-//! Example demonstrating the self-sponsor scenario for claiming a Iota basic
+//! Example demonstrating the self-sponsor scenario for claiming an IOTA basic
//! output. In order to work, it requires a network with test objects
//! generated from iota-genesis-builder/src/stardust/test_outputs.
@@ -42,7 +42,7 @@ async fn main() -> Result<(), anyhow::Error> {
// For this example we need to derive addresses that are at different
// indexes and coin_types, one for sponsoring with IOTA coin type and one for
- // claiming the Basic Output with Iota coin type.
+ // claiming the Basic Output with IOTA coin type.
let sponsor_derivation_path =
DerivationPath::from_str(format!("m/44'/{IOTA_COIN_TYPE}'/0'/0'/5'").as_str())?;
let sender_derivation_path =
diff --git a/docs/examples/typescript/src/stardust/iota-self-sponsor.ts b/docs/examples/typescript/src/stardust/iota-self-sponsor.ts
index df6e6c375d0..ffab095986c 100644
--- a/docs/examples/typescript/src/stardust/iota-self-sponsor.ts
+++ b/docs/examples/typescript/src/stardust/iota-self-sponsor.ts
@@ -1,7 +1,7 @@
/** Copyright (c) 2024 IOTA Stiftung
* SPDX-License-Identifier: Apache-2.0
*
- * Example demonstrating the self-sponsor scenario for claiming a Iota basic
+ * Example demonstrating the self-sponsor scenario for claiming an IOTA basic
* output. In order to work, it requires a network with test objects
* generated from iota-genesis-builder/src/stardust/test_outputs.
*/
@@ -18,7 +18,7 @@ async function main() {
// For this example we need to derive addresses that are at different
// indexes and coin_types, one for sponsoring with IOTA coin type and one for
- // claiming the Basic Output with Iota coin type.
+ // claiming the Basic Output with IOTA coin type.
const sponsorDerivationPath = "m/44'/4218'/0'/0'/5'"
const senderDerivationPath = "m/44'/4218'/0'/0'/50'"
diff --git a/docs/site/config/jargon.js b/docs/site/config/jargon.js
index 669bc6d8cff..55b59f6defa 100644
--- a/docs/site/config/jargon.js
+++ b/docs/site/config/jargon.js
@@ -7,7 +7,7 @@ module.exports = {
'eventual consistency': 'Eventual consistency is the consensus model employed by IOTA; if one honest validator certifies the transaction, all of the other honest validators will too eventually.',
finality: 'Finality is the assurance a transaction will not be revoked. This stage is considered closure for an exchange or other blockchain transaction.',
gas: 'Gas refers to the computational effort required for executing operations on the IOTA network. In IOTA, gas is paid with the network\'s native currency IOTA. The cost of executing a transaction in IOTA units is referred to as the transaction fee.',
- genesis: 'Genesis is the initial act of creating accounts and gas objects for a IOTA network. IOTA provides a `genesis` command that allows users to create and inspect the genesis object setting up the network for operation.',
+ genesis: 'Genesis is the initial act of creating accounts and gas objects for an IOTA network. IOTA provides a `genesis` command that allows users to create and inspect the genesis object setting up the network for operation.',
'multi-writer objects': 'Multi-writer objects are objects that are owned by more than one address. Transactions affecting multi-writer objects require consensus in IOTA. This contrasts with transactions affecting only single-writer objects, which require only a confirmation of the owner\'s address contents.',
object: `
The basic unit of storage in IOTA is object. In contrast to many other blockchains, where storage is centered around address and each address contains a key-value store, IOTA\'s storage is centered around objects. IOTA objects have one of the following primary states:
diff --git a/docs/site/static/img/concepts/execution-architecture/dark/iota-architecture.svg b/docs/site/static/img/concepts/execution-architecture/dark/iota-architecture.svg
index ab6607556e2..f3f9d191dea 100644
--- a/docs/site/static/img/concepts/execution-architecture/dark/iota-architecture.svg
+++ b/docs/site/static/img/concepts/execution-architecture/dark/iota-architecture.svg
@@ -1,4 +1,4 @@
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/docs/site/static/img/concepts/execution-architecture/iota-architecture.svg b/docs/site/static/img/concepts/execution-architecture/iota-architecture.svg
index ba261ecd774..4ab82fef1e3 100644
--- a/docs/site/static/img/concepts/execution-architecture/iota-architecture.svg
+++ b/docs/site/static/img/concepts/execution-architecture/iota-architecture.svg
@@ -1,4 +1,4 @@
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/examples/custom-indexer/rust/README.md b/examples/custom-indexer/rust/README.md
index ff88fc603b5..00bf9f214ee 100644
--- a/examples/custom-indexer/rust/README.md
+++ b/examples/custom-indexer/rust/README.md
@@ -1,8 +1,8 @@
-# Iota Custom Indexer Example
+# IOTA Custom Indexer Example
-This is a complimentary example to the Iota Custom Indexer documentation.
-It demonstrates how to create a custom indexer for the Iota search engine.
-See the [Iota Custom Indexer documentation](https://docs.iota.org/developer/advanced/custom-indexer) for more information.
+This is a complimentary example to the IOTA Custom Indexer documentation.
+It demonstrates how to create a custom indexer for the IOTA search engine.
+See the [IOTA Custom Indexer documentation](https://docs.iota.org/developer/advanced/custom-indexer) for more information.
## Prerequisites
diff --git a/examples/move/asset_tokenization/asset_tokenization/sources/proxy.move b/examples/move/asset_tokenization/asset_tokenization/sources/proxy.move
index 872ffb29ca2..ce8a73e5eee 100644
--- a/examples/move/asset_tokenization/asset_tokenization/sources/proxy.move
+++ b/examples/move/asset_tokenization/asset_tokenization/sources/proxy.move
@@ -8,7 +8,7 @@
/// will not be the same as the publisher of the tokenized asset type.
module asset_tokenization::proxy {
- // Iota imports
+ // IOTA imports
use iota::package::{Self, Publisher};
use iota::transfer_policy::{Self, TransferPolicy, TransferPolicyCap};
use iota::display::{Self, Display};
diff --git a/examples/move/asset_tokenization/asset_tokenization/sources/tokenized_asset.move b/examples/move/asset_tokenization/asset_tokenization/sources/tokenized_asset.move
index c2ad98d3524..6bc7df1aea2 100644
--- a/examples/move/asset_tokenization/asset_tokenization/sources/tokenized_asset.move
+++ b/examples/move/asset_tokenization/asset_tokenization/sources/tokenized_asset.move
@@ -14,7 +14,7 @@ module asset_tokenization::tokenized_asset {
use std::ascii;
use std::type_name::{Self};
- // Iota imports
+ // IOTA imports
use iota::url::{Url};
use iota::vec_map::{Self, VecMap};
use iota::balance::{Self, Supply, Balance};
diff --git a/examples/move/asset_tokenization/asset_tokenization/sources/unlock.move b/examples/move/asset_tokenization/asset_tokenization/sources/unlock.move
index d39e45b27dc..cdd34df42e2 100644
--- a/examples/move/asset_tokenization/asset_tokenization/sources/unlock.move
+++ b/examples/move/asset_tokenization/asset_tokenization/sources/unlock.move
@@ -8,7 +8,7 @@
/// of requirements (rules / policies).
module asset_tokenization::unlock {
- // Iota imports
+ // IOTA imports
use iota::transfer_policy::{Self, TransferRequest};
use asset_tokenization::tokenized_asset::{Self, TokenizedAsset, AssetCap};
diff --git a/examples/move/asset_tokenization/template/sources/genesis.move b/examples/move/asset_tokenization/template/sources/genesis.move
index 4b4732245b1..ca7d0c90cd8 100644
--- a/examples/move/asset_tokenization/template/sources/genesis.move
+++ b/examples/move/asset_tokenization/template/sources/genesis.move
@@ -4,7 +4,7 @@
module template::genesis {
- // Iota imports
+ // IOTA imports
use iota::package::{ Self };
public struct GENESIS has drop {}
diff --git a/examples/move/asset_tokenization/template/sources/template.move b/examples/move/asset_tokenization/template/sources/template.move
index 62e1a7b0d7b..d985e231ed0 100644
--- a/examples/move/asset_tokenization/template/sources/template.move
+++ b/examples/move/asset_tokenization/template/sources/template.move
@@ -8,7 +8,7 @@ module asset_tokenization::template {
use std::string::{Self};
use std::ascii;
- // Iota imports
+ // IOTA imports
use iota::url;
// Asset tokenization imports
diff --git a/examples/move/random/raffles/sources/example1.move b/examples/move/random/raffles/sources/example1.move
index 8e7c5858d52..3a42c8757a5 100644
--- a/examples/move/random/raffles/sources/example1.move
+++ b/examples/move/random/raffles/sources/example1.move
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-/// Basic raffle game that depends on Iota randomness.
+/// Basic raffle game that depends on IOTA randomness.
///
/// Anyone can create a new raffle game with an end time and a price. After the end time, anyone can trigger
/// a function to determine the winner, and the winner gets the entire balance of the game.
diff --git a/examples/move/random/raffles/sources/example2.move b/examples/move/random/raffles/sources/example2.move
index 429599cf382..ac7b6a63e24 100644
--- a/examples/move/random/raffles/sources/example2.move
+++ b/examples/move/random/raffles/sources/example2.move
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-/// Basic raffles game that depends on Iota randomness.
+/// Basic raffles game that depends on IOTA randomness.
///
/// Anyone can create a new raffle game with an end time and a price. After the end time, anyone can trigger
/// a function to determine the winner, and the winner gets the entire balance of the game.
diff --git a/examples/move/random/slot_machine/sources/example.move b/examples/move/random/slot_machine/sources/example.move
index 4115f91a24d..eb2aa0ef0f7 100644
--- a/examples/move/random/slot_machine/sources/example.move
+++ b/examples/move/random/slot_machine/sources/example.move
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-/// A betting game that depends on Iota randomness.
+/// A betting game that depends on IOTA randomness.
///
/// Anyone can create a new game for the current epoch by depositing IOTA as the initial balance. The creator can
/// withdraw the remaining balance after the epoch is over.
diff --git a/examples/move/transfer-to-object/README.md b/examples/move/transfer-to-object/README.md
index ebcbf24a31b..c63ef955bc3 100644
--- a/examples/move/transfer-to-object/README.md
+++ b/examples/move/transfer-to-object/README.md
@@ -1,7 +1,7 @@
# Transfer-to-Object: Cash Register Example
This document explores various methods of implementing a cash register that can
-accept and process payments on Iota. We'll focus on highlighting the trade-offs
+accept and process payments on IOTA. We'll focus on highlighting the trade-offs
of each approach. Through these examples, you'll gain insights into the new
transfer-to-object functionality and understand some of its applications and
the types of issues it can address.
diff --git a/examples/tic-tac-toe/README.md b/examples/tic-tac-toe/README.md
index ae7ad482f7f..17b4cca9e73 100644
--- a/examples/tic-tac-toe/README.md
+++ b/examples/tic-tac-toe/README.md
@@ -90,7 +90,7 @@ can choose not to place a move, or simply forget to). That third party
may also need to run a service that keeps track of marks sent to games
in order to apply them promptly, which adds complexity.
-There is an alternative approach, which leverages Iota's support for
+There is an alternative approach, which leverages IOTA's support for
**multisigs** and **sponsored transactions**. Instead of entrusting
the Game to a third party, it is sent to an address owned by a 1-of-2
multisig, signed for by Player X and Player O.
@@ -115,7 +115,7 @@ multisig account can be generalized from two accounts to a max of ten
multisig).
In order to create a multisig, the public keys of all the signers
-needs to be known. Each account address on Iota is the hash of a public
+needs to be known. Each account address on IOTA is the hash of a public
key, but this operation cannot be reversed, so in order to start a
multisig game, players must exchange public keys instead of addresses.
diff --git a/examples/tic-tac-toe/cli/src/client.rs b/examples/tic-tac-toe/cli/src/client.rs
index 4fd315cfa92..10f32085f8f 100644
--- a/examples/tic-tac-toe/cli/src/client.rs
+++ b/examples/tic-tac-toe/cli/src/client.rs
@@ -41,7 +41,7 @@ use crate::{
#[derive(Parser, Debug)]
pub struct Connection {
- /// The Iota CLI config file, (default: ~/.iota/iota_config/client.yaml)
+ /// The IOTA CLI config file, (default: ~/.iota/iota_config/client.yaml)
#[clap(long)]
config: Option,
diff --git a/examples/tic-tac-toe/ui/README.md b/examples/tic-tac-toe/ui/README.md
index e6bb47f0d24..504fe8a22c3 100644
--- a/examples/tic-tac-toe/ui/README.md
+++ b/examples/tic-tac-toe/ui/README.md
@@ -6,7 +6,7 @@ owned objects and multi-sigs functionality.
This part of the demo illustrates how to:
-- Set-up an application to interact with a blockchain, using the Iota TypeScript
+- Set-up an application to interact with a blockchain, using the IOTA TypeScript
SDK and dApp-kit, including deploying its Move packages.
- Build UIs that represent on-chain data, and update in response to running
transactions.
diff --git a/examples/tic-tac-toe/ui/src/components/NewMultiSigGame.tsx b/examples/tic-tac-toe/ui/src/components/NewMultiSigGame.tsx
index 2b456845fae..f3026e7a7cb 100644
--- a/examples/tic-tac-toe/ui/src/components/NewMultiSigGame.tsx
+++ b/examples/tic-tac-toe/ui/src/components/NewMultiSigGame.tsx
@@ -85,7 +85,7 @@ export function NewMultiSigGame(): ReactElement {
In order to construct the multi-sig, we need to know the public keys of the two players.
- Although addresses on Iota are derived from public keys, the derivation cannot be reversed,
+ Although addresses on IOTA are derived from public keys, the derivation cannot be reversed,
so to start a multi-sig game, we ask for the public keys directly.
@@ -122,7 +122,7 @@ function Validation({
}
/**
- * If `key` is a valid base64 encoded Iota public key, return it as a
+ * If `key` is a valid base64 encoded IOTA public key, return it as a
* `PublicKey`, otherwise return null.
*/
function parsePublicKey(key?: string): PublicKey | null {
diff --git a/external-crates/move/crates/move-analyzer/editors/code/README.md b/external-crates/move/crates/move-analyzer/editors/code/README.md
index d880304ae7c..832ab04a1b1 100644
--- a/external-crates/move/crates/move-analyzer/editors/code/README.md
+++ b/external-crates/move/crates/move-analyzer/editors/code/README.md
@@ -39,7 +39,7 @@ that you have Rust development already [installed](https://www.rust-lang.org/too
This can be done in two steps:
1. Install the move-analyzer installation prerequisites for your platform. They are the same
- as prerequisites for Iota installation - for Linux, macOS and Windows these prerequisites and
+ as prerequisites for IOTA installation - for Linux, macOS and Windows these prerequisites and
their installation instructions can be found
[here](https://docs.iota.org/developer/getting-started/install-iota#additional-prerequisites-by-operating-system)
2. Invoke `cargo install --git https://github.com/iotaledger/iota iota-move-lsp` to install the
@@ -67,7 +67,7 @@ extension.
## What if everything else fails?
-Check the [Iota Discord](https://discord.iota.org/) to see if the problem
+Check the [IOTA Discord](https://discord.iota.org/) to see if the problem
has already been reported and, if not, report it there.
# Features
diff --git a/external-crates/move/crates/move-analyzer/editors/code/package.json b/external-crates/move/crates/move-analyzer/editors/code/package.json
index c5199da4812..e98c8ff67ad 100644
--- a/external-crates/move/crates/move-analyzer/editors/code/package.json
+++ b/external-crates/move/crates/move-analyzer/editors/code/package.json
@@ -22,7 +22,7 @@
],
"keywords": [
"move",
- "Iota",
+ "IOTA",
"iotaledger",
"IOTA Foundation"
],
diff --git a/external-crates/move/crates/move-analyzer/editors/code/scripts/create.sh b/external-crates/move/crates/move-analyzer/editors/code/scripts/create.sh
index f94940ab8fa..7756f0cfe2b 100755
--- a/external-crates/move/crates/move-analyzer/editors/code/scripts/create.sh
+++ b/external-crates/move/crates/move-analyzer/editors/code/scripts/create.sh
@@ -46,7 +46,7 @@ done
# these will have to change if we want a different version
VERSION="0.7.2-rc"
-# a map from os version identifiers in Iota's binary distribution to os version identifiers
+# a map from os version identifiers in IOTA's binary distribution to os version identifiers
# representing VSCode's target platforms used for creating platform-specific plugin distributions
declare -A SUPPORTED_OS
SUPPORTED_OS[macos-arm64]=darwin-arm64
@@ -65,9 +65,9 @@ mkdir $LANG_SERVER_DIR
for DIST_OS VSCODE_OS in "${(@kv)SUPPORTED_OS}"; do
# IOTA distribution identifier
IOTA_VERSION="v"$VERSION
- # name of the Iota distribution archive file, for example iota-v1.0.0-macos-arm64.tgz
+ # name of the IOTA distribution archive file, for example iota-v1.0.0-macos-arm64.tgz
IOTA_ARCHIVE="iota-"$IOTA_VERSION"-"$DIST_OS".tgz"
- # a path to downloaded Iota archive
+ # a path to downloaded IOTA archive
IOTA_ARCHIVE_PATH=$TMP_DIR"/"$IOTA_ARCHIVE
# download IOTA archive file to a given location and uncompress it
@@ -75,7 +75,7 @@ for DIST_OS VSCODE_OS in "${(@kv)SUPPORTED_OS}"; do
tar -xf $IOTA_ARCHIVE_PATH --directory $TMP_DIR
# names of the move-analyzer binary, both the one becoming part of the extension ($SERVER_BIN)
- # and the one in the Iota archive ($ARCHIVE_SERVER_BIN)
+ # and the one in the IOTA archive ($ARCHIVE_SERVER_BIN)
SERVER_BIN="move-analyzer"
ARCHIVE_SERVER_BIN=$SERVER_BIN
if [[ "$DIST_OS" == *"windows"* ]]; then
diff --git a/external-crates/move/crates/move-analyzer/editors/code/src/configuration.ts b/external-crates/move/crates/move-analyzer/editors/code/src/configuration.ts
index 919d8086ad7..c1aeb4b4868 100644
--- a/external-crates/move/crates/move-analyzer/editors/code/src/configuration.ts
+++ b/external-crates/move/crates/move-analyzer/editors/code/src/configuration.ts
@@ -57,7 +57,7 @@ export class Configuration {
return path.resolve(serverPath);
}
- /** The path to the Iota binary. */
+ /** The path to the IOTA binary. */
get iotaPath(): string {
const iotaBin = process.platform === 'win32' ? 'iota.exe' : 'iota';
const iotaPath = this.configuration.get(IOTA_PATH_OPT) ?? iotaBin;
diff --git a/external-crates/move/crates/move-analyzer/editors/code/src/main.ts b/external-crates/move/crates/move-analyzer/editors/code/src/main.ts
index 5b2f073ca0b..67d57903097 100644
--- a/external-crates/move/crates/move-analyzer/editors/code/src/main.ts
+++ b/external-crates/move/crates/move-analyzer/editors/code/src/main.ts
@@ -84,7 +84,7 @@ async function iotaMoveCmd(context: Readonly, cmd: string): Promise AliasMapBuilder {
.map(|(m, mem, k)| (std_address, m, mem, k)),
);
}
- // if iota is defined and the current package is in Iota mode, add implicit iota
+ // if iota is defined and the current package is in IOTA mode, add implicit iota
// aliases
if iota_address.is_some()
&& context.env().package_config(current_package).flavor == Flavor::Iota
diff --git a/external-crates/move/crates/move-compiler/src/hlir/translate.rs b/external-crates/move/crates/move-compiler/src/hlir/translate.rs
index 46fce24ed4f..6479a8d577e 100644
--- a/external-crates/move/crates/move-compiler/src/hlir/translate.rs
+++ b/external-crates/move/crates/move-compiler/src/hlir/translate.rs
@@ -2921,7 +2921,7 @@ fn gen_unused_warnings(
if let H::StructFields::Defined(fields) = &sdef.fields {
for (f, _) in fields {
- // skip for Iota ID fields
+ // skip for IOTA ID fields
if is_iota_mode && has_key && f.value() == ID_FIELD_NAME {
continue;
}
diff --git a/external-crates/move/crates/move-compiler/src/iota_mode/linters/freezing_capability.rs b/external-crates/move/crates/move-compiler/src/iota_mode/linters/freezing_capability.rs
index e55ff3b48d5..a5c099b96c6 100644
--- a/external-crates/move/crates/move-compiler/src/iota_mode/linters/freezing_capability.rs
+++ b/external-crates/move/crates/move-compiler/src/iota_mode/linters/freezing_capability.rs
@@ -2,7 +2,7 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-//! Implements lint to warn against freezing capability-like types in Iota, identifying function calls that may incorrectly freeze such types.
+//! Implements lint to warn against freezing capability-like types in IOTA, identifying function calls that may incorrectly freeze such types.
//! The lint checks for specific freezing functions defined in constants and inspects their type arguments for capability-like type names.
use super::{LinterDiagnosticCategory, LinterDiagnosticCode, LINT_WARNING_PREFIX};
diff --git a/external-crates/move/crates/move-compiler/src/iota_mode/typing.rs b/external-crates/move/crates/move-compiler/src/iota_mode/typing.rs
index 40485c1010e..db1a1344e9b 100644
--- a/external-crates/move/crates/move-compiler/src/iota_mode/typing.rs
+++ b/external-crates/move/crates/move-compiler/src/iota_mode/typing.rs
@@ -229,7 +229,7 @@ fn struct_def(context: &mut Context, name: DatatypeName, sdef: &N::StructDefinit
}
fn invalid_object_id_field_diag(key_loc: Loc, loc: Loc, name: DatatypeName) -> Diagnostic {
- const KEY_MSG: &str = "The 'key' ability is used to declare objects in Iota";
+ const KEY_MSG: &str = "The 'key' ability is used to declare objects in IOTA";
let msg = format!(
"Invalid object '{}'. \
diff --git a/external-crates/move/crates/move-compiler/src/typing/core.rs b/external-crates/move/crates/move-compiler/src/typing/core.rs
index bf4f5560509..0de9596828d 100644
--- a/external-crates/move/crates/move-compiler/src/typing/core.rs
+++ b/external-crates/move/crates/move-compiler/src/typing/core.rs
@@ -1680,7 +1680,7 @@ fn check_function_visibility(
pub enum PublicForTesting {
/// The function is entry, so it can be called in unit tests
Entry(Loc),
- // TODO we should allow calling init in unit tests, but this would need Iota bytecode verifier
+ // TODO we should allow calling init in unit tests, but this would need IOTA bytecode verifier
// support. Or we would need to name dodge init in unit tests
// IotaInit(Loc),
}
diff --git a/external-crates/move/crates/move-compiler/src/typing/translate.rs b/external-crates/move/crates/move-compiler/src/typing/translate.rs
index 386d187e2a7..85314d24049 100644
--- a/external-crates/move/crates/move-compiler/src/typing/translate.rs
+++ b/external-crates/move/crates/move-compiler/src/typing/translate.rs
@@ -4687,7 +4687,7 @@ fn unused_module_members(context: &mut Context, mident: &ModuleIdent_, mdef: &T:
continue;
}
if is_iota_mode && *name == iota_mode::INIT_FUNCTION_NAME {
- // a Iota-specific filter to avoid signaling that the init function is unused
+ // an IOTA-specific filter to avoid signaling that the init function is unused
continue;
}
context
diff --git a/external-crates/move/crates/move-compiler/tests/iota_mode/init/unused_function.move b/external-crates/move/crates/move-compiler/tests/iota_mode/init/unused_function.move
index c5eac6ef8e1..2cb13fd84a7 100644
--- a/external-crates/move/crates/move-compiler/tests/iota_mode/init/unused_function.move
+++ b/external-crates/move/crates/move-compiler/tests/iota_mode/init/unused_function.move
@@ -1,4 +1,4 @@
-// init is unused but does not error because we are in Iota mode
+// init is unused but does not error because we are in IOTA mode
module a::m {
fun init(_: &mut iota::tx_context::TxContext) {}
}
diff --git a/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_first_field_not_id.exp b/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_first_field_not_id.exp
index 47f134853a3..a6dc8d901b6 100644
--- a/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_first_field_not_id.exp
+++ b/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_first_field_not_id.exp
@@ -2,7 +2,7 @@ error[Iota E02007]: invalid object declaration
┌─ tests/iota_mode/struct_with_key/key_struct_first_field_not_id.move:4:9
│
3 │ struct S has key {
- │ --- The 'key' ability is used to declare objects in Iota
+ │ --- The 'key' ability is used to declare objects in IOTA
4 │ flag: bool
│ ^^^^ Invalid object 'S'. Structs with the 'key' ability must have 'id: iota::object::UID' as their first field
diff --git a/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_struct_address.exp b/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_struct_address.exp
index c509b1a175d..0c329f614d7 100644
--- a/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_struct_address.exp
+++ b/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_struct_address.exp
@@ -2,7 +2,7 @@ error[Iota E02007]: invalid object declaration
┌─ tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_struct_address.move:5:9
│
4 │ struct S has key {
- │ --- The 'key' ability is used to declare objects in Iota
+ │ --- The 'key' ability is used to declare objects in IOTA
5 │ id: UID
│ ^^ --- But found type: 'a::object::UID'
│ │
@@ -12,7 +12,7 @@ error[Iota E02007]: invalid object declaration
┌─ tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_struct_address.move:13:9
│
12 │ struct S has key {
- │ --- The 'key' ability is used to declare objects in Iota
+ │ --- The 'key' ability is used to declare objects in IOTA
13 │ id: UID
│ ^^ --- But found type: '0x2::object::UID'
│ │
diff --git a/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_struct_name.exp b/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_struct_name.exp
index 1328d8554ff..831d2cb3bdf 100644
--- a/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_struct_name.exp
+++ b/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_struct_name.exp
@@ -2,7 +2,7 @@ error[Iota E02007]: invalid object declaration
┌─ tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_struct_name.move:5:9
│
4 │ struct S has key {
- │ --- The 'key' ability is used to declare objects in Iota
+ │ --- The 'key' ability is used to declare objects in IOTA
5 │ id: object::ID
│ ^^ ---------- But found type: 'iota::object::ID'
│ │
diff --git a/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_type.exp b/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_type.exp
index 660d3945fdf..6db9e2c6919 100644
--- a/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_type.exp
+++ b/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_type.exp
@@ -2,7 +2,7 @@ error[Iota E02007]: invalid object declaration
┌─ tests/iota_mode/struct_with_key/key_struct_id_field_incorrect_type.move:4:9
│
3 │ struct S has key {
- │ --- The 'key' ability is used to declare objects in Iota
+ │ --- The 'key' ability is used to declare objects in IOTA
4 │ id: bool
│ ^^ ---- But found type: 'bool'
│ │
diff --git a/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_second_field_id.exp b/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_second_field_id.exp
index d6f55db8757..2c68e51dc9d 100644
--- a/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_second_field_id.exp
+++ b/external-crates/move/crates/move-compiler/tests/iota_mode/struct_with_key/key_struct_second_field_id.exp
@@ -2,7 +2,7 @@ error[Iota E02007]: invalid object declaration
┌─ tests/iota_mode/struct_with_key/key_struct_second_field_id.move:6:9
│
5 │ struct S has key {
- │ --- The 'key' ability is used to declare objects in Iota
+ │ --- The 'key' ability is used to declare objects in IOTA
6 │ flag: bool,
│ ^^^^ Invalid object 'S'. Structs with the 'key' ability must have 'id: iota::object::UID' as their first field
@@ -10,7 +10,7 @@ error[Iota E02007]: invalid object declaration
┌─ tests/iota_mode/struct_with_key/key_struct_second_field_id.move:11:9
│
10 │ struct R has key {
- │ --- The 'key' ability is used to declare objects in Iota
+ │ --- The 'key' ability is used to declare objects in IOTA
11 │ flag: bool,
│ ^^^^ Invalid object 'R'. Structs with the 'key' ability must have 'id: iota::object::UID' as their first field
diff --git a/external-crates/move/crates/move-model/src/model.rs b/external-crates/move/crates/move-model/src/model.rs
index b66d0bef83a..af13b12c7d1 100644
--- a/external-crates/move/crates/move-model/src/model.rs
+++ b/external-crates/move/crates/move-model/src/model.rs
@@ -159,7 +159,7 @@ impl Default for Loc {
}
}
-/// Return true if `f` is a Iota framework function declared in `module` with a
+/// Return true if `f` is an IOTA framework function declared in `module` with a
/// name in `names`
fn is_framework_function(f: &FunctionRef, module: &str, names: Vec<&str>) -> bool {
*f.module_id.address() == IOTA_FRAMEWORK_ADDRESS
diff --git a/external-crates/move/crates/move-stdlib/docs/address.md b/external-crates/move/crates/move-stdlib/docs/address.md
index 97d6130091e..ea6c4e8e395 100644
--- a/external-crates/move/crates/move-stdlib/docs/address.md
+++ b/external-crates/move/crates/move-stdlib/docs/address.md
@@ -19,7 +19,7 @@ platform-specific parameter.
## Function `length`
Should be converted to a native function.
-Current implementation only works for Iota.
+Current implementation only works for IOTA.
publicfunlength(): u64
diff --git a/external-crates/move/crates/move-stdlib/sources/address.move b/external-crates/move/crates/move-stdlib/sources/address.move
index 924a1d939dd..79e0c960c42 100644
--- a/external-crates/move/crates/move-stdlib/sources/address.move
+++ b/external-crates/move/crates/move-stdlib/sources/address.move
@@ -6,7 +6,7 @@
/// platform-specific parameter.
module std::address {
/// Should be converted to a native function.
- /// Current implementation only works for Iota.
+ /// Current implementation only works for IOTA.
public fun length(): u64 {
32
}
diff --git a/external-crates/move/documentation/book/src/abilities.md b/external-crates/move/documentation/book/src/abilities.md
index 5d6d99bc7b7..30c8afd457b 100644
--- a/external-crates/move/documentation/book/src/abilities.md
+++ b/external-crates/move/documentation/book/src/abilities.md
@@ -7,7 +7,7 @@ the notion of storage for the blockchain). This is implemented by gating access
instructions so that for a value to be used with the bytecode instruction, it must have the ability
required (if one is required at all—not every instruction is gated by an ability).
-For Iota, `key` is used to signify an [object](./abilities/object.md). Objects are the basic unit of
+For IOTA, `key` is used to signify an [object](./abilities/object.md). Objects are the basic unit of
storage where each object has a unique, 32-byte ID. `store` is then used to both indicate what data
can be stored inside of an object, and is also used to indicate what types can be transferred
outside of their defining module.
@@ -26,13 +26,13 @@ The four abilities are:
- Allows values of types with this ability to be popped/dropped.
- [`store`](#store)
- Allows values of types with this ability to exist inside a value in storage.
- - For Iota, `store` controls what data can be stored inside of an [object](./abilities/object.md).
+ - For IOTA, `store` controls what data can be stored inside of an [object](./abilities/object.md).
`store` also controls what types can be transferred outside of their defining module.
- [`key`](#key)
- Allows the type to serve as a "key" for storage. Ostensibly this means the value can be a
top-level value in storage; in other words, it does not need to be contained in another value to
be in storage.
- - For Iota, `key` is used to signify an [object](./abilities/object.md).
+ - For IOTA, `key` is used to signify an [object](./abilities/object.md).
### `copy`
@@ -66,7 +66,7 @@ directly gate an operation. Instead it gates the existence in storage when used
If a value has `store`, all values contained inside of that value have `store`.
-For Iota, `store` serves double duty. It controls what values can appear inside of an
+For IOTA, `store` serves double duty. It controls what values can appear inside of an
[object](./abilities/object.md), and what objects can be
[transferred](./abilities/object.md#transfer-rules) outside of their defining module.
@@ -80,7 +80,7 @@ ability.
If a value has `key`, all values contained inside of that value have `store`. This is the only
ability with this sort of asymmetry.
-For Iota, `key` is used to signify an [object](./abilities/object.md).
+For IOTA, `key` is used to signify an [object](./abilities/object.md).
## Builtin Types
diff --git a/external-crates/move/documentation/book/src/abilities/object.md b/external-crates/move/documentation/book/src/abilities/object.md
index 3caddf73f73..757084c8ef9 100644
--- a/external-crates/move/documentation/book/src/abilities/object.md
+++ b/external-crates/move/documentation/book/src/abilities/object.md
@@ -1,9 +1,9 @@
-# Iota Objects
+# IOTA Objects
-For Iota, `key` is used to signify an _object_. Objects the only way to store data in Iota--allowing
+For IOTA, `key` is used to signify an _object_. Objects the only way to store data in IOTA--allowing
the data to persist between transactions.
-For more details, see the Iota documentation on
+For more details, see the IOTA documentation on
- [The Object Model](https://docs.iota.io/concepts/object-model)
- [Move Rules for Objects](https://docs.iota.io/concepts/iota-move-concepts#global-unique)
@@ -40,4 +40,4 @@ module a::my_module {
`A` can only be transferred using the `iota::transfer::transfer` inside of `a::my_module`, while `B`
can be transferred anywhere using `iota::transfer::public_transfer`. These rules are enforced by a
-custom type system (bytecode verifier) rule in Iota.
+custom type system (bytecode verifier) rule in IOTA.
diff --git a/external-crates/move/documentation/book/src/abort-and-assert.md b/external-crates/move/documentation/book/src/abort-and-assert.md
index 88142ec1bcc..0bef6915aac 100644
--- a/external-crates/move/documentation/book/src/abort-and-assert.md
+++ b/external-crates/move/documentation/book/src/abort-and-assert.md
@@ -18,7 +18,7 @@ the current transaction (note though that this guarantee must be upheld by the a
specific deployment of Move). There is no mechanism for "catching" or otherwise handling an `abort`.
Luckily, in Move transactions are all or nothing, meaning any changes to storage are made all at
-once only if the transaction succeeds. For Iota, this means no objects are modified.
+once only if the transaction succeeds. For IOTA, this means no objects are modified.
Because of this transactional commitment of changes, after an abort there is no need to worry about
backing out changes. While this approach is lacking in flexibility, it is incredibly simple and
diff --git a/external-crates/move/documentation/book/src/coding-conventions.md b/external-crates/move/documentation/book/src/coding-conventions.md
index 3eed816e75c..7e2bdd9e75e 100644
--- a/external-crates/move/documentation/book/src/coding-conventions.md
+++ b/external-crates/move/documentation/book/src/coding-conventions.md
@@ -1 +1 @@
-See [Iota's Coding Conventions for Move](https://docs.iota.io/concepts/iota-move-concepts/conventions)
+See [IOTA's Coding Conventions for Move](https://docs.iota.io/concepts/iota-move-concepts/conventions)
diff --git a/external-crates/move/documentation/book/src/functions.md b/external-crates/move/documentation/book/src/functions.md
index f8e81fb866c..93336f68fef 100644
--- a/external-crates/move/documentation/book/src/functions.md
+++ b/external-crates/move/documentation/book/src/functions.md
@@ -130,7 +130,7 @@ module a::n {
`entry` functions may have restrictions on their parameters and return types. Although, these
restrictions are specific to each individual deployment of Move.
-[The documentation for `entry` functions on Iota can be found here.](https://docs.iota.io/concepts/iota-move-concepts/entry-functions).
+[The documentation for `entry` functions on IOTA can be found here.](https://docs.iota.io/concepts/iota-move-concepts/entry-functions).
### Name
diff --git a/external-crates/move/documentation/book/src/packages.md b/external-crates/move/documentation/book/src/packages.md
index f6c052dc314..f67d2e2fa9e 100644
--- a/external-crates/move/documentation/book/src/packages.md
+++ b/external-crates/move/documentation/book/src/packages.md
@@ -59,7 +59,7 @@ edition* = # e.g., "2024.alpha" to use the Move 2024 edition,
license* = # e.g., "MIT", "GPL", "Apache 2.0"
authors* = [,+] # e.g., ["Joe Smith (joesmith@noemail.com)", "John Snow (johnsnow@noemail.com)"]
-# Additional fields may be added to this section by external tools. E.g., on Iota the following sections are added:
+# Additional fields may be added to this section by external tools. E.g., on IOTA the following sections are added:
published-at* = "" # The address that the package is published at. Should be set after the first publication.
[dependencies] # (Optional section) Paths to dependencies
@@ -222,7 +222,7 @@ source = { local = "../local-dep" }
### The `[move.toolchain-version]` Section
As mentioned above, additional fields may be added to the lock file by external tools. For example,
-the Iota package manager adds toolchain version information to the lock file that can then be used
+the IOTA package manager adds toolchain version information to the lock file that can then be used
for on-chain source verification:
```
diff --git a/external-crates/move/documentation/book/src/primitive-types/address.md b/external-crates/move/documentation/book/src/primitive-types/address.md
index b0a38fbbd71..22a020ceb91 100644
--- a/external-crates/move/documentation/book/src/primitive-types/address.md
+++ b/external-crates/move/documentation/book/src/primitive-types/address.md
@@ -6,7 +6,7 @@ differentiate packages of [modules](../modules.md), where each package has its o
modules. Specific deployments of Move might also use the `address` value for
[storage](../abilities.md#key) operations.
-> For Iota, `address` is used to represent "accounts", and also objects via strong type wrappers
+> For IOTA, `address` is used to represent "accounts", and also objects via strong type wrappers
> (with `iota::object::UID` and `iota::object::ID`).
Although an `address` is a 256 bit integer under the hood, Move addresses are intentionally
diff --git a/external-crates/move/documentation/book/src/structs.md b/external-crates/move/documentation/book/src/structs.md
index 1c59c75f4da..8ddf35c96bf 100644
--- a/external-crates/move/documentation/book/src/structs.md
+++ b/external-crates/move/documentation/book/src/structs.md
@@ -475,4 +475,4 @@ module a::m {
Structs can be used to define storage schemas, but the details are different per deployment of Move.
See the documentation for the [`key` ability](./abilities.md#key) and
-[Iota objects](./abilities/object.md) for more details.
+[IOTA objects](./abilities/object.md) for more details.
diff --git a/iota-execution/README.md b/iota-execution/README.md
index 4648b13328e..cd53647744e 100644
--- a/iota-execution/README.md
+++ b/iota-execution/README.md
@@ -1,4 +1,4 @@
-# Iota Execution
+# IOTA Execution
The `iota-execution` crate is responsible for abstracting access to the
execution layer. It allows us to isolate big changes to the execution
@@ -10,7 +10,7 @@ The Execution Layer include:
- The metered verifier, used during signing.
- The VM, for executing transactions to effects.
-- The adapter, that integrates Move into Iota.
+- The adapter, that integrates Move into IOTA.
- Access to the state as seen by the VM, such as type layout
resolution.
diff --git a/iota-execution/cut/README.md b/iota-execution/cut/README.md
index 746bf03d000..c7aa0d68f9c 100644
--- a/iota-execution/cut/README.md
+++ b/iota-execution/cut/README.md
@@ -1,4 +1,4 @@
-# Iota Execution: Cut
+# IOTA Execution: Cut
The `cut` binary is responsible for making copies of sets of crates
from the repository. Use the `--dry-run` option to inspect the copies
diff --git a/iota-execution/latest/iota-adapter/src/adapter.rs b/iota-execution/latest/iota-adapter/src/adapter.rs
index 295facc2e8f..29fc004b12f 100644
--- a/iota-execution/latest/iota-adapter/src/adapter.rs
+++ b/iota-execution/latest/iota-adapter/src/adapter.rs
@@ -196,7 +196,7 @@ mod checked {
Ok(())
}
- /// Run both the Move verifier and the Iota verifier, checking just for
+ /// Run both the Move verifier and the IOTA verifier, checking just for
/// timeouts. Returns Ok(()) if the verifier completes within the module
/// meter limit and the ticks are successfully transfered to the package
/// limit (regardless of whether verification succeeds or not).
diff --git a/iota-execution/latest/iota-adapter/src/execution_engine.rs b/iota-execution/latest/iota-adapter/src/execution_engine.rs
index 26353e36d0a..9b9128532b6 100644
--- a/iota-execution/latest/iota-adapter/src/execution_engine.rs
+++ b/iota-execution/latest/iota-adapter/src/execution_engine.rs
@@ -734,10 +734,10 @@ mod checked {
/// Mints epoch rewards by creating both storage and computation rewards
/// using a `ProgrammableTransactionBuilder`. The function takes in the
/// `AdvanceEpochParams`, serializes the storage and computation
- /// charges, and invokes the reward creation function within the Iota
+ /// charges, and invokes the reward creation function within the IOTA
/// Prepares invocations for creating both storage and computation rewards
/// with a `ProgrammableTransactionBuilder` using the `AdvanceEpochParams`.
- /// The corresponding functions from the Iota framework can be invoked later
+ /// The corresponding functions from the IOTA framework can be invoked later
/// during execution of the programmable transaction.
fn mint_epoch_rewards_in_pt(
builder: &mut ProgrammableTransactionBuilder,
@@ -778,7 +778,7 @@ mod checked {
/// `mint_epoch_rewards_in_pt`, advances the epoch by setting up the
/// necessary arguments, such as epoch number, protocol version, storage
/// rebate, and slashing rate, and executing the `advance_epoch` function
- /// within the Iota system. Then, it destroys the storage rebates to
+ /// within the IOTA system. Then, it destroys the storage rebates to
/// complete the transaction.
pub fn construct_advance_epoch_pt(
mut builder: ProgrammableTransactionBuilder,
@@ -1018,7 +1018,7 @@ mod checked {
)
}
- /// This function adds a Move call to the Iota framework's
+ /// This function adds a Move call to the IOTA framework's
/// `authenticator_state_create` function, preparing the transaction for
/// execution.
fn setup_authenticator_state_create(
@@ -1112,7 +1112,7 @@ mod checked {
/// Sets up and executes a `ProgrammableTransaction` to update the
/// authenticator state. This function constructs a transaction that
- /// invokes the `authenticator_state_update` function from the Iota
+ /// invokes the `authenticator_state_update` function from the IOTA
/// framework, passing the authenticator state object and new active JWKS as
/// arguments. It then executes the transaction using the system
/// execution mode.
@@ -1160,7 +1160,7 @@ mod checked {
/// Configures a `ProgrammableTransactionBuilder` to expire authenticator
/// state by invoking the `authenticator_state_expire_jwks` function
- /// from the Iota framework. The function adds the necessary Move call
+ /// from the IOTA framework. The function adds the necessary Move call
/// with the authenticator state object and the minimum epoch as arguments.
fn setup_authenticator_state_expire(
mut builder: ProgrammableTransactionBuilder,
@@ -1186,7 +1186,7 @@ mod checked {
}
/// The function constructs a transaction that invokes
- /// the `randomness_state_update` function from the Iota framework,
+ /// the `randomness_state_update` function from the IOTA framework,
/// passing the randomness state object, the `randomness_round`,
/// and the `random_bytes` as arguments. It then executes the transaction
/// using the system execution mode.
diff --git a/iota-execution/latest/iota-adapter/src/gas_charger.rs b/iota-execution/latest/iota-adapter/src/gas_charger.rs
index be082050188..2264267db71 100644
--- a/iota-execution/latest/iota-adapter/src/gas_charger.rs
+++ b/iota-execution/latest/iota-adapter/src/gas_charger.rs
@@ -235,7 +235,7 @@ pub mod checked {
let total_size = temporary_store
.objects()
.iter()
- // don't charge for loading Iota Framework or Move stdlib
+ // don't charge for loading IOTA Framework or Move stdlib
.filter(|(id, _)| !is_system_package(**id))
.map(|(_, obj)| obj.object_size_for_gas_metering())
.sum();
diff --git a/iota-execution/latest/iota-adapter/src/programmable_transactions/execution.rs b/iota-execution/latest/iota-adapter/src/programmable_transactions/execution.rs
index 09ab7564c29..41d3dfe5679 100644
--- a/iota-execution/latest/iota-adapter/src/programmable_transactions/execution.rs
+++ b/iota-execution/latest/iota-adapter/src/programmable_transactions/execution.rs
@@ -875,9 +875,9 @@ mod checked {
}
/// Publishes a set of `CompiledModule` instances to the blockchain under
- /// the specified package ID and verifies them using the Iota bytecode
+ /// the specified package ID and verifies them using the IOTA bytecode
/// verifier. The modules are serialized and published via the VM,
- /// and the Iota verifier runs additional checks after the Move bytecode
+ /// and the IOTA verifier runs additional checks after the Move bytecode
/// verifier has passed.
fn publish_and_verify_modules(
context: &mut ExecutionContext<'_, '_, '_>,
@@ -903,9 +903,9 @@ mod checked {
.publish_module_bundle(new_module_bytes, AccountAddress::from(package_id))
.map_err(|e| context.convert_vm_error(e))?;
- // run the Iota verifier
+ // run the IOTA verifier
for module in modules {
- // Run Iota bytecode verifier, which runs some additional checks that assume the
+ // Run IOTA bytecode verifier, which runs some additional checks that assume the
// Move bytecode verifier has passed.
iota_verifier::verifier::iota_verify_module_unmetered(module, &BTreeMap::new())?;
}
@@ -1191,7 +1191,7 @@ mod checked {
.collect()
}
- /// Verifies that certain private functions in the Iota framework are not
+ /// Verifies that certain private functions in the IOTA framework are not
/// directly invoked. This function checks if the module and function
/// being called belong to restricted areas, such as the `iota::event`
/// or `iota::transfer` modules.
diff --git a/iota-execution/latest/iota-adapter/src/temporary_store.rs b/iota-execution/latest/iota-adapter/src/temporary_store.rs
index 87587c322c9..b549f8cec98 100644
--- a/iota-execution/latest/iota-adapter/src/temporary_store.rs
+++ b/iota-execution/latest/iota-adapter/src/temporary_store.rs
@@ -631,7 +631,7 @@ impl TemporaryStore<'_> {
assert!(
is_epoch_change,
"Immutable objects cannot be written, except for \
- Iota Framework/Move stdlib upgrades at epoch change boundaries"
+ IOTA Framework/Move stdlib upgrades at epoch change boundaries"
);
// Note: this assumes that the only immutable objects an epoch change
// tx can update are system packages,
diff --git a/iota-execution/latest/iota-move-natives/src/config.rs b/iota-execution/latest/iota-move-natives/src/config.rs
index ca0c7e1105e..07c20bf26aa 100644
--- a/iota-execution/latest/iota-move-natives/src/config.rs
+++ b/iota-execution/latest/iota-move-natives/src/config.rs
@@ -75,7 +75,7 @@ pub fn read_setting_impl(
_ => {
return Err(
PartialVMError::new(StatusCode::UNKNOWN_INVARIANT_VIOLATION_ERROR)
- .with_message("Iota verifier guarantees this is a struct".to_string()),
+ .with_message("IOTA verifier guarantees this is a struct".to_string()),
);
}
};
diff --git a/iota-execution/latest/iota-move-natives/src/dynamic_field.rs b/iota-execution/latest/iota-move-natives/src/dynamic_field.rs
index e087c44b1a7..7743b5a74b0 100644
--- a/iota-execution/latest/iota-move-natives/src/dynamic_field.rs
+++ b/iota-execution/latest/iota-move-natives/src/dynamic_field.rs
@@ -232,7 +232,7 @@ pub fn add_child_object(
_ => {
return Err(
PartialVMError::new(StatusCode::UNKNOWN_INVARIANT_VIOLATION_ERROR)
- .with_message("Iota verifier guarantees this is a struct".to_string()),
+ .with_message("IOTA verifier guarantees this is a struct".to_string()),
);
}
};
@@ -513,7 +513,7 @@ pub fn has_child_object_with_ty(
_ => {
return Err(
PartialVMError::new(StatusCode::UNKNOWN_INVARIANT_VIOLATION_ERROR)
- .with_message("Iota verifier guarantees this is a struct".to_string()),
+ .with_message("IOTA verifier guarantees this is a struct".to_string()),
);
}
};
diff --git a/iota-execution/latest/iota-move-natives/src/event.rs b/iota-execution/latest/iota-move-natives/src/event.rs
index ea09a3aa9b6..b3839efe16f 100644
--- a/iota-execution/latest/iota-move-natives/src/event.rs
+++ b/iota-execution/latest/iota-move-natives/src/event.rs
@@ -69,7 +69,7 @@ pub fn emit(
_ => {
return Err(
PartialVMError::new(StatusCode::UNKNOWN_INVARIANT_VIOLATION_ERROR)
- .with_message("Iota verifier guarantees this is a struct".to_string()),
+ .with_message("IOTA verifier guarantees this is a struct".to_string()),
);
}
};
diff --git a/iota-execution/latest/iota-move-natives/src/lib.rs b/iota-execution/latest/iota-move-natives/src/lib.rs
index 94ff40bd61f..3e8b0823dcd 100644
--- a/iota-execution/latest/iota-move-natives/src/lib.rs
+++ b/iota-execution/latest/iota-move-natives/src/lib.rs
@@ -1125,7 +1125,7 @@ pub(crate) fn get_tag_and_layouts(
_ => {
return Err(
PartialVMError::new(StatusCode::UNKNOWN_INVARIANT_VIOLATION_ERROR)
- .with_message("Iota verifier guarantees this is a struct".to_string()),
+ .with_message("IOTA verifier guarantees this is a struct".to_string()),
);
}
};
diff --git a/iota-execution/latest/iota-move-natives/src/transfer.rs b/iota-execution/latest/iota-move-natives/src/transfer.rs
index 81eb4f37c1f..c35f740f59f 100644
--- a/iota-execution/latest/iota-move-natives/src/transfer.rs
+++ b/iota-execution/latest/iota-move-natives/src/transfer.rs
@@ -244,7 +244,7 @@ fn object_runtime_transfer(
if !matches!(context.type_to_type_tag(&ty)?, TypeTag::Struct(_)) {
return Err(
PartialVMError::new(StatusCode::UNKNOWN_INVARIANT_VIOLATION_ERROR)
- .with_message("Iota verifier guarantees this is a struct".to_string()),
+ .with_message("IOTA verifier guarantees this is a struct".to_string()),
);
}
diff --git a/iota-execution/latest/iota-move-natives/src/types.rs b/iota-execution/latest/iota-move-natives/src/types.rs
index d5837407015..61d3b0e48ac 100644
--- a/iota-execution/latest/iota-move-natives/src/types.rs
+++ b/iota-execution/latest/iota-move-natives/src/types.rs
@@ -29,7 +29,7 @@ pub(crate) fn is_otw_struct(
// capitalized, and it has a single field of type bool, it means that it's a
// one-time witness type. The remaining properties of a one-time witness
// type are checked in the one_time_witness_verifier pass in
- // the Iota bytecode verifier (a type with this name and with a single bool
+ // the IOTA bytecode verifier (a type with this name and with a single bool
// field that does not have all the remaining properties of a one-time
// witness type will cause a verifier error).
matches!(
diff --git a/iota-execution/latest/iota-verifier/Cargo.toml b/iota-execution/latest/iota-verifier/Cargo.toml
index ac4c84687a3..a9282c2b242 100644
--- a/iota-execution/latest/iota-verifier/Cargo.toml
+++ b/iota-execution/latest/iota-verifier/Cargo.toml
@@ -5,7 +5,7 @@ authors = ["IOTA Foundation "]
edition = "2021"
license = "Apache-2.0"
publish = false
-description = "Move framework for Iota platform"
+description = "Move framework for IOTA platform"
[dependencies]
iota-protocol-config.workspace = true
diff --git a/iota-execution/latest/iota-verifier/src/id_leak_verifier.rs b/iota-execution/latest/iota-verifier/src/id_leak_verifier.rs
index 6df340594d7..adf8ecda646 100644
--- a/iota-execution/latest/iota-verifier/src/id_leak_verifier.rs
+++ b/iota-execution/latest/iota-verifier/src/id_leak_verifier.rs
@@ -2,11 +2,11 @@
// Modifications Copyright (c) 2024 IOTA Stiftung
// SPDX-License-Identifier: Apache-2.0
-//! Objects whose struct type has key ability represent Iota objects.
+//! Objects whose struct type has key ability represent IOTA objects.
//! They have unique IDs that should never be reused. This verifier makes
-//! sure that the id field of Iota objects never get leaked.
+//! sure that the id field of IOTA objects never get leaked.
//! Unpack is the only bytecode that could extract the id field out of
-//! a Iota object. From there, we track the flow of the value and make
+//! an IOTA object. From there, we track the flow of the value and make
//! sure it can never get leaked outside of the function. There are four
//! ways it can happen:
//! 1. Returned
diff --git a/iota-execution/latest/iota-verifier/src/one_time_witness_verifier.rs b/iota-execution/latest/iota-verifier/src/one_time_witness_verifier.rs
index ed956ac4e81..53ea3d80d64 100644
--- a/iota-execution/latest/iota-verifier/src/one_time_witness_verifier.rs
+++ b/iota-execution/latest/iota-verifier/src/one_time_witness_verifier.rs
@@ -42,8 +42,8 @@ pub fn verify_module(
// When verifying test functions, a check preventing by-hand instantiation of
// one-time withess is disabled
- // In Iota's framework code there is an exception to the one-time witness type
- // rule - we have a IOTA type in the iota module but it is instantiated
+ // In IOTA's framework code there is an exception to the one-time witness type
+ // rule - we have an IOTA type in the iota module but it is instantiated
// outside of the module initializer (in fact, the module has no
// initializer). The reason for it is that the IOTA coin is only instantiated
// during genesis. It is easiest to simply special-case this module particularly
diff --git a/iota-execution/latest/iota-verifier/src/private_generics.rs b/iota-execution/latest/iota-verifier/src/private_generics.rs
index bf7dbb30b20..2de2ffd081e 100644
--- a/iota-execution/latest/iota-verifier/src/private_generics.rs
+++ b/iota-execution/latest/iota-verifier/src/private_generics.rs
@@ -53,7 +53,7 @@ pub fn verify_module(module: &CompiledModule) -> Result<(), ExecutionError> {
if *module.address() == IOTA_FRAMEWORK_ADDRESS
&& module.name() == IdentStr::new(TEST_SCENARIO_MODULE_NAME).unwrap()
{
- // exclude test_module which is a test-only module in the Iota framework which
+ // exclude test_module which is a test-only module in the IOTA framework which
// "emulates" transactional execution and needs to allow test code to
// bypass private generics
return Ok(());
diff --git a/iota-execution/latest/iota-verifier/src/verifier.rs b/iota-execution/latest/iota-verifier/src/verifier.rs
index 7303e6a9ef1..adbb89b2b06 100644
--- a/iota-execution/latest/iota-verifier/src/verifier.rs
+++ b/iota-execution/latest/iota-verifier/src/verifier.rs
@@ -27,7 +27,7 @@ pub fn iota_verify_module_metered(
one_time_witness_verifier::verify_module(module, fn_info_map)
}
-/// Runs the Iota verifier and checks if the error counts as a Iota verifier
+/// Runs the IOTA verifier and checks if the error counts as an IOTA verifier
/// timeout NOTE: this function only check if the verifier error is a timeout
/// All other errors are ignored
pub fn iota_verify_module_metered_check_timeout_only(
@@ -35,7 +35,7 @@ pub fn iota_verify_module_metered_check_timeout_only(
fn_info_map: &FnInfoMap,
meter: &mut (impl Meter + ?Sized),
) -> Result<(), ExecutionError> {
- // Checks if the error counts as a Iota verifier timeout
+ // Checks if the error counts as an IOTA verifier timeout
if let Err(error) = iota_verify_module_metered(module, fn_info_map, meter) {
if matches!(
error.kind(),
diff --git a/kiosk/docs/creating_a_rule_guide.md b/kiosk/docs/creating_a_rule_guide.md
index dd96434af19..94f7e6f96bd 100644
--- a/kiosk/docs/creating_a_rule_guide.md
+++ b/kiosk/docs/creating_a_rule_guide.md
@@ -164,7 +164,7 @@ module examples::time_rule {
## Generalizing approach: Witness policy
-Iota Move has two main ways for authorizing an action: static - by using the Witness pattern, and dynamic - via the Capability pattern. With a small addition of type parameters to the Rule, it is possible to create a _generic Rule_ which will not only vary by configuration but also by the type of the Rule.
+IOTA Move has two main ways for authorizing an action: static - by using the Witness pattern, and dynamic - via the Capability pattern. With a small addition of type parameters to the Rule, it is possible to create a _generic Rule_ which will not only vary by configuration but also by the type of the Rule.
```move
module examples::witness_rule {
diff --git a/nre/ansible/README.md b/nre/ansible/README.md
index 5c1791b9987..30abf1ab264 100644
--- a/nre/ansible/README.md
+++ b/nre/ansible/README.md
@@ -1,4 +1,4 @@
-# Configure a Linux system as a IOTA Node using Ansible
+# Configure a Linux system as an IOTA Node using Ansible
This is a self-contained Ansible role for configuring a Linux system as an IOTA Node.
diff --git a/nre/ansible/roles/iota-node/tasks/main.yaml b/nre/ansible/roles/iota-node/tasks/main.yaml
index f039f982856..97b3fd0d323 100644
--- a/nre/ansible/roles/iota-node/tasks/main.yaml
+++ b/nre/ansible/roles/iota-node/tasks/main.yaml
@@ -17,5 +17,5 @@
ansible.builtin.include_tasks: "{{ role_path }}/tasks/monitoring.yaml"
when: skip_monitoring == false
-- name: Include Iota tasks
+- name: Include IOTA tasks
ansible.builtin.include_tasks: "{{ role_path }}/tasks/iota.yaml"
diff --git a/nre/dashboards/iota_mainnet_validators.json b/nre/dashboards/iota_mainnet_validators.json
index ccba9b70714..dde3b855701 100644
--- a/nre/dashboards/iota_mainnet_validators.json
+++ b/nre/dashboards/iota_mainnet_validators.json
@@ -1939,7 +1939,7 @@
]
},
"timezone": "America/Los_Angeles",
- "title": "Iota Mainnet Validators",
+ "title": "IOTA Mainnet Validators",
"uid": "e3f62ded-4845-497c-b879-3f958b8561c2",
"version": 27,
"weekStart": ""
diff --git a/nre/helm/README.md b/nre/helm/README.md
index d77e77806ad..be5d97f44e5 100644
--- a/nre/helm/README.md
+++ b/nre/helm/README.md
@@ -1,6 +1,6 @@
# Helm Charts
-This directory contains helm charts to deploy Iota RPC2.0 infra. These charts are intended to be starting points for RPC2.0 providers. Not everything here will necessarily work out of the box to fit each provider's need. Some of this infra has some scope/setup needed outside of these charts. It's encouraged to clone these files and tweak to your infra needs.
+This directory contains helm charts to deploy IOTA RPC2.0 infra. These charts are intended to be starting points for RPC2.0 providers. Not everything here will necessarily work out of the box to fit each provider's need. Some of this infra has some scope/setup needed outside of these charts. It's encouraged to clone these files and tweak to your infra needs.
(Currently) Out of Scope of these Helm charts:
diff --git a/nre/helm/graphql/values.yaml b/nre/helm/graphql/values.yaml
index d0fb1fb374c..8e0b91a691d 100644
--- a/nre/helm/graphql/values.yaml
+++ b/nre/helm/graphql/values.yaml
@@ -20,7 +20,7 @@ command: [
"--config",
"/opt/iota/config/graphql.toml",
"--ide-title",
- "Iota RPC2.0 GraphQL",
+ "IOTA RPC2.0 GraphQL",
]
env:
diff --git a/nre/k8s/iota-graphql-deployment.yaml b/nre/k8s/iota-graphql-deployment.yaml
index a96694112a5..6afe7b0ec73 100644
--- a/nre/k8s/iota-graphql-deployment.yaml
+++ b/nre/k8s/iota-graphql-deployment.yaml
@@ -36,7 +36,7 @@ spec:
- --config
- /opt/iota/config/iota-graphql.toml
- --ide-title
- - Iota Mainnet GraphQL
+ - IOTA Mainnet GraphQL
env:
- name: RUST_BACKTRACE
value: "1"
diff --git a/nre/ssfn_guide.md b/nre/ssfn_guide.md
index 3aeec9f0108..cc3eea14046 100644
--- a/nre/ssfn_guide.md
+++ b/nre/ssfn_guide.md
@@ -1,6 +1,6 @@
State sync fullnodes are in essence just regular fullnodes, with a few tweaks.
-I won't detail setting up a Iota fullnode here, just the ways in which state sync fullnodes differ:
+I won't detail setting up an IOTA fullnode here, just the ways in which state sync fullnodes differ:
1. State sync fullnodes should be peered directly to a validator, these are the only nodes in the network that explictly set validators as their peer
diff --git a/nre/systemd/README.md b/nre/systemd/README.md
index 5a93e608618..2d3fa06bb46 100644
--- a/nre/systemd/README.md
+++ b/nre/systemd/README.md
@@ -1,4 +1,4 @@
-# Run a IOTA Node using Systemd
+# Run an IOTA Node using Systemd
Tested using:
diff --git a/nre/validator_tasks.md b/nre/validator_tasks.md
index 80547c3ee23..4c8e44f91de 100644
--- a/nre/validator_tasks.md
+++ b/nre/validator_tasks.md
@@ -35,7 +35,7 @@ This document focuses on running the IOTA Node software as a Validator.
## Requirements
-To run an Iota Validator a machine with the following is required:
+To run an IOTA Validator a machine with the following is required:
- CPU: 24 physical cores (or 48 virtual cores)
- Memory: 128 GB
@@ -76,7 +76,7 @@ Configuration templates are available here:
## Connectivity
-Iota Node uses the following ports by default:
+IOTA Node uses the following ports by default:
| protocol/port | reachability | purpose |
| ------------- | ---------------- | --------------------------------- |
@@ -136,7 +136,7 @@ sudo sysctl -a | egrep [rw]mem
## Storage
-All Iota Node-related data is stored by default under `/opt/iota/db/`. This is controlled in the Iota Node configuration
+All IOTA Node-related data is stored by default under `/opt/iota/db/`. This is controlled in the IOTA Node configuration
file.
```shell
@@ -147,7 +147,7 @@ db-path: /opt/iota/db/authorities_db
Ensure that you have an appropriately sized disk mounted for the database to write to.
-- To check the size of the local Iota Node databases:
+- To check the size of the local IOTA Node databases:
```shell
du -sh /opt/iota/db/
@@ -155,7 +155,7 @@ du -sh /opt/iota/db/authorities_db
du -sh /opt/iota/db/consensus_db
```
-- To delete the local Iota Node databases:
+- To delete the local IOTA Node databases:
```shell
sudo systemctl stop iota-node
@@ -164,7 +164,7 @@ sudo rm -rf /opt/iota/db/authorities_db /opt/iota/db/consensus_db
## Key Management
-The following keys are used by Iota Node:
+The following keys are used by IOTA Node:
| key | scheme | purpose |
| ------------- | -------- | ------------------------------------------------------- |
@@ -173,13 +173,13 @@ The following keys are used by Iota Node:
| network.key | ed25519 | consensus primary, iota state sync |
| protocol.key | ed25519 | key to sign mysticeti consensus blocks |
-These are configured in the [Iota Node configuration file](#configuration).
+These are configured in the [IOTA Node configuration file](#configuration).
## Monitoring
### Metrics
-Iota Node exposes metrics via a local HTTP interface. These can be scraped for use in a central monitoring system as
+IOTA Node exposes metrics via a local HTTP interface. These can be scraped for use in a central monitoring system as
well as viewed directly from the node.
- View all metrics:
@@ -194,7 +194,7 @@ curl -s http://localhost:9184/metrics
curl http://localhost:9184/metrics | grep
```
-Iota Node also pushes metrics to a central Iota metrics proxy.
+IOTA Node also pushes metrics to a central IOTA metrics proxy.
### Logs
@@ -208,7 +208,7 @@ Depending on your deployment method, these will be configured in the following p
- If using Systemd natively, [here](./systemd/iota-node.service)
- If using Docker Compose, [here](./docker/docker-compose.yaml)
-To view and follow the Iota Node logs:
+To view and follow the IOTA Node logs:
```shell
journalctl -u iota-node -f
@@ -238,7 +238,7 @@ curl localhost:1337/logging -d "info"
## Software Updates
-When an update is required to the Iota Node software the following process can be used. Follow the relevant Systemd or
+When an update is required to the IOTA Node software the following process can be used. Follow the relevant Systemd or
Docker Compose runbook depending on your deployment type. It is highly unlikely that you will want to restart with a
clean database.
@@ -247,7 +247,7 @@ clean database.
## State Sync
-Checkpoints in Iota contain the permanent history of the network. They are comparable to blocks in other blockchains
+Checkpoints in IOTA contain the permanent history of the network. They are comparable to blocks in other blockchains
with the biggest difference being that they are lagging instead of leading. All transactions are final and executed
prior to being included in a checkpoint.
@@ -257,7 +257,7 @@ Inter-validator state sync is always permitted, however, there are controls avai
allowed to sync from a specific validator.
The default and recommended `max-concurrent-connections: 0` configuration does not affect inter-validator state sync,
-but will restrict all fullnodes from syncing. The Iota Node [configuration](#configuration) can be modified to allow a
+but will restrict all fullnodes from syncing. The IOTA Node [configuration](#configuration) can be modified to allow a
known fullnode to sync from a validator:
```shell
@@ -294,13 +294,13 @@ Other metadata (keys, addresses etc) only come into effect at the next epoch.
To update metadata, a validator makes a MoveCall transaction that interacts with the System Object. For example:
-1. To update the name to `new_validator_name`, use the Iota Client CLI to call `iota_system::update_validator_name`:
+1. To update the name to `new_validator_name`, use the IOTA Client CLI to call `iota_system::update_validator_name`:
```shell
iota client call --package 0x3 --module iota_system --function update_validator_name --args 0x5 \"new_validator_name\" --gas-budget 10000
```
-2. To update the p2p address starting from next epoch to `/ip4/192.168.1.1`, use the Iota Client CLI to call
+2. To update the p2p address starting from next epoch to `/ip4/192.168.1.1`, use the IOTA Client CLI to call
`iota_system::update_validator_next_epoch_p2p_address`:
```shell
@@ -319,7 +319,7 @@ validator.
Upon creating a `Validator`, an `UnverifiedValidatorOperationCap` is created as well and transferred to the validator
address. The holder of this `Cap` object (short for "Capability") therefore could perform operational actions for this
validator. To authorize another address to conduct these operations, a validator transfers the object to another address
-that they control. The transfer can be done by using the Iota Client CLI: `iota client transfer`.
+that they control. The transfer can be done by using the IOTA Client CLI: `iota client transfer`.
To rotate the delegatee address or revoke the authorization, the current holder of `Cap` transfers it to another
address. In the event of compromised or lost keys, the validator could create a new `Cap` object to invalidate the
@@ -332,7 +332,7 @@ iota client call --package 0x3 --module iota_system --function rotate_operation_
By default the new `Cap` object is transferred to the validator address, which then could be transferred to the new
delegatee address. At this point, the old `Cap` becomes invalidated and no longer represents eligibility.
-To get the current valid `Cap` object's ID of a validator, use the Iota Client CLI `iota client objects` command after
+To get the current valid `Cap` object's ID of a validator, use the IOTA Client CLI `iota client objects` command after
setting the holder as the active address.
@@ -351,7 +351,7 @@ Once a validator is reported by `2f + 1` other validators by voting power, their
### Joining the Validator Set
-In order for an Iota address to join the validator set, they need to first sign up as a validator candidate by calling
+In order for an IOTA address to join the validator set, they need to first sign up as a validator candidate by calling
`iota_system::request_add_validator_candidate` with their metadata and initial configs:
```shell
diff --git a/nre/validator_tool.md b/nre/validator_tool.md
index 2dd32ef695c..bf37f25b177 100644
--- a/nre/validator_tool.md
+++ b/nre/validator_tool.md
@@ -26,16 +26,16 @@ This document is focused on using Validator Tool.
export IOTA_BINARY="$(pwd)/target/debug/iota"
-3. Run the following command to set up your Iota account and CLI environment.
+3. Run the following command to set up your IOTA account and CLI environment.
- 1. If this is the first time running this program, it will ask you to provide a Iota Fullnode Server URL and a meaningful environment alias. It will also generate a random key pair in `iota.keystore` and a config `client.yaml`. Swap in your validator account key if you already have one.
+ 1. If this is the first time running this program, it will ask you to provide an IOTA Fullnode Server URL and a meaningful environment alias. It will also generate a random key pair in `iota.keystore` and a config `client.yaml`. Swap in your validator account key if you already have one.
2. If you already set it up, simply make sure
a. `rpc` is correct in `client.yaml`.
b. `active_address` is correct in `client.yaml`.
b. `iota.keystore` contains your account key pair.
- If at this point you can't find where `client.yaml` or `iota.keystore` is or have other questions, read [Iota Client CLI tutorial](https://docs.iota.org/references/cli/client).
+ If at this point you can't find where `client.yaml` or `iota.keystore` is or have other questions, read [IOTA Client CLI tutorial](https://docs.iota.org/references/cli/client).
```bash
$IOTA_BINARY client
diff --git a/scripts/generate-release-notes.sh b/scripts/generate-release-notes.sh
index ed757cc67e2..7505df6d8be 100755
--- a/scripts/generate-release-notes.sh
+++ b/scripts/generate-release-notes.sh
@@ -14,7 +14,7 @@ else
new_branch=$2
fi
-echo -e "Iota Protocol Version in this release: XX\n"
+echo -e "IOTA Protocol Version in this release: XX\n"
for pr_number in $(git log --grep "\[x\]" --pretty=oneline --abbrev-commit origin/"${new_branch}"...origin/"${prev_branch}" -- crates dashboards doc docker external-crates kiosk nre iota-execution | grep -o '#[0-9]\+' | grep -o '[0-9]\+')
do
pr_body=$(gh api -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" /repos/iotaledger/iota/pulls/"${pr_number}" --jq ".body")
diff --git a/scripts/slipstream/patches_slipstream/fix_invalid_comments.patch b/scripts/slipstream/patches_slipstream/fix_invalid_comments.patch
index bbe7fc67bc7..a868b1979cd 100644
--- a/scripts/slipstream/patches_slipstream/fix_invalid_comments.patch
+++ b/scripts/slipstream/patches_slipstream/fix_invalid_comments.patch
@@ -77,7 +77,7 @@ index 4522fe20..c7ad18c6 100644
@@ -67,6 +70,7 @@ pub trait IndexerApi {
) -> RpcResult;
- /// Subscribe to a stream of Iota event
+ /// Subscribe to a stream of IOTA event
+ #[rustfmt::skip]
#[subscription(name = "subscribeEvent", item = IotaEvent)]
fn subscribe_event(
@@ -149,7 +149,7 @@ index e77620d8..b28b4af6 100644
@@ -35,6 +36,7 @@ pub trait TransactionBuilder {
) -> RpcResult;
- /// Create an unsigned transaction to send IOTA coin object to a Iota address. The IOTA object is also used as the gas object.
+ /// Create an unsigned transaction to send IOTA coin object to an IOTA address. The IOTA object is also used as the gas object.
+ #[rustfmt::skip]
#[method(name = "transferIota")]
async fn transfer_iota(
diff --git a/scripts/update_fastcrypto.sh b/scripts/update_fastcrypto.sh
index b5a6bb9d784..b7f67542810 100755
--- a/scripts/update_fastcrypto.sh
+++ b/scripts/update_fastcrypto.sh
@@ -4,7 +4,7 @@
# SPDX-License-Identifier: Apache-2.0
# shellcheck disable=SC2181
-# This script attempts to update the Fastcrypto pointer in Iota
+# This script attempts to update the Fastcrypto pointer in IOTA
# It is expected to fail in some cases, notably when those updates require code changes
set -e
set -eo pipefail
@@ -54,7 +54,7 @@ function current_fc_revision() {
fi
done
- [[ -n "$not_equal" ]] && echo "Different values found for the current Fastcrypto revision in Iota, aborting" && exit 1
+ [[ -n "$not_equal" ]] && echo "Different values found for the current Fastcrypto revision in IOTA, aborting" && exit 1
echo "$watermark"
}
@@ -65,7 +65,7 @@ check_gnu_grep
CURRENT_FC=$(current_fc_revision)
LATEST_FC=$(latest_fc_revision)
if [[ "$CURRENT_FC" != "$LATEST_FC" ]]; then
- echo "About to replace $CURRENT_FC with $LATEST_FC as the fastcrypto pointer in Iota"
+ echo "About to replace $CURRENT_FC with $LATEST_FC as the fastcrypto pointer in IOTA"
else
exit 0
fi
diff --git a/scripts/update_move.sh b/scripts/update_move.sh
index 2aafeb16105..81f480b912b 100755
--- a/scripts/update_move.sh
+++ b/scripts/update_move.sh
@@ -48,7 +48,7 @@ COMMIT=$(git ls-remote "$REMOTE" "$BRANCH" | cut -f1)
REPO=$(git rev-parse --show-toplevel)
>&2 echo "Updating Move Cargo dependency"
->&2 echo "Iota Repo : $REPO"
+>&2 echo "IOTA Repo : $REPO"
>&2 echo "Move Repo : $REMOTE"
>&2 echo "Move Branch : $BRANCH"
>&2 echo "Move Commit : $COMMIT"
diff --git a/sdk/graphql-transport/src/generated/queries.ts b/sdk/graphql-transport/src/generated/queries.ts
index 58466fbde89..695dcdaada3 100644
--- a/sdk/graphql-transport/src/generated/queries.ts
+++ b/sdk/graphql-transport/src/generated/queries.ts
@@ -1150,7 +1150,7 @@ export type DryRunReturn = {
* an object stored in this kind of field will be considered wrapped and
* will not be accessible directly via its ID by external tools (explorers,
* wallets, etc) accessing storage.
- * 2) Dynamic Object Fields values must be Iota objects (have the `key` and
+ * 2) Dynamic Object Fields values must be IOTA objects (have the `key` and
* `store` abilities, and id: UID as the first field), but will still be
* directly accessible off-chain via their object ID after being attached.
*/
@@ -1254,7 +1254,7 @@ export type EndOfEpochTransactionKindEdge = {
};
/**
- * Operation of the Iota network is temporally partitioned into non-overlapping
+ * Operation of the IOTA network is temporally partitioned into non-overlapping
* epochs, and the network aims to keep epochs roughly the same duration as
* each other. During a particular epoch the following data is fixed:
*
@@ -1372,7 +1372,7 @@ export type Epoch = {
/**
- * Operation of the Iota network is temporally partitioned into non-overlapping
+ * Operation of the IOTA network is temporally partitioned into non-overlapping
* epochs, and the network aims to keep epochs roughly the same duration as
* each other. During a particular epoch the following data is fixed:
*
@@ -1389,7 +1389,7 @@ export type EpochCheckpointsArgs = {
/**
- * Operation of the Iota network is temporally partitioned into non-overlapping
+ * Operation of the IOTA network is temporally partitioned into non-overlapping
* epochs, and the network aims to keep epochs roughly the same duration as
* each other. During a particular epoch the following data is fixed:
*
@@ -1922,7 +1922,7 @@ export type MergeCoinsTransaction = {
};
/**
- * Abilities are keywords in Iota Move that define how types behave at the
+ * Abilities are keywords in IOTA Move that define how types behave at the
* compiler level.
*/
export enum MoveAbility {
@@ -2959,7 +2959,7 @@ export enum MoveVisibility {
Public = 'PUBLIC'
}
-/** Mutations are used to write to the Iota network. */
+/** Mutations are used to write to the IOTA network. */
export type Mutation = {
__typename?: 'Mutation';
/**
@@ -2987,14 +2987,14 @@ export type Mutation = {
};
-/** Mutations are used to write to the Iota network. */
+/** Mutations are used to write to the IOTA network. */
export type MutationExecuteTransactionBlockArgs = {
signatures: Array;
txBytes: Scalars['String']['input'];
};
/**
- * An object in Iota is a package (set of Move bytecode modules) or object
+ * An object in IOTA is a package (set of Move bytecode modules) or object
* (typed data structure with fields) with additional metadata detailing its
* id, version, transaction digest, owner field indicating how this object can
* be accessed.
@@ -3122,7 +3122,7 @@ export type Object = IObject & IOwner & {
/**
- * An object in Iota is a package (set of Move bytecode modules) or object
+ * An object in IOTA is a package (set of Move bytecode modules) or object
* (typed data structure with fields) with additional metadata detailing its
* id, version, transaction digest, owner field indicating how this object can
* be accessed.
@@ -3133,7 +3133,7 @@ export type ObjectBalanceArgs = {
/**
- * An object in Iota is a package (set of Move bytecode modules) or object
+ * An object in IOTA is a package (set of Move bytecode modules) or object
* (typed data structure with fields) with additional metadata detailing its
* id, version, transaction digest, owner field indicating how this object can
* be accessed.
@@ -3147,7 +3147,7 @@ export type ObjectBalancesArgs = {
/**
- * An object in Iota is a package (set of Move bytecode modules) or object
+ * An object in IOTA is a package (set of Move bytecode modules) or object
* (typed data structure with fields) with additional metadata detailing its
* id, version, transaction digest, owner field indicating how this object can
* be accessed.
@@ -3162,7 +3162,7 @@ export type ObjectCoinsArgs = {
/**
- * An object in Iota is a package (set of Move bytecode modules) or object
+ * An object in IOTA is a package (set of Move bytecode modules) or object
* (typed data structure with fields) with additional metadata detailing its
* id, version, transaction digest, owner field indicating how this object can
* be accessed.
@@ -3173,7 +3173,7 @@ export type ObjectDynamicFieldArgs = {
/**
- * An object in Iota is a package (set of Move bytecode modules) or object
+ * An object in IOTA is a package (set of Move bytecode modules) or object
* (typed data structure with fields) with additional metadata detailing its
* id, version, transaction digest, owner field indicating how this object can
* be accessed.
@@ -3187,7 +3187,7 @@ export type ObjectDynamicFieldsArgs = {
/**
- * An object in Iota is a package (set of Move bytecode modules) or object
+ * An object in IOTA is a package (set of Move bytecode modules) or object
* (typed data structure with fields) with additional metadata detailing its
* id, version, transaction digest, owner field indicating how this object can
* be accessed.
@@ -3198,7 +3198,7 @@ export type ObjectDynamicObjectFieldArgs = {
/**
- * An object in Iota is a package (set of Move bytecode modules) or object
+ * An object in IOTA is a package (set of Move bytecode modules) or object
* (typed data structure with fields) with additional metadata detailing its
* id, version, transaction digest, owner field indicating how this object can
* be accessed.
@@ -3213,7 +3213,7 @@ export type ObjectObjectsArgs = {
/**
- * An object in Iota is a package (set of Move bytecode modules) or object
+ * An object in IOTA is a package (set of Move bytecode modules) or object
* (typed data structure with fields) with additional metadata detailing its
* id, version, transaction digest, owner field indicating how this object can
* be accessed.
@@ -3229,7 +3229,7 @@ export type ObjectReceivedTransactionBlocksArgs = {
/**
- * An object in Iota is a package (set of Move bytecode modules) or object
+ * An object in IOTA is a package (set of Move bytecode modules) or object
* (typed data structure with fields) with additional metadata detailing its
* id, version, transaction digest, owner field indicating how this object can
* be accessed.
@@ -3818,7 +3818,7 @@ export type Query = {
* field when its parent was at `rootVersion`.
*
* If `rootVersion` is omitted, dynamic fields will be from a consistent
- * snapshot of the Iota state at the latest checkpoint known to the
+ * snapshot of the IOTA state at the latest checkpoint known to the
* GraphQL RPC. Similarly, `Owner.asObject` will return the object's
* version at the latest checkpoint.
*/
diff --git a/sdk/kiosk/README.md b/sdk/kiosk/README.md
index 39ed8172f18..b42e73c0dab 100644
--- a/sdk/kiosk/README.md
+++ b/sdk/kiosk/README.md
@@ -27,7 +27,7 @@ You can follow this example to create a KioskClient.
import { KioskClient } from '@iota/kiosk';
import { getFullnodeUrl, IotaClient, Network } from '@iota/iota-sdk/client';
-// We need a IOTA Client. You can re-use the IotaClient of your project
+// We need an IOTA Client. You can re-use the IotaClient of your project
// (it's not recommended to create a new one).
const client = new IotaClient({ url: getFullnodeUrl(Network.Testnet) });
diff --git a/sdk/typescript/src/client/client.ts b/sdk/typescript/src/client/client.ts
index e1fd627a2bc..0133cdabdf1 100644
--- a/sdk/typescript/src/client/client.ts
+++ b/sdk/typescript/src/client/client.ts
@@ -134,7 +134,7 @@ export class IotaClient {
}
/**
- * Establish a connection to a IOTA RPC endpoint
+ * Establish a connection to an IOTA RPC endpoint
*
* @param options configuration options for the API Client
*/
diff --git a/sdk/typescript/src/client/types/generated.ts b/sdk/typescript/src/client/types/generated.ts
index 26c4f5a9d2f..2018c763413 100644
--- a/sdk/typescript/src/client/types/generated.ts
+++ b/sdk/typescript/src/client/types/generated.ts
@@ -276,7 +276,7 @@ export interface IotaEvent {
packageId: string;
/** Parsed json value of the event */
parsedJson: unknown;
- /** Sender's Iota address. */
+ /** Sender's IOTA address. */
sender: string;
/** UTC timestamp in milliseconds since epoch (1/1/1970) */
timestampMs?: string | null;
@@ -353,7 +353,7 @@ export type IotaEventFilter =
Or: [IotaEventFilter, IotaEventFilter];
};
/**
- * Unique ID of a Iota Event, the ID is a combination of tx seq number and event seq number, the ID is
+ * Unique ID of an IOTA Event, the ID is a combination of tx seq number and event seq number, the ID is
* local to this particular fullnode and will be different from other fullnode.
*/
export interface EventId {
diff --git a/sdk/typescript/src/client/types/params.ts b/sdk/typescript/src/client/types/params.ts
index 6d6a88d5b48..8790b5a12d3 100644
--- a/sdk/typescript/src/client/types/params.ts
+++ b/sdk/typescript/src/client/types/params.ts
@@ -182,12 +182,12 @@ export interface TryMultiGetPastObjectsParams {
}
/** Return the total coin balance for all coin type, owned by the address owner. */
export interface GetAllBalancesParams {
- /** the owner's Iota address */
+ /** the owner's IOTA address */
owner: string;
}
/** Return all Coin objects owned by an address. */
export interface GetAllCoinsParams {
- /** the owner's Iota address */
+ /** the owner's IOTA address */
owner: string;
/** optional paging cursor */
cursor?: string | null | undefined;
@@ -199,7 +199,7 @@ export interface GetAllEpochAddressMetricsParams {
}
/** Return the total coin balance for one coin type, owned by the address owner. */
export interface GetBalanceParams {
- /** the owner's Iota address */
+ /** the owner's IOTA address */
owner: string;
/**
* optional type names for the coin (e.g., 0x168da5bf1f48dafc111b0a488fa454aca95e0b5e::usdc::USDC),
@@ -217,7 +217,7 @@ export interface GetCoinMetadataParams {
}
/** Return all Coin<`coin_type`> objects owned by an address. */
export interface GetCoinsParams {
- /** the owner's Iota address */
+ /** the owner's IOTA address */
owner: string;
/**
* optional type name for the coin (e.g., 0x168da5bf1f48dafc111b0a488fa454aca95e0b5e::usdc::USDC),
@@ -287,7 +287,7 @@ export interface GetNetworkMetricsParams {}
* been updated when the next page is fetched. Please use iotax_queryObjects if this is a concern.
*/
export type GetOwnedObjectsParams = {
- /** the owner's Iota address */
+ /** the owner's IOTA address */
owner: string;
/**
* An optional paging cursor. If provided, the query will start from the next item after the specified
@@ -350,7 +350,7 @@ export type QueryTransactionBlocksParams = {
/** query result ordering, default to false (ascending order), oldest record first. */
order?: 'ascending' | 'descending' | null | undefined;
} & RpcTypes.IotaTransactionBlockResponseQuery;
-/** Subscribe to a stream of Iota event */
+/** Subscribe to a stream of IOTA event */
export interface SubscribeEventParams {
/**
* The filter criteria of the event stream. See
@@ -359,13 +359,13 @@ export interface SubscribeEventParams {
*/
filter: RpcTypes.IotaEventFilter;
}
-/** Subscribe to a stream of Iota transaction effects */
+/** Subscribe to a stream of IOTA transaction effects */
export interface SubscribeTransactionParams {
filter: RpcTypes.TransactionFilter;
}
/** Create an unsigned batched transaction. */
export interface UnsafeBatchTransactionParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
/** list of transaction request parameters */
singleTransactionParams: RpcTypes.RPCTransactionRequestParams[];
@@ -381,7 +381,7 @@ export interface UnsafeBatchTransactionParams {
}
/** Create an unsigned transaction to merge multiple coins into one coin. */
export interface UnsafeMergeCoinsParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
/** the coin object to merge into, this coin will remain after the transaction */
primaryCoin: string;
@@ -403,7 +403,7 @@ export interface UnsafeMergeCoinsParams {
* function in the module of a given package.
*/
export interface UnsafeMoveCallParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
/** the Move package ID, e.g. `0x2` */
packageObjectId: string;
@@ -438,9 +438,9 @@ export interface UnsafeMoveCallParams {
* auto-select one.
*/
export interface UnsafePayParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
- /** the Iota coins to be used in this transaction */
+ /** the IOTA coins to be used in this transaction */
inputCoins: string[];
/** the recipients' addresses, the length of this vector must be the same as amounts. */
recipients: string[];
@@ -462,9 +462,9 @@ export interface UnsafePayParams {
* sum(input_coins) - actual_gas_cost. 4. all other input coins other than the first are deleted.
*/
export interface UnsafePayAllIotaParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
- /** the Iota coins to be used in this transaction, including the coin for gas payment. */
+ /** the IOTA coins to be used in this transaction, including the coin for gas payment. */
inputCoins: string[];
/** the recipient address, */
recipient: string;
@@ -481,9 +481,9 @@ export interface UnsafePayAllIotaParams {
* than the first one are deleted.
*/
export interface UnsafePayIotaParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
- /** the Iota coins to be used in this transaction, including the coin for gas payment. */
+ /** the IOTA coins to be used in this transaction, including the coin for gas payment. */
inputCoins: string[];
/** the recipients' addresses, the length of this vector must be the same as amounts. */
recipients: string[];
@@ -494,7 +494,7 @@ export interface UnsafePayIotaParams {
}
/** Create an unsigned transaction to publish a Move package. */
export interface UnsafePublishParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
sender: string;
/** the compiled bytes of a Move package */
compiledModules: string[];
@@ -510,13 +510,13 @@ export interface UnsafePublishParams {
}
/** Add stake to a validator's staking pool using multiple coins and amount. */
export interface UnsafeRequestAddStakeParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
/** Coin object to stake */
coins: string[];
/** stake amount */
amount?: string | null | undefined;
- /** the validator's Iota address */
+ /** the validator's IOTA address */
validator: string;
/**
* gas object to be used in this transaction, node will pick one from the signer's possession if not
@@ -528,11 +528,11 @@ export interface UnsafeRequestAddStakeParams {
}
/** Add timelocked stake to a validator's staking pool using multiple balances and amount. */
export interface UnsafeRequestAddTimelockedStakeParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
/** TimeLock> object to stake */
lockedBalance: string;
- /** the validator's Iota address */
+ /** the validator's IOTA address */
validator: string;
/** gas object to be used in this transaction */
gas: string;
@@ -541,7 +541,7 @@ export interface UnsafeRequestAddTimelockedStakeParams {
}
/** Withdraw stake from a validator's staking pool. */
export interface UnsafeRequestWithdrawStakeParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
/** StakedIota object ID */
stakedIota: string;
@@ -555,7 +555,7 @@ export interface UnsafeRequestWithdrawStakeParams {
}
/** Withdraw timelocked stake from a validator's staking pool. */
export interface UnsafeRequestWithdrawTimelockedStakeParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
/** TimelockedStakedIota object ID */
timelockedStakedIota: string;
@@ -566,7 +566,7 @@ export interface UnsafeRequestWithdrawTimelockedStakeParams {
}
/** Create an unsigned transaction to split a coin object into multiple coins. */
export interface UnsafeSplitCoinParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
/** the coin object to be spilt */
coinObjectId: string;
@@ -582,7 +582,7 @@ export interface UnsafeSplitCoinParams {
}
/** Create an unsigned transaction to split a coin object into multiple equal-size coins. */
export interface UnsafeSplitCoinEqualParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
/** the coin object to be spilt */
coinObjectId: string;
@@ -597,17 +597,17 @@ export interface UnsafeSplitCoinEqualParams {
gasBudget: string;
}
/**
- * Create an unsigned transaction to send IOTA coin object to a Iota address. The IOTA object is also
+ * Create an unsigned transaction to send IOTA coin object to an IOTA address. The IOTA object is also
* used as the gas object.
*/
export interface UnsafeTransferIotaParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
- /** the Iota coin object to be used in this transaction */
+ /** the IOTA coin object to be used in this transaction */
iotaObjectId: string;
/** the gas budget, the transaction will fail if the gas cost exceed the budget */
gasBudget: string;
- /** the recipient's Iota address */
+ /** the recipient's IOTA address */
recipient: string;
/** the amount to be split out and transferred */
amount?: string | null | undefined;
@@ -617,7 +617,7 @@ export interface UnsafeTransferIotaParams {
* must allow public transfers
*/
export interface UnsafeTransferObjectParams {
- /** the transaction signer's Iota address */
+ /** the transaction signer's IOTA address */
signer: string;
/** the ID of the object to be transferred */
objectId: string;
@@ -628,6 +628,6 @@ export interface UnsafeTransferObjectParams {
gas?: string | null | undefined;
/** the gas budget, the transaction will fail if the gas cost exceed the budget */
gasBudget: string;
- /** the recipient's Iota address */
+ /** the recipient's IOTA address */
recipient: string;
}
diff --git a/sdk/typescript/src/cryptography/publickey.ts b/sdk/typescript/src/cryptography/publickey.ts
index 32b238942ee..34dfda93019 100644
--- a/sdk/typescript/src/cryptography/publickey.ts
+++ b/sdk/typescript/src/cryptography/publickey.ts
@@ -58,7 +58,7 @@ export abstract class PublicKey {
/**
* Return the IOTA representation of the public key encoded in
- * base-64. A IOTA public key is formed by the concatenation
+ * base-64. An IOTA public key is formed by the concatenation
* of the scheme flag with the raw bytes of the public key
*/
toIotaPublicKey(): string {
diff --git a/sdk/typescript/src/graphql/generated/2024.11/schema.graphql b/sdk/typescript/src/graphql/generated/2024.11/schema.graphql
index 8821213b8ef..ec5f1a351d7 100644
--- a/sdk/typescript/src/graphql/generated/2024.11/schema.graphql
+++ b/sdk/typescript/src/graphql/generated/2024.11/schema.graphql
@@ -951,7 +951,7 @@ of dynamic fields:
an object stored in this kind of field will be considered wrapped and
will not be accessible directly via its ID by external tools (explorers,
wallets, etc) accessing storage.
-2) Dynamic Object Fields values must be Iota objects (have the `key` and
+2) Dynamic Object Fields values must be IOTA objects (have the `key` and
`store` abilities, and id: UID as the first field), but will still be
directly accessible off-chain via their object ID after being attached.
"""
@@ -1061,7 +1061,7 @@ type EndOfEpochTransactionKindEdge {
}
"""
-Operation of the Iota network is temporally partitioned into non-overlapping
+Operation of the IOTA network is temporally partitioned into non-overlapping
epochs, and the network aims to keep epochs roughly the same duration as
each other. During a particular epoch the following data is fixed:
@@ -1664,7 +1664,7 @@ type MergeCoinsTransaction {
}
"""
-Abilities are keywords in Iota Move that define how types behave at the
+Abilities are keywords in IOTA Move that define how types behave at the
compiler level.
"""
enum MoveAbility {
@@ -2610,7 +2610,7 @@ enum MoveVisibility {
}
"""
-Mutations are used to write to the Iota network.
+Mutations are used to write to the IOTA network.
"""
type Mutation {
"""
@@ -2638,7 +2638,7 @@ type Mutation {
}
"""
-An object in Iota is a package (set of Move bytecode modules) or object
+An object in IOTA is a package (set of Move bytecode modules) or object
(typed data structure with fields) with additional metadata detailing its
id, version, transaction digest, owner field indicating how this object can
be accessed.
@@ -3279,7 +3279,7 @@ type Query {
field when its parent was at `rootVersion`.
If `rootVersion` is omitted, dynamic fields will be from a consistent
- snapshot of the Iota state at the latest checkpoint known to the
+ snapshot of the IOTA state at the latest checkpoint known to the
GraphQL RPC. Similarly, `Owner.asObject` will return the object's
version at the latest checkpoint.
"""