Open Ben-Rey opened 1 year ago
Here are succinct responses that should be added to the docs.
When calling create_sc
, two charges happen:
create_sc
is charged with 0.001
coins for the creation of a new ledger entrycreate_sc
is charged with 0.0001
coins per byte of bytecode stored on the newly created SCSpace is always available because occupying space requires locking coins. The available space is therefore naturally limited by the total supply of coins in circulation, but as long as you have coins you can always store.
Storage is paid by the address at the top of the call stack. When storage bytes are freed, the unlocked coins are given to the address on top of the call stack.
Very clear thanks !
It's a good opportunity to explain in which context accounts have write access.
Not directly related but in the previous documentation there was this document that was created which documented the stack https://github.com/massalabs/massa-docs/blob/main/web3-dev/smart-contracts/address-stack.rst.
There seems to be confusion regarding the use of coins in smart contracts, whether it's for a function call or during deployment.
Some example of questions:
@damip Please challenge the questions if they appear unclear or illogical.