Este enfoque centrado en el individuo ha impulsado la mayoría del desarrollo del ecosistema, abstrayendo la complejidad de Ethereum en wallets para navegador y dispositivos móviles. Aunque este enfoque funciona bien para usuarios individuales, pasa por alto una oportunidad crítica: entidades u organizaciones que coordinan a múltiples personas hacia objetivos colectivos.

Esto crea una oportunidad. Las herramientas diseñadas para la coordinación colectiva representan un solo punto de acceso con un impacto multiplicador en el ecosistema: los millones de startups y micro, pequeñas y medianas empresas (MIPYMES) que ya existen, generan empleos y gestionan recursos económicos reales.

Si logramos que Ethereum sea un entorno accesible y sin barreras para estas organizaciones, podemos acelerar la incorporación tanto de usuarios colectivos como individuales al mismo tiempo. Cada startup o MIPYME que se constituye, incorpora a sus fundadores, equipos, clientes y socios. Esta es la motivación detrás de este artículo y del trabajo que hemos realizado como parte del Programa Devconnect Scholars y en Zenbit.

En este artículo exploramos:

1. El contexto de las startups y las MIPYMES y por qué son un segmento natural de “mayoría temprana” para Ethereum.

2. MicroDAOs como un patrón de “DAO mínimamente viable” que combina cinco componentes fundamentales de Ethereum: ENS, Safe, DeFi, EAS y un token empresarial, con ejemplos reales como Axolotarium y AxoloDAO.

3. Startupchain, un producto integrado que reduce la complejidad UX, conjuntando todos estos componentes en un único producto, desde el prototipo construido en ETH New York hasta su PRD.

1. Contexto

1a. ¿Qué son las startups y las MIPYMES?

A nivel mundial, las startups y las MIPYMES representan la mayoría de las empresas, así como una proporción significativa del empleo y del PIB. Incluso en contextos de informalidad, son el vehículo principal para que fundadores y emprendedores aprovechen oportunidades económicas. Alrededor del 99% de las empresas del mundo son startups o MIPYMES, sumando más de 391 millones de negocios. Más de la mitad se encuentran en Asia (51%), seguidas de África (23%), Europa (10%), Norteamérica (10%), Sudamérica (5%) y Oceanía (1%).

Esta distribución no solo muestra lo enorme que es el segmento MIPYME, sino también su gran diversidad geográfica. Cualquier estrategia para llevar la economía onchain tiene que dirigirse a este 99% y funcionar en regiones muy distintas, con niveles de infraestructura y realidades regulatorias muy diferentes.

Cada uno de estos tipos de organización ofrece características distintas que se ajustan a diferentes contextos mundiales. Quienes pueden aprovechar nuevas tecnologías o modelos de negocio pueden optar por crear startups enfocadas en un crecimiento rápido y en la escalabilidad a largo plazo, aceptando mayor riesgo mientras innovan con tecnologías emergentes. Las pequeñas empresas, en cambio, se apoyan en modelos probados que les permiten operaciones estables y una rentabilidad más predecible.

Aunque existen diferencias notables entre startups y pequeños negocios —por ejemplo, sus objetivos, tolerancia al riesgo y horizontes de tiempo—, ambos perfiles pueden beneficiarse de herramientas onchain para:

• Establecer confianza y coordinación entre cofundadores.

• Administrar tesorerías compartidas y flujos de caja de manera transparente.

• Formalizar relaciones con colaboradores, inversionistas y partes interesadas (stakeholders).

• Registrar propiedad intelectual, contribuciones y logros de manera verificable.

Todo esto los hace candidatos ideales para la coordinación onchain, especialmente en regiones donde la infraestructura financiera y legal tradicional es lenta, opaca o excluyente.

1b. Impacto económico real e informalidad de startups y MIPYMES

Dado que las startups y MIPYMES ya generan un impacto económico considerable, incorporarlas no es cuestión de especulación; son la columna vertebral del empleo y la producción en cada región del mundo. Su impacto en el empleo es abrumador: en África, las startups y MIPYMES generan alrededor del 84% del empleo; en Sudamérica y Europa, cerca del 70%; en Oceanía, 70%; en Asia, 64%; y en Norteamérica, 59%. En otras palabras, la mayoría de las personas que trabajan en la economía formal lo hacen en organizaciones que se parecen mucho más a una pequeña empresa o a una startup que a una corporación multinacional.

Al mismo tiempo, una proporción importante de estas startups y MIPYMES opera en la economía informal, lo que limita su acceso al crédito, a herramientas digitales y a la planificación de largo plazo. Aproximadamente 38% de las startups y MIPYMES en África, 35% en Sudamérica y 22% en Asia son informales, frente a 16% en Norteamérica, 15% en Europa y 11% en Oceanía. Esto significa que algunas regiones con mayor creación de empleo por estas empresas son también las menos integradas en sistemas financieros y legales formales.

En muchos países, especialmente del Sur Global, esta informalidad se refleja en situaciones como:

• Sin entidad legal clara o acta constitutiva.

• Falta de tabla de capitalización estructurada, esquemas de vesting ni registros de propiedad.

• Ausencia de acuerdos formales con colaboradores.

• Contabilidad en efectivo con pocas o ninguna auditoría

Dada esta paradoja — son fundamentales para el empleo pero operan mayormente al margen de los sistemas formales — incorporar startups y MIPYMES a Ethereum no es solo una mejora de eficiencia, sino una manera de:

• Canalizar ingresos reales (pagos, facturas, suscripciones) a través de infraestructura flexible y automatizable.

• Respaldar empleo real (nóminas, pagos a contratistas) con tesorerías transparentes y flujos auditables.

• Proteger y monetizar activos reales e intangibles (licencias, patentes, contenidos, datos científicos) con registros verificables.

• Habilitar resultados comunitarios reales (educación, conservación, desarrollo local) haciendo que el financiamiento y la toma de decisiones sean transparentes y verificables.

Si Ethereum quiere convertirse en una infraestructura financiera global confiable, debe soportar estas operaciones empresariales “cotidianas y aburridas”, especialmente en regiones con alta informalidad y empleo por startups y MIPYMES, mostrando cuán frágiles son los sistemas financieros y de coordinación actuales.

1c. Startups y MIPYMES como “mayoría temprana” del mercado masivo

La adopción tecnológica rara vez ocurre de golpe. Sigue una curva donde distintos segmentos de usuarios se incorporan en momentos diferentes, cada uno con sus necesidades y expectativas.

En el lado izquierdo de la curva encontramos a los innovadores (entusiastas tecnológicos, ~2.5%), que adoptan nuevas herramientas simplemente porque son nuevas y están dispuestos a tolerar errores y falta de funcionalidades. Posteriormente siguen los early adopters (adoptadores tempranos, ~13.5%), que buscan una ventaja estratégica y experimentan si la ganancia potencial es significativa.

Estos dos grupos forman el “mercado temprano”. Gran parte de la primera década de Ethereum ha estado dominada por ellos: investigadores de protocolos, “entusiastas DeFi”, coleccionistas de NFTs, equipos nativos de DAOs; personas que se sienten cómodas manejando frases de recuperación (seed phrases), firmando transacciones a nivel de protocolo y desarrollando protocolos como si fueran piezas de Lego.

Entre este mercado temprano y el resto de la sociedad está lo que Geoffrey Moore llama “el abismo”: una brecha estructural entre lo que los adoptadores tempranos **toleran y lo que el mercado masivo demanda (Crossing the Chasm: Marketing and Selling High-Tech Products to Mainstream Customers, 1991). Al otro lado del abismo se encuentran la mayoría temprana (pragmáticos, ~34%) y la mayoría tardía (conservadores, ~34%), seguidos por los rezagados (escépticos, ~16%). A los pragmáticos no les importa que una tecnología sea nueva; les importa que funcione de forma confiable, encaje en sus flujos de trabajo existentes y mejore claramente el costo, la velocidad o el riesgo. Los conservadores y escépticos son aún más exigentes: esperan productos maduros, estándares claros y soporte.

En general, si una tecnología no evoluciona para satisfacer las necesidades del siguiente segmento, no logra cruzar el abismo y permanece como una herramienta de nicho. Pero si se adapta —mejorando la UX, ocultando la complejidad y resolviendo problemas específicos y visibles— puede cruzar esta brecha y acceder a un mercado mucho más amplio.

En el contexto de Ethereum, esto implica reconocer que:

• Los “entusiastas DeFi”, coleccionistas de NFTs y equipos de protocolos corresponden a los innovadores y adoptadores tempranos en el lado izquierdo de la curva. Se sienten cómodos usando múltiples wallets, interfaces y protocolos para desarrollar sus propias soluciones.

• Las startups y MIPYMES corresponden a la mayoría temprana de pragmáticos que adoptarán Ethereum no por novedad, sino porque resuelve problemas operativos concretos—administración de tesorería, gobernanza, cumplimiento y financiamiento— de manera más barata, rápida o transparente que el status quo*.*

Para este segmento, las principales propuestas de valor son:

• Eficiencia de costos: usar Ethereum como plataforma operativa de bajo costo para tesorería, gobernanza y registros, en lugar de combinar SaaS personalizado con hojas de cálculo fragmentadas.

• Interoperabilidad: integración nativa en la economía global onchain —stablecoins, crédito DeFi, subvenciones, financiamiento cuadrático, mercados onchain.

• Capacidad de integración: conectarse con otras herramientas (KYC, nómina, seguros, analítica) mediante estándares compartidos, no integraciones personalizadas.

Los componentes fundamentales de Ethereum pueden ayudar cruzar este abismo: tomar herramientas originalmente diseñadas para usuarios individuales y técnicos (wallets, protocolos DeFi, ENS, EAS, tokens) y ensamblarlas en flujos de trabajo estructurados que funcionen para organizaciones. Al integrar estos componentes básicos en procesos de incorporación guiados, estructuras de gobernanza compartida (Safe) y registros verificables (EAS), transformamos a Ethereum de un espacio experimental para entusiastas en una plataforma operativa confiable para startups y MIPYMES: el segmento de mayoría temprana que puede impulsar al ecosistema hacia la adopción masiva.

2. MicroDAOs

Definimos a una MicroDAO como una DAO mínimamente viable: el conjunto mínimo de componentes onchain que una startup, MIPYME o equipo de proyecto necesita para operar de manera transparente, programable e interoperable, evitando las complejidades de gobernanza innecesarias que caracterizan a muchas DAOs.

La MicroDAO mínima utiliza tres componentes fundamentales de Ethereum (ENS, Safe, EAS), que pueden ampliarse con integraciones DeFi y un token empresarial, a medida que la organización madure y sus necesidades operativas crezcan.

En nuestro trabajo en Zenbit, intencionalmente reducimos este stack, a tres componentes fundamentales de Ethereum:

1. ENS (Ethereum Name Service): Identidad y un sistema de subdominios (namespace) para el colectivo y sus miembros.

2. Safe (multichain): Una cuenta inteligente compartida para tesorería y ejecución, con la misma dirección en múltiples redes.

3. EAS (Ethereum Attestation Service): Un sistema de registro verificable para documentar roles, hitos y resultados.

Este stack mínimo es suficiente para proporcionar a un equipo en etapa temprana:

• Un nombre e identidad direccionable onchain.

• Una cuenta compartida para mantener fondos y ejecutar decisiones.

• Una memoria pública de lo que se ha hecho, por quién y cuándo.

Para fundadores de startups y MIPYMES, esta estructura mínima ofrece certeza sobre quién posee qué, visibilidad de los movimientos de dinero y un registro verificable de actividades, todo implementado con herramientas abiertas sin necesidad de complejos procesos legales ni corporativos.

2a. DAO mínimamente viable: ENS + Safe (multichain) + EAS

A mayor detalle, un MicroDAO combina:

ENS – identidad y sistema de subdominios

• Un nombre comprensible para la organización (por ejemplo, miempresa.eth) en lugar de direcciones hexadecimales.

• Un sistema de subdominios (por ejemplo, alice.miempresa.eth, safe.miempresa.eth) para distinguir roles, cuentas de tesorería y organizaciones asociadas.

• Una identidad que wallets, exploradores y aplicaciones pueden identificar automáticamente, lo cual es crucial cuando una MIPYME comienza a interactuar con clientes, financiadores u otras DAOs.

Safe (multichain) – Tesorería compartida y ejecución

• Un Safe multichain que gestiona los fondos (stablecoins, tokens nativos y, más adelante, un token empresarial si hace falta).

• Control multi-firmas (por ejemplo, 2 de 3 fundadores), de manera que ninguna persona pueda vaciar los fondos por sí sola.

• La misma dirección de Safe en todas las redes soportadas, lo que simplifica el modelo mental y permite al equipo elegir las L2 más convenientes para sus operaciones.

En la práctica, Safe funciona como la combinación de cuenta bancaria conjunta + sistema de aprobación del consejo de administración de la MicroDAO.

EAS– Registro verificable del historial

• Formatos estandarizados que definen qué tipo de eventos se certifican (por ejemplo “DAO formada”, “objetivo operativo definido”, “hito de financiamiento alcanzado”).

• Certificaciones emitidas por mentores, coordinadores o la misma DAO para registrar eventos, contribuciones y logros.

• Un registro público y auditable que después pueden reutilizar programas de financiamiento, incubadoras o incluso reguladores como evidencia de actividad.

En lugar de PDFs dispersos, hojas de cálculo y chats privados, una MicroDAO tiene un inventario compartido de decisiones y actividades, portátil entre herramientas y jurisdicciones.

Para fundadores de startups y MIPYMES, esta estructura mínima ofrece una forma de formalizar su organización sin perder flexibilidad y de moverse, poco a poco, de la informalidad total hacia operaciones verificables y auditables.

2b. El programa de incubación de microDAOs de Zenbit

Para hacer este patrón accesible a equipos no nativos de cripto, Zenbit diseñó un programa de incubación de microDAOs que guía a los proyectos a través de seis etapas:

1. Creación de la MicroDAO

   Integración de un Safe multichain con un nombre ENS como versión mínimamente viable de una MicroDAO. El equipo define firmantes, elige redes y conecta la identidad onchain (dao-nombre.eth) a la cuenta compartida.

2. Presentación de la DAO

   Introducción pública formal de la iniciativa —a menudo a través de un artículo en Mirror o presentación pública— que explica su misión, stakeholders (actores clave) y por qué opera como MicroDAO. Este suele ser el primer momento en que el proyecto aparece como actor colectivo onchain, no solo como una wallet personal.

3. Objetivo operativo

   Definición de una meta concreta y medible que justifica la existencia de la MicroDAO (por ejemplo, “operar un biomuseo”, “lanzar un MVP”, “ejecutar un piloto con 10 clientes”) y vincula actividades cotidianas con resultados esperados. Esto crea un ancla para certificaciones posteriores.

4. Gestión de tesorería

   Diseño de un modelo financiero básico usando el Safe: quién puede gastar, bajo qué reglas, y cómo se categoriza el ingreso (donaciones, grants, ventas). DeFi puede añadirse después, pero el enfoque en esta fase es la transparencia y trazabilidad de los flujos.

5. Implementación onchain

   Registro de las acciones clave del proyecto como certificaciones EAS y transacciones onchain: formación, objetivos, eventos, pagos y metas. La idea es que un observador externo pueda reconstruir lo que la MicroDAO realmente ha hecho, sin necesitar acceso interno.

6. Financiamiento onchain

   Uso de mecanismos onchain —grants, donaciones, crowdfunding o canales de ingresos— para traer capital al Safe. En este punto la MicroDAO no es solo una estructura; se convierte en un vehículo listo para recibir financiamiento, con historial verificable y gobernanza.

Este programa de seis fases está diseñado para ser portátil: puede usarse con proyectos científicos como Axolotarium, pero también para startups y MIPYMES en etapa temprana que necesitan una forma ligera de estructurar propiedad, operaciones y financiamiento sin incorporar una empresa completa desde el día uno.

2c. Zenbit Badges: seguimiento del progreso onchain

Para hacer este proceso de incubación transparente y auditable, Zenbit desarrolló Zenbit Badges [GitHub] —una dapp de identidad onchain que automatiza certificaciones EAS desde una cuenta dedicada (por ejemplo, badges.zenbit.eth). La dapp mantiene un registro de eventos, mentores y participantes, y emite certificaciones automáticamente cuando se cumplen ciertas condiciones.

Zenbit Badges:

• Expone diferentes interfaces por rol (mentores vs participantes) y estructura el aprendizaje y las tareas como “eventos” y “cuestionarios”.

• Utiliza un contrato Solidity (EASOnboarding) para registrar actividad y emitir certificaciones en la red principal de Optimism.

• Define un catálogo de certificaciones y tipos de cuestionarios, incluyendo verificación de membresía en Safe vía ENS y validación de autoría de artículos en Mirror.

Para el piloto de incubación de DAOs, Zenbit creó una serie de ocho badges que rastrean aproximadamente la evolución de un proyecto desde cero hasta una MicroDAO completamente operativa: Introducción a Web3, formación de DAO, presentación de DAO, objetivo operativo, construcción de comunidad, financiamiento descentralizado, artículo académico y desarrollo tecnológico.

Estos ocho badges se mapean con las seis fases de incubación, con algunos hitos otorgando múltiples badges para reconocer logros distintos.

Desde la perspectiva de startups y MIPYMES, Zenbit Badges actúa como:

• Un rastreador de progreso que muestra qué tan avanzado está cada equipo en el recorrido de incubación.

• Una capa de reputación que futuros donantes, socios o aceleradoras pueden consultar.

• Un mecanismo de reporteo estandarizado que reduce la necesidad de formatos de reporte personalizados entre distintos programas.

2d. Axolotarium: una MicroDAO científica en la práctica

Axolotarium es un centro especializado para la conservación, reproducción e investigación científica de ajolotes mexicanos, mientras que Zenbit se enfoca en tecnologías onchain y gobernanza descentralizada. Su colaboración comenzó a mediados de 2024 como parte del programa piloto de incubación, con el objetivo de transformar a Axolotarium en una MicroDAO capaz de coordinar trabajo de conservación, investigación y financiamiento a través de Ethereum. Para una visión detallada de esta colaboración, consulta nuestro informe completo.

En la práctica, Axolotarium:

• Publicó su primer artículo en Mirror, “Axolotarium: Axolotls, science and blockchain”, como meta de presentación de la DAO, explicando su misión y alianzas.

• Completó las primeras metas del programa de incubación y recibió Zenbit Badges por:

  • Introducción a herramientas Web3,

  • Creación formal de su MicroDAO (Safe + ENS), y

  • Presentación pública vía Mirror.

• Adoptó un Safe multichain vinculado a axolotarium.eth como tesorería compartida, experimentando con flujos de financiamiento onchain para el biomuseo y actividades de investigación.

A través de este proceso, Axolotarium fortaleció su estructura organizativa, alfabetización digital y modelo de sostenibilidad, pasando de un grupo de investigación informal a un proyecto con identidad onchain verificable, tesorería transparente y una hoja de ruta para el financiamiento descentralizado.

Para la narrativa más amplia de este artículo, Axolotarium muestra que las MicroDAOs no se limitan a startups nativas de cripto: pueden estructurar instituciones del mundo real —laboratorios, centros de conservación, pequeñas ONG— con las mismas herramientas que usaría una startup tecnológica.

2e. AxoloDAO: de una coordinación centrada en Safe a una centrada en ENS

Conforme avanzaba el piloto con Axolotarium, varias limitaciones del diseño inicial centrado en Safe se hicieron evidentes:

• El dominio principal ENS axolotarium.eth apuntaba directamente a un Safe multichain.

• Acciones administrativas en algunas dapps (por ejemplo, publicar en Mirror) requerían una EOA (cuenta de propiedad externa), por lo que un subdominio adicional (info.axolotarium.eth) se ligó a una wallet personal de administración.

• Otros miembros no tenían subdominios propios, lo que hacía difícil distinguir claramente acciones personales vs. institucionales.

• Cambios en los firmantes del Safe entre múltiples cadenas podían generar desajustes o requerir coordinación repetida.

• Concentrar el poder administrativo y las llaves privadas en una sola creaba riesgos de seguridad y gobernanza.

Estos problemas no eran exclusivos de Axolotarium: reflejan lo que muchas startups y MIPYMES enfrentan cuando intentan “simplemente usar un multisig” sin pensar en la identidad y separación de roles.

AxoloDAO se diseñó como una iteración sobre esta experiencia, cambiando de un enfoque centrado en Safe a un enfoque centrado en ENS:

• El dominio principal axolodao.eth es utilizado como identidad administrativa compartida, cuyas llaves y políticas de acceso son gobernadas explícitamente por el colectivo.

• Un subdominio dedicado como safe.axolodao.eth apunta al Safe multichain, haciendo de la tesorería un componente claramente etiquetado en lugar de la única identidad.

• Miembros institucionales clave reciben sus propios subdominios (ndali.axolodao.eth, xolotlcalli.axolodao.eth, zenbit.axolodao.eth, etc.), que pueden vincularse a sus wallets o Safes para operaciones basadas en roles.

• Certificaciones EAS codifican estándares de datos, actividades de investigación y métricas de conservación, convirtiendo a AxoloDAO en una capa de infraestructura pública digital en lugar de un solo proyecto.

Aprende más sobre la misión de AxoloDAO para revolucionar la conservación de Ambystoma en México

Más allá de la rearquitectura ENS/Safe, AxoloDAO aborda el problema más profundo descubierto durante el piloto con Axolotarium: asimetría de información en conservación de biodiversidad. Usa infraestructura onchain para:

• Estandarizar la captura y el reporte de datos entre laboratorios y proyectos de campo.

• Proporcionar registros verificables y auditables de genética, reproducción y actividades de monitoreo.

• Crear repositorios abiertos y mecanismos de gobernanza interoperables que conecten iniciativas locales con estrategias a nivel nacional.

En otras palabras, AxoloDAO convierte un conjunto de esfuerzos aislados en un sistema coordinado de información y decisión, con MicroDAOs como su unidad básica.

2f. De pilotos científicos a MicroDAOs de startups y MIPYMES

Los pilotos de Axolotarium y AxoloDAO pueden parecer lejanos al mundo de las startups SaaS o de las MIPYMES locales, pero el patrón subyacente es el mismo:

• Un grupo pequeño con una misión (conservación, desarrollo de producto, servicios locales).

• Operando en un contexto de informalidad, registros fragmentados e incertidumbre en el financiamiento.

• Necesitando una forma de formalizar lo necesario para acceder a recursos, demostrar impacto y coordinar múltiples stakeholders.

El patrón MicroDAO —ENS + Safe multichain + EAS, guiado por el modelo de incubación en seis fases y seguido con Zenbit Badges— ofrece precisamente eso: un sistema operativo ligero pero robusto para organizaciones en etapa temprana.

Para startups y MIPYMES, esto significa que pueden:

• Obtener una identidad onchain y una tesorería compartida en días, no meses.

• Construir un historial verificable de objetivos alcanzados, clientes y disciplina financiera desde el principio.

• Conectarse a mecanismos de financiamiento, incubadoras y ecosistemas que reconocen certificaciones de MicroDAO como evidencia creíble.

En la práctica, usar MicroDAOs representa una reducción del 95–99% tanto en costo como en tiempo en comparación con la constitución tradicional y apertura de cuenta bancaria, especialmente en regiones donde la infraestructura legal y financiera es lenta o excluyente. Lo que podría tomar de 3 a 6 meses y entre 2,000 y 10,000 USD mediante canales tradicionales, puede lograrse en 2 o 3 días por menos de 100 USD en tarifas de transacción.

En la siguiente sección exploraremos cómo llevar este patrón un paso más allá al integrar estas herramientas en una UX única, para que los fundadores no necesiten ser expertos en protocolos para empezar a operar como MicroDAOs.

3. Startupchain: integración de MicroDAOs en servicios de empresa onchain

La sección anterior describió a las MicroDAOs como una DAO mínimamente viable para startups y MIPYMES: ENS para identidad, un Safe multichain para tesorería compartida y EAS para historial verificable. Para muchos equipos, esto ya representa un salto enorme desde la informalidad total. Pero para realmente para servir a startups y MIPYMES como la mayoría temprana de la base de usuarios de Ethereum, también necesitamos facilitar la incorporación de:

• Funcionalidades de DeFi para ahorros y crédito (protocolos de yield/ rendimientos y préstamos).

• Un token empresarial que actúe como instrumento para stakeholders y mecanismo de Sistema de incentivos interno (tokens de participación, recompensas a contribuidores, reparto de ingresos).

Startupchain es nuestro intento de empaquetar todo esto en un único producto coherente: una aplicación descentralizada que ofrece Servicios de Empresa Onchain (OCS, por sus siglas en inglés) para establecer y administrar startups y pequeños negocios.

En lugar de esperar que los fundadores agrupen manualmente ENS, Safe, DeFi, EAS y contratos de tokens a través de múltiples dapps, Startupchain busca proporcionar un solo punto de acceso para crear y operar una empresa onchain.

3a. De una UX fragmentada a una empresa onchain integrada

Hoy, establecer una MicroDAO —o cualquier empresa onchain— todavía es un proceso fragmentado y complejo:

1. Registrar un nombre ENS en una interfaz.

2. Crear un Safe multichain en otra.

3. Enviar fondos manualmente a protocolos DeFi para obtener rendimiento o acceder a crédito.

4. Usar una UI distinta para definir formatos EAS y emitir certificaciones.

5. Desplegar un token empresarial a través de otra herramienta o contrato personalizado.

6. Llevar registro de todo esto en documentos privados y hojas de cálculo.

Para los innovadores y adoptadores tempranos descritos en la Sección 1c, esta complejidad es aceptable. Para los fundadores pragmáticos de la mayoría temprana que dirigen startups y PyMEs —ya sobrecargados con gestión de nómina, cumplimiento regulatorio y desarrollo de producto— simplemente es demasiado.

Por lo que, el objetivo central de Startupchain es simplificar y agilizar este recorrido en un flujo guiado y estructurado que refleje el diseño MicroDAO:

1. Identidad: elegir y registrar el dominio ENS de la empresa y sus subdominios.

2. Tesorería: crear y configurar el Safe multichain como cuenta compartida.

3. Historial: configurar formatos EAS y emitir las primeras certificaciones (constitución, fundadores, depósitos iniciales).

4. Integraciones financieras: conectar la tesorería con opciones DeFi para ahorro (yield) y crédito (préstamos).

5. Sistemas de incentivos interno: Opcionalmente, establecer un token empresarial que represente reclamaciones de los stakeholders e incentivos internos.

Desde la perspectiva de una startup o MIPYME, esto transforma a Ethereum de un conjunto de protocolos en un servicio: “configura mi empresa onchain y ayúdame a gestionarla de forma segura”.

3b. Prototipo en ETH New York: simplificando el primer paso

El primer paso hacia esta visión fue el prototipo de Startupchain en ETHGlobal New York 2025. El equipo se enfocó en la primera acción que cualquier empresa onchain debe realizar: asegurar un dominio ENS único para reconocer su identidad.

En el flujo estándar de ENS, los fundadores deben navegar múltiples pantallas y pasos técnicos del proceso (selección de nombre, duración, proceso de registro, configuración, compromiso, nombre primario). El prototipo:

• Comprimió el proceso de registro ENS de cinco pasos a solo dos,

• Lo integró en un flujo sencillo para startups (“elige el nombre de tu empresa” → “confirma registro”), y

• Integró Privy para permitir inicio de sesión con correo electrónico o wallets existentes, produciendo la experiencia accesible para fundadores no nativos de cripto.

A pesar de cubrir solo este primer paso, el prototipo demostró que pequeñas mejoras de UX en la capa correcta pueden reducir dramáticamente la barrera de entrada para que startups y MIPYMES se integren a Ethereum. El proyecto obtuvo el tercer lugar en la categoría de premio “Mejor Uso de ENS”, validando que esta dirección se alinea con los objetivos propios de ENS de accesibilidad y adopción.

3c. Startupchain PRD: Onchain Company Services para startups y MIPYMES

Después de ETH New York, ampliamos el concepto hasta convertirlo en un Documento de Requerimientos de Producto (PRD, por sus siglas en inglés. Product Requirements Document). El PRD define a Startupchain como:

“Una aplicación descentralizada (dApp) que proporciona Servicios de Empresa Onchain (OCS) para establecer y administrar startups y pequeños negocios.”

En términos generales, el MVP integra cinco bloques de construcción de Ethereum en un solo servicio:

1. ENS – nombres de empresa comprensibles y subdominios para fundadores y miembros.

2. Cuentas de empresa – incorporación de EOA más Safes multichain para tesorería y gobernanza.

3. Gestión DeFi – transferencias básicas, generación de rendimientos mediante protocolos de ahorro y acceso a crédito mediante protocolos de préstamo (por ejemplo Aave, Morpho, Moonwell).

4. Certificaciones EAS – registros verificables de eventos de la empresa (constitución, hitos, financiamiento, contrataciones).

5. Tokenización de la empresa – tokens ERC-20 de participación empresarial con tokenomics personalizable, previsto para la fase posterior al MVP/Beta.

Startupchain es la extensión natural del diseño natural MicroDAO:

• La DAO mínimamente viable (ENS + Safe + EAS) es la base que toda empresa obtiene.

• Las funcionalidades DeFi convierten la tesorería Safe en una cuenta funcional de ahorro y crédito, no solo en una wallet estática.

• El token empresarial proporciona un instrumento para stakeholders y un mecanismo de Sistema de incentivos interno, permitiendo que fundadores, empleados, contribuidores y aliados tempranos compartan el beneficio potencial de forma transparente y programable.

El PRD también construye explícitamente a Startupchain, alrededor de las necesidades de startups, pequeños negocios y entidades organizadoras como aceleradoras o clusters, enfatizando:

• Menor carga legal y administrativa (reducción del 95–99% en costo y tiempo vs. a la constitución tradicional).

• Control transparente de fondos mediante firmas múltiples.

• Acceso más fácil a fuentes alternativas de financiamiento.

• Reportes estandarizados y verificables a través de certificaciones y paneles de control.

En resumen, mientras el diseño de MicroDAO define qué es una empresa onchain, Startupchain define cómo los fundadores y MIPYMES realmente lo usarán en la práctica.

3d. Trabajo en curso: hacia un MVP a finales de 2025

Startupchain se plantea deliberadamente como un proyecto en desarrollo en lugar de un producto terminado. La hoja de ruta descrita en el PRD estructura el proyecto en dos etapas:

• Un MVP, enfocado en:

  • Registro de dominios y subdominios ENS desde un único panel de control,

  • Creación de Safe multichain y mecanismos básicos de gobernanza,

  • Flujos de “ahorros y crédito” DeFi para la tesorería de la empresa,

  • Certificaciones EAS integradas para el historial de la empresa.

• Una fase Beta que añade:

  • Lanzamiento de tokens empresariales con tokenomics configurables,

  • Integración más profunda con Superchain, y

  • Funcionalidades más avanzadas de gobernanza y presentación de informes.

Nuestra meta es entregar el MVP de Startupchain para finales de 2025, alineando su lanzamiento con la evolución del programa de incubación de MicroDAOs y con las experiencias recabadas en pilotos como Axolotarium y AxoloDAO.

Para fundadores y operadores de MIPYMES, la promesa es simple:

“Danos el nombre de tu empresa, tu equipo fundador y tu capital inicial. Te entregaremos una empresa onchain —identidad, tesorería, ahorros, crédito, Sistema de incentivos interno e historial verificable— en un solo flujo comprensible.”

Al construir sobre las bases de las MicroDAOs y extenderlas con DeFi y tokens empresariales, Startupchain busca cerrar la brecha existente entre proyectos onchain experimentales y negocios cotidianos, ayudando a Ethereum a cruzar realmente el abismo hacia el mundo de startups y MIPYMES.

Empezamos este artículo hablando de onboardear “a los próximos mil millones” en Ethereum— una meta que suena abstracta y distante. Pero el camino es más sencillo de lo que parece: no hay que incorporar a usuarios individuales uno por uno. Hay que integrar a las organizaciones con las que ya trabajan.

Cada startup que se transforma en onchain incorpora a sus fundadores, su equipo, su clientela y sus aliados. Cada MIPYME que adopta una tesorería transparente se convierte en una demostración para otras diez en su comunidad. Ese es el efecto multiplicador que necesitamos.

Las MicroDAOs proporcionan el patrón arquitectónico; Startupchain aporta el producto. Y si tenemos razón —si realmente logramos comprimir meses de constitución en días y miles de dólares en decenas—, entonces cruzar el abismo no es un sueño lejano.

Es cosa de los próximos 12 meses.

This individual-focused approach has driven most ecosystem development, abstracting Ethereum's complexity into browser and mobile wallets. While this approach serves individual users well, it overlooks a critical opportunity: entities or organizations that coordinate multiple people toward collective goals.

This creates an opportunity. Tools designed for collective action represents a highly leveraged entry point into the ecosystem: the millions of startups and small & medium enterprises (SMEs) that already exist, employ people, and move real economic value every day.

If we can make Ethereum a credible, low-friction environment for these organizations, we can speed up the onboarding of both collective and individual users at the same time. Every startup or SME that comes onchain brings its founders, teams, customers, and partners with it. That is the motivation behind this article and the work we have been doing as part of the Devconnect Scholars Program and at Zenbit.

In this article, we explore:

1. The context of startups and SMEs and why they are a natural “early majority” segment for Ethereum.

2. MicroDAOs as a minimum viable DAO pattern that combines five Ethereum primitives: ENS, Safe, DeFi, EAS, and a Company Token, with real-world examples like Axolotarium and AxoloDAO.

3. Startupchain, an integrated product that reduces UX friction by orchestrating all these tools in a single flow, starting from the prototype built at ETH New York and continued through the Startupchain PRD.

1. Context

1a. What are startups and SMEs?

Globally, startups and SMEs represent the majority of firms as well as a large share of employment and GDP. Even in informality, they are the main vehicle to leverage economic opportunities for founders and entrepreneurs. Around 99% of companies worldwide are startups or SMEs, adding up to more than 391 million businesses. Over half are in Asia (51%), followed by Africa (23%), Europe (10%), North America (10%), South America (5%), and Oceania (1%). This distribution shows not only how massive the SME segment is, but also how geographically diverse it is. Any strategy to bring the real economy onchain must speak to this 99% and work across very different regions, levels of infrastructure, and regulatory realities.

