# Events

At several points throughout this documentation you're going to encounter this warning : \
\
\&#xNAN;*<mark style="color:red;">**KEEP IN MIND THAT RANDOMLY TRIGGERED ON-CHAIN EVENTS WILL POSSIBLY ALTER THESE SETS OF RULES AND VALUES AND REMEMBER TO DESIGN YOUR STRATEGY ACCORDINGLY.**</mark>* \
\
We might as well dive straight into it and explain what that warning actually means. \
**The protocol is designed to stay up and running for as long as possible**. Tokenomics-wise, it involves **the Black Hole mechanism**, which grants **$TWICE** tokens sustainability. Product-wise, it sparked our ideas of building the protocol as a game centered around **locking times, vestings, fees and redistributing rewards**, which also helps to preserve **TwiceProtocol** as a whole. \
But, we also wanted to make sure the community was kept involved and interested,  so we had to build something else to maintain your excitement as the project lives on.&#x20;

<figure><img src="/files/45RoeSwnBZddxNAut3c0" alt=""><figcaption></figcaption></figure>

**We have designed around 50 unique events that will be triggered sporadically throughout the project's course**. **At any point can an event come and subvert your expectations of the protocol by changing an APR, a tax fee, by introducing new mechanics or removing ones.** Other events will be more built around the community side of the project, incentivizing interactions and engagement. However, **most events will essentially allow us to patch the protocol in real time**, and adjust it in the best way possible to ensure its sustainability. Some events will be **brief**, some will be **everlasting**.

Overall, events allow us to keep you all hooked as, **in order to maximise your potential income, you will have to perpetually fix and tune your strategy and positions**. Nothing tells you that the stuff that works best on day one will work best on day two, let alone day 40.&#x20;


---

# 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://twiceprotocol.gitbook.io/twiceprotocol/welcome-to-twiceprotocol/events.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.