Autonomous market infrastructure

Measured before it moves capital.

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
  • Solvers & routing
  • Replay & simulation
  • Risk & controls
  • Market research

Method

An engine is live when its claims hold up.

  1. 01

    Receipts

    Every result keeps its inputs, outputs, timing and code version.

  2. 02

    Fences

    Limits on time, spend and failure are set before anything runs.

  3. 03

    Reuse

    Replay, monitoring and rollback carry over to the next engine.

Work

What we’re building.

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

Flagship

CoW Solver

In development

Batch auctions reward the solver that finds the best settlement for everyone in the batch. This engine competes for that, carefully: every answer is simulated first, and every change is tested against history before it goes anywhere near live flow.

  • Starts from the official baseline and searches for better routes.
  • Simulates every candidate before answering.
  • Checks itself against replayed auctions.
  • Stops when it isn’t sure.
  • Shared infrastructure

    Replay & Evidence Plane

    Shared plumbing that makes every engine checkable: what it saw, what it did, which version did it, and how to replay the moment exactly. Every engine runs on it.

  • Research

    UniswapX Observer

    A read-only lane for studying intent-based order flow: which orders appear, how they resolve, and what a filler could have done. It watches and records. Nothing more.

New engines enter the same way: research, simulation, a capital cap, a gate.

Architecture

Five layers. One risk book per engine.

  1. 01

    Network & data plane

    Chain data, event feeds and endpoint health. Every later claim points back to a record kept here.

  2. 02

    Shadow & replay plane

    Rebuilds past opportunities from saved inputs and replays them, including what the engine would have done.

  3. 03

    Execution & policy plane

    Where signing, nonce handling, simulate-before-send and loss limits live, walled off from everything else.

  4. 04

    Protocol engines

    One adapter per protocol. Each keeps its own risk book, its own gate and its own evidence.

  5. 05

    Intelligence surface

    Status, incidents and metrics taken from what actually ran. No forecasts.

How the stages work

About

Founder-led, deliberately small.

Aurifern is founded and run by Danil Zak. Automation does the repetitive work. Judgement stays with a person. Nothing touches capital before it has been measured.

Danil ZakFounder

hello@aurifern.com

Say hello

The next proof should be smaller than the claim.

Building something where correctness matters more than volume? Write to us. Small experiments first.