Onyxcoin has a fixed max supply of 68,892,071,756 units which 20,489,639,348 is currently burned on the Ethereum blockchain giving total supply of 48,402,437,326 XCN.

As of 8/18/2025:

• 34,766,197,525 is circulating in open markets.

• 11,000,000,146

• Gas token: Used to pay for all transactions and smart contract executions across the Onyx L3 blockchain. A portion of every transaction fee is burned, making XCN total supply deflationary.

• Service payments & discounts: Required to access and pay for Onyx Cloud (RPC/API) and Sequence ledger services, with XCN holders receiving discounted or premium access.

Onyxcoin is available to be purchased and/or sold on the the following exchanges as of 6/25/2025.

Developing and testing decentralized applications (dApps) on Onyx requires a robust set of tools. Below is an overview of essential development environments, testing frameworks, and SDKs that streamline the process of building, deploying, and debugging smart contracts on the Onyx blockchain.

Hardhat is a comprehensive development environment tailored for Ethereum, Onyx, and other EVM-compatible networks. It simplifies the creation, compilation, deployment, testing, and debugging of smart contracts while providing an extensible framework.

Key Features:

• Built-in console for interactive debugging.

This guide provides step-by-step instructions for running an Onyx full node using Arbitrum Nitro. It incorporates the exact parameters and chain configuration for the conduit-orbit-deployer Orbit chain.

• Chain Name: Onyx

• Chain ID: 80888

The proposal threshold represents the minimum number of votes required for an account to create and submit a governance proposal within the Onyx governance framework. This requirement ensures that only stakeholders with a significant vested interest in the protocol can initiate changes, preventing spam or frivolous proposals.

In the CHNGovernance contract, the proposalThreshold() function is implemented to enforce the required voting power threshold before a proposal can be submitted.

RETURN: This function returns an unsigned integer (uint) representing the minimum number of votes required for an account to be eligible to create a proposal.

To retrieve the proposal threshold in a Solidity environment, the proposalThreshold()

The propose function allows eligible stakeholders to create governance proposals that can introduce changes to Onyx. Proposals may include modifications to the staking interest rate model, risk parameters within the protocol, or other governance-directed alterations to protocol parameters.

Once a proposal is submitted, it enters the voting phase, where token holders can vote for or against the proposed changes. If the proposal meets the required quorum and is approved, it is queued and executed via the Onyx Timelock contract after the predefined waiting period.

• The proposer must hold more XCN than the current proposal threshold (proposalThreshold()) as of the immediately preceding block.

The queue function is responsible for moving a successful proposal into the Onyx Timelock queue. Once a proposal has been approved by the governance process, it must be queued before it can be executed. Only proposals that have met the required voting threshold and have been successfully passed can be queued.

In the CHNGovernance contract, the queue() function ensures that only validated proposals are added to the Timelock queue, preventing unauthorized executions.

• proposalId: The unique identifier of the governance proposal that has been successfully approved and is eligible to be queued.

The execute function is responsible for applying changes from a successfully approved and queued proposal to the designated target contracts within the Onyx protocol. Once a proposal has passed the governance process and completed the Timelock delay period, it can be executed, implementing the proposed modifications.

The execute() function ensures that only successful and properly queued proposals can be executed, enforcing governance integrity and protocol security.

• proposalId: The unique identifier of the proposal to be executed. This proposal must have successfully passed governance voting, been queued, and completed the Timelock delay period.

The Passive Points mechanism is designed to reward users simply for maintaining eligible digital assets in their self-custodied Web3 wallets. This approach incentivizes long-term alignment with the Onyx ecosystem by recognizing and rewarding passive asset holders who contribute to ecosystem stability without requiring active trading or liquidity deployment.

To qualify for Passive Points accrual, users must hold whitelisted assets—a curated list of tokens approved by the Onyx DAO for point rewards—within non-custodial Web3 wallets. Supported wallets include widely-used browser-based solutions such as MetaMask, WalletConnect-compatible interfaces, and secure hardware wallets like Ledger and Trezor.

Importantly, any assets held within centralized exchange (CEX) accounts are categorically ineligible for point accumulation. This restriction ensures that all qualifying holdings are verifiably on-chain, transparent, and cryptographically linked to user-owned wallet addresses. This design choice also encourages decentralized custody practices and aligns user incentives with the ethos of DeFi sovereignty.

Onyx utilizes a snapshot-based system to periodically capture wallet balances of whitelisted assets. These snapshots are taken at each block allowing the protocol to calculate time-weighted holdings for each address. This means that the longer a user holds a qualifying asset, the more Passive Points they accumulate, scaled proportionally to the quantity held.

APP POINTS ARE NOT ACTIVE YET

The App Points program represents a powerful layer of optional, developer-directed incentives within the broader Onyx Points architecture. It introduces a modular, app-specific mechanism in which partnered decentralized applications (dApps) are allocated a share of the total Onyx airdrop budget—known as Onyx App Points—and are granted full autonomy in designing their own internal reward frameworks.

This subsystem fosters a competitive environment among integrated applications, where each app competes to attract and retain user liquidity by offering unique and potentially lucrative point-based incentives. App Points are thus an extension of the core Onyx Points system, tailored to promote innovation and deepen protocol integrations across the DeFi composability stack.

Under this model, the Onyx Foundation pre-allocates a fixed quantity of Onyx airdrop tokens (e.g., XCN or other relevant distribution assets) to partnered applications. These applications—ranging from DEXs and lending platforms to staking services and DeFi aggregators—are given full discretion over:

The following digital assets have been officially whitelisted for Season Two of the Onyx Points Program. Each asset is associated with a specific Ethereum contract address and contributes a defined percentage of the total point emission rate, based on its strategic value and utility within the Onyx XCN Ledger ecosystem. Staked XCN on Etheruem for XCN Stakers is also included.

Ethereum

Onyx Ledger (XCN Ledger)

Onyx AI supports a wide spectrum of on-chain interactions, with dynamic routing logic that enables it to choose optimal execution paths based on real-time conditions. Key supported features include:

✅ Token Minting

• Interacts with ERC-20/ERC-721/ERC-1155 minting contracts.

• Can deploy new tokens or mint additional supply of existing contracts.

The request to the Proposal API can specify various filters, allowing retrieval of proposals by IDs, state, and pagination parameters.

Request Parameters

Onyx, also referred to as the XCN Ledger, is a highly scalable Layer 3 blockchain network that is architected for performance, security, and cost efficiency. It is deployed using the Arbitrum Orbit stack and benefits from the robust security foundation of Coinbase’s Base Layer 2 blockchain. This unique architecture enables Onyx to inherit the modular scalability of Arbitrum while maintaining the security assurances provided by Base, offering an optimized environment for developers building next-generation decentralized applications (dApps).

