validator_id and an associated auth_address.
Table Schema
| Column Name | Data Type | Description |
|---|---|---|
| validator_id | VARCHAR | Unique identifier for the validator |
| auth_address | VARCHAR | The validator’s authorization/operator address |
| commission_percentage | DECIMAL | Initial commission rate as decimal (e.g., 0.10 = 10%) |
| contract_address | VARCHAR | Address of the staking precompile contract |
| transaction_hash | VARCHAR | Hash of the transaction that created the validator |
| transaction_index | INTEGER | Index of the transaction in the block |
| transaction_from_address | VARCHAR | Address that initiated the transaction |
| transaction_to_address | VARCHAR | Target address of the transaction |
| log_index | INTEGER | Index of the event log in the transaction |
| block_timestamp | TIMESTAMP | Timestamp of the block containing the validator creation |
| block_number | INTEGER | Block number containing the validator creation |
| block_hash | VARCHAR | Hash of the block containing the validator creation |
| unique_id | VARCHAR | Unique identifier for the validator creation event |
Understanding Validator Creation
When a new validator is created on Monad, it receives:- Validator ID: A unique integer identifier assigned sequentially by the network
- Auth Address: The authorization address that has control over the validator’s stake and operations
- Initial Commission: The percentage of block rewards the validator will retain before distributing to delegators