Merge branch 'master' into add_near_intents_tutorial

blog/2024-04-24.md

@@ -15,7 +15,7 @@ hide_table_of_contents: true
 ## Organic growth
 Our documentation is the result of multiple people collaborating across the span of four very active years, and it has seen a lot of changes: [2942 commits and counting](https://github.com/near/docs/commits/master/).
 
-In the beginning, our docs only needed to explain how to create [smart contracts](/build/smart-contracts/what-is), and how to [interact with them through a frontend](/build/web3-apps/quickstart). Fast forward to today, and we have more than 200 pages of documentation, covering topics such as [chain abstraction](/build/chain-abstraction/what-is), [data infrastructure](/build/data-infrastructure/what-is), and [primitives such as NFT, FT](/build/primitives/what-is).
+In the beginning, our docs only needed to explain how to create [smart contracts](/build/smart-contracts/what-is), and how to [interact with them through a frontend](/build/web3-apps/quickstart). Fast forward to today, and we have more than 200 pages of documentation, covering topics such as [chain abstraction](/chain-abstraction/what-is), [data infrastructure](/build/data-infrastructure/what-is), and [primitives such as NFT, FT](/build/primitives/what-is).
 
 The best thing is that new features are released every single month. However, all progress comes at a cost, and as our ecosystem grew, so did the disorganization of our documentation.
 

blog/2024-05-15.md

@@ -24,7 +24,7 @@ As an added bonus, trades are atomic across chains, settlement takes just 2 seco
 :::tip Keep in mind
 
  There are transactions happening on different blockchains.
- The difference is that a [Multi-Party Computation service](/concepts/abstraction/chain-signatures#multi-party-computation-service) (MPC) signs a transaction for you, and that transaction is then broadcast to another blockchain RPC node or API.
+ The difference is that a [Multi-Party Computation service](/chain-abstraction/chain-signatures#multi-party-computation-service) (MPC) signs a transaction for you, and that transaction is then broadcast to another blockchain RPC node or API.
 
 :::
 

blog/2024-05-30.md

@@ -23,7 +23,7 @@ There is also a new documentation page on [Yield and Resume](/build/smart-contra
 ## The problem of waiting
 Currently, smart contracts have no way to wait for an external event to happen. This can be a problem when the contract relies on an external service to provide a result.
 
-We encountered this issue while implementing [Chain Signatures](/concepts/abstraction/chain-signatures), which work by requiring an external service to provide a signature.
+We encountered this issue while implementing [Chain Signatures](/chain-abstraction/chain-signatures), which work by requiring an external service to provide a signature.
 
 Until now, the only workaround has been to make the contract call itself in a loop, checking on each iteration if the result is ready. Each call delays the result by one block (~1 second), allowing the contract to wait almost a minute before running out of gas.
 

blog/2024-08-13.md

@@ -33,7 +33,7 @@ The Infrastructure Committee feels that Pagoda's fully-subsidized near.org RPC s
 
 ### Chain Abstraction Services
 
-[Chain Signatures](https://docs.near.org/concepts/abstraction/chain-signatures), Multichain Gas Relayer, and [FastAuth](https://docs.near.org/build/chain-abstraction/fastauth-sdk) will continue to be developed by Pagoda, then will be taken over by the new Chain Abstraction / Multichain spinout from Pagoda and Proximity. More information will be shared in September or October 2024.
+[Chain Signatures](https://docs.near.org/chain-abstraction/chain-signatures), Multichain Gas Relayer, and [FastAuth](https://docs.near.org/chain-abstraction/fastauth-sdk) will continue to be developed by Pagoda, then will be taken over by the new Chain Abstraction / Multichain spinout from Pagoda and Proximity. More information will be shared in September or October 2024.
 
 ### Pagoda Operations & Ecosystem Services
 

blog/2025-01-01.md

@@ -39,7 +39,7 @@ To keep the sidebar clean, we added a `What is...` page for each major topic, wh
 For example, we now have the following pages:
 
 - [What is NEAR Protocol?](/concepts/basics/protocol)
-- [What is Chain Abstraction?](/build/chain-abstraction/what-is)
+- [What is Chain Abstraction?](/chain-abstraction/what-is)
 - [What is a Smart Contract?](/build/smart-contracts/what-is)
 
 ## Code Explainer
@@ -68,7 +68,7 @@ Every page is full of snippets that explain how to leverage each primitive from
 
 ### Chain Abstraction
 
-We also added a section about [Chain Abstraction](/build/chain-abstraction/what-is), which explains how NEAR accounts can be used to control accounts on other chains.
+We also added a section about [Chain Abstraction](/chain-abstraction/what-is), which explains how NEAR accounts can be used to control accounts on other chains.
 
 ![alt text](/docs/blog/2024-review/2024-blog-4.jpg)
 _Did you know you can control Ethereum and Bitcoin accounts from NEAR?_

docs/1.concepts/basics/protocol.md

@@ -38,7 +38,7 @@ NEAR is a technical marvel, offering built-in features such as named accounts an
 3. Transactions are **fast** _(~1.3s transactions)_ and **cheap** _(< 1¢ in fees)_
 4. You don't need to buy crypto thanks to **built-in account abstraction**
 5. [Access Keys](../protocol/access-keys.md) make it safe and easy to use
-6. Control accounts on **other chains** thanks to [chain signatures](../abstraction/chain-signatures.md)
+6. Control accounts on **other chains** thanks to [chain signatures](../../chain-abstraction/chain-signatures.md)
 
 ### 🛡️ Battle-Tested
 

docs/2.build/2.smart-contracts/release/deploy.md

@@ -118,7 +118,7 @@ Considering this, we advise to name methods using `snake_case` in all SDKs as th
 ---
 
 ## Initializing the Contract
-If your contract has an [initialization method](/build/smart-contracts/anatomy/storage#initializing-the-state) you can call it to
+If your contract has an [initialization method](../anatomy/storage.md) you can call it to
 initialize the state. This is not necessary if your contract implements `default` values for the state.
 
 <Tabs groupId="cli-tabs">

docs/2.build/2.smart-contracts/release/upgrade.md

@@ -11,7 +11,7 @@ allowing the code to be changed.
 
 Contract's can be updated in two ways:
 
-1. **Through tools** such as [NEAR CLI](../../../4.tools/cli.md) or the 
+1. **Through tools** such as [NEAR CLI](../../../4.tools/cli.md) or the
    [NEAR API](../../../4.tools/near-api.md) (if you hold
    the account's
    [full access key](../../../1.concepts/protocol/access-keys.md)).
@@ -244,7 +244,7 @@ state, removes the `payments` vector and adds the information to the
 </CodeTabs>
 
 Notice that `migrate` is actually an
-[initialization method](/build/smart-contracts/anatomy/storage#initializing-the-state)
+[initialization method](../anatomy/storage.md)
 that **ignores** the existing state (`[#init(ignore_state)]`), thus being able
 to execute and rewrite the state.