[Brahma] LTIPP Application Draft

SECTION 1: APPLICANT INFORMATION

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: Alessandro Tenconi

Project Name: Brahma.fi

Project Description: Brahma Console is the fast and secure execution environment to navigate DeFi on Arbitrum, built on Safe. Designed to be the go-to suite for both individuals and teams, it brings programmable automation, delegation, and streamlined execution.

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

Brahma has an international team of 20 contributors in 12 countries (65% ENG + 35% PROD), combining unique engineering, Quant, and product development expertise.

Project Links:

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

Website https://www.brahma.fi/

Twitter https://twitter.com/0xdanzu

Github https://github.com/Brahma-fi/console-core-v2/

Contact Information

Point of Contact: Forum handle: ale_brahma.fi

Point of Contact’s TG handle: [Telegram] alessandrotc

Twitter: [Twitter Handle] @BrahmaFi

Email: [Email Address] alessandro@brahma.fi

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

Brahma has an international team of 20 contributors in 12 countries (65% ENG + 35% PROD), combining unique engineering, Quant, and product development expertise. Brahma’s engineering team comprises a unique blend of deep expertise in DeFi infrastructure at the EVM level, quantitative analysis, DevOps, and cybersecurity.

The Product & Marketing team is crypto native and comes together from a variety of backgrounds, including experience at market makers, exchanges, and crypto providers such as Efficient Frontier, Crypto.com, and IntoTheBlock.

The team has worked together for over two years and has built Console from the ground up as a unique interaction layer facilitating the interaction of Arbitrum users within the ecosystem.

Brahma was one of the inaugural grantees of the Safe grant program (Safe Grants Program: Wave 1 Retro - Wave 1 - Safe Community Forum), to build an open source module to enable automated execution on Safes. The Brahma team delivered on the grant received, exceeding all expectations and launching the Safe module ahead of schedule.

What novelty or innovation does your product bring to Arbitrum?

Console brings the first Safe-compatible automation and execution suite to Arbitrum, empowering teams and individuals to streamline their DeFi and on-chain operations while retaining higher security than with traditional setups.

Console is a uniquely secure and performant stack for both individuals and teams, with:

  1. Sub-Accounts to segregate risk across their wallets.

  2. Trustless delegation and access control through Policies applied on top of Sub-Accounts

  3. Automations and batched execution on top of Arbitrum protocols

  4. Improved governance participation from DAOs and protocols, which can leverage Console to solve coordination problems across multi-sig signers.

  5. Manage multiple Safes all at once

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

Console is fully composable by design. It integrates with Safe, the most widely used self-custody solution with over $100B TVL. Console lets users access and build multiple automation and execution routines with multiple Arbitrum dApps simultaneously.

Console also supports key actions in-app for extra speed and security, including swapping, lending, and bridging. Furthermore, anyone can access Console using an EOA wallet (Metamask, Rabby, etc.), and users can connect with any dApps on the Arbitrum using Wallet Connect (as part of our roadmap, we are also launching a browser extension to simplify the user experience when interacting with dApps).

In addition to this:

  1. We are working to develop specific automations and batched routines with Arbitrum protocols, facilitating the flow of on-chain operations

  2. Console is a coordination and execution stack that can be leveraged by any DAO team using a Safe multi-sig. We are already working with selected protocol teams on Arbitrum, including Savvy, Rysk, and Poolshark.

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

Brahma Console doesn’t have a direct comparable. It is a unique combined suite to: automate, delegate, and improve on-chain execution while setting granular access control with policies. Additionally, it does so while being fully self-custodial on top of Safe wallets. Users are in full control of their keys and can detach and utilize their Safes separately at any time.

Consoles’ USP is delivering efficient execution without compromising security for individuals and large teams. This comes from the ability to combine Safe’s programmability with a stack built from the ground up for on-chain execution.

Parallels with other protocols can be drawn to individual pillars of Console:

  • Automation: DeFiSaver has been pioneering smart contract wallet automation with batched capabilities on Ethereum, powering automated lending positions and risk management.
  • Access Control/Delegation: Gnosis Guild Zodiac Modules have brought configurable delegation to Safe wallets.

