feat: give pallpark gas estimates #422
Conversation
|
Your Render PR Server URL is https://docs-pr-422.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-bsfmseo951cet71p0hng. |
chadoh
force-pushed
the
gas
branch
4 times, most recently
from
0e04472 to
7533420
Compare
|
|
||
| Note that this covers the cost of uploading and writing bytes to storage, but does _not_ cover the cost of holding these bytes in storage. Long-term storage is compensated via [storage staking], a recoverable cost-per-byte amount that will also be deducted from your account during contract deployment. | ||
|
|
||
| The AssemblyScript contract in [this example Fungible Token](https://github.com/near-examples/FT/pull/42) compiles to just over 16kb (the Rust contract is much larger, but this [will be optimized](???)). Using the calculation above, we find that it requires **0.81 TGas** (and thus 0.081mN at minimum gas price) for the transaction fee to deploy the contract, while 1.5N will be locked up for storage staking. |
There was a problem hiding this comment.
@nearmax is there an existing issue for tracking the Rust contract size optimization?
There was a problem hiding this comment.
| | Setting an escrow for a fungible token | [44k] | 0.926 | 2.51 | [8] | 0.8 | ||
| | Checking a balance for a fungible token | 0 | 0 | 0 | 0 | 0 | ||
|
|
||
| <super>†</super> Function calls require spinning up a VM and loading all compiled Wasm bytes into memory, hence the increased cost over base operations; this is [being optimized](???). |
There was a problem hiding this comment.
@nearmax is there a an existing issue for tracking runtime-starting/Wasm-loading optimization?
There was a problem hiding this comment.
| And in [`near-api-js`](https://github.com/near/near-api-js), given a `contract` that you've instantiated with `new Contract`, you can attach an explicit gas amount when calling a change method on this contract with: | ||
|
|
||
| contract.myFunction({ arg1: 'val1' }, '300000000000000') | ||
| And in [`near-api-js`](https://github.com/near/near-api-js), you can also specify an explicit amount of gas units to attach when calling a change method; see [example here](https://github.com/near-examples/guest-book/blob/ceb2a39e53351b4ffc21d01987e2b0b21d633fa7/src/App.js#L29). |
There was a problem hiding this comment.
Curious why we want the user to click away for a line of code example?
There was a problem hiding this comment.
Because it's actually many lines of code, plus an entire src/config.js file. @janedegtiareva and I discussed and thought maybe it was better to link to an example rather than bulk this page with all that boilerplate.
Here's how we usually bootstrap a contract object so you can finally call your change method on it:
import getConfig from './config.js'
import { connect, Contract, keyStores, WalletConnection } as nearAPI from 'near-api-js'
const nearConfig = getConfig(process.env.NODE_ENV || 'testnet')
async function initContract() {
window.near = await connect({
deps: {
keyStore: new keyStores.BrowserLocalStorageKeyStore()
},
...nearConfig
})
window.walletConnection = new WalletConnection(near)
window.contract = await new Contract(walletConnection.account(), nearConfig.contractName, {
changeMethods: ['myFunction'],
})
}
window.nearInitPromise = initContract()
// then later, when some event happens
window.contract.addMessage({ arg1: "val1" }, '300000000000000')I think all of this boilerplate can and should go away, but until then, I don't see a great way to simplify it to a point that it fits into this document without being a bit distracting.
What do you think?
chadoh
force-pushed
the
gas
branch
2 times, most recently
from
c3106fc to
3cba71b
Compare
chadoh
requested review from
amgando,
bowenwang1996,
evgenykuzyakov,
ilblackdragon,
janedegtiareva,
mattlockyer,
mikedotexe,
MaksymZavershynskyi,
behaviary,
vgrichina and
willemneal
Co-authored-by: janedegtiareva <[email protected]>
Partially addresses near/devx#235
This is a largely a rewrite of our previous gas document
git is terrible at formatting such diffs; I recommend viewing this work primarily by looking at the preview: https://docs-pr-422.onrender.com/docs/concepts/gas (but please do come back and comment on specific lines in the "Files changed" tab here)