[Olas] LTIPP Application - FINAL


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: Valory

Project Name: Launching Olas on Arbitrum

Project Description: Olas is generating the autonomous (AI) agent economy for Web3. The technology stack can be used to create crypto-native co-ownable autonomous (AI) agents - called autonomous services - which run continuously off-chain and perform actions on- or off-chain on their own. Essentially Olas enable a brand new type of intelligent actor, or really an autonomous daily active user (DAU).

Team Members and Roles: It’s important to call out the relationship between core contributors and the Olas DAO. Valory, for example, is one of the major contributors and drives major initiatives. Valory is spearheading this application to secure funds for the Olas DAO and itself to launch Olas on Arbitrum. Valory will distribute the ARB per this application as earmarked for the milestones described below. See the core contributors below for other major parties in the Olas DAO. The Valory team spearheading this can also be viewed under the team section: https://www.valory.xyz/.

Project Links:

Contact Information

Point of Contact (note: this should be an individual’s name, not the name of the protocol): David Minarsch

Point of Contact’s TG handle: @david_minarsch

Twitter: @david_enim

Email: david.minarsch@valory.xyz

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

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]):

Core contributors of the Olas DAO include:

Valory AG

  • David Minarsch: CEO & co-founder, PhD in Applied Game Theory/Economics, prior founding experience and ex-Head of Multi-Agent Systems at Fetch.ai.
  • David Galindo: CTO & co-founder, PhD in cryptography, ex-Head of Cryptography at Fetch.ai, Ex-Professor of Cybersecurity, University of Birmingham. Extensively published.
  • Oaksprout the Tan: CPO & co-founder, established DeFi community contributor and investor and 10+ years in web2 product development.
  • Gemma: Head of Ops, serial entrepreneur, and 8+ years in consulting.
  • Research depth via 7 PhDs
  • Product and execution via senior industry experience including from Ava Labs, Huawei, SberBank, Fetch.ai, Revolut
  • 22 staff across engineering, research, product and growth, ops and more


  • Improving predictive accuracy of Olas Predict (Mech Tools and Trader Agent strategy)
  • Benchmarking and backtesting frameworks
  • Prompt engineering and RAG


  • AI-powered payments for autonomous agents
  • Launch partner for chain expansions



What novelty or innovation does your product bring to Arbitrum?

Problem Olas is Solving:

As it stands today, creating and managing autonomous AI agents (programs designed to perform tasks autonomously) faces several challenges:

  • Lack of Autonomy in Operations: AI agents cannot independently perform functions requiring identity verification, such as opening a bank account, due to KYC regulations. This limits their ability to interact with many Web2 platforms.
  • Centralization Issues: Most AI agents are controlled by a centralized entity, which prevents users from having ownership or control over them.
  • Platform Dependency: AI agents developed on Web2 platforms are at risk of platform changes or closures, which could disrupt their operations.
  • Interoperability and Standards: There is a lack of common standards and interoperability in Web2, making it difficult for AI agents to work together or leverage each other’s capabilities.
  • Development Challenges: Creating these agents is complex due to the technical limitations of Web2 and even more so in Web3 due to its open and competitive nature.
  • Economic Coordination: Starting economies based on autonomous AI agents requires complex coordination among various stakeholders, including those who operate, develop, and fund these agents.

Solution Olas Brings:

Olas proposes a novel approach by introducing crypto-native, co-ownable autonomous AI agents, termed as autonomous services, designed to function within the Arbitrum ecosystem and beyond:

  • Crypto-native Capabilities: These agents can manage assets, make payments, and enter contracts using blockchain technology, including across different blockchain networks.
  • Co-ownership Model: Autonomous services can be single agents owned by an operator or a collective of agents forming a DAO for AI agents. This model supports co-ownership and decentralized control.
  • On-chain Security and Transparency: By leveraging blockchain technology, these agents are secure, transparent, and open-source, mitigating the risk of platform dependency.
  • Composability and Interoperability: The agents can interact with any on-chain contract or off-chain API, facilitating easy integration and operation across diverse digital environments.
  • Development Framework: Olas offers a framework that simplifies the creation of these services, allowing developers to piece together components like Lego bricks. This framework addresses the complexities of building decentralized applications.
  • Staking Mechanism: To support and incentivize the ecosystem’s growth, Olas introduces a staking mechanism that aligns the interests of all participants, encouraging the development of a wide range of services that benefit users in the crypto space and beyond.