Each of these types of organization offers different features that suit diverse contexts worldwide. Those able to leverage new technologies or business models may choose to found startups focused on rapid growth and long-term scalability, accepting higher risk as they build at the knowledge frontier. Small businesses, on the other hand, rely on proven models that deliver stable operations and more predictable profitability.

While there are notable differences between startups and small businesses, such as their goals, risk tolerance and time horizons, both profiles can benefit from onchain tools to:

• Bootstrap trust and coordination among co-founders.

• Manage shared treasuries and cashflow transparently.

• Formalize relationships with collaborators, investors, and community.

• Record IP, contributions, and milestones in a verifiable way.

This makes them ideal candidates for onchain coordination, especially in regions where traditional financial and legal infrastructure is slow, opaque, or exclusionary.

1b. Real economic impact and informality of startups and SMEs

Because startups and SMEs already move significant economic value, onboarding them is not about speculation; it’s about the backbone of employment and production in every region of the world. Their impact on jobs is overwhelming: in Africa, startups and SMEs generate around 84% of employment, in South America and Europe about 70%, in Oceania 70%, in Asia 64%, and in North America 59%. In other words, most people who work in the formal economy do so in organizations that look much more like a small firm or startup than a multinational corporation.

At the same time, a substantial share of these startups and SMEs operate in the informal economy, which limits their access to credit, digital tools, and long-term planning. Approximately 38% of African startups and SMEs, 35% of those in South America, and 22% in Asia are informal, compared with 16% in North America, 15% in Europe, and 11% in Oceania. This means that some of the regions where startups and SMEs create the most jobs are also those where they are least integrated into formal financial and legal systems.

In many countries, especially in the Global South, this informality shows up as:

• No clear legal entity or incorporation.

• No structured cap table, vesting, or ownership records.

• No formal agreements with collaborators.

• Cash-based accounting with limited or no audit trail.

Because of this dual reality—central to employment but often structurally excluded—onboarding startups and SMEs to Ethereum is not just an efficiency upgrade. It is a way to:

• Channel real-world revenue (payments, invoices, subscriptions) through open, programmable infrastructure.

• Support real employment (payroll, contractor payments) with transparent treasuries and auditable flows.

• Protect and monetize real assets and IP (licenses, patents, content, scientific data) with verifiable records.

• Enable real community outcomes (education, conservation, local development) by making funding and governance legible and accountable.

If Ethereum wants to become a credible global settlement layer, it must support these everyday, “boring” business operations — especially in regions where the combination of high startup/SME employment and high informality reveals how fragile current coordination and finance rails really are.

1c. Startups and SMEs as the early majority of mainstream market

Technology adoption rarely happens all at once. It follows a curve where different segments of users come in at different moments, each with their own needs and expectations. At the left side of the curve we find innovators (tech enthusiasts, ~2.5%), people who adopt new tools simply because they are new and are willing to tolerate bugs, rough edges, and missing features. Next come the early adopters (visionaries, ~13.5%), who see strategic advantage in being first and are willing to experiment as long as the upside is big enough.

These two groups form the early market. Most of Ethereum’s first decade has been dominated by them: protocol researchers, DeFi degens, NFT collectors, DAO-native teams — people who are happy to manage seed phrases, sign raw transactions, and compose protocols like Lego bricks.

Between this early market and the rest of society lies what Geoffrey Moore calls “the chasm”: a structural gap between what early adopters are willing to accept and what the mainstream market demands (Crossing the Chasm: Marketing and Selling High-Tech Products to Mainstream Customers, 1991). On the other side of the chasm sit the early majority (pragmatists, ~34%) and the late majority (conservatives, ~34%), followed by laggards (skeptics, ~16%). Pragmatists don’t care that a technology is new; they care that it works reliably, fits into their existing workflows, and clearly improves cost, speed, or risk. Conservatives and skeptics are even more demanding: they expect mature products, standards, and support.

In general, if a technology doesn’t evolve to meet the needs of the next segment, it fails to cross the chasm and remains a niche tool for enthusiasts. But if it adapts—by improving UX, hiding complexity, and solving specific, visible problems—it can bridge this gap and access a much broader market.

In the context of Ethereum, this means recognizing that:

• DeFi degens, NFT collectors, and protocol-native teams map to the innovators and early adopters on the left side of the curve. They are comfortable juggling multiple wallets, interfaces, and protocols to compose their own solutions.

• Startups and SMEs correspond to the early majority of pragmatists. They will adopt Ethereum not because it is novel, but because it solves concrete operational problems—treasury management, governance, compliance, funding—cheaper, faster, or more transparently than the status quo.

For this early-majority segment, the main value propositions are:

• Cost-efficiency: Using Ethereum as a low-cost back-office for treasury, governance, and record-keeping, instead of bespoke SaaS plus fragmented spreadsheets.

• Interoperability: Being “natively integrated” into the global onchain economy – stablecoins, DeFi credit, grants, quadratic funding, onchain marketplaces.

• Composability: Being able to plug into other tools (KYC, payroll, insurance, analytics) through shared standards, not custom integrations.

The integration of Ethereum primitives can help bridge this chasm: taking tools that were originally built for individuals and power users (wallets, DeFi protocols, ENS, EAS, tokens) and composing them into opinionated, end-to-end flows that make sense for collective entities. By wrapping these primitives in clear onboarding journeys, shared governance structures (Safe), and verifiable records (EAS), we turn Ethereum from a playground for enthusiasts into a credible operating system for startups and SMEs—the early majority that can carry the ecosystem into the mainstream.

2. MicroDAOs

A MicroDAO is our term for a minimum viable DAO: the smallest set of onchain components needed for a startup, SME, or project team to operate in a transparent, programmable, and interoperable way—without falling into “DAO governance theater.”

The minimal MicroDAO uses three core primitives (ENS, Safe, EAS), which can be extended with DeFi integrations and a Company Token as the organization matures and its operational needs grow.

In our work at Zenbit, we intentionally reduced this stack to three Ethereum primitives:

1. ENS – identity and namespace for the collective and its members.

2. Safe (multichain) – a shared smart account for treasury and execution, with the same address across multiple networks.

3. EAS attestations – a standard way to record verifiable claims about roles, milestones, and outcomes.

This minimum stack is enough to give an early-stage team:

• A name and addressable identity onchain.

• A shared account to hold funds and execute decisions.

• A public memory of what has been done, by whom, and when.

For startups and SMEs, this is precisely what is missing in the informal, early stages: clear ownership, transparent money flows, and verifiable history—but implemented through open infrastructure instead of heavy legal and corporate overhead.

2a. Minimum viable DAO: ENS + Safe (multichain) + EAS

In more detail, a MicroDAO combines:

ENS – Identity and namespace

• A human-readable primary name for the organization (e.g. mycompany.eth) instead of raw addresses.

• A namespace of subdomains (e.g. alice.mycompany.eth, safe.mycompany.eth) to distinguish roles, treasury accounts, and partner organizations.

• A discoverable identity that wallets, explorers, and apps can resolve, which is crucial once an SME starts interacting with customers, funders, or other DAOs.

Safe (multichain) – Shared treasury and execution

• A multichain Safe that holds the treasury (stablecoins, native tokens, later a company token if needed).

• Multi-sig control (e.g. 2-of-3 founders) so that no single person can unilaterally drain funds.

• The same Safe address on all supported networks, simplifying mental models and allowing the team to choose the most convenient L2s for operations.

In practice, Safe acts like the joint bank account + board approval system of the MicroDAO.

EAS attestations – Verifiable history

• Schemas that define what is being attested (e.g. “DAO formed,” “operational goal defined,” “funding milestone reached”).

• Attestations issued by mentors, coordinators, or the DAO itself to record events, contributions, and achievements.

• A public, queryable record that can later be reused by funding programs, incubators, or regulators as evidence of activity.

Instead of scattered PDFs, spreadsheets, and private chats, a MicroDAO has a shared ledger of decisions and milestones that is portable across tools and jurisdictions.

For founders of startups and SMEs, this minimal structure offers a way to formalize their organization without losing flexibility, and to gradually move from full informality towards verifiable, auditable operations.

2b. The Zenbit microDAO incubation program

To make this pattern accessible to non-crypto-native teams, Zenbit designed a microDAO incubation program that walks projects through six milestones:

1. MicroDAO Creation

   Integration of a multichain Safe with an ENS name as the minimum viable version of a MicroDAO. The team defines signers, chooses networks, and connects the onchain identity (dao-name.eth) to the shared account.

2. DAO Presentation

   Formal public introduction of the initiative—often through a Mirror article or public presentation—that explains its mission, stakeholders, and why it operates as a MicroDAO. This is usually the first moment where the project appears as a collective onchain actor, not just a personal wallet.

3. Operational Goal

   Definition of a concrete, measurable goal that justifies the MicroDAO’s existence (e.g., “operate a biomuseum,” “launch an MVP,” “run a pilot with 10 customers”) and links day-to-day activities with expected outcomes. This creates an anchor for later attestations.

4. Treasury Management

   Design of a basic financial model using the Safe: who can spend, under what rules, and how income is categorized (donations, grants, sales). DeFi can be added later, but the focus in this phase is transparency and traceability of flows.

5. Onchain Implementation

   Recording of the project’s key actions as EAS attestations and onchain transactions: formation, goals, events, payments, and milestones. The idea is that an external observer can reconstruct what the MicroDAO has actually done, without needing insider access.

6. Onchain Funding

   Use of onchain mechanisms—grants, donations, crowdfunding, or revenue channels—to bring capital into the Safe. At this point, the MicroDAO is not just a structure; it becomes a funding-ready vehicle with verifiable history and governance.

This six-phase program is designed to be portable: it can be used for scientific projects like Axolotarium, but also for early-stage startups and SMEs that need a lightweight way to structure ownership, operations, and funding without incorporating a full company from day one.

2c. Zenbit Badges: tracking progress onchain

To make this incubation process transparent and auditable, Zenbit developed Zenbit Badges [GitHub] —an onchain identity dapp that automates EAS attestations from a dedicated account (e.g. badges.zenbit.eth). The dapp maintains a registry of events, mentors, and participants, and issues attestations automatically when conditions are met.

Zenbit Badges:

• Exposes different interfaces by role (mentors and participants) and structures learning and tasks as “events” and “quizzes.”

• Uses a Solidity contract (EASOnboarding) to record activity and issue attestations on Optimism mainnet.

• Defines a catalog of certifications and quiz types, including verifying Safe membership via ENS and validating authorship of Mirror articles.

For the DAO incubation pilot, Zenbit created a series of eight badges that roughly track the evolution of a project from zero to a fully operational MicroDAO: Introduction to Web3, DAO formation, DAO presentation, operational goal, community building, decentralized funding, academic paper, and technical development.

These eight badges map to the six incubation milestones, with some milestones awarding multiple badges to recognize distinct achievements.

From the perspective of startups and SMEs, Zenbit Badges acts as:

• A progress tracker that shows how far along the incubation journey each team is.

• A reputation layer that future funders, partners, or accelerators can query.

• A standardized reporting mechanism that reduces the need for bespoke reporting formats across different programs.

2d. Axolotarium: a scientific MicroDAO in practice

Axolotarium is a specialized center for conservation, reproduction, and scientific research of Mexican axolotls, while Zenbit focuses on onchain technologies and decentralized governance. Their collaboration began in mid-2024 as part of the pilot incubation program, with the goal of transforming Axolotarium into a MicroDAO capable of coordinating conservation work, research, and funding through Ethereum. For a detailed overview of this collaboration, see our full report.

In practice, Axolotarium:

• Published its first Mirror article, “Axolotarium: Axolotls, science and blockchain”, as a DAO presentation milestone, explaining its mission and alliances.

• Completed the first milestones of the incubation program and received Zenbit Badges for:

  • Introduction to Web3 tools,

  • Formal creation of its MicroDAO (Safe + ENS), and

  • Public presentation via Mirror.

• Adopted a multichain Safe linked to axolotarium.eth as its shared treasury, experimenting with onchain funding flows for the biomuseum and research activities.

Through this process, Axolotarium strengthened its organizational structure, digital literacy, and sustainability model, moving from an informal research group to a project with a verifiable onchain identity, transparent treasury, and a roadmap for decentralized funding.

For the broader narrative of this article, Axolotarium shows that MicroDAOs are not limited to crypto-native startups: they can structure real-world institutions—labs, conservation centers, small NGOs—with the same tooling that a tech startup would use.

2e. AxoloDAO: from Safe-centered to ENS-centered coordination

As the pilot with Axolotarium progressed, several limitations of the initial Safe-centered design became evident:

• The main ENS domain axolotarium.eth pointed directly to a multichain Safe.

• Administrative actions on some dapps (for example, publishing on Mirror) required an EOA (externally owned account), so an additional subdomain (info.axolotarium.eth) was mapped to a personal admin wallet.

• Other members had no subdomains of their own, which made it hard to clearly distinguish personal vs. institutional actions.

• Changes in Safe signers across multiple chains could create mismatches or require repeated coordination.

• Concentrating administrative power and private keys in a single account created security and governance risks.

These issues were not unique to Axolotarium—they mirror what many startups and SMEs face when they try to “just use a multisig” without thinking about identity and role separation.

AxoloDAO was designed as an iteration on this experience, shifting from a Safe-centered to an ENS-centered approach:

• The main domain axolodao.eth is used as a shared admin identity whose keys and access policies are explicitly governed by the collective.

• A dedicated subdomain like safe.axolodao.eth points to the multichain Safe, making the treasury a clearly labeled component rather than the only identity.

• Key institutional members receive their own subdomains (ndali.axolodao.eth, xolotlcalli.axolodao.eth, zenbit.axolodao.eth, etc.), which can be tied to their wallets or Safes for role-based operations.

• EAS attestations encode data standards, research activities, and conservation metrics, turning AxoloDAO into a digital public infrastructure layer rather than a single project.

Learn more about AxoloDAO's mission to revolutionize Ambystoma conservation in Mexico

Beyond the ENS/Safe re-architecture, AxoloDAO tackles the deeper problem discovered during the Axolotarium pilot: information asymmetry in biodiversity conservation. It uses onchain infrastructure to:

• Standardize data capture and reporting across labs and field projects.

• Provide verifiable, auditable records of genetics, reproduction, and monitoring activities.

• Create open repositories and interoperable governance mechanisms that connect local initiatives with national-level strategies.

In other words, AxoloDAO turns a set of isolated efforts into a coordinated information and decision system, with MicroDAOs as its basic unit.

2f. From scientific pilots to startup & SME microDAOs

The Axolotarium and AxoloDAO pilots may seem far from the world of SaaS startups or local SMEs—but the underlying pattern is the same:

• A small group with a mission (conservation, product development, local services).

• Operating in a context of informality, fragmented records, and funding uncertainty.

• Needing a way to formalize just enough to access resources, prove impact, and coordinate multiple stakeholders.

The MicroDAO pattern—ENS + multichain Safe + EAS, guided by the six-phase incubation model and tracked with Zenbit Badges—offers exactly that: a lightweight but robust operating system for early-stage organizations.

For startups and SMEs, this means they can:

• Get an onchain identity and shared treasury in days, not months.

• Build a verifiable track record of milestones, customers, and financial discipline from the beginning.

• Plug into funding mechanisms, incubators, and ecosystems that recognize MicroDAO attestations as credible evidence.

In practice, using MicroDAOs represents a 95-99% reduction in both cost and time compared to traditional incorporation and bank account setup, especially in regions where legal and financial infrastructure is slow or exclusionary. What might take 3-6 months and $2,000-$10,000 USD through traditional channels can be accomplished in 2-3 days for less than $100 USD in transaction fees

In the next section we will explore how to take this pattern one step further by integrating these tools into a single UX, so that founders don’t need to be protocol experts to start operating as MicroDAOs.

3. Startupchain: integrating MicroDAOs into Onchain Company Services

The previous section described MicroDAOs as a minimum viable DAO for startups and SMEs: ENS for identity, a multichain Safe for shared treasury, and EAS for verifiable history. For many teams, this is already a huge leap from full informality. But to truly serve startups and SMEs as the early majority of Ethereum’s user base, we also need to make it easy to add:

• DeFi features for savings and credit (yield protocols and lending/borrowing).

• A company token that acts as a stakeholder instrument and internal economy mechanism (equity-like shares, contributor rewards, revenue sharing).

Startupchain is our attempt to bundle all of this into a single, coherent product: a decentralized application that offers Onchain Company Services (OCS) for establishing and managing startups and small businesses.

Instead of expecting founders to manually stitch together ENS, Safe, DeFi, EAS, and token contracts across multiple dapps, Startupchain aims to provide one entry point for creating and operating an onchain company.

3a. From fragmented UX to an integrated onchain company

Today, setting up a MicroDAO—or any onchain company—still looks like a scavenger hunt:

1. Register an ENS name in one interface.

2. Create a multichain Safe in another.

3. Manually wire funds to DeFi protocols to earn yield or access credit.

4. Use a separate UI to define EAS schemas and issue attestations.

5. Deploy a company token through yet another tool or custom contract.

6. Keep track of all of this in private docs and spreadsheets.

For the innovators and early adopters described in Section 1c, this is acceptable friction. For the pragmatic early-majority founders running startups and SMEs—already juggling payroll, regulation, and product development—it is simply too much.

Startupchain’s core goal is to compress this journey into a guided, opinionated flow that reflects the MicroDAO pattern:

1. Identity: choose and register the company’s ENS domain and subdomains.

2. Treasury: create and configure the multichain Safe as a shared account.

3. History: set up EAS schemas and issue the first attestations (formation, founders, initial deposits).

4. Financial rails: plug the treasury into curated DeFi options for savings (yield) and credit (lending/borrowing).

5. Internal economy: optionally bootstrap a company token representing stakeholder claims and internal incentives.

From a startup/SME perspective, this turns Ethereum from a collection of protocols into a Service: “set up my onchain company and help me run it safely.”

3b. ETH New York prototype: simplifying the first step

The first public step toward this vision was the Startupchain prototype at ETHGlobal New York 2025. The team focused on the very first action any onchain company must take: securing a unique ENS domain for its identity.

In the standard ENS flow, founders must navigate multiple screens and concepts (label selection, duration, commitment, reveal, resolver, primary name). The prototype:

• Compressed the ENS registration process from five steps into just two,

• Wrapped it in a startup-friendly flow (“choose your company name” → “confirm registration”), and

• Integrated Privy to allow sign-in with email or existing wallets, making the experience approachable for non-crypto-native founders.

Despite only covering this first step, the prototype demonstrated that small UX improvements at the right layer can dramatically lower the barrier for startups and SMEs to enter Ethereum. The project received 3rd place in the “Best Use of ENS” prize track, validating that this direction aligns with ENS’s own goals of accessibility and adoption.

3c. Startupchain PRD: Onchain Company Services for startups and SMEs

After ETH New York, we expanded the concept into a full Product Requirements Document (PRD). The PRD defines Startupchain as:

“A decentralized application (dApp) providing Onchain Company Services (OCS) for establishing and managing startups and small businesses.”

At a high level, the MVP integrates five Ethereum building blocks into one service:

1. ENS – human-readable company names and subdomains for founders and members.

2. Company accounts – EOA onboarding plus multichain Safes for treasury and governance.

3. DeFi management – basic transfers, yield-generating savings, and collateralized credit via lending/borrowing protocols (e.g. Aave, Morpho, Moonwell).

4. EAS attestations – verifiable records of company events (formation, milestones, funding, hires).

5. Company tokenization – ERC-20 shares with customizable tokenomics, staged for post-MVP / Beta.

In narrative terms, Startupchain is the natural extension of the MicroDAO pattern:

• The minimum viable DAO (ENS + Safe + EAS) is the baseline every company gets.

• DeFi features turn the Safe treasury into a functional savings and credit account, not just a static wallet.

• The company token provides a stakeholder instrument and mechanism for an internal economy—letting founders, employees, contributors, and early supporters share upside in a transparent, programmable way.

The PRD also frames Startupchain explicitly around the needs of startups, small businesses, and organizing entities like accelerators or clusters, emphasizing:

• Lower legal and administrative overhead (95-99% cost and time reduction vs traditional incorporation),

• Transparent multi-signer control of funds,

• Easier access to alternative funding, and

• Standardized, verifiable reporting via attestations and dashboards.

In short, where the MicroDAO pattern defines what an onchain company is, Startupchain defines how founders and SMEs will actually use it in practice.

3d. Work in progress: towards an MVP by the end of 2025

Startupchain is intentionally framed as a work in progress rather than a finished product. The roadmap described in the PRD situates the project in two phases:

• An MVP, targeting:Y

  • ENS domain + subdomain registration from a single dashboard,

  • Multichain Safe creation and basic governance rails,

  • DeFi “savings and credit” flows for the company treasury, and

  • Integrated EAS attestations for company history.

• A Beta phase that layers on:

  • Company token bootstrapping with configurable tokenomics,

  • Deeper Superchain integration, and

  • More advanced governance and reporting features.

Our working goal is to deliver the Startupchain MVP by the end of 2025, aligning its launch with the maturation of the MicroDAO incubation program and the experiences gathered from pilots such as Axolotarium and AxoloDAO.

For founders and SME operators, the promise is simple:

“Give us your company name, your founding team, and your initial capital. We’ll give you an onchain company—identity, treasury, savings, credit, internal economy, and verifiable history—in a single, understandable flow.”

By building on the MicroDAO foundations and extending them with DeFi and company tokens, Startupchain aims to bridge the remaining gap between experimental onchain projects and everyday businesses, helping Ethereum truly cross the chasm into the world of startups and SMEs.

We started this article talking about onboarding "the next billion" to Ethereum—a goal that feels abstract and distant. But the path is simpler than it seems: don't onboard individuals one by one. Onboard the organizations they already work with.

Every startup that comes onchain brings its founders, team, customers, and partners. Every SME that adopts transparent treasury management becomes a proof point for ten others in its community. This is the multiplier effect we need.

MicroDAOs provide the architectural pattern; Startupchain provides the product. And if we're right—if we can truly compress months of incorporation into days, and thousands of dollars into tens—then crossing the chasm isn't a distant dream. It's the next 12 months.

The genus Ambystoma comprises approximately 32 species of salamanders distributed exclusively across North America. Mexico harbors 17 of these species, with 16 of them being endemic to the national territory (SEMARNAT, 2018; Parra-Olea et al., 2014). Despite possessing more than 50% of the global diversity of these neotenic amphibians and being home to the Mexican axolotl (Ambystoma mexicanum)—a species that has demonstrated therapeutic potential in regenerative medicine for treating spinal cord injuries, heart diseases, and neurodegenerative disorders (McCusker & Gardiner, 2011; Tanaka & Reddien, 2011)—Mexico contributes only 3.3% of global scientific publications on the genus and holds no patents. Paradoxically, the Mexican axolotl represents nearly half (48%) of all worldwide research on Ambystoma, establishing itself as a fundamental model organism for understanding tissue regeneration mechanisms. In response to this crisis of scientific underrepresentation, AxoloDAO emerges as a decentralized organization that, through digital public infrastructure, participatory governance, and onchain tools, seeks to revolutionize conservation and accelerate research on the genus Ambystoma in Mexico, positioning the country as a leader in the knowledge and sustainable use of its unique biological heritage.

1. Introduction: The Genus Ambystoma as Underutilized Biological Heritage

The genus Ambystoma, endemic to North America, represents one of the most extraordinary evolutionary phenomena on the planet. These salamanders, distributed from southern Alaska to central Mexico, exhibit neoteny—the retention of larval characteristics in the adult state—and possess unprecedented regenerative capabilities unprecedented in vertebrates: complete regeneration of limbs, spinal cord (30% of neural tissue), cardiac tissue (up to 25% of the ventricle), and even portions of the brain without scar tissue formation (Reiß et al., 2015; Joven et al., 2019; Sousounis et al., 2014).

The medical importance of the Mexican axolotl has been extensively documented. Recent studies demonstrate that axolotl-derived growth factors (particularly FGF-8 and BMP-2) promote cardiac tissue regeneration in murine models (Godwin et al., 2017), while proteins identified in its regenerative process show potential for treating traumatic spinal cord injuries (Sabin et al., 2015). The global regenerative medicine market, driven in part by research on Ambystoma, is projected to reach $151.9 billion USD by 2026 (Grand View Research, 2024).

Mexico is the global epicenter of Ambystoma diversity, harboring 17 species of which 16 are endemic (Parra-Olea et al., 2014; SEMARNAT, 2018). These species inhabit an extraordinary variety of high-altitude aquatic ecosystems (1,800-3,500 meters above sea level) distributed primarily throughout the Trans-Mexican Volcanic Belt: from the ancient lakes of the Valley of Mexico (Xochimilco-Chalco system) to crater lakes such as Alchichica in Puebla (2,300 masl), Michoacán lake systems (Pátzcuaro at 2,035 masl, Zacapu at 1,980 masl), the Lerma-Santiago system in the State of Mexico, mountain streams in the Sierra de las Cruces (3,100 masl), and springs in the Sierra Madre Occidental from Chihuahua to Guerrero (Contreras et al., 2009; Zambrano et al., 2010).

Each species is adapted to unique ecological conditions: the Pátzcuaro salamander (A. dumerilii), the Alchichica axolotl (A. taylori), the Tarahumara axolotl (A. rosaceum) from pine-oak forests between 2,000-2,800 masl, or the stream axolotl (A. altamirani) from mountainous areas of central Mexico (Shaffer et al., 2008). These species are not only exceptional laboratory models but also cultural emblems deeply rooted in the Mesoamerican cosmovision, where Xólotl, the Mexica god of transformation and the underworld, took the form of the axolotl to escape sacrifice (Aguilar-Moreno, 2006; Zambrano et al., 2010).

However, the conservation reality is alarming: at least 11 Mexican species of Ambystoma are in categories of highest risk (9 Critically Endangered-CR, 2 Endangered-EN according to IUCN, 2024), evidencing a systemic crisis affecting fragile mountain freshwater ecosystems throughout the national territory.

Currently, the genus Ambystoma faces a devastating paradox while the genome of the Mexican axolotl, with 32 billion base pairs (10 times larger than the human genome) is intensively studied in laboratories in the United States, Germany, Austria, and Japan (Nowoshilow et al., 2018; Smith et al., 2019), Mexico—home to 53% of the world's Ambystoma biodiversity—holds zero patents and contributes only 3.3% of scientific articles about the genus. Wild populations continue collapsing, with A. mexicanum reduced to fewer than 1,000 individuals in Xochimilco, detectable only through environmental DNA analysis (Voss et al., 2015; Zambrano et al., 2010; SEMARNAT, 2018).

In response to this unprecedented crisis, AxoloDAO emerges: a decentralized organization dedicated to the conservation of the genus Ambystoma. AxoloDAO is based on a fundamental premise: conservation data must be managed as a shared, accessible, and verifiable public good for all ecosystem stakeholders.

To achieve this, AxoloDAO builds onchain digital public infrastructure that integrates the complete conservation cycle: it creates decentralized records of biological, environmental, and genetic data verifiable on Ethereum and the Superchain; preserves native germplasm in open repositories that safeguard genetic diversity; facilitates scientific collaboration among researchers, institutions, and communities without intermediaries; generates sustainable financing through impact contracts that release funds based on verifiable onchain metrics; restores critical habitats through local MicroDAOs with community governance; and educates on the ecological and cultural importance of these endemic species. This transparent and collaborative architecture allows Mexico to reclaim sovereignty over scientific knowledge of its unique biological heritage, establishing a replicable model of decentralized biobanks for endangered biodiversity conservation worldwide.

2. The Mexican Scientific Paradox

2.1 Asymmetric Distribution of Global Research

Bibliometric analysis of 5,805 publications on the genus Ambystoma during the 2015-2025 period reveals not only a dynamic field but one profoundly unequal in its geographic and thematic distribution. Worldwide research is dominated by genomics and genetics, which with 1,552 articles represents 26.7% of the total, followed by conservation studies with 1,054 publications (18.2%). This thematic distribution exposes an evident disconnect between the basic knowledge generated and its clinical application: while cell and molecular biology encompasses 1,002 articles (17.3%) and ecological studies total 920 (15.9%), regenerative medicine—the area with the greatest translational and economic potential—barely reaches 70 publications in the entire decade (1.2%), despite the documented therapeutic potential of these species (Tanaka & Reddien, 2011; McCusker & Gardiner, 2011).

The geographic distribution shows that the United States and Europe generate more than 80% of publications, while Mexico, the center of endemism for the genus with 17 species, contributes only 194 articles (3.3% of the total). This underrepresentation is particularly significant considering that A. mexicanum represents almost half (48%) of all global research on Ambystoma (2,783 of 5,805 publications), establishing itself as the dominant model organism (Bryant et al., 2017; Voss et al., 2015).

Temporal trends show an initial expansion followed by contraction: the peak production in 2016 (1,154 articles) coincided with advances in sequencing technologies (Nowoshilow et al., 2018), but production has declined to 548 articles in 2023. This deceleration reveals a severe geographic concentration of knowledge: more than 80% of studies are produced in the United States and Europe, consolidated in elite research groups such as the Ambystoma Genetic Stock Center (Kentucky), the Max Planck Institute (Dresden), and the Center for Regenerative Medicine (Vienna), which maintain reference colonies and dominate high-impact publications (Smith et al., 2019; Bryant et al., 2017). While these foreign institutions lead worldwide research on Mexican endemic species, Mexico—a country with 16 endemic species of the genus—contributes only 194 publications, evidencing an unprecedented intellectual extraction of its biological resources.

The hyperconcentration on A. mexicanum has two faces: on one hand, it consolidates the species as the model organism par excellence for regeneration studies with 2,787 publications; on the other, it means that the other 16 Mexican endemic species are virtually ignored by global science. This downward trend in total production suggests a possible exhaustion of traditional research lines or, more worryingly, a consolidation of the field in the hands of a few elite research groups that control both the animal colonies and specialized techniques.

The "post-2018 genomic explosion" following the publication of the complete genome of the Mexican axolotl perfectly illustrates Mexico's exclusion from the scientific development of its own resources. This scientific milestone, led by European and American institutions, generated hundreds of subsequent publications on gene regulation, developmental evolution, and regenerative medicine. However, no Mexican laboratory participated as a principal author in these fundamental studies, relegating the country to the role of passive observer of the scientific revolution based on its endemic biodiversity.

2.2 The Absolute Void of Intellectual Property

The paradox reaches its most critical expression in the analysis of the biotechnological patent landscape. Mexico, home to 53% of the world's Ambystoma biodiversity, maintains a record of zero patents while observing how other countries monetize knowledge derived from its endemic species. Of the 253 patents registered globally between 2015 and 2025, the United States dominates with 149 patents (59%), followed by WIPO (international patents) with 63 (25%), Europe with 30 (12%), and China with 8 (3%). This distribution does not reflect scientific capacity but rather an appropriation strategy: while other countries capture commercial value through patents, Mexico remains absent from technological development based on its own endemic species.

The science-to-patent conversion analysis exposes the systemic inefficiency of the global innovation ecosystem in Ambystoma. Regeneration, a central theme with 649 scientific articles, has generated only 8 patents (81:1 ratio), suggesting enormous missed opportunities or insurmountable barriers to technological translation. Genomics, with its 1,552 articles, produced 42 patents (37:1 ratio), representing the field where the most knowledge is being lost without intellectual property protection; while regenerative medicine shows the most efficient conversion with 70 articles generating 12 patents (6:1 ratio). These ratios reveal that regenerative medicine, although less studied, shows the highest efficiency, suggesting unexploited opportunities in tissue regeneration and genomics (Oviedo & Beane, 2009; Godwin et al., 2017; Tanaka & Ferretti, 2009).

Patent categories are distributed as: culture methods (102, 40.3%), cellular/tissue applications (76, 30%), gene sequences (42, 16.6%), proteins and growth factors (35, 13.8%), and direct therapeutic applications (12, 4.7%). This distribution indicates that technological control is concentrated in fundamental tools and methods rather than final applications, characteristic of emerging biotechnological fields (Tanaka & Ferretti, 2009). Temporal analysis shows a growing lag between scientific publication and patenting: the peak of articles occurred in 2016 while the peak of patents arrived in 2024, an 8-year gap that continues expanding, suggesting accelerated commercial consolidation of the field with approximately 50% of patents still active.

2.3 Structural Factors and Critical Gaps of the Paradox

The Mexican paradox in Ambystoma research responds to structural factors that perpetuate the gap between endemic biodiversity and scientific production. Mexico has fewer than 5 specialized laboratories in developmental biology and regenerative medicine with capacity to maintain axolotl colonies, compared to more than 200 in the United States and Europe.

The scarcity of infrastructure and funding drives brain drain: specialized Mexican researchers systematically emigrate to foreign institutions where they find better conditions to develop their research. Regulatory barriers aggravate the problem—permits for research with endangered species can take more than 18 months—discouraging local projects. Additionally, there is a critical disconnect between academia and conservation, creating a gap between in situ conservation efforts and basic research that limits the application of scientific knowledge to the preservation of wild populations.

These deficiencies translate into multiple gaps. Geographically, Mexican research remains underrepresented while countries without native populations dominate studies, and threatened species other than A. mexicanum are practically ignored. Thematically, regenerative medicine remains underdeveloped (~70 articles in 10 years despite a market potential of $150 billion), there is severe imbalance between laboratory studies and fieldwork, and biotechnological applications remain unexplored. In application, the transfer of basic knowledge to clinical uses is nearly null, conservation remains disconnected from recent scientific evidence, and there is a complete absence of validation in Mexican preclinical models.

However, encouraging trends emerge in the last two years, although dominated by foreign institutions: regenerative medicine grows steadily focusing on growth factors; omics technologies are consolidating (single-cell sequencing and spatial transcriptomics); genomics is beginning to be applied to population management; comparative studies between axolotls and mammals in biomedicine are increasing; and there is intensifying emphasis on translating basic research into clinical applications.

3. The Genus Ambystoma in Mexico: A Systemic Crisis

3.1 Endemic Diversity in Accelerated Extinction

