address_metadata
Schema: public
Description
The address_metadata table holds additional information about the contracts that we’re ingesting. This includes various bits of metadata like a friendly alias for the contract, the number of decimals a contract uses, the company a contract is associated with, etc.
Columns
| Column Name | Data Type | Description |
|---|---|---|
| account | text | The wallet or contract address associated with the metadata. |
| alias | text | A human readable name for this address. |
| context | jsonb | Custom metadata per address. See this page for more details |
| created_at | timestamptz | The timestamp when address metadata was originally created |
| updated_at | timestamptz | The timestamp when the address metadata was last updated. |
| deleted_at | timestamptz | The timestamp when the address metadata was deleted. |
The account field
The account field often maps to the contract in tables like contract_calls, contract_logs, etc. and can be used in joins to retrieve contract information that is useful for calculations. E.g. underlying_token_decimals is often used to convert a raw value to it's contract-specific decimal value.
Similarly, the account field can be joined to the sender or recipient fields in the transactions table to
include additional address metadata with a transaction.