Onyx is fully Ethereum Virtual Machine (EVM) compatible, allowing seamless deployment of smart contracts and interoperability with existing Ethereum-based applications and tooling. Developers can build and deploy decentralized finance (DeFi) protocols, payment solutions, governance frameworks, and other blockchain-based services while leveraging Onyx’s high throughput and low transaction costs.

With an institutional-grade infrastructure, Onyx is designed to support large-scale applications and enterprise adoption, ensuring high availability, robust security mechanisms, and scalability optimizations.

The Onyx Documentation Hub is the central resource for institutions and developers looking to build, integrate, and leverage the full potential of Onyx This comprehensive documentation provides in-depth technical details, architecture specifications, and implementation guidelines for developers aiming to utilize Onyx’s blockchain infrastructure efficiently.

Beyond just technical references, this hub serves as a developer-centric knowledge base, offering code samples, API references, SDK integration guides, and best practices for optimizing smart contract deployments and blockchain interactions. Whether you are designing custom dApps, implementing scalable payment systems, or integrating Onyx into multi-chain architectures, the documentation provides a structured approach to understanding transaction finality, network security, gas optimizations, and governance mechanisms within the Onyx ecosystem.

By leveraging the resources provided, institutions and developers can streamline development workflows, enhance security practices, and maximize the performance of their blockchain-based applications on Onyx.

Quick Start Below:

Onyxcoin (XCN) is the native cryptocurrency of the Onyx Protocol, a next-generation Web3 blockchain platform specifically designed to power decentralized financial services. As the cornerstone of the Onyx ecosystem, XCN plays a dual role as both a utility token and a governance asset, underpinning the protocol’s core operations and community-led development.

Within the ecosystem, XCN enables a wide range of functionalities. It is essential for participating in protocol governance, where token holders can propose and vote on critical updates, changes to the network’s parameters, and allocation of treasury funds—ensuring a decentralized and transparent decision-making process. In addition, XCN acts as a payment mechanism for accessing Onyx’s suite of financial applications and premium services, including Chain.com and other infrastructure products.

XCN is also the native gas token for the Onyx Ledger, a high-performance Layer-3 blockchain built atop Ethereum and Base. This means that all transactions and smart contract executions on the Onyx Ledger are powered by XCN, with a portion of each transaction fee being burned to introduce a deflationary mechanism and support long-term value appreciation.

Overall, Onyxcoin (XCN) functions as the economic engine driving innovation, security, and user engagement across the entire Onyx Protocol—empowering users, developers, and stakeholders in a truly decentralized financial ecosystem.

Release Schedule

XCN is released monthly from two smart contracts.

• 200 million from XCN Timelock

• 200 million from XCN DAO

XCN Timelock

The XCN Timelock release is governed by a time-locked smart contract designed to release a fixed amount of tokens over time in a predictable and transparent manner. Specifically, 200 million XCN tokens are unlocked every 30 days—defined as one epoch—until the scheduled conclusion of the emission period in March 1, 2030.

The XCN DAO operates through a separate smart contract that governs the distribution of tokens tied to community governance and user rewards. Like the Treasury, the DAO is subject to the same 200 million XCN per month release cap. However, the actual release of tokens from this contract is conditional:

• Tokens are only distributed when users claim staking or governance rewards, or

• When an Onyx Improvement Proposal (OIP) is deployed and executed onchain.

Importantly, any unused allocation rolls over into the next month. For example, if only 100 million XCN are claimed or utilized in June, the remaining 100 million will be added to July’s allocation, allowing up to 300 million XCN to be distributed that month.

This structure ensures controlled token emissions while allowing flexibility for ecosystem participation and governance engagement to scale over time.

The unlock schedule illustration below guides users to a predictable emission schedule:

The illustration below shows the current XCN distribution figures and market capitalization as of August 18th, 2025.

Onyxcoin (XCN) is, and always will be, native to the Ethereum blockchain. XCN is deployed on other blockchains through onchain bridging where one XCN is locked on the Ethereum blockchain and one is made availble or minted on a subsequent blockchain.

Contract Addresses

XCN on Ethereum (Native XCN): 0xA2cd3D43c775978A96BdBf12d733D5A1ED94fb18

XCN on Base: 0x9c632e6aaa3ea73f91554f8a3cb2ed2f29605e0c

XCN on Onyx Ledger: N/A

XCN on BNB Chain: 0x7324c7C0d95CEBC73eEa7E85CbAac0dBdf88a05b

Explorers

Ethereum: https://etherscan.io/token/0xa2cd3d43c775978a96bdbf12d733d5a1ed94fb18 Base: https://basescan.org/token/0x9c632e6aaa3ea73f91554f8a3cb2ed2f29605e0c Onyx Ledger: https://explorer.onyx.org BNB Chain: https://bscscan.com/token/0x7324c7c0d95cebc73eea7e85cbaac0dbdf88a05b

This section provides essential technical details regarding Onyx’s publicly available Remote Procedure Call (RPC) endpoints, allowing developers to interact with the Onyx blockchain network. These RPC endpoints facilitate smart contract deployments, transaction broadcasting, data querying, and state synchronization with the Onyx blockchain. Developers and infrastructure providers can integrate these endpoints into their applications, wallets, or blockchain indexing services to ensure seamless interaction with the Onyx network.

Onyx provides both HTTPS and WebSocket (WSS) RPC endpoints, enabling developers to connect to the network for executing transactions and retrieving blockchain state data. The WebSocket endpoint is particularly useful for applications requiring real-time event subscriptions, such as monitoring contract events or transaction confirmations. The available endpoints are:

You can access the MiCA whitepaper by following the provided link below. The document, titled “MiCA Whitepaper,” serves as a comprehensive guide to the Markets in Crypto-Assets (MiCA) regulation, outlining its objectives, framework, and implications for the cryptocurrency and digital asset sectors.

Access the MiCA whitepaper here.

The Onyx SDK is a powerful TypeScript library that facilitates seamless interaction with Onyx networks. It provides robust tools for bridging assets, passing messages across networks, and interfacing with smart contracts through an intuitive and developer-friendly API.

Key Features

• Token Bridging: Effortlessly transfer assets between Base and Onyx.

• Message Passing: Enable cross-chain communication.

• Contracts Interface: Utilize strongly-typed methods for smart contract interaction.

This guide provides an overview of the Onyx SDK functionality. Refer to the tutorials for more examples and in-depth explanations. [UNDER CONSTRUCTION]

