@@ -399,7 +399,7 @@ Then copy and paste your **contract address** below and click **Get cupcake!**.
Our first `VendingMachine` is labeled "Web2" because it demonstrates traditional client-server web application architecture: the back-end lives in a centralized network of servers.
diff --git a/docs/build-decentralized-apps/arbitrum-vs-ethereum/01-comparison-overview.mdx b/docs/build-decentralized-apps/arbitrum-vs-ethereum/01-comparison-overview.mdx
index bdc949749a..53e9b1357a 100644
--- a/docs/build-decentralized-apps/arbitrum-vs-ethereum/01-comparison-overview.mdx
+++ b/docs/build-decentralized-apps/arbitrum-vs-ethereum/01-comparison-overview.mdx
@@ -9,7 +9,7 @@ content_type: concept
displayed_sidebar: buildAppsSidebar
---
-Arbitrum's design is to be as compatible and consistent with Ethereum as possible, from its high-level RPCs to its low-level bytecode and everything in between. Decentralized app (dApp) developers with experience building on Ethereum will likely find that little to no new specific knowledge is required to build on Arbitrum.
+Arbitrum's design is to be as compatible and consistent with Ethereum as possible, from its high-level RPCs to its low-level bytecode and everything in between. Decentralized app developers with experience building on Ethereum will likely find that little to no new specific knowledge is required to build on Arbitrum.
This article outlines the key differences, benefits, and potential pitfalls that devs should be aware of when working with Arbitrum. This first page serves as an outline, with links to the relevant pages.
diff --git a/docs/build-decentralized-apps/oracles/01-overview.mdx b/docs/build-decentralized-apps/oracles/01-overview.mdx
index 39920000f8..a4228fbe40 100644
--- a/docs/build-decentralized-apps/oracles/01-overview.mdx
+++ b/docs/build-decentralized-apps/oracles/01-overview.mdx
@@ -36,13 +36,13 @@ Oracles can be classified based on their source, direction of information, trust
Push oracles proactively provide data to smart contracts without being explicitly requested. When a specified event or condition occurs, the push oracle triggers the smart contract with the relevant data. For example, a push oracle might send weather data to a smart contract once the temperature reaches a certain threshold.
-
+
### How do pull oracles work?
Pull oracles require smart contracts to request data explicitly. A smart contract sends a query to the oracle, retrieving and relaying the requested information to the contract. For example, a smart contract might request the current price of a specific digital asset from a pull oracle.
-
+
### Use cases for oracles
diff --git a/docs/build-decentralized-apps/token-bridging/02-token-bridge-ether.mdx b/docs/build-decentralized-apps/token-bridging/02-token-bridge-ether.mdx
index d51c2789aa..84732de423 100644
--- a/docs/build-decentralized-apps/token-bridging/02-token-bridge-ether.mdx
+++ b/docs/build-decentralized-apps/token-bridging/02-token-bridge-ether.mdx
@@ -28,7 +28,7 @@ If the transaction comes from a `7702-enabled account`, the destination address
The following diagram depicts the process that funds follow during a deposit operation.
-
+
Regarding the parent chain, all deposited funds are held in the Arbitrum Bridge contract. Once finalized, the `ETH` becomes available on the L2 at the aliased or specified address, depending on the sender type.
@@ -46,4 +46,4 @@ Upon withdrawal, the Ether balance is burned on the Arbitrum side and will later
The following diagram depicts the process that funds follow during a withdrawal operation.
-
+
diff --git a/docs/build-decentralized-apps/token-bridging/03-token-bridge-erc20.mdx b/docs/build-decentralized-apps/token-bridging/03-token-bridge-erc20.mdx
index 5d9e8e6f43..007f1bfd03 100644
--- a/docs/build-decentralized-apps/token-bridging/03-token-bridge-erc20.mdx
+++ b/docs/build-decentralized-apps/token-bridging/03-token-bridge-erc20.mdx
@@ -10,7 +10,7 @@ displayed_sidebar: buildAppsSidebar
import ImageZoom from '@site/src/components/ImageZoom';
-The Arbitrum protocol itself has no notion of token standards and gives no built-in advantage or special recognition to any particular token bridge. In this article, we describe the "canonical bridge," which was implemented by Offchain Labs, and should be the primary bridge most users and applications use; it is (effectively) a decentralized app (dApp) with contracts on both Ethereum (parent chain) and Arbitrum (child chain) that leverages Arbitrum's [cross-chain messaging protocol](/build-decentralized-apps/04-cross-chain-messaging.mdx) to achieve basic desired token-bridging functionality. We recommend that you use it!
+The Arbitrum protocol itself has no notion of token standards and gives no built-in advantage or special recognition to any particular token bridge. In this article, we describe the "canonical bridge," which was implemented by Offchain Labs, and should be the primary bridge most users and applications use; it is (effectively) a decentralized app with contracts on both Ethereum (parent chain) and Arbitrum (child chain) that leverages Arbitrum's [cross-chain messaging protocol](/build-decentralized-apps/04-cross-chain-messaging.mdx) to achieve basic desired token-bridging functionality. We recommend that you use it!
## Design rationale
@@ -45,15 +45,15 @@ Our architecture consists of three types of contracts:
2. **Gateways**: Pairs of contracts (one on the parent chain, one on the child chain) that implement a particular type of cross-chain asset bridging.
3. **Routers**: Exactly two contracts (one on the parent chain, one on the child chain) that route each asset to its designated gateway.
-
+
All Ethereum-to-Arbitrum token transfers are initiated via the router contract on the parent chain, specifically the `L1GatewayRouter` contract. `L1GatewayRouter` forwards the token's deposit call to the appropriate gateway contract on the parent chain, the `L1ArbitrumGateway` contract. `L1GatewayRouter` is responsible for mapping the parent chain token addresses to L1Gateway contracts, thus acting as a parent/child chain address oracle and ensuring each token corresponds to only one gateway. The `L1ArbitrumGateway` then communicates to its counterpart gateway contract on the child chain, the `L2ArbitrumGateway` contract (typically/expectedly via [retryable tickets](/how-arbitrum-works/10-l1-to-l2-messaging.mdx)).
-
+
Similarly, Arbitrum-to-Ethereum transfers initiate via the router contract on the child chain, specifically the `L2GatewayRouter` contract, which in turn calls the token's gateway contract on the child chain. This `L2ArbitrumGateway` contract in turn communicates to its corresponding gateway contract on the parent chain, the `L1ArbitrumGateway` contract (typically/expectedly via [sending child-to-parent messages to the outbox](/how-arbitrum-works/11-l2-to-l1-messaging.mdx)).
-
+
For any given gateway pairing, we require that calls initiate through the corresponding router (`L1GatewayRouter` or `L2GatewayRouter`), and that the gateways conform to the [`TokenGateway`](https://github.com/OffchainLabs/token-bridge-contracts/blob/main/contracts/tokenbridge/libraries/gateway/TokenGateway.sol) interfaces; the `TokenGateway` interfaces should be flexible and extensible enough to support any bridging functionality a particular token may require.
diff --git a/docs/for-devs/oracles/api3/api3.mdx b/docs/for-devs/oracles/api3/api3.mdx
index a5efdbb54e..16d0ad1c69 100644
--- a/docs/for-devs/oracles/api3/api3.mdx
+++ b/docs/for-devs/oracles/api3/api3.mdx
@@ -5,11 +5,11 @@ sidebar_label: 'API3'
description: 'Learn how to query a price feed for your smart contract.'
author: GreatSoshiant
sme: GreatSoshiant
-user_story: As an Arbitrum developer, I want to learn how to use oracles in my dApp.
+user_story: As an Arbitrum developer, I want to learn how to use oracles in my app.
content_type: get-started
---
-[API3](https://api3.org/) is a collaborative project to deliver price feeds to smart contract platforms in a decentralized and trust-minimized way. The Price feeds provided by API3 allow dapps to regain lost value with Oracle Extractable Value built in to the price feed allowing the ability to earn additional revenue for your dapp.
+[API3](https://api3.org/) is a collaborative project to deliver price feeds to smart contract platforms in a decentralized and trust-minimized way. The Price feeds provided by API3 allow apps to regain lost value with Oracle Extractable Value built in to the price feed allowing the ability to earn additional revenue for your app.
### Querying the price of `ARB` through API3
diff --git a/docs/for-devs/oracles/chainlink/chainlink.mdx b/docs/for-devs/oracles/chainlink/chainlink.mdx
index f345b1763a..89ff8923c9 100644
--- a/docs/for-devs/oracles/chainlink/chainlink.mdx
+++ b/docs/for-devs/oracles/chainlink/chainlink.mdx
@@ -1,12 +1,12 @@
---
id: 'chainlink'
title: 'Chainlink'
-description: Learn how to integrate oracles into your Arbitrum dapp
+description: Learn how to integrate oracles into your Arbitrum app
user_story: As a developer, I want to understand how to use oracles in Arbitrum to get offchain data onchain.
content_type: how-to
---
-[Chainlink](https://chain.link/) is a widely-recognized Web3 services platform that specializes in decentralized oracle networks. It lets you build Ethereum and Arbitrum dApps that connect to a variety of offchain data feeds and APIs, including those that provide asset prices, weather data, random number generation, and more.
+[Chainlink](https://chain.link/) is a widely-recognized Web3 services platform that specializes in decentralized oracle networks. It lets you build Ethereum and Arbitrum apps that connect to a variety of offchain data feeds and APIs, including those that provide asset prices, weather data, random number generation, and more.
### Querying the price of `ARB` through Chainlink
diff --git a/docs/for-devs/oracles/chronicle/chronicle.mdx b/docs/for-devs/oracles/chronicle/chronicle.mdx
index 4dedbf0bd1..5f5a975a6e 100644
--- a/docs/for-devs/oracles/chronicle/chronicle.mdx
+++ b/docs/for-devs/oracles/chronicle/chronicle.mdx
@@ -1,7 +1,7 @@
---
id: 'chronicle'
title: 'Chronicle'
-description: Learn how to integrate oracles into your Arbitrum dapp
+description: Learn how to integrate oracles into your Arbitrum app
user_story: As a developer, I want to understand how to use oracles in Arbitrum to get offchain data onchain.
content_type: how-to
---
diff --git a/docs/for-devs/oracles/dia/dia.mdx b/docs/for-devs/oracles/dia/dia.mdx
index 7f6d1b1fb1..7366ea1761 100644
--- a/docs/for-devs/oracles/dia/dia.mdx
+++ b/docs/for-devs/oracles/dia/dia.mdx
@@ -1,7 +1,7 @@
---
id: 'dia'
title: 'DIA'
-description: Learn how to integrate oracles into your Arbitrum dapp
+description: Learn how to integrate oracles into your Arbitrum app
user_story: As a developer, I want to understand how to use oracles in Arbitrum to get offchain data onchain.
content_type: how-to
---
@@ -12,7 +12,7 @@ You can find an example on how to use DIA in your project on this [page](https:/
### How to use DIA oracles on Arbitrum
-**Requesting a custom oracle**: DIA deploys oracles tailored to each dApp’s needs. Each oracle is customizable, including data sources, cleansing filters, pricing, computational methodologies, update mechanisms, and more. This flexibility ensures that the data and oracle remain robust and resilient to the market conditions and provide a global market price and specific individual or cross-chain market prices.
+**Requesting a custom oracle**: DIA deploys oracles tailored to each app’s needs. Each oracle is customizable, including data sources, cleansing filters, pricing, computational methodologies, update mechanisms, and more. This flexibility ensures that the data and oracle remain robust and resilient to the market conditions and provide a global market price and specific individual or cross-chain market prices.
→ [Request a Custom Oracle for your dApp | DIA Documentation](https://docs.diadata.org/introduction/intro-to-dia-oracles/request-an-oracle)
### Token Price Feeds
diff --git a/docs/for-devs/oracles/trellor/trellor.mdx b/docs/for-devs/oracles/trellor/trellor.mdx
index f6444e5261..73148fa918 100644
--- a/docs/for-devs/oracles/trellor/trellor.mdx
+++ b/docs/for-devs/oracles/trellor/trellor.mdx
@@ -1,7 +1,7 @@
---
id: 'trellor'
title: 'Trellor'
-description: Learn how to integrate oracles into your Arbitrum dapp
+description: Learn how to integrate oracles into your Arbitrum app
user_story: As a developer, I want to understand how to use oracles in Arbitrum to get offchain data onchain.
sidebar_label: 'Trellor'
content_type: how-to
diff --git a/docs/for-devs/third-party-docs/MetaMask/metamask.mdx b/docs/for-devs/third-party-docs/MetaMask/metamask.mdx
index f3ab3394b8..72e549a60e 100644
--- a/docs/for-devs/third-party-docs/MetaMask/metamask.mdx
+++ b/docs/for-devs/third-party-docs/MetaMask/metamask.mdx
@@ -6,7 +6,7 @@ third_party_content_owner: 'alexandratran'
---
The [MetaMask Delegation Toolkit](https://docs.metamask.io/delegation-toolkit/) is a collection of tools for embedding
-MetaMask Smart Accounts into dapps.
+MetaMask Smart Accounts into apps.
These [smart accounts](https://docs.metamask.io/delegation-toolkit/concepts/smart-accounts/) support programmable
account behavior and advanced features like delegated permissions, multi-signature approvals, and gas abstraction.
diff --git a/docs/for-devs/third-party-docs/Webacy/webacy.mdx b/docs/for-devs/third-party-docs/Webacy/webacy.mdx
index f67e54ad04..c3553a562c 100644
--- a/docs/for-devs/third-party-docs/Webacy/webacy.mdx
+++ b/docs/for-devs/third-party-docs/Webacy/webacy.mdx
@@ -26,7 +26,7 @@ Wallets, protocols, & applications use Webacy throughout their user experience:
### Before a transaction
-- Block harmful dApps and links
+- Block harmful apps and links
- Review address trust and safety prior to signature
- Protect users from interacting with malicious smart contracts
diff --git a/docs/how-arbitrum-works/01-a-gentle-introduction.mdx b/docs/how-arbitrum-works/01-a-gentle-introduction.mdx
index 88b9d03981..1de8f9e39d 100644
--- a/docs/how-arbitrum-works/01-a-gentle-introduction.mdx
+++ b/docs/how-arbitrum-works/01-a-gentle-introduction.mdx
@@ -41,7 +41,7 @@ The network stays secure if there is at least one honest validator, which means
It's not as complicated as it seems. If two validators disagree, only one is telling the truth. In the event of a dispute, the two validators engage in an interactive game, where they respond to each other in a call-and-response format. This process enables them to narrow their disagreement down to a single computational step—something straightforward, such as multiplying two numbers. This step executes on the parent chain, which shows which party is honest. For a more detailed explanation, [read the explainer on interactive fraud proofs and the challenge protocol](/how-arbitrum-works/05-validation-and-proving/03-proving-and-challenges.mdx#5-interactive-fraud-proofs-and-the-challenge-protocol).
-Users only experience delays when they withdraw funds from Arbitrum back to Ethereum. When withdrawing directly from Arbitrum to Ethereum, users usually wait one week to receive their funds on the parent chain. However, users can skip this waiting period if they use a fast bridge application, often for a small fee. Other activities do not have this delay, like depositing funds from Ethereum to Arbitrum or using a decentralized application (dApp) on the Arbitrum chain.
+Users only experience delays when they withdraw funds from Arbitrum back to Ethereum. When withdrawing directly from Arbitrum to Ethereum, users usually wait one week to receive their funds on the parent chain. However, users can skip this waiting period if they use a fast bridge application, often for a small fee. Other activities do not have this delay, like depositing funds from Ethereum to Arbitrum or using a decentralized application on the Arbitrum chain.
### How is it cheaper?
diff --git a/docs/how-arbitrum-works/05-validation-and-proving/02-rollup-protocol.mdx b/docs/how-arbitrum-works/05-validation-and-proving/02-rollup-protocol.mdx
index fcbee1353b..6190591275 100644
--- a/docs/how-arbitrum-works/05-validation-and-proving/02-rollup-protocol.mdx
+++ b/docs/how-arbitrum-works/05-validation-and-proving/02-rollup-protocol.mdx
@@ -207,7 +207,7 @@ The only delay users experience during a dispute is their [Child to parent chain
Anyone can do it, but most people will choose not to. In practice, we expect people to validate a chain for several reasons.
- It is possible to pay validators for their work by the party that created the chain or someone else. A chain is configurable, so some of the funds from user transaction fees are paid directly to validators.
-- Parties with significant assets at bond on a chain, such as dApp developers, exchanges, power users, and liquidity providers, may choose to validate in order to protect their investment.
+- Parties with significant assets at bond on a chain, such as decentralized app developers, exchanges, power users, and liquidity providers, may choose to validate in order to protect their investment.
- Anyone who wants to validate can do so. Some users may choose to validate to protect their interests or be good citizens. But ordinary users don't need to validate, and we expect most users won't.
### Staking and validator incentives
@@ -266,7 +266,7 @@ Arbitrum's validation process is permissionless, allowing anyone to participate.
Common validator motivations include:
- **Financial incentives**: Some validators receive payment from network fees or the chain's owner.
-- **Asset protection**: dApp developers, exchanges, and liquidity providers may validate the chain to protect their holdings.
+- **Asset protection**: app developers, exchanges, and liquidity providers may validate the chain to protect their holdings.
- **Public interest**: Some participants validate purely for network integrity, ensuring fair execution.
For most users, validation is unnecessary, as the network relies on economic incentives and fraud-proof mechanisms to maintain security.
diff --git a/docs/how-arbitrum-works/10-l1-to-l2-messaging.mdx b/docs/how-arbitrum-works/10-l1-to-l2-messaging.mdx
index 94d45fef5b..048cf712fb 100644
--- a/docs/how-arbitrum-works/10-l1-to-l2-messaging.mdx
+++ b/docs/how-arbitrum-works/10-l1-to-l2-messaging.mdx
@@ -373,7 +373,7 @@ We can build **customized feature messaging** (for example, token bridging) usin
### `ERC-20` token bridging
-The Arbitrum protocol technically has no native notion of any token standards and gives no built-in advantage or special recognition to any particular token bridge. In this page, we describe the "canonical bridge", which was implemented by Offchain Labs and should be the primary bridge most users and applications use; it is (effectively) a decentralized app (dApp) with contracts on both parent and child chains that leverages Arbitrum's [cross-chain message passing system](/build-decentralized-apps/04-cross-chain-messaging.mdx) to achieve basic desired token-bridging functionality. We recommend that you use it!
+The Arbitrum protocol technically has no native notion of any token standards and gives no built-in advantage or special recognition to any particular token bridge. In this page, we describe the "canonical bridge", which was implemented by Offchain Labs and should be the primary bridge most users and applications use; it is (effectively) a decentralized app with contracts on both parent and child chains that leverages Arbitrum's [cross-chain message passing system](/build-decentralized-apps/04-cross-chain-messaging.mdx) to achieve basic desired token-bridging functionality. We recommend that you use it!
### Design rationale
diff --git a/docs/how-arbitrum-works/11-l2-to-l1-messaging.mdx b/docs/how-arbitrum-works/11-l2-to-l1-messaging.mdx
index f0e2cc472c..0ee37c144f 100644
--- a/docs/how-arbitrum-works/11-l2-to-l1-messaging.mdx
+++ b/docs/how-arbitrum-works/11-l2-to-l1-messaging.mdx
@@ -101,7 +101,7 @@ Upon withdrawing, the Ether balance is burnt on the child chain side and will la
The following diagram depicts the process that funds follow during a withdrawal operation.
@@ -115,7 +115,7 @@ Arbitrum has a canonical bridge design and a
3. `L2ArbitrumGateway` finally communicates to its corresponding gateway contract on the parent chain using the `L1ArbitrumGateway` contract.
diff --git a/docs/launch-arbitrum-chain/01-a-gentle-introduction.mdx b/docs/launch-arbitrum-chain/01-a-gentle-introduction.mdx
index 8ee5d47a42..e3aea4fc7d 100644
--- a/docs/launch-arbitrum-chain/01-a-gentle-introduction.mdx
+++ b/docs/launch-arbitrum-chain/01-a-gentle-introduction.mdx
@@ -76,4 +76,4 @@ It depends on your definition of "app chain". Arbitrum chains can be used as app
- You can use your Arbitrum chain to host the smart contracts that support one app, two apps, an ecosystem of apps, or no apps at all.
- You can use your Arbitrum chain to host a private, centralized service.
- Your Arbitrum chain can be special-purpose, general-purpose, and everything in-between.
-- You could even build an app that uses multiple Arbitrum chains to support strange new forms of redundancy, high availability, and trustlessness.
+- You could even build an app that uses multiple Arbitrum chains to support strange new forms of redundancy, high availability, and trustlessness.
diff --git a/docs/partials/_gentle-intro-partial.mdx b/docs/partials/_gentle-intro-partial.mdx
index d73baf0ff9..2175a91deb 100644
--- a/docs/partials/_gentle-intro-partial.mdx
+++ b/docs/partials/_gentle-intro-partial.mdx
@@ -51,7 +51,7 @@ Oh, it’s not so bad. In essence, if two validators disagree, only one of them
#### Q: This dispute game obviously takes some time; does this impose any sort of delay on Arbitrum users' transactions?
-The only delay that's felt by a user is in "withdrawing" — moving their funds from Arbitrum back to Ethereum; if users are withdrawing directly from Arbitrum to Ethereum, they must typically wait 1 week before receiving their funds on L1. If users use a fast-Bridge application, however, they can bypass this delay period entirely (likely for a small fee). Anything else a user does — i.e., depositing funds from Ethereum onto Arbitrum, or using a dApp deployed on an Arbitrum chain — doesn't incur this delay period.
+The only delay that's felt by a user is in "withdrawing" — moving their funds from Arbitrum back to Ethereum; if users are withdrawing directly from Arbitrum to Ethereum, they must typically wait 1 week before receiving their funds on L1. If users use a fast-Bridge application, however, they can bypass this delay period entirely (likely for a small fee). Anything else a user does — i.e., depositing funds from Ethereum onto Arbitrum, or using a decentralized app deployed on an Arbitrum chain — doesn't incur this delay period.
#### Q: Okay, so backing up: the “optimistic execution” part is how and why Arbitrum is able to offer low fees, yes?
@@ -71,7 +71,7 @@ They can; the latest version of the Arbitrum tech stack, called app use-cases with different security considerations, different tools in the Arbitrum suite are appropriate; i.e., Arbitrum AnyTrust chains!
#### Q: What’s an AnyTrust chain?
diff --git a/docs/partials/_glossary-partial.mdx b/docs/partials/_glossary-partial.mdx
index 9400361253..668eb36f26 100644
--- a/docs/partials/_glossary-partial.mdx
+++ b/docs/partials/_glossary-partial.mdx
@@ -3,7 +3,7 @@ partial_type: glossary
title: 'Arbitrum Glossary Definitions'
description: 'Comprehensive glossary of Arbitrum terminology and definitions'
author: anegg0
-last_reviewed: 2025-10-08
+last_reviewed: 2025-10-16
---
### Active Validator {#active-validator}
@@ -14,6 +14,11 @@ A bonded [Validator](/intro/glossary#validator) that makes disputable assertions
An address deterministically generated from a parent chain contract address used on child chain to safely identify the source of an parent to child chain message.
+### Decentralized application {#dapp}
+
+A decentralized application typically consists of smart contracts as well as a user-interface for interacting with them.
+Note: In our documentation, "apps" and "decentralized applications" are used interchangeably.
+
### Arb Token Bridge {#arb-token-bridge}
A series of contracts on an Arbitrum chain and its underlying chain that facilitate trustless movement of `ERC-20` tokens between the two layers.
@@ -159,10 +164,6 @@ Any child chain token contract registered to the [Arb Token Bridge](/intro/gloss
Any [Token Gateway](/intro/glossary#token-gateway) that isn't the [`StandardERC20` gateway](/intro/glossary#standarderc20-gateway).
-### dApp {#dapp}
-
-Short for "decentralized application." A dApp typically consists of smart contracts as well as a user-interface for interacting with them.
-
### Data Availability Certificate {#data-availability-certificate}
Signed promise from a [Data Availability Committee (DAC)](/intro/glossary#data-availability-committee-dac) attesting to the availability of a batch of data for an [Arbitrum AnyTrust Chain](/intro/glossary#arbitrum-anytrust-chain).
diff --git a/docs/partials/glossary/_app.mdx b/docs/partials/glossary/_app.mdx
new file mode 100644
index 0000000000..c48a036fd5
--- /dev/null
+++ b/docs/partials/glossary/_app.mdx
@@ -0,0 +1,8 @@
+---
+title: Decentralized application
+key: dapp
+titleforSort: application
+---
+
+A decentralized application typically consists of smart contracts as well as a user-interface for interacting with them.
+Note: In our documentation, "apps" and "decentralized applications" are used interchangeably.
diff --git a/docs/partials/glossary/_dapp.mdx b/docs/partials/glossary/_dapp.mdx
deleted file mode 100644
index 59b8fd44f6..0000000000
--- a/docs/partials/glossary/_dapp.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: dApp
-key: dapp
-titleforSort: dApp
----
-
-Short for "decentralized application." A dApp typically consists of smart contracts as well as a user-interface for interacting with them.
diff --git a/docs/stylus/quickstart.mdx b/docs/stylus/quickstart.mdx
index 588f015ca1..c19b3cf5bc 100644
--- a/docs/stylus/quickstart.mdx
+++ b/docs/stylus/quickstart.mdx
@@ -276,7 +276,7 @@ interface ICounter {
}
```
-Ensure you save the console output to a file that you'll be able to use with your dApp.
+Ensure you save the console output to a file that you'll be able to use with your decentralized app.
## Interacting with your Stylus contract
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current.json b/i18n/ja/docusaurus-plugin-content-docs/current.json
index e905b80658..10191d9853 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current.json
+++ b/i18n/ja/docusaurus-plugin-content-docs/current.json
@@ -1,330 +1,1057 @@
{
- "version.label": {
- "message": "Next",
- "description": "The label for version current"
+ "sidebar.additionalResourcesSidebar.category.Oracles": {
+ "message": "Oracles",
+ "description": "The label for category Oracles in sidebar additionalResourcesSidebar"
},
- "sidebar.buildDecentralizedAppsSidebar.category.Build dApps (Solidity)": {
- "message": "Build dApps (Solidity)",
- "description": "The label for category Build dApps (Solidity) in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.additionalResourcesSidebar.category.Third-party docs": {
+ "message": "Third-party docs",
+ "description": "The label for category Third-party docs in sidebar additionalResourcesSidebar"
},
- "sidebar.buildDecentralizedAppsSidebar.category.How-tos": {
- "message": "How-tos",
- "description": "The label for category How-tos in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.additionalResourcesSidebar.doc.Audit reports": {
+ "message": "Audit reports",
+ "description": "The label for the doc item Audit reports in sidebar additionalResourcesSidebar, linking to the doc audit-reports"
},
- "sidebar.buildDecentralizedAppsSidebar.category.Concepts": {
- "message": "Concepts",
- "description": "The label for category Concepts in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.additionalResourcesSidebar.doc.Chain info": {
+ "message": "Chain info",
+ "description": "The label for the doc item Chain info in sidebar additionalResourcesSidebar, linking to the doc for-devs/dev-tools-and-resources/chain-info"
},
- "sidebar.buildDecentralizedAppsSidebar.category.Differences between Arbitrum and Ethereum": {
- "message": "Differences between Arbitrum and Ethereum",
- "description": "The label for category Differences between Arbitrum and Ethereum in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.additionalResourcesSidebar.doc.Contribute": {
+ "message": "Contribute",
+ "description": "The label for the doc item Contribute in sidebar additionalResourcesSidebar, linking to the doc for-devs/contribute"
},
- "sidebar.buildDecentralizedAppsSidebar.category.Build dApps (Rust) (TESTNET)": {
- "message": "Build dApps (Rust) (TESTNET)",
- "description": "The label for category Build dApps (Rust) (TESTNET) in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.additionalResourcesSidebar.doc.FAQ": {
+ "message": "FAQ",
+ "description": "The label for the doc item FAQ in sidebar additionalResourcesSidebar, linking to the doc learn-more/faq"
},
- "sidebar.buildDecentralizedAppsSidebar.category.Developer reference": {
- "message": "Developer reference",
- "description": "The label for category Developer reference in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.additionalResourcesSidebar.doc.Glossary": {
+ "message": "Glossary",
+ "description": "The label for the doc item Glossary in sidebar additionalResourcesSidebar, linking to the doc intro/glossary"
},
- "sidebar.buildDecentralizedAppsSidebar.category.Launch your own chain (Orbit)": {
- "message": "Launch your own chain (Orbit)",
- "description": "The label for category Launch your own chain (Orbit) in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.additionalResourcesSidebar.doc.undefined": {
+ "description": "The label for the doc item undefined in sidebar additionalResourcesSidebar, linking to the doc for-devs/oracles/trellor/trellor"
},
- "sidebar.buildDecentralizedAppsSidebar.category.Reference": {
- "message": "Reference",
- "description": "The label for category Reference in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.additionalResourcesSidebar.link.DAO docs": {
+ "message": "DAO docs",
+ "description": "The label for link DAO docs in sidebar additionalResourcesSidebar, linking to https://docs.arbitrum.foundation/gentle-intro-dao-governance"
},
- "sidebar.buildDecentralizedAppsSidebar.category.Bridge tokens between chains": {
- "message": "Bridge tokens between chains",
- "description": "The label for category Bridge tokens between chains in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.additionalResourcesSidebar.link.Prysm docs": {
+ "message": "Prysm docs",
+ "description": "The label for link Prysm docs in sidebar additionalResourcesSidebar, linking to https://www.offchainlabs.com/prysm/docs"
},
- "sidebar.buildDecentralizedAppsSidebar.category.More": {
- "message": "More",
- "description": "The label for category More in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.bridgeSidebar.category.Arbitrum bridge": {
+ "message": "Arbitrum bridge",
+ "description": "The label for category Arbitrum bridge in sidebar bridgeSidebar"
},
- "sidebar.buildDecentralizedAppsSidebar.category.Third-party docs": {
- "message": "Third-party docs",
- "description": "The label for category Third-party docs in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.bridgeSidebar.doc.Embedded bridge widget": {
+ "message": "Embedded bridge widget",
+ "description": "The label for the doc item Embedded bridge widget in sidebar bridgeSidebar, linking to the doc arbitrum-bridge/embedded-bridge-widget"
},
- "sidebar.buildDecentralizedAppsSidebar.category.Supra": {
- "message": "Supra",
- "description": "The label for category Supra in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.bridgeSidebar.doc.Quickstart": {
+ "message": "Quickstart",
+ "description": "The label for the doc item Quickstart in sidebar bridgeSidebar, linking to the doc arbitrum-bridge/quickstart"
},
- "sidebar.buildDecentralizedAppsSidebar.link.Rust crate docs": {
- "message": "Rust crate docs",
- "description": "The label for link Rust crate docs in sidebar buildDecentralizedAppsSidebar, linking to https://docs.rs/stylus-sdk/latest/stylus_sdk/index.html"
+ "sidebar.bridgeSidebar.doc.Troubleshooting": {
+ "message": "Troubleshooting",
+ "description": "The label for the doc item Troubleshooting in sidebar bridgeSidebar, linking to the doc arbitrum-bridge/troubleshooting"
},
- "sidebar.buildDecentralizedAppsSidebar.link.Source code repository": {
- "message": "Source code repository",
- "description": "The label for link Source code repository in sidebar buildDecentralizedAppsSidebar, linking to https://github.com/OffchainLabs/stylus"
+ "sidebar.bridgeSidebar.doc.USDC on Arbitrum One": {
+ "message": "USDC on Arbitrum One",
+ "description": "The label for the doc item USDC on Arbitrum One in sidebar bridgeSidebar, linking to the doc arbitrum-bridge/usdc-arbitrum-one"
},
- "sidebar.buildDecentralizedAppsSidebar.link.Arbitrum SDK": {
+ "sidebar.buildAppsSidebar.category.Arbitrum SDK": {
"message": "Arbitrum SDK",
- "description": "The label for link Arbitrum SDK in sidebar buildDecentralizedAppsSidebar, linking to /sdk"
+ "description": "The label for category Arbitrum SDK in sidebar buildAppsSidebar"
},
- "sidebar.buildDecentralizedAppsSidebar.link.Tutorials": {
- "message": "Tutorials",
- "description": "The label for link Tutorials in sidebar buildDecentralizedAppsSidebar, linking to https://github.com/OffchainLabs/arbitrum-tutorials"
+ "sidebar.buildAppsSidebar.category.Arbitrum vs Ethereum": {
+ "message": "Arbitrum vs Ethereum",
+ "description": "The label for category Arbitrum vs Ethereum in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.AssetBridger": {
+ "message": "AssetBridger",
+ "description": "The label for category AssetBridger in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Bridge tokens programmatically": {
+ "message": "Bridge tokens programmatically",
+ "description": "The label for category Bridge tokens programmatically in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Build apps with Solidity": {
+ "message": "Build apps with Solidity",
+ "description": "The label for category Build apps with Solidity in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Build apps with Stylus": {
+ "message": "Build apps with Stylus",
+ "description": "The label for category Build apps with Stylus in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Concepts": {
+ "message": "Concepts",
+ "description": "The label for category Concepts in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.DataEntities": {
+ "message": "DataEntities",
+ "description": "The label for category DataEntities in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Examples": {
+ "message": "Examples",
+ "description": "The label for category Examples in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Inbox": {
+ "message": "Inbox",
+ "description": "The label for category Inbox in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Message": {
+ "message": "Message",
+ "description": "The label for category Message in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.NodeInterface": {
+ "message": "NodeInterface",
+ "description": "The label for category NodeInterface in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Precompiles": {
+ "message": "Precompiles",
+ "description": "The label for category Precompiles in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Reference": {
+ "message": "Reference",
+ "description": "The label for category Reference in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Rust CLI": {
+ "message": "Rust CLI",
+ "description": "The label for category Rust CLI in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Rust SDK": {
+ "message": "Rust SDK",
+ "description": "The label for category Rust SDK in sidebar buildAppsSidebar"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.A gentle introduction": {
+ "sidebar.buildAppsSidebar.category.Token bridging": {
+ "message": "Token bridging",
+ "description": "The label for category Token bridging in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.category.Utils": {
+ "message": "Utils",
+ "description": "The label for category Utils in sidebar buildAppsSidebar"
+ },
+ "sidebar.buildAppsSidebar.doc.A gentle introduction": {
"message": "A gentle introduction",
- "description": "The label for the doc item A gentle introduction in sidebar buildDecentralizedAppsSidebar, linking to the doc for-devs/gentle-introduction-dapps"
+ "description": "The label for the doc item A gentle introduction in sidebar buildAppsSidebar, linking to the doc stylus/gentle-introduction"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Estimate gas": {
- "message": "Estimate gas",
- "description": "The label for the doc item Estimate gas in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/how-to-estimate-gas"
+ "sidebar.buildAppsSidebar.doc.Abi Decode": {
+ "message": "Abi Decode",
+ "description": "The label for the doc item Abi Decode in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/abi_decode"
+ },
+ "sidebar.buildAppsSidebar.doc.Abi Encode": {
+ "message": "Abi Encode",
+ "description": "The label for the doc item Abi Encode in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/abi_encode"
+ },
+ "sidebar.buildAppsSidebar.doc.Address": {
+ "message": "Address",
+ "description": "The label for the doc item Address in sidebar buildAppsSidebar, linking to the doc sdk/dataEntities/address"
+ },
+ "sidebar.buildAppsSidebar.doc.Advanced features": {
+ "message": "Advanced features",
+ "description": "The label for the doc item Advanced features in sidebar buildAppsSidebar, linking to the doc stylus/reference/rust-sdk-guide"
+ },
+ "sidebar.buildAppsSidebar.doc.Arb Provider": {
+ "message": "Arb Provider",
+ "description": "The label for the doc item Arb Provider in sidebar buildAppsSidebar, linking to the doc sdk/utils/arbProvider"
+ },
+ "sidebar.buildAppsSidebar.doc.Architecture overview": {
+ "message": "Architecture overview",
+ "description": "The label for the doc item Architecture overview in sidebar buildAppsSidebar, linking to the doc stylus/concepts/how-it-works"
+ },
+ "sidebar.buildAppsSidebar.doc.Asset Bridger": {
+ "message": "Asset Bridger",
+ "description": "The label for the doc item Asset Bridger in sidebar buildAppsSidebar, linking to the doc sdk/assetBridger/assetBridger"
+ },
+ "sidebar.buildAppsSidebar.doc.Block gas limit, numbers and time": {
+ "message": "Block gas limit, numbers and time",
+ "description": "The label for the doc item Block gas limit, numbers and time in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/arbitrum-vs-ethereum/block-numbers-and-time"
+ },
+ "sidebar.buildAppsSidebar.doc.Byte_serialize_params": {
+ "message": "Byte_serialize_params",
+ "description": "The label for the doc item Byte_serialize_params in sidebar buildAppsSidebar, linking to the doc sdk/utils/byte_serialize_params"
+ },
+ "sidebar.buildAppsSidebar.doc.Bytes In Bytes Out": {
+ "message": "Bytes In Bytes Out",
+ "description": "The label for the doc item Bytes In Bytes Out in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/bytes_in_bytes_out"
+ },
+ "sidebar.buildAppsSidebar.doc.Cache contracts": {
+ "message": "Cache contracts",
+ "description": "The label for the doc item Cache contracts in sidebar buildAppsSidebar, linking to the doc stylus/how-tos/caching-contracts"
+ },
+ "sidebar.buildAppsSidebar.doc.Chain parameters": {
+ "message": "Chain parameters",
+ "description": "The label for the doc item Chain parameters in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/reference/chain-params"
+ },
+ "sidebar.buildAppsSidebar.doc.Chains and testnets": {
+ "message": "Chains and testnets",
+ "description": "The label for the doc item Chains and testnets in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/public-chains"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Use oracles": {
- "message": "Use oracles",
- "description": "The label for the doc item Use oracles in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/oracles/how-to-use-oracles"
+ "sidebar.buildAppsSidebar.doc.Child To Parent Message": {
+ "message": "Child To Parent Message",
+ "description": "The label for the doc item Child To Parent Message in sidebar buildAppsSidebar, linking to the doc sdk/message/ChildToParentMessage"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Arbitrum chains": {
- "message": "Arbitrum chains",
- "description": "The label for the doc item Arbitrum chains in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/public-chains"
+ "sidebar.buildAppsSidebar.doc.Child To Parent Message Classic": {
+ "message": "Child To Parent Message Classic",
+ "description": "The label for the doc item Child To Parent Message Classic in sidebar buildAppsSidebar, linking to the doc sdk/message/ChildToParentMessageClassic"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Cross-chain messaging": {
+ "sidebar.buildAppsSidebar.doc.Child To Parent Message Nitro": {
+ "message": "Child To Parent Message Nitro",
+ "description": "The label for the doc item Child To Parent Message Nitro in sidebar buildAppsSidebar, linking to the doc sdk/message/ChildToParentMessageNitro"
+ },
+ "sidebar.buildAppsSidebar.doc.Child Transaction": {
+ "message": "Child Transaction",
+ "description": "The label for the doc item Child Transaction in sidebar buildAppsSidebar, linking to the doc sdk/message/ChildTransaction"
+ },
+ "sidebar.buildAppsSidebar.doc.Comparison overview": {
+ "message": "Comparison overview",
+ "description": "The label for the doc item Comparison overview in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/arbitrum-vs-ethereum/comparison-overview"
+ },
+ "sidebar.buildAppsSidebar.doc.Composition and trait-based routing model": {
+ "message": "Composition and trait-based routing model",
+ "description": "The label for the doc item Composition and trait-based routing model in sidebar buildAppsSidebar, linking to the doc stylus/how-tos/using-inheritance"
+ },
+ "sidebar.buildAppsSidebar.doc.Constants": {
+ "message": "Constants",
+ "description": "The label for the doc item Constants in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/constants"
+ },
+ "sidebar.buildAppsSidebar.doc.Cross-chain messaging": {
"message": "Cross-chain messaging",
- "description": "The label for the doc item Cross-chain messaging in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/cross-chain-messaging"
+ "description": "The label for the doc item Cross-chain messaging in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/cross-chain-messaging"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Precompiles": {
- "message": "Precompiles",
- "description": "The label for the doc item Precompiles in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/precompiles/reference"
+ "sidebar.buildAppsSidebar.doc.Custom gas token SDK": {
+ "message": "Custom gas token SDK",
+ "description": "The label for the doc item Custom gas token SDK in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/custom-gas-token-sdk"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Oracles": {
- "message": "Oracles",
- "description": "The label for the doc item Oracles in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/oracles/reference"
+ "sidebar.buildAppsSidebar.doc.Debug transactions": {
+ "message": "Debug transactions",
+ "description": "The label for the doc item Debug transactions in sidebar buildAppsSidebar, linking to the doc stylus/how-tos/debugging-tx"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Troubleshooting": {
- "message": "Troubleshooting",
- "description": "The label for the doc item Troubleshooting in sidebar buildDecentralizedAppsSidebar, linking to the doc for-devs/troubleshooting-building"
+ "sidebar.buildAppsSidebar.doc.Debugging tools": {
+ "message": "Debugging tools",
+ "description": "The label for the doc item Debugging tools in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/reference/debugging-tools"
+ },
+ "sidebar.buildAppsSidebar.doc.Development frameworks": {
+ "message": "Development frameworks",
+ "description": "The label for the doc item Development frameworks in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/reference/development-frameworks"
+ },
+ "sidebar.buildAppsSidebar.doc.ERC-20 token bridging": {
+ "message": "ERC-20 token bridging",
+ "description": "The label for the doc item ERC-20 token bridging in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/token-bridging/token-bridge-erc20"
+ },
+ "sidebar.buildAppsSidebar.doc.ETH bridging": {
+ "message": "ETH bridging",
+ "description": "The label for the doc item ETH bridging in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/token-bridging/token-bridge-ether"
+ },
+ "sidebar.buildAppsSidebar.doc.Erc20": {
+ "message": "Erc20",
+ "description": "The label for the doc item Erc20 in sidebar buildAppsSidebar, linking to the doc stylus-by-example/applications/erc20"
+ },
+ "sidebar.buildAppsSidebar.doc.Erc20 Bridger": {
+ "message": "Erc20 Bridger",
+ "description": "The label for the doc item Erc20 Bridger in sidebar buildAppsSidebar, linking to the doc sdk/assetBridger/erc20Bridger"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Overview": {
+ "sidebar.buildAppsSidebar.doc.Erc721": {
+ "message": "Erc721",
+ "description": "The label for the doc item Erc721 in sidebar buildAppsSidebar, linking to the doc stylus-by-example/applications/erc721"
+ },
+ "sidebar.buildAppsSidebar.doc.Errors": {
+ "message": "Errors",
+ "description": "The label for the doc item Errors in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/errors"
+ },
+ "sidebar.buildAppsSidebar.doc.Estimate gas": {
+ "message": "Estimate gas",
+ "description": "The label for the doc item Estimate gas in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/how-to-estimate-gas"
+ },
+ "sidebar.buildAppsSidebar.doc.Eth Bridger": {
+ "message": "Eth Bridger",
+ "description": "The label for the doc item Eth Bridger in sidebar buildAppsSidebar, linking to the doc sdk/assetBridger/ethBridger"
+ },
+ "sidebar.buildAppsSidebar.doc.Event": {
+ "message": "Event",
+ "description": "The label for the doc item Event in sidebar buildAppsSidebar, linking to the doc sdk/dataEntities/event"
+ },
+ "sidebar.buildAppsSidebar.doc.Event Fetcher": {
+ "message": "Event Fetcher",
+ "description": "The label for the doc item Event Fetcher in sidebar buildAppsSidebar, linking to the doc sdk/utils/eventFetcher"
+ },
+ "sidebar.buildAppsSidebar.doc.Events": {
+ "message": "Events",
+ "description": "The label for the doc item Events in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/events"
+ },
+ "sidebar.buildAppsSidebar.doc.Function": {
+ "message": "Function",
+ "description": "The label for the doc item Function in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/function"
+ },
+ "sidebar.buildAppsSidebar.doc.Function Selector": {
+ "message": "Function Selector",
+ "description": "The label for the doc item Function Selector in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/function_selector"
+ },
+ "sidebar.buildAppsSidebar.doc.Gas & Ink Pricing": {
+ "message": "Gas & Ink Pricing",
+ "description": "The label for the doc item Gas & Ink Pricing in sidebar buildAppsSidebar, linking to the doc stylus/reference/opcode-hostio-pricing"
+ },
+ "sidebar.buildAppsSidebar.doc.Gas metering": {
+ "message": "Gas metering",
+ "description": "The label for the doc item Gas metering in sidebar buildAppsSidebar, linking to the doc stylus/concepts/gas-metering"
+ },
+ "sidebar.buildAppsSidebar.doc.Get started": {
+ "message": "Get started",
+ "description": "The label for the doc item Get started in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/token-bridging/bridge-tokens-programmatically/get-started"
+ },
+ "sidebar.buildAppsSidebar.doc.Hashing": {
+ "message": "Hashing",
+ "description": "The label for the doc item Hashing in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/hashing"
+ },
+ "sidebar.buildAppsSidebar.doc.Hello World": {
+ "message": "Hello World",
+ "description": "The label for the doc item Hello World in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/hello_world"
+ },
+ "sidebar.buildAppsSidebar.doc.Inbox": {
+ "message": "Inbox",
+ "description": "The label for the doc item Inbox in sidebar buildAppsSidebar, linking to the doc sdk/inbox/inbox"
+ },
+ "sidebar.buildAppsSidebar.doc.Inheritance": {
+ "message": "Inheritance",
+ "description": "The label for the doc item Inheritance in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/inheritance"
+ },
+ "sidebar.buildAppsSidebar.doc.Introduction": {
+ "message": "Introduction",
+ "description": "The label for the doc item Introduction in sidebar buildAppsSidebar, linking to the doc sdk/index"
+ },
+ "sidebar.buildAppsSidebar.doc.L1l3 Bridger": {
+ "message": "L1l3 Bridger",
+ "description": "The label for the doc item L1l3 Bridger in sidebar buildAppsSidebar, linking to the doc sdk/assetBridger/l1l3Bridger"
+ },
+ "sidebar.buildAppsSidebar.doc.Lib": {
+ "message": "Lib",
+ "description": "The label for the doc item Lib in sidebar buildAppsSidebar, linking to the doc sdk/utils/lib"
+ },
+ "sidebar.buildAppsSidebar.doc.Mainnet risks": {
+ "message": "Mainnet risks",
+ "description": "The label for the doc item Mainnet risks in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/reference/mainnet-risks"
+ },
+ "sidebar.buildAppsSidebar.doc.Message": {
+ "message": "Message",
+ "description": "The label for the doc item Message in sidebar buildAppsSidebar, linking to the doc sdk/dataEntities/message"
+ },
+ "sidebar.buildAppsSidebar.doc.Migrate from v3 to v4": {
+ "message": "Migrate from v3 to v4",
+ "description": "The label for the doc item Migrate from v3 to v4 in sidebar buildAppsSidebar, linking to the doc sdk/migrate"
+ },
+ "sidebar.buildAppsSidebar.doc.Monitoring tools and block explorers": {
+ "message": "Monitoring tools and block explorers",
+ "description": "The label for the doc item Monitoring tools and block explorers in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/reference/monitoring-tools-block-explorers"
+ },
+ "sidebar.buildAppsSidebar.doc.Multi Call": {
+ "message": "Multi Call",
+ "description": "The label for the doc item Multi Call in sidebar buildAppsSidebar, linking to the doc stylus-by-example/applications/multi_call"
+ },
+ "sidebar.buildAppsSidebar.doc.Multicall": {
+ "message": "Multicall",
+ "description": "The label for the doc item Multicall in sidebar buildAppsSidebar, linking to the doc sdk/utils/multicall"
+ },
+ "sidebar.buildAppsSidebar.doc.Networks": {
+ "message": "Networks",
+ "description": "The label for the doc item Networks in sidebar buildAppsSidebar, linking to the doc sdk/dataEntities/networks"
+ },
+ "sidebar.buildAppsSidebar.doc.Optimize WASM binaries": {
+ "message": "Optimize WASM binaries",
+ "description": "The label for the doc item Optimize WASM binaries in sidebar buildAppsSidebar, linking to the doc stylus/how-tos/optimizing-binaries"
+ },
+ "sidebar.buildAppsSidebar.doc.Oracles": {
+ "message": "Oracles",
+ "description": "The label for the doc item Oracles in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/oracles/overview-oracles"
+ },
+ "sidebar.buildAppsSidebar.doc.Overview": {
"message": "Overview",
- "description": "The label for the doc item Overview in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/token-bridging/get-started"
+ "description": "The label for the doc item Overview in sidebar buildAppsSidebar, linking to the doc stylus/using-cli"
+ },
+ "sidebar.buildAppsSidebar.doc.Parent To Child Message": {
+ "message": "Parent To Child Message",
+ "description": "The label for the doc item Parent To Child Message in sidebar buildAppsSidebar, linking to the doc sdk/message/ParentToChildMessage"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Standard gateway": {
- "message": "Standard gateway",
- "description": "The label for the doc item Standard gateway in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/token-bridging/how-to-bridge-tokens-standard"
+ "sidebar.buildAppsSidebar.doc.Parent To Child Message Creator": {
+ "message": "Parent To Child Message Creator",
+ "description": "The label for the doc item Parent To Child Message Creator in sidebar buildAppsSidebar, linking to the doc sdk/message/ParentToChildMessageCreator"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Generic-custom gateway": {
- "message": "Generic-custom gateway",
- "description": "The label for the doc item Generic-custom gateway in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/token-bridging/how-to-bridge-tokens-generic-custom"
+ "sidebar.buildAppsSidebar.doc.Parent To Child Message Gas Estimator": {
+ "message": "Parent To Child Message Gas Estimator",
+ "description": "The label for the doc item Parent To Child Message Gas Estimator in sidebar buildAppsSidebar, linking to the doc sdk/message/ParentToChildMessageGasEstimator"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Custom gateway": {
- "message": "Custom gateway",
- "description": "The label for the doc item Custom gateway in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/token-bridging/how-to-bridge-tokens-custom-gateway"
+ "sidebar.buildAppsSidebar.doc.Parent Transaction": {
+ "message": "Parent Transaction",
+ "description": "The label for the doc item Parent Transaction in sidebar buildAppsSidebar, linking to the doc sdk/message/ParentTransaction"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.RPC endpoints and providers": {
+ "sidebar.buildAppsSidebar.doc.Primitive Data Types": {
+ "message": "Primitive Data Types",
+ "description": "The label for the doc item Primitive Data Types in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/primitive_data_types"
+ },
+ "sidebar.buildAppsSidebar.doc.Quickstart": {
+ "message": "Quickstart",
+ "description": "The label for the doc item Quickstart in sidebar buildAppsSidebar, linking to the doc stylus/quickstart"
+ },
+ "sidebar.buildAppsSidebar.doc.RPC endpoints and providers": {
"message": "RPC endpoints and providers",
- "description": "The label for the doc item RPC endpoints and providers in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/reference/node-providers"
+ "description": "The label for the doc item RPC endpoints and providers in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/reference/node-providers"
+ },
+ "sidebar.buildAppsSidebar.doc.RPC methods": {
+ "message": "RPC methods",
+ "description": "The label for the doc item RPC methods in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/arbitrum-vs-ethereum/rpc-methods"
+ },
+ "sidebar.buildAppsSidebar.doc.Recommended Rust Crates": {
+ "message": "Recommended Rust Crates",
+ "description": "The label for the doc item Recommended Rust Crates in sidebar buildAppsSidebar, linking to the doc stylus/recommended-libraries"
+ },
+ "sidebar.buildAppsSidebar.doc.Reference": {
+ "message": "Reference",
+ "description": "The label for the doc item Reference in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/nodeinterface/reference"
+ },
+ "sidebar.buildAppsSidebar.doc.Retryable Data": {
+ "message": "Retryable Data",
+ "description": "The label for the doc item Retryable Data in sidebar buildAppsSidebar, linking to the doc sdk/dataEntities/retryableData"
+ },
+ "sidebar.buildAppsSidebar.doc.Rpc": {
+ "message": "Rpc",
+ "description": "The label for the doc item Rpc in sidebar buildAppsSidebar, linking to the doc sdk/dataEntities/rpc"
+ },
+ "sidebar.buildAppsSidebar.doc.Sending Ether": {
+ "message": "Sending Ether",
+ "description": "The label for the doc item Sending Ether in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/sending_ether"
+ },
+ "sidebar.buildAppsSidebar.doc.Signer Or Provider": {
+ "message": "Signer Or Provider",
+ "description": "The label for the doc item Signer Or Provider in sidebar buildAppsSidebar, linking to the doc sdk/dataEntities/signerOrProvider"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Smart contract addresses": {
+ "sidebar.buildAppsSidebar.doc.Smart contract addresses": {
"message": "Smart contract addresses",
- "description": "The label for the doc item Smart contract addresses in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/reference/useful-addresses"
+ "description": "The label for the doc item Smart contract addresses in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/reference/contract-addresses"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Chain Params": {
- "message": "Chain Params",
- "description": "The label for the doc item Chain Params in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/reference/chain-params"
+ "sidebar.buildAppsSidebar.doc.Solidity support": {
+ "message": "Solidity support",
+ "description": "The label for the doc item Solidity support in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/arbitrum-vs-ethereum/solidity-support"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Development frameworks": {
- "message": "Development frameworks",
- "description": "The label for the doc item Development frameworks in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/reference/development-frameworks"
+ "sidebar.buildAppsSidebar.doc.Structure of a Contract": {
+ "message": "Structure of a Contract",
+ "description": "The label for the doc item Structure of a Contract in sidebar buildAppsSidebar, linking to the doc stylus/reference/project-structure"
+ },
+ "sidebar.buildAppsSidebar.doc.Testing contracts": {
+ "message": "Testing contracts",
+ "description": "The label for the doc item Testing contracts in sidebar buildAppsSidebar, linking to the doc stylus/how-tos/testing-contracts"
+ },
+ "sidebar.buildAppsSidebar.doc.Transaction Request": {
+ "message": "Transaction Request",
+ "description": "The label for the doc item Transaction Request in sidebar buildAppsSidebar, linking to the doc sdk/dataEntities/transactionRequest"
+ },
+ "sidebar.buildAppsSidebar.doc.Troubleshooting": {
+ "message": "Troubleshooting",
+ "description": "The label for the doc item Troubleshooting in sidebar buildAppsSidebar, linking to the doc stylus/troubleshooting-building-stylus"
+ },
+ "sidebar.buildAppsSidebar.doc.Types": {
+ "message": "Types",
+ "description": "The label for the doc item Types in sidebar buildAppsSidebar, linking to the doc sdk/utils/types"
+ },
+ "sidebar.buildAppsSidebar.doc.Use the custom gateway": {
+ "message": "Use the custom gateway",
+ "description": "The label for the doc item Use the custom gateway in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/token-bridging/bridge-tokens-programmatically/how-to-bridge-tokens-custom-gateway"
+ },
+ "sidebar.buildAppsSidebar.doc.Use the generic-custom gateway": {
+ "message": "Use the generic-custom gateway",
+ "description": "The label for the doc item Use the generic-custom gateway in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/token-bridging/bridge-tokens-programmatically/how-to-bridge-tokens-generic-custom"
+ },
+ "sidebar.buildAppsSidebar.doc.Use the standard gateway": {
+ "message": "Use the standard gateway",
+ "description": "The label for the doc item Use the standard gateway in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/token-bridging/bridge-tokens-programmatically/how-to-bridge-tokens-standard"
+ },
+ "sidebar.buildAppsSidebar.doc.Using other languages": {
+ "message": "Using other languages",
+ "description": "The label for the doc item Using other languages in sidebar buildAppsSidebar, linking to the doc stylus/how-tos/adding-support-for-new-languages"
+ },
+ "sidebar.buildAppsSidebar.doc.Variables": {
+ "message": "Variables",
+ "description": "The label for the doc item Variables in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/variables"
+ },
+ "sidebar.buildAppsSidebar.doc.Vending Machine": {
+ "message": "Vending Machine",
+ "description": "The label for the doc item Vending Machine in sidebar buildAppsSidebar, linking to the doc stylus-by-example/applications/vending_machine"
+ },
+ "sidebar.buildAppsSidebar.doc.Verify contracts": {
+ "message": "Verify contracts",
+ "description": "The label for the doc item Verify contracts in sidebar buildAppsSidebar, linking to the doc stylus/how-tos/verifying-contracts"
+ },
+ "sidebar.buildAppsSidebar.doc.Verify on Arbiscan": {
+ "message": "Verify on Arbiscan",
+ "description": "The label for the doc item Verify on Arbiscan in sidebar buildAppsSidebar, linking to the doc stylus/how-tos/verifying-contracts-arbiscan"
+ },
+ "sidebar.buildAppsSidebar.doc.Vm Affordances": {
+ "message": "Vm Affordances",
+ "description": "The label for the doc item Vm Affordances in sidebar buildAppsSidebar, linking to the doc stylus-by-example/basic_examples/vm_affordances"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Web3 libraries and tools": {
+ "sidebar.buildAppsSidebar.doc.Web3 libraries and tools": {
"message": "Web3 libraries and tools",
- "description": "The label for the doc item Web3 libraries and tools in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/reference/web3-libraries-tools"
+ "description": "The label for the doc item Web3 libraries and tools in sidebar buildAppsSidebar, linking to the doc build-decentralized-apps/reference/web3-libraries-tools"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Monitoring tools and block explorers": {
- "message": "Monitoring tools and block explorers",
- "description": "The label for the doc item Monitoring tools and block explorers in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/reference/monitoring-tools-block-explorers"
+ "sidebar.buildAppsSidebar.link.Awesome Stylus": {
+ "message": "Awesome Stylus",
+ "description": "The label for link Awesome Stylus in sidebar buildAppsSidebar, linking to https://github.com/OffchainLabs/awesome-stylus"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Debugging tools": {
- "message": "Debugging tools",
- "description": "The label for the doc item Debugging tools in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/reference/debugging-tools"
+ "sidebar.buildAppsSidebar.link.Cargo Stylus CLI GitHub": {
+ "message": "Cargo Stylus CLI GitHub",
+ "description": "The label for link Cargo Stylus CLI GitHub in sidebar buildAppsSidebar, linking to https://github.com/OffchainLabs/cargo-stylus"
},
- "sidebar.buildDecentralizedAppsSidebar.doc.Mainnet risks": {
- "message": "Mainnet risks",
- "description": "The label for the doc item Mainnet risks in sidebar buildDecentralizedAppsSidebar, linking to the doc build-decentralized-apps/reference/mainnet-risks"
+ "sidebar.buildAppsSidebar.link.Rust SDK Crate": {
+ "message": "Rust SDK Crate",
+ "description": "The label for link Rust SDK Crate in sidebar buildAppsSidebar, linking to https://docs.rs/stylus-sdk/latest/stylus_sdk/index.html"
},
- "sidebar.bridgeTokensSidebar.category.Get started": {
- "message": "Get started",
- "description": "The label for category Get started in sidebar bridgeTokensSidebar"
+ "sidebar.buildAppsSidebar.link.Source Code Repository": {
+ "message": "Source Code Repository",
+ "description": "The label for link Source Code Repository in sidebar buildAppsSidebar, linking to https://github.com/OffchainLabs/stylus"
},
- "sidebar.bridgeTokensSidebar.category.Concepts": {
- "message": "Concepts",
- "description": "The label for category Concepts in sidebar bridgeTokensSidebar"
+ "sidebar.buildAppsSidebar.link.Stylus by Example": {
+ "message": "Stylus by Example",
+ "description": "The label for link Stylus by Example in sidebar buildAppsSidebar, linking to https://stylus-by-example.org/"
},
- "sidebar.bridgeTokensSidebar.category.More": {
- "message": "More",
- "description": "The label for category More in sidebar bridgeTokensSidebar"
+ "sidebar.buildAppsSidebar.link.Tutorials": {
+ "message": "Tutorials",
+ "description": "The label for link Tutorials in sidebar buildAppsSidebar, linking to https://github.com/OffchainLabs/arbitrum-tutorials"
},
- "sidebar.bridgeTokensSidebar.doc.A gentle introduction": {
- "message": "A gentle introduction",
- "description": "The label for the doc item A gentle introduction in sidebar bridgeTokensSidebar, linking to the doc bridge-tokens/gentle-introduction-bridge"
+ "sidebar.getStartedSidebar.category.Build apps": {
+ "message": "Build apps",
+ "description": "The label for category Build apps in sidebar getStartedSidebar"
},
- "sidebar.bridgeTokensSidebar.doc.Quickstart": {
- "message": "Quickstart",
- "description": "The label for the doc item Quickstart in sidebar bridgeTokensSidebar, linking to the doc arbitrum-bridge/quickstart"
+ "sidebar.getStartedSidebar.doc.Arbitrum: introduction": {
+ "message": "Arbitrum: introduction",
+ "description": "The label for the doc item Arbitrum: introduction in sidebar getStartedSidebar, linking to the doc get-started/arbitrum-introduction"
},
- "sidebar.bridgeTokensSidebar.doc.Troubleshooting": {
- "message": "Troubleshooting",
- "description": "The label for the doc item Troubleshooting in sidebar bridgeTokensSidebar, linking to the doc arbitrum-bridge/troubleshooting"
+ "sidebar.getStartedSidebar.doc.Build apps with Solidity": {
+ "message": "Build apps with Solidity",
+ "description": "The label for the doc item Build apps with Solidity in sidebar getStartedSidebar, linking to the doc build-decentralized-apps/quickstart-solidity-remix"
+ },
+ "sidebar.getStartedSidebar.doc.Build apps with Stylus": {
+ "message": "Build apps with Stylus",
+ "description": "The label for the doc item Build apps with Stylus in sidebar getStartedSidebar, linking to the doc stylus/quickstart"
},
- "sidebar.runNodesSidebar.category.Get started": {
+ "sidebar.getStartedSidebar.doc.Get started": {
"message": "Get started",
- "description": "The label for category Get started in sidebar runNodesSidebar"
+ "description": "The label for the doc item Get started in sidebar getStartedSidebar, linking to the doc get-started/overview"
+ },
+ "sidebar.getStartedSidebar.link.Arbitrum bridge": {
+ "message": "Arbitrum bridge",
+ "description": "The label for link Arbitrum bridge in sidebar getStartedSidebar, linking to /arbitrum-bridge/quickstart"
+ },
+ "sidebar.getStartedSidebar.link.How Arbitrum works": {
+ "message": "How Arbitrum works",
+ "description": "The label for link How Arbitrum works in sidebar getStartedSidebar, linking to /how-arbitrum-works/a-gentle-introduction"
+ },
+ "sidebar.getStartedSidebar.link.Run an Arbitrum (Orbit) chain": {
+ "message": "Run an Arbitrum (Orbit) chain",
+ "description": "The label for link Run an Arbitrum (Orbit) chain in sidebar getStartedSidebar, linking to /launch-arbitrum-chain/a-gentle-introduction"
+ },
+ "sidebar.getStartedSidebar.link.Run an Arbitrum node": {
+ "message": "Run an Arbitrum node",
+ "description": "The label for link Run an Arbitrum node in sidebar getStartedSidebar, linking to /run-arbitrum-node/overview"
+ },
+ "sidebar.howItWorksSidebar.category.How Arbitrum works": {
+ "message": "How Arbitrum works",
+ "description": "The label for category How Arbitrum works in sidebar howItWorksSidebar"
},
- "sidebar.runNodesSidebar.category.How-tos": {
- "message": "How-tos",
- "description": "The label for category How-tos in sidebar runNodesSidebar"
+ "sidebar.howItWorksSidebar.category.State Transition Function": {
+ "message": "State Transition Function",
+ "description": "The label for category State Transition Function in sidebar howItWorksSidebar"
},
- "sidebar.runNodesSidebar.category.More": {
- "message": "More",
- "description": "The label for category More in sidebar runNodesSidebar"
+ "sidebar.howItWorksSidebar.category.The BoLD dispute protocol": {
+ "message": "The BoLD dispute protocol",
+ "description": "The label for category The BoLD dispute protocol in sidebar howItWorksSidebar"
},
- "sidebar.runNodesSidebar.doc.A gentle introduction": {
+ "sidebar.howItWorksSidebar.category.Timeboost": {
+ "message": "Timeboost",
+ "description": "The label for category Timeboost in sidebar howItWorksSidebar"
+ },
+ "sidebar.howItWorksSidebar.category.Validation and Proving": {
+ "message": "Validation and Proving",
+ "description": "The label for category Validation and Proving in sidebar howItWorksSidebar"
+ },
+ "sidebar.howItWorksSidebar.doc.A gentle introduction": {
"message": "A gentle introduction",
- "description": "The label for the doc item A gentle introduction in sidebar runNodesSidebar, linking to the doc run-arbitrum-node/overview"
+ "description": "The label for the doc item A gentle introduction in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/bold/gentle-introduction"
},
- "sidebar.runNodesSidebar.doc.Quickstart": {
- "message": "Quickstart",
- "description": "The label for the doc item Quickstart in sidebar runNodesSidebar, linking to the doc run-arbitrum-node/quickstart"
+ "sidebar.howItWorksSidebar.doc.AnyTrust protocol": {
+ "message": "AnyTrust protocol",
+ "description": "The label for the doc item AnyTrust protocol in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/anytrust-protocol"
},
- "sidebar.runNodesSidebar.doc.Troubleshooting": {
- "message": "Troubleshooting",
- "description": "The label for the doc item Troubleshooting in sidebar runNodesSidebar, linking to the doc run-arbitrum-node/troubleshooting"
+ "sidebar.howItWorksSidebar.doc.ArbOS": {
+ "message": "ArbOS",
+ "description": "The label for the doc item ArbOS in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/state-transition-function/arbos"
},
- "sidebar.runNodesSidebar.doc.Frequently asked questions": {
- "message": "Frequently asked questions",
- "description": "The label for the doc item Frequently asked questions in sidebar runNodesSidebar, linking to the doc node-running/faq"
+ "sidebar.howItWorksSidebar.doc.Child to parent chain messaging": {
+ "message": "Child to parent chain messaging",
+ "description": "The label for the doc item Child to parent chain messaging in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/l2-to-l1-messaging"
},
- "sidebar.runNodesSidebar.doc.Command-line options": {
- "message": "Command-line options",
- "description": "The label for the doc item Command-line options in sidebar runNodesSidebar, linking to the doc node-running/command-line-options"
+ "sidebar.howItWorksSidebar.doc.Data Availability": {
+ "message": "Data Availability",
+ "description": "The label for the doc item Data Availability in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/data-availability"
},
- "sidebar.learnMoreSidebar.category.Get started": {
- "message": "Get started",
- "description": "The label for category Get started in sidebar learnMoreSidebar"
+ "sidebar.howItWorksSidebar.doc.Economics of disputes": {
+ "message": "Economics of disputes",
+ "description": "The label for the doc item Economics of disputes in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/bold/bold-economics-of-disputes"
},
- "sidebar.learnMoreSidebar.category.Introductory concepts": {
- "message": "Introductory concepts",
- "description": "The label for category Introductory concepts in sidebar learnMoreSidebar"
+ "sidebar.howItWorksSidebar.doc.Ethereum vs Arbitrum": {
+ "message": "Ethereum vs Arbitrum",
+ "description": "The label for the doc item Ethereum vs Arbitrum in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/state-transition-function/ethereum-vs-arbitrum"
},
- "sidebar.learnMoreSidebar.category.Gas / fees": {
- "message": "Gas / fees",
- "description": "The label for category Gas / fees in sidebar learnMoreSidebar"
+ "sidebar.howItWorksSidebar.doc.Gas and fees": {
+ "message": "Gas and fees",
+ "description": "The label for the doc item Gas and fees in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/gas-fees"
},
- "sidebar.learnMoreSidebar.category.Advanced concepts": {
- "message": "Advanced concepts",
- "description": "The label for category Advanced concepts in sidebar learnMoreSidebar"
+ "sidebar.howItWorksSidebar.doc.Modified Geth on Arbitrum": {
+ "message": "Modified Geth on Arbitrum",
+ "description": "The label for the doc item Modified Geth on Arbitrum in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/state-transition-function/modified-geth-on-arbitrum"
},
- "sidebar.learnMoreSidebar.category.Cross-chain messaging": {
- "message": "Cross-chain messaging",
- "description": "The label for category Cross-chain messaging in sidebar learnMoreSidebar"
+ "sidebar.howItWorksSidebar.doc.Parent to Child chain messaging": {
+ "message": "Parent to Child chain messaging",
+ "description": "The label for the doc item Parent to Child chain messaging in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/l1-to-l2-messaging"
+ },
+ "sidebar.howItWorksSidebar.doc.Proving and challenges": {
+ "message": "Proving and challenges",
+ "description": "The label for the doc item Proving and challenges in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/validation-and-proving/proving-and-challenges"
+ },
+ "sidebar.howItWorksSidebar.doc.Public preview": {
+ "message": "Public preview",
+ "description": "The label for the doc item Public preview in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/timeboost/gentle-introduction"
+ },
+ "sidebar.howItWorksSidebar.doc.Rollup protocol": {
+ "message": "Rollup protocol",
+ "description": "The label for the doc item Rollup protocol in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/validation-and-proving/rollup-protocol"
+ },
+ "sidebar.howItWorksSidebar.doc.STF Overview": {
+ "message": "STF Overview",
+ "description": "The label for the doc item STF Overview in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/state-transition-function/stf-gentle-intro"
+ },
+ "sidebar.howItWorksSidebar.doc.STF inputs": {
+ "message": "STF inputs",
+ "description": "The label for the doc item STF inputs in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/state-transition-function/stf-inputs"
+ },
+ "sidebar.howItWorksSidebar.doc.Sequencing, Followed by Deterministic Execution": {
+ "message": "Sequencing, Followed by Deterministic Execution",
+ "description": "The label for the doc item Sequencing, Followed by Deterministic Execution in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/transaction-lifecycle"
+ },
+ "sidebar.howItWorksSidebar.doc.Stylus execution path": {
+ "message": "Stylus execution path",
+ "description": "The label for the doc item Stylus execution path in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/state-transition-function/stylus-execution-path"
},
- "sidebar.learnMoreSidebar.category.ArbOS": {
+ "sidebar.howItWorksSidebar.doc.Technical deep dive": {
+ "message": "Technical deep dive",
+ "description": "The label for the doc item Technical deep dive in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/bold/bold-technical-deep-dive"
+ },
+ "sidebar.howItWorksSidebar.doc.The Sequencer and Censorship Resistance": {
+ "message": "The Sequencer and Censorship Resistance",
+ "description": "The label for the doc item The Sequencer and Censorship Resistance in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/sequencer"
+ },
+ "sidebar.howItWorksSidebar.doc.Timeboost FAQ": {
+ "message": "Timeboost FAQ",
+ "description": "The label for the doc item Timeboost FAQ in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/timeboost/timeboost-faq"
+ },
+ "sidebar.howItWorksSidebar.doc.Troubleshoot Timeboost": {
+ "message": "Troubleshoot Timeboost",
+ "description": "The label for the doc item Troubleshoot Timeboost in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/timeboost/troubleshoot-timeboost"
+ },
+ "sidebar.howItWorksSidebar.doc.Use Timeboost": {
+ "message": "Use Timeboost",
+ "description": "The label for the doc item Use Timeboost in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/timeboost/how-to-use-timeboost"
+ },
+ "sidebar.howItWorksSidebar.doc.Validation and proving overview": {
+ "message": "Validation and proving overview",
+ "description": "The label for the doc item Validation and proving overview in sidebar howItWorksSidebar, linking to the doc how-arbitrum-works/validation-and-proving/validation-and-proving"
+ },
+ "sidebar.howItWorksSidebar.link.Audit Report by Code4rena": {
+ "message": "Audit Report by Code4rena",
+ "description": "The label for link Audit Report by Code4rena in sidebar howItWorksSidebar, linking to https://code4rena.com/reports/2024-05-arbitrum-foundation"
+ },
+ "sidebar.howItWorksSidebar.link.Audit Report by Trail of Bits": {
+ "message": "Audit Report by Trail of Bits",
+ "description": "The label for link Audit Report by Trail of Bits in sidebar howItWorksSidebar, linking to https://github.com/trailofbits/publications/blob/master/reviews/2024-04-offchainbold-securityreview.pdf"
+ },
+ "sidebar.howItWorksSidebar.link.BoLD Whitepaper": {
+ "message": "BoLD Whitepaper",
+ "description": "The label for link BoLD Whitepaper in sidebar howItWorksSidebar, linking to https://arxiv.org/abs/2404.10491"
+ },
+ "sidebar.howItWorksSidebar.link.Deploy a validator on testnet": {
+ "message": "Deploy a validator on testnet",
+ "description": "The label for link Deploy a validator on testnet in sidebar howItWorksSidebar, linking to https://github.com/offchainlabs/bold-validator-starter-kit"
+ },
+ "sidebar.howItWorksSidebar.link.Nitro whitepaper": {
+ "message": "Nitro whitepaper",
+ "description": "The label for link Nitro whitepaper in sidebar howItWorksSidebar, linking to https://github.com/OffchainLabs/nitro/blob/master/docs/Nitro-whitepaper.pdf"
+ },
+ "sidebar.howItWorksSidebar.link.Specification on Github": {
+ "message": "Specification on Github",
+ "description": "The label for link Specification on Github in sidebar howItWorksSidebar, linking to https://github.com/OffchainLabs/bold"
+ },
+ "sidebar.howItWorksSidebar.link.Specification: Timeboost": {
+ "message": "Specification: Timeboost",
+ "description": "The label for link Specification: Timeboost in sidebar howItWorksSidebar, linking to https://github.com/OffchainLabs/timeboost-design/blob/main/research_spec.md"
+ },
+ "sidebar.howItWorksSidebar.link.Specification: Timeboost with decentralized sequencing": {
+ "message": "Specification: Timeboost with decentralized sequencing",
+ "description": "The label for link Specification: Timeboost with decentralized sequencing in sidebar howItWorksSidebar, linking to https://github.com/OffchainLabs/decentralized-timeboost-spec"
+ },
+ "sidebar.howItWorksSidebar.link.White paper: Timeboost": {
+ "message": "White paper: Timeboost",
+ "description": "The label for link White paper: Timeboost in sidebar howItWorksSidebar, linking to https://arxiv.org/abs/2306.02179"
+ },
+ "sidebar.runArbitrumChainSidebar.category.Advanced features": {
+ "message": "Advanced features",
+ "description": "The label for category Advanced features in sidebar runArbitrumChainSidebar"
+ },
+ "sidebar.runArbitrumChainSidebar.category.ArbOS": {
"message": "ArbOS",
- "description": "The label for category ArbOS in sidebar learnMoreSidebar"
+ "description": "The label for category ArbOS in sidebar runArbitrumChainSidebar"
+ },
+ "sidebar.runArbitrumChainSidebar.category.Common features": {
+ "message": "Common features",
+ "description": "The label for category Common features in sidebar runArbitrumChainSidebar"
+ },
+ "sidebar.runArbitrumChainSidebar.category.Configure AEP fee routing": {
+ "message": "Configure AEP fee routing",
+ "description": "The label for category Configure AEP fee routing in sidebar runArbitrumChainSidebar"
+ },
+ "sidebar.runArbitrumChainSidebar.category.Configure your chain": {
+ "message": "Configure your chain",
+ "description": "The label for category Configure your chain in sidebar runArbitrumChainSidebar"
+ },
+ "sidebar.runArbitrumChainSidebar.category.Customize your chain": {
+ "message": "Customize your chain",
+ "description": "The label for category Customize your chain in sidebar runArbitrumChainSidebar"
+ },
+ "sidebar.runArbitrumChainSidebar.category.Data Availability Committees": {
+ "message": "Data Availability Committees",
+ "description": "The label for category Data Availability Committees in sidebar runArbitrumChainSidebar"
+ },
+ "sidebar.runArbitrumChainSidebar.category.Deploy a production chain": {
+ "message": "Deploy a production chain",
+ "description": "The label for category Deploy a production chain in sidebar runArbitrumChainSidebar"
+ },
+ "sidebar.runArbitrumChainSidebar.category.Deploy an Arbitrum chain": {
+ "message": "Deploy an Arbitrum chain",
+ "description": "The label for category Deploy an Arbitrum chain in sidebar runArbitrumChainSidebar"
},
- "sidebar.learnMoreSidebar.category.Fraud proofs": {
- "message": "Fraud proofs",
- "description": "The label for category Fraud proofs in sidebar learnMoreSidebar"
+ "sidebar.runArbitrumChainSidebar.category.Guidance": {
+ "message": "Guidance",
+ "description": "The label for category Guidance in sidebar runArbitrumChainSidebar"
},
- "sidebar.learnMoreSidebar.category.More": {
- "message": "More",
- "description": "The label for category More in sidebar learnMoreSidebar"
+ "sidebar.runArbitrumChainSidebar.category.Maintain your chain": {
+ "message": "Maintain your chain",
+ "description": "The label for category Maintain your chain in sidebar runArbitrumChainSidebar"
},
- "sidebar.learnMoreSidebar.link.Deeper dive: Whitepaper": {
- "message": "Deeper dive: Whitepaper",
- "description": "The label for link Deeper dive: Whitepaper in sidebar learnMoreSidebar, linking to https://github.com/OffchainLabs/nitro/blob/master/docs/Nitro-whitepaper.pdf"
+ "sidebar.runArbitrumChainSidebar.category.Migrate your chain": {
+ "message": "Migrate your chain",
+ "description": "The label for category Migrate your chain in sidebar runArbitrumChainSidebar"
},
- "sidebar.learnMoreSidebar.doc.A gentle introduction": {
+ "sidebar.runArbitrumChainSidebar.category.Run a node for an Arbitrum chain": {
+ "message": "Run a node for an Arbitrum chain",
+ "description": "The label for category Run a node for an Arbitrum chain in sidebar runArbitrumChainSidebar"
+ },
+ "sidebar.runArbitrumChainSidebar.category.Run an Arbitrum (Orbit) chain": {
+ "message": "Run an Arbitrum (Orbit) chain",
+ "description": "The label for category Run an Arbitrum (Orbit) chain in sidebar runArbitrumChainSidebar"
+ },
+ "sidebar.runArbitrumChainSidebar.category.Third-party integrations and features": {
+ "message": "Third-party integrations and features",
+ "description": "The label for category Third-party integrations and features in sidebar runArbitrumChainSidebar"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.A gentle introduction": {
"message": "A gentle introduction",
- "description": "The label for the doc item A gentle introduction in sidebar learnMoreSidebar, linking to the doc intro/intro"
+ "description": "The label for the doc item A gentle introduction in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/a-gentle-introduction"
},
- "sidebar.learnMoreSidebar.doc.Frequently asked questions": {
- "message": "Frequently asked questions",
- "description": "The label for the doc item Frequently asked questions in sidebar learnMoreSidebar, linking to the doc learn-more/faq"
+ "sidebar.runArbitrumChainSidebar.doc.AEP fee router overview": {
+ "message": "AEP fee router overview",
+ "description": "The label for the doc item AEP fee router overview in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/advanced-configurations/aep-fee-router/aep-fee-router-introduction"
},
- "sidebar.learnMoreSidebar.doc.Glossary": {
- "message": "Glossary",
- "description": "The label for the doc item Glossary in sidebar learnMoreSidebar, linking to the doc intro/glossary"
+ "sidebar.runArbitrumChainSidebar.doc.Add your chain to the bridge": {
+ "message": "Add your chain to the bridge",
+ "description": "The label for the doc item Add your chain to the bridge in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/ecosystem-support/add-arbitrum-chain-to-bridge-ui"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Additional configuration parameters": {
+ "message": "Additional configuration parameters",
+ "description": "The label for the doc item Additional configuration parameters in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/reference/additional-configuration-parameters"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Arbitrum chain licensing": {
+ "message": "Arbitrum chain licensing",
+ "description": "The label for the doc item Arbitrum chain licensing in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/aep-license"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.BoLD for Arbitrum chains": {
+ "message": "BoLD for Arbitrum chains",
+ "description": "The label for the doc item BoLD for Arbitrum chains in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/common-configurations/bold-adoption-for-arbitrum-chains"
},
- "sidebar.learnMoreSidebar.doc.Why Nitro?": {
- "message": "Why Nitro?",
- "description": "The label for the doc item Why Nitro? in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/why-nitro"
+ "sidebar.runArbitrumChainSidebar.doc.Calculate AEP license fees": {
+ "message": "Calculate AEP license fees",
+ "description": "The label for the doc item Calculate AEP license fees in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/advanced-configurations/aep-fee-router/calculate-aep-fees"
},
- "sidebar.learnMoreSidebar.doc.Transaction lifecycle": {
- "message": "Transaction lifecycle",
- "description": "The label for the doc item Transaction lifecycle in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/tx-lifecycle"
+ "sidebar.runArbitrumChainSidebar.doc.Canonical factory contracts": {
+ "message": "Canonical factory contracts",
+ "description": "The label for the doc item Canonical factory contracts in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/deploy-an-arbitrum-chain/canonical-factory-contracts"
},
- "sidebar.learnMoreSidebar.doc.Sequencer": {
+ "sidebar.runArbitrumChainSidebar.doc.Configure Batch Poster and Assertion Control": {
+ "message": "Configure Batch Poster and Assertion Control",
+ "description": "The label for the doc item Configure Batch Poster and Assertion Control in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/common-configurations/batch-posting-assertion-control"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Configure a Data Availability Committee (DAC)": {
+ "message": "Configure a Data Availability Committee (DAC)",
+ "description": "The label for the doc item Configure a Data Availability Committee (DAC) in sidebar runArbitrumChainSidebar, linking to the doc run-arbitrum-node/data-availability-committees/configure-dac"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Configure a custom AnyTrust gas token": {
+ "message": "Configure a custom AnyTrust gas token",
+ "description": "The label for the doc item Configure a custom AnyTrust gas token in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/common-configurations/use-a-custom-gas-token-anytrust"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Configure a custom Rollup gas token": {
+ "message": "Configure a custom Rollup gas token",
+ "description": "The label for the doc item Configure a custom Rollup gas token in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/common-configurations/use-a-custom-gas-token-rollup"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Configure delayed inbox finality": {
+ "message": "Configure delayed inbox finality",
+ "description": "The label for the doc item Configure delayed inbox finality in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/common-configurations/arbitrum-chain-finality"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Customize ArbOS version": {
+ "message": "Customize ArbOS version",
+ "description": "The label for the doc item Customize ArbOS version in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/customize-your-chain/customize-arbos"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Customize the challenge period": {
+ "message": "Customize the challenge period",
+ "description": "The label for the doc item Customize the challenge period in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/common-configurations/customizable-challenge-period"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Customize your chain's behavior": {
+ "message": "Customize your chain's behavior",
+ "description": "The label for the doc item Customize your chain's behavior in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/customize-your-chain/customize-stf"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Customize your chain's deployment": {
+ "message": "Customize your chain's deployment",
+ "description": "The label for the doc item Customize your chain's deployment in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/how-tos/customize-deployment-configuration"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Customize your chain's precompiles": {
+ "message": "Customize your chain's precompiles",
+ "description": "The label for the doc item Customize your chain's precompiles in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/customize-your-chain/customize-precompile"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Deploy a Data Availability Server (DAS)": {
+ "message": "Deploy a Data Availability Server (DAS)",
+ "description": "The label for the doc item Deploy a Data Availability Server (DAS) in sidebar runArbitrumChainSidebar, linking to the doc run-arbitrum-node/data-availability-committees/deploy-das"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Deploy a mirror Data Availability Server": {
+ "message": "Deploy a mirror Data Availability Server",
+ "description": "The label for the doc item Deploy a mirror Data Availability Server in sidebar runArbitrumChainSidebar, linking to the doc run-arbitrum-node/data-availability-committees/deploy-mirror-das"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Deploy a token bridge": {
+ "message": "Deploy a token bridge",
+ "description": "The label for the doc item Deploy a token bridge in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/deploy-an-arbitrum-chain/deploying-token-bridge"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Deploy an Arbitrum chain": {
+ "message": "Deploy an Arbitrum chain",
+ "description": "The label for the doc item Deploy an Arbitrum chain in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/deploy-an-arbitrum-chain/deploying-an-arbitrum-chain"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Enable blob transactions": {
+ "message": "Enable blob transactions",
+ "description": "The label for the doc item Enable blob transactions in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/common-configurations/enable-post-4844-blobs"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Enable fast withdrawals": {
+ "message": "Enable fast withdrawals",
+ "description": "The label for the doc item Enable fast withdrawals in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/advanced-configurations/fast-withdrawals"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.FAQ": {
+ "message": "FAQ",
+ "description": "The label for the doc item FAQ in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/faq-troubleshooting/troubleshooting-building-arbitrum-chain"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Gas optimization tools": {
+ "message": "Gas optimization tools",
+ "description": "The label for the doc item Gas optimization tools in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/common-configurations/gas-optimization-tools"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Generate the node config file": {
+ "message": "Generate the node config file",
+ "description": "The label for the doc item Generate the node config file in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/how-tos/arbitrum-chain-sdk-preparing-node-config"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Get started": {
+ "message": "Get started",
+ "description": "The label for the doc item Get started in sidebar runArbitrumChainSidebar, linking to the doc run-arbitrum-node/data-availability-committees/get-started"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Implement Circle bridged USDC": {
+ "message": "Implement Circle bridged USDC",
+ "description": "The label for the doc item Implement Circle bridged USDC in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/third-party-integrations/bridged-usdc-standard"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Manage gas speed limit": {
+ "message": "Manage gas speed limit",
+ "description": "The label for the doc item Manage gas speed limit in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/maintain-your-chain/guidance/state-size-limit"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Manage gas state growth": {
+ "message": "Manage gas state growth",
+ "description": "The label for the doc item Manage gas state growth in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/maintain-your-chain/guidance/state-growth"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Manage the fee parameters": {
+ "message": "Manage the fee parameters",
+ "description": "The label for the doc item Manage the fee parameters in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/common-configurations/fee-management"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Migrate between RaaSes": {
+ "message": "Migrate between RaaSes",
+ "description": "The label for the doc item Migrate between RaaSes in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/migrate-between-raases"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Migrate from another stack": {
+ "message": "Migrate from another stack",
+ "description": "The label for the doc item Migrate from another stack in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/migrate-from-another-stack"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Monitoring tools and considerations": {
+ "message": "Monitoring tools and considerations",
+ "description": "The label for the doc item Monitoring tools and considerations in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/maintain-your-chain/monitoring-tools-and-considerations"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Overview": {
+ "message": "Overview",
+ "description": "The label for the doc item Overview in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/arbitrum-chain-sdk-introduction"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Ownership structure and access control": {
+ "message": "Ownership structure and access control",
+ "description": "The label for the doc item Ownership structure and access control in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/maintain-your-chain/ownership-structure-access-control"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Post-launch deployments": {
+ "message": "Post-launch deployments",
+ "description": "The label for the doc item Post-launch deployments in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/maintain-your-chain/guidance/post-launch-contract-deployments"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Public preview": {
+ "message": "Public preview",
+ "description": "The label for the doc item Public preview in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/concepts/public-preview-expectations"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Report your fees": {
+ "message": "Report your fees",
+ "description": "The label for the doc item Report your fees in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/advanced-configurations/aep-fee-router/reporting-on-fees"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Set up AEP fee router": {
+ "message": "Set up AEP fee router",
+ "description": "The label for the doc item Set up AEP fee router in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/advanced-configurations/aep-fee-router/set-up-aep-fee-router"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Third-party infrastructure providers": {
+ "message": "Third-party infrastructure providers",
+ "description": "The label for the doc item Third-party infrastructure providers in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/third-party-integrations/third-party-providers"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Timeboost for Arbitrum chains": {
+ "message": "Timeboost for Arbitrum chains",
+ "description": "The label for the doc item Timeboost for Arbitrum chains in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/common-configurations/timeboost-for-arbitrum-chains"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Upgrade ArbOS": {
+ "message": "Upgrade ArbOS",
+ "description": "The label for the doc item Upgrade ArbOS in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/common-configurations/arbos-upgrade"
+ },
+ "sidebar.runArbitrumChainSidebar.doc.Use Layer Leap": {
+ "message": "Use Layer Leap",
+ "description": "The label for the doc item Use Layer Leap in sidebar runArbitrumChainSidebar, linking to the doc launch-arbitrum-chain/configure-your-chain/advanced-configurations/layer-leap"
+ },
+ "sidebar.runNodeSidebar.category.ArbOS software releases": {
+ "message": "ArbOS software releases",
+ "description": "The label for category ArbOS software releases in sidebar runNodeSidebar"
+ },
+ "sidebar.runNodeSidebar.category.More node types": {
+ "message": "More node types",
+ "description": "The label for category More node types in sidebar runNodeSidebar"
+ },
+ "sidebar.runNodeSidebar.category.Run an Arbitrum node": {
+ "message": "Run an Arbitrum node",
+ "description": "The label for category Run an Arbitrum node in sidebar runNodeSidebar"
+ },
+ "sidebar.runNodeSidebar.category.Sequencer": {
"message": "Sequencer",
- "description": "The label for the doc item Sequencer in sidebar learnMoreSidebar, linking to the doc sequencer"
+ "description": "The label for category Sequencer in sidebar runNodeSidebar"
},
- "sidebar.learnMoreSidebar.doc.AnyTrust protocol": {
- "message": "AnyTrust protocol",
- "description": "The label for the doc item AnyTrust protocol in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/inside-anytrust"
+ "sidebar.runNodeSidebar.doc.ArbOS 11": {
+ "message": "ArbOS 11",
+ "description": "The label for the doc item ArbOS 11 in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/arbos-releases/arbos11"
},
- "sidebar.learnMoreSidebar.doc.L2 gas": {
- "message": "L2 gas",
- "description": "The label for the doc item L2 gas in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/gas-fees"
+ "sidebar.runNodeSidebar.doc.Atlas (ArbOS 20)": {
+ "message": "Atlas (ArbOS 20)",
+ "description": "The label for the doc item Atlas (ArbOS 20) in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/arbos-releases/arbos20"
},
- "sidebar.learnMoreSidebar.doc.L1 pricing": {
- "message": "L1 pricing",
- "description": "The label for the doc item L1 pricing in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/l1-gas-pricing"
+ "sidebar.runNodeSidebar.doc.Bianca (ArbOS 32)": {
+ "message": "Bianca (ArbOS 32)",
+ "description": "The label for the doc item Bianca (ArbOS 32) in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/arbos-releases/arbos32"
},
- "sidebar.learnMoreSidebar.doc.Deep dive: Inside Arbitrum": {
- "message": "Deep dive: Inside Arbitrum",
- "description": "The label for the doc item Deep dive: Inside Arbitrum in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/inside-arbitrum-nitro"
+ "sidebar.runNodeSidebar.doc.Build Nitro locally": {
+ "message": "Build Nitro locally",
+ "description": "The label for the doc item Build Nitro locally in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/nitro/build-nitro-locally"
},
- "sidebar.learnMoreSidebar.doc.Assertion tree": {
- "message": "Assertion tree",
- "description": "The label for the doc item Assertion tree in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/assertion-tree"
+ "sidebar.runNodeSidebar.doc.Callisto (ArbOS 40)": {
+ "message": "Callisto (ArbOS 40)",
+ "description": "The label for the doc item Callisto (ArbOS 40) in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/arbos-releases/arbos40"
},
- "sidebar.learnMoreSidebar.doc.L1-to-L2 messaging": {
- "message": "L1-to-L2 messaging",
- "description": "The label for the doc item L1-to-L2 messaging in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/arbos/l1-l2-messaging"
+ "sidebar.runNodeSidebar.doc.Convert databases from LevelDB to Pebble": {
+ "message": "Convert databases from LevelDB to Pebble",
+ "description": "The label for the doc item Convert databases from LevelDB to Pebble in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/nitro/how-to-convert-databases-from-leveldb-to-pebble"
},
- "sidebar.learnMoreSidebar.doc.L2-to-L1 messaging": {
- "message": "L2-to-L1 messaging",
- "description": "The label for the doc item L2-to-L1 messaging in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/arbos/l2-l1-messaging"
+ "sidebar.runNodeSidebar.doc.Database snapshots": {
+ "message": "Database snapshots",
+ "description": "The label for the doc item Database snapshots in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/nitro/nitro-database-snapshots"
},
- "sidebar.learnMoreSidebar.doc.ArbOS": {
- "message": "ArbOS",
- "description": "The label for the doc item ArbOS in sidebar learnMoreSidebar, linking to the doc arbos/arbos"
+ "sidebar.runNodeSidebar.doc.FAQ": {
+ "message": "FAQ",
+ "description": "The label for the doc item FAQ in sidebar runNodeSidebar, linking to the doc node-running/faq"
},
- "sidebar.learnMoreSidebar.doc.Geth": {
- "message": "Geth",
- "description": "The label for the doc item Geth in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/arbos/geth"
+ "sidebar.runNodeSidebar.doc.L1 Ethereum RPC providers": {
+ "message": "L1 Ethereum RPC providers",
+ "description": "The label for the doc item L1 Ethereum RPC providers in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/l1-ethereum-beacon-chain-rpc-providers"
},
- "sidebar.learnMoreSidebar.doc.Interactive challenges": {
- "message": "Interactive challenges",
- "description": "The label for the doc item Interactive challenges in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/fraud-proofs/challenge-manager"
+ "sidebar.runNodeSidebar.doc.Migrate to Nitro from Classic": {
+ "message": "Migrate to Nitro from Classic",
+ "description": "The label for the doc item Migrate to Nitro from Classic in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/nitro/migrate-state-and-history-from-classic"
},
- "sidebar.learnMoreSidebar.doc.One step proof assumptions": {
- "message": "One step proof assumptions",
- "description": "The label for the doc item One step proof assumptions in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/fraud-proofs/osp-assumptions"
+ "sidebar.runNodeSidebar.doc.Overview": {
+ "message": "Overview",
+ "description": "The label for the doc item Overview in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/arbos-releases/overview"
},
- "sidebar.learnMoreSidebar.doc.Wasm To WAVM": {
- "message": "Wasm To WAVM",
- "description": "The label for the doc item Wasm To WAVM in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/fraud-proofs/wasm-wavm"
+ "sidebar.runNodeSidebar.doc.Read the sequencer feed": {
+ "message": "Read the sequencer feed",
+ "description": "The label for the doc item Read the sequencer feed in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/sequencer/read-sequencer-feed"
},
- "sidebar.learnMoreSidebar.doc.Custom WAVM opcodes": {
- "message": "Custom WAVM opcodes",
- "description": "The label for the doc item Custom WAVM opcodes in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/fraud-proofs/wavm-custom-opcodes"
+ "sidebar.runNodeSidebar.doc.Run a Classic node": {
+ "message": "Run a Classic node",
+ "description": "The label for the doc item Run a Classic node in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/more-types/run-classic-node"
},
- "sidebar.learnMoreSidebar.doc.WAVM floats": {
- "message": "WAVM floats",
- "description": "The label for the doc item WAVM floats in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/fraud-proofs/wavm-floats"
+ "sidebar.runNodeSidebar.doc.Run a Sequencer Coordination Manager (SQM)": {
+ "message": "Run a Sequencer Coordination Manager (SQM)",
+ "description": "The label for the doc item Run a Sequencer Coordination Manager (SQM) in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/sequencer/run-sequencer-coordination-manager"
},
- "sidebar.learnMoreSidebar.doc.WAVM modules": {
- "message": "WAVM modules",
- "description": "The label for the doc item WAVM modules in sidebar learnMoreSidebar, linking to the doc how-arbitrum-works/fraud-proofs/wavm-modules"
+ "sidebar.runNodeSidebar.doc.Run a feed relay": {
+ "message": "Run a feed relay",
+ "description": "The label for the doc item Run a feed relay in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/run-feed-relay"
},
- "sidebar.learnMoreSidebar.doc.Audit reports": {
- "message": "Audit reports",
- "description": "The label for the doc item Audit reports in sidebar learnMoreSidebar, linking to the doc audit-reports"
+ "sidebar.runNodeSidebar.doc.Run a full node": {
+ "message": "Run a full node",
+ "description": "The label for the doc item Run a full node in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/run-full-node"
+ },
+ "sidebar.runNodeSidebar.doc.Run a local dev node": {
+ "message": "Run a local dev node",
+ "description": "The label for the doc item Run a local dev node in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/run-nitro-dev-node"
+ },
+ "sidebar.runNodeSidebar.doc.Run a local full chain simulation": {
+ "message": "Run a local full chain simulation",
+ "description": "The label for the doc item Run a local full chain simulation in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/run-local-full-chain-simulation"
+ },
+ "sidebar.runNodeSidebar.doc.Run a sequencer node": {
+ "message": "Run a sequencer node",
+ "description": "The label for the doc item Run a sequencer node in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/sequencer/run-sequencer-node"
+ },
+ "sidebar.runNodeSidebar.doc.Run a split validator": {
+ "message": "Run a split validator",
+ "description": "The label for the doc item Run a split validator in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/more-types/run-split-validator-node"
+ },
+ "sidebar.runNodeSidebar.doc.Run a validator": {
+ "message": "Run a validator",
+ "description": "The label for the doc item Run a validator in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/more-types/run-validator-node"
+ },
+ "sidebar.runNodeSidebar.doc.Run an archive node": {
+ "message": "Run an archive node",
+ "description": "The label for the doc item Run an archive node in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/more-types/run-archive-node"
+ },
+ "sidebar.runNodeSidebar.doc.Run high availability sequencer nodes": {
+ "message": "Run high availability sequencer nodes",
+ "description": "The label for the doc item Run high availability sequencer nodes in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/sequencer/high-availability-sequencer-docs"
+ },
+ "sidebar.runNodeSidebar.doc.Troubleshooting": {
+ "message": "Troubleshooting",
+ "description": "The label for the doc item Troubleshooting in sidebar runNodeSidebar, linking to the doc run-arbitrum-node/troubleshooting"
+ },
+ "version.label": {
+ "message": "Next",
+ "description": "The label for version current"
}
}
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current.json b/i18n/zh/docusaurus-plugin-content-docs/current.json
index d61bacbefa..adf523fd81 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/current.json
+++ b/i18n/zh/docusaurus-plugin-content-docs/current.json
@@ -3,9 +3,9 @@
"message": "Next",
"description": "The label for version current"
},
- "sidebar.buildDecentralizedAppsSidebar.category.Build dApps (Solidity)": {
- "message": "Build dApps (Solidity)",
- "description": "The label for category Build dApps (Solidity) in sidebar buildDecentralizedAppsSidebar"
+ "sidebar.buildDecentralizeappsSidebar.category.Build apps (Solidity)": {
+ "message": "Build apps (Solidity)",
+ "description": "The label for category Build apps (Solidity) in sidebar buildDecentralizedAppsSidebar"
},
"sidebar.buildDecentralizedAppsSidebar.category.How-tos": {
"message": "How-tos",
diff --git a/static/glossary.json b/static/glossary.json
index 5319f42ac4..e11f822ecd 100644
--- a/static/glossary.json
+++ b/static/glossary.json
@@ -1,102 +1,402 @@
{
-"active-validator":{"title":"Active Validator","text":"A bonded Validator that makes disputable assertions to advance the state of an Arbitrum chain or to challenge the validity of others' assertions. (Not to be confused with the Sequencer.)
\n"},
-"address-alias":{"title":"Address Alias","text":"An address deterministically generated from a parent chain contract address used on child chain to safely identify the source of an parent to child chain message.
\n"},
-"arb-token-bridge":{"title":"Arb Token Bridge","text":"A series of contracts on an Arbitrum chain and its underlying chain that facilitate trustless movement of ERC-20 tokens between the two layers.
\n"},
-"arbified-token-list":{"title":"Arbified Token List","text":"A token list that conforms to Uniswap's token list specification; Arbified lists are generated by inputting externally maintained list (i.e., coinmarketcap's list) and outputting a list that includes all of the instances of token contracts on the Arbitrum chain bridged via the canonical Arb Token Bridge from tokens on the input list. (See code here.)
\n"},
-"arbitrum":{"title":"Arbitrum","text":"A suite of Ethereum child chain scaling technologies built with the Arbitrum Nitro tech stack that includes Arbitrum One (a live implementation of the Arbitrum Rollup Protocol) and Arbitrum Nova (a live implementation of the Arbitrum AnyTrust Protocol).
\n"},
-"arbitrum-anytrust-chain":{"title":"Arbitrum AnyTrust Chain","text":"An Arbitrum chain that implements the Arbitrum AnyTrust Protocol.
\n"},
-"arbitrum-anytrust-protocol":{"title":"Arbitrum AnyTrust Protocol","text":"An Arbitrum protocol that manages data availability with a permissioned set of parties known as the Data Availability Committee (DAC). This protocol reduces transaction fees by introducing an additional trust assumption for data availability in lieu of Ethereum's Trustless data availability mechanism. Arbitrum Nova is an example of an AnyTrust chain; Arbitrum One is an alternative chain that implements the purely trustless (and more L1-gas intensive) Arbitrum Rollup Protocol.
\n"},
-"arbitrum-bridge-ui":{"title":"Arbitrum Bridge UI","text":"Web application built and maintained by Offchain Labs for user-interactions with the Arb Token Bridge; visit it here.
\n"},
-"arbitrum-chain":{"title":"Arbitrum chain","text":"A blockchain that runs on the Arbitrum protocol. Arbitrum chains are EVM compatible, and use an underlying EVM chain (e.g., Ethereum) for settlement and for succinct fraud-proofs (as needed). Arbitrum chains come in two forms: Arbitrum Rollup Chains and Arbitrum AnyTrust Chains.
\n"},
-"arbitrum-chains":{"title":"Arbitrum Chains","text":"Arbitrum chains (Orbit) refers to the ability for anyone to permissionlessly deploy Layer 3 (L3) chains on top of Arbitrum Layer 2 (L2) chains.
\n"},
-"arbitrum-classic":{"title":"Arbitrum Classic","text":"Old Arbitrum stack that used custom virtual machine ("AVM"); no public Arbitrum chain uses the classic stack as of 8/31/2022 (they instead use Arbitrum Nitro.)
\n"},
-"arbitrum-full-node":{"title":"Arbitrum Full Node","text":"A party who keeps track of the state of an Arbitrum chain and receives remote procedure calls (RPCs) from clients. Analogous to a non-staking parent Ethereum node.
\n"},
-"arbitrum-nitro":{"title":"Arbitrum Nitro","text":"Current Arbitrum tech stack; runs a fork of Geth and uses WebAssembly as its underlying VM for fraud proofs.
\n"},
-"arbitrum-nova":{"title":"Arbitrum Nova","text":"The first Arbitrum AnyTrust Chain running on Ethereum mainnet. Introduces cheaper transactions; great for gaming and social use-cases. Implements the Arbitrum AnyTrust Protocol, not the Arbitrum Rollup Protocol protocol. Governed by the Arbitrum DAO.
\n"},
-"arbitrum-one":{"title":"Arbitrum One","text":"The first Arbitrum Rollup Chain running on Ethereum mainnet. Great for decentralized finance and other use-cases that demand strong security guarantees. Governed by the Arbitrum DAO.
\n"},
-"arbitrum-rollup-chain":{"title":"Arbitrum Rollup Chain","text":"An Arbitrum chain that implements the Arbitrum Rollup Protocol.
\n"},
-"arbitrum-rollup-protocol":{"title":"Arbitrum Rollup Protocol","text":"A trustless, permissionless Arbitrum protocol that uses its underlying base layer for data availability and inherits its security. This protocol is implemented by our Arbitrum One chain.
\n"},
-"arbos":{"title":"ArbOS","text":"Arbitrum's "operating system" that trustlessly handles system-level operations; includes the ability to emulate the EVM.
\n"},
-"assertion":{"title":"Assertion","text":"A bonded claim made by an Arbitrum Validator representing a claim about an Arbitrum chain's state. An Assertion may, e.g., propose a new assertion, or may be a step in a Challenge.
\n"},
-"auction-contract":{"title":"Auction Contract","text":"A smart contract that handles the state, accounting of funds for bids, and various operations of the Timeboost auction. The contract is deployed on the target chain for which Timeboost is enabled.
\n"},
-"autonomous-auctioneer":{"title":"Autonomous Auctioneer","text":"Offchain software that receives bids from Timeboost participants, processes and validates bids, and then posts the top valid bid (or top two valid bids in the case of a tie) to the Auction Contract to resolve the on going Timeboost auction. The autonomous auctioneer, for a given chain, is provisioned and deployed by an entity designated by the chain's owner.
\n"},
-"batch":{"title":"Batch","text":"A group of Arbitrum transactions posted in a single transaction on the Underlying Chain into the Sequencer Inbox by the Sequencer.
\n"},
-"blockchain":{"title":"Blockchain","text":"A distributed digital ledger that is used to record transactions and store data in a secure, transparent, and tamper-resistant way, notably in cryptocurrency protocols.
\n"},
-"bls-signature":{"title":"BLS Signature","text":"A cryptographic scheme that allows multiple signatures to be aggregated and compacted into one efficiently verifiable, constant-sized signature. Used in the Arbitrum AnyTrust Protocol for the Data Availability Committee (DAC)'s signatures.
\n"},
-"bold":{"title":"BoLD","text":"Short for "Bounded Liquidity Delay"; latest version of the Arbitrum Challenge protocol designed to eliminate delay attack vectors (see here for more).
\n"},
-"bonder":{"title":"Bonder","text":"A Validator who deposits a bond (in Ether on Arbitrum One and Arbitrum Nova ) to vouch for a particular assertion in an Arbitrum Chain. A validator who bonds on a false assertion can expect to lose their bond. An honest bonder can recover their bond once the assertion they are bonded on has been confirmed.\nAlso known as: staker
\n"},
-"bridge":{"title":"Bridge","text":"A set of smart contracts for sending Cross-chain messages between blockchains. Every Arbitrum chain includes a bridge to/from its Parent chain.
\n"},
-"chain-owner":{"title":"Chain Owner","text":"An entity (i.e., a smart contract) with affordance to carry out critical upgrades to an Arbitrum chain's core protocol; this includes upgrading protocol contracts, setting core system parameters, and adding and removing other chain owners.
\n"},
-"chain-state":{"title":"Chain state","text":"A particular point in the history of an Arbitrum chain. A chain's state is determined by applying Arbitrum state-transition function to sequence of transactions (i.e., the chain's history).
\n"},
-"challenge":{"title":"Challenge","text":"When two bonders disagree about the correct verdict on an assertion, those bonders can be put in a challenge. The challenge is refereed by the contracts on the underlying chain. Eventually one bonder wins the challenge. The protocol guarantees that an honest party will always win a challenge; the loser forfeits their bond.
\n"},
-"challenge-period":{"title":"Challenge Period","text":"Window of time (one week on Arbitrum One) over which an Assertion can be challenged, and after which the assertion can be confirmed.
\n"},
-"challenge-protocol":{"title":"Challenge protocol","text":"The protocol by which assertions are submitted, disputed, and ultimately confirmed. The Challenge Protocol guarantees that only valid assertions will be confirmed provided that there is at least one honest active validator.
\n"},
-"child-chain":{"title":"Child chain","text":"An Arbitrum Chain that settles to a Parent chain. For example, Arbitrum One and Arbitrum Nova are child chains of Ethereum.
\n"},
-"client":{"title":"Client","text":"A program running on a user's machine, often in the user's browser, that interacts with contracts on an Arbitrum chain and provides a user interface.
\n"},
-"confirmation":{"title":"Confirmation","text":"The decision by an Arbitrum chain to finalize an assertion as part of the chain's history. Once an assertion is confirmed its Child to parent chain Messages (e.g., withdrawals) can be executed.
\n"},
-"crosschain-message":{"title":"Cross-chain message","text":"An action taken on some chain A which asynchronously initiates an additional action on chain B.
\n"},
-"custom-arbtoken":{"title":"Custom Arb-Token","text":"Any child chain token contract registered to the Arb Token Bridge that isn't a standard arb-token (i.e., a token that uses any gateway other than the StandardERC20 gateway ).
\n"},
-"custom-gateway":{"title":"Custom gateway","text":"Any Token Gateway that isn't the StandardERC20 gateway.
\n"},
-"dapp":{"title":"dApp","text":"Short for "decentralized application." A dApp typically consists of smart contracts as well as a user-interface for interacting with them.
\n"},
-"data-availability-certificate":{"title":"Data Availability Certificate","text":"Signed promise from a Data Availability Committee (DAC) attesting to the availability of a batch of data for an Arbitrum AnyTrust Chain.
\n"},
-"data-availability-committee-dac":{"title":"Data Availability Committee (DAC)","text":"A permissioned set of parties responsible for enforcing data availability on a chain using the Arbitrum AnyTrust Protocol.
\nSee Introducing AnyTrust Chains: Cheaper, Faster L2 Chains with Minimal Trust Assumptions to learn more.
\n"},
-"defensive-validator":{"title":"Defensive Validator","text":"A Validator that watches an Arbitrum chain and takes action (i.e., bonds and challenges) only when and if an invalid Assertion occurs.
\n"},
-"delayed-inbox":{"title":"Delayed Inbox","text":"A contract that holds Parent chain initiated messages to be eventually included in the Sequencer Inbox. Inclusion of messages doesn't depend on the Sequencer.
\n"},
-"devtools-dashboard":{"title":"Dev-Tools Dashboard","text":"Web application built and maintained by Offchain Labs for developers and users to debug Arbitrum transactions; i.e., executing or checking the status of Cross-chain messages; visit it here.
\n"},
-"dissection":{"title":"Dissection","text":"A step in the Challenge protocol in which two challenging parties interactively narrow down their disagreement until they reach a One Step Proof.
\n"},
-"ethereum-wallet":{"title":"Ethereum Wallet","text":"A software application used for transacting with the Ethereum Blockchain.
\n"},
-"evm":{"title":"EVM+","text":"The paradigm introduced by Stylus in which Arbitrum's EVM compatibility is preserved while new features and improvements are introduced.
\n"},
-"express-lane":{"title":"Express Lane","text":"A component of Timeboost, the express lane is a special endpoint on the Sequencer that immediately sequences incoming, valid transactions signed by the current express lane controller.
\n"},
-"express-lane-controller":{"title":"Express Lane Controller","text":"An address, defined in the Auction Contract, that is granted the privilege to use the Express Lane. These privileges are granted after verifying that the incoming transactions were properly signed by the express lane controller, among other checks.
\n"},
-"externally-owned-accounts":{"title":"Externally Owned Accounts","text":"An externally owned account (EOA) is the account (public/private key pairs) that has a physical address location. Commonly referred to as a wallet, however, we distinguish an EOA from the user client software wallet.
\n"},
-"fast-exit--liquidity-exit":{"title":"Fast Exit / Liquidity Exit","text":"A means by which a user can bypass an Arbitrum chain's Challenge Period when withdrawing fungible assets (or more generally, executing some "fungible" child chain to parent chain operation); for trustless fast exits, a liquidity provider facilitates an atomic swap of the asset on a child chain directly to a parent chain.
\n"},
-"first-come-first-serve-fcfs":{"title":"First Come First Serve (FCFS)","text":"A type of Transaction Ordering Policy used by the sequencer in Arbitrum chains whereby incoming transactions are sequenced into a block in the order that the transactions arrived.
\n"},
-"forceinclusion":{"title":"Force-Inclusion","text":"Censorship resistant path for including a message into an Arbitrum chain via the Delayed Inbox on its Parent chain; bypasses any Sequencer involvement.
\n"},
-"fraud-proof":{"title":"Fraud proof","text":"The means by which an Active Validator proves to its underlying chain that an invalid state transition has taken place.
\n"},
-"gas-price-floor":{"title":"Gas Price Floor","text":"Protocol-enforced minimum gas price on an Arbitrum chain; currently 0.1 gwei on Arbitrum One and 0.01 gwei on Arbitrum Nova.
\n"},
-"gateway-router":{"title":"Gateway Router","text":"Contracts in the Arb Token Bridge responsible for mapping tokens to their appropriate Token Gateway.
\n"},
-"genericcustom-gateway":{"title":"Generic-Custom Gateway","text":"A particular Custom gateway via which a parent chain token contract can be registered to a token contract deployed to a child chain. A useful alternative to the StandardERC20 gateway for projects that wish to control the address of their child chain token contract, maintain the child chain token contract upgradability, and for various other use-cases.
\n"},
-"geth":{"title":"Geth","text":"An execution-layer client that defines the Ethereum state transition function and handles network-layer logic like transaction memory pooling. Arbitrum Nitro utilizes a fork of Geth to implement Arbitrum's state transition function.
\n"},
-"ink":{"title":"Ink","text":"The equivalent of gas in the Stylus vm. Ink is introduced for finer granularity than gas offers since Stylus's operations are considerably cheaper than their EVM analogs.
\n"},
-"l2-block":{"title":"L2 Block","text":"Data structure that represents a group of L2 transactions (analogous to L1 blocks).
\n"},
-"l2-to-l1-message":{"title":"L2 to L1 Message","text":"A message initiated from within an Arbitrum chain to be eventually executed on Layer 1 (parent chain) (e.g., token or Ether withdrawals). On Rollup chains like Arbitrum One, the Challenge Period must pass before a child to parent chain message is executed.
\n"},
-"layer-1-l1":{"title":"Layer 1 (L1)","text":"The base protocol and underlying blockchain of the Ethereum network. Responsible for maintaining the integrity of the distributed ledger and executing smart contracts. Contains both Ethereum's execution layer and consensus layer.
\n"},
-"layer-2-l2":{"title":"Layer 2 (L2)","text":"Trustless scaling solutions built on top of Ethereum's Layer 1 (L1) base protocol, such as state channels, plasma chains, optimistic rollups, and ZK-rollups. Layer 2 solutions aim to increase scalability and reduce the cost of transactions on Ethereum's Layer 1 without introducing additional trust assumptions.
\n"},
-"layer-3-l3":{"title":"Layer 3 (L3)","text":"An Arbitrum chain whose core contract reside on an Arbitrum Layer 2 (L2) chain.
\n"},
-"native-fee-token":{"title":"Native Fee Token","text":"An ERC-20 token used as the native currency for gas fees on an Arbitrum chain (i.e., as opposed to using Ether). Arbitrum chains introduced the option for chains to use native fee tokens.
\n"},
-"offchain-labs":{"title":"Offchain Labs","text":"The initial builders Arbitrum; current contributors to the Arbitrum ecosystem and service providers to the Arbitrum DAO. Offchain also runs and maintains the Sequencers for Arbitrum One and Arbitrum Nova.
\n"},
-"one-step-proof":{"title":"One Step Proof","text":"Final step in a challenge; a single operation of the Arbitrum VM (WASM ) is executed on the underlying chain, and the validity of its state transition is verified.
\n"},
-"outbox":{"title":"Outbox","text":"A parent chain contract responsible for tracking Child to parent chain Messages, including withdrawals, which can be executed once they are confirmed. The outbox stores a Merkle Root of all outgoing messages.
\n"},
-"parent-chain":{"title":"Parent chain","text":"EVM compatible chain that acts as the settlement layer for one or more Arbitrum Chains (aka Child chain ). E.g., Ethereum is the parent chain of both Arbitrum One and Arbitrum Nova. Parent chain is synonymous with "underlying chain."
\n"},
-"portal":{"title":"Portal","text":"A web application maintained by Offchain Labs showcasing the Arbitrum ecosystem; visit it here.
\n"},
-"raas":{"title":"raas","text":"RaaS (Rollup as a Service) is a platform that provides the necessary infrastructure and tools to deploy and operate blockchain Rollups, eliminating the need for teams to build the underlying technical infrastructure themselves. It typically includes pre-built Rollup software, node hosting, data availability solutions, and monitoring tools, allowing developers to focus on their application logic rather than the complex technical implementation of Rollup technology.
\n"},
-"rblock":{"title":"RBlock","text":"Refer to Assertion
\n"},
-"reorg":{"title":"Reorg","text":"A situation in which transactions on a chain that were at some point considered accepted then get rejected. In the context of an Arbitrum chain, once transactions are posted in the chain's Sequencer Inbox, the only way the chain can experience a reorg is if its Underlying Chain itself reorgs. Of note, Fraud proofs do not cause reorgs.
\n"},
-"retryable-autoredeem":{"title":"Retryable Autoredeem","text":"The "automatic" (i.e., requiring no additional user action) execution of a Retryable Ticket on an Arbitrum chain.
\n"},
-"retryable-redeem":{"title":"Retryable Redeem","text":"The execution of a Retryable Ticket on a child chain; can be automatic (see Retryable Autoredeem) or manual via a user-initiated child chain transaction.
\n"},
-"retryable-ticket":{"title":"Retryable Ticket","text":"A parent to child cross chain message initiated by a parent chain transaction sent to an Arbitrum chain for execution (e.g., a token deposit).
\n"},
-"reverse-token-gateway":{"title":"Reverse Token Gateway","text":"A Token Gateway in which the Child chain gateway contract escrows and releases tokens, which the Parent chain Gateway contract mints and burns tokens. This in the inverse to how "typical" gateways work.
\n"},
-"sequencer":{"title":"Sequencer","text":"An entity (currently a single-party on Arbitrum One) given rights to reorder transactions in the Sequencer Inbox over a fixed window of time, who can thus give clients sub-blocktime Soft Confirmations. (Not to be confused with a Validator).
\n"},
-"sequencer-feed":{"title":"Sequencer Feed","text":"Offchain data feed published by the Sequencer which clients can subscribe to for Soft Confirmations of transactions before they are posted in batches.
\n"},
-"sequencer-inbox":{"title":"Sequencer Inbox","text":"Contract that holds a sequence of messages sent by clients to an Arbitrum Chain; a message can be put into the Sequencer Inbox directly by the Sequencer or indirectly through the Delayed Inbox.
\n"},
-"shared-sequencing":{"title":"Shared Sequencing","text":"A protocol design space in which multiple rollups use the same entity as their Sequencer; potential benefits include enhanced interoperability and credible neutrality.
\n"},
-"smart-contract":{"title":"Smart Contract","text":"A computer program whose operations are defined and executed within a blockchain consensus protocol.
\n"},
-"soft-confirmation":{"title":"Soft Confirmation","text":"A semi-trusted promise from the Sequencer to post a user's transaction in the near future; soft-confirmations happen prior to posting on the Parent chain, and thus can be given near-instantaneously (i.e., faster than the parent chain's block times)
\n"},
-"speed-limit":{"title":"Speed Limit","text":"Target computation limit for an Arbitrum chain. Arbitrum One and Arbitrum Nova currently target 7,000,000 gas / second. When computation exceeds this limit, fees rise, via EIP-1559.
\n"},
-"standard-arbtoken":{"title":"Standard Arb-Token","text":"An token contract on an Arbitrum chain deployed via the StandardERC20 gateway; offers basic ERC-20 functionality in addition to deposit / withdrawal affordances.
\n"},
-"standarderc20-gateway":{"title":"StandardERC20 gateway","text":"Token Gateway via which any underlying chain's ERC-20 token can permissionlessly bridge; the StandardERC20 gateway contracts deploy a Standard Arb-Token on the Child chain for each bridged token.
\n"},
-"state-transition-function":{"title":"State Transition Function","text":"The STF (State Transition Function) defines how new blocks are produced from input messages (i.e., transactions) in an Arbitrum chain.
\n"},
-"stylus":{"title":"Stylus","text":"Upgrade to the Arbitrum Nitro virtual machine that allows smart contract support for languages like Rust and C++ by taking advantage of Nitro's use of WASM. Currently on testnet (read more).
\n"},
-"timeboost":{"title":"Timeboost","text":"A transaction ordering policy in which entities can bid for the right to access an express lane on the Sequencer for faster transaction inclusion. See the research specification to learn more.
\n"},
-"token-gateway":{"title":"Token Gateway","text":"A pair of contracts in the token bridge — one on the Parent chain , one on the Child chain — that provide a particular mechanism for handling the transfer of tokens between layers. Token gateways currently active in the bridge include the StandardERC20 gateway , the Generic-Custom Gateway , and the WETH Gateway.
\n"},
-"transaction":{"title":"Transaction","text":"A user-initiated interaction with a Blockchain. Transactions are typically signed by users via wallets and are paid for via transaction fees.
\n"},
-"transaction-ordering-policy":{"title":"Transaction Ordering Policy","text":"The rules and logic employed by a chain to order incoming transactions into a block.
\n"},
-"trustless":{"title":"Trustless","text":"In the context of Ethereum, trustless refers to the ability of a system to operate without reliance on a central authority or intermediary. Instead, users place their trust in math and protocols.
\nThis is achieved through the use of cryptographic techniques and decentralized consensus mechanisms that let users verify the integrity of network transactions using open-source software. Trustless systems are considered to be more secure and resistant to fraud or tampering because they don't rely on a single point of failure that can be exploited by attackers.
\n"},
-"underlying-chain":{"title":"Underlying Chain","text":"Synonymous with Parent chain.
\n"},
-"validator":{"title":"Validator","text":"An Arbitrum Full Node that tracks the status of the chains' Assertions. A validator may be a Watchtower Validator, a Defensive Validator, or an Active Validator.
\n"},
-"wallet":{"title":"Wallet","text":"When referring to a wallet, we mean the user client software enabling user actions. Often, client software is a browser extension, mobile, or desktop app. Also refer to Externally Owned Accounts.
\n"},
-"wasm":{"title":"WASM","text":"Widely supported binary code format for executable programs. Used by Arbitrum Nitro for Fraud proofs , and more broadly used by Stylus to support performant smart contracts in a wide variety of languages.
\n"},
-"wasmer":{"title":"WASMer","text":"A popular WebAssembly runtime for executing WASM binaries. A fork of WASMer is used for executing Stylus programs. WASMer executes considerably faster than Geth executes EVM code, contributing to Stylus's lower fees.
\n"},
-"watchtower-validator":{"title":"Watchtower Validator","text":"A Validator that never bonds / never takes on chain action, who raises the alarm (by whatever offchain means it chooses) if it witnesses an invalid assertion.
\n"},
-"weth-gateway":{"title":"WETH Gateway","text":"Token Gateway for handing the bridging of wrapped Ether (WETH). WETH is unwrapped on the parent chain and rewrapped on the parent chain upon depositing (and vice-versa upon withdrawing), ensuring WETH on the child chain always remains collateralized.
\n"}
-}
\ No newline at end of file
+ "active-validator": {
+ "title": "Active Validator",
+ "text": "A bonded Validator that makes disputable assertions to advance the state of an Arbitrum chain or to challenge the validity of others' assertions. (Not to be confused with the Sequencer.)
\n"
+ },
+ "address-alias": {
+ "title": "Address Alias",
+ "text": "An address deterministically generated from a parent chain contract address used on child chain to safely identify the source of an parent to child chain message.
\n"
+ },
+ "dapp": {
+ "title": "Decentralized application",
+ "text": "A decentralized application typically consists of smart contracts as well as a user-interface for interacting with them.\nNote: In our documentation, "apps" and "decentralized applications" are used interchangeably.
\n"
+ },
+ "arb-token-bridge": {
+ "title": "Arb Token Bridge",
+ "text": "A series of contracts on an Arbitrum chain and its underlying chain that facilitate trustless movement of ERC-20 tokens between the two layers.
\n"
+ },
+ "arbified-token-list": {
+ "title": "Arbified Token List",
+ "text": "A token list that conforms to Uniswap's token list specification; Arbified lists are generated by inputting externally maintained list (i.e., coinmarketcap's list) and outputting a list that includes all of the instances of token contracts on the Arbitrum chain bridged via the canonical Arb Token Bridge from tokens on the input list. (See code here.)
\n"
+ },
+ "arbitrum": {
+ "title": "Arbitrum",
+ "text": "A suite of Ethereum child chain scaling technologies built with the Arbitrum Nitro tech stack that includes Arbitrum One (a live implementation of the Arbitrum Rollup Protocol) and Arbitrum Nova (a live implementation of the Arbitrum AnyTrust Protocol).
\n"
+ },
+ "arbitrum-anytrust-chain": {
+ "title": "Arbitrum AnyTrust Chain",
+ "text": "An Arbitrum chain that implements the Arbitrum AnyTrust Protocol.
\n"
+ },
+ "arbitrum-anytrust-protocol": {
+ "title": "Arbitrum AnyTrust Protocol",
+ "text": "An Arbitrum protocol that manages data availability with a permissioned set of parties known as the Data Availability Committee (DAC). This protocol reduces transaction fees by introducing an additional trust assumption for data availability in lieu of Ethereum's Trustless data availability mechanism. Arbitrum Nova is an example of an AnyTrust chain; Arbitrum One is an alternative chain that implements the purely trustless (and more L1-gas intensive) Arbitrum Rollup Protocol.
\n"
+ },
+ "arbitrum-bridge-ui": {
+ "title": "Arbitrum Bridge UI",
+ "text": "Web application built and maintained by Offchain Labs for user-interactions with the Arb Token Bridge; visit it here.
\n"
+ },
+ "arbitrum-chain": {
+ "title": "Arbitrum chain",
+ "text": "A blockchain that runs on the Arbitrum protocol. Arbitrum chains are EVM compatible, and use an underlying EVM chain (e.g., Ethereum) for settlement and for succinct fraud-proofs (as needed). Arbitrum chains come in two forms: Arbitrum Rollup Chains and Arbitrum AnyTrust Chains.
\n"
+ },
+ "arbitrum-chains": {
+ "title": "Arbitrum Chains",
+ "text": "Arbitrum chains (Orbit) refers to the ability for anyone to permissionlessly deploy Layer 3 (L3) chains on top of Arbitrum Layer 2 (L2) chains.
\n"
+ },
+ "arbitrum-classic": {
+ "title": "Arbitrum Classic",
+ "text": "Old Arbitrum stack that used custom virtual machine ("AVM"); no public Arbitrum chain uses the classic stack as of 8/31/2022 (they instead use Arbitrum Nitro.)
\n"
+ },
+ "arbitrum-full-node": {
+ "title": "Arbitrum Full Node",
+ "text": "A party who keeps track of the state of an Arbitrum chain and receives remote procedure calls (RPCs) from clients. Analogous to a non-staking parent Ethereum node.
\n"
+ },
+ "arbitrum-nitro": {
+ "title": "Arbitrum Nitro",
+ "text": "Current Arbitrum tech stack; runs a fork of Geth and uses WebAssembly as its underlying VM for fraud proofs.
\n"
+ },
+ "arbitrum-nova": {
+ "title": "Arbitrum Nova",
+ "text": "The first Arbitrum AnyTrust Chain running on Ethereum mainnet. Introduces cheaper transactions; great for gaming and social use-cases. Implements the Arbitrum AnyTrust Protocol, not the Arbitrum Rollup Protocol protocol. Governed by the Arbitrum DAO.
\n"
+ },
+ "arbitrum-one": {
+ "title": "Arbitrum One",
+ "text": "The first Arbitrum Rollup Chain running on Ethereum mainnet. Great for decentralized finance and other use-cases that demand strong security guarantees. Governed by the Arbitrum DAO.
\n"
+ },
+ "arbitrum-rollup-chain": {
+ "title": "Arbitrum Rollup Chain",
+ "text": "An Arbitrum chain that implements the Arbitrum Rollup Protocol.
\n"
+ },
+ "arbitrum-rollup-protocol": {
+ "title": "Arbitrum Rollup Protocol",
+ "text": "A trustless, permissionless Arbitrum protocol that uses its underlying base layer for data availability and inherits its security. This protocol is implemented by our Arbitrum One chain.
\n"
+ },
+ "arbos": {
+ "title": "ArbOS",
+ "text": "Arbitrum's "operating system" that trustlessly handles system-level operations; includes the ability to emulate the EVM.
\n"
+ },
+ "assertion": {
+ "title": "Assertion",
+ "text": "A bonded claim made by an Arbitrum Validator representing a claim about an Arbitrum chain's state. An Assertion may, e.g., propose a new assertion, or may be a step in a Challenge.
\n"
+ },
+ "auction-contract": {
+ "title": "Auction Contract",
+ "text": "A smart contract that handles the state, accounting of funds for bids, and various operations of the Timeboost auction. The contract is deployed on the target chain for which Timeboost is enabled.
\n"
+ },
+ "autonomous-auctioneer": {
+ "title": "Autonomous Auctioneer",
+ "text": "Offchain software that receives bids from Timeboost participants, processes and validates bids, and then posts the top valid bid (or top two valid bids in the case of a tie) to the Auction Contract to resolve the on going Timeboost auction. The autonomous auctioneer, for a given chain, is provisioned and deployed by an entity designated by the chain's owner.
\n"
+ },
+ "batch": {
+ "title": "Batch",
+ "text": "A group of Arbitrum transactions posted in a single transaction on the Underlying Chain into the Sequencer Inbox by the Sequencer.
\n"
+ },
+ "blockchain": {
+ "title": "Blockchain",
+ "text": "A distributed digital ledger that is used to record transactions and store data in a secure, transparent, and tamper-resistant way, notably in cryptocurrency protocols.
\n"
+ },
+ "bls-signature": {
+ "title": "BLS Signature",
+ "text": "A cryptographic scheme that allows multiple signatures to be aggregated and compacted into one efficiently verifiable, constant-sized signature. Used in the Arbitrum AnyTrust Protocol for the Data Availability Committee (DAC)'s signatures.
\n"
+ },
+ "bold": {
+ "title": "BoLD",
+ "text": "Short for "Bounded Liquidity Delay"; latest version of the Arbitrum Challenge protocol designed to eliminate delay attack vectors (see here for more).
\n"
+ },
+ "bonder": {
+ "title": "Bonder",
+ "text": "A Validator who deposits a bond (in Ether on Arbitrum One and Arbitrum Nova ) to vouch for a particular assertion in an Arbitrum Chain. A validator who bonds on a false assertion can expect to lose their bond. An honest bonder can recover their bond once the assertion they are bonded on has been confirmed.\nAlso known as: staker
\n"
+ },
+ "bridge": {
+ "title": "Bridge",
+ "text": "A set of smart contracts for sending Cross-chain messages between blockchains. Every Arbitrum chain includes a bridge to/from its Parent chain.
\n"
+ },
+ "chain-owner": {
+ "title": "Chain Owner",
+ "text": "An entity (i.e., a smart contract) with affordance to carry out critical upgrades to an Arbitrum chain's core protocol; this includes upgrading protocol contracts, setting core system parameters, and adding and removing other chain owners.
\n"
+ },
+ "chain-state": {
+ "title": "Chain state",
+ "text": "A particular point in the history of an Arbitrum chain. A chain's state is determined by applying Arbitrum state-transition function to sequence of transactions (i.e., the chain's history).
\n"
+ },
+ "challenge": {
+ "title": "Challenge",
+ "text": "When two bonders disagree about the correct verdict on an assertion, those bonders can be put in a challenge. The challenge is refereed by the contracts on the underlying chain. Eventually one bonder wins the challenge. The protocol guarantees that an honest party will always win a challenge; the loser forfeits their bond.
\n"
+ },
+ "challenge-period": {
+ "title": "Challenge Period",
+ "text": "Window of time (one week on Arbitrum One) over which an Assertion can be challenged, and after which the assertion can be confirmed.
\n"
+ },
+ "challenge-protocol": {
+ "title": "Challenge protocol",
+ "text": "The protocol by which assertions are submitted, disputed, and ultimately confirmed. The Challenge Protocol guarantees that only valid assertions will be confirmed provided that there is at least one honest active validator.
\n"
+ },
+ "child-chain": {
+ "title": "Child chain",
+ "text": "An Arbitrum Chain that settles to a Parent chain. For example, Arbitrum One and Arbitrum Nova are child chains of Ethereum.
\n"
+ },
+ "client": {
+ "title": "Client",
+ "text": "A program running on a user's machine, often in the user's browser, that interacts with contracts on an Arbitrum chain and provides a user interface.
\n"
+ },
+ "confirmation": {
+ "title": "Confirmation",
+ "text": "The decision by an Arbitrum chain to finalize an assertion as part of the chain's history. Once an assertion is confirmed its Child to parent chain Messages (e.g., withdrawals) can be executed.
\n"
+ },
+ "crosschain-message": {
+ "title": "Cross-chain message",
+ "text": "An action taken on some chain A which asynchronously initiates an additional action on chain B.
\n"
+ },
+ "custom-arbtoken": {
+ "title": "Custom Arb-Token",
+ "text": "Any child chain token contract registered to the Arb Token Bridge that isn't a standard arb-token (i.e., a token that uses any gateway other than the StandardERC20 gateway ).
\n"
+ },
+ "custom-gateway": {
+ "title": "Custom gateway",
+ "text": "Any Token Gateway that isn't the StandardERC20 gateway.
\n"
+ },
+ "data-availability-certificate": {
+ "title": "Data Availability Certificate",
+ "text": "Signed promise from a Data Availability Committee (DAC) attesting to the availability of a batch of data for an Arbitrum AnyTrust Chain.
\n"
+ },
+ "data-availability-committee-dac": {
+ "title": "Data Availability Committee (DAC)",
+ "text": "A permissioned set of parties responsible for enforcing data availability on a chain using the Arbitrum AnyTrust Protocol.
\nSee Introducing AnyTrust Chains: Cheaper, Faster L2 Chains with Minimal Trust Assumptions to learn more.
\n"
+ },
+ "defensive-validator": {
+ "title": "Defensive Validator",
+ "text": "A Validator that watches an Arbitrum chain and takes action (i.e., bonds and challenges) only when and if an invalid Assertion occurs.
\n"
+ },
+ "delayed-inbox": {
+ "title": "Delayed Inbox",
+ "text": "A contract that holds Parent chain initiated messages to be eventually included in the Sequencer Inbox. Inclusion of messages doesn't depend on the Sequencer.
\n"
+ },
+ "devtools-dashboard": {
+ "title": "Dev-Tools Dashboard",
+ "text": "Web application built and maintained by Offchain Labs for developers and users to debug Arbitrum transactions; i.e., executing or checking the status of Cross-chain messages; visit it here.
\n"
+ },
+ "dissection": {
+ "title": "Dissection",
+ "text": "A step in the Challenge protocol in which two challenging parties interactively narrow down their disagreement until they reach a One Step Proof.
\n"
+ },
+ "ethereum-wallet": {
+ "title": "Ethereum Wallet",
+ "text": "A software application used for transacting with the Ethereum Blockchain.
\n"
+ },
+ "evm": {
+ "title": "EVM+",
+ "text": "The paradigm introduced by Stylus in which Arbitrum's EVM compatibility is preserved while new features and improvements are introduced.
\n"
+ },
+ "express-lane": {
+ "title": "Express Lane",
+ "text": "A component of Timeboost, the express lane is a special endpoint on the Sequencer that immediately sequences incoming, valid transactions signed by the current express lane controller.
\n"
+ },
+ "express-lane-controller": {
+ "title": "Express Lane Controller",
+ "text": "An address, defined in the Auction Contract, that is granted the privilege to use the Express Lane. These privileges are granted after verifying that the incoming transactions were properly signed by the express lane controller, among other checks.
\n"
+ },
+ "externally-owned-accounts": {
+ "title": "Externally Owned Accounts",
+ "text": "An externally owned account (EOA) is the account (public/private key pairs) that has a physical address location. Commonly referred to as a wallet, however, we distinguish an EOA from the user client software wallet.
\n"
+ },
+ "fast-exit--liquidity-exit": {
+ "title": "Fast Exit / Liquidity Exit",
+ "text": "A means by which a user can bypass an Arbitrum chain's Challenge Period when withdrawing fungible assets (or more generally, executing some "fungible" child chain to parent chain operation); for trustless fast exits, a liquidity provider facilitates an atomic swap of the asset on a child chain directly to a parent chain.
\n"
+ },
+ "first-come-first-serve-fcfs": {
+ "title": "First Come First Serve (FCFS)",
+ "text": "A type of Transaction Ordering Policy used by the sequencer in Arbitrum chains whereby incoming transactions are sequenced into a block in the order that the transactions arrived.
\n"
+ },
+ "forceinclusion": {
+ "title": "Force-Inclusion",
+ "text": "Censorship resistant path for including a message into an Arbitrum chain via the Delayed Inbox on its Parent chain; bypasses any Sequencer involvement.
\n"
+ },
+ "fraud-proof": {
+ "title": "Fraud proof",
+ "text": "The means by which an Active Validator proves to its underlying chain that an invalid state transition has taken place.
\n"
+ },
+ "gas-price-floor": {
+ "title": "Gas Price Floor",
+ "text": "Protocol-enforced minimum gas price on an Arbitrum chain; currently 0.1 gwei on Arbitrum One and 0.01 gwei on Arbitrum Nova.
\n"
+ },
+ "gateway-router": {
+ "title": "Gateway Router",
+ "text": "Contracts in the Arb Token Bridge responsible for mapping tokens to their appropriate Token Gateway.
\n"
+ },
+ "genericcustom-gateway": {
+ "title": "Generic-Custom Gateway",
+ "text": "A particular Custom gateway via which a parent chain token contract can be registered to a token contract deployed to a child chain. A useful alternative to the StandardERC20 gateway for projects that wish to control the address of their child chain token contract, maintain the child chain token contract upgradability, and for various other use-cases.
\n"
+ },
+ "geth": {
+ "title": "Geth",
+ "text": "An execution-layer client that defines the Ethereum state transition function and handles network-layer logic like transaction memory pooling. Arbitrum Nitro utilizes a fork of Geth to implement Arbitrum's state transition function.
\n"
+ },
+ "ink": {
+ "title": "Ink",
+ "text": "The equivalent of gas in the Stylus vm. Ink is introduced for finer granularity than gas offers since Stylus's operations are considerably cheaper than their EVM analogs.
\n"
+ },
+ "l2-block": {
+ "title": "L2 Block",
+ "text": "Data structure that represents a group of L2 transactions (analogous to L1 blocks).
\n"
+ },
+ "l2-to-l1-message": {
+ "title": "L2 to L1 Message",
+ "text": "A message initiated from within an Arbitrum chain to be eventually executed on Layer 1 (parent chain) (e.g., token or Ether withdrawals). On Rollup chains like Arbitrum One, the Challenge Period must pass before a child to parent chain message is executed.
\n"
+ },
+ "layer-1-l1": {
+ "title": "Layer 1 (L1)",
+ "text": "The base protocol and underlying blockchain of the Ethereum network. Responsible for maintaining the integrity of the distributed ledger and executing smart contracts. Contains both Ethereum's execution layer and consensus layer.
\n"
+ },
+ "layer-2-l2": {
+ "title": "Layer 2 (L2)",
+ "text": "Trustless scaling solutions built on top of Ethereum's Layer 1 (L1) base protocol, such as state channels, plasma chains, optimistic rollups, and ZK-rollups. Layer 2 solutions aim to increase scalability and reduce the cost of transactions on Ethereum's Layer 1 without introducing additional trust assumptions.
\n"
+ },
+ "layer-3-l3": {
+ "title": "Layer 3 (L3)",
+ "text": "An Arbitrum chain whose core contract reside on an Arbitrum Layer 2 (L2) chain.
\n"
+ },
+ "native-fee-token": {
+ "title": "Native Fee Token",
+ "text": "An ERC-20 token used as the native currency for gas fees on an Arbitrum chain (i.e., as opposed to using Ether). Arbitrum chains introduced the option for chains to use native fee tokens.
\n"
+ },
+ "offchain-labs": {
+ "title": "Offchain Labs",
+ "text": "The initial builders Arbitrum; current contributors to the Arbitrum ecosystem and service providers to the Arbitrum DAO. Offchain also runs and maintains the Sequencers for Arbitrum One and Arbitrum Nova.
\n"
+ },
+ "one-step-proof": {
+ "title": "One Step Proof",
+ "text": "Final step in a challenge; a single operation of the Arbitrum VM (WASM ) is executed on the underlying chain, and the validity of its state transition is verified.
\n"
+ },
+ "outbox": {
+ "title": "Outbox",
+ "text": "A parent chain contract responsible for tracking Child to parent chain Messages, including withdrawals, which can be executed once they are confirmed. The outbox stores a Merkle Root of all outgoing messages.
\n"
+ },
+ "parent-chain": {
+ "title": "Parent chain",
+ "text": "EVM compatible chain that acts as the settlement layer for one or more Arbitrum Chains (aka Child chain ). E.g., Ethereum is the parent chain of both Arbitrum One and Arbitrum Nova. Parent chain is synonymous with "underlying chain."
\n"
+ },
+ "portal": {
+ "title": "Portal",
+ "text": "A web application maintained by Offchain Labs showcasing the Arbitrum ecosystem; visit it here.
\n"
+ },
+ "raas": {
+ "title": "raas",
+ "text": "RaaS (Rollup as a Service) is a platform that provides the necessary infrastructure and tools to deploy and operate blockchain Rollups, eliminating the need for teams to build the underlying technical infrastructure themselves. It typically includes pre-built Rollup software, node hosting, data availability solutions, and monitoring tools, allowing developers to focus on their application logic rather than the complex technical implementation of Rollup technology.
\n"
+ },
+ "rblock": {
+ "title": "RBlock",
+ "text": "Refer to Assertion
\n"
+ },
+ "reorg": {
+ "title": "Reorg",
+ "text": "A situation in which transactions on a chain that were at some point considered accepted then get rejected. In the context of an Arbitrum chain, once transactions are posted in the chain's Sequencer Inbox, the only way the chain can experience a reorg is if its Underlying Chain itself reorgs. Of note, Fraud proofs do not cause reorgs.
\n"
+ },
+ "retryable-autoredeem": {
+ "title": "Retryable Autoredeem",
+ "text": "The "automatic" (i.e., requiring no additional user action) execution of a Retryable Ticket on an Arbitrum chain.
\n"
+ },
+ "retryable-redeem": {
+ "title": "Retryable Redeem",
+ "text": "The execution of a Retryable Ticket on a child chain; can be automatic (see Retryable Autoredeem) or manual via a user-initiated child chain transaction.
\n"
+ },
+ "retryable-ticket": {
+ "title": "Retryable Ticket",
+ "text": "A parent to child cross chain message initiated by a parent chain transaction sent to an Arbitrum chain for execution (e.g., a token deposit).
\n"
+ },
+ "reverse-token-gateway": {
+ "title": "Reverse Token Gateway",
+ "text": "A Token Gateway in which the Child chain gateway contract escrows and releases tokens, which the Parent chain Gateway contract mints and burns tokens. This in the inverse to how "typical" gateways work.
\n"
+ },
+ "sequencer": {
+ "title": "Sequencer",
+ "text": "An entity (currently a single-party on Arbitrum One) given rights to reorder transactions in the Sequencer Inbox over a fixed window of time, who can thus give clients sub-blocktime Soft Confirmations. (Not to be confused with a Validator).
\n"
+ },
+ "sequencer-feed": {
+ "title": "Sequencer Feed",
+ "text": "Offchain data feed published by the Sequencer which clients can subscribe to for Soft Confirmations of transactions before they are posted in batches.
\n"
+ },
+ "sequencer-inbox": {
+ "title": "Sequencer Inbox",
+ "text": "Contract that holds a sequence of messages sent by clients to an Arbitrum Chain; a message can be put into the Sequencer Inbox directly by the Sequencer or indirectly through the Delayed Inbox.
\n"
+ },
+ "shared-sequencing": {
+ "title": "Shared Sequencing",
+ "text": "A protocol design space in which multiple rollups use the same entity as their Sequencer; potential benefits include enhanced interoperability and credible neutrality.
\n"
+ },
+ "smart-contract": {
+ "title": "Smart Contract",
+ "text": "A computer program whose operations are defined and executed within a blockchain consensus protocol.
\n"
+ },
+ "soft-confirmation": {
+ "title": "Soft Confirmation",
+ "text": "A semi-trusted promise from the Sequencer to post a user's transaction in the near future; soft-confirmations happen prior to posting on the Parent chain, and thus can be given near-instantaneously (i.e., faster than the parent chain's block times)
\n"
+ },
+ "speed-limit": {
+ "title": "Speed Limit",
+ "text": "Target computation limit for an Arbitrum chain. Arbitrum One and Arbitrum Nova currently target 7,000,000 gas / second. When computation exceeds this limit, fees rise, via EIP-1559.
\n"
+ },
+ "standard-arbtoken": {
+ "title": "Standard Arb-Token",
+ "text": "An token contract on an Arbitrum chain deployed via the StandardERC20 gateway; offers basic ERC-20 functionality in addition to deposit / withdrawal affordances.
\n"
+ },
+ "standarderc20-gateway": {
+ "title": "StandardERC20 gateway",
+ "text": "Token Gateway via which any underlying chain's ERC-20 token can permissionlessly bridge; the StandardERC20 gateway contracts deploy a Standard Arb-Token on the Child chain for each bridged token.
\n"
+ },
+ "state-transition-function": {
+ "title": "State Transition Function",
+ "text": "The STF (State Transition Function) defines how new blocks are produced from input messages (i.e., transactions) in an Arbitrum chain.
\n"
+ },
+ "stylus": {
+ "title": "Stylus",
+ "text": "Upgrade to the Arbitrum Nitro virtual machine that allows smart contract support for languages like Rust and C++ by taking advantage of Nitro's use of WASM. Currently on testnet (read more).
\n"
+ },
+ "timeboost": {
+ "title": "Timeboost",
+ "text": "A transaction ordering policy in which entities can bid for the right to access an express lane on the Sequencer for faster transaction inclusion. See the research specification to learn more.
\n"
+ },
+ "token-gateway": {
+ "title": "Token Gateway",
+ "text": "A pair of contracts in the token bridge — one on the Parent chain , one on the Child chain — that provide a particular mechanism for handling the transfer of tokens between layers. Token gateways currently active in the bridge include the StandardERC20 gateway , the Generic-Custom Gateway , and the WETH Gateway.
\n"
+ },
+ "transaction": {
+ "title": "Transaction",
+ "text": "A user-initiated interaction with a Blockchain. Transactions are typically signed by users via wallets and are paid for via transaction fees.
\n"
+ },
+ "transaction-ordering-policy": {
+ "title": "Transaction Ordering Policy",
+ "text": "The rules and logic employed by a chain to order incoming transactions into a block.
\n"
+ },
+ "trustless": {
+ "title": "Trustless",
+ "text": "In the context of Ethereum, trustless refers to the ability of a system to operate without reliance on a central authority or intermediary. Instead, users place their trust in math and protocols.
\nThis is achieved through the use of cryptographic techniques and decentralized consensus mechanisms that let users verify the integrity of network transactions using open-source software. Trustless systems are considered to be more secure and resistant to fraud or tampering because they don't rely on a single point of failure that can be exploited by attackers.
\n"
+ },
+ "underlying-chain": {
+ "title": "Underlying Chain",
+ "text": "Synonymous with Parent chain.
\n"
+ },
+ "validator": {
+ "title": "Validator",
+ "text": "An Arbitrum Full Node that tracks the status of the chains' Assertions. A validator may be a Watchtower Validator, a Defensive Validator, or an Active Validator.
\n"
+ },
+ "wallet": {
+ "title": "Wallet",
+ "text": "When referring to a wallet, we mean the user client software enabling user actions. Often, client software is a browser extension, mobile, or desktop app. Also refer to Externally Owned Accounts.
\n"
+ },
+ "wasm": {
+ "title": "WASM",
+ "text": "Widely supported binary code format for executable programs. Used by Arbitrum Nitro for Fraud proofs , and more broadly used by Stylus to support performant smart contracts in a wide variety of languages.
\n"
+ },
+ "wasmer": {
+ "title": "WASMer",
+ "text": "A popular WebAssembly runtime for executing WASM binaries. A fork of WASMer is used for executing Stylus programs. WASMer executes considerably faster than Geth executes EVM code, contributing to Stylus's lower fees.
\n"
+ },
+ "watchtower-validator": {
+ "title": "Watchtower Validator",
+ "text": "A Validator that never bonds / never takes on chain action, who raises the alarm (by whatever offchain means it chooses) if it witnesses an invalid assertion.
\n"
+ },
+ "weth-gateway": {
+ "title": "WETH Gateway",
+ "text": "Token Gateway for handing the bridging of wrapped Ether (WETH). WETH is unwrapped on the parent chain and rewrapped on the parent chain upon depositing (and vice-versa upon withdrawing), ensuring WETH on the child chain always remains collateralized.
\n"
+ }
+}
diff --git a/static/img/dapps-bridge_deposits.png b/static/img/apps-bridge_deposits.png
similarity index 100%
rename from static/img/dapps-bridge_deposits.png
rename to static/img/apps-bridge_deposits.png
diff --git a/static/img/dapps-bridge_withdrawals.png b/static/img/apps-bridge_withdrawals.png
similarity index 100%
rename from static/img/dapps-bridge_withdrawals.png
rename to static/img/apps-bridge_withdrawals.png
diff --git a/static/img/dapps-depositing-ether.svg b/static/img/apps-depositing-ether.svg
similarity index 100%
rename from static/img/dapps-depositing-ether.svg
rename to static/img/apps-depositing-ether.svg
diff --git a/static/img/dapps-gatewayUML.svg b/static/img/apps-gatewayUML.svg
similarity index 100%
rename from static/img/dapps-gatewayUML.svg
rename to static/img/apps-gatewayUML.svg
diff --git a/static/img/dapps-metamask-add-localhost-2025-01-13.png b/static/img/apps-metamask-add-localhost-2025-01-13.png
similarity index 100%
rename from static/img/dapps-metamask-add-localhost-2025-01-13.png
rename to static/img/apps-metamask-add-localhost-2025-01-13.png
diff --git a/static/img/dapps-pull-oracle.svg b/static/img/apps-pull-oracle.svg
similarity index 100%
rename from static/img/dapps-pull-oracle.svg
rename to static/img/apps-pull-oracle.svg
diff --git a/static/img/dapps-push-oracle.svg b/static/img/apps-push-oracle.svg
similarity index 100%
rename from static/img/dapps-push-oracle.svg
rename to static/img/apps-push-oracle.svg
diff --git a/static/img/dapps-quickstart-import-metamask.png b/static/img/apps-quickstart-import-metamask.png
similarity index 100%
rename from static/img/dapps-quickstart-import-metamask.png
rename to static/img/apps-quickstart-import-metamask.png
diff --git a/static/img/dapps-quickstart-vending-machine-architecture.png b/static/img/apps-quickstart-vending-machine-architecture.png
similarity index 100%
rename from static/img/dapps-quickstart-vending-machine-architecture.png
rename to static/img/apps-quickstart-vending-machine-architecture.png
diff --git a/static/img/dapps-remix-compile-contract-2025-01-07.gif b/static/img/apps-remix-compile-contract-2025-01-07.gif
similarity index 100%
rename from static/img/dapps-remix-compile-contract-2025-01-07.gif
rename to static/img/apps-remix-compile-contract-2025-01-07.gif
diff --git a/static/img/dapps-remix-connect-metamask-2025-01-13.gif b/static/img/apps-remix-connect-metamask-2025-01-13.gif
similarity index 100%
rename from static/img/dapps-remix-connect-metamask-2025-01-13.gif
rename to static/img/apps-remix-connect-metamask-2025-01-13.gif
diff --git a/static/img/dapps-remix-create-blank-project-2025-01-07.gif b/static/img/apps-remix-create-blank-project-2025-01-07.gif
similarity index 100%
rename from static/img/dapps-remix-create-blank-project-2025-01-07.gif
rename to static/img/apps-remix-create-blank-project-2025-01-07.gif
diff --git a/static/img/dapps-remix-deploy-to-local-chain-2025-01-14.gif b/static/img/apps-remix-deploy-to-local-chain-2025-01-14.gif
similarity index 100%
rename from static/img/dapps-remix-deploy-to-local-chain-2025-01-14.gif
rename to static/img/apps-remix-deploy-to-local-chain-2025-01-14.gif
diff --git a/static/img/dapps-remix-paste-vending-machine-contract-2025-01-07.gif b/static/img/apps-remix-paste-vending-machine-contract-2025-01-07.gif
similarity index 100%
rename from static/img/dapps-remix-paste-vending-machine-contract-2025-01-07.gif
rename to static/img/apps-remix-paste-vending-machine-contract-2025-01-07.gif
diff --git a/static/img/dapps-withdrawing-ether.svg b/static/img/apps-withdrawing-ether.svg
similarity index 100%
rename from static/img/dapps-withdrawing-ether.svg
rename to static/img/apps-withdrawing-ether.svg