> For the complete documentation index, see [llms.txt](https://docs.geminon.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geminon.fi/safety-tips.md).

# Safety tips

Risks in a crypto protocol can come from both outside (hackers) and inside (malicious team). External attackers can target the protocol (flash loans, reentrancy attacks...) or users (phishing, website spoofing).

As a user, you can't do anything to prevent external attacks on the protocol (that's our job), but you can do everything to prevent attacks that are directed at you and, if the protocol is well designed, you can also do a lot to help prevent internal attacks and minimize their consequences.

In this section we give you some tips to be safer when interacting with Geminon Protocol.

### Always track the actions of the deployer address

The deployer of the smart contracts is the owner and therefore is the only address that can use certain functions in the contracts, some of which are critical for the safety of the protocol since their use in a malicious way can compromise the value of the tokens. 

All critical functions of the protocol have timelocks implemented as a security measure as they facilitate public control of those actions.

For this reason, the public accountability of the owner address is very important. Always review periodically the actions of that address over the protocol smart contracts in a blockchain explorer and check that they have been publicly announced and their objectives and motivation clearly explained.

Actions that must always be announced by the owner:

* Add minter to the GEX token or the stablecoins (timelock 7 days).
* Apply price feed change of a Genesis Liquidity Pool (timelock 7 days).
* Apply Stablecoin Minter change in a Genesis Liquidity Pool (timelock 30 days).
* Apply Oracle change in a Genesis Liquidity Pool (timelock 30 days).
* Apply Treasury Lender change in a Genesis Liquidity Pool (timelock 30 days).
* Set pool weight of a Genesis Liquidity Pool, specially if it is a lower weight and this action is repeated several times.
* Request Migration of a Genesis Liquidity Pool (timelock 30 days + reduce pool weight to less than 5% previously and 2% after + mint gets paused in the pool).
* Request Remove of a Genesis Liquidity Pool (timelock 30 days+ reduce pool weight to less than 5% previously and 1% after + mint gets paused in the pool).

You can find the deployer address in the corresponding section:

{% content-ref url="/pages/astSBmKxXda9pD5Wjskt" %}
[Deployment addresses](/geminon-protocol/deployment-addresses.md)
{% endcontent-ref %}


---

# 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.geminon.fi/safety-tips.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.