update glossary

oftenbach · Mar 14, 2023 · 7485f88 · 7485f88
1 parent ed54079
commit 7485f88
Show file tree

Hide file tree

Showing 2 changed files with 20 additions and 0 deletions.
diff --git a/arbitrum-docs/partials/_glossary-partial.md b/arbitrum-docs/partials/_glossary-partial.md
@@ -51,6 +51,9 @@
 ### Batch {#batch}
 <p>A group of L2 transactions posted in a single L1 transaction into the <a href="/intro/glossary#fast-inbox">Fast Inbox</a>  by the <a href="/intro/glossary#sequencer">Sequencer</a>.</p>
 
+### Blockchain {#blockchain}
+<p>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. </p>
+
 ### **Chain state** {#chain-state}
 <p>A particular point in the history of an <a href="/intro/glossary#arbitrum-chain">Arbitrum chain</a>. A chain's state is determined by applying Arbitrum state-transition function to sequence of transactions (i.e., the chain's history).</p>
 
@@ -78,6 +81,9 @@
 ### Custom gateway {#custom-gateway}
 <p>Any <a href="/intro/glossary#token-gateway">Token Gateway</a> that isn't the <a href="/intro/glossary#standarderc20-gateway">StandardERC20 gateway</a>.</p>
 
+### dApp {#dapp}
+<p>Short for "decentralized application." A dApp typically consists of smart contracts as well as a user-interface for interacting with them.</p>
+
 ### **Data Availability Certificate** {#data-availability-certificate}
 <p>Signed promise from a <a href="/intro/glossary#data-availability-committee-dac"><strong>Data Availability Committee (DAC)</strong></a> attesting to the availability of a batch of data for an <a href="/intro/glossary#arbitrum-anytrust-chain"><strong>Arbitrum AnyTrust Chain</strong></a>.</p>
 
@@ -97,6 +103,9 @@
 ### Dissection {#dissection}
 <p>A step in the <a href="/intro/glossary#challenge-protocol">Challenge protocol</a>  in which two challenging parties interactively narrow down their disagreement until they reach a <a href="/intro/glossary#one-step-proof">One Step Proof</a>.</p>
 
+### Ethereum Wallet {#ethereum-wallet}
+<p>A software application used for transacting with the Ethereum <a href="/intro/glossary#blockchain">Blockchain</a>.</p>
+
 ### Fair Ordering Algorithm {#fair-ordering-algorithm}
 <p>BFT algorithm in which a committee comes to consensus on transaction ordering; current single-party <a href="/intro/glossary#sequencer">Sequencer</a> on Arbitrum may eventually be replaced by a fair-ordering committee.</p>
 
@@ -160,6 +169,9 @@
 ### Sequencer Feed {#sequencer-feed}
 <p>Off chain data feed published by the <a href="/intro/glossary#sequencer">Sequencer</a> which clients can subscribe to for <a href="/intro/glossary#soft-confirmation">Soft Confirmation</a>s of transactions before they are posted in <a href="/intro/glossary#batch">Batch</a>es.</p>
 
+### Smart Contract {#smart-contract}
+<p>A computer program whose operations are defined and executed within a blockchain consensus protocol.</p>
+
 ### Soft Confirmation {#soft-confirmation}
 <p>A semi-trusted promise from the <a href="/intro/glossary#sequencer">Sequencer</a>  to post a user's transaction in the near future; soft-confirmations happen prior to posting on L1, and thus can be given near-instantaneously (i.e., faster than L1 block times)</p>
 
@@ -181,6 +193,9 @@
 ### Token Gateway {#token-gateway}
 <p>A pair of contracts in the token bridge — one on L1, one on L2 — that provide a particular mechanism for handling the transfer of tokens between layers. Token gateways currently active in the bridge include the <a href="/intro/glossary#standarderc20-gateway">StandardERC20 gateway</a> , the <a href="/intro/glossary#genericcustom-gateway">Generic-Custom Gateway</a> , and the <a href="/intro/glossary#weth-gateway">WETH Gateway</a>.</p>
 