Usage and Metrics

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

User retention is extremely important to us, just like the quality of their interactions.

Brahma’s value proposition goes beyond the incentives proposed. On the one hand, we leverage incentives to attract users to the value propositions Console offers, ensuring a balanced distribution encouraging long-term usage and high-quality interactions. On the other hand, we are continuously partnering with protocols to offer new automations and execution routines, simplifying the user experience on Arbitrum. The idea is that once users get onboarded to Brahma they are never leaving. To ensure user retention after the incentives are over, we are working on our TGE in late 2024, including further campaigns (e.g., rebates on user fees, rewarding users for their activity on Brahma, and offering exclusive features).

We will monitor key user-centric metrics and build analytics to assess user retention better.

Among the criteria that we will monitor we include:

  1. The frequency of interactions within Console

  2. The frequency and quality of interactions with dApps on Arbitrum

  3. The growth of the utilization rate of the capital deposited in Consoles overtime

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:

We want Console to become the main interaction layer for users on Arbitrum, providing them with better execution efficiency when navigating DeFi without compromising on security. In turn, this will drive usage to dApps and Arbitrum.

  • Console key KPIs are TVL, number, and quality of transactions.
  • Daily Transaction count
  • Daily Active Users
  • The number of Consoles and retention of users is also highly important to us. We are building analytics to be able to better assess individual user retention, including the quality of their interactions (e.g. top protocols on Arbitrum, and further measures to avoid washtrading)
  • Protocols Integrated in Console

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

No third-party consultant was engaged or involved.



SECTION 2b: PROTOCOL DETAILS

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]

No, Console is born to be EVM compatible and function across multiple chains. Its unique selling proposition as a cross-chain interaction layer, makes Brahma born to be EVM-compatible and function across multiple chains.
Nonetheless, we recognise and want to establish Arbitrum as our home due to its unique DeFi ecosystem and the involvement of protocols and DAOs in its decentralized governance.

We first released Console on ETH Mainnet in mid-December 2023 as the base network for adopting Safe Wallets. Less than a month later, we performed our first expansion to Arbitrum in January 2024 (launch blog here), drawn in by the Arbitrum thriving DeFi ecosystem as the best place to unlock the full value of Console for users. Our targeted efforts allowed Console to kickstart on Arbitrum with profuse feedback over its first month and a half of operation.

On what other networks is the protocol deployed?:

ETH Mainnet, Blast

What date did you deploy on Arbitrum mainnet?:

We deployed Console’s contracts on Arbitrum on December 5th, 2023, onboarding early existing mainnet users, and then announced the full Arbitrum launch on January 11th, 2024: https://www.brahma.fi/blog/console-is-live-on-arbitrum.

Here is the contract deployment transaction:

For the contract: AddressProvider | Address 0x6fcf22e22f736d9ead75de8a1f12ca869287e229 | Arbiscan

Do you have a native token?:

No. It is planned for Q3/4 2024.

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

No

Current Incentivization: How are you currently incentivizing your protocol?

No. Console has not run/announced, or teased any incentive. Its usage and growth thus far have been completely organic.

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

  • TVL on Arbitrum: $2m
  • Over 500 users and 1000 operations on Arbitrum
  • 20% of Console users have created Sub-Accounts
  • 3 Arbitrum DAOs and protocols are testing Console for their own operations

Console has onboarded over 500 new Safe users with over 1000 transactions and 2M TVL in its first 1.5 months on Arbitrum.

Protocol Roadmap:

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

Throughout the year, Brahma is planning a series of standalone and incremental feature updates to fortify how the different Unique Selling Propositions of Console come together to facilitate how users and protocols navigate and interact with the Arbitrum ecosystem. Our Arbitrum product milestones are as follows:

March:

  • New dApp connection and execution Framework: Load and simulate actions on multiple dApps, then execute all in 1 transaction
  • New in-app swap experience with manual route selection, combining 4+ aggregators

