Collections

Ripstr does not care what an NFT is. A position is any supported NFT plus SOL backing. What the protocol does care about is which collections a given pool will admit, and that is governed by a per-pool whitelist.

Supported standards

A "collection" on Ripstr means the Metaplex collection address:

• ✦Token Metadata — the verified collection on the NFT's metadata account.
• ✦Programmable NFTs (pNFT) — same, with the stricter transfer rules honoured.
• ✦Metaplex Core — the Core collection address.

The whitelist gates entry only

Whitelist enforcement is on by default. When it is on, a collection must be whitelisted for a new listing or a relist to be accepted.

It does not gate anything after that. Existing positions always allocate, settle and withdraw normally even if their collection is removed from the whitelist afterward. Nothing you already put in can be stranded by a curation decision made later.

Who curates

The pool's admin, or a separately configured whitelist manager, may add or remove collections on that pool.

Blocking is deliberately sticky: blocking a collection also de-whitelists it immediately, and the permissionless path cannot re-add it. Unblocking a collection does not re-whitelist it — that is a second, explicit decision.

The burn path

There is a permissionless way onto the whitelist that does not require asking anyone: irreversibly burn a configured number of designated NFTs, and an unblocked collection becomes whitelisted.

At launch the required amount is 0, which disables the path entirely. The admin can enable it later by setting a nonzero amount. When enabled, the burn is permanent, grants no control over the pool, and creates no deposit — it buys admission for a collection and nothing else.

Per-pool whitelists

The whitelist lives on the pool, not on the protocol. Two pools can admit completely different sets of collections, and a pool can be created with a whitelist already populated at creation time.

That is the mechanism behind collection pools — a pool whose whitelist contains exactly one collection, so every NFT in it is from the same set. See Create a pool for how to deploy one.