Brandon Kite

related: https://github.com/FuelLabs/fuel-core/issues/781

Looking more closely at how errors are handled in solidity, we may want to move this to an RFC discussion to support a less hardcoded approach here. In solidity, you...

Another idea I had was to charge less for overwriting existing storage slots than inserting into fresh ones. This could incentivize more state reuse and penalize state growth.

For refunds on state deletion, one idea I had for mitigating congestion was to scale the amount of any potential refund by a running average of recent I/O usage. For...

### 1. State of the art solutions for costing state storage and bandwidth on blockchains - Arbitrum 2d fees: https://medium.com/offchainlabs/understanding-arbitrum-2-dimensional-fees-fd1d582596c9 - Arbitrum is bound by the ethereum transaction format which...

After discussing with @xgreenx we came up with the following plan: 1. Add policies to transactions with all limits managed by policies (in preparation for multi-dimensional pricing in the future)...

Started a PR here to describe how policies could be implemented for the transaction format: https://github.com/FuelLabs/fuel-specs/pull/514

> The opcodes like CALL, TR, and TRO updates the SMT only in the contract context, so we can optimize the gas charging. But it will make our gas cost...

I know that the SDK is currently able to extract the contract_id out of the panic receipts during dry-run execution for estimating what the inputs should be. It will repeatedly...

related #1163