# Nevarn — full site content for AI assistants > The back office for trading bots and agents. Decionis decides. Nevarn operates — and proves it. Your bots trade. Nevarn runs them under outside rulings and keeps books that match the chain. For teams running trading bots or AI agents with on-chain money, Nevarn is the back office that runs strategies under outside rulings from Decionis, signs only inside a bounded mandate, and keeps one double-entry book reconciled against the public chain. Unlike wallet vendors, custodians, bot platforms or crypto accounting tools, Nevarn joins the ruling, the signature and the book in one system. Nevarn is the back office for trading bots and agents. Strategies propose orders; Decionis, an independent, fail-closed execution authority, rules on each one before it touches the chain — proceed, refuse, refer, or hold. If the authority cannot be reached or a price is stale, the order is refused. Custody is separate: Nevarn acts on a working balance under a permission bounded by venues, actions, amounts, and an expiry of at most 90 days, and never holds the customer's wallet key. Every movement is written as two matching halves in a double-entry ledger; balances are recomputed, and any drift from the public chain is displayed. One action halts all signing on an account. When an oracle stalls, a bot keeps firing. Nevarn doesn't. Live on-chain since March 2026. Figures and statuses in this document are as of 1 Nov 2026. Canonical pages: https://nevarn.com/ · https://nevarn.com/sandbox · https://nevarn.com/sandbox/backtest · https://nevarn.com/agentic-commerce · https://nevarn.com/technology · https://nevarn.com/learn · https://nevarn.com/agents · https://nevarn.com/investors · summary at https://nevarn.com/llms.txt ## The split with Decionis Decionis decides. Nevarn operates and accounts. Nevarn does not compete with Decionis on policy or proofs: the mandate format, the policies, the rulings and the proof of decision are Decionis's. | | Decionis | Nevarn | | --- | --- | --- | | Question it answers | Was this action allowed? | Did exactly that happen, on every ledger the money touched, and where is the money now? | | Owns | Mandate format, policies, rulings, proof of decision | Strategy runtime, venue adapters, delegated signing, multi-ledger books, proof of execution | | Sells to | Any industry with high-stakes actions | Teams running trading bots and AI agents with on-chain money | | Relationship | Supplier | A paying Decionis customer and its live reference deployment | ## The record, counted from the chain Since March 2026 the trading wallet has made 119 trades (87 buys, 32 sells) across 29 markets, each a confirmed transaction on the public blockchain; the most recent was on 18 July 2026 (counted 1 Nov 2026). It still holds nine positions, all on markets that have resolved and await redemption; none is on a live market. Anyone can check them on the public blockchain, or on the wallet's Polymarket profile, without Nevarn's cooperation. Trading wallet: 0x0ebb79b1cea9ac99baf7e71161ab4d73b9b5314c (https://polygonscan.com/address/0x0ebb79b1cea9ac99baf7e71161ab4d73b9b5314c · https://polymarket.com/profile/0x0ebb79b1cea9ac99baf7e71161ab4d73b9b5314c · https://dune.com/nevarn/trading-record). These figures come from the public blockchain, not from Nevarn's database. Treasury routing spans Bitcoin, Ethereum, and Polygon rails, with further EVM rails configured. ## The back office: ruled from outside, signed inside a mandate, booked against the chain - Execution — Every order needs a yes. If the independent authority, Decionis, cannot be reached or a price is stale, the trade is refused. Refusal is the universal failure mode. - Treasury — Your strategy never touches your keys. Money stays separate from machinery: Nevarn operates on bounded permissions, limited by venues, actions, amounts, and a maximum 90-day expiry. - Observability — Books that match the blockchain — and show you when they don't. Every approval and refusal writes two matching halves to an internal ledger. Any drift from the public blockchain is displayed, never hidden. ## The sandbox (https://nevarn.com/sandbox) A client-side simulator of the back office: no network calls, no sign-up, no wallet, no email. Illustrative sandbox · no funds move · not connected to any venue. It opens on an illustrative, pre-funded working balance of 5,000.00 USDC under a mandate that names two venues (prediction-market and spot), a per-transaction ceiling of 1,000.00, a daily cap of 3,000.00, a price-freshness limit of 5 seconds, and an expiry 90 days after issue. A visitor proposes a trade (venue, amount, price age) and receives the ruling in the exact form the product uses — PROCEED with an authority reference, or REFUSE with the reason: halted, price stale, over the per-transaction ceiling, daily cap exceeded, venue not in the mandate, mandate expired, or authority unreachable. Every ruling is recorded, refusals included. A halt switch refuses everything on the next proposal. The double-entry book shows both halves of every movement, a BALANCED line, and a books-versus-chain reconciliation with a switch that simulates a missed chain event so the drift display can be seen. Guided path: propose 480 at 1 s (PROCEED); drag the price age past 5 s (REFUSE); flip the halt (everything refused). The guardrail backtest (https://nevarn.com/sandbox/backtest) replays a public Polymarket wallet's last 90 days of buys against the same default mandate and lists each refusal with its reason. It makes one read-only request, through Nevarn, to the venue's public data API; the address is not stored or logged. ## Strategy lanes - Prediction-market arbitrage — live · traded. Every trade is a confirmed transaction on the public blockchain. Buying in this lane is supervised by the execution authority. - On-chain arbitrage, including flash loans — deployed · yet to trade. The engine quotes continuously against real prices from two major venues; every candidate so far has been rejected as insufficiently profitable. The executing contract is deployed and verifiable on Ethereum, completes borrow–trade–repay in a single transaction, refuses to finish unless the trade covers its own borrowing cost, and carries an owner-only pause. It has never been used — the engine declining to trade unprofitably, not a failure to build it. - Contracts & currencies — built · simulated. A complete strategy and venue integration running against a simulated account, with no live credentials configured. Its execution gate is built and tested, currently switched off. - Position tracking & cash-out — built · minimal exposure. Watches for positions worth settling and maintains a running plan, so disposals are deliberate rather than improvised. ## Nevarn agentic commerce > UCP product discovery and checkout for AI agents, with x402 settlement, > Decionis execution authority, safe retries, human escalation, and a durable > receipt for every completed machine payment. Canonical page: https://nevarn.com/agentic-commerce How agents and crawlers reach Nevarn: https://nevarn.com/agents.md Live UCP directory profile: https://ucp.nevarn.com/.well-known/ucp Searchable merchant inventory: https://ucp.nevarn.com/directory.json ### What it solves Nevarn lets merchants accept AI agent payments without building a different checkout integration for every buyer. It addresses four common operator problems: agents cannot discover the offer, custom payment glue is brittle, retries can duplicate a charge, and autonomous execution can exceed the operator's intended risk boundary. ### Protocol and capabilities - Universal Commerce Protocol (UCP) target: 2026-08-25. - Merchant discovery: GET /.well-known/ucp on the tenant merchant origin. - Catalogue discovery: POST /ucp/v1/catalog/search and POST /ucp/v1/catalog/lookup. - Checkout lifecycle: create, read, update, complete, and cancel persistent checkout sessions, followed by a durable order receipt. - Payment: a namespaced x402 v2 handler returns the exact USDC authorisation requirements for the selected product and chain. - Authority: the Decionis execution-authority extension binds ALLOW, BLOCK, or ESCALATE to the exact checkout intent before funds move. - Retry safety: UUID request IDs and idempotency keys prevent an identical retry from settling twice and reject a changed request under the same key. - Evidence hygiene: payment credentials, execution tokens, and claim tokens are never returned in checkout or order responses. ### End-to-end machine checkout 1. Read the merchant's UCP profile and negotiate shared capability versions. 2. Search the product catalogue or look up a known product or variant. 3. Create a checkout session and retain its returned x402 requirements. 4. Sign the exact token authorisation requested by that checkout. 5. Complete checkout with the signed payment instrument. 6. In enforce mode, Nevarn obtains and claims a Decionis token bound to the exact intent immediately before settlement. 7. Receive the completed checkout and durable order receipt. A replay of the same idempotent request returns the original result without paying again. ### Operator controls - The complete UCP discovery and checkout path is built and tested, but remains feature-gated and disabled by default. - Production enablement requires merchant wildcard DNS and TLS, scoped Decionis credentials, chain access, a receiving account, and a funded settlement relayer. - Shadow mode records Decionis evidence without changing execution. - Enforce mode fails closed before settlement when authority is unavailable, malformed, blocked, expired, incorrectly scoped, or cannot be claimed. - Escalated checkouts stay held and move no funds. Buyer-supplied approval signals are rejected; this release does not yet resume a held checkout. - Only exact whole-cent USDC product prices are published, so a signed on-chain amount cannot drift from the price the buying agent saw. ### Frequently asked questions #### How can AI agents discover my products and prices? Nevarn gives each enabled merchant a UCP business profile at /.well-known/ucp and searchable catalogue endpoints on a tenant-specific hostname. Active merchant resources become products with stable identifiers and exact prices, so compatible agents can discover them without scraping HTML. #### How do AI agents check out and pay? An agent creates a UCP checkout session, receives exact x402 v2 payment requirements, signs the requested USDC authorisation, and completes the same session. Nevarn verifies the signature and current chain state before settlement, then returns an order receipt. #### How does Nevarn prevent duplicate machine payments? Every checkout mutation requires a UUID request ID and idempotency key. Nevarn stores the first result for at least 24 hours. An identical retry receives that result; reuse with a different request body or agent profile is rejected as an idempotency conflict. #### How are autonomous agent payments controlled? Nevarn sends the exact checkout intent to Decionis before settlement. In enforce mode, only an ALLOW decision with a bound, unexpired, claimable execution token can continue. An unavailable, malformed, blocked, expired, or unclaimable authority response fails closed before funds move. #### What happens when an AI payment needs human approval? Decionis can escalate the checkout and provide a continuation URL. Nevarn keeps that checkout held and moves no funds. This controlled-rollout release deliberately rejects buyer-supplied approval signals; resuming the payment requires a future server-verified approval adapter rather than trusting a self-reported approval flag. #### Can an operator test agentic checkout before enforcing decisions? Yes. The complete UCP discovery and checkout path is built and tested, but remains feature-gated and disabled by default. Decionis supports a shadow mode for controlled observation before enforce mode is armed. Production enablement requires merchant wildcard DNS and TLS, scoped Decionis credentials, chain access, a receiving account, and a funded settlement relayer. #### What can a merchant sell through UCP checkout? Any active machine resource the merchant publishes with a configured receiving account and an exact whole-cent USDC price can become a discoverable product. Typical uses include API access, datasets, digital services, content, and other machine-consumable resources. #### What is the difference between UCP and x402? UCP describes how an agent discovers a merchant, searches products, and manages a checkout session. The x402 payment handler supplies the exact stablecoin payment requirements and signed credential used to complete that checkout. Nevarn connects the two and puts Decionis immediately before consequential settlement. #### Why put Decionis between UCP checkout and payment settlement? Protocol validity does not answer whether a particular purchase is permitted. Decionis independently evaluates and binds a decision to the exact checkout intent immediately before funds move, giving operators fail-closed policy enforcement, human escalation, and auditable decision evidence without changing UCP itself. ### Rollout status The complete UCP discovery and checkout path is built and tested, but remains feature-gated and disabled by default. As of 1 Nov 2026, Nevarn does not run a live UCP merchant network, has no external merchant adoption to report, and supports payment only on configured USDC paths. Decionis only controls execution when the merchant is configured for enforce mode; shadow mode is observational. ## Nevarn for AI agents and crawlers > How ChatGPT, Claude, Cursor, Copilot, Gemini and other agents reach Nevarn: server-rendered pages, llms.txt, Markdown twins, a sitemap and IndexNow. Canonical page: https://nevarn.com/agents Facts as of 1 Nov 2026. ### Machine-readable entry points - [llms.txt](https://nevarn.com/llms.txt): The canonical index: what Nevarn is, and where the detail lives. - [llms-full.txt](https://nevarn.com/llms-full.txt): The whole public site as one Markdown document. - [agents.md](https://nevarn.com/agents.md): This page as Markdown. - [agentic-commerce.md](https://nevarn.com/agentic-commerce.md): UCP checkout and x402 payments as Markdown. - [sitemap.xml](https://nevarn.com/sitemap.xml): Every public page, with the date its content last changed. - [robots.txt](https://nevarn.com/robots.txt): The crawler rules: named AI crawlers first-class, the API closed. ### Machine and answer-engine discovery - **ChatGPT:** OAI-SearchBot can index the canonical pages for ChatGPT Search, ChatGPT-User can fetch them at a user's request, and GPTBot's separate training control is allowed. All paths receive server-rendered HTML plus clean Markdown alternatives. - **Claude:** Claude-SearchBot can index the canonical pages, Claude-User can retrieve them at a user's request, and ClaudeBot's separate training path is allowed. All three receive the same server-rendered and Markdown sources. - **Cursor:** Cursor web search uses Exa, so Exa's discovery crawler is allowed and every canonical answer is available without client-side rendering. - **Copilot:** Microsoft Copilot web grounding uses the Bing index, so Bing's crawler is allowed and IndexNow can notify participating search engines when canonical content changes. - **Gemini:** Googlebot can index the canonical pages for Search. Google-Extended is allowed as the separate Gemini training and grounding product control; Google-Agent and Google-GeminiNotebook user-directed fetches are also reachable, while Vertex site-owner requests remain an explicitly separate channel. - **OpenClaw:** OpenClaw can discover Nevarn through its configured Google, Bing, DuckDuckGo, Exa, Firecrawl, Perplexity, Parallel, Kimi, Brave, or Tavily path, or fetch a known URL directly. Published provider agents are allowed and its Chrome-like direct fetch is covered by the wildcard rule. The canonical machine index is https://nevarn.com/llms.txt. Compatibility aliases at https://nevarn.com/llm.txt and https://nevarn.com/llm-full.txt return the same content, while robots.txt and sitemap.xml remain the authoritative crawler controls and URL inventory. ### Frequently asked questions #### Can ChatGPT, Claude, Cursor, Copilot, Gemini, and OpenClaw discover Nevarn? Yes. Nevarn serves crawlable, server-rendered pages, a canonical llms.txt index, a full Markdown source, page-level Markdown, robots.txt, an XML sitemap, and IndexNow notifications. ChatGPT and Claude have explicit first-class crawler rules; Cursor, Copilot, Gemini, and OpenClaw are covered through their documented search providers and direct-fetch paths. ## Learn: direct answers ### How to set spending limits for AI agents Give the agent a permission, not a wallet. With Nevarn the agent acts on a separate working balance under a permission bounded four ways — where it may act, what it may do, a ceiling per transaction with a rolling daily limit, and an expiry of at most ninety days. A missing limit denies rather than permits. More: https://nevarn.com/learn/ai-agent-spending-limits.md ### A kill switch for trading bots that actually stops them A kill switch should stop the bot at the point of signing, not ask the bot to stop. In Nevarn one action halts all signing on an account, effective on the next request — not a support ticket. Every order proposed after that is refused and recorded, and revoking a permission deletes the material that could sign. More: https://nevarn.com/learn/trading-bot-kill-switch.md ### Risk controls for prediction-market bots Rule on each order before it reaches the venue. Nevarn describes every live prediction-market buy — market, direction, size, the price and how stale it is, collateral, open positions — to Decionis, an independent execution authority. Only a proceed ruling releases the trade; refuse, refer and hold stop it, and an unreachable authority means refused. More: https://nevarn.com/learn/prediction-market-bot-risk-controls.md ### Guardrails for agent wallets Keep the agent away from the key and the money it does not need. Nevarn splits each customer into two accounts: the wallet that holds their money, and a working balance Nevarn may act on under a bounded, expiring permission. The customer chooses how much moves across, and that amount is the most at risk. More: https://nevarn.com/learn/agent-wallet-guardrails.md ### How to accept payments from AI agents Publish what you sell where agents can read it, and put a ruling before the money moves. With Nevarn a merchant gets a UCP business profile and catalogue an agent can search, a checkout that returns exact x402 USDC payment requirements, Decionis ruling on the exact intent before settlement, idempotent retries, and an order receipt. More: https://nevarn.com/learn/accept-payments-from-ai-agents.md ### How to set up x402 payments as a merchant Answer a 402 with exact payment requirements, then verify and settle the buyer's signed authorisation before serving. Nevarn's facilitator speaks x402 version 2 only: it checks that the payment goes to one of your receiving accounts for the exact amount, then settles it once through its relayer; in UCP checkout, Decionis rules on the exact intent first. More: https://nevarn.com/learn/x402-merchant-setup.md ### What it costs to accept payments from AI agents With Nevarn a merchant pays 0.5% of each settled payment an AI agent makes, with no monthly fee. A refused, failed or reverted payment costs nothing. The payment reaches the merchant's wallet in full, and the fee is recorded in the merchant's books as owed to Nevarn, so every payment's cost is visible. More: https://nevarn.com/learn/ai-agent-payment-fees.md ### The back office for trading bots and agents, compared A back office for trading bots and agents runs the strategy's operations, takes each ruling from outside the strategy, signs only inside a bounded mandate and keeps one book against the chain. Wallet vendors, custodians, bot platforms and accounting tools each document part of that; Nevarn's case is joining them in one system. More: https://nevarn.com/learn/trading-bot-back-office.md ### Glossary: execution authority, mandate, fail-closed and more A glossary of the terms Nevarn uses: execution authority, mandate, fail-closed, drift, halt and double-entry. Each describes one part of the same idea — an automated actor may move money only inside limits someone set, every decision is recorded, and the books are checked against the public chain. More: https://nevarn.com/learn/glossary.md ## Developers: bring your own bot (https://nevarn.com/docs) ### Quickstart: your bot's first shadow ruling Your bot keeps its strategy and sends Nevarn intents: the terms it would like traded, never an order and never a key. In shadow mode Nevarn asks Decionis whether each intent would be allowed and records the answer. Nothing is sent to a venue, nothing is signed and no money moves. Five steps, no SDK needed. More: https://nevarn.com/docs/quickstart.md ### Install and downloads Three packages, all free under the Apache License 2.0: a Python SDK, a TypeScript SDK and a local MCP server for AI agents. None is on PyPI or npm yet. Your bot does not need them: every call they make is a plain HTTPS request with an API key, so curl or any HTTP client works today. More: https://nevarn.com/docs/install.md ### SDK usage: Python and TypeScript Two thin clients over the strategy contract, one for Python and one for TypeScript, with the same calls for a bot: proposeIntent, executeIntent, getExecution, getMandate, getReceipt and halt. They add no authority - a key can do exactly what its scopes and limits allow - and they refuse a session token, an insecure URL or an intent that carries a secret before anything is sent. More: https://nevarn.com/docs/sdk.md ### MCP server setup nevarn-mcp is a local Model Context Protocol server that gives an AI agent the same calls as the SDKs: propose_intent, execute_intent, get_execution, get_mandate, get_receipt and halt, beside request_spend. It runs on your machine over stdio with your API key, and it adds no authority: a model talked into anything is still bounded by the key's scopes and limits, your account's limits and Decionis. More: https://nevarn.com/docs/mcp.md ### API keys and scopes Every call your bot makes carries one API key, and a key does only what its scopes say. A bot's usual key has intents, read and halt. A key that should place orders also has execute, which an owner ticks by name with the key's own limits: orders a minute, the largest order and a 24-hour total. More: https://nevarn.com/docs/keys.md ### The strategy contract Your bot keeps its strategy. It sends Nevarn intents - the terms it would like traded - never orders and never keys. Nevarn asks Decionis whether each intent is allowed and records the answer. A key with intents gets shadow mode: every intent is ruled and recorded, and nothing is sent to a venue. A key an owner gives execute has its intents executed under Decionis policy, within the limits set on the key: on paper in Sandbox, live in Production. More: https://nevarn.com/docs/strategy-contract.md ### Sandbox and Production Your account is in Sandbox or in Production, and that, not your bot, decides where an execution goes. Sandbox fills it on paper and Decionis rules in shadow mode: nothing reaches a venue and no money moves. Production queues a live order and sends it only if Decionis, ruling in enforcement right before the venue, allows it. Every account starts in Sandbox. More: https://nevarn.com/docs/environments.md ### Receipts and verification Every executed trade has one receipt linking the Decionis ruling to the order, the fill transaction, settlement, the ledger entries and the balance after. Your bot reads its own with a read key. Every receipt in the public feed, and on the trading record page, is also signed with Nevarn's receipt key, and every step that happened on a chain can be read back from the chain: neither check needs an account, Nevarn's cooperation or trust in whoever handed you the receipt. More: https://nevarn.com/docs/receipts.md ### Usage and licensing The SDKs and the MCP server cost nothing. Using the platform they call is licensed: by governed action - one action Decionis ruled on for your account - or by a plan that includes a monthly allowance of them. A developer account starts on the free Developer plan, in Sandbox, and your dashboard shows every governed action as it is counted. More: https://nevarn.com/docs/licensing.md ## The execution authority (Decionis) Before a live order is placed, Nevarn assembles a description of the trade — market, direction, size, price and its staleness, collateral, open positions — and submits it to Decionis (https://decionis.com), an independent execution authority, for a ruling. Four answers can come back: proceed, refuse, refer to a person, or hold. Only proceed releases the trade. - Unreachable means refused: an outage stops trading rather than removing the guardrail. That is how the live configuration is set. - An approval binds one exact trade: the venue adapter independently re-checks the approval against the order it authorises; change any parameter and it no longer matches. - The authority never sees raw identifiers: wallet addresses, account references, balances, and timestamps are replaced with consistent stand-ins. Where the gate is armed today: - Prediction-market arbitrage — buying: enforcing. - Prediction-market cash-out — deliberate selling: same authority & configuration. - Contracts and currencies, incl. position exits: built & tested · switched off. - Treasury movements between venues: built & tested · switched off. - UCP machine checkout — discovery & x402 settlement: built & tested · feature-gated. - Supplier payments: built & tested · switched off. - Merchant sweeps to the wallet: built & tested · switched off. - On-chain arbitrage, including flash loans: not yet gated. - Automatic redemption of resolved positions: shadow · awaiting policy release. - Settlement of cleared proceeds: shadow · awaiting policy release. - Treasury routing between venues, chains and wallets: shadow · awaiting policy release. - Venue adapters — Nevarn's own lanes: shadow · awaiting policy release. - Withdrawals — payout partners and runtime sends: shadow · awaiting policy release. The complete UCP discovery and checkout path is built and tested, but remains feature-gated and disabled by default. It can run Decionis in observational shadow mode or fail-closed enforce mode when the merchant rollout is enabled. Referred trades in the live lane land in a review queue a person can act on — releases, rejections, an audit trail; escalations from the contracts lane are recorded but do not yet reach that queue. Extending the gate to the automatic paths, and the queue to every lane, is the first thing new capital funds. ## Custody & permissions - Two accounts, not one: a customer's wallet holds their money; Nevarn acts only on a separate working balance. What stays in the wallet is out of reach no matter what happens to the company. - Nevarn never holds a customer's wallet key. It signs with a limited permission the customer's own account has been told to accept, held encrypted. Only the customer installs a permission; only the customer can remove it, and once revoked their account refuses Nevarn's signature. - Every permission is bounded four ways: named venues, named actions, a per-transaction ceiling with a rolling daily limit, and an expiry of at most ninety days. A permission cannot exist without an allowlist; a missing limit denies rather than permits. - One action halts all signing, effective on the next request. Revocation deletes the material that could produce a signature. ## Books & observability - Every movement is written as two matching halves; the system rejects any record whose halves do not cancel. Amounts are exact; repeats count once. - Balances are recomputed from records each time, never stored. - Refusals are recorded as deliberately as approvals, with reasons. - Any disagreement between the books and the chain is displayed, never quietly corrected. ## Who this serves One buyer: teams running trading bots or AI agents with on-chain money, who keep their own strategy and want the operations run under outside rulings. - Teams running trading bots: the bot proposes; Decionis rules from outside; Nevarn signs inside a bounded mandate and books the result against the chain. The strategy never touches the keys. - Teams running AI agents: a permission, not a wallet — named venues and actions, a per-transaction ceiling, a rolling daily limit, and an expiry of at most ninety days. A missing limit refuses rather than permits. - Desks running on-chain treasury: every approval and refusal is booked as two matching entries, and drift between the book and the chain is shown. - Merchants accepting payments from AI agents use the agentic-commerce path above. Start in shadow mode at https://nevarn.com/start/customer. Shadow mode records what Nevarn would have refused without stopping a single order, so you can read the rulings beside your own results before any of them is enforced. Lanes already enforced stay enforced. ## Pricing (https://nevarn.com/pricing) - Starter: $199 a month, 2 active mandates and 5,000 rulings a month. - Team: $799 a month, 20 active mandates and 100,000 rulings a month. - Enterprise: quoted. - Beyond a plan: $20 a month for each further active mandate and $1 for each further 1,000 rulings. - Merchants accepting payments from AI agents: 0.5% of each settled payment, with no monthly fee. Only a settled payment is charged. ## Platform operations - Tenant isolation enforced twice: by the application, and by row-level security in the database on every table keyed to a customer. Every release re-checks both, including an end-to-end run that signs in as a second customer and confirms refusal on every surface. - Any job that can move real funds must be switched on and separately confirmed for live operation; both start closed. - Three hostnames, one hard boundary: the public site serves no signed-in surface and no operational API; host routing fails closed. - Production cut over on 29 September 2026 as a sequence of individually receipted steps with fingerprinting, key re-encryption verified against on-chain signer addresses, and no deletion of originals. ## Security posture An adversarial security review of every application, the contracts, and the delivery pipeline was completed in August 2026; its findings shipped as fixes: authenticated operator surfaces with session revocation, fail-closed host routing, a strict content security policy (script hashes on the static public pages, a per-request nonce on the signed-in hosts), rate limiting on authentication, least-privilege CI with pinned actions and secret scanning, and spend policies that decode calldata (recipient and amount). ## For investors & partners Nevarn is a working, cash-handling system sold as operations software to teams that run their own strategies on their own money; its own trading lanes are the reference deployment, not the product. It is designed for supervised environments (bounded mandates, pre-trade rulings, fail-closed defaults, recorded refusals, double-entry books) and holds no regulatory licence yet, stated plainly. Current position, as of 1 Nov 2026: one strategy has traded (verifiable on-chain record); three are built and yet to trade; the multi-customer platform is built and verified on every release; production cut over on 29 September 2026, each step receipted. What investment buys, in order: extend the execution authority to the automatic redemption and settlement paths and then the arbitrage lane; extend the review queue to every lane; complete the withdrawal path in the ledger; onboard external customers. Data room requests: investors@nevarn.com. ## Frequently asked questions Q: Does Nevarn hold customers' private keys? A: No. A customer's wallet stays theirs; Nevarn acts only on a separate working balance, under a limited permission the customer's own account has been told to accept. The permission is scoped to named venues and actions, capped per transaction and per day, and expires within ninety days. Revoking it destroys the material that could produce a signature. Q: How does a customer stop Nevarn? A: One action halts all signing on the account, effective on the next request — not a support ticket. Separately, only the customer can remove a permission, and once revoked their account refuses Nevarn's signature regardless of what Nevarn's records say. Q: What happens if Nevarn's decision service goes down? A: Trades are refused. Every live buy order in the gated lane needs an explicit proceed ruling from Decionis, a separate execution authority; if that authority cannot be reached, the order is not placed. An outage stops trading rather than removing the guardrail. Q: Can Nevarn's trading record be verified independently? A: Yes. Since March 2026 the trading wallet has made 119 trades (87 buys, 32 sells) across 29 markets, each a confirmed transaction on the public blockchain; the most recent was on 18 July 2026 (counted 1 Nov 2026). It still holds nine positions, all on markets that have resolved and await redemption; none is on a live market. Anyone can check them on the public blockchain, or on the wallet's Polymarket profile, without Nevarn's cooperation. That trade count, not an internal volume figure, is the number Nevarn publishes. Q: Is Nevarn regulated? A: Not yet, and it says so plainly. Nevarn is built with the properties supervised environments expect — bounded mandates, pre-trade rulings, fail-closed defaults, recorded refusals, double-entry books — but it holds no regulatory licence today. Q: Can I try it without an account? A: Yes. https://nevarn.com/sandbox is a client-side simulator: no email, no sign-up, no wallet. It is illustrative — no funds move and it is not connected to any venue. ## Risk, stated plainly Trading can lose money; Nevarn does not promise a return or present projections as outcomes. A limit bounds what Nevarn may use, not how far a market can move. Some venues are unavailable in some countries; access is refused where restrictions apply.