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

# protector notes

### 🌿 *<mark style="color:red;">**`Closed`**</mark>*&#x4F;live Pantheon Pool at [<mark style="color:red;">**OOX Marketplace**</mark>](https://oox.art/marketplace/collections/OLVP-e06a55?tab=staking)

New **staking pool**  for all NFTs holders from the Olive Pantheon collection at [`OOX Marketplace`](https://oox.art/marketplace/collections/OLVP-e06a55?tab=staking) **.**  <mark style="color:$primary;">**Harvest 15.000 $OLV - Duration 60days**</mark>

08/11 Protectors *Hash :* 31d2ef2b08817017f8a369bb9d43e27ae6edfc0e093433f415da911dfc6d125d

*Olive Protector* guards the ancient orchards with courage and charm. Armed with a gleaming sword and a handcrafted shield bearing the mark of his lineage. Each Olive Protector safeguards the grove and embodies courage, purity and trust. When returned, half the strength flows back to its bearer, and half nourishes the Olive ecosystem with $OLV. Stability through faith. Growth through harmony.&#x20;

* Weapon: Silver Leaf Blade
*

{
\
"name": "Olive Protector Card",
\
"description": "A guardian of trust — An Olive Protector to sustain the Olive Grove through yield and buybacks.",
\\

\
{"trait\_type": "Type", "value": "Olive Protector"},
\
{trait\_type": "Shield", "value": "Emblem of the Grove"},

{"trait\_type": "Mood", "value": "Fearlessly Optimistic"},
\
{"trait\_type": "Weapon", "value": "Silver Leaf Blade"},

\
{"trait\_type": "Staked Amount", "value": "10 EGLD"},
\
{"trait\_type": "Backing Protocol", "value": "Hatom"},
\
{"trait\_type": "Return Ratio", "value": "50 / 50 Split"},
\\

{"trait\_type": "Spirit Alignment", "value": "Trust"},
\\

{"trait\_type": "Buyback Trigger", "value": "25% OLV Decrease"},
\
{"trait\_type": "Buyback Share", "value": "5% Staked EGLD"},
\
{"trait\_type": "Reward Token", "value": "$OLV"},

The **Olive Protector Card** is a limited SFT (10 total) representing the founding guardians of the Olive ecosystem.\
Allocated funds will be staked  into the Hatom Protocol, generating yield used for **continuous $OLV buybacks** and **ecosystem support (10 Cards - 10\*egld per card = 100\*egld)**

When an $OLV price drop threatens the grove, a **buyback protocol** activates — protecting the ecosystem and its holders.\
If a Protector chooses to return their card, **50% of the staked EGLD** is returned, while the other **50%** fuels **$OLV buybacks** which will be retured or directed to the pool of their choice (NFT or Token Farm).

### 🌿   *<mark style="color:red;">**`Closed`**</mark>* Olive Pantheon’s Treasury Staking Pool (new Dynamic )

New Dynamic **exclusive staking pool** for holders of **Legendary** ,**Norse Gods &** **Rare** NFTs from the Olive Pantheon collection at [`OOX Marketplace`](https://oox.art/marketplace/collections/OLVP-e06a55?tab=staking) **.**  Only 13 are chosen {Class: Major Hero, Hero King, Norse God, Legendary, Rare} <mark style="color:$primary;">**Harvest 40.000 $OLV - Duration 90 days**</mark>


---

# 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://olivemvx.gitbook.io/olivemvx/protector-notes.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.