Mexico is the global epicenter of Ambystoma diversity with 17 species (>50% of the global total), of which 16 are endemic—94% endemism—concentrated in high-mountain aquatic ecosystems (Shaffer et al., 2004; Contreras et al., 2009). According to the official categorization of NOM-059-SEMARNAT-2010, 15 of the 16 endemic species are in some risk category: one species Endangered (P), three Threatened (A), and eleven subject to Special Protection (Pr) (SEMARNAT, 2010). The IUCN Red List presents an even more critical panorama: at least 9 species are classified as Critically Endangered (CR)—A. mexicanum, A. dumerilii, A. leorae, A. taylori, A. andersoni, A. granulosum, A. lermaense, A. amblycephalum, and A. bombypellum—while two additional species are Endangered (EN)—A. altamirani and A. rivulare (IUCN, 2024). This categorization means that approximately 65% of Mexican endemic species face an extremely high or very high risk of extinction in the wild.

The threats are multifactorial and synergistic: (1) habitat degradation and loss through accelerated urbanization, desiccation of water bodies for human consumption and agriculture, and pollution from urban discharges and agrochemicals; (2) introduction of invasive species—mainly tilapias (Oreochromis spp.), carp (Cyprinus carpio), and trout (Oncorhynchus spp.)—that prey on larvae, compete for resources, and transmit diseases; (3) historical overexploitation for traditional consumption and medicinal use; (4) climate change altering hydrological regimes in already fragile ecosystems; and (5) genetic disconnection between remnant populations that increases vulnerability through inbreeding (Contreras et al., 2009; Zambrano et al., 2010; Parra-Olea et al., 2007).

The crisis is not only biological but also cultural. Species such as A. dumerilii and A. mexicanum have been deeply integrated into the cosmovision and traditional medicine of Purépecha and Mexica cultures respectively for centuries, forming part of Mesoamerican biocultural heritage (Aguilar-Moreno, 2006). Their disappearance represents not only a loss of biodiversity but also the irreversible erosion of traditional ecological knowledge and the rupture of ancestral symbolic systems.

3.2 Global Genetic Impoverishment

The global captive population of A. mexicanum, widely distributed in biomedical research laboratories, teaching centers, aquariums, and private collections worldwide, has as common ancestors only 34 specimens captured in Xochimilco and taken to Paris in 1864 by naturalist Auguste Duméril (Voss et al., 2015; Smith et al., 2019; Khattak et al., 2014).

This limited genetic base has resulted in profound genomic consequences documented through single nucleotide polymorphism (SNP) analyses and complete genome sequencing: heterozygosity reduction of more than 60% compared to historical wild populations, loss of rare functional alleles associated with immune response and pathogen resistance, homogenization of mitochondrial haplotypes, and accumulation of deleterious mutations through genetic drift in small populations with prolonged inbreeding (Voss et al., 2015; Nowoshilow et al., 2018).

This genetic erosion represents a vulnerability for biomedical research: the regenerative, immunological, and metabolic responses observed in laboratory populations may not reflect the complete phenotypic plasticity of the wild genetic reservoir, limiting the general applicability of findings and the discovery of potentially valuable allelic variants for therapeutic applications (Khattak et al., 2014; Bryant et al., 2017). Recent studies demonstrate that individuals from wild populations in Xochimilco exhibit genetic variants associated with greater regenerative efficiency and resistance to Batrachochytrium dendrobatidis (chytrid fungus) absent in laboratory lineages (Zamudio & Wieczorek, 2007; Voss et al., 2015).

Preservation the genetic diversity of Mexican wild populations is fundamental both for species conservation and for maximizing their potential in regenerative medicine. Each wild population that disappears—whether A. mexicanum, A. dumerilii, A. andersoni, A. velasci, or any other endemic species—implies losing genetic adaptations specific to their local environments, the result of prolonged evolutionary processes under specific ecological conditions (Parra-Olea et al., 2007, 2014; Shaffer et al., 2004). Native germplasm constitutes an invaluable biological repository that must be documented, preserved, and analyzed before its extinction.

This disconnection between captive abundance and genetic impoverishment underscores the urgent need for biobanks that integrate ex situ conservation of native genetic diversity with comparative genomic research, ensuring both species survival and sustainable utilization of their biomedical potential.

4. AxoloDAO: A Public Digital Infrastructure Proposal for Conservation

4.1 Genesis and Vision

AxoloDAO was born from the collaboration between Zenbit—an onchain company oriented toward public goods and biodiversity conservation—, Xolotlcalli—a living axolotl biomuseum —and Ndali—a connection center and museum headquarters. This founding core integrates complementary capabilities in technological innovation, biological conservation, and cultural dissemination. From its origin, AxoloDAO is conceived as an open and neutral digital public coordination infrastructure—based on data standards and verifiable traceability—where laboratories, rescue centers, universities, and local projects can integrate, align protocols, and share scientific evidence without losing operational autonomy.

The starting point was Zenbit's sustained interest in biodiversity conservation, which led to a pilot project with Axolotarium to explore onchain tools applied to Ambystoma mexicanum conservation. As the project progressed, it became evident that limiting efforts to captive maintenance and reproduction was insufficient to achieve conservation objectives. While the technology showed its potential for traceability and financing, it also exposed project weaknesses that prevent converting individual rescue into effective conservation of wild populations: fragmented reports, dependence on third parties to validate and disseminate data, absence of common standards in data capture and reporting, and lack of key scientific infrastructure and capabilities (population genetics, genomic diversity analysis, systematized reproductive studies, and robust monitoring). This situation deepened informational asymmetry—critical for a species on the brink of extinction—and made management, reproduction, reintroduction, and research decisions vulnerable.

To address these gaps, Zenbit reaffirmed that the value of onchain infrastructure does not reside in the technology itself, but in what it enables: protocol standardization, verifiable and auditable data verification and traceability, open repositories, and interoperable governance that connects local efforts with coordinated strategies at national scale.

AxoloDAO implements these lessons through digital public infrastructure: shared standards for data capture and reporting, onchain verification and traceability mechanisms, open repositories, and interoperable governance among diverse actors that transforms isolated efforts into comparable and auditable knowledge, reduces dependence on intermediaries, and enables evidence-based coordinated strategies at local, regional, and national scales. AxoloDAO responds directly to the genetic impoverishment crisis documented in global captive populations and to the urgency of preserving the native genetic diversity of Mexican species before their definitive extinction. In summary, AxoloDAO converts collaboration into a reliable information and coordination system that prioritizes transparency, reproducibility, and real impact on Ambystoma populations.

4.2 Mission and System Architecture

This digital infrastructure materializes through a robust technical architecture designed to support the following strategic conservation lines:

1. Creation of a decentralized registry of the axolotl ecosystem, interconnecting data from natural sites, restored refuges, environmental variables, and population biological data.

2. Construction of open repositories of genetic data and field observations, including an onchain germplasm repository that preserves native genetic diversity under ethical and legal guidelines.

3. Facilitation of collaboration among researchers, institutions, and local communities through onchain infrastructure that reduces informational asymmetry and allows coordination without intermediaries.

4. Generation of sustainable financing models with environmental impact contracts that release funds according to verified onchain metrics.

5. Restoration and protection of critical Ambystoma habitats through local MicroDAOs in ecological refuges and chinampas with community governance.

6. Education on the ecological and cultural importance of these endemic species, highlighting their extraordinary regenerative capacities.

7. Demonstration of how digital public infrastructure can accelerate biodiversity conservation, establishing a model of decentralized biobanks for endangered species.

Therefore, its mission and vision are structured as follows:

• Mission: Conserve species of the genus Ambystoma in Mexico through public digital infrastructure that democratizes access to scientific data, facilitates intersectoral collaboration, and generates sustainable financing based on verifiable impact.

• Vision: Establish the global reference model in endemic species conservation through public digital infrastructure that transforms scientific collaboration, transparent resource management, and open access to biodiversity data, positioning Mexico as a leader in decentralized biobanks and open science.

• 
  

Technical Architecture

AxoloDAO's technical architecture is built on four fundamental components:

1. Smart contracts deployed on Ethereum L2 (OP Stack) to store verifiable metadata of each specimen, conservation site, and research project.

2. Attestation System (EAS) that validates data provenance from certified laboratories, environmental sensors, and accredited researchers.

3. Decentralized identifiers (ENS/DID) that assign unique and immutable identity to each monitored axolotl, ecological refuge, or research dataset.

4. Programmable treasuries (Safe) that automatically fund projects according to verified onchain impact metrics (water quality improvements, population increase detected by eDNA, scientific publications).

This infrastructure transforms conservation into a transparent, auditable, and coordinated process, where researchers, communities, and donors participate in a public network of scientific evidence and environmental action.

4.3 Strategic Action Axes

To materialize this vision, AxoloDAO structures its operation in three strategic axes that address the critical dimensions of the Ambystoma conservation crisis: generation and standardization of scientific data, preservation of native genetic heritage, and ecosystem restoration through decentralized governance. These axes operate in an integrated manner, where generated data informs management decisions, preserved genetic diversity enables population recovery strategies, and restored ecosystems provide viable habitats for sustainable wild populations.

4.3.1 Axolotl and Environment Data System

Effective conservation decision-making requires standardized, verifiable, and accessible information about population status, habitat quality, and ecological dynamics that determine their viability. However, information about Ambystoma in Mexico is fragmented among institutions, projects, and jurisdictions, without common collection protocols or shared access platforms. This disarticulation prevents comparative assessments between sites, hinders monitoring of long-term population trends, and limits response capacity to conservation emergencies.

AxoloDAO creates a decentralized registry of the axolotl ecosystem, interconnecting data from multiple sources. The system integrates three critical information categories:

1. Specimen data: Information on monitored individuals allows tracking population demographics, reproductive success, and responses to management interventions. Includes taxonomic identification of the 17 species, natural behavior and feeding ethograms that document behavioral health, regeneration events that evidence physiological capacities, and traceability of the origin center or project to guarantee verifiable provenance.

2. Environmental data: Habitat conditions determine population viability and reintroduction success. The system records water quality (temperature, pH, conductivity, dissolved oxygen), geographic location (precise GPS coordinates and altitude), and habitat type (Xochimilco canals, high-mountain lakes, restored refuges), allowing correlation of environmental parameters with conservation results.

3. Population biological data: Understanding genetic structure, demography, and spatial distribution is fundamental for evidence-based conservation strategies. Phenotypes and morphological variations indicating expressed genetic diversity are documented, reproduction rates and population demography to assess long-term viability, genetic evidence through eDNA for non-invasive monitoring of presence and abundance, and spatial and temporal mapping that identifies critical conservation sites.

This data architecture enables systematic comparisons between sites, early identification of declining populations, and quantitative evaluation of conservation intervention impact.

4.3.2 Onchain Native Germplasm Repository

The genetic homogeneity of global captive populations of A. mexicanum—descendants of only 34 founding individuals—represents a critical vulnerability documented through genomic analyses evidencing heterozygosity reduction exceeding 60%, loss of rare alleles associated with immune response, and accumulation of deleterious mutations (Voss et al., 2015; Nowoshilow et al., 2018). This genetic erosion not only compromises the evolutionary viability of captive populations but limits scientific discovery potential by restricting phenotypic variability available for biomedical research. Simultaneously, wild populations of the 17 Mexican species continue collapsing, taking with them millions of years of unique evolutionary adaptations to specific ecological conditions that have never been documented or preserved.

Facing this urgency, AxoloDAO proposes creating the first decentralized biobank of native Ambystoma genetic material that preserves the genetic diversity of Mexican endemic species before their definitive extinction. The repository operates through:

• Ethical and legally grounded collection: Obtaining gametes, tissues, and DNA from representative wild populations under SEMARNAT protocols that guarantee minimum impact on vulnerable populations, application of the Nagoya Protocol on access to genetic resources and fair benefit distribution, and prior informed consent from local communities safeguarding territories where species inhabit.

• Sequencing and genomic characterization: Analysis of complete genomes and transcriptomes of representative populations of each species to document allelic diversity, population structure, genetic variants associated with local adaptations, and candidate genes relevant for differential regenerative capacities among species.

• Resilient distributed storage: Preservation of genomic data on IPFS/Filecoin with geographic redundancy guaranteeing persistence, accessibility, and resistance to information loss from centralized infrastructure failures.

• Onchain registry with complete traceability: Each sample is registered with environmental metadata (habitat parameters), geographic (exact collection site), phenotypic (specimen morphological characteristics), and provenance (collecting institution, date, protocol used), creating an immutable and auditable history from collection to research use.

• Participatory governance for access: A DAO governance system where certified researchers request access through peer review protocols, origin communities participate in decisions about authorized uses, and fair benefit- distribution mechanisms are implemented when genetic material use derives in commercial applications.

This repository not only preserves the genetic diversity of the 17 Mexican species but establishes a model of sovereign management of national genetic resources aligned with the Nagoya Protocol, guaranteeing that knowledge derived from Mexican endemic biodiversity primarily benefits Mexico. Additionally, it constitutes a replicable precedent of decentralized biobanks for endangered species operating under principles of open science, verifiable traceability, and transparent governance.

4.3.3 Ecosystem Restoration through MicroDAOs

Effective conservation requires coordination between local action and rigorous scientific monitoring. AxoloDAO implements a local MicroDAO model that decentralizes ecological refuge management while maintaining shared standards of monitoring, reporting, and governance:

1. MicroDAOs in each refuge: Decentralized autonomous organizations established in chinampas, restored refuges, and critical conservation sites, with direct participation of chinamperos, local communities, and scientists.

2. IoT sensors connected to smart contracts: Continuous 24/7 monitoring of water quality parameters (temperature, pH, conductivity, dissolved oxygen) automatically feeding verifiable onchain records.

3. Environmental impact contracts: Programmable agreements that automatically compensate local guardians according to verified conservation metrics (population increases detected by eDNA, maintenance of optimal water quality, habitat restoration).

4. Public monitoring panels: Dashboards accessible in real-time for citizens, researchers, donors, and decision-makers, showing conservation status, environmental quality, and intervention effectiveness.

This model converts local communities into central conservation actors with economic incentives directly aligned to measurable results, while guaranteeing transparency and accountability through onchain verification of data and impact. Coordination among MicroDAOs enables shared learning about effective interventions, replication of best practices, and construction of a national network of ecological refuges operating under interoperable protocols.

4.4 Governance Model and Collaboration Network

AxoloDAO operates under a participatory decentralized governance model where multiple actors collaborate while maintaining operational autonomy:

• Researchers and scientists: Propose standardized data collection protocols, validate monitoring methodologies, and publish verifiable results onchain that feed evidence-based decisions.

• Local communities: Actively participate in habitat management decisions in their territories through MicroDAOs with proportional voting power, ensuring conservation strategies respect traditional ecological knowledge and community needs.

• Donors and funders: Track in real-time the quantifiable impact of their contributions through public dashboards reporting verified metrics: water quality improvements, population increases detected by eDNA, hectares of restored habitat, and scientific publications generated.

• Academic and governmental institutions: Collaborate through interoperable protocols without ceding proprietary data or institutional autonomy, publishing only verifiable metadata allowing coordination without centralization.

AxoloDAO operates as a multisectoral collaboration network integrating:

• Academic institutions: Universidad Autónoma de Querétaro (Faculty of Natural Sciences), Universidad Tecnológica de Querétaro, and universities throughout the Mexican Republic developing research in conservation and Ambystoma

• Governmental institutions: Secretaría de Medio Ambiente y Recursos Naturales (SEMARNAT), state and municipal environment secretariats, local governments, Secretaría de Desarrollo Sustentable (SEDESU), and Secretaría de la Juventud (SEJUVE) in environmental education projects.

• Private sector: Zenbit (onchain technological infrastructure), Ginger Birra, Querétaro Restaurant and Hotel Association, and companies committed to sustainability financing projects through verifiable impact contracts.

• Civil society organizations: Local conservation initiatives, chinampa communities, environmental collectives, and non-governmental organizations dedicated to protecting aquatic ecosystems.

5. Conclusions

5.1 Transformation of the Conservation Paradigm

The conservation crisis of the genus Ambystoma in Mexico represents both a critical threat and a transformative opportunity. The bibliometric analysis presented documents an unprecedented scientific paradox: while Mexico harbors 17 species of Ambystoma—53% of global genus diversity—and 16 of them are endemic exclusively to national territory, the country contributes only 3.3% of global scientific publications and maintains zero related patents. This underrepresentation is not merely statistical; it reflects a systematic extraction of knowledge where foreign institutions dominate research on Mexican endemic species, generate intellectual property derived from Mexican biological resources, and capture the economic value of a regenerative medicine market projected at $151.9 billion USD by 2026. However, the magnitude of this systemic crisis also evidences the transformative potential of new conservation models.

The Ambystoma case demonstrates that effective conservation of critically endangered species is not achieved exclusively through isolated habitat protection efforts or ex situ reproduction; it requires a comprehensive transformation in how scientific knowledge is generated, validated, shared, and used for evidence-based conservation decision-making. AxoloDAO proposes a paradigm shift: from centralized models dependent on individual institutions and unstable governmental funding, toward digital public infrastructure that operates as a shared common good. This infrastructure does not replace existing institutions—universities, research centers, environmental authorities, local communities—but rather connects them through standardized data collection and reporting protocols, onchain verification and traceability mechanisms, open repositories, and participatory governance allowing coordination without centralization.

AxoloDAO's three strategic axes—standardized data system, decentralized germplasm repository, and ecosystem restoration through MicroDAOs—address complementary dimensions of the crisis: information fragmentation preventing evidence-based decisions, genetic vulnerability compromising evolutionary viability of captive populations, and habitat degradation eliminating refuges for wild populations. This integrated architecture enables local conservation efforts to articulate into nationally coordinated strategies, where knowledge generated at one site informs interventions at others, preserved genetic resources enable population recovery programs, and restored ecosystems provide viable habitats for long-term persistence.

5.2 Research and Scientific Development Potential

The infrastructure proposed by AxoloDAO not only preserves endangered biodiversity; it enables a new era of scientific research on Ambystoma. The onchain germplasm repository represents the first systematic effort to document and preserve the complete genetic diversity of the 17 Mexican species before their extinction. This collection of genomes, transcriptomes, and associated environmental metadata will constitute an invaluable resource for comparative research: What genetic variants explain differences in regenerative capacities among species? What evolutionary adaptations allowed A. taylori to colonize unique saline environments? What alleles present in wild populations but absent in laboratory colonies confer resistance to emerging pathogens?

The standardized data system enables for the first time metapopulation-scale studies correlating environmental parameters, genetic diversity, and population viability across multiple sites. Fundamental questions that have remained unanswered due to lack of comparable data—What is the minimum viable population size for long-term persistence? What water quality thresholds determine reproductive success? How does habitat fragmentation affect population genetic structure?— can be addressed through aggregated data analysis from dozens of sites operating under standardized protocols.

Beyond conservation, this model of decentralized biobanks with transparent governance establishes a precedent for other critically endangered species. If AxoloDAO demonstrates that it is possible to preserve genetic diversity, generate high-impact scientific knowledge, and financially sustain long-term conservation operations through public digital infrastructure, the model will be replicable for hundreds of Mexican endemic species facing similar threats.

5.3 Call to Action

The time to act is now. The window of opportunity to preserve the native genetic diversity of Mexican Ambystoma species is closing rapidly: each wild population that disappears represents the irreversible loss of millions of years of evolution and unique adaptations. The public digital infrastructure proposed by AxoloDAO offers a concrete path to transform this crisis into an opportunity for scientific leadership and effective conservation.

We invite researchers, academic institutions, conservation organizations, local communities, companies committed to sustainability, and interested citizens to join this collective effort. Participation can take multiple forms: contributing monitoring data under standardized protocols, integrating local projects into the MicroDAO network, financing verifiable environmental impact contracts onchain, collaborating in genomic characterization of wild populations, or simply disseminating the importance of conserving these extraordinary species.

AxoloDAO's success will not be measured solely by publications generated or funds raised, but by the fundamental result: viable populations of the 17 Mexican Ambystoma species persisting in restored habitats, with their genetic diversity documented and preserved, generating scientific knowledge that benefits Mexico and serving as a replicable model of effective conservation for the 21st century.

6. Methodological Note

The bibliometric analysis presented in this article is based on multiple specialized data sources:

Scientific publications: 5,807 articles on the genus Ambystoma (period 2015-2025), including 2,783 publications specific to A. mexicanum, 194 articles with participation from Mexican institutions, and specific analyses of Mexican endemic species: A. andersoni (104 publications), A. dumerilii (141 publications), and A. velasci (159 publications). Data were extracted from Lens.org, Web of Science, Scopus, and PubMed through systematic searches by species scientific name, related terms (regeneration, conservation, genomics), and co-citation analysis. Institutional authorship analysis was based on first author and corresponding author affiliation according to publication metadata.

Biotechnological patents: 253 Ambystoma-related patents registered between 2015-2025, extracted from Google Patents, USPTO, EPO, and WIPO through keyword searches (Ambystoma, axolotl, regeneration, salamander) in titles, abstracts, and claims. Registration jurisdiction, legal status, technological category, and non-patent literature citations were documented.

Economic projections: Regenerative medicine market estimates are based on reports from Grand View Research (2024) and Markets and Markets (2024), projecting the global market at $151.9 billion USD by 2026 with a compound annual growth rate (CAGR) of 23.3%.

Conservation analysis: Species conservation status according to IUCN Red List categories (2024) and NOM-059-SEMARNAT-2010, complemented with data from the Action Program for Conservation of Ambystoma spp. Species (SEMARNAT, 2018).

Methodological limitations include possible underrepresentation of publications in languages other than English, bias toward literature indexed in Anglo-American databases, and difficulty in quantifying Mexican participation in international collaborations where institutional affiliation does not reflect researcher nationality. Bibliometric data represent robust general trends but specific figures should be interpreted as approximations with an estimated margin of error of ±5%.

7. Bibliographic References

Aguilar-Moreno, M. (2006). Handbook to life in the Aztec world. Oxford University Press

Arenas-Gómez, C. M., & Delgado, J. P. (2021). Limb regeneration in salamanders: the plethodontid tale. The International journal of developmental biology, 65(4-5-6), 313–321. https://doi.org/10.1387/ijdb.200228jd

Bryant, D. M., Johnson, K., DiTommaso, T., Tickle, T., Couger, M. B., Payzin-Dogru, D., Lee, T. J., Leigh, N. D., Kuo, T. H., Davis, F. G., Bateman, J., Bryant, S., Guzikowski, A. R., Tsai, S. L., Coyne, S., Ye, W. W., Freeman, R. M., Jr, Peshkin, L., Tabin, C. J., Regev, A., … Whited, J. L. (2017). A Tissue-Mapped Axolotl De Novo Transcriptome Enables Identification of Limb Regeneration Factors. Cell reports, 18(3), 762–776. https://doi.org/10.1016/j.celrep.2016.12.063

Contreras, V., Martínez-Meyer, E., Valiente, E., & Zambrano, L. (2009). Recent decline and potential distribution in the last remnant area of the microendemic Mexican axolotl. Biological Conservation, 142(12), 2881-2885. https://doi.org/10.1016/j.biocon.2009.07.008

Godwin, J. W., Debuque, R., Salimova, E., & Rosenthal, N. A. (2017). Heart regeneration in the salamander relies on macrophage-mediated control of fibroblast activation and the extracellular landscape. NPJ Regenerative medicine, 2, 22. https://doi.org/10.1038/s41536-017-0027-y

Grand View Research. (2024). Regenerative Medicine Market Size, Share & Trends Analysis Report 2024-2030. https://www.grandviewresearch.com/industry-analysis/regenerative-medicine-market

IUCN. (2024). The IUCN Red List of Threatened Species. Ambystoma species assessments. https://www.iucnredlist.org/search?query=ambystoma

Joven, A., Elewa, A., & Simon, A. (2019). Model systems for regeneration: salamanders. Development (Cambridge, England), 146(14), dev167700. https://doi.org/10.1242/dev.167700

Khattak, S., Schuez, M., Richter, T., Knapp, D., Haigo, S. L., Sandoval-Guzmán, T., Hradlikova, K., Duemmler, A., Kerney, R., & Tanaka, E. M. (2014). Germline Transgenic Methods for Tracking Cells and Testing Gene Function during Regeneration in the Axolotl. Stem cell reports, 2(2), 243. https://doi.org/10.1016/j.stemcr.2014.01.017

McCusker, C., & Gardiner, D. M. (2011). The axolotl model for regeneration and aging research: a mini-review. Gerontology, 57(6), 565–571. https://doi.org/10.1159/000323761

Nowoshilow, S., Schloissnig, S., Fei, J. F., Dahl, A., Pang, A. W. C., Pippel, M., Winkler, S., Hastie, A. R., Young, G., Roscito, J. G., Falcon, F., Knapp, D., Powell, S., Cruz, A., Cao, H., Habermann, B., Hiller, M., Tanaka, E. M., & Myers, E. W. (2018). The axolotl genome and the evolution of key tissue formation regulators. Nature, 559(7712), E2. https://doi.org/10.1038/s41586-018-0141-z

Oviedo, N. J., & Beane, W. S. (2009). Regeneration: The origin of cancer or a possible cure?. Seminars in cell & developmental biology, 20(5), 557–564. https://doi.org/10.1016/j.semcdb.2009.04.005

Parra-Olea, G., Flores-Villela, O., & Mendoza-Almeralla, C. (2014) Biodiversidad de anfibios en México. Revista Mexicana de Biodiversidad. 85, suppl., pp. S460-S466. https://doi.org/10.7550/rmb.32027

Parra-Olea, G., Recuero, E. & Zamudio, K. R. (2007) Polymorphic microsatellite markers for Mexican salamanders of the genus Ambystoma. Molecular Ecology Notes, 7: 818-820. https://doi.org/10.1111/j.1471-8286.2007.01714.x

Reardon S. (2018). Frustrated Alzheimer's researchers seek better lab mice. Nature, 563(7733), 611–612. https://doi.org/10.1038/d41586-018-07484-w

Reiß, C., Olsson, L., & Hoßfeld, U. (2015). The history of the oldest self-sustaining laboratory animal: 150 years of axolotl research. Journal of Experimental Zoology Part B, 324(5), 393-404. https://doi.org/10.1002/jez.b.22617

Sabin, K., Santos-Ferreira, T., Essig, J., Rudasill, S., & Echeverri, K. (2015). Dynamic membrane depolarization is an early regulator of ependymoglial cell response to spinal cord injury in axolotl. Developmental biology, 408(1), 14–25. https://doi.org/10.1016/j.ydbio.2015.10.012

SEMARNAT (2010). NORMA Oficial Mexicana NOM-059-SEMARNAT-2010, Protección ambiental-Especies nativas de México de flora y fauna silvestres-Categorías de riesgo y especificaciones para su inclusión, exclusión o cambio-Lista de especies en riesgo. Diario Oficial de la Federación. https://www.dof.gob.mx/normasOficiales/4254/semarnat/semarnat.htm

SEMARNAT (2018). Programa de Acción para la Conservación de las Especies. Ambystoma spp, SEMARNAT/CONANP, México https://share.google/Zf2VLiuFHBk5yxJX8

Shaffer, H. B., Pauly, G. B., Oliver, J. C., & Trenham, P. C. (2004). The molecular phylogenetics of endangerment: cryptic variation and historical phylogeography of the California tiger salamander, Ambystoma californiense. Molecular ecology, 13(10), 3033–3049. https://doi.org/10.1111/j.1365-294X.2004.02317.x

Smith, J. J., Timoshevskaya, N., Timoshevskiy, V. A., Keinath, M. C., Hardy, D., & Voss, S. R. (2019). A chromosome-scale assembly of the axolotl genome. Genome research, 29(2), 317–324. https://doi.org/10.1101/gr.241901.118

Sousounis, K., Baddour, J. A., & Tsonis, P. A. (2014). Aging and regeneration in vertebrates. Current topics in developmental biology, 108, 217–246. https://doi.org/10.1016/B978-0-12-391498-9.00008-5

Tanaka, E. M., & Ferretti, P. (2009). Considering the evolution of regeneration in the central nervous system. Nature Reviews Neuroscience, 10(10), 713-723. https://doi.org/10.1038/nrn2707

Tanaka, E. M., & Reddien, P. W. (2011). The cellular basis for animal regeneration. Developmental cell, 21(1), 172–185. https://doi.org/10.1016/j.devcel.2011.06.016

Voss, S. R., Epperlein, H. H., & Tanaka, E. M. (2009). Ambystoma mexicanum, the axolotl: a versatile amphibian model for regeneration, development, and evolution studies. Cold Spring Harbor protocols, 2009(8), pdb.emo128. https://doi.org/10.1101/pdb.emo128

Voss, S. R., Woodcock, M. R., & Zambrano, L. (2015). A Tale of Two Axolotls. Bioscience, 65(12), 1134–1140. https://doi.org/10.1093/biosci/biv153

Zambrano, L., Valiente, E., & Vander Zanden, M. J. (2010). Food web overlap among native axolotl (Ambystoma mexicanum) and two exotic fishes: Carp (Cyprinus carpio) and tilapia (Oreochromis niloticus) in Xochimilco, Mexico City. Biological Invasions, 12(9), 3061-3069. https://doi.org/10.1007/s10530-010-9697-8

Zamudio, K. R., & Wieczorek, A. M. (2007). Fine-scale spatial genetic structure and dispersal among spotted salamander (Ambystoma maculatum) breeding populations. Molecular ecology, 16(2), 257–274. https://doi.org/10.1111/j.1365-294X.2006.03139.x

Axolotarium is a specialized center for conservation, reproduction, and scientific research of the Mexican axolotl, while Zenbit is a company focused on developing onchain technologies and implementing decentralized governance systems. Although their institutional lines of action are distinct —one centered on biodiversity and the other on technological infrastructure— both organizations have developed a strategic collaboration since mid-2024, aimed at integrating decentralized technologies into biological conservation projects, initiating an incubation process to transform Axolotarium into a microDAO with operational and governance capabilities. The alliance emerges within the framework of the pilot microDAO Incubation program promoted by Zenbit Badges, a platform developed by Zenbit for onchain certification specialized in scientific research and technological development through Web3 tools.

In one of the first joint actions, Axolotarium published its inaugural article on Mirror: "Axolotarium: Axolotls, science and blockchain”, an official presentation of their vision, institutional alliances, and commitment to decentralization as an operational model. Following this publication, the team obtained their first three Zenbit Badges: the first for completing the Introduction to Onchain Tools, the second for the formal creation of their microDAO, and the third for their participation in outreach through the Mirror article.

Thanks to specialized advisory from Zenbit, including technical, methodological, and operational guidance, Axolotarium has not only strengthened its digital and operational capabilities but has also established a sustainability model based on autonomous income, DAO management, and onchain funding.

This strategic alliance demonstrates how the integration of decentralized technologies, not only in conservation projects but into a wide range of initiatives, enables the articulation of sustainable, measurable, and scalable models, where citizen science is enhanced through Web3 tools.

This report details the core components of the collaboration, including the context and motivations that support axolotl conservation, Axolotarium's incubation process as a microDAO, advances in digital infrastructure implementation, and the development of their operational goals for 2025.

Why Protect the Axolotl?

Cultural Value

The axolotl has been a fundamental part of the Mexican collective imagination since pre-Hispanic times. In Mexica mythology, it is linked to Xólotl, god of the underworld and symbol of sacrifice. Its Nahuatl name, axolotl, can be translated as "water monster" or "water game," reflecting its ethereal and enigmatic nature. Beyond myth, this animal has also been used in traditional Mexican medicine for its presumed healing properties, especially in treating respiratory diseases.

This cultural dimension not only enriches the symbolic value of the axolotl, but also connects ancestral knowledge with contemporary science and strengthens a legacy that transcends generations. At Zenbit, we consider that preserving the axolotl is also preserving an invaluable part of Mexico's cultural, symbolic, and therapeutic heritage.

Tissue Regeneration

One of the most remarkable aspects of the axolotl —and a major reason why the international scientific community has focused its attention on this species— is its ability to regenerate functional limbs, organs, and tissues. As described in Axolotarium's article, this regeneration process—epimorphosis—not only allows the axolotl to survive serious injuries but also opens the door to revolutionary medical advances.

When an axolotl loses a limb, it begins a regeneration process called epimorphosis. First, a protective layer of cells called epithelium forms to prevent infections. Then the blastema appears, a group of specialized cells capable of dividing and transforming into any type of tissue. Finally, genetic signals organize these cells to fully reconstruct the lost structure.

At Axolotarium, this phenomenon is frequently observed, especially in juveniles that suffer minor injuries during feeding. This controlled environment offers a unique opportunity to observe and document the regenerative process, which has proven to be functional and complete: bones, muscles, nerves, and organs can be reconstructed without scarring.

65.6% of the axolotl genome consists of repetitive sequences, a technical challenge that could contain the fundamental clues to human regenerative medicine. At Zenbit, we consider that supporting this line of research also means investing in cutting-edge solutions in neurology, cardiology, and degenerative diseases.

Endangered Species

Despite its biological, cultural, and scientific value, the axolotl is on the brink of extinction. Axolotarium's article makes it clear: less than 1% of its natural habitat remains, and it is estimated that there are fewer than 1,000 specimens in the wild. The causes are multiple: urbanization, contamination, invasive species, climate change, unregulated tourism, and infectious diseases such as the fungus Batrachochytrium dendrobatidis.

Furthermore, the axolotl is an indicator species: its disappearance would also be a critical warning about the health status of the Xochimilco ecosystem. Therefore, conserving the axolotl is not only protecting a species but preserving a natural environment that sustains biodiversity and ecological balance in the Valley of Mexico.

Faced with this crisis scenario, specialized centers like Axolotarium play a crucial role in species conservation. The simulated habitat of the axolotls is meticulously maintained, recreating ideal conditions for their well-being: spacious areas, shallow depth, cold and well-oxygenated water, dim lighting, and advanced filtration systems.

Each specimen has its own space, specialized feeding, and veterinary care. These conditions not only guarantee their survival but allow precise observation of their behavior, regenerative response, and development over time.

Incubation of Axolotarium as a microDAO

Zenbit's pilot microDAO incubation program emerges as a response to the critical importance of the early stages in the life of any project, company, or scientific initiative. These early phases, although decisive, are usually marked by a high abandonment rate due to lack of organizational structure, clear governance, and financial sustainability. Aware of this challenge, at Zenbit we have developed an accompaniment model that supports both emerging organizations and individuals or teams seeking to incubate technological, social, or scientific projects under a decentralized logic.

Through a guided process, each initiative is supported in six key milestones:

1. microDAO Creation: Integration of a shared account (safe multichain) with an onchain domain (Ethereum Name Service) as a minimum viable version of a microDAO.

2. DAO Presentation: Formal dissemination of the initiative and its value proposition to the community.