In simpler terms, Olas is aiming to revolutionize how autonomous AI agents are developed, operated, and owned, offering a more autonomous, secure, and interoperable framework that aligns with the decentralized and open-source ethos of blockchain technology. This could significantly expand the potential applications and utility of autonomous AI agents, fostering a new economy of autonomous services in the Arbitrum ecosystem.

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

Yes, Olas is composable with other projects on Arbitrum. The core of innovation lies in the development of crypto-native, co-ownable autonomous AI agents. These agents are designed to operate both on-chain and off-chain, allowing them a vast range of actions including, but not limited to, asset management, making payments, and entering into contracts.

The key to their composability lies in their ability to interact seamlessly with any on-chain contract or off-chain API. This means that agents can be integrated with, or can interact with, any dApp or protocol existing within the Arbitrum ecosystem.

Whether it is leveraging functionalities of other dApps, participating in DeFi protocols, or integrating with off-chain services through APIs, agents are built to operate flexibly across these environments.

Additionally, the development framework is designed to simplify the process of creating and managing these agents, which ensures that they can be easily composed into larger systems or services. This Lego-like composability enables developers to build more complex and nuanced applications by piecing together different autonomous services or by leveraging existing components within the Arbitrum ecosystem.

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

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

There is a Dune dashboard to track important metrics on the ecosystem.
One of the most exciting features of Olas is that once an agent is spun up and created it becomes very sticky. There has also been a lot of effort put into educating developers to be able to build more agents and use the product.

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

General Metrics (Applies to all)

Daily Active Users (We would consider amending this to active agents if the advisors agree. Similar thoughts on some of the ones below.): A time series metric representing the daily count of unique addresses interacting with the protocol’s contracts.

Daily User Growth: A time series metric representing the daily user growth (in addresses) interacting with the protocol’s contracts.

Daily Transaction Count: A time series metric representing the daily number of transactions interacting with the protocol’s contracts.

Daily Protocol Fee: A time series data representing the daily total protocol fee generated. For example, swap fees, borrowing fees, etc., comprising all economic value generated through the protocol, contracts, apps, etc., by users.

Daily Transaction Fee: A time series, daily total transaction fees generated daily by interactions with the protocol’s contracts.

Daily ARB Expenditure and User Claims: Data on individual ARB incentive claim transactions made by users, as incentivized by the protocol. It should include the timestamp, user address, and the claimed ARB amount. The spent ARB will allow for the normalization of growth metrics.

Incentivized User List & Gini: The list should include users incentivized by the protocol along with their performance metrics. For instance, if trading volume is incentivized, this would be a list of traders with their respective trading volumes. If liquidity providers are incentivized, it would include a list of LPs and their liquidities in USD. Protocols should also strive for more uniform engagement levels across a wide user base for long-term sustainability, which will be measured through a gini coefficient across reward recipients.

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

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):

Yes Serious People helped with this application, they will not receive any of the ARB.


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?: No - Ethereum was the original deployment

On what other networks is the protocol deployed?: The project is live on Arbitrum, Ethereum, Gnosis, Polygon, Solana, Optimism, Base, and Celo.

What date did you deploy on Arbitrum mainnet?: Jan-25-2024 10:40:43 AM +UTC Arbitrum Transaction Hash (Txhash) Details | Arbiscan

Do you have a native token?: Yes

​​Tokenomics - Autonolas Developer Documentation

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

