[grant update] bleu Tech Partner of OP Native Projects

[bleu_builders]

Dear Optimism Community,

We want to provide a brief update on our “Tech Partner of OP Native Projects” grant approved in Season 5 and seek your input on our path forward.

Background

Our grant aims to offer 1,000 hours of technical support (UI/UX, backend, frontend, data analysis, launch support) to Optimism ecosystem projects. We’re eager to start but have encountered a challenge with project selection.

In the first version of the proposal, we proposed to handle vetting projects ourselves. During the review process, the reviewers asked for a change so that the Grants Council does the selection instead (see approved proposal), which got incorporated into our final grant scope. Despite the grant’s approval, though, we haven’t received any project assignments from the Grants Council so far.

We understand that the Grants Council is currently managing a high workload, which may have contributed to the delay in project assignments. Given this situation, we reached out to @gonna.eth to discuss potential solutions, and he proposed.

Proposed Approach

After discussing with @gonna.eth, he proposed an alternative that doesn’t require the Grants Council’s direct involvement given their current workload:

1. 50% of our services to existing grantees
2. 50% to projects we select independently, based off the selection criteria below

We like this suggestion because it potentially allows us to start working promptly, supporting both vetted grantees and new initiatives without additional Grants Council intervention.

Considerations

• Selecting and negotiating with projects will require time that wasn’t accounted for in the original grant. We propose deducting these hours from the total grant hours to ensure we’re being fair with our time.
• We recognize that this approach represents a change from the approved grant scope. We want to ensure this change aligns with the community’s expectations and Optimism’s governance standards, hence why this forum post.
• The 50/50 split is not based on any specific reason. We’re open to amending the split in favor of either part down the line upon community feedback and also our own perception from watching the process unfold.

Selection Criteria

For the projects we select independently, we propose focusing on open-source projects building on Optimism. Our criteria will include:

1. Open-source nature of the project
2. Relevance to the Optimism ecosystem
3. Potential impact and innovation
4. Technical feasibility and need for our expertise

Our proposal is to announce selected projects every month, allowing the community to provide feedback or intervene if necessary.

What We Need From You

We’re seeking community feedback on:

1. The 50/50 split between grantees and independently selected projects
2. Our proposed selection criteria for independent projects
3. Any other concerns we should address

Next Steps

1. Review the community feedback in this post over the next week
2. Do a follow-up post summarizing key points and our planned actions
3. Share list of potential grantees that could benefit from our services by next Monday

Finally, if you’re building on Optimism and think our services could be useful, please reach out to us on Telegram at rpunktj or comment in this thread.

We’re looking forward to rolling up our sleeves and getting to work!

[Bunnic]

I support the idea of removing the need for the GC intervention from the overall process. The approach of addressing both existing grantees and selecting projects independently is also sound. Additional feedback from the GC members would be valuable for refining the selection criteria further.

The current 50/50 split seems reasonable as an initial approach: adjustments probably will be necessary over time, which you have already anticipated.

The only thing that concerns me a bit, is how the time spent selecting projects and negotiating will be measured/recorded. These steps are crucial indeed, and can easily vary per project, making them harder to calculate and register.

[bleu_builders]

We’re back with an update on our “Tech Partner of OP Native Projects” grant. Here’s what we’ve done so far and what’s next.

Project selection

• We realized that reviewing all grantees submissions wouldn’t necessarily increase response rates and would eat up a lot of the time we’d rather be helping projects
• Thus, to reduce time spent on project selection and any potential bias, we decided to serve teams on a first-come, first-served basis.
  • What that means is that we’ll be reaching out to everyone and making decisions as responses come in.
  • This way, we can allocate more time to delivering value to projects, allows them to self-identify their needs and also ensures we don’t miss any opportunities.
• To start, we chose the following mission requests from Season 5, which seemed to allow for broader support rather than assisting with closed-scope projects that have already been funded:
  • Builders grants program mission request
  • Growth and experiments grants program mission request
  • Deliver a Best-in-Class Perp Dex Mission Request
  • Making Optimism a primary home of liquid staked eth