+### Transaction {#transaction}
+<p>A user-initiated interaction with a Blockchain. Transactions are typically signed by users via wallets and are paid for via transaction fees. </p>
+
 ### Trustless {#trustless}
 <p>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.<br />
 <br />

diff --git a/website/static/glossary.json b/website/static/glossary.json
@@ -16,6 +16,7 @@
 "arbos":{"title":"ArbOS","text":"<p>Layer 2 \"operating system\" that trustlessly handles system-level operations; includes the ability to emulate the EVM.</p>"},
 "assertion":{"title":"Assertion","text":"<p>A staked claim by an Arbitrum <a href=\"/intro/glossary#validator\">Validator</a>. An assertion may, e.g., propose a new <a href=\"/intro/glossary#rblock\">RBlock</a>, or may be a step in a <a href=\"/intro/glossary#challenge\">Challenge</a>.</p>"},
 "batch":{"title":"Batch","text":"<p>A group of L2 transactions posted in a single L1 transaction into the <a href=\"/intro/glossary#fast-inbox\">Fast Inbox</a>  by the <a href=\"/intro/glossary#sequencer\">Sequencer</a>.</p>"},
+"blockchain":{"title":"Blockchain","text":"<p>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. </p>"},
 "chain-state":{"title":"**Chain state**","text":"<p>A particular point in the history of an <a href=\"/intro/glossary#arbitrum-chain\">Arbitrum chain</a>. A chain's state is determined by applying Arbitrum state-transition function to sequence of transactions (i.e., the chain's history).</p>"},
 "challenge":{"title":"Challenge","text":"<p>When two <a href=\"/intro/glossary#staker\">Staker</a>s disagree about the correct verdict on an <a href=\"/intro/glossary#assertion\">Assertion</a>, those stakers can be put in a challenge. The challenge is refereed by the contracts on L1. Eventually one staker wins the challenge. The protocol guarantees that an honest  party will always win a challenge; the loser forfeits their stake. </p>"},
 "challenge-period":{"title":"Challenge Period","text":"<p>Window of time (1 week on Arbitrum One) over which an asserted <a href=\"/intro/glossary#rblock\">RBlock</a>  can be challenged, and after which the RBlock can be confirmed.</p>"},
@@ -25,11 +26,13 @@
 "crosschain-message":{"title":"Cross-chain message","text":"<p>An action taken on some chain A which asynchronously initiates an additional action on chain B. </p>"},
 "custom-arbtoken":{"title":"Custom Arb-Token","text":"<p>Any L2 token contract registered to the <a href=\"/intro/glossary#arb-token-bridge\">Arb Token Bridge</a> that isn't a standard arb-token (i.e., a token that uses any gateway other than the <a href=\"/intro/glossary#standarderc20-gateway\">StandardERC20 gateway</a> ).</p>"},
 "custom-gateway":{"title":"Custom gateway","text":"<p>Any <a href=\"/intro/glossary#token-gateway\">Token Gateway</a> that isn't the <a href=\"/intro/glossary#standarderc20-gateway\">StandardERC20 gateway</a>.</p>"},
