A verified-participant lending market on Hemi.
BNQ is a non-custodial money market: verified users supply crypto to earn interest and borrow against collateral. The lending engine is unmodified Aave v3; BNQ adds a soulbound access layer and a fail-closed price oracle.
What is BNQ
BNQ is a permissioned lending market — a decentralized, non-custodial protocol where verified users supply assets to earn interest and borrow against their collateral. BNQ never holds user funds; all positions live in smart contracts on-chain.
Built on Aave v3
The lending engine — interest-bearing bnq-Tokens, debt tokens, interest-rate curves, health factors and liquidation mathematics — is Aave v3, one of the most widely used and audited protocols in DeFi. BNQ does not modify the core lending logic. What BNQ adds is an access layer:
- Every protocol action (supply, borrow, liquidate, flash loan) requires the caller to hold a matching access token — a non-transferable, on-chain "soulbound token" (SBT) issued per wallet after verification.
- Access tokens cannot be bought, sold, or moved. They attest that a specific wallet has been verified for a specific market.
- The permission gates can be opened per action class by governance if BNQ later transitions parts of the market to permissionless operation.
Why permissioned?
A verified-participant market enables use cases open pools cannot serve: institutional participation with counterparty assurances, jurisdictional compliance, and curated asset listings — while remaining fully non-custodial.
BNQ launches on Hemi mainnet (chain id 43111), an EVM network that settles to Bitcoin and Ethereum. The BTC-adjacent asset set reflects that focus.
Getting access
Before you can supply or borrow, your wallet must hold the matching access tokens. The app walks you through this the first time you connect — it is a real, ordered sequence:
- Connect your wallet. The app detects you don't yet hold access tokens and shows the Verify your wallet dialog.
- Sign one message. An off-chain signature — free, no gas, and it authorizes no transaction or spending. It only proves you control the wallet. The message lists the grants requested, the chain id, and a timestamp.
- The issuer mints your access tokens. BNQ's issuer verifies the signature (wallet, requested grants, message age, replay guard) and mints your SBTs on-chain in a few seconds. BNQ pays the gas.
- Done. The market loads and you can supply and borrow. You never repeat this unless new assets are listed.
Revocation
An access token for an asset in which you hold an active position cannot be revoked through the standard path — the contract checks your balances first, so routine administration can never strand your funds. A separate emergency revocation power exists for compliance cases, restricted to the protocol admin (a multisig) and logged on-chain. See Risks & FAQ for a frank discussion.
Using the market
BNQ works like Aave v3. If you've used Aave, everything here is familiar.
Supplying
Deposit a listed asset and receive bnq-Tokens (e.g. bnqHemiWETH) 1:1. They grow in balance as interest accrues — paid by borrowers of that asset. Withdraw any time, as long as your remaining collateral still covers your debts and liquidity allows. Only assets flagged as collateral count toward borrowing power.
Borrowing
With collateral supplied, you can borrow any borrow-enabled asset up to your borrowing power = Σ (collateral value × that asset's Max LTV). Every position has a health factor (HF):
- HF > 1 position is safe.
- HF ≤ 1 position can be liquidated.
Borrow interest is variable, driven by each asset's utilization. Stable-rate borrowing is disabled protocol-wide (deprecated upstream by Aave after its 2023 incident).
Restricted assets. Some assets can be supplied and used as collateral by every verified member but borrowed only by members who have been approved for that specific asset (an additional AssetBorrower access token, granted per wallet and per asset by BNQ). HEMI is treated this way so that the market cannot be used to short the network token at scale. A restricted asset simply does not appear in your borrow list until you are approved; supplying, withdrawing and repaying it are never affected.
Liquidations
If your HF falls to 1 or below, a liquidator repays part of your debt and receives collateral worth the repaid amount plus a liquidation penalty. Between HF 0.95 and 1, at most 50% of a position can be closed per liquidation; below 0.95, up to 100%. On BNQ, liquidation is a permissioned role executed by a monitored service that scans positions continuously — not an open bot market.
Avoiding liquidation: keep a buffer — repay debt or add collateral as your HF approaches ~1.1. Price moves on volatile collateral can be fast.
Flash loans
The protocol supports Aave-style flash loans, but they are disabled at launch on every reserve and additionally gated by a FlashLoaner access token. If enabled later, the premium is 0.05%.
Markets & risk parameters
Eight reserves are live on Hemi mainnet, and a ninth (msUSD) is listed but frozen. Parameters reflect the current on-chain configuration; the authoritative source is the PoolConfigurator state.
| Asset | Collateral | Borrowable | Max LTV | Liq. threshold | Liq. penalty |
|---|---|---|---|---|---|
| hemiBTC | Yes | Yes | 73% | 78% | 10% |
| WBTC | Yes | Yes | 73% | 78% | 10% |
| WETH | Yes | Yes | 75% | 80% | 10% |
| USDT | Yes | Yes | 75% | 78% | 10% |
| USDC.e | Yes | Yes | 75% | 78% | 10% |
| HEMI | Yes | Yes | 11.11% | 15% | 10% |
| VUSD | Yes | Yes | 75% | 78% | 10% |
| sVUSD | Isolated | No | 75% | 78% | 10% |
HEMI at 9:1. HEMI is accepted as collateral at a deliberately conservative ratio — roughly 9 units of HEMI value per 1 unit borrowed (Max LTV 11.11%) — reflecting its volatility and market depth. HEMI can also be borrowed.
sVUSD in isolation mode. sVUSD is collateral-only and isolated: a position using it as collateral can borrow only isolation-eligible assets, and total debt against sVUSD collateral is capped at $1,000.
Interest rate model
Borrow rates are variable and rise with utilization. Below the optimal point they climb gently; above it, steeply, to attract liquidity back.
| Curve | Assets | Optimal utilization | Rate at optimal |
|---|---|---|---|
| Stablecoin | USDC.e, USDT, VUSD | 75% | 4.5% |
| Volatile | hemiBTC, WBTC, WETH, HEMI | 75% | 2.5% |
Supply & borrow caps
Every reserve launches capped, and caps are raised as liquidity forms. Current on-chain values (supply / borrow): hemiBTC and WBTC 25 / 3 each; WETH 500 / 150; USDC.e 2,000,000 / 1,500,000; USDT 1,000,000 / 750,000; VUSD 5,000 / 2,500; sVUSD 25 supply; HEMI 20,000,000 supply.
Frozen and planned assets: msUSD is listed but frozen while it trades below its peg: no new supply or borrowing, while withdrawals and repayments stay open. svetBTC and Beefy VUSD/crvUSD are configured but remain unlisted until each has an independently verified price feed on Hemi.
Oracles
BNQ's price infrastructure is designed to halt rather than misprice: if no sufficiently fresh price is available for an asset, reads revert and that asset's market pauses until a fresh price returns.
Price resolution order
- RedStone push feeds — primary. On-chain Chainlink-compatible feeds updated on a 0.5% deviation or at least every 6 hours.
- BNQ backstop feeds — second source. One BNQ-operated on-chain feed per asset, posted from a median of independent public market data (exchanges and aggregators, see the table). When both sources are fresh they must agree within the asset's divergence bound (2%, HEMI 5%) or the asset halts. If the primary is missing or stale, the backstop serves alone under the same freshness bound.
- Staleness halt — any price older than 8 hours is rejected. If no tier can serve a fresh price, pricing-dependent actions for that asset revert until feeds recover.
Feed assignment per asset
| Asset | Primary source | Second source (BNQ backstop feed, median of) |
|---|---|---|
| hemiBTC, WBTC | RedStone BTC/USD | Coinbase, Kraken, Binance |
| WETH | RedStone ETH/USD | Coinbase, Kraken, Binance |
| USDC.e | RedStone USDC/USD | Coinbase, Kraken |
| USDT | RedStone USDT/USD | Coinbase, Kraken |
| HEMI | RedStone HEMI/USD | Binance, Gate.io, MEXC, CoinGecko |
| VUSD | Vetro push oracle VUSD/USD | CoinGecko, DefiLlama (Hemi and Ethereum) |
| sVUSD | Vetro push oracle sVUSD/USD | VUSD backstop × Ethereum sVUSD vault share rate |
| msUSD (frozen) | BNQ feed: CoinGecko + DefiLlama median (no third-party feed exists on Hemi) | BNQ feed: on-chain msUSD/USDC spot from Aerodrome (Base) and Velodrome (Optimism) |
Disclosure: hemiBTC and WBTC share the BTC/USD feed. A de-peg of one wrapper relative to native BTC would not be reflected in its price. Supply caps on these assets are sized with this in mind.
BNQ-operated feeds
The backstop feeds are BNQ-operated on-chain feed contracts with safety enforced by the contract itself, not by trust in the updater: hard owner-set min/max price bounds, a per-update deviation cap (5%, or 10% for BTC-denominated assets), and fail-closed staleness. A malfunctioning or compromised updater cannot teleport a price. Re-anchoring after a large legitimate move requires the protocol admin (multisig) after human review. The updater re-posts whenever a price moves 0.5% and on a regular heartbeat; if it stops, the feed goes stale and the asset halts under the 8-hour rule above.
Why BNQ runs its own second source. Pyth Network was the original backstop. Its price service stopped serving Hemi in August 2026, which left the cross-check with nothing to compare against, so BNQ replaced it with these feeds. BNQ intends to retire them in favour of independent third-party second sources (eOracle, Stork, or Pyth if it returns to Hemi) as they become available.
Fees
BNQ charges no deposit, withdrawal, or account fees. Protocol revenue comes from three standard Aave v3 mechanics.
Reserve factor
A share of borrower interest goes to the protocol treasury; the rest goes to suppliers.
| Assets | Reserve factor |
|---|---|
| Stablecoins (USDC.e, USDT, VUSD, sVUSD, msUSD) | 10% |
| BTC (hemiBTC, WBTC) | 20% |
| WETH | 15% |
| HEMI | 10% |
Liquidation protocol fee
When a position is liquidated, the liquidator receives the liquidation penalty; 10% of that penalty goes to the protocol treasury.
Flash loan premium
Flash loans are disabled at launch. If enabled, the premium is 0.05% of the loaned amount (0.04% to the protocol, 0.01% to suppliers).
Security & audits
BNQ's security posture rests on three pillars: an extensively audited foundation, a small and fully disclosed modification surface, and fail-closed operational design.
Audited foundation
The Aave v3 lending engine, secured by eleven third-party audit and formal-verification reports.
Disclosed surface
~1,550 lines of BNQ-specific Solidity, fully documented — no hidden changes to lending math.
Fail-closed design
No fresh price ⇒ the asset halts. Caps bound exposure. Reserves stay frozen until feeds prove out.
Inherited audits — the Aave v3 lending engine
BNQ's lending engine is Aave v3, unmodified in its core logic. aTokens, debt tokens, interest-rate strategies, and health-factor/liquidation mathematics are exactly the audited upstream code, which has secured tens of billions of dollars under these reports:
| Date | Auditor | Scope | Report |
|---|---|---|---|
| Nov 2021 | OpenZeppelin | Aave v3 core | Published |
| Jan 2022 | Trail of Bits | Aave v3 core | Published |
| Jan 2022 | ABDK | Aave v3 core | Published |
| Jan 2022 | PeckShield | Aave v3 core | Published |
| Jan 2022 | Sigma Prime | Aave v3 core | Published |
| Dec 2022 | PeckShield | Aave v3.0.1 | Published |
| Dec 2022 | Sigma Prime | Aave v3.0.1 | Published |
| Apr 2023 | Sigma Prime | Aave v3.0.2 | Published |
| Jan 2022 | Certora | Formal verification | Published |
| Dec 2022 | Certora | Formal verification v3.0.1 | Published |
| Mar 2023 | Certora | Formal verification v3.0.2 | Published |
Full report PDFs are distributed with the BNQ documentation package and are available from each auditor and the Aave protocol's published audit set. Stable-rate borrowing — the subject of Aave's 2023 incident and later removed upstream — is disabled on every BNQ reserve.
BNQ modifications — what we changed, exactly
The audits above do not cover BNQ's additions. In the interest of full transparency, this is the complete modification surface:
SoulBoundToken
Non-transferable ERC-721-based access token. Roles: Member (supply+borrow), Liquidator, FlashLoaner, and AssetBorrower (per-asset borrow approval for restricted assets such as HEMI). Revoking a Member token with an open position is blocked on-chain; an emergency admin path is multisig-gated. UUPS-upgradeable by the admin.
PermissionedLendingPool
Extends the Aave v3 Pool: every user action checks the caller's access token. Four per-action-class gates can open the market to permissionless operation by governance. No lending math is modified.
AaveOracle (modified)
Adds RedStone (Chainlink-compatible) sources as the primary tier with a staleness threshold, a bounded second source (the BNQ backstop feeds) that is cross-checked against the primary, and fail-closed behavior: no fresh price, or sources that disagree ⇒ the asset halts.
BNQPriceFeed
BNQ-operated AggregatorV3-compatible feed: the second source for every asset, and the only source for msUSD. Hard min/max bounds, per-update deviation cap (5–10%), owner-only re-anchoring, two-step ownership.
Responsible disclosure
If you believe you've found a vulnerability, please contact the BNQ security team at the address published on the official BNQ site — do not open a public issue. Good-faith reports are appreciated and will be acknowledged.
Contract addresses
Hemi mainnet (chain id 43111). Verified against the live deployment on 2026-11-03. Explorer: explorer.hemi.xyz. The previous market (Pool 0xefAA24d6…) is retired and withdraw-only; do not use its addresses.
Core protocol
| Contract | Address |
|---|---|
| PoolAddressesProvider | 0x381D905bA4bc8378E09A910b4EDbC763A0F2dc92 |
| Pool (proxy, user entry point) | 0x5af1BaC695d38D6769EC4A6d031776C8A6AB0e1d |
| Pool implementation | 0xa9325fC16bb588FE096298CFd9c86eC3Dd5c5283 |
| PoolConfigurator (proxy) | 0xb7E0408DB9963b4Cddeb9680C1d6b7C6299b7d18 |
| PoolConfigurator implementation | 0xA989233904487184AE66d0fD4B550a27B3eCC173 |
| ACLManager | 0xACA0D936909Bf7fFD6eBC581b9e1E0b60156d5a5 |
| PoolDataProvider | 0xB3D711832d1cf0F03D34D74d8a560071d52319a3 |
| Protocol oracle (AaveOracle) | 0x4E2B7848c717EFa31f3aE2cbFa18720e8A95C835 |
| Backstop price adapter (second oracle tier) | 0x11062fA6802B6469816C00E099420cA4f9842b36 |
| Access token (SoulBoundToken, proxy) | 0xF2AD206F2e30EA84DB48FA318effbf01609DC594 |
| SoulBoundToken implementation | 0x996E61a10B53e148F785C481867f2bD73B6e86e5 |
Helpers and periphery
| Contract | Address |
|---|---|
| WrappedTokenGatewayV3 (native ETH in and out) | 0x01EE51EBA2357482236Cd8788E67384bD104d9A4 |
| UiPoolDataProvider | 0xE1C706ca537D8eA9Fbac01577263902202E6D66D |
| UiIncentiveDataProvider | 0xa6ECFc126989baef4C9Ceb4F0f651DCC582460a3 |
| WalletBalanceProvider | 0xDeA543D5d2F4326A3e320FF9B929C3278170AE8f |
Rewards and treasury
| Contract | Address |
|---|---|
| RewardsController (IncentivesProxy) | 0x1b2D9db57424C6909C48faa224EB032C029e0b55 |
| RewardsController implementation | 0x81F65BF02Bc495AAD74d374393e59B220515eddB |
| EmissionManager | 0x4A33022D0B08D2B3F0366cd4cC21200674C6e03b |
| Treasury (Collector proxy, receives reserve-factor fees) | 0x59111972B64aBcB302ddEeD77B67837c0339a2C5 |
| Treasury implementation | 0x4623bDFBCfF47d58C16145C9AF6D41cC82067Ae5 |
| Treasury controller | 0x1335790F941cAF7a6835B2ceDA63bCe387223fBE |
Listed assets
Nine reserves. Stable-rate borrowing is disabled on every reserve, so only the bnq-Token (aToken) and the variable-debt token are in use.
| Asset | Underlying token | bnq-Token (aToken) | Variable debt token |
|---|---|---|---|
| hemiBTC | 0xAA40c0c7644e0b2B224509571e10ad20d9C4ef28 | 0x28B52ca791af19241D3D1f2E0Dd1Eb1d65C92bbb | 0xC4Bb3B8c61C41D483464fAe27968d0A95b3E4FA2 |
| WBTC | 0x03C7054BCB39f7b2e5B2c7AcB37583e32D70Cfa3 | 0x9A6026fFcbCf0918BDA5F749Bb2b80511389D841 | 0x5908395c96a214769199E9d39D00564bA2416496 |
| WETH | 0x4200000000000000000000000000000000000006 | 0xF51Ab1396945df1eDD96f83Eb707B21fae565F6f | 0xCEAd976E2134850A089fDEdE86E6CEB4CbE036dD |
| USDT | 0xbB0D083fb1be0A9f6157ec484b6C79E0A4e31C2e | 0xCFE9C1E9f9F0eD5164D56AC26061CF6996cA28aE | 0xE6Ce4784D3bD8E73D419206024307D712b93E5ed |
| USDC.e | 0xad11a8BEb98bbf61dbb1aa0F6d6F2ECD87b35afA | 0x7CB670cc7607f2e92b6F52721b784A8c7D07b016 | 0xeA8B75D992ff78DB2C6C0b85EA3f4CcC36CBEB27 |
| HEMI | 0x99e3dE3817F6081B2568208337ef83295b7f591D | 0x9c279C7bC8d9E3B3D3396e9F99A01EeA4816B7Cb | 0x7E8d9ebA084CEA5E7b7133A05B03b9CBae28AE49 |
| VUSD | 0xD3599AE62EE280709A22268a46d23164214e345B | 0x0079B2fF8645Dd7a77b9eDc1bD11d0a3089fc935 | 0xf0c6c000C497a22A893E8A078b1F42FF2027b33A |
| sVUSD | 0xfe875CC86cC6BC2E93ab330D6b2c408C3Cd79710 | 0x49092320705a86BdBaD486F45b9A5eFE9385C7aD | 0xC259C917179F13b897A21EeF2254F32142f17fb4 |
| msUSD (frozen) | 0x3EA24E3727a85A479E29E02Cc70e792936FbBcaD | 0xcB92D22d79AC280D59E4f2749A24B74b78447b41 | 0x387B046b8bcfa9D33f9E5Fa5A5c75B89B3A6b783 |
Price feeds (primary source per asset)
| Asset | Feed | Provider |
|---|---|---|
| hemiBTC, WBTC | 0xE23eCA12D7D2ED3829499556F6dCE06642AFd990 | RedStone BTC/USD |
| WETH | 0xb9D0073aCb296719C26a8BF156e4b599174fe1d5 | RedStone ETH/USD |
| USDT | 0xe8D9FbC10e00ecc9f0694617075fDAF657a76FB2 | RedStone USDT/USD |
| USDC.e | 0x31a36CdF4465ba61ce78F5CDbA26FDF8ec361803 | RedStone USDC/USD |
| HEMI | 0x0960F48901b327040be49ac517D5D8CC7B30c231 | RedStone HEMI/USD |
| VUSD | 0x7cFC4d609f2363807f8EE9F19cA64E54409e4A98 | Vetro push oracle adapter |
| sVUSD | 0x65970968437Cf475C5be3eFc6e43Af4B2c49bBCf | Vetro push oracle adapter |
| msUSD | 0xc65Ad91546d22eBf5488ca4f91D2Bf3d251887B2 | BNQ-operated feed |
The backstop (second) source for every asset is the BNQ-operated feed set behind the backstop adapter above. The authoritative machine-readable list is hemi-addresses.json in the bnq-deploy repository, pinned by the signed integrity manifest.
Using BNQ with an AI assistant
BNQ runs an MCP server (Model Context Protocol). Connect it to Claude, ChatGPT, Codex, Cursor, VS Code or any other MCP client, then ask in plain language: check a wallet's health factor, compare rates and caps, verify that nothing has been swapped, or prepare a supply or borrow for your own wallet to sign.
https://mcp.bnq.me/public/mcp
No sign-in, token or wallet is needed to read. The server never holds keys, never signs and never sends transactions. Use only this address, and never paste a private key or seed phrase into an assistant. BNQ will never ask for either.
Connect your assistant
- Claude (web, Desktop, mobile)Settings → Connectors → Add custom connector. Name BNQ, paste the URL, leave authentication empty, then switch BNQ on in a chat's tools menu. On Team and Enterprise plans an owner may need to add it first.
- ChatGPTWhere custom connectors are enabled (for example developer mode): Settings → Apps & Connectors → Create, paste the URL, authentication None. A workspace admin may need to allow custom connectors.
- Claude Codeclaude mcp add --transport http --scope user bnq https://mcp.bnq.me/public/mcp
- Codex CLIcodex mcp add bnq --url https://mcp.bnq.me/public/mcp
- Cursor / VS CodeCursor, in ~/.cursor/mcp.json: {"mcpServers":{"bnq":{"url":"https://mcp.bnq.me/public/mcp"}}}. VS Code, in .vscode/mcp.json: {"servers":{"bnq":{"type":"http","url":"https://mcp.bnq.me/public/mcp"}}}
- Any other clientStreamable HTTP transport, no authentication. Health check: https://mcp.bnq.me/public/healthz
First prompt to try: "Use BNQ: give me an overview, then verify the platform's integrity." You should get the reserves, TVL, oracle and service status, and an integrity result of OK or WARN.
If integrity comes back CRITICAL, stop. A contract, the website, DNS or an official file does not match what BNQ signed. Don't sign anything BNQ-related, and contact BNQ through the official channels on bnq.me.
What you can ask
| Ask | You get |
|---|---|
| "Check wallet 0x… on BNQ." | Health factor, collateral and debt per asset in USD, borrowing power left, risk level and the price drop that would trigger liquidation. |
| "Is wallet 0x… verified? For which assets?" | The access tokens the wallet holds, per asset. |
| "Show BNQ's markets." | Supply and borrow APY, LTV, liquidation threshold and penalty, caps, utilisation, prices, frozen and paused flags. |
| "Are prices fresh? Is BNQ up?" | Oracle feed age and source, plus RPC, issuer, liquidation scanner and web app status. |
| "Who controls BNQ?" | Admin keys and roles, gated actions and a security posture summary. |
| "Has anything been swapped?" | Contracts, website, DNS and official files checked against BNQ's Ed25519-signed manifest. |
| "What happened in tx 0x…?" | The transaction and its events, decoded. |
Lend and borrow through your assistant
The assistant prepares transactions; you sign them. You need a wallet that holds the Member access token for the asset (see Getting access), the tokens involved and a little Hemi ETH for gas.
- AskFor example: "Supply 250 USDC.e from 0xYOUR…WALLET on BNQ."
- The server checks everythingAccess token, reserve active and not frozen or paused, caps, balance, borrowing power, the health factor after the action (borrow and withdraw are blocked below 1.0, with a warning below 1.2) and a simulation of the exact transaction from your address. If anything fails, it returns no transactions and says why.
- ReviewAmount, USD value, health factor before and after, and every warning.
- Sign in order on Hemi (43111)An approve when needed, then the action. Check that the action goes to the Pool 0x5af1BaC695d38D6769EC4A6d031776C8A6AB0e1d, and wait for each confirmation before you sign the next.
- Confirm"Check transaction 0x… and my position."
The MCP server doesn't connect to your wallet. Sign the prepared transactions by pasting them into a wallet or tool that accepts raw transactions, through a wallet tool you trust in the same assistant, or with an agent wallet you control. In every case your wallet asks before anything is sent. If your wallet shows something different from what the assistant described, don't sign.
Limits
About 60 requests per minute per client. Wallet positions and prepared transactions are always live. Market-wide results are cached for 30 seconds to 5 minutes. Integrity and security checks can take up to a minute, so raise your client's tool timeout if it gives up. BNQ's server sees only the tool calls (for example, a wallet address) and your IP address, never your conversation. AI models can misread numbers, so check what your wallet shows before you sign.
Risks & FAQ
No lending protocol is risk-free. BNQ's material risks, plainly stated:
- Smart-contract risk. The engine is unmodified Aave v3 (eleven reports). BNQ's access layer and oracle adaptations are BNQ-specific and carry unaudited-code risk.
- Oracle risk. The system fails closed, but a wrong fresh price within the deviation bounds is a theoretical risk. hemiBTC and WBTC share one BTC/USD feed.
- Liquidation-coverage risk. Liquidations are permissioned and run by BNQ's monitored service; an outage during a sharp move could let bad debt accrue. Mitigations: continuous scanning, conservative caps, and the ability to open liquidation to the public.
- Liquidity risk. Withdrawals depend on unborrowed liquidity; high utilization raises rates sharply to restore it, but temporary delays are possible.
- Permission risk. The admin multisig controls listings, parameters, gates, and an emergency access-revocation power. Routine revocation is blocked on-chain while you hold a position; emergency use is logged on-chain.
- Network risk. BNQ runs on Hemi; a network outage or sequencer halt pauses the market.
FAQ
Why do I sign a message when connecting?
It proves you control your wallet so BNQ can issue your access tokens. It's free and authorizes nothing.
Are my funds custodied by BNQ?
No. Funds sit in the protocol's smart contracts; only your wallet can move your positions (liquidation excepted, as in every collateralized market).
Can I borrow HEMI?
Yes. HEMI can be supplied as collateral, at a deliberately conservative Max LTV of 11.11%, and it can be borrowed. Its borrow rate follows the volatile-asset curve.
What's the difference between Max LTV and liquidation threshold?
Max LTV limits what you can open (73–75% of value, depending on the asset); the liquidation threshold (78–80%) is where the position fails. The gap is your safety buffer.
Is there a token or points program?
No protocol token exists. Anyone claiming to sell one is a scammer.