3. Operational Goal: Formulation of a concrete goal that justifies the microDAO's operation and links its activities with expected results.

4. Treasury Management: Design of a financial model that guarantees transparency, traceability, and operational sustainability through onchain tools and decentralized finance protocols.

5. Onchain Implementation: Integration of public onchain records derived from the project's daily operation to offer verifiable, transparent, and public data that provide certainty to project stakeholders.

6. Onchain Funding: Access to cryptocurrency resources through decentralized funding mechanisms.

This process is supported by Zenbit Badges, an onchain certification system that allows public validation of compliance with each milestone. Incubated microDAOs evolve transparently, recording their advances onchain and operating with decentralized infrastructure from the start.

After completing the first two stages of the incubation process with Axolotarium, we began a closer collaboration at the site, where our collaborator Maggie accompanied Axolotarium's director, Fernanda, during the first semester of 2025. During this period, operational processes were restructured to provide greater clarity and certainty about the population, financial sustainability, and organizational structure.

This joint work allowed the consolidation of an evidence-based management system, reflected in the precise characterization of the center's inhabitants, the definition of a realistic and verifiable operational goal, and the implementation of more efficient administrative procedures.

Thanks to this synergy, a more robust and transparent operation model was consolidated, laying the foundations for decentralized management through a microDAO. As a result of this restructuring, Axolotarium managed to advance with greater solidity in formulating its operational goal, developing clear strategies for biological traceability, financial strengthening, and technical decision-making based on operational data.

The Inhabitants of Axolotarium

The current axolotl population at Axolotarium consists of a diverse community that reflects the success of measures implemented for their well-being and conservation. The center houses three main phenotypes: golden albino, leucistic, and nominal (brown), distributed among different developmental stages.

The population structure includes six adult specimens—Mango, Vainilla, Fresita, Iztaccihuatl, Crepita, and Manotas—who form the reproductive base; thirty-five juveniles born in 2024, among which are Tintín, Limón, Astro, Xoli, Scarface, and Godzilla; and 190 surviving offspring from the reproductive cycle of the first quarter of 2025.

Although these offspring were segmented from the first weeks post-hatching, individual differences in growth are evident, requiring constant adjustments in their management. To ensure monitoring and differentiated attention for each cohort, a stage-based segmentation system was established based on observable biological characteristics such as body size, coloration, and feeding behavior. Additionally, improvements were made to the center's infrastructure, including filtration and oxygenation systems and more frequent scheduling for water changes.

Operational Goal 2025 and Financial Sustainability

For advances in research and conservation to be sustainable, it is fundamental to guarantee the continuous operation of Axolotarium. This center not only protects an endangered species but also represents a unique opportunity to drive research that could change how we understand and treat human injuries.

Axolotarium's operation requires covering essential operational costs, such as feeding the axolotls, specialized veterinary care, and maintenance of its facilities, designed to replicate their natural habitat. Additionally, the center constantly works on scientific dissemination and creating strategic collaborations to expand the impact of its work.

With a view to improving its operational and financial efficiency, Axolotarium restructured its cost system, achieving clear definition of its expense categories: infrastructure, fixed costs, and variable costs, each with its adjustments, learnings, and new projections.

The operational goal for 2025 amounts to approximately $5,000 USD ($110,869.16 MXN), a carefully calculated budget that includes the following components:

Infrastructure-Associated Expenses

$1,065.19 USD ($19,919.20 MXN) - 18% of total:

Includes a contingency fund of $399 USD ($7,469.70 MXN) intended to cover emergencies or failures without compromising general operation, and a necessary expansion of $665 USD ($12,449.50 MXN) to acquire new tanks and additional filtration systems that accommodate population growth derived from the December reproductive cycle.

Fixed Costs

$874 USD ($16,355.16 MXN) - 15% of total:

Covers logistics expenses $513 USD ($9,600.00 MXN) for transportation and supply acquisition, and legal procedures $361.23 USD ($6,755.16 MXN) necessary to maintain required registrations with IMPI, SEMARNAT, and INDAUTOR, guaranteeing the center's legal operation.

Variable Costs

$3,987.42 USD ($74,594.80 MXN) - 67% of total:

This category represents the largest part of the budget and is divided into food $2,609.65 USD ($48,800.00 MXN - 44.02% of total) to cover the specific nutritional needs of each developmental stage, medications $256.68 USD ($4,800.00 MXN - 4.33% of total) for prevention and treatment of common conditions, basic supplies $192.51 USD ($3,600.00 MXN - 3.25% of total) for daily maintenance materials, and services such as water and electricity $930.20 USD ($17,394.80 MXN - 15.69% of total).

2025 Administration Advances

Since January 2025, Axolotarium's administration has consolidated significant advances in population management, operational strengthening, biological traceability, and construction of an evidence-based governance model. During the first quarter of the year, key progress was achieved in reproduction strategies, population management, infrastructure improvement, and technical governance.

The center's operation has been led by a multidisciplinary team, coordinated by Fernanda Beltrán and Tania Gómez from the General Direction, with institutional and strategic accompaniment from Zenbit. All this work has been possible thanks to the commitment of more than 40 volunteers and scholarship recipients who actively collaborate in the project's different areas, with continuous support from Zenbit as a strategic ally.

One of the most important milestones has been the successful management of the reproductive cycle recorded during the first quarter of 2025. Faced with this demographic explosion, effective population control measures were implemented, including:

1. Segmentation by developmental stages, based on physiological variables such as body size, coloration, and feeding behavior.

2. Symbolic coding of tanks, which facilitates technical and volunteer work.

3. Strategic redistribution of specimens, considering density per water volume.

These actions have made it possible to guarantee the individual well-being of each axolotl, reduce intraspecific stress, and optimize available operational resources.

Likewise, the center's infrastructure was strengthened through improvements in filtration and oxygenation systems and increased frequency of water changes, in response to operational pressure generated by the new cohort. In parallel, a photographic documentation system was developed that constitutes a living database for monitoring growth, phenotypic differentiation, and evolution of each specimen.

In terms of governance, a technical decision-making model based on biological and operational data was consolidated. Multivariable tools and analysis of births per tank were incorporated, allowing anticipation of infrastructure, feeding, and differentiated attention needs. This structure facilitates individual traceability of each axolotl from birth and lays the foundations for future adoption, reintroduction, scientific research, and environmental education processes.

Make a Difference: Sponsor an Axolotl

Axolotarium not only has the mission of preserving the axolotl; it also seeks to be a bridge between environmental conservation and medical advances that could benefit millions of people. Your support not only guarantees the survival of this iconic species but allows research on tissue regeneration to continue advancing toward a future where healing complex wounds is possible.

Each contribution, however small it may seem, translates into tangible and lasting impact.

To ensure the sustainability of our efforts, we launch an innovative sponsorship campaign with two modalities:

1. Remote Crypto Sponsorship – Axolocards

Directed at those who want to support the project from anywhere in the world. Each Axolocard is a unique NFT with collectible design and contributes directly to Axolotarium 2025 operational goal. Funds are deposited directly to Axolotarium.eth address.

• Cost: 0.01 ETH

• Limited collection: 6 unique cards

• Available until: September 30

• Benefits: Direct impact on conservation, access to special content, and your name on the digital allies mural

https://opensea.io/assets/ethereum/0xD039998721df29A20217d076c8B837a9Fc67fDc8/2

Iztaccihuatl

Sex: FemaleAge: 4 yearsPhenotype: Nominal (Brown)

Personality: Iztaccihuatl or Izta for friends, is the wisest and calmest of our axolotls, and her sweet "smile" seems to invite everyone to meet her. She's a glutton at heart and, although she's not as active due to her age, she remains one of the most beloved by the team and is always ready for a moment of affection with her caregivers.

https://opensea.io/assets/ethereum/0xD039998721df29A20217d076c8B837a9Fc67fDc8/0

Manotas

Sex: FemaleAge: 3.5 yearsPhenotype: Leucistic

Manotas, our "mama" axolotl, has raised several litters and takes care of her little corner in the aquarium. Physically large and strong, she has a shy and protective character. She loves enjoying her favorite tilapia and floating peacefully after a good meal, showing her most relaxed side. Manotas is not only a dedicated and resilient mother but also a symbol of the spirit of care and protection that defines Axolotarium.

https://opensea.io/assets/ethereum/0xD039998721df29A20217d076c8B837a9Fc67fDc8/1

Crepita

Sex: MaleAge: 3.5 yearsPhenotype: Leucistic

Crepita is the protective dad of the group, always making sure the youngest eat before he does. With infinite patience and paternal affection, he ensures his family is well and comfortable. His caregivers describe him as a young and loving dad, always concerned about the well-being of his little ones.

https://opensea.io/assets/ethereum/0xD039998721df29A20217d076c8B837a9Fc67fDc8/3

Mango

Sex: FemaleAge: 2 yearsPhenotype: Golden Albino

Mango, with her brilliant golden albino color, is one of Axolotarium's most admired axolotls. Her curious and playful personality makes her stand out: she's more active and extroverted than her sister Vainilla, as well as being healthier and considerably larger. Always ready to socialize, Mango is Manotas' inseparable friend and especially enjoys fresh fish.

https://opensea.io/assets/ethereum/0xD039998721df29A20217d076c8B837a9Fc67fDc8/4

Godzilla

Sex: FemaleAge: 1.5 yearsPhenotype: Brown

Godzilla is pure love... and pure appetite! She was the one who grew fastest among her siblings, and it's no surprise: as soon as someone approaches with pellets or worms, she's already in the front row moving her gills with excitement. She loves hiding in her little cave, but if she sees bubbles in the water, she comes out to chase them as if they were her favorite toy. She's a curious little axolotl who loves having fun.

https://opensea.io/assets/ethereum/0xD039998721df29A20217d076c8B837a9Fc67fDc8/5

Tintin

Sex: MaleAge: 1.5 yearsPhenotype: Leucistic

Since he was a baby, Tintín has been inseparable from his caregiver Nicole. He recognizes her as soon as she appears at the laboratory and swims excitedly to greet her and ask for food. He's so smart he even seems to understand what they tell him. Among all his siblings, he's the most observant, curious, and sociable. The cutest thing is that sometimes he stays with Nicole while listening to music... his favorite: Pink Floyd. A little axolotl with very good taste!

2. Local Peso Sponsorship – Axolobebés

Contribute to the care of the 24 axolotls in the special physical sponsorship program.

For a monthly fee of $480 MXN, you will receive:

• A personalized digital certificate

• Monthly photos and videos of your axolotl

