New answers tagged

0

From purely a cost perspective, all that matters is the number of slots (32 bytes) used. The storage costs on Ethereum are on a per-byte basis. Ethereum's Keccack-256, as the name implies, is 256 bits, or 32 bytes. The number of bytes for the RIPEMD hash depends on the algorithm chosen. If you use RIPEMD-128 or RIPEMD-160, you will use 16 bytes and 20 ...


0

Instead of answering your question directly, I will take a different approach, because it sounds to me that you've started a work which involves using a storage variable, and by the time you finished, it turned out that this storage variable wasn't needed to begin with. If the storage variable attains its original value at the end of the transaction, then ...


0

I don't think there is any special treatment. The EVM is "stupid" in that sense that it only executes an instruction at a time and count how much gas was used (or refunded). So it just executes the first instruction, counts how much gas is spend, starts the next instruction and so on... I really don't remember the exact gas costs but at least your idea is ...


Top 50 recent answers are included