Ethereum

Solidity devs, need your help confirming something: 

Let’s say I have 100 ERC721 tokens that have a custom uint8 state, and I want to update that state by -1 for all tokens at once. Would you:

A. Loop over in the contract with high gas estimation 

B. Loop on the client sending lots of smaller transactions

DX Engineer | Head of Developer Relations at /pinata | Tinkering with everything | stevedylan.dev/links

Protocol Engineer @ OP Labs | https://amadimichael.github.io | Prev: @rareskills

Interesting, what about scaling? Like if I wanted to keep minting NFTs and eventually get to something crazy like 10k? Not saying that’s the plan but trying to think ahead

Transaction has a 21k gas overhead so doing it in the contract would be cheaper since you just pay the 21k gas overhead once

For only 100? One transaction 
General case with n? In batches 
Best to avoid this situation where possible. State writes are by far the most expensive operation in the evm

Interesting approach! The problem its dynamic, like health for a game. It fluctuates based on certain actions and events. In one particular event we want to enable a "catastrophe" where it affects all the NFTs

I think I would try to avoid that. How about storing a single global diff value and subtracting it on read in a getter function?