The Onyx Governor follows a structured governance model that balances decentralization with security and efficiency. The Timelock contract prevents sudden, unauthorized modifications to the protocol, ensuring all decisions undergo rigorous scrutiny before being enacted. Additionally, the on-chain governance mechanism provides an immutable and transparent record of all proposals, votes, and implementations, reinforcing accountability and trust within the community.

By leveraging Ethereum-based smart contract governance, the Onyx Governor facilitates an efficient and transparent decision-making process that aligns with the interests of long-term stakeholders, ultimately promoting protocol sustainability and robust security standards.

Mechanisms for Earning Onyx Points

The Onyx Points incentive framework provides users with three distinct, yet synergistic, methods through which they can actively participate in the Onyx ecosystem and accrue points. These earning pathways are not arbitrarily defined; rather, they are strategically constructed to align with the foundational principles and operational capabilities of the XCN Ledger. This ensures that the accrual of Onyx Points reflects meaningful engagement, protocol-enhancing behavior, and sustainable economic activity governed by Onyx DAO.

Each method has been optimized to reward users for interacting with core decentralized finance primitives—liquidity provision, asset management, and on-chain utility—while reinforcing protocol security, stability, and user growth. The design intention is to embed incentive structures directly into behaviors that the XCN Ledger is uniquely equipped to support at the protocol level.

Onyx AI: Autonomous Blockchain Intelligence on the XCN Ledger

Onyx AI is a next-generation, blockchain-native autonomous agent engineered to interface directly with decentralized infrastructure on the XCN Ledger. It combines on-chain execution capabilities with off-chain artificial intelligence reasoning, enabling intelligent automation of complex tasks across decentralized finance (DeFi), token management, and cross-chain operations. This hybrid agent is designed to operate with programmable autonomy, execute smart contract interactions, and respond to user prompts with contextual awareness and transaction precision.

At its core, Onyx AI functions as a self-directed, modular smart agent deployed natively on the XCN Ledger, leveraging XCN as the sole gas asset for computation, execution, and value transfer. XCN is required to purchase Credits that enable the user to utilize prompts with the Agent.

The agent is architected to bridge the gap between AI-driven logic systems and the deterministic nature of EVM-compatible smart contract environments. It operates under a permissionless framework but utilizes embedded security policies to ensure safe execution across trusted protocols and wallet environments. The agent operates on a gas-free basis on supported chains therefore there is no requirement for native gas on the blockchain.

Onyx AI marks a pivotal shift in the evolution of decentralized automation. By tightly integrating artificial intelligence with blockchain-native execution, it enables a future where agents—not just humans—can reason, transact, and operate autonomously within secure, deterministic environments. With Onyx AI, intelligent on-chain automation becomes accessible, programmable, and trustless.

The Onyx Governance API provides programmatic access to governance data, proposal tracking, and voting details within the Onyx protocol. Developers and governance participants can use this API to fetch real-time governance data, submit transactions, and monitor proposal statuses.

The Governance API Base URL is: govapi.onyx.org

The Onyx Governor, also known as the Chain Governor, serves as the governance module of Onyx, enabling a decentralized, on-chain decision-making process that ensures protocol upgrades, parameter adjustments, and policy implementations are collectively determined by the Onyx community. This governance framework is designed to provide transparency, security, and adaptability, allowing token holders to actively participate in the protocol's evolution while maintaining the integrity of its decentralized architecture.

• Governance proposals can only be initiated by addresses that hold more than 100,000,000 XCN tokens at the time of submission. This requirement ensures that only stakeholders with a significant vested interest in the protocol can propose changes, thereby maintaining governance integrity and preventing frivolous proposals.

The quorum votes represent the minimum number of affirmative votes required for a proposal to be successfully executed within the Onyx governance framework. This threshold is critical in ensuring that governance decisions reflect a sufficient level of participation from the voting community and are not subject to manipulation by a small number of token holders.

To enforce this quorum requirement, the CHNGovernance contract implements the quorumVotes() function, which returns the predefined vote threshold necessary for a proposal to pass.

RETURN: The function returns an unsigned integer (uint) representing the minimum number of votes required for a proposal to achieve quorum and be successfully executed.

In Solidity, the quorumVotes()

The proposal max operations parameter defines the maximum number of executable actions that can be included in a single governance proposal within the Onyx governance framework. Each action represents a function call that will be executed if the proposal is approved and successfully implemented. This limitation ensures governance proposals remain manageable and do not introduce excessive complexity or execution risks.

In the CHNGovernance contract, the proposalMaxOperations() function is implemented to enforce this restriction, defining the upper limit of actions within a proposal.

RETURN: The function returns an unsigned integer (uint) representing the maximum number of actions that can be included in a governance proposal.

To retrieve the maximum allowed operations in a proposal, the proposalMaxOperations()

The voting delay represents the number of Ethereum blocks that must elapse before voting can begin on a newly created proposal. This delay is added to the current block number at the time of proposal creation and serves as a buffer period, allowing stakeholders to become aware of the proposal before voting starts.

In the CHNGovernance contract, the votingDelay() function is implemented to enforce this rule, ensuring that there is a defined waiting period before a proposal is open for voting.

RETURN: The function returns an unsigned integer (uint) representing the number of Ethereum blocks that must pass before voting on a proposal can commence.

To retrieve the voting delay in a Solidity environment, the votingDelay()

The voting period defines the duration for which a governance proposal remains open for voting, measured in Ethereum blocks. During this period, eligible token holders can cast their votes to either support or reject the proposal. Once the voting period ends, the results determine whether the proposal advances to execution or is dismissed.

In the CHNGovernance contract, the votingPeriod() function establishes the length of time a proposal remains open for voting.

RETURN: The function returns an unsigned integer (uint) representing the number of Ethereum blocks during which voting is active for a given proposal.

To retrieve the voting period in a Solidity environment, the votingPeriod() function can be called using an instance of the

The cancel() function allows the Guardian or any eligible participant to cancel a governance proposal that has not yet been executed. This mechanism provides a safeguard against malicious or outdated proposals that no longer align with the protocol’s best interests.

A proposal can be canceled under the following conditions:

• If the Guardian invokes the cancel function, the proposal will be immediately revoked.

The getReceipt function retrieves the ballot receipt for a specific voter in relation to a particular governance proposal. This function enables governance participants and developers to track and verify voting activity, ensuring transparency in the decision-making process.

The getReceipt() function is implemented in the CHNGovernance contract to return structured voting details for a given voter’s participation in a proposal.

• proposalId

