Validator Activity
Tracks activities related to validators, identified by NodeIDs or SubnetIDs.
- Sub-events:
validator_stake:Triggered when a validator registers on a specified subnet or via a specificNodeID.delegator_stake:Triggered when a delegator’s staking transaction is confirmed, initiating their staking period with a validator.reward_distribution:Triggered when a validator or delegator receives a reward, monitored byNodeIDorSubnetID.l1_validator_balance_increased:Triggered when an L1 validator’s balance increases via a specific transaction.l1_validator_disabled:Triggered when an L1 validator is marked inactive (e.g., due to insufficient balance or a disable transaction).l1_validator_removed:Triggered when an L1 validator is removed from the validator set.l1_validator_threshold_reached:Triggered when an L1 validator’s balance falls below a specified threshold.
Understanding balance types
On the P and X chains, addresses can hold assets in various states, referred to as balance types. These are essential for configuring events like BALANCE_THRESHOLD_PLATFORM. Below is a summary:
unlockedUnstaked:Assets neither locked nor staked; immediately available for transactions.unlockedStaked:Assets previously staked, now unlocked and available.lockedPlatform:Unstaked assets locked at the platform level (not immediately usable).lockedStakeable:Locked assets usable only for staking.lockedStaked:Staked assets that remain locked post-staking period.pendingStaked:Assets committed to staking, awaiting the staking period start.atomicMemoryUnlocked:Unlocked assets in atomic memory (for cross-chain transfers).atomicMemoryLocked:Locked assets in atomic memory.
Understanding these types helps you set precise thresholds and interpret balance-related webhook data. For detailed definitions, refer to the API documentation
What Data Will You Receive?
When an event triggers your webhook, you’ll receive a JSON payload with details about the event. Here’s what to expect for each event:
Validator Stake
This event describes a validator NodeID-Ns1eDN3K9HTnavgiBQhtpzRxUCxJ55Xhc staking 2,700,000 AVAX on the Avalanche primary network for approximately 31 days. The transaction processes previously unlocked funds, stakes the specified amount, and returns the remainder, with a small fee burned. The validator anticipates earning 13,481.66 AVAX in rewards and has set a 5% delegation fee for potential delegators. This event strengthens the network’s security while rewarding the validator for its participation.
Delegator Stake
This example shows a delegator staking 184.507739834 AVAX with the validator NodeID-8mFFkAeyLkQ5Kgw85ZeAb5XFXjqsxPGUv on the Avalanche Primary Network. The delegation, starting at timestamp 1742850281 and ending at 1744153333 (~15 days), was processed through a permissionless delegation transaction. The delegator is expected to earn approximately 0.444953 AVAX in rewards, which will be sent to avax19zfygxaf59stehzedhxjesads0p5jdvfeedal0.
Delegation:
- A delegator staked 184.507739834 AVAX with the validator
NodeID-8mFFkAeyLkQ5Kgw85ZeAb5XFXjqsxPGUvon the Avalanche Primary Network. - The staking period begins at Unix timestamp
1742850281and ends at1744153333, lasting approximately 15.08 days. - The estimated staking reward is 0.444953 AVAX, to be sent to the address
avax19zfygxaf59stehzedhxjesads0p5jdvfeedal0.
Transaction:
- Executed via transaction
DLwC2zX2oS5gwQ9yahpQNzprN4CFzvcDkG8YeYDxhSpeBvPsLin block20994783at timestamp1742850281. - Consumed ~362.2002 AVAX from two UTXOs and emitted two new UTXOs: one for the staked amount (~184.5077 AVAX) and one for the change (~177.6924 AVAX).
- A transaction fee of ~0.00001126 AVAX was burned.
Reward distribution
Validator Reward Distribution
This example shows a payload where the validator with NodeID-ARXUBU2TCXBYG7JdCx7ntuPwBf73pHsTN has received a staking reward of 4.836372611 AVAX after staking 2009.726899312 AVAX from 1741545923 to 1742841915. The reward was distributed to the address avax10f8305248c0wsfsdempdtpx7lpkc30vwzl9y9q via the reward transaction iK11FDhbLvNKwXXrzGXE1eQfdWQVHyqjkmh8wiii8DTTZ73nM.
Reward Details
- Reward Amount:
4836372611nanoAVAX
Since AVAX has a denomination of 9 (1 AVAX = 10^9 nanoAVAX), this converts to 4.836372611 AVAX. - Reward Type:
VALIDATOR
Indicates that this reward is for the validator’s staking activity. - Reward Address:
avax10f8305248c0wsfsdempdtpx7lpkc30vwzl9y9q
The address where the reward is sent.
Staking Period
- Start Timestamp:
1741545923(Unix timestamp)
Corresponds to the time the staking transaction was included in the blockchain, marking the start of the staking period. - End Timestamp:
1742841915(Unix timestamp)
Marks the end of the staking period, coinciding with the reward distribution. \ - Duration: From
1741545923to1742841915, approximately 15 days (1295992 seconds).
Delegator Reward Distribution
This example shows a payload where a delegator received a reward of 0.467719668 AVAX for delegating 197.312156887 AVAX to the validator NodeID-5ZXpg581dpjG8AdoJgTDeXXLnxrQc9Wtd on the Avalanche Primary Network. The delegation lasted approximately 15 days, from 1741539323 to 1742841909. The reward, slightly less than the estimated 0.477264968 AVAX, was successfully distributed to avax19zfygxaf59stehzedhxjesads0p5jdvfeedal0.
Summary of the Event Delegation:
- On timestamp
1741539323(block20884474), the delegator staked 197.312156887 AVAX with the validatorNodeID-5ZXpg581dpjG8AdoJgTDeXXLnxrQc9Wtdvia transaction22TKPMsMFb3Z8Dpk89FnLjA5HnCvSDj9VLQjuyqm4jmNX6W8R4. - The staking period was set to end at 1742841909 (~15 days later), with an estimated reward of 0.477264968 AVAX. Reward Distribution:
- On timestamp
1742841909(block20993983), the staking period concluded, and transactionnhgqAsJQsFcTEwsqMWktwfF1SPbp1488LYZvYSWt9WTjzSnSCdistributed a reward of 0.467719668 AVAX to the addressavax19zfygxaf59stehzedhxjesads0p5jdvfeedal0.
L1 Validator Balance Increased
The l1_validator_balance_increased event happens when an L1 validator gets more balance added to its account. Think of it like depositing money into a bank account so the validator can keep working.
A special transaction (called IncreaseL1BValidatorBalanceTx) is used to give the validator more resources.
Details it includes:
- When it happened (
timestamp). - Which validator got the boost (
nodeId). - Which network it’s part of (
subnetId). - How much balance was added (
balanceIncrease). - Info about the validator (
l1ValidatorInfo) and the transaction itself (tx).
L1 Validator Disabled
The l1_validator_balance_disabled event will be triggered whenever a relevant L1 validator is marked as inactive, either due to insufficient validator balance or when a DisableL1Validatator transaction is issued. The disableType property will indicate whether the validator is disabled to low balance or DisableL1ValidatorTx.
Details it includes:
- When it happened (
timestamp). - Which validator was disabled (
nodeId). - Which network it’s part of (
subnetId). - Why it was disabled (disableType: either
low_balanceordisable_tx_issued). - Info about the validator (
l1ValidatorInfo) and the transaction, if any (tx).
L1 Validator Removed
The l1_validator_removed event will be triggered whenever an L1 validator is completely removed from the L1’s validator set. This generally happens when the SetL1ValidatorWeight transaction is issued with a final weight set as 0.
Details it includes:
- When it happened (
timestamp). - Which validator was removed (
nodeId). - Which network it’s part of (
subnetId). - Why it was disabled (
disableType: eitherlow_balanceordisable_tx_issued). - Info about the validator (
l1ValidatorInfo) and the transaction (tx).
L1 Validator Threshold Reached
The l1_validator_balance_threshold_reached event This event warns that a validator’s balance has dropped below a certain level (a “threshold”). It’s a heads-up that the validator might stop working soon if it doesn’t get more resources. The balance decreases gradually over time (like a subscription fee), and no specific transaction causes this.
Details it includes:
- When it happened (
timestamp). - Which validator is low on balance (
nodeId). - Which network it’s part of (
subnetId). - What the balance was before (
previousPaygBalance) and what it is now (currentPaygBalance). - Info about the validator (
l1ValidatorInfo).
Was this page helpful?