# Roadmap

### Bootstrap Phase

The Voyage Protocol is a novel and complex protocol that pushes the boundaries. In order to safeguard it from denial-of-service and other early existential threats, we begin with a cautious approach, progressively increasing the inherent level of decentralization and permissiveness as the protocol matures with observation and analysis of real-world data.

Hence, during the bootstrap phase we plan to enable only the purchases of the **floor-tier assets** for the collections we support.

### Post-Bootstrap

#### Support for non-floor assets

In collaboration with data and analytics partners, our immediate post-bootstrap priority is to utilise predictive models for automated valuation of NFTs (e.g. NFTBank, Upshot or Nansen) that account for factors such as:

* **Attributes** (e.g. land proximity to city);
* **Rarity** (e.g. combination of desired traits);
* **Lagged** **prices.**

This will enable Voyage to issue credit for non-floor assets within predetermined risk parameters with minimal risk to the protocol’s ongoing solvency, as the protocol will be able to appraise assets at purchase and liquidation with tolerable error.

As qualitative factors will inevitably influence the value of non-floor assets, we additionally plan to implement a dutch auction system for the liquidation of such NFTs. Automatic valuations will be used to determine auction start price, while the ultimate value will be left to the market to determine.


---

# Agent Instructions: 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:

```
GET https://docs.voyage.finance/voyage/whitepaper/roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.