• We’re reaching out to the 58 projects that fall into those mission requests from S5. We’ll reach out to grantees via Charmverse and TG (if we can find one). We also posted a message to Discord but got no engagement there.
  • We set up a dedicated Notion page where you can verify the status of this process.
  • Note: we’re NOT reaching out to Balancer specifically to avoid a potential conflict of interest since we’ve been grantees for Balancer in the past and one of our founders (Fábio Mendes) currently works at Balancer Labs.

Triaging interested projects

We’ve created a simple Application Form for projects to use when applying for our support. If you’re building on Optimism or know someone who is and think our services could be useful, please fill it out and post it to this thread or send it to @rpunktj (Telegram) or jose@bleu.builders or straight up schedule a call with José using this link.

Project Name:
Contact Person:
Email/Telegram:

1. Brief Project Description:

2. What specific technical support do you need? (Select all that apply)
   [ ] UI/UX Design
   [ ] Backend Development
   [ ] Frontend Development
   [ ] Data Analysis
   [ ] Other (please specify)

3. Estimated time requirement (in hours, if known):

4. Any specific deadlines or timelines we should be aware of?

5. Additional information you'd like to share:

Reporting

To @Bunnic 's point and to ensure we’re being transparent with how we’re utilizing our time and allow for community feedback about how they’re being used, we also want to show a breakdown of how hours are spent.

Here’s a link where you can check our progress broken down by task (i.e. project selection, design/UX/UI, development, and data science/analytics) and by project.

Note: op-tech-partner-s5-project-selection is our internal name for the projects “prospection” project.

Next Steps

1. Finish reaching out to all the 58 grantees from the aforementioned mission requests in S5;
2. Process incoming applications;
3. We’ll share updates on the projects we’re assisting and the impact of our work.

We appreciate the community’s support and open to any feedbacks here!

[bleu_builders]

Hey folks, here’s an update on our efforts over the past two weeks:

Latest Activities

After reaching out to all 60 selected projects from S5/S6 via Charmverse, email, and Telegram (when available), we’ve received positive responses and interest from several grantees. We’re now moving forward with initial meetings and excited to roll up our sleeves!

First Impressions

As we’ve begun engaging with interested teams, we’ve faced some challenges in our initial interactions. While many teams are enthusiastic about our potential collaboration, they often struggle to pinpoint exactly where they need support within their projects.

Despite these hurdles, we’re maintaining a proactive approach, consistently following up with all teams that have expressed interest in working with us.

Addressing Challenges

To tackle these issues and optimize our collaboration, we’re considering a new approach:

• We’ve realized that spending too much time on scope finalization could eat into our actual execution time. That’s not ideal for anyone involved.
• We’ve opted to test a more flexible collaboration model, where we start working closely with a team’s internal members without a rigid scope. This approach allows us to dive in, get our hands dirty, and adapt as we go.
• The goal is to streamline the process and potentially boost our productivity by being more adaptive and responsive to the team’s evolving needs.

It’s worth noting that this is an experimental approach. We’re not setting it on stone – please speak up if you have thoughts, concerns, or alternative ideas.

Highlights

Silo Finance:

They requested our help on building a Telegram bot to notify users when their borrow positions become risky (near liquidation). You can find more details on the Meeting Notes.

We’ve already delivered a PoC and received positive feedback to continue working with them. In case you’re curious, you can find the bot’s code here. Also, there’s a dev-only live version you can try out at @silo_hf_dev_bot — be warned, it’s WIP and will be potentially at times broken

Pike:
Also a promising start with Pike on their project for the Growth and Experiments Grants Program. We’ve sent a proposal based on the agreed-upon scope (check here the meeting notes and the proposal) and received positive feedback from the Pike team regarding our initial proposal.

The next step is to wait for Pike to share their codebase with us. Once we have access to their code, we’ll be able to refine our proposal and provide a more detailed plan for our collaboration.

Project Status Overview

We’ve added more status categories to our project tracking pipeline for better transparency. Here’s a summary of our current engagement status:

Status	Count	Notable Projects
POC	1	Silo Finance
Pending team proposal	4	Pike, Candide, Namespace, Covenant
Pending bleu proposal	2	Dark Forest ARES, aToken Network
Follow up	7	ETHx on OP, Strands’ Optimism Integration, Executable, and more
Contact Attempted	44	Various projects across S5, S6
Lost	2	In-depth fee tracker, dAppBooster

Next Steps

• Continue discussions with interested projects to define specific assistance scopes.
• Begin providing technical support to projects that have completed the scoping process.
• Follow up with non-responsive projects one final time. Otherwise mark as lost if they don’t respond by EOW next week (Aug 30);

As a last note, if you’re building on Optimism and think our services could be useful, please reach out to us on Telegram at rpunktj or comment in this thread. We’re excited about the progress we’ve made and look forward to contributing to the growth of the Optimism ecosystem. Stay tuned for more updates!

[Jrocki]

Hello and thank you for your continued updates here. The meeting note links for Pike and Silo do not seem to be accessible.

@bleu_builders

You can find more details on the Meeting Notes.

[mendesfabio]

I made the links public now - thanks for pointing out!

[bleu_builders]

We’re excited to provide our latest update! Here’s a summary of our recent activities and upcoming plans:

Project Status Overview

This table provides a detailed view of each project’s current status:

Project Name	Status	Point of Contact	Estimated demand (hours)
Silo Finance (Liquidations Telegram Bot)	Wrapping up	Ayham (AJ)	40
Pike (Liquidation Bot Pt. 1)	In progress	@ladderchaos	40
Namespace (Fullstack development)	In progress	@thecap.eth	160, initially
Candide (Account Recovery Frontend)	In progress	@heymarcopolo	~100
DarkForest ARES	Waiting for resources to free up (bleu)	@fromddy	~100
aDeal network	Waiting for resources to free up (bleu)	@jacoblair	200
Optimistic Crowdstaking	Waiting for scope	@OxRussel	Unclear
ETHx on OP	Waiting for scope	@AnoothiKumar	Unclear
Executable: An intent-oriented Multi-Tx Tool	Waiting for scope	Cecilia	Unclear
Covenant - Tradeable Debt Markets Backed By Any Asset	Waiting for scope	Alan Hampton	Unclear
Strands’ Optimism Integration	Waiting for scope	Bella/Lochcres	Unclear
Bloom Metrics	Lost - no interest	(at)launamu
Contact Attempted (44 projects)	No response or follow-up yet	Multiple Contacts

Project Highlights

Silo Finance: Telegram Health Factor Bot

• Completed development of a Telegram Bot to notify users based on their health factor in Silo.

• Key features: health factor monitoring, customizable notifications, group chat integration

• Bot code available at: GitHub - bleu/silo-hf-monitor

  • It should be pretty intuitive, but you can check a user manual we wrote here.

  Silo Bot User Manual

• Dev-only live version at Telegram: Contact @silo_hf_dev_bot (Note: consider this WIP until final delivery and may be unstable at times)

• Next: Silo team will announce the dev version of the bot so we get feedback from users and then we’ll discuss next steps. Either deploying and maintaining a production version of the bot on a separate scope (since maintenance costs would be out of scope for this grant) or supporting them in launching their own production infrastructure.

Pike: Liquidation Bot Research

• Completed research on liquidation bots in Optimism vs Ethereum
• Delivered Dune Dashboard: https://dune.com/bleu/state-of-liquidations-in-optimism
• Insights on tech requirements, MEV understanding, profitability, and liquidity sources
• Next: Discuss POCA and new work proposals

Namespace: Project Kickoff

