SOS - Notice Period: One-Off Objectives Submissions Feb '25

This is the forum thread for contributors to submit one-off objectives and related key results for consideration by those looking to develop a full-fledged objectives matrix submission.

The thread will be open for submissions during the Notice Period (Monday, February 10 to Monday, February 24, 2025) such that those looking to propose a full-fledged objectives matrix during the Submission Period will have access to the same information no matter at which point they submit their matrix.

A one-off objective and related key results submission should be commented under this forum post and formatted as follows:

  • 1-/2-Year Strategic Objective (specify which one in the header)
    • A clear and specific statement of the objective and the main focus area it targets.
    • Explanation of how the objective is aligned with Arbitrum’s MVP, why it was chosen given Arbitrum’s current state, and what risks, required non-capital resources, and expected wider-reaching outcomes are related to the objective.
    • Key assumptions and strategic reasoning behind the objective.
    • ~2-5 measurable key results/success metrics for the objective. These should be as tangible as possible.
  • If relevant, additional 1-/2-Year Strategic Objective(s) (specify which one in the header)
    • Same format as described above.
  • Further Details
    • Anything else the author feels is relevant to include in their submission.

Please refer to the SOS - FAQ & Relevant Links post for more information on the Strategic Objective Setting process.

3 Likes

1-Year Strategic Objective: Expanding Arbitrum via Institutional Orbit Chains

Statement

Onboard at least three institutional partners to launch an L2 or L3 chain using the Arbitrum Orbit stack. The main focus is expanding Arbitrum’s ecosystem through institutional adoption.

Explanation

This objective aligns with Arbitrum’s mission, vision, and purpose (MVP) by driving the “universal shift onchain”. Arbitrum’s current state is that it has strong technical foundation and good TVL, but it should not rest on the laurels. Attracting institutional partners can significantly increase network usage and demonstrate the viability of Orbit chains for enterprise solutions.

Risks include the complexity of enterprise sales cycles, and the need for tailored support. Non-capital resources required involve mainly solid business development efforts, and potentially customized solutions engineering.

Wider-reaching outcomes include increased transaction volume and TVL, and the establishment of Arbitrum as a leading platform for enterprise blockchain deployments.

Strategic Reasoning

With a more crypto-friendly regulatory environment, more and more institutions are showing interest in crypto, including launching their own blockchains.

Arbitrum is now in a perfect position, with a mature L2 tech stack and strong dApp use cases on Arbitrum One, to onboard institutions, especially from tradfi and fintech.

This proactive approach will position Arbitrum as the preferred choice for enterprises entering the blockchain space.

Key Results (KPIs)

  1. Secure commitments from at least three institutional partners to deploy Orbit chains.
  2. Launch at least one institutional Orbit chain on mainnet in 2025.
  3. Achieve a 20% increase in total transaction volume across all Arbitrum chains due to these new institutional chain(s). This can be measured as increase in TPS or UOPS since the launch of partner chain(s) within a certain timeframe (e.g. 6 months).
  4. Document these enterprise use cases and publish them as case studies to attract further interest.

Further Details

  • Institutional partners can be either tradfi partners such as banks, or fintech startups such as Robinhood, or some other non-crypto-native partners.
  • I was unsure whether to make this a 1-year objective with fewer institutional partners as a KPI, or a 2-year objective with a larger KPI. But I think a shorter timeframe will incentivize early and fast action to achieve the goals of this objective.
  • As for the objective itself, I think we all quietly assume that AF or OCL are reaching out to institutions (and they probably are), but it does not mean that the DAO should not do the same. Though, both DAO and AF/OCL should coordinate to avoid reaching out to the same potential clients and causing confusion.
  • I imagine achieving the objective KPIs would require people involved with it to attend non-crypto events/conferences to start developing relationships with potential clients. Arbitrum’s participation in non-crypto events is something that @krst has proposed many times before, maybe now this objective will provide a good incentive to start doing so.

P.S.: Since no one has posted a reply in this topic before me, I’m not sure if I’ve done it correctly or even in the right place, so I’d appreciate feedback from @Entropy on whether everything is fine with this submission.

Also, I’m open to update the submission, especially in the KPI section, so everyone’s feedback is welcome!

1 Like

Hey @TempeTechie.

Thanks for the one-off submission!

We can confirm that the submission has indeed been made in the right place. One piece of feedback we’d like to offer when it comes to the submission’s structure is that you might want to specify your third key result further. For example, when and how should the initial total transaction volume be calculated? Otherwise, everyone might not be using the same figures to assess the change in the metric.

