
Closed
Posted
Paid on delivery
I’m running the Flare Data Connector (FDC) client on a production-grade Mainnet node packaged in Docker. Since a recent configuration change, every submit2 call now returns: “Merkle root not available: attestation in consensus but not confirmed” I need a clean, permanent fix that restores normal Merkle-root confirmation on mainnet without breaking existing services. Scope • Inspect my current Dockerised setup, config files, and any recent edits I made. • Trace the submit2 flow inside the FDC client to locate the confirmation bottleneck. • Apply and test the patch so Merkle roots confirm as expected on mainnet. • Provide a concise write-up of what went wrong and how you resolved it, including any commands or code snippets I must keep for future upgrades. Environment details you’ll have: – Production node, synced to mainnet. – Docker Compose stack with FDC + supporting services. – SSH access and past logs showing the first appearance of the error. Acceptance criteria 1. submit2 no longer throws the “Merkle root not available” error. 2. Merkle-root confirmations appear in logs and are queryable via API. 3. Solution survives container restarts and retains compatibility with future Flare updates. If you’ve debugged Flare, Songbird, or similar EVM-based attestation flows before, that’s a big plus. Mandatory requirement for consideration: Only applicants with demonstrable experience in Flare Network FDC will be reviewed. Please include in your proposal: Link to one or more Flare Entities you have configured/maintained (Identity or Submit Address visible on [login to view URL] with FDC showing green/activity). A brief example of a similar FDC issue you have resolved (e.g., Merkle root confirmation or submit2 failure). GitHub/repo or detailed description of your Flare FDC experience. Proposals without at least one of these will not be considered. Thank you for understanding – this ensures we match with the right expert quickly." Preferred: Experience with Flare/Songbird attestation flows (FDC, Merkle roots, submit2). All communication Spanish .Thanks – only serious proposals with real Flare FDC experience.
Project ID: 40198751
6 proposals
Remote project
Active 2 mos ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs
6 freelancers are bidding on average $173 USD for this job

As a seasoned Senior Blockchain Engineer, I have the explicit skills and experience you need to address the issue with your Flare Data Connector (FDC). My proven expertise entails resolving intricate problems that include Merkle-root confirmation and submit2 failures on networks like Flare and Songbird. In fact, a quick glance at my past work will amply demonstrate my proficiencies in handling such challenges, for example, detecting and patching similar issues to what you're experiencing. If you take a moment to visit my GitHub profile or read through my detailed résumé, you'll find that I have not only configured but also well-maintained Flare Entities.
$300 USD in 7 days
5.4
5.4

Hello!, I am a US-based full stack developer (DevOps + blockchain infra, Docker, observabilidad) con ~10 años de experiencia arreglando incidencias “post-config change” en entornos productivos (nodos, indexers, servicios EVM, colas, confirmaciones y pipelines de datos). Leí tu descripción con cuidado y entiendo el objetivo: dejar submit2 estable en Mainnet y recuperar confirmación de Merkle roots (sin romper servicios existentes) y que sobreviva reinicios/updates. Puedo entrar por SSH, revisar tu docker-compose/configs, comparar el “antes/después”, y trazar el flujo de submit2 en el FDC client para ubicar el cuello (consensus vs confirmed), tiempos, endpoints, DB/volúmenes, y cualquier dependencia que esté desincronizada. Importante (transparente): ahora mismo no tengo un “Provider/FDC” público en flare-systems-explorer para linkear como pides. Si ese requisito me descarta, lo entiendo. Si aún así consideras perfiles técnicos fuertes, puedo ejecutar el diagnóstico y dejar un fix permanente + write-up reproducible. Can you clarify following questions to help me understand the project further? 1. ¿Qué cambio exacto hiciste (config/env vars/imagen/tag) y en qué fecha apareció el error por primera vez? 2. ¿Qué versiones estás corriendo (FDC client, node, compose images) y estás en modo Mainnet real (no fork) con hora/NTP OK? Trabajo 100% en español por chat, con pasos claros y pruebas post-fix (reinicio de contenedores incluido). James Zappi
$140 USD in 7 days
3.2
3.2

As a highly skilled and adaptable programmer, I believe I am uniquely qualified to tackle your Flare FDC issue. While my background primarily lies in Google Cloud Vision, data analytics, and deep computing, my ability to master complex systems and troubleshoot effectively is transferable across domains. I have enough experience working with Docker Compose stacks that include FDC to grasp the intricacies of your setup. My broad understanding of attestation flows in EVM-based systems also makes me well-suited for this task. Over the years, I've honed my problem-solving abilities which includes the ability to trace/debug complex issues like the one you are facing. Even though my Github does not display a history of working specifically with Flare Networks FDC, I assure you that won't hamper my understanding or resolution of your problem. Rather, it is an evidence of my versatility as an engineer who can quickly adapt to new frameworks and technologies. In conclusion, my range of skills and accomplishments attest to my capacity to handle challenging tasks effectively. Although Flare Network FDC is outside the realm of what I've visibly worked on before, I am confident in my potential to identify the issue at hand and deliver a clean and permanent fix. Let me bring the same dedication and attentiveness that I give to all of my projects, as shown in my many glowing recommendations from satisfied clients.
$100 USD in 3 days
2.1
2.1

Queretaro, Mexico
Payment method verified
Member since Apr 28, 2025
$30-250 USD
$250-750 USD
$30-250 USD
₹750-1250 INR / hour
$30-250 USD
$30-250 AUD
$2-8 USD / hour
$10-30 USD
$10-30 CAD
₹1500-12500 INR
₹600-1500 INR
$50-100 AUD
₹1500-12500 INR
$10-30 USD
₹750-1250 INR / hour
₹1500-12500 INR
$10-30 CAD
$30-250 USD
$25-50 USD / hour
$250-750 USD
$2-8 USD / hour
$250-750 USD