+"dapp":{"title":"dApp","text":"<p>Short for \"decentralized application.\" A dApp typically consists of smart contracts as well as a user-interface for interacting with them.</p>"},
 "data-availability-certificate":{"title":"**Data Availability Certificate**","text":"<p>Signed promise from a <a href=\"/intro/glossary#data-availability-committee-dac\"><strong>Data Availability Committee (DAC)</strong></a> attesting to the availability of a batch of data for an <a href=\"/intro/glossary#arbitrum-anytrust-chain\"><strong>Arbitrum AnyTrust Chain</strong></a>.</p>"},
 "data-availability-committee-dac":{"title":"**Data Availability Committee (DAC)**","text":"<p>A permissioned set of parties responsible for enforcing data availability in an <a href=\"/intro/glossary#arbitrum-anytrust-protocol\"><strong>Arbitrum AnyTrust Protocol</strong></a> chain. See <em><a href=\"https://medium.com/offchainlabs/introducing-anytrust-chains-cheaper-faster-l2-chains-with-minimal-trust-assumptions-31def59eb8d7\">Introducing AnyTrust Chains: Cheaper, Faster L2 Chains with Minimal Trust Assumptions</a></em> to learn more.</p>\n\n<p></p>\n\n"},
 "defensive-validator":{"title":"Defensive Validator","text":"<p>A <a href=\"/intro/glossary#validator\">Validator</a> that watches an Arbitrum chain and takes action (i.e., stakes and challenges) only when and if an invalid <a href=\"/intro/glossary#assertion\">Assertion</a> occurs.</p>"},
 "delayed-inbox":{"title":"Delayed Inbox","text":"<p>A contract that holds L1 initiated messages to be eventually included in the <a href=\"/intro/glossary#fast-inbox\">Fast Inbox</a>. Inclusion of messages doesn't depend on the <a href=\"/intro/glossary#sequencer\">Sequencer</a>.</p>"},
 "dissection":{"title":"Dissection","text":"<p>A step in the <a href=\"/intro/glossary#challenge-protocol\">Challenge protocol</a>  in which two challenging parties interactively narrow down their disagreement until they reach a <a href=\"/intro/glossary#one-step-proof\">One Step Proof</a>.</p>"},
+"ethereum-wallet":{"title":"Ethereum Wallet","text":"<p>A software application used for transacting with the Ethereum <a href=\"/intro/glossary#blockchain\">Blockchain</a>.</p>"},
 "fair-ordering-algorithm":{"title":"Fair Ordering Algorithm","text":"<p>BFT algorithm in which a committee comes to consensus on transaction ordering; current single-party <a href=\"/intro/glossary#sequencer\">Sequencer</a> on Arbitrum may eventually be replaced by a fair-ordering committee.</p>"},
 "fast-exit--liquidity-exit":{"title":"**Fast Exit / Liquidity Exit**","text":"<p>A means by which a user can bypass an Arbitrum chain's <a href=\"/intro/glossary#challenge-period\">Challenge Period</a> when withdrawing fungible assets (or more generally, executing some \"fungible\" L2 to L1 operation); for trustless fast exits, a liquidity provider facilitates an atomic swap of the asset on L2 directly to L1.</p>"},
 "fast-inbox":{"title":"Fast Inbox","text":"<p>Contract that holds a sequence of messages sent by clients to an Arbitrum Chain; a message can be put into the fast Inbox directly by the <a href=\"/intro/glossary#sequencer\">Sequencer</a>  or indirectly through the <a href=\"/intro/glossary#delayed-inbox\">Delayed Inbox</a>.</p>"},
@@ -51,13 +54,15 @@
 "retryable-ticket":{"title":"**Retryable Ticket**","text":"<p>An L1 to L2 cross chain message initiated by an L1 transaction sent to an Arbitrum chain for execution (e.g., a token deposit).</p>"},
 "sequencer":{"title":"Sequencer","text":"<p>An entity (currently a single-party on Arbitrum One) given rights to reorder transactions in the <a href=\"/intro/glossary#fast-inbox\">Fast Inbox</a>  over a fixed window of time, who can thus give clients sub-blocktime <a href=\"/intro/glossary#soft-confirmation\">Soft Confirmation</a>s. (Not to be confused with a <a href=\"/intro/glossary#validator\">Validator</a>).</p>"},
 "sequencer-feed":{"title":"Sequencer Feed","text":"<p>Off chain data feed published by the <a href=\"/intro/glossary#sequencer\">Sequencer</a> which clients can subscribe to for <a href=\"/intro/glossary#soft-confirmation\">Soft Confirmation</a>s of transactions before they are posted in <a href=\"/intro/glossary#batch\">Batch</a>es.</p>"},