Q2:

  • DCA and TWAP automations on Arbitrum
  • Policy and transaction templates to allow users to quickly access the needed transaction/policy type from a unified UI
  • Lending position management Automation
  • In-app bridging experience
  • Mobile signature experience

Q3 & Q4:

  • Third-party Automation API: enable external teams to build automations on Console and automated trading to be performed on individual SubAccounts
  • Advanced order types for in-app swapping and automation
  • Passkey support with biometric signing
  • Multiple automation releases based on user demand, including:
    • Depeg automations on LP positions
    • Yield harvesting automations
    • Auto-withdrawal automations based on security alerts, APY, and liquidity figures

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

Console has been audited by: Spearbit, Code4rena, and Ackee.

Other independent auditors, including Trust90, have audited the previous version of Console.

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.



SECTION 3: GRANT INFORMATION

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]

150k ARB

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]

The request for 150k ARB is calculated to achieve significant TVL growth from the current $2M to $10M, incentivizing volume and quality interactions with Arbitrum protocols throughout the program’s length.

To bring activity to Console we are setting up our incentives first to attract TVL, and then optimize for volume:

1. New Users and TVL Incentives: 55k ARB (~36.67% of the total grant)

  1. Transactions on Arbitrum Protocols and Quality Interactions: 50k ARB (~33.33% of total grant)
  2. DAO Operations and Ecosystem Engagement: 20k ARB (~13.33% of total grant)
  3. Arbitrum Interaction Booster with Incentivized Bridging: 25k ARB (~16.67% of the total grant)

Emissions Strategy:

The emissions are designed to kickstart this growth and attract substantial early participation, reflected in a higher initial distribution of the incentives distributed in Month 1 during the first 2 weeks. By achieving more than half of the targeted TVL growth by the end of Week 4, we will create a strong foundation for sustained growth and engagement, ensuring that we can focus on incentivizing user activity for the rest of the program.

The structured weekly emissions ensure that participants have continuous incentives to contribute to the TVL and engage with the platform, promoting stickiness and long-term engagement beyond the incentive period.

Given our initial goal to incentivize TVL growth, with more than half of our target TVL achieved by Week 4, the weekly emissions in the first month will be front-loaded.

Month 1 starts with a higher distribution in Weeks 1 and 2—respectively 16,666 and 12,500 ARB. The total monthly emissions will be equal, with 50k ARB/month emission.

Weekly ARB Emissions in Month 1:

Week ARB Emissions Cumulative ARB Emissions
1 16,666 16,666
2 12,500 29,166
3 10,417 39,583
4 10,417 50,000

For the subsequent two months, the remaining 90k ARB will be distributed linearly (11,250 ARB/week) to support continuous growth and engagement, encouraging on-chain interactions using Console and ensuring the TVL grows steadily towards the $10M target.

The distribution will be done through a point system with bi-weekly epochs. These points will be accrued by users performing operations on Console and scored on these metrics on a daily basis. Users can see their score change and can claim at the end of each epoch. To incentivize retention and long-term usage, a multiplier is applied on interaction frequency and unclaimed points. This way, users can compound their points based on usage across the three months, disincentivizing leaving early.

We estimated to offer an estimated 3.75% yield over three months, designed to be attractive enough to ramp up the TVL to our target, while the points system and boost mechanism will ensure ongoing engagement and stickiness.

Breakdown of Average Yield:

To calculate the % yield for average depositors over the 3 months, considering the TVL growth to $10M and an average boost for transacting users, we consider the total value of incentives distributed and the average TVL over the period.

The TVL gained by Brahma, assuming a linear growth from $2M to $10M over 3 months, would be:

TVL Accumulated = (End TVL - Start TVL) =($10 M - $ 2M ) = $8M

The total value of incentives distributed over 3 months is $300k (150k ARB at $2 per ARB).

The % yield over the 3 months would then be:

% Yield = (Total Incentives / TVL Accumulated) * 100 = ($300k / $8M) *100 ≈ 3.75%

