chore: change the tezostaquito.io domain to taquito.io

.github/workflows/deploy_edge.yml

@@ -34,15 +34,15 @@ jobs:
     - run: git config user.email "actions@github.com" && git config user.name "Github Actions"
     - run: git add . && git commit -m "committing changes to files to make lerna happy in next step, this is expected to never be pushed to remote"
     - run: echo ${VERDACCIO_TOKEN} >> ~/.npmrc
-    - run: npx lerna publish --dist-tag edge from-package --yes --registry https://npm.preview.tezostaquito.io/
+    - run: npx lerna publish --dist-tag edge from-package --yes --registry https://npm.preview.taquito.io/
     - if: ${{ github.event_name == 'pull_request' }}
       run: |
           echo "COMMENT_BODY<<EOF"  >> $GITHUB_ENV
-          echo "New packages have been deployed to the preview repository at https://npm.preview.tezostaquito.io/." >> $GITHUB_ENV
+          echo "New packages have been deployed to the preview repository at https://npm.preview.taquito.io/." >> $GITHUB_ENV
           echo "" >> $GITHUB_ENV
           echo "### Published packages:" >> $GITHUB_ENV
           echo "\`\`\`" >> $GITHUB_ENV
-          find packages/ -mindepth 1 -maxdepth 2 -name package.json | xargs -I{} node -pe "require('./{}')['name']" | sed "s/^\(.*\)$/npm i \1@${TARGET_VERSION} --registry https:\/\/npm.preview.tezostaquito.io\//" >> $GITHUB_ENV
+          find packages/ -mindepth 1 -maxdepth 2 -name package.json | xargs -I{} node -pe "require('./{}')['name']" | sed "s/^\(.*\)$/npm i \1@${TARGET_VERSION} --registry https:\/\/npm.preview.taquito.io\//" >> $GITHUB_ENV
           echo "\`\`\`" >> $GITHUB_ENV
           echo 'EOF' >> $GITHUB_ENV
     - if: ${{ github.event_name == 'pull_request' }}

.github/workflows/deploy_website.yml

@@ -57,4 +57,4 @@ jobs:
       if: github.event_name == 'pull_request'
       with:
         header: netlify-preview
-        message: 'A new deploy preview is available on Netlify at https://${{ env.short_sha }}--tezostaquito.netlify.app'
+        message: 'A new deploy preview is available on Netlify at https://${{ env.short_sha }}--taquito.netlify.app'

README.md

@@ -31,7 +31,7 @@ Taquito provides convenient abstractions for a multitude of common operations, i
 
 ## Ok, I'm Ready!
 
