Update language to use compute units instead of gas for Cadence txs #1571
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
...opment-tutorials/cadence/cadence-advantages/native-data-availibility-with-cadence-scripts.md
Outdated
Show resolved
Hide resolved
docs/blockchain-development-tutorials/cadence/getting-started/production-deployment.md
Outdated
Show resolved
Hide resolved
docs/blockchain-development-tutorials/cross-vm-apps/introduction.md
Outdated
Show resolved
Hide resolved
| ### Payer | ||
|
|
||
| A payer is the account that pays the fees for the transaction. A transaction must specify exactly one payer. The payer is only responsible for paying the network and gas fees; the transaction is not authorized to access resources or code stored in the payer account. | ||
| A payer is the account that pays the fees for the transaction. A transaction must specify exactly one payer. The payer is only responsible for paying the network and compute unit fees; the transaction is not authorized to access resources or code stored in the payer account. |
Contributor
There was a problem hiding this comment.
what is the network fees?
Contributor
Author
There was a problem hiding this comment.
It would really be a synonym of compute unit fees or gas fees. Sort of a catch all for anything else - inclusion fees, etc.
We can delete it for precision, or keep it since it's an introductory article and devs from other ecosystems will interpret it as "whatever you have to pay to make the transaction happen"
| A transaction is only valid if its declared sequence number matches the current on-chain sequence number for that key. The sequence number increments by one after the transaction is executed. | ||
|
|
||
| **Payer** is the account that pays the fees for the transaction. A transaction must specify exactly one payer. The payer is only responsible for paying the network and gas fees; the transaction is not authorized to access resources or code stored in the payer account. | ||
| **Payer** is the account that pays the fees for the transaction. A transaction must specify exactly one payer. The payer is only responsible for paying the network and compute unit (gas) fees; the transaction is not authorized to access resources or code stored in the payer account. |
Contributor
There was a problem hiding this comment.
do we want the (gas) here? It can confuse the user with EVM Gas.
Also, what is the network fees?
Contributor
Author
There was a problem hiding this comment.
I left (or sometimes added) the gas in parens for articles that I thought an EVM developer converting to Cadence might see as the first, or an early exposure to compute units.
| A transaction expires after `600` blocks are committed on top of the reference block, which takes about 10 minutes at average Mainnet block rates. | ||
| Keep in mind that Flow is **very** efficient, so transaction fees are generally low. A limit resulting in max charges of `.001` Flow is sufficient to cover even complex transactions. | ||
|
|
||
| - Flow token transfer: 19 CU. |
Contributor
There was a problem hiding this comment.
ty for updating these to the latest numbers!
…production-deployment.md Co-authored-by: Vishal <1117327+vishalchangrani@users.noreply.github.com>
…es/native-data-availibility-with-cadence-scripts.md Co-authored-by: Vishal <1117327+vishalchangrani@users.noreply.github.com>
…on.md Co-authored-by: Vishal <1117327+vishalchangrani@users.noreply.github.com>
Co-authored-by: Vishal <1117327+vishalchangrani@users.noreply.github.com>
Co-authored-by: Vishal <1117327+vishalchangrani@users.noreply.github.com>
Co-authored-by: Vishal <1117327+vishalchangrani@users.noreply.github.com>
Co-authored-by: Vishal <1117327+vishalchangrani@users.noreply.github.com>
Co-authored-by: Vishal <1117327+vishalchangrani@users.noreply.github.com>
Co-authored-by: Vishal <1117327+vishalchangrani@users.noreply.github.com>
Co-authored-by: Vishal <1117327+vishalchangrani@users.noreply.github.com>
vishalchangrani
approved these changes
Nov 19, 2025
briandoyle81
deleted the
brian-doyle/update-cadence-computation-language
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.