• The opportunity to choose its name (if it doesn't have one yet)

• A guided visit to meet it in person

• Additionally, an Axolocard will be generated in its honor

Help conserve this unique species!

Write to the Axolotarium team for more information or to start the sponsorship process. (Only available in México with transfer in pesos via SPEI)

As part of the closing of this first incubation phase, Zenbit and Axolotarium are currently working on formalizing a collaboration agreement that will allow for the continuity of the progress made and the implementation of the three remaining milestones of the program: treasury management, on-chain implementation, and decentralized financing. These objectives are scheduled to be developed during the second half of 2025, thus consolidating a decentralized, sustainable, and replicable operating model for biological conservation centers.

From Zenbit, we extend an open invitation to organizations, academic institutions, scientific communities, and actors in the Web3 ecosystem to join this cause. Supporting the conservation of the axolotl through Axolotarium, as well as other centers dedicated to preserving endemic species, is also a bet on a future where biodiversity, open science, and decentralized technology are articulated to generate real and measurable impact. We firmly believe that the microDAO model can serve as an effective vehicle for scientific projects, conservation initiatives, and early-stage university ventures that have not yet consolidated their business model, but that have a clear vision and a genuine commitment to solving urgent challenges.

We invite these initiatives to explore the possibilities offered by on-chain technologies: from operational traceability and participatory governance to access to decentralized funding and global visibility. At Zenbit, we are committed to accompanying these processes and facilitating the adoption of digital infrastructures that allow more projects to prosper under principles of transparency, autonomy, and sustainability. The axolotl, a symbol of resilience and regeneration, inspires us to imagine and build together more just, collaborative, and decentralized ecosystems.

This Development Report documents the engineering process behind the OPcity Fault Proofs system, a functional prototype implemented on the OP Stack. The system architecture integrates modular components influenced by state-of-the-art approaches from projects such as Canon FPVM, opML, and DAVE.

The initial system design was structured around four interoperable layers: Execution, Intelligence, Privacy, and Verification. Each layer introduced specialized capabilities, ranging from RISC-V-compatible deterministic execution and predictive optimization to selective zero-knowledge privacy and adversarial dispute resolution. However, for this development phase, the implementation scope was deliberately constrained to a minimal but impactful subset of eight features that could be tested, validated, and benchmarked in real environments.

While the Privacy Layer was originally conceived to introduce zero-knowledge proof support and model partitioning, its implementation has been deferred to a future phase. Similarly, the planned extension of the Execution Layer to support RISC-V alongside MIPS remains a future milestone, intended to enhance compatibility and performance across diverse virtual machine environments. This decision helps maintain focus on verifiable system correctness and core protocol stability.

The OPcity project started as the exploration to integrate machine learning within the fault proof system. Drawing inspiration from opML’s multi-phase fraud-proof mechanism and Canon FPVM’s interactive dispute model, we aimed to investigate whether ML inference could enhance dispute resolution by introducing adaptive state transitions or predictive optimizations.

However, our research and experimentation revealed that no current ML component meaningfully improves the core performance or correctness of fault proof systems. As a result, no machine learning-specific features from opML were implemented in this phase. Nevertheless, structural enhancements introduced by opML—such as the multi-phase dispute resolution and the lazy loading manager—were retained and integrated into the OPcity prototype. These features contribute to improved modularity and computational efficiency without requiring probabilistic or non-deterministic processes. The computational complexity, unpredictability, and lack of deterministic guarantees in ML models conflict with the strict reproducibility requirements of fault-proof execution environments.

Our evaluation found that our opML-based implementation is not strictly superior to existing fault proof systems. However, it offers meaningful trade-offs in modularity, granularity, and execution strategy, making it a compelling experimental path. As part of this exploration, we focused specifically on multi-phase fault proof systems inspired by both opML and DAVE. As a result, the OPcity prototype incorporates two distinct multi-phase dispute resolution mechanisms—each fully compatible with the current OP Stack—that demonstrate different approaches to layered dispute workflows and verifier coordination.

Original Proposed Modifications

The initial OPcity framework proposed a unified fault proof system capable of integrating deterministic machine learning inferences directly into the Canon FPVM architecture. While these proposed modifications were not implemented due to the incompatibility of ML with the deterministic constraints of fault proof systems, they provided a valuable conceptual foundation for assessing system’s extensibility.

• Memory Management and System Modeling

  Proposed extensions for memory management, such as ML-related batching, caching, and dynamic loading, were not pursued due to the lack of a compelling ML integration path. The FPVM continues to employ deterministic memory structures consistent with its canonical specification.

• Syscalls and I/O Extensions

  No additional syscalls or I/O structures for ML model interaction were added. The current system maintains compatibility with standard OP Stack data pipelines and syscall interfaces.

• Formal Verification and Error Propagation

  With ML components excluded, formal verification efforts focused exclusively on the deterministic and adversarial game logic of the FPVM. This narrowed scope allowed for more rigorous validation of dispute behavior and reduced the complexity of exception handling.

Implemented Modifications

The actual modifications in the OPcity Stack prototype represent a pragmatic adaptation of the original design objectives into features compatible with the OP Stack fault proof pipeline. These features aim to extend execution scalability, dispute resolution flexibility, and performance optimizations, all while preserving determinism and reproducibility.

At the core of the system is Optimism’s Canon FPVM, which functions as the base execution and dispute environment. All other enhancements, including the multi-phase dispute resolution mechanisms inspired by opML and DAVE, are layered on top of this canonical foundation to ensure compatibility and reusability within the OP Stack.

Base Layer from Optimism’s Canon FPVM

1. OP-cannon: The core execution engine responsible for running and verifying the Layer 2 transition state using the Canon FPVM framework.

2. OP-challenger: The dispute mechanism client that interacts with the OP-cannon by initiating challenges against invalid state transitions during fault proof validation.

3. Multi-threaded dispute resolution: An extension that enables concurrent processing of multiple disputes within the Canon FPVM environment, improving throughput and enabling parallel challenge game execution.

opML inspired Multi-Phase mechanism

1. Multi-phase dispute resolution: A layered challenge mechanism implemented over the Canon FPVM that segments disputes into coarse-grained and fine-grained phases, reducing verification complexity while maintaining deterministic execution.

2. Lazy loading manager: A memory optimization component that loads data on demand rather than upfront, reducing memory consumption and improving efficiency, particularly during Phase 1 state bisection.

DAVE inspired Tournament-based mechanism

1. Tournament structure: A permissionless, hierarchical challenge process layered atop Canon FPVM, where disputes escalate through successive rounds before reaching final resolution.

2. Parallel dispute games: Enables multiple independent fault dispute games to run simultaneously within the same underlying Canon environment, enhancing scalability and reducing bottlenecks.

3. Incentive mechanisms: Incentives economic alignment to ensure honest behavior across dispute participants, through rewards and penalties schemes tied to correct or incorrect resolution outcomes.

4. Cross-architecture trace verification (RISC-V support):

   The DAVE implementation introduces a modular off-chain trace system that supports both MIPS (used by Cannon) and RISC-V (used in Cartesi-style VMs). This is achieved through a unified interface defined in trace_provider.go, with RISC-V trace generation implemented in riscv_trace_provider.go. These components allow the op-challenger to produce execution traces and witness proofs for either architecture, enabling architecture-agnostic dispute resolution within the same tournament flow. The system is designed to be extendable for future virtual machines, laying the groundwork for flexible, future-proof fraud proof systems in rollup ecosystems.

Future Considerations: Privacy

The Privacy Layer, initially outlined in the project blueprint, is intended to introduce selective zero-knowledge proofs and model partitioning to enable protected computations. These features will improve the system’s capacity to handle sensitive inputs and outputs in a verifiable yet private manner. This upgrade will allow the OPcity FPVM to process a wider range of computation models, increasing its extensibility and alignment with industry trends in modular virtual machines.

The following sections of this report detail the development process, technical architecture, and testing methodology. This report serves both as implementation documentation and as a contribution to the broader rollup ecosystem, offering insights for future work on scalable and modular fault proof systems.

2. OPcity’s Fault Proof system design

This section outlines a system design for enhancing Optimism’s fault proof system by integrating two complementary dispute resolution mechanisms: a multi-phase protocol inspired by opML and a tournament-based model adapted from Cartesi’s DAVE. Implemented without any machine learning components or native execution dependencies. The combined approach aims to improve the efficiency, scalability, and resource utilization of Optimism’s fault proof architecture while preserving its core security guarantees.

Optimism’s current system relies on a single-phase bisection protocol using the Cannon Fault Proof Virtual Machine (FPVM), which can become resource-intensive and suboptimal for resolving complex or large-scale disputes. To address this, OPcity adopts a multi-phase resolution framework that segments the dispute process into distinct phases—beginning with coarse-grained segment validation and narrowing down to instruction-level verification only when necessary. This structure improves modularity and allows partial verification paths to be short-circuited when possible, reducing redundant onchain computation.

In parallel, OPcity incorporates a tournament-style resolution layer inspired by DAVE. This design allows multiple independent dispute games to evolve concurrently and escalate through structured arbitration rounds. Disputes are resolved via adversarial interactions, where honest participants are incentivized, and invalid claims are disincentivized through staking and penalties. The tournament structure supports asynchronous convergence, enabling high-throughput dispute resolution across a decentralized verifier network.

Both mechanisms are layered atop the existing Cannon FPVM environment and maintain full compatibility with OP Stack components such as the Dispute Game Protocol and the Preimage Oracle. Together, these enhancements provide a scalable and modular framework for fault proofs, with clearly defined implementation milestones and integration points within the OP Stack.

System Goals

The primary goals of this system design are to:

1. Improve the efficiency of dispute resolution in Optimism's fault proof system

2. Reduce computational and memory overhead during the dispute resolution

3. Enhance scalability for complex state transitions

4. Maintain or improve security guarantees

5. Ensure compatibility with the existing OP Stack components

Proposed OPcity Architecture

The OPcity architecture extends the foundational components of Optimism’s fault proof system and extends it with two advanced dispute resolution mechanisms: a multi-phase challenge protocol inspired by opML and a tournament-based resolution model adapted from Cartesi’s DAVE. Both mechanisms are layered atop the Canon FPVM and are fully compatible with the OP Stack’s core infrastructure, including the Dispute Game Protocol, Preimage Oracle, and Cannon verifier.

While both mechanisms pursue the same core goals—modular verification, efficient state narrowing, and decentralized resolution—they they diverge in terms of in dispute granularity, execution path, and verifier interaction.

The opML-inspired design segments disputes into hierarchical verification phases, enabling progressively granular resolution. In contrast, the DAVE mechanism models dispute resolution as a permissionless tournament, where multiple challenges can evolve and converge asynchronously. Together, they form a modular and extensible architecture for fault proof verification, capable of addressing a wide range of dispute patterns in high-throughput rollup environments.

Optimism's Fault Proof System

Optimism's current fault proof system employs a modular design centered around the Cannon Fault Proof Virtual Machine (FPVM) and a dispute game protocol. the key components include:

1. Fault Proof Program (FPP)

   The FPP is responsible for executing and verifying the correctness of state transitions. It identifies discrepancies between the claimed and actual states, serving as the core logic for fault detection.

2. Cannon FPVM

   Cannon is the default FPVM used in Optimism's dispute resolution process. It emulates a minimal Linux environment on the MIPS32 architecture to generate execution traces and witness proofs for disputed instructions. It consists of:

   • Onchain MIPS.sol: A Solidity-based verifier that executes a single MIPS instruction to confirm the correctness of an offchain proof.

   • Offchain mipsevm: A Go based emulator of the MIPS environment, capable of producing proofs for any instruction.

3. Dispute Game Protocol

   The current dispute game protocol involves a single-phase bisection process where disputes over state transitions are bisected down to a single instruction. The process includes:

   • Identifying the root instruction of disagreement via a bisection game.

   • Generating a witness proof containing all data needed for onchain execution.

   • Executing the instruction onchain in MIPS.sol to verify the result.

4. PreimageOracle

   The PreimageOracle interface maps hash-based claims to their corresponding preimages, which are essential for validating the correctness of state transitions. It supports multiple key types and supplies required preimages for hash claims used in dispute games.

opML inspired Multi-Phase mechanism

The opML framework introduces a multi-phase dispute resolution protocol that segments the verification process into multiple stages, each optimized for different computational environments and data granularities. The OPcity design integrates:

1. Phase Segmentation

   The dispute resolution process is segmented into multiple phases:

   • Phase 1: Performs coarse-grained verification of large computation segments.

   • Phase 2: Conducts fine-grained analysis to isolate the specific erroneous step within a smaller, disputed segment.

2. Enhanced Bisection Protocol

   An iterative process that progressively narrows the disputed computation segment:

   • In Phase 1, the verifier challenges large computation chunks.

   • When a discrepancy is detected, the challenge is refined to a smaller segment.

   • The process continues until the dispute is localized to a single instruction or micro-operation

3. State Transition and Merkle Trees

   The system models computation as a state transition function, with Merkle trees representing the VM states at each step, enabling efficient verification of complex state transitions.

The diagram below ilustrates the interaction between onchain and off-chain components within the opML-inspired Multi-Phase mechanism of the OPcity architecture. It highlights how different modules coordinate across trust boundaries to enable scalable, deterministic, and phase-separated fault proofs.

Color Key:

• 🟥 Red components: Core components from Optimism’s Canon FPVM

• 🟦 Blue components: Modified components adapted to support multi-phase logic

• 🟨 Yellow components: New components introduced by the OPcity implementation

https://zora.co/coin/base:0x34f5ebe2e4451661630e0d1e8113b2d0513c3351

The following sequence diagram presents the complete procedural flow of a dispute within the opML-inspired Multi-Phase system in OPcity. It complements the component-level architecture diagram by detailing message passing, verification boundaries, and phase transitions, while aligning with the canonical rules defined in the protocol specification.

Multi-phase Dispute Resolution Flow:

1. Dispute Initiation

• The Proposer submits a state transition claim.

• The Challenger submits a challenge against the claim, triggering the creation of a DisputeGame instance.

• The Multi-Phase Resolver initializes the dispute process and queries the Phase Selector.

1. Phase 1: Coarse-Grained Verification

   • If the Phase Selector determines the dispute spans a large segment, Phase 1 is selected.

   • The Phase 1 Verifier begins by requesting coarse-grained state data from MIPS.sol and validating it using Merkle tree proofs.

   • Claims and challenges in this phase follow the format of:

struct Phase1Claim {
    bytes32 stateRoot;
    uint256 startIndex;
    uint256 endIndex;
    bytes32 claimHash;
}

struct Phase1Challenge {
    uint256 challengeIndex;
    bytes32 expectedStateRoot;
    bytes32 challengerBond;
}

• The verifier performs recursive bisection of the disputed range. At each step, Merkle proofs are exchanged, and state roots are verified.

• Once a segment of disagreement is identified and narrowed below the PHASE_TRANSITION_THRESHOLD, the system prepares for Phase 2.

1. Transition to Phase 2

   • The Multi-Phase Resolver invokes transitionToPhase2(), preserving the current state context and segment boundaries.

   • The Phase Selector updates the dispute state and notifies relevant components of the phase shift.

transitionToPhase2(disputeId, segmentStart, segmentEnd, segmentStateRoot);

This ensures:

• State roots and segment boundaries are preserved.

• Bonds and roles remain intact.

• Phase context is correctly recorded.

1. Phase 2: Fine-Grained Verification

   • The Phase 2 Verifier requests fine-grained state data and performs bisection at the instruction level.

   • Claims and challenges in this phase follow:

struct Phase2Claim {
    bytes32 preStateRoot;
    bytes32 postStateRoot;
    uint256 instructionIndex;
    bytes32 witnessHash;
}

struct Phase2Challenge {
    uint256 instructionIndex;
    bytes32 expectedPostStateRoot;
    bytes32 challengerBond;
}

• Once the disputed instruction is isolated, it is executed using MIPS.sol, with the result compared to the claimed post-state.

• The PreimageOracle may be queried to resolve any missing hashed values used in the instruction.

(success, postStateRoot) = MIPS.executeInstruction(preStateRoot, instructionIndex, witnessData);

• A match between computed and claimed state results in Proposer victory; otherwise, the Challenger prevails.

5. Dispute Resolution

• Once a result is obtained, it is submitted to the Multi-Phase Resolver.

• The Dispute Game contract emits a final result event and notifies both the Proposer and Challenger of the outcome.

opML Multi-Phase Mechanism: Trade-offs Summary

The opML-inspired multi-phase dispute resolution introduces notable improvements in scalability, modularity, and efficiency. However, these benefits come with trade-offs that must be carefully managed to maintain system integrity, security, and OP Stack compatibility.

Performance vs. Security

• ✅ Improved performance through selective execution avoids full VM runs in every dispute.

• ⚠️ Trade-off: Increased complexity in handling phase transitions and state consistency.

• 📌 Mitigation: Formal verification of transition logic and rigorous testing of lazy-loaded state segments ensures security without sacrificing speed.

Complexity vs. Efficiency

• ✅ Modular components and memory optimization (via Lazy Loading Manager) improve efficiency and resource use.

• ⚠️ Trade-off: Increased system complexity and higher integration/testing burden.

• 📌 Mitigation: Interfaces are clearly defined, with strict separation of concerns and exhaustive unit/integration testing per phase.

Compatibility vs. Innovation

• ✅ Maintains compatibility with core OP Stack components (e.g., Dispute Game, Preimage Oracle, MIPS.sol).

• ⚠️ Trade-off: Limits the scope of optimization and innovation when working within legacy structures.

• 📌 Mitigation: New components (e.g., MultiPhaseResolver, PhaseSelector) were designed for minimal disruption, with migration paths and interface-based extensibility

DAVE’s Tournament-Based Dispute Resolution

The DAVE (Decentralized Adversarial Verification Engine) framework introduces a scalable, permissionless tournament model for fault proof resolution. Unlike bisection-based protocols, DAVE enables multiple, concurrent challenge games to evolve in parallel through modular arbitration rounds. Key components of this approach include:

1. Tournament Structure

   Dispute resolution is structured as a multi-round tournament, where participants engage in a controlled structured escalation:

   • Initial claims are submitted and stored onchain.

   • Challengers may initiate parallel dispute branches by submitting counter-claims.

   • Rounds proceed iteratively until only one valid dispute path remains, which determines the final result.

2. Parallel Dispute Games

   DAVE supports simultaneous execution of multiple independent fault proof games:

   • Each dispute instance runs in isolation, reducing contention.

   • A shared arbitration layer tracks progress and enforces round-based resolution.

   • Disputes converge asynchronously toward resolution without global coordination bottlenecks.

3. Incentivized Resolution Layer

   The protocol integrates a game-theoretic mechanism to ensure honest behaviour:

   • Participants are required to stake collateral when submitting or challenging claims

   • Honest actors are rewarded upon successful resolution

   • Malicious or incorrect claims result are penalized via slashing and exclusion from future participation

4. Modular Dispute Contracts

   The dispute coordination logic is handled through composable smart contracts:

   • Tracks state progression across rounds.

   • Manages dispute game lifecycles and challenge resolution outcomes.

   • Designed to plug into existing OP Stack protocols without requiring structural changes

5. RISC-V Trace Provider Support

   DAVE off-chain components introduce a RISC-V-compatible trace and proof generation, enabling architecture-agnostic verification flows:

   • riscv_trace_provider.go delivers execution traces, witness proofs, and state transitions for RISC-V-based disputes

   • trace_provider.go abstracts architecture details, enabling unified interaction with MIPS and RISC-V traces

   • types.go defines standardized interfaces and types to allow smooth emulator interoperability and system-wide extensibility

   This implementation allows the OPcity-DAVE module to support cross-architecture tournament-style fraud proof games, paving the way for more expressive and future-proof virtual machine support within the fault dispute resolution.

   The diagram below visualizes the integration of the DAVE tournament-based dispute resolution system into the broader OP Stack architecture. It illustrates how newly implemented components—such as Tournament Contracts, the Tournament Factory, and the off-chain Trace Providers—interact across Ethereum Layer 1, the OP Stack’s off-chain infrastructure, and Layer 2.

https://zora.co/coin/base:0xf0b7d8dc8f8bf12f0b76ff1272deebfc60458b56

The following sequence diagram illustrates the lifecycle of a dispute within the DAVE (Decentralized Adversarial Verification Engine) system, as implemented in the OPcity prototype. It shows how a proposed L2 output can be challenged via a tournament game deployed onchain, how execution traces are retrieved off-chain, and how dispute matches are processed until a final result confirms or rejects the output.

Tournament-based Dispute Resolution Flow:

1. L2 Output Proposal

The op-proposer submits a state root claim via proposeL2Output(output) to the L2OutputOracle. This iniates the challenge period:

function proposeL2Output(bytes32 outputRoot, uint256 l2BlockNumber, ... ) external {
    require(_withinChallengeWindow(l2BlockNumber), "Challenge window closed");
    outputs.push(OutputProposal({
        outputRoot: outputRoot,
        ...
    }));
}

2. Challenge and Game Initialization

If challenged, the op-challenger initiates a dispute:

function createGame(GameType gameType, bytes32 rootClaim) external returns (address) {
    address game = _deployGame(gameType, rootClaim);
    emit GameCreated(gameType, rootClaim, game);
    return game;
}

To generate the trace:

// From trace_provider.go
func (p *RISCTraceProvider) GenerateTrace(blockNumber uint64) ([]Instruction, error) {
    ...
    return trace, nil
}

Then the tournament is created onchain:

function createTournament(bytes32 rootClaim) external onlyFactory {
    ...
    tournaments[rootClaim] = Tournament({ ... });
    emit TournamentCreated(rootClaim);
}

3. Tournament Progression

Participants use joinTournament(claim) to engage in the bracket:

function joinTournament(bytes32 claim) external payable {
    require(msg.value == BOND_AMOUNT, "Invalid bond");
    _addPlayerToBracket(msg.sender, claim);
}

Tournament logic enforces match progression:

function resolveMatch(uint256 matchId) external {
    Match storage m = matches[matchId];
    bytes32 winner = _evaluateMatch(m.claimA, m.claimB);
    m.winner = winner;
    emit MatchResolved(matchId, winner);
}

4. Dispute Resolution

Once the tournament concludes:

function resolveDispute(bytes32 result) external onlyTournament {
    Output storage o = outputs[dispute.outputIndex];
    if (result == o.outputRoot) {
        o.status = Confirmed;
    } else {
        o.status = Rejected;
    }
    emit OutputResolved(dispute.outputIndex, o.status);
}

Supporting Off-Chain Components

The DAVE system depends on modular, architecture-agnostic off-chain services:

• trace_provider.go: Supplies MIPS and RISC-V traces.

• agent.go, manager.go, player.go: Automate agent actions and tournament lifecycle.

• match_monitor.go: Optimizes match selection and monitoring.

• riscv_trace_provider.go: Generates step-level traces for Cartesi-style VM execution.

3. OPcity Implementation

The third milestone of the OPcity project delivers a fully functional prototype that integrates two complementary fault proof mechanisms into the OP Stack: a multi-phase dispute resolution system inspired by opML and a tournament-based resolution framework adapted from Cartesi’s DAVE. This implementation extends the canonical Cannon FPVM architecture while preserving deterministic execution and protocol compatibility.

While the full documentation, system design files, and implementation artifacts are maintained in the OPcity repository, it was necessary to fork the Optimism monorepo in order to enable core fault proof components—such as the dispute game contracts, FPVM interfaces, and challenger logic—and to build functional extensions fully compatible with the OP Stack. This approach ensured that both mechanisms could be developed, tested, and benchmarked in a real-world rollup execution environment without compromising modularity or core system integrity.

Together, they showcase how opML’s phase-based refinement and DAVE’s economically incentivized tournaments can coexist within a cohesive protocol, enabling scalable, parallel, and architecture-agnostic fault resolution. All components were developed with strict attachment to reproducibility, determinism, and OP Stack integration standards.

Milestone 3: OPcity Proof of Concept

[Feature/opML] Multi-phase Dispute Resolution

Closed Issues / Pull Request

Zenbit/OPcity:

• [opML] Multi-phase Dispute resolution #38

Zenbit/Optimism:

• [opML] Multi-phase Dispute resolution #1

Files changed on Zenbit/Optimism

1. op-challenger/game/fault/types/position.go

   The commit exports the parent method of the Position type by renaming it from parent() to Parent(), and updates all internal references to use the new name. In Go language, this enables other packages access to the parent position of a Position instance by make it public the access.

2. packages/contracts-bedrock/interfaces/dispute/ICanonFPVM.sol

   ICanonFPVM.sol introduces a critical interface for handling instruction, execution and verification in the fault proof mechanism, forming the foundation for dispute resolution logic in the protocol.

3. packages/contracts-bedrock/interfaces/dispute/IMultiPhaseResolver.sol

   IMultiPhaseResolver.sol is an interface for managing, tracking, and resolving disputes across a two-phase process. It includes all necessary protocol events and function signatures for managing multi-phase dispute resolution, for robust, onchain challenge-response games.

4. packages/contracts-bedrock/interfaces/dispute/IPhaseSelector.sol

   IPhaseSelector.sol is an interface that provides a standardized interaction with a contract that manages dispute resolution phases, including:

   • Selecting the appropriate phase.

   • Verifying state roots for dispute segments.

   • Managing and querying the transitions thresholds.

   It is intended for use in more complex dispute resolution mechanisms, likely found in rollup or optimistic execution environments.

5. packages/contracts-bedrock/src/dispute/MultiPhaseResolver.sol

   MultiPhaseResolver.sol is a contract that implements a structured, two-phase process to resolve disagreements about state roots, allowing for efficient narrowing of disputes and final resolution through instruction execution. It is modular, leveraging external contracts for verification and execution at each step.

   Key Features

   • createDispute: Starts a new dispute between a proposer and a challenger.

   • submitPhase1Claim/challengePhase1Claim/bisectPhase1Claim: Allow participants to submit claims, challenge, and bisect segments during Phase 1.

   • transitionToPhase2 / _autoTransitionToPhase2: Assigns the dispute to Phase 2 when the segment is sufficiently narrow.

   • submitPhase2Claim/challengePhase2Claim: Handles claims and challenges at the instruction level in Phase 2.

   • executeDisputedInstruction: Executes a disputed instruction using an external FPVM (Fraud Proof Virtual Machine) and resolves the dispute based on the result.

   • resolveDispute / _resolveDispute: Marks the dispute as resolved and records the winner.

   • getDisputeDetails / getBisectionStep: View functions to retrieve dispute and bisection details.

   • Modifiers & Access Control: Only the proposer or challenger can interact with dispute functions. Certain functions are restricted to specific dispute phases.

   External Integrations

   • Phase Selector: Verifies segment state roots.

   • Cannon FPVM: Executes and verifies disputed instructions.

   • Fault Dispute Game: Notified when a dispute is resolved.

6. packages/contracts-bedrock/src/dispute/PhaseSelector.sol

   PhaseSelector.sol  is a utility contract designed to route disputes to different resolution phases based on complexity and manages verified segment state roots, with update controls restricted to the contract owner

   Key Features

   • Phase Management: Determines whether a dispute should be handled in Phase 1 or Phase 2, based on the complexity of the dispute and a configurable threshold.

   • State Root Verification: Verifies and registers state roots associated to dispute segments.

   • Configurable Thresholds: Enables the contract owner to update the threshold that triggers a transition between dispute phases.

   • Access Control: Only the contract owner can register verified state roots and update the phase transition threshold (leveraging OpenZeppelin’s Ownable).

[Feature/opML] Off-chain Components

Closed Issues / Pull Request

Zenbit/OPcity:

• [opML]Off-chain components #39

• [opML] Lazy Loading Manager #40

Zenbit/Optimism:

• [opML] Off-chain Components #2

Files changed on Zenbit/Optimism

1. op-challenger/game/fault/types/position.go

   position.go makes the parent method publicly accessible by renaming it to Parent .

2. op-challenger/game/multiphase/engine.go

   engine.go introduces an extensible dispute game engine for managing multiphase workflows, with support for smart contract interactions.

3. op-challenger/game/multiphase/lazy_loading_manager.go

   lazy_loading_manager.go Implements an efficient, thread-safe, and memory-conscious loading of state data needed for game dispute resolution, using a combination of caching and lazy loading from onchain resources. It is designed to optimize memory and performance during dispute resolution by:

   • Reducing redundant blockchain state fetches from the blockchain.

   • Managing memory usage via a capped, LRU-evicted in-memory cache.

   • Providing monitoring statistics to evaluate cache efficiency.

4. op-challenger/game/multiphase/phase1_verifier.go

   phase1_verifier.go implements a scalable, mechanism for identifying and validatingstate discrepancies over large segments through:

   • Bisecting the segment recursively (divide-and-conquer search).

   • Using a lazy-loading cache to speed up state retrieval.

   • Falling back to local state computation (with Cannon VM) when needed.

   • Isolating the segment needing more detailed (phase 2) verification.

   This approach speeds up dispute resolution in optimistic rollup games, minimizing onchain computation and network calls.

5. op-challenger/game/multiphase/phase2_verifier.go

   phase2_verifier.go provides the logic required to:

   • Precisely pinpoint the faulty instruction within a disputed state segment.

   • Verify the validity of each transition using deterministic VM execution.

   • Generate cryptographic witness data for use in protocol-level dispute resolution.

   This is a critical component for secure, efficient, and transparent optimistic rollup fault proofs and dispute games.

6. op-challenger/game/multiphase/phase_selector.go

phase_selector.go Implements automated logic top to determine which phase of verification should be used for Optimistic dispute resolution. This is based on:

• Checking onchain game outcomes for the relevant state segment.

• Selectic fast, segment-based checking if a finalized game supports the state root.

• Otherwise, requiring slower, fine-grained instruction verification.

This helps optimize the dispute process by avoiding unnecessary detailed checks when recent onchain results can be reused.

[Feature/DAVE] Tournament based Contracts

This feature enables robust, permissionless, and highly modular tournament-based dispute games for fraud proof systems, representing a significant advancement towards scalable, parallelizable, and economically secure dispute resolution on OP Stack/Cartesi. The new contracts and interfaces collectively cover everything from low-level game status and type management to high-level deployment, game logic, and factory-driven extensibility.

Closed Issues / Pull Request

Zenbit/OPcity:

• [DAVE] Tournament structure #41

• [DAVE] Parallel Dispute Games #42

• [DAVE] Incentive Mechanism #43

Zenbit/Optimism:

• [DAVE] Tournament based Contracts #3

Files changed on Zenbit/Optimism

1. packages/contracts-bedrock/interfaces/dispute/IDisputeGameDAVE.sol

   IDisputeGameDAVE.sol defines the required methods and events for any contract implementing a DAVE-based dispute game within the Cartesi/optimism ecosystem, enabling modular, tournament-style fraud proof games.

2. packages/contracts-bedrock/interfaces/dispute/ITournamentGame.sol

   ITournamentGame.sol specifies the structure and functions of tournament-style dispute games in a blockchain context. It defines how participants join, how matches are formed and resolved, and how rewards are distributed, along with a set of events for tracking progress and errors to enforce correct behavior.

3. packages/contracts-bedrock/src/dispute/DisputeGameFactoryExtension.sol

   DisputeGameFactoryExtension.sol is a contract for deploying, tracking, and managing dispute games of multiple types onchain, including both standard and tournament-based games. It ensures that each game is unique, can be easily looked up, and that only authorized contracts or users can register or create games. It supports extensibility by registering new game types. Tournament games are handled specially by integrating with a dedicated TournamentFactory.

4. packages/contracts-bedrock/src/dispute/Tournament.sol

   Tournament.sol is a smart contract that implements a multi-round, power-of-two tournament for dispute resolution, where participants join with a bond and a claim, progressing through via head-to-head matches. At the end, the winner claims the total bond pool. The contract enforces fair participation, time constraints, and valid state transitions, making it suitable for robust, permissionless dispute resolution in systems like Cartesi DAVE.

5. packages/contracts-bedrock/src/dispute/TournamentFactory.sol

   TournamentFactory.sol is an upgradeable factory contract for deploying and managing tournament-based dispute games. It supports both standard and custom tournament parameters, clones or deploys new contracts as needed, ensures system registration with a central factory, and provides easy querying and management of all tournaments. This is a foundational component for scalable, and modular onchain dispute resolution systems.

6. packages/contracts-bedrock/src/dispute/TournamentGame.sol

   TournamentGame.sol is a secure, and extensible smart contract designed to manage bracketed, tournament-style onchain dispute games with real economic incentives. It tracks every participant, match, and round; enforces timeouts and bonds; and guarantees only the legitimate winner can claim the pooled bond. This makes it well-suited for high-stakes fraud-proof protocols such as Cartesi DAVE.

https://github.com/zenbitETH/optimism/pull/3/files#diff-6406356f27eae6b578490a8bc85fb050b331bb50062fa35bb13888e88b8279db

GameTypes.sol is a utility library that defines type identifiers (as constants) and a status enum for dispute games. It ensures consistency and interoperability when referencing game types and their statuses across different smart contracts in both the OP Stack and Cartesi DAVE ecosystem.

[Feature/DAVE] Off-chain components

Closed Issues / Pull Request

Zenbit/OPcity:

• [DAVE] Entire DAVE PoC #48

Zenbit/Optimism:

• [DAVE] Off-chain components implementation #4

Files changed on Zenbit/Optimism

1. op-challenger/game/tournament/agent.go

   agent.go defines the core logic of an automated agent that interacts with the blockchain-based tournament system: joining tournaments, participating in matches, and managing game progression through to completion. It's modular, testable, and built to react dynamically to onchain events and timeouts.

2. op-challenger/game/tournament/contracts.go

   contracts.go abstracts and simplifies all onchain interactions related to tournament dispute games. It provides efficient, thread-safe, execution and high-level access to the tournament game contract, including both state queries and transaction submissions, with built-in caching and error handling.

3. op-challenger/game/tournament/manager.go

   manager.go centralizes all state and interaction logic for tournament dispute games. It provides robust, efficient, and extensible interfaces for game state management, participation, match resolution, and metrics reporting, with special attention to concurrency, caching, and blockchain interaction patterns.

4. op-challenger/game/tournament/match_monitor.go

   match_monitor.go is a concurrency-safe, cache-aware component tracking active matches in a tournament. It helps to prioritize which matches require attention, and provides deadline/complexity utilities. It is essential for automating and optimizing dispute resolution flows in live tournament environments.

5. op-challenger/game/tournament/player.go

   player.go is a strategic, high-level participant in Cartesi tournament-based dispute games. It automates:

   • Game participation,

   • Match handling,

   • Proof generation and validation,

   • Strategic decision making.

   The Player coordinates with lower-level components (Agent, Manager), adheres to resource/concurrency limits, and is designed for robust, autonomous operation in blockchain-based dispute games.

6. op-challenger/game/tournament/riscv_trace_provider.go

   riscv_trace_provider.go plugs into the dispute game framework, to provide execution traces, proofs, and step-wise state transitions in a standardized way, allowing to swap in different machine architectures (here, RISC-V).

7. op-challenger/game/tournament/riscv_trace_provider_test.go

   riscv_trace_provider_test.go serves as a comprehensive test suit of the RISCVTraceProvider’s API surface. It ensures all methods are present, callable, and return the expected results or errors under normal conditions. This is especially valuable given the current placeholder implementations: it establishes a baseline for future development, preserving API correctness. It:

   • Tests all public methods of RISCVTraceProvider.

   • Verifies input/output correctness and error handling.

   • Validates configuration management and the full mock emulator lifecycle.

   • Confirms the provider is robust for future development and real integration.

8. op-challenger/game/tournament/trace_provider.go

   trace_provider.go is a unified interface for trace and proof handling in tournament-style dispute games, supporting step-by-stepxecution trace generation and verification across multiple VM architectures. Key capabilities include details.

   • Unified provider for trace/proof in Cartesi DAVE tournaments.

   • Support for both MIPS64 (Cannon) and RISC-V (Cartesi) architectures.

   • Built-in caching and thread safety for performance.

   • Modular and design extendable to future architectures.

   • Simplified and demo-oriented proof output, with logging for observability.

9. op-challenger/game/tournament/types.go

   types.go is a foundational layer for the tournament dispute game system that defines interfaces and types for trace providers, tournament contracts, transactions, tournament logic (matches, nodes), metrics, and RISC-V emulator configuration. It enables the rest of the system to build strongly-typed, architecture-agnostic, and contract-aware logic for fault proof tournaments.

Milestone 4: Comparative metrics and performance

This section provides a comparative analysis of the OPcity fault proof systems—Multi-Phase and Tournament-based—against the existing OP Stack fault proof model. All metrics are based solely on implemented and verifiable code within the zenbitETH/OPcity and zenbitETH/Optimism repositories. While these figures are grounded in real development artifacts, they are illustrative projections and have not yet been formally benchmarked under standardized test conditions.

The goal of this comparison is to assess how OPcity’s modular enhancements affect contract complexity, dispute flow, and gas efficiency—key factors in the scalability and maintainability of onchain fault proof protocols.

Contract Structure & Codebase Complexity

The OPcity implementations exhibit a significantly reduced code footprint relative to the standard OP Stack fault proof contracts. This reduction is due to their modularity, isolated concern boundaries, and deliberate separation between the onchain resolution layers and offchain trace infrastructure.

Dispute Resolution Flow Comparison

The Multi-Phase mechanism reduces the frequency of onchain MIPS execution by isolating fine-grained verification to Phase 2 only, optimizing onchain usage for simpler disputes. The Tournament-based system introduces parallelism via bracketed games, significantly improving throughput in high-volume scenarios.

Gas Cost Projections (Theoretical)

These estimates show that OPcity’s optimizations can reduce gas usage in common-case disputes (Phase 1-only), while incurring modest overhead during escalation or match resolution. A full benchmarking suite will be required to validate these figures empirically.

The OPcity prototypes show clear improvements in structural modularity and resolution efficiency. The Multi-Phase model introduces dynamic resolution paths that avoid unnecessary VM execution. The Tournament mechanism offers horizontally scalable resolution with built-in economic incentives and cross-architecture trace compatibility. Together, these results validate OPcity’s design hypothesis: that fault proofs can be more scalable, parallel, and modular—without sacrificing correctness or OP Stack compatibility.

Milestone 5: Updates in Social Media

Onchain:

Farcaster

1. OPcity: Research Compilation thread

2. OPcity Research Report thread

3. OPcity Development Report thread

Mirror

1. OPcity: Research Compilation

2. OPcity: Compilación de investigación

3. OPcity: Research Report

4. OPcity: Development Report

Zora

1. OP Stack Protocol Upgrades

2. Fault Proofs Comparative

3. OPcity Multi-phase Fault Proofs

4. OPcity Tournament-based Fault Proofs

Off-chain:

X

1. OPcity Research Compilation thread

2. OPcity Research Report thread

3. OPcity Development Report thread

LinkedIn

1. OPcity Research Compilation

2. OPcity Research Report

3. OPcity Development Report

Milestone 6: OPcity Stack OSS repository

The OPcity GitHub repository serves as the primary workspace for documenting, developing, and reviewing the fault proof systems that power the OPcity prototype. This repository separates the research, design artifacts, and standalone code modules for both the opML-inspired multi-phase mechanism and the DAVE-inspired tournament-based mechanism, enabling modular development and community peer review.

In contrast, the Zenbit/Optimism fork contains the integrated implementation of both fault proof mechanisms within the OP Stack. It is designed to demonstrate functional compatibility with Optimism’s architecture and serves as the candidate repository for submitting an official upgrade proposal to the OP Stack in the coming weeks.

This dual-repository strategy allows for clear separation of concerns:

• zenbitETH/OPcity: Research, specification, and per-mechanism development

• zenbitETH/Optimism: Canonical integration into the OP Stack for validation, benchmarking, and eventual protocol upgrade proposals

Zenbit/Optimism (Integrated OP Stack Implementation)

1. op-challenger/game/Tournament

   Contains the off-chain logic for the DAVE-inspired tournament-based dispute system, including match orchestration (match_monitor.go), automated agents (agent.go, player.go), trace providers (trace_provider.go, riscv_trace_provider.go), and cross-VM execution trace handling.

2. op-challenger/game/Multiphase

   Implements the opML-style multi-phase engine, including recursive Phase 1 bisection (phase1_verifier.go), instruction-level Phase 2 logic (phase2_verifier.go), state handling via the Lazy Loading Manager, and game automation (engine.go).

3. packages/contracts-bedrock/src/dispute

   Contains Solidity contracts for managing disputes across both mechanisms. This includes MultiPhaseResolver.sol, PhaseSelector.sol, Tournament.sol, and TournamentFactory.sol, as well as interfaces and shared utilities for dispute orchestration and protocol upgrades.

Zenbit/OPcity (Research & Module Development)

1. FPVM Research

   Documents design experiments on the Canon FPVM, including proposals for trace extensions, memory architecture, and RISC-V compatibility. Contains detailed architecture diagrams and VM modeling experiments that guided OPcity’s modular VM interaction.

2. Milestone Reports

   Contains published research outputs such as the OPcity Research Report and Development Report. Each report summarizes findings, design trade-offs, benchmarking results, and links to relevant PRs or modules.

3. OPstack Research

   Aggregates protocol upgrade reviews, version benchmarks, and specification mappings across OPstack releases. Includes the comparative protocol upgrade table and supporting notes used to identify compatibility targets for OPcity.

4. OPcity Multi-Phase FP

   Contains the standalone implementation and logic of the opML-inspired multi-phase system. Includes Markdown diagrams, dispute flow descriptions, claim formats, and off-chain strategy notes.

5. OPcity Tournament-based FP

   Provides the design overview and implementation details for the DAVE-style tournament system, including modular claim handling, game rounds, match resolution flow, and RISC-V integration strategy.

Conclusion

The OPcity Fault Proofs project delivers a dual-mechanism prototype that enhances the OP Stack’s dispute resolution architecture through modularity, scalability, and execution extensibility. By combining the opML multi-phase flow and DAVE tournament model, OPcity demonstrates how alternative dispute mechanisms can coexist atop a canonical execution engine (Cannon FPVM), while introducing paths toward RISC-V support, cross-architecture verification, and private proof systems.

Through extensive off-chain infrastructure, robust on-chain arbitration, and carefully scoped design trade-offs, OPcity provides a blueprint for the next generation of modular, fault-proof infrastructure in optimistic rollups. With the full system now integrated into the OP Stack via the zenbitETH/Optimism fork, the next milestone is to propose this work as a formal protocol upgrade for evaluation by the Optimism Collective and broader L2 research community.

Layer 2 (L2) rollups have emerged as a practical solution to Ethereum’s scalability challenges, addressing issues such as cost, capacity, and transaction throughput. Among these, optimistic rollups allow transactions to be executed off-chain while posting minimal data on-chain, thereby preserving decentralization and network security.

The OP Stack, developed by OP Labs and coordinated by the Optimism Foundation, is one of the most widely adopted open-source frameworks for deploying dedicated L2 rollups. Its minimal, and modular architecture allows chains to post periodic state roots to Ethereum (or alternative L1s), relying on optimistic validation. These state roots can be challenged within a seven-day window using Fault Proof mechanisms. A robust and permissionless implementation of these mechanisms is essential to achieving Stage 1 requirements in L2BEAT’s state validation maturity framework.

This research report examines the evolution and implementation of fault proof systems in the OP Stack. It builds on our earlier work, OP City: Research and Optimization of OP Stack Deployments and Canon Fault Proofs VM, and presents findings across three milestones: (1) a comprehensive review of OP Stack upgrades and their impact for fault proofs; (2) a technical analysis of emerging mechanisms like Canon FPVM, opML, oppAI, and DAVE; and (3) a comparative benchmark to assess readiness, performance, and integration paths. Together, these contributions aim to advance the decentralization and resilience of the OP Stack—and, by extension, Ethereum as a truly global computational engine.

Milestone 0: OP stack research

This milestone also included a version benchmark of the OP Stack, conducted through a dual-node deployment to evaluate the performance of rollups built from different configurations and protocol versions. The goal was to compare their behavior under equivalent conditions and identify meaningful differences in efficiency and execution. The results of this test were documented in our previous Mirror article, and the full research process, including setup and data, is available in our GitHub repository.

OP stack background

Before the OP Stack was formalized as a unified, modular framework, its architecture evolved through iterative stages that laid the groundwork for scalable Layer 2 execution. The journey began with the Unipig Demo in October 2019, a proof-of-concept developed in collaboration with Uniswap that showcased the power of Optimistic Rollups. It demonstrated a ~10× increase in throughput and significant reductions in gas fees compared to Ethereum mainnet, proving the concept’s viability.

This was followed by the lauch of SNX Testnet in September 2020, which introduced general-purpose smart contract execution on Layer 2. Transactions ran at approximately ~10% of L1’s cost, with improved latency and faster confirmation times.

In January 2021, the network transitioned into its first mainnet phase—often referred to as the OVM Era—with a version of the Optimistic Virtual Machine that relied on a custom Solidity transpiler. While functional, this setup introduced significant inefficiencies: over 25,000 lines of bespoke code, complex tooling, and inflated state transition costs.

By October 2021, Optimism rolled out the EVM Equivalence Upgrade, a major step forward that removed the transpiler, drastically simplified the execution layer, and brought the network into full compatibility with Ethereum tooling. Throughput increased to ~100 TPS, and developer experience improved significantly. Just two months later, in December 2021, the launch of OP mainnet enable public contract deployment and catalyzing adoption by removing whitelists. This major achievment on open access marked a turning point in Optimism’s growth.

The culmination of these early experiments arrived with the Bedrock Upgrade in june 2023, which replaced legacy OVM components with a leaner, modular, and Ethereum-equivalent design. Bedrock slashed code complexity by ~90%, cut transaction costs by ~30%, and boosted throughput to ~450 TPS—ushering in the era of the OP Stack and laying the foundation for a Superchain of standardized, interoperable rollups.

OP stack protocol upgrades

All referenced documents are available in our open repository for transparency and further review: 🔗 OP Stack Protocol Upgrades Review – Zenbit GitHub

Since the formalization of the OP Stack, the protocol has undergone 15 official upgrades, ranging from foundational architectural transitions to fine-grained feature releases across the OP Stack’s modular layers. Our review spanned 62 curated sources, including governance forum proposals, developer documentation, audit reports, and OP Stack specification entries. These materials were analyzed to trace the evolution of the OP Stack’s dispute system—from the launch of permissionless Cannon-based fault proofs in Protocol Upgrade #7, to the infrastructure pre-requisites for multi-threaded MIPS64 fault games in Upgrades #14 and #15. Sources such as governance threads, public audit reports, and design documents not only clarified technical intent, but also allowed us to assess how each upgrade contributed to meeting Stage 1 decentralization criteria from the L2BEAT framework.

Through this analysis, we identified 13 upgrades with direct impact on the settlement layer, including 8 upgrades that significantly advanced the fault proof system —transforming it from a trusted fallback into a fully modular, permissionless verification layer.

Protocol Upgrade #4 Superchain Config

Superchain Config laid the groundwork for coordinated multi-chain security by introducing a global SuperchainConfig contract on L1. This enabled the Security Council to pause cross-chain operations via an expanded emergency mechanism, extending control beyond withdrawals to include message relays and token bridges. It also included critical fixes—such as closing reentrancy attack vectors—and enhanced L2 token compatibility through deterministic CREATE2 deployments. While not altering fault proof logic directly, this upgrade provided a crucial fallback security layer for fault proof systems, strengthening the OP Stack’s operational resilience.

Protocol Upgrade #7 Fault Proof

The state validation improvements began with Fault Proofs, which marked a foundational shift in the OP Stack’s security model by replacing the previously trusted state root proposer mechanism with a permissionless fault proof system. This upgrade introduced a modular, on-chain binary bisection game powered by the Cannon VM, allowing any participant to propose or challenge state roots. Supporting this dispute flow, key components such as the DisputeGameFactory, AnchorStateRegistry, and bonding mechanisms were deployed. Together, these features enabled the OP Stack to meet the Stage 1 decentralization milestone set by L2BEAT, especially through the integration of a Security Council override to pause withdrawals in emergencies.

Protocol Upgrade #8 Guardian

Guardian introduced formalized guardian governance. This upgrade extended the Security Council’s role by granting them authority over L2 ProxyAdmin control and emergency withdrawal pausing, providing a critical safeguard during fault proof escalation periods. It was a vital step in building the governance infrastructure required for fault proof decentralization, ensuring that challenge games could proceed trustlessly without introducing systemic risk.

Protocol Upgrade #10 Granite

Granite focused on enhancing the protocol infrastructure to support more advanced proof systems. Updates to SystemConfig and dispute game interfaces increased flexibility for challenger clients and made space for introducing alternative VMs, such as MIPS64. These changes future-proofed the OP Stack’s dispute layer, ensuring compatibility with evolving fault proof implementations such MT-Cannon and potential zk variants.

Protocol Upgrade #11 Holocene

As fault proofs moved into production, Holocene standardized the format for L2-to-L1 outputs, refining how withdrawals and challenge games would be validated across chains. These improvements enhanced compatibility with new proof types and helped streamline the verification logic for post-upgrade withdrawals, an essential update as the system transitioned away from trusted third parties.

Protocol Upgrade #12 Pre pectra

In preparation for Ethereum’s Pectra hard fork, Pre-Pectra Readiness introduced important features to support hybrid and forward-compatible proofs. This included access to the L1 Beacon Root, enabling withdrawal verification against Ethereum’s consensus layer, and introduced precompiles like BLS and timestamp access that are critical for next-gen dispute VMs. These changes ensured that fault proofs could continue to operate in a post-Dencun Ethereum environment and opened the door to zk-fault proof hybrids.

Protocol Upgrade #14 Pre Isthmus

This set the stage for Pre-Isthmus, which established the L1 infrastructure for MT-Cannon, a multithreaded, 64-bit evolution of the Cannon VM. Without requiring a hard fork, this upgrade deployed new contracts like OPChainManagerV2, deployed MIPS64.sol, and restructured the fault game logic to support more scalable dispute execution. MT-Cannon could now be tested in production environments in parallel with legacy Cannon, serving as a trial run for the more performant and deterministic VM architecture.

Protocol Upgrade #15 Isthmus

Finally, Isthmus completed the transition by activating MT-Cannon as the canonical fault proof VM. This hard fork integrated Pectra-compatible features, such as support for new precompiles and the inclusion of withdrawalsRoot in L2 block headers, solidifying the OP Stack’s ability to anchor dispute data efficiently. Additionally, it also introduced operator fee fields and formally recognized MIPS64 in dispute logic, ensuring that fault proofs could now run faster, more securely, and with greater parallelism.

https://zora.co/coin/base:0x6e07a6c86e96fa9a0fb3349819675883a1049afa?referrer=0x04cc6b487566B1C821bEa04d7ac0d23CEDe05cC9

Evolution of the Fault-Proof Mechanism

A critical component of the OP Stack’s security model is its fault-proof mechanism, which ensures the validity of Layer 2 state transitions through fraud detection rather than pre-execution verification. The initial implementation featured a monolithic Cannon-based fault proof system, which was later restructured to enhance modularity and reduce reliance on Optimism-specific execution logic.

Key developments in fault proofs include:

• Cannon's Optimized Proof System: Introduced an approach where the execution client compiles directly into the proof system, simplifying the verification process⁵.

• Multi-Client Fault Proofs: A strategic shift toward supporting multiple fault-proof implementations, increasing security resilience and minimizing the risks of single-client reliance⁶.

• Introduction of Stage 1 Decentralization: The Guardian upgrade improved security council threshold mechanisms, decentralizing the governance of fault proofs⁷.

• Settlement Layer Refinement: Modular proof verification was introduced, allowing future upgrades to transition toward ZK-enabled rollups without disrupting OP Stack’s core execution model⁸.

• Modular Fraud Proofs Architecture: A long-term goal of OP Stack fault proofs is modular dispute resolution, allowing new execution clients to integrate their own fraud-proof mechanisms

Milestone 1: Fault Proofs mechanisms research

All referenced documents are available in our open repository for transparency and further review: 🔗 FP research reports – Zenbit GitHub

Fault proofs are a foundational component of optimistic rollups, enabling trustless verification of off-chain state transitions. As the OP Stack advances toward greater decentralization and modularity, the architecture and implementation of fault proof mechanisms have evolved significantly. This milestone documents our research into the key architectures shaping this landscape—beginning with Optimism’s default Canon FPVM, and expanding into cutting-edge systems like opML, oppAI, and Cartesi’s DAVE. Each mechanism offers unique trade-offs between performance, verifiability, and scalability, collectively enriching the design space for secure and efficient Layer 2 systems.

Optimism's Fault Proofs & Canon FPVM

At the core of the OP Stack’s security model lies its Fault Proof system, a cryptoeconomic mechanism that ensures the correctness of off-chain state transitions by enabling anyone to challenge invalid claims posted to Ethereum. This milestone focused on analyzing the evolution of this mechanism, beginning with Optimism’s Canon Fault Proof Virtual Machine (Canon FPVM)—the default system currently securing Layer 2 outputs.

Canon employs a dispute resolution game, where participants engage in an interactive bisection protocol to isolate a single disputed MIPS instruction. The system combines onchain and offchain components: MIPS.sol, a lightweight smart contract that deterministically executes a single instruction, and Cannon, a Go-based offchain VM that computes the state transition trace and generates verifiable proofs. Key elements such as the DisputeGameFactory, AnchorStateRegistry, and OP-Challenger infrastructure coordinate to handle challenges, execute proofs, and enforce results. Memory in Cannon is modeled as a Merkleized 32-bit address space, enabling stateless onchain verification of computation with minimal inputs.

This architecture was tested in production during the release of feature-complete fault proofs on OP Sepolia, and subsequently evolved through multiple protocol upgrades to enhance modularity, precision, and compatibility with Ethereum’s Pectra roadmap. Our technical deep dive revealed strengths—such as deterministic execution, statelessness, and modular game design—but also current limitations, including limited syscall support and high computational overhead.

opML

One of the most forward-looking proposals in fault proof innovation is opML, an optimistic verification system designed to support scalable and verifiable onchain machine learning (ML) inference. Inspired by optimistic rollups, opML replaces expensive zero-knowledge proofs with an interactive fraud-proof process, allowing ML computations to be challenged only when disputed. This approach significantly reduces overhead, making it feasible to run complex models onchain without compromising trust. At its core, opML features a Fraud Proof Virtual Machine (FPVM) optimized for ML workloads, equipped with Merkleized memory and a segmented layout that separates code, input/output buffers, oracle data, and model parameters. This structure supports a full 32-bit address space and deterministic execution, essential for cryptographic verifiability.

The opML architecture consists of four integrated components: the FPVM, a dual-compilation Machine Learning Engine (MLE), an interactive dispute game, and the protocol layer. The MLE is particularly innovative, compiling the same ML source code into two targets: one optimized for high-speed native execution (with GPU/CUDA support), and another for verifiable execution on the FPVM, using fixed-point arithmetic to preserve determinism. With a typical use, trusted actors submit computation results offchain, while verifiers can trigger a two-phase interactive dispute. The first phase isolates disputed computation nodes at the graph level with semi-native execution, while the second drills down into low-level FPVM instructions to prove or disprove correctness.

This multi-phase bisection protocol improves upon Optimism’s single-phase approach by tailoring fraud proof resolution to ML-specific workflows, striking a balance between performance and trust minimization. Disputes are resolved onchain via MIPS-like instructions executed within the FPVM, with proofs derived offchain using opML’s Merkleized memory model. Security is guaranteed through an AnyTrust model, where only one honest validator is needed to contest false claims. Submitters and challengers are incentivized with crypto-economic stakes and penalties to ensure honest behavior.

To further enhance scalability, opML incorporates performance optimizations like lazy loading—loading only required model segments into memory—and semi-native execution, where only disputed segments revert to verifiable computation. This approach enables opML to support large-scale models (e.g. 7B LLaMA) while maintaining verifiability when needed. On the protocol layer, smart contract interfaces manage submission, challenge periods, and dispute resolution workflows, enabling seamless integration with onchain systems. While opML still faces constraints—such as fixed finality windows and memory limitations—it presents a robust pathway for integrating verifiable ML into rollup environments, aligning with the broader goals of modular and decentralized computation.

oppAI

The oppAI framework introduces a novel hybrid architecture that merges the computational efficiency of Optimistic Machine Learning (opML) with the strong privacy guarantees of Zero-Knowledge Machine Learning (zkML). Designed to enable secure, verifiable, and privacy-preserving AI inference on blockchain systems, oppAI addresses the core tradeoff in onchain AI: achieving both performance and confidentiality. By allowing developers to selectively partition AI models into components executed via optimistic or zero-knowledge verification, oppAI provides a flexible system tailored to diverse privacy and cost constraints.

At the core of oppAI lies a dual execution model. Non-sensitive or performance-critical model components are processed via opML’s Fraud Proof Virtual Machine (FPVM), while sensitive logic or proprietary model weights are processed under zkML, using zero-knowledge proofs such as zk-SNARKs. This architecture enables the same AI model to achieve high performance where needed, and high privacy where necessary. The execution workflow begins with a partitioned AI model—e.g., f₁ᵒᵖ, f₁ᶻᵏ, ..., fₙᵒᵖ, fₙᶻᵏ—where each submodel is designated for either optimistic or zk execution. After processing, the results are submitted to an onchain verifier, and a challenge-response game can be initiated if needed.

The oppAI system architecture builds on opML’s foundation and extends it with additional zkML capabilities. It includes components such as:

• The FPVM (adapted from opML) for step-by-step verifiability in optimistic disputes;

• A dual-compiled Machine Learning Engine, supporting both native and FPVM-compatible execution;

• An interactive dispute resolution game for verifying opML results;

• A zkML Prover that generates ZKPs for private components, alongside an onchain Verifier contract to check them.

This design offers direct applications whithin fault proof systems like those used in the OP Stack. First, oppAI enables privacy-preserving fault proofs, allowing sensitive data (e.g. user inputs or proprietary models) to be verified without full exposure. Second, it proposes a hybrid verification scheme where only the most privacy-sensitive operations incur zk costs, while the rest benefit from lower overhead optimistic execution. This creates a more efficient yet secure fraud proof system, especially valuable for increasingly complex computations such as AI oracles or ML-based coordination mechanisms in DAOs and L2 governance.

From a security standpoint, oppAI adopts an AnyTrust model, requiring only a single honest verifier to guarantee system integrity. Its economic security model disincentivizes attacks through dynamic inference pricing, calculated to keep the cost of reconstructing private models prohibitively high. Notably, the system allows tuning the ratio between zkML and opML (represented by p) to balance the tradeoff between privacy and efficiency. Performance benchmarks confirm that reducing zkML usage (lower p) significantly lowers computational overhead while still enabling verification of critical model segments like attention layers in large language models (e.g. Stable Diffusion, LLaMA).

In practical terms, oppAI’s capabilities significantly the scope of OP Stack-based chains by allowing:

• Secure AI oracles, which deliver verifiable predictions to smart contracts without revealing internal logic;

• Privacy-enhanced onchain inference, protecting model IP while maintaining fraud-proof guarantees;

• Support for high-complexity computation, including federated ML, game theory agents, and dynamic governance models.

Despite its advantages, oppAI introduces new design and implementation challenges. Determining the optimal partitioning of model components require privacy demands interdisciplinary knowledge of ML and blockchain. Furthermore, managing performance tradeoffs and adapting to rapidly evolving zkML and opML ecosystems require continual iteration. Nonetheless, oppAI sets a strong precedent for modular, privacy-aware fault proof design—bridging efficient onchain computation with the next generation of decentralized AI applications.

DAVE

DAVE (a name, not an acronym) is Cartesi’s advanced fraud-proof protocol, designed to strengthen decentralization, liveness, and efficiency in blockchain verification. It introduces a permissionless, tournament-style dispute mechanism, offering a compelling alternative to Optimism’s Fault Proofs and Arbitrum’s BoLD.

At its core, DAVE leverages Permissionless Refereed Tournaments (PRT)—a novel framework resitant to Sybil attacks, with constant hardware and bond requirements, and provides exponential resource advantages for honest actors. This design allows that a single honest validator can defend the network—even against coordinated adversaries—at minimal cost.

DAVE operates on top the Cartesi Machine, a deterministic RISC-V emulator that separates execution logic into two layers: a micro-architecture in Solidity and a high-performance offchain computation layer. This dual-layer architecture ensures execution integrity while supporting instructions without inflating the onchain footprint.

Unlike traditional fault proof systems, DAVE employs a tournament-style challenge mechanism, where validators resolve disputes through logarithmically-scaling games. These disputes typically conclude within 2–5 challenge periods, significantly reducing the overhead seen in earlier systems like Cartesi’s own PRT (which could take up to 20 weeks).

Compared to other systems, DAVE offers notable advantages:

• Versus Optimism’s OPFP, it provides stronger Sybil resistance, faster dispute resolution, and lower validator costs.

• Compared to Arbitrum’s BoLD, DAVE maintains similar security guarantees significantly reduced bond requirements (~3 ETH vs. 3,600 ETH).

• Internally, it improves liveness and reduces delay over Cartesi’s prior models while keeping decentralization intact.

DAVE’s flexible architecture allows it to serve both rollups with continuous input processing and compute-focused systems. While it currently relies on the Cartesi Machine, its execution environment agnosticism opens paths for integration with other rollup ecosystems.

Milestone 2: FPVM Comparative Analysis

All referenced documents are available in our open repository for transparency and further review: 🔗 FP research reports – Zenbit GitHub

Originally titled “2. Research on oppAI compatibility with the OP Stack,” this milestone was later renamed to “2. FPVM Comparative Analysis” to better reflect the broader scope of our investigation. While the initial focus centered on oppAI and opML, our research expanded to include a full evaluation of Optimism’s Canon FPVM and Cartesi’s DAVE—both foundational and alternative approaches to fault proof architecture. This milestone presents a structured comparison of these four mechanisms, each tackling a different facet of the fault proof challenge, from deterministic execution and computational efficiency to privacy-preserving inference and decentralized dispute resolution.

Our primary objective is to analyze the tradeoffs in architecture, performance, security, and accessibility, and to propose integration pathways that strengthen the OP Stack’s fault proof system. This comparative research is intended not only as a conceptual evaluation but as a blueprint for the OPcity prototype, guiding future technical contributions to the OP Stack and aligning with the broader mission of building decentralized, modular, and verifiable infrastructure.

Core Architecture Comparison

These systems represent three main verification paradigms. Optimism’s Canon FPVM relies on deterministic execution using a lightweight MIPS VM and binary bisection games. opML enhances this by integrating ML-based prediction to streamline verification. oppAI extends opML by adding selective zkML to protect privacy-sensitive components. Meanwhile, Cartesi’s DAVE diverges with a tournament-based architecture running on a full RISC-V emulator, prioritizing permissionless participation and Sybil resistance.

1. Execution Environment:

• Optimism uses a MIPS-based VM for its simplicity and determinism

• Cartesi employs a more powerful RISC-V emulator with two-layer implementation

• opML works within existing VMs but adds ML capabilities

• oppAI partitions execution between zkML and opML components

2. Verification Approach:

• Optimism uses a traditional bisection protocol to narrow disputes

• opML enhances verification with machine learning predictions

• oppAI selectively applies zero-knowledge proofs for privacy-critical components

• DAVE implements tournament-style verification to improve decentralization

3. State Representation:

• All systems use Merkle trees for state representation, but with different implementations

• Optimism and Cartesi focus on complete state transitions

• opML and oppAI allow for partial verification of specific components

https://zora.co/coin/base:0x9e365da701c63481ad70ecc7583c982be44c606d?referrer=0xeCB4C1245665e8A1F43826355aaB0Dd6bF336e05

Performance and Efficiency Analysis

While Canon FPVM sets a reliable baseline, its simplicity constrains scalability. opML reduces computational load via ML-enhanced execution, offering performance improvements without altering core architecture. oppAI introduces more variable overhead due to zkML, but allows developers to balance privacy and efficiency by configuring which sub-models require zero-knowledge proofs. DAVE’s structure ensures that honest participants incur low costs even in worst-case scenarios, making it well-suited for decentralized validator environments.

1. Computational Requirements:

• Optimism's Canon requires full execution of disputed transactions

• opML reduces computation through predictive models

• oppAI optimizes by applying heavy computation only to privacy-sensitive parts

• DAVE minimizes honest validator costs regardless of adversary resources

2. Verification Time:

• Optimism's verification time scales with computation complexity

• opML potentially accelerates verification through ML predictions

• oppAI's verification time varies based on privacy requirements

• DAVE guarantees resolution in 2-5 challenge periods regardless of adversary count

3. Resource Asymmetry:

• DAVE provides the strongest resource asymmetry, giving honest validators exponential advantage

• opML offers efficiency advantages through prediction

• oppAI balances resources based on privacy needs

• Optimism requires similar resources for all participants

Security Model Comparison

All systems adhere to a 1-of-N honesty assumption—where a single honest verifier can enforce correctness. Canon and opML rely on traditional bond-based incentives. oppAI innovates by making attack costs dynamic, based on the proportion of the model using zkML. DAVE provides the most robust Sybil resistance and censorship resilience, minimizing reliance on high bonds by leveraging logarithmic dispute scaling and permissionless participation.

1. Adversary Models:

   • All systems use a 1-of-N security model where a single honest validator can enforce correctness

   • DAVE specifically addresses Sybil attacks through its tournament structure

   • oppAI adds privacy considerations to the security model

   • opML potentially improves detection of sophisticated attacks

2. Economic Security:

   • Optimism relies on bonds to ensure honest behavior

   • DAVE minimizes bond requirements while maintaining security

   • oppAI introduces variable costs based on privacy needs

   • opML maintains the economic model of its host system

3. Censorship Resistance:

   • DAVE explicitly addresses censorship, requiring censorship for more than one challenge period to break consensus

   • Other systems have less explicit censorship resistance guarantees

Decentralization and Accessibility

Cartesi’s DAVE leads in terms of decentralization, with its low capital requirements and open validator access encouraging broader participation. Canon maintains moderate requirements, while opML and oppAI, despite their technical innovation, face participation challenges due to higher complexity and expertise requirements—particularly in machine learning and zero-knowledge systems.

1. Capital Requirements:

   • DAVE explicitly minimizes capital requirements (3 ETH vs. 3,600 ETH for Arbitrum's BoLD)

   • Optimism has moderate requirements

   • oppAI and opML inherit requirements from their base systems

2. Technical Barriers:

   • opML and oppAI introduce additional complexity through ML components

   • DAVE and Optimism have more straightforward verification processes

   • All systems require some technical expertise to participate effectively

3. Validator Diversity:

   • DAVE's low capital requirements potentially enable greater validator diversity

   • ML-based approaches might limit participation to those with ML expertise

   • All systems benefit from diverse validator sets for security

Integration Opportunities and Synergies

Several integration pathways could merge the best features of these mechanisms into a next-generation fault proof system. For example, pairing Canon FPVM with opML’s prediction layer could optimize dispute prioritization without modifying the core VM. Adding oppAI’s privacy-preserving zkML submodules would extend Canon’s use cases to sensitive applications like AI oracles. Most transformative would be adopting DAVE’s tournament-style dispute resolution, enabling permissionless participation with lower bonds and faster resolution—making Canon-based fault proofs more robust and accessible.

More ambitious would be a multi-system integration—combining Canon’s deterministic foundation, opML’s efficiency, oppAI’s privacy, and DAVE’s decentralization. While technically demanding, this could yield a modular fault proof architecture tailored for emerging rollup demands, from governance security to machine-learning-powered agents

Optimism Canon FPVM + opML

Potential Integration:

• Enhance Canon FPVM with ML-based prediction for faster verification

• Use ML to identify likely dispute points before full verification

• Maintain Canon's deterministic execution while improving efficiency

Implementation Approach:

• Add ML prediction layer to Canon without modifying core execution

• Train models on historical dispute patterns

• Use predictions to prioritize verification steps

Benefits:

• Faster dispute resolution

• Reduced computational overhead

• Maintained security guarantees

Optimism Canon FPVM + oppAI

Potential Integration:

• Add privacy capabilities to Canon through selective zkML

• Partition sensitive computations for privacy protection

• Maintain efficiency for non-sensitive operations

Implementation Approach:

• Implement model partitioning within Canon

• Add zkML verification for privacy-critical components

• Develop clear interfaces between zkML and opML parts

Benefits:

• Enhanced privacy for sensitive operations

• Maintained efficiency for standard operations

• New use cases for private computation

Optimism Canon FPVM + Cartesi's DAVE

Potential Integration:

• Adopt DAVE's tournament approach for Canon's dispute resolution

• Maintain Canon's execution environment while improving the challenge mechanism

• Reduce capital requirements for participation

Implementation Approach:

• Implement tournament-style challenges within Optimism's framework

• Adapt Canon to work with logarithmic dispute resolution

• Maintain compatibility with existing Optimism deployments

Benefits:

• Improved decentralization through lower capital requirements

• Enhanced resistance to Sybil attacks

• Faster dispute resolution

Multi-System Integration

Comprehensive Approach:

• Combine elements from all four systems for a next-generation fault proof system

• Use Canon's deterministic execution as the foundation

• Enhance with opML's efficiency improvements

• Add oppAI's privacy capabilities for sensitive operations

• Implement DAVE's tournament structure for dispute resolution

Implementation Challenges:

• Complexity of combining multiple novel approaches

• Ensuring security guarantees are maintained

• Managing the increased technical barriers to participation

Potential Benefits:

• Best-in-class performance across all metrics

• Support for diverse use cases including privacy-sensitive applications

• Improved accessibility and decentralization

Conclusion

While Canon FPVM provides the deterministic foundation for state validation in the OP Stack, opML introduces machine learning-driven optimizations that reduce overhead and improve execution speed. oppAI extends this with a hybrid zkML/opML approach that brings selective privacy to verifiable AI computations, and DAVE’s tournament-based protocol raises the bar for decentralization, liveness, and Sybil resistance.

Rather than selecting a single solution, our analysis supports a modular integration of these technologies as the optimal path forward. By synthesizing their complementary strengths and mitigating their individual tradeoffs, we envision a next-generation fault proof system that is efficient, private, accessible, and secure—one capable of meeting the evolving needs of Ethereum rollups and complex decentralized applications.

This vision forms the design framework for the OPcity prototype, a research-driven implementation of an advanced fault proof system built on the OP Stack. Our blueprint is structured across four interoperable layers:

1. Execution Layer: Modified Canon FPVM with RISC-V compatibility

• Deterministic execution environment based on Canon FPVM

• Extended instruction set supporting both MIPS and RISC-V operations

• Unified state representation using enhanced Merkle trees

• Compatibility layer for existing applications

2. Intelligence Layer: ML-enhanced prediction and optimization engine

• Predictive models for identifying potential dispute points

• Optimization algorithms for efficient execution paths

• Lightweight DNN library for in-VM machine learning

• Training framework for continuous improvement

• 
  

3. Privacy Layer: Selective zero-knowledge proof system

• Model partitioning framework for separating privacy-sensitive components

• Zero-knowledge proof generation for protected components

• Efficient verification of ZK proofs on-chain

• Economic security model for privacy protection

4. Verification Layer: Tournament-based dispute resolution system

• Permissionless tournament structure for dispute resolution

• Logarithmic scaling with adversary count

• Low capital requirements for participation

• Guaranteed dispute resolution timeframes

Together, these layers interact through clean, modular interfaces, enabling phased integration and future extensibility. This composable approach aligns with the principles of the OP Stack and supports OPcity’s long-term goal: to contribute a production-ready, decentralized fault proof architecture that strengthens Ethereum’s rollup ecosystem and expands its utility to civic infrastructure, public goods, and autonomous organizations.

In this context, the OPcity stack delves into the theoretical and practical aspects of the OP Stack and the Canon Fault Proofs VM, providing valuable insights into their implementation, performance benchmark, and potential future improvements. Additionally, it gathers the contributions and knowledge necessary to achieve the OP City milestones, compiling documents developed from December 2023 to 2024. Its purpose is to serve as a starting point for researchers and students to explore and test the implementation of OP Stack rollups, pushing its limits through the OP City stack.

1. OP Stack Theoretical Framework

Based on the OPcity repository

This section establishes the foundations for understanding the OP Stack and Fault Proofs, key elements in Ethereum’s scalability solutions. It begins by addressing Ethereum’s inherent scalability issues and how Layer 2 rollups offer strategies to address these challenges. It highlights how the evolution of the OP Stack, alongside the concept of the Superchain and fault proofs, is crucial for optimizing operational costs in decentralized technologies. This analysis is supported by academic references and relevant URLs, providing an overview of the theoretical foundations driving these advancements.

Ethereum Scalability

Ethereum has established itself as one of the most important blockchain platforms, transforming the development and functioning of applications. Unlike traditional systems, Ethereum is a decentralized, open-source computing network that allows developers to create and execute smart contracts, supporting a wide range of decentralized applications (dApps).

Ethereum functions as a state transition system, where transactions modify the global state of accounts and balances. This is driven by the Ethereum Virtual Machine (EVM), a flexible programming environment designed to execute smart contracts and complex dApps[1]. Smart contracts, a key feature of Ethereum, are self-executing agreements recorded on the blockchain that enable automated and trustless interactions. These contracts are widely used in cases such as custom tokens, financial products, Decentralized Autonomous Organizations (DAOs), and file storage solutions, among others. The immutability and irreversibility of blockchain ensure that these contracts function with high integrity, resilience, and transparency[2].

However, Ethereum faces the “blockchain trilemma,” a challenge of achieving scalability, decentralization, and security simultaneously, where improving one aspect often compromises another. Scalability is measured in transactions per second (TPS), decentralization distributes control across the network preventing censorship and manipulation, and security focuses on the system’s ability to resist attacks[3].

Rollups as Layer 2 solution

Traditional blockchains, like Bitcoin and Ethereum, are recognized for their security and decentralization but face significant scalability limitations. To address this challenge, Ethereum has explored "simple techniques" like Layer 2 solutions, which aim to increase network capacity by allowing different applications to operate on multiple interconnected chains through a crosschain communication protocol, thereby achieving interoperability. Although this approach is decentralized and scalable, it presents security vulnerabilities, as an attacker could compromise the main chain by gaining control of the majority of consensus nodes on a single chain, causing ripple effects on other interconnected chains[4].

One of the most important Layer 2 solutions is the rollup. Rollups aggregate multiple transactions off the main chain (Layer 1) and process them in batches, reducing the workload on Ethereum, allowing more transactions per second, and decreasing the gas fee, data, and computation required [1], without compromising security or decentralization. There are two main types of rollups:

1. Optimistic Rollups: These assume all transactions are valid by default and employ fraud proofs to identify false transactions within seven days.

2. Zero Knowledge ZK Rollups: These provide instant verification of transaction validity using validity proofs

The primary security weakness lies in the verification process of blocks generated by these Layer 2 technologies. Unlike Layer 1, where blocks are fully verified, Layer 2 blocks only contain the necessary state parts to process the block, along with some hashes that prove these provided parts represent the claimed state in the block. This solution involves verifying computation and data availability to ensure the system has performed computations correctly, assuming block validators have access to all necessary inputs and are stored accessibly for anyone to download if needed[5]

In Optimistic Rollups, fraud or fault proofs come into play if a dispute arises, detecting and proving that a specific block or transaction is invalid using Merklized data. This allows network nodes to receive and verify block states without downloading the entire blockchain, assuming that at least one honest node is willing to generate these proofs[6]. This mechanism is also known as an interactive game [7], where a participant optimistically assumes that each proposed outcome is valid[8]. This approach enables faster and more cost-effective scalability by assuming transactions are valid by default[9]

Optimism and the OP stack

Optimism, a Layer 2 scalability solution for Ethereum, utilizes Optimistic Rollups to enhance scalability, reduce transaction time and costs, and maintain robust security [10]. At the core of this ecosystem is OP Mainnet, a Layer 2 blockchain equivalent to the Ethereum Virtual Machine (EVM), directly connected to Ethereum and very similar to its main network, with minor differences mainly related to the specification of different network endpoints[11].

OP Mainnet leverages the OP Stack, a modular open-source software stack that facilitates the creation of Optimistic Rollups and production-ready Layer 2 blockchains. This allows developers to independently customize and upgrade components like consensus, execution, and settlement layers, fostering innovation and ensuring long-term adaptability. Additionally, the OP Stack is compatible with the Optimism Superchain, a network of interoperable OP Stack chains with common standards and protocols. This modular design enables scalability, customization, interoperability, and innovation, helping to avoid the repetitive development of similar software from scratch [12].

The introduction of a fault-proof system in OP Mainnet has been a significant advancement toward total decentralization. This system eliminates reliance on privileged roles for withdrawals and allows users to challenge and verify transactions, reducing centralization and fostering greater network security.

As the OP Stack continues to evolve, additional functionalities are expected, such as more advanced Fault Proof systems and improved interoperability features. This will pave the way for a more robust and interconnected ecosystem of decentralized applications on Ethereum. The current version of the OP Stack, Optimism Bedrock, not only powers the OP Mainnet but also simplifies the deployment of Optimistic Rollups and supports the Superchain concept. This vision aims to build a scalable and interconnected blockchain ecosystem where multiple Layer 2 chains can interact seamlessly, leveraging shared security and development standards.

As the technology matures in terms of security and reliability, the plan is to extend these capabilities, including fraud proofs, to other networks within the optimism ecosystem, such as Base, Metal, Mode, and Zora. This expansion will reinforce the Superchain concept and push the boundaries of Layer 2 scalability and interoperability [13].

Layers of the OP Stack

Based on the *** Optimism Docs***

The OP Stack can be understood as a set of software components that define new layers or integrate as modules within the stack, enabling the construction of a Layer 2 blockchain ecosystem. Below is a detailed breakdown of its layers:

• 1 Data Availability

  The Data Availability Layer defines where the raw inputs of an OP Stack-based chain are published. An OP Stack chain can source input data from one or more data availability modules. These modules significantly impact the system's security model. The most used Data Availability module is Ethereum, allowing source data to come from any accessible information on the Ethereum blockchain, including Ethereum calldata, events, and 4844 data blobs.

• 2 Sequencing Layer

  The Sequencing Layer determines how user transactions on an OP Stack Chain are collected and published to the Data Availability modules in use. In the default OP Stack rollup configuration, sequencing is generally handled by a single dedicated sequencer. The rules defined in the Derivation Layer limit the sequencer's ability to withhold transactions beyond a specific time.

• 3 Derivation Layer

  The Derivation Layer defines how the raw data in the Data Availability Layer is processed to form the processed inputs that are sent to the Execution Layer via the standard Ethereum Engine API(opens in a new tab). The Derivation Layer may also use the current system state, as defined by the Execution Layer, to inform the parsing of raw input data. The Derivation Layer can be modified to derive Engine API inputs from many different data sources. The Derivation Layer is typically tied closely to the Data Availability Layer because it must understand how to parse any raw input data.

• 4 Execution Layer

  The Execution Layer defines the state structure within an OP Stack system and establishes the state transition function that modifies this state. State transitions are triggered when inputs are received from the Derivation Layer via the Engine API. The abstraction of this layer allows modifications in the EVM or different underlying virtual machines.

  EVM
  The EVM is a module within the Execution Layer that uses the same state representation and state transition function as the Ethereum Virtual Machine. The EVM module in the OP Stack´s Ethereum rollup configuration is a slightly modified version that supports Layer 2 transactions initiated on Ethereum and adds an L1 data fee to each transaction to cover the cost of publishing transactions on Ethereum.

  5 Settlement Layer

  The Settlement Layer is a mechanism found in external blockchains that establishes a view of the state of an OP Stack chain on those chains (including other OP Stack chains). For each OP Stack chain, there may be one or more Settlement mechanisms on one or more external chains. The mechanisms of this layer are read-only and allow external parties to make decisions based on the state of an OP Stack chain.

  The term "Settlement Layer" originates from the fact that Settlement Layer mechanisms are often used to handle withdrawals of ETH and tokens from a blockchain. This withdrawal process involves first verifying the target blockchain's state on a third-party chain and then processing the withdrawal based on that state. Essentially, the Settlement Layer allows a third-party chain to be aware of the target chain's state.

  A Fault Proof mechanism based on attestations uses an optimistic protocol to establish a view of the state of an OP Stack chain. In optimistic settlement mechanisms, proposers can suggest what they consider the current valid state of the OP Stack chain. If these proposals are not invalidated within a specific period (the "challenge period"), then the mechanism assumes the proposals are correct. Specifically, in the Attestation Proof mechanism, a proposal can be invalidated if a certain threshold of predefined participants provides attestations of a valid state that differs from the proposed state. This assumes trust in the honesty of at least a threshold number of these predefined participants.

• 6 Governance Layer

  The Governance Layer refers to the general tools and processes utilized to manage system configuration, updates, and design decisions. It is a relatively abstract layer that can include a wide range of mechanisms on a target OP Stack chain and third-party chains, impacting many other layers of the OP Stack.

  From OPcity Repository:

2. Node & Rollup Setup

From OPcity repository:

This section comprehensively explains our experience setting up and running a node and deploying a rollup using the OP Stack. We carried out the setup process using two Intel NUC 13 PRO NUC13ANHi7 Arena Canyon devices, each equipped with an Intel Core i7-1360P 13th generation CPU, 32GB of RAM, and a 4TB SSD running Linux (Ubuntu).

In the test conducted in December, we used a remote VM and a third-party RPC service. However, this configuration presented significant challenges, mainly related to the limitations of RPC calls and restrictions imposed by proprietary hardware. Additionally, using third-party RPC services generated timeouts and raised security concerns, negatively affecting the overall performance of our testing environment. The reliance on a remote VM limited our control over the hardware, leading to scalability and reliability issues during the testing phase.

To overcome these challenges, we migrated to a local environment configuration using the Intel NUC devices. This transition allowed us to eliminate the limitations of third-party RPC services and gain full control over the hardware, resulting in a more reliable and efficient testing environment. We documented the entire setup process in our GitHub repository, including commands and screenshots to guide other developers in deploying a rollup, divided into two main stages for implementation in the Holesky testnet.

A. Spin up a L1 Node (Holesky Testnet):

• Geth (Execution Layer) setup instructions

• Prysm (Consensus Layer) setup instructions

This stage details the steps to configure an L1 node, starting with acquiring the necessary hardware. The Intel NUC devices provided adequate computing power for installing Linux (Ubuntu) and setting up the Geth and Prysm dependencies. Subsequently, we installed and ran Geth, which forms the base layer of the Ethereum network, followed by installing and initializing Prysm, facilitating the execution of the proof-of-stake consensus mechanism. This resulted in a robust L1 node capable of supporting subsequent rollup deployments.

B. Deploy a L2 rollup from the OP stack

• OPstack setup and deployment instructions

• OPstack Data Visualisation Dashboard setup

Building on the L1 node infrastructure, we documented the process of deploying an L2 rollup using the OP Stack. We began by installing the necessary Optimism dependencies and compiling the source code. Subsequently, we deployed contracts on L1 and initiated the OP-GETH instance, which involved setting up and running key components such as op-geth and op-node. The process culminated in obtaining Holesky ETH on the L2 network and sending test transactions, demonstrating the successful deployment of a rollup in a controlled local environment.

3. OP stack version benchmark

From OPcity repository:

This section presents the results of three test deployments, one in December 2023 and two in June 2024. The analyses show a significant reduction in operational costs for the batcher and proposer from the test deployment with the OP Stack V4.0.0 Canyon in December compared to the deployments with OP Stack V7.0.0 Fjord, conducted in June 2024.

The most notable difference between these versions is the reduction in the total gas fees used by the rollup with V7.0.0 , reducing ~75% of the operation cost, approximately 75% less than operational costs with V4.0.0. Additionally, the June deployments compared the use of calldata methods versus data blobs for registering data in Layer 1, revealing that data blobs consume approximately 60% fewer resources than call data.

Test Deployment 1 (OP stack V4.0.0 / December 2023)

From December 4 to 11, 2023, we conducted an exploratory evaluation of operational cost performance for OP Stack in a testnet environment, focusing on gas expenditure for the batcher and proposer. This testing phase was strategically scheduled before updates Dencun, Ecotone, and Fjord to prepare for implementing advanced features such as span batches, data blobs, and fault proofs, that were not yet implemented. During the 7-day deployment of the OP Stack on Testnet Sepolia, the batcher generated significant transactions (~27,000), resulting in substantial gas expenditure (~9.5 ETH) despite the absence of additional user or contract interactions

We have used a Virtual Machine in Google Cloud to deploy an OP rollup with the following configuration:

Machine type: e2-standard-2 Cores: 2 vCPU Memory: 8 GB

After connecting to a Sepolia node through Alchemy, installing dependencies, and building the Optimism Monorepo and op-geth, we created the four accounts that manage the rollup operation:

• The Admin (0x…92D5) account can upgrade contracts.

• The Batcher(0x…898ce) account, which publishes Sequencer transaction data to L1.

• The Proposer(0x…B561) account which publishes L2 transaction results to L1.

• The Sequencer(0x…3868) account signs blocks on the p2p network.

Additionally, a Bridge contract was created to transfer funds to the rollup.

https://x.com/zenbitMX/status/1731886578673254564

Key Findings

During this initial deployment, we faced several limitations related to operational costs for the batcher and proposer and restrictions stemming from RPC service usage. These challenges became evident during a 7-day deployment of OP Stack rollup on the Testnet Sepolia, where the batcher generated significant transactions (~27,000) with considerable gas consumption (~9.5 ETH). As mentioned earlier, this activity was exclusively the default operation of the rollup, without additional user or contract interactions. This expenditure was attributed to limitations in RPC calls from our provider (Alchemy), causing empty blockchain chains from sequencer to batcher increasing transaction rates and gas expenditure. This behavior highlighted the need to address scalability within OP Stack to support efficiently high performance and diverse user interactions.

Comparing the data with the OP Sepolia batcher, we observed a significant difference in transaction numbers during similar dates (~11,000, equivalent to 40% of the 7-day reference period) but not in higher gas consumption (~12 ETH). This is attributable to testnet usage by a significant number of real users and contracts; however, this circumstance could jeopardize Superchain's vision, which aims to sustain multiple derived chains from OP Stack that may not necessarily have similar user volumes or performance—especially those intended for non-DeFi applications that do not rely on sequencer income for profitability.

Test Deployment 2 (OP stack V7.0.0 - Call Data) / June 2024

From OPcity repository:

Following issues detected with using an RPC provider during our first deployment, we decided to set up a local node that would provide a reliable source of RPC calls. This allowed us to observe and measure impacts on transaction numbers and associated gas fees for each one; details of this setup process are outlined in previous sections, just as in the OP City repository.

With our node configured, we deployed a rollup from the OP Stack on Holesky testnet using version 7.0.0 Fjord and calldata method to publish transactions from Batcher and Proposer. This test deployment lasted 20 days following multiple network updates, including the span batches, compatibility of data blobs, and other optimizations that notably impacted the rollup operation cost from the December test. Using the same data posting method from the December test, during the first seven days, the Total Gas Fees used on the default rollup operation transactions were reduced by ~75%, from 10.63 to 2.59 ETH, while the cost per day fell from 1.5 down to 0.37 ETH.

The data from the rollup addresses are available here:

• Sequencer Address

• Batcher Address

• Proposer Address

• Admin Address

Test Deployment 3 (OP stack V7.0.0 - Data Blobs) / June 2024

From OPcity repository:

While the reduction in the Total Gas Fees using Calldata is significant, the implementation of data blobs as a data posting method enables an alternative that can significantly impact the rollup operation cost. To prove it, we deployed a third testnet rollup a week later using the same V7.0.0.0 and data blobs as the data posting method to compare with. By comparing the performance of both configurations, we identified the following:

1. A notable reduction in the number of transactions made by the Batcher and Proposer addresses with around 50% less activity (+100k txn with calldata vs 50k txn with data blobs)

2. ~65% fewer gas fees used by the rollup (2.59 from calldata vs 0.64 ETH from data blobs per 7-days operation and 0.37 vs 0.09 ETH per day, respectively)

The data from the rollup addresses are available here:

• Sequencer address (0x...414E)

• Batcher address (0x...1c84)

• Proposer address (0x...F093)

• Admin address (0x...AABC)

4. Proposed changes to Fault Proofs

Proposed during the OP Governance Season 5 and grant finalist during cycle 22

In addition to benchmarking two versions of the OP Stack, OP City also integrates research on the compatibility of the OP Stack’s Canon Fault Proof Virtual Machine (FPVM) with the opML Multiphase Fault Proof protocol. The objective is to implement a customized Fault Dispute Game that addresses challenges related to data availability in L2 rollups and the computational outcomes of Deep Neural Networks (DNN) from the opML multi-phase. This will be possible through an incentive mechanism for node validators who resolve disputes in both technologies.

Proposed Modifications:

OpML uses a multiphase fraud proof to ensure the accuracy of on-chain machine learning results. This mechanism is similar to the experimental Canon Fault Proofs of the OP Stack. Both technologies utilize a Fault Dispute Game for validators to resolve challenges in a game tree. We aim to expand the merklized data in the OP Stack’s FPVM to include state transitions in the opML Multiphase Dispute Game. By doing so, we pursue a unified framework capable of natively processing machine learning inferences on-chain, enhancing or replacing the current FPVM specifications.

A. State Transition Function Modeling

The FPVM functions as a state transition system where a function f maps a pre-state$$Spre$$ to a post-state $$Spost$$ based on an executed instruction: $$𝑓(𝑆𝑝𝑟𝑒)→𝑆𝑝𝑜𝑠𝑡$$

For integration:

• Proposed Framework Modification: Introduce an additional layer that handles complex decision trees or neural network outputs, which adjusts how the state transitions are computed, especially in handling error states or exceptions.

• Consider a modified state transition $$𝑓(𝑆𝑝𝑟𝑒,D)$$ function where $$D$$ represents data or decisions derived from opML processes, impacting the transition to $$Spost$$.

• Modified Function: $$f(Spre,D)→Spost$$

• Define a new state component that includes neural network inference results, which influences the transition process, particularly in how exceptions are handled.

B. Memory Management Analysis

Given the detailed memory specifications:

• Heap and Memory Operations: Analyze the implications of integrating a mechanism for handling large datasets required by machine learning models directly within the memory structure of FPVM.

• Suppose $$M(S)$$ is the memory utilization state function. Introduce *$$M'(S, D) $$*to handle additional data structures or caching mechanisms to optimize ML data handling.

Memory Function: $$M(S) → M(S,D)$$

C. Syscalls and I/O Enhancements

The proposed framework could potentially extend the syscall and I/O functionalities to better support ML-driven data processing:

• Extended Syscalls for ML: Introduce new syscalls specific to ML operations, such as data batching or model loading.

• I/O Modeling: Adjust the I/O model to handle larger data streams efficiently, crucial for ML processes. Propose modifications like enhanced buffer management or asynchronous I/O operations.

D. Formal Verification and Error Analysis

Given the complexity of ML integrations and the critical role of fault-proofing:

• Model how errors in the ML phase could propagate through the system, influencing state transitions and memory states.

• Utilize formal methods to verify the correctness of the integrated system under various operational conditions, ensuring that the modifications do not introduce new vulnerabilities.

E. Simulation and Evaluation Metrics

Develop simulations that mimic real-world operational conditions to evaluate the effectiveness of the proposed modifications:

• Create scenarios where traditional and ML-modified FPVMs are subjected to typical and atypical loads, measuring performance metrics like throughput, error rate, and response time.

• Define specific metrics to evaluate improvements or regressions in system behavior due to the integration, such as memory efficiency, fault detection accuracy, and computational overhead.

Additionally, with the implementation of this framework, we aim to provide the necessary infrastructure for on-chain processing of high volumes of public data generated in cities and utilize on-chain models to make ML inferences from those datasets. To protect the privacy of sensitive citizen data, we will explore implementing zkML through ORA's oppAI framework. This extension strategically balances trade-offs between privacy and computational efficiency. By combining the strengths of zkML privacy-preserving techniques with opML efficiency, oppAI enables a hybrid model to optimize both aspects for on-chain AI applications.

Conclusions

OP City, through its research on the OP Stack and the Canon Fault Proofs VM (FPVM), reveals a significant advancement in scalability and efficiency for Layer 2 solutions in the Ethereum ecosystem:

• Comparing versions 4.0.0 and 7.0.0 of the OP Stack has shown improvements in code, new functionalities, and a substantial reduction in transaction costs and gas consumption for both the batcher and proposer.

• The implementation of data blobs in version 7.0.0 demonstrated an additional 65% reduction in operational costs, underscoring the importance of continuous innovation in Optimism’s infrastructure architecture.

• Practical deployment and benchmarking exercises have empirically validated theoretical improvements, identified additional optimization areas, provided concrete data to guide future decisions, and created a set of best practices.

• Integration of Canon Fault Proofs VM with the opML Multiphase Fault Proof protocol opens new possibilities for expanding Layer 2 infrastructure capabilities, such as implementing a customized Fault Dispute Game and exploring zkML through the oppAI framework.

• Proposed modifications, such as introducing additional layers for handling decision trees and memory management analysis, demonstrate a commitment to continuous improvement and adaptability to emerging needs in deep neural networks.

In conclusion, OP City not only demonstrates that as versions of the OP Stack evolve, transaction efficiency improves and operational gas costs decrease, but it also enables optimized management of public data generated in cities. Through the infrastructure provided by this framework, we aim to process large volumes of on-chain data and utilize machine learning models (opML) to make inferences from these datasets. At the same time, citizen privacy will be protected through zkML, offering secure and effective artificial intelligence solutions on-chain.

References

Ethereum and Fault Proofs

[1] Buterin, V. (2015). A Next Generation Smart Contract & Decentralized Application Platform.

[2] Karbasi, A.H., Shahpasand, S. A post-quantum end-to-end encryption over smart contract-based blockchain for defeating man-in-the-middle and interception attacks. Peer-to-Peer Netw. Appl. 13, 1423–1441 (2020).

[3] Werth, J., Hajian Berenjestanaki, M., Barzegar, H. R., El Ioini, N., & Pahl, C. (2023). A review of blockchain platforms based on the scalability, security and decentralization trilemma. Proceedings of the 19th International Conference on Web Information Systems and Technologies (WEBIST 2023).

[4] Buterin, V. (2021). Why sharding is great: demystifying the technical properties.

[5] Buterin, V. (2018). A note on data availability and erasure coding.

[6] Mustafa Al-Bassam, Alberto Sonnino, Vitalik Buterin: Fraud Proofs and Data Availability: Maximising Light Client Security and Scaling Blockchains with Dishonest Majorities. CoRRabs/1809.09044 (2018)

[7] Optimism. OP stack Specification.

[8] Conway, KD., So, C., Yu, X., & Wong, K. (2024). opML: Optimistic Machine Learning on Blockchain

OP Stack

[9] Poon, J., & Buterin, V. (2016). Plasma: Scalable Autonomous Smart Contracts.

[10] Buterin, v. (2021) An Incomplete Guide to Rollups.

[11] Optimism documents: Glossary.

[12] Getting started: OP Mainnet.

[13] Optimism Developer Blog. Protocol Development: The Fault Proof System is available for the OP Stack.

Zenbit Operational Model

Over the past four years, we have evolved into Zenbit.eth, an organization focused on Research, Development, and Innovation (R&D&I) for public goods in cities. Initially, we aimed to establish ourselves as a Simplified Joint-Stock Company (SAS). However, the COVID-19 contingency caused significant delays in government procedures, and due to a lack of liquidity for legal and operational expenses, we turned to decentralized technologies for funding and talent. This shift led to the formation of a Decentralized Autonomous Organization (DAO), zenbit.eth.

The efficiency of the decentralized organization has been proven through our connection with global talent via hackathons, as well as the development and implementation of automatable and deterministic contracts and standards for Zenbit, using Open-Source Software (OSS) and Ethereum technologies. Additionally, we have leveraged on-chain funding programs to enhance and increase capabilities in our prototypes and carry out technology transfers. Thanks to decentralized funding, we have covered local operating expenses and global talent coordination, generating income and liquidity for Zenbit with weekly increases from decentralized finance mechanisms. This has significantly improved our responsiveness and adaptability in developing solutions to meet urban needs.

Locally, our constitution as a SAS has allowed us to develop and implement projects consistent with the reality of Querétaro, Mexico, strengthen our commercial, academic, and institutional relationships, and collaborate with local and federal governments.

Based on this experience, Zenbit operates as a SAS and a DAO. Despite the differences in operational, financial, and governance mechanisms between the two structures, those of the DAO are comparable to those of the SAS, albeit they vary in magnitude, security, and efficiency. Therefore, by merging both, we have established a hybrid model that allows us broader access to products, services, and intangibles at the local and global levels. This approach is consistent with Zenbit's vision of designing based on user needs, implementing decentralized technologies, and collaborating with talents regardless of their geographic location to improve the quality of life for citizens and urban management.

R&D Model: Zenbit Stack

All this journey and our experience have materialized in the Zenbit Stack, a Research and Development (R&D) model for cities designed to streamline coordination between local talents and connect them with world-renowned mentors. This model tackles urban challenges by facilitating scientific research projects and fostering collaborations with the private sector and government entities.

The Zenbit Stack does not seek to compete with conventional centralized public budget systems but rather complement them to overcome their limitations. It focuses on developing technological capabilities to generate a public digital infrastructure, driving the creation of startups in the decentralized technology industry and its application across various economic sectors. Thus, the city and its inhabitants have the necessary resources and assets to reach their full potential.

The Zenbit Stack comprises three levels. Its base is Collective Research, Development, and Innovation, defined by four pillars that characterize the operation, logistics, communication, and linkage of the Zenbit team with emerging talent. This base level facilitates the development of exploratory and applied research projects collaborating with specialists, focusing on implementing Ethereum and decentralized technologies in cities.

By characterizing this level, we identified that the legislative pillar could provide a local competitive advantage by driving legislative proposals to formally acknowledge Decentralized Autonomous Organizations (DAOs) as commercial or civil entities. This approach would allow the development of a reference framework for implementing decentralized infrastructure in public processes. Starting in 2022, this base was consolidated in Zenbit through an ongoing and iterative process and refinement of the public goods produced by the global talent that has collaborated in recent years.

The following levels of the Zenbit Stack refer to the integration of technological capabilities, which we will develop in the coming months. The second level, Infrastructure for Cities, consists of three protocol-level components aimed at driving a new industry for the city and leveraging the production of public data to create new highly specialized jobs dedicated to generating digital infrastructure.

The first component is OP City, an Ethereum Rollup dedicated to cities that enables the efficient and economical processing of large volumes of public data transparently and verifiably. This system will integrate machine learning and artificial intelligence algorithms with zero-knowledge technologies to extract and analyze relevant data, enabling informed decision-making while protecting citizens' privacy. In addition, this level will also include the acceleration of models focused on developing the city's scientific and technological capabilities.

Together, these decentralized user-focused functions, structured in the third level of the Zenbit Stack, will enable the validation and authentication of urban data, incentivize sustainable mobility practices, promote citizen participation, address urban needs, verify the identity and authenticity of individuals in digital interactions, as well as automate urban processes and improve the efficiency of public services.

Projects and Results

The experience earned from iterating our projects in real-world environments has enabled us to generate the Zenbit Stack and develop key technological components. At the City Infrastructure level, we have progressed with the OP City project, while at the user-focused applications level, we have developed Zengo, Supercities, and Zenbit Badges.

Zengo: Decentralized Budgeting

Zengo is a platform developed to manage public proposals focused on improving urban spaces through a decentralized and transparent process that includes registration, verification, quadratic voting, and initiative monitoring. Its purpose is to empower citizens and foster collaboration with government representatives, civil organizations, the private sector, academia, and other stakeholders. Additionally, it promotes decentralized urban governance and transparency and fights corruption, ensuring that public funds are used transparently and efficiently for the community's well-being.

From the pilot test carried out in the city of Querétaro during the second half of 2023, Zengo has achieved remarkable results, such as participating in the 2023 Transparency Innovation Contest organized by the National Institute for Access to Public Information (INAI), a federal agency in Mexico. Furthermore, it participated in the 3rd round of Retroactive Public Goods Funding (Retro PGF3), where, with 27 ballots from Optimism Badgeholders, the collective rewarded us with 24,845 OP tokens. Zengo has also been included in lists such as Bear Market Builders, End User Experience & Adoption Projects, and Ecosystem Impact Vectors, highlighting its relevance and effectiveness in decentralizing public funds.

https://github.com/zenbitETH/zengo

https://round3.optimism.io/projects/0xa0e0d386a862f8f1ee625bf5837bfb8ef5a8201d70c459efbe9172602ff3d831

Zenbit Badges

Zenbit Badges is a platform that allows on-chain certification of activity completion and the acquisition and application of web3 knowledge during in-person or virtual events, facilitating the use of the Ethereum Attestation Service (EAS). It has a contract deployed on the OP mainnet that allows registering events, mentors, and participants to issue automated attestations on behalf of badges.zenbit.eth. Currently, it verifies Optimisim Onboarding and DAO Formation.

https://github.com/zenbitETH/Zenbit-Badges

https://badges.zenbit.mx/

Zenbit Badges has completed three events and has one active. Two of these events were conducted in collaboration with Arkansas State University, Querétaro campus, Mexico, certifying students and teachers for their acquired knowledge and skills. Additionally, the technological project Axolotarium formed the DAO axolotarium.eth to implement decentralized technologies in preserving the axolotl, an endangered species endemic to Mexico.

The third event allowed the formation of the Zenbit VG subDAO, facilitating participation in the 3rd round of the Dark Forest game, organized by the DFArchon community on the Redstone chain. After seven days of intense competition, two members achieved positions in the Top 10 and distributed 420 OP tokens among non-core Zenbit collaborators.

https://x.com/zenbitMX/status/1790047178217378273

Finally, the fourth event is active and focused. In June of this year, it will provide residents of the Felipe Carrillo Puerto Delegation in Querétaro with knowledge about Optimism. The objective is to create a DAO for its neighborhoods using Zenbit Badges.

Supercities

In Supercities, we implemented the MUD engine developed by Lattice to improve public data management and facilitate modularity between the different urban experiences previously prototyped by Zenbit, built during the 2023 Autonomous Worlds hackathon. Its objective is to provide a user experience with as little friction as possible, leveraging MUD's capabilities to link smart accounts and enable urban verifications, mobility rewards, decentralized governance, human authenticity tools, and autonomous agents on an integral platform.

We paused the development of Supercities temporarily due to limited funding received from our participation in Round 9 of the Quadratic Funding organized by CLR. However, the project will resume in the third quarter of 2024, thanks to the support obtained from the third round of Retroactive Public Goods Funding (Retro PGF3).

OP City Stack

Although we can expand Zenbit's solid technological core with Supercities, technological and operational limitations were evident in its proof-of-concept tests where due to the intensive use of on-chain contracts to register and update urban data, which would generate prohibitive gas costs on the Ethereum mainnet. To address this problem, we explored Layer 2 (Layer 2, Rollup) solutions to reduce operational costs. Although we managed to reduce costs through tests on Optimism, they remained significant in intensive platform use.

https://x.com/zenbitMX/status/1731886578673254564

During this process, we identified Redstone as a variant of the OP stack that implements Plasma technology to reduce Data Availability costs, making the deployment of Supercities sustainable. However, the growth of our knowledge in the OP stack led us to conceive the idea of developing a city-dedicated Rollup, integrating functionalities for Large Language Model (LLM) inferences in public data processing through Optimistic Machine Learning (opML), and providing privacy tools through ZK and Optimistic Privacy Preserving AI (oppAI).

We are currently in the research phase, thanks to the approval of funding for our proposal by Optimism's governance. We prepared the grant proposal in collaboration with Dr. Cathie So, an expert in ML/AI/ZK. The collective granted funding for this proposal during cycle 22 of season 6 of Optimism Governance, and it will be developed over 12 months, starting this month.

Initiatives

In addition to the projects that underpin the Zenbit Stack, we are also involved in initiatives with global web3 communities and protocols. We recognize the importance of these collaborations to strengthen our ties with talent in non-technical specialties. However, our participation depends on the operational availability of Zenbit's collaborators.

Quadratic Funding with Gitcoin

During 2023, we participated in two Gitcoin quadratic funding rounds (Beta Round and GG19), seeking funding to support our project development and cover operational expenses. Although the results were moderate, the analysis of 471 projects in the main categories of the Beta Round stands out.

https://x.com/zenbitMX/status/1655863569416609792

Fundcaster

Fundcaster is an application that facilitates the creation of funding campaigns in posts on the Farcaster social network. Developed at the 2024 Frames Hackathon, it won the Best No-Code Tool award for simplifying the programming of contracts that manage donation campaigns. It is accessible to any user regardless of their technical skills.

https://ethglobal.com/showcase/fundcaster-34qsd

We Love The Art de Optimism

In late 2023, we participated in the Optimism We Love the Art contest in the AI ART category, presenting our work Zenbit City. This artistic piece, generated with Stable Diffusion, represents an optimistic vision of integrating public goods into urban environments, reflecting our commitment to strengthening emerging technologies for the benefit of citizens.

https://opensea.io/assets/0xa053Fd844f4Cb080e664C87914dF98ee876E3e80/1

Builders Council with SEED Latam

We have been actively involved in Optimism's governance ecosystem. Additionally, thanks to our experience and collaboration with SEED Latam, we have played important roles within the Optimism ecosystem. Habacuc.eth, the founder and R&D director of Zenbit, participated in the Builders Sub-committee of the Grants Council during Season 5, supporting the delegate Joxes. The delegation reviewed over 300 proposals in this role, and the collective recognized their Optimism Grants Council analysis posted in the forum. This exercise provided a deep understanding of the governance processes, so we will seek to continue our collaboration with SEED Latam to participate again in Season 6.

https://x.com/SEEDGov/status/1798134350833160428

In summary, the period since May 2023 has represented significant progress for Zenbit, thanks to its hybrid operating model as a DAO and SAS. This combination has provided us with a favorable environment, resources, and access to global talent to build our vision sustainably. Over the next 12 months, we will focus on the comprehensive development of the Zenbit Stack across its three levels, with Querétaro, Mexico, as our base of operations. We will collaborate closely with local universities, research centers, and civil organizations to foster the adoption of decentralized technologies, facilitate the linkage between emerging talents from the region and global experts, and promote technology transfer to catalyze the development of the local industry.

En nuestro informe inicial, compartimos los orígenes de Zenbit y establecimos nuestro objetivo de abordar las necesidades públicas de la colonia Santa Mónica 2 en Querétaro, México. Colaboramos estrechamente con los residentes locales y el gobierno para solucionar dichas necesidades y garantizar la transparencia en cada etapa del proceso. Nuestro trabajo continuó en la Unidad de Desarrollo Tecnológico e Innovación (UDTEI) de la Universidad Autónoma de Querétaro, donde comenzamos a investigar e integrar tecnologías descentralizadas para crear un sistema de datos urbanos, público, abierto y económicamente sostenible. Además, exploramos como estas tecnologías pueden ayudar a superar los desafíos que enfrentan los emprendimientos tecnológicos y científicos en sus etapas iniciales.

1. Modelo Operativo Zenbit

En los últimos cuatro años, hemos evolucionado hacia Zenbit.eth, una organización enfocada en la Investigación, Desarrollo e Innovación (I+D+I) de bienes públicos para ciudades. Inicialmente, comenzamos el proceso para constituirnos como una Sociedad de Acciones Simplificadas (SAS). Sin embargo, la contingencia del Covid-19 provocó significativos retrasos en los trámites gubernamentales y, junto con la falta de liquidez necesaria para gastos legales y operativos, nos llevó a buscar financiamiento y talento en las tecnologías descentralizadas. Lo que resultó en la creación de una Organización Autónoma Descentralizada (DAO), zenbit.eth.

La eficiencia de la organización descentralizada se ha comprobado mediante nuestra conexión con talento global a través de hackathones, así cómo el desarrollo e implementación de contratos y estándares automatizables y deterministas para Zenbit, utilizando Software de Código Abierto (OSS) y tecnologías de Ethereum. Además, hemos aprovechado programas de financiamiento ejecutados en registros públicos de cadena de bloques (onchain) para mejorar y aumentar las capacidades en nuestros prototipos y realizar transferencias tecnológicas. Gracias al fondeo descentralizado, hemos cubierto los gastos de operación local y la coordinación global de talentos, generando ingresos y liquidez para Zenbit con incrementos semanales gracias a los rendimientos de mecanismos de finanzas descentralizadas. Esto ha optimizado nuestra capacidad de respuesta y adaptación en el desarrollo de soluciones para atender las necesidades urbanas.

Mientras que, a nivel local, nuestra constitución como una SAS nos ha permitido desarrollar e implementar proyectos coherentes con la realidad de Querétaro, México, fortalecer nuestras relaciones comerciales, académicas e institucionales, y colaborar con los gobiernos local y federal.

Basándonos en esta experiencia, Zenbit actualmente opera tanto como una SAS como una DAO. A pesar de las diferencias en los mecanismos operativos, financieros y de gobernanza entre ambas organizaciones, los de la DAO son comparables con los de la SAS, aunque varían en magnitud, seguridad y eficiencia. Por lo tanto, mediante la fusión de ambas, hemos logrado establecer un modelo híbrido que nos permite un acceso más amplio a productos, servicios e intangibles a nivel local y global. Este enfoque es congruente con la visión de Zenbit de diseñar a partir de las necesidades del usuario, implementar tecnologías descentralizadas y colaborar con talentos independientemente de su ubicación geográfica para mejorar la calidad de vida de los ciudadanos y la gestión urbana.

2. Modelo de R&D: Zenbit Stack

Todo este recorrido y nuestra experiencia se han materializado en el Zenbit Stack, un modelo de Investigación y Desarrollo (I+D) para ciudades, diseñado para agilizar la coordinación entre talentos locales y conectarlos con mentores de renombre mundial. Este modelo aborda desafíos urbanos a través de proyectos de investigación científica y colaboraciones con el sector privado y entidades gubernamentales.

El Zenbit Stack no busca competir con los sistemas convencionales que centralizan el presupuesto público, sino complementarlos para superar sus limitaciones. Se enfoca en desarrollar capacidades tecnológicas para generar una infraestructura digital pública, impulsando la creación de startups en la industria de las tecnologías descentralizadas y su aplicación en diversos sectores económicos. De este modo, la ciudad y sus habitantes disponen de herramientas y recursos necesarios para alcanzar su máximo potencial.

El Zenbit Stack se compone de tres niveles. En su base se encuentra la Investigación, Desarrollo e Innovación Colectivos, definida por cuatro pilares que caracterizan la operación, logística, comunicación y vinculación del equipo de Zenbit con talento emergente. Esto facilita el desarrollo de proyectos de investigación exploratoria y aplicada colaborando con especialistas, enfocándose en el uso de Ethereum y tecnologías descentralizadas en ciudades.

Al caracterizar este nivel, identificamos que el pilar legislativo podría brindar una ventaja competitiva local, impulsando propuestas de ley que reconozcan a las Organizaciones Autónomas Descentralizadas (DAOs) como entidades comerciales o civiles. Esto permitiría desarrollar un marco de referencia para la implementación de infraestructura descentralizada en los procesos públicos. Esta base se consolidó en Zenbit, desde 2022, resultado de un proceso iterativo y perfeccionamiento de los bienes públicos producidos por el talento global que ha colaborado en los últimos años.

Los siguientes niveles del Zenbit Stack se refieren a la integración de las capacidades tecnológicas, que desarrollaremos en los próximos meses. El segundo nivel es la Infraestructura para ciudades, que consta de tres componentes a nivel de protocolo, con el fin de impulsar una nueva industria para la ciudad y aprovechar la producción de datos públicos en la creación de nuevos puestos de trabajo altamente especializados dedicados a generar infraestructura digital.

El primer componente es OP City, un Rollup de Ethereum dedicado a las ciudades que permite el procesamiento eficiente y económico de grandes volúmenes de datos públicos de manera transparente y verificable. Este sistema integrará algoritmos de aprendizaje automático e inteligencia artificial con tecnologías de conocimiento cero (ZK) para extraer y analizar datos relevantes, posibilitando la toma de decisiones informadas mientras se protege la privacidad de los ciudadanos. Además, este nivel también contemplará la aceleración de modelos enfocados en el desarrollo de capacidades científicas y tecnológicas de la ciudad.

En conjunto estas funciones descentralizadas enfocadas al usuario, estructuradas en el tercer nivel del Zenbit Stack; permitirán validar y autenticar datos urbanos, incentivar prácticas de movilidad sostenible, promover la participación ciudadana, resolver necesidades urbanas, verificar la identidad y autenticidad de los individuos en interacciones digitales, así como automatizar procesos urbanos y mejorar la eficiencia de los servicios públicos.

3. Proyectos y resultados

La experiencia adquirida con la iteración de nuestros proyectos en entornos reales nos ha permitido no solo generar el Zenbit Stack, sino también desarrollar componentes tecnológicos clave. A nivel de Infraestructura para Ciudades, hemos avanzado con el proyecto OP City; mientras que, en el nivel de aplicaciones enfocadas en el usuario, hemos desarrollado Zengo, Supercities y Zenbit Badges.

Zengo: Presupuesto Descentralizado

Zengo es una plataforma desarrollada para gestionar propuestas públicas enfocadas en la mejora de espacios urbanos mediante un proceso descentralizado y transparente que incluye el registro, verificación, voto cuadrático y monitoreo de iniciativas. Su propósito es empoderar a los ciudadanos y fomentar la colaboración con representantes del gobierno, organizaciones civiles, el sector privado, academia y otras partes interesadas. Además, promueve la gobernanza urbana descentralizada, la transparencia y combate la corrupción, asegurando que los fondos públicos se utilicen de manera transparente y eficiente para el bienestar de la comunidad.

A partir de la prueba piloto realizada en la ciudad de Querétaro durante el segundo semestre de 2023, Zengo ha logrado impactos destacados, como la participación en el Certamen de Innovación en Transparencia 2023 organizado por el Instituto Nacional de Acceso a la Información Pública (INAI), una dependencia federal de México. Además, participó en la 3ra ronda de Fondeo Retroactivo de Bienes Públicos (Retro PGF3), donde con 27 votos de los Badgeholders de Optimism, fue recompensada con 24,845 tokens OP. Zengo también ha sido incluida en listas como Bear Market Builders, End user experience & adoption projects y Ecosystem Impact Vectors, destacando su relevancia y efectividad en la descentralización de fondos públicos.

https://github.com/zenbitETH/zengo

https://round3.optimism.io/projects/0xa0e0d386a862f8f1ee625bf5837bfb8ef5a8201d70c459efbe9172602ff3d831

Zenbit Badges

Zenbit Badges es una plataforma que permite certificar onchain el cumplimiento de actividades, así como la adquisición y aplicación de conocimientos web3 durante eventos presenciales o virtuales, facilitando el uso de Ethereum Attestation Service (EAS). Cuenta con un contrato desplegado en OP mainnet que permite registrar eventos, mentores y participantes para emitir attestations automatizadas en nombre de badges.zenbit.eth. Actualmente, verifica la Introducción a Optimism y la Formación de DAOs.

https://github.com/zenbitETH/Zenbit-Badges

https://badges.zenbit.mx/

Zenbit Badges ha finalizado tres eventos y tiene uno activo. Dos de estos eventos fueron desarrollados en colaboración con la Universidad Arkansas State, campus Querétaro, México, certificando la adquisición de conocimientos y habilidades por parte de estudiantes y docentes. Además, ha sido utilizada por los integrantes del proyecto tecnológico Axolotarium, quienes formaron la DAO axolotarium.eth para implementar tecnologías descentralizadas en la preservación del ajolote, una especie endémica de México en peligro de extinción.

El tercer evento permitió la formación de la subDAO zenbit VG, lo que facilitó la participación en la 3ra ronda del juego Dark Forest, organizada por la comunidad DFArchon en la chain Redstone. Tras 7 días de intensa competencia, dos miembros lograron posiciones en el Top 10 y se repartieron 420 tokens OP entre colaboradores non-core de Zenbit.

https://x.com/zenbitMX/status/1790047178217378273?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1790047178217378273%7Ctwgr%5E%7Ctwcon%5Es1_&ref_url=notion%3A%2F%2Fwww.notion.so%2Fzenbiteth%2FReporte-Zenbit-2-47785e606a16411c95f5bcc6e5f1bb3f

Finalmente, el cuarto evento activo está enfocado en proveer conocimientos sobre Optimism a residentes de la Delegación Felipe Carrillo Puerto en Querétaro, en junio del presente año. El objetivo es la creación de una DAO para sus colonias mediante el uso de Zenbit Badges.

Supercities

En Supercities implementamos el motor MUD desarrollado por Lattice para mejorar la gestión de datos públicos y facilitar la modularidad entre las diferentes experiencias urbanas prototipadas previamente por Zenbit, fue desarrollado durante el hackathon Autonomous Worlds 2023. Su objetivo es brindar una experiencia al usuario con la menor fricción posible, aprovechando las capacidades de MUD para vincular cuentas inteligentes y habilitar verificaciones urbanas, recompensas por movilidad, gobernanza descentralizada, herramientas de autenticidad humana y agentes autónomos en una plataforma integral.

Para continuar desarrollando Supercities, hemos buscado financiamiento, participando con un resultado modesto en la Ronda 9 de Fondeo Cuadrático organizada por CLR. Esto pausó el proyecto, pero será retomado en el 3er trimestre de 2024 debido a los múltiples beneficios que ofrece y gracias al respaldo obtenido en la 3ra ronda de Fondeo Retroactivo de Bienes Públicos (Retro PFG3).

https://github.com/zenbitETH/supercities

https://x.com/zenbitMX/status/1676122407306657792

OP City Stack

A pesar del sólido core tecnológico de Zenbit probado en Supercities, se evidenciaron limitantes tecnológicas y operativas en sus pruebas de concepto. Esto se debe al uso intensivo de contratos onchain para registrar y actualizar datos urbanos, lo que generaría costos prohibitivos de gas en la red principal de Ethereum. Para abordar este problema, exploramos soluciones de segunda capa (Layer 2, Rollup) en busca de una reducción de costos operativos. Aunque logramos reducir los costos mediante pruebas en Optimism, estos seguían siendo significativos en el uso intensivo de la plataforma.

https://x.com/zenbitMX/status/1731886578673254564

Durante este proceso, identificamos Redstone como una variante del OP stack, que implementa tecnología Plasma para reducir el costo de disponibilidad de datos (Data Availability), lo que haría sostenible el despliegue de Supercities. Sin embargo, el crecimiento de nuestro conocimiento en OP stack nos llevó a concebir la idea de desarrollar un Rollup dedicado a las ciudades, integrando funcionalidades para inferencias de Large Language Models (LLM) en el procesamiento de datos públicos mediante Optimistic Machine Learning (opML) y proporcionando herramientas de privacidad mediante ZK y Optimistic Privacy Perserving AI (oppAI).

Actualmente, estamos en la fase de investigación gracias a la aprobación del financiamiento en nuestra propuesta en la gobernanza de Optimism, elaborada en colaboración con la Dra. Cathie So, experta en ML/AI/ZK. Este respaldo financiero fue otorgado durante el ciclo 22 de la temporada 6 de Optimism y se desarrollará durante 12 meses, comenzando este mes.

https://app.charmverse.io/op-grants/page-1306815702055122

4. Iniciativas

Además de los proyectos que sustentan el Zenbit Stack, también nos involucramos en iniciativas con comunidades y protocolos web3 de alcance global. Reconocemos la importancia de estas colaboraciones para fortalecer nuestros vínculos con talento en especialidades no técnicas. Sin embargo, nuestra participación depende de la disponibilidad operativa de los colaboradores de Zenbit.

Fondeo Cuadrático con Gitcoin

Durante 2023, participamos en dos rondas de fondeo cuadrático de Gitcoin (Beta Round y GG19), buscando financiamiento para apoyar el desarrollo de nuestros proyectos y cubrir gastos operativos. Aunque los resultados fueron moderados, destaca el análisis realizado a 471 proyectos de las modalidades principales de la Beta Round.

https://x.com/zenbitMX/status/1655863569416609792

Fundcaster

Fundcaster es una aplicación que facilita la creación de campañas de fondeo en publicaciones de la red social Farcaster. Durante su desarrollo en el Frames Hackathon 2024, obtuvo el premio a la Mejor Herramienta Sin Código por simplificar la programación de los contratos que gestionan las campañas de donación, permitiendo su accesibilidad a cualquier usuario independientemente de sus habilidades técnicas.

https://ethglobal.com/showcase/fundcaster-34qsd

We Love The Art de Optimism

A finales de 2023, participamos en el concurso We Love the Art de Optimism en la categoría de AI ART, presentando nuestra obra Zenbit City. Esta pieza artística, generada con Stable Diffusion, representa una visión optimista de la integración de bienes públicos en entornos urbanos, reflejando nuestro compromiso con el fortalecimiento de las tecnologías emergentes en beneficio de los ciudadanos.

https://opensea.io/assets/0xa053Fd844f4Cb080e664C87914dF98ee876E3e80/1

Consejo de Subvenciones OP con SEED Latam

Zenbit no solo ha sido un proponente en la gobernanza de Optimism, sino que, gracias a nuestra experiencia y colaboración con SEED Latam, hemos desempeñado roles importantes en el ecosistema. Habacuc.eth, fundador y director de R&D, participó en el Sub-comité de builders del Consejo de Fondeo durante la Temporada 5, brindando apoyo al delegado Joxes. En esta función, se revisaron más de 300 propuestas y la delegación fue reconocida por su análisis exhaustivo del Grants Council de Optimism. Este ejercicio proporcionó una comprensión profunda de los procesos de gobernanza, por lo que buscará continuar su colaboración con SEED Latam para participar nuevamente en la temporada 6.

https://x.com/SEEDGov/status/1798134350833160428

En resumen, el período desde mayo de 2023 ha representado un progreso significativo para Zenbit, gracias a su modelo operativo híbrido como DAO y SAS. Esta combinación nos ha brindado un entorno propicio, recursos y acceso a talento global para construir nuestra visión de manera sostenible. Durante los próximos 12 meses, nos enfocaremos en el desarrollo integral del Zenbit Stack en sus tres niveles, con Querétaro, México, como nuestra base de operaciones. Colaboraremos estrechamente con universidades locales, centros de investigación y organizaciones civiles para fomentar la adopción de tecnologías descentralizadas, facilitar la vinculación entre talentos emergentes de la región y expertos globales, y promover la transferencia tecnológica. Todo esto con el fin de servir como catalizador del desarrollo de la industria local.

Zenbit is a platform for building the tools that future scientists and technology developers need. This laboratory results from the coordination effort of many citizens, heads of households, young people, scientists, activists, and older adults. An effort that has been contained by the abuses allowed by plutocracy and degenerative mechanisms in Mexico. In Ethereum and the web3 ecosystem, we have found the opportunity to solve these coordination failures and to coordinate to turn those efforts into public goods that everyone can enjoy, and that can be scaled in as many cities as possible. Let's build an infinite garden with space and opportunities for all.

1. Zenbit.eth origins

Zenbit.eth is a digital laboratory that promotes the creation, monitoring, and flexibility of public goods, enhancing coordination in cities and increasing the utility of their social, statistical, and economic dynamics.

Founded in 2019, Zenbit.eth was born from academic research on digital divides, urban information systems, and government innovation incubated at the Technological Development and Innovation Unit (UDTEI) of the Autonomous University of Querétaro. This was done in collaboration with citizens, representatives of civil organizations¹, and government entities from the city of Querétaro².

The research was integrated to conceptualize an alternative to smart cities, proposing Web3 Cities with the goals of (1) promoting traceability, modularity, and adaptability of tangible and digital public goods, exploring their ability to (2) mitigate the impact of digital, financial, and social divides in cities, and to (3) continuously improve citizens' quality of life. With this context, Zenbit.eth established three fundamental pillars for developing strategic urban solutions:

a) Customized city design: We analyze and understand the specific needs of each city to design personalized and strategic solutions³ ⁴.

b) Creation of digital public goods: We focus our efforts on creating digital public goods that contribute to the development, coordination, and well-being of urban communities⁵ ⁶.

