AT (AT) Price

AT is the ticker for the APRO-related token; the token information page lists its name as APRO and its ticker as AT. APRO provides data services for decentralized applications, and its core architecture combines off-chain data processing with on-chain verification. This definition does not mean that all AT holders automatically become data nodes or receive node rewards. The holding, transfer, and market trading of the token are matters separate from how applications call APRO data services.

APRO provides external data services for decentralized applications, for example enabling applications to obtain data such as prices. Its goal is to allow data originally located off-chain to be used by smart contracts or other decentralized applications after processing and in conjunction with on-chain verification. On-chain contracts cannot arbitrarily read data from the off-chain world directly. Therefore, the key to data services is not only “providing a value,” but also how data is processed and delivered to or verified on-chain. The types of data and integration methods actually available to an application depend on the APRO service model it chooses.

Data push means that nodes proactively submit updates on-chain when conditions such as preset price thresholds or time intervals are met. It is suitable for scenarios in which contracts need to continuously read the latest on-chain data and data is expected to be available in advance when conditions are triggered. Data pull, by contrast, is initiated by an application when needed, after which it obtains the required data. Compared with continuous pushing, it can avoid repeated on-chain updates when there is no demand, although the corresponding interaction must still be completed when a request occurs. The difference between the two models lies in who triggers an update and when it occurs, rather than merely in different data content.

The token information page lists AT's total supply as 1 billion tokens and identifies it as a BSC token. Total supply describes the total token amount stated in that material; it does not equal the circulating supply at a particular point in time or the amount immediately tradable in the market. To determine actual tradable supply, holdings, transfers, locks, or other circulation states must be distinguished separately. Such dynamic information cannot be directly inferred from the figure “total supply is 1 billion tokens,” nor does it represent price performance.

The APRO Chain design proposed by APRO Research in the ATTPs document envisions validation nodes staking APRO tokens as a performance constraint: nodes first put assets at risk and then participate in relevant verification; if malicious behavior is found, the design includes a mechanism to slash staked assets. This arrangement seeks to link node behavior to economic consequences, but it is a chain design proposed in a document. It should not be described as a mechanism already effective for all AT holders, nor does merely holding AT automatically mean participating in staking, bearing penalties, or receiving staking rewards.

In the push model, preset conditions such as price thresholds or time intervals determine when nodes submit on-chain updates. When the conditions are not triggered, the system need not proactively continue updating under the same rule. Time conditions limit the maximum update interval, while threshold conditions trigger updates when data changes reach a specified level. Therefore, the frequency of on-chain updates for pushed data is jointly determined by rules and actual data changes. It does not mean updates occur every block, and a specific data source's update cycle cannot be inferred merely from the word “push.”