The castVote function allows an eligible voter to cast their approval or disapproval on a governance proposal. The voting power of an account is determined based on the number of votes delegated to it at the time the proposal transitioned into the Active state.

The castVote() function ensures that only eligible voters can participate in governance decisions, maintaining the integrity of the Onyx governance system.

Parameters

• proposalId

The Timelock contract is a governance-controlled smart contract that facilitates secure, time-delayed upgrades to system parameters, logic, and contracts within the Onyx protocol. This contract ensures that all governance actions are transparent and auditable, preventing instantaneous or unauthorized modifications.

• Implements a time-delayed, opt-out upgrade pattern to enhance protocol security.

• Enforces a minimum delay before any governance action can be executed.

Onyx Points is a user-centric rewards mechanism integrated into the Onyx XCN Ledger, specifically engineered to incentivize liquidity provision and active engagement within the broader Onyx blockchain infrastructure. This program is designed to reinforce ecosystem stability, promote organic asset utilization, and position Onyx as a premier protocol hub for institutional blockchain and bank applications, decentralized finance practitioners, capital allocators, and yield-maximizing participants.

Participants can accrue Onyx Points by holding and transacting with approved (whitelisted) digital assets across a curated selection of decentralized applications (dApps) that will be available by Season Two within the Onyx ecosystem. These interactions are tracked and quantified through an on-chain metric system that reflects real economic activity and protocol contribution. Onyx Points serve as non-transferable, reward-bearing credentials to the associated wallet addresses connected to the system.

The distribution of Onyx Points is decentralised and organized into discrete epochs known as “Seasons.” Each Season is finite and governed by predefined block height parameters to ensure deterministic issuance and prevent inflationary supply shocks. Points earned are tokenized in the form of NFT-based positions, enabling composability, future utility layering, and provable ownership while also enhancing the gamification layer of user engagement.

Season One of the Onyx Points Program commenced with the protocol’s initial deployment at Onyx XCN Ledger mainnet block height

The following smart contract addresses are integral to the Onyx blockchain infrastructure. These addresses correspond to core protocol contracts and token bridge contracts, which facilitate transaction processing, cross-chain interoperability, and protocol governance. Developers building on Onyx should reference these addresses for contract interactions, cross-chain asset transfers, and network-specific implementations.

Layer 1 Governance & Staking

The smart contracts for Onyx on Ethereum are below:

The core smart contracts of Onyx define the network’s fundamental operations, including transaction finalization, message passing, and state synchronization.

The Token Bridge Contracts enable seamless asset transfers between Onyx and external networks. These contracts are responsible for asset locking, minting, and validation in both Layer 2 (L2) and Layer 3 (L3) environments.

The Onyx Protocol operates under a decentralized governance framework, enabling XCN token holders to participate in protocol decision-making and upgrades. Governance is facilitated through four core smart contract components.

The Onyx Governance module is available on Onyx dApp. This module is exclusively controlled by XCN stakers on Ethereum. This section of the documentation hub goes over the entire Governance functions.

Core Components

• XCN Token – The governance token used for voting power and protocol participation.

• Staking Module – A mechanism that allows users to stake XCN, granting them voting weight proportional to their staked balance.

• Governance Module (Governor) – The primary contract responsible for processing governance proposals and vote execution.

• Timelock Contract – A security mechanism ensuring that approved proposals are subject to a mandatory delay before execution, allowing the community to react if necessary.

Together, these components enable a decentralized governance model where protocol modifications, parameter adjustments, and new asset integrations can be proposed, voted on, and executed through administrative functions within oToken contracts or the Comptroller contract.

Proposal Eligibility: To submit a governance proposal, an address must hold a minimum of 100,000,000 XCN in voting weight. Proposals consist of executable smart contract code, defining precise changes to the protocol, such as modifying interest rate models, listing new collateral assets, or adjusting risk parameters.

Voting and Approval: Once a proposal is submitted, a three-day (3-day) voting period is initiated. During this window, XCN holders can vote either for or against the proposal. A proposal is deemed successful if it receives:

• A majority vote in favor.

• A minimum of 200,000,000 XCN votes supporting it. Upon approval, the proposal is queued in the Timelock contract and becomes executable after a mandatory two-day (2-day) delay. This delay period allows the community to review the proposed changes before they are enacted on-chain.

To obtain voting rights, users must stake XCN tokens. The amount of XCN staked determines the voting weight of an address. Governance power is dynamically adjusted based on staking activity:

• Increasing stake grants additional voting weight.

• Withdrawing XCN from staking automatically reduces voting power.

This staking mechanism ensures that governance influence is directly proportional to active participation in securing and supporting the protocol.

This governance structure ensures that protocol decisions remain community-driven and subject to transparent, on-chain governance mechanisms.

The Guardian Wallet within Onyx Governance serves as a critical safeguard against malicious proposals, ensuring that even if a proposal achieves the necessary vote weight through hostile or manipulative means, it can be canceled before execution. This wallet is controlled by a trusted security council or smart contract logic designed to detect governance attacks, preventing unauthorized or harmful protocol changes. The Guardian has the authority to nullify proposals that violate security policies, such as those attempting to transfer funds improperly, alter fundamental contract logic, or introduce vulnerabilities into the system. By integrating this failsafe mechanism, Onyx Governance maintains a robust security posture while still enabling decentralized decision-making.

The Guardian Wallet operates by continuously monitoring governance proposals and tracking vote behavior to identify anomalies, including vote concentration from potentially compromised accounts. If a proposal is flagged as malicious or harmful, the Guardian can intervene before the proposal progresses to execution within the Timelock contract. This feature ensures that the governance process remains resilient against coordinated attacks or governance takeovers. Additionally, the Guardian Wallet can be enhanced through onchain automation, further reducing the risk of unilateral actions while maintaining the integrity and trustworthiness of the Onyx Protocol's decentralized governance framework.

The state function retrieves the current state of a specified governance proposal. The function returns an enumerated value representing one of the possible states defined in the CHNGovernance contract. This function allows governance participants to track the progress and outcome of any proposal.

Function Implementation in CHNGovernance

The state() function ensures that governance participants can query and verify the status of proposals, maintaining transparency in decision-making.

Function Signature

function state(uint proposalId) public view returns (ProposalState)

Parameters

• proposalId: The unique identifier of the proposal whose state is being queried.

• RETURN: If the function call is successful, it returns an enumerated type ProposalState, which may have one of the following values:

  • Pending: The proposal has been submitted and is awaiting the start of the voting period.

  • Active: The proposal is currently in the voting period.

To retrieve the state of a proposal using Solidity, the state() function can be called from an instance of the CHNGovernance contract:

For interacting with the CHNGovernance contract using Web3.js, the following example demonstrates how to retrieve a proposal’s state:

• The state() function is a view function, meaning it does not modify blockchain state and can be executed without incurring gas costs.

• The proposal state helps governance participants track where a proposal stands in the decision-making process.

• Proposals that expire before execution need to be resubmitted if they are still relevant.

The castVoteBySig function allows an offline signer to participate in Onyx governance voting by submitting a digitally signed vote. Unlike the castVote function, which requires the voter to be online and execute the transaction, this function enables voting via an EIP-712-compliant signature, making it useful for delegated and gasless voting.

Function Implementation in CHNGovernance

The castVoteBySig() function ensures that votes can be cast securely and efficiently using off-chain signatures, reducing the need for direct blockchain interaction while maintaining the integrity of the voting process.

Function Signature

function castVoteBySig(
    uint proposalId,
    bool support,
    uint8 v,
    bytes32 r,
    bytes32 s
) public

Parameters

• proposalId: The unique identifier of the governance proposal on which the vote is being cast.

• support: A boolean value indicating the vote choice:

  • true → Vote in favor of the proposal (Yes)

  • false → Vote against the proposal (No)

• v: The recovery byte of the signature, used for ECDSA signature verification.

• r: First half of the ECDSA signature pair.

• s: Second half of the ECDSA signature pair.

• RETURN:The function does not return a value. If the proposal ID is invalid or the signature is not valid, the transaction reverts with an error.

To cast a vote using Solidity, the castVoteBySig() function can be called from an instance of the CHNGovernance contract:

For interacting with the CHNGovernance contract using Web3.js, the following example demonstrates how to cast a vote by signature:

• The castVoteBySig() function is state-modifying and will incur gas costs.

• Votes are weighted based on the voting power at the moment the proposal became Active.

• EIP-712-compliant signatures ensure the security and authenticity of the vote.

At Onyx, security is fundamental to our mission. We highly value the contributions of ethical hackers who help us uphold the highest standards of security across the Onyx ecosystem. While Onyx has undergone rigorous professional audits and formal verification, it operates on evolving technology that may still contain undiscovered vulnerabilities.

We encourage the community to actively audit our smart contracts and infrastructure and responsibly disclose any security concerns. This program is designed to incentivize responsible security research, outlining the expectations for ethical vulnerability disclosure and the rewards available for eligible findings.

Rewards

Onyx offers substantial rewards for vulnerabilities that could lead to the loss or freezing of assets or otherwise cause harm to users. The reward amount is determined based on the severity and exploitability of the vulnerability. Eligible discoveries may receive rewards ranging from $500 to $150,000, in accordance with the terms outlined below.

Scope

Primary Scope:

The primary focus of the bug bounty program is vulnerabilities impacting the on-hain Onyx Protocol, deployed on Ethereum Mainnet, specifically for the contract addresses listed in this developer documentation. This scope is subject to change as new contracts are deployed or existing contracts are deprecated.

Out-of-scope items include:

• Vulnerabilities in third-party contracts built on top of Onyx (e.g., smart contract wallets).

• Issues that require admin key ownership.

Secondary Scope:

The program also includes vulnerabilities affecting the Onyx Interface hosted at app.onyx.org, particularly those that could lead to unauthorized account access or asset manipulation.

Out of Scope:

• Vulnerabilities affecting test environments (Rinkeby, other testnets, and staging servers), unless they also impact the Onyx Protocol or Interface in a way that could put user funds at risk.

All vulnerability disclosures should be submitted to [email protected] with detailed steps for reproducing the issue. Reports may be submitted in written or video format to ensure clarity. Onyx will acknowledge all valid submissions promptly.

To qualify for a bounty reward, you must:

• Identify a previously unreported, original, and non-public vulnerability within the defined scope.

• Provide a detailed disclosure that enables Onyx engineers to reproduce and resolve the issue efficiently.

• Be at least 18 years old.

To encourage ethical security research and distinguish good-faith efforts from malicious activity, researchers must:

• Follow program terms and any other applicable agreements. If conflicts arise, the bug bounty program terms take precedence.

• Report vulnerabilities promptly.

• Avoid causing harm, including privacy violations, service disruptions, or data loss.

When engaging with Onyx under this program, we commit to:

• Offering competitive rewards for eligible findings, with payouts determined based on severity and exploitability at Onyx's discretion.

• Providing Safe Harbor for researchers who comply with program guidelines, ensuring Onyx will not pursue legal action against those acting in good faith.

• Validating and acknowledging reports promptly, including an initial response and further investigation.

All decisions regarding eligibility, reward amounts, and payout determinations are made at Onyx’s sole discretion. Onyx reserves the right to reject submissions and modify the terms of this program at any time.

AI Agent Wallet Architecture

Each instance of Onyx AI is provisioned with a dedicated on-chain wallet, referred to as an agent wallet. These wallets are permissionless and have no centralized control. These wallets serve as the execution layer for autonomous tasks. Users can:

• Fund the agent wallet with any ERC20 token or Ethereum on Onyx, Ethereum, Base, and BNB Chain.

• Predefine operational rules (e.g., budget limits, whitelisted dApps, risk thresholds).

• Allow the agent to execute autonomously within those constraints, using AI to interpret prompts and derive task sequences.

Wallets are deterministic, derived via cryptographic hashing of user identifiers and secured by permissionless layers that enforce non-custodial ownership. Additionally, agent wallets can integrate time locks, multisig guards, and circuit breakers to ensure execution safety.

• Blockchain: Onyx, Ethereum, Base, BNB

• Gas Token: All computational and transaction costs are paid in XCN, the native token of the Onyx Ledger which are converted to Credits . There is no gas required as the agent is gas-free.

• dApp Support: Onyx AI is extensible and continuously updated with support for top-tier dApps in categories including DeFi, NFT marketplaces, staking, and governance.

Example Architecture

This guide is intended for developers and users seeking to understand gas calculations on Onyx, including how gas fees are determined and estimated before submitting transactions. This document provides a detailed breakdown of Onyx's gas estimation methods, practical ways to calculate fees, and code examples for implementation.

For most practical applications, gas estimation can be done via a standard process by calling an Onyx node’s eth_estimateGas method. This method provides a gas limit that should sufficiently cover the entire transaction fee at the given L2 gas price.

To determine the transaction fee, multiply the gas limit by the current L2 gas price:

Transaction Fees = Gas Limit × L2 Gas Price