c) Urban space regeneration: We concentrate on revitalizing urban spaces to harmonize them with the environment, geographical features, and economic dynamics of each city⁷ ⁸.

Based on these pillars, we identified four relevant user experiences in cities that facilitate the creation of a modular urban data system and lay the conceptual foundation for Web3 Cities:

1. Digitizing data in public spaces

2. Coordinating urban governance activities

3. Decentralized e-commerce

4. Incentivizing emission-free mobility and logistics

Since 2020, we have publicly developed applications and iterations of these experiences, connecting and collaborating with global talent through ETH Global hackathons. Zenbit.eth was formally established in Querétaro, Mexico, where we have implemented and tested many of the public goods we developed for recording, verifying, and updating urban data. We have also tested some prototypes in Mexico City, Bogotá, and San Francisco related to regenerative tourism and a game for incentivizing emission-free mobility.

2. Ciudades DAO / SpacetimeDAO

To explore data tokenization in public spaces and urban governance interactions, we began integrating a decentralized urban data system in western Querétaro City in the Bajío region of Mexico. The Felipe Carrillo Puerto delegation bounds this area, one of the seven delegations of the municipality of Querétaro, composed of 4 regions with more than 100 neighborhoods or colonies inhabited by more than 135,000 people and with a composition between urban and some rural regions⁹. The initial diagnosis showed that although the neighborhoods have different characteristics, they share roads, public spaces, and governmental processes. This facilitates the composition and contrast of data between the neighborhoods and allows identifying similar patterns in other areas or cities.

