<p class="text-node"><strong>📦 Deliverables: High-load API server for FT transfers, benchmark code &amp; results, usage documentation.</strong></p><hr><h3 class="heading-node">📘 Background</h3><p class="text-node">There are a number of teams launching their tokens on NEAR, and they often want to implement a service that will be distributing their tokens to the users. The launch is usually a time-constraint event, so naturally there is a high demand in a short period of time.</p><p class="text-node">As part of this bounty, we’d like to get a reference implementation for an efficient REST/RPC API service that will be able to handle 100s requests per second to transfer FT from the owner account to the recipient account (create + sign + send the <code class="inline" spellcheck="false">ft_transfer</code> function call transactions).</p><p class="text-node">It is designed to be a component for a centralized “linkdrop” solution that can be adopted and deployed by the engineering teams as-is as an internal service.</p><h3 class="heading-node">🧩 Scope of Work</h3><h4 class="heading-node">1. <strong>Implement an API service in Rust or TypeScript</strong></h4><p class="text-node">The API service only needs a single endpoint - send FT tokens, and it needs the receiver account id, the amount, and optional memo.</p><p class="text-node">The method must efficiently schedule the FT transfer calls - potentially batch multiple <code class="inline" spellcheck="false">ft_transfer</code> calls into a single transaction, cache the access key nonce in memory, and use multiple access keys to reduce the nonce issues.</p><p class="text-node">Note: There are nice packages that can already handle access key nonces for concurrent transactions efficiently:</p><ul class="list-node tight" data-tight="true"><li><p class="text-node">Rust: <a class="link" href="https://github.com/near/near-api-rs">https://github.com/near/near-api-rs</a></p></li><li><p class="text-node">TypeScript: <a class="link" href="https://github.com/eclipseeer/near-api-ts">https://github.com/eclipseeer/near-api-ts</a></p></li></ul><h3 class="heading-node">2. Benchmark the API service</h3><p class="text-node">We need to achieve at least 100 transfers per second and gracefully handle the load for 10 minutes (100 × 60 × 10 = 60000 transfers in 10 minutes).</p><p class="text-node">Implement the benchmark using near-sandbox and once the performance is confirmed, run one round of the load testing on testnet as well.</p><h3 class="heading-node">3. Document how to deploy the service</h3><p class="text-node">There is no need for authentication or authorization, assume that the service will be running internally and another backend will be in front of it making the decision if the transfer should be made and only trigger your service when needed.</p><hr><h3 class="heading-node">✅ Deliverables</h3><ul class="list-node"><li><p class="text-node">✅ Full codebase in a new public GitHub repository (MIT or Apache-2.0 licensed)</p></li><li><p class="text-node">✅ API service implementation in Rust or TypeScript</p></li><li><p class="text-node">✅ Developer-focused documentation how to build and deploy the API service</p></li><li><p class="text-node">✅ Benchmark code and results on localnet and testnet</p></li></ul><hr><h3 class="heading-node">💰 Budget &amp; Timeline</h3><ul class="list-node"><li><p class="text-node"><strong>Budget</strong>: 1,000 NEAR</p></li><li><p class="text-node"><strong>Timeline</strong>: Flexible, but preferred delivery within <strong>3-4 weeks</strong></p></li><li><p class="text-node"><strong>Payment</strong>: lump sum upon successful delivery</p></li><li><p class="text-node"><strong>Winner selection</strong>: The best complete solution submitted by the deadline of the bounty will be selected 2 days after the bounty deadline.</p></li></ul><hr><h3 class="heading-node">🌱 Why This Matters</h3><p class="text-node">This project will fill a critical gap in the NEAR token launches experience both for dApp developers and the users claiming the tokens.</p><p class="text-node">It will be open-source and publicly maintained for the benefit of the NEAR community.</p><hr><h3 class="heading-node">🚀 Ready to Apply?</h3><p class="text-node">Submit a comment with:</p><ul class="list-node"><li><p class="text-node">A short description of your relevant experience</p></li><li><p class="text-node">Estimated timeline (if different)</p></li><li><p class="text-node">Any clarifying questions</p></li><li><p class="text-node">To avoid spending your time and risking for getting no reward, please, regularly check the Tools Community chat to see if someone already works on it - make your own judgement if you can do better than the existing submissions and go for it!</p></li></ul><hr><p class="text-node">Join community chats to ask for feedback and discuss technical questions:</p><ul class="list-node tight" data-tight="true"><li><p class="text-node">Telegram: <a class="link" href="https://t.me/NEAR_Tools_Community_Group" target="_blank">@NEAR_Tools_Community_Group,</a> <a class="link" href="https://t.me/neardev" target="_blank">@NEARDev</a></p></li></ul><hr><h3 class="heading-node">🔒 Internal Info (for tracking only)</h3><ul class="list-node"><li><p class="text-node"><strong>DevHub Area: </strong>DevTools</p></li><li><p class="text-node"><strong>DevHub Moderator: </strong>Vlad Frolov</p></li></ul>

Vlad Frolov

NEAR DevHub

Fungible Tokens Claiming Service

Full Payment

Sonce

Sarin

Himanshu Ranjan

Peni Vera

0xjesus

Tomáš Blažek

Ahnaf

r-near

Posma JS

1,000NEAR Total Prizes
1,000 NEAR 1st