> For the complete documentation index, see [llms.txt](https://cifer.gitbook.io/cifer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cifer.gitbook.io/cifer-docs/ghost-economy/cifer-access-auction.md).

# Cifer Access Auction

The proposed Cifer Access Auction connects Web2 subscription activity with the on-chain Wisp and Fantom market—without requiring customers to understand wallets, ETH on Robinhood Chain, or NFTs.

> **A subscription always activates. A market purchase happens only when an eligible offer clears Cifer's maximum bid.**

### Core principle

A Web2 customer is buying Cifer Premium, not an NFT.

When the auction is active, Cifer may separately source the matching on-chain access character:

| Web2 purchase            | Eligible auction route                                               |
| ------------------------ | -------------------------------------------------------------------- |
| Monthly Premium          | Buy and consume one eligible Wisp                                    |
| Yearly Premium           | Buy and consume one eligible Fantom                                  |
| Alternative yearly route | Buy ten eligible Wisps, converge them into a Fantom, then consume it |

The yearly router compares the valid direct Fantom route with the complete ten-Wisp route, including convergence and execution costs.

### Subscription flow

```mermaid
flowchart TD
    A["Alice buys Premium with Web2 checkout"] --> B["Premium activates"]
    B --> C["Auction router checks eligible offers"]
    C --> D{"Cheapest route at or below maximum bid?"}
    D -->|Yes| E["Purchase through Cifer Marketplace"]
    E --> F["Pay seller and consume character"]
    D -->|No| G["No NFT purchase"]
    G --> H["Cifer retains subscription revenue"]
```

Alice receives the same Premium experience in both outcomes. She does not need a wallet and does not take custody of the purchased character.

### Capped reverse auction

Owners compete by offering eligible characters for sale.

1. The owner lists an eligible Wisp or Fantom under the published marketplace rules.
2. The listing states its sell price and validity period.
3. A subscription event or auction batch creates conditional demand.
4. The router finds the cheapest valid route.
5. Cifer executes only when the total route cost is at or below its maximum bid.
6. If every route is too expensive, no purchase occurs.
7. A winning character is settled and consumed for the matching subscription.

The maximum bid protects Cifer from subsidizing an overpriced market. Subscription revenue remains with Cifer when no route clears the cap.

### Relationship to MARK and Ghost Eggs

MARK, Direct Eggs, and the Access Auction serve different purposes:

* Validated creators earn MARK and spend 100 MARK to redeem from the Creator Reward Pool.
* A verified Swaymark account may mint a Direct Egg for 0.004 ETH on Robinhood Chain from the separate Direct Mint Pool without earning MARK.
* Direct mints cannot consume Creator Reward inventory and are not part of the $20,000 creator allocation.
* The Access Auction purchases eligible revealed Wisps or Fantoms from holders when Web2 subscription demand clears Cifer's maximum bid.
* Egg redemption creates ownership; an Access Auction purchase removes and consumes an eligible character.

### Relationship to the January Creator Reward buyback

Cifer plans to open a voluntary buyback early enough for accepted transactions involving eligible MARK-funded Creator Reward characters to complete no later than **31 January 2027**. Direct Egg characters are excluded.

| Access Auction                            | January Creator Reward buyback                                        |
| ----------------------------------------- | --------------------------------------------------------------------- |
| Ongoing subscription-driven demand        | Time-bound creator-campaign program                                   |
| Eligible Wisp and Fantom routes initially | Eligible Creator Reward Pool Alpha, Omega, Wisp, and Fantom           |
| Cheapest valid route below a maximum bid  | Published terms accepted voluntarily by eligible holders              |
| Any eligible origin may compete           | MARK-funded Creator Reward origin only                                |
| May produce no purchase                   | Subject to published price, funding, submission, and acceptance rules |

The final buyback price, funding, opening date, submission deadline, settlement asset, acceptance rules, and support process must be published before activation.

### Owner access

Once the marketplace is live, every owner may list an eligible, unconsumed, unlocked character:

* Alpha and Omega may be offered through the general marketplace.
* Wisps and Fantoms may be offered through the general marketplace and Access Auction.
* Eligible MARK-funded Creator Reward characters may also use the separate January buyback.
* Direct Egg characters may use the general marketplace and, if Wisp or Fantom, the Access Auction, but not the January Creator Reward buyback.
* Locked, consumed, burned, committed, or otherwise ineligible assets cannot be sold.

{% hint style="success" %}
**Holding preserves optionality.** Depending on its stage and origin, an eligible character may remain collectible, participate in lineage mechanics, compete for subscription demand, be listed for another buyer, enter the January Creator Reward buyback when eligible, or be consumed for Premium.
{% endhint %}

### Settlement

Every completed ordinary paid marketplace transaction settles in ETH on Robinhood Chain and follows the published split:

* 90% of the displayed sale price to the seller.
* 10% to Cifer.
* Atomic payment and character transfer.
* Immediate consumption after a successful subscription-auction purchase.

The January Creator Reward buyback settlement will be published separately before that program opens.

### What the auction does not promise

The Access Auction does not guarantee:

* That every subscription causes an NFT purchase.
* That every listed character is selected.
* A minimum price, resale floor, buyer, sale date, or recurring demand.
* That holding produces income or appreciation.
* That Cifer will purchase above its configured maximum bid.

These auction limitations do not change the separate plan to complete accepted buybacks of eligible MARK-funded Creator Reward characters by 31 January 2027; the two mechanisms have different eligibility and pricing.

### Rules required before activation

Cifer must publish or finalize:

* Real-time versus batch-auction cadence.
* Maximum-bid formula, approval authority, and disclosure policy.
* Offer escrow and cancellation rules.
* Tie-breaking when offers have the same price.
* Eligibility validation and failure recovery.
* Ten-Wisp aggregation and convergence execution.
* Payment-channel and payment-reversal controls.
* Auction monitoring, reporting, and emergency pause authority.

Until these controls are implemented, audited, and activated, the Access Auction remains a proposed mechanism.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cifer.gitbook.io/cifer-docs/ghost-economy/cifer-access-auction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