+"smart-contract":{"title":"Smart Contract","text":"<p>A computer program whose operations are defined and executed within a blockchain consensus protocol.</p>"},
 "soft-confirmation":{"title":"Soft Confirmation","text":"<p>A semi-trusted promise from the <a href=\"/intro/glossary#sequencer\">Sequencer</a>  to post a user's transaction in the near future; soft-confirmations happen prior to posting on L1, and thus can be given near-instantaneously (i.e., faster than L1 block times)</p>"},
 "speed-limit":{"title":"Speed Limit","text":"<p>Target L2 computation limit for an Arbitrum chain. <a href=\"/intro/glossary#arbitrum-one\">Arbitrum One</a> and <a href=\"/intro/glossary#arbitrum-nova\">Arbitrum Nova</a>  currently target 7,000,000 gas / second. When computation exceeds this limit, fees rise, ala <a href=\"https://notes.ethereum.org/@vbuterin/eip-1559-faq\">EIP-1559</a>.</p>"},
 "staker":{"title":"Staker","text":"<p>A <a href=\"/intro/glossary#validator\">Validator</a> who deposits a stake (in Ether on <a href=\"/intro/glossary#arbitrum-one\">Arbitrum One</a> and <a href=\"/intro/glossary#arbitrum-nova\">Arbitrum Nova</a> ) to vouch for a particular <a href=\"/intro/glossary#rblock\">RBlock</a>  in an Arbitrum Chain. A validator who stakes on a false RBlock can expect to lose their stake. An honest staker can recover their stake once the RBlock they are staked on has been confirmed.</p>"},
 "standard-arbtoken":{"title":"Standard Arb-Token","text":"<p>An L2 token contract deployed via the <a href=\"/intro/glossary#standarderc20-gateway\">StandardERC20 gateway</a>; offers basic ERC20 functionality in addition to deposit / withdrawal affordances.</p>"},
 "standarderc20-gateway":{"title":"StandardERC20 gateway","text":"<p><a href=\"/intro/glossary#token-gateway\">Token Gateway</a> via which any L1 ERC20 token can permissionlessly bridge; the StandrardERC20 gateway contracts deploy a <a href=\"/intro/glossary#standard-arbtoken\">Standard Arb-Token</a> on L2 for each bridged token.</p>"},
 "stylus":{"title":"Stylus","text":"<p>Upcoming upgrade to the the <a href=\"/intro/glossary#arbitrum-nitro\">Arbitrum Nitro</a> virtual machine that will allow smart contract support for languages like Rust and C++ by taking advantage of Nitro's use of WASM (<a href=\"https://offchain.medium.com/hello-stylus-6b18fecc3a22\">read more</a>).</p>"},
 "token-gateway":{"title":"Token Gateway","text":"<p>A pair of contracts in the token bridge — one on L1, one on L2 — that provide a particular mechanism for handling the transfer of tokens between layers. Token gateways currently active in the bridge include the <a href=\"/intro/glossary#standarderc20-gateway\">StandardERC20 gateway</a> , the <a href=\"/intro/glossary#genericcustom-gateway\">Generic-Custom Gateway</a> , and the <a href=\"/intro/glossary#weth-gateway\">WETH Gateway</a>.</p>"},
+"transaction":{"title":"Transaction","text":"<p>A user-initiated interaction with a Blockchain. Transactions are typically signed by users via wallets and are paid for via transaction fees. </p>"},
 "trustless":{"title":"Trustless","text":"<p>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.<br />\n<br />\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.</p>\n\n<p></p>\n\n"},
 "validator":{"title":"Validator","text":"<p>An <a href=\"/intro/glossary#arbitrum-full-node\"><strong>Arbitrum Full Node</strong></a> that tracks the status of the chains' <a href=\"/intro/glossary#assertion\">Assertion</a>s. A validator may be a <a href=\"/intro/glossary#watchtower-validator\">Watchtower Validator</a>, a <a href=\"/intro/glossary#defensive-validator\">Defensive Validator</a>, or an <a href=\"/intro/glossary#active-validator\">Active Validator</a>. </p>"},
 "watchtower-validator":{"title":"Watchtower Validator","text":"<p>A <a href=\"/intro/glossary#validator\">Validator</a>  that never stakes / never takes on chain action, who raises the alarm (by whatever off-chain means it chooses) if it witnesses an invalid assertion.</p>"},