> For the complete documentation index, see [llms.txt](https://docs.feg.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feg.io/resources/archive/roxary-custom-upgrades.md).

# ROXary Custom Upgrades

Development Advisory

### FEG's lead developer, [FEGrox](https://twitter.com/lifeisdefi?lang=en), announces his new ROXary service!

With the release of SmartDeFi staking on the horizon and the ability to offer FEG stakers infinite reward types, I have started to utilize that ability and find ways to generate more reward types.

One of the best things I have to offer is my unique ability to work with coding and give direction. So I put out some feelers to see if any up-and-coming projects need the service of a technical advisor in exchange for tokens we can allocate as rewards to FEG stakers.

Now, let's get more detailed as to what that means. 

**Advisory does not mean the FEG project is affiliated, nor am I on the team of any/all advised projects; it** only means that I agreed to help advise on future codebase and utility ideas. I cannot guarantee any success in any project or protocol. My advisory only provides advice on code and planning. Unless it is strictly said otherwise, an advisory position is just as it sounds.

I am focused on developing ways to give FEG stakers more reward options and help move the industry forward. One of the best ways to do that is to allow others to benefit from my advisory services. All proceeds from this service will be allocated to FEG stakers, and I am building this decentralized service so FEG stakers can have a voice on who is allowed to benefit from this service.

I hope that makes it more straightforward as we advance.

\~\~ROX<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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.feg.io/resources/archive/roxary-custom-upgrades.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.