1 Like

Thanks for the feedback! As for the tx volume, I was thinking about the raise in TPS or even UOPS (user ops per second), as measured on the L2beat website. I’ll update my submission with this info :+1:

2-Year Strategic Objective: Driving Mobile Adoption on Arbitrum

Statement

Significantly increase mobile adoption of Arbitrum by establishing a robust mobile ecosystem, including the launch of a dedicated Arbitrum mobile wallet, to improve accessibility and user engagement.

Explanation

When it comes to end users (aka retail), having a strong mobile presence is crucial. This was especially evident in the past two years, as the adoption of the Phantom wallet by Gen Z users significantly increased Solana’s usage.

Arbitrum should not be a platform that just sits and waits for someone to use it. Instead, in this very competitive space, a pro-active approach is needed. Increasing Arbitrum’s mobile presence will help onboard more users, especially younger generations.

Risks include the complexity of developing and maintaining secure and user-friendly mobile apps, and the need for ongoing marketing and user education.

Non-capital resources required involve software development, UI/UX design, security audits, marketing, and community support.

Wider-reaching outcomes include increased transaction volume, a more age-diverse and engaged user base, and the establishment of Arbitrum as a leading platform for mobile-first dApps.

Key Results

  1. Launch at least one dedicated Arbitrum wallet on iOS and/or Android, preferably within the first year of the start of the objective.
  2. Reach 500,000 mobile wallet downloads within two years of launch, and maintain a user rating of at least 4 stars on app stores.
  3. Integration of Arbitrum One (and perhaps other Orbit chains) into at least five web3 projects’ mobile apps.
  4. Get at least five established non-crypto mobile apps to integrate Arbitrum One.
  5. Organize mobile-focused hackathons or similar initiatives to bring new mobile apps (either native or PWAs) into the Arbitrum ecosystem.

Further Details

  • A dedicated mobile app could be built by issuing a request for offers, to which development companies would apply - ideally those that have already built a mobile wallet before and can develop a white-label solution for Arbitrum.
  • Arbitrum DAO could then pick one or multiple offers. Selecting multiple would encourage competition between mobile wallets, benefiting both end-users and the Arbitrum ecosystem as a whole.
  • Besides having its own dedicated wallet, Arbitrum should also work toward integrating with existing established mobile apps, both crypto-related and non-crypto-related.

I’m open to updating this submission, so please share your feedback.

2-year Objective: Arbitrum’s Social Media and Chat App Expansion

Statement

Expand Arbitrum’s presence and usefulness by adding onchain features to popular social networks and messaging apps using bots, agents, and mini-apps. Also, support the creation of native decentralized social networks and chat apps on Arbitrum.

Explanation

This objective aligns with Arbitrum’s MVP by making Arbitrum more accessible and integrating it into users’ daily online interactions.

We’ve seen many interesting use cases in recent months where onchain actions were performed through text-based interactions with agents on social media and messaging apps. The most commonly used platforms were X (Twitter), Farcaster, Telegram, and Discord, while the most used blockchains were Solana, Base, and, to some extent, TON.

Performing onchain actions through social media and messaging apps will become more common over time, and it’s important that Arbitrum doesn’t get left behind. That’s why we need to take action to integrate Arbitrum with popular social networks and chat apps.

Risks include the complexities of integrating with centralized platforms (API restrictions, deplatforming), security considerations, and existing competition.

Non-capital resources required involve software development, community engagement, and marketing.

Wider-reaching outcomes include increased DeFi activity, easier onboarding for people new to crypto, and establishing Arbitrum as a trusted platform to enhance the usefulness of social applications.

Key Results

  1. The launch of at least 10 functional bots, agents, and mini-apps for popular social networks (e.g., Twitter/X, Facebook) and chat apps (e.g., Telegram, Discord), which will perform onchain Arbitrum actions such as sending and swapping tokens, using DeFi, and copy trading.

  2. Achieve a combined user base of 10,000 users across all integrated bots, agents, and mini-apps within two years of launch.

  3. Establish a grants program to support the development of these bots, agents, and mini-apps on existing social media and messaging apps. As well as development of Arbitrum-native decentralized social networks and chat apps.

  4. Host at least two hackathons focused on building social and chat applications (bots, agents, mini-apps, standalone apps) with Arbitrum integration.

  5. Launch at least two successful Arbitrum-native decentralized social networks or chat apps with a combined user base of 50,000 within two years of launch.

I look forward to hearing everyone’s thoughts on this.