From 6582c8200b8f3f2df46325929f27df277b19e502 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 14 Feb 2025 09:38:18 -0500 Subject: [PATCH 1/8] Move links to octez.tezos.com/docs --- docs/architecture.md | 2 +- docs/architecture/bakers.md | 2 +- docs/architecture/data-availability-layer.md | 4 +- docs/architecture/governance.md | 2 +- .../governance/amendment-history.md | 66 +++++++++---------- docs/architecture/nodes.md | 4 +- docs/architecture/smart-rollups.md | 6 +- docs/architecture/tokens/FA1.2.md | 2 +- docs/developing.md | 2 +- docs/developing/octez-client.md | 4 +- docs/developing/octez-client/installing.md | 6 +- docs/developing/sandbox.md | 8 +-- docs/developing/testing.md | 4 +- docs/developing/testnets.md | 2 +- docs/overview/index.md | 4 +- docs/overview/resources.md | 2 +- docs/reference/style-guide.md | 2 +- docs/smart-contracts.mdx | 2 +- docs/smart-contracts/constants.md | 2 +- .../data-types/complex-data-types.md | 15 +++-- .../data-types/crypto-data-types.md | 4 +- .../data-types/primitive-data-types.md | 2 +- docs/smart-contracts/delegation.md | 2 +- docs/smart-contracts/entrypoints.md | 2 +- docs/smart-contracts/events.md | 2 +- docs/smart-contracts/languages/michelson.mdx | 2 +- docs/smart-contracts/logic/comparing.md | 2 +- docs/smart-contracts/logic/errors.md | 4 +- docs/smart-contracts/logic/loops.md | 2 +- docs/smart-contracts/logic/operations.md | 2 +- docs/smart-contracts/multisig.md | 2 +- docs/smart-contracts/sapling.md | 2 +- docs/smart-contracts/special-values.md | 2 +- docs/smart-contracts/views.md | 2 +- .../tutorials/build-files-archive-with-dal.md | 2 +- .../set-up-environment.md | 2 +- docs/tutorials/dapp/part-1.md | 2 +- docs/tutorials/join-dal-baker.md | 6 +- .../join-dal-baker/prepare-account.md | 2 +- docs/tutorials/join-dal-baker/run-baker.md | 10 +-- docs/tutorials/join-dal-baker/run-dal-node.md | 4 +- docs/tutorials/join-dal-baker/run-node.md | 6 +- .../tutorials/join-dal-baker/verify-rights.md | 2 +- docs/tutorials/smart-rollup/deploy.md | 2 +- docs/tutorials/smart-rollup/optimize.md | 2 +- docs/tutorials/smart-rollup/run.md | 4 +- .../smartpy-fa2-fungible/basic-fa2-token.md | 2 +- docs/unity/calling-contracts.md | 2 +- docs/using/staking.md | 2 +- docs/using/user-accounts.md | 2 +- 50 files changed, 112 insertions(+), 113 deletions(-) diff --git a/docs/architecture.md b/docs/architecture.md index 61c43dce4..fdc009db1 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -38,7 +38,7 @@ Nodes reach consensus on the next block before adding it to the chain. As shown in the diagram, the data inside a Tezos block includes the hash of the previous block in the chain and many operations, such as transactions that transfer tez or call smart contracts. Blocks also include operations that are necessary for the management of the chain, including nodes' attestations that blocks are valid, called _consensus operations_, and votes on changes to the protocol, called _voting operations_. -For more information on the operations that can be included in blocks, see [Blocks and operations](https://tezos.gitlab.io/alpha/blocks_ops.html) in the Octez documentation. +For more information on the operations that can be included in blocks, see [Blocks and operations](https://octez.tezos.com/docs/active/blocks_ops.html) in the Octez documentation. ### Tezos clients and servers diff --git a/docs/architecture/bakers.md b/docs/architecture/bakers.md index 08dafa843..ee38bb482 100644 --- a/docs/architecture/bakers.md +++ b/docs/architecture/bakers.md @@ -87,6 +87,6 @@ To start delegating and staking, use the app at https://stake.tezos.com. To start baking, use our [tutorial for bakers](/tutorials/join-dal-baker). -For more information about the different options to participate to the Tezos network (baking, staking, or delegating), see [Running Octez](https://tezos.gitlab.io/introduction/howtorun.html) in the Octez documentation. +For more information about the different options to participate to the Tezos network (baking, staking, or delegating), see [Running Octez](https://octez.tezos.com/docs/introduction/howtorun.html) in the Octez documentation. To learn more about baking and the related concepts, see [Node and Baking](https://opentezos.com/node-baking/baking/introduction/) on opentezos.com. diff --git a/docs/architecture/data-availability-layer.md b/docs/architecture/data-availability-layer.md index a037e33e4..d1be658ad 100644 --- a/docs/architecture/data-availability-layer.md +++ b/docs/architecture/data-availability-layer.md @@ -14,7 +14,7 @@ For a tutorial on how to use the DAL, see [Implement a file archive with the DAL The DAL depends on individual people running nodes, just like Tezos layer 1. -- If you are already a Tezos baker, you can add a DAL node to your setup with the instructions in [Running a DAL attester node](https://tezos.gitlab.io/shell/dal_run.html). +- If you are already a Tezos baker, you can add a DAL node to your setup with the instructions in [Running a DAL attester node](https://octez.tezos.com/docs/shell/dal_run.html). - For step-by-step instructions on running a DAL node, accessible to anyone, see [Join the DAL as a baker in 5 steps](/tutorials/join-dal-baker). ## How the DAL works @@ -156,4 +156,4 @@ if 0 < bytes_read { ## Reference -For more information about the DAL, see [DAL overview](https://tezos.gitlab.io/shell/dal_overview.html) in the Octez documentation. +For more information about the DAL, see [DAL overview](https://octez.tezos.com/docs/shell/dal_overview.html) in the Octez documentation. diff --git a/docs/architecture/governance.md b/docs/architecture/governance.md index 4a76d4962..0725d7396 100644 --- a/docs/architecture/governance.md +++ b/docs/architecture/governance.md @@ -79,5 +79,5 @@ At the end of the Adoption period, Mainnet automatically enables the new protoco ## References -- [The Amendment (and Voting) Process](https://tezos.gitlab.io/active/voting.html) in the Octez documentation +- [The Amendment (and Voting) Process](https://octez.tezos.com/docs/active/voting.html) in the Octez documentation - [Amending Tezos](https://medium.com/tezos/amending-tezos-b77949d97e1e) on Medium diff --git a/docs/architecture/governance/amendment-history.md b/docs/architecture/governance/amendment-history.md index 3e09fd377..3d254fda2 100644 --- a/docs/architecture/governance/amendment-history.md +++ b/docs/architecture/governance/amendment-history.md @@ -9,7 +9,7 @@ As presented in [Governance](/architecture/governance), the Tezos blockchain is These approved amendments form the history of the Tezos protocol: -## [Athens](https://tezos.gitlab.io/protocols/004_Pt24m4xi.html) (Pt24m4xiP) +## [Athens](https://octez.tezos.com/docs/protocols/004_Pt24m4xi.html) (Pt24m4xiP) Athens was autonomously [activated](https://tzstats.com/458753) in May 2019. @@ -17,7 +17,7 @@ Athens was autonomously [activated](https://tzstats.com/458753) in May 2019. Of the two proposals, _Athens A_ sought to increase the gas limit and reduce the required roll size for baking from 10,000 tez to 8,000 tez. _Athens B_ only sought to increase the gas limit. Athens A was voted and was autonomously [activated](https://twitter.com/tezos/status/1133907926907797504) into the protocol in May 2019. -For a full list of changes, be sure to read this corresponding [blog post](https://research-development.nomadic-labs.com/athens-proposals-injected.html) from Nomadic Labs and [reflections](https://medium.com/tqtezos/reflecting-on-athens-the-first-self-amendment-of-tezos-4791ab3b1de1) by Jacob Arluck, and the [reference documentation](https://tezos.gitlab.io/protocols/004_Pt24m4xi.html). +For a full list of changes, be sure to read this corresponding [blog post](https://research-development.nomadic-labs.com/athens-proposals-injected.html) from Nomadic Labs and [reflections](https://medium.com/tqtezos/reflecting-on-athens-the-first-self-amendment-of-tezos-4791ab3b1de1) by Jacob Arluck, and the [reference documentation](https://octez.tezos.com/docs/protocols/004_Pt24m4xi.html). ## [Brest A](https://www.tezosagora.org/proposal/PtdRxBHvc91c2ea2evV6wkoqnzW7TadTg9aqS9jAn2GbcPGtumD) (PtdRxBHv) @@ -25,7 +25,7 @@ For a full list of changes, be sure to read this corresponding [blog post](https This proposal would have fixed a security breach linked to the rehashing push during the _Athens_ protocol change. Moreover, it would have facilitated the amendment's invoice tracking. But the invoice for this proposal, 6,000 tez, was much higher than the usual cost. -## [Babylon](https://tezos.gitlab.io/protocols/005_babylon.html) (PsBABY5HQ) +## [Babylon](https://octez.tezos.com/docs/protocols/005_babylon.html) (PsBABY5HQ) Babylon was autonomously [activated](https://tzstats.com/655361) in October 2019. @@ -33,7 +33,7 @@ The *Babylon* proposal was made of two proposals made in July/August 2019: [Baby Notable changes included a new variant of the consensus algorithm (`Emmy+`). There were new Michelson features and accounts rehaul to aid smart contract developers. The accounts rehaul enabled a clearer distinction between "_tz_" and "_KT_" addresses. Furthermore, there was a refinement of the Quorum formula and the addition of the 5% threshold. -For a full list of changes, be sure to read the corresponding blog posts from [Nomadic Labs](https://research-development.nomadic-labs.com/babylon-proposal-injected.html), and [Cryptium Labs](https://medium.com/metastatedev/on-babylon2-0-1-58058d9d2106) (Metastate), and the [reference documentation](https://tezos.gitlab.io/protocols/005_babylon.html). +For a full list of changes, be sure to read the corresponding blog posts from [Nomadic Labs](https://research-development.nomadic-labs.com/babylon-proposal-injected.html), and [Cryptium Labs](https://medium.com/metastatedev/on-babylon2-0-1-58058d9d2106) (Metastate), and the [reference documentation](https://octez.tezos.com/docs/protocols/005_babylon.html). ## [Carthage](https://www.tezosagora.org/proposal/PtCarthavAMoXqbjBPVgDCRd5LgT7qqKWUPXnYii3xCaHRBMfHH) (PtCarthav) @@ -41,23 +41,23 @@ For a full list of changes, be sure to read the corresponding blog posts from [N The purpose of this proposal was to increase the gas limit per block and per operation by 30% to improve the accuracy of the existing formula used for calculating baking, endorsing rewards, and to fix various minor issues. -## [Carthage 2.0](https://tezos.gitlab.io/protocols/006_carthage.html) (PsCARTHAG) +## [Carthage 2.0](https://octez.tezos.com/docs/protocols/006_carthage.html) (PsCARTHAG) *Carthage 2.0* was autonomously [activated](https://tzstats.com/851969) in March 2020. Notable changes included increasing the gas limit per block and per operation by 30%, improving the accuracy of the formula used to calculate baking and endorsing rewards, as well as several minor improvements to Michelson. The main difference with _Carthage_ was the new and more secure formula to calculate rewards. -For a full list of changes be sure to read the corresponding [changelog](https://tezos.gitlab.io/protocols/006_carthage.html#changelog) and blog posts from [Nomadic Labs](https://research-development.nomadic-labs.com/carthage-changelog-and-testnet.html) and [Cryptium Labs](https://medium.com/metastatedev/updating-the-potential-carthage-proposal-and-resetting-the-carthagenet-test-network-f413a792571f) (Metastate). You may also check the [reference documentation](https://tezos.gitlab.io/protocols/006_carthage.html). +For a full list of changes be sure to read the corresponding [changelog](https://octez.tezos.com/docs/protocols/006_carthage.html#changelog) and blog posts from [Nomadic Labs](https://research-development.nomadic-labs.com/carthage-changelog-and-testnet.html) and [Cryptium Labs](https://medium.com/metastatedev/updating-the-potential-carthage-proposal-and-resetting-the-carthagenet-test-network-f413a792571f) (Metastate). You may also check the [reference documentation](https://octez.tezos.com/docs/protocols/006_carthage.html). -## [Delphi](https://tezos.gitlab.io/protocols/007_delphi.html) (PsDELPH1K) +## [Delphi](https://octez.tezos.com/docs/protocols/007_delphi.html) (PsDELPH1K) *Delphi* was autonomously [activated](https://tzstats.com/1212417) in November 2020. Notable changes included improving the performance of the Michelson interpreter, improving gas costs by adjusting the gas model, reducing storage costs by 4 times, and various minor fixes. -For a full list of changes, be sure to read the corresponding [changelog](https://research-development.nomadic-labs.com/delphi-changelog.html#007-delphi-changelog) and blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/delphi-official-release.html). You may also check the [reference documentation](https://tezos.gitlab.io/protocols/007_delphi.html). +For a full list of changes, be sure to read the corresponding [changelog](https://research-development.nomadic-labs.com/delphi-changelog.html#007-delphi-changelog) and blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/delphi-official-release.html). You may also check the [reference documentation](https://octez.tezos.com/docs/protocols/007_delphi.html). -## [Edo](https://tezos.gitlab.io/protocols/008_edo.html) (PtEdo2Zk) +## [Edo](https://octez.tezos.com/docs/protocols/008_edo.html) (PtEdo2Zk) *Edo* was autonomously [activated](https://tzstats.com/1343489) in February 2021. @@ -69,9 +69,9 @@ Edo added two major features to Tezos smart contracts: Among other features, Edo also updated the Tezos amendment process by lowering the period length to 5 cycles and by adding a 5th *Adoption Period*. -For more information check the [reference documentation](https://tezos.gitlab.io/protocols/008_edo.html). +For more information check the [reference documentation](https://octez.tezos.com/docs/protocols/008_edo.html). -## [Florence](https://tezos.gitlab.io/protocols/009_florence.html) (PsFLorena) +## [Florence](https://octez.tezos.com/docs/protocols/009_florence.html) (PsFLorena) *Florence* was autonomously [activated](https://tzstats.com/1466368) in May 2021. @@ -87,9 +87,9 @@ Florence's notable bug fixes and improvements are the: [*Bakings Accounts*](https://midl-dev.medium.com/tezos-in-favor-of-baking-accounts-3886effa370c) was also included in the feature set. However, ongoing testing uncovered some important and previously undocumented breaking changes in the proposal with *Baking Accounts*. Hence, the feature was postponed until a thorough audit of the functionality was completed or an alternative implementation was produced. The version of *Florence* without *Baking Accounts* was considered a [safer choice](https://research-development.nomadic-labs.com/baking-accounts-proposal-contains-unexpected-breaking-changes.html). -For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/florence-our-next-protocol-upgrade-proposal.html) and [Tarides](https://tarides.com/blog/2021-03-04-florence-and-beyond-the-future-of-tezos-storage), as well as the [reference documentation](https://tezos.gitlab.io/protocols/009_florence.html). +For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/florence-our-next-protocol-upgrade-proposal.html) and [Tarides](https://tarides.com/blog/2021-03-04-florence-and-beyond-the-future-of-tezos-storage), as well as the [reference documentation](https://octez.tezos.com/docs/protocols/009_florence.html). -## [Granada](https://tezos.gitlab.io/protocols/010_granada.html) (PtGRANAD) +## [Granada](https://octez.tezos.com/docs/protocols/010_granada.html) (PtGRANAD) *Granada* was autonomously [activated](https://tzstats.com/1589248) in August 2021. @@ -101,9 +101,9 @@ Granada's main changes are: * The reduction of gas consumption of smart contracts by a factor of three to six, through a number of performance improvements. -For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/granada-the-latest-tezos-upgrade-is-live.html) and the [reference documentation](https://tezos.gitlab.io/protocols/010_granada.html). +For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/granada-the-latest-tezos-upgrade-is-live.html) and the [reference documentation](https://octez.tezos.com/docs/protocols/010_granada.html). -## [Hangzhou](https://tezos.gitlab.io/protocols/011_hangzhou.html) (PtHangz2) +## [Hangzhou](https://octez.tezos.com/docs/protocols/011_hangzhou.html) (PtHangz2) *Hanghzou* was autonomously [activated](https://tzstats.com/1916929) in December 2021. @@ -119,9 +119,9 @@ Hangzhou's main changes are: * Context flattening, an optimized rewrite of the protocol's database internals. -For more information, see the blog post from [Marigold](https://www.marigold.dev/post/hangzhou-the-latest-tezos-upgrade-is-live) and the [reference documentation](https://tezos.gitlab.io/protocols/011_hangzhou.html). +For more information, see the blog post from [Marigold](https://www.marigold.dev/post/hangzhou-the-latest-tezos-upgrade-is-live) and the [reference documentation](https://octez.tezos.com/docs/protocols/011_hangzhou.html). -## [Ithaca](https://tezos.gitlab.io/protocols/012_ithaca.html) (Psithaca2) +## [Ithaca](https://octez.tezos.com/docs/protocols/012_ithaca.html) (Psithaca2) *Ithaca* was autonomously [activated](https://tzstats.com/2244609) in April 2022. @@ -138,9 +138,9 @@ Along with numerous minor improvements, Ithaca contained two major updates to th * Adding approximately ten months to the liquidity baking sunset level. -For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/announcing-tezos-9th-protocol-upgrade-proposal-ithaca.html) and the [reference documentation](https://tezos.gitlab.io/protocols/012_ithaca.html). +For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/announcing-tezos-9th-protocol-upgrade-proposal-ithaca.html) and the [reference documentation](https://octez.tezos.com/docs/protocols/012_ithaca.html). -## [Jakarta](https://tezos.gitlab.io/protocols/013_jakarta.html) (PtJakart2) +## [Jakarta](https://octez.tezos.com/docs/protocols/013_jakarta.html) (PtJakart2) *Jakarta* was autonomously [activated](https://tzstats.com/2490369) in June 2022. @@ -158,9 +158,9 @@ Jakarta's main changes are: * The voting power of delegates is now defined directly by their stake expressed in mutez, and no more in terms of rolls. The minimal stake required to be assigned voting rights is kept at 6000 tez. -For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/announcing-jakarta-two.html) and the [reference documentation](https://tezos.gitlab.io/protocols/013_jakarta.html). +For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/announcing-jakarta-two.html) and the [reference documentation](https://octez.tezos.com/docs/protocols/013_jakarta.html). -## [Kathmandu](https://tezos.gitlab.io/protocols/014_kathmandu.html) (PtKathman) +## [Kathmandu](https://octez.tezos.com/docs/protocols/014_kathmandu.html) (PtKathman) *Kathmandu* was autonomously [activated](https://tzstats.com/2736129) in September 2022. @@ -174,9 +174,9 @@ Kathmandu's main changes are: * A new operation for increasing paid storage of a smart contract allowing DApps developers to pay the storage fees on behalf of their users. -For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/announcing-tezos-11th-protocol-upgrade-proposal-kathmandu.html) and the [reference documentation](https://tezos.gitlab.io/protocols/014_kathmandu.html). +For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/announcing-tezos-11th-protocol-upgrade-proposal-kathmandu.html) and the [reference documentation](https://octez.tezos.com/docs/protocols/014_kathmandu.html). -## [Lima](https://tezos.gitlab.io/protocols/015_lima.html) (PtLimaPt) +## [Lima](https://octez.tezos.com/docs/protocols/015_lima.html) (PtLimaPt) *Lima* was autonomously [activated](https://tzstats.com/2981889) in December 2022. @@ -184,9 +184,9 @@ In addition to improvements to enable higher Layer 1 throughput, the main featur * Consensus keys: bakers can now create a dedicated key for signing blocks and consensus operations without changing the baker’s public address. -For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/announcing-tezos-12th-protocol-upgrade-proposal-lima.html) and the [reference documentation](https://tezos.gitlab.io/protocols/015_lima.html). +For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/announcing-tezos-12th-protocol-upgrade-proposal-lima.html) and the [reference documentation](https://octez.tezos.com/docs/protocols/015_lima.html). -## [Mumbai](https://tezos.gitlab.io/protocols/016_mumbai.html) (PtMumbai) +## [Mumbai](https://octez.tezos.com/docs/protocols/016_mumbai.html) (PtMumbai) *Mumbai* was autonomously [activated](https://tzstats.com/3268609) in March 2023. @@ -196,9 +196,9 @@ Mumbai's main changes are: * Minimal block time reduction from 30s to 15s. * Ticket transfers between user accounts. -For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/mumbai-announcement.html) and the [reference documentation](https://tezos.gitlab.io/protocols/016_mumbai.html). +For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/mumbai-announcement.html) and the [reference documentation](https://octez.tezos.com/docs/protocols/016_mumbai.html). -## [Nairobi](https://tezos.gitlab.io/protocols/017_nairobi.html) (PtNairob) +## [Nairobi](https://octez.tezos.com/docs/protocols/017_nairobi.html) (PtNairob) *Nairobi* was autonomously [activated](https://tzstats.com/3760129) in June 2023. @@ -208,9 +208,9 @@ Nairobi's main changes are: * Renaming endorsements to attestations to specify the behavior of these consensus operations. * Smart Rollups can now be aware of protocol updates happening on the L1. -For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/nairobi-announcement.html) and the [reference documentation](https://tezos.gitlab.io/protocols/017_nairobi.html). +For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/nairobi-announcement.html) and the [reference documentation](https://octez.tezos.com/docs/protocols/017_nairobi.html). -## [Oxford](https://tezos.gitlab.io/protocols/018_oxford.html) (Proxford) +## [Oxford](https://octez.tezos.com/docs/protocols/018_oxford.html) (Proxford) *Oxford* was autonomously [activated](https://tzkt.io/5070849) on 9 February 2024. @@ -222,9 +222,9 @@ The latter aims to smoothen the transition towards a new staked funds management Additionally, Oxford [simplifies the deployment of rollups](https://research-development.nomadic-labs.com/oxford2-announcement.html#introducing-private-rollups-and-other-improvements-to-smart-rollups) both on protocol and periodic test networks, as well as on ad-hoc dedicated ones. * [Timelocks are re-enabled](https://research-development.nomadic-labs.com/oxford2-announcement.html#timelocks-are-re-enabled): a new design and implementation of Timelocks addresses security concerns that led to their temporary deactivation in a previous protocol upgrade. -For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/oxford-announcement.html) and the [reference documentation](https://tezos.gitlab.io/protocols/018_oxford.html). +For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/oxford-announcement.html) and the [reference documentation](https://octez.tezos.com/docs/protocols/018_oxford.html). -## [Paris](https://tezos.gitlab.io/protocols/019_paris.html) (PtParisB) +## [Paris](https://octez.tezos.com/docs/protocols/019_paris.html) (PtParisB) *Paris* was autonomously [activated](https://tzkt.io/5726209) on 5 June 2024. @@ -236,9 +236,9 @@ It enables Tezos Layer 1 to attest the publication of data living outside Layer * [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. -For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/paris-announcement.html) and the [reference documentation](https://tezos.gitlab.io/protocols/019_paris.html). +For more information, see the blog post from [Nomadic Labs](https://research-development.nomadic-labs.com/paris-announcement.html) and the [reference documentation](https://octez.tezos.com/docs/protocols/019_paris.html). -## [Quebec](https://tezos.gitlab.io/protocols/021_quebec.html) (PsQuebec) +## [Quebec](https://octez.tezos.com/docs/protocols/021_quebec.html) (PsQuebec) *Quebec* was autonomously activated on 20 January 2025. diff --git a/docs/architecture/nodes.md b/docs/architecture/nodes.md index f079555e9..de6f3be21 100644 --- a/docs/architecture/nodes.md +++ b/docs/architecture/nodes.md @@ -26,7 +26,7 @@ In order to meet these requirements, the software that nodes run is structured a Nodes cooperate with clients and with each other through an [RPC interface](#the-rpc-interface). -The Octez suite, which is an implementation of the Tezos node and other executables, instantiates these principles in the [Octez software architecture](https://tezos.gitlab.io/shell/the_big_picture.html). +The Octez suite, which is an implementation of the Tezos node and other executables, instantiates these principles in the [Octez software architecture](https://octez.tezos.com/docs/shell/the_big_picture.html). For instructions on running a node, see the tutorial [Run a Tezos node in 5 steps](/tutorials/join-dal-baker). @@ -79,7 +79,7 @@ Tezos nodes act as servers and accept HTTP requests from clients and other nodes Tezos RPC uses JSON to send and receive data, but it does not adhere to the JSON-RPC specification. -All the RPCs served by the Tezos node are described as an OpenAPI specification at [Octez Node RPCs](https://tezos.gitlab.io/api/openapi.html#octez-node) in the Octez documentation. +All the RPCs served by the Tezos node are described as an OpenAPI specification at [Octez Node RPCs](https://octez.tezos.com/docs/api/openapi.html#octez-node) in the Octez documentation. ### Public and private RPC nodes diff --git a/docs/architecture/smart-rollups.md b/docs/architecture/smart-rollups.md index 27f1d626b..8de4daab1 100644 --- a/docs/architecture/smart-rollups.md +++ b/docs/architecture/smart-rollups.md @@ -20,7 +20,7 @@ In this way, multiple nodes can run the same rollup and each node can verify the For a tutorial on Smart Rollups, see [Deploy a Smart Rollup](/tutorials/smart-rollup). -For reference on Smart Rollups, see [Smart Optimistic Rollups](https://tezos.gitlab.io/active/smart_rollups.html) in the Octez documentation. +For reference on Smart Rollups, see [Smart Optimistic Rollups](https://octez.tezos.com/docs/active/smart_rollups.html) in the Octez documentation. This diagram shows a high-level view of how Smart Rollups interact with layer 1: @@ -212,7 +212,7 @@ When a commitment includes layer 1 transactions, these transactions go into the After the commitment is cemented, clients can trigger transactions in the outbox with the Octez client `execute outbox message` command. When they trigger a transaction, it runs like any other call to a smart contract. -For more information, see [Triggering the execution of an outbox message](https://tezos.gitlab.io/shell/smart_rollup_node.html?highlight=triggering) in the Octez documentation. +For more information, see [Triggering the execution of an outbox message](https://octez.tezos.com/docs/shell/smart_rollup_node.html#triggering-the-execution-of-an-outbox-message) in the Octez documentation. ### Bailout process @@ -222,7 +222,7 @@ Nodes that post commitments cannot stop immediately without risking their bonds For this reason, nodes can switch to bailout mode to prepare to shut down without risking their bonds. In bailout mode, nodes defend their existing commitments without posting new commitments. When their final commitment is cemented, they can shut down safely. -For more information about node modes, see [Smart rollup node](https://tezos.gitlab.io/shell/smart_rollup_node.html) in the Octez documentation. +For more information about node modes, see [Smart rollup node](https://octez.tezos.com/docs/shell/smart_rollup_node.html) in the Octez documentation. ## Examples diff --git a/docs/architecture/tokens/FA1.2.md b/docs/architecture/tokens/FA1.2.md index 01e683977..4dd9885fd 100644 --- a/docs/architecture/tokens/FA1.2.md +++ b/docs/architecture/tokens/FA1.2.md @@ -21,7 +21,7 @@ You can verify that a contract follows the FA1.2 standard by running the followi octez-client check contract $CONTRACT_ADDRESS implements fa1.2 ``` -The Octez client also supports other interactions with FA1.2 contracts, such as transferring tokens or checking balances, as described at [FA1.2 support](https://tezos.gitlab.io/user/fa12.html) in the Octez documentation. +The Octez client also supports other interactions with FA1.2 contracts, such as transferring tokens or checking balances, as described at [FA1.2 support](https://octez.tezos.com/docs/user/fa12.html) in the Octez documentation. ## Allowances diff --git a/docs/developing.md b/docs/developing.md index 774d5d246..639dc6955 100644 --- a/docs/developing.md +++ b/docs/developing.md @@ -59,7 +59,7 @@ See https://taqueria.io/. To test smart contracts and dApps, you can use these test environments: - Test networks behave like Tezos Mainnet but have differences that make it easier to test on them, such as faucets that provide free tokens and reduced block times for faster testing. -- Sandbox environments like [Flextesa](https://tezos.gitlab.io/flextesa/) run Tezos nodes locally on your computer in a sandbox mode. +- Sandbox environments like Flextesa and Tezbox run Tezos nodes locally on your computer in a sandbox mode; see [Using a local sandbox](/developing/sandbox). - You can also set up your own private test network. For more information about test environments, see [Testing on testnets](/developing/testnets) and [Using a local sandbox](/developing/sandbox). diff --git a/docs/developing/octez-client.md b/docs/developing/octez-client.md index 87227f114..fe83fb5ca 100644 --- a/docs/developing/octez-client.md +++ b/docs/developing/octez-client.md @@ -15,5 +15,5 @@ Developers use the Octez client for many tasks, including: Other parts of Octez allow you to host, manage, and monitor nodes, bake blocks, and host RPC nodes. This documentation is an overview of the Octez client for Tezos smart contract and dApp developers. -For more detailed information, see the [Octez documentation](https://tezos.gitlab.io/) and opentezos.com. -For system requirements, see the documentation for the latest release of the Octez suite here: https://tezos.gitlab.io/releases/latest.html. +For more detailed information, see the [Octez documentation](https://octez.tezos.com/docs/) and opentezos.com. +For system requirements, see the documentation for the latest release of the Octez suite here: https://octez.tezos.com/docs/releases/latest.html. diff --git a/docs/developing/octez-client/installing.md b/docs/developing/octez-client/installing.md index 9516d5259..f5a751baa 100644 --- a/docs/developing/octez-client/installing.md +++ b/docs/developing/octez-client/installing.md @@ -38,7 +38,7 @@ Then, initialize it to use the RPC node of your choice: dnf install -y tezos-client ``` - For more local installation options, see [How to get Tezos](https://tezos.gitlab.io/introduction/howtoget.html) in the Octez documentation. + For more local installation options, see [Installing Octez](https://octez.tezos.com/docs/introduction/howtoget.html) in the Octez documentation. 1. Verify that the Octez client is installed by running this command: @@ -47,7 +47,7 @@ Then, initialize it to use the RPC node of your choice: ``` If you see a message with the version of Octez that you have installed, the Octez client is installed correctly. - For help on Octez, run `octez-client --help` or see the [Octez documentation](http://tezos.gitlab.io/index.html). + For help on Octez, run `octez-client --help` or see the [Octez documentation](http://octez.tezos.com/docs/index.html). 1. Initialize the client's configuration file by running this command: @@ -98,4 +98,4 @@ octez-client --version Then set the RPC node for the client as described above. -For more information about using the Docker image, see [Using Docker Images And Docker-Compose](https://tezos.gitlab.io/introduction/howtoget.html#using-docker-images-and-docker-compose) in the Octez documentation. +For more information about using the Docker image, see [Using Docker images](https://octez.tezos.com/docs/introduction/howtoget.html#using-docker-images) in the Octez documentation. diff --git a/docs/developing/sandbox.md b/docs/developing/sandbox.md index e00aa12ab..39bf9e10c 100644 --- a/docs/developing/sandbox.md +++ b/docs/developing/sandbox.md @@ -22,8 +22,8 @@ Here are some options for running local Tezos sandboxes: The Octez client sandboxed and mockup modes run a local version of the Tezos network. -- [Sandboxed mode](https://tezos.gitlab.io/user/sandbox.html) runs a local network with one or more nodes. -- [Mockup mode](https://tezos.gitlab.io/user/mockup.html) runs a light version of the network without nodes. +- [Sandboxed mode](https://octez.tezos.com/docs/user/sandbox.html) runs a local network with one or more nodes. +- [Mockup mode](https://octez.tezos.com/docs/user/mockup.html) runs a light version of the network without nodes. ## Tezbox @@ -51,7 +51,7 @@ Tezbox provides sample accounts in the `/tezbox/context/accounts.json` file. ## Flextesa -The [Flextesa](https://tezos.gitlab.io/flextesa/) is also a simulated Tezos environment that runs in a container. +[Flextesa](https://tezos.gitlab.io/flextesa/) is also a simulated Tezos environment that runs in a container. The Flextesa image has different scripts that start different versions of the Tezos protocol. For example, to start a Flextesa sandbox with the Oxford protocol, run this command: @@ -82,4 +82,4 @@ Now you can use the Octez client to deploy contracts and send transactions to th Flextesa allows you to control baking manually, so blocks are only backed when you trigger them. -For more information, see the [Flextesa documentation](https://tezos.gitlab.io/flextesa/). +For more information, see the [Flextesa documentation](https://octez.tezos.com/docs/flextesa/). diff --git a/docs/developing/testing.md b/docs/developing/testing.md index ac6cadd07..a32f94db4 100644 --- a/docs/developing/testing.md +++ b/docs/developing/testing.md @@ -11,7 +11,7 @@ Tezos smart contracts are immutable after deployment, so you must rigorously tes - The Michelson interpreter is an OCaml function that can be used by tools to simulate a call to any entry point of any smart contract, given an initial value of the storage and parameters. Some programming languages like LIGO or SmartPy use this as part of their testing frameworks. -- The mockup mode of `octez-client` can be used to test contract calls and other features such as some RPC calls, all without running an actual node, saving the time of going through the consensus mechanism and waiting to get blocks created and validated. Tools like Completium, built by the team behind the Archetype language, use this for their testing framework. Find out more in the [documentation of the mockup mode](https://tezos.gitlab.io/user/mockup.html). +- The mockup mode of `octez-client` can be used to test contract calls and other features such as some RPC calls, all without running an actual node, saving the time of going through the consensus mechanism and waiting to get blocks created and validated. Tools like Completium, built by the team behind the Archetype language, use this for their testing framework. Find out more in the [documentation of the mockup mode](https://octez.tezos.com/docs/user/mockup.html). For example, when you compile the contract in the tutorial [Create a smart contract](/tutorials/smart-contract) to Michelson, its first line defines the parameter type that the contract accepts: @@ -101,7 +101,7 @@ For more information about avoiding flaws in contracts, see [Avoiding flaws](htt ## Implementation details -- Michelson: [Mockup mode](https://tezos.gitlab.io/user/mockup.html) +- Michelson: [Mockup mode](https://octez.tezos.com/docs/user/mockup.html) - Archetype: [Completium test scenario](https://completium.com/docs/contract/test-scenario) - SmartPy: [Test scenarios](https://smartpy.io/manual/scenarios/test_scenarios) - LIGO: [Testing LIGO](https://ligolang.org/docs/next/testing/) diff --git a/docs/developing/testnets.md b/docs/developing/testnets.md index 8b524ca5a..5fd10b5e9 100644 --- a/docs/developing/testnets.md +++ b/docs/developing/testnets.md @@ -139,5 +139,5 @@ See the [Private blockchain](https://opentezos.com/private) section on OpenTezos ## More information -- [Test networks by Nomadic Labs](https://tezos.gitlab.io/introduction/test_networks.html) +- [Test networks](https://octez.tezos.com/docs/user/multinetwork.html#test-networks) - Medium post: [Introducing Ghostnet](https://medium.com/the-aleph/introducing-ghostnet-1bf39976e61f) diff --git a/docs/overview/index.md b/docs/overview/index.md index 468db3e8a..9e2294b0c 100644 --- a/docs/overview/index.md +++ b/docs/overview/index.md @@ -21,7 +21,7 @@ This site includes: - A brief introduction to Tezos for end users (non-technical users) - A presentation of the main Tezos concepts and features for technical users, including developers and bakers -For more details on installing, using, or contributing to the platform, see the Octez documentation at https://tezos.gitlab.io/index.html. +For more details on installing, using, or contributing to the platform, see the Octez documentation at https://octez.tezos.com/docs/index.html. For interactive learning material (including exercises) about Tezos concepts, the underlying technology, application development, and the ecosystem, see https://opentezos.com. @@ -102,7 +102,7 @@ The proof-of-stake consensus mechanism eliminates the need for high energy use, Tezos's proof-of-stake mechanism improves scalability and encourages cooperation via incentives. It also increases the cost of consensus attacks and avoids environmentally wasteful proof-of-work. Tezos launched in June 2018 as one of the first major proof-of-stake networks. -For more information about how Tezos handles proof of stake, see https://tezos.gitlab.io/alpha/proof_of_stake.html. +For more information about how Tezos handles proof of stake, see https://octez.tezos.com/docs/active/proof_of_stake.html. For more information about delegating and staking, see [Bakers](/architecture/bakers). ### Tezos accepts multiple languages diff --git a/docs/overview/resources.md b/docs/overview/resources.md index 29114144f..a74afa907 100644 --- a/docs/overview/resources.md +++ b/docs/overview/resources.md @@ -12,7 +12,7 @@ This site is not exhaustive. It covers the main topics that concern Tezos develo More detailed developer and user documentation on Tezos in general or on specific tools in the Tezos ecosystem is available at these sites: - https://opentezos.com/ is a complete course for learning Tezos concepts, mainly for developers but also for bakers and other users, in the form of tutorials with exercises -- https://tezos.gitlab.io/ is the official documentation of the Octez suite, which contains a complete implementation of the Tezos platform (including a node, a baker, a client, and other tools) +- https://octez.tezos.com/docs/ is the official documentation of the Octez suite, which contains a complete implementation of the Tezos platform (including a node, a baker, a client, and other tools) - https://taqueria.io/docs/intro/ is the official documentation of [Taqueria](https://taqueria.io/), a flexible framework for building Web3 applications on Tezos - https://tezostaquito.io/docs/quick_start is the official documentation of [Taquito](https://tezostaquito.io/), a TypeScript library for developing Tezos applications faster and easier - https://ligolang.org/docs/intro/introduction is the official documentation of the [LIGO](https://ligolang.org/) language for writing Tezos smart contracts diff --git a/docs/reference/style-guide.md b/docs/reference/style-guide.md index 678a87254..8ee034f1d 100644 --- a/docs/reference/style-guide.md +++ b/docs/reference/style-guide.md @@ -20,7 +20,7 @@ You can say that Tezos has advantages over other blockchains, but don't say that - Do not use the term "initial coin offering (ICO)" or refer to Tezos "investors." Instead, refer to the Tezos fundraiser. -See https://tezos.gitlab.io/user/key-management.html#getting-keys-for-fundraiser-accounts. +See https://octez.tezos.com/docs/user/key-management.html#getting-keys-for-fundraiser-accounts. ## Blockchain terminology diff --git a/docs/smart-contracts.mdx b/docs/smart-contracts.mdx index 3d6deacce..3c8a5a726 100644 --- a/docs/smart-contracts.mdx +++ b/docs/smart-contracts.mdx @@ -104,6 +104,6 @@ A smart contract can be called by a classic account or by a smart contract accou Users can call smart contracts from different platforms, including: -- The Octez command-line program, which is provided by Tezos to send transactions to Tezos and interact with the chain in other ways, including hosting a node. For more information about the Octez client, see https://tezos.gitlab.io/. +- The Octez command-line program, which is provided by Tezos to send transactions to Tezos and interact with the chain in other ways, including hosting a node. For more information about the Octez client, see https://octez.tezos.com/docs/. - Remote Procedure Calls (RPCs) via HTTP. - SDKs such as [Taquito](https://tezostaquito.io/). diff --git a/docs/smart-contracts/constants.md b/docs/smart-contracts/constants.md index 00b575da0..5f73ba329 100644 --- a/docs/smart-contracts/constants.md +++ b/docs/smart-contracts/constants.md @@ -15,6 +15,6 @@ It can be used to store code, types, or data. ## Implementation details -- Michelson: [Global constants](https://tezos.gitlab.io/active/global_constants.html) +- Michelson: [Global constants](https://octez.tezos.com/docs/active/global_constants.html) - LIGO: [Global constants](https://ligolang.org/docs/protocol/hangzhou#global-constant) - Archetype: [Global constants](https://archetype-lang.org/docs/cli/contract/) diff --git a/docs/smart-contracts/data-types/complex-data-types.md b/docs/smart-contracts/data-types/complex-data-types.md index 1fa955b17..42de8ffad 100644 --- a/docs/smart-contracts/data-types/complex-data-types.md +++ b/docs/smart-contracts/data-types/complex-data-types.md @@ -63,7 +63,7 @@ $$O(\log_2 (size))$$, whereas for a right comb, it's $$O(size)$$. ### Implementation details -- Michelson: [Operations on pairs and right combs](https://tezos.gitlab.io/active/michelson.html#operations-on-pairs-and-right-combs) +- Michelson: [Pairs](https://tezos.gitlab.io/michelson-reference/#type-pair) - LIGO: [Tuples](https://ligolang.org/docs/language-basics/sets-lists-tuples#tuples) - SmartPy: [Tuples](https://smartpy.io/manual/data-types/tuples) - Archetype: [Composite types](https://archetype-lang.org/docs/language-basics/composite#tuple), [Tuple](https://archetype-lang.org/docs/reference/types#tuple) @@ -164,7 +164,7 @@ Alternatively (but harder to understand without comments), you can use the speci ### Implementation details -- Michelson: [Operations on optional values](https://tezos.gitlab.io/active/michelson.html#operations-on-optional-values) +- Michelson: [Options](https://tezos.gitlab.io/michelson-reference/#type-option) - LIGO: [Optional values](https://ligolang.org/docs/language-basics/unit-option-pattern-matching#optional-values) - SmartPy: [Options and variants](https://smartpy.io/manual/data-types/options-and-variants) - Archetype: [Options](https://archetype-lang.org/docs/reference/types#option%3CT%3E) @@ -282,7 +282,7 @@ Here is a table representing an example of a contract that uses two big-maps: ### Implementation details -- Michelson: [Operations on big-maps](https://tezos.gitlab.io/active/michelson.html#operations-on-big-maps) +- Michelson: [Big-maps](https://tezos.gitlab.io/michelson-reference/#type-big_map) - Archetype: [Assets](https://archetype-lang.org/docs/reference/instructions/asset), [Map](https://archetype-lang.org/docs/language-basics/container#map) - LIGO: [Maps](https://ligolang.org/docs/language-basics/maps-records#maps), [Big-maps](https://ligolang.org/docs/language-basics/maps-records#big-maps) - SmartPy: [Maps](https://smartpy.io/manual/data-types/lists-sets-and-maps#maps) @@ -310,7 +310,7 @@ In general, use big-maps to store large amounts of data. ### Implementation details -- Michelson: [Operations on lists](https://tezos.gitlab.io/active/michelson.html#operations-on-lists) +- Michelson: [Lists](https://tezos.gitlab.io/michelson-reference/#type-list) - SmartPy: [List](https://smartpy.io/manual/data-types/lists-sets-and-maps#lists) - Archetype: [List](https://archetype-lang.org/docs/language-basics/container#list) - LIGO: [List](https://ligolang.org/docs/reference/list-reference) @@ -347,7 +347,7 @@ For example, a variant can hold either an `int` or a `string`. ### Implementation details -- Michelson: [Operations on unions](https://tezos.gitlab.io/active/michelson.html#operations-on-unions) +- Michelson: [Or](https://tezos.gitlab.io/michelson-reference/#type-or) - LIGO: [Variant types](https://ligolang.org/docs/language-basics/unit-option-pattern-matching#variant-types) - SmartPy: [Options and variants](https://smartpy.io/manual/data-types/options-and-variants) - Archetype: [Enum](https://archetype-lang.org/docs/language-basics/composite#enum) @@ -374,7 +374,7 @@ Note that the ability to upgrade the contract can cause users to worry about the ### Implementation details -- Michelson: [Control structures](https://tezos.gitlab.io/active/michelson.html#control-structures) +- Michelson: [Lambdas](https://tezos.gitlab.io/michelson-reference/#type-lambda) - Archetype: [apply_lambda](https://archetype-lang.org/docs/reference/expressions/builtins#apply_lambda%28f%20:%20lambda%3CA%20*%20T,%20R%3E,%20x%20:%20A%29) - SmartPy: [Lambdas](https://smartpy.io/manual/syntax/lambdas) - LIGO: [Anonymous functions](https://ligolang.org/docs/language-basics/functions#anonymous-functions-aka-lambdas) @@ -461,7 +461,7 @@ Contracts can run these operations on tickets: ### Implementation details -- Michelson: [Operations on tickets](https://tezos.gitlab.io/active/michelson.html#operations-on-tickets) +- Michelson: [Tickets](https://tezos.gitlab.io/michelson-reference/#type-ticket) - LIGO: [Tickets](https://ligolang.org/docs/reference/current-reference#tickets) - Archetype: [create_ticket and related](https://archetype-lang.org/docs/reference/expressions/builtins/#create_ticket%28s%20:%20T,%20n%20:%20nat%29) - SmartPy: [Tickets](https://smartpy.io/manual/data-types/tickets) @@ -487,6 +487,7 @@ Unit is a concept that Tezos inherits from OCaml; see [Side-Effects and the unit ### Implementation details +- Michelson: [Unit](https://tezos.gitlab.io/michelson-reference/#type-unit) - LIGO: [Unit](https://ligolang.org/docs/next/data-types/variants#unit) - Archetype: [Unit](https://archetype-lang.org/docs/reference/types/#unit) - SmartPy: [Unit](https://smartpy.io/manual/data-types/unit) diff --git a/docs/smart-contracts/data-types/crypto-data-types.md b/docs/smart-contracts/data-types/crypto-data-types.md index 5d1b5c1d4..06e0f8b45 100644 --- a/docs/smart-contracts/data-types/crypto-data-types.md +++ b/docs/smart-contracts/data-types/crypto-data-types.md @@ -31,7 +31,7 @@ It can also be used for identity-based cryptography, single-round multi-party ke ## Implementation details -- Michelson: [Cryptographic primitives](https://tezos.gitlab.io/active/michelson.html#cryptographic-primitives), [BLS12-381 primitives](https://tezos.gitlab.io/active/michelson.html#bls12-381-primitives) +- Michelson: [Cryptographic primitives](https://octez.tezos.com/docs/active/randomness_generation.html#cryptographic-primitives.html#cryptographic-primitives) - LIGO: [Crypto](https://ligolang.org/docs/reference/crypto-reference) - Archetype: [Blake2b and related](https://archetype-lang.org/docs/reference/expressions/builtins#blake2b%28b%20:%20bytes%29), [Elliptic curves](https://archetype-lang.org/docs/language-basics/crypto#elliptic-curves) - SmartPy: [BLS12-381 ](https://smartpy.io/manual/data-types/bls12-381) @@ -45,6 +45,6 @@ For information about using time-locks, see [Timelocks](/smart-contracts/timeloc ## Implementation details -- Michelson: [Time-lock](https://tezos.gitlab.io/active/timelock.html) +- Michelson: [Time-lock](https://octez.tezos.com/docs/active/timelock.html) - Archetype: [Timelock](https://archetype-lang.org/docs/language-basics/crypto#timelock) - LIGO: [Timelock](https://ligolang.org/docs/reference/current-reference/?lang=jsligo#timelock) diff --git a/docs/smart-contracts/data-types/primitive-data-types.md b/docs/smart-contracts/data-types/primitive-data-types.md index cafbdce33..678ded709 100644 --- a/docs/smart-contracts/data-types/primitive-data-types.md +++ b/docs/smart-contracts/data-types/primitive-data-types.md @@ -185,7 +185,7 @@ The next part of the string is a `Base58` encoded hash, followed by a 4-byte che See these links for technical information about how different languages handle different data types: -- Michelson: [int and nat](https://tezos.gitlab.io/active/michelson.html#operations-on-integers-and-natural-numbers), [booleans](https://tezos.gitlab.io/active/michelson.html#operations-on-booleans), [strings](https://tezos.gitlab.io/active/michelson.html#operations-on-strings), [timestamps](https://tezos.gitlab.io/active/michelson.html#operations-on-timestamps), [mutez](https://tezos.gitlab.io/active/michelson.html#operations-on-mutez). +- Michelson: [int](https://tezos.gitlab.io/michelson-reference/#type-int), [nat](https://tezos.gitlab.io/michelson-reference/#type-nat) [bool](https://tezos.gitlab.io/michelson-reference/#type-bool), [string](https://tezos.gitlab.io/michelson-reference/#type-string), [timestamp](https://tezos.gitlab.io/michelson-reference/#type-timestamp), [mutez](https://tezos.gitlab.io/michelson-reference/#type-mutez). - Archetype: [Types basics](https://archetype-lang.org/docs/language-basics/types), [Types](https://archetype-lang.org/docs/reference/types), [Arithmetic operators](https://archetype-lang.org/docs/reference/expressions/operators/arithmetic) - SmartPy: [Integers and mutez](https://smartpy.io/manual/data-types/integers-and-mutez), [Booleans](https://smartpy.io/manual/data-types/booleans), [Strings and Bytes](https://smartpy.io/manual/data-types/strings-and-bytes), [Timestamps](https://smartpy.io/manual/data-types/timestamps) - LIGO: [numbers and tez](https://ligolang.org/docs/language-basics/math-numbers-tez), [strings & bytes](https://ligolang.org/docs/language-basics/strings-bytes), [booleans](https://ligolang.org/docs/language-basics/boolean-if-else) diff --git a/docs/smart-contracts/delegation.md b/docs/smart-contracts/delegation.md index 162e14c29..fd895502a 100644 --- a/docs/smart-contracts/delegation.md +++ b/docs/smart-contracts/delegation.md @@ -18,6 +18,6 @@ In practice, both the voting power of a contract and the total voting power of a ## Implementation details -- Michelson: [Operations on contracts](https://tezos.gitlab.io/active/michelson.html#operations-on-contracts) +- Michelson: [`SET_DELEGATE`](https://tezos.gitlab.io/michelson-reference/#instr-SET_DELEGATE) - Archetype: [Total voting power](https://archetype-lang.org/docs/reference/expressions/constants#total_voting_power), [Voting power](https://archetype-lang.org/docs/reference/expressions/builtins#voting_power%28k%20:%20key_hash%29), [set_delegate](https://archetype-lang.org/docs/reference/expressions/builtins#set_delegate%28opkh%20:%20option%3Ckey_hash%3E%29) - SmartPy: [Operations](https://smartpy.io/manual/data-types/operations) diff --git a/docs/smart-contracts/entrypoints.md b/docs/smart-contracts/entrypoints.md index 3561bde30..12ea2d8c6 100644 --- a/docs/smart-contracts/entrypoints.md +++ b/docs/smart-contracts/entrypoints.md @@ -86,7 +86,7 @@ Working from the previous example, they convert a call to the `increment` entryp Different languages have different ways of indicating entrypoints. For information about coding entrypoints in specific languages, see these links: -- Michelson: [Entrypoint](https://tezos.gitlab.io/active/michelson.html#entrypoints) +- Michelson: [Entrypoints](https://octez.tezos.com/docs/active/michelson.html#entrypoints) - Archetype: [Entrypoint](https://archetype-lang.org/docs/reference/declarations/entrypoint) - SmartPy: [Contracts](https://smartpy.io/manual/syntax/contracts) - LIGO: [Main function and Entrypoints](https://ligolang.org/docs/advanced/entrypoints-contracts) diff --git a/docs/smart-contracts/events.md b/docs/smart-contracts/events.md index 2aae418d5..b3b355429 100644 --- a/docs/smart-contracts/events.md +++ b/docs/smart-contracts/events.md @@ -175,7 +175,7 @@ For example, to see the operation in the previous example, look up the operation ## Implementation details -- Michelson: [Contract events](https://tezos.gitlab.io/alpha/event.html) +- Michelson: [Contract events](https://octez.tezos.com/docs/active/event.html) - LIGO: [Events](https://ligolang.org/docs/contract/events) - SmartPy: [`sp.emit`](https://smartpy.io/manual/syntax/operations) - Archetype: [Events](https://archetype-lang.org/blog/events/#event) diff --git a/docs/smart-contracts/languages/michelson.mdx b/docs/smart-contracts/languages/michelson.mdx index fc2d1dde2..6c7afeb0b 100644 --- a/docs/smart-contracts/languages/michelson.mdx +++ b/docs/smart-contracts/languages/michelson.mdx @@ -64,6 +64,6 @@ For more information, see [Entrypoints](/smart-contracts/entrypoints). ## Further reading -* [Michelson documentation](http://tezos.gitlab.io/007/michelson.html) +* [Michelson documentation](https://octez.tezos.com/docs/active/michelson.html) * [Michelson Reference](https://tezos.gitlab.io/michelson-reference/) * [Michelson tutorial series](https://gitlab.com/camlcase-dev/michelson-tutorial/tree/master) diff --git a/docs/smart-contracts/logic/comparing.md b/docs/smart-contracts/logic/comparing.md index 93d6e73cc..d657bd6e5 100644 --- a/docs/smart-contracts/logic/comparing.md +++ b/docs/smart-contracts/logic/comparing.md @@ -36,7 +36,7 @@ In Michelson, comparisons are done in two steps: ### Implementation details -- Michelson: [Generic comparison](https://tezos.gitlab.io/active/michelson.html#generic-comparison) +- Michelson: [Generic comparison](https://octez.tezos.com/docs/active/michelson.html#compare) - Archetype: [Comparison operators](https://archetype-lang.org/docs/reference/expressions/operators/arithmetic#a--b-7) - SmartPy: [Comparison](https://smartpy.io/manual/data-types/integers-and-mutez#comparison) - LIGO: [Comparing values](https://ligolang.org/docs/language-basics/boolean-if-else#comparing-values) diff --git a/docs/smart-contracts/logic/errors.md b/docs/smart-contracts/logic/errors.md index 4b100fd62..0a151b488 100644 --- a/docs/smart-contracts/logic/errors.md +++ b/docs/smart-contracts/logic/errors.md @@ -63,9 +63,7 @@ In particular, the error value is often used when testing contracts, where the ## Implementation details - Michelson: - - [Failures](https://tezos.gitlab.io/active/michelson.html#failures) - - [Control structures](https://tezos.gitlab.io/active/michelson.html#control-structures) - - [FAIL](https://tezos.gitlab.io/active/michelson.html#fail) + - [Failures](https://octez.tezos.com/docs/active/michelson.html#failures) - [Assertion macros](https://tezos.gitlab.io/active/michelson.html#assertion-macros), - Archetype: [require](https://archetype-lang.org/docs/reference/declarations/entrypoint/#require), [fail if](https://archetype-lang.org/docs/reference/declarations/entrypoint/#fail-if) - SmartPy: [Exceptions](https://smartpy.io/manual/syntax/exceptions) diff --git a/docs/smart-contracts/logic/loops.md b/docs/smart-contracts/logic/loops.md index ea7925031..24e6df635 100644 --- a/docs/smart-contracts/logic/loops.md +++ b/docs/smart-contracts/logic/loops.md @@ -18,6 +18,6 @@ In many cases, it is possible to avoid performing loops in the contract itself b ## Implementation details -- Michelson: [Control structures](https://tezos.gitlab.io/active/michelson.html#control-structures) +- Michelson: [`LOOP`](https://tezos.gitlab.io/michelson-reference/#instr-LOOP) - Archetype: [Asset - iteration](https://archetype-lang.org/docs/asset#iteration), [for](https://archetype-lang.org/docs/reference/instructions/control#for), [while](https://archetype-lang.org/docs/reference/instructions/control#while), [iter](https://archetype-lang.org/docs/reference/instructions/control#iter) - LIGO: [Iteration](https://ligolang.org/docs/language-basics/loops) diff --git a/docs/smart-contracts/logic/operations.md b/docs/smart-contracts/logic/operations.md index f8db905e7..1ff6fbe8d 100644 --- a/docs/smart-contracts/logic/operations.md +++ b/docs/smart-contracts/logic/operations.md @@ -120,7 +120,7 @@ To summarize: ## Implementation details -- Michelson: [Operations on contracts](https://tezos.gitlab.io/active/michelson.html#operations-on-contracts) +- Michelson: [Operations](https://tezos.gitlab.io/michelson-reference/#type-operation) - Archetype: [Operation](https://archetype-lang.org/docs/reference/instructions/operation) - LIGO: [Inter-contract invocations](https://ligolang.org/docs/advanced/entrypoints-contracts#inter-contract-invocations) - SmartPy: [Operations](https://smartpy.io/manual/data-types/operations) diff --git a/docs/smart-contracts/multisig.md b/docs/smart-contracts/multisig.md index e54a555b4..4736e1bda 100644 --- a/docs/smart-contracts/multisig.md +++ b/docs/smart-contracts/multisig.md @@ -256,7 +256,7 @@ octez-client run transaction "$TO_SIGN" \ The contract uses a counter to ensure that the signatures work only once. -For more information, run the command `octez-client man multisig` and see [Built-in multisig contracts](https://tezos.gitlab.io/user/multisig.html) in the Octez documentation. +For more information, run the command `octez-client man multisig` and see [Built-in multisig contracts](https://octez.tezos.com/docs/user/multisig.html) in the Octez documentation. ## Setting up multi-signature wallets diff --git a/docs/smart-contracts/sapling.md b/docs/smart-contracts/sapling.md index 5d2477bce..a96b83187 100644 --- a/docs/smart-contracts/sapling.md +++ b/docs/smart-contracts/sapling.md @@ -36,6 +36,6 @@ The process uses a mix of cryptographic tools including SNARKs, incremental Merk ## Implementation information -- Michelson: [Sapling integration](https://tezos.gitlab.io/active/sapling.html) +- Michelson: [Sapling integration](https://octez.tezos.com/docs/active/sapling.html) - Archetype: [Sapling](https://archetype-lang.org/docs/language-basics/crypto#sapling) - LIGO: [Sapling](https://ligolang.org/docs/reference/current-reference#sapling) diff --git a/docs/smart-contracts/special-values.md b/docs/smart-contracts/special-values.md index b8e93308b..670d35d44 100644 --- a/docs/smart-contracts/special-values.md +++ b/docs/smart-contracts/special-values.md @@ -58,7 +58,7 @@ It increments by one for each new block. ## Implementation details -- Michelson: [Special operations](https://tezos.gitlab.io/active/michelson.html#special-operations), [Operations on contracts](https://tezos.gitlab.io/active/michelson.html#operations-on-contracts) +- Michelson: [Michelson reference](https://tezos.gitlab.io/michelson-reference/) - Archetype: [Constants](https://archetype-lang.org/docs/reference/expressions/constants/#now) - SmartPy: [Timestamps](https://smartpy.io/manual/data-types/timestamps) - LIGO: [Tezos](https://ligolang.org/docs/reference/current-reference), [Tezos specific built-ins](https://ligolang.org/docs/advanced/entrypoints-contracts#tezos-specific-built-ins), [Tezos.now](https://ligolang.org/docs/advanced/timestamps-addresses#starting-time-of-the-current-block) diff --git a/docs/smart-contracts/views.md b/docs/smart-contracts/views.md index b7fad13a7..e425e138d 100644 --- a/docs/smart-contracts/views.md +++ b/docs/smart-contracts/views.md @@ -218,7 +218,7 @@ If the view takes no parameters, you can pass Unit or omit the `with input`. ## Implementation details -- Octez: [On-chain views](https://tezos.gitlab.io/active/views.html) +- Octez: [On-chain views](https://octez.tezos.com/docs/active/views.html) - Archetype: [View](https://archetype-lang.org/docs/reference/declarations/view) - SmartPy: [Testing expressions](https://smartpy.io/manual/scenarios/testing_contracts#testing-expressions-views-and-lambdas) - LIGO: [On-chain views](https://ligolang.org/docs/protocol/hangzhou#on-chain-views) diff --git a/docs/tutorials/build-files-archive-with-dal.md b/docs/tutorials/build-files-archive-with-dal.md index 224b36768..6659c00f4 100644 --- a/docs/tutorials/build-files-archive-with-dal.md +++ b/docs/tutorials/build-files-archive-with-dal.md @@ -24,7 +24,7 @@ You will learn: See these links for more information about the DAL: -- For technical information about how the DAL works, see [Data Availability Layer](https://tezos.gitlab.io/shell/dal.html) in the Octez documentation. +- For technical information about how the DAL works, see [Data Availability Layer](https://octez.tezos.com/docs/shell/dal.html) in the Octez documentation. - For more information about the approach for the DAL, see [The Rollup Booster: A Data-Availability Layer for Tezos](https://research-development.nomadic-labs.com/data-availability-layer-tezos.html). ## Tutorial applications diff --git a/docs/tutorials/build-files-archive-with-dal/set-up-environment.md b/docs/tutorials/build-files-archive-with-dal/set-up-environment.md index c43645a8b..58791f852 100644 --- a/docs/tutorials/build-files-archive-with-dal/set-up-environment.md +++ b/docs/tutorials/build-files-archive-with-dal/set-up-environment.md @@ -10,7 +10,7 @@ To work with these elements, you need the Octez suite, which includes the Octez You must use the same version of the Octez suite that the network is using. The easiest way to use the Octez suite is to use the `tezos/tezos` Docker image. -As another option, you can get the built version of the Octez suite from https://tezos.gitlab.io/ or build the specific version of the Octez suite locally. +As another option, you can get the built version of the Octez suite from https://octez.tezos.com/docs/ or build the specific version of the Octez suite locally. To set up an environment and account in a Docker container, follow these steps: diff --git a/docs/tutorials/dapp/part-1.md b/docs/tutorials/dapp/part-1.md index ef5da823e..a80d04afe 100644 --- a/docs/tutorials/dapp/part-1.md +++ b/docs/tutorials/dapp/part-1.md @@ -102,7 +102,7 @@ The LIGO command-line provides sub-commands to test your LIGO code. Taqueria is generating the `.tz` Michelson file in the `artifacts` folder. The Michelson language is the default stack language used by the Michelson VM to run your code on a node. It is something similar to WASM. - [Have a look on the Michelson documentation](https://tezos.gitlab.io/active/michelson.html) + [Have a look on the Michelson documentation](https://octez.tezos.com/docs/active/michelson.html) 1. Taqueria is generating two additional files, edit the first file `pokeGame.storageList.jsligo` replacing the current code with: diff --git a/docs/tutorials/join-dal-baker.md b/docs/tutorials/join-dal-baker.md index 0e6057967..edf3dd740 100644 --- a/docs/tutorials/join-dal-baker.md +++ b/docs/tutorials/join-dal-baker.md @@ -42,7 +42,7 @@ For now, bakers can join the DAL without risking any reward loss, ensuring a smo ## Do you already run a baker? For current bakers, it's a straightforward process to add a DAL node. -If you are familiar with running a node and baker, you can add a DAL node to your existing setup by following the instructions in [Running a DAL attester node](https://tezos.gitlab.io/shell/dal_run.html). +If you are familiar with running a node and baker, you can add a DAL node to your existing setup by following the instructions in [Running a DAL attester node](https://octez.tezos.com/docs/shell/dal_run.html). ## Running a baker and DAL node from start to finish @@ -74,7 +74,7 @@ The following diagram shows these daemons with a blue background: ## Prerequisites To run the Octez daemons persistently, you need a cloud-based computer or a computer that stays running constantly. -For other system requirements, see the documentation for the [latest release of the Octez suite](https://tezos.gitlab.io/releases/latest.html) +For other system requirements, see the documentation for the [latest release of the Octez suite](https://octez.tezos.com/docs/releases/latest.html) (search for section "Minimal hardware specifications"). ## Other options for running a baker @@ -91,7 +91,7 @@ Here are some of these tools: - For an overview of the DAL, see [Data Availability Layer](/architecture/data-availability-layer). - For an introduction to how the DAL works, see the tutorial [Implement a file archive with the DAL and a Smart Rollup](/tutorials/build-files-archive-with-dal). -- For technical information about the DAL, see [Data-Availability Layer](https://tezos.gitlab.io/shell/dal.html) in the Octez documentation. +- For technical information about the DAL, see [Data-Availability Layer](https://octez.tezos.com/docs/shell/dal.html) in the Octez documentation. ## Getting started diff --git a/docs/tutorials/join-dal-baker/prepare-account.md b/docs/tutorials/join-dal-baker/prepare-account.md index b43fd5481..45437cd13 100644 --- a/docs/tutorials/join-dal-baker/prepare-account.md +++ b/docs/tutorials/join-dal-baker/prepare-account.md @@ -22,7 +22,7 @@ In this way you can avoid transferring or backing up the consensus key or you ca However, the consensus key can drain the liquid (unstaked) tez from the baker key, so you must keep the consensus key secure like all other keys. -For more information about consensus keys, see [Consensus key](https://tezos.gitlab.io/user/key-management.html#consensus-key) in the Octez documentation. +For more information about consensus keys, see [Consensus key](https://octez.tezos.com/docs/user/key-management.html#consensus-key) in the Octez documentation. ## Creating the accounts diff --git a/docs/tutorials/join-dal-baker/run-baker.md b/docs/tutorials/join-dal-baker/run-baker.md index 2e4298192..08b38d318 100644 --- a/docs/tutorials/join-dal-baker/run-baker.md +++ b/docs/tutorials/join-dal-baker/run-baker.md @@ -16,14 +16,14 @@ However, it is safe to run two baking daemons during the protocol upgrade proces ::: -1. Optional: Set up a remote signer to secure the keys that the baker uses as described in [Signer](https://tezos.gitlab.io/user/key-management.html#signer) in the Octez documentation. +1. Optional: Set up a remote signer to secure the keys that the baker uses as described in [Signer](https://octez.tezos.com/docs/user/key-management.html#signer) in the Octez documentation. 1. Run a baking daemon with the following arguments: - Use the consensus key, not the baker key, if you are using a consensus key - Pass the URL to your DAL node with the `--dal-node` argument - - Pass the `--liquidity-baking-toggle-vote` argument; for more information, see [Liquidity baking](https://tezos.gitlab.io/active/liquidity_baking.html) in the Octez documentation - - Pass the `--adaptive-issuance-vote` argument; for more information, see [Adaptive Issuance and Staking](https://tezos.gitlab.io/active/adaptive_issuance.html) in the Octez documentation + - Pass the `--liquidity-baking-toggle-vote` argument; for more information, see [Liquidity baking](https://octez.tezos.com/docs/active/liquidity_baking.html) in the Octez documentation + - Pass the `--adaptive-issuance-vote` argument; for more information, see [Adaptive issuance](https://octez.tezos.com/docs/active/adaptive_issuance.html) in the Octez documentation For example: @@ -109,7 +109,7 @@ Therefore, when a new version of the Tezos protocol becomes active, you must sta To simplify the upgrade process, you can follow these steps when the new protocol is about to be activated: -1. Check the release pages in the [Octez documentation](https://tezos.gitlab.io) (section `Changes in Octez releases`) or check the posts on the forum at https://forum.tezosagora.org to see which version of the Octez suite supports the upcoming protocol and upgrade your Octez suite if necessary. +1. Check the release pages in the [Octez documentation](https://octez.tezos.com/docs) (section `Changes in Octez releases`) or check the posts on the forum at https://forum.tezosagora.org to see which version of the Octez suite supports the upcoming protocol and upgrade your Octez suite if necessary. The Octez release page gives instructions for upgrading. 1. Leave the baker for the previous protocol running, such as the `octez-baker-PsParisC` daemon. @@ -126,7 +126,7 @@ You can upgrade accusers with a similar process. ## Backing up and restoring the baker -The Octez baking daemon stores persistent operational data in the Octez client's data directory, notably consensus high-water marks and [random seed nonces](https://tezos.gitlab.io/active/randomness_generation.html). +The Octez baking daemon stores persistent operational data in the Octez client's data directory, notably consensus high-water marks and [random seed nonces](https://octez.tezos.com/docs/active/randomness_generation.html). If you want to back up the baker or move it to another machine and restore it, you must copy the nonce file or files from the Octez client's data directory to the equivalent directory on the new machine. These nonce files are named `net_stateful_nonces` and `net_nonces`, where `` is the ID of the network, such as `netXdQprcVkpaWU_stateful_nonces` for Mainnet or `netXnHfVqm9ie_stateful_nonces` for Ghostnet. All deployments have the `net_stateful_nonces` file but only legacy baking deployments running versions of Octez prior to 20.0rc1 have the `net_nonces` file. diff --git a/docs/tutorials/join-dal-baker/run-dal-node.md b/docs/tutorials/join-dal-baker/run-dal-node.md index c46cfa319..4f7b8afec 100644 --- a/docs/tutorials/join-dal-baker/run-dal-node.md +++ b/docs/tutorials/join-dal-baker/run-dal-node.md @@ -12,7 +12,7 @@ Follow these steps to run the DAL node: 1. Ensure that the port on which the DAL node listens for connections from peer nodes (by default, 11732) is accessible from outside its system. You may need to adapt your firewall rules or set up network address translation (NAT) to direct external traffic to the DAL node. -For more information, see [Running a DAL attester node](https://tezos.gitlab.io/shell/dal_run.html) in the Octez documentation. +For more information, see [Running a DAL attester node](https://octez.tezos.com/docs/shell/dal_run.html) in the Octez documentation. 1. Initialize the DAL node by running its `config init` command, passing the address of your `octez-node` instance in the `--endpoint` argument and your baker's account address in the `--attester-profiles` argument. For example, this command initializes the DAL node with the address of a local `octez-node` instance on port 8732 and stores data in the default DAL node directory (`~/.tezos-dal-node`): @@ -110,7 +110,7 @@ For example, this command initializes the DAL node with the address of a local ` 1. Ensure that the DAL node runs persistently. Look up how to run programs persistently in the documentation for your operating system. -You can also refer to [Setting up Octez Services](https://tezos.gitlab.io/introduction/services.html) in the Octez documentation. +You can also refer to [Setting up Octez Services](https://octez.tezos.com/docs/introduction/services.html) in the Octez documentation. For example, if your operating system uses the `systemd` software suite, your service file might look like this example: diff --git a/docs/tutorials/join-dal-baker/run-node.md b/docs/tutorials/join-dal-baker/run-node.md index 820e4ae69..9f8d52536 100644 --- a/docs/tutorials/join-dal-baker/run-node.md +++ b/docs/tutorials/join-dal-baker/run-node.md @@ -30,7 +30,7 @@ The version of Octez to use depends on the Tezos network that you are using. - For Weeklynet, look up the necessary version of Octez at https://teztnets.com/weeklynet-about and install it with the instructions there. -For more installation options, see [Installing Octez](https://tezos.gitlab.io/introduction/howtoget.html) in the Octez documentation. +For more installation options, see [Installing Octez](https://octez.tezos.com/docs/introduction/howtoget.html) in the Octez documentation. If you build from source, you can use the `latest-release` branch to work with Ghostnet. @@ -63,7 +63,7 @@ For example, the command to download a Ghostnet snapshot from the European serve octez-node snapshot import snapshot_file ``` -1. Install the Zcash parameters as described [Install Zcash Parameters](https://tezos.gitlab.io/introduction/howtoget.html#setup-zcash-params) in the Octez documentation. +1. Install the Zcash parameters as described [Install Zcash Parameters](https://octez.tezos.com/docs/introduction/howtoget.html#setup-zcash-params) in the Octez documentation. 1. Start the node: @@ -104,7 +104,7 @@ For example, the command to download a Ghostnet snapshot from the European serve 1. Ensure that the node runs persistently. Look up how to run programs persistently in the documentation for your operating system. -You can also refer to [Setting up Octez Services](https://tezos.gitlab.io/introduction/services.html) in the Octez documentation. +You can also refer to [Setting up Octez Services](https://octez.tezos.com/docs/introduction/services.html) in the Octez documentation. For example, if your operating system uses the `systemd` software suite, your service file might look like this example: diff --git a/docs/tutorials/join-dal-baker/verify-rights.md b/docs/tutorials/join-dal-baker/verify-rights.md index 8cb2374c5..562f7e5fa 100644 --- a/docs/tutorials/join-dal-baker/verify-rights.md +++ b/docs/tutorials/join-dal-baker/verify-rights.md @@ -140,7 +140,7 @@ After the delay that you calculated in [Step 4: Run an Octez baking daemon](/tut If you don't see DAL attestation rights: - - Verify that your DAL node is connected to the network by following the instructions in [Troubleshooting](https://tezos.gitlab.io/shell/dal_run.html#troubleshooting) in the Octez documentation. + - Verify that your DAL node is connected to the network by following the instructions in [Troubleshooting](https://octez.tezos.com/docs/shell/dal_run.html#troubleshooting) in the Octez documentation. ## Optional: Changing the consensus key diff --git a/docs/tutorials/smart-rollup/deploy.md b/docs/tutorials/smart-rollup/deploy.md index 74320167b..168444316 100644 --- a/docs/tutorials/smart-rollup/deploy.md +++ b/docs/tutorials/smart-rollup/deploy.md @@ -16,7 +16,7 @@ This command creates an address for the rollup and stores a small amount of data This command starts a Tezos testing environment, including a baking node running in sandbox mode and a group of test accounts. The console shows repeated messages that show that the node is baking blocks. - For more information about sandbox mode, see [sandbox mode](https://tezos.gitlab.io/user/sandbox.html). + For more information about sandbox mode, see [Sandboxed mode](https://octez.tezos.com/docs/user/sandbox.html). If you see an error that says "Unable to connect to the node," you can ignore it because it happens only once while the node is starting. diff --git a/docs/tutorials/smart-rollup/optimize.md b/docs/tutorials/smart-rollup/optimize.md index 7fd656a01..1e0595ce6 100644 --- a/docs/tutorials/smart-rollup/optimize.md +++ b/docs/tutorials/smart-rollup/optimize.md @@ -73,7 +73,7 @@ In these steps, you reduce the size of the kernel: - `preimages/`: A directory that contains the preimages that allow nodes to restore the original kernel code When a node runs the installer kernel, it retrieves the preimages through the reveal data channel, a channel that Smart Rollups use to request data from outside of layer 1. - For more information about the reveal data channel, see [reveal data channel](https://tezos.gitlab.io/alpha/smart_rollups.html#reveal-data-channel). + For more information about the reveal data channel, see [Reveal data channel](https://octez.tezos.com/docs/active/smart_rollups.html#reveal-data-channel). 1. Verify the size of the installer kernel by running this command: diff --git a/docs/tutorials/smart-rollup/run.md b/docs/tutorials/smart-rollup/run.md index a8d340d62..d974e166c 100644 --- a/docs/tutorials/smart-rollup/run.md +++ b/docs/tutorials/smart-rollup/run.md @@ -96,7 +96,7 @@ If you want to explore further, you can try deploying the rollup to a testnet as The workflow for deploying to a testnet is similar to the workflow that you used to deploy to the sandbox: 1. Configure the network to use the testnet -1. Run a node (needs to synchronize with the network — can make use of [snapshots](https://tezos.gitlab.io/user/snapshots.html)) +1. Run a node (needs to synchronize with the network — can make use of [snapshots](https://octez.tezos.com/docs/user/snapshots.html)) 1. Create or import an account and fun it by a faucet 1. Originate the rollup to the testnet 1. Start the rollup node @@ -107,7 +107,7 @@ To continue your work with Smart Rollups, you can you can explore examples from ## References -- [Smart Rollup documentation](https://tezos.gitlab.io/alpha/smart_rollups.html) +- [Smart Rollup documentation](https://octez.tezos.com/docs/active/smart_rollups.html) - [Smart Rollup kernel SDK](https://gitlab.com/tezos/tezos/-/tree/master/src/kernel_sdk) - [Smart Rollup kernel examples](https://gitlab.com/tezos/kernel-gallery/-/tree/main/) - [Tezos Smart Rollups resources](https://airtable.com/shrvwpb63rhHMiDg9/tbl2GNV1AZL4dkGgq) diff --git a/docs/tutorials/smartpy-fa2-fungible/basic-fa2-token.md b/docs/tutorials/smartpy-fa2-fungible/basic-fa2-token.md index 5b66313f6..ed6c4a188 100644 --- a/docs/tutorials/smartpy-fa2-fungible/basic-fa2-token.md +++ b/docs/tutorials/smartpy-fa2-fungible/basic-fa2-token.md @@ -514,7 +514,7 @@ Follow these steps to set up the Octez client mockup mode and deploy the contrac -For more information, see [Mockup mode](https://tezos.gitlab.io/user/mockup.html) in the Octez documentation. +For more information, see [Mockup mode](https://octez.tezos.com/docs/user/mockup.html) in the Octez documentation. Now you have a basic FA2 fungible token contract that starts with a predefined amount of tokens. diff --git a/docs/unity/calling-contracts.md b/docs/unity/calling-contracts.md index 4ca58844f..01e548ec7 100644 --- a/docs/unity/calling-contracts.md +++ b/docs/unity/calling-contracts.md @@ -92,7 +92,7 @@ private void OperationResulted(OperationResponse operationResponse) ### Encoding parameters -Tezos entrypoint parameters must be in [Micheline](https://tezos.gitlab.io/shell/micheline.html) JSON format, which is the format that the Michelson language uses for values. +Tezos entrypoint parameters must be in [Micheline](https://octez.tezos.com/docs/shell/micheline.html) JSON format, which is the format that the Michelson language uses for values. You can use the [Netezos](https://netezos.dev/) SDK to format Micheline parameters or construct them as JSON strings. #### Encoding parameters with the Netezos Micheline SDK diff --git a/docs/using/staking.md b/docs/using/staking.md index bcdcb9d8d..7da22bac6 100644 --- a/docs/using/staking.md +++ b/docs/using/staking.md @@ -23,7 +23,7 @@ Users can stake any amount of tez, but there is a limit to how much staked tez a :::note How much tez do I receive in return for staking tez? The amount of tez that you receive for staking tez depends on many factors, including how much you stake and how lucky your baker is. -Due to the mechanism of [adaptive issuance](https://tezos.gitlab.io/active/adaptive_issuance.html), the returns for staking also depend on the ratio of staked tez to total tez in existence, to encourage a balance of staked tez to liquid tez. +Due to the mechanism of [adaptive issuance](https://octez.tezos.com/docs/active/adaptive_issuance.html), the returns for staking also depend on the ratio of staked tez to total tez in existence, to encourage a balance of staked tez to liquid tez. You can look up an estimated rate of return on block explorers. ::: diff --git a/docs/using/user-accounts.md b/docs/using/user-accounts.md index acb3b1ac7..530e6de27 100644 --- a/docs/using/user-accounts.md +++ b/docs/using/user-accounts.md @@ -19,7 +19,7 @@ In this way, using a Tezos account is how you prove your identity to the Tezos s This page discusses user accounts. As described in [Accounts](/architecture/accounts), other types of Tezos accounts include [smart contracts](/smart-contracts) and [Smart Rollups](/architecture/smart-rollups). -For technical information on user accounts, see [Accounts and addresses](https://tezos.gitlab.io/active/accounts.html) in the Octez documentation. +For technical information on user accounts, see [Accounts and addresses](https://octez.tezos.com/docs/active/accounts.html) in the Octez documentation. Tezos users use wallets to manage their accounts; see [Wallets](/using/wallets). From 0b7ea87687754b92ed6fd8325135042ac55af42a Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 14 Feb 2025 09:49:38 -0500 Subject: [PATCH 2/8] New glossary path --- src/scripts/process_downloaded_glossary.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/scripts/process_downloaded_glossary.js b/src/scripts/process_downloaded_glossary.js index e374372aa..94059288d 100644 --- a/src/scripts/process_downloaded_glossary.js +++ b/src/scripts/process_downloaded_glossary.js @@ -36,7 +36,7 @@ const process_glossary = async () => { // Download glossary and conversion script const glossarySourceFileName = path.resolve(buildFolder, 'glossary.html'); - const glossaryFilePromise = download('https://tezos.gitlab.io/active/glossary.html', glossarySourceFileName); + const glossaryFilePromise = download('https://octez.tezos.com/docs/active/glossary.html', glossarySourceFileName); await Promise.resolve(glossaryFilePromise); const downloadedGlossaryDom = new JSDOM(await fs.promises.readFile(glossarySourceFileName, 'utf8')); From 889d19c7869b650aef1ea4b7b39e2ed919406df9 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 14 Feb 2025 10:58:26 -0500 Subject: [PATCH 3/8] Fix for flextesa link --- docs/developing/sandbox.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developing/sandbox.md b/docs/developing/sandbox.md index 39bf9e10c..a7bcffb5c 100644 --- a/docs/developing/sandbox.md +++ b/docs/developing/sandbox.md @@ -82,4 +82,4 @@ Now you can use the Octez client to deploy contracts and send transactions to th Flextesa allows you to control baking manually, so blocks are only backed when you trigger them. -For more information, see the [Flextesa documentation](https://octez.tezos.com/docs/flextesa/). +For more information, see the [Flextesa documentation](https://tezos.gitlab.io/flextesa/). From ae0e1b22dda60d86e44c3f643543614b4a1b5c83 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 14 Feb 2025 11:00:53 -0500 Subject: [PATCH 4/8] Apply suggestions from code review Co-authored-by: NicNomadic <148877430+NicNomadic@users.noreply.github.com> --- docs/overview/index.md | 2 +- docs/smart-contracts/data-types/crypto-data-types.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/overview/index.md b/docs/overview/index.md index 9e2294b0c..2ab7bbef6 100644 --- a/docs/overview/index.md +++ b/docs/overview/index.md @@ -21,7 +21,7 @@ This site includes: - A brief introduction to Tezos for end users (non-technical users) - A presentation of the main Tezos concepts and features for technical users, including developers and bakers -For more details on installing, using, or contributing to the platform, see the Octez documentation at https://octez.tezos.com/docs/index.html. +For more details on installing, using, or contributing to the platform, see the Octez documentation at https://octez.tezos.com/docs/. For interactive learning material (including exercises) about Tezos concepts, the underlying technology, application development, and the ecosystem, see https://opentezos.com. diff --git a/docs/smart-contracts/data-types/crypto-data-types.md b/docs/smart-contracts/data-types/crypto-data-types.md index 06e0f8b45..f220fca70 100644 --- a/docs/smart-contracts/data-types/crypto-data-types.md +++ b/docs/smart-contracts/data-types/crypto-data-types.md @@ -31,7 +31,7 @@ It can also be used for identity-based cryptography, single-round multi-party ke ## Implementation details -- Michelson: [Cryptographic primitives](https://octez.tezos.com/docs/active/randomness_generation.html#cryptographic-primitives.html#cryptographic-primitives) +- Michelson: [Cryptographic primitives](https://octez.tezos.com/docs/active/randomness_generation.html#cryptographic-primitives) - LIGO: [Crypto](https://ligolang.org/docs/reference/crypto-reference) - Archetype: [Blake2b and related](https://archetype-lang.org/docs/reference/expressions/builtins#blake2b%28b%20:%20bytes%29), [Elliptic curves](https://archetype-lang.org/docs/language-basics/crypto#elliptic-curves) - SmartPy: [BLS12-381 ](https://smartpy.io/manual/data-types/bls12-381) From 235de68e0f9c015ecec8a35958c7ec32c6f35379 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 14 Feb 2025 11:02:06 -0500 Subject: [PATCH 5/8] Add VOTING_POWER and TOTAL_VOTING_POWER --- docs/smart-contracts/delegation.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/smart-contracts/delegation.md b/docs/smart-contracts/delegation.md index fd895502a..5f7e0349f 100644 --- a/docs/smart-contracts/delegation.md +++ b/docs/smart-contracts/delegation.md @@ -18,6 +18,9 @@ In practice, both the voting power of a contract and the total voting power of a ## Implementation details -- Michelson: [`SET_DELEGATE`](https://tezos.gitlab.io/michelson-reference/#instr-SET_DELEGATE) +- Michelson: + - [`SET_DELEGATE`](https://tezos.gitlab.io/michelson-reference/#instr-SET_DELEGATE) + - [`VOTING_POWER`](https://tezos.gitlab.io/michelson-reference/#instr-VOTING_POWER) + - [`TOTAL_VOTING_POWER`](https://tezos.gitlab.io/michelson-reference/#instr-TOTAL_VOTING_POWER) - Archetype: [Total voting power](https://archetype-lang.org/docs/reference/expressions/constants#total_voting_power), [Voting power](https://archetype-lang.org/docs/reference/expressions/builtins#voting_power%28k%20:%20key_hash%29), [set_delegate](https://archetype-lang.org/docs/reference/expressions/builtins#set_delegate%28opkh%20:%20option%3Ckey_hash%3E%29) - SmartPy: [Operations](https://smartpy.io/manual/data-types/operations) From 7610e6868c764e2860d50d0e2e83c3bb26018fa3 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 14 Feb 2025 11:03:15 -0500 Subject: [PATCH 6/8] Add FAILWITH --- docs/smart-contracts/logic/errors.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/smart-contracts/logic/errors.md b/docs/smart-contracts/logic/errors.md index 0a151b488..8a7ff8c73 100644 --- a/docs/smart-contracts/logic/errors.md +++ b/docs/smart-contracts/logic/errors.md @@ -64,7 +64,8 @@ In particular, the error value is often used when testing contracts, where the - Michelson: - [Failures](https://octez.tezos.com/docs/active/michelson.html#failures) - - [Assertion macros](https://tezos.gitlab.io/active/michelson.html#assertion-macros), + - [Assertion macros](https://tezos.gitlab.io/active/michelson.html#assertion-macros) + - [`FAILWITH`](https://tezos.gitlab.io/michelson-reference/#instr-FAILWITH) - Archetype: [require](https://archetype-lang.org/docs/reference/declarations/entrypoint/#require), [fail if](https://archetype-lang.org/docs/reference/declarations/entrypoint/#fail-if) - SmartPy: [Exceptions](https://smartpy.io/manual/syntax/exceptions) - LIGO: [Exceptions](https://ligolang.org/docs/language-basics/exceptions) From 7dcca44e23271f2123dc07a1427cae4fd39ba3a1 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 14 Feb 2025 11:04:34 -0500 Subject: [PATCH 7/8] Link to control structures Co-authored-by: NicNomadic <148877430+NicNomadic@users.noreply.github.com> --- docs/smart-contracts/logic/loops.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/smart-contracts/logic/loops.md b/docs/smart-contracts/logic/loops.md index 24e6df635..73c9e1ab2 100644 --- a/docs/smart-contracts/logic/loops.md +++ b/docs/smart-contracts/logic/loops.md @@ -18,6 +18,6 @@ In many cases, it is possible to avoid performing loops in the contract itself b ## Implementation details -- Michelson: [`LOOP`](https://tezos.gitlab.io/michelson-reference/#instr-LOOP) +- Michelson: [`Control structures`](https://tezos.gitlab.io/michelson-reference/#instructions-control_structure) - Archetype: [Asset - iteration](https://archetype-lang.org/docs/asset#iteration), [for](https://archetype-lang.org/docs/reference/instructions/control#for), [while](https://archetype-lang.org/docs/reference/instructions/control#while), [iter](https://archetype-lang.org/docs/reference/instructions/control#iter) - LIGO: [Iteration](https://ligolang.org/docs/language-basics/loops) From f31d2762423b9533a5a8400b255d23318ba0bec3 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 14 Feb 2025 11:05:25 -0500 Subject: [PATCH 8/8] ADd link to control structures --- docs/smart-contracts/logic/errors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/smart-contracts/logic/errors.md b/docs/smart-contracts/logic/errors.md index 8a7ff8c73..bc0f7d407 100644 --- a/docs/smart-contracts/logic/errors.md +++ b/docs/smart-contracts/logic/errors.md @@ -64,7 +64,7 @@ In particular, the error value is often used when testing contracts, where the - Michelson: - [Failures](https://octez.tezos.com/docs/active/michelson.html#failures) - - [Assertion macros](https://tezos.gitlab.io/active/michelson.html#assertion-macros) + - [Control structures](https://tezos.gitlab.io/michelson-reference/#instructions-control_structure) - [`FAILWITH`](https://tezos.gitlab.io/michelson-reference/#instr-FAILWITH) - Archetype: [require](https://archetype-lang.org/docs/reference/declarations/entrypoint/#require), [fail if](https://archetype-lang.org/docs/reference/declarations/entrypoint/#fail-if) - SmartPy: [Exceptions](https://smartpy.io/manual/syntax/exceptions)