Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
23 commits
Select commit Hold shift + click to select a range
9972dd0
fix: double title and inconsistent spacing issues /defi
bguiz Oct 30, 2025
2dea5b1
fix: removed h1s from MDX body and shifted to frontmatter title field
bguiz Oct 30, 2025
0552c01
fix: update broken links to remove trailing '/README.md'
bguiz Oct 30, 2025
23d705d
fix: more broken links
bguiz Oct 30, 2025
90c2d5d
fix: even more broken links
bguiz Oct 30, 2025
ea2c3bd
fix: even more broken links
bguiz Oct 30, 2025
e5aeee7
refactor: move /.gitbook/assets/ to /img/
bguiz Oct 30, 2025
2e9b9be
fix: broken links for image files
bguiz Oct 30, 2025
c4f93db
fix: broken links upstream from injective-core spec files
bguiz Oct 30, 2025
d95769f
fix: broken link from upstream cosmos-sdk specs
bguiz Oct 30, 2025
10ffab6
fix: copy script to replace cosmos-sdk URLs
bguiz Oct 30, 2025
e27781b
refactor: mv /README/ to /
bguiz Oct 31, 2025
6df8aec
refactor: mv MDX file in parent dir into index within same dir for: /…
bguiz Oct 31, 2025
e1ce05a
refactor: mv ./dirname.mdx file in parent dir into ./dirname/index.md…
bguiz Oct 31, 2025
16f94da
refactor: mv ./dirname.mdx file in parent dir into ./dirname/index.md…
bguiz Oct 31, 2025
4de1277
refactor: mv ./dirname.mdx file in parent dir into ./dirname/index.md…
bguiz Oct 31, 2025
4bea9d6
refactor: mv (part 2) ./dirname.mdx file in parent dir into ./dirname…
bguiz Oct 31, 2025
d55afed
chore: update files from upstream repo - cosmos-sdk
bguiz Oct 31, 2025
f6b2080
chore: update files from upstream repo - injective-core
bguiz Oct 31, 2025
ef07308
feat: update copy injective docs script
bguiz Oct 31, 2025
450d0f2
fix: replace table with cards on /
bguiz Oct 31, 2025
da9501a
fix: syntax for cards in /developers and /developers-evm
bguiz Oct 31, 2025
e34ec35
fix: add cards for /developers-evm /developers-native /infra
bguiz Oct 31, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
51 changes: 0 additions & 51 deletions .gitbook/README.mdx

This file was deleted.

File renamed without changes.
9 changes: 0 additions & 9 deletions .gitbook/defi.mdx

This file was deleted.

4 changes: 3 additions & 1 deletion .gitbook/defi/bridge.mdx
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
# Bridge
---
title: Bridge
---

Bridging assets into the Injective ecosystem is effortless, with support for 23+ networks and growing. Here, you'll find step-by-step instructional guides for bridging assets from Ethereum, Solana, via IBC, and using the Wormhole protocol, making it easy to connect with Injective's ecosystem.
4 changes: 3 additions & 1 deletion .gitbook/defi/community-burn.mdx
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@
# Community Burn
---
title: Community Burn
---

### What is the Community Burn?

Expand Down
5 changes: 3 additions & 2 deletions .gitbook/defi/governance.mdx
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@
# Governance
---
title: Governance
---

## Governance

