Arbitrum One
¿Listo para usar esto en producción?
El plan gratuito cubre proyectos personales. El pago por uso escala sin necesidad de tarjeta.
Arbitrum One
El plan gratuito cubre proyectos personales. El pago por uso escala sin necesidad de tarjeta.
web3_sha3 computes the Keccak-256 hash of the hex-encoded data you pass in and returns it as a 0x-prefixed 32-byte value. Despite the sha3 in its name, it is the original Keccak-256 used throughout Ethereum — not the later NIST SHA3-256 standard, which produces different output for the same input. Arbitrum One (chain ID 42161) is EVM-equivalent — an Optimistic Rollup that settles to Ethereum and pays gas in ETH — so it hashes exactly as L1 does, and the result from https://arbitrum.therpc.io/YOUR_API_KEY matches what your contracts and tooling compute locally. This is a pure utility call: it touches no chain state and takes a single hex-string parameter.
Transfer(address,address,uint256) — to build topics filters for eth_getLogs against Arbitrum One contracts like Uniswap or Aave.| # | Nombre | Tipo | Requerido | Descripción |
|---|---|---|---|---|
| 1 | data | string | Sí | Arbitrary data to hash, provided as a 0x-prefixed hex string. Empty input (`"0x"`) is valid. |
| Tipo | Descripción |
|---|---|
| string | 0x-prefixed 32-byte (64-character) Keccak-256 hash of the input. |
Try it live in the Arbitrum One playground.
| Código | Mensaje | Causa |
|---|---|---|
-32602 | invalid argument | Input is not a valid 0x-prefixed hex string. |
Transfer(address,address,uint256), encode it to hex first — passing the literal text yields the hash of the wrong bytes.sha3 function may return a different digest unless it specifically implements the Ethereum Keccak variant, so confirm your local hashing matches before relying on it interchangeably with this method.Parámetros
0x-prefixed hex string