Join the dedicated Builder Chat to ask for feedback and discuss technical questions:Telegram: <a class="link" href="https://t.me/+Xfx2Mx6pbRYxMzA5">https://t.me/+Xfx2Mx6pbRYxMzA5</a><h2 class="heading-node">Context</h2>We want to build a dashboard that will compare quotes and liquidity depth across NEAR Intents and its leading competitors, but first we need to gather the proper data.<h2 class="heading-node">Objective</h2>Adapt <a class="link" href="https://github.com/NEARBuilders/data-provider-playground" target="">this template repository</a> to build an <a class="link" href="https://plugin.everything.dev/" target="">every-plugin</a> plugin that collects and normalizes the desired market data from one of the competitors of NEAR Intents. The various plugins built from this bounty will be compared and aggregated to build our future dashboard.Build a plugin that collects data from one of the below providers (choose exactly one for your submission, you may submit multiple times):<ul class="list-node tight" data-tight="true"><li>LayerZero: <a class="link" href="https://layerzero.network/">https://layerzero.network/</a></li><li>Wormhole: <a class="link" href="https://wormhole.com/">https://wormhole.com/</a></li><li>CCTP: <a class="link" href="https://developers.circle.com/cctp">https://developers.circle.com/cctp</a></li><li>Across: <a class="link" href="https://across.to/">https://across.to/</a></li><li>deBridge: <a class="link" href="https://debridge.com/">https://debridge.com/</a></li><li>Axelar: <a class="link" href="https://www.axelar.network/">https://www.axelar.network/</a></li><li><a class="link" href="http://Li.Fi">Li.Fi</a>: <a class="link" href="https://li.fi/">https://li.fi/</a></li><li>cBridge</li></ul>Metrics required from your chosen provider:<ul class="list-node tight" data-tight="true"><li>Volume</li><li>Rates (Fees)</li><li>Liquidity Depth</li><li>Available Assets</li></ul><blockquote class="block-node">⚠️ ImportantOne submission = one provider. Do NOT implement multiple providers in the same plugin. We will select and aggregate up to seven independent plugins (one per provider) into our system.You may submit multiple times.</blockquote><hr><h2 class="heading-node">Requirements</h2><ol class="list-node tight" data-tight="true"><li>Implement the contract for your single chosen provider using the provider’s official off-chain APIs or SDKs. Avoid on-chain simulation.</li><li>ENV-based configuration for keys, base URLs, and rate limits.</li><li>Resilience: retries with exponential backoff and per-provider rate limiting. A successful plugin must be reliable.</li><li>Documentation: clear README explaining setup, ENV, how to run locally, and how data is derived.</li><li>Sample tests have already been provided <a class="link" href="https://github.com/NEARBuilders/data-provider-playground/tree/main/packages/_plugin_template/src/__tests__" target="">here</a>. A good plugin will enhance these tests, and all tests should pass.</li></ol><h2 class="heading-node">Contract Specification</h2>Each adapter is its own service implementing the same oRPC contract, this is how these plugins work and are composable. You can find the desired contract specification in the template plugin, here: <a class="link" href="https://github.com/NEARBuilders/data-provider-playground/blob/main/packages/_plugin_template/src/contract.ts">https://github.com/NEARBuilders/data-provider-playground/blob/main/packages/_plugin_template/src/contract.ts</a>Contract rules:<ul class="list-node tight" data-tight="true"><li>One repo = one provider. Do not add additional providers in the same codebase.</li><li>Do not change field names or shapes. If you must change names or introduce new fields, let’s discuss in the Telegram Group and document your reasoning.</li><li>Normalize decimals when computing effectiveRate, but keep raw strings for on-chain smallest units.</li><li>LiquidityDepth must at least include thresholds for ≤0.5% and ≤1.0% slippage.</li></ul><hr><h2 class="heading-node">Template Repository</h2>As mentioned, your plugin should be adapted the template repository found here: <a class="link" href="https://github.com/NEARBuilders/data-provider-playground">https://github.com/NEARBuilders/data-provider-playground</a> The repository features a helpful README to get you started, a starter test suite, and an LLM.txt that will help with best practices when working with every-plugin. <a class="link" href="https://github.com/NEARBuilders/data-provider-playground/blob/main/packages/_plugin_template/LLM.txt">https://github.com/NEARBuilders/data-provider-playground/blob/main/packages/_plugin_template/LLM.txt</a><hr><h3 class="heading-node">Budget &amp; Timeline</h3><ul class="list-node"><li>Budget: 800 NEAR<ul class="list-node"><li>100 NEAR per unique competitor data plugin built.</li></ul></li><li>Timeline: Flexible, but preferred delivery within 1-2 weeks</li><li>Payment: lump sum upon successful delivery</li><li>Winner selection: The 8 best solutions (one per competitors) submitted by the deadline of the bounty will be selected 2 days after the bounty deadline. Tip: Consider running your implementation against the community in chats (see them at the end of the description)</li></ul><h2 class="heading-node">Evaluation</h2><ul class="list-node tight" data-tight="true"><li>Contract compliance and type safety.</li><li>Correctness and repeatability of metrics.</li><li>Robustness under rate limits and transient failures.</li><li>Clarity of tests and documentation.</li></ul><hr><h2 class="heading-node">Submission</h2><ul class="list-node tight" data-tight="true"><li>GitHub repository link, forked from the original template.</li><li>README with provider chosen, endpoints used, and any API access constraints.</li></ul><hr><h2 class="heading-node">Notes</h2><ul class="list-node tight" data-tight="true"><li>This bounty is solely for the single-provider adapter implementation. Frontend and aggregation will be handled separately.</li><li>We will aggregate up to seven independent provider-specific plugins downstream, using this identical contract across all of them.</li><li>On November 10, an additional bounty was added for the cBridge provider.</li><li>On November 11, after winners have been chosen, the prizes were adjusted to accommodate the multi-submission wins. </li></ul>

Build a Data Adapter for an Intent's Competitor API (7 providers)

Build a Data Adapter for an Intent's Competitor API (7 providers)

Status: Paid

800NEAR Total Prizes
500 NEAR 1st 100 NEAR 2nd 100 NEAR 3rd 100 NEAR 4th