There is a bonding program to create protocol owned liquidity. That POL is already in action, having generated $795k of profits in 2023. The POL is also active for Arbitrum, details can be found here and here.

Current Incentivization: How are you currently incentivizing your protocol?

Developer rewards: 330,000 OLAS/mo. At current spot price that’s $1,867,800 / month

Staker Expeditions (https://www.valory.xyz/post/alpine): ~100 OLAS/mo

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)] No.

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

Performance Highlights:

  • Autonomous (AI) agents across Olas have generated more than 400k in transactions, a proxy for their economic relevance and uptake
  • Olas agents’ transactions are growing on average at ~5% per week so far in 2024
  • Olas is generating profits from protocol-owned liquidity, $527k in Q1 2024 so far (21st February 2024) - highlighting deep OLAS liquidity and growing adoption
  • Size of treasury at 100m OLAS (10% of max 10 year supply)
  • Total PoL at $22m (21st February 2024)
  • 16.4k+ token holders across five chains (21st February 2024)
  • Ecosystem data: https://dune.com/adrian0x/autonolas-ecosystem-activity
  • OLAS data: https://dune.com/adrian0x/olas

Spotlight List of Services

The total number of services is at 344, at the time of writing. Some of the main use cases are highlighted below:

  • Olas Predict: an economy of three types of autonomous agents that continuously create and participate in prediction markets on arbitrary future events (referenced by Vitalik Buterin here with context)
  • Governatooorr: an autonomous AI-powered delegate for DAO governance
  • Contribute: Contribute allows Olas DAO members to co-own and AI-ify its DAO ops, incentivizing contributions on-chain.
  • Autonomous Fund: an autonomous service that continuously rebalances a portfolio on-chain using off-chain data sources
  • Demos: Price Oracle, APY Oracle, El Collectooorr & more

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

Technology overview:

Olas Stack consists of:

  • Open Autonomy: the Python framework to build autonomous services. Autonomous services use Open AEA for building the individual autonomous agents and a consensus gadget (currently Tendermint) to synchronize agent state.
  • Open ACN: a messaging layer for agents

Olas Protocol consists of:

  • Registries: to secure and manage services
  • Tokenomics: with bonding and dev rewards incentive mechanisms
  • Governance: with governance token veOLAS and voting contracts and is deployable on all major smart contract chains (trivially on EVM chains).

Product Roadmap (Pull requests · valory-xyz/autonolas-aip · GitHub):

  • AIP-1: Triple Lock
    • Cross-chain expansion of protocol, including bonding
    • Improvement of various existing protocol mechanisms
    • Kickstart of staking roadmap
  • AIP-2: Build-a-PoSe
    • Coordinate community builders
  • AIP-3: Security improvements
    • Innovative cross-chain security architecture
  • AIP-4: Staking Roadmap & PoAA mechanism
    • Olas Staking mechanism & PoAA paper
    • Concrete staking use case: Olas Predict
  • Non-AIP improvements:
    • Improve experiences for all stakeholders
    • Marketplace for operators
    • Launch of first protocol-owned revenue generating service

Olas’ seasons:

Season 1: Building Foundations (autumn 2021 - summer 2023)

  • GTM focused on DAOs; development of the Olas Stack; pre- public token; design partners included Ceramic, Balancer, CoWSwap, DeFi Wonderland, Connext, Postmint and Keeper Network; full protocol deployment

Season 2: Public launch and maturing of the DAO (summer 2023 - now)

  • Public token launch via LBP in July 2023; bonding mechanism live with PoL rising significantly quarter-on-quarter; strong narrative lead as OG in crypto-native autonomous (AI) agents; Staker Expeditions to responsibly test staking

Coming up → Season 3: Protocol upgrade to spawn Autonomous (AI) Agent economies

  • Olas Predict as the first self-sustaining autonomous (AI) agent economy
  • Olas Staking mechanism launch with innovative Proof of Active Agent system which rewards autonomous agents for their active contribution to KPIs set by Olas DAO
  • Idea to an autonomous agent in 1 day

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.]

