Arkham vs HAL (formerly NapBots)

Arkham functions as an on-chain analytics and portfolio intelligence engine designed to deanonymize and aggregate public ledger transactions. The core platform ingests raw block data from major networks including Bitcoin, Ethereum, Arbitrum, Polygon, Avalanche, Optimism, Solana, and TRON, organizing fragmented wallet clusters into identifiable entity dossiers. These profiles span centralized exchanges, market makers, hedge funds, decentralized finance protocols, and prominent individual figures. Users can track composite token holdings, evaluate historical balance trajectories, and examine specific asset inflows across supported ecosystems.

The visual transaction graph, known as the Arkham Visualizer, maps relationships between source addresses, intermediary routing contracts, and destination wallets. Traders and researchers can construct custom dashboards that filter transactions by nominal token value, asset type, timestamp, or protocol category. Additionally, Arkham supports public token contract telemetry, displaying liquidity pools, top token holders, and contract deployer addresses. This depth facilitates rigorous forensic tracking, counterparty risk assessment, and protocol balance monitoring across fragmented distributed environments.

HAL functions strictly as a strategy automation software layer rather than a direct brokerage or trading venue. The core offering centres on ready-to-use algorithmic models that dynamically allocate capital across major cryptocurrencies such as Bitcoin, Ethereum, and selected liquid altcoins. These strategies range from trend-following systems designed to capture sustained market direction to mean-reversion and allocation models that rebalance between crypto assets and stablecoins during market pullbacks. Users do not need to write Python code or build custom indicator triggers from scratch, as the platform curates and maintains the underlying mathematical rules.

Connectivity relies on external exchange APIs, linking user accounts on platforms like Binance, Kraken, Bitstamp, and Bitfinex. Because HAL does not maintain its own order books or internal matching engine, asset availability matches the spot and derivative pairs listed on your linked exchange. The platform interface allows users to allocate specific capital amounts to distinct strategies, enabling multi-strategy distribution within a single connected exchange portfolio. However, flexibility is focused on strategy selection and allocation percentages rather than modular script development, making it less suitable for traders who require complex bespoke indicators or tick-level algorithmic customization.

Access to the primary Arkham web intelligence platform, standard entity search, visualizer graphing tools, and standard transaction alert setups is structured without mandatory recurring consumer subscription tiers. Users register an account to configure custom dashboards, set threshold alerts via email or webhooks, and query indexed addresses across supported blockchains. Because the core tracking portal operates as an informational data interface rather than a trading venue or asset custodian, it does not charge transaction spreads, asset deposit fees, or network withdrawal surcharges.

For enterprise institutions requiring high-throughput API endpoints, tailored attribution pipelines, and low-latency programmatic access, Arkham arranges commercial data agreements. The network also utilizes the native ARKM utility token within its broader intelligence marketplace ecosystem, where users submit bounties or acquire exclusive analytical intelligence. Platform revenue stems from institutional licensing, commercial partnerships, and affiliated operational services. Retail analysts monitoring public wallet portfolios encounter minimal direct overhead, making the software accessible for routine on-chain research.

HAL operates on a software-as-a-service model with tiered monthly subscription pricing rather than charging performance fees or taking a percentage cut of trading profits. Pricing tiers have traditionally scaled based on trading volume limits, active strategy counts, or capital allocation caps. Users pay this recurring software fee directly via credit card or supported crypto payment routes to maintain active strategy triggers. Because HAL does not manage internal custody or execution, there are no internal deposit or withdrawal fees charged by the platform itself, and capital remains within the user exchange account at all times.

Traders must account for secondary execution costs generated by their linked exchange. Every trade executed by HAL triggers standard maker or taker fees on the underlying platform, which fluctuate according to the exchange fee schedule and the user tier. High-frequency or active rebalancing strategies generate a higher volume of transactions, accumulating exchange commission costs and potential bid-ask slippage. These exchange expenses exist alongside HAL monthly subscription fees, meaning smaller capital allocations can experience significant performance drag if monthly software costs represent a large percentage of total deployed trading funds.

Arkham maintains a non-custodial operational model for its intelligence and portfolio tracking application. Users never upload private keys, grant seed phrases, or provide custodial account authorization to track wallet balances or view transaction flows. All portfolio calculations derive entirely from public blockchain data indexed by Arkham's parsing infrastructure. This architecture prevents protocol-level asset compromise within the analytics suite, as the platform cannot initiate transfers or alter on-chain smart contract state.