• Namespace is small team of two people enabling Digital Identities management on top of ENS.
• Gained write access to their GitHub repositories: https://github.com/thenamespace/frontend-app-v2 and https://github.com/thenamespace/namespace-backend-api
• Analyzing codebase and running code to identify improvement areas
• Next: Make sure they commit to making their code open source forever (which is a condition for any work done in the purview of this grant). Finalize focus areas and begin initial development

Candide: Account Recovery Frontend

• Candide was a grantee for OP Season 1
• Confirmed interest in building the Account Recovery Frontend
• Next: Start development with logic-related parts this week and move to frontend as our design resources free up

Next Steps

1. Continue discussions with interested projects to define specific assistance scopes
2. Proceed with active development for ongoing projects
3. Follow up with non-responsive projects one final time

You can track our progress, broken down by task and project, at our public dashboard: Metabase

As always, if you’re building on Optimism and think our services could be useful, please reach out to us on Telegram at @rpunktj, email jose@bleu.builders, or schedule a call using this link.

We’re excited about our progress and look forward to further contributing to the Optimism ecosystem!

[bleu_builders]

GM! We’re excited to provide our latest update on the “Tech Partner of OP Native Projects” grant. Here’s a summary of our recent activities and upcoming plans:

Project Status Overview

This table provides a detailed view of each project’s current status:

Project Name	Status	Point of Contact	Estimated Demand (hours)
Silo Finance (Liquidations Telegram Bot)	Launched, light usage	Ayham (AJ)	40
Pike (Liquidation Bot Pt. 1)	Waiting for code to be open-sourced	@ladderchaos	40
Namespace (Offchain Subnames Manager)	In progress (Scope finalized)	@thecap.eth	~300 (adjusted)
Candide (Account Recovery Frontend)	Started, halted (approval concerns)	@heymarcopolo	~200 (adjusted)
DarkForest ARES	Waiting for resources to free up	@fromddy	~100
aDeal network	Waiting for resources to free up	@jacoblair	200
Optimistic Crowdstaking	Waiting for scope	@OxRussel	Unclear
Executable: An intent-oriented Multi-Tx Tool	Waiting for scope	Cecilia	Unclear
Covenant - Tradeable Debt Markets Backed By Any Asset	Waiting for scope	Alan Hampton	Unclear
Strands’ Optimism Integration	Waiting for scope	Bella/Lochcres	Unclear
ETHx on OP	Lost - asked to reach out in the future	@AnoothiKumar	Unclear
Bloom Metrics	Lost - no interest	(at)launamu
Contact Attempted (44 projects)	No response or follow-up yet	Multiple Contacts

Project Highlights

Silo Finance: Telegram Health Factor Bot

• Launched the tool, and we’ve seen light usage so far.
• Next: Working with Silo’s team to increase usage and get more feedback.

Pike: Liquidation Bot Research

• Current Status: Waiting for their code to be open-sourced before continuing work under the scope of the grant.

Namespace: Offchain Subnames Manager

• We’ve honed in on the scope and will be developing the Namespace Offchain Manager app.
• Project Overview: The app enables ENS name owners to create and manage offchain subnames, resolvable via the CCIP-Read protocol.
  • see the full proposal/scope here
• Next: Begin initial development following final confirmation of focus areas.

Candide: Account Recovery Frontend

• Current Status: Work has started but is halted due to Candide’s concerns about optimistic approval and their time investment.
• Next: Awaiting resolution on approval to proceed.

Challenges with Optimistic Approvals

While we’ve been operating under an optimistic approval model to expedite our support for Optimism ecosystem projects, we’ve encountered a significant challenge that needs community attention and discussion.

Our collaboration with Candide on their Account Recovery Frontend has highlighted concerns regarding optimistic approvals. Candide, like other partners, has expressed hesitation to invest in mission-critical projects under the current model due to the risk of work stoppage.

Key points include:

• Risk of Work Stoppage: There’s a risk that work could be halted at any point if objections are raised after we’ve already started.
• Impact on Critical Infrastructure: Candide’s Account Recovery Frontend is essential to their operations, and any disruptions could delay their launch.
• Resource Investment: Partners like Candide are hesitant to invest resources without assurances that the work won’t be interrupted.
• Potential for Delays: This situation could result in partners staffing these projects internally, leading to longer timelines and missed opportunities for collaboration.

Seeking Community Input

We are seeking the community’s guidance on how to balance the benefits of optimistic approvals with the need for certainty in mission-critical projects. More generally, we would love to get your input regarding how can we work with the Grants Council to provide more assurance to partners on high-priority projects, so they feel secure delegating work to us?

Next Steps

1. Finalize the scope with Namespace and kick off development of the Offchain Subnames Manager.
2. Seek guidance from the Grants Council on how to address approval concerns and provide assurance to Candide, as we believe we can deliver substantial work and good case for proving the value from this Mission Request if this issue is resolved.

You can track our progress, broken down by task and project, at our public dashboard: Metabase

As always, if you’re building on Optimism and think our services could be useful, please reach out to us on Telegram at @rpunktj, email jose@bleu.builders, or schedule a call using this link.

We’re excited about our progress and look forward to further contributing to the Optimism ecosystem!

[marc]

Hello,

We’re interested in engaging with Bleu, but we’re currently blocked from moving forward on our side. Before proceeding, we would like to confirm if the projects mentioned above have received approval, as it’s unclear whether the Mission Council has given the go-ahead.

@Gonna.eth, could you please clarify the approval status? We want to ensure that we have the necessary confirmation before starting engagement.

Thank you

[Gonna.eth]

The Grants Council coordinates a public document with The Foundation for everyone to follow the status of applicants. You can find out if a project is approved here:

Optimism GovFund Grants: Public Delivery Tracking

For season 6 we decided to include approved projects only.

[bleu_builders]

Hey @gonna.eth, thanks for the response.

I think there might be some confusion here. The question isn’t about whether this grant has been approved, but rather about the approval process for individual projects we work with under our grant.

To clarify the background:

1. Our grant allows us to provide technical support to Optimism ecosystem projects
2. We’ve been operating under an optimistic approval model for selecting projects, as discussed in our earlier updates
3. The concern raised by Marc (Candide) is that this optimistic approval model isn’t sufficient assurance for them to proceed

They’re hesitant to delegate work on mission-critical components (like their Account Recovery Frontend) when there’s a theoretical risk of work being halted under the optimistic model.

Do you think there is a way we can provide more concrete assurance to projects like Candide while still maintaining the spirit of the optimistic approval process? This would help unblock several potential collaborations that are currently in limbo due to this uncertainty.

[bleu_builders]

Hey folks! We’re thrilled to share the latest update on our “Tech Partner for OP Native Projects” grant. Here’s a summary of our recent activities and what we have planned next:

Project Status Overview

This table provides a detailed view of each project’s current status:

Project Name	Status	Point of Contact	Estimated Demand (hours)
Silo Finance (Liquidations Telegram Bot)	Launched	Ayham (AJ)	40
Pike (Liquidation Bot Pt. 1)	In progress	@ladderchaos	40
Namespace (Offchain Subnames Manager)	In progress	@thecap.eth	~300 (adjusted)
Candide (Account Recovery Frontend)	Pending team ok	@heymarcopolo	~200 (adjusted)
DarkForest ARES	Waiting to start	@fromddy	~100
aDeal network	Waiting to start	@jacoblair	200
Optimistic Crowdstaking	Pending team ok	@OxRussel	Unclear
Executable: An intent-oriented Multi-Tx Tool	Lost - no response	Cecilia	Unclear
Covenant - Tradeable Debt Markets Backed By Any Asset	Lost	Alan Hampton	Unclear
Strands’ Optimism Integration	Pending team ok	Bella/Lochcres	Unclear
ETHx on OP	Lost - asked to reach out in the future	@AnoothiKumar	Unclear
Bloom Metrics	Lost - no interest	(at)launamu
Contact Attempted (44 projects)	No response or follow-up yet	Multiple Contacts