-To get started with Taquito quickly, visit the [Taquito QuickStart](https://tezostaquito.io/docs/quick_start).
+To get started with Taquito quickly, visit the [Taquito QuickStart](https://taquito.io/docs/quick_start).
 
 If you prefer to start with a skeleton project, check out our [Taquito React Template](https://github.com/ecadlabs/taquito-react-template).
 
@@ -83,7 +83,7 @@ Taquito is organized as a [monorepo](https://en.wikipedia.org/wiki/Monorepo), an
 
 ## API Documentation
 
-TypeDoc API documentation for Taquito [is available here](https://tezostaquito.io/typedoc).
+TypeDoc API documentation for Taquito [is available here](https://taquito.io/typedoc).
 
 ## Versioning Strategy
 
@@ -222,7 +222,7 @@ Special thanks to these libraries, which have been excellent references for deve
 [0]: https://github.com/ecadlabs/tezos-indexer-api
 [2]: https://keybase.io/jevonearth
 [3]: https://keybase.io/simrob
-[4]: https://tezostaquito.io
+[4]: https://taquito.io
 [5]: https://docusaurus.io/
 [stackexchange]: https://tezos.stackexchange.com/questions/tagged/taquito
 [discord]: https://discord.com/channels/934567382700146739/939205889901092874

apps/taquito-test-dapp/src/tests.ts

@@ -575,7 +575,7 @@ export const init = (
       id: "send-tez",
       name: "Send tez",
       description: "This test sends 0.1 tez to Alice's address",
-      documentation: 'https://tezostaquito.io/docs/wallet_API#making-transfers',
+      documentation: 'https://taquito.io/docs/wallet_API#making-transfers',
       keyword: 'transfer',
       run: () => sendTez(Tezos),
       showExecutionTime: false,
@@ -586,7 +586,7 @@ export const init = (
       id: "contract-call-simple-type",
       name: "Contract call with int",
       description: "This test calls a contract entrypoint and passes an int",
-      documentation: 'https://tezostaquito.io/docs/smartcontracts',
+      documentation: 'https://taquito.io/docs/smartcontracts',
       keyword: 'methods',
       run: () => sendInt(contract),
       showExecutionTime: false,
@@ -598,7 +598,7 @@ export const init = (
       name: "Contract call with (pair nat string)",
       description:
         "This test calls a contract entrypoint and passes a pair holding a nat and a string",
-      documentation: 'https://tezostaquito.io/docs/smartcontracts/#choosing-between-the-methods-or-methodsobject-members-to-interact-with-smart-contracts',
+      documentation: 'https://taquito.io/docs/smartcontracts/#choosing-between-the-methods-or-methodsobject-members-to-interact-with-smart-contracts',
       keyword: 'methodsObject',
       run: () => sendComplexParam(contract),
       showExecutionTime: false,
@@ -610,7 +610,7 @@ export const init = (
       name: "Contract call that fails",
       description:
         'This test calls a contract entrypoint that fails with the message "Fail entrypoint"',
-      documentation: 'https://tezostaquito.io/docs/failwith_errors/',
+      documentation: 'https://taquito.io/docs/failwith_errors/',
       keyword: 'failwith',
       run: () => callFail(contract),
       showExecutionTime: false,
@@ -621,7 +621,7 @@ export const init = (
       id: "contract-call-fail-with-int",
       name: "Contract call that fails with int",
       description: "This test calls a contract entrypoint that fails with an int",
-      documentation: 'https://tezostaquito.io/docs/failwith_errors/',
+      documentation: 'https://taquito.io/docs/failwith_errors/',
       keyword: 'failwith',
       run: () => callFaiWithInt(contract),
       showExecutionTime: false,
@@ -632,7 +632,7 @@ export const init = (
       id: "contract-call-fail-with-pair",
       name: "Contract call that fails with (pair int string)",
       description: "This test calls a contract entrypoint that fails with a pair",
-      documentation: 'https://tezostaquito.io/docs/failwith_errors/',
+      documentation: 'https://taquito.io/docs/failwith_errors/',
       keyword: 'failwith',
       run: () => callFaiWithPair(contract),
       showExecutionTime: false,
@@ -643,7 +643,7 @@ export const init = (
       id: "originate-success",
       name: "Originate smart contract with success",
       description: "This test successfully originates a smart contract",
-      documentation: 'https://tezostaquito.io/docs/originate/#originate-the-contract-using-taquito',
+      documentation: 'https://taquito.io/docs/originate/#originate-the-contract-using-taquito',
       keyword: 'originate',
       run: () => originateSuccess(Tezos),
       showExecutionTime: false,
@@ -654,7 +654,7 @@ export const init = (
       id: "batch-api",
       name: "Use the Batch API with a wallet",
       description: "This test sends 0.3 tez to 3 different addresses",
-      documentation: 'https://tezostaquito.io/docs/batch_api/#--the-withtransfer-method',
+      documentation: 'https://taquito.io/docs/batch_api/#--the-withtransfer-method',
       keyword: 'withTransfer',
       run: () => batchApiTest(Tezos),
       showExecutionTime: false,
@@ -665,7 +665,7 @@ export const init = (
       id: "batch-api-contract-call",
       name: "Use the Batch API for contract calls",
       description: "This test calls the same entrypoint 3 times in 1 transaction",
-      documentation: 'https://tezostaquito.io/docs/batch_api/#--the-withcontractcall-method',
+      documentation: 'https://taquito.io/docs/batch_api/#--the-withcontractcall-method',
       keyword: 'withcontractcall',
       run: () =>
         batchApiContractCallsTest(
@@ -681,7 +681,7 @@ export const init = (
       id: "sign-payload",
       name: "Sign the provided payload",
       description: "This test signs the payload provided by the user",
-      documentation: 'https://tezostaquito.io/docs/signing/#generating-a-signature-with-beacon-sdk',
+      documentation: 'https://taquito.io/docs/signing/#generating-a-signature-with-beacon-sdk',
       keyword: 'requestSignPayload',
       run: input => signPayload(input.text, wallet),
       showExecutionTime: false,
@@ -694,7 +694,7 @@ export const init = (
       name: "Sign and send the signature to the contract",
       description:
         "This test signs the provided payload and sends it to the contract to check it",
-      documentation: 'https://tezostaquito.io/docs/signing/#sending-the-signature-to-a-smart-contract',
+      documentation: 'https://taquito.io/docs/signing/#sending-the-signature-to-a-smart-contract',
       keyword: 'check_signature',
       run: input => signPayloadAndSend(input.text, wallet, contract),
       showExecutionTime: false,
@@ -706,7 +706,7 @@ export const init = (
       id: "sign-failingNoop",
       name: "Sign the provided payload in a failing noop",
       description: "This test signs the payload provided by the user wrapped in a failing noop",
-      documentation: 'https://tezostaquito.io/docs/failing_noop',
+      documentation: 'https://taquito.io/docs/failing_noop',
       keyword: 'failingNoop',
       run: input => signFailingNoop(input.text, Tezos),
       showExecutionTime: false,
@@ -719,7 +719,7 @@ export const init = (
       name: "Verify a provided signature",
       description:
         "This test signs the provided payload and uses Taquito to verify the signature",
-      documentation: 'https://tezostaquito.io/docs/signing/#verifying-a-signature',
+      documentation: 'https://taquito.io/docs/signing/#verifying-a-signature',
       keyword: 'verifySignature',
       run: input => verifySignatureWithTaquito(input.text, wallet, contract),
       showExecutionTime: false,
@@ -732,7 +732,7 @@ export const init = (
       name: "Set the transaction limits",
       description:
         "This test allows you to set the fee, storage limit and gas limit manually",
-      documentation: 'https://tezostaquito.io/docs/transaction_limits/#setting-the-limits',
+      documentation: 'https://taquito.io/docs/transaction_limits/#setting-the-limits',
       keyword: 'transaction limits',
       run: input =>
         setTransactionLimits(
@@ -751,7 +751,7 @@ export const init = (
       name: "Subscribe to confirmations",
       description:
         "This test updates the underlying contract and subscribes to 3 confirmations",
-      documentation: 'https://tezostaquito.io/docs/confirmation_event_stream/#setting-up-the-observable',
+      documentation: 'https://taquito.io/docs/confirmation_event_stream/#setting-up-the-observable',
       keyword: 'confirmationObservable',
       run: () =>
         tryConfirmationObservable(contract as ContractAbstraction<Wallet>),
@@ -773,7 +773,7 @@ export const init = (
       id: "sapling-shielded",
       name: "Sapling shielded transaction",
       description: "This test prepares and sends a shielded transaction to a Sapling pool",
-      documentation: 'https://tezostaquito.io/docs/sapling/',
+      documentation: 'https://taquito.io/docs/sapling/',
       keyword: 'sapling',
       run: () => saplingShielded(contract as ContractAbstraction<Wallet>),
       showExecutionTime: false,

docs/ballot.md

@@ -16,7 +16,7 @@ const op = await Tezos.contract.ballot({
 
 await op.confirmation();
 ```
-- `proposal` is the proposal hash string that you (a delegate) would like to point your ballot towards. Information on the current proposal can be obtained by calling [this RPC endpoint](https://tezos.gitlab.io/alpha/rpc.html#get-block-id-votes-current-proposal). Alternatively, you could also get the proposal hash by using Taquito's RPC Client method `RpcClient.getCurrentProposal`. For more information on the `RpcClient` refer to [this document](https://tezostaquito.io/docs/rpc_package/)
+- `proposal` is the proposal hash string that you (a delegate) would like to point your ballot towards. Information on the current proposal can be obtained by calling [this RPC endpoint](https://tezos.gitlab.io/alpha/rpc.html#get-block-id-votes-current-proposal). Alternatively, you could also get the proposal hash by using Taquito's RPC Client method `RpcClient.getCurrentProposal`. For more information on the `RpcClient` refer to [this document](https://taquito.io/docs/rpc_package/)
 - `ballot` is your ballot vote (`yay`, `nay`, or `pass`)
 
 

docs/batch-api.md

@@ -152,4 +152,4 @@ In addition to that, only a single account can sign batched operations.
 ## References
 
 - [Integration tests](https://github.com/ecadlabs/taquito/blob/master/integration-tests/batch-api.spec.ts)
-- [Documentation](https://tezostaquito.io/typedoc/classes/_taquito_taquito.walletoperationbatch.html)
+- [Documentation](https://taquito.io/typedoc/classes/_taquito_taquito.walletoperationbatch.html)

docs/complex_parameters.md

@@ -43,7 +43,7 @@ storage (pair
           (map %validators nat address));
 ```
 
-In this example, we originate the contract with initial values in the storage. We use the `MichelsonMap` class' of Taquito to initialize [the maps and the bigMap](https://tezostaquito.io/docs/maps_bigmaps).
+In this example, we originate the contract with initial values in the storage. We use the `MichelsonMap` class' of Taquito to initialize [the maps and the bigMap](https://taquito.io/docs/maps_bigmaps).
 
 As described above, the `map %data` uses a value that we chose between different types. When using Taquito, we need to surround the chosen argument with curly braces. In the current example, we initialize the value in the `map %data` to the boolean true: `{ bool: true }`.
 

docs/confirmation_event_stream.md

@@ -4,7 +4,7 @@ id: confirmation_event_stream
 author: Claude Barde
 ---
 
-Every operation forged with the [Wallet API](https://tezostaquito.io/docs/wallet_API) has a `confirmationObservable` method that can be used to set a certain number of confirmations to wait for and to get an update every time a new confirmation is received.
+Every operation forged with the [Wallet API](https://taquito.io/docs/wallet_API) has a `confirmationObservable` method that can be used to set a certain number of confirmations to wait for and to get an update every time a new confirmation is received.
 
 For example, if you want to wait 10 confirmations before giving a final confirmation to your users, you can implement a counter that will be increased at each confirmation.
 
@@ -43,7 +43,7 @@ const entries = await new Promise((resolve, reject) => {
 First, we create a new promise to wrap the Observable.
 Then, we declare an array to save every confirmation returned by the Observable.
 Next, we set up the Observable. The operation we created earlier has a `confirmationObservable` method that takes as a parameter the number of confirmations you want to wait for and returns an object with a `subscribe` method to start waiting for confirmations. This method takes 3 arguments:
-- the function to run when a confirmation is received with a parameter holding [different properties](https://tezostaquito.io/typedoc/classes/_taquito_taquito.walletoperation.html#confirmationobservable), for example, details about the current block or the confirmation status
+- the function to run when a confirmation is received with a parameter holding [different properties](https://taquito.io/typedoc/classes/_taquito_taquito.walletoperation.html#confirmationobservable), for example, details about the current block or the confirmation status
 - the function to run if the promise is rejected
 - the function to run if the promise is resolved
 

docs/contract-test-collection.md

@@ -81,7 +81,7 @@ storage: 1;
 
 ## MichelsonMapContract
 
-The contract supports a [Michelson Tutorial](https://tezostaquito.io/docs/michelsonmap). It has a default endpoint that takes a pair of an address and an amount of tez.
+The contract supports a [Michelson Tutorial](https://taquito.io/docs/michelsonmap). It has a default endpoint that takes a pair of an address and an amount of tez.
 
 - [See the full tutorial](https://claudebarde.medium.com/?p=8d8be9930662)
 
@@ -760,7 +760,7 @@ const op = await tezos.contract.originate({
 
 # On Chain Views Contracts
 
-Views are meant to be called by a contract using the Michelson Instruction View followed by the view name and its result type. See [TaquitoDocs](https://tezostaquito.io/docs/on_chain_views) for more details.
+Views are meant to be called by a contract using the Michelson Instruction View followed by the view name and its result type. See [TaquitoDocs](https://taquito.io/docs/on_chain_views) for more details.
 
 ## ContractCallFib
 
@@ -1054,8 +1054,8 @@ const metadataJSON = {
   description: 'A metadata test',
   version: '0.1',
   license: 'MIT',
-  authors: ['Taquito <https://tezostaquito.io/>'],
-  homepage: 'https://tezostaquito.io/',
+  authors: ['Taquito <https://taquito.io/>'],
+  homepage: 'https://taquito.io/',
 };
 
 const metadataBigMap = new MichelsonMap();
@@ -1082,7 +1082,7 @@ description: A metadata test
 version: 0.1
 license: MIT
 authors: Taquito
-homepage: https://tezostaquito.io/
+homepage: https://taquito.io/
 ```
 
 </TabItem>
@@ -1377,7 +1377,7 @@ const contract = await Tezos.wallet.at('KT1B4WtE3MSEjGKnucRL5xhqnXCEX1QkLGPx');
 
 This line creates a contract abstraction with multiple methods named after the contract entrypoints. For example, if you have a `transfer` entrypoint in your contract, you will also have a `.transfer()` method in the `contract` object. Each method accepts parameters required by the contract entrypoint.
 
-For more details see [Taquito Wallet API doc](https://tezostaquito.io/docs/wallet_API)
+For more details see [Taquito Wallet API doc](https://taquito.io/docs/wallet_API)
 
 #### Entrypoints:
 

docs/contract_call_parameters.md

@@ -80,7 +80,7 @@ The `methodsObject` method always takes a single object to represent the pair to
 
 ## Map and big_map
 
-See the [documentation about creating and updating maps and big_maps](https://tezostaquito.io/docs/michelsonmap/)
+See the [documentation about creating and updating maps and big_maps](https://taquito.io/docs/michelsonmap/)
 
 ## Bypassing the Michelson Encoder
 Users can bypass the `michelson-encoder` and `ContractAbstraction` by directly passing JSON Michelson in a `transfer` call. This eliminates the need to fetch and create a JS/TS contract abstraction using `tezos.wallet.at` or `tezos.contract.at` and also removes the requirement to create a local contract instance for interaction. As a result, the conversion of entrypoint parameters to the JSON Michelson format using the michelson-encoder is no longer necessary as used in the ContractAbstraction entrypoints as listed prior for `methods` and `methodsObject`.

docs/dapp_prelaunch.md

@@ -5,7 +5,7 @@ author: Claude Barde
 
 #### You will find below a few considerations that you may take into account when building your Tezos dapp or before publishing it. These pointers help you prevent eventual bugs and improve your users' experience.
 
-- Is your dapp using a reliable and scalable RPC node? Running your own RPC node is often the best choice, especially if you anticipate significant traffic to your dapp. Using a paid hosted node is also a great idea, such as Nautilus from Cryptonomic, or TezTools. You can find [here](http://tezostaquito.io/docs/rpc_nodes#list-of-community-run-nodes) a list of public Tezos nodes.
+- Is your dapp using a reliable and scalable RPC node? Running your own RPC node is often the best choice, especially if you anticipate significant traffic to your dapp. Using a paid hosted node is also a great idea, such as Nautilus from Cryptonomic, or TezTools. You can find [here](https://taquito.io/docs/rpc_nodes#list-of-community-run-nodes) a list of public Tezos nodes.
 - Have you specified (hard-coded) fees and storage limits for smart contract calls from your dapp? Specifying these values has two advantages. Your dapp needs to make fewer calls to an RPC node (which makes your dapp faster!), and you can fine-tune your gas and storage values which, if set correctly, will reduce the likelihood of your users getting backtracked operations when using your dapp.
 - Have you tested your dapp with the popular wallets? Testing with Kukai and Temple wallets is essential. Testing with all the wallets is recommended!
 - Did you enable `Local Pack` in your dapp? Local Pack reduces the search time in bigmaps by 50%, and you can easily add it to your dapp by providing a new instance of the `MichelCodecPacker` class to the `setPackerProvider` method of the `TezosToolkit`.