LTIPP Application Template

Application Template Background

The Application Template below was created by the LTIPP Council (GFX Labs, 404 DAO, Wintermute, GMX, and Karel Vuong) and the LTIPP Advisors (JoJo, SeedLatam Gov, Castle Capital).

Applicants must use this template to create their applications for LTIPP funding.

For more info on the program and the application/selection process please read the LTIPP FAQ

How to apply

  1. Create a new forum thread in the LTIPP section of the forum
  2. Title thread [Protocol Name] LTIPP Application Draft
  3. Use the Application template to apply
  4. Post application by March 3rd, 2024 at 11:59 PM EST

Eligibility Requirements

The pilot program is for protocols that did not receive ARB during STIP or the Backfund. However, protocols that received grants from the Arbitrum Foundation, Questbook’s grant program, or any other Arbitrum Grants program are eligible to receive Pilot Program funding. Additionally, receiving funding from the Pilot Program does not prohibit protocols from applying for funding from other DAO or foundation programs including the Long Term Incentives Program.

Additional eligibility requirements

  • Grantees must either
    • Be live* on Arbitrum at the time of the application
    • If available on other chains that are not Arbitrum, be live* in Arbitrum by the end of the Feedback Period
    • If live only on Arbitrum testnet, be live* with their product(s)/protocol on Arbitrum mainnet by the end of the Feedback Period
    • Be an Orbit L3 chain that settles on Arbitrum One or Arbitrum Nova
    • Be an Orbit L2 utilizing the Arbitrum tech stack
  • Grantees must refrain from farming their own incentive programs.
  • Grantees must outline a spending plan, provide a pro forma, and state the grant’s objective.
  • Grantees must commit to providing data on distributions, all ARB spending transactions, and key metrics like daily TVL, transactions, volumes, unique addresses, and transaction fees. This data should cover 30 days before, during, and after the Incentivization period, and be presented preferably in a Dune Spell/dashboard.
  • Grantees must agree to share all contract addresses being used to distribute incentive rewards.
  • Grantees must disclose the contracts being incentivized and denote any external contracts being incentivized as part of the program.
  • Grantees can only incentive contracts on the Arbitrum Network.
  • Grants are not to be used in DAO governance.
  • Grantees are expected to not encourage or partake in Sybil attacks against the forum to sway community opinion.
  • Grantees must agree to KYC with the Arbitrum Foundation to receive funds.
  • Grantees must apply using the approved program application template.

* “Live” means that either the protocol, the token, or other products are available on the Arbitrum mainnet in a manner that is usable by users, functioning, and have a non-zero amount of Total Value Locked (TVL) or activities. In general, the protocol must be available on the Arbitrum mainnet in such a way that, even if only a subset of core functionalities are available, it can still fulfill the main value accrual proposition for which it was built. The council retains the right to evaluate and, if necessary, veto protocols that do not meet the above criteria from applying to this program.

Template Rationale

The Application Template was designed to be kept simple and easy to follow for applicants while attempting to encourage high-quality and impactful information.

To achieve this, we have created an accompanying checklist based on the Application Rubric to help ensure applicants are ticking all the boxes when it comes to delivering a great application!

Application tips:

  1. Keep your application clear & concise! You will be judged on the quality of your answers and information, not how many words you have written.
  2. Make sure you demonstrate a clear understanding of why you are applying, the goals of your application, why it’ll benefit the Arbitrum ecosystem, and how you intend to achieve these goals with the grant you receive.
  3. Provide your most applicable supporting data to justify your application where relevant.
  4. Get creative and think about the long-term benefits you can bring to Arbitrum!
  5. Lastly, don’t forget to crosscheck your answers with the Application Rubric and Checklist!

Application Rubric
Application Checklist

Application Template


Provide personal or organizational details, including applicant name, contact information, and any associated organization. This information ensures proper identification and communication throughout the grant process.

Applicant Name: [Enter full name]

Project Name: [Enter Project Name]

Project Description: [Enter Project Description (1-3 sentences)]

Team Members and Roles: [List team members and their roles/responsibilities]

Project Links: [Enter Any Relevant Project Links (website, demo, github, twitter, etc.)]

Contact Information

Point of Contact (note: this should be an individual’s name, not the name of the protocol): [forum handle]

Point of Contact’s TG handle: [Telegram]

Twitter: [Twitter Handle]

Email: [Email Address]

Do you acknowledge that your team will be subject to a KYC requirement?: [Yes/No]

SECTION 2a: Team and Product Information

Provide details on your team’s past and current experience. Any details relating to past projects, recent achievements and any past experience utilizing incentives. Additionally, please provide further details on the state of your product, audience segments, and how you expect incentives to impact the product’s long-term growth and sustainability.

Team experience (Any relevant experience that may be useful in evaluating ability to ship, or execution with grant incentives. Please provide references knowledgeable about past work, where relevant. If you wish to do so privately, indicate that. [Optional, but recommended]):

What novelty or innovation does your product bring to Arbitrum?

Is your project composable with other projects on Arbitrum? If so, please explain:

Do you have any comparable protocols within the Arbitrum ecosystem or other blockchains?

How do you measure and think about retention internally? (metrics, target KPIs)

Relevant usage metrics - Please refer to the OBL relevant metrics chart. For your category (DEX, lending, gaming, etc) please provide a list of all respective metrics as well as all metrics in the general section:

Do you agree to remove team-controlled wallets from all milestone metrics AND exclude team-controlled wallets from any incentives included in your plan: [Yes/No]

Did you utilize a grants consultant or other third party not named as a grantee to draft this proposal? If so, please disclose the details of that arrangement here, including conflicts of interest (Note: this does NOT disqualify an applicant):


Provide details about the Arbitrum protocol requirements relevant to the grant. This information ensures that the applicant is aligned with the technical specifications and commitments of the grant.

Is the protocol native to Arbitrum?: [Yes/No, and provide explanation]

On what other networks is the protocol deployed?: [Yes/No, and provide chains]

What date did you deploy on Arbitrum mainnet?: [Date + transaction ID. If not yet live on mainnet, explain why.]

Do you have a native token?: [Yes/No/Planned, link tokenomics docs]

Past Incentivization: What liquidity mining/incentive programs, if any, have you previously run? Please share results and dashboards, as applicable?

Current Incentivization: How are you currently incentivizing your protocol?

Have you received a grant from the DAO, Foundation, or any Arbitrum ecosystem related program? [yes/no, please provide any details around how the funds were allocated and any relevant results/learnings(Note: this does NOT disqualify an applicant)]

Protocol Performance: [Detail the past performance of the protocol and relevance, including any key metrics or achievements, dashboards, etc.]

Protocol Roadmap: [Describe relevant roadmap details for your protocol or relevant products to your grant application. Include tangible milestones over the next 12 months.]

Audit History & Security Vendors: [Provide historic audits and audit results. Do you have a bug bounty program? Please provide details around your security implementation including any advisors and vendors.]

Security Incidents: [Has your protocol ever been exploited? If so, please describe what, when and how for ALL incidents as well as the remedies to solve and mitigate for future incidents]


Detail the requested grant size, provide an overview of the budget breakdown, specify the funding and contract addresses, and describe any matching funds if relevant.

Requested Grant Size: [Enter Amount of ARB Requested]

Justification for the size of the grant: [Enter explanation. More details are better, including how you arrived at the required funding for individual categories of expenses covered by your grant plan]

Grant Matching: [Enter Amount of Matching Funds Provided - If Relevant]

Grant Breakdown: [Please provide a high-level overview of the budget breakdown and planned use of funds]

Funding Address: [Enter the specific address where funds will be sent for grant recipients]

Funding Address Characteristics: [Enter details on the status of the address; the eligible address must be a 2/3, 3/5 or similar setup multisig with unique signers and private keys securely stored (or an equivalent custody setup that is clearly stated). The multisig must be able to accept and interact with ERC-721s in order to accept the funding stream.

Treasury Address: [Please list out ALL DAO wallets that hold ANY DAO funds]

Contract Address: [Enter any specific address that will be used to disburse funds for grant recipients]


Clearly outline the primary objectives of the program and the Key Performance Indicators (KPIs), execution strategy, and milestones used to measure success. This helps reviewers understand what the program aims to achieve and how progress will be assessed.

Objectives: [Clearly state the primary objectives of the grant and what you intend to achieve]

Execution Strategy: [Describe the plan for executing including token distribution method (e.g. farming, staking, bonds, referral program, etc), what you are incentivizing, resources, products, use of funds, and risk management. This includes allocations for specific pools, eligible assets, products, etc.]

What mechanisms within the incentive design will you implement to incentivize “stickiness” whether it be users, liquidity or some other targeted metric? [Provide relevant design and implementation details]

Specify the KPIs that will be used to measure success in achieving the grant objectives and designate a source of truth for governance to use to verify accuracy. [Please also justify why these specific KPIs will indicate that the grant has met its objective. Distribution of the grant itself should not be one of the KPIs.]

Grant Timeline and Milestones: [Describe the timeline for the grant, including ideal milestones with respective KPIs. Include at least one milestone that shows progress en route to a final outcome. Please justify the feasibility of these milestones.]

How will receiving a grant enable you to foster growth or innovation within the Arbitrum ecosystem? [Clearly explain how the inputs of your program justify the expected benefits to the DAO. Be very clear and tangible, and you must back up your claims with data]

Do you accept the funding of your grant streamed linearly for the duration of your grant proposal, and that the multisig holds the power to halt your stream? [Yes/No]

SECTION 5: Data and Reporting

OpenBlock Labs has developed a comprehensive data and reporting checklist for tracking essential metrics across participating protocols. Teams must adhere to the specifications outlined in the provided link here: Onboarding Checklist from OBL. Along with this list, please answer the following:

Is your team prepared to comply with OBL’s data requirements for the entire life of the program and three months following and then handoff to the Arbitrum DAO? Are there any special requests/considerations that should be considered?

Does your team agree to provide bi-weekly program updates on the Arbitrum Forum thread that reference your OBL dashboard? [Please describe your strategy and capabilities for data/reporting]

First Offense: *In the event that a project does not provide a bi-weekly update, they will be reminded by an involved party (council, advisor, or program manager). Upon this reminder, the project is given 72 hours to complete the requirement or their funding will be halted.

Second Offense: Discussion with an involved party (advisor, pm, council member) that will lead to understanding if funds should keep flowing or not.

Third Offense: Funding is halted permanently

Does your team agree to provide a final closeout report not later than two weeks from the ending date of your program? This report should include summaries of work completed, final cost structure, whether any funds were returned, and any lessons the grantee feels came out of this grant. Where applicable, be sure to include final estimates of acquisition costs of any users, developers, or assets onboarded to Arbitrum chains. (NOTE: No future grants from this program can be given until a closeout report is provided.)

Does your team acknowledge that failure to comply with any of the above requests can result in the halting of the program’s funding stream?: [Y/N]