Initial implementation of a caniuse.com-like view to compare support of a given feature (e.g. opcode, transaction type, etc.) across chains. So far it only supports opcodes.
Supporting other things gets tricky, for example we have to be able to recognize that arbitrum's WETH and optimism's WETH are both WETH predeploys, so all chains have WETH, even though the names or addresses don't match. Maybe a good way to do this is add a normalizedName field to each type that we use to identify the same concept across chains
Initial implementation of a caniuse.com-like view to compare support of a given feature (e.g. opcode, transaction type, etc.) across chains. So far it only supports opcodes.
Supporting other things gets tricky, for example we have to be able to recognize that arbitrum's WETH and optimism's WETH are both WETH predeploys, so all chains have WETH, even though the names or addresses don't match. Maybe a good way to do this is add a
normalizedName
field to each type that we use to identify the same concept across chainsUsage: