move concepts

Author: bucanero

docs/2.build/2.smart-contracts/anatomy/actions.md

@@ -486,7 +486,7 @@ There are two scenarios in which you can use the `delete_account` action:
 </Tabs>
 
 :::warning Token Loss
-If the beneficiary account does not exist the funds will be [**dispersed among validators**](../../../1.concepts/basics/token-loss.md).
+If the beneficiary account does not exist the funds will be [**dispersed among validators**](../../../protocol/network/token-loss.md).
 :::
 
 :::warning Token Loss

docs/2.build/2.smart-contracts/anatomy/environment.md

@@ -130,7 +130,7 @@ The `timestamp` attribute represents the approximated **UNIX timestamp** in **na
 
 ### Current Epoch
 
-The NEAR blockchain groups blocks in [Epochs](../../../1.concepts/basics/epoch.md). The `current_epoch` attribute measures how many epochs have passed so far. It is very useful to coordinate with other contracts that measure time in epochs, such as the [validators](../../../1.concepts/basics/validators.md).
+The NEAR blockchain groups blocks in [Epochs](../../../protocol/network/epoch.md). The `current_epoch` attribute measures how many epochs have passed so far. It is very useful to coordinate with other contracts that measure time in epochs, such as the [validators](../../../protocol/network/validators.md).
 
 ### Block Index
 

docs/2.build/2.smart-contracts/testing/integration-test.md

@@ -422,7 +422,7 @@ This approach is more complex to do and also cannot be performed without restart
 
 ## Using Testnet
 
-NEAR Workspaces is set up so that you can write tests once and run them against a local Sandbox node (the default behavior) or against [NEAR TestNet](../../../1.concepts/basics/networks.md). Some reasons this might be helpful:
+NEAR Workspaces is set up so that you can write tests once and run them against a local Sandbox node (the default behavior) or against [NEAR TestNet](../../../protocol/network/networks.md). Some reasons this might be helpful:
 
 * Gives higher confidence that your contracts work as expected
 * You can test against deployed testnet contracts

docs/3.tutorials/crosswords/01-basics/02-add-functions-call.md

