From 887acf55c4ca52de683e4ccade1680895161b14c Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Thu, 19 Dec 2024 10:30:17 -0500 Subject: [PATCH 1/9] Capitalize DAL --- docs/architecture/governance/amendment-history.md | 2 +- docs/architecture/smart-rollups.md | 2 +- docs/tutorials.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/architecture/governance/amendment-history.md b/docs/architecture/governance/amendment-history.md index 3e09fd377..df14ed834 100644 --- a/docs/architecture/governance/amendment-history.md +++ b/docs/architecture/governance/amendment-history.md @@ -231,7 +231,7 @@ For more information, see the blog post from [Nomadic Labs](https://research-dev Paris's main changes are: * [10-second block time](https://research-development.nomadic-labs.com/10-second-blocktime.html): Lower latency and faster finality on layer 1 without compromising decentralization or security. -* [Data availability layer](https://research-development.nomadic-labs.com/paris-announcement.html#the-dal-activates-on-mainnet-boosting-smart-rollups-capacity): Boosting throughput and scalability of Smart Rollups. +* [Data Availability Layer](https://research-development.nomadic-labs.com/paris-announcement.html#the-dal-activates-on-mainnet-boosting-smart-rollups-capacity): Boosting throughput and scalability of Smart Rollups. It enables Tezos Layer 1 to attest the publication of data living outside Layer 1 blocks, increasing by orders of magnitude the bandwidth of data attested by the Layer 1. * [Adaptive issuance, staking, and adaptive slashing](https://research-development.nomadic-labs.com/adaptive-issuance-paris.html): A major overhaul of Tezos Proof-of-Stake, adapting the economics of tez to fit better with real-world usage, and to increase the chain security. The proposed mechanism ties the protocol’s regular issuance of tez to the ratio of staked tez over the total supply, in order to nudge the staked fund ratio towards a protocol-defined target. * [Further proof-of-stake refinements](https://research-development.nomadic-labs.com/paris-announcement.html#further-proof-of-stake-refinements): Simplified computation and faster updates of consensus rights. diff --git a/docs/architecture/smart-rollups.md b/docs/architecture/smart-rollups.md index 27f1d626b..a96f909eb 100644 --- a/docs/architecture/smart-rollups.md +++ b/docs/architecture/smart-rollups.md @@ -46,7 +46,7 @@ Smart Rollups are limited to information from these sources: - The Smart Rollup inbox, which contains messages from layer 1 to all rollups - The reveal data channel, which allows Smart Rollups to request information from outside sources -- The [Data availability layer](/architecture/data-availability-layer) +- The [Data Availability Layer](/architecture/data-availability-layer) These are the only sources of information that rollups can use. In particular, Smart Rollup nodes cannot communicate directly with each other; they do not have a peer-to-peer communication channel like layer 1 nodes. diff --git a/docs/tutorials.mdx b/docs/tutorials.mdx index c47eb1e80..94fc2d90d 100644 --- a/docs/tutorials.mdx +++ b/docs/tutorials.mdx @@ -137,7 +137,7 @@ These tutorials are intended for developers who are familiar with Tezos and want title="Implement a file archive with the DAL" emoji="🗃️" href="/tutorials/build-files-archive-with-dal" - description="Learn how to build a file archive with a Smart Rollup and the data availability layer" + description="Learn how to build a file archive with a Smart Rollup and the Data Availability Layer" link="Start tutorial" /> From 3171dbe71a4f29620dc97ad2541cf9ae5018ef26 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Tue, 21 Jan 2025 13:04:12 -0500 Subject: [PATCH 2/9] teztnets.com --- docs/developing/testnets.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developing/testnets.md b/docs/developing/testnets.md index 8b524ca5a..dc0033236 100644 --- a/docs/developing/testnets.md +++ b/docs/developing/testnets.md @@ -108,7 +108,7 @@ curl https://teztnets.com/teztnets.json | jq '.[] | select(.human_name == "Weekl You can use the response to set environment variables like the RPC endpoint, as in this code: ```bash -curl https://teztnets.xyz/teztnets.json | jq '.[] | select(.human_name == "Weeklynet")' > weeklynet.json +curl https://teztnets.com/teztnets.json | jq '.[] | select(.human_name == "Weeklynet")' > weeklynet.json export WEEKLYNET_ENDPOINT=$(jq -r .rpc_url weeklynet.json) export WEEKLYNET_COMMIT=$(jq -r .git_ref weeklynet.json) export DOCKER_IMAGE=$(jq -r .docker_build weeklynet.json) From 0e835ff39c2896420cf3023d8f12b5b6b1eb5f98 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Mon, 27 Jan 2025 14:27:24 -0500 Subject: [PATCH 3/9] wrong unity link --- docs/unity/managing-tokens.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/unity/managing-tokens.md b/docs/unity/managing-tokens.md index 4e99ec147..615fd24d5 100644 --- a/docs/unity/managing-tokens.md +++ b/docs/unity/managing-tokens.md @@ -31,7 +31,7 @@ FA2 tokens can be fungible tokens or non-fungible tokens, which makes the standa To create and work with FA2 tokens you must deploy an FA2-compatible smart contract. For examples of FA2 contracts, see [Sample smart contracts](/smart-contracts/samples). -You can also use the tutorial [Create a fungible token with the SmartPy FA2 library](/smart-contracts/samples) to walk through the process of creating, customizing, and deploying an FA2 contract. +You can also use the tutorial [Create a fungible token with the SmartPy FA2 library](/tutorials/smartpy-fa2-fungible) to walk through the process of creating, customizing, and deploying an FA2 contract. :::note From e1d45fc51e2ae15f276d9036c010e650810c78bd Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Mon, 27 Jan 2025 15:26:09 -0500 Subject: [PATCH 4/9] root-relative link --- docs/unity/connecting-accounts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/unity/connecting-accounts.md b/docs/unity/connecting-accounts.md index 2fbda2610..6261682eb 100644 --- a/docs/unity/connecting-accounts.md +++ b/docs/unity/connecting-accounts.md @@ -48,7 +48,7 @@ The SDK supports three types of wallets: ## Connecting to Beacon wallets Unity applications can connect to Beacon wallets by showing a QR code that the user scans with a wallet app or by opening that app directly through the Beacon protocol. -For an example of this method, see [Quickstart](./quickstart). +For an example of this method, see [Quickstart](/unity/quickstart). This method for connecting follows these general steps: From 3adc1f640185cdb27ed670da02cf0abc98c2bb59 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Tue, 28 Jan 2025 14:00:37 -0500 Subject: [PATCH 5/9] The the --- docs/tutorials/smart-rollup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorials/smart-rollup.md b/docs/tutorials/smart-rollup.md index 61a3c28a9..21b744de3 100644 --- a/docs/tutorials/smart-rollup.md +++ b/docs/tutorials/smart-rollup.md @@ -148,7 +148,7 @@ TODO Could we install some of the tools in the docker container instead of makin - WebAssembly Toolkit - The the [WebAssembly Toolkit (`wabt`)](https://github.com/WebAssembly/wabt) provides tooling for reducing (or _stripping_) the size of WebAssembly binaries (with the `wasm-strip` command) and conversion utilities between the textual and binary representations of WebAssembly (including the `wat2wasm` and `wasm2wat` commands). + The [WebAssembly Toolkit (`wabt`)](https://github.com/WebAssembly/wabt) provides tooling for reducing (or _stripping_) the size of WebAssembly binaries (with the `wasm-strip` command) and conversion utilities between the textual and binary representations of WebAssembly (including the `wat2wasm` and `wasm2wat` commands). Most distributions ship a `wabt` package, which you can install with the appropriate command for your operating system: From d33d7ab277f596330796b93aa2560eae44a9033c Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 31 Jan 2025 14:08:39 -0500 Subject: [PATCH 6/9] Stray comma --- docs/architecture/governance/amendment-history.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/governance/amendment-history.md b/docs/architecture/governance/amendment-history.md index df14ed834..f283b6de1 100644 --- a/docs/architecture/governance/amendment-history.md +++ b/docs/architecture/governance/amendment-history.md @@ -5,7 +5,7 @@ last_update: date: 6 June 2024 --- -As presented in [Governance](/architecture/governance), the Tezos blockchain is constantly evolving, through new amendments. +As presented in [Governance](/architecture/governance), the Tezos blockchain is constantly evolving through new amendments. These approved amendments form the history of the Tezos protocol: From 886680975ab649fb3b1d0d25d0de1cdb7e205aa0 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 31 Jan 2025 15:11:35 -0500 Subject: [PATCH 7/9] Simplify verb aspect --- docs/tutorials/smart-rollup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorials/smart-rollup.md b/docs/tutorials/smart-rollup.md index 21b744de3..d3e303fb3 100644 --- a/docs/tutorials/smart-rollup.md +++ b/docs/tutorials/smart-rollup.md @@ -140,7 +140,7 @@ TODO Could we install some of the tools in the docker container instead of makin - AR (macOS only) To compile to WebAssembly on macOS, you need to use the LLVM archiver. - If you've used Homebrew to install LLVM, you can configure it to use the archiver by running this command: + If you used Homebrew to install LLVM, you can configure it to use the archiver by running this command: ```bash export AR="$(brew --prefix llvm)/bin/llvm-ar" From 2b7180d3fc4f8c8a17a00aa8e57716ecd56bbb33 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 31 Jan 2025 15:12:15 -0500 Subject: [PATCH 8/9] Extra period --- docs/tutorials/smart-rollup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorials/smart-rollup.md b/docs/tutorials/smart-rollup.md index d3e303fb3..12b4e1845 100644 --- a/docs/tutorials/smart-rollup.md +++ b/docs/tutorials/smart-rollup.md @@ -178,7 +178,7 @@ TODO Could we install some of the tools in the docker container instead of makin To verify that `wabt` is installed, run the command `wasm-strip --version` and verify that the version is at least 1.0.31. If not, you can download this version directly and extract its files: https://github.com/WebAssembly/wabt/releases/tag/1.0.31. - Then, whenever you have to use `wasm-strip`, you can use `./bin/wasm-strip` instead. + Then, whenever you have to use `wasm-strip`, you can use `/bin/wasm-strip` instead. ## Tutorial application From f070f09543aa89d1717dd734c0854a9896668090 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 14 Feb 2025 13:05:23 -0500 Subject: [PATCH 9/9] big-maps tend to be more efficient as they get large --- docs/smart-contracts/data-types/complex-data-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/smart-contracts/data-types/complex-data-types.md b/docs/smart-contracts/data-types/complex-data-types.md index 1fa955b17..a79d5e465 100644 --- a/docs/smart-contracts/data-types/complex-data-types.md +++ b/docs/smart-contracts/data-types/complex-data-types.md @@ -211,7 +211,7 @@ Maps support all the features of big-maps plus these: Furthermore, unlike big-maps, maps can be passed as parameters and included in records or big-maps. You cannot pass big-maps as parameters or include them in records because doing so would require manipulating the serialized content of the big-map and defeat the purpose of big-maps. -In general, developers use big-maps unless there is a good reason to use maps because big-maps. +In general, developers use big-maps unless there is a good reason to use maps because big-maps tend to be more efficient as they get large, which future-proofs the contract. If you choose to use a map, take precautions and optimize your code. ### Example contract using big-maps