From f67542cd03b3c4c5d9f627c72ba112ed72e8939c Mon Sep 17 00:00:00 2001 From: Tarun Bansal Date: Thu, 4 Jul 2024 12:20:19 +0530 Subject: [PATCH] fix: maximum gas limit per transaction is 0.4 TON for basechain (#298) --- pages/book/lifecycle.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/book/lifecycle.mdx b/pages/book/lifecycle.mdx index 6c8a5c60..71f65bed 100644 --- a/pages/book/lifecycle.mdx +++ b/pages/book/lifecycle.mdx @@ -6,7 +6,7 @@ There are several stages of message processing by a contract, there are more of This phase combines multiple low-level phases. -It starts by adding a **message value to the contract balance**. The value of an incoming message is the maximum price that a contract can pay for gas to process this message. The contract can overwrite this limit, but it is not recommended and is suitable only for advanced developers since it could lead to a contract being drained. 1 million of gas is the maximum amount that a contract can spend in a single contract which equals 1 TON (currently). If the message value is zero then execution is aborted. +It starts by adding a **message value to the contract balance**. The value of an incoming message is the maximum price that a contract can pay for gas to process this message. The contract can overwrite this limit, but it is not recommended and is suitable only for advanced developers since it could lead to a contract being drained. 1 million of gas is the maximum amount that a contract can spend in a single contract which equals 0.4 TON for basechain (currently). If the message value is zero then execution is aborted. Then some (usually small) amount of nanotons gets subtracted from the contract balance for storage. This means that you can't perfectly predict balance changes and have to adjust your code to this instability.