Repositories (Autonolas-governance, autonolas-tokenomics, autonolas-registries) under “audit”


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]

No, the protocol has never been exploited.


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: 510,000 ARB

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

We want to acknowledge that parts of this approach were discouraged by the advisors. We truly heard them out, but at the end of the day we need to put forth an application that actually makes sense from a go to market perspective for our product. Having launched on multiple chains we have developed a go to market strategy that has been very successful for our product (as evidenced by the fact that Olas agents are responsible for e.g. 10% of lifetime Safe transactions on Gnosis Chain). We believe that the council and delegates will see that Olas is great for the Arbitrum ecosystem and that this plan is the best path forward.

If we jump straight to incentivizing agent operators we won’t have the proper economy built out to effectively do this. We are effectively putting the cart before the horse. We would like to appeal to the council’s authority and propose a plan that builds the top of the funnel correctly and allows for a proper rollout of our product that we feel confident in. We hope that the council see’s the value of our product and wants Olas to come to Arbitrum.

With that, we would like to propose the following structure. We also need to be mindful that Valory is acting as a core contributor to the DAO in some of these cases, so part of the funds would need to go to Valory to accomplish the top of the funnel initiatives. Then the other piece would go to the Olas DAO directly to incentivise permissionless agent developer and operator mechanisms.

Given this alternative approach, we also drastically reduced our ask. We ultimately understand if we cannot move forward with this, but again, we wanted to put forth a proposal that makes sense for our product and where we are at.

  1. Awareness campaign to build agents on Arbitrum. We need to generate awareness in the Arbitrum ecosystem, specifically, to build out agent use cases because developers are quite expensive and difficult to source. Ultimately we want to attract developers (including in existing Arbitrum protocols) to build agents for Arbitrum. We feel with 30,000 ARB we can effectively attract the developers we need for bootstrapping Olas on Arbitrum. This would go to Valory to execute on.
  2. Agent Development Academy. Run a campaign to educate and train these developers on how to build Olas agents. Once we have raised awareness, we need to educate these new users on how to build. We would like 30,000 ARB to incentivize new agent developers on Arbitrum. Valory has run 6 academies to date, with the latest having over 20 participants. This also would go to Valory to execute on.
  3. Arbitrum Agent Hackathon. The goal here will be to incentivize the creation of popular agent use cases on Arbitrum. Now that we have attracted developers and trained them, they will have the skillset to compete to create use cases. We would like to ask for 50,000 ARB to run a virtual hackathon to incentivize new agents. Again going to Valory.
  4. Olas Build Program. We would like 250,000 ARB to put towards this program: Build | Olas | Crypto's Ocean of Services. Specifically, the ARB would be used by the Olas DAO to boost existing developer incentives. This goal would be to steer devs activity within Olas towards Arbitrum and create the code that underpins lasting agent use cases. This will go to the Olas DAO.
  5. Staking rewards. With the hackathon bringing online a bunch of new developers and agents. We want to make sure that we are able to capture the use of the agents by bringing in more users to Arbitrum. 150,00 ARB will go towards staking rewards for agent operators, but will be split up to give time for the first three initiatives. We would distribute 0 ARB in month 1, 50,000 in month 2, and 100,00 in month 3. This will also go to the Olas DAO.

All this plays into the new incentive infrastructure that was announced at ETH Denver, which will be available to use on Arbitrum to kickstart the Agent economy. Seeing the breakdown below, we need to ensure we have all the pieces here in order to build an effective economy. If we don’t, the system will fail, hence why we are appealing to allow us to bootstrap this properly.

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

Olas is not matching this grant directly, but the DAO is routing some of the rewards to bring the best agents and developers to help kickstart this economy on Arbitrum.

