ON (ON) Price

ON is the native token of Orochi Network and serves its “verifiable data infrastructure.” It connects those who use the network with those who provide network capabilities: users can use ON to pay for network interactions or rent storage space, while validators, storage infrastructure providers, and zero-knowledge sequencers receive ON compensation for providing their respective services. Specifically, validators need to stake ON to participate in consensus, and the network grants ON rewards based on their contributions; fees for distributed storage rentals are used to compensate providers that maintain storage infrastructure; ZK sequencers process transactions and provide privacy-related computational work, also receiving compensation in ON. Therefore, ON is not only a medium for transactions, but also a tool for staking, payments, and incentive settlement among these participant roles.

ON's use in the network can be understood by service type. Validators participating in consensus first stake ON and then receive ON rewards based on their contributions to network security and integrity; users who need to store verifiable data use ON to rent distributed storage space, with fees flowing to providers that maintain this infrastructure; ZK sequencers that process transactions and undertake computational work also receive ON compensation. When users initiate transactions or other network interactions, ON is also used to pay network fees. This creates the following relationship: users pay for network resources and interactions, while participants providing validation, storage, or sequencing services receive corresponding incentives; whether a participant takes on a particular role and the specific returns involved depend on actual services and network rules, rather than merely holding ON.

The ON code repository released by Orochi Network includes token and vesting contracts, and describes its goal as a transparent, phased release arrangement for tokens allocated to the community and supporters. Vesting links the time at which certain tokens become obtainable to preset periods, rather than releasing all of the relevant allocation at once. The deployment instructions in the repository require the token generation event time and vesting terms to be set before deployment, which also indicates that specific addresses, periods, and arrangements should be determined by the actually adopted contracts and their configurations. The repository describes the phased-release mechanism; it should not be used to infer that a particular on-chain contract has already been deployed or that a specific unlock schedule is being executed.