> For the complete documentation index, see [llms.txt](https://docs.honey.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.honey.fun/our-vision/rfa-approval.md).

# RFA approval

<figure><img src="/files/8YDoIRQqoNMf9MtNiQk6" alt=""><figcaption></figcaption></figure>

We’re proud to announce that as one of the protocols building on Berachain, we’ve received **$BERA** tokens through the RFB program. On our testnet, **Bartio**, over **120,000 transactions** have been executed, and every tester who wasn’t flagged as Sybil by our verification process will receive their token allocation.

What’s even more noteworthy is that **70% of the funds we received** will be allocated as rewards for users and liquidity incentives on the mainnet. This ensures a strong, long-term position for us within the Berachain ecosystem.\
\
Proof: <https://blog.berachain.com/blog/request-for-broposal-update-applications>


---

# 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://docs.honey.fun/our-vision/rfa-approval.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.