The Gluing Queue ranks liquidity modules based on their importance to the ecosystem and its integration partners.
Each liquidity module is ranked using the Gluing Score formula:
- Trade volume and TVL should be in millions, USD.
- If any data is missing, the protocol is placed at the bottom of the queue.
- Anyone (protocol teams, community members) can challenge rankings by submitting updated data with verifiable sources.
🔗 View the Live Queue: https://gluex.xyz/gluing-queue
If you are a protocol team or community member, you can submit a Pull Request (PR) for one of the following reasons:
- Add your protocol to the queue.
- Provide missing trade volume, TVL, or chain deployment data.
- Request a re-evaluation of your Gluing Score.
- Assign a bounty to fast-track integration.
NOTE:
Before submitting an update to the gluing queue, please ensure your liquidity module has not already been glued to GlueX.
The latest list of integrated protocols is available here: GlueX Integrated Liquidity.
- Fork this repository.
- Navigate to
docs/data/gluing_queue.json. - Update your protocol's data following the example below:
{
"protocol": "Protocol X",
"docs": "<module_docs_url>",
"chains": ["Ethereum", "Polygon"],
"trade_volume_7d_million": 100,
"tvl_million": 200,
"bounty_add_on":{
"amount": null,
"token_address": null,
"token_symbol": null,
"network": null
},
"status": "not_glued",
"active_gluers": [],
"prs": []
}- Submit a Pull Request using the PR Submission Template.
- The GlueX team will review and approve your update.
If you are an active gluer, you can submit a PR to:
- Change the status of a protocol in the queue from
not_gluedtobeing_glued. - Change the status of a protocol in the queue from
being_gluedtoglue_pending. - Add PR details to a protocol in the queue.
The status in the queue represents a protocol's integration stage.
| Status | Description |
|---|---|
not_glued |
No one has started working on this module |
being_glued |
One or more Gluers are actively working on the integration |
glue_pending |
A PR has been approved and the liquidity module is ready to be onboarded into GlueX |
glued |
Module has been integrated into the GlueX execution layer |
- Fork this repository.
- Navigate to
docs/data/gluing_queue.json. - Update the protocol's data by changing the status, adding yourself as active gluer or adding a PR according to the following example:
{
"protocol": "Protocol X",
"docs": "<module_docs_url>",
"chains": ["Ethereum", "Polygon"],
"trade_volume_7d_million": 100,
"tvl_million": 200,
"bounty_add_on":{
"amount":null,
"token_address":null,
"token_symbol":null,
"network":null
},
"status": "glue_pending",
"active_gluers": ["<gluer1_github_profile_url>", "<gluer2_github_profile_url>"],
"prs": [
{
"author": "<gluer1_github_profile_url>",
"url": "<gluer1_pr_url>",
"submitted_at": "2024-04-03T18:45:00Z"
},
{
"author": "<gluer2_github_profile_url>",
"url": "<gluer2_pr_url>",
"submitted_at": "2024-04-04T09:22:00Z"
}
]
}- Submit a Pull Request using the PR Submission Template.
- The GlueX team will review and approve your update.
The GlueX Bounty System defines how contributors ("Gluers") are rewarded for integrating liquidity modules into GlueX. The system rewards effort, originality, and ecosystem value while allowing additional incentives from the protocols themselves.
The total bounty achievable by a Gluer upon successful integration is computed as follows:
The base payout for gluing a protocol is determined according the the protocol's rank in the Glueing Queue. The current tier-to-payout system implemented for base payouts is as follows.
| Rank Range | Tier | Base Payout |
|---|---|---|
| 1 – 10 | Tier 1 | $400 |
| 11 – 30 | Tier 2 | $300 |
| 31 – 60 | Tier 3 | $200 |
| 61 – 90 | Tier 4 | $100 |
| 91 - 100 | Tier 5 | $50 |
| +100 | Tier 6 | $0 |
NOTE:
Base payouts are the primary driver of GlueX-funded rewards. They may be adjusted at the discretion of GlueX Protocol and must be announced to the Gluer community in advance.
The complexity multiplier reflects the estimated level of effort required to implement a liquidity module. It is based solely on the approximate number of functional lines of code (LoC) written by the Gluer. This provides an objective, scalable measure of technical complexity—regardless of the protocol type or use case. The more logic required to mirror the protocol's liquidity, the higher the reward.
| Complexity Tier | Approx. Lines of Code | Multiplier |
|---|---|---|
| Tier 1 | ≤ 100 | ×1.0 |
| Tier 2 | 101 – 200 | ×1.1 |
| Tier 3 | 201 – 300 | ×1.2 |
| Tier 4 | 301 – 400 | ×1.3 |
| Tier 5 | 401 – 500 | ×1.4 |
| Tier 6 | 501 – 600 | ×1.5 |
| Tier 7 | 601 – 700 | ×1.6 |
| Tier 8 | 701 – 800 | ×1.7 |
| Tier 9 | 801 – 900 | ×1.8 |
| Tier 10 | 900 – 1000 | ×1.9 |
| Tier X | +1000 | ×2.2 |
NOTE:
Reviewers should count only functional logic: comments, imports, and boilerplate should be excluded. If an integration spans multiple files, total LoC may be summed.
The Uniqueness Factor is a multiplier applied to a bounty after a Gluer submits a liquidity module. It helps differentiate between:
-
Protocols that are original and technically novel
-
Protocols that are minor forks or clones of already-glued architectures
The idea is simple. The more original and technically distinct the protocol is, the more valuable the integration—and the higher the bounty.
| Protocol Type | Multiplier |
|---|---|
| Fork / Direct Clone | ×0 |
| Modified Fork | ×0.5 |
| Original Protocol | ×1.0 |
NOTE:
Gluers are encouraged to provide documentation or context in the PR to help reviewers assess originality. GlueX Labs may validate claims through internal review or community feedback.
The bounty add-on is an optional reward assigned by the protocol itself (or its community) to accelerate its integration. This extra incentive is separate from GlueX's core bounty structure and can be denominated in any token.
Protocols can assign a bounty add-on by modifying their entry in the Glueing Queue JSON. Gluers are responsible for verifying the existence, terms, and conditions of these external rewards with the protocol team.
- Fork this repository.
- Navigate to
data/gluing_queue.json. - Update the protocol's data by populating the fileds relevant to the bounty add-on:
{
"protocol": "Protocol X",
"docs": "<module_docs_url>",
"chains": ["Ethereum", "Polygon"],
"trade_volume_7d_million": 100,
"tvl_million": 200,
"bounty_add_on": {
"amount": 1000000000,
"decimals": 6,
"token_address": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48",
"token_symbol": "USDC",
"network": "Ethereum"
},
"status": "not_glued",
"active_gluers": [],
"prs": []
}- Submit a Pull Request using the PR Submission Template.
- The GlueX team will review and approve your update.
To ensure the integrity of the gluing process, we might require bounties to be locked on an escrow account as soon as a Gluer has officially started your integration.
For further information on integration, ranking, and submitting requests, refer to:
- Live Gluing Queue – View the latest queue rankings.
- PR Submission Template – Follow the correct format when updating the queue.
- GlueX Liquidity Module Integration Guide – Technical documentation for developing a liquidity module.
For inquiries, contact the GlueX team at:
Telegram: https://t.me/+yf_US2ACNrgyNzY0
By submitting a Pull Request to integrate a liquidity module into the GlueX Protocol via the official self-integration repository, the contributor (“Gluer”) acknowledges and agrees to the terms of the GlueX Nobel Bounty System. This includes the payout methodology, discretionary nature of base bounty adjustments, and post-review scoring.
Participation in the bounty program does not constitute employment or formal engagement, and GlueX reserves the right to approve, deny, or adjust any reward based on the quality, accuracy, or legitimacy of the contribution.