Expand Down Expand Up @@ -29,4 +31,3 @@ If a proposal passes, Injective contributors will begin to work together to put
* For more details on the governance proposal process, read Injective's [blog](https://injective.com/blog/injective-governance-proposal-procedure/).
* To participate in blockchain governance, join the [Injective Discord](https://discord.com/invite/NK4qdbv) or the [Injective Governance Forum](https://gov.injective.network).
* Visit the [Injective Hub](https://injhub.com/governance) to view Injective proposals and participate in voting.

8 changes: 8 additions & 0 deletions .gitbook/defi/index.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
title: DeFi
description: >-
This section helps traders to learn more about trading instruments and start
trading on Injective
---

Here you can find a comprehensive overview of Injective's **exchange module**, as well as tutorials, guides, reward programs, leaderboard competitions, and general resources for developers and API traders.
13 changes: 6 additions & 7 deletions .gitbook/defi/open-liquidity-program/eligibility.mdx
Original file line number Diff line number Diff line change
@@ -1,16 +1,15 @@
---
description: How to Qualify and Remain Qualified for OLP Rewards
title: Eligibility
---

# Eligibility

## Clean Slate Qualification

An Injective address can qualify for OLP by meeting the following criteria:

* The **address must be opted out of the Trade & Earn (T\&E) program** prior to the start of the qualification process. The address will not earn T\&E rewards during the qualification process. See examples in [Python](https://github.com/InjectiveLabs/sdk-python/blob/master/examples/chain\_client/24\_MsgRewardsOptOut.py), [Go](https://github.com/InjectiveLabs/sdk-go/blob/master/examples/chain/24\_MsgRegisterAsDMM/example.go), and [TS](https://github.com/InjectiveLabs/injective-ts/wiki/04CoreModulesExchange#msgrewardsoptout) for opting out programatically.
* Note: Eligibility for the qualification process begins at 00:00 UTC the day after the opt out is complete. To check if an address has been successfully opted out of T\&E, [this list can be cross referenced](https://lcd.injective.network/injective/exchange/v1beta1/opted\_out\_of\_rewards\_accounts).
* The address's maker volume must account for **at least 0.25% of the total daily exchange maker volume of** [**eligible markets**](./eligible-markets.md) **for 3 days in a row** in the same epoch. Self trading is strictly prohibited.
* The address's maker volume must account for **at least 0.25% of the total daily exchange maker volume of** [**eligible markets**](./eligible-markets/) **for 3 days in a row** in the same epoch. Self trading is strictly prohibited.

Assuming both of these requirements have been met, the address will qualify for OLP rewards on the 4th day at 00:00 UTC. Once qualified, an address will remain eligible for rewards through the rest of the epoch unless special circumstances (e.g. abusing the system, wash trading, etc.) compel the removal of the address. Note that activity prior to qualification will not count towards rewards.

Expand All @@ -22,17 +21,17 @@ See [documentation on the Injective `authz` module](https://docs.injective.netwo

## Maintaining Next Epoch Eligibility/Pre-Qualification

To automatically qualify for the next epoch after qualifying for the current epoch, an **address must account for at least 0.25% of total exchange maker volume** of [eligible markets](./eligible-markets.md) (not including KAVA reward markets) from the date of qualification to the last day of the epoch. 
To automatically qualify for the next epoch after qualifying for the current epoch, an **address must account for at least 0.25% of total exchange maker volume** of [eligible markets](./eligible-markets/) (not including KAVA reward markets) from the date of qualification to the last day of the epoch. 

* Example: Address `inj1a` enters epoch 21 ineligible for OLP rewards. `inj1a` accounts for 1%, 0.1%, and 0.2% of total daily exchange maker volume of [eligible markets](./eligible-markets.md) on days 1, 2, and 3 of epoch 21, respectively. On days 4, 5, and 6, `inj1a` accounts for 0.5% of the applicable volume each day. `inj1a` qualifies on day 7 of the epoch. To maintain eligibility/qualification for epoch 22, `inj1a` must account for at least 0.25% of the cumulative applicable maker volume from day 7 through day 28 of epoch 21. If the cumulative maker volume of [eligible markets](./eligible-markets.md) for this period (days 7 through 28) was $100M, then `inj1a` must account for $250,000 of cumulative maker volume in those markets within the same period.
* Example: Address `inj1a` enters epoch 21 ineligible for OLP rewards. `inj1a` accounts for 1%, 0.1%, and 0.2% of total daily exchange maker volume of [eligible markets](./eligible-markets/) on days 1, 2, and 3 of epoch 21, respectively. On days 4, 5, and 6, `inj1a` accounts for 0.5% of the applicable volume each day. `inj1a` qualifies on day 7 of the epoch. To maintain eligibility/qualification for epoch 22, `inj1a` must account for at least 0.25% of the cumulative applicable maker volume from day 7 through day 28 of epoch 21. If the cumulative maker volume of [eligible markets](./eligible-markets/) for this period (days 7 through 28) was $100M, then `inj1a` must account for $250,000 of cumulative maker volume in those markets within the same period.

If the address was eligible for the entire epoch through a previous epoch's pre-qualification, that address must account for at least 0.25% of the maker volume of [eligible markets](./eligible-markets.md) in the entire epoch. 
If the address was eligible for the entire epoch through a previous epoch's pre-qualification, that address must account for at least 0.25% of the maker volume of [eligible markets](./eligible-markets/) in the entire epoch. 

* Example: Address `inj1a` enters epoch 22 prequalified from maintaining eligibility in epoch 21. Suppose the cumulative maker volume of [eligible markets](./eligible-markets.md) in epoch 22 totals $200M. Then `inj1a` must contribute at least $500,000 of the $200M in [eligible markets](./eligible-markets.md) by the end of epoch 22 to maintain automatic eligibility for epoch 23.

## Disqualification

**Any address that fails to account for at least 0.25% of applicable maker volume in an epoch will be disqualified from OLP at the start of the next epoch**. If the address wishes to rejoin the program, the address must go through the [clean slate qualification process](eligibility.md#clean-slate-qualification) again (though the address does not have to opt out of T\&E another time). Note that any liquidity contributed on days that the address is not eligible will not be rewarded retroactively once the address requalifies.
**Any address that fails to account for at least 0.25% of applicable maker volume in an epoch will be disqualified from OLP at the start of the next epoch**. If the address wishes to rejoin the program, the address must go through the [clean slate qualification process](./eligibility/#clean-slate-qualification) again (though the address does not have to opt out of T\&E another time). Note that any liquidity contributed on days that the address is not eligible will not be rewarded retroactively once the address requalifies.

<Callout icon="info" color="#07C1FF" iconType="regular">
Disqualification occurs at the end of each epoch, meaning addresses continue to accrue rewards within the epoch regardless of next epoch eligibility.
Expand Down
3 changes: 1 addition & 2 deletions .gitbook/defi/open-liquidity-program/eligible-markets.mdx
Original file line number Diff line number Diff line change
@@ -1,9 +1,8 @@
---
description: Markets Eligible for Rewards in OLP
title: Eligible Markets
---

# Eligible Markets

To view a list of markets currently eligible for OLP rewards, please refer to the [OLP Dashboard](https://trading.injective.network/program/liquidity):&#x20;

<iframe src="https://trading.injective.network/program/liquidity" className="w-full h-96 rounded-xl"></iframe>
6 changes: 2 additions & 4 deletions .gitbook/defi/open-liquidity-program/epochs.mdx
Original file line number Diff line number Diff line change
@@ -1,14 +1,12 @@
---
description: OLP Epoch Duration and Schedule
title: Epochs
---

# Epochs

An epoch is the period of time in which market makers are evaluated based on their relative performance. Several metrics are cumulatively tracked during each epoch, which reset upon the commencement of a new epoch. Rewards are disbursed after the completion each epoch (see [Rewards Disbursement](reward-disbursements.md)). Currently, **each epoch is 28 days long**.&#x20;
An epoch is the period of time in which market makers are evaluated based on their relative performance. Several metrics are cumulatively tracked during each epoch, which reset upon the commencement of a new epoch. Rewards are disbursed after the completion each epoch (see [Rewards Disbursement](./reward-disbursements/)). Currently, **each epoch is 28 days long**.&#x20;

The **first public OLP epoch (epoch 21) began on June 13, 2023 at 0:00 UTC**.

Start and end dates for OLP epochs can be found in the following table, which is updated occasionally (typically a few months in advance) to include future epochs :&#x20;

<table><thead><tr><th width="99.33333333333331" align="center">Epoch</th><th align="right">Start Date (UTC)</th><th align="right">End Date (UTC)</th></tr></thead><tbody><tr><td align="center">21</td><td align="right">Jun 13, 2023 00:00:00 </td><td align="right">Jul 11, 2023 00:00:00 </td></tr><tr><td align="center">22</td><td align="right">Jul 11, 2023 00:00:00 </td><td align="right">Aug 8, 2023 00:00:00 </td></tr><tr><td align="center">23</td><td align="right">Aug 8, 2023 00:00:00 </td><td align="right">Sep 5, 2023 00:00:00 </td></tr><tr><td align="center">24</td><td align="right">Sep 5, 2023 00:00:00 </td><td align="right">Oct 3, 2023 00:00:00 </td></tr><tr><td align="center">25</td><td align="right">Oct 3, 2023 00:00:00 </td><td align="right">Oct 31, 2023 00:00:00 </td></tr><tr><td align="center">26</td><td align="right">Oct 31, 2023 00:00:00 </td><td align="right">Nov 28, 2023 00:00:00 </td></tr><tr><td align="center">27</td><td align="right">Nov 28, 2023 00:00:00 </td><td align="right">Dec 26, 2023 00:00:00 </td></tr><tr><td align="center">28</td><td align="right">Dec 26, 2023 00:00:00 </td><td align="right">Jan 23, 2024 00:00:00 </td></tr><tr><td align="center">29</td><td align="right">Jan 23, 2024 00:00:00 </td><td align="right">Feb 20, 2024 00:00:00 </td></tr><tr><td align="center">30</td><td align="right">Feb 20, 2024 00:00:00 </td><td align="right">Mar 19, 2024 00:00:00 </td></tr><tr><td align="center">31</td><td align="right">Mar 19, 2024 00:00:00 </td><td align="right">Apr 16, 2024 00:00:00 </td></tr><tr><td align="center">32</td><td align="right">Apr 16, 2024 00:00:00 </td><td align="right">May 14, 2024 00:00:00 </td></tr><tr><td align="center">33</td><td align="right">May 14, 2024 00:00:00 </td><td align="right">Jun 11, 2024 00:00:00 </td></tr><tr><td align="center">34</td><td align="right">Jun 11, 2024 00:00:00 </td><td align="right">July 9, 2024 00:00:00</td></tr><tr><td align="center">35</td><td align="right">July 9, 2024 00:00:00</td><td align="right">Aug 6, 2024 00:00:00</td></tr><tr><td align="center">36</td><td align="right">Aug 6, 2024 00:00:00</td><td align="right">Sep 3, 2024 00:00:00</td></tr><tr><td align="center">37</td><td align="right">Sep 3, 2024 00:00:00</td><td align="right">Oct 1, 2024 00:00:00</td></tr><tr><td align="center">38</td><td align="right">Oct 1, 2024 00:00:00</td><td align="right">Oct 29, 2024 00:00:00</td></tr><tr><td align="center">39</td><td align="right">Oct 29, 2024 00:00:00</td><td align="right">Nov 26, 2024 00:00:00</td></tr><tr><td align="center">40</td><td align="right">Nov 26, 2024 00:00:00</td><td align="right">Dec 24, 2024 00:00:00</td></tr><tr><td align="center">41</td><td align="right">Dec 24, 2024 00:00:00</td><td align="right">Jan 21, 2025 00:00:00</td></tr><tr><td align="center">42</td><td align="right">Jan 21, 2025 00:00:00</td><td align="right">Feb 18, 2025 00:00:00</td></tr><tr><td align="center">43</td><td align="right">Feb 18, 2025 00:00:00</td><td align="right">Mar 18, 2025 00:00:00</td></tr><tr><td align="center">44</td><td align="right">Mar 18, 2025 00:00:00</td><td align="right">Apr 15, 2025 00:00:00</td></tr><tr><td align="center">45</td><td align="right">Apr 15, 2025 00:00:00</td><td align="right">May 13, 2025 00:00:00</td></tr><tr><td align="center">46</td><td align="right">May 13, 2025 00:00:00</td><td align="right">Jun 10, 2025 00:00:00</td></tr><tr><td align="center">47</td><td align="right">Jun 10, 2025 00:00:00</td><td align="right">July 8, 2025 00:00:00</td></tr><tr><td align="center">48</td><td align="right">July 8, 2025 00:00:00</td><td align="right">Aug 5, 2025 00:00:00</td></tr><tr><td align="center">49</td><td align="right">Aug 5, 2025 00:00:00</td><td align="right">Sep 2, 2025 00:00:00</td></tr><tr><td align="center">50</td><td align="right">Sep 2, 2025 00:00:00</td><td align="right">Sep 30, 2025 00:00:00</td></tr><tr><td align="center">51</td><td align="right">Sep 30, 2025 00:00:00</td><td align="right">Oct 28, 2025 00:00:00</td></tr><tr><td align="center">52</td><td align="right">Oct 28, 2025 00:00:00</td><td align="right">Nov 25, 2025 00:00:00</td></tr><tr><td align="center">53</td><td align="right">Nov 25, 2025 00:00:00</td><td align="right">Dec 23, 2025 00:00:00</td></tr></tbody></table>

5 changes: 3 additions & 2 deletions .gitbook/defi/open-liquidity-program/fee-tiers.mdx
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
# Fee Tiers
---
title: Fee Tiers
---

Traders who meet threshold criteria for minimum staked INJ and minimum trading volume on a 28-day rolling basis are eligible for discounts on Injective trading fees. More information can be found on the page linked below.

<iframe src="https://helixapp.com/fee-discounts" className="w-full h-96 rounded-xl"></iframe>

Original file line number Diff line number Diff line change
@@ -1,10 +1,9 @@
---
description: OLP Reward Allocations to Markets and Institutional Liquidity Providers
title: Flexible Reward Allocations
---

# Flexible Reward Allocations

Part of the changes implemented for epoch 43 include a fully discretionary dynamic reward to bootstrap liquidity for certain markets at specific times. Following the exact same calculations detailed in [reward-allocations.md](reward-allocations.md "mention"), and the classic formula/scoring methodology to determine a liquidity provider's share of the total reward for a market, this will be accomplished through the concept of Mini Epochs.
Part of the changes implemented for epoch 43 include a fully discretionary dynamic reward to bootstrap liquidity for certain markets at specific times. Following the exact same calculations detailed in [reward-allocations.md](./reward-allocations/ "mention"), and the classic formula/scoring methodology to determine a liquidity provider's share of the total reward for a market, this will be accomplished through the concept of Mini Epochs.

Mini Epochs are flexible in that they are not constrained by the typical 00:00 UTC starting/ending point for a pair to exist in a Primary Epoch. Mini Epochs can begin or end at any time within a Primary Epoch, though they cannot span across multiple epochs.

Expand Down
Loading