Pierre Seznec

And also adding it somewhere in AS VM to be used in SmartContracts

everytime you need to call a smartContract from another. To compute the "coin" param

not really critical. Its just to avoid hardcoded value. And it will allow to write smartContract compatible for different network configuration. like today where buildnet and testnet 26 have different...

ok good to know but my main issue is not about refunding the user. its to be able to put a correct value in the "coin" parameter. when calling an...

but the point of the issue was only to avoid hardcoded values ^^ like here: https://github.com/massalabs/massa-standards/blob/b2e665cc62831de4dc5c0a33cb29e2b5e714b494/smart-contracts/assembly/contracts/website-deployer/websiteDeployer.ts#L20-L30

Yeah totally agree on that, and this idea of `estimate_call_coins` is nice! But to implement it, i still need to have the value of LEDGER_COST_PER_BYTE, which lead us back to...

The ```__*__``` syntax is also used in typescript (for the test folder ```__tests__``` ) , but it could be something else... I am using utility files common to a group...