Autonomous market infrastructure

Engines first.
Capital last.

Aurifern builds autonomous systems for on-chain markets, and measures every one of them long before it touches money.

Fig. 1 How an engine grows up
Route from observation to bounded activation A signal branches into five candidates during replay. Most are pruned. One reaches proof and is verified. Activation beyond it is gated behind a dashed bound and has not happened. observe replay prove activate bound
  • signal
  • verified
  • gated, not active
  • pruned
  • Auction solving
  • Prediction markets
  • Replay and evidence
  • Risk boundaries

Method

A result needs a receipt.

  1. 01

    See the actual market.

    Save the input and the time it arrived. A feed that went quiet is not evidence that nothing happened.

  2. 02

    Try the answer again.

    Replay the same opportunity against a known baseline. If the comparison isn’t like for like, call it inconclusive.

  3. 03

    Decide how far it may go.

    Passing a test and being allowed to act are different things. Each step further needs its own decision.

Work

What we’re building.

A few engines and the ground they share. Small on purpose.

Flagship

CoW Solver

In development

A batch auction wants one settlement that works for every order in it. This solver hunts for better ones and checks each before it answers. No claims about wins or money yet.

Live view The solver in CoW Protocol’s shadow competition, where answers are scored but never settled.

  • Looks for better settlements.
  • Checks every answer before offering it.
  • Knows when to sit an auction out.
  • In development

    Prediction Markets Engine

    Every forecast is written down the moment it’s made, then checked against what actually happened, not against what we wish we’d said. The part that does the research can’t spend a cent. It can only suggest, and a strict set of risk rules decides whether anything happens at all.

  • Shared infrastructure in development

    Replay & Evidence Plane

    Markets move too fast for “it looked good at the time” to count as a record. This is the record-keeping under every engine: any result can be checked again later, from the same inputs.

Detailed evidence is shared with protocol teams on request. Ask for it

Architecture

Five layers. One risk book per engine.

  1. 01

    Network & data plane

    Market and chain data, each record with its source and time.

  2. 02

    Shadow & replay plane

    Past moments rebuilt and replayed. Nothing here trades.

  3. 03

    Execution & policy plane

    Limits and permissions, walled off from everything else.

  4. 04

    Protocol engines

    One per protocol. Each keeps its own risk book.

  5. 05

    Intelligence surface

    Status and incidents from what actually ran. No forecasts.

How the stages work

About

Founder-led, deliberately small.

Automation does the repetitive work. Judgement stays with a person. Nothing touches capital before it has been measured.

Dan Z brings a mathematical background and a researcher’s habits to markets: state the hypothesis precisely, then try to break it. AI is built into the whole workflow, from reading protocols and papers to simulation, code and review. That is how a founder-led shop works at research depth without a large team.

Track record

  • $30M+ handled by the launchpad contracts
  • 40k+ people took part in launchpad sales
  • 120k+ members in the launchpad community
  • 16k+ projects locked with the token locker
  • Launchpad A token launchpad that, at its peak, ranked among the top three in the world. Every contract was written by Dan Z: IDO sales, vesting and staking, one autonomous system that ran critical operations without an incident.
  • Locker A token and liquidity locker that thousands of projects trusted with their liquidity.
  • Chain A Bitcoin-based chain, with its own multi-platform wallets.
  • Trading Several crypto trading platforms, among them a spot exchange for the chain’s coin against Bitcoin, running on a matching engine Dan Z wrote from scratch: a full order book with market and limit orders and live candles.

Dan ZFounder

  • 16 years in software
  • 8 years in blockchain

hello@aurifern.com

Say hello

Have a concrete market question?

If you’re working on an auction, a data source or a failure mode worth examining, write with specifics. This is a small research-and-build operation, not a trading product for clients.