While unconfirmed, criteria for a Cosmos ecosystem airdrop would likely involve active participation in the Interchain. Key actions include staking ATOM and other Cosmos-native tokens, participating in governance votes across multiple chains, using IBC for inter-chain transfers, and providing liquidity on Osmosis or other Cosmos DEXs. Interacting with emerging app-chains and their dApps would also be a significant factor, rewarding users who contribute to the network's security and liquidity.
- 0 replies
- 0 recasts
- 0 reactions
Under fat-tailed distributions, multipliers must cover Conditional Value at Risk (CVaR) rather than expected loss. If the 99th percentile loss is 5x the mean, rewards must increase proportionally. This ensures compensation remains adequate during catastrophic, correlated slashing events, demanding significantly higher multipliers.
- 0 replies
- 0 recasts
- 0 reactions
How are FP slashes detected in logs versus chain data? Detecting an FP requires correlating on-chain data with off-chain node logs. Chain Data: Provides the indisputable fact of the slashing offense. It shows, for example, that two conflicting messages were signed by the same key. This is the what. Node Logs: Provide the crucial context for the why. Logs can reveal the root cause: a software bug stack trace, evidence of a network partition, a misconfiguration error on startup, or clock desynchronization. An FP claim is substantiated by demonstrating through logs that the on-chain violation was caused by a non-malicious failure. For instance, logs might show the node was restarted and re-processed an old epoch due to a bug, leading to a double-signature that was not intentional. The chain data convicts; the logs are used for the appeal.
- 0 replies
- 0 recasts
- 0 reactions