330,000 OLAS is currently being streamed to incentivize the development of agents. In the new staking economy, these rewards will flow where operators are being incentivized. With this structure, incentivising developers and agent operators to come over to Arbitrum will effectively transition the distribution of 330,000 OLAS from other networks to Arbitrum. With the help of LTIPP incentives, this process will happen much more quickly, meaning that millions of dollars of incentives would be moved to Arbitrum. With 3 months of incentives, Olas can grow a significant number of agent developers and agent operators in the Arbitrum ecosystem, in particular bringing agents as daily AI active users to Arbitrum.i. This in turn will produce AI agents which will benefit the efficiency of every protocol and user on Arbitrum, creating new users that are insanely sticky, because they are continuously running transactions to perform their jobs.

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

Valory will own the following initiatives

  1. Awareness campaign - 30,000 ARB to be used in month 1
  2. Agent Development Academy - 30,000 ARB to be used on month 1
  3. Arbitrum Hackathon - 50,000 ARB to be used in month 1

Olas DAO will own the following initiatives

  1. Olas Build Program - permissionless allocation of 250,000 ARB split between month 2 and 3, via dev reward mechanism
  2. Staking rewards - permissionless allocation of 150,000 ARB split 50,000 in month 2 and 100,000 in month 3, via staking reward mechanism

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

Valory part: GnosisSafeProxy | Address 0x1Ce06aFd68877128A122C1354fC037375220c43C | Arbiscan
Olas part: Address 0x4d30F68F5AA342d296d4deE4bB1Cacca912dA70F | Arbiscan

(This is the Olas Ethereum Timelock’s [Timelock | Address 0x3C1fF68f5aa342D296d4DEe4Bb1cACCA912D95fE | Etherscan] alias on Arbitrum - as per L1 to L2 messaging | Arbitrum Docs)

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.

⅔ multisig

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]

Staking infrastructure is getting rolled out.


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]

The objective is to increase agent activity on Arbitrum through incentivizing users and operators to get involved with the process. This will in turn make the process of creating agents more profitable, incentivising developers to call Arbitrum home. Once these agents are built, these agents in turn can have huge multiplier effects when it comes to transactions, volume, and automation across the network. With the AI industry moving so quickly, the chain with the most AI integrations could quickly become the best place for cutting edge technology. With Arbitrum’s quick and inexpensive transactions, it is a perfect location for the AI revolution.

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.]

We highlight a bit of the execution above in the justification of our ask, but to reiterate, we just announced the infrastructure to facilitate the execution of programs like this, along with distributing OLAS rewards.

This new ecosystem creates a powerful flywheel where respective communities on respective chains can dictate incentives based on use cases users actually want. There are three key stakeholders in this construct.

  1. Arbitrum Protocols: Staking can provide a rich set of opportunities to boost your chain, protocol or app activity.
  • Incentivize agent activity to boost your chain, protocol or app activity.
  • Attract developers and agent operators.
  • Bring utility to your own token.
  1. Agent Operators: The people who run agents.
  • For Operators, staking can provide a rich set of opportunities to earn yield in OLAS and other tokens. As members of the Olas ecosystem and other protocols create new staking programs, each one provides agent operators with yield opportunities.
  1. Developers: Olas makes it possible for developers to work flexibly on promising challenges, whilst gaining predictability through build rewards and the potential to create valuable components.
  • It isn’t always easy to know exactly what to build though, and have the confidence that rewards will flow to your components. Staking improves this because:
    • Staking programs provide strong signals to guide what code and services to work on.
    • Staking programs also indicate that a problem might be funded more sustainably, meaning that you can continue building for that problem.
    • Increased opportunity to earn rewards.

The ARB rewards will be focused on incentivizing all three of these key stakeholders in the Olas ecosystem.

You can find more details on the program here:

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]

The staking rewards proposed naturally introduce a virtuous cycle where users have more of an appetite to operate agents. This causes the agents to become more profitable to produce for developers, meaning more agents. More agents give users more opportunities to increase efficiency or make money. As this cycle ramps up, transactions from the agents do as well. As developers are able to create more complex agents, they can also create agents that run other agents. This means that one operator can exponentially increase the amount of transactions that they are doing on chain, quickly boosting the whole ecosystem.