Since Onyx leverages L3 technology with an Arbitrum Orbit stack, gas estimates can fluctuate based on L1 calldata pricing. The eth_estimateGas result may change over time as the L1 calldata cost varies.

The Activity Points mechanism serves as a core pillar of the Onyx Points incentive model, specifically designed to reward users for contributing active liquidity and engaging with decentralized applications (dApps) across the Onyx-powered DeFi landscape. Unlike passive asset holding, this method reflects active capital deployment, which directly enhances the protocol’s composability, capital efficiency, and market depth.

By utilizing whitelisted assets within integrated DeFi protocols—such as decentralized exchanges (DEXs), automated market makers (AMMs), lending platforms, and yield aggregators—users earn Activity Points at a higher multiplier rate. Specifically, Activity Points are issued at 2x the rate of Passive Points, recognizing the increased economic value and risk-adjusted utility provided by active liquidity participation.

The Onyx ecosystem maintains a vetted and evolving list of participating applications, which are eligible for Activity Point accrual. These integrations are chosen based on security audits, TVL metrics, protocol activity, and alignment with Onyx’s broader strategic roadmap. Users can view the complete list of supported dApps through the Onyx Points Dashboard, which offers real-time tracking, analytics, and application-specific multipliers where applicable.

Examples of eligible apps may include:

The getActions function retrieves the details of a specified proposal by providing its unique proposal ID. This function allows governance participants and developers to inspect the actions of a given proposal, including:

1. The contract addresses that the proposal intends to call.

2. The values (ETH amounts) associated with each call.

Retrieve a list of active and past governance proposals.

Retrieve details of a specific proposal by proposalId.

Submit a vote for a proposal.

Retrieve voting receipt details for a given proposalId and voter address.

Retrieve the current state of a proposal.

• Rate limits apply to prevent abuse of the API.

Quickstart: Building a Decentralized Application (dApp) on Onyx (Solidity)

Introduction

This guide is designed for web developers seeking to build decentralized applications (dApps) on Onyx. No prior knowledge of Ethereum, Onyx, or Solidity is required, but a basic understanding of JavaScript and Yarn is expected. If you are new to Ethereum, it may be beneficial to review the Ethereum documentation before proceeding.

Learning Objectives

In this tutorial, developers will learn:

• The differences between Ethereum’s decentralized architecture and traditional client-server models.

• The fundamentals of Solidity smart contracts.

• How to compile and deploy a smart contract on Onyx.

• The functionality of an Ethereum-compatible Web3 wallet.

To demonstrate these concepts, we will create a decentralized token dispenser using Solidity smart contracts. This dispenser will operate under the following constraints:

1. A user can receive a token only if they have not received one recently.

2. The contract rules are immutable and cannot be modified after deployment.

This guide will walk through transitioning from a centralized Web2 implementation to a decentralized Web3 version on Onyx.

Before starting, ensure you have the following installed:

• VS Code (or any preferred IDE)

• A Web3-compatible wallet (e.g., MetaMask)

• Yarn

• Foundry (for smart contract development)

Additional dependencies will be introduced throughout the guide.

Ethereum is a decentralized network that maintains a shared blockchain ledger across a global network of nodes. Smart contracts execute within the Ethereum Virtual Machine (EVM) and facilitate trustless, programmable transactions.

Key features include:

• Smart contracts: Self-executing programs that enforce business logic.

• Decentralized identity and data portability: Users retain control over their assets and identities.

• Transaction fees: Users pay gas fees in ETH to incentivize network validators.

However, Ethereum transactions can become costly during high network congestion, necessitating scaling solutions such as Onyx.

Onyx is an advanced Layer 3 blockchain built using Arbitrum Orbit and secured by Coinbase’s Base Layer 2. It provides developers with:

• EVM compatibility, enabling Solidity smart contracts to run seamlessly.

• Higher transaction throughput and lower fees compared to Ethereum.

• Optimistic rollup technology for efficient data processing.

A conventional Web2 application relies on centralized servers, leading to risks such as downtime, censorship, and security vulnerabilities. By migrating to Web3, smart contract logic is executed on the Onyx blockchain, ensuring:

• Immutable business logic

• Decentralized data storage

• Trustless interactions between users

Example: Token Dispenser Implementation

We will first examine a JavaScript-based token dispenser and then implement its Web3 equivalent using Solidity.

Web2 Implementation:

Smart contracts need to be compiled into bytecode before they can be deployed on-chain. We will use Remix, a browser-based IDE, for this step.

1. Open Remix:

2. Create a new workspace.

3. Copy the Solidity contract into a new file.

4. Compile the contract in Remix.

Web3 Libraries and Tools for Onyx Development

Developers building on Onyx, an EVM-compatible Layer 3 blockchain, can leverage various libraries and SDKs to interact with smart contracts, manage wallets, and streamline blockchain development. Below is a list of essential frameworks for Web3 development on Onyx.

Essential Web3 Libraries and Tools

If you know of additional Web3 tools that would enhance Onyx development, please contribute by submitting suggestions via GitHub Issues

Efficient debugging is essential for Onyx developers to ensure the reliability and security of smart contracts. The following tool provides powerful debugging capabilities for smart contract development and testing.

Tenderly is a comprehensive Web3 development platform that supports smart contract development, testing, monitoring, and debugging. It enables developers to analyze precise lines of code in a human-readable format, making it easier to identify and resolve issues.

Key Features:

• Tenderly Debugger: Provides detailed analysis of smart contract execution, allowing developers to inspect transactions at a granular level.

• Transaction Simulator: Enables replaying historical transactions and simulating current transaction outcomes before sending them on-chain.

• Real-time Monitoring: Detects anomalies and unexpected behavior in smart contract execution.

While Tenderly is highly effective, debugging L1-to-L2 messages (Retryable Tickets) has certain limitations due to custom Geth errors. Developers should refer to Onyx documentation for specific debugging guidance regarding cross-layer transactions.

Contributing & Additional Debugging Tools

If you know of additional debugging tools that would enhance Onyx development, consider submitting suggestions via GitHub Issues.

GET: /voter/accounts

VoterAccountRequest

The Voter Accounts API retrieves information about all accounts that have participated in governance voting.

Request Parameters

The API returns a list of voter accounts, including participation details and governance influence.

Response Structure

Pagination metadata for the voter list.

A detailed structure representing voter participation metrics.

• Retrieving Voter Data: Use this endpoint to fetch detailed voting activity across governance participants.

• Sorting by Voting Influence: The rank field allows sorting of top governance participants.

• Monitoring Staked Influence: The chnStake field indicates the staked CHN backing each voter.

Terms of Service

Updated: March 1, 2023

The app.onyx.org website (the “Interface” or “App”) is an open-source and public website hosted on GitHub by Onyx DAO (“we”, “our”, or “us”). The Interface provides access to a decentralized protocol on the Ethereum blockchain that allows suppliers and borrowers of certain digital assets to participate in autonomous interest rate markets (the “Protocol”).

This Terms of Service Agreement (the “Agreement”) explains the terms and conditions by which you may access and use the Interface. You must read this Agreement carefully. By accessing or using the Interface, you signify that you have read, understand, and agree to be bound by this Agreement in its entirety. If you do not agree, you are not authorized to access or use the Interface.

1. Modification of this Agreement

We reserve the right, in our sole discretion, to modify this Agreement from time to time. If we make any modifications, we will notify you by updating the date at the top of the Agreement and by maintaining a current version of the Agreement at https://docs.onyx.org/terms-of-service. All modifications will be effective when they are posted, and your continued use of the Interface will serve as confirmation of your acceptance of those modifications. If you do not agree with any modifications to this Agreement, you must immediately stop accessing and using the Interface.

2. Eligibility

To access or use the Interface, you must be able to form a legally binding contract with us. Accordingly, you represent that you are at least eighteen years old and have the full right, power, and authority to enter into and comply with the terms and conditions of this Agreement on behalf of yourself and any company or legal entity for which you may access or use the Interface. You further represent that you are not a citizen, resident, or member of any jurisdiction or group that is subject to economic sanctions by the United States or the United Kingdom, or where your use of the Interface would be illegal or otherwise violate any applicable law. You further represent that your access and use of the Interface will fully comply with all applicable laws and regulations, and that you will not access or use the Interface to conduct, promote, or otherwise facilitate any illegal activity.

3. Proprietary Rights

We own all intellectual property and other rights in the Interface and its contents, including (but not limited to) software, text, images, trademarks, service marks, copyrights, patents, and designs. Unless expressly authorized by us, you may not copy, modify, adapt, rent, license, sell, publish, distribute, or otherwise permit any third party to access or use the Interface or any of its contents. Provided that you are eligible, you are hereby granted a single, personal, limited license to access and use the Interface. This license is non-exclusive, non-transferable, and freely revocable by us at any time without notice or cause. Use of the Interface or its contents for any purpose not expressly permitted by this Agreement is strictly prohibited. Unlike the Interface, the Protocol is comprised entirely of open-source software running on the public Ethereum blockchain and is not our proprietary property.

4. Privacy

We care about your privacy. Although we will comply with all valid subpoena requests, we will carefully consider each request to ensure that it comports with the spirit and letter of the law, and we will not hesitate to challenge invalid, overbroad, or unconstitutional requests as appropriate. We use commercially reasonable safeguards to preserve the integrity and security of your personally identifiable information (“PII”) and aggregate data. However, we cannot guarantee that unauthorized third parties will never be able to obtain or use your PII or aggregate data for improper purposes. You acknowledge that you provide your PII and aggregate data at your own risk. By accessing and using the Interface, you understand and consent to our collection, use, and disclosure of your PII and aggregate data.

5. Prohibited Activity

You agree not to engage in, or attempt to engage in, any of the following categories of prohibited activity in relation to your access and use of the Interface:

· Intellectual Property Infringement. Activity that infringes on or violates any copyright, trademark, service mark, patent, right of publicity, right of privacy, or other proprietary or intellectual property rights under the law.

· Cyberattack. Activity that seeks to interfere with or compromise the integrity, security, or proper functioning of any computer, server, network, personal device, or other information technology system, including (but not limited to) the deployment of viruses and denial of service attacks.

· Fraud and Misrepresentation. Activity that seeks to defraud us or any other person or entity, including (but not limited to) providing any false, inaccurate, or misleading information in order to unlawfully obtain the property of another.

· Market Manipulation. Activity that violates any applicable law, rule, or regulation concerning the integrity of trading markets, including (but not limited to) the manipulative tactics commonly known as spoofing and wash trading.

· Any Other Unlawful Conduct. Activity that violates any applicable law, rule, or regulation of the United States or another relevant jurisdiction, including (but not limited to) the restrictions and regulatory requirements imposed by U.S. law.

6. No Professional Advice

All information provided by the Interface is for informational purposes only and should not be construed as professional advice. You should not take, or refrain from taking, any action based on any information contained in the Interface. Before you make any financial, legal, or other decisions involving the Interface, you should seek independent professional advice from an individual who is licensed and qualified in the area for which such advice would be appropriate.

7. No Warranties

The Interface is provided on an “AS IS” and “AS AVAILABLE” basis. To the fullest extent permitted by law, we disclaim any representations and warranties of any kind, whether express, implied, or statutory, including (but not limited to) the warranties of merchantability and fitness for a particular purpose. You acknowledge and agree that your use of the Interface is at your own risk. We do not represent or warrant that access to the Interface will be continuous, uninterrupted, timely, or secure; that the information contained in the Interface will be accurate, reliable, complete, or current; or that the Interface will be free from errors, defects, viruses, or other harmful elements. No advice, information, or statement that we make should be treated as creating any warranty concerning the Interface. We do not endorse, guarantee, or assume responsibility for any advertisements, offers, or statements made by third parties concerning the Interface.

8. No Fiduciary Duties

This Agreement is not intended to, and does not, create or impose any fiduciary duties on us. To the fullest extent permitted by law, you acknowledge and agree that we owe no fiduciary duties or liabilities to you or any other party, and that to the extent any such duties or liabilities may exist at law or in equity, those duties and liabilities are hereby irrevocably disclaimed, waived, and eliminated. You further agree that the only duties and obligations that we owe you are those set out expressly in this Agreement.

9. Compliance Obligations

The Interface may not be available or appropriate for use in other jurisdictions. By accessing or using the Interface, you agree that you are solely and entirely responsible for compliance with all laws and regulations that may apply to you. You may not use the Interface if you are a citizen, resident, or member of any jurisdiction or group that is subject to economic sanctions by the United States of the United Kingdom, or if your use of the Interface would be illegal or otherwise violate any applicable law. The Interface and all of its contents are solely directed to individuals, companies, and other entities located within the United States or the United Kingdom.

10. Assumption of Risk

By accessing and using the Interface, you represent that you understand the inherent risks associated with using cryptographic and blockchain-based systems, and that you have a working knowledge of the usage and intricacies of digital assets such as bitcoin (BTC), ether (ETH), and other digital tokens such as those following the Ethereum Token Standard (ERC-20). You further understand that the markets for these digital assets are highly volatile due to factors including (but not limited to) adoption, speculation, technology, security, and regulation. You acknowledge that the cost and speed of transacting with cryptographic and blockchain-based systems such as Ethereum are variable and may increase dramatically at any time. You further acknowledge the risk that your digital assets may lose some or all of their value while they are supplied to the Protocol. If you borrow digital assets from the Protocol, you will have to supply digital assets of your own as collateral. If your collateral declines in value such that it is no longer sufficient to secure the amount that you borrowed, others may interact with the Protocol to seize your collateral in a liquidation event. You further acknowledge that we are not responsible for any of these variables or risks, do not own or control the Protocol, and cannot be held liable for any resulting losses that you experience while accessing or using the Interface. Accordingly, you understand and agree to assume full responsibility for all of the risks of accessing and using the Interface and interacting with the Protocol.

11. Third-Party Resources and Promotions

The Interface may contain references or links to third-party resources, including (but not limited to) information, materials, products, or services, that we do not own or control. In addition, third parties may offer promotions related to your access and use of the Interface. We do not endorse or assume any responsibility for any such resources or promotions. If you access any such resources or participate in any such promotions, you do so at your own risk, and you understand that this Agreement does not apply to your dealings or relationships with any third parties. You expressly relieve us of any and all liability arising from your use of any such resources or participation in any such promotions.

12. Release of Claims

You expressly agree that you assume all risks in connection with your access and use of the Interface and your interaction with the Protocol. You further expressly waive and release us from any and all liability, claims, causes of action, or damages arising from or in any way relating to your use of the Interface and your interaction with the Protocol. If you are a California resident, you waive the benefits and protections of California Civil Code § 1542, which provides: “[a] general release does not extend to claims that the creditor or releasing party does not know or suspect to exist in his or her favor at the time of executing the release and that, if known by him or her, would have materially affected his or her settlement with the debtor or released party.”

13. Indemnity

You agree to hold harmless, release, defend, and indemnify us and our officers, directors, employees, contractors, agents, affiliates, and subsidiaries from and against all claims, damages, obligations, losses, liabilities, costs, and expenses arising from: (a) your access and use of the Interface; (b) your violation of any term or condition of this Agreement, the right of any third party, or any other applicable law, rule, or regulation; and (c) any other party’s access and use of the Interface with your assistance or using any device or account that you own or control.

14. Limitation of Liability

Under no circumstances shall we or any of our officers, directors, employees, contractors, agents, affiliates, or subsidiaries be liable to you for any indirect, punitive, incidental, special, consequential, or exemplary damages, including (but not limited to) damages for loss of profits, goodwill, use, data, or other intangible property, arising out of or relating to any access or use of the Interface, nor will we be responsible for any damage, loss, or injury resulting from hacking, tampering, or other unauthorized access or use of the Interface or the information contained within it. We assume no liability or responsibility for any: (a) errors, mistakes, or inaccuracies of content; (b) personal injury or property damage, of any nature whatsoever, resulting from any access or use of the Interface; (c) unauthorized access or use of any secure server or database in our control, or the use of any information or data stored therein; (d) interruption or cessation of function related to the Interface; (e) bugs, viruses, trojan horses, or the like that may be transmitted to or through the Interface; (f) errors or omissions in, or loss or damage incurred as a result of the use of, any content made available through the Interface; and (g) the defamatory, offensive, or illegal conduct of any third party. Under no circumstances shall we or any of our officers, directors, employees, contractors, agents, affiliates, or subsidiaries be liable to you for any claims, proceedings, liabilities, obligations, damages, losses, or costs in an amount exceeding the amount you paid to us in exchange for access to and use of the Interface, or $100.00, whichever is greater. This limitation of liability applies regardless of whether the alleged liability is based on contract, tort, negligence, strict liability, or any other basis, and even if we have been advised of the possibility of such liability. Some jurisdictions do not allow the exclusion of certain warranties or the limitation or exclusion of certain liabilities and damages. Accordingly, some of the disclaimers and limitations set forth in this Agreement may not apply to you. This limitation of liability shall apply to the fullest extent permitted by law.

15. Dispute Resolution

We will use our best efforts to resolve any potential disputes through informal, good faith negotiations. If a potential dispute arises, you must contact us by sending an email to [email protected] so that we can attempt to resolve it without resorting to formal dispute resolution. If we aren’t able to reach an informal resolution within sixty days of your email, then you and we both agree to resolve the potential dispute according to the process set forth below.

Any claim or controversy arising out of or relating to the Interface, this Agreement, or any other acts or omissions for which you may contend that we are liable, including (but not limited to) any claim or controversy as to arbitrability (“Dispute”), shall be finally and exclusively settled by arbitration under the LCIA Arbitration Procedures. You understand that you are required to resolve all Disputes by binding arbitration. The arbitration shall be held on a confidential basis before a single arbitrator, who shall be selected pursuant to LCIA rules. The arbitration will be held in London, United Kingdom, unless you and we both agree to hold it elsewhere. Unless we agree otherwise, the arbitrator may not consolidate your claims with those of any other party. Any judgment on the award rendered by the arbitrator may be entered in any court of competent jurisdiction.

16. Class Action and Jury Trial Waiver

You must bring any and all Disputes against us in your individual capacity and not as a plaintiff in or member of any purported class action, collective action, private attorney general action, or other representative proceeding. This provision applies to class arbitration. You and we both agree to waive the right to demand a trial by jury.

17. Governing Law

You agree that the laws of the London, United Kingdom without regard to principles of conflict of laws, including criminal or civil, that govern this Agreement and any Dispute between you and us. You further agree that the Interface shall be deemed to be based solely in London, United Kingdom, and that although the Interface may be available in other jurisdictions, its availability does not give rise to general or specific personal jurisdiction in any forum outside of London. Any arbitration conducted pursuant to this Agreement shall be governed by the LICA Arbitration procedures. You agree that London is the proper forum for any appeals of an arbitration award or for court proceedings in the event that this Agreement’s binding arbitration clause is found to be unenforceable.

GET: /voter/:proposalId

VoterProposalRequest

The request to the Voter Proposal API allows filtering by specific accounts and voting support status.

Request Parameters

The API returns a list of voters who participated in the specified proposal, along with their vote details.

Response Structure

Pagination and summary metadata for the voter list.

A detailed structure representing a voter's participation in a governance proposal.

• Retrieving Voter Data: Use this endpoint to fetch detailed information on voters participating in a given proposal.

• Filtering by Support Status: The support parameter allows querying for supporting or opposing votes.

• Tracking Voting Trends: The sumVotes metadata field provides a total count of votes cast.