> For the complete documentation index, see [llms.txt](https://guardian-validator.gitbook.io/guardian-validator/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian-validator.gitbook.io/guardian-validator/road-map.md).

# Road Map

### :heavy\_check\_mark:  Extensive research and documentation

:white\_check\_mark:  Market and economic data.\
:white\_check\_mark:  Current validator standards.\
:white\_check\_mark:  Code base & environment.\
:white\_check\_mark:  NFT types and deployment.\
:white\_check\_mark:  Validator Client and best practices.\
:white\_check\_mark:  RPC in depth analysis.

### :heavy\_check\_mark:  Deploy Testnet Validator

:white\_check\_mark:  Configuration optimization.\
:white\_check\_mark:  Performance maximization.\
:white\_check\_mark:  Test Anza Client extensively.\
:white\_check\_mark:  Move to Jito Client and test.\
:white\_check\_mark:  Automate Jito Client update process.\
:white\_check\_mark:  Implement advanced monitoring and alerting.\
:white\_check\_mark:  Implement hotswap-faliover system.

### :heavy\_check\_mark: LST Deployment

:white\_check\_mark:  SPL pool testnet activation.\
:white\_check\_mark:  Block rewards sharing mechanism.\
:white\_check\_mark:  LST Validator management.\
:white\_check\_mark:  LST Metadata management.\
:white\_check\_mark:  LST Sanctum Listing.

### :heavy\_check\_mark: Website and Socials

:white\_check\_mark:  Design and structure.\
:white\_check\_mark:  Build and Deploy.\
:white\_check\_mark:  Speed optimize.\
:white\_check\_mark:  Performance test.\
:white\_check\_mark:  Security and DDOS protection.\
:white\_check\_mark:  Deploy Socials.

:white\_check\_mark:   Source a top-tier artist.\
:white\_check\_mark:   Test NFT types and deploy.\
:white\_check\_mark:   P.O.C rewards sharing.\
:white\_check\_mark:   Start white-listing process.\
:black\_square\_button:  NFT  launch and mint.

### :heavy\_check\_mark:  Mainnet-beta Validator

:white\_check\_mark:  Secure state of the art data-center & hardware.\
:white\_check\_mark:  Create advanced monitoring and logger.\
:white\_check\_mark:  Apply for SFPD.\
:white\_check\_mark:  Mainnet-beta Launch.

### :black\_square\_button: Post-MB-launch&#x20;

:white\_check\_mark: Supercharged Solana fund deployment.\
:white\_check\_mark: Stake-pool optimization.\
:black\_square\_button:  Marketing strategy deployment.\
:black\_square\_button:  Partnership reveals and expansion.\
:black\_square\_button:  Airdrop Guardian NFT's with partner tokens.\
:black\_square\_button:  Announce un-revealed plans.

More announcements soon!<br>

## :heart:

\ <br>


---

# 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://guardian-validator.gitbook.io/guardian-validator/road-map.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.
