Traction & technology
Nevarn's traction is presented the way its books are kept: exact, checkable, and stated before anyone has to ask. The strongest evidence in the product is the part that requires no trust in us.
Deliveries land in the trading wallet on the public blockchain. Anyone can count them without our cooperation — which is exactly why this is the number we publish.
111
On-chain deliveries
Outcome-token settlements received, March–July 2026.
14
Distinct markets
Traded at one venue over the period.
1
Open position
Matching our own records exactly at last reconciliation.
4
Strategy lanes
One traded live; three built, running, and yet to trade.
Trade-level economics, reconciliation history, and wallet references are shared with qualified parties through the data room. The public figure is deliberately the conservative one.
Strategy lanes
Between March and July 2026 the trading wallet received 111 outcome-token deliveries across 14 distinct markets, all confirmed on the public blockchain by anyone who cares to look. One open position matches our books exactly. Buying in this lane is supervised by the execution authority.
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.
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.
Watches for positions worth settling and maintains a running plan, so disposals are deliberate rather than improvised.
The execution authority
Before a live order is placed, Nevarn assembles a description of the trade — market, direction, size, the price it is seeing and how stale that price is, collateral, open positions — and submits it to Decionis, 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.
Where the gate is armed today
Prediction-market arbitrage — buying
EnforcingPrediction-market cash-out — deliberate selling
Same authority & configurationContracts and currencies, incl. position exits
Built & tested · switched offTreasury movements between venues
Built & tested · switched offUCP machine checkout — discovery & x402 settlement
Built & tested · feature-gatedSupplier payments
Built & tested · switched offMerchant sweeps to the wallet
Built & tested · switched offOn-chain arbitrage, including flash loans
Not yet gatedAutomatic redemption & settlement
Not yet gatedBeing precise about this matters more than being impressive about it: buying and deliberate cash-out in the prediction-market lane are supervised; the automatic redemption, settlement, and arbitrage paths are not yet. The gate has genuinely run against the live decision service and genuinely stopped real orders — proven as a mechanism, not yet at volume. Referred trades in this lane land in a working review queue; extending the gate to the automatic paths, and the queue to every lane, is the first thing new capital funds.
Authority envelope · live
Authority
Inside your limits
Decision
Approval or refusal
Record
Balanced in the books
Custody & permissions
A customer's wallet holds their money; a separate working balance is what Nevarn may act on. Whatever stays in the wallet is out of our reach no matter what happens to the company. The amount moved across is the amount at risk — and the customer chooses it.
Where Nevarn signs on a customer's behalf, it does so with a limited permission their own account has been told to accept — held encrypted. Only the customer installs a permission, and only the customer can remove it; once revoked, their account refuses our signature regardless of what our records say.
The specific places it may act, the specific actions it may take, a ceiling per transaction with a rolling daily limit, and an expiry of at most ninety days. A permission cannot be created without an allowlist, and a missing limit denies rather than permits.
One action halts all signing on an account, effective on the next request — not a support ticket. Revocation deletes the material that could produce a signature, rather than marking a row inactive.
Books & observability
Every movement of money is written as two matching entries, and the system physically rejects any record whose halves do not cancel. Amounts are held exactly; a repeated notification is counted once.
No balance is a number someone typed. Each is derived from the underlying records every time it is shown, so the figure and its evidence cannot drift apart.
What our records say is shown beside what the account actually holds on the blockchain, with the difference. We never quietly correct ourselves to make the two agree — that would destroy the only evidence that something happened.
Every request our automation makes is written down with its outcome and, where refused, the reason. A run of refusals surfaces as a warning rather than as silence.
Operating as a platform
The multi-customer platform — isolation, permissions, scheduling, and books — is built and verified on every release. It has not yet carried anyone but us, and we would rather present that as the position than imply otherwise.
A request for another customer's holdings, records, or permissions is answered as though the account does not exist. Verification includes an end-to-end run that signs in as a second customer and confirms refusal across every surface.
Any job that can move real funds must be both switched on and separately confirmed for live operation. Both start closed; refusing to act is the default everywhere.
The public site, the tenant console, and operator tooling are separated by host routing that fails closed. The public domain serves no signed-in surface and no operational API at all.
Promotion to production infrastructure is a sequence of deliberate, individually receipted steps — refusing to copy into a non-empty destination, fingerprinting every record before and after, re-encrypting key material and verifying it against signer addresses recorded on the blockchain, never deleting the original.
Security posture
In August 2026 we ran an adversarial security review across every application, the contracts, and the delivery pipeline — scoped to custody, risk controls, and the attack surface an internet-facing money system actually presents. Its findings shipped as fixes, not as a report.
The stack
Execution
Python agent services for strategy, accounting, and workflow state
Control plane
Next.js treasury and operator console behind host-isolated surfaces
On-chain
Execution contract deployed and source-verifiable on Ethereum
Rails
Bitcoin, Ethereum, and Polygon under treasury routing today
Plain answers
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.
Yes. Between March and July 2026 the trading wallet received 111 outcome-token deliveries across 14 distinct markets, all confirmed on the public blockchain — anyone can count them without Nevarn's cooperation. That delivery count, not an internal volume figure, is the number Nevarn publishes.
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.
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.
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.
Stated in advance
Written here so nobody has to discover it in diligence.
If this is the kind of precision you want in an early-stage digital-asset company, the investor brief goes deeper.
Investor & partner portal