Hot answers tagged


Do bytes in the contract code cost the same as bytes in the contract storage? Yes. In both cases the cost is 0.25 tez per kilobyte. These are not fees that go to the baker including the operation, they are simply burnt.


Storage price is 0.25tez per kilobyte. Gas units are not directly charged, see


The main reason is the storage diff resulted from the transaction. Adding 380 items to a big map at once is very expensive. For your use case, storing the corner coordinates should be enough.


As Raphaël mentioned, the fees go to the baker that includes that non-applied (failed/backtracked/skipped) operation into the block it baked. Those operations are included in the blockchain! But they're not applied. It's normal that you do not want to pay for operations that fail. You should run simulations before you make an operation that might fail. You ...


Transaction fees are up to the client to offer. While the documentation will say that there is no gas cost (which is technically true), the default baker config comes with a setup that specifies a minimum fee per gas. Any operation that offers less than this is ignored. Operations that offer higher than this will be prioritised. Its up to each baker to ...


Don't worry, your funds are safe. You need to wait a bit and then try again with a higher fee or lower gas_limit. Why did that happen? You sent a transaction with large gas_limit: 50000 (despite a simple tz-to-tz transfer consumes about 1427 gas) and rather small, for such gas limit, fee:10000. So no one baker picked your transaction to include into a block ...

Only top voted, non community-wiki answers of a minimum length are eligible