What is Analog?

This program is set to run in 3 distinct phases with the first phase for Developers starting on April 16, 2024 phase 2 for Community beginning on April 30, 2024 and Phase 3 for Validators beginning on May 15, 2024. Each phase will run approximately 3 months in duration.

The timeline is subject to change at the sole discretion of Analog.

1. Battle-Testing Analog Watch and GMP SDK: Conduct rigorous testing of the Analog Watch and GMP SDK to gather product feedback and ensure their robustness and reliability for real-world applications.
2. Bootstrapping a Decentralized Community: Focus on growing a decentralized community by attracting more developers and users to the Analog network, fostering collaboration and innovation within the ecosystem.
3. Assessing Validator Resilience and Performance: Evaluate the resilience and performance of validators to ensure they are prepared for seamless integration with the mainnet, ensuring network security and efficiency.

A total reward pool of up to 1,811,594 ANLOG tokens, representing 2.0% of the total token supply, has been allocated for Analog’s Incentivized testnet participants. Analog reserves the right to increase the allocation at a later stage. 

Rewards will be allocated across validators, developers, and the community:

• 30% will be allocated to validators
• 70% will be allocated to community/dApp users and developers
• Specific reward amounts are based on activities and calculations done will be communicated at the end of Phase 3 of the Incentivized Testnet which can be found on the testnet leaderboard here. 
• It is possible for participants to be eligible for more than one reward pool if they satisfy the requirements. Scores are not final, the Analog Team may introduce additional requirements to deter sybil attacks and incentivize the Analog ecosystem. Near the end of Phase I, the Analog team will release the minimum ATP points needed to be eligible on their website, blog, and Twitter.

For more information on eligibility, please view the Eligibility Section here.

Certain jurisdictional limitations may apply (i.e. users must be non-U.S./Canada and OFAC compliant), as outlined here.