This approach ensures that the incentives are substantial enough to meaningfully impact TVL growth and user engagement while also being distributed in a manner that encourages long-term platform use and ecosystem integration, justifying the specific request for 150k ARB.

Our primary goal is to onboard new users to Safes through Brahma and increase their transaction volume on Arbitrum over time. This incentive grant will be instrumental in attracting new users to Console and boosting our growth on Arbitrum.

Due to its nature, Console also helps increase users’ activity on Arbitrum, providing them with tools to execute transactions more efficiently. Console’s basis is composability, allowing users to execute securely across Arbitrum protocols.

Indirectly, all of the grant contributions will contribute to second-order impact across the Arbitrum ecosystem in terms of increased activity and fees and increased security for its users

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

NA

Grant Breakdown:

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

1. New Users and TVL Incentives: 55k ARB (~36.67% of the total grant)

  1. Transactions on Arbitrum Protocols and Quality Interactions: 50k ARB (~33.33% of total grant)
  2. DAO Operations and Ecosystem Engagement: 20k ARB (~13.33% of total grant)
  3. Arbitrum Interaction Booster with Incentivized Bridging: 25k ARB (~16.67% of the total grant)

Grant Specifications:

  • Current TVL: $2M

  • Targeted TVL by end of Month 3: $10M (with >50% of the total $8M growth to be achieved by Week 4)

  • Total Incentives: 150k ARB (at an assumed price of $2 per ARB)

  • The incentives are distributed in weekly epochs, with a focus on exponential distribution in the early weeks to kick-start growth, followed by a linear increase in TVL; points and incentives will be streamed continuously for the rest of the program, with users able to claim them on a bi-weekly basis.

Grant allocation factors:

1. New Users and TVL Incentives:

  • Objective: Jumpstart the TVL and attract new users with an exponential incentive distribution in the first weeks, transitioning to retaining and activating TVL with quality volume across the Arbitrum ecosystem.
  • Allocation: 55k ARB (~36.67% of the total grant)
    • Out of this, we will allocate 10k ARB(6.66%) for gas fee rebates, subsidizing up to 70% of transaction gas fee costs for users
  • Rationale: The structure will be tiered by deposit size and early participation to reward early adopters. This strategy aims to rapidly build up the TVL and user base, creating a foundation for building transaction volume on Arbitrum protocols and engagement.

2. Transactions on Arbitrum Protocols and Quality Interactions:

  • Objective: Encourage a high volume of transactions and quality interactions within the Arbitrum ecosystem, rewarding consistent behavior and repeated operations.
  • Allocation: 50k ARB (~33.33% of total grant)
  • Rationale: After the initial TVL growth, the focus will shift towards activating this liquidity and user base with high-quality volume and interactions in the Arbitrum ecosystem. This includes not just the number of transactions but the diversity and impact of these transactions on the ecosystem. Consistent behaviour and repeated operations will be incentivized to ensure stickiness and ongoing engagement.

3. DAO Operations and Ecosystem Engagement:

  • Objective: Incentivize DAOs and protocol teams for managing operations through the Brahma Console and engaging deeply within the Arbitrum ecosystem.
  • Allocation: 20k ARB (~13.33% of total grant)
  • Rationale: DAOs are pivotal in driving forward protocol usage and ecosystem growth. By incentivizing DAOs to onboard, operate and interact through Brahma on Arbitrum, we aim to embed our platform deeply within the ecosystem’s operational frameworks, ensuring sustained growth and utility.

4. Arbitrum Interaction Booster with Incentivized Bridging:

  • Objective: Boost interactions by rewarding bridging to Arbitrum from other chains and utilizing selected protocols, on top of rewarding top-quality interactions.
  • Allocation: 25k ARB (~16.67% of the total grant) distributed linearly rewarding Console users bridging to Arbitrum
  • Rationale: This booster will reward users who bring liquidity to Arbitrum from other chains and engage with selected high-impact protocols. This will increase the TVL and user base and enhance the interconnectedness of the Arbitrum ecosystem with the broader DeFi landscape. High-quality interactions, particularly those that support underutilized or strategically important protocols, will be highly rewarded to foster a diverse and robust ecosystem.

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

0x6b29610D6c6a9E47812bE40F1335918bd63321bf

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.

Team governance ARB Safe multi-sig with 8/15 cold wallets signatures threshold.

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

We don’t have a native token or DAO wallet, only our governance Safe wallets and company treasury.

ETH: 0x6b29610D6c6a9E47812bE40F1335918bd63321bf ARB:0x6b29610D6c6a9E47812bE40F1335918bd63321bf

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

N/A, not built yet



SECTION 4: GRANT OBJECTIVES, EXECUTION AND MILESTONES

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]

  1. Strengthen the offer of interaction tools to navigate the Arbitrum ecosystem efficiently
  2. Introduce a new concept of multi-sigs as a best practice in DeFi without compromising between security and execution.
  3. Improve the way Arbitrum protocols manage their treasury, operations and participate in governance.
  4. Attract new users to Console and stimulate high-quality interactions with Arbitrum protocols
  5. Strengthening the security of users navigating the Arbitrum ecosystem
  6. Encourage the creation of Arbitrum-native Safes, migrating from Ethereum.
  7. Stimulate and increase composability within the ecosystem with batched execution and custom automation routines across Arbitrum protocols.
  8. Trickle-down the utility, increasing fees generated by Arbitrum dApps used by Brahma users.

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

Month 1 (Kickstart Phase):

  • Objective: Aggressively build TVL and attract new users (6m TVL target)
  • Allocation: 1/3 of total incentives (50k ARB).
  • Method: Exponential weekly distribution to front-load incentives, creating a strong initial growth in TVL and user base. Points are earned based on the amount deposited, interaction with the dApp, and bridging activities from other chains to Arbitrum.

Months 2 & 3 (Retention and Activation Phase):

  • Objective: Retain the built TVL and encourage high-quality volume and interactions within the ecosystem ($10m TVL)
  • Allocation: 66.66% of total incentives (100k ARB)
  • Method: Points continue to be distributed with a focus on rewarding repeat operations, consistent behavior, and quality interactions within selected Arbitrum protocols. This phase aims to encourage users to utilize their TVL actively, rewarding a high utilization ratio and fostering a habit that extends beyond the incentive period.

Points-Based Incentive System:

  • Users earn points weekly based on their activities: deposits (TVL growth), transactions (volume), quality interactions (utilizing selected Arbitrum protocols), and bridging activities.
  • The points system is designed to reward not just the quantity but the quality and consistency of user engagement.
  • Points can be claimed as ARB rewards every two weeks, with the claimable amount increasing if points are held unclaimed and boosted by continued interaction in subsequent months. This design encourages users to remain active on the platform to maximize their rewards.

Console will implement incentives for high-quality interactions to avoid washtrading and Sybill. We will also implement a monitoring system to ensure that we maximise the grant distributions to the users who are contributing the most value and engaging in the most interactions within the Arbitrum ecosystem.

This will include operating on key Arbitrum protocols, including:

  1. GMX
  2. Camelot
  3. MUX
  4. Pendle
  5. AAVE
  6. Uniswap
  7. Balancer
  8. Savvy
  9. Rysk
  10. Radiant

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]

  • Unclaimed Points Boost: We will reward users who do not claim their ARB on each period with a multiplier. By allowing unclaimed points to accumulate and increase in value with continued platform interaction, users are incentivized to remain active and engaged to maximize their rewards. This mechanism discourages immediate withdrawal after claiming rewards and encourages long-term platform use.
  • Quality Interaction Rewards: Focusing on rewarding high-quality interactions with the ecosystem ensures that users are not just passively depositing for rewards but actively participating in ways that benefit the ecosystem. This active participation is more likely to lead to sustained platform use.
  • Key Focus on User Retention and Transactions: As Brahma was developed as a tool to facilitate users’ on-chain interaction and increase their productivity, most of our KPIs will reflect this, focusing on user growth and volume-based KPIs and metrics.