@@ -33,7 +33,7 @@ Before moving on, let's talk about these changes and how to think about them, be
 const PUZZLE_NUMBER: u8 = 1;
 ```
 
-This is an in-memory value, meaning that when the smart contract is spun up and executed in the virtual machine, the value `1` is contained in the contract code. This differs from the next change, where a field is added to the struct containing the `#[near]` macro. The field `crossword_solution` has the type of `String` and, like any other fields added to this struct, the value will live in **persistent storage**. With NEAR, storage is "paid for" via the native NEAR token (Ⓝ). It is not "state rent" but storage staking, paid once, and returned when storage is deleted. This helps incentivize users to keep their state clean, allowing for a more healthy chain. Read more about [storage staking here](https://docs.near.org/concepts/storage/storage-staking).
+This is an in-memory value, meaning that when the smart contract is spun up and executed in the virtual machine, the value `1` is contained in the contract code. This differs from the next change, where a field is added to the struct containing the `#[near]` macro. The field `crossword_solution` has the type of `String` and, like any other fields added to this struct, the value will live in **persistent storage**. With NEAR, storage is "paid for" via the native NEAR token (Ⓝ). It is not "state rent" but storage staking, paid once, and returned when storage is deleted. This helps incentivize users to keep their state clean, allowing for a more healthy chain. Read more about [storage staking here](https://docs.near.org/protocol/storage/storage-staking).
 
 Let's now look at the three new functions:
 

docs/3.tutorials/crosswords/02-beginner/00-overview.md

@@ -36,7 +36,7 @@ In this chapter we'll:
 As we implement the list above, we'll learn key concepts about NEAR:
 
 - [Actions](https://nomicon.io/RuntimeSpec/Actions.html)
-- Full and function-call [access keys](https://docs.near.org/concepts/basics/account#access-keys)
+- Full and function-call [access keys](https://docs.near.org/protocol/network/account#access-keys)
 - NEAR's specialized [Collections](../../../2.build/2.smart-contracts/anatomy/collections.md) that are generally preferable to, say, Rust's standard HashMap 
 - The flow of logging in to a decentralized app (dApp)
 - more…

docs/3.tutorials/nfts/minting-nfts.md

@@ -43,7 +43,7 @@ The [InterPlanetary File System](https://ipfs.io/) (IPFS) is a protocol and peer
 
 ### Uploading the image {#uploading-the-image}
 
-To upload the NFT image, you should use a [decentralized storage](/concepts/storage/storage-solutions) provider such as IPFS.
+To upload the NFT image, you should use a [decentralized storage](/protocol/storage/storage-solutions) provider such as IPFS.
 
 :::note
 This example uses IPFS, but you could use a different solution like Filecoin, Arweave, or a regular centralized Web2 hosting.

docs/5.api/rpc/setup.md

@@ -23,7 +23,7 @@ In order to use the RPC API you will need to setup the correct RPC endpoints.
 <hr className="subsection" />
 
 ## Querying Historical Data
-Querying historical data (older than 5 [epochs](../../1.concepts/basics/epoch.md) or ~2.5 days), you may get responses that the data is not available anymore. In that case, archival RPC nodes will come to your rescue:
+Querying historical data (older than 5 [epochs](../../protocol/network/epoch.md) or ~2.5 days), you may get responses that the data is not available anymore. In that case, archival RPC nodes will come to your rescue:
 
 - mainnet `https://archival-rpc.mainnet.near.org`
 - testnet `https://archival-rpc.testnet.near.org`

docs/6.integrations/tokens.md

@@ -150,7 +150,7 @@ Decoded result in this case is:
 
 To follow this guide, please check the [step by step instructions](/integrations/create-transactions#low-level----create-a-transaction) on how to create a transaction first.
 
-In order to send a fungible token to an account, the receiver must have a storage deposit. This is because each smart contract on NEAR must account for storage used, and each account on a fungible token contract is a key-value pair, taking up a small amount of storage. For more information, please see [how storage works in NEAR](/concepts/storage/storage-staking). To check if account has deposited the storage for this FT do the following:
+In order to send a fungible token to an account, the receiver must have a storage deposit. This is because each smart contract on NEAR must account for storage used, and each account on a fungible token contract is a key-value pair, taking up a small amount of storage. For more information, please see [how storage works in NEAR](/protocol/storage/storage-staking). To check if account has deposited the storage for this FT do the following:
 
 Get storage balance of the account. `storage_balance_of` function returns the amount of deposited storage or `null` if there is no deposit.
   - using NEAR CLI:

docs/data-infrastructure/lake-framework/running-near-lake/run-near-lake.md

@@ -132,7 +132,7 @@ $ aws s3 --no-sign-request cp --no-sign-request --recursive s3://near-protocol-p
 
 It's not necessary but in order to index everything in the network it is better to do it from the genesis.
 `nearcore` node is running in non-archival mode by default. That means that the node keeps data only
-for [5 last epochs](https://docs.near.org/concepts/basics/epoch). In order to index data from the genesis
+for [5 last epochs](https://docs.near.org/protocol/network/epoch). In order to index data from the genesis
 you need to turn the node in archival mode.
 
 To do it you need to update `config.json` located in `--home-dir` (by default it is `~/.near`).

docs/1.concepts/basics/epoch.md docs/protocol/network/epoch.md

@@ -6,9 +6,9 @@ sidebar_label: Networks
 
 NEAR Protocol operates on several networks each operating with their own independent validators and unique state. These networks are as follows:
 
-- [`mainnet`](/concepts/basics/networks#mainnet)
-- [`testnet`](/concepts/basics/networks#testnet)
-- [`localnet`](/concepts/basics/networks#localnet)
+- [`mainnet`](/protocol/network/networks#mainnet)
+- [`testnet`](/protocol/network/networks#testnet)
+- [`localnet`](/protocol/network/networks#localnet)
 
 ## Mainnet {#mainnet}
 

docs/1.concepts/basics/networks.md docs/protocol/network/networks.md

@@ -20,7 +20,7 @@ For storing data on-chain it's important to keep in mind the following:
 - There is a 4 MB limit on how much you can upload at once
 
 
-For example, if you want to store an NFT purely on-chain (rather than using IPFS or some other decentralized storage solution as mentioned below) you'll have almost an unlimited amount of storage but will have to pay 1 $NEAR per 100 KB of storage used (see [Storage Staking](https://docs.near.org/concepts/storage/storage-staking))
+For example, if you want to store an NFT purely on-chain (rather than using IPFS or some other decentralized storage solution as mentioned below) you'll have almost an unlimited amount of storage but will have to pay 1 $NEAR per 100 KB of storage used (see [Storage Staking](https://docs.near.org/protocol/storage/storage-staking))
 
 Users will be limited to 4MB per contract call upload due to `MAX_GAS` constraints. The maximum amount of gas one can attach to a given `functionCall` is 300TGas.
 

docs/1.concepts/basics/runtime.md docs/protocol/network/runtime.md

@@ -30,7 +30,7 @@ Take care, then, when designing your smart contracts to ensure that such attacks
 
 ## btw, you can remove data to unstake some tokens
 
-People familiar with the "immutable data" narrative about blockchains find this surprising. While it's true that an _indexing node_ will keep all data forever, _validating nodes_ (that is, the nodes run by most validators in the network) do not. Smart contracts can provide ways to delete data, and this data will be purged from most nodes in the network within a few [epochs](../basics/epoch.md).
+People familiar with the "immutable data" narrative about blockchains find this surprising. While it's true that an _indexing node_ will keep all data forever, _validating nodes_ (that is, the nodes run by most validators in the network) do not. Smart contracts can provide ways to delete data, and this data will be purged from most nodes in the network within a few [epochs](../network/epoch.md).
 
 Note that a call to your smart contract to remove data has an associated gas fee. Given NEAR's gas limit, this creates an upper limit on how much data can be deleted in a single transaction.
 

docs/1.concepts/basics/staking.md docs/protocol/network/staking.md

@@ -15,7 +15,7 @@ Imagine a place where you can build Web3 apps with the simplicity of Web2. Imagi
           title="NEAR Protocol"
           text="Learn what NEAR is and how it works"
           links={{
-            "What is NEAR?": "/concepts/basics/protocol",
+            "What is NEAR?": "/protocol/network/protocol",
             "Named Accounts": "/protocol/account-id",
             "Access Keys": "/protocol/access-keys",
             "Transactions": "/protocol/transactions"

docs/1.concepts/basics/token-loss.md docs/protocol/network/token-loss.md

@@ -38,20 +38,23 @@ const sidebar = {
           ]
         },
         {
-          "Tokens": ["concepts/basics/tokens", "concepts/basics/token-loss"]
+          "Tokens": [
+             "protocol/network/tokens",
+             "protocol/network/token-loss"
+          ]
         },
         {
           "Storage": [
-            "concepts/storage/storage-staking",
-            "concepts/storage/storage-solutions"
+            "protocol/storage/storage-staking",
+            "protocol/storage/storage-solutions"
           ]
         },
         {
           "Network": [
-            "concepts/basics/validators",
-            "concepts/basics/networks",
-            "concepts/basics/epoch",
-            "concepts/basics/runtime",
+            "protocol/network/validators",
+            "protocol/network/networks",
+            "protocol/network/epoch",
+            "protocol/network/runtime",
           ]
         },
       ]
@@ -259,7 +262,7 @@ const sidebar = {
             },
           ]
         },
-        "concepts/basics/staking",
+        "protocol/network/staking",
         "build/primitives/linkdrop",
         "build/primitives/oracles",
         "build/primitives/dao",