From 8f893f18dac5f41767c734202f85dc4c1b2c59bb Mon Sep 17 00:00:00 2001 From: Vladislav ~ cryptomolot <88001005+cryptomolot@users.noreply.github.com> Date: Mon, 2 Dec 2024 16:30:40 +0300 Subject: [PATCH 1/5] Update bootstrap-fullnode.mdx It was the wrong link --- apps/nextra/pages/en/network/nodes/bootstrap-fullnode.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/nextra/pages/en/network/nodes/bootstrap-fullnode.mdx b/apps/nextra/pages/en/network/nodes/bootstrap-fullnode.mdx index a3643beab..b1fe6ca8b 100644 --- a/apps/nextra/pages/en/network/nodes/bootstrap-fullnode.mdx +++ b/apps/nextra/pages/en/network/nodes/bootstrap-fullnode.mdx @@ -6,5 +6,5 @@ title: "Bootstrap a Node" Bootstrapping a new node usually only depends on [state sync](configure/state-sync.mdx) in its fast sync mode, which synchronises to a recent state with help from its peers and start syncing recent ledger history from there. However, if longer ledger history is needed for any reason, we have these choices: -- ### [Bootstrap from a Snapshot](bootstrap-fullnode.mdx) +- ### [Bootstrap from a Snapshot](bootstrap-fullnode/bootstrap-fullnode.mdx) - ### [Bootstrap from a Backup](bootstrap-fullnode/aptos-db-restore.mdx) From 963fbf0586b0865e9c99d86f1a13806a75c300e2 Mon Sep 17 00:00:00 2001 From: Vladislav ~ cryptomolot <88001005+cryptomolot@users.noreply.github.com> Date: Thu, 16 Jan 2025 20:32:16 +0300 Subject: [PATCH 2/5] Update gas-txn-fee.mdx --- apps/nextra/pages/en/network/blockchain/gas-txn-fee.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/apps/nextra/pages/en/network/blockchain/gas-txn-fee.mdx b/apps/nextra/pages/en/network/blockchain/gas-txn-fee.mdx index 9505f1a4a..1211ee9c8 100755 --- a/apps/nextra/pages/en/network/blockchain/gas-txn-fee.mdx +++ b/apps/nextra/pages/en/network/blockchain/gas-txn-fee.mdx @@ -32,7 +32,7 @@ Transactions can range from simple and inexpensive to complicated based upon wha See [How Base Gas Works](base-gas.mdx) for a detailed description of gas fee types and available optimizations. -👉 A **unit of gas** is a dimensionless number or a unit that is not associated with any one item such as a coin, expressed as an integer. The total gas units consumed by your transaction depend on the complexity of your transaction. The **gas price**, on the other hand, is expressed in terms of Aptos blockchain’s native coin [APT](../glossary.mdx#APT) and it's subunit [Octas](../glossary.mdx#octa). Also see [Transactions and States](txns-states.mdx) for how a transaction submitted to the Aptos blockchain looks like. +👉 A **unit of gas** is a dimensionless number or a unit that is not associated with any one item such as a coin, expressed as an integer. The total gas units consumed by your transaction depend on the complexity of your transaction. The **gas price**, on the other hand, is expressed in terms of Aptos blockchain’s native coin [APT](../glossary.mdx#apt) and it's subunit [Octas](../glossary.mdx#octa). Also see [Transactions and States](txns-states.mdx) for how a transaction submitted to the Aptos blockchain looks like. ## The Fee Statement @@ -91,7 +91,7 @@ However, within a block, the order of transaction execution is determined by the When a transaction is submitted to the Aptos blockchain, the transaction must contain the following mandatory gas fields: - `max_gas_amount`: The maximum number of gas units that the transaction sender is willing to spend to execute the transaction. This determines the maximum computational and storage resources that can be consumed by the transaction. -- `gas_price`: The price per gas unit the transaction sender is willing to pay. It is expressed in[Octas](../glossary.mdx#Octa). +- `gas_price`: The price per gas unit the transaction sender is willing to pay. It is expressed in [Octas](../glossary.mdx#octa). During the transaction execution, the total gas amount, expressed as: @@ -129,7 +129,7 @@ There are some nuances with regard to price changing and legacy slots which didn It should also be noted that due to some backward compatibility reasons, the total storage fee of a transaction is currently presented to the client as part of the total `gas_used`. This means, this amount could vary based on the gas unit price even for the same transaction. -Here is an example. Suppose we have a transaction that costs `100` gas units in execution & IO, and `5000` [Octas](../glossary.mdx#Octa) in storage fees. The network will show that you have used +Here is an example. Suppose we have a transaction that costs `100` gas units in execution & IO, and `5000` [Octas](../glossary.mdx#octa) in storage fees. The network will show that you have used - `100 + 5000 / 100 = 150` gas units if the gas unit price is `100`, or - `100 + 5000 / 200 = 125` gas units if the unit price is `200`. From 5b244cd4d0a5f091dda80b505904f5194c468bd6 Mon Sep 17 00:00:00 2001 From: Vladislav ~ cryptomolot <88001005+cryptomolot@users.noreply.github.com> Date: Thu, 16 Jan 2025 20:34:25 +0300 Subject: [PATCH 3/5] Update base-gas.mdx --- apps/nextra/pages/en/network/blockchain/base-gas.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/nextra/pages/en/network/blockchain/base-gas.mdx b/apps/nextra/pages/en/network/blockchain/base-gas.mdx index ffa6c3b48..883d9cd83 100644 --- a/apps/nextra/pages/en/network/blockchain/base-gas.mdx +++ b/apps/nextra/pages/en/network/blockchain/base-gas.mdx @@ -297,7 +297,7 @@ In extreme cases it is possible for instruction gas to far outweigh storage gas, ### Payload gas -As of the time of this writing, [`transaction/mod.rs`](https://github.com/aptos-labs/aptos-core/blob/main/aptos-move/aptos-gas-schedule/src/gas_schedule/transaction.rs) defines the minimum amount of internal gas per transaction as 1,500,000 internal units (15,000 [octas](../glossary.mdx#Octa) at minimum), an amount that increases by 2,000 internal gas units (20 octas minimum) per byte for payloads larger than 600 bytes, with the maximum number of bytes permitted in a transaction set at 65536. +As of the time of this writing, [`transaction/mod.rs`](https://github.com/aptos-labs/aptos-core/blob/main/aptos-move/aptos-gas-schedule/src/gas_schedule/transaction.rs) defines the minimum amount of internal gas per transaction as 1,500,000 internal units (15,000 [octas](../glossary.mdx#octa) at minimum), an amount that increases by 2,000 internal gas units (20 octas minimum) per byte for payloads larger than 600 bytes, with the maximum number of bytes permitted in a transaction set at 65536. Hence, in practice, payload gas is unlikely to be a concern. [#4540]: https://github.com/aptos-labs/aptos-core/pull/4540/files From b5ce681c1aa2b70f91c0bbacee2944d3aff2acc3 Mon Sep 17 00:00:00 2001 From: Vladislav ~ cryptomolot <88001005+cryptomolot@users.noreply.github.com> Date: Thu, 16 Jan 2025 20:46:51 +0300 Subject: [PATCH 4/5] Update delegation-pool-operations.mdx --- .../validator-node/connect-nodes/delegation-pool-operations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/nextra/pages/en/network/nodes/validator-node/connect-nodes/delegation-pool-operations.mdx b/apps/nextra/pages/en/network/nodes/validator-node/connect-nodes/delegation-pool-operations.mdx index e4250748b..668b99344 100644 --- a/apps/nextra/pages/en/network/nodes/validator-node/connect-nodes/delegation-pool-operations.mdx +++ b/apps/nextra/pages/en/network/nodes/validator-node/connect-nodes/delegation-pool-operations.mdx @@ -136,7 +136,7 @@ Once the beneficiary address is set, the operator commission earned by the deleg ## Check delegation pool information -Until the delegation pool has received 1 million APT and the validator has been added to the set of active validators, there will be no rewards to track during each cycle. In order to obtain information about a delegation pool, use the Aptos [View function](../../../build/apis/fullnode-rest-api.mdx#reading-state-with-the-view-function) +Until the delegation pool has received 1 million APT and the validator has been added to the set of active validators, there will be no rewards to track during each cycle. In order to obtain information about a delegation pool, use the Aptos [View function](../../../../build/apis/fullnode-rest-api.mdx#reading-state-with-the-view-function) - `get_owned_pool_address(owner: address): address` - Returns the address of the delegation pool belonging to the owner, or produces an error if there is no delegation pool associated with the owner. From 02d8ae34b893672af298f885704a6fc5525e501b Mon Sep 17 00:00:00 2001 From: Vladislav ~ cryptomolot <88001005+cryptomolot@users.noreply.github.com> Date: Thu, 16 Jan 2025 20:52:24 +0300 Subject: [PATCH 5/5] Update node-liveness-criteria.mdx --- .../validator-node/verify-nodes/node-liveness-criteria.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/nextra/pages/en/network/nodes/validator-node/verify-nodes/node-liveness-criteria.mdx b/apps/nextra/pages/en/network/nodes/validator-node/verify-nodes/node-liveness-criteria.mdx index afecbdf99..8d961c06e 100644 --- a/apps/nextra/pages/en/network/nodes/validator-node/verify-nodes/node-liveness-criteria.mdx +++ b/apps/nextra/pages/en/network/nodes/validator-node/verify-nodes/node-liveness-criteria.mdx @@ -77,7 +77,7 @@ If you are a node operator, there are several tools available to you to verify t - **REST API:** You can also monitor your node's health by querying the REST API. For example, you can verify the current block height of your node by pinging the index page of your node's REST API. For more information, see the - [Aptos API Specification](../../fullnode-rest-api-reference.mdx). + [Aptos API Specification](../../../../build/apis/fullnode-rest-api-reference.mdx). - **Monitoring tools:** To improve observability, you can also install monitoring tools that scrape the local metrics endpoint: - For Kubernetes based deployments, install the monitoring Helm chart ([https://github.com/aptos-labs/aptos-core/tree/main/terraform/helm/monitoring](https://github.com/aptos-labs/aptos-core/tree/main/terraform/helm/monitoring)).