Orixa Features: A Complete Guide to Token Safety Analysis

What Orixa is designed to do

Orixa brings several kinds of token-security evidence into one workflow. Its current product is built around a shared Decision Pipeline: the scan interface, stored history, monitoring views, alerts, and PDF reports use the same final decision instead of calculating unrelated conclusions in each screen.

This guide describes capabilities that are present in the current application. Provider coverage can vary by network, token, plan, and configuration.

Contract analysis

For supported EVM tokens, Orixa can evaluate contract evidence including source verification, ownership state, minting controls, blacklist or trading controls, proxy behavior, and sell-simulation or honeypot findings when a compatible provider returns them. Solana analysis uses mint and freeze-authority evidence rather than pretending an SPL token is an EVM contract.

The report distinguishes a confirmed negative signal from unavailable data. That distinction matters: “not detected” and “not checked” are not equivalent.

Liquidity and market structure

The scanner can use DEX pair data to show liquidity, price, volume, market value, and pair context when available. The decision process considers liquidity weakness and sudden changes alongside other evidence. Orixa monitoring stores periodic snapshots so changes can be surfaced later rather than treating one scan as permanent.

Liquidity figures are provider snapshots. Pool selection, multi-pool fragmentation, stale indexing, and rapid transactions can affect what is visible at a particular moment.

Holder and whale analysis

Where the network and configured sources permit, Orixa examines top-holder concentration and large-wallet flow. This helps identify whether a small number of wallets could materially influence supply or market conditions.

The interface does not assume every large address is a hostile whale. Burn addresses, exchange wallets, bridges, vesting contracts, treasuries, and liquidity pools need contextual labels. Users should confirm large addresses in a blockchain explorer.

Taxes and sellability

Orixa surfaces buy, sell, and transfer tax evidence when it is reported or simulated by a source. Independent honeypot checks are available only on networks supported by the current provider integration. A successful simulation is useful evidence but not a lifetime guarantee: owner-controlled settings or upgradeable implementations can change later.

Risk Score, Rug Probability, and Confidence

The Risk Score summarizes the severity of the final decision. Rug Probability estimates rug-like failure risk. Confidence describes the strength and coverage of the supporting evidence. These values are presented together because a score without evidence quality can be misleading.

The detailed report also shows Top Reasons and a Recommended Action. They are derived from the final pipeline decision and are intended to explain the result in plain language.

Data-source transparency

Orixa exposes provider state rather than silently treating failures as safe outcomes. EVM scans can use GoPlus, Moralis, the relevant EVM explorer, DEX Screener, and Honeypot.is on supported networks. Additional configured market sources may contribute evidence. Solana scans can use GoPlus’s Solana endpoint, Solana RPC, RugCheck, DEX Screener, and optional Birdeye flow data.

If a source is degraded or unavailable, coverage is reduced. The appropriate response is to seek independent confirmation, not to infer safety from an empty field.

PDF reports

The current application can generate a PDF from an analysis result. The PDF is useful for a portable snapshot, review, or internal documentation. It does not remain live after download; time-sensitive data should be rechecked in the product.

Watchlist and monitoring

Authenticated users can add tokens to a watchlist. The product stores token snapshots and events that support a risk timeline, latest change, monitoring status, and current recommendation. Monitoring is especially valuable for owner actions, liquidity movement, concentration changes, and other facts that can change after an initial scan.

Monitoring frequency and retained history can depend on plan entitlements and production worker availability.

Alerts and notifications

Users can create per-token alert rules with an event type, severity, language, channel, and optional delivery target. Current alert workflows include pausing and resuming rules, editing them, test notifications, delivery history, retrying failed deliveries, and grouping rules by token.

Notifications are designed to answer both what changed and why it changed when the stored evidence contains an explanation. Alerts do not replace direct verification of a critical event.

History, dashboard, and exploration

Scan History provides a user-scoped record of previous scans. The Dashboard prioritizes items that may require attention, including watched tokens that became riskier and failed alert deliveries. Explore surfaces discoverable token activity from configured market sources; it is not a recommendation list.

Supported networks

The scan interface currently lists:

• Ethereum
• BNB Chain
• Polygon
• Arbitrum
• Base
• Optimism
• Avalanche
• Solana

Some tools are EVM-only, and some providers support only a subset of those networks. Orixa reports the coverage available for the selected token rather than claiming every check runs everywhere.

What Orixa does not promise

Orixa is not a formal smart-contract audit, a guarantee that a token is safe, or financial advice. Automated analysis can miss novel logic, off-chain deception, compromised team accounts, governance attacks, delayed malicious changes, or market manipulation that has not yet produced visible evidence.

Use Orixa to organize due diligence: confirm the address, review the decision and reasons, inspect missing coverage, cross-check critical claims, and monitor changes when continued exposure matters.