Project Highlights

Pike: Liquidation Bot Research

• Current Status: In the last weeks, Pike shared their smart contract with us, what allowed us to start developing the liquidation bot example. We started exploring the contracts and developing a simple liquidation call on a forked environment and creating a ponder app to track users positions.
• Next steps:
  • Create multiple positions to test the bot behavior.
  • Create the bot monitoring strategy.
  • Improve liquidation call to use flash loans.

Namespace: Offchain Subnames Manager

• Current Status: We developed a user-friendly interface that lists connected user ENS names and includes an option to set the ENS resolver to the Namespace Offchain Resolver address. Furthermore, we created a UI with CRUD operations for managing ENS offchain subnames, complete with validations and instant feedback to enhance the user experience.
• Next Steps
  • Integrate SIWE authentication.
  • Implement API keys management
  • Set up the payment flow.

Candide: Account Recovery Frontend

• Current Status: Talked to @gonna.eth about the assurances that the Candide team wanted and we’re ready to start.
• Next: Waiting on spec from the team to get officially going.

Next Steps

1. Continue development of the Pike (Liquidation Bot Research) and Namespace (Offchain Subnames Manager).
2. Update about candide as well, e.g plan development of the Candide project

You can track our progress, broken down by task and project, at our public dashboard: Metabase

As always, if you’re building on Optimism and think our services could be useful, please reach out to us on Telegram at @rpunktj, email jose@bleu.builders, or schedule a call using this link.

We’re excited about our progress and look forward to further contributing to the Optimism ecosystem!

[0xR]

Hi @Gonna.eth,

cc: @bleu_builders

I’m the grant lead for the Optimistic Crowdstaking project.

We were approved in Season 5 for this grant by the Optimism Grant Council , and have been completing our first milestones successfully. After the first research phase, we made some changes to improve the product—a yield-bearing stablecoin directed toward approved Optimism builder grantees through grant approval attestations found on Charmverse. Once we were introduced to Bleu Studios’ services, we discussed delegating some of the front-end work to them. Here’s why:

• Our developers have been fully focused on building the smart contract and back-end architecture, leaving limited bandwidth/hours for the front end.
• Strategic resource utilization: By bringing in Bleu Studios, we’re ensuring that our milestones are met on schedule without overstretching our team or delaying delivery.
• We’ve also been dealing with issues related to undocumented attestations on Optimism, which has taken up more of our time and are in discussions with @optimistic_emily for clarity and a solution to resolve this.

We wanted to let you know that we’re considering engaging Bleu Studios to handle the front-end work, as their support would be invaluable in helping us deliver a high-quality solution. Before moving forward, we’d like to confirm that their involvement won’t lead to any future complications or grant clawbacks for either party.

Looking forward to hearing from you!

[bleu_builders]

Hey folks! Here’s a summary of our recent activities and next steps:

Project Status Overview

This table provides a detailed view of each project’s current status:

Project Name	Status	Point of Contact	Estimated Demand (hours)
Silo Finance (Liquidations Telegram Bot)	Launched	Ayham (AJ)	40
Pike (Liquidation Bot Pt. 1)	In progress	@ladderchaos	~200 (adjusted)
Namespace (Offchain Subnames Manager)	In progress	@thecap.eth	~300 (adjusted)
Candide (Account Recovery Frontend)	Waiting to start	@heymarcopolo	~100 (adjusted)
DarkForest ARES	Waiting to start	@fromddy	~100
aDeal network	Waiting to start	@jacoblair	200
Optimistic Crowdstaking	Waiting to start	@OxRussel	~300
Executable: An intent-oriented Multi-Tx Tool	Lost - no response	Cecilia	Unclear
Covenant - Tradeable Debt Markets Backed By Any Asset	Lost - no answer	Alan Hampton	Unclear
Strands’ Optimism Integration	Lost - no answer	Bella/Lochcres	Unclear
ETHx on OP	Lost - asked to reach out in the future	@AnoothiKumar	Unclear
Bloom Metrics	Lost - no interest	(at)launamu
obUSD Frontend	Lost - no interest	@0xR	Unclear
Pike User Interface	Waiting proposal (bleu)	@ladderchaos	To be defined
Contact Attempted (44 projects)	No response or follow-up yet	Multiple Contacts