We’ll monitor user stickiness through metrics such as weekly and monthly active users, utilization rate, TVL flows, and high-quality interactions using Console. We’ll also employ secondary metrics such as the number of sub-accounts and automation created and the number of quality protocols interacted with.

We will employ additional checks to reward the most qualitative transactions and avoid being played by mercenary capital.

We’ll complement the LTIP incentives with our own campaigns to reduce turnover after the grant incentives are over, and we’ll continue to develop partnerships with Arbitrum protocols.

One point we wish to highlight is that Brahma will have a different usage curve due to its positioning as an interaction layer and smart wallet. While protocols might suffer from reduced user activity post-LTIPP, Brahma’s unique value propositions will stay, making it the best way users and protocols can execute on-chain on Arbitrum and increasing overall user productivity and dApp usage on Arbitrum.

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

•TVL at the end of the program: $10m (5x of current TVL on Arbitrum)

•Interactions with dApps on Arbitrum: 10,000 (10x of current)

•Console users: 770 new users (2.2x of current users)

All the relevant KPIs will be monitored through a Dune dashboard.

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

Milestones Month 1 Month 2 Month 3
TVL 6m 8m >10m
Number of Users 257 514 770
Number of Operations 3,333 6,666 10,000

The feasibility of these milestones is justified based on the growth we have achieved since our launch on Arbitrum ($2m in TVL in less than 2 months) organically.

The combination of incentives to attract TVL and reward high-quality interactions ensures the sustainability of the objectives in two phases.

Furthermore, the development of Arbitrum-specific automations and our integrations (future and in progress) with protocols and DAOs, ensures additional processes are in place to reach the targets projected.

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]

Due to our positioning, we are poised to contribute to the Arbitrum ecosystem in more than one way:

  1. Improving user security through risk segregation (advanced custody through multi-sig as the best standard nowadays)
  2. Trustless Delegation for DAOs: governance, voting, operations delegation, grant programs.
  3. In-house composability: batched and chained transactions across protocols, and easier way to compose strategies across protocols.
  4. Accessibility: level the playing field, allowing everyone to execute complex routines with automations
  5. Bringing efficiency to multisigs on Arbitrum and streamlining the way protocols and DAOs contribute to Governance and deal with Treasury Management and Operations.

While our product was initially launched on Mainnet, the high gas fees hinder the use of Console through a broader public. Thanks to much lower fees, Arbitrum users can create a new Console for just a few cents. For this reason, the barrier of entry to the USP of Console is much lower on Arbitrum. The product can be used by a broader public and unlock its full potential to improve on-chain execution on a wider range of use cases.

We are already working with several Arbitrum protocols, and we envision Brahma as a uniquely positioned stack that improves the way Arbitrum users and protocols operate on-chain.

In this sense, Brahma will be a booster that will help Arbitrum users navigate protocols and LTIPP incentives seamlessly. By developing more upcoming automations with Arbitrum protocols, we will also ensure that we continue contributing to Arbitrum volume and fees generated from the sequencer.

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



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?

Yes

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]

Yes. We will share a Dune dashboard covering the grant metrics required for milestone tracking.

First Offense: *If a project does not provide a bi-weekly update, an involved party (council, advisor, or program manager) will remind it. Upon this reminder, the project is given 72 hours to complete the requirement, or its 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

1 Like

Hello @BrahmaConsole ,

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

@BrahmaConsole join Arbitrum LTIPP

As ITU Blockchain, we strongly support Brahma’s proposal.

Their proposal includes a comprehensive plan to grow the Arbitrum ecosystem and foster innovation. In particular, important points such as facilitating DeFi access for users such as DAOs and multi-signatures are highlighted. We also believe that the grant amount is reasonable, given the current demand and the size of the project. The experience and past success of the Brahma team increase the likelihood that the proposed plan will materialize. It is noted that the proposed objectives are ambitious but supported by the team’s past successes and the organic growth of the Arbitrum ecosystem. Therefore, Brahma’s proposal could make significant contributions to the Arbitrum ecosystem and should be supported.