https://www.google.com/maps/d/embed?mid=1EmfSuQL0Lh4RHzsRJfhUkdLvHAU&ehbc=2E312F?display=iframe

To validate this hypothesis, we developed a prototype in the Santa Mónica 2 neighborhood, an area with more than 5,000 residents, part of the Felipe Carrillo Puerto delegation. This prototype was carried out in collaboration with the residents of Santa Mónica 2, who participated through various web2 tools¹⁰ to collect relevant public data¹¹, such as:

1. Demographic distribution¹²

2. The state of public infrastructure¹³

3. Security incident registry¹⁴

4. Mapping of the local economy¹⁵

5. Geolocation of the main problems in the neighborhood¹⁶

6. Monitoring of government actions to provide greater transparency¹⁷

This urban data system prototype formed a digital community on Facebook with about 700 followers among residents, business owners, and street representatives. Of these, 27% joined instant messaging groups to manage and communicate the project's progress. In addition, 18 events were organized, most in-person and some virtual, which, along with digital activity, accelerated the identification of emerging issues and facilitated the coordination of 67 actions to address findings in Santa Mónica 2 with the help of local government and digital tools.

While these tools facilitated the initial approach of an urban data system, the following barriers were identified when using web2 platforms and public mechanisms for citizen participation:

1. Authoritarianism and centralization of urban governance, public budget, and management of technological development projects involving public data.

