Amorphous.
Parametric insurance and prediction markets, across two chains.
Flight delay cover that pays itself from an oracle, and a market on every flight it covers, linked by a one way settlement bridge, tested end to end across two chains. The onchain engineering we take on for clients.
One flight, the full lifecycle, end to end on local chains.
Diamond contracts · onchain market maker · one way bridge
Flight delay cover that pays itself, and a market on every flight it covers.
On one chain, parametric insurance: a flight delay policy that resolves from an oracle and pays out automatically, no claim form, no adjuster. On the other, a prediction market on those same flights, so the risk is priced and hedged in the open. A one way bridge carries the finalized outcome between them, and the whole lifecycle runs and is tested end to end on local chains.
Buy a flight delay policy in plain words: quote, approve, mint a policy that pays automatically on delay.
A prediction market opens on each insured flight, priced by an on chain automated market maker.
An oracle resolves the outcome on one chain and a one way bridge carries it to the other to settle.
Underwriting capital flows through a vault: providers deposit and withdraw through a queue.
Two chains, each doing what it is best at.
An insurance protocol, a market protocol and a settlement path between them, plus the services that drive them. Each layer is built on the real standards, to the security bar that value bearing code demands.
A diamond and a vault
The insurance side is an upgradeable diamond of focused facets (policies, pool, claims, commissions, governance) over an ERC-4626 capital vault hardened against the inflation attack. Quotes are signed off chain and bound to their holder, so a quote cannot be replayed or stolen.
An automated market maker
The market side is a logarithmic market scoring rule maker written in fixed point integer math, with the price of every outcome guaranteed to sum to one and its loss bounded and reconciled. A market opens automatically for each insured flight.
One way, replay proof settlement
An oracle reaches consensus across independent flight data feeds and resolves the outcome on chain. A one way cross chain bridge carries only the finalized result to the other chain, guarded against replay, so a settled outcome can never be forged or applied twice.
The services around it
A set of small services in Rust coordinate quoting, signing, oracle relay, market routing and indexing over a durable message bus, with a chain indexer built for reorg safety and confirmation depth. Each service owns its own data and nothing else.
One protocol, two chains, paying out on its own.
What the build actually does, end to end.
Insurance on Ethereum, prediction markets on Solana, linked by a single settlement bridge.
Parametric cover: the policy resolves from an oracle and pays out on its own, no claim, no adjuster.
A plain request becomes a signed, settled trade on a single confirmation.
At a hundred concurrent requests, every quote came back in about fifty milliseconds.
The whole protocol runs end to end. The rest is deployment.
The full lifecycle already runs across two chains. What is left is reach and depth, both scoped and moving.
The full lifecycle
Buy, resolve, hedge, settle, claim and provide capital all run and pass end to end, on local Ethereum and Solana chains.
Public testnet
Deploying the contracts to public Ethereum and Solana test networks. The runbook is written; this is next.
Claims intelligence and disputes
Automated claim triage and on chain dispute adjudication, designed and scaffolded, moving to fully built.
The hard parts of onchain systems, already built.
The parts that sink most blockchain projects, safe contracts, sound market math, sound cross chain settlement, are the parts this build gets right. If your problem lives on chain, this is the team that has already shipped them.
Smart contract systems
Upgradeable contract architectures, tokenised vaults, signed and replay proof interactions, built to the standards and the security bar that value bearing code demands.
Onchain market makers
Automated market makers and pricing mechanisms in fixed point integer math, with the invariants that keep them solvent proven in code.
Cross chain systems
Moving state safely between chains: one way settlement, replay protection, and oracles that reach consensus across independent sources before anything is finalised.
Distributed backends
Services that coordinate over a durable message bus, with clear data ownership and a chain indexer built for reorgs and confirmation depth.
Mechanism design
Parametric products, markets and incentives designed so the economics hold under adversarial conditions, then implemented and stress tested against them.
Verification at the protocol level
Fuzzing, invariant testing and end to end suites that boot real chains and demonstrate correctness on them.
Questions
Amorphous is a La Boetie lab experiment: a decentralised protocol that pairs parametric flight delay insurance on one chain with prediction markets on those same flights on another, linked by a one way settlement bridge. It is a working prototype, built and tested end to end on local chains, and it shows the onchain engineering we do for clients.
Build on chain with people who have shipped the hard parts.
Protocols, vaults, market makers, cross chain settlement, the parts that have to be right. Tell us what you are building on chain, and we will tell you how it should be built.