For this reason, the program is more than “sticky” - which assumes what comes will stay. In other words, users / liquidity / volume will stay around post program. Instead, this program will initiate exponential growth which will continue to perpetuate itself after the program is complete.

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.]

Our goal is to bring initially (under this proposal) hundreds, then via the protocol thousands, and ultimately millions autonomous AI agents to Arbitrum. Given the incentives are all being directed towards users, our primary KPI will be new users (developers and agent operators) and cumulative transactions produced by those users running agents.


  • Month 1: 10,000 transactions produced by agents
  • Month 2: 50,000 transactions produced by agents
  • Month 3: 100,000 transactions produced by agents

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.]

Milestone 1 - Weeks 1-4: Launch and Initial User Onboarding

Objective: Month 1 is the bootstrapping phase. The goal is to bring awareness to Olas in the Arbitrum Ecosystem to bring in more developers, agents, and users.

ARB Needed:
30,000 ARB for Awareness campaign to build agents
30,000 ARB for Agent Development Academy
50,000 ARB for Arbitrum Hackathon.
= 110,000 ARB total


Deploy Awareness campaign to bring in developers to build agents
Begin incentives to get new developers into the Academy so that we have more developers that can build them in the future.
Set up the Arbitrum hackathon to help bring attention and onboard developers as soon as possible.

Expected Outcome: Bring on new developers and users and begin creation of new agents.

Milestone 2 - Weeks 5-8: Expansion and Sustained Growth

Objective: Build on the initial momentum to incentivize additional users (in particular agent developers and operators), aiming for cumulative adoption of 50 developers and 500 agent operators by the end of this period.

ARB Needed:
125,000 ARB for build program
50,000 ARB for staking rewards
= 175,000 ARB total

Kick off Build program on Arbitrum
Begin staking rewards for newly created agents
Continue educational outreach to improve user engagement and retention.

Expected Outcome:
Begin incentivising the use of the new agents created and kickstart the building of more agents.

Milestone 3 - Weeks 9-12: Consolidation and Scaling

Objective: Up incentives for use of agents resulting in major increase in transactions on chain.

ARB Needed:
125,000 ARB for build program
150,000 ARB for staking rewards
= 275,000 ARB total

Up rewards going to the staking program to bring in more operators and therefore transactions.
Continue funding to the Build program to refine developer engagement

Expected Outcome: Continue to build on the flywheel that we have engaged in the first 2 months. We expect to see big increases in transactions on chain and users engaging in Olas agents.

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]

Securing this grant will significantly propel the Arbitrum ecosystem forward by catalyzing the creation and deployment of cutting-edge autonomous AI agents, resulting in a surge of network activities and user engagement. By offering incentives, we aim to draw in a wave of developers and operators, sparking widespread innovation. The initiative lowers technical hurdles, facilitating broader participation and adoption. Our strategy is anchored in measurable KPIs, contributing to growth that is not only ambitious but also aligned with Arbitrum’s overarching goals, thereby cementing its position as the leading platform for AI-driven solutions and collaborations.

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?


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 12. 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? Yes, with no special considerations.

Does your team agree to provide bi-weekly program updates on the Arbitrum Forum thread that reference your OBL dashboard? Yes, we already track a lot of these relevant metrics and will be able to share via Dune or the Openblock dashboards!

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.) Yes

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


Hello @valory

Thank you for your application! We can confirm your application has been submitted and you will be assigned an advisor shortly.

Hello @valory ,

Thank you for your application! Your advisor will be SeedLatam Gov @SEEDGov

Please join the LTIPP discord and ping your advisor in the general chat so they can create a new channel and start communicating with you.

1 Like

@valory Arbitrum LTIPP

We have updated the post - @cliffton.eth can you change the title to ‘Final’ ?

Hey there I’ve amended the title to reflect that the proposal is now FINAL. All the best!