Benqi vs HAL (formerly NapBots)

Benqi operates two foundational product lines natively on Avalanche: Benqi Liquid Staking (BLS) and the Benqi Liquidity Market (BLM). Through the liquid staking interface, participants deposit native AVAX into staking contracts to mint sAVAX. The sAVAX token automatically accumulates validator staking rewards by appreciating in value relative to AVAX over time, removing the need for manual reward claims while allowing holders to transfer, trade, or collateralize their staked balance across external decentralized finance protocols.

Alongside liquid staking, Benqi provides non-custodial money markets patterned after algorithmic pool structures. Users supply assets such as AVAX, sAVAX, wrapped Bitcoin, wrapped Ethereum, and leading stablecoins including USDC and USDT to earn variable interest funded by borrowers. Suppliers receive interest-bearing qiTokens representing their proportional share of the underlying liquidity pool. Borrowers can then draw overcollateralized loans against their supplied collateral balance, paying floating interest rates determined mathematically by supply and demand utilization curves within each individual asset reserve.

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.

Engaging with Benqi involves several distinct protocol-level and network-level costs rather than traditional commercial account fees. On the liquid staking side, Benqi applies a protocol fee deducted directly from incoming validator staking rewards prior to distribution, funding protocol development and reserve management. When minting sAVAX or redeeming back to AVAX, transactions incur Avalanche C-Chain network gas fees settled in AVAX, which fluctuate based on prevailing blockchain congestion levels.

In the Benqi Liquidity Market, suppliers and borrowers encounter variable interest rate models. Borrowers pay annualized interest rates that escalate as pool utilization rises, while a reserve factor percentage is directed to protocol reserves. Unstaking sAVAX through the native redemption queue involves an unbonding period dictated by Avalanche network consensus validation cycles. Alternatively, users requiring immediate liquidity can trade sAVAX for AVAX on decentralized exchanges, though this route exposes traders to market spreads, liquidity pool depth limits, and decentralized exchange swap fees.

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.

Benqi operates on a fully non-custodial framework where users retain direct ownership of their private keys throughout every interaction. Connecting to the protocol occurs via self-custody Web3 wallets such as Core, MetaMask, or hardware-linked wallet software. Assets deposited into the money market or liquid staking contracts are governed entirely by programmatic code on the Avalanche C-Chain, meaning no centralized custodian or corporate entity holds administrative custody over user balances.

Protocol security relies on automated smart contracts, multi-signature governance frameworks, and third-party security audits conducted by external blockchain security firms. Price feeds for lending valuations and liquidation calculations are supplied by decentralized oracle networks such as Chainlink. Users must actively manage their health factor metrics within the interface, as collateral balances are subject to automated partial liquidation by independent keeper bots if market price swings push account health below required collateralization thresholds.

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.

Because Benqi is deployed as permissionless smart contracts on the public Avalanche blockchain, the underlying protocol is accessible globally to anyone with an internet connection, a compatible Web3 wallet, and network gas tokens. The decentralized nature of the application removes traditional banking onboarding hurdles, credit checks, and identity verification requirements. However, regulatory restrictions may apply to front-end hosted interfaces in specific geographic regions, leading some users to interact through alternative nodes or decentralized front-ends.

Governance of protocol parameters, supported collateral tiers, and reserve factors is driven through the native QI governance token and community snapshot votes. Customer support follows a decentralized model rather than a corporate helpdesk format. Assistance is available primarily through community documentation, developer GitHub repositories, and official community chat servers on Discord and Telegram, where moderators provide technical guidance regarding interface connectivity, contract interactions, and documentation interpretation.

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.

When depositing 100 AVAX into Benqi Liquid Staking, the user receives an equivalent value of sAVAX based on the prevailing exchange rate. Staking rewards accumulate continuously into the token exchange ratio over time. If the user decides to exit through the native protocol queue, they wait the standard unbonding duration without trading fees, paying only the final withdrawal gas transaction in native AVAX.

If the user instead swaps 100 sAVAX on a decentralized exchange during periods of market volatility, they bypass the multi-day unbonding cooldown in exchange for paying prevailing decentralized exchange liquidity pool fees and absorbing minor price impact spreads. For money market borrowers, borrowing costs fluctuate dynamically based on pool utilization rates, where higher asset utilization increases the annualized interest rate charged on notable loan balances.

Evaluating total operational expenses on HAL requires combining the fixed software subscription fee with variable exchange transaction costs. For example, a user running an active trend strategy on an exchange with standard maker or taker commissions incurs charges on every algorithmic rebalance. If the strategy triggers frequent order adjustments during choppy market phases, accumulated exchange transaction fees alongside the monthly software plan charge can impact net trading balances. Factoring in potential bid-ask spread costs across varying liquidity pools helps maintain a realistic perspective on net software overhead. Users operating with modest capital must verify that expected trade frequencies do not generate cumulative fees that outweigh their planned trading allocations.