2. Coordination failures, privacy issues, and censorship when using web2 platforms.

3. A significant digital skills gap for using any digital tool is more evident in groups over 35.

From these findings, work continued with Santa Mónica 2 residents, and the exploration of web3 tools to address these issues was proposed. After several virtual meetings, the following agreements were reached to continue developing the urban data system and seek the decentralization of urban governance in Querétaro:

• Implement the DAO model in the neighborhood to coordinate neighborhood governance and establish a decentralized budget to complement the public budget allocated to address neighborhood needs.

• Promote creative talent through exhibitions of digitized urban art as NFTs.

• Digitize local businesses to improve their reach and contact channels.

• Use web3 protocols to encourage citizen participation.

https://www.facebook.com/groups/551318162242804/posts/682998892408063/

https://www.facebook.com/CiudadDAO.eth/videos/939694276555570/

To formalize these agreements, "Cities Protocol" was developed at the Scaling Ethereum 2021 hackathon, a prototype urban governance application that facilitates decentralized registration of proposals and urban data through a contract that manages governance proposals and voting (Governor Alpha) and another that generates VOTE tokens with which users are rewarded and used as voting power to approve or reject governance proposals during the two weeks following their creation.

From this prototype, version 0.1 was localized as Cities DAO to conceptualize using these contracts in a relevant environment such as western Querétaro. In the design process, we considered introducing web3 tools as part of the application tutorial to ensure users understand basic web3 concepts and smooth the learning curve toward governance interactions. The application prototype includes four interactions for citizens:

1. Obtain web3 skills certification for six months and voting power (VOTE governance token).

2. Create governance proposals and increase voting power.

3. Create governance proposals and increase their voting power.

4. Use voting power to approve or reject governance proposals.

5. Check the history of accepted and rejected proposals.

Once developed, this first version was tested with 35 residents of the Santa Monica 2 neighborhood who participated in the introduction to web3 tools events, of which 87% approved the web3 skills questionnaire, 71% voted for governance proposals, but only 23% encouraged to create them. The exercise was carried out in 2 rounds in which 100 transactions were generated in smart contracts and 18 governance proposals, of which 27% were for requesting construction or maintenance, 27% for organizing face-to-face events, 22% proposed improvements in public administration, 12% online events, 6% generated security reports, and 6% proposed additional functions.

When creating a proposal, the following information must be filled in:

• Proposal name

• Description

• Type of proposal

• Location URL (location on Google Maps)

• Cloud content URL (reference documents, images, or videos)

• Social media reference (URL of the publication)

However, not all proposals included all the data. The digital skills gap became evident, with some residents trying to participate through the web2 platforms they were familiar with.

The process was documented in Mexico Transparente magazine No. 2 (pages 107-111)¹⁹ of the National Transparency System, and the results report**²⁰** awarded the project an honorary mention in the 2022 Innovation in Transparency Contest organized by the National Institute for Transparency and Personal Data Protection (INAI) in conjunction with public, national, and regional institutions.

https://twitter.com/vinculasociedad/status/1592582849315581952?s=61&t=67LS0vTpoHk9rgVy4y2mmg

After testing version 0.1 of DAO Cities, we identified some friction points in the user experience and the technical capacity required to store the reference content generated in each governance proposal in a decentralized manner.

Among the functions or areas of opportunity to improve in version 0.2, the first is to update the governance model to one vote per person, since while the first version seeks to encourage citizen participation with the test tokens, in addition to facilitating the conceptualization of fungible tokens and their usefulness as voting power, its function in the pilot test was merely didactic, and the one vote per token model predisposes decision-making towards plutocratic models. We also identified that the references to social media or documents included in the proposals were not verifiable in all cases or contrasted with public records. Therefore, the urban governance process must include an evaluation period where citizens can complement their proposals while stakeholders participating as moderators can verify their reliability before moving on to a funding stage.

On the other hand, we identified a technical limitation in the use of smart contracts on networks like Ethereum, as they are designed to store lightweight data such as numerical or simple text values, so the content such as photographs, videos, or government management documents accompanying each proposal must be stored in centralized systems or through intermediaries that manage storage through decentralized networks.

After this review, we participated in the FVM Space Warp virtual hackathon. We developed Spacetime DAO²¹, a data DAO that integrates storage deals made on the Filecoin network through EVM-compatible smart contracts²². In this experiment, we explored solving the need to store content in a decentralized and intermediary-free manner with this mechanism. We also implemented additional stages for moderators, citizens, and government representatives to coordinate and evaluate the content at different stages. As a use case in Mexico, we implemented a verification stage where the information of each proposal is contrasted with public records through the integration of requests made on the National Transparency Platform (PNT)²³, which is a public information database managed by the National Transparency System of the National Institute of Transparency that facilitates queries of documentation and evidence about public processes at local, state, and federal levels. The PNT currently stores more than 8 million transparency obligation records and processes more than 600,000 queries monthly²⁴.

Spacetime DAO allows for incentivizing citizen participation and proposes funding the proposals through a decentralized budget. These functions have been tested and iterated during the first quarter of 2023 throughout the six rounds of Protocol Labs' Impact Builder Evaluator campaign²⁵, in which we started testing on the Hyperspace test network and gradually refined the implementation of storage deals in the urban governance process until deploying a stable version on the main network²⁶, with which we can link the storage of content in SpacetimeDAO and other applications with storage deals on the Filecoin network.

3. Punk Cities / Bright Forest

Although the development of Ciudades DAO / Spacetime DAO occupied much of our development efforts during 2022, we simultaneously explored user experiences that expand the experience in public spaces beyond urban governance.

In Punk Cities, we explored the gamification of data in public spaces through a collaborative game in which public space NFTs (ERC1155) are collected²⁷, and rewards (energy tokens) are obtained by verifying the current state of that public space with photos. These rewards are collaboratively staked to improve the level of the NFT, increasing rewards for those who have collected or verified it.

This project helps new users understand complex concepts such as digital collectibles, staking, and geolocation of content and incentives. Punk Cities was developed at the Build Quest 2022 hackathon, where it won the award for the best implementation of collectible NFTs²⁸; it received a Next Step Grant from Filecoin²⁹ and was inducted into the Filecoin Hall of Fame³⁰.

With this first version, we conducted an internal test by generating NFTs of some public spaces in the city of Querétaro. We conceptualized other relevant interactions in public spaces by iterating Punk Cities in other cities with recreational and regenerative tourism experiences.

During ETHMéxico, we developed Voyage³¹, an application in which travel content represented in NFTs is accumulated. The content was linked with public spaces generated in Punk Cities, so "travelers" receive rewards from a contract representing the city's decentralized budget vault by generating content in that city's public spaces. Additionally, the application publishes the generated content on the decentralized social network Lens³² and has Sybil resistance capabilities through WorldID³³.

Later, during Devcon 2022 week, we developed Regens at ETHBogotá³⁴, where we explored roles with regenerative task routes in public spaces of Bogotá issued in the Punk Cities contract as implementing video functionality as content linked to those NFTs.

https://twitter.com/zenbitMX/status/1593456014673805317?s=20

With the Bright Forest app, we experimented with a zero-emission mobility application where users can register as cyclists to make trips between public places in the city of Querétaro registered in Punk Cities and earn reward units based on calories burned during the journeys. This application aims to align incentives for cycling with the impact of each trip on gasoline savings, quantifying non-emitted carbon emissions and participants' physical health. The proof of concept for this application was developed during the online event HackFS 2022³⁵, and was submitted for Filecoin Green Grants³⁶ and ReFi Future Quest 2022³⁷.

Additionally, during the ETHSanFrancisco hackathon³⁸ , we developed Sparkz, an iteration of Bright Forest in which the user interface was redesigned³⁹ and zero-knowledge proofs (ZK proofs) were implemented in the smart contracts⁴⁰ to protect users' privacy during their journeys, proving that they started and completed the trip without publicly revealing the personal data emitted during the use of GPS on their devices.

4. Deco

In zenbit deco, we use NFTs (ERC721) for a decentralized commerce application in which small business owners can create their store, choose one of the six types of stores (general, clothing, urban, art, beauty, professional services), add products, and manage revenue through a vault in which they can withdraw income in DAI or provide it as liquidity to obtain returns from product sales in zenbit deco. This proof of concept integrates Aave⁴¹, a decentralized finance (DeFi) protocol, and the use of the stablecoin DAI⁴² for commercial transactions on the platform. This project was developed at Hack Money 2022⁴³ and received a Next Step Grant from Filecoin⁴⁴.

We are currently preparing a pilot test of DeCo in the city of Querétaro, and in the process, we have successfully deployed its contracts on the Goerli⁴⁵, Polygon Mumbai⁴⁶, Optimism Goerli⁴⁷, and Arbitrum Goerli⁴⁸ test networks.

To reduce friction in the user experience during the introduction of web3 tools, we developed POAPcet⁴⁹, an application that allows developers or community leaders to create a customizable faucet that facilitates this process. This is achieved through a smart contract that allows linking attendance certificates (POAPs) from web3 introduction events to users about to test applications on test networks, facilitating the distribution of test ether for the payment of necessary gas fees for the test. POAPcet was developed during the virtual hackathon Scaling Ethereum.

https://ethglobal.com/showcase/deco-zxa8s

5. Development and funding of public goods

To be consistent with the design principles of zenbit.eth, we have developed all our projects in public and with open source repositories⁵⁰. However, the knowledge and talent required to develop in public require mechanisms to fund these types of projects. To address the sustainability of zenbit.eth, we have participated in different public goods funding calls, first in the quadratic funding round @ devcon Colombia, where thanks to the invaluable donation of the person who supported our project, we obtained third place in the funding table for participants⁵¹.

Additionally, we participated in the second round of retroactive public goods funding from Optimisim with Eneagon⁵², a pre-filtering application for public goods projects that implements Optimism's bicameral model⁵³ and task traceability with gitbub goals⁵⁴ to facilitate coordination between developers and stakeholders developing public goods. We have used this application internally to retroactively distribute funds to the talent that has collaborated in developing the different experiences we develop in zenbit. In the pursuit of improving the modularity and utility of the application, we participated in the "Circles" of ReFiDAO⁵⁵, where we conducted a collaborative analysis of the participants to identify the socio-technical dimensions in which they have an impact and their current state of development⁵⁶. This analysis identified several functions that could be implemented to accelerate the development of public goods projects. However, due to communication errors in the project's approach, we obtained little preference among evaluators⁵⁷, in addition to opinions that reflect the areas of opportunity⁵⁸ we have not only with this project but with the set of public goods for web3 cities that make up zenbit.

https://twitter.com/samonchain/status/1597743254245502976?s=20

https://twitter.com/zenbitMX/status/1641496256307515392?s=20

During the 2nd quarter of 2023, we will continue with the development of the public goods that make up web3 cities and will carry out field tests in the city of Querétaro to validate the ability of contracts to register public places, small businesses, infrastructure, and organic elements as NFTs to generate historical data on their interactions and model the incentives that participants and collaborators will receive for creating, verifying, and updating the data of these digitalized spaces.

Following this test in the city of Querétaro, we will iterate the tools for web3 cities in other urban areas of Mexico and Latin America. In Mexico, we will carry out field tests in collaboration with INAI, the Secretariat of Sustainable Development of the Municipality of Querétaro, and the Public Space Laboratory, as well as inviting representatives from civil organizations, experts from multiple disciplines, representatives of autonomous agencies and public agencies to participate in the integration of a DAO that manages and evaluates the use of decentralized budget during these tests.

The results will be shared with different Latin American communities to propose a collaborative research and development protocol in multiple regional cities and evaluate the performance of web3 city tools in different urban environments.

If you want to support the public goods developed in zenbit.eth, you can help us:

1. By subscribing

2. Collecting this article

3. Minting the commemorative NFTs that will accompany each zenbit report. All income and royalties will be used to finance the operation and talent of our team.

https://opensea.io/assets/ethereum/0x6C5ECb541457924c919b4C1536708D0d621E6579/0

En este contexto, Zenbit.eth se presenta como una solución para abordar estas deficiencias y construir las herramientas necesarias para científicos y desarrolladores de tecnología. Este laboratorio es fruto del esfuerzo coordinado de ciudadanos y ciudadanas, jefas de familia, jóvenes, científicos, activistas y adultos mayores, con el objetivo de contener los abusos de la plutocracia y mecanismos degenerativos en México. Gracias a la adopción de tecnologías Web3 y las herramientas de Ethereum, en Zenbit.eth hemos comenzado a solucionar las fallas de coordinación con la finalidad de generar bienes públicos que no sólo beneficien a la mayor cantidad de personas y reflejen las necesidades reales de la población en general, sino que también sean replicables en la mayor parte de ciudades de Latinoamérica.

Es momento de construir un jardín infinito con espacio y oportunidades para todos.

1. Zenbit.eth y las Ciudades Web3

Zenbit.eth es un laboratorio digital dedicado al desarrollo de bienes públicos y proyectos innovadores con el objetivo de mejorar la calidad de vida en áreas urbanas. Nuestro enfoque se basa en principios vanguardistas de diseño y desarrollo, y colaboramos estrechamente con organizaciones locales e internacionales. Nuestro centro de innovación promueve la creación, seguimiento y flexibilidad de bienes públicos que buscan mejorar la coordinación en las ciudades, basándose en su dinámica social, estadística y económica.

El laboratorio fue creado en 2019 a partir de investigaciones académicas sobre brechas digitales, sistemas de información urbana e innovación gubernamental, generadas en la Unidad de Desarrollo Tecnológico e Innovación (UDTEI) de la Universidad Autónoma de Querétaro, en colaboración con ciudadanos, representantes de organizaciones¹ y entidades gubernamentales de la ciudad de Querétaro².

Estas investigaciones permitieron acuñar Ciudades Web3, que buscan (1) promover la trazabilidad, modularidad y adaptabilidad de bienes públicos tangibles y digitales, (2) mitigar el impacto de la brecha digital, financiera y social en las ciudades, y (3) mejorar continuamente la calidad de vida de los ciudadanos. En consecuencia, Zenbit.eth trabaja en tres vertientes fundamentales para el desarrollo de soluciones estratégicas en el ámbito urbano:

a) Diseño personalizado para la ciudad: Comprendemos y analizamos las necesidades específicas de los espacios urbanos con el fin de generar soluciones personalizadas y estratégicas³ ⁴.

b) Creación de bienes públicos digitales: Creamos recursos digitales que promuevan el desarrollo, la coordinación y el bienestar de la sociedad en general.⁵ ⁶.

c) Regeneración de espacios urbanos: Revitalización de espacios urbanos: Buscamos regenerar y armonizar los entornos urbanos con el medio ambiente, las características geográficas y las dinámicas económicas de cada ciudad.⁷ ⁸.

Estas vertientes posibilitan la generación de cuatro tipos de interacciones de usuario, lo cual facilita la construcción de un sistema modular de datos urbanos y establece los principios conceptuales de las Ciudades Web3:

1. Tokenización de datos en espacios públicos

2. Coordinación de actividades de gobernanza urbana

3. Comercio electrónico descentralizado

4. Promoción de la movilidad y logística sostenibles sin emisiones

Zenbit.eth tiene su sede en la ciudad de Querétaro, México. Desde 2020, hemos estado trabajando en la generación, implementación e iteración de prototipos y aplicaciones de bienes públicos en México, Colombia y Estados Unidos. Estas soluciones se basan en las interacciones de usuario y se han desarrollado en colaboración con expertos a través de Hackathones organizados por ETH Global. Esto nos ha permitido registrar, verificar y actualizar el sistema modular de datos urbanos relacionados con turismo regenerativo y la movilidad sin emisiones. Las aplicaciones más relevantes que hemos desarrollado son: Ciudades DAO, Punk Cities, Bright Forest, Deco y Eneagon.

2. Ciudades DAO / SpacetimeDAO

El concepto de ciudades Web3 se refiere a la aplicación de tecnologías descentralizadas basadas en blockchain en la gobernanza urbana y en la gestión de datos en espacios públicos. En este sentido, se implementó un sistema de datos urbanos descentralizado en el oeste de la Ciudad de Querétaro, específicamente en la delegación Felipe Carrillo Puerto, que consta de más de 100 colonias o vecindarios con una población aproximada de 135,000 personas. Se realizó un diagnóstico inicial que reveló la compartición que se comparten vialidades, espacios públicos y procesos gubernamentales; lo cual facilitó la comparación y contraste de datos entre las colonias, lo que permitió identificar patrones similares en otras áreas de la ciudad.⁹

El diagnóstico inicial mostró que si bien las colonias tienen diferentes características, comparten vialidades, espacios públicos y procesos gubernamentales, lo cual facilita la composición y contraste de datos entre las colonias y permite identificar patrones similares en otras zonas o ciudades.

https://www.google.com/maps/d/embed?mid=1EmfSuQL0Lh4RHzsRJfhUkdLvHAU&ehbc=2E312F?display=iframe

Con el objetivo de promover la tokenización y las interacciones urbanas se llevó a cabo una colaboración con los residentes de la colonia Santa Mónica 2, perteneciente a la delegación seleccionada, la cual cuenta con una población de 5 mil residentes. Los residentes participaron activamente utilizando herramientas Web2¹⁰ para recolectar datos sobre públicos relevantes¹¹, tal como:

1. La distribución demográfica¹²

2. El estado de la infraestructura pública¹³

3. Registro de incidentes de seguridad¹⁴

4. Mapeo de la economía local¹⁵

5. Geolocalización de las principales problemáticas de la colonia¹⁶

6. Monitoreo de las gestiones gubernamentales para brindar mayor transparencia¹⁷

A partir esta colaboración, se formó una comunidad digital en Facebook con más de 700 personas, que incluye residentes, dueños de negocio y representantes de calle. De ellos, el 27% crearon grupos de mensajería instantánea para gestionar y comunicar efectivamente el avance del proyecto. Además, se organizaron 18 eventos, en su mayoría presenciales, lo que aceleró la identificación de problemáticas emergentes y la coordinación de 67 gestiones públicas para resolver los problemas más apremiantes, en colaboración con el gobierno local, utilizando herramientas digitales como apoyo en el proceso. Se identificaron algunas barreras en el uso de plataformas Web2 en los mecanismos públicos de participación ciudadana, incluyendo autoritarismo y centralización en la gobernanza urbana, la gestión del presupuesto público y proyectos de desarrollo tecnológico, así como fallas de coordinación, privacidad y censura en el uso de estas plataformas. Además, se encontró una brecha representativa en habilidades digitales, especialmente en personas mayores a 35 años.

A partir de estos descubrimientos obtenidos, se llevó a cabo un continuo trabajo con los residentes de Santa Mónica 2, a través de reuniones virtuales y se exploraron las posibilidades del uso de herramientas Web3 para abordar las problemáticas identificadas. Entre las acciones implementadas se incluyó la implementación del modelo Organización Autónoma Descentralizada (DAO, por sus siglas en inglés) en la colonia, que estableció un presupuesto descentralizado para complementar el presupuesto público asignado a la colonia, así como la promoción del talento creativo de los residentes a través de exposiciones de arte urbano digitalizado con NFTs. Además, se digitalizaron la mayoría de los comercios locales con el objetivo de mejorar su alcance y canales de contacto con los usuarios principales.

https://www.facebook.com/groups/551318162242804/posts/682998892408063/

https://www.facebook.com/CiudadDAO.eth/videos/939694276555570/

Con la finalidad de otorgar mayor formalidad a los acuerdos, durante el hackathon Scaling Ethereum 2021 se creó el ¨Cities Protocol”¹⁸ , una aplicación descentralizada de gobernanza urbana que permite el registro y seguimiento de propuestas y datos mediante la generación de dos contratos. El primero habilita la gestión de propuestas y votaciones de gobernanza por parte del usuario Gobernador Alfa, mientras que el segundo genera tokens denominados “VOTO”, que recompensan a los usuarios y permiten la votación para aprobar o rechazar las propuestas de gobernanza. En el proceso de diseño de la versión 0.1 de la aplicación de Ciudades DAO, se incluyó una introducción al uso de herramientas Web3 para que los usuarios pudieran familiarizarse con los conceptos básicos. Este prototipo cuenta con cuatro funcionalidades principales: obtención de una certificación de habilidades Web3 por 6 meses y la obtención de token “VOTO”, creación de propuestas de gobernanza para aumentar el poder de su voto, aumento del poder de voto para aprobar o rechazar las propuestas, y consulta del historial de propuestas aceptadas y rechazadas. Cada propuesta debe incluir la siguiente información: nombre, descripción breve, categorización, URL de ubicación en Google Maps, URL dle contenido que valide la propuesta (documentos, imágenes o videos de referencia) y una demostración de la propuesta en redes sociales (URL de la publicación). La versión 0.1 de la aplicación fue comprobada por 35 residentes de la colonia Santa Mónica 2, a través de dos rondas introductorias a las herramientas Web3. Los resultados fueron alentadores, con un 87% de aprobación en el cuestionario, un 23% de los participantes generaron propuestas y un 71% votaron para aprobar o rechazar las mismas. Además, se llevaron a cabo 100 transacciones en los contratos inteligentes con un total de 18 propuestas de gobernanza. En cuanto al tipo de propuestas, el 27% solicitaba obras o mantenimiento, otro 27% demandaban la organización de eventos presenciales, el 22% proponía mejoras en la administración pública, el 12% generaba eventos en línea, mientras que el 6% realizaba reportes de seguridad y otro 6% proponía funciones adicionales.

El proceso fue documentado en la revista México Transparente No. 2 (pags 107-111)¹⁹ del Sistema Nacional de Transparencia, donde los resultados hicieron evidente que algunos residentes carecían de las habilidades digitales necesarias para generar propuestas. Además, se observó en la versión 0.1, la cual tenía una función didáctica, que la experiencia del usuario no era óptima y la capacidad técnica de la aplicación para almacenar las propuestas de manera descentralizada era insuficiente. Asimismo, el objetivo de esta versión era incentivar la participación ciudadana con tokens de prueba y facilitar la conceptualización de tokens fungible como poder de voto. No obstante, se observó que el modelo de un voto por token predispone la toma de decisiones hacia la plutocracia.

Cabe destacar que la aplicación también participó en el Certamen de Innovación en Transparencia 2022, organizado por el Instituto Nacional de Transparencia y Protección de Datos Personales (INAI), junto con otras instituciones públicas a nivel nacional y regional, y recibió una Mención Honorífica en reconocimiento a su labor.²⁰

https://twitter.com/vinculasociedad/status/1592582849315581952?s=61&t=67LS0vTpoHk9rgVy4y2mmg

Con base en los aprendizajes de la versión 0.1 de Ciudades DAO, se diseñó la versión 0.2 con las siguientes mejoras: actualización del modelo de gobernanza para permitir un único voto por persona por propuesta, inclusión de un periodo de evaluación por parte de usuarios con el rol de moderadores para verificar la fiabilidad y veracidad de las propuestas antes de la etapa de fondeo, ampliación técnica mediante el uso de contratos inteligente en Ethereum con la finalidad de almacenar valores numéricos o texto simple, y el uso de sistemas centralizados de intermedios para gestionar el almacenamiento de fotografías, videos y documentos asociados a gestiones documentales. Durante el hackathon virtual FVM Space Warp se propuso una versión optimizada llamada Spacetime DAO²¹. Se trata de una data DAO con el objetivo de centralizar, democratizar, y mejorar la calidad y seguridad de los datos. Además, integra tratos de almacenamiento en la red Filecoin mediante contratos inteligentes compatibles con EVMs²². También se implementó un almacenamiento descentralizado de contenido y junto con etapas adicionales para permitir la coordinación entre los usuarios con los roles de moderador, ciudadano y representante gubernamental durante todo el proceso. Posteriormente, se llevó a cabo un estudio de caso en México donde se contrastaron las propuestas con los registros públicos integrados en las solicitudes realizadas en la Plataforma Nacional de Transparencia (PNT))²³. La PNT es una base de datos de dominio público que facilita el acceso a la documentación y evidencia sobre procesos públicos a nivel local, estatal y federal, y es gestionada por el Sistema Nacional de Transparencia del Instituto Nacional de Transparencia. Actualmente, la PNT almacena más de 8 millones de registros de obligaciones de transparencia y procesa mensualmente más de 600,000 consultas²⁴. Spacetime DAO promueve la participación ciudadana y permite el financiamiento de propuestas con un presupuesto descentralizado. Durante el año 2023, ha sido objeto de iteraciones, incluyendo seis rondas de evaluación organizadas por Impact Builder Evaluator de Protocol Labs²⁵. Se inició con la validación en la red de pruebas Hyperspace, mejorando la implementación de los tratos de almacenamiento en el proceso de gobernanza urbana hasta conseguir una versión estable en la red principal²⁶. Esto permite vincular el almacenamiento de contenido en SpacetimeDAO con otras aplicaciones con los tratos de almacenamiento en la red de Filecoin.

3. Punk Cities / Bright Forest

Si bien el desarrollo de Ciudades DAO / Spacetime DAO ocupo gran parte de nuestros esfuerzos de desarrollo durante 2022, de manera paralela exploramos experiencias de usuario que expanden la experiencia en los espacios públicos más allá de la gobernanza urbana.

En Punk Cities exploramos la ludificación de datos en espacios públicos mediante un juego colaborativo en el que se coleccionan NFTs (ERC1155) de espacios públicos²⁷ y se obtienen recompensas (tokens de energía) al verificar con fotografías del estado actual de ese espacio público, las cuales se acumulan (staking) de manera colabora colaborativa para mejorar el nivel del NFT incrementando las recompensas para aquellos que lo hayan coleccionado o verificado.

Este proyecto facilita a nuevos usuarios la comprensión de conceptos complejos como coleccionables digitales, staking y geolocalización de contenido e incentivos. Punk Cities fue desarrollado en el hackathon Build Quest 2022 donde obtuvo el premio a la mejor implementación de NFTs coleccionables ²⁸ y posteriormente obtuvo una beca Next Step Grant de Filecoin²⁹ además de ser inducido al Salon de la Fama de Filecoin³⁰.

Con esta primer versión realizamos una prueba interna con al generar los NFTs de algunos espacios públicos en la ciudad de Querétaro y para conceptualizar otras interacciones relevantes en espacios públicos iteramos Punk Cities en otras ciudades con experiencias de turismo recreativo y regenerativo.

Durante ETHMéxico desarrollamos Voyage³¹, una aplicación en la que se acumula contenido sobre viajes representados en NFTs. El contenido se vinculó con espacios públicos generados en Punk Cities, con lo que los ¨viajeros¨ obtienen recompensas de un contrato que representa la bóveda del presupuesto descentralizado de la ciudad al generar contenido en espacios públicos de esa ciudad. Adicionalmente la aplicación pública el contenido generado en la red social descentralizada Lens ³² y tiene capacidades de resistencia a actores malintencionados (sybil resistance) a través de WorldID³³.

Después, durante la semana de Devcon 2022 desarrollamos Regens en ETHBogotá³⁴ en donde exploramos roles con rutas de tareas regenerativas en espacios públicos de Bogotá emitidos en el contrato de Punk Cities, además de implementar la funcionalidad de video como contenido vinculado esos NFTs.

https://twitter.com/zenbitMX/status/1593456014673805317?s=20

Con la aplicación Bright Forest experimentamos con una aplicación de movilidad con cero emisiones donde los usuarios pueden registrarse como ciclistas para realizar viajes entre lugares públicos de la ciudad de Querétaro registrados en Punk Cities y obtener unidades recompensas según las calorías quemadas durante los trayectos. Con esta aplicación se busca empatar los incentivos para realizar viajes en bicicleta con el impacto que tiene cada traslado en el ahorro de gasolina, cuantificar las emisiones de carbono no emitidas y en la salud física de los participantes. La prueba concepto de esta aplicación se desarrollo durante el evento en linea HackFS 2022³⁵, y fue inscrita para las becas Green Grant de Filecoin³⁶ y ReFi Future Quest 2022³⁷.

Adicionalmente, durante el hackathon ETHSanFranciso³⁸ desarrollamos Sparkz, una iteración de Bright Forest en la que se rediseño la interfaz de usuario³⁹ además de implementar pruebas de conocimiento cero (ZK proofs) en los contratos inteligentes⁴⁰ para proteger la privacidad de los usuarios en los trayectos que realicen, probando que iniciaron y terminaron el viaje sin revelar públicamente los datos personales emitidos durante el uso del GPS en sus dispositivos.

4. Deco

En zenbit deco utilizamos NFTs (ERC721) para una aplicación de comercio descentralizado en el que los dueños de pequeños negocios pueden crear su tienda, elegir uno de los 6 tipos de tiendas (general, de ropa, urbana, de arte, de belleza, de servicios profesionales), agregar productos y gestionar los ingresos mediante una bóveda (vault) en la que pueden retirar los ingresos en DAI o proveerlos como liquidez para obtener un rendimiento a partir de las ventas de productos en zenbit deco. Esta prueba de concepto integra Aave⁴¹, un protocolo de finanzas descentralizadas (DeFi) y el uso de la moneda estable DAI⁴² para las transacciones comerciales en la plataforma. Este proyecto obtuvo fue desarrollado en Hack Money 2022⁴³ y obtuvo una beca Next Step Grant de Filecoin⁴⁴.

Actualmente estamos preparando una prueba piloto de DeCo en la ciudad de Querétaro y en el proceso hemos desplegado sus contratos de manera satisfactoria en las redes de prueba Goerli⁴⁵, Polygon Mumbai⁴⁶, Optimism Goerli⁴⁷ y Arbitrum Goerli⁴⁸.

Para reducir la fricción en la experiencia de usuario durante la introducción de herramientas web3 desarrollamos POAPcet, una aplicación que permite a desarrolladores o lideres de comunidad crear un grifo (faucet) personalizable que facilita este proceso. Esto se logra mediante un contrato inteligente que permite vincular la tenencia de certificados de asistencia (POAPs) de eventos de introducción a web3 con usuarios a punto de probar aplicaciones en redes de prueba, facilitando la distribución de ether de prueba para el pago de comisiones de gas necesarias para la prueba. POAPcet fue desarrollada durante el hackathon virtual Scaling Ethereum.

https://ethglobal.com/showcase/deco-zxa8s

5. Desarrollo y fondeo de bienes públicos

Para ser congruentes con los principios de diseño de zenbit.eth, hemos desarrollado todos nuestros proyectos en público y con repositorios de código abierto⁵⁰. Sin embargo, el conocimiento y talento necesario para desarrollar en público requiere de mecanismos para fondear este tipo de proyectos. Para atender la sustentabilidad de zenbit.eth hemos participado en diferentes convocatorias de fondeo de bienes públicos, primero en la ronda de fondeo cuadrático @ devcon Colombia, donde gracias a la invaluable donación de quien apoyo nuestro proyecto pudimos obtener el tercer lugar en la tabla de fondeo de participantes⁵¹.

Adicionalmente, participamos en la segunda ronda de fondeo retroactivo de bienes públicos de Optimisim con Eneagon⁵², una aplicación de prefiltrado de proyectos de bienes públicos que implementa el modelo bicameral de Optimism⁵³ y la trazabilidad de tareas con metas de gitbub⁵⁴ para facilitar la coordinación entre desarrolladores y actores de interés desarrollando bienes públicos. Hemos utilizado esta aplicación de manera interna para distribuir fondos de manera retroactiva al talento que ha colaborado en el desarrollo de las diferentes experiencias que desarrollamos en zenbit. En la búsqueda de mejorar la modularidad y utilidad de la aplicación, participamos en los ¨Círculos¨de la ReFiDAO⁵⁵, donde realizamos un análisis colaborativo de los participantes para identificar las dimensiones sociotécnicas en la que que tienen impacto y su estado actual de desarrollo⁵⁶. A partir de este análisis identificamos varias funciones que podrían ser implementadas para acelerar el desarrollo de proyectos de bienes públicos. Sin embargo, debido a errores en la comunicación en el planteamiento del proyecto obtuvimos poca preferencia entre los evaluadores⁵⁷, además de opiniones que reflejan las áreas de oportunidad⁵⁸ que tenemos no solo con este proyecto sino como el conjunto de bienes públicos para ciudades web3 que componen a zenbit.

https://twitter.com/samonchain/status/1597743254245502976?s=20

https://twitter.com/zenbitMX/status/1641496256307515392?s=20

Durante el 2do trimestre de 2023 continuaremos con el desarrollo de los bienes públicos que componen a las ciudades web3 y realizaremos pruebas de campo en la ciudad de Querétaro para validar la capacidad de los contratos para registrar lugares públicos, negocios pequeños, la infraestructura y elementos organicos como NFTs con el fin de generar datos historicos sobre sus interacciones y modelar los incentivos que los participantes y colaboradores recibirán por crear, verificar y actualizar los datos de estos espacios digitalizados.

A partir de esta prueba en la ciudad de Querétaro, iteraremos las herramientas para ciudades web3 en otras urbes de México y Latinoamérica. En México realizaremos las pruebas de campo en colaboración con el INAI, la Secretaria de Desarrollo Sostenible del Municipio de Querétaro y el Laboratorio de Espacio Público, además de que convocaremos a representantes de organizaciones civiles, expertos de multiples disciplinas, representantes de organísmos autónomos y de dependencias públicas para ser participantes en la integración de una DAO que gestione y evalue el uso del presupuesto descentralizado durante estas pruebas.

Los resultados serán compartidos con diferentes comunidades de latinoamerica para plantear un protocolo de investigación y desarrollo colaborativos en multiples ciudades de la región y poder evaluar el desempeño de las herramientas para ciudades web3 en diferentes entornos urbanos.

Si deseas apoyar los bienes públicos desarrollados en zenbit.eth puedes ayudarnos:

1. Suscribiendote

2. Recolectando este artículo

3. Minteando los NFTs conmemorativos que acompañarán a cada reporte zenbit.Todos los ingresos y regalias serán usados para financiar la operación y el talento de nuestro equipo.

https://opensea.io/assets/ethereum/0x6C5ECb541457924c919b4C1536708D0d621E6579/0