Project Highlights

Pike: Liquidation Bot

• Current Status: In the last weeks, we finished the first version of the liquidation bot, which is enabled to monitor and liquidate unhealthy positions. We shared developed work with Pike and they sent improvement points to be worked on in the next few days. The demo can be accessed on these links:
  • 1 - Intro and Agenda
  • 2- Context and mocked data
  • 3- Bot helper contract and API for consulting positions
  • 4- Bot high-level workflow
  • 5- Liquidation example
• Next steps:
  • Decrease RPC calls dependency by off-chain liquidation allowance calculations.
  • Add a minProfitUsdValue to allow setting parameters to determine how profitable a liquidation needs to be.
  • Ability to liquidate non-profit positions.
  • Consume off-chain data to decrease the time to reply to the bot.
  • Write tech documentation of the project on the repo readme.

Pike: SDK/Indexer/UI

• Current Status: Pike reached out to ask for a follow-up project. They’re heads down in Smart Contracts work and would prefer to outsource a community version for the protocol UI and reached out to us to check whether we’d be available to deliver that. This is a potentially larger project than we have scope in hours, but we’ll scope the project and present a proposal for Pike.
• Next steps:
  • Check the project viability since it must be done by the end of 2025 Q1.
  • Scope the project and present a proposal for Pike by end of this week.

Namespace: Offchain Subnames Manager

• Current Status: Since the last update we developed the authentication of the backend for all the necessary endpoints using SIWE and implemented the API key management using CRUD standard. These features were also presented to the Namespace team that provided feedback. Namespace also reached for us to work in follow up projects but this is still in discussion and we haven’t committed any resources for those.
• Next Steps
  • Set up the payment flow and get final feedback from their team by end of December.

Candide: Account Recovery Frontend

• Current Status: The Candide team sent us the project specs on this document. We’re currently checking viability and planning the project. We should start this grant as soon as the other ongoing projects are finished. It should be a small one, taking 2-3 weeks at most.
• Next Steps
  • Give feedback the Candide team about their proposal
  • [tentative] kick off the project in late December / early January

obUSD: Optimistic Crowdstaking Frontend (Awaiting Grants Council feedback on scope overlap)

• Current Status: We’ve been talking to the obUSD team (working on the Optimistic Crowdstaking grant) for some months and have assisted them during the research phase of their grant. They approached us requesting front-end development support for their product, with designs to be handled by them.
• However, we observed their approved grant proposal also contained some frontend work. To avoid any issues with either grant and have clarity about our involvement, we asked the team to seek feedback from the Grants Council about how to operate here since it’s a bit of a gray area in our own grant. (Thanks @0xR for sending the message above!)
• To overcommunicate: we’re considering this situation falls under our previous agreement of optimistically approving projects and are ready to should there not be any negative feedback from the community.
• Next:
  • Send the team a work proposal.
  • [tentative] kick off the project in early/mid January.

Next Steps

1. Finish the development of the Pike (Liquidation Bot Research) and Namespace (Offchain Subnames Manager).
2. Present a proposal for the Pike User Interface project.
3. Start the development of new projects (obUSD, Candide, or Pike UI).

You can track our progress, broken down by task and project, at our public dashboard: Metabase

As always, if you’re building on Optimism and think our services could be useful, please reach out to us on Telegram at @rpunktj, email jose@bleu.builders, or schedule a call using this link.

We’re excited about our progress and look forward to further contributing to the Optimism ecosystem!

[Jrocki]

Appreciate the continued updates here. Love that you are building in public and personally for me, it is nice to see what your grant has funded in the ecosystem