Documentation

Collections

The protocol is collection-agnostic and aims to support every NFT collection permissionlessly, starting with a curated allowlist of established collections at launch.

The protocol is collection-agnostic by design. Nothing in the core accounting cares which NFT a position holds: a position is just a listed ERC-721 paired with ETH backing, so any standard collection can in principle be deposited, weighted, priced, and settled exactly like any other1. The long-term goal is for the protocol to support every NFT collection, permissionlessly.

We're getting there in stages. At launch, deposits are restricted to a curated allowlist of established collections. This concentrates early liquidity into a handful of pools deep enough to be useful, keeps pricing and selection meaningful while the protocol is young, and avoids low-quality or malicious contracts before the broader permissionless path is opened2.

Allowlisted at launch

The allowlist will expand over time, and is intended to give way to a fully permissionless model where any collection can launch its own pool.

Technical breakdownonchain

  1. 1.
    The pool stores each position's collection address and token id and moves the NFT with the standard transferFrom / safeTransferFrom interface. Weighting, pricing, VRF selection, and settlement all operate on the ETH backing and are independent of which collection a position belongs to.
  2. 2.
    Eligibility is an owner-gated allowlist keyed by collection address, checked on deposit. Adding or removing a collection emits an event, so the eligible set is reconstructable from logs. Removing a collection blocks new deposits but never touches positions already in the pool, which settle and withdraw normally.