Account security for the web application is managed through standard access controls, including encrypted authentication credentials, session monitoring, and multi-factor verification options. Users tracking specific internal wallets or configuring private counterparty tags manage those settings under isolated user accounts. While Arkham employs automated clustering algorithms to associate anonymous addresses with real-world organizations, identity labels remain analytical attributions subject to algorithm updates and manual verification adjustments. The platform does not claim absolute protection against tracking errors, making dual verification prudent for critical operational compliance workflows.

The security model of HAL relies entirely on non-custodial API architecture. When onboarding, users generate API keys within their chosen exchange account and enter them into the HAL dashboard. To protect exchange balances, the platform explicitly requires users to restrict API permissions to read and trade access only. Users must disable withdrawal permissions on their exchange API settings, ensuring that HAL algorithms have no technical capability to transfer or withdraw funds from the external account.

Account protection on HAL includes standard security practices such as two-factor authentication for dashboard logins, encrypted storage of API credentials, and transport layer security across data transmissions. While non-custodial operation reduces direct custody risk on the automation platform, users remain exposed to exchange-side risks, including API key compromise, exchange downtime, and order routing errors during periods of severe market volatility. Users should regularly review API key expiration policies, monitor active strategy permissions, and utilize IP whitelisting where supported by their exchange to maintain tight operational security boundaries.

The Arkham intelligence interface is accessible globally across modern web browsers without standard geographical restrictions for read-only blockchain queries. Users must agree to standard terms of service that prohibit malicious scraping, distributed denial-of-service attempts, and platform abuse. Because the core product provides informational analytics on public ledger transactions, general access does not require standard financial identity verification. However, distinct affiliated products or associated trading ventures may impose regional eligibility boundaries and compliance screening under applicable local jurisdictions.

Customer assistance is delivered primarily through documentation portals, community discussion channels, developer resources, and direct support ticketing. Response times vary depending on query complexity, with enterprise API clients receiving prioritized technical routing under specific service terms. The documentation outlines query syntax, visualizer controls, and alert payload configurations, helping researchers optimize their monitoring pipelines. For general users, community forums and official knowledge bases serve as the primary resource for troubleshooting dashboard views or addressing balance discrepancy reports.

HAL is accessible globally as a software tool, though user eligibility is inherently bound by the geographic restrictions and regulatory policies of the underlying linked exchanges. Users residing in jurisdictions where specific exchanges restrict operations, such as certain regions of the United States or restricted FATF jurisdictions, cannot connect to those platforms through HAL. Because HAL provides automated software tools rather than acting as a custodial broker, fiduciary adviser, or asset manager, it does not execute individualized suitability reviews or provide tailored financial advice.

Customer support is primarily delivered through online ticketing, knowledge base documentation, and community channels. The help centre covers foundational onboarding procedures, including step-by-step guides for generating API keys, allocating capital to bots, and troubleshooting connection timeouts. Response times follow standard software support workflows, with inquiries handled during business hours. Traders requiring immediate phone support or dedicated institutional account representatives may find the self-service model basic, reinforcing the need for users to familiarize themselves with bot management and exchange controls independently.

Entity attribution relies on proprietary machine learning models, public registry records, transaction clustering heuristics, and verified operational disclosures. While address clustering offers valuable market intelligence, the underlying algorithmic calculations remain probabilistic and are not infallible. Smart contract proxies, shared multi-signature setups, privacy pools, and dynamic exchange deposit addresses can occasionally lead to misattribution or temporary reporting delays. Organizations utilizing this platform for compliance screening or risk mitigation must recognize that Arkham provides analytical intelligence rather than definitive legal records. Teams should implement secondary verification processes before executing decisive operational, legal, or financial actions based on on-chain labels. Furthermore, platform metrics reflect public ledger state updates and may experience short latency intervals during periods of intense blockchain network congestion.

Automated trading strategies carry intrinsic market and technological risks that participants must monitor carefully. Algorithmic models rely on historical mathematical patterns that may underperform during unprecedented market regimes, sudden liquidity drops, or extreme volatility spikes. Furthermore, exchange API rate limits or network latency can result in delayed order routing, leading to slippage between theoretical strategy triggers and actual exchange fill prices. HAL does not assurance positive trading outcomes or eliminate market downside under any circumstances. Users must establish prudent stop-loss boundaries, maintain appropriate strategy diversification, and periodically verify API connection stability across all connected trading venues to manage operational exposure.