SECTION 1: APPLICANT INFORMATION
Applicant Name:
Joshua Baker
Project Name:
Aori
Project Description:
N/A
Team Members and Roles:
Joshua Baker, CEO
Hilliam Tung, CTO
Project Links:
Website: aori.io
Github: aori · GitHub
Twitter: https://twitter.com/aori_io
Discord: aori
Do you acknowledge that your team will be subject to a KYC requirement?: [Yes/No]
Contact Information
Point of Contact (note: this should be an individual’s name, not the name of the protocol): [@Damian]
Damian Alvarez
Point of Contact’s TG handle: [Damian0x]
Twitter: [0xDamian0x]
Email: [damian@aori.io]
Do you acknowledge that your team will be subject to a KYC requirement?: [Yes/No]
N/A
SECTION 2a: TEAM AND PRODUCT INFORMATION
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]):
N/A
What novelty or innovation does your product bring to Arbitrum?
N/A
Is your project composable with other projects on Arbitrum? If so, please explain:
N/A
Do you have any comparable protocols within the Arbitrum ecosystem or other blockchains?
N/A
How do you measure and think about retention internally? (metrics, target KPIs)
N/A
Relevant usage metrics - Please refer to the OBL relevant metrics chart 23. For your category (DEX, lending, gaming, etc) please provide a list of all respective metrics as well as all metrics in the general section:
N/A
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]
N/A
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):
N/A
SECTION 2b: PROTOCOL DETAILS
Is the protocol native to Arbitrum?: [Yes/No, and provide explanation]:
N/A
On what other networks is the protocol deployed?: [Yes/No, and provide chains]
N/A
What date did you deploy on Arbitrum mainnet?:
N/A
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?
N/A
Current Incentivization: How are you currently incentivizing your protocol?
N/A
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.]
N/A
Protocol Roadmap: [Describe relevant roadmap details for your protocol or relevant products to your grant application. Include tangible milestones over the next 12 months.]
N/A
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.]
N/A
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]
N/A
SECTION 3: GRANT INFORMATION
Requested Grant Size: [Enter Amount of ARB Requested]
N/A
Justification for the size of the grant 25: [Enter explanation. More details are better, including how you arrived at the required funding for individual categories of expenses covered by your grant plan] Can explain once we have the amount.
N/A
Grant Matching: [Enter Amount of Matching Funds Provided - If Relevant]
N/A
Grant Breakdown: [Please provide a high-level overview of the budget breakdown and planned use of funds]
N/A
Funding Address: [Enter the specific address where funds will be sent for grant recipients]
N/A
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.
N/A
Treasury Address: [Please list out ALL DAO wallets that hold ANY DAO funds]
N/A
Contract Address: [Enter any specific address that will be used to disburse funds for grant recipients]
N/A
SECTION 4: GRANT OBJECTIVES, EXECUTION AND MILESTONES
Objectives: [Clearly state the primary objectives of the grant and what you intend to achieve]
N/A
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.]
N/A
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]
N/A
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.]
N/A
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.]
N/A
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]
N/A
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]
N/A
SECTION 5: Data and Reporting
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?
N/A
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]
N/A
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.)
N/A
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?: [Yes/No]
N/A