diff --git a/pr-1699/404.html b/pr-1699/404.html index 275f35ba4d..baaebac9eb 100644 --- a/pr-1699/404.html +++ b/pr-1699/404.html @@ -35,7 +35,7 @@

Appearance

404

PAGE NOT FOUND

But if you don't change your direction, and if you keep looking, you may end up where you are heading.
Take me home
- + \ No newline at end of file diff --git a/pr-1699/README.html b/pr-1699/README.html index e8cc0bf556..a2e3332084 100644 --- a/pr-1699/README.html +++ b/pr-1699/README.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Celestia Documentation Site ​

Welcome to the official documentation repository for Celestia.

Here you'll find comprehensive guides, tutorials, and reference materials to help you make the most out of Celestia.

Building the site ​

To get started, clone the repository and run the following:

bash
yarn && yarn dev
yarn && yarn dev

This documentation site is built with VitePress

Contribution Guidelines ​

We love contributions from the community! Whether you're fixing typos, improving content clarity, or adding new topics, every contribution helps.

  • Fork & Clone: Fork this repository and clone it to your local machine.
  • Branch: Always create a new branch for your changes. Naming it relevantly.
  • Commit Changes: Make your changes and commit them with a clear and concise commit message.
  • Push & Create PR: Push your changes to your fork and create a pull request to the main branch of this repository.

Please ensure to review the detailed Contribution Guidelines above before making a pull request.

Directory Structure ​

  • /learn: A category for learning about Celestia.
  • /developers: A category with tutorials and guides for deploying rollups and interacting with Celestia nodes.
  • /nodes: Technical reference materials for all node types.
  • /community: A category for the Celestia community.
  • /public: Images, diagrams, and other media files used in the documentation.

Feedback & Suggestions ​

We value feedback from the community. If you have suggestions for improvements or find any discrepancies in the documentation, please raise an issue in this repository.

- +

Celestia Documentation Site ​

Welcome to the official documentation repository for Celestia.

Here you'll find comprehensive guides, tutorials, and reference materials to help you make the most out of Celestia.

Building the site ​

To get started, clone the repository and run the following:

bash
yarn && yarn dev
yarn && yarn dev

This documentation site is built with VitePress

Contribution Guidelines ​

We love contributions from the community! Whether you're fixing typos, improving content clarity, or adding new topics, every contribution helps.

  • Fork & Clone: Fork this repository and clone it to your local machine.
  • Branch: Always create a new branch for your changes. Naming it relevantly.
  • Commit Changes: Make your changes and commit them with a clear and concise commit message.
  • Push & Create PR: Push your changes to your fork and create a pull request to the main branch of this repository.

Please ensure to review the detailed Contribution Guidelines above before making a pull request.

Directory Structure ​

  • /learn: A category for learning about Celestia.
  • /developers: A category with tutorials and guides for deploying rollups and interacting with Celestia nodes.
  • /nodes: Technical reference materials for all node types.
  • /community: A category for the Celestia community.
  • /public: Images, diagrams, and other media files used in the documentation.

Feedback & Suggestions ​

We value feedback from the community. If you have suggestions for improvements or find any discrepancies in the documentation, please raise an issue in this repository.

+ \ No newline at end of file diff --git a/pr-1699/assets/README.md.44659d85.js b/pr-1699/assets/README.md.ebe4136d.js similarity index 96% rename from pr-1699/assets/README.md.44659d85.js rename to pr-1699/assets/README.md.ebe4136d.js index 75c92a611e..9498a67469 100644 --- a/pr-1699/assets/README.md.44659d85.js +++ b/pr-1699/assets/README.md.ebe4136d.js @@ -1 +1 @@ -import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Celestia Documentation Site","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Celestia Documentation Site | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"README.md","filePath":"README.md","lastUpdated":1725971357000}'),o={name:"README.md"},n=i('

Celestia Documentation Site ​

Welcome to the official documentation repository for Celestia.

Here you'll find comprehensive guides, tutorials, and reference materials to help you make the most out of Celestia.

Building the site ​

To get started, clone the repository and run the following:

bash
yarn && yarn dev
yarn && yarn dev

This documentation site is built with VitePress

Contribution Guidelines ​

We love contributions from the community! Whether you're fixing typos, improving content clarity, or adding new topics, every contribution helps.

Please ensure to review the detailed Contribution Guidelines above before making a pull request.

Directory Structure ​

Feedback & Suggestions ​

We value feedback from the community. If you have suggestions for improvements or find any discrepancies in the documentation, please raise an issue in this repository.

',16),s=[n];function r(l,c,u,d,p,h){return t(),a("div",null,s)}const y=e(o,[["render",r]]);export{g as __pageData,y as default}; +import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Celestia Documentation Site","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Celestia Documentation Site | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"README.md","filePath":"README.md","lastUpdated":1725992025000}'),o={name:"README.md"},n=i('

Celestia Documentation Site ​

Welcome to the official documentation repository for Celestia.

Here you'll find comprehensive guides, tutorials, and reference materials to help you make the most out of Celestia.

Building the site ​

To get started, clone the repository and run the following:

bash
yarn && yarn dev
yarn && yarn dev

This documentation site is built with VitePress

Contribution Guidelines ​

We love contributions from the community! Whether you're fixing typos, improving content clarity, or adding new topics, every contribution helps.

Please ensure to review the detailed Contribution Guidelines above before making a pull request.

Directory Structure ​

Feedback & Suggestions ​

We value feedback from the community. If you have suggestions for improvements or find any discrepancies in the documentation, please raise an issue in this repository.

',16),s=[n];function r(l,c,u,d,p,h){return t(),a("div",null,s)}const y=e(o,[["render",r]]);export{g as __pageData,y as default}; diff --git a/pr-1699/assets/README.md.44659d85.lean.js b/pr-1699/assets/README.md.ebe4136d.lean.js similarity index 76% rename from pr-1699/assets/README.md.44659d85.lean.js rename to pr-1699/assets/README.md.ebe4136d.lean.js index 8589025f51..35a2a79da5 100644 --- a/pr-1699/assets/README.md.44659d85.lean.js +++ b/pr-1699/assets/README.md.ebe4136d.lean.js @@ -1 +1 @@ -import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Celestia Documentation Site","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Celestia Documentation Site | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"README.md","filePath":"README.md","lastUpdated":1725971357000}'),o={name:"README.md"},n=i("",16),s=[n];function r(l,c,u,d,p,h){return t(),a("div",null,s)}const y=e(o,[["render",r]]);export{g as __pageData,y as default}; +import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Celestia Documentation Site","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Celestia Documentation Site | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"README.md","filePath":"README.md","lastUpdated":1725992025000}'),o={name:"README.md"},n=i("",16),s=[n];function r(l,c,u,d,p,h){return t(),a("div",null,s)}const y=e(o,[["render",r]]);export{g as __pageData,y as default}; diff --git a/pr-1699/assets/community_calendar.md.5a6b1214.js b/pr-1699/assets/community_calendar.md.f70856a8.js similarity index 95% rename from pr-1699/assets/community_calendar.md.5a6b1214.js rename to pr-1699/assets/community_calendar.md.f70856a8.js index e35f3c5b42..12873454d8 100644 --- a/pr-1699/assets/community_calendar.md.5a6b1214.js +++ b/pr-1699/assets/community_calendar.md.f70856a8.js @@ -1 +1 @@ -import{_ as t,o as n,c as o,k as e,a}from"./chunks/framework.b47e54aa.js";const b=JSON.parse(`{"title":"Community calendar","description":"Find all the different community call events happening in Celestia's community.","frontmatter":{"description":"Find all the different community call events happening in Celestia's community.","head":[["meta",{"name":"og:title","content":"Community calendar | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/calendar.md","filePath":"community/calendar.md","lastUpdated":1725971357000}`),l={name:"community/calendar.md"},c=e("h1",{id:"community-calendar",tabindex:"-1"},[a("Community calendar "),e("a",{class:"header-anchor",href:"#community-calendar","aria-label":'Permalink to "Community calendar"'},"​")],-1),i=e("p",null,"The Celestia community calendar is available for finding all the different community call events happening in Celestia's community.",-1),r=e("p",null,[e("a",{href:"https://calendar.google.com/calendar/u/0?cid=Y19za2JzbjIzNWszYmlzdHNoZ3RvNmw5ODYyNEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t",target:"_blank",rel:"noreferrer"},"Add the community calendar to your personal calendar"),a(" to stay updated with all the events.")],-1),s=e("p",null,[a("Explore "),e("a",{href:"https://github.com/celestiaorg/community-calls/blob/main/README.md",target:"_blank",rel:"noreferrer"},"past community call agendas, notes, and recordings"),a(" for more insights.")],-1),m=[c,i,r,s];function d(u,h,p,f,_,y){return n(),o("div",null,m)}const C=t(l,[["render",d]]);export{b as __pageData,C as default}; +import{_ as t,o as n,c as o,k as e,a}from"./chunks/framework.b47e54aa.js";const b=JSON.parse(`{"title":"Community calendar","description":"Find all the different community call events happening in Celestia's community.","frontmatter":{"description":"Find all the different community call events happening in Celestia's community.","head":[["meta",{"name":"og:title","content":"Community calendar | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/calendar.md","filePath":"community/calendar.md","lastUpdated":1725992025000}`),l={name:"community/calendar.md"},c=e("h1",{id:"community-calendar",tabindex:"-1"},[a("Community calendar "),e("a",{class:"header-anchor",href:"#community-calendar","aria-label":'Permalink to "Community calendar"'},"​")],-1),i=e("p",null,"The Celestia community calendar is available for finding all the different community call events happening in Celestia's community.",-1),r=e("p",null,[e("a",{href:"https://calendar.google.com/calendar/u/0?cid=Y19za2JzbjIzNWszYmlzdHNoZ3RvNmw5ODYyNEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t",target:"_blank",rel:"noreferrer"},"Add the community calendar to your personal calendar"),a(" to stay updated with all the events.")],-1),s=e("p",null,[a("Explore "),e("a",{href:"https://github.com/celestiaorg/community-calls/blob/main/README.md",target:"_blank",rel:"noreferrer"},"past community call agendas, notes, and recordings"),a(" for more insights.")],-1),m=[c,i,r,s];function d(u,h,p,f,_,y){return n(),o("div",null,m)}const C=t(l,[["render",d]]);export{b as __pageData,C as default}; diff --git a/pr-1699/assets/community_calendar.md.5a6b1214.lean.js b/pr-1699/assets/community_calendar.md.f70856a8.lean.js similarity index 95% rename from pr-1699/assets/community_calendar.md.5a6b1214.lean.js rename to pr-1699/assets/community_calendar.md.f70856a8.lean.js index e35f3c5b42..12873454d8 100644 --- a/pr-1699/assets/community_calendar.md.5a6b1214.lean.js +++ b/pr-1699/assets/community_calendar.md.f70856a8.lean.js @@ -1 +1 @@ -import{_ as t,o as n,c as o,k as e,a}from"./chunks/framework.b47e54aa.js";const b=JSON.parse(`{"title":"Community calendar","description":"Find all the different community call events happening in Celestia's community.","frontmatter":{"description":"Find all the different community call events happening in Celestia's community.","head":[["meta",{"name":"og:title","content":"Community calendar | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/calendar.md","filePath":"community/calendar.md","lastUpdated":1725971357000}`),l={name:"community/calendar.md"},c=e("h1",{id:"community-calendar",tabindex:"-1"},[a("Community calendar "),e("a",{class:"header-anchor",href:"#community-calendar","aria-label":'Permalink to "Community calendar"'},"​")],-1),i=e("p",null,"The Celestia community calendar is available for finding all the different community call events happening in Celestia's community.",-1),r=e("p",null,[e("a",{href:"https://calendar.google.com/calendar/u/0?cid=Y19za2JzbjIzNWszYmlzdHNoZ3RvNmw5ODYyNEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t",target:"_blank",rel:"noreferrer"},"Add the community calendar to your personal calendar"),a(" to stay updated with all the events.")],-1),s=e("p",null,[a("Explore "),e("a",{href:"https://github.com/celestiaorg/community-calls/blob/main/README.md",target:"_blank",rel:"noreferrer"},"past community call agendas, notes, and recordings"),a(" for more insights.")],-1),m=[c,i,r,s];function d(u,h,p,f,_,y){return n(),o("div",null,m)}const C=t(l,[["render",d]]);export{b as __pageData,C as default}; +import{_ as t,o as n,c as o,k as e,a}from"./chunks/framework.b47e54aa.js";const b=JSON.parse(`{"title":"Community calendar","description":"Find all the different community call events happening in Celestia's community.","frontmatter":{"description":"Find all the different community call events happening in Celestia's community.","head":[["meta",{"name":"og:title","content":"Community calendar | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/calendar.md","filePath":"community/calendar.md","lastUpdated":1725992025000}`),l={name:"community/calendar.md"},c=e("h1",{id:"community-calendar",tabindex:"-1"},[a("Community calendar "),e("a",{class:"header-anchor",href:"#community-calendar","aria-label":'Permalink to "Community calendar"'},"​")],-1),i=e("p",null,"The Celestia community calendar is available for finding all the different community call events happening in Celestia's community.",-1),r=e("p",null,[e("a",{href:"https://calendar.google.com/calendar/u/0?cid=Y19za2JzbjIzNWszYmlzdHNoZ3RvNmw5ODYyNEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t",target:"_blank",rel:"noreferrer"},"Add the community calendar to your personal calendar"),a(" to stay updated with all the events.")],-1),s=e("p",null,[a("Explore "),e("a",{href:"https://github.com/celestiaorg/community-calls/blob/main/README.md",target:"_blank",rel:"noreferrer"},"past community call agendas, notes, and recordings"),a(" for more insights.")],-1),m=[c,i,r,s];function d(u,h,p,f,_,y){return n(),o("div",null,m)}const C=t(l,[["render",d]]);export{b as __pageData,C as default}; diff --git a/pr-1699/assets/community_coc.md.db13614f.js b/pr-1699/assets/community_coc.md.de9fdd2a.js similarity index 98% rename from pr-1699/assets/community_coc.md.db13614f.js rename to pr-1699/assets/community_coc.md.de9fdd2a.js index c8fdf73327..b045dde83b 100644 --- a/pr-1699/assets/community_coc.md.db13614f.js +++ b/pr-1699/assets/community_coc.md.de9fdd2a.js @@ -1 +1 @@ -import{_ as e,o,c as a,Q as t}from"./chunks/framework.b47e54aa.js";const f=JSON.parse(`{"title":"Celestia.org Code of Conduct","description":"Fundamental shared values and special norms that distinguish Celestia's community.","frontmatter":{"description":"Fundamental shared values and special norms that distinguish Celestia's community.","head":[["meta",{"name":"og:title","content":"Celestia.org Code of Conduct | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/coc.md","filePath":"community/coc.md","lastUpdated":1725971357000}`),n={name:"community/coc.md"},i=t('

Celestia.org Code of Conduct ​

Our Pledge ​

We as Celestia.org members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards ​

Examples of behavior that contributes to a positive environment for our community include:

Examples of unacceptable behavior include:

Enforcement Responsibilities ​

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Scope ​

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement ​

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at Celestia.org Discord. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines ​

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction ​

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2. Warning ​

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban ​

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent Ban ​

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution ​

This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

',35),r=[i];function s(c,l,d,p,u,h){return o(),a("div",null,r)}const g=e(n,[["render",s]]);export{f as __pageData,g as default}; +import{_ as e,o,c as a,Q as t}from"./chunks/framework.b47e54aa.js";const f=JSON.parse(`{"title":"Celestia.org Code of Conduct","description":"Fundamental shared values and special norms that distinguish Celestia's community.","frontmatter":{"description":"Fundamental shared values and special norms that distinguish Celestia's community.","head":[["meta",{"name":"og:title","content":"Celestia.org Code of Conduct | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/coc.md","filePath":"community/coc.md","lastUpdated":1725992025000}`),n={name:"community/coc.md"},i=t('

Celestia.org Code of Conduct ​

Our Pledge ​

We as Celestia.org members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards ​

Examples of behavior that contributes to a positive environment for our community include:

Examples of unacceptable behavior include:

Enforcement Responsibilities ​

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Scope ​

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement ​

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at Celestia.org Discord. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines ​

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction ​

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2. Warning ​

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban ​

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent Ban ​

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution ​

This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

',35),r=[i];function s(c,l,d,p,u,h){return o(),a("div",null,r)}const g=e(n,[["render",s]]);export{f as __pageData,g as default}; diff --git a/pr-1699/assets/community_coc.md.db13614f.lean.js b/pr-1699/assets/community_coc.md.de9fdd2a.lean.js similarity index 82% rename from pr-1699/assets/community_coc.md.db13614f.lean.js rename to pr-1699/assets/community_coc.md.de9fdd2a.lean.js index d99f8d7830..65087f7b28 100644 --- a/pr-1699/assets/community_coc.md.db13614f.lean.js +++ b/pr-1699/assets/community_coc.md.de9fdd2a.lean.js @@ -1 +1 @@ -import{_ as e,o,c as a,Q as t}from"./chunks/framework.b47e54aa.js";const f=JSON.parse(`{"title":"Celestia.org Code of Conduct","description":"Fundamental shared values and special norms that distinguish Celestia's community.","frontmatter":{"description":"Fundamental shared values and special norms that distinguish Celestia's community.","head":[["meta",{"name":"og:title","content":"Celestia.org Code of Conduct | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/coc.md","filePath":"community/coc.md","lastUpdated":1725971357000}`),n={name:"community/coc.md"},i=t("",35),r=[i];function s(c,l,d,p,u,h){return o(),a("div",null,r)}const g=e(n,[["render",s]]);export{f as __pageData,g as default}; +import{_ as e,o,c as a,Q as t}from"./chunks/framework.b47e54aa.js";const f=JSON.parse(`{"title":"Celestia.org Code of Conduct","description":"Fundamental shared values and special norms that distinguish Celestia's community.","frontmatter":{"description":"Fundamental shared values and special norms that distinguish Celestia's community.","head":[["meta",{"name":"og:title","content":"Celestia.org Code of Conduct | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/coc.md","filePath":"community/coc.md","lastUpdated":1725992025000}`),n={name:"community/coc.md"},i=t("",35),r=[i];function s(c,l,d,p,u,h){return o(),a("div",null,r)}const g=e(n,[["render",s]]);export{f as __pageData,g as default}; diff --git a/pr-1699/assets/community_foundation-delegation-program.md.abd31332.js b/pr-1699/assets/community_foundation-delegation-program.md.ff7a7f05.js similarity index 99% rename from pr-1699/assets/community_foundation-delegation-program.md.abd31332.js rename to pr-1699/assets/community_foundation-delegation-program.md.ff7a7f05.js index 9495c771b2..7a9bda1272 100644 --- a/pr-1699/assets/community_foundation-delegation-program.md.abd31332.js +++ b/pr-1699/assets/community_foundation-delegation-program.md.ff7a7f05.js @@ -1 +1 @@ -import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/foundation-delegation-program.jpg",r="/docs-preview/pr-1699/img/cohort-timeline.jpg",b=JSON.parse('{"title":"The Celestia Foundation Delegation Program","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"The Celestia Foundation Delegation Program | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/foundation-delegation-program.md","filePath":"community/foundation-delegation-program.md","lastUpdated":1725971357000}'),n={name:"community/foundation-delegation-program.md"},l=i('

The Celestia Foundation Delegation Program ​

Delegation program banner

Objectives of the program ​

The primary objectives of the Celestia Foundation Delegation Program are:

Foundation delegation process ​

Program launch ​

Prospective validators are welcome to apply to the program starting February 6, 2024. The application is designed to assess a validator’s uptime performance and contributions to the Celestia ecosystem. Of the 100 total slots in Celestia’s active validator set, up to 50 will receive delegations within the program.

Application submissions will be reviewed by the Celestia Foundation. More details about the application and eligibility criteria are described below.

Cohort process ​

cohort timeline

Every 4 months, the Celestia Foundation will distribute a portion of the Foundation’s total available stake to a cohort of validators who meet certain criteria, detailed below. Here is an overview of how the cohort process will work for Cohort 1 and what that means for future cohorts.

Key Points ​

TierPlacementDelegation DurationRenewal By Cohort
First PlaceApplicants 1-2012 monthsCohort 4
Second PlaceApplicants 21-358 monthsCohort 3
Third PlaceApplicants 36-504 monthsCohort 2

During this period, so long as the validator maintains high uptime and does not violate the rules of the program, the validator will receive the delegation for the duration of the cohort they are currently in.

Eligibility criteria ​

The minimum requirements for participation in the program are as follows:

Not adhering to any of the criteria above will automatically disqualify your application, and violating any of the criteria after you have received delegation will result in withdrawal of the delegation. A participant who loses stake due to being jailed by the protocol may reapply to the program after 2 cohort periods.

Applicants are also expected to have reviewed Celestia docs and recommended guides on devops and monitoring setups.

Other optional but important criteria:

Undelegation criteria ​

Application ​

The program will be divided into cohorts with applications open for new applicants and renewal of existing applicants every 4 months. Validators will be delegated for up to a year. For each cohort, the deadline to apply/be evaluated (if you are reapplying) is exactly 1 month prior to the date of being delegated to.

Application details ​

Before applying, be ready to share the following:

Please note, the objective of the program is to contribute to Celestia’s resilience and uptime. If you contribute a lot to the Celestia ecosystem, but your validator uptime is low, this will negatively impact your chance at selection for the program. Furthermore, merely receiving delegation from the Foundation under the program does not guarantee your placement in the active validator set.

Get Started with the Application Form

Cohort information ​

The Foundation will report each cohort’s composition and the duration of their respective delegations.

IMPORTANT: Each validator selected for the program has to maintain a fully archival (non pruned) bridge node for both Mainnet Beta and Mocha.

Feedback process ​

Validators in the program will receive a feedback form every quarter, so the program can be continually improved.

',39),s=[l];function d(c,h,p,u,m,g){return t(),a("div",null,s)}const y=e(n,[["render",d]]);export{b as __pageData,y as default}; +import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/foundation-delegation-program.jpg",r="/docs-preview/pr-1699/img/cohort-timeline.jpg",b=JSON.parse('{"title":"The Celestia Foundation Delegation Program","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"The Celestia Foundation Delegation Program | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/foundation-delegation-program.md","filePath":"community/foundation-delegation-program.md","lastUpdated":1725992025000}'),n={name:"community/foundation-delegation-program.md"},l=i('

The Celestia Foundation Delegation Program ​

Delegation program banner

Objectives of the program ​

The primary objectives of the Celestia Foundation Delegation Program are:

Foundation delegation process ​

Program launch ​

Prospective validators are welcome to apply to the program starting February 6, 2024. The application is designed to assess a validator’s uptime performance and contributions to the Celestia ecosystem. Of the 100 total slots in Celestia’s active validator set, up to 50 will receive delegations within the program.

Application submissions will be reviewed by the Celestia Foundation. More details about the application and eligibility criteria are described below.

Cohort process ​

cohort timeline

Every 4 months, the Celestia Foundation will distribute a portion of the Foundation’s total available stake to a cohort of validators who meet certain criteria, detailed below. Here is an overview of how the cohort process will work for Cohort 1 and what that means for future cohorts.

Key Points ​

TierPlacementDelegation DurationRenewal By Cohort
First PlaceApplicants 1-2012 monthsCohort 4
Second PlaceApplicants 21-358 monthsCohort 3
Third PlaceApplicants 36-504 monthsCohort 2

During this period, so long as the validator maintains high uptime and does not violate the rules of the program, the validator will receive the delegation for the duration of the cohort they are currently in.

Eligibility criteria ​

The minimum requirements for participation in the program are as follows:

Not adhering to any of the criteria above will automatically disqualify your application, and violating any of the criteria after you have received delegation will result in withdrawal of the delegation. A participant who loses stake due to being jailed by the protocol may reapply to the program after 2 cohort periods.

Applicants are also expected to have reviewed Celestia docs and recommended guides on devops and monitoring setups.

Other optional but important criteria:

Undelegation criteria ​

Application ​

The program will be divided into cohorts with applications open for new applicants and renewal of existing applicants every 4 months. Validators will be delegated for up to a year. For each cohort, the deadline to apply/be evaluated (if you are reapplying) is exactly 1 month prior to the date of being delegated to.

Application details ​

Before applying, be ready to share the following:

Please note, the objective of the program is to contribute to Celestia’s resilience and uptime. If you contribute a lot to the Celestia ecosystem, but your validator uptime is low, this will negatively impact your chance at selection for the program. Furthermore, merely receiving delegation from the Foundation under the program does not guarantee your placement in the active validator set.

Get Started with the Application Form

Cohort information ​

The Foundation will report each cohort’s composition and the duration of their respective delegations.

IMPORTANT: Each validator selected for the program has to maintain a fully archival (non pruned) bridge node for both Mainnet Beta and Mocha.

Feedback process ​

Validators in the program will receive a feedback form every quarter, so the program can be continually improved.

',39),s=[l];function d(c,h,p,u,m,g){return t(),a("div",null,s)}const y=e(n,[["render",d]]);export{b as __pageData,y as default}; diff --git a/pr-1699/assets/community_foundation-delegation-program.md.abd31332.lean.js b/pr-1699/assets/community_foundation-delegation-program.md.ff7a7f05.lean.js similarity index 91% rename from pr-1699/assets/community_foundation-delegation-program.md.abd31332.lean.js rename to pr-1699/assets/community_foundation-delegation-program.md.ff7a7f05.lean.js index ee53d1015c..d7d20fb5d4 100644 --- a/pr-1699/assets/community_foundation-delegation-program.md.abd31332.lean.js +++ b/pr-1699/assets/community_foundation-delegation-program.md.ff7a7f05.lean.js @@ -1 +1 @@ -import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/foundation-delegation-program.jpg",r="/docs-preview/pr-1699/img/cohort-timeline.jpg",b=JSON.parse('{"title":"The Celestia Foundation Delegation Program","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"The Celestia Foundation Delegation Program | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/foundation-delegation-program.md","filePath":"community/foundation-delegation-program.md","lastUpdated":1725971357000}'),n={name:"community/foundation-delegation-program.md"},l=i("",39),s=[l];function d(c,h,p,u,m,g){return t(),a("div",null,s)}const y=e(n,[["render",d]]);export{b as __pageData,y as default}; +import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/foundation-delegation-program.jpg",r="/docs-preview/pr-1699/img/cohort-timeline.jpg",b=JSON.parse('{"title":"The Celestia Foundation Delegation Program","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"The Celestia Foundation Delegation Program | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/foundation-delegation-program.md","filePath":"community/foundation-delegation-program.md","lastUpdated":1725992025000}'),n={name:"community/foundation-delegation-program.md"},l=i("",39),s=[l];function d(c,h,p,u,m,g){return t(),a("div",null,s)}const y=e(n,[["render",d]]);export{b as __pageData,y as default}; diff --git a/pr-1699/assets/community_itn-tos.md.23529d8e.js b/pr-1699/assets/community_itn-tos.md.6454438f.js similarity index 99% rename from pr-1699/assets/community_itn-tos.md.23529d8e.js rename to pr-1699/assets/community_itn-tos.md.6454438f.js index 55f36bfa45..285a6686f2 100644 --- a/pr-1699/assets/community_itn-tos.md.23529d8e.js +++ b/pr-1699/assets/community_itn-tos.md.6454438f.js @@ -1 +1 @@ -import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const m=JSON.parse('{"title":"SUPPLEMENTAL INCENTIVIZED TESTNET TERMS","description":"These Terms govern your ability to participate in the Incentivized Testnet Award Program.","frontmatter":{"description":"These Terms govern your ability to participate in the Incentivized Testnet Award Program.","lastUpdated":false,"editLink":false,"head":[["meta",{"name":"og:title","content":"SUPPLEMENTAL INCENTIVIZED TESTNET TERMS | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/itn-tos.md","filePath":"community/itn-tos.md","lastUpdated":1725971357000}'),r={name:"community/itn-tos.md"},n=a('

SUPPLEMENTAL INCENTIVIZED TESTNET TERMS ​

Last Revised on 1/16/2023

Welcome to the Supplemental Terms (these "ITN Award Program Terms" or "Terms") for the Incentivized Testnet Award Program (the "ITN Award Program" or the "Program") as operated on behalf of Strange Loop Labs AG ("Company", "we" or "us"). The ITN Award Program provides eligible users of a Testnet designated by the Company the opportunity to earn rewards, which may include Celestia tokens. These Terms are supplemental to, and incorporate by reference, the broader Celestia Terms of Service ("Services Terms") available at Celestia Terms of Service.

Defined terms used but not defined herein have the meaning set forth in the Services Terms. The Program and your participation in it is a Service as defined under the Services Terms.

These Terms govern your ability to participate in the Program and any awards you receive from that participation, which may include Celestia tokens ("ITN Rewards").

Please read these Terms carefully, as they include important information about your legal rights. By participating in the Program or claiming ITN Rewards, you are agreeing to these Terms. If you do not understand or agree to these Terms, please do not participate in the Program or claim ITN Rewards.

In order to participate in the Program you must provide certain information about you. Our collection of such information, your rights with respect to such collection, and other relevant information is described in the Celestia Privacy Policy available at Celestia Privacy Policy, and is supplemented by Section 3 of these Terms.

The Program is a discretionary Service provided by the Company, pursuant to which the Company may, in its sole discretion, provide you ITN Rewards for your successful completion of certain tasks on a Testnet designated by the Company. Please note that any such Testnet itself (as well as any other Testnets or any mainnet deployment of the Celestia Protocol) is not a Service and does not constitute an element of the Services. We do not control the Celestia Protocol and accept no liability for its operation or its deployment in any testnet or mainnet environment.

1. General Terms ​

1.1 You must be eighteen (18) years of age or older and capable of forming a binding contract with the Company in order to participate in the Program or receive ITN Rewards.

1.2 You agree and acknowledge that you (a) may receive ITN Rewards for free (other than applicable taxes, if any) from your participation in the Program, (b) were not previously promised ITN Rewards, unless pursuant to a separate written agreement, and (c) took no action in anticipation of or in reliance on receiving any ITN Rewards, unless pursuant to a separate written agreement.

1.3 Your eligibility to participate in or receive ITN Rewards from the Program is subject to our sole discretion. The complete list of actions you must complete to earn ITN Rewards may not have been described in the documentation released by us from time to time, you may not receive ITN Rewards even if you successfully complete such actions, and no documentation related to the Program entitles you to any ITN Rewards or to participate in the Program.

1.4 You agree and acknowledge that (a) you are not a Prohibited Person, (b) you are not a U.S. Person as defined in Rule 902(k) of Regulation S under the U.S. Securities Act of 1933, as amended (the "1933 Act" or "Act"), (c) you will not use a VPN or other tool to circumvent any geoblock or other restrictions that we may have implemented for participants in the Program, and (d) you are not participating in, and have not become eligible to participate in, the Program by receiving credentials from any other person or entity. Any circumvention or violation of the above will permanently disqualify you from participation in the Program.

1.5 You agree and acknowledge that if you are unable to claim ITN Rewards due to technical bugs, gas fees, loss of access to a Wallet or the keys thereto, or for any other reason, you will have no recourse or claim against us or any other Company Entity and that neither we nor any other Company Entity will bear any liability.

1.6 You agree and acknowledge that claiming an ITN Reward may require reliance on or an integration with third party products (e.g., a Wallet or an unaffiliated network or blockchain) that we do not control. In the event that you are unable to access such products or integrations, or if they fail for any reason, and you are unable to participate in the Program or claim ITN Rewards, you will have no recourse or claim against us or any other Company Entity and neither we nor any other Company Entity will bear any liability.

1.7 The Company may share identifying information and documentation with certain vendors or third-party providers who provide such identity verification and sanctions and watchlist screening services (the "Third-Party Services"). You agree that your access and use of such Third-Party Services is governed solely by the terms and conditions of such Third-Party Services, and the Company is not responsible or liable for, and make no representations as to any aspect of such Third-Party Services, including, without limitation, their content or the manner in which they handle, protect, manage or process data or any interaction between you and the provider of such Third-Party Services. You irrevocably waive any claim against the Company with respect to such Third-Party Services. We are not liable for any damage or loss caused or alleged to be caused by or in connection with your enablement, access or use of any such Third-Party Services, or your reliance on the privacy practices, data security processes or other policies of such Third-Party Services.

2. Taxes ​

2.1 You are responsible for the payment of all taxes associated with your participation in the Program and your receipt of ITN Rewards. You agree to provide the Company with any additional information and complete any required tax or other forms relating to your receipt of ITN Rewards. You may suffer adverse tax consequences as a result of your participation in the Program or your receipt of ITN Rewards. You hereby represent that (a) you have consulted with a tax adviser that you deem advisable in connection with your participation, or that you have had the opportunity to obtain tax advice but have chosen not to do so, (b) the Company has not provided you with any tax advice with respect to your participation, and (c) you are not relying on the Company for any tax advice.

3. Supplemental Privacy Information ​

We may collect information to help us determine the reliability or uptime of your activities within the Program, including through the use of telemetry or metrics endpoints to collect and analyse such information, and link this information to a unique identifier to represent your activities within the Program. We may display all of the foregoing information on a public dashboard.

Additionally, we may collect certain information about you from Third-Party Services and may combine information we receive from you with information we obtain from Third-Party Services, including but not limited to:

We collect this information to confirm your eligibility to participate in the Program and receive ITN Rewards, comply with our legal obligations, detect and prevent fraud, and to provide you with the Program.

Any information we receive from third-party sources will be treated in accordance with the Celestia Privacy Policy, available at Celestia Privacy Policy. We are not responsible or liable for the accuracy of the information provided to us by third parties and are not responsible for any third party’s policies or practices. See Section 9 of the Celestia Privacy Policy for more information.

4. Certain Additional Representations ​

4.1 Receipt of Rewards Entirely for Own Account. Your eligibility to receive ITN Rewards is made in reliance upon your representation to the Company, which by your agreement to these Terms you hereby confirm, that any ITN Rewards you receive will be for your own account, not as a nominee or agent, and not with a view to the resale or distribution of any part thereof, and that you have no present intention of selling, granting any participation in, or otherwise distributing the same. By agreeing to these Terms, you further represent that you do not presently have any contract, undertaking, agreement or arrangement with any person to sell, transfer or grant participations to such person or to any third person, with respect to any ITN Rewards. If you are agreeing to these terms on behalf of an entity, that entity has not been formed for the specific purpose of obtaining the ITN Rewards.

4.2 Disclosure of Information. Your eligibility to receive ITN Rewards is made in reliance upon your representation to the Company, which by your agreement to these Terms you hereby confirm, that you have sufficient knowledge of and experience in business and financial matters to be able to evaluate the risks and merits of your participation in the Program and of any ITN Rewards and are able to bear the risks thereof. You hereby affirm that you have not relied on any representations or warranties made by the Company related to the Program, including, but not limited to, conversations of any kind, whether through oral or electronic communication, or any white paper.

4.3 Compliance with United States Securities Laws. You understand that the ITN Rewards have not been, and will not be, registered under the 1933 Act or any applicable state securities laws. You acknowledge that the availability of an exemption from the registration provisions of the Securities Act and other applicable state securities laws depends upon, among other things, the bona fide nature of your intent as described in Section 4.1 above and with respect to the accuracy of your representations as expressed throughout these Terms. You understand that the ITN Rewards may be deemed "restricted securities" under applicable United States federal and state securities laws and that, pursuant to these laws, you may be restricted from transferring any ITN Rewards unless they are registered with the Securities and Exchange Commission and qualified by state authorities, or an exemption from such registration and qualification requirements is available. You acknowledge that the Company does not undertake any obligation to register or qualify the ITN Rewards for resale, and exemptions from registration and qualification may not be available or may not permit you to transfer all or any of the ITN Rewards in the amounts or at the times proposed by you. You further acknowledge that if an exemption from registration or qualification is available, such exemption may be conditioned on various requirements including, but not limited to, the time and manner of sale, the holding period for the ITN Rewards, and on other factors outside of your control, for which the Company makes no assurances and may not be able to satisfy.

4.4 Compliance with Liechtenstein Security Law. You understand that nothing in these Terms will be deemed to constitute a prospectus of any sort in Liechtenstein or in any jurisdiction in the EU; nor does it in any way pertain to a public offering or a solicitation of an offer to buy any securities in Liechtenstein or in any jurisdiction in the EU.

4.5 No Public Market. You understand that no public market now exists for the ITN Rewards, and that the Company has not made any assurances that a public market will ever exist for the ITN Rewards.

4.6 No Solicitation. At no time were you presented with or solicited by any publicly issued or circulated newspaper, mail, radio, television or other form of general advertising or solicitation in connection with any invitation to participate in the Program or offer of the ITN Rewards.

4.7 Other Applicable Laws. You hereby represent that you have satisfied yourself as to the full observance of the laws of your jurisdiction in connection with any invitation to participate in the Program, receipt of ITN Awards, and other use of these Terms, including (a) the legal requirements within your jurisdiction for participating in the Program and receiving ITN Rewards, (b) any foreign exchange restrictions applicable to such participation or receipt, (c) any governmental or other consents that may need to be obtained, and (d) the income tax and other tax consequences, if any, that may be relevant to the receipt, holding, sale, or transfer of the ITN Rewards. Your participation in the Program and continued beneficial ownership of ITN Rewards will not violate any applicable securities or other laws of your jurisdiction.

4.8 Non-US Transaction. You are not a U.S. Person as defined in Rule 902(k) of Regulation S under the 1933 Act. The offer of the ITN Rewards to you was made in an offshore transaction (as defined in Rule 902(h) of Regulation S), no directed selling efforts (as defined in Rule 902(c) of Regulation S) were made in the United States, and you are not obtaining the ITN Rewards for the account or benefit of any U.S. Person.

4.9 Transfer Restrictions. You will not, during the Restricted Period (as defined below) offer or sell any of the ITN Rewards (or create or maintain any derivative position equivalent thereto) in the United States, to or for the account or benefit of a U.S. Person or other than in accordance with Regulation S. The Company reserves the right to impose additional transfer restrictions with respect to the ITN Rewards in its sole discretion.

4.10 Subsequent Sales. You will, after the expiration of the applicable Restricted Period, only offer, sell, pledge or otherwise transfer the ITN Rewards (or create or maintain any derivative position equivalent thereto) pursuant to registration under the 1933 Act or any available exemption therefrom and, in any case, in accordance with applicable state securities laws.

4.11 Legends. You acknowledge and agree that the ITN Rewards will be deemed to bear the following legends: (a) any legend required by the securities laws of any state or country to the extent such laws are applicable to the ITN Rewards represented by the certificate so legended, and (b): the following legend (and even without such legend the following restrictions apply):

THE ITN REWARDS HAVE NOT BEEN REGISTERED UNDER THE ACT WITH THE UNITED STATES SECURITIES AND EXCHANGE COMMISSION, AND THE COMPANY DOES NOT INTEND TO REGISTER THEM. THE ITN REWARDS HAVE BEEN OBTAINED TO HOLD FOR THE LONG TERM AND NOT WITH A VIEW TO, OR IN CONNECTION WITH, THE SALE OR DISTRIBUTION THEREFOR. PRIOR TO THE ONE YEAR ANNIVERSARY FROM THE TERMINATION OF THE ITN REWARD PROGRAM (THE "PROGRAM COMPLETION DATE" AND SUCH ONE YEAR PERIOD, THE "RESTRICTED PERIOD"), THE ITN REWARDS MAY NOT BE OFFERED OR SOLD (INCLUDING OPENING A SHORT POSITION IN SUCH ITN REWARDS) IN THE UNITED STATES OR TO U.S. PERSONS AS DEFINED BY RULE 902(k) ADOPTED UNDER THE ACT, OTHER THAN TO DISTRIBUTORS, UNLESS THE ITN REWARDS ARE REGISTERED UNDER THE ACT, OR AN EXEMPTION FROM THE REGISTRATION REQUIREMENTS OF THE ACT IS AVAILABLE. RECIPIENTS OF ITN REWARDS PRIOR TO THE ONE YEAR ANNIVERSARY OF THE PROGRAM COMPLETION DATE MAY SELL SUCH ITN REWARDS ONLY PURSUANT TO AN EXEMPTION FROM REGISTRATION UNDER THE ACT OR OTHERWISE IN ACCORDANCE WITH THE PROVISIONS OF REGULATION S OF THE ACT, OR IN TRANSACTIONS EFFECTED OUTSIDE OF THE UNITED STATES PROVIDED THEY DO NOT SOLICIT (AND NO ONE ACTING ON THEIR BEHALF SOLICITS) PURCHASERS IN THE UNITED STATES OR OTHERWISE ENGAGE(S) IN SELLING EFFORTS IN THE UNITED STATES AND PROVIDED THAT HEDGING TRANSACTIONS INVOLVING THESE ITN REWARDS MAY NOT BE CONDUCTED UNLESS IN COMPLIANCE WITH THE ACT. A HOLDER OF THE ITN REWARDS WHO IS A DISTRIBUTOR, DEALER, SUB-UNDERWRITER OR OTHER SECURITIES PROFESSIONAL, IN ADDITION, CANNOT PRIOR TO THE ONE YEAR ANNIVERSARY OF THE PROGRAM COMPLETION DATE SELL THE ITN REWARDS TO A U.S. PERSON AS DEFINED BY RULE 902(k) OF REGULATION S UNLESS THE ITN REWARDS ARE REGISTERED UNDER THE ACT OR AN EXEMPTION FROM REGISTRATION UNDER THE ACT IS AVAILABLE.

',37),i=[n];function s(c,l,d,h,u,p){return t(),o("div",null,i)}const T=e(r,[["render",s]]);export{m as __pageData,T as default}; +import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const m=JSON.parse('{"title":"SUPPLEMENTAL INCENTIVIZED TESTNET TERMS","description":"These Terms govern your ability to participate in the Incentivized Testnet Award Program.","frontmatter":{"description":"These Terms govern your ability to participate in the Incentivized Testnet Award Program.","lastUpdated":false,"editLink":false,"head":[["meta",{"name":"og:title","content":"SUPPLEMENTAL INCENTIVIZED TESTNET TERMS | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/itn-tos.md","filePath":"community/itn-tos.md","lastUpdated":1725992025000}'),r={name:"community/itn-tos.md"},n=a('

SUPPLEMENTAL INCENTIVIZED TESTNET TERMS ​

Last Revised on 1/16/2023

Welcome to the Supplemental Terms (these "ITN Award Program Terms" or "Terms") for the Incentivized Testnet Award Program (the "ITN Award Program" or the "Program") as operated on behalf of Strange Loop Labs AG ("Company", "we" or "us"). The ITN Award Program provides eligible users of a Testnet designated by the Company the opportunity to earn rewards, which may include Celestia tokens. These Terms are supplemental to, and incorporate by reference, the broader Celestia Terms of Service ("Services Terms") available at Celestia Terms of Service.

Defined terms used but not defined herein have the meaning set forth in the Services Terms. The Program and your participation in it is a Service as defined under the Services Terms.

These Terms govern your ability to participate in the Program and any awards you receive from that participation, which may include Celestia tokens ("ITN Rewards").

Please read these Terms carefully, as they include important information about your legal rights. By participating in the Program or claiming ITN Rewards, you are agreeing to these Terms. If you do not understand or agree to these Terms, please do not participate in the Program or claim ITN Rewards.

In order to participate in the Program you must provide certain information about you. Our collection of such information, your rights with respect to such collection, and other relevant information is described in the Celestia Privacy Policy available at Celestia Privacy Policy, and is supplemented by Section 3 of these Terms.

The Program is a discretionary Service provided by the Company, pursuant to which the Company may, in its sole discretion, provide you ITN Rewards for your successful completion of certain tasks on a Testnet designated by the Company. Please note that any such Testnet itself (as well as any other Testnets or any mainnet deployment of the Celestia Protocol) is not a Service and does not constitute an element of the Services. We do not control the Celestia Protocol and accept no liability for its operation or its deployment in any testnet or mainnet environment.

1. General Terms ​

1.1 You must be eighteen (18) years of age or older and capable of forming a binding contract with the Company in order to participate in the Program or receive ITN Rewards.

1.2 You agree and acknowledge that you (a) may receive ITN Rewards for free (other than applicable taxes, if any) from your participation in the Program, (b) were not previously promised ITN Rewards, unless pursuant to a separate written agreement, and (c) took no action in anticipation of or in reliance on receiving any ITN Rewards, unless pursuant to a separate written agreement.

1.3 Your eligibility to participate in or receive ITN Rewards from the Program is subject to our sole discretion. The complete list of actions you must complete to earn ITN Rewards may not have been described in the documentation released by us from time to time, you may not receive ITN Rewards even if you successfully complete such actions, and no documentation related to the Program entitles you to any ITN Rewards or to participate in the Program.

1.4 You agree and acknowledge that (a) you are not a Prohibited Person, (b) you are not a U.S. Person as defined in Rule 902(k) of Regulation S under the U.S. Securities Act of 1933, as amended (the "1933 Act" or "Act"), (c) you will not use a VPN or other tool to circumvent any geoblock or other restrictions that we may have implemented for participants in the Program, and (d) you are not participating in, and have not become eligible to participate in, the Program by receiving credentials from any other person or entity. Any circumvention or violation of the above will permanently disqualify you from participation in the Program.

1.5 You agree and acknowledge that if you are unable to claim ITN Rewards due to technical bugs, gas fees, loss of access to a Wallet or the keys thereto, or for any other reason, you will have no recourse or claim against us or any other Company Entity and that neither we nor any other Company Entity will bear any liability.

1.6 You agree and acknowledge that claiming an ITN Reward may require reliance on or an integration with third party products (e.g., a Wallet or an unaffiliated network or blockchain) that we do not control. In the event that you are unable to access such products or integrations, or if they fail for any reason, and you are unable to participate in the Program or claim ITN Rewards, you will have no recourse or claim against us or any other Company Entity and neither we nor any other Company Entity will bear any liability.

1.7 The Company may share identifying information and documentation with certain vendors or third-party providers who provide such identity verification and sanctions and watchlist screening services (the "Third-Party Services"). You agree that your access and use of such Third-Party Services is governed solely by the terms and conditions of such Third-Party Services, and the Company is not responsible or liable for, and make no representations as to any aspect of such Third-Party Services, including, without limitation, their content or the manner in which they handle, protect, manage or process data or any interaction between you and the provider of such Third-Party Services. You irrevocably waive any claim against the Company with respect to such Third-Party Services. We are not liable for any damage or loss caused or alleged to be caused by or in connection with your enablement, access or use of any such Third-Party Services, or your reliance on the privacy practices, data security processes or other policies of such Third-Party Services.

2. Taxes ​

2.1 You are responsible for the payment of all taxes associated with your participation in the Program and your receipt of ITN Rewards. You agree to provide the Company with any additional information and complete any required tax or other forms relating to your receipt of ITN Rewards. You may suffer adverse tax consequences as a result of your participation in the Program or your receipt of ITN Rewards. You hereby represent that (a) you have consulted with a tax adviser that you deem advisable in connection with your participation, or that you have had the opportunity to obtain tax advice but have chosen not to do so, (b) the Company has not provided you with any tax advice with respect to your participation, and (c) you are not relying on the Company for any tax advice.

3. Supplemental Privacy Information ​

We may collect information to help us determine the reliability or uptime of your activities within the Program, including through the use of telemetry or metrics endpoints to collect and analyse such information, and link this information to a unique identifier to represent your activities within the Program. We may display all of the foregoing information on a public dashboard.

Additionally, we may collect certain information about you from Third-Party Services and may combine information we receive from you with information we obtain from Third-Party Services, including but not limited to:

We collect this information to confirm your eligibility to participate in the Program and receive ITN Rewards, comply with our legal obligations, detect and prevent fraud, and to provide you with the Program.

Any information we receive from third-party sources will be treated in accordance with the Celestia Privacy Policy, available at Celestia Privacy Policy. We are not responsible or liable for the accuracy of the information provided to us by third parties and are not responsible for any third party’s policies or practices. See Section 9 of the Celestia Privacy Policy for more information.

4. Certain Additional Representations ​

4.1 Receipt of Rewards Entirely for Own Account. Your eligibility to receive ITN Rewards is made in reliance upon your representation to the Company, which by your agreement to these Terms you hereby confirm, that any ITN Rewards you receive will be for your own account, not as a nominee or agent, and not with a view to the resale or distribution of any part thereof, and that you have no present intention of selling, granting any participation in, or otherwise distributing the same. By agreeing to these Terms, you further represent that you do not presently have any contract, undertaking, agreement or arrangement with any person to sell, transfer or grant participations to such person or to any third person, with respect to any ITN Rewards. If you are agreeing to these terms on behalf of an entity, that entity has not been formed for the specific purpose of obtaining the ITN Rewards.

4.2 Disclosure of Information. Your eligibility to receive ITN Rewards is made in reliance upon your representation to the Company, which by your agreement to these Terms you hereby confirm, that you have sufficient knowledge of and experience in business and financial matters to be able to evaluate the risks and merits of your participation in the Program and of any ITN Rewards and are able to bear the risks thereof. You hereby affirm that you have not relied on any representations or warranties made by the Company related to the Program, including, but not limited to, conversations of any kind, whether through oral or electronic communication, or any white paper.

4.3 Compliance with United States Securities Laws. You understand that the ITN Rewards have not been, and will not be, registered under the 1933 Act or any applicable state securities laws. You acknowledge that the availability of an exemption from the registration provisions of the Securities Act and other applicable state securities laws depends upon, among other things, the bona fide nature of your intent as described in Section 4.1 above and with respect to the accuracy of your representations as expressed throughout these Terms. You understand that the ITN Rewards may be deemed "restricted securities" under applicable United States federal and state securities laws and that, pursuant to these laws, you may be restricted from transferring any ITN Rewards unless they are registered with the Securities and Exchange Commission and qualified by state authorities, or an exemption from such registration and qualification requirements is available. You acknowledge that the Company does not undertake any obligation to register or qualify the ITN Rewards for resale, and exemptions from registration and qualification may not be available or may not permit you to transfer all or any of the ITN Rewards in the amounts or at the times proposed by you. You further acknowledge that if an exemption from registration or qualification is available, such exemption may be conditioned on various requirements including, but not limited to, the time and manner of sale, the holding period for the ITN Rewards, and on other factors outside of your control, for which the Company makes no assurances and may not be able to satisfy.

4.4 Compliance with Liechtenstein Security Law. You understand that nothing in these Terms will be deemed to constitute a prospectus of any sort in Liechtenstein or in any jurisdiction in the EU; nor does it in any way pertain to a public offering or a solicitation of an offer to buy any securities in Liechtenstein or in any jurisdiction in the EU.

4.5 No Public Market. You understand that no public market now exists for the ITN Rewards, and that the Company has not made any assurances that a public market will ever exist for the ITN Rewards.

4.6 No Solicitation. At no time were you presented with or solicited by any publicly issued or circulated newspaper, mail, radio, television or other form of general advertising or solicitation in connection with any invitation to participate in the Program or offer of the ITN Rewards.

4.7 Other Applicable Laws. You hereby represent that you have satisfied yourself as to the full observance of the laws of your jurisdiction in connection with any invitation to participate in the Program, receipt of ITN Awards, and other use of these Terms, including (a) the legal requirements within your jurisdiction for participating in the Program and receiving ITN Rewards, (b) any foreign exchange restrictions applicable to such participation or receipt, (c) any governmental or other consents that may need to be obtained, and (d) the income tax and other tax consequences, if any, that may be relevant to the receipt, holding, sale, or transfer of the ITN Rewards. Your participation in the Program and continued beneficial ownership of ITN Rewards will not violate any applicable securities or other laws of your jurisdiction.

4.8 Non-US Transaction. You are not a U.S. Person as defined in Rule 902(k) of Regulation S under the 1933 Act. The offer of the ITN Rewards to you was made in an offshore transaction (as defined in Rule 902(h) of Regulation S), no directed selling efforts (as defined in Rule 902(c) of Regulation S) were made in the United States, and you are not obtaining the ITN Rewards for the account or benefit of any U.S. Person.

4.9 Transfer Restrictions. You will not, during the Restricted Period (as defined below) offer or sell any of the ITN Rewards (or create or maintain any derivative position equivalent thereto) in the United States, to or for the account or benefit of a U.S. Person or other than in accordance with Regulation S. The Company reserves the right to impose additional transfer restrictions with respect to the ITN Rewards in its sole discretion.

4.10 Subsequent Sales. You will, after the expiration of the applicable Restricted Period, only offer, sell, pledge or otherwise transfer the ITN Rewards (or create or maintain any derivative position equivalent thereto) pursuant to registration under the 1933 Act or any available exemption therefrom and, in any case, in accordance with applicable state securities laws.

4.11 Legends. You acknowledge and agree that the ITN Rewards will be deemed to bear the following legends: (a) any legend required by the securities laws of any state or country to the extent such laws are applicable to the ITN Rewards represented by the certificate so legended, and (b): the following legend (and even without such legend the following restrictions apply):

THE ITN REWARDS HAVE NOT BEEN REGISTERED UNDER THE ACT WITH THE UNITED STATES SECURITIES AND EXCHANGE COMMISSION, AND THE COMPANY DOES NOT INTEND TO REGISTER THEM. THE ITN REWARDS HAVE BEEN OBTAINED TO HOLD FOR THE LONG TERM AND NOT WITH A VIEW TO, OR IN CONNECTION WITH, THE SALE OR DISTRIBUTION THEREFOR. PRIOR TO THE ONE YEAR ANNIVERSARY FROM THE TERMINATION OF THE ITN REWARD PROGRAM (THE "PROGRAM COMPLETION DATE" AND SUCH ONE YEAR PERIOD, THE "RESTRICTED PERIOD"), THE ITN REWARDS MAY NOT BE OFFERED OR SOLD (INCLUDING OPENING A SHORT POSITION IN SUCH ITN REWARDS) IN THE UNITED STATES OR TO U.S. PERSONS AS DEFINED BY RULE 902(k) ADOPTED UNDER THE ACT, OTHER THAN TO DISTRIBUTORS, UNLESS THE ITN REWARDS ARE REGISTERED UNDER THE ACT, OR AN EXEMPTION FROM THE REGISTRATION REQUIREMENTS OF THE ACT IS AVAILABLE. RECIPIENTS OF ITN REWARDS PRIOR TO THE ONE YEAR ANNIVERSARY OF THE PROGRAM COMPLETION DATE MAY SELL SUCH ITN REWARDS ONLY PURSUANT TO AN EXEMPTION FROM REGISTRATION UNDER THE ACT OR OTHERWISE IN ACCORDANCE WITH THE PROVISIONS OF REGULATION S OF THE ACT, OR IN TRANSACTIONS EFFECTED OUTSIDE OF THE UNITED STATES PROVIDED THEY DO NOT SOLICIT (AND NO ONE ACTING ON THEIR BEHALF SOLICITS) PURCHASERS IN THE UNITED STATES OR OTHERWISE ENGAGE(S) IN SELLING EFFORTS IN THE UNITED STATES AND PROVIDED THAT HEDGING TRANSACTIONS INVOLVING THESE ITN REWARDS MAY NOT BE CONDUCTED UNLESS IN COMPLIANCE WITH THE ACT. A HOLDER OF THE ITN REWARDS WHO IS A DISTRIBUTOR, DEALER, SUB-UNDERWRITER OR OTHER SECURITIES PROFESSIONAL, IN ADDITION, CANNOT PRIOR TO THE ONE YEAR ANNIVERSARY OF THE PROGRAM COMPLETION DATE SELL THE ITN REWARDS TO A U.S. PERSON AS DEFINED BY RULE 902(k) OF REGULATION S UNLESS THE ITN REWARDS ARE REGISTERED UNDER THE ACT OR AN EXEMPTION FROM REGISTRATION UNDER THE ACT IS AVAILABLE.

',37),i=[n];function s(c,l,d,h,u,p){return t(),o("div",null,i)}const T=e(r,[["render",s]]);export{m as __pageData,T as default}; diff --git a/pr-1699/assets/community_itn-tos.md.23529d8e.lean.js b/pr-1699/assets/community_itn-tos.md.6454438f.lean.js similarity index 92% rename from pr-1699/assets/community_itn-tos.md.23529d8e.lean.js rename to pr-1699/assets/community_itn-tos.md.6454438f.lean.js index 8b587ee2a2..b5a0776f20 100644 --- a/pr-1699/assets/community_itn-tos.md.23529d8e.lean.js +++ b/pr-1699/assets/community_itn-tos.md.6454438f.lean.js @@ -1 +1 @@ -import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const m=JSON.parse('{"title":"SUPPLEMENTAL INCENTIVIZED TESTNET TERMS","description":"These Terms govern your ability to participate in the Incentivized Testnet Award Program.","frontmatter":{"description":"These Terms govern your ability to participate in the Incentivized Testnet Award Program.","lastUpdated":false,"editLink":false,"head":[["meta",{"name":"og:title","content":"SUPPLEMENTAL INCENTIVIZED TESTNET TERMS | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/itn-tos.md","filePath":"community/itn-tos.md","lastUpdated":1725971357000}'),r={name:"community/itn-tos.md"},n=a("",37),i=[n];function s(c,l,d,h,u,p){return t(),o("div",null,i)}const T=e(r,[["render",s]]);export{m as __pageData,T as default}; +import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const m=JSON.parse('{"title":"SUPPLEMENTAL INCENTIVIZED TESTNET TERMS","description":"These Terms govern your ability to participate in the Incentivized Testnet Award Program.","frontmatter":{"description":"These Terms govern your ability to participate in the Incentivized Testnet Award Program.","lastUpdated":false,"editLink":false,"head":[["meta",{"name":"og:title","content":"SUPPLEMENTAL INCENTIVIZED TESTNET TERMS | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/itn-tos.md","filePath":"community/itn-tos.md","lastUpdated":1725992025000}'),r={name:"community/itn-tos.md"},n=a("",37),i=[n];function s(c,l,d,h,u,p){return t(),o("div",null,i)}const T=e(r,[["render",s]]);export{m as __pageData,T as default}; diff --git a/pr-1699/assets/community_modular-meetup-guide.md.3d71d8e8.js b/pr-1699/assets/community_modular-meetup-guide.md.6b50cb94.js similarity index 99% rename from pr-1699/assets/community_modular-meetup-guide.md.3d71d8e8.js rename to pr-1699/assets/community_modular-meetup-guide.md.6b50cb94.js index d614ca4552..86143fd40e 100644 --- a/pr-1699/assets/community_modular-meetup-guide.md.3d71d8e8.js +++ b/pr-1699/assets/community_modular-meetup-guide.md.6b50cb94.js @@ -1 +1 @@ -import{_ as e,o as t,c as i,Q as o}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Modular Meetup guide","description":"A guide that helps in organizing a successful Modular Meetup.","frontmatter":{"description":"A guide that helps in organizing a successful Modular Meetup.","head":[["meta",{"name":"og:title","content":"Modular Meetup guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-guide.md","filePath":"community/modular-meetup-guide.md","lastUpdated":1725971357000}'),a={name:"community/modular-meetup-guide.md"},n=o('

Modular Meetup guide ​

These are recommended steps you can follow that can help you organize a successful Modular Meetup. You aren’t required to follow the entire checklist but it is available to help aid you in your journey to organize a Modular Meetup.

Before the Meetup ​

  1. Determine the meetup topic and objectives.
  2. Select a suitable date and time for the event.
  3. Secure a convenient and accessible venue that can accommodate the expected number of attendees.
  4. Finalize a schedule or agenda for the event, including speakers, presentations, and activities.
  5. Prepare and send out invitations to potential attendees using various channels (email, social media, community platforms, etc.).
  6. Create and share promotional materials (graphics, blog posts, etc.) to raise awareness about the meetup.
  7. Confirm speakers, including their availability, presentation topics, and technical requirements. If you are working from a Speaker List, please reach out to Nat for any support needed on coordination with speakers.
  8. Arrange any necessary equipment, such as microphones, projectors, and whiteboards.
  9. Plan and arrange refreshments, if applicable.
  10. Prepare and print any required materials, like agendas, name tags, and feedback forms.
  11. Coordinate with volunteers or team members to help manage the event.
  12. Set up a registration system or RSVP process to track attendance.
  13. Send out reminder messages to registered attendees prior to the event.
  14. Conduct a final review of the event logistics, including venue setup, equipment functionality, and volunteer roles.

During the Meetup ​

  1. Set up the venue, including arranging seating, preparing equipment, and displaying any promotional materials.
  2. Designate a registration area and ensure that someone is available to greet and check-in attendees.
  3. Welcome the attendees and provide an overview of the event schedule.
  4. Introduce speakers and facilitate any presentations or discussions.
  5. Encourage networking and interaction among attendees during breaks or dedicated activities.
  6. Capture the event with photos or videos for future promotions and documentation.
  7. Collect feedback from attendees using forms, online surveys, or informal conversations if needed.

After the Meetup ​

  1. Send follow-up messages to attendees, thanking them for their participation and soliciting additional feedback.
  2. Evaluate the success of the event by reviewing feedback and assessing key performance indicators (e.g., attendance, engagement, etc.).
  3. Analyze and document lessons learned, identifying areas for improvement in future meetups.
  4. Share event highlights, photos, and key takeaways with the community through social media, blog posts, or newsletters.
  5. Connect with speakers, attendees, and volunteers to maintain and strengthen relationships.
  6. Begin planning for the next meetup, applying insights gained from the previous event to enhance the experience for future attendees.

Logistics and guidance ​

These are provided guidelines for different components of kickstarting a Modular Meetup to help you get started on the logistics of organizing a meetup. A lot of those guidelines are thanks to the wonderful write ups in Ethereum Meetup Support Program and Elastic Community Organizer Guides.

Venue ​

Selecting the perfect venue for your Modular Meetup is essential in creating a welcoming atmosphere for the Celestia community.

  1. Startup Incubators
    • Often they would have spaces for meetups.
  2. Libraries
    • Libraries can normally have spaces for meetups at little to no costs
  3. Co-working spaces:
    • Co-working spaces might be able to offer necessary equipment like microphones, projectors, and whiteboards.
  4. Restaurants:
    • Restaurants might have private rooms for larger groups of people that you can book, depending on the restaurant.
  5. Universities and Blockchain Clubs:
    • Partnering with universities and their local university clubs can offer you a lot of spaces for meetups, as well as necessary equipments if needed for giving a talk.
  6. Other options:
    • If you're having difficulty finding a venue, don't hesitate to ask for help within the Celestia community. Your fellow organizers and attendees may have valuable suggestions or connections.

An ideal venue should offer:

Consider recording the event, even with a smartphone, to share with the community later. If the speaker uses a microphone, their voice will be more audible in the video. We might be able to post those recordings of the meetup talks on a meetup youtube channel after.

Remember to negotiate on costs and seek discounts, emphasizing that your meetup benefits the community.

Collaborate with your venue provider to explore options like borrowing recording equipment, tripods, or even having them record the event for you. Some providers may offer these services for free or at a reduced cost.

Catering and refreshments ​

Providing refreshments or catering for your Modular Meetup enhances the overall experience and encourages networking among attendees.

  1. Determine your budget
    • Identify the amount you can allocate for food and drinks at your event which will help you determine how much you can bring in refreshments. You can also contact the Celestia Devrel team for ideas and support. Costs for refreshments and drinks can vary depending on your location, so be mindful to be flexible on your plans according to your specific location and budget.
  2. Offer a variety of refreshments
    • If you're ordering in, pizza and finger foods work well, but you can also have more budget-friendly options for food.
    • Offering drinks like beer, soda, or lemonade are great, but water also works. Keep in mind that not everyone drinks alcohol so it’s not a requirement. But having at least water and plastic cups works well.
  3. Plan ahead
    • Order refreshments 1 or 2 days in advance and schedule delivery to avoid last-minute stress during the event.

By following these recommendations, you'll be able to provide enjoyable refreshments for your Celestia Modular Meetup attendees while fostering a friendly and engaging atmosphere.

Audience ​

Understanding your audience and estimating attendance are crucial for organizing successful Modular Meetups for Celestia.

  1. Research the local tech scene:
    • Investigate the types of meetups and events popular in your area. Attend other technology-focused events to get a sense of the audience size and interests. This information will help you tailor your meetup to attract a larger audience.
  2. Assess the availability of speakers:
    • Before organizing a meetup, ensure that you have access to a pool of knowledgeable speakers. If you anticipate difficulty in securing speakers, consider joining forces with an existing meetup group or speaking at other events before launching a new group. This approach will help spread the word about your planned Modular Meetup and gauge interest. Speakers are covered in the following section with a reference to Speaker List offered by the Modular Meetup program.
  3. Establish connections with other user groups:
    • Forge relationships with other tech-focused meetup groups to mutually promote each other's events, potentially increasing attendance.
  4. Set a regular routine for your meetup:
    • Communicate how often you plan to hold meetups, whether it's monthly or quarterly, to help attendees manage their expectations and maintain their interest.
  5. Organize casual meetups:
    • If there's a gap between more formal events, arrange casual meetups at pubs or cafes to keep people engaged and connect with potential speakers for future events.
  6. Estimate the number of attendees:
    • Consider factors such as the size of your city, the popularity of the topic, and the appeal of the event description when estimating attendance.

Speakers ​

Securing engaging and knowledgeable speakers is key to hosting an exceptional Celestia Modular Meetup.

  1. Define your event topic
    • Determine the theme of your event, focusing on areas such as DeFi, Gaming, NFTs, coding workshops, protocol changes, rollups, data availability, or other topics relevant to the Modular ecosystem. This will help you find speakers with expertise in the chosen subject.
  2. Utilize the Speaker List provided by the Modular Meetup program
    • As a meetup organizer, you have access to a curated list of talented speakers from Celestia Labs and the broader Modular ecosystem. This valuable resource can connect you with experts who can share their knowledge with your meetup attendees.
  3. Aim for multiple speakers
    • Ideally, invite 2-3 speakers to your event, allotting 20-40 minutes per talk. Schedule short breaks between presentations to maintain audience engagement.
  4. Organize the speaker lineup
    • Discuss the topics and slides with your speakers before the event to ensure a smooth flow. Arrange the talks in a logical order, saving the most impactful presentation for last.
  5. Invite local speakers
    • For your first meetup, consider presenting an introduction to the Celestia ecosystem or a specific area of interest. Encourage local experts or enthusiasts to speak at future meetups. This approach fosters community involvement and helps build a network of potential speakers.
  6. Seek speaker referrals
    • Ask your current speakers, attendees, or other meetup organizers for referrals. Personal connections often lead to discovering new speakers with valuable insights.
  7. Leverage your meetup discussion board
    • Post a call for speakers on your meetup discussion board to reach out to potential presenters within your community. Be clear about the event theme and requirements to attract relevant speakers.
  8. Offer incentives and appreciation
    • Reward speakers with tokens of gratitude, such as T-shirts, gifts, or public recognition, to show your appreciation for their contribution to the meetup. The Celestia Labs Devrel team can help with swag logistics if needed.

Sponsors ​

Finding sponsors for your meetup can be challenging, but securing financial support is crucial for covering costs related to venue and refreshments.

  1. Leverage Celestia Labs' support
    • Celestia Labs may offer co-sponsorship for your meetup. However, they also encourage organizers to find local co-sponsors to help cover costs and create a more sustainable event.
  2. Offer value to your sponsors:
    • Show potential sponsors how partnering with your event will benefit them. Include their logo on event banners, mention them in the event description, and give them a shoutout at the beginning of the event. If they desire, allow them to place a rollup banner at the venue.
  3. Reach out to your network
    • Ask friends and acquaintances if they know of coworking spaces, schools, universities, or companies interested in sponsorship. A personal connection can significantly increase the chances of securing support.
  4. Approach speakers for sponsorship
    • Request speakers or their affiliated projects to contribute towards the event's expenses, such as catering costs. This can be an effective way to obtain additional funding.
  5. Create a sponsorship deck
    • Develop a compelling sponsorship deck to pitch your event to tech companies in your city or potential online sponsors. This presentation should highlight the benefits of supporting your event and showcase past successful meetups.
  6. Research local companies
    • Investigate businesses in your area that may be interested in sponsoring your event. Tailor your pitch to align with their industry and demonstrate how the meetup can benefit their company.
  7. Engage sponsors during the event
    • Allow sponsors to briefly address the audience, participate in Q&A sessions, or mention their hiring needs. Remember to avoid sales pitches, as they can negatively impact the meetup experience.
  8. Thank your sponsors
    • Express gratitude to your sponsors at the beginning and end of the meetup. Acknowledging their support encourages continued collaboration and enhances the credibility of your event.

Communications and marketing ​

Effectively marketing and announcing your Modular Meetup is essential for attracting attendees and ensuring a successful event.

  1. Plan your announcement
    • Announce your meetup at least two weeks prior. This gives your audience ample time to prepare and increases the likelihood of their attendance.
  2. Utilize Celestia Labs' resources
    • Celestia Labs can help co-promote your meetup on social media and Discord. They can also add your event to their online calendar, email local contacts, and share the event via their Developer Relations Team on Twitter. Don't hesitate to reach out to them for assistance.
  3. Share on social media
    • Promote your event on Twitter and any other popular social media platforms in your area. Tag speakers, sponsors, and use relevant hashtags to increase visibility.
  4. Leverage local community groups
    • Post your event in local Telegram, Discord, or other community groups relevant to your city. These groups often have many members who may be interested in attending your event.
  5. Engage speakers and the venue
    • Maintain communication with speakers and the venue to ensure any changes can be announced in advance. Trust is critical, so avoid canceling planned meetups whenever possible.
  6. Send reminders via meetup.com (optional)
    • After announcing your event, send a warm invite to your meetup group members through meetup.com. Additionally, send a reminder email one day before the event to encourage attendance.
  7. Share with friends and family
    • Invite your friends, family, and acquaintances to the meetup, as they may help spread the word or know someone interested in the event.
  8. Utilize conference groups
    • If you've attended conferences, share your meetup in the associated Telegram or social media groups, as there may be members nearby who would be interested in attending.

Recording ​

Recording and live-streaming your Modular Meetup can greatly benefit those who cannot attend in person and expand the reach of your event.

  1. Plan for recording
    • Consider recording your meetup to create additional learning resources and share the knowledge with a broader audience.
  2. Consider live-streaming
    • Live-streaming your event on platforms like Twitch, YouTube, or Twitter allows remote participants to watch and engage in the meetup. This can also boost your event's reach and create a sense of inclusion for those who couldn't attend in person.
  3. Coordinate with Celestia Labs
    • Celestia Labs can potentially help cover recording costs and promote recorded meetups. Reach out to them at meetups@celestia.org to discuss available options and support. They can also assist with finding local contacts for recording if you don't have one already.
  4. Utilize available resources
    • If you have a small budget, consider allocating some funds for recording and live-streaming your event. Look for local professionals or affordable equipment rentals to ensure high-quality recordings.
  5. Share recordings on Celestia Labs' channels
    • Celestia Labs can help promote recorded meetups by sharing videos in their meetups playlist on YouTube and hosting them on their website. Ensure you coordinate with Celestia Labs to provide them with the recorded video.
  6. Promote recorded content
    • Share the recordings on your social media channels and meetup group after the event. This helps attendees revisit the content and allows those who couldn't attend to learn from the talks.

Utilizing Meetup.com platform ​

Celestia Labs is committed to supporting your meetup efforts by helping you with meetup.com, from setting up the group to covering organizer dues. Below is a detailed overview of how Celestia Labs can assist you.

  1. Meetup.com organizer dues
    • Celestia Labs is happy to cover organizer dues for meetup.com. To get started, send an email to meetups@celestia.org and let them help you with the process.
  2. Co-organizing existing groups
    • If you already have a meetup.com group but need Celestia Labs' assistance with organizing or covering dues, email meetups@celestia.org to add one of their employees as the Organizer.
  3. Setting up groups on Meetup.com
    • Celestia Labs will help you set up your meetup group, including logos, naming, custom URLs, group description, and other essential details. They provide a unique logo for Celestia Modular Meetups, which you can use for your group.
  4. User group naming
    • Celestia Labs recommends naming your group "Celestia Modular Meetup" to encompass various aspects of the Celestia community and create a consistent brand.
  5. Custom URL for the group
    • Meetup.com allows you to create a custom URL for your user group. Celestia Labs encourages consistent URLs across regions, making it easy for people to find your meetup group.
  6. Group description
    • Celestia Labs has a standard group description to ensure consistency across all meetups. However, if you'd like to customize it, let them know.
  7. New member intake questions
    • To improve the quality of your meetups, Celestia Labs suggests a set of intake questions for new members. The answers can help you better understand their needs and interests, allowing you to plan engaging meetups.
  8. Welcome message
    • Celestia Labs provides a welcome message for new members joining your group. If you'd like to customize this message, let them know.

Onboarding questions for community members joining a Modular Meetup ​

  1. Q1: How did you hear about this Modular Meetup?
    • Why: This information helps us understand the most effective channels for recruiting new participants to the meetup.
  2. Q2: What do you hope to gain by participating in this meetup? (e.g., networking, learning about Celestia, learning about Modularity, finding a job, etc.)
    • Why: This information helps us cater to the needs of the user group members. If most attendees are looking for networking opportunities, we can schedule casual meetups alongside informative talks.
  3. Q3: Are you currently using or planning to use Celestia, Rollkit, Celestia’s Node API or any of the rollups deployed on Celestia? Tell us all about it. We will use your response to help us better understand what talks would be most beneficial to the group.
    • Why: Responses to this question help us determine the most relevant talks for the group members. If we discover that most participants are interested in a specific area, we can tailor the talks accordingly.
  4. Q4: We love Celestia and the modular ecosystem, but we also appreciate other Web3 technologies. What other topics would you like to hear about? (e.g., Infrastructure, Data Storage, DID, MEV)
    • Why: Knowing our group participants' interests in other technical areas helps us understand what related topics would be useful and valuable to the group, which in turn helps when recruiting speakers.
  5. Q5: Would you be interested in speaking at a future meetup? We welcome 2-minute lightning talks to 1-hour deep dives. Would you be interested in hosting a meetup? If you answer yes to this question, the group organizers will contact you to follow up.
    • Why: One of the challenges in hosting regular meetups is finding speakers. We hope this question will identify people eager to share their stories and expertise with the group, making the lives of organizers easier.
',42),r=[n];function s(l,u,c,d,h,p){return t(),i("div",null,r)}const f=e(a,[["render",s]]);export{g as __pageData,f as default}; +import{_ as e,o as t,c as i,Q as o}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Modular Meetup guide","description":"A guide that helps in organizing a successful Modular Meetup.","frontmatter":{"description":"A guide that helps in organizing a successful Modular Meetup.","head":[["meta",{"name":"og:title","content":"Modular Meetup guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-guide.md","filePath":"community/modular-meetup-guide.md","lastUpdated":1725992025000}'),a={name:"community/modular-meetup-guide.md"},n=o('

Modular Meetup guide ​

These are recommended steps you can follow that can help you organize a successful Modular Meetup. You aren’t required to follow the entire checklist but it is available to help aid you in your journey to organize a Modular Meetup.

Before the Meetup ​

  1. Determine the meetup topic and objectives.
  2. Select a suitable date and time for the event.
  3. Secure a convenient and accessible venue that can accommodate the expected number of attendees.
  4. Finalize a schedule or agenda for the event, including speakers, presentations, and activities.
  5. Prepare and send out invitations to potential attendees using various channels (email, social media, community platforms, etc.).
  6. Create and share promotional materials (graphics, blog posts, etc.) to raise awareness about the meetup.
  7. Confirm speakers, including their availability, presentation topics, and technical requirements. If you are working from a Speaker List, please reach out to Nat for any support needed on coordination with speakers.
  8. Arrange any necessary equipment, such as microphones, projectors, and whiteboards.
  9. Plan and arrange refreshments, if applicable.
  10. Prepare and print any required materials, like agendas, name tags, and feedback forms.
  11. Coordinate with volunteers or team members to help manage the event.
  12. Set up a registration system or RSVP process to track attendance.
  13. Send out reminder messages to registered attendees prior to the event.
  14. Conduct a final review of the event logistics, including venue setup, equipment functionality, and volunteer roles.

During the Meetup ​

  1. Set up the venue, including arranging seating, preparing equipment, and displaying any promotional materials.
  2. Designate a registration area and ensure that someone is available to greet and check-in attendees.
  3. Welcome the attendees and provide an overview of the event schedule.
  4. Introduce speakers and facilitate any presentations or discussions.
  5. Encourage networking and interaction among attendees during breaks or dedicated activities.
  6. Capture the event with photos or videos for future promotions and documentation.
  7. Collect feedback from attendees using forms, online surveys, or informal conversations if needed.

After the Meetup ​

  1. Send follow-up messages to attendees, thanking them for their participation and soliciting additional feedback.
  2. Evaluate the success of the event by reviewing feedback and assessing key performance indicators (e.g., attendance, engagement, etc.).
  3. Analyze and document lessons learned, identifying areas for improvement in future meetups.
  4. Share event highlights, photos, and key takeaways with the community through social media, blog posts, or newsletters.
  5. Connect with speakers, attendees, and volunteers to maintain and strengthen relationships.
  6. Begin planning for the next meetup, applying insights gained from the previous event to enhance the experience for future attendees.

Logistics and guidance ​

These are provided guidelines for different components of kickstarting a Modular Meetup to help you get started on the logistics of organizing a meetup. A lot of those guidelines are thanks to the wonderful write ups in Ethereum Meetup Support Program and Elastic Community Organizer Guides.

Venue ​

Selecting the perfect venue for your Modular Meetup is essential in creating a welcoming atmosphere for the Celestia community.

  1. Startup Incubators
    • Often they would have spaces for meetups.
  2. Libraries
    • Libraries can normally have spaces for meetups at little to no costs
  3. Co-working spaces:
    • Co-working spaces might be able to offer necessary equipment like microphones, projectors, and whiteboards.
  4. Restaurants:
    • Restaurants might have private rooms for larger groups of people that you can book, depending on the restaurant.
  5. Universities and Blockchain Clubs:
    • Partnering with universities and their local university clubs can offer you a lot of spaces for meetups, as well as necessary equipments if needed for giving a talk.
  6. Other options:
    • If you're having difficulty finding a venue, don't hesitate to ask for help within the Celestia community. Your fellow organizers and attendees may have valuable suggestions or connections.

An ideal venue should offer:

Consider recording the event, even with a smartphone, to share with the community later. If the speaker uses a microphone, their voice will be more audible in the video. We might be able to post those recordings of the meetup talks on a meetup youtube channel after.

Remember to negotiate on costs and seek discounts, emphasizing that your meetup benefits the community.

Collaborate with your venue provider to explore options like borrowing recording equipment, tripods, or even having them record the event for you. Some providers may offer these services for free or at a reduced cost.

Catering and refreshments ​

Providing refreshments or catering for your Modular Meetup enhances the overall experience and encourages networking among attendees.

  1. Determine your budget
    • Identify the amount you can allocate for food and drinks at your event which will help you determine how much you can bring in refreshments. You can also contact the Celestia Devrel team for ideas and support. Costs for refreshments and drinks can vary depending on your location, so be mindful to be flexible on your plans according to your specific location and budget.
  2. Offer a variety of refreshments
    • If you're ordering in, pizza and finger foods work well, but you can also have more budget-friendly options for food.
    • Offering drinks like beer, soda, or lemonade are great, but water also works. Keep in mind that not everyone drinks alcohol so it’s not a requirement. But having at least water and plastic cups works well.
  3. Plan ahead
    • Order refreshments 1 or 2 days in advance and schedule delivery to avoid last-minute stress during the event.

By following these recommendations, you'll be able to provide enjoyable refreshments for your Celestia Modular Meetup attendees while fostering a friendly and engaging atmosphere.

Audience ​

Understanding your audience and estimating attendance are crucial for organizing successful Modular Meetups for Celestia.

  1. Research the local tech scene:
    • Investigate the types of meetups and events popular in your area. Attend other technology-focused events to get a sense of the audience size and interests. This information will help you tailor your meetup to attract a larger audience.
  2. Assess the availability of speakers:
    • Before organizing a meetup, ensure that you have access to a pool of knowledgeable speakers. If you anticipate difficulty in securing speakers, consider joining forces with an existing meetup group or speaking at other events before launching a new group. This approach will help spread the word about your planned Modular Meetup and gauge interest. Speakers are covered in the following section with a reference to Speaker List offered by the Modular Meetup program.
  3. Establish connections with other user groups:
    • Forge relationships with other tech-focused meetup groups to mutually promote each other's events, potentially increasing attendance.
  4. Set a regular routine for your meetup:
    • Communicate how often you plan to hold meetups, whether it's monthly or quarterly, to help attendees manage their expectations and maintain their interest.
  5. Organize casual meetups:
    • If there's a gap between more formal events, arrange casual meetups at pubs or cafes to keep people engaged and connect with potential speakers for future events.
  6. Estimate the number of attendees:
    • Consider factors such as the size of your city, the popularity of the topic, and the appeal of the event description when estimating attendance.

Speakers ​

Securing engaging and knowledgeable speakers is key to hosting an exceptional Celestia Modular Meetup.

  1. Define your event topic
    • Determine the theme of your event, focusing on areas such as DeFi, Gaming, NFTs, coding workshops, protocol changes, rollups, data availability, or other topics relevant to the Modular ecosystem. This will help you find speakers with expertise in the chosen subject.
  2. Utilize the Speaker List provided by the Modular Meetup program
    • As a meetup organizer, you have access to a curated list of talented speakers from Celestia Labs and the broader Modular ecosystem. This valuable resource can connect you with experts who can share their knowledge with your meetup attendees.
  3. Aim for multiple speakers
    • Ideally, invite 2-3 speakers to your event, allotting 20-40 minutes per talk. Schedule short breaks between presentations to maintain audience engagement.
  4. Organize the speaker lineup
    • Discuss the topics and slides with your speakers before the event to ensure a smooth flow. Arrange the talks in a logical order, saving the most impactful presentation for last.
  5. Invite local speakers
    • For your first meetup, consider presenting an introduction to the Celestia ecosystem or a specific area of interest. Encourage local experts or enthusiasts to speak at future meetups. This approach fosters community involvement and helps build a network of potential speakers.
  6. Seek speaker referrals
    • Ask your current speakers, attendees, or other meetup organizers for referrals. Personal connections often lead to discovering new speakers with valuable insights.
  7. Leverage your meetup discussion board
    • Post a call for speakers on your meetup discussion board to reach out to potential presenters within your community. Be clear about the event theme and requirements to attract relevant speakers.
  8. Offer incentives and appreciation
    • Reward speakers with tokens of gratitude, such as T-shirts, gifts, or public recognition, to show your appreciation for their contribution to the meetup. The Celestia Labs Devrel team can help with swag logistics if needed.

Sponsors ​

Finding sponsors for your meetup can be challenging, but securing financial support is crucial for covering costs related to venue and refreshments.

  1. Leverage Celestia Labs' support
    • Celestia Labs may offer co-sponsorship for your meetup. However, they also encourage organizers to find local co-sponsors to help cover costs and create a more sustainable event.
  2. Offer value to your sponsors:
    • Show potential sponsors how partnering with your event will benefit them. Include their logo on event banners, mention them in the event description, and give them a shoutout at the beginning of the event. If they desire, allow them to place a rollup banner at the venue.
  3. Reach out to your network
    • Ask friends and acquaintances if they know of coworking spaces, schools, universities, or companies interested in sponsorship. A personal connection can significantly increase the chances of securing support.
  4. Approach speakers for sponsorship
    • Request speakers or their affiliated projects to contribute towards the event's expenses, such as catering costs. This can be an effective way to obtain additional funding.
  5. Create a sponsorship deck
    • Develop a compelling sponsorship deck to pitch your event to tech companies in your city or potential online sponsors. This presentation should highlight the benefits of supporting your event and showcase past successful meetups.
  6. Research local companies
    • Investigate businesses in your area that may be interested in sponsoring your event. Tailor your pitch to align with their industry and demonstrate how the meetup can benefit their company.
  7. Engage sponsors during the event
    • Allow sponsors to briefly address the audience, participate in Q&A sessions, or mention their hiring needs. Remember to avoid sales pitches, as they can negatively impact the meetup experience.
  8. Thank your sponsors
    • Express gratitude to your sponsors at the beginning and end of the meetup. Acknowledging their support encourages continued collaboration and enhances the credibility of your event.

Communications and marketing ​

Effectively marketing and announcing your Modular Meetup is essential for attracting attendees and ensuring a successful event.

  1. Plan your announcement
    • Announce your meetup at least two weeks prior. This gives your audience ample time to prepare and increases the likelihood of their attendance.
  2. Utilize Celestia Labs' resources
    • Celestia Labs can help co-promote your meetup on social media and Discord. They can also add your event to their online calendar, email local contacts, and share the event via their Developer Relations Team on Twitter. Don't hesitate to reach out to them for assistance.
  3. Share on social media
    • Promote your event on Twitter and any other popular social media platforms in your area. Tag speakers, sponsors, and use relevant hashtags to increase visibility.
  4. Leverage local community groups
    • Post your event in local Telegram, Discord, or other community groups relevant to your city. These groups often have many members who may be interested in attending your event.
  5. Engage speakers and the venue
    • Maintain communication with speakers and the venue to ensure any changes can be announced in advance. Trust is critical, so avoid canceling planned meetups whenever possible.
  6. Send reminders via meetup.com (optional)
    • After announcing your event, send a warm invite to your meetup group members through meetup.com. Additionally, send a reminder email one day before the event to encourage attendance.
  7. Share with friends and family
    • Invite your friends, family, and acquaintances to the meetup, as they may help spread the word or know someone interested in the event.
  8. Utilize conference groups
    • If you've attended conferences, share your meetup in the associated Telegram or social media groups, as there may be members nearby who would be interested in attending.

Recording ​

Recording and live-streaming your Modular Meetup can greatly benefit those who cannot attend in person and expand the reach of your event.

  1. Plan for recording
    • Consider recording your meetup to create additional learning resources and share the knowledge with a broader audience.
  2. Consider live-streaming
    • Live-streaming your event on platforms like Twitch, YouTube, or Twitter allows remote participants to watch and engage in the meetup. This can also boost your event's reach and create a sense of inclusion for those who couldn't attend in person.
  3. Coordinate with Celestia Labs
    • Celestia Labs can potentially help cover recording costs and promote recorded meetups. Reach out to them at meetups@celestia.org to discuss available options and support. They can also assist with finding local contacts for recording if you don't have one already.
  4. Utilize available resources
    • If you have a small budget, consider allocating some funds for recording and live-streaming your event. Look for local professionals or affordable equipment rentals to ensure high-quality recordings.
  5. Share recordings on Celestia Labs' channels
    • Celestia Labs can help promote recorded meetups by sharing videos in their meetups playlist on YouTube and hosting them on their website. Ensure you coordinate with Celestia Labs to provide them with the recorded video.
  6. Promote recorded content
    • Share the recordings on your social media channels and meetup group after the event. This helps attendees revisit the content and allows those who couldn't attend to learn from the talks.

Utilizing Meetup.com platform ​

Celestia Labs is committed to supporting your meetup efforts by helping you with meetup.com, from setting up the group to covering organizer dues. Below is a detailed overview of how Celestia Labs can assist you.

  1. Meetup.com organizer dues
    • Celestia Labs is happy to cover organizer dues for meetup.com. To get started, send an email to meetups@celestia.org and let them help you with the process.
  2. Co-organizing existing groups
    • If you already have a meetup.com group but need Celestia Labs' assistance with organizing or covering dues, email meetups@celestia.org to add one of their employees as the Organizer.
  3. Setting up groups on Meetup.com
    • Celestia Labs will help you set up your meetup group, including logos, naming, custom URLs, group description, and other essential details. They provide a unique logo for Celestia Modular Meetups, which you can use for your group.
  4. User group naming
    • Celestia Labs recommends naming your group "Celestia Modular Meetup" to encompass various aspects of the Celestia community and create a consistent brand.
  5. Custom URL for the group
    • Meetup.com allows you to create a custom URL for your user group. Celestia Labs encourages consistent URLs across regions, making it easy for people to find your meetup group.
  6. Group description
    • Celestia Labs has a standard group description to ensure consistency across all meetups. However, if you'd like to customize it, let them know.
  7. New member intake questions
    • To improve the quality of your meetups, Celestia Labs suggests a set of intake questions for new members. The answers can help you better understand their needs and interests, allowing you to plan engaging meetups.
  8. Welcome message
    • Celestia Labs provides a welcome message for new members joining your group. If you'd like to customize this message, let them know.

Onboarding questions for community members joining a Modular Meetup ​

  1. Q1: How did you hear about this Modular Meetup?
    • Why: This information helps us understand the most effective channels for recruiting new participants to the meetup.
  2. Q2: What do you hope to gain by participating in this meetup? (e.g., networking, learning about Celestia, learning about Modularity, finding a job, etc.)
    • Why: This information helps us cater to the needs of the user group members. If most attendees are looking for networking opportunities, we can schedule casual meetups alongside informative talks.
  3. Q3: Are you currently using or planning to use Celestia, Rollkit, Celestia’s Node API or any of the rollups deployed on Celestia? Tell us all about it. We will use your response to help us better understand what talks would be most beneficial to the group.
    • Why: Responses to this question help us determine the most relevant talks for the group members. If we discover that most participants are interested in a specific area, we can tailor the talks accordingly.
  4. Q4: We love Celestia and the modular ecosystem, but we also appreciate other Web3 technologies. What other topics would you like to hear about? (e.g., Infrastructure, Data Storage, DID, MEV)
    • Why: Knowing our group participants' interests in other technical areas helps us understand what related topics would be useful and valuable to the group, which in turn helps when recruiting speakers.
  5. Q5: Would you be interested in speaking at a future meetup? We welcome 2-minute lightning talks to 1-hour deep dives. Would you be interested in hosting a meetup? If you answer yes to this question, the group organizers will contact you to follow up.
    • Why: One of the challenges in hosting regular meetups is finding speakers. We hope this question will identify people eager to share their stories and expertise with the group, making the lives of organizers easier.
',42),r=[n];function s(l,u,c,d,h,p){return t(),i("div",null,r)}const f=e(a,[["render",s]]);export{g as __pageData,f as default}; diff --git a/pr-1699/assets/community_modular-meetup-guide.md.3d71d8e8.lean.js b/pr-1699/assets/community_modular-meetup-guide.md.6b50cb94.lean.js similarity index 91% rename from pr-1699/assets/community_modular-meetup-guide.md.3d71d8e8.lean.js rename to pr-1699/assets/community_modular-meetup-guide.md.6b50cb94.lean.js index dfab948967..b4794c340b 100644 --- a/pr-1699/assets/community_modular-meetup-guide.md.3d71d8e8.lean.js +++ b/pr-1699/assets/community_modular-meetup-guide.md.6b50cb94.lean.js @@ -1 +1 @@ -import{_ as e,o as t,c as i,Q as o}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Modular Meetup guide","description":"A guide that helps in organizing a successful Modular Meetup.","frontmatter":{"description":"A guide that helps in organizing a successful Modular Meetup.","head":[["meta",{"name":"og:title","content":"Modular Meetup guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-guide.md","filePath":"community/modular-meetup-guide.md","lastUpdated":1725971357000}'),a={name:"community/modular-meetup-guide.md"},n=o("",42),r=[n];function s(l,u,c,d,h,p){return t(),i("div",null,r)}const f=e(a,[["render",s]]);export{g as __pageData,f as default}; +import{_ as e,o as t,c as i,Q as o}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Modular Meetup guide","description":"A guide that helps in organizing a successful Modular Meetup.","frontmatter":{"description":"A guide that helps in organizing a successful Modular Meetup.","head":[["meta",{"name":"og:title","content":"Modular Meetup guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-guide.md","filePath":"community/modular-meetup-guide.md","lastUpdated":1725992025000}'),a={name:"community/modular-meetup-guide.md"},n=o("",42),r=[n];function s(l,u,c,d,h,p){return t(),i("div",null,r)}const f=e(a,[["render",s]]);export{g as __pageData,f as default}; diff --git a/pr-1699/assets/community_modular-meetup-intro.md.1b04ad48.js b/pr-1699/assets/community_modular-meetup-intro.md.b7a491a8.js similarity index 98% rename from pr-1699/assets/community_modular-meetup-intro.md.1b04ad48.js rename to pr-1699/assets/community_modular-meetup-intro.md.b7a491a8.js index 67c2f53e23..e2eeb1a611 100644 --- a/pr-1699/assets/community_modular-meetup-intro.md.1b04ad48.js +++ b/pr-1699/assets/community_modular-meetup-intro.md.b7a491a8.js @@ -1 +1 @@ -import{_ as e,o,c as a,Q as t}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia_Modular_meetup2.jpg",f=JSON.parse('{"title":"Celestia Modular Meetup program","description":"The ultimate guide for Modular Meetup organizers!","frontmatter":{"description":"The ultimate guide for Modular Meetup organizers!","head":[["meta",{"name":"og:title","content":"Celestia Modular Meetup program | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-intro.md","filePath":"community/modular-meetup-intro.md","lastUpdated":1725971357000}'),i={name:"community/modular-meetup-intro.md"},n=t('

Celestia Modular Meetup program ​

Modular Meetup Banner

Welcome to the ultimate guide for Modular Meetup organizers! This collection of resources is designed for those enthusiastic about fostering grassroots Modular Meetups with support from Celestia around the world.

Program description ​

The Celestia Modular Meetup Program aims to empower meetup organizers, providing education and support, and encouraging collaboration within the Web3 ecosystem. This rapidly growing community has already achieved incredible success with the first Modular Meetup in Lisbon, and will grow from there.

Join fellow enthusiasts, engage in enlightening discussions, and make the most of the insightful resources provided. These resources are designed to serve as a go-to playbook for meetup organizers, especially when starting your journey.

Important info ​

Celestia.org Community Code of Conduct ​

The purpose of our Community Code of Conduct is to foster an inclusive, welcoming, and supportive environment for everyone participating in Celestia community events. We're all here to learn from each other, expand our skillsets, and enjoy a positive experience together.

All meetup attendees, speakers, sponsors, and volunteers, including the event organizing team, are kindly asked to adhere to the following Code of Conduct. Organizers will respectfully enforce this code throughout the event. We genuinely appreciate the cooperation of all participants in maintaining a safe and empowering space for everyone.

Signup form ​

To become part of the program, please complete the registration form.

Following the review and approval of your submission, you will receive an email confirmation and an invitation to participate in the upcoming Modular Meetup call. Furthermore, you will be granted access to the exclusive Discord channel labeled "#modular-meetup" on our Discord server. Please take note that joining our Discord is a prerequisite for channel access. It's essential to recognize that this program is tailored for dedicated organizers with a genuine interest in nurturing their local modular ecosystem community.

Emails ​

As a participant in the Celestia Modular Meetup Program, you can expect to receive the following emails:

  1. Welcome email with links to calendar events and Discord channel
  2. Monthly Catch-up call invites
  3. Recap emails with notes from calls

Discord ​

Your active participation is key to unlocking the full potential of this vibrant community. Our primary communication tool is Discord, providing an engaging platform to connect with fellow organizers:

Materials ​

As a meetup organizer, you'll gain access to the Celestia Modular Meetup Program's list of resources. This collection should become your trusted companion in organizing events. Drawing upon the wisdom of seasoned event organizers, this resource is available for you and your co-organizers to explore and learn.

',23),s=[n];function l(u,c,d,p,m,h){return o(),a("div",null,s)}const y=e(i,[["render",l]]);export{f as __pageData,y as default}; +import{_ as e,o,c as a,Q as t}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia_Modular_meetup2.jpg",f=JSON.parse('{"title":"Celestia Modular Meetup program","description":"The ultimate guide for Modular Meetup organizers!","frontmatter":{"description":"The ultimate guide for Modular Meetup organizers!","head":[["meta",{"name":"og:title","content":"Celestia Modular Meetup program | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-intro.md","filePath":"community/modular-meetup-intro.md","lastUpdated":1725992025000}'),i={name:"community/modular-meetup-intro.md"},n=t('

Celestia Modular Meetup program ​

Modular Meetup Banner

Welcome to the ultimate guide for Modular Meetup organizers! This collection of resources is designed for those enthusiastic about fostering grassroots Modular Meetups with support from Celestia around the world.

Program description ​

The Celestia Modular Meetup Program aims to empower meetup organizers, providing education and support, and encouraging collaboration within the Web3 ecosystem. This rapidly growing community has already achieved incredible success with the first Modular Meetup in Lisbon, and will grow from there.

Join fellow enthusiasts, engage in enlightening discussions, and make the most of the insightful resources provided. These resources are designed to serve as a go-to playbook for meetup organizers, especially when starting your journey.

Important info ​

Celestia.org Community Code of Conduct ​

The purpose of our Community Code of Conduct is to foster an inclusive, welcoming, and supportive environment for everyone participating in Celestia community events. We're all here to learn from each other, expand our skillsets, and enjoy a positive experience together.

All meetup attendees, speakers, sponsors, and volunteers, including the event organizing team, are kindly asked to adhere to the following Code of Conduct. Organizers will respectfully enforce this code throughout the event. We genuinely appreciate the cooperation of all participants in maintaining a safe and empowering space for everyone.

Signup form ​

To become part of the program, please complete the registration form.

Following the review and approval of your submission, you will receive an email confirmation and an invitation to participate in the upcoming Modular Meetup call. Furthermore, you will be granted access to the exclusive Discord channel labeled "#modular-meetup" on our Discord server. Please take note that joining our Discord is a prerequisite for channel access. It's essential to recognize that this program is tailored for dedicated organizers with a genuine interest in nurturing their local modular ecosystem community.

Emails ​

As a participant in the Celestia Modular Meetup Program, you can expect to receive the following emails:

  1. Welcome email with links to calendar events and Discord channel
  2. Monthly Catch-up call invites
  3. Recap emails with notes from calls

Discord ​

Your active participation is key to unlocking the full potential of this vibrant community. Our primary communication tool is Discord, providing an engaging platform to connect with fellow organizers:

Materials ​

As a meetup organizer, you'll gain access to the Celestia Modular Meetup Program's list of resources. This collection should become your trusted companion in organizing events. Drawing upon the wisdom of seasoned event organizers, this resource is available for you and your co-organizers to explore and learn.

',23),s=[n];function l(u,c,d,p,m,h){return o(),a("div",null,s)}const y=e(i,[["render",l]]);export{f as __pageData,y as default}; diff --git a/pr-1699/assets/community_modular-meetup-intro.md.1b04ad48.lean.js b/pr-1699/assets/community_modular-meetup-intro.md.b7a491a8.lean.js similarity index 91% rename from pr-1699/assets/community_modular-meetup-intro.md.1b04ad48.lean.js rename to pr-1699/assets/community_modular-meetup-intro.md.b7a491a8.lean.js index b11e972388..4703144cda 100644 --- a/pr-1699/assets/community_modular-meetup-intro.md.1b04ad48.lean.js +++ b/pr-1699/assets/community_modular-meetup-intro.md.b7a491a8.lean.js @@ -1 +1 @@ -import{_ as e,o,c as a,Q as t}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia_Modular_meetup2.jpg",f=JSON.parse('{"title":"Celestia Modular Meetup program","description":"The ultimate guide for Modular Meetup organizers!","frontmatter":{"description":"The ultimate guide for Modular Meetup organizers!","head":[["meta",{"name":"og:title","content":"Celestia Modular Meetup program | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-intro.md","filePath":"community/modular-meetup-intro.md","lastUpdated":1725971357000}'),i={name:"community/modular-meetup-intro.md"},n=t("",23),s=[n];function l(u,c,d,p,m,h){return o(),a("div",null,s)}const y=e(i,[["render",l]]);export{f as __pageData,y as default}; +import{_ as e,o,c as a,Q as t}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia_Modular_meetup2.jpg",f=JSON.parse('{"title":"Celestia Modular Meetup program","description":"The ultimate guide for Modular Meetup organizers!","frontmatter":{"description":"The ultimate guide for Modular Meetup organizers!","head":[["meta",{"name":"og:title","content":"Celestia Modular Meetup program | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-intro.md","filePath":"community/modular-meetup-intro.md","lastUpdated":1725992025000}'),i={name:"community/modular-meetup-intro.md"},n=t("",23),s=[n];function l(u,c,d,p,m,h){return o(),a("div",null,s)}const y=e(i,[["render",l]]);export{f as __pageData,y as default}; diff --git a/pr-1699/assets/community_modular-meetup-toolkit.md.f6184c46.js b/pr-1699/assets/community_modular-meetup-toolkit.md.0a2e761b.js similarity index 98% rename from pr-1699/assets/community_modular-meetup-toolkit.md.f6184c46.js rename to pr-1699/assets/community_modular-meetup-toolkit.md.0a2e761b.js index 441b2af4d2..a9ea711a1d 100644 --- a/pr-1699/assets/community_modular-meetup-toolkit.md.f6184c46.js +++ b/pr-1699/assets/community_modular-meetup-toolkit.md.0a2e761b.js @@ -1 +1 @@ -import{_ as e,o,c as i,Q as t}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Modular Meetup Toolkit","description":"A toolkit for Modular Meetups.","frontmatter":{"description":"A toolkit for Modular Meetups.","head":[["meta",{"name":"og:title","content":"Modular Meetup Toolkit | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-toolkit.md","filePath":"community/modular-meetup-toolkit.md","lastUpdated":1725971357000}'),l={name:"community/modular-meetup-toolkit.md"},a=t('

Modular Meetup Toolkit ​

Welcome to the Modular Meetups Toolkit! This kit is designed to help you run successful meetups for the Celestia community. As the first modular blockchain, Celestia offers a lot to discuss and explore. This kit includes useful resources and materials to help you plan and execute your meetups effectively.

Celestia branding guidelines ​

Sample “Introduction to Modularity” workshop presentation ​

Sample “Run a Celestia light node” workshop presentation ​

Sample “Deploy a Sovereign Rollup” workshop presentation ​

Sample “Modular Meetup Introduction” workshop presentation ​

Swag logistics ​

With this Modular Meetups Organizer Kit, you’ll have everything you need to plan and execute engaging, informative, and successful meetups for the Celestia community. Happy organizing!

',15),r=[a];function n(s,p,u,d,h,c){return o(),i("div",null,r)}const f=e(l,[["render",n]]);export{g as __pageData,f as default}; +import{_ as e,o,c as i,Q as t}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Modular Meetup Toolkit","description":"A toolkit for Modular Meetups.","frontmatter":{"description":"A toolkit for Modular Meetups.","head":[["meta",{"name":"og:title","content":"Modular Meetup Toolkit | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-toolkit.md","filePath":"community/modular-meetup-toolkit.md","lastUpdated":1725992025000}'),l={name:"community/modular-meetup-toolkit.md"},a=t('

Modular Meetup Toolkit ​

Welcome to the Modular Meetups Toolkit! This kit is designed to help you run successful meetups for the Celestia community. As the first modular blockchain, Celestia offers a lot to discuss and explore. This kit includes useful resources and materials to help you plan and execute your meetups effectively.

Celestia branding guidelines ​

Sample “Introduction to Modularity” workshop presentation ​

Sample “Run a Celestia light node” workshop presentation ​

Sample “Deploy a Sovereign Rollup” workshop presentation ​

Sample “Modular Meetup Introduction” workshop presentation ​

Swag logistics ​

With this Modular Meetups Organizer Kit, you’ll have everything you need to plan and execute engaging, informative, and successful meetups for the Celestia community. Happy organizing!

',15),r=[a];function n(s,p,u,d,h,c){return o(),i("div",null,r)}const f=e(l,[["render",n]]);export{g as __pageData,f as default}; diff --git a/pr-1699/assets/community_modular-meetup-toolkit.md.f6184c46.lean.js b/pr-1699/assets/community_modular-meetup-toolkit.md.0a2e761b.lean.js similarity index 90% rename from pr-1699/assets/community_modular-meetup-toolkit.md.f6184c46.lean.js rename to pr-1699/assets/community_modular-meetup-toolkit.md.0a2e761b.lean.js index 9597a91257..d8bb639ced 100644 --- a/pr-1699/assets/community_modular-meetup-toolkit.md.f6184c46.lean.js +++ b/pr-1699/assets/community_modular-meetup-toolkit.md.0a2e761b.lean.js @@ -1 +1 @@ -import{_ as e,o,c as i,Q as t}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Modular Meetup Toolkit","description":"A toolkit for Modular Meetups.","frontmatter":{"description":"A toolkit for Modular Meetups.","head":[["meta",{"name":"og:title","content":"Modular Meetup Toolkit | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-toolkit.md","filePath":"community/modular-meetup-toolkit.md","lastUpdated":1725971357000}'),l={name:"community/modular-meetup-toolkit.md"},a=t("",15),r=[a];function n(s,p,u,d,h,c){return o(),i("div",null,r)}const f=e(l,[["render",n]]);export{g as __pageData,f as default}; +import{_ as e,o,c as i,Q as t}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Modular Meetup Toolkit","description":"A toolkit for Modular Meetups.","frontmatter":{"description":"A toolkit for Modular Meetups.","head":[["meta",{"name":"og:title","content":"Modular Meetup Toolkit | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/modular-meetup-toolkit.md","filePath":"community/modular-meetup-toolkit.md","lastUpdated":1725992025000}'),l={name:"community/modular-meetup-toolkit.md"},a=t("",15),r=[a];function n(s,p,u,d,h,c){return o(),i("div",null,r)}const f=e(l,[["render",n]]);export{g as __pageData,f as default}; diff --git a/pr-1699/assets/community_overview.md.aec66ec4.js b/pr-1699/assets/community_overview.md.fb9fd608.js similarity index 94% rename from pr-1699/assets/community_overview.md.aec66ec4.js rename to pr-1699/assets/community_overview.md.fb9fd608.js index 76edb82189..236d03da46 100644 --- a/pr-1699/assets/community_overview.md.aec66ec4.js +++ b/pr-1699/assets/community_overview.md.fb9fd608.js @@ -1 +1 @@ -import{_ as o,o as i,c as a,k as e,a as t}from"./chunks/framework.b47e54aa.js";const y=JSON.parse('{"title":"Community overview","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Community overview | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/overview.md","filePath":"community/overview.md","lastUpdated":1725971357000}'),n={name:"community/overview.md"},r=e("h1",{id:"community-overview",tabindex:"-1"},[t("Community overview "),e("a",{class:"header-anchor",href:"#community-overview","aria-label":'Permalink to "Community overview"'},"​")],-1),c=e("p",null,"This section will highlight all the different resources and activities for the Celestia community.",-1),s=e("p",null,[t("Here you will find links to our "),e("a",{href:"./calendar"},"community calendar"),t(", "),e("a",{href:"./coc"},"Code of Conduct"),t(" and other community-related resources.")],-1),m=[r,c,s];function l(d,u,v,h,_,f){return i(),a("div",null,m)}const w=o(n,[["render",l]]);export{y as __pageData,w as default}; +import{_ as o,o as i,c as a,k as e,a as t}from"./chunks/framework.b47e54aa.js";const y=JSON.parse('{"title":"Community overview","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Community overview | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/overview.md","filePath":"community/overview.md","lastUpdated":1725992025000}'),n={name:"community/overview.md"},r=e("h1",{id:"community-overview",tabindex:"-1"},[t("Community overview "),e("a",{class:"header-anchor",href:"#community-overview","aria-label":'Permalink to "Community overview"'},"​")],-1),c=e("p",null,"This section will highlight all the different resources and activities for the Celestia community.",-1),s=e("p",null,[t("Here you will find links to our "),e("a",{href:"./calendar"},"community calendar"),t(", "),e("a",{href:"./coc"},"Code of Conduct"),t(" and other community-related resources.")],-1),m=[r,c,s];function l(d,u,v,h,_,f){return i(),a("div",null,m)}const w=o(n,[["render",l]]);export{y as __pageData,w as default}; diff --git a/pr-1699/assets/community_overview.md.aec66ec4.lean.js b/pr-1699/assets/community_overview.md.fb9fd608.lean.js similarity index 94% rename from pr-1699/assets/community_overview.md.aec66ec4.lean.js rename to pr-1699/assets/community_overview.md.fb9fd608.lean.js index 76edb82189..236d03da46 100644 --- a/pr-1699/assets/community_overview.md.aec66ec4.lean.js +++ b/pr-1699/assets/community_overview.md.fb9fd608.lean.js @@ -1 +1 @@ -import{_ as o,o as i,c as a,k as e,a as t}from"./chunks/framework.b47e54aa.js";const y=JSON.parse('{"title":"Community overview","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Community overview | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/overview.md","filePath":"community/overview.md","lastUpdated":1725971357000}'),n={name:"community/overview.md"},r=e("h1",{id:"community-overview",tabindex:"-1"},[t("Community overview "),e("a",{class:"header-anchor",href:"#community-overview","aria-label":'Permalink to "Community overview"'},"​")],-1),c=e("p",null,"This section will highlight all the different resources and activities for the Celestia community.",-1),s=e("p",null,[t("Here you will find links to our "),e("a",{href:"./calendar"},"community calendar"),t(", "),e("a",{href:"./coc"},"Code of Conduct"),t(" and other community-related resources.")],-1),m=[r,c,s];function l(d,u,v,h,_,f){return i(),a("div",null,m)}const w=o(n,[["render",l]]);export{y as __pageData,w as default}; +import{_ as o,o as i,c as a,k as e,a as t}from"./chunks/framework.b47e54aa.js";const y=JSON.parse('{"title":"Community overview","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Community overview | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/overview.md","filePath":"community/overview.md","lastUpdated":1725992025000}'),n={name:"community/overview.md"},r=e("h1",{id:"community-overview",tabindex:"-1"},[t("Community overview "),e("a",{class:"header-anchor",href:"#community-overview","aria-label":'Permalink to "Community overview"'},"​")],-1),c=e("p",null,"This section will highlight all the different resources and activities for the Celestia community.",-1),s=e("p",null,[t("Here you will find links to our "),e("a",{href:"./calendar"},"community calendar"),t(", "),e("a",{href:"./coc"},"Code of Conduct"),t(" and other community-related resources.")],-1),m=[r,c,s];function l(d,u,v,h,_,f){return i(),a("div",null,m)}const w=o(n,[["render",l]]);export{y as __pageData,w as default}; diff --git a/pr-1699/assets/community_speaker-list.md.716e09e6.js b/pr-1699/assets/community_speaker-list.md.872a3b69.js similarity index 97% rename from pr-1699/assets/community_speaker-list.md.716e09e6.js rename to pr-1699/assets/community_speaker-list.md.872a3b69.js index 7f4f1d8399..afb87ec372 100644 --- a/pr-1699/assets/community_speaker-list.md.716e09e6.js +++ b/pr-1699/assets/community_speaker-list.md.872a3b69.js @@ -1 +1 @@ -import{_ as t,o as a,c as s,k as e,a as i}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Speaker list","description":"Invite a speaker from the ecosystem to your Modular Meetup.","frontmatter":{"description":"Invite a speaker from the ecosystem to your Modular Meetup.","head":[["meta",{"name":"og:title","content":"Speaker list | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/speaker-list.md","filePath":"community/speaker-list.md","lastUpdated":1725971357000}'),o={name:"community/speaker-list.md"},r=e("h1",{id:"speaker-list",tabindex:"-1"},[i("Speaker list "),e("a",{class:"header-anchor",href:"#speaker-list","aria-label":'Permalink to "Speaker list"'},"​")],-1),n=e("p",null,"As a Modular Meetup organizer, we understand the importance of delivering engaging and informative content to your attendees. That's why we've created an exclusive Speaker List specifically tailored for organizers participating in the Modular Meetup Program. This resource gives you access to a curated selection of top-tier speakers who are passionate about Celestia and the modular ecosystem. Due to privacy, the list is not shared publicly but is accessible to participants of the Modular Meetup program when they create a meetup.",-1),l=e("p",null,"The Speaker List features experts from Celestia Labs, as well as prominent figures from the broader Celestia and modular communities. Each individual is well-versed in various aspects of the modular ecosystem, ensuring that your meetup attendees gain valuable insights and deepen their understanding of modular blockchains.",-1),c=e("p",null,"By joining the Modular Meetup Program, you can enjoy the benefits of our Speaker List and bring a touch of expertise to your events. The speakers can participate either in person or virtually, depending on location and timing.",-1),p=e("p",null,"You can expect benefits from the Speaker List including high-quality presentations, interactive Q&A sessions, and knowledge-sharing opportunities facilitated by the best and brightest in the Celestia ecosystem. With our Speaker List, you'll be able to create memorable and impactful Modular Meetups that foster genuine connections and promote growth within the community.",-1),d=[r,n,l,c,p];function u(h,m,f,g,y,k){return a(),s("div",null,d)}const v=t(o,[["render",u]]);export{b as __pageData,v as default}; +import{_ as t,o as a,c as s,k as e,a as i}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Speaker list","description":"Invite a speaker from the ecosystem to your Modular Meetup.","frontmatter":{"description":"Invite a speaker from the ecosystem to your Modular Meetup.","head":[["meta",{"name":"og:title","content":"Speaker list | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/speaker-list.md","filePath":"community/speaker-list.md","lastUpdated":1725992025000}'),o={name:"community/speaker-list.md"},r=e("h1",{id:"speaker-list",tabindex:"-1"},[i("Speaker list "),e("a",{class:"header-anchor",href:"#speaker-list","aria-label":'Permalink to "Speaker list"'},"​")],-1),n=e("p",null,"As a Modular Meetup organizer, we understand the importance of delivering engaging and informative content to your attendees. That's why we've created an exclusive Speaker List specifically tailored for organizers participating in the Modular Meetup Program. This resource gives you access to a curated selection of top-tier speakers who are passionate about Celestia and the modular ecosystem. Due to privacy, the list is not shared publicly but is accessible to participants of the Modular Meetup program when they create a meetup.",-1),l=e("p",null,"The Speaker List features experts from Celestia Labs, as well as prominent figures from the broader Celestia and modular communities. Each individual is well-versed in various aspects of the modular ecosystem, ensuring that your meetup attendees gain valuable insights and deepen their understanding of modular blockchains.",-1),c=e("p",null,"By joining the Modular Meetup Program, you can enjoy the benefits of our Speaker List and bring a touch of expertise to your events. The speakers can participate either in person or virtually, depending on location and timing.",-1),p=e("p",null,"You can expect benefits from the Speaker List including high-quality presentations, interactive Q&A sessions, and knowledge-sharing opportunities facilitated by the best and brightest in the Celestia ecosystem. With our Speaker List, you'll be able to create memorable and impactful Modular Meetups that foster genuine connections and promote growth within the community.",-1),d=[r,n,l,c,p];function u(h,m,f,g,y,k){return a(),s("div",null,d)}const v=t(o,[["render",u]]);export{b as __pageData,v as default}; diff --git a/pr-1699/assets/community_speaker-list.md.716e09e6.lean.js b/pr-1699/assets/community_speaker-list.md.872a3b69.lean.js similarity index 97% rename from pr-1699/assets/community_speaker-list.md.716e09e6.lean.js rename to pr-1699/assets/community_speaker-list.md.872a3b69.lean.js index 7f4f1d8399..afb87ec372 100644 --- a/pr-1699/assets/community_speaker-list.md.716e09e6.lean.js +++ b/pr-1699/assets/community_speaker-list.md.872a3b69.lean.js @@ -1 +1 @@ -import{_ as t,o as a,c as s,k as e,a as i}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Speaker list","description":"Invite a speaker from the ecosystem to your Modular Meetup.","frontmatter":{"description":"Invite a speaker from the ecosystem to your Modular Meetup.","head":[["meta",{"name":"og:title","content":"Speaker list | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/speaker-list.md","filePath":"community/speaker-list.md","lastUpdated":1725971357000}'),o={name:"community/speaker-list.md"},r=e("h1",{id:"speaker-list",tabindex:"-1"},[i("Speaker list "),e("a",{class:"header-anchor",href:"#speaker-list","aria-label":'Permalink to "Speaker list"'},"​")],-1),n=e("p",null,"As a Modular Meetup organizer, we understand the importance of delivering engaging and informative content to your attendees. That's why we've created an exclusive Speaker List specifically tailored for organizers participating in the Modular Meetup Program. This resource gives you access to a curated selection of top-tier speakers who are passionate about Celestia and the modular ecosystem. Due to privacy, the list is not shared publicly but is accessible to participants of the Modular Meetup program when they create a meetup.",-1),l=e("p",null,"The Speaker List features experts from Celestia Labs, as well as prominent figures from the broader Celestia and modular communities. Each individual is well-versed in various aspects of the modular ecosystem, ensuring that your meetup attendees gain valuable insights and deepen their understanding of modular blockchains.",-1),c=e("p",null,"By joining the Modular Meetup Program, you can enjoy the benefits of our Speaker List and bring a touch of expertise to your events. The speakers can participate either in person or virtually, depending on location and timing.",-1),p=e("p",null,"You can expect benefits from the Speaker List including high-quality presentations, interactive Q&A sessions, and knowledge-sharing opportunities facilitated by the best and brightest in the Celestia ecosystem. With our Speaker List, you'll be able to create memorable and impactful Modular Meetups that foster genuine connections and promote growth within the community.",-1),d=[r,n,l,c,p];function u(h,m,f,g,y,k){return a(),s("div",null,d)}const v=t(o,[["render",u]]);export{b as __pageData,v as default}; +import{_ as t,o as a,c as s,k as e,a as i}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Speaker list","description":"Invite a speaker from the ecosystem to your Modular Meetup.","frontmatter":{"description":"Invite a speaker from the ecosystem to your Modular Meetup.","head":[["meta",{"name":"og:title","content":"Speaker list | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"community/speaker-list.md","filePath":"community/speaker-list.md","lastUpdated":1725992025000}'),o={name:"community/speaker-list.md"},r=e("h1",{id:"speaker-list",tabindex:"-1"},[i("Speaker list "),e("a",{class:"header-anchor",href:"#speaker-list","aria-label":'Permalink to "Speaker list"'},"​")],-1),n=e("p",null,"As a Modular Meetup organizer, we understand the importance of delivering engaging and informative content to your attendees. That's why we've created an exclusive Speaker List specifically tailored for organizers participating in the Modular Meetup Program. This resource gives you access to a curated selection of top-tier speakers who are passionate about Celestia and the modular ecosystem. Due to privacy, the list is not shared publicly but is accessible to participants of the Modular Meetup program when they create a meetup.",-1),l=e("p",null,"The Speaker List features experts from Celestia Labs, as well as prominent figures from the broader Celestia and modular communities. Each individual is well-versed in various aspects of the modular ecosystem, ensuring that your meetup attendees gain valuable insights and deepen their understanding of modular blockchains.",-1),c=e("p",null,"By joining the Modular Meetup Program, you can enjoy the benefits of our Speaker List and bring a touch of expertise to your events. The speakers can participate either in person or virtually, depending on location and timing.",-1),p=e("p",null,"You can expect benefits from the Speaker List including high-quality presentations, interactive Q&A sessions, and knowledge-sharing opportunities facilitated by the best and brightest in the Celestia ecosystem. With our Speaker List, you'll be able to create memorable and impactful Modular Meetups that foster genuine connections and promote growth within the community.",-1),d=[r,n,l,c,p];function u(h,m,f,g,y,k){return a(),s("div",null,d)}const v=t(o,[["render",u]]);export{b as __pageData,v as default}; diff --git a/pr-1699/assets/developers_arbitrum-bridge.md.d7cda10d.js b/pr-1699/assets/developers_arbitrum-bridge.md.8c851802.js similarity index 99% rename from pr-1699/assets/developers_arbitrum-bridge.md.d7cda10d.js rename to pr-1699/assets/developers_arbitrum-bridge.md.8c851802.js index 06c06a180f..2f62953223 100644 --- a/pr-1699/assets/developers_arbitrum-bridge.md.d7cda10d.js +++ b/pr-1699/assets/developers_arbitrum-bridge.md.8c851802.js @@ -1 +1 @@ -import{_ as r,o,c as t,Q as e}from"./chunks/framework.b47e54aa.js";const i="/docs-preview/pr-1699/arbitrum/bridge-overview-deposit-and-withdrawal-l3.png",a="/docs-preview/pr-1699/arbitrum/bridge-settings.png",n="/docs-preview/pr-1699/arbitrum/add-custom-chain-to-bridge.png",s="/docs-preview/pr-1699/arbitrum/live-orbit-chains.png",p="/docs-preview/pr-1699/arbitrum/bridge-in-start.png",l="/docs-preview/pr-1699/arbitrum/bridge-in-pending-txs.png",d="/docs-preview/pr-1699/arbitrum/bridge-in-settled-txs.png",g="/docs-preview/pr-1699/arbitrum/bridge-in-explorer-rollup-tx.png",u="/docs-preview/pr-1699/arbitrum/bridge-in-success.png",c="/docs-preview/pr-1699/arbitrum/bridge-in-sepolia-tx-explorer.png",b="/docs-preview/pr-1699/arbitrum/bridge-out-small-screenshot.png",h="/docs-preview/pr-1699/arbitrum/bridge-out-begin.png",m="/docs-preview/pr-1699/arbitrum/bridge-out-pending.png",w="/docs-preview/pr-1699/arbitrum/bridge-out-begin-overview.png",f="/docs-preview/pr-1699/arbitrum/bridge-out-rollup-tx-details.png",y="/docs-preview/pr-1699/arbitrum/bridge-out-logs-details-1.png",_="/docs-preview/pr-1699/arbitrum/bridge-out-logs-explorer-2.png",v="/docs-preview/pr-1699/arbitrum/bridge-out-claim-withdrawal.png",x="/docs-preview/pr-1699/arbitrum/bridge-out-claim-success-withdrawal.png",D=JSON.parse('{"title":"Bridging in and out of your Orbit rollup","description":"A guide on how to bridge in and out of your Arbitrum Orbit rollup.","frontmatter":{"description":"A guide on how to bridge in and out of your Arbitrum Orbit rollup.","head":[["meta",{"name":"og:title","content":"Bridging in and out of your Orbit rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-bridge.md","filePath":"developers/arbitrum-bridge.md","lastUpdated":1725971357000}'),A={name:"developers/arbitrum-bridge.md"},S=e('

Bridging in and out of your Orbit rollup ​

This guide covers how to bridge in (deposit) and bridge out (withdrawal) from your Arbitrum Orbit L3 rollup.

This guide will cover bridging in and out of your Orbit rollup.

Below are two example transactions, one of a deposit and one of a withdrawal:

bridge-overview-deposit-and-withdrawal-l3

Bridge in (deposit) to your rollup ​

Step 1: Add your custom chain config ​

(1a) In the Arbitrum Bridge UI, click the menu dropdown in the top right. Select Settings.

bridge-settings

(1b) Under Developer Mode, select Turn on testnet mode. Add your custom chain config from outputInfo.json in the root of your orbit-setup-script directory.

add-testnet-orbit-chain

(1c) You'll then see the chain under Live Orbit Chains:

live-orbit-chains

Step 2: Deposit to your Orbit rollup ​

(2a) Choose an amount of Arbitrum Sepolia ETH to bridge into your rollup. Click Move funds to <YOUR_ROLLUP_NAME>, in this case Move funds to Arbitrum L3 Rollup. Approve the transaction in your wallet.

bridge-in-start

(2b) You'll then see it load in the Pending transactions tab:

bridge-in-pending

(2c) Shortly after, in the Settled transactions tab you can see the transaction status. Click Success.

bridge-in-settled-txs

(2d) View the transaction on your local instance of Blockscout for your rollup:

bridge-in-explorer-rollup-tx

(2e) Optionally, click See Details for an overview of your deposit:

bridge-in-success

(2f) From the details page, you can also see the transaction for your deposit on Arbitrum Sepolia:

bridge-in-sepolia-tx-explorer

Bridge out (withdrawal) from your rollup ​

Step 1: Choose an amount to withdraw from your rollup ​

(1a) In the Arbitrum Bridge UI, choose your origin chain to your Arbitrum L3 Rollup and the destination chain as Arbitrum Sepolia.

bridge-out-small-screenshot

(1b) Click Move funds to Arbitrum Sepolia and read the disclaimer, check the boxes, and click Continue.

bridge-out-begin

(1c) Optionally, set a reminder on your calendar so you don't forget.

(1d) After approving the transaction in your wallet, you'll be able to see the transaction in the Pending transactions tab:

bridge-out-pending

After approximately two hours, you will be able to proceed to Step 2: Claim your withdrawal.

(1e) Click See details to see an overview of your withdrawal:

bridge-out-begin-overview

(1f) Optionally, view the transaction on your local explorer.

bridge-out-tx-details

(1g) To learn more about what is going on, click the Logs tab:

bridge-out-logs-details-1

bridge-out-logs-explorer-2

Step 2: Claim your withdrawal ​

After approximately 2 hours, you will be able to claim your withdrawal.

(2a) Head back to the bridge UI and you will have a notification to claim your withdrawal. Click Claim in the details of the transaction:

bridge-out-claim-withdrawal

(2b) Approve the transaction in your wallet.

(2c) After your transaction goes through, you can see the details in the bridge UI under Settled transactions:

bridge-out-claim-success-withdrawal

',50),k=[S];function C(O,B,q,P,T,I){return o(),t("div",null,k)}const L=r(A,[["render",C]]);export{D as __pageData,L as default}; +import{_ as r,o,c as t,Q as e}from"./chunks/framework.b47e54aa.js";const i="/docs-preview/pr-1699/arbitrum/bridge-overview-deposit-and-withdrawal-l3.png",a="/docs-preview/pr-1699/arbitrum/bridge-settings.png",n="/docs-preview/pr-1699/arbitrum/add-custom-chain-to-bridge.png",s="/docs-preview/pr-1699/arbitrum/live-orbit-chains.png",p="/docs-preview/pr-1699/arbitrum/bridge-in-start.png",l="/docs-preview/pr-1699/arbitrum/bridge-in-pending-txs.png",d="/docs-preview/pr-1699/arbitrum/bridge-in-settled-txs.png",g="/docs-preview/pr-1699/arbitrum/bridge-in-explorer-rollup-tx.png",u="/docs-preview/pr-1699/arbitrum/bridge-in-success.png",c="/docs-preview/pr-1699/arbitrum/bridge-in-sepolia-tx-explorer.png",b="/docs-preview/pr-1699/arbitrum/bridge-out-small-screenshot.png",h="/docs-preview/pr-1699/arbitrum/bridge-out-begin.png",m="/docs-preview/pr-1699/arbitrum/bridge-out-pending.png",w="/docs-preview/pr-1699/arbitrum/bridge-out-begin-overview.png",f="/docs-preview/pr-1699/arbitrum/bridge-out-rollup-tx-details.png",y="/docs-preview/pr-1699/arbitrum/bridge-out-logs-details-1.png",_="/docs-preview/pr-1699/arbitrum/bridge-out-logs-explorer-2.png",v="/docs-preview/pr-1699/arbitrum/bridge-out-claim-withdrawal.png",x="/docs-preview/pr-1699/arbitrum/bridge-out-claim-success-withdrawal.png",D=JSON.parse('{"title":"Bridging in and out of your Orbit rollup","description":"A guide on how to bridge in and out of your Arbitrum Orbit rollup.","frontmatter":{"description":"A guide on how to bridge in and out of your Arbitrum Orbit rollup.","head":[["meta",{"name":"og:title","content":"Bridging in and out of your Orbit rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-bridge.md","filePath":"developers/arbitrum-bridge.md","lastUpdated":1725992025000}'),A={name:"developers/arbitrum-bridge.md"},S=e('

Bridging in and out of your Orbit rollup ​

This guide covers how to bridge in (deposit) and bridge out (withdrawal) from your Arbitrum Orbit L3 rollup.

This guide will cover bridging in and out of your Orbit rollup.

Below are two example transactions, one of a deposit and one of a withdrawal:

bridge-overview-deposit-and-withdrawal-l3

Bridge in (deposit) to your rollup ​

Step 1: Add your custom chain config ​

(1a) In the Arbitrum Bridge UI, click the menu dropdown in the top right. Select Settings.

bridge-settings

(1b) Under Developer Mode, select Turn on testnet mode. Add your custom chain config from outputInfo.json in the root of your orbit-setup-script directory.

add-testnet-orbit-chain

(1c) You'll then see the chain under Live Orbit Chains:

live-orbit-chains

Step 2: Deposit to your Orbit rollup ​

(2a) Choose an amount of Arbitrum Sepolia ETH to bridge into your rollup. Click Move funds to <YOUR_ROLLUP_NAME>, in this case Move funds to Arbitrum L3 Rollup. Approve the transaction in your wallet.

bridge-in-start

(2b) You'll then see it load in the Pending transactions tab:

bridge-in-pending

(2c) Shortly after, in the Settled transactions tab you can see the transaction status. Click Success.

bridge-in-settled-txs

(2d) View the transaction on your local instance of Blockscout for your rollup:

bridge-in-explorer-rollup-tx

(2e) Optionally, click See Details for an overview of your deposit:

bridge-in-success

(2f) From the details page, you can also see the transaction for your deposit on Arbitrum Sepolia:

bridge-in-sepolia-tx-explorer

Bridge out (withdrawal) from your rollup ​

Step 1: Choose an amount to withdraw from your rollup ​

(1a) In the Arbitrum Bridge UI, choose your origin chain to your Arbitrum L3 Rollup and the destination chain as Arbitrum Sepolia.

bridge-out-small-screenshot

(1b) Click Move funds to Arbitrum Sepolia and read the disclaimer, check the boxes, and click Continue.

bridge-out-begin

(1c) Optionally, set a reminder on your calendar so you don't forget.

(1d) After approving the transaction in your wallet, you'll be able to see the transaction in the Pending transactions tab:

bridge-out-pending

After approximately two hours, you will be able to proceed to Step 2: Claim your withdrawal.

(1e) Click See details to see an overview of your withdrawal:

bridge-out-begin-overview

(1f) Optionally, view the transaction on your local explorer.

bridge-out-tx-details

(1g) To learn more about what is going on, click the Logs tab:

bridge-out-logs-details-1

bridge-out-logs-explorer-2

Step 2: Claim your withdrawal ​

After approximately 2 hours, you will be able to claim your withdrawal.

(2a) Head back to the bridge UI and you will have a notification to claim your withdrawal. Click Claim in the details of the transaction:

bridge-out-claim-withdrawal

(2b) Approve the transaction in your wallet.

(2c) After your transaction goes through, you can see the details in the bridge UI under Settled transactions:

bridge-out-claim-success-withdrawal

',50),k=[S];function C(O,B,q,P,T,I){return o(),t("div",null,k)}const L=r(A,[["render",C]]);export{D as __pageData,L as default}; diff --git a/pr-1699/assets/developers_arbitrum-bridge.md.d7cda10d.lean.js b/pr-1699/assets/developers_arbitrum-bridge.md.8c851802.lean.js similarity index 96% rename from pr-1699/assets/developers_arbitrum-bridge.md.d7cda10d.lean.js rename to pr-1699/assets/developers_arbitrum-bridge.md.8c851802.lean.js index 1acd97e708..19bcbcda38 100644 --- a/pr-1699/assets/developers_arbitrum-bridge.md.d7cda10d.lean.js +++ b/pr-1699/assets/developers_arbitrum-bridge.md.8c851802.lean.js @@ -1 +1 @@ -import{_ as r,o,c as t,Q as e}from"./chunks/framework.b47e54aa.js";const i="/docs-preview/pr-1699/arbitrum/bridge-overview-deposit-and-withdrawal-l3.png",a="/docs-preview/pr-1699/arbitrum/bridge-settings.png",n="/docs-preview/pr-1699/arbitrum/add-custom-chain-to-bridge.png",s="/docs-preview/pr-1699/arbitrum/live-orbit-chains.png",p="/docs-preview/pr-1699/arbitrum/bridge-in-start.png",l="/docs-preview/pr-1699/arbitrum/bridge-in-pending-txs.png",d="/docs-preview/pr-1699/arbitrum/bridge-in-settled-txs.png",g="/docs-preview/pr-1699/arbitrum/bridge-in-explorer-rollup-tx.png",u="/docs-preview/pr-1699/arbitrum/bridge-in-success.png",c="/docs-preview/pr-1699/arbitrum/bridge-in-sepolia-tx-explorer.png",b="/docs-preview/pr-1699/arbitrum/bridge-out-small-screenshot.png",h="/docs-preview/pr-1699/arbitrum/bridge-out-begin.png",m="/docs-preview/pr-1699/arbitrum/bridge-out-pending.png",w="/docs-preview/pr-1699/arbitrum/bridge-out-begin-overview.png",f="/docs-preview/pr-1699/arbitrum/bridge-out-rollup-tx-details.png",y="/docs-preview/pr-1699/arbitrum/bridge-out-logs-details-1.png",_="/docs-preview/pr-1699/arbitrum/bridge-out-logs-explorer-2.png",v="/docs-preview/pr-1699/arbitrum/bridge-out-claim-withdrawal.png",x="/docs-preview/pr-1699/arbitrum/bridge-out-claim-success-withdrawal.png",D=JSON.parse('{"title":"Bridging in and out of your Orbit rollup","description":"A guide on how to bridge in and out of your Arbitrum Orbit rollup.","frontmatter":{"description":"A guide on how to bridge in and out of your Arbitrum Orbit rollup.","head":[["meta",{"name":"og:title","content":"Bridging in and out of your Orbit rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-bridge.md","filePath":"developers/arbitrum-bridge.md","lastUpdated":1725971357000}'),A={name:"developers/arbitrum-bridge.md"},S=e("",50),k=[S];function C(O,B,q,P,T,I){return o(),t("div",null,k)}const L=r(A,[["render",C]]);export{D as __pageData,L as default}; +import{_ as r,o,c as t,Q as e}from"./chunks/framework.b47e54aa.js";const i="/docs-preview/pr-1699/arbitrum/bridge-overview-deposit-and-withdrawal-l3.png",a="/docs-preview/pr-1699/arbitrum/bridge-settings.png",n="/docs-preview/pr-1699/arbitrum/add-custom-chain-to-bridge.png",s="/docs-preview/pr-1699/arbitrum/live-orbit-chains.png",p="/docs-preview/pr-1699/arbitrum/bridge-in-start.png",l="/docs-preview/pr-1699/arbitrum/bridge-in-pending-txs.png",d="/docs-preview/pr-1699/arbitrum/bridge-in-settled-txs.png",g="/docs-preview/pr-1699/arbitrum/bridge-in-explorer-rollup-tx.png",u="/docs-preview/pr-1699/arbitrum/bridge-in-success.png",c="/docs-preview/pr-1699/arbitrum/bridge-in-sepolia-tx-explorer.png",b="/docs-preview/pr-1699/arbitrum/bridge-out-small-screenshot.png",h="/docs-preview/pr-1699/arbitrum/bridge-out-begin.png",m="/docs-preview/pr-1699/arbitrum/bridge-out-pending.png",w="/docs-preview/pr-1699/arbitrum/bridge-out-begin-overview.png",f="/docs-preview/pr-1699/arbitrum/bridge-out-rollup-tx-details.png",y="/docs-preview/pr-1699/arbitrum/bridge-out-logs-details-1.png",_="/docs-preview/pr-1699/arbitrum/bridge-out-logs-explorer-2.png",v="/docs-preview/pr-1699/arbitrum/bridge-out-claim-withdrawal.png",x="/docs-preview/pr-1699/arbitrum/bridge-out-claim-success-withdrawal.png",D=JSON.parse('{"title":"Bridging in and out of your Orbit rollup","description":"A guide on how to bridge in and out of your Arbitrum Orbit rollup.","frontmatter":{"description":"A guide on how to bridge in and out of your Arbitrum Orbit rollup.","head":[["meta",{"name":"og:title","content":"Bridging in and out of your Orbit rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-bridge.md","filePath":"developers/arbitrum-bridge.md","lastUpdated":1725992025000}'),A={name:"developers/arbitrum-bridge.md"},S=e("",50),k=[S];function C(O,B,q,P,T,I){return o(),t("div",null,k)}const L=r(A,[["render",C]]);export{D as __pageData,L as default}; diff --git a/pr-1699/assets/developers_arbitrum-dapp-deploy.md.26b815d3.js b/pr-1699/assets/developers_arbitrum-dapp-deploy.md.4b34cdb2.js similarity index 99% rename from pr-1699/assets/developers_arbitrum-dapp-deploy.md.26b815d3.js rename to pr-1699/assets/developers_arbitrum-dapp-deploy.md.4b34cdb2.js index 33a271421c..407f4c0493 100644 --- a/pr-1699/assets/developers_arbitrum-dapp-deploy.md.26b815d3.js +++ b/pr-1699/assets/developers_arbitrum-dapp-deploy.md.4b34cdb2.js @@ -1,4 +1,4 @@ -import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/gm-arb.png",F=JSON.parse('{"title":"Deploy a dapp on your Arbitrum rollup devnet","description":"Make your own GM Portal dapp on your Arbitrum rollup.","frontmatter":{"description":"Make your own GM Portal dapp on your Arbitrum rollup.","next":{"text":"Intro to OP Stack integration","link":"/developers/intro-to-op-stack"},"head":[["meta",{"name":"og:title","content":"Deploy a dapp on your Arbitrum rollup devnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-dapp-deploy.md","filePath":"developers/arbitrum-dapp-deploy.md","lastUpdated":1725971357000}'),p={name:"developers/arbitrum-dapp-deploy.md"},t=n(`

Deploy a dapp on your Arbitrum rollup devnet ​

First, review the Arbitrum integration, Quickstart: Deploy an Arbitrum Orbit rollup, and Deploy a smart contract to your Arbitrum rollup pages.

Dependencies ​

Setup and contract deployment ​

  1. Clone the gm-portal from GitHub and start the frontend:

    bash
    cd $HOME
+import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/gm-arb.png",F=JSON.parse('{"title":"Deploy a dapp on your Arbitrum rollup devnet","description":"Make your own GM Portal dapp on your Arbitrum rollup.","frontmatter":{"description":"Make your own GM Portal dapp on your Arbitrum rollup.","next":{"text":"Intro to OP Stack integration","link":"/developers/intro-to-op-stack"},"head":[["meta",{"name":"og:title","content":"Deploy a dapp on your Arbitrum rollup devnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-dapp-deploy.md","filePath":"developers/arbitrum-dapp-deploy.md","lastUpdated":1725992025000}'),p={name:"developers/arbitrum-dapp-deploy.md"},t=n(`
    Deploy a dapp on your Arbitrum rollup devnet ​
    First, review the Arbitrum integration, Quickstart: Deploy an Arbitrum Orbit rollup, and Deploy a smart contract to your Arbitrum rollup pages.
    Dependencies ​
    Setup and contract deployment ​
    1. Clone the gm-portal from GitHub and start the frontend:
      bash
      cd $HOME
 git clone https://github.com/jcstein/gm-portal.git
 cd gm-portal && git checkout arbitrum
 cd frontend && yarn && yarn dev
      cd $HOME
diff --git a/pr-1699/assets/developers_arbitrum-dapp-deploy.md.26b815d3.lean.js b/pr-1699/assets/developers_arbitrum-dapp-deploy.md.4b34cdb2.lean.js
similarity index 92%
rename from pr-1699/assets/developers_arbitrum-dapp-deploy.md.26b815d3.lean.js
rename to pr-1699/assets/developers_arbitrum-dapp-deploy.md.4b34cdb2.lean.js
index bfb905f493..a7a3fca98a 100644
--- a/pr-1699/assets/developers_arbitrum-dapp-deploy.md.26b815d3.lean.js
+++ b/pr-1699/assets/developers_arbitrum-dapp-deploy.md.4b34cdb2.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/gm-arb.png",F=JSON.parse('{"title":"Deploy a dapp on your Arbitrum rollup devnet","description":"Make your own GM Portal dapp on your Arbitrum rollup.","frontmatter":{"description":"Make your own GM Portal dapp on your Arbitrum rollup.","next":{"text":"Intro to OP Stack integration","link":"/developers/intro-to-op-stack"},"head":[["meta",{"name":"og:title","content":"Deploy a dapp on your Arbitrum rollup devnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-dapp-deploy.md","filePath":"developers/arbitrum-dapp-deploy.md","lastUpdated":1725971357000}'),p={name:"developers/arbitrum-dapp-deploy.md"},t=n("",16),e=[t];function r(c,i,y,d,E,h){return a(),o("div",null,e)}const m=s(p,[["render",r]]);export{F as __pageData,m as default};
+import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/gm-arb.png",F=JSON.parse('{"title":"Deploy a dapp on your Arbitrum rollup devnet","description":"Make your own GM Portal dapp on your Arbitrum rollup.","frontmatter":{"description":"Make your own GM Portal dapp on your Arbitrum rollup.","next":{"text":"Intro to OP Stack integration","link":"/developers/intro-to-op-stack"},"head":[["meta",{"name":"og:title","content":"Deploy a dapp on your Arbitrum rollup devnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-dapp-deploy.md","filePath":"developers/arbitrum-dapp-deploy.md","lastUpdated":1725992025000}'),p={name:"developers/arbitrum-dapp-deploy.md"},t=n("",16),e=[t];function r(c,i,y,d,E,h){return a(),o("div",null,e)}const m=s(p,[["render",r]]);export{F as __pageData,m as default};
diff --git a/pr-1699/assets/developers_arbitrum-deploy.md.c142d06c.js b/pr-1699/assets/developers_arbitrum-deploy.md.26acb828.js
similarity index 99%
rename from pr-1699/assets/developers_arbitrum-deploy.md.c142d06c.js
rename to pr-1699/assets/developers_arbitrum-deploy.md.26acb828.js
index 98b7a65143..34ecd5e936 100644
--- a/pr-1699/assets/developers_arbitrum-deploy.md.c142d06c.js
+++ b/pr-1699/assets/developers_arbitrum-deploy.md.26acb828.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const e="/docs-preview/pr-1699/arbitrum/choose_da.png",t="/docs-preview/pr-1699/arbitrum/configuration.png",l="/docs-preview/pr-1699/arbitrum/download-config.png",p="/docs-preview/pr-1699/arbitrum/blockscout.png",r="/docs-preview/pr-1699/arbitrum/explorer-view.png",B=JSON.parse('{"title":"Quickstart: Deploy an Arbitrum Orbit rollup","description":"A guide on how to deploy an Arbitrum Orbit rollup using the Arbitrum Orbit deployment UI and deploying the rollup to Mocha testnet.","frontmatter":{"description":"A guide on how to deploy an Arbitrum Orbit rollup using the Arbitrum Orbit deployment UI and deploying the rollup to Mocha testnet.","head":[["meta",{"name":"og:title","content":"Quickstart: Deploy an Arbitrum Orbit rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-deploy.md","filePath":"developers/arbitrum-deploy.md","lastUpdated":1725971357000}'),c={name:"developers/arbitrum-deploy.md"},i=n('
      Quickstart: Deploy an Arbitrum Orbit rollup ​
      This guide covers deploying a rollup using the Celestia Orbit chain deployment portal.
      After completing this tutorial, you will have a local development network rollup capable of hosting EVM-compatible smart contracts. This rollup will process transactions locally, settle on the public Arbitrum Sepolia testnet, and post data to Celestia's Mocha testnet.
      If you're looking to learn more about the integration of Celestia and Orbit, read the Arbitrum Orbit integration overview. If you're looking to learn more about Orbit, read A gentle introduction: Orbit chains.
      Thank you, Offchain Labs!
      This guide was made possible with the support and information provided by the Offchain Labs team, the creators of Arbitrum. For more detailed information and support, visit Arbitrum documentation and the original deployment guide.
      Prerequisites ​
      Setup ​
      This section was adapted from Arbitrum's Orbit quickstart.
      Step 1: Acquire Arbitrum Sepolia ETH ​
      You'll need at least 1 testnet ETH for a regular Orbit rollup or 0.6 ETH plus 0.4 of your desired native token for Orbit rollups with a custom gas token. The funds will cover the cost of deploying the base contracts to the base chain, in this case, Arbitrum Sepolia.
      The simplest way to do this is to:
      1. Use an L1 testnet ETH faucet like sepoliafaucet.com to acquire some testnet ETH on Ethereum Sepolia testnet.
      2. Bridge your L1 testnet ETH to L2 Arbitrum Sepolia using the Arbitrum bridge.
      Step 2: Pick your deployment type ​
      Visit the Celestia Orbit chain deployment portal. This portal offers the following options:
      1. Celestia Rollup: Transaction data is posted to Celestia
      2. Rollup: Transaction data is posted to Ethereum
      3. AnyTrust: Transaction data is posted by a Data Availability Committee
      Connect your wallet to the deployment portal. You may be prompted to add the Arbitrum Sepolia network to your wallet and/or switch your wallet to this network; approve this.
      In this guide, we will select Celestia ✨ and deploy a rollup which posts data to Celestia (1 above).
      Choose Celestia for DA
      Click Next. In the next step, we will configure the deployment.
      Step 3: Configure your Orbit chain's deployment ​
      The deployment portal will then display a form that looks like this:
      configuration
      Parameter descriptions can be found in the table below (more in-depth descriptions can be found in the deployment UI). We recommend sticking to the defaults; to learn more about customizing your Orbit chain's deployment configuration, visit How to customize your Orbit chain's deployment configuration:
      ParameterDescription
      Chain IDThis is a unique integer identifier for your chain's network, primarily used on chain indexes like Chainlist.org. It's not crucial for development networks, but in production, you'll need to choose a unique ID.
      Chain NameThe name you assign to your Orbit chain, which helps users and developers distinguish it from other chains. It should be memorable and recognizable.
      Challenge Period BlocksDetermines the time frame within which validators can dispute the state of the chain posted to the base chain. It's measured in blocks on the underlying L1 chain. A longer period allows more time for disputes but also delays withdrawals.
      Stake TokenSpecifies the token that validators must stake to participate in the validation process, using the token's contract address on the base chain. This can be ETH or another token, defined by its address.
      Base StakeThe minimum amount of stake token required for validators to post state assertions. A lower base stake lowers the barrier to entry but increases vulnerability to attacks, whereas a higher stake encourages honest participation but raises the entry barrier.
      OwnerThe account address that has the authority to deploy, own, and update the base contracts of your Orbit chain on its base chain. In production, this is usually a high-stakes address controlled by a DAO or a multisig setup. For development chains, it's a lower-stakes administrative account.
      Gas TokenThe token used for gas payments on the network, which must be natively deployed on the parent chain. There are specific requirements for custom gas tokens, such as having 18 decimals and not being a rebasing or fee-on-transfer token. This feature is primarily for Orbit AnyTrust chains.
      ValidatorsThis is the number of validators for your chain, including their addresses. The first validator is auto-generated and immutable. Validators are crucial for maintaining the integrity of the chain and posting state assertions to the base chain.
      Batch PosterResponsible for posting transaction batches from your Orbit chain to the base chain. An address for this role is automatically generated, with the private key stored in a configuration file.
      In the Configure Validators section, specify the number of validators and their addresses for your chain. The initial validator's address is pre-generated and immutable, with its key stored in a JSON file. Validators ensure transaction integrity and state assertions on the base chain. They're added to an allow-list for validation and staking. Base contracts refer to your Orbit chain's L2 contracts, and base chain to the L2 chain they're deployed on.
      In the Configure Batch Poster section, a batch poster address is auto-generated for posting transaction batches to the base contracts on the base chain. The address and its private key are also stored in a JSON configuration file. After configuring, proceed to review and deploy your Orbit chain.
      After configuring your batch poster, proceed to the next step.
      Step 3: Review & Deploy your Orbit chain ​
      Now, deploy your chain's base contracts to Arbitrum Sepolia!
      Click the Deploy button on the Review & Deploy page. Your wallet should prompt you to submit a transaction to the Arbitrum testnet. You'll have to pay a little gas; your wallet may denominate this in ETH; as long as you see your chosen Arbitrum testnet in the transaction details, this gas fee will be paid in testnet ETH.
      Before proceeding, let's briefly review what just happened:
      1. You submitted a deployment transaction to an Orbit "factory" smart contract on the Arbitrum testnet, the public L2 chain that your local Orbit chain will settle transactions to.
      2. This Orbit smart contract then initialized your Orbit chain's base contracts with the values that you specified in the previous step, and deployed these base contracts to the Arbitrum testnet.
      Your Orbit chain's base contracts are responsible for facilitating the exchange of information between your chain's node(s) and its base chain's nodes. This includes the batch posting of transactions from your Orbit chain to its base chain, the staking of tokens by your Orbit chain's validators the challenge mechanism, bridging mechanisms, and more.
      Once your transaction is complete, continue to Step 4 to download your chain's configuration files and launch your chain.
      Step 4: Download your chain's configuration files and launch your chain ​
      After configuring your chain, you will need to download the necessary configuration files to launch your chain. Click the Download zip files button to download both the Rollup Config and L3 Config in a single ZIP file.
      • Rollup Config: This is the nodeConfig.json file, encapsulating your chain's node configuration. It is crucial as it contains the private keys for your validator and batch poster, essential for signing transactions for RBlocks and batch postings to your chain's base contracts on the L2 chain.
      • L3 Config: This is the orbitSetupScriptConfig.json file, which holds your chain's configuration, including configurations needed for your Token Bridge contracts.
      Ensure to securely store these downloaded files as they contain sensitive information crucial for your chain's operation.
      download config
      Step 5: Clone the setup script repository and add your configuration files ​
      1. Clone the orbit-setup-script repository:
        bash
        git clone https://github.com/celestiaorg/orbit-setup-script.git
        git clone https://github.com/celestiaorg/orbit-setup-script.git
      2. Move the nodeConfig.json and orbitSetupScriptConfig.json files that you downloaded into the config directory in the root of your cloned orbit-setup-script repository.
      3. Install dependencies by running yarn install from the root of the orbit-setup-script repository.
      Step 6: Pick an L2 RPC URL for the Batch Poster ​
      In order for the Batch Poster, which is responsible for posting batches of data, to subscribe to Blobstream's smart contract events, the node most use a WebSocket connection, since an HTTP one will not support subscriptions. This RPC URL is different from the parent-chain.connection.url object used in the node config, and is not necessary when running a full node. WebSocket (WSS) URLs which are essential for real-time data fetching and interaction with the Arbitrum Sepolia network.
      To establish a WebSocket connection for your rollup to Arbitrum Sepolia, it's recommended to find an RPC provider with WSS connections from Arbitrum's docs.
      For this example, we will make an account on Alchemy. Follow these steps to set up your account and obtain a WSS URL using Alchemy:
      1. Visit Alchemy's website and sign up for an account.
      2. Once logged in, create a new app by selecting the Arbitrum network, specifically targeting the Arbitrum Sepolia testnet.
      3. After creating your app, navigate to the "API key" section to find your WebSocket (WSS) URL.
      4. In the next step, use this WSS URL in your nodeConfig.json under the celestia-cfg.eth-rpc object to ensure your node can establish a WebSocket connection to the Arbitrum Sepolia network and successfully subscribe to Blobstream events.
      Without a WSS connection, the Batch Poster won't be able to subscribe to Blobstream events, and thus will fall back to posting data to parent chain.
      Step 7: Run your light node for Mocha testnet ​
      First, be sure that your light node is running, using a command similar to:
      TIP
      If you are on Linux (or are not using Docker desktop), you may need to add the extra flags: --rpc.addr 0.0.0.0 and --rpc.port 26658 to your start command for your light node.
      Additionally, you will need to add host.docker.internal as a host in your docker-compose.yml:
      yaml
      extra_hosts:
+import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const e="/docs-preview/pr-1699/arbitrum/choose_da.png",t="/docs-preview/pr-1699/arbitrum/configuration.png",l="/docs-preview/pr-1699/arbitrum/download-config.png",p="/docs-preview/pr-1699/arbitrum/blockscout.png",r="/docs-preview/pr-1699/arbitrum/explorer-view.png",B=JSON.parse('{"title":"Quickstart: Deploy an Arbitrum Orbit rollup","description":"A guide on how to deploy an Arbitrum Orbit rollup using the Arbitrum Orbit deployment UI and deploying the rollup to Mocha testnet.","frontmatter":{"description":"A guide on how to deploy an Arbitrum Orbit rollup using the Arbitrum Orbit deployment UI and deploying the rollup to Mocha testnet.","head":[["meta",{"name":"og:title","content":"Quickstart: Deploy an Arbitrum Orbit rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-deploy.md","filePath":"developers/arbitrum-deploy.md","lastUpdated":1725992025000}'),c={name:"developers/arbitrum-deploy.md"},i=n('
      Quickstart: Deploy an Arbitrum Orbit rollup ​
      This guide covers deploying a rollup using the Celestia Orbit chain deployment portal.
      After completing this tutorial, you will have a local development network rollup capable of hosting EVM-compatible smart contracts. This rollup will process transactions locally, settle on the public Arbitrum Sepolia testnet, and post data to Celestia's Mocha testnet.
      If you're looking to learn more about the integration of Celestia and Orbit, read the Arbitrum Orbit integration overview. If you're looking to learn more about Orbit, read A gentle introduction: Orbit chains.
      Thank you, Offchain Labs!
      This guide was made possible with the support and information provided by the Offchain Labs team, the creators of Arbitrum. For more detailed information and support, visit Arbitrum documentation and the original deployment guide.
      Prerequisites ​
      Setup ​
      This section was adapted from Arbitrum's Orbit quickstart.
      Step 1: Acquire Arbitrum Sepolia ETH ​
      You'll need at least 1 testnet ETH for a regular Orbit rollup or 0.6 ETH plus 0.4 of your desired native token for Orbit rollups with a custom gas token. The funds will cover the cost of deploying the base contracts to the base chain, in this case, Arbitrum Sepolia.
      The simplest way to do this is to:
      1. Use an L1 testnet ETH faucet like sepoliafaucet.com to acquire some testnet ETH on Ethereum Sepolia testnet.
      2. Bridge your L1 testnet ETH to L2 Arbitrum Sepolia using the Arbitrum bridge.
      Step 2: Pick your deployment type ​
      Visit the Celestia Orbit chain deployment portal. This portal offers the following options:
      1. Celestia Rollup: Transaction data is posted to Celestia
      2. Rollup: Transaction data is posted to Ethereum
      3. AnyTrust: Transaction data is posted by a Data Availability Committee
      Connect your wallet to the deployment portal. You may be prompted to add the Arbitrum Sepolia network to your wallet and/or switch your wallet to this network; approve this.
      In this guide, we will select Celestia ✨ and deploy a rollup which posts data to Celestia (1 above).
      Choose Celestia for DA
      Click Next. In the next step, we will configure the deployment.
      Step 3: Configure your Orbit chain's deployment ​
      The deployment portal will then display a form that looks like this:
      configuration
      Parameter descriptions can be found in the table below (more in-depth descriptions can be found in the deployment UI). We recommend sticking to the defaults; to learn more about customizing your Orbit chain's deployment configuration, visit How to customize your Orbit chain's deployment configuration:
      ParameterDescription
      Chain IDThis is a unique integer identifier for your chain's network, primarily used on chain indexes like Chainlist.org. It's not crucial for development networks, but in production, you'll need to choose a unique ID.
      Chain NameThe name you assign to your Orbit chain, which helps users and developers distinguish it from other chains. It should be memorable and recognizable.
      Challenge Period BlocksDetermines the time frame within which validators can dispute the state of the chain posted to the base chain. It's measured in blocks on the underlying L1 chain. A longer period allows more time for disputes but also delays withdrawals.
      Stake TokenSpecifies the token that validators must stake to participate in the validation process, using the token's contract address on the base chain. This can be ETH or another token, defined by its address.
      Base StakeThe minimum amount of stake token required for validators to post state assertions. A lower base stake lowers the barrier to entry but increases vulnerability to attacks, whereas a higher stake encourages honest participation but raises the entry barrier.
      OwnerThe account address that has the authority to deploy, own, and update the base contracts of your Orbit chain on its base chain. In production, this is usually a high-stakes address controlled by a DAO or a multisig setup. For development chains, it's a lower-stakes administrative account.
      Gas TokenThe token used for gas payments on the network, which must be natively deployed on the parent chain. There are specific requirements for custom gas tokens, such as having 18 decimals and not being a rebasing or fee-on-transfer token. This feature is primarily for Orbit AnyTrust chains.
      ValidatorsThis is the number of validators for your chain, including their addresses. The first validator is auto-generated and immutable. Validators are crucial for maintaining the integrity of the chain and posting state assertions to the base chain.
      Batch PosterResponsible for posting transaction batches from your Orbit chain to the base chain. An address for this role is automatically generated, with the private key stored in a configuration file.
      In the Configure Validators section, specify the number of validators and their addresses for your chain. The initial validator's address is pre-generated and immutable, with its key stored in a JSON file. Validators ensure transaction integrity and state assertions on the base chain. They're added to an allow-list for validation and staking. Base contracts refer to your Orbit chain's L2 contracts, and base chain to the L2 chain they're deployed on.
      In the Configure Batch Poster section, a batch poster address is auto-generated for posting transaction batches to the base contracts on the base chain. The address and its private key are also stored in a JSON configuration file. After configuring, proceed to review and deploy your Orbit chain.
      After configuring your batch poster, proceed to the next step.
      Step 3: Review & Deploy your Orbit chain ​
      Now, deploy your chain's base contracts to Arbitrum Sepolia!
      Click the Deploy button on the Review & Deploy page. Your wallet should prompt you to submit a transaction to the Arbitrum testnet. You'll have to pay a little gas; your wallet may denominate this in ETH; as long as you see your chosen Arbitrum testnet in the transaction details, this gas fee will be paid in testnet ETH.
      Before proceeding, let's briefly review what just happened:
      1. You submitted a deployment transaction to an Orbit "factory" smart contract on the Arbitrum testnet, the public L2 chain that your local Orbit chain will settle transactions to.
      2. This Orbit smart contract then initialized your Orbit chain's base contracts with the values that you specified in the previous step, and deployed these base contracts to the Arbitrum testnet.
      Your Orbit chain's base contracts are responsible for facilitating the exchange of information between your chain's node(s) and its base chain's nodes. This includes the batch posting of transactions from your Orbit chain to its base chain, the staking of tokens by your Orbit chain's validators the challenge mechanism, bridging mechanisms, and more.
      Once your transaction is complete, continue to Step 4 to download your chain's configuration files and launch your chain.
      Step 4: Download your chain's configuration files and launch your chain ​
      After configuring your chain, you will need to download the necessary configuration files to launch your chain. Click the Download zip files button to download both the Rollup Config and L3 Config in a single ZIP file.
      • Rollup Config: This is the nodeConfig.json file, encapsulating your chain's node configuration. It is crucial as it contains the private keys for your validator and batch poster, essential for signing transactions for RBlocks and batch postings to your chain's base contracts on the L2 chain.
      • L3 Config: This is the orbitSetupScriptConfig.json file, which holds your chain's configuration, including configurations needed for your Token Bridge contracts.
      Ensure to securely store these downloaded files as they contain sensitive information crucial for your chain's operation.
      download config
      Step 5: Clone the setup script repository and add your configuration files ​
      1. Clone the orbit-setup-script repository:
        bash
        git clone https://github.com/celestiaorg/orbit-setup-script.git
        git clone https://github.com/celestiaorg/orbit-setup-script.git
      2. Move the nodeConfig.json and orbitSetupScriptConfig.json files that you downloaded into the config directory in the root of your cloned orbit-setup-script repository.
      3. Install dependencies by running yarn install from the root of the orbit-setup-script repository.
      Step 6: Pick an L2 RPC URL for the Batch Poster ​
      In order for the Batch Poster, which is responsible for posting batches of data, to subscribe to Blobstream's smart contract events, the node most use a WebSocket connection, since an HTTP one will not support subscriptions. This RPC URL is different from the parent-chain.connection.url object used in the node config, and is not necessary when running a full node. WebSocket (WSS) URLs which are essential for real-time data fetching and interaction with the Arbitrum Sepolia network.
      To establish a WebSocket connection for your rollup to Arbitrum Sepolia, it's recommended to find an RPC provider with WSS connections from Arbitrum's docs.
      For this example, we will make an account on Alchemy. Follow these steps to set up your account and obtain a WSS URL using Alchemy:
      1. Visit Alchemy's website and sign up for an account.
      2. Once logged in, create a new app by selecting the Arbitrum network, specifically targeting the Arbitrum Sepolia testnet.
      3. After creating your app, navigate to the "API key" section to find your WebSocket (WSS) URL.
      4. In the next step, use this WSS URL in your nodeConfig.json under the celestia-cfg.eth-rpc object to ensure your node can establish a WebSocket connection to the Arbitrum Sepolia network and successfully subscribe to Blobstream events.
      Without a WSS connection, the Batch Poster won't be able to subscribe to Blobstream events, and thus will fall back to posting data to parent chain.
      Step 7: Run your light node for Mocha testnet ​
      First, be sure that your light node is running, using a command similar to:
      TIP
      If you are on Linux (or are not using Docker desktop), you may need to add the extra flags: --rpc.addr 0.0.0.0 and --rpc.port 26658 to your start command for your light node.
      Additionally, you will need to add host.docker.internal as a host in your docker-compose.yml:
      yaml
      extra_hosts:
       - "host.docker.internal:host-gateway"
      extra_hosts:
       - "host.docker.internal:host-gateway"
      bash
      celestia light start --p2p.network mocha --core.ip <RPC_URL>
      celestia light start --p2p.network mocha --core.ip <RPC_URL>
      To set your light node's auth token, you will use the auth token that returns when you run:
      bash
      celestia light auth admin --p2p.network mocha
      celestia light auth admin --p2p.network mocha
      Since the contracts deployed through the factories above are already configured to communicate with Blobstream, you now only have to configure your node accordingly. First understand the different variables that will be set in the config:
      • enable: set it to true if you are using Celestia DA 😁
      • rpc: RPC endpoint for celestia-node
      • tendermint-rpc: a celestia-core endpoint from a full node (NOTE: only needed for a batch poster node)
      • eth-rpc: Ethereum Client WSS RPC endpoint, only used when the node is a batch poster. The eth-rpc must be WSS. Otherwise, it won't be able to subscribe to events for Blobstream.
      • namespace-id: namespace being used to post data to Celestia
      • auth-token: auth token for your Celestia Node
      • is-poster: is the node with Celestia DA the batch poster, set to true if so.
      • gas-price: how much to pay for gas (in uTIA)
      • event-channel-size: size of the events channel used by the batch poster to wait for a range of headers that contains the header for the block in which it posted a blob, before posting the batch to the base layer for verification on Blobstream X.
      • blobstreamx-address: address of the Blobstream X contract on the base chain. 
        • Note that the SequencerInbox contract for each chain has a constant address for the BlobstreamX contract, thus make sure that the Blobstream X address in the SequencerInbox being used for the templates in RollupCreator matches the one in your config.
      Now enable Celestia DA in your Arbitrum chain params in config/nodeConfig.json. If you'd like to use your own namespace, use a custom 10 byte value or random value using openssl rand -hex 10 for namespace-id:
      WARNING
      The Orbit contracts depend on the existing Blobstream X deployments. Before using these addresses, please verify the contract addresses on the official source below to avoid any issues due to incorrect addresses. This is crucial to protect against potential misuse by copy-paste errors.
      ts
      "celestia-cfg": {
   "enable": true,
diff --git a/pr-1699/assets/developers_arbitrum-deploy.md.c142d06c.lean.js b/pr-1699/assets/developers_arbitrum-deploy.md.26acb828.lean.js
similarity index 94%
rename from pr-1699/assets/developers_arbitrum-deploy.md.c142d06c.lean.js
rename to pr-1699/assets/developers_arbitrum-deploy.md.26acb828.lean.js
index 2914086824..2761838c60 100644
--- a/pr-1699/assets/developers_arbitrum-deploy.md.c142d06c.lean.js
+++ b/pr-1699/assets/developers_arbitrum-deploy.md.26acb828.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const e="/docs-preview/pr-1699/arbitrum/choose_da.png",t="/docs-preview/pr-1699/arbitrum/configuration.png",l="/docs-preview/pr-1699/arbitrum/download-config.png",p="/docs-preview/pr-1699/arbitrum/blockscout.png",r="/docs-preview/pr-1699/arbitrum/explorer-view.png",B=JSON.parse('{"title":"Quickstart: Deploy an Arbitrum Orbit rollup","description":"A guide on how to deploy an Arbitrum Orbit rollup using the Arbitrum Orbit deployment UI and deploying the rollup to Mocha testnet.","frontmatter":{"description":"A guide on how to deploy an Arbitrum Orbit rollup using the Arbitrum Orbit deployment UI and deploying the rollup to Mocha testnet.","head":[["meta",{"name":"og:title","content":"Quickstart: Deploy an Arbitrum Orbit rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-deploy.md","filePath":"developers/arbitrum-deploy.md","lastUpdated":1725971357000}'),c={name:"developers/arbitrum-deploy.md"},i=n("",95),y=[i];function E(d,F,h,u,b,C){return a(),o("div",null,y)}const g=s(c,[["render",E]]);export{B as __pageData,g as default};
+import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const e="/docs-preview/pr-1699/arbitrum/choose_da.png",t="/docs-preview/pr-1699/arbitrum/configuration.png",l="/docs-preview/pr-1699/arbitrum/download-config.png",p="/docs-preview/pr-1699/arbitrum/blockscout.png",r="/docs-preview/pr-1699/arbitrum/explorer-view.png",B=JSON.parse('{"title":"Quickstart: Deploy an Arbitrum Orbit rollup","description":"A guide on how to deploy an Arbitrum Orbit rollup using the Arbitrum Orbit deployment UI and deploying the rollup to Mocha testnet.","frontmatter":{"description":"A guide on how to deploy an Arbitrum Orbit rollup using the Arbitrum Orbit deployment UI and deploying the rollup to Mocha testnet.","head":[["meta",{"name":"og:title","content":"Quickstart: Deploy an Arbitrum Orbit rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-deploy.md","filePath":"developers/arbitrum-deploy.md","lastUpdated":1725992025000}'),c={name:"developers/arbitrum-deploy.md"},i=n("",95),y=[i];function E(d,F,h,u,b,C){return a(),o("div",null,y)}const g=s(c,[["render",E]]);export{B as __pageData,g as default};
diff --git a/pr-1699/assets/developers_arbitrum-full-node.md.09e489d4.js b/pr-1699/assets/developers_arbitrum-full-node.md.319badbc.js
similarity index 98%
rename from pr-1699/assets/developers_arbitrum-full-node.md.09e489d4.js
rename to pr-1699/assets/developers_arbitrum-full-node.md.319badbc.js
index d5ecd85972..e9ead3d65b 100644
--- a/pr-1699/assets/developers_arbitrum-full-node.md.09e489d4.js
+++ b/pr-1699/assets/developers_arbitrum-full-node.md.319badbc.js
@@ -1,3 +1,3 @@
-import{_ as n,o as e,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Running a full node and/or validator","description":"A guide on how to run a full node or validating full node on your Orbit rollup.","frontmatter":{"description":"A guide on how to run a full node or validating full node on your Orbit rollup.","head":[["meta",{"name":"og:title","content":"Running a full node and/or validator | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-full-node.md","filePath":"developers/arbitrum-full-node.md","lastUpdated":1725971357000}'),t={name:"developers/arbitrum-full-node.md"},r=a(`
      Running a full node and/or validator ​
      Prerequisites ​
      Running a full node ​
      To run a full node, you can follow the steps outlined in the Arbitrum docs, with the difference being that you will use this image: dfcelestia/nitro-node-dev:latest instead of the one mentioned in the Arbitrum docs.
      Note that you can either use the flags in the nitro binary + the flags found in the celestia package, or you can just provide a node config.json file with the celestia-cfg for them to run it, which would look something like this:
      json
      docker run --rm -v "$HOME/Documents/configs/nodeConfig.json:/config.json:ro" \\
+import{_ as n,o as e,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Running a full node and/or validator","description":"A guide on how to run a full node or validating full node on your Orbit rollup.","frontmatter":{"description":"A guide on how to run a full node or validating full node on your Orbit rollup.","head":[["meta",{"name":"og:title","content":"Running a full node and/or validator | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-full-node.md","filePath":"developers/arbitrum-full-node.md","lastUpdated":1725992025000}'),t={name:"developers/arbitrum-full-node.md"},r=a(`
      Running a full node and/or validator ​
      Prerequisites ​
      Running a full node ​
      To run a full node, you can follow the steps outlined in the Arbitrum docs, with the difference being that you will use this image: dfcelestia/nitro-node-dev:latest instead of the one mentioned in the Arbitrum docs.
      Note that you can either use the flags in the nitro binary + the flags found in the celestia package, or you can just provide a node config.json file with the celestia-cfg for them to run it, which would look something like this:
      json
      docker run --rm -v "$HOME/Documents/configs/nodeConfig.json:/config.json:ro" \\
   --network host celestia-nitro:v2.3.1-rc.1 --conf.file /config.json
      docker run --rm -v "$HOME/Documents/configs/nodeConfig.json:/config.json:ro" \\
   --network host celestia-nitro:v2.3.1-rc.1 --conf.file /config.json
      Running a full node with validation ​
      The information above applies to the steps outlined to run a validating full node (validator).
      Finally, note that this will require connection to a DA node, and we recommend running a Bridge node if you will be instantiating multiple rollups.
      `,10),i=[r];function l(s,d,u,c,p,h){return e(),o("div",null,i)}const m=n(t,[["render",l]]);export{g as __pageData,m as default};
diff --git a/pr-1699/assets/developers_arbitrum-full-node.md.09e489d4.lean.js b/pr-1699/assets/developers_arbitrum-full-node.md.319badbc.lean.js
similarity index 92%
rename from pr-1699/assets/developers_arbitrum-full-node.md.09e489d4.lean.js
rename to pr-1699/assets/developers_arbitrum-full-node.md.319badbc.lean.js
index b0e772dd20..39ddbee454 100644
--- a/pr-1699/assets/developers_arbitrum-full-node.md.09e489d4.lean.js
+++ b/pr-1699/assets/developers_arbitrum-full-node.md.319badbc.lean.js
@@ -1 +1 @@
-import{_ as n,o as e,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Running a full node and/or validator","description":"A guide on how to run a full node or validating full node on your Orbit rollup.","frontmatter":{"description":"A guide on how to run a full node or validating full node on your Orbit rollup.","head":[["meta",{"name":"og:title","content":"Running a full node and/or validator | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-full-node.md","filePath":"developers/arbitrum-full-node.md","lastUpdated":1725971357000}'),t={name:"developers/arbitrum-full-node.md"},r=a("",10),i=[r];function l(s,d,u,c,p,h){return e(),o("div",null,i)}const m=n(t,[["render",l]]);export{g as __pageData,m as default};
+import{_ as n,o as e,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Running a full node and/or validator","description":"A guide on how to run a full node or validating full node on your Orbit rollup.","frontmatter":{"description":"A guide on how to run a full node or validating full node on your Orbit rollup.","head":[["meta",{"name":"og:title","content":"Running a full node and/or validator | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-full-node.md","filePath":"developers/arbitrum-full-node.md","lastUpdated":1725992025000}'),t={name:"developers/arbitrum-full-node.md"},r=a("",10),i=[r];function l(s,d,u,c,p,h){return e(),o("div",null,i)}const m=n(t,[["render",l]]);export{g as __pageData,m as default};
diff --git a/pr-1699/assets/developers_arbitrum-integration.md.2b72ec21.js b/pr-1699/assets/developers_arbitrum-integration.md.fd5df284.js
similarity index 99%
rename from pr-1699/assets/developers_arbitrum-integration.md.2b72ec21.js
rename to pr-1699/assets/developers_arbitrum-integration.md.fd5df284.js
index d29c19ab35..96fd8db714 100644
--- a/pr-1699/assets/developers_arbitrum-integration.md.2b72ec21.js
+++ b/pr-1699/assets/developers_arbitrum-integration.md.fd5df284.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia-Arbitrum.png",f=JSON.parse('{"title":"Introduction to Arbitrum rollups with Celestia as DA","description":"An overview of the integration of Arbitrum Nitro with Celestia, detailing the key features and benefits, including the Ethereum fallback mechanism.","frontmatter":{"description":"An overview of the integration of Arbitrum Nitro with Celestia, detailing the key features and benefits, including the Ethereum fallback mechanism.","head":[["meta",{"name":"og:title","content":"Introduction to Arbitrum rollups with Celestia as DA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-integration.md","filePath":"developers/arbitrum-integration.md","lastUpdated":1725971357000}'),o={name:"developers/arbitrum-integration.md"},n=i('
      Introduction to Arbitrum rollups with Celestia as DA ​
      Celestia_Arbitrum
      Overview ​
      The integration of Celestia with Arbitrum Orbit and the Nitro tech stack marks the first external contribution to the Arbitrum Orbit protocol layer, offering developers an additional option for selecting a data availability layer alongside Arbitrum AnyTrust. The integration allows developers to deploy an Orbit Chain that uses Celestia for data availability and settles on Arbitrum One, Ethereum, or other EVM chains.
      Learn more about Orbit in Arbitrum's introduction.
      Key components ​
      The integration of Celestia with Arbitrum orbit is possible thanks to 3 key components:
      Additionally, the Ethereum fallback mechanism is a feature of the integration, which is native in Nitro.
      DA provider implementation ​
      The Arbitrum Nitro code has a DataAvailabilityProvider interface that is used across the codebase to store and retrieve data from a specific provider (eip4844 blobs, Anytrust, and now Celestia).
      This integration implements the DataAvailabilityProvider interface for Celestia DA
      Additionally, this integration comes with the necessary code for a Nitro chain node to post and retrieve data from Celestia.
      The core logic behind posting and retrieving data happens in celestia.go where data is stored on Celestia and serialized into a small batch of data that gets published once the necessary range of headers (data roots) has been relayed to the BlobstreamX contract. Then the Read logic takes care of taking the deserialized Blob Pointer struct and consuming it in order to fetch the data from Celestia and additionally inform the fetcher about the position of the data on Celestia (we'll get back to this in the next section).
      The following represents a non-exhaustive list of considerations when running a Batch Poster node for a chain with Celestia underneath:
      • You will need to use a consensus node RPC endpoint, you can find a list of them for Mocha
      • The Batch Poster will only post a Celestia batch to the underlying chain if the height for which it posted is in a recent range in BlobstreamX and if the verification succeeds, otherwise it will discard the batch. Since it will wait until a range is relayed, it can take several minutes for a batch to be posted, but one can always make an on-chain request for the BlobstreamX contract to relay a header promptly.
      The following represents a non-exhaustive list of considerations when running a Nitro node for a chain with Celestia underneath:
      • The TendermintRpc endpoint is only needed by the batch poster, every other node can operate without a connection to a full node.
      • The message header flag for Celestia batches is 0x0c.
      • You will need to know the namespace for the chain that you are trying to connect to, but don't worry if you don't find it, as the information in the BlobPointer can be used to identify where a batch of data is in the Celestia Data Square for a given height, and thus can be used to find out the namespace as well!
      Preimage Oracle Implementation ​
      In order to support fraud proofs, this integration has the necessary code for a Nitro validator to populate its preimage mapping with Celestia hashes that then get "unpealed" in order to reveal the full data for a Blob. You can read more about the "Hash Oracle Trick".
      The data structures and hashing functions for this can be found in the nitro/das/celestia/tree folder
      You can see where the preimage oracle gets used in the fraud proof replay binary here
      Something important to note is that the preimage oracle only keeps track of hashes for the rows in the Celestia data square in which a blob resides in, this way each Orbit chain with Celestia underneath does not need validators to recompute an entire Celestia Data Square, but instead, only have to compute the row roots for the rows in which it's data lives in, and the header data root, which is the binary merkle tree hash built using the row roots and column roots fetched from a Celestia node. Because only data roots that can be confirmed on Blobstream get accepted into the sequencer inbox, one can have a high degree of certainty that the canonical data root being unpealed as well as the row roots are in fact correct.
      Blobstream X implementation ​
      Finally, the integration only accepts batches with information that can be confirmed on BlobstreamX, which gives us a high certainty that data was made available on Celestia.
      You can see how BlobstreamX is integrated into the SequencerInbox.sol contract here, which allows us to discard batches with otherwise faulty data roots, thus giving us a high degree of confidence that the data root can be safely unpacked in case of a challenge.
      The Celestia and Arbitrum integration also includes Blobstream, which relays commitments to Celestia’s data root to an onchain light client on Ethereum. This allows L2 solutions that settle on Ethereum to benefit from the scalability Celestia’s data availability layer can provide.
      Ethereum fallback mechanism in Nitro ​
      By default in Arbitrum Nitro, the Ethereum fallback mechanism in the BatchPoster function is handling the process of storing data, with a fallback mechanism to store data onchain if the primary data availability storage fails.
      The @celestiaorg/nitro integration uses the same fallback mechanism.
      More information can be found on the Ethereum fallback mechanisms for Celestia, which enables Ethereum L2s (or L3s) to “fall back” to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta.
      The fallback logic for Celestia DA is configurable, providing an alternative to the previous default fallback mechanism. Additionally, an ability has been added to the Arbitrum node software which allows the sequencer to call VerifyAttestation to check if a data root has been posted on Blobstream or not, before it sends the sequencer message (data pointer) to the underlying chain.
      Next steps ​
      In the next page, learn how to deploy an Arbitrum rollup devnet using Celestia as DA.
      ',34),s=[n];function l(h,c,d,m,b,u){return t(),a("div",null,s)}const g=e(o,[["render",l]]);export{f as __pageData,g as default};
+import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia-Arbitrum.png",f=JSON.parse('{"title":"Introduction to Arbitrum rollups with Celestia as DA","description":"An overview of the integration of Arbitrum Nitro with Celestia, detailing the key features and benefits, including the Ethereum fallback mechanism.","frontmatter":{"description":"An overview of the integration of Arbitrum Nitro with Celestia, detailing the key features and benefits, including the Ethereum fallback mechanism.","head":[["meta",{"name":"og:title","content":"Introduction to Arbitrum rollups with Celestia as DA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-integration.md","filePath":"developers/arbitrum-integration.md","lastUpdated":1725992025000}'),o={name:"developers/arbitrum-integration.md"},n=i('
      Introduction to Arbitrum rollups with Celestia as DA ​
      Celestia_Arbitrum
      Overview ​
      The integration of Celestia with Arbitrum Orbit and the Nitro tech stack marks the first external contribution to the Arbitrum Orbit protocol layer, offering developers an additional option for selecting a data availability layer alongside Arbitrum AnyTrust. The integration allows developers to deploy an Orbit Chain that uses Celestia for data availability and settles on Arbitrum One, Ethereum, or other EVM chains.
      Learn more about Orbit in Arbitrum's introduction.
      Key components ​
      The integration of Celestia with Arbitrum orbit is possible thanks to 3 key components:
      Additionally, the Ethereum fallback mechanism is a feature of the integration, which is native in Nitro.
      DA provider implementation ​
      The Arbitrum Nitro code has a DataAvailabilityProvider interface that is used across the codebase to store and retrieve data from a specific provider (eip4844 blobs, Anytrust, and now Celestia).
      This integration implements the DataAvailabilityProvider interface for Celestia DA
      Additionally, this integration comes with the necessary code for a Nitro chain node to post and retrieve data from Celestia.
      The core logic behind posting and retrieving data happens in celestia.go where data is stored on Celestia and serialized into a small batch of data that gets published once the necessary range of headers (data roots) has been relayed to the BlobstreamX contract. Then the Read logic takes care of taking the deserialized Blob Pointer struct and consuming it in order to fetch the data from Celestia and additionally inform the fetcher about the position of the data on Celestia (we'll get back to this in the next section).
      The following represents a non-exhaustive list of considerations when running a Batch Poster node for a chain with Celestia underneath:
      • You will need to use a consensus node RPC endpoint, you can find a list of them for Mocha
      • The Batch Poster will only post a Celestia batch to the underlying chain if the height for which it posted is in a recent range in BlobstreamX and if the verification succeeds, otherwise it will discard the batch. Since it will wait until a range is relayed, it can take several minutes for a batch to be posted, but one can always make an on-chain request for the BlobstreamX contract to relay a header promptly.
      The following represents a non-exhaustive list of considerations when running a Nitro node for a chain with Celestia underneath:
      • The TendermintRpc endpoint is only needed by the batch poster, every other node can operate without a connection to a full node.
      • The message header flag for Celestia batches is 0x0c.
      • You will need to know the namespace for the chain that you are trying to connect to, but don't worry if you don't find it, as the information in the BlobPointer can be used to identify where a batch of data is in the Celestia Data Square for a given height, and thus can be used to find out the namespace as well!
      Preimage Oracle Implementation ​
      In order to support fraud proofs, this integration has the necessary code for a Nitro validator to populate its preimage mapping with Celestia hashes that then get "unpealed" in order to reveal the full data for a Blob. You can read more about the "Hash Oracle Trick".
      The data structures and hashing functions for this can be found in the nitro/das/celestia/tree folder
      You can see where the preimage oracle gets used in the fraud proof replay binary here
      Something important to note is that the preimage oracle only keeps track of hashes for the rows in the Celestia data square in which a blob resides in, this way each Orbit chain with Celestia underneath does not need validators to recompute an entire Celestia Data Square, but instead, only have to compute the row roots for the rows in which it's data lives in, and the header data root, which is the binary merkle tree hash built using the row roots and column roots fetched from a Celestia node. Because only data roots that can be confirmed on Blobstream get accepted into the sequencer inbox, one can have a high degree of certainty that the canonical data root being unpealed as well as the row roots are in fact correct.
      Blobstream X implementation ​
      Finally, the integration only accepts batches with information that can be confirmed on BlobstreamX, which gives us a high certainty that data was made available on Celestia.
      You can see how BlobstreamX is integrated into the SequencerInbox.sol contract here, which allows us to discard batches with otherwise faulty data roots, thus giving us a high degree of confidence that the data root can be safely unpacked in case of a challenge.
      The Celestia and Arbitrum integration also includes Blobstream, which relays commitments to Celestia’s data root to an onchain light client on Ethereum. This allows L2 solutions that settle on Ethereum to benefit from the scalability Celestia’s data availability layer can provide.
      Ethereum fallback mechanism in Nitro ​
      By default in Arbitrum Nitro, the Ethereum fallback mechanism in the BatchPoster function is handling the process of storing data, with a fallback mechanism to store data onchain if the primary data availability storage fails.
      The @celestiaorg/nitro integration uses the same fallback mechanism.
      More information can be found on the Ethereum fallback mechanisms for Celestia, which enables Ethereum L2s (or L3s) to “fall back” to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta.
      The fallback logic for Celestia DA is configurable, providing an alternative to the previous default fallback mechanism. Additionally, an ability has been added to the Arbitrum node software which allows the sequencer to call VerifyAttestation to check if a data root has been posted on Blobstream or not, before it sends the sequencer message (data pointer) to the underlying chain.
      Next steps ​
      In the next page, learn how to deploy an Arbitrum rollup devnet using Celestia as DA.
      ',34),s=[n];function l(h,c,d,m,b,u){return t(),a("div",null,s)}const g=e(o,[["render",l]]);export{f as __pageData,g as default};
diff --git a/pr-1699/assets/developers_arbitrum-integration.md.2b72ec21.lean.js b/pr-1699/assets/developers_arbitrum-integration.md.fd5df284.lean.js
similarity index 93%
rename from pr-1699/assets/developers_arbitrum-integration.md.2b72ec21.lean.js
rename to pr-1699/assets/developers_arbitrum-integration.md.fd5df284.lean.js
index a64f5642d9..e28e178656 100644
--- a/pr-1699/assets/developers_arbitrum-integration.md.2b72ec21.lean.js
+++ b/pr-1699/assets/developers_arbitrum-integration.md.fd5df284.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia-Arbitrum.png",f=JSON.parse('{"title":"Introduction to Arbitrum rollups with Celestia as DA","description":"An overview of the integration of Arbitrum Nitro with Celestia, detailing the key features and benefits, including the Ethereum fallback mechanism.","frontmatter":{"description":"An overview of the integration of Arbitrum Nitro with Celestia, detailing the key features and benefits, including the Ethereum fallback mechanism.","head":[["meta",{"name":"og:title","content":"Introduction to Arbitrum rollups with Celestia as DA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-integration.md","filePath":"developers/arbitrum-integration.md","lastUpdated":1725971357000}'),o={name:"developers/arbitrum-integration.md"},n=i("",34),s=[n];function l(h,c,d,m,b,u){return t(),a("div",null,s)}const g=e(o,[["render",l]]);export{f as __pageData,g as default};
+import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia-Arbitrum.png",f=JSON.parse('{"title":"Introduction to Arbitrum rollups with Celestia as DA","description":"An overview of the integration of Arbitrum Nitro with Celestia, detailing the key features and benefits, including the Ethereum fallback mechanism.","frontmatter":{"description":"An overview of the integration of Arbitrum Nitro with Celestia, detailing the key features and benefits, including the Ethereum fallback mechanism.","head":[["meta",{"name":"og:title","content":"Introduction to Arbitrum rollups with Celestia as DA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-integration.md","filePath":"developers/arbitrum-integration.md","lastUpdated":1725992025000}'),o={name:"developers/arbitrum-integration.md"},n=i("",34),s=[n];function l(h,c,d,m,b,u){return t(),a("div",null,s)}const g=e(o,[["render",l]]);export{f as __pageData,g as default};
diff --git a/pr-1699/assets/developers_arbitrum-smart-contract.md.5de83013.js b/pr-1699/assets/developers_arbitrum-smart-contract.md.8b7aa3c4.js
similarity index 99%
rename from pr-1699/assets/developers_arbitrum-smart-contract.md.5de83013.js
rename to pr-1699/assets/developers_arbitrum-smart-contract.md.8b7aa3c4.js
index 62951e2472..4f662138a9 100644
--- a/pr-1699/assets/developers_arbitrum-smart-contract.md.5de83013.js
+++ b/pr-1699/assets/developers_arbitrum-smart-contract.md.8b7aa3c4.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Deploy a smart contract to your Arbitrum rollup","description":"A tutorial that guides you through the process of deploying a smart contract to your Arbitrum rollup using a L2 Nitro devnet, including setting up the environment, creating and testing the smart contract, and interacting with the deployed contract.","frontmatter":{"description":"A tutorial that guides you through the process of deploying a smart contract to your Arbitrum rollup using a L2 Nitro devnet, including setting up the environment, creating and testing the smart contract, and interacting with the deployed contract.","head":[["meta",{"name":"og:title","content":"Deploy a smart contract to your Arbitrum rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-smart-contract.md","filePath":"developers/arbitrum-smart-contract.md","lastUpdated":1725971357000}'),l={name:"developers/arbitrum-smart-contract.md"},p=o(`
      Deploy a smart contract to your Arbitrum rollup ​
      Overview ​
      Welcome to the guide on deploying a smart contract to your Arbitrum rollup. In this tutorial, you will learn how to deploy a smart contract using the L2 Nitro devnet and the provided public and private keys for testing purposes.
      Prerequisites ​
      Setup ​
      First, in your $HOME directory, set up a new project folder for this tutorial and init the project with npm:
      bash
      cd $HOME
+import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Deploy a smart contract to your Arbitrum rollup","description":"A tutorial that guides you through the process of deploying a smart contract to your Arbitrum rollup using a L2 Nitro devnet, including setting up the environment, creating and testing the smart contract, and interacting with the deployed contract.","frontmatter":{"description":"A tutorial that guides you through the process of deploying a smart contract to your Arbitrum rollup using a L2 Nitro devnet, including setting up the environment, creating and testing the smart contract, and interacting with the deployed contract.","head":[["meta",{"name":"og:title","content":"Deploy a smart contract to your Arbitrum rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-smart-contract.md","filePath":"developers/arbitrum-smart-contract.md","lastUpdated":1725992025000}'),l={name:"developers/arbitrum-smart-contract.md"},p=o(`
      Deploy a smart contract to your Arbitrum rollup ​
      Overview ​
      Welcome to the guide on deploying a smart contract to your Arbitrum rollup. In this tutorial, you will learn how to deploy a smart contract using the L2 Nitro devnet and the provided public and private keys for testing purposes.
      Prerequisites ​
      Setup ​
      First, in your $HOME directory, set up a new project folder for this tutorial and init the project with npm:
      bash
      cd $HOME
 mkdir counter-project && cd counter-project && npm init -y
      cd $HOME
 mkdir counter-project && cd counter-project && npm init -y
      Next, initialize a Foundry project with the following command:
      bash
      forge init counter_contract
      forge init counter_contract
      Create your smart contract ​
      Take a look at the Counter.sol file in your counter-project/counter_contract/src directory:
      solidity
      // SPDX-License-Identifier: UNLICENSED
 pragma solidity ^0.8.13;
diff --git a/pr-1699/assets/developers_arbitrum-smart-contract.md.5de83013.lean.js b/pr-1699/assets/developers_arbitrum-smart-contract.md.8b7aa3c4.lean.js
similarity index 94%
rename from pr-1699/assets/developers_arbitrum-smart-contract.md.5de83013.lean.js
rename to pr-1699/assets/developers_arbitrum-smart-contract.md.8b7aa3c4.lean.js
index c1a7dffad6..a30757b580 100644
--- a/pr-1699/assets/developers_arbitrum-smart-contract.md.5de83013.lean.js
+++ b/pr-1699/assets/developers_arbitrum-smart-contract.md.8b7aa3c4.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Deploy a smart contract to your Arbitrum rollup","description":"A tutorial that guides you through the process of deploying a smart contract to your Arbitrum rollup using a L2 Nitro devnet, including setting up the environment, creating and testing the smart contract, and interacting with the deployed contract.","frontmatter":{"description":"A tutorial that guides you through the process of deploying a smart contract to your Arbitrum rollup using a L2 Nitro devnet, including setting up the environment, creating and testing the smart contract, and interacting with the deployed contract.","head":[["meta",{"name":"og:title","content":"Deploy a smart contract to your Arbitrum rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-smart-contract.md","filePath":"developers/arbitrum-smart-contract.md","lastUpdated":1725971357000}'),l={name:"developers/arbitrum-smart-contract.md"},p=o("",60),e=[p];function t(c,r,i,y,E,u){return a(),n("div",null,e)}const h=s(l,[["render",t]]);export{F as __pageData,h as default};
+import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Deploy a smart contract to your Arbitrum rollup","description":"A tutorial that guides you through the process of deploying a smart contract to your Arbitrum rollup using a L2 Nitro devnet, including setting up the environment, creating and testing the smart contract, and interacting with the deployed contract.","frontmatter":{"description":"A tutorial that guides you through the process of deploying a smart contract to your Arbitrum rollup using a L2 Nitro devnet, including setting up the environment, creating and testing the smart contract, and interacting with the deployed contract.","head":[["meta",{"name":"og:title","content":"Deploy a smart contract to your Arbitrum rollup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/arbitrum-smart-contract.md","filePath":"developers/arbitrum-smart-contract.md","lastUpdated":1725992025000}'),l={name:"developers/arbitrum-smart-contract.md"},p=o("",60),e=[p];function t(c,r,i,y,E,u){return a(),n("div",null,e)}const h=s(l,[["render",t]]);export{F as __pageData,h as default};
diff --git a/pr-1699/assets/developers_blobstream-contracts.md.25c4c416.js b/pr-1699/assets/developers_blobstream-contracts.md.06e023da.js
similarity index 99%
rename from pr-1699/assets/developers_blobstream-contracts.md.25c4c416.js
rename to pr-1699/assets/developers_blobstream-contracts.md.06e023da.js
index c15be70f04..8d7abc4808 100644
--- a/pr-1699/assets/developers_blobstream-contracts.md.25c4c416.js
+++ b/pr-1699/assets/developers_blobstream-contracts.md.06e023da.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as o,Q as e}from"./chunks/framework.b47e54aa.js";const d=JSON.parse(`{"title":"Integrate with Blobstream contracts","description":"Learn how to integrate your L2's onchain logic with Blobstream","frontmatter":{"sidebar_label":"Integrate with Blobstream contracts","description":"Learn how to integrate your L2's onchain logic with Blobstream","prev":{"text":"New SP1 Blobstream deployments","link":"/developers/sp1-blobstream-deploy"},"head":[["meta",{"name":"og:title","content":"Integrate with Blobstream contracts | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-contracts.md","filePath":"developers/blobstream-contracts.md","lastUpdated":1725971357000}`),n={name:"developers/blobstream-contracts.md"},l=e(`
      Integrate with Blobstream contracts ​
      Getting started ​
      Prerequisites ​
      Make sure to have the following installed:
      Installing Blobstream contracts ​
      We will be using the IDAOracle interface to verify inclusion. So, we will install the Blobstream contracts repo as a dependency:
      sh
      forge install celestiaorg/blobstream-contracts --no-commit
      forge install celestiaorg/blobstream-contracts --no-commit
      Make sure that the directory you're running this command from is an initialized git repository. If not, just initialize the repo using:
      sh
      git init
      git init
      Note that the minimum Solidity compiler version for using the Blobstream contracts is 0.8.19.
      Example usage ​
      Example minimal Solidity contract for a stub ZK rollup that leverages the BlobstreamX.sol contract to check that data has been posted to Celestia:
      solidity
      // SPDX-License-Identifier: Apache-2.0
+import{_ as s,o as a,c as o,Q as e}from"./chunks/framework.b47e54aa.js";const d=JSON.parse(`{"title":"Integrate with Blobstream contracts","description":"Learn how to integrate your L2's onchain logic with Blobstream","frontmatter":{"sidebar_label":"Integrate with Blobstream contracts","description":"Learn how to integrate your L2's onchain logic with Blobstream","prev":{"text":"New SP1 Blobstream deployments","link":"/developers/sp1-blobstream-deploy"},"head":[["meta",{"name":"og:title","content":"Integrate with Blobstream contracts | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-contracts.md","filePath":"developers/blobstream-contracts.md","lastUpdated":1725992025000}`),n={name:"developers/blobstream-contracts.md"},l=e(`
      Integrate with Blobstream contracts ​
      Getting started ​
      Prerequisites ​
      Make sure to have the following installed:
      Installing Blobstream contracts ​
      We will be using the IDAOracle interface to verify inclusion. So, we will install the Blobstream contracts repo as a dependency:
      sh
      forge install celestiaorg/blobstream-contracts --no-commit
      forge install celestiaorg/blobstream-contracts --no-commit
      Make sure that the directory you're running this command from is an initialized git repository. If not, just initialize the repo using:
      sh
      git init
      git init
      Note that the minimum Solidity compiler version for using the Blobstream contracts is 0.8.19.
      Example usage ​
      Example minimal Solidity contract for a stub ZK rollup that leverages the BlobstreamX.sol contract to check that data has been posted to Celestia:
      solidity
      // SPDX-License-Identifier: Apache-2.0
 pragma solidity ^0.8.19;
 
 import "blobstream-contracts/IDAOracle.sol";
diff --git a/pr-1699/assets/developers_blobstream-contracts.md.25c4c416.lean.js b/pr-1699/assets/developers_blobstream-contracts.md.06e023da.lean.js
similarity index 93%
rename from pr-1699/assets/developers_blobstream-contracts.md.25c4c416.lean.js
rename to pr-1699/assets/developers_blobstream-contracts.md.06e023da.lean.js
index 52b246dd5a..9b62309a06 100644
--- a/pr-1699/assets/developers_blobstream-contracts.md.25c4c416.lean.js
+++ b/pr-1699/assets/developers_blobstream-contracts.md.06e023da.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as o,Q as e}from"./chunks/framework.b47e54aa.js";const d=JSON.parse(`{"title":"Integrate with Blobstream contracts","description":"Learn how to integrate your L2's onchain logic with Blobstream","frontmatter":{"sidebar_label":"Integrate with Blobstream contracts","description":"Learn how to integrate your L2's onchain logic with Blobstream","prev":{"text":"New SP1 Blobstream deployments","link":"/developers/sp1-blobstream-deploy"},"head":[["meta",{"name":"og:title","content":"Integrate with Blobstream contracts | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-contracts.md","filePath":"developers/blobstream-contracts.md","lastUpdated":1725971357000}`),n={name:"developers/blobstream-contracts.md"},l=e("",27),t=[l];function r(p,c,i,y,E,h){return a(),o("div",null,t)}const u=s(n,[["render",r]]);export{d as __pageData,u as default};
+import{_ as s,o as a,c as o,Q as e}from"./chunks/framework.b47e54aa.js";const d=JSON.parse(`{"title":"Integrate with Blobstream contracts","description":"Learn how to integrate your L2's onchain logic with Blobstream","frontmatter":{"sidebar_label":"Integrate with Blobstream contracts","description":"Learn how to integrate your L2's onchain logic with Blobstream","prev":{"text":"New SP1 Blobstream deployments","link":"/developers/sp1-blobstream-deploy"},"head":[["meta",{"name":"og:title","content":"Integrate with Blobstream contracts | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-contracts.md","filePath":"developers/blobstream-contracts.md","lastUpdated":1725992025000}`),n={name:"developers/blobstream-contracts.md"},l=e("",27),t=[l];function r(p,c,i,y,E,h){return a(),o("div",null,t)}const u=s(n,[["render",r]]);export{d as __pageData,u as default};
diff --git a/pr-1699/assets/developers_blobstream-offchain.md.3b490822.js b/pr-1699/assets/developers_blobstream-offchain.md.fbd363f2.js
similarity index 99%
rename from pr-1699/assets/developers_blobstream-offchain.md.3b490822.js
rename to pr-1699/assets/developers_blobstream-offchain.md.fbd363f2.js
index be63273ceb..692ce497b2 100644
--- a/pr-1699/assets/developers_blobstream-offchain.md.3b490822.js
+++ b/pr-1699/assets/developers_blobstream-offchain.md.fbd363f2.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse(`{"title":"Integrate with Blobstream client","description":"Learn how to integrate your L2's offchain logic with Blobstream","frontmatter":{"description":"Learn how to integrate your L2's offchain logic with Blobstream","head":[["meta",{"name":"og:title","content":"Integrate with Blobstream client | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-offchain.md","filePath":"developers/blobstream-offchain.md","lastUpdated":1725971357000}`),e={name:"developers/blobstream-offchain.md"},o=l(`
      Integrate with Blobstream client ​
      Blobstream demo rollup ​
      Rollups can use Blobstream for DA by posting their data to Celestia and then proving that it was posted on Ethereum. This is done identically to how any rollup or user would post data to Celestia. Then, a zero-knowledge proof that Celestia validators have come to consensus on Celestia block headers is generated, and subsequently relayed to Ethereum to the Blobstream smart contract.
      This demo rollup will outline (the outline is not an implementation! Please do not expect to copy and paste this code 🙂) a very simple Blobstream rollup to illustrate at a high level what this could look like.
      Defining a chain ​
      The first step to starting a new chain is to define the structure of the commitments that each block consists of.
      go
      type Block struct {
+import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse(`{"title":"Integrate with Blobstream client","description":"Learn how to integrate your L2's offchain logic with Blobstream","frontmatter":{"description":"Learn how to integrate your L2's offchain logic with Blobstream","head":[["meta",{"name":"og:title","content":"Integrate with Blobstream client | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-offchain.md","filePath":"developers/blobstream-offchain.md","lastUpdated":1725992025000}`),e={name:"developers/blobstream-offchain.md"},o=l(`
      Integrate with Blobstream client ​
      Blobstream demo rollup ​
      Rollups can use Blobstream for DA by posting their data to Celestia and then proving that it was posted on Ethereum. This is done identically to how any rollup or user would post data to Celestia. Then, a zero-knowledge proof that Celestia validators have come to consensus on Celestia block headers is generated, and subsequently relayed to Ethereum to the Blobstream smart contract.
      This demo rollup will outline (the outline is not an implementation! Please do not expect to copy and paste this code 🙂) a very simple Blobstream rollup to illustrate at a high level what this could look like.
      Defining a chain ​
      The first step to starting a new chain is to define the structure of the commitments that each block consists of.
      go
      type Block struct {
     // Data is the data of a block that is submitted to Celestia.
     Data \`json:"Data"\`
     // Header is the set of commitments over a block that is submitted to
diff --git a/pr-1699/assets/developers_blobstream-offchain.md.3b490822.lean.js b/pr-1699/assets/developers_blobstream-offchain.md.fbd363f2.lean.js
similarity index 91%
rename from pr-1699/assets/developers_blobstream-offchain.md.3b490822.lean.js
rename to pr-1699/assets/developers_blobstream-offchain.md.fbd363f2.lean.js
index 77cad7d9e2..60a399a397 100644
--- a/pr-1699/assets/developers_blobstream-offchain.md.3b490822.lean.js
+++ b/pr-1699/assets/developers_blobstream-offchain.md.fbd363f2.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse(`{"title":"Integrate with Blobstream client","description":"Learn how to integrate your L2's offchain logic with Blobstream","frontmatter":{"description":"Learn how to integrate your L2's offchain logic with Blobstream","head":[["meta",{"name":"og:title","content":"Integrate with Blobstream client | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-offchain.md","filePath":"developers/blobstream-offchain.md","lastUpdated":1725971357000}`),e={name:"developers/blobstream-offchain.md"},o=l("",42),p=[o];function t(r,c,i,E,y,h){return a(),n("div",null,p)}const b=s(e,[["render",t]]);export{u as __pageData,b as default};
+import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse(`{"title":"Integrate with Blobstream client","description":"Learn how to integrate your L2's offchain logic with Blobstream","frontmatter":{"description":"Learn how to integrate your L2's offchain logic with Blobstream","head":[["meta",{"name":"og:title","content":"Integrate with Blobstream client | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-offchain.md","filePath":"developers/blobstream-offchain.md","lastUpdated":1725992025000}`),e={name:"developers/blobstream-offchain.md"},o=l("",42),p=[o];function t(r,c,i,E,y,h){return a(),n("div",null,p)}const b=s(e,[["render",t]]);export{u as __pageData,b as default};
diff --git a/pr-1699/assets/developers_blobstream-proof-queries.md.21c99b59.js b/pr-1699/assets/developers_blobstream-proof-queries.md.19225b90.js
similarity index 99%
rename from pr-1699/assets/developers_blobstream-proof-queries.md.21c99b59.js
rename to pr-1699/assets/developers_blobstream-proof-queries.md.19225b90.js
index d6021f6e67..50113a9ae3 100644
--- a/pr-1699/assets/developers_blobstream-proof-queries.md.21c99b59.js
+++ b/pr-1699/assets/developers_blobstream-proof-queries.md.19225b90.js
@@ -1,4 +1,4 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/blobstream/blobstream-square.png",p="/docs-preview/pr-1699/img/blobstream/blobstream-commitment-diagram.png",h=JSON.parse('{"title":"Blobstream proofs queries","description":"Learn how to query the inclusion proofs used in Blobstream","frontmatter":{"description":"Learn how to query the inclusion proofs used in Blobstream","next":{"text":"Requesting data commitment ranges","link":"/developers/blobstream-x-requesting-data-commitment-ranges"},"head":[["meta",{"name":"og:title","content":"Blobstream proofs queries | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-proof-queries.md","filePath":"developers/blobstream-proof-queries.md","lastUpdated":1725971357000}'),e={name:"developers/blobstream-proof-queries.md"},t=l(`
      Blobstream proofs queries ​
      Prerequisites ​
      • Access to a Celestia consensus node RPC endpoint (or full node). The node doesn't need to be a validating node in order for the proofs to be queried. A full node is enough.
      For golang snippets, the tendermint RPC client, referred to as trpc, will be used for the queries. It can be initialized using:
      go
          trpc, err := http.New("<rpc_endpoint>", "/websocket")
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/blobstream/blobstream-square.png",p="/docs-preview/pr-1699/img/blobstream/blobstream-commitment-diagram.png",h=JSON.parse('{"title":"Blobstream proofs queries","description":"Learn how to query the inclusion proofs used in Blobstream","frontmatter":{"description":"Learn how to query the inclusion proofs used in Blobstream","next":{"text":"Requesting data commitment ranges","link":"/developers/blobstream-x-requesting-data-commitment-ranges"},"head":[["meta",{"name":"og:title","content":"Blobstream proofs queries | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-proof-queries.md","filePath":"developers/blobstream-proof-queries.md","lastUpdated":1725992025000}'),e={name:"developers/blobstream-proof-queries.md"},t=l(`
      Blobstream proofs queries ​
      Prerequisites ​
      • Access to a Celestia consensus node RPC endpoint (or full node). The node doesn't need to be a validating node in order for the proofs to be queried. A full node is enough.
      For golang snippets, the tendermint RPC client, referred to as trpc, will be used for the queries. It can be initialized using:
      go
          trpc, err := http.New("<rpc_endpoint>", "/websocket")
 	if err != nil {
 		...
 	}
@@ -24,7 +24,7 @@ import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const o=
 		if err != nil {
 			...
 		}
-	}(trpc)
      The <rpc_endpoint> can be retrieved from mainnet for Celestia mainnet beta, and mocha for the Mocha testnet.
      In case the reader wants to interact with an on-chain contract that can be used to verify that data was posted to Celestia, the bindings of that contract are needed.
      For Blobstream, the golang bindings can be found in the following links:
      text
      https://github.com/succinctlabs/blobstreamx/blob/main/bindings/BlobstreamX.go
      https://github.com/succinctlabs/blobstreamx/blob/main/bindings/BlobstreamX.go
      text
      https://github.com/succinctlabs/sp1-blobstream/blob/main/bindings/SP1Blobstream.go
      https://github.com/succinctlabs/sp1-blobstream/blob/main/bindings/SP1Blobstream.go
      For other languages, the corresponding smart contract bindings should be generated. Refer to abigen for more information.
      Overview of the proof queries ​
      To prove the inclusion of PayForBlobs (PFB) transactions, blobs or shares, committed to in a Celestia block, we use the Celestia consensus node's RPC to query for proofs that can be verified in a rollup settlement contract via Blobstream. In fact, when a PFB transaction is included in a block, it gets separated into a PFB transaction (without the blob), and the actual data blob that it carries. These two are split into shares, which are the low level constructs of a Celestia block, and saved to the corresponding Celestia block. Learn more about shares in the shares specs.
      The two diagrams below summarize how a single share, which can contain a PFB transaction, or a part of the rollup data that was posted using a PFB, is committed to in Blobstream.
      The share is highlighted in green. R0, R1 etc, represent the respective row and column roots, the blue and pink gradients are erasure encoded data. More details on the square layout can be found in the data square layout and data structures portion of the specs.
      The Celestia square ​
      Square
      The commitment scheme ​
      Blobstream Commitment Diagram
      So to prove inclusion of a share to a Celestia block, we use Blobstream as a source of truth. In a nutshell, Blobstream attests to the data posted to Celestia in the zk-Blobstream contract via verifying a zk-proof of the headers of a batch of Celestia blocks. Then, it keeps reference of that batch of blocks using the merkleized commitment of their (dataRoot, height) resulting in a data root tuple root. Check the above diagram which shows:
      • 0: those are the shares, that when unified, contain the PFB or the rollup data blob.
      • 1: the row and column roots are the namespace merkle tree roots over the shares. More information on the NMT in the NMT specs. These commit to the rows and columns containing the above shares.
      • 2: the data roots: which are the binary merkle tree commitment over the row and column roots. This means that if you can prove that a share is part of a row, using a namespace merkle proof. Then prove that this row is committed to by the data root. Then you can be sure that that share was published to the corresponding block.
      • 3: in order to batch multiple blocks into the same commitment, we create a commitment over the (dataRoot, height) tuple for a batch of blocks, which results in a data root tuple root. It's this commitment that gets stored in the Blobstream smart contract.
      So, if we're able to prove:
      • That a share is part of a row, then that row is committed to by a data root.
      • Then, prove that that data root along with its height is committed to by the data root tuple root, which gets saved to the Blobstream contract.
      We can be sure that that share was committed to in the corresponding Celestia block.
      In this document, we will provide details on how to query the above proofs, and how to adapt them to be sent to a rollup contract for verification.
      Hands-on demonstration ​
      This part will provide the details of proof generation, and the way to make the results of the proofs queries ready to be consumed by the target rollup contract.
      NOTE
      For the go client snippets, make sure to have the following replaces in your go.mod:
      go
      // go.mod
+	}(trpc)
      The <rpc_endpoint> can be retrieved from mainnet for Celestia mainnet beta, and mocha for the Mocha testnet.
      In case the reader wants to interact with an on-chain contract that can be used to verify that data was posted to Celestia, the bindings of that contract are needed.
      For Blobstream, the golang bindings can be found in the following links:
      text
      https://github.com/succinctlabs/blobstreamx/blob/main/bindings/BlobstreamX.go
      https://github.com/succinctlabs/blobstreamx/blob/main/bindings/BlobstreamX.go
      text
      https://github.com/succinctlabs/sp1-blobstream/blob/main/bindings/SP1Blobstream.go
      https://github.com/succinctlabs/sp1-blobstream/blob/main/bindings/SP1Blobstream.go
      For other languages, the corresponding smart contract bindings should be generated. Refer to abigen for more information.
      Overview of the proof queries ​
      To prove the inclusion of PayForBlobs (PFB) transactions, blobs or shares, committed to in a Celestia block, we use the Celestia consensus node's RPC to query for proofs that can be verified in a rollup settlement contract via Blobstream. In fact, when a PFB transaction is included in a block, it gets separated into a PFB transaction (without the blob), and the actual data blob that it carries. These two are split into shares, which are the low level constructs of a Celestia block, and saved to the corresponding Celestia block. Learn more about shares in the shares specs.
      The two diagrams below summarize how a single share, which can contain a PFB transaction, or a part of the rollup data that was posted using a PFB, is committed to in Blobstream.
      The share is highlighted in green. R0, R1 etc, represent the respective row and column roots, the blue and pink gradients are erasure encoded data. More details on the square layout can be found in the data square layout and data structures portion of the specs.
      The Celestia square ​
      Square
      The commitment scheme ​
      Blobstream Commitment Diagram
      So to prove inclusion of a share to a Celestia block, we use Blobstream as a source of truth. In a nutshell, Blobstream attests to the data posted to Celestia in the zk-Blobstream contract via verifying a zk-proof of the headers of a batch of Celestia blocks. Then, it keeps reference of that batch of blocks using the merkleized commitment of their (dataRoot, height) resulting in a data root tuple root. Check the above diagram which shows:
      • 0: those are the shares, that when unified, contain the PFB or the rollup data blob.
      • 1: the row and column roots are the namespace merkle tree roots over the shares. More information on the NMT in the NMT specs. These commit to the rows and columns containing the above shares.
      • 2: the data roots: which are the binary merkle tree commitment over the row and column roots. This means that if you can prove that a share is part of a row, using a namespace merkle proof. Then prove that this row is committed to by the data root. Then you can be sure that that share was published to the corresponding block.
      • 3: in order to batch multiple blocks into the same commitment, we create a commitment over the (dataRoot, height) tuple for a batch of blocks, which results in a data root tuple root. It's this commitment that gets stored in the Blobstream smart contract.
      So, if we're able to prove:
      • That a share is part of a row, then that row is committed to by a data root.
      • Then, prove that that data root along with its height is committed to by the data root tuple root, which gets saved to the Blobstream contract.
      We can be sure that that share was committed to in the corresponding Celestia block.
      In this document, we will provide details on how to query the above proofs, and how to adapt them to be sent to a rollup contract for verification.
      Hands-on demonstration ​
      This part will provide the details of proof generation, and the way to make the results of the proofs queries ready to be consumed by the target rollup contract.
      NOTE
      For the go client snippets, make sure to have the following replaces in your go.mod:
      go
      // go.mod
     github.com/cosmos/cosmos-sdk => github.com/celestiaorg/cosmos-sdk v1.18.3-sdk-v0.46.14
     github.com/gogo/protobuf => github.com/regen-network/protobuf v1.3.3-alpha.regen.1
     github.com/syndtr/goleveldb => github.com/syndtr/goleveldb v1.0.1-0.20210819022825-2ae1ddf74ef7
@@ -122,7 +122,7 @@ import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const o=
 		os.Exit(1)
 	}
 	fmt.Println(dcProof.Proof.String())
-}
      Full example of proving that a Celestia block was committed to by Blobstream contract ​
      go
      package main
+}
      Full example of proving that a Celestia block was committed to by Blobstream contract ​
      go
      package main
 
 import (
 	"context"
@@ -1122,7 +1122,7 @@ import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const o=
 			NumLeaves: big.NewInt(dataRootInclusionProof.Total),
 		},
 	}
-}
      With the nonce being the attestation nonce, which can be retrieved using Blobstream contract events. Check below for an example. And height being the Celestia Block height that contains the rollup data, along with the blockDataRoot being the data root of the block height. Finally, dataRootInclusionProof is the Celestia block data root inclusion proof to the data root tuple root that was queried at the beginning of this page.
      If the dataRoot or the tupleRootNonce is unknown during the verification:
      • dataRoot: can be queried using the /block?height=15 query (15 in this example endpoint), and taking the data_hash field from the response.
      • tupleRootNonce: can be retried via querying the data commitment stored events from the Blobstream contract and looking for the nonce attesting to the corresponding data.
      Querying the proof's tupleRootNonce ​
      go
      	// get the nonce corresponding to the block height that contains the PayForBlob transaction
+}
      With the nonce being the attestation nonce, which can be retrieved using Blobstream contract events. Check below for an example. And height being the Celestia Block height that contains the rollup data, along with the blockDataRoot being the data root of the block height. Finally, dataRootInclusionProof is the Celestia block data root inclusion proof to the data root tuple root that was queried at the beginning of this page.
      If the dataRoot or the tupleRootNonce is unknown during the verification:
      • dataRoot: can be queried using the /block?height=15 query (15 in this example endpoint), and taking the data_hash field from the response.
      • tupleRootNonce: can be retried via querying the data commitment stored events from the Blobstream contract and looking for the nonce attesting to the corresponding data.
      Querying the proof's tupleRootNonce ​
      go
      	// get the nonce corresponding to the block height that contains the PayForBlob transaction
 	// since BlobstreamX emits events when new batches are submitted, we will query the events
 	// and look for the range committing to the blob
 	// first, connect to an EVM RPC endpoint
@@ -1246,7 +1246,7 @@ import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const o=
 import {
     sp1blobstreamwrapper "github.com/succinctlabs/sp1-blobstream/bindings"
 } 
-// and use the \`BlobstreamDataCommitmentStored\` event instead.
      Listening for new data commitments ​
      For listening for new data commitment stored events, sequencers can use the WatchDataCommitmentStored as follows:
      go
          ethClient, err := ethclient.Dial("evm_rpc")
+// and use the \`BlobstreamDataCommitmentStored\` event instead.
      Listening for new data commitments ​
      For listening for new data commitment stored events, sequencers can use the WatchDataCommitmentStored as follows:
      go
          ethClient, err := ethclient.Dial("evm_rpc")
     if err != nil {
 	    return err
     }
@@ -1364,7 +1364,7 @@ import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const o=
         // (4) verify invalid state transition
         // (5) effects
     }
-}
      Then, you can submit the fraud proof using golang as follows:
      go
      package main
+}
      Then, you can submit the fraud proof using golang as follows:
      go
      package main
 
 import (
 	"context"
diff --git a/pr-1699/assets/developers_blobstream-proof-queries.md.21c99b59.lean.js b/pr-1699/assets/developers_blobstream-proof-queries.md.19225b90.lean.js
similarity index 93%
rename from pr-1699/assets/developers_blobstream-proof-queries.md.21c99b59.lean.js
rename to pr-1699/assets/developers_blobstream-proof-queries.md.19225b90.lean.js
index d1b644c78b..6906f60b0e 100644
--- a/pr-1699/assets/developers_blobstream-proof-queries.md.21c99b59.lean.js
+++ b/pr-1699/assets/developers_blobstream-proof-queries.md.19225b90.lean.js
@@ -1 +1 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/blobstream/blobstream-square.png",p="/docs-preview/pr-1699/img/blobstream/blobstream-commitment-diagram.png",h=JSON.parse('{"title":"Blobstream proofs queries","description":"Learn how to query the inclusion proofs used in Blobstream","frontmatter":{"description":"Learn how to query the inclusion proofs used in Blobstream","next":{"text":"Requesting data commitment ranges","link":"/developers/blobstream-x-requesting-data-commitment-ranges"},"head":[["meta",{"name":"og:title","content":"Blobstream proofs queries | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-proof-queries.md","filePath":"developers/blobstream-proof-queries.md","lastUpdated":1725971357000}'),e={name:"developers/blobstream-proof-queries.md"},t=l("",158),c=[t];function r(E,y,i,A,F,d){return n(),a("div",null,c)}const m=s(e,[["render",r]]);export{h as __pageData,m as default};
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/blobstream/blobstream-square.png",p="/docs-preview/pr-1699/img/blobstream/blobstream-commitment-diagram.png",h=JSON.parse('{"title":"Blobstream proofs queries","description":"Learn how to query the inclusion proofs used in Blobstream","frontmatter":{"description":"Learn how to query the inclusion proofs used in Blobstream","next":{"text":"Requesting data commitment ranges","link":"/developers/blobstream-x-requesting-data-commitment-ranges"},"head":[["meta",{"name":"og:title","content":"Blobstream proofs queries | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-proof-queries.md","filePath":"developers/blobstream-proof-queries.md","lastUpdated":1725992025000}'),e={name:"developers/blobstream-proof-queries.md"},t=l("",158),c=[t];function r(E,y,i,A,F,d){return n(),a("div",null,c)}const m=s(e,[["render",r]]);export{h as __pageData,m as default};
diff --git a/pr-1699/assets/developers_blobstream-rollups.md.580268e1.js b/pr-1699/assets/developers_blobstream-rollups.md.9c8cb137.js
similarity index 99%
rename from pr-1699/assets/developers_blobstream-rollups.md.580268e1.js
rename to pr-1699/assets/developers_blobstream-rollups.md.9c8cb137.js
index ff483df0f8..6101f29f93 100644
--- a/pr-1699/assets/developers_blobstream-rollups.md.580268e1.js
+++ b/pr-1699/assets/developers_blobstream-rollups.md.9c8cb137.js
@@ -1,3 +1,3 @@
-import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Introduction to Blobstream rollups","description":"Learn how to build rollups that use Blobstream.","frontmatter":{"description":"Learn how to build rollups that use Blobstream.","prev":{"text":"Ethereum fallback mechanism","link":"/developers/ethereum-fallback"},"next":{"text":"Submitting data blobs to Celestia","link":"/developers/submit-data"},"head":[["meta",{"name":"og:title","content":"Introduction to Blobstream rollups | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-rollups.md","filePath":"developers/blobstream-rollups.md","lastUpdated":1725971357000}'),s={name:"developers/blobstream-rollups.md"},r=a(`
      Introduction to Blobstream rollups ​
      Blobstream is the first data availability solution for EVM chains that securely scales with the number of users. It allows rollups to post their data on Celestia while proving their availability in the rollup settlement contract.
      This document will outline a few ways to build optimistic or zk-rollups that post their data to Celestia and use Blobstream to prove that data's availability.
      Concepts ​
      This section will go over two constructs that can be used in building Blobstream rollups. Each with its pros and cons and the rollup developer can choose which one suits their needs better.
      Note: Only the sequence of spans method can be used currently to build Blobstream rollups. The blob share commitment way still requires some tooling that will be built in the upcoming months.
      Blob share commitment ​
      The blob share commitment is a commitment over the data contained in the MsgPayForBlobs transaction. This commitment allows proving that the corresponding data exists on Celestia efficiently.
      Blob share commitment: Proof details ​
      To prove that the data corresponding to a blob share commitment was posted to Celestia using Blobstream, the following proofs need to be verified:
      1. share inclusion proof to the blob share commitment: meaning creating two merkle proofs: 
        1. share merkle proof up to the subtree root corresponding to that share
        2. subtree root merkle proof to the blob share commitment
      2. blob share commitment inclusion proof to the data root tuple root: meaning four merkle proofs: 
        1. subtree roots merkle proofs to the blob share commitment: to make sure the subtree roots are valid
        2. subtree roots merkle proofs up to the row roots: to prove that the subtree roots belong to a set of rows in the Celestia block
        3. row roots proofs to the data root: to prove that those rows belong to the Celestia Block
        4. data root tuple proof to the data root tuple: to prove that the Celestia block referenced by its height and data root, was committed to by Blobstream.
      More details on the blob share commitment inclusion proof can be found in the commitment scheme docs and also the data square layout.
      If all of these proofs are valid, then you successfully managed to prove that the data corresponding to that blob share commitment has been posted to Celestia.
      NOTE
      Generating/verifying blob share commitment proofs is still not supported. It still needs tooling to generate the proofs on the node side, and verifying them on the Solidity side which will be built in the upcoming months.
      Blob share commitment: Compact proofs ​
      There is a way to have compact proofs, when using blob share commitments, unlike the ones defined above; that allow less costly inclusion proofs. These require the ability to parse the protobuf encoded PFBs.
      In fact, if the rollup project has a way to parse the protobuf encoded PFB, either in a smart contract or a zk-circuit, they will be able to create compact proofs of the rollup data.
      These proofs will work as follows:
      • Parsing the PFB and taking out the blob share commitment
      • Comparing the PFB commitment to the one saved in the rollup contract
      • Proving inclusion of the PFB to the data root tuple root. This will be a compact proof since we will only be proving two shares regardless of the size of the rollup data.
      More details on compact proofs can be found in ADR-011.
      Blob share commitment: Pros ​
      The pros of referencing rollup data using a blob share commitment:
      • Using the same commitment that exists on the PFB, without having to find another way of referencing the rollup data.
      • If the team has access to protobuf parsing, it allows for compact proof, but the parsing costs need to be investigated.
      Blob share commitment: Cons ​
      • Large/expensive proofs in the case of having no way to parse the protobuf PFB encoding.
      • In the optimistic rollups construction, defined below, this requires waiting for the Celestia block to be committed to by Blobstream before saving updating the settlement contract. This might require waiting for a few hours, depending on the batches size on each chain, to finally submit the rollup update.
      Given these limitations, an alternative design will be discussed in the next section.
      Sequence of spans ​
      An alternative way of referencing rollup data in the rollup settlement contract is using a sequence of spans.
      A sequence of spans is a data pointer that allows pointing to the rollup data inside a Celestia square using its location inside the square. It can be defined using the following information:
      • height: The height of the Celestia block containing the rollup data.
      • startIndex: The index of the first share containing the rollup data.
      • dataLen: The number of shares containing the rollup data.
      The startIndex and the dataLen can be queried from Celestia after the corresponding transaction gets included in a block and committed to the chain. An example of how to query them can be found in the verify command. The TxShareRange returns the start and end share of the data referenced by a transaction hash.
      NOTE
      If the rollup data is submitted in multiple blocks, the above sequence of spans can be generalized to include multiple blocks. For simplicity, we will stick with the data only submitted to a single Celestia block.
      Sequence of spans: Proof details ​
      Using sequence of spans is different from using the blob share commitment because we're referencing a location in the square, and not actual data commitment. So, the proof types and their generation are different.
      Sequence of spans: Proving unavailable data ​
      By construction, if the sequence of spans refers to a certain location in the square, that location is the data. This location can be in the reserved namespaces, the parity bytes, etc. What matters is that it's part of the square. So to prove that the sequence of spans is invalid, i.e., refers to data that is not available on Celestia, it is necessary and sufficient to show that the sequence of spans doesn't belong to the Celestia block, i.e., the span is out of bounds.
      We could create this proof via generating a binary Merkle proof of any row/column to the Celestia data root. This proof will provide the total which is the number of rows/columns in the extended data square. This can be used to calculate the square size. The computeSquareSizeFromRowProof method in the DAVerifier library allows calculating the square size from a row proof or a share proof.
      Then, we will use that information to check if the provided share index, in the header, is out of the square size bounds. In order words, we will check if the startIndex and the startIndex + dataLen are included in the range [0, 4*square_size].
      NOTE
      The square size is the number of rows of the original square.
      For the data root, we will use a binary Merkle proof to prove its inclusion in a data root tuple root that was committed to by the Blobstream smart contract. More on this in the data root inclusion proofs section.
      Sequence of spans: Proving inclusion of some data ​
      The difference between using a blob share commitment and a sequence of spans is that when using a blob share commitment, an extra merkle proof is needed to prove inclusion of the share to the blob share commitment. However, in the case of a sequence of spans, only the usual inclusion proof of a share to the data root tuple root is needed. The inclusion of the share to the sequence of spans is gotten using the same proof.
      In fact, proving that a share is part of the sequence of spans, i.e., part of the rollup data is done as follows:
      1. Prove that the data root tuple is committed to by the Blobstream smart contract:
        To prove the data root is committed to by the Blobstream smart contract, we will need to provide a Merkle proof of the data root tuple to a data root tuple root. This can be created using the data_root_inclusion_proof query. More on this can be found in the data root inclusion proofs documentation.
      2. Verify inclusion proof of the data to Celestia data root:
        To prove that the data is part of the data root, we will need to provide two proofs: a namespace Merkle proof of the data to a row root. This could be done via proving the shares that contain the data to the row root using a namespace Merkle proof. And, a binary Merkle proof of the row root to the data root.
        These proofs can be generated using the ProveShares query.
        More details on these proofs can be found in the transaction inclusion proof documentation.
      3. Prove that the data is in the sequence spans:
        To prove that the data is part of the rollup sequence of spans, we take the authenticated share proofs in step (2) and use the shares begin/end key to define the shares' positions in the row.
        Then, we use the row proof to get the row index in the extended Celestia square and get the index of the share in row major order:
        solidity
        uint256 shareIndexInRow = shareProof.shareProofs[0].beginKey;
+import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Introduction to Blobstream rollups","description":"Learn how to build rollups that use Blobstream.","frontmatter":{"description":"Learn how to build rollups that use Blobstream.","prev":{"text":"Ethereum fallback mechanism","link":"/developers/ethereum-fallback"},"next":{"text":"Submitting data blobs to Celestia","link":"/developers/submit-data"},"head":[["meta",{"name":"og:title","content":"Introduction to Blobstream rollups | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-rollups.md","filePath":"developers/blobstream-rollups.md","lastUpdated":1725992025000}'),s={name:"developers/blobstream-rollups.md"},r=a(`
        Introduction to Blobstream rollups ​
        Blobstream is the first data availability solution for EVM chains that securely scales with the number of users. It allows rollups to post their data on Celestia while proving their availability in the rollup settlement contract.
        This document will outline a few ways to build optimistic or zk-rollups that post their data to Celestia and use Blobstream to prove that data's availability.
        Concepts ​
        This section will go over two constructs that can be used in building Blobstream rollups. Each with its pros and cons and the rollup developer can choose which one suits their needs better.
        Note: Only the sequence of spans method can be used currently to build Blobstream rollups. The blob share commitment way still requires some tooling that will be built in the upcoming months.
        Blob share commitment ​
        The blob share commitment is a commitment over the data contained in the MsgPayForBlobs transaction. This commitment allows proving that the corresponding data exists on Celestia efficiently.
        Blob share commitment: Proof details ​
        To prove that the data corresponding to a blob share commitment was posted to Celestia using Blobstream, the following proofs need to be verified:
        1. share inclusion proof to the blob share commitment: meaning creating two merkle proofs: 
          1. share merkle proof up to the subtree root corresponding to that share
          2. subtree root merkle proof to the blob share commitment
        2. blob share commitment inclusion proof to the data root tuple root: meaning four merkle proofs: 
          1. subtree roots merkle proofs to the blob share commitment: to make sure the subtree roots are valid
          2. subtree roots merkle proofs up to the row roots: to prove that the subtree roots belong to a set of rows in the Celestia block
          3. row roots proofs to the data root: to prove that those rows belong to the Celestia Block
          4. data root tuple proof to the data root tuple: to prove that the Celestia block referenced by its height and data root, was committed to by Blobstream.
        More details on the blob share commitment inclusion proof can be found in the commitment scheme docs and also the data square layout.
        If all of these proofs are valid, then you successfully managed to prove that the data corresponding to that blob share commitment has been posted to Celestia.
        NOTE
        Generating/verifying blob share commitment proofs is still not supported. It still needs tooling to generate the proofs on the node side, and verifying them on the Solidity side which will be built in the upcoming months.
        Blob share commitment: Compact proofs ​
        There is a way to have compact proofs, when using blob share commitments, unlike the ones defined above; that allow less costly inclusion proofs. These require the ability to parse the protobuf encoded PFBs.
        In fact, if the rollup project has a way to parse the protobuf encoded PFB, either in a smart contract or a zk-circuit, they will be able to create compact proofs of the rollup data.
        These proofs will work as follows:
        • Parsing the PFB and taking out the blob share commitment
        • Comparing the PFB commitment to the one saved in the rollup contract
        • Proving inclusion of the PFB to the data root tuple root. This will be a compact proof since we will only be proving two shares regardless of the size of the rollup data.
        More details on compact proofs can be found in ADR-011.
        Blob share commitment: Pros ​
        The pros of referencing rollup data using a blob share commitment:
        • Using the same commitment that exists on the PFB, without having to find another way of referencing the rollup data.
        • If the team has access to protobuf parsing, it allows for compact proof, but the parsing costs need to be investigated.
        Blob share commitment: Cons ​
        • Large/expensive proofs in the case of having no way to parse the protobuf PFB encoding.
        • In the optimistic rollups construction, defined below, this requires waiting for the Celestia block to be committed to by Blobstream before saving updating the settlement contract. This might require waiting for a few hours, depending on the batches size on each chain, to finally submit the rollup update.
        Given these limitations, an alternative design will be discussed in the next section.
        Sequence of spans ​
        An alternative way of referencing rollup data in the rollup settlement contract is using a sequence of spans.
        A sequence of spans is a data pointer that allows pointing to the rollup data inside a Celestia square using its location inside the square. It can be defined using the following information:
        • height: The height of the Celestia block containing the rollup data.
        • startIndex: The index of the first share containing the rollup data.
        • dataLen: The number of shares containing the rollup data.
        The startIndex and the dataLen can be queried from Celestia after the corresponding transaction gets included in a block and committed to the chain. An example of how to query them can be found in the verify command. The TxShareRange returns the start and end share of the data referenced by a transaction hash.
        NOTE
        If the rollup data is submitted in multiple blocks, the above sequence of spans can be generalized to include multiple blocks. For simplicity, we will stick with the data only submitted to a single Celestia block.
        Sequence of spans: Proof details ​
        Using sequence of spans is different from using the blob share commitment because we're referencing a location in the square, and not actual data commitment. So, the proof types and their generation are different.
        Sequence of spans: Proving unavailable data ​
        By construction, if the sequence of spans refers to a certain location in the square, that location is the data. This location can be in the reserved namespaces, the parity bytes, etc. What matters is that it's part of the square. So to prove that the sequence of spans is invalid, i.e., refers to data that is not available on Celestia, it is necessary and sufficient to show that the sequence of spans doesn't belong to the Celestia block, i.e., the span is out of bounds.
        We could create this proof via generating a binary Merkle proof of any row/column to the Celestia data root. This proof will provide the total which is the number of rows/columns in the extended data square. This can be used to calculate the square size. The computeSquareSizeFromRowProof method in the DAVerifier library allows calculating the square size from a row proof or a share proof.
        Then, we will use that information to check if the provided share index, in the header, is out of the square size bounds. In order words, we will check if the startIndex and the startIndex + dataLen are included in the range [0, 4*square_size].
        NOTE
        The square size is the number of rows of the original square.
        For the data root, we will use a binary Merkle proof to prove its inclusion in a data root tuple root that was committed to by the Blobstream smart contract. More on this in the data root inclusion proofs section.
        Sequence of spans: Proving inclusion of some data ​
        The difference between using a blob share commitment and a sequence of spans is that when using a blob share commitment, an extra merkle proof is needed to prove inclusion of the share to the blob share commitment. However, in the case of a sequence of spans, only the usual inclusion proof of a share to the data root tuple root is needed. The inclusion of the share to the sequence of spans is gotten using the same proof.
        In fact, proving that a share is part of the sequence of spans, i.e., part of the rollup data is done as follows:
        1. Prove that the data root tuple is committed to by the Blobstream smart contract:
          To prove the data root is committed to by the Blobstream smart contract, we will need to provide a Merkle proof of the data root tuple to a data root tuple root. This can be created using the data_root_inclusion_proof query. More on this can be found in the data root inclusion proofs documentation.
        2. Verify inclusion proof of the data to Celestia data root:
          To prove that the data is part of the data root, we will need to provide two proofs: a namespace Merkle proof of the data to a row root. This could be done via proving the shares that contain the data to the row root using a namespace Merkle proof. And, a binary Merkle proof of the row root to the data root.
          These proofs can be generated using the ProveShares query.
          More details on these proofs can be found in the transaction inclusion proof documentation.
        3. Prove that the data is in the sequence spans:
          To prove that the data is part of the rollup sequence of spans, we take the authenticated share proofs in step (2) and use the shares begin/end key to define the shares' positions in the row.
          Then, we use the row proof to get the row index in the extended Celestia square and get the index of the share in row major order:
          solidity
          uint256 shareIndexInRow = shareProof.shareProofs[0].beginKey;
 uint256 shareIndexInRowMajorOrder = shareIndexInRow + shareProof.rowProofs[0].numLeaves * shareProof.rowProofs[0].key;
          uint256 shareIndexInRow = shareProof.shareProofs[0].beginKey;
 uint256 shareIndexInRowMajorOrder = shareIndexInRow + shareProof.rowProofs[0].numLeaves * shareProof.rowProofs[0].key;
        Finally, we can compare the computed index with the sequence of spans, and be sure that the data/shares is part of the rollup data.
        Sequence of spans: Pros ​
        • Using a sequence of spans instead of the blob share commitment allows for simpler proofs
        Sequence of spans: Cons ​
        None
        Optimistic rollups ​
        One type of rollups that can be built with Blobstream is optimistic rollups. An optimistic rollup is a rollup that commits optimistically to a set of blocks, and allows the other parties to verify that the blocks are valid, and if they're not, they can create fraud proofs to signal that.
        Celestia allows optimistic rollups to post their data on its DA layer, and to prove that the data is available using Blobstream.
        To build an optimistic rollup that uses Celestia as a DA layer, the following constructions can be inspired by.
        Optimistic rollups that use a sequence of spans ​
        Optimistic rollups can post their data in Celestia, then in the rollup settlement contract, they can reference optimistically that data using a sequence of spans. Then, rollup full nodes can verify if that data is valid. If not, they can trigger a fraud proof.
        When using a sequence of spans, triggering the data availability fraud proofs, which are different from the state transitions fraud proofs (left for the rollup to define), goes back to the following cases:
        Optimistic rollups that use a sequence of spans: Pros ​
        • Not needing to verify anything at the moment of submitting the commitments to the rollup settlement contracts
        • The fraud proofs are simple and can be reduced to a single share: if, for example, a single transaction in the rollup data that was posted to Celestia is faulty, only the shares containing that transaction, which can be as minimal as a single share, need to be proven on chain and verified.
        Optimistic rollups that use a sequence of spans: Cons ​
        None
        Optimistic rollups that use a sequence of spans: Example ​
        An example optimistic rollup that uses sequence of spans to reference its data can be found in the RollupInclusionProofs. It portrays the different possible data availability proofs, constructs them and shows how to verify them.
        Also, more details on querying these kinds of proofs can be found in the proof queries documentation.
        Optimistic rollups that use blob share commitments ​
        Another way to build a rollup is to replace the sequence of spans with a height and a blob share commitment. Then, users/rollup full nodes will be able to query that data and validate it. If the rollup data is not valid, they can create a fraud proof.
        The first difference between the sequence of spans construction and the share commitment construction is having to verify that the provided blob share commitment is part of the Celestia block, referenced by its height in the moment of submitting the rollup commitments to the settlement contract. This is necessary to make sure that the commitment is part of Celestia. Otherwise, rollup sequencers can commit to random blob share commitments and there won't be a way to prove they're invalid.
        The second difference is the proof types. In the case of a fraud proof, the proofs outlined in the proofs details of blob share commitment section would need to be verified to be sure that the share containing the invalid state transition is part of the rollup data. Alternatively, the rollup settlement contract would need to have a library to parse protobuf encoded PFBs, as explained in the compact proofs of blob share commitment section, to have less expensive proofs. The cost of parsing the protobuf is not included in this analysis and needs to be investigated separately.
        Optimistic rollups that use blob share commitments: Pros ​
        • Using the same blob share commitment as the one saved in Celestia which gives access to existing tooling
        Optimistic rollups that use blob share commitments: Cons ​
        • The proofs are expensive in the base case. And if the settlement contract is able to parse the PFBs, thorough investigations of the cost of that would need to be done.
        Zk-rollups ​
        Zk-rollups, aka validity rollups, can also use Celestia as a DA and Blobstream to verify that the data was posted. However, the submission process is different from the above constructions, since there are no fraud proofs, and everything should be verified when submitting the commitment to the settlement contract.
        Similar to the optimistic case, the rollup settlement contract can reference the rollup data using either the sequence of spans approach or the blob share commitments. We will discuss both in this section.
        Zk-rollups that use sequence of spans ​
        When submitting the commitments to the rollup settlement contract, this latter will need to verify the following:
        1. Zk-proof of the state transitions, which is left for the rollup to define.
        2. Verify that the sequence of spans is valid, i.e., is part of the Celestia block referenced by its height, as described in the proof details section.
        3. Zk-proof of the rollup data to the data root. The verification process of this should accept a commitment as input so that the settlement contract makes sure it's the correct value that's being saved. The commitment can be the data root and the sequence of spans. And, when the rollup data is proven inside the circuit to the data root, the used data root is asserted to be the input one. Similarly, the data's location is asserted to be the same as the input sequence of spans. These arguments are the ones used in the sequence of spans verification in (2).
        Once these are valid, the settlement contract can be sure that the rollup data was posted to Celestia, and the sequence of spans references it correctly.
        Zk-rollups that use sequence of spans: Pros ​
        • The inclusion proof inside the zk-circuit is a simple proof that uses traditional merkle tree. In the case of using blob share commitment, as will be explained below, additional libraries that can be expensive to prove are required.
        Zk-rollups that use sequence of spans: Cons ​
        None
        Zk-rollups that use blob share commitments ​
        To use blob share commitments to reference rollup data in the zk-rollup settlement contract, the zk-circuits need to be able to deserialize protobuf encoded messages. Alternatively, more involved merkle proofs will need to be verified.
        Protobuf deserialization inside a zk-circuit ​
        One way of using the blob share commitment to reference the rollup data in zk-rollups is via using a protobuf deserialization library inside the zk-circuit. And the verification would proceed as follows:
        1. Zk-proof of the state transitions, which is left to the rollup team to define.
        2. Verify that the blob share commitment is valid using the proofs laid out in the proof details of blob share commitment section.
        3. The zk-proof verifier would take as argument the data root and the blob share commitment. Then, inside the circuit, the protobuf encoded PFB transaction will be deserialized and then verify the following:
        • The deserialized blob share commitment is the same as the one provided as input
        • The circuit will prove the inclusion of the PFB to the data root, then assert that the data root is the same as the one provided as input.
        If the above conditions are valid, the rollup settlement contract can be sure that the rollup data was posted to Celestia and is correctly referenced.
        Zk-rollups that use blob share commitments: Pros ​
        None
        Zk-rollups that use blob share commitments: Cons ​
        • This approach requires having access to a protobuf decoder inside a zk-circuit which is not straightforward to have. Also, the relative costs will need to be investigated.
        Heavy merkle proofs usage ​
        Similar to Protobuf deserialization inside a zk-circuit, the zk-circuit will proceed to the verification of the availability of the data. The difference is that instead of parsing the encoded protobuf, the proofs defined under the blob share commitment proof details section will need to be verified inside the zk-circuit as follows:
        1. Zk-proof of the state transitions, which is left to the rollup team to define.
        2. Verify that the blob share commitment is valid using the proofs laid out in the blob share commitment proof details section.
        3. The zk-proof verifier would take as argument the data root and the blob share commitment. Then, inside the circuit:
        • It will verify that the input blob share commitment corresponds to the rollup data.
        • Verify that the input data root commits to that blob share commitment. Check the blob share commitment proof details for more details
        Once these proofs are valid, the rollup settlement contract can be sure that the rollup data was posted to Celestia and is correctly referenced.
        heavy merkle proofs usage: Pros ​
        None
        heavy merkle proofs usage: Cons ​
        • More heavy usage of merkle proofs inside and outside the zk-circuit.
        Conclusion ​
        Given the above details, using the sequence of spans is the better solution in the general case as explained in the optimistic rollups that uses a sequence of spans and zk-rollups that use sequence of spans sections. The proof sizes are small and allow for greater flexibility. However, if the rollup team has different requirements, then the other designs can be explored.
        FAQ ​
        Should I use the Celestia transaction hash to reference the rollup data? ​
        This is asked a lot since it's the most intuitive way of referencing data. However, in Celestia, referencing the data using the transaction hash is not recommended.
        A transaction proof in Celestia goes back to providing an inclusion proof of the shares containing the transaction. This means if the transaction hash is used to reference data in a Celestia block, the rollup verification mechanism should do the following:
        • Verify an inclusion proof of the shares comprising the transaction up to the data root tuple root
        • Decode those shares and parse the transaction, then hash its components to generate the transaction hash
        • Verify that the generated transaction hash matches the one used to reference the data
        At this level, the transaction hash is authenticated and the verification contract has the shares of the transaction. Then, the verification contract needs to take the share commitment from the parsed transaction and follow the steps outlined in the blob share commitment section.
        As observed, using the transaction hash is expensive and doesn't yield any advantages over using the blob share commitment, which in turn is more expensive than using the sequence of spans.
        So, unless there are more reasons to use the transaction hash to reference the rollup data, the sequence of spans approach remains better.
        `,113),i=[r];function n(l,h,c,p,u,d){return t(),o("div",null,i)}const b=e(s,[["render",n]]);export{f as __pageData,b as default};
diff --git a/pr-1699/assets/developers_blobstream-rollups.md.580268e1.lean.js b/pr-1699/assets/developers_blobstream-rollups.md.9c8cb137.lean.js
similarity index 92%
rename from pr-1699/assets/developers_blobstream-rollups.md.580268e1.lean.js
rename to pr-1699/assets/developers_blobstream-rollups.md.9c8cb137.lean.js
index c2b61d93a7..f7f0593f23 100644
--- a/pr-1699/assets/developers_blobstream-rollups.md.580268e1.lean.js
+++ b/pr-1699/assets/developers_blobstream-rollups.md.9c8cb137.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Introduction to Blobstream rollups","description":"Learn how to build rollups that use Blobstream.","frontmatter":{"description":"Learn how to build rollups that use Blobstream.","prev":{"text":"Ethereum fallback mechanism","link":"/developers/ethereum-fallback"},"next":{"text":"Submitting data blobs to Celestia","link":"/developers/submit-data"},"head":[["meta",{"name":"og:title","content":"Introduction to Blobstream rollups | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-rollups.md","filePath":"developers/blobstream-rollups.md","lastUpdated":1725971357000}'),s={name:"developers/blobstream-rollups.md"},r=a("",113),i=[r];function n(l,h,c,p,u,d){return t(),o("div",null,i)}const b=e(s,[["render",n]]);export{f as __pageData,b as default};
+import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Introduction to Blobstream rollups","description":"Learn how to build rollups that use Blobstream.","frontmatter":{"description":"Learn how to build rollups that use Blobstream.","prev":{"text":"Ethereum fallback mechanism","link":"/developers/ethereum-fallback"},"next":{"text":"Submitting data blobs to Celestia","link":"/developers/submit-data"},"head":[["meta",{"name":"og:title","content":"Introduction to Blobstream rollups | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-rollups.md","filePath":"developers/blobstream-rollups.md","lastUpdated":1725992025000}'),s={name:"developers/blobstream-rollups.md"},r=a("",113),i=[r];function n(l,h,c,p,u,d){return t(),o("div",null,i)}const b=e(s,[["render",n]]);export{f as __pageData,b as default};
diff --git a/pr-1699/assets/developers_blobstream-x-deploy.md.e0b78833.js b/pr-1699/assets/developers_blobstream-x-deploy.md.6ed5e09e.js
similarity index 99%
rename from pr-1699/assets/developers_blobstream-x-deploy.md.e0b78833.js
rename to pr-1699/assets/developers_blobstream-x-deploy.md.6ed5e09e.js
index b5f8450a95..69c0b2979a 100644
--- a/pr-1699/assets/developers_blobstream-x-deploy.md.e0b78833.js
+++ b/pr-1699/assets/developers_blobstream-x-deploy.md.6ed5e09e.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"New Blobstream X deployments","description":"","frontmatter":{"next":{"text":"Celestia-node key","link":"/developers/celestia-node-key"},"head":[["meta",{"name":"og:title","content":"New Blobstream X deployments | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-x-deploy.md","filePath":"developers/blobstream-x-deploy.md","lastUpdated":1725971357000}'),o={name:"developers/blobstream-x-deploy.md"},l=e(`
        New Blobstream X deployments ​
        This document will go over the instructions to deploy BlobstreamX to a new chain.
        Deploying the contracts ​
        To deploy a Blobstream X to a new chain, where a Gateway contract does not exist yet, the following steps need to be followed.
        If any of the components already exist in the target chain, feel free to skip the corresponding step.
        Deploy a new SuccinctGateway ​
        The SuccinctGateway is a contract that acts as a registry for onchain circuit verifiers and manages their access control. It is the entrypoint for proof verification and does the following:
        1. Receive a PLONK proof from the prover
        2. Fetch the address of the target function verifier
        3. Verify if the prover is whitelisted, if whitelisting is enabled
        4. Forward the proof to the function verifier to be verified
        5. If the proof is valid, it calls back the BlobstreamX contract to update its state
        The BlobstreamX requires the update to be provided through the SuccinctGateway. Otherwise, the contract can't be updated.
        To deploy a SuccinctGateway contract, you need to have foundry installed. If not, refer to foundry documentation.
        Then, clone the succinctx repo:
        shell
        git clone https://github.com/succinctlabs/succinctx
+import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"New Blobstream X deployments","description":"","frontmatter":{"next":{"text":"Celestia-node key","link":"/developers/celestia-node-key"},"head":[["meta",{"name":"og:title","content":"New Blobstream X deployments | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-x-deploy.md","filePath":"developers/blobstream-x-deploy.md","lastUpdated":1725992025000}'),o={name:"developers/blobstream-x-deploy.md"},l=e(`
        New Blobstream X deployments ​
        This document will go over the instructions to deploy BlobstreamX to a new chain.
        Deploying the contracts ​
        To deploy a Blobstream X to a new chain, where a Gateway contract does not exist yet, the following steps need to be followed.
        If any of the components already exist in the target chain, feel free to skip the corresponding step.
        Deploy a new SuccinctGateway ​
        The SuccinctGateway is a contract that acts as a registry for onchain circuit verifiers and manages their access control. It is the entrypoint for proof verification and does the following:
        1. Receive a PLONK proof from the prover
        2. Fetch the address of the target function verifier
        3. Verify if the prover is whitelisted, if whitelisting is enabled
        4. Forward the proof to the function verifier to be verified
        5. If the proof is valid, it calls back the BlobstreamX contract to update its state
        The BlobstreamX requires the update to be provided through the SuccinctGateway. Otherwise, the contract can't be updated.
        To deploy a SuccinctGateway contract, you need to have foundry installed. If not, refer to foundry documentation.
        Then, clone the succinctx repo:
        shell
        git clone https://github.com/succinctlabs/succinctx
 cd succinctx
        git clone https://github.com/succinctlabs/succinctx
 cd succinctx
        Next, build the contracts:
        shell
        cd contracts
 forge build
        cd contracts
diff --git a/pr-1699/assets/developers_blobstream-x-deploy.md.e0b78833.lean.js b/pr-1699/assets/developers_blobstream-x-deploy.md.6ed5e09e.lean.js
similarity index 90%
rename from pr-1699/assets/developers_blobstream-x-deploy.md.e0b78833.lean.js
rename to pr-1699/assets/developers_blobstream-x-deploy.md.6ed5e09e.lean.js
index 784d4faeca..98c031944b 100644
--- a/pr-1699/assets/developers_blobstream-x-deploy.md.e0b78833.lean.js
+++ b/pr-1699/assets/developers_blobstream-x-deploy.md.6ed5e09e.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"New Blobstream X deployments","description":"","frontmatter":{"next":{"text":"Celestia-node key","link":"/developers/celestia-node-key"},"head":[["meta",{"name":"og:title","content":"New Blobstream X deployments | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-x-deploy.md","filePath":"developers/blobstream-x-deploy.md","lastUpdated":1725971357000}'),o={name:"developers/blobstream-x-deploy.md"},l=e("",112),t=[l];function p(c,r,i,y,d,E){return a(),n("div",null,t)}const F=s(o,[["render",p]]);export{u as __pageData,F as default};
+import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"New Blobstream X deployments","description":"","frontmatter":{"next":{"text":"Celestia-node key","link":"/developers/celestia-node-key"},"head":[["meta",{"name":"og:title","content":"New Blobstream X deployments | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-x-deploy.md","filePath":"developers/blobstream-x-deploy.md","lastUpdated":1725992025000}'),o={name:"developers/blobstream-x-deploy.md"},l=e("",112),t=[l];function p(c,r,i,y,d,E){return a(),n("div",null,t)}const F=s(o,[["render",p]]);export{u as __pageData,F as default};
diff --git a/pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.409fcb45.js b/pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.adbc6c7c.js
similarity index 98%
rename from pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.409fcb45.js
rename to pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.adbc6c7c.js
index 3c0753e972..e79401eb40 100644
--- a/pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.409fcb45.js
+++ b/pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.adbc6c7c.js
@@ -1 +1 @@
-import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Requesting data commitment ranges","description":"","frontmatter":{"prev":{"text":"Querying the Blobstream proofs","link":"/developers/blobstream-proof-queries"},"head":[["meta",{"name":"og:title","content":"Requesting data commitment ranges | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-x-requesting-data-commitment-ranges.md","filePath":"developers/blobstream-x-requesting-data-commitment-ranges.md","lastUpdated":1725971357000}'),r={name:"developers/blobstream-x-requesting-data-commitment-ranges.md"},n=a('
        Requesting data commitment ranges ​
        By default, the Blobstream X deployments on Ethereum will be updated every 4 hours, and on Arbitrum One and Base, updating every 1 hour. If you wish for the Blobstream X contract to be updated at a different cadence, then you have several different options for how to update the smart contract.
        To request proofs to be submitted to the Blobstream X contract at a different cadence, you can do one of the following:
        NOTE: The requested proof ranges cannot include blocks that were already used in a previous batch. The ranges should start from the last proven block, aka, latest_block and they should end in a block already committed by Celestia. In other words, it's the end-inclusive range defined by [latest_block, target_block] with target_block <= Celestia tip.
        Local proving ​
        To run the Blobstream X operator with local proving, follow this guide.
        Local proving allows self-generating the proofs and submitting them to an existing BlobstreamX contract. Alternatively, if a team needs a very specific cadence that starts at very specific heights, they can deploy their own BlobstreamX contract and submit proofs to it. Deployment instructions can be found in the BlobstreamX deploy documentation.
        ::: Note Requires a large cloud machine to run in a reasonable amount of time. EC2 r6a.16xlarge, i.e., 64CPU 512GB RAM, takes ~30 minutes to generate a header range proof. :::
        Request proofs from the Succinct platform ​
        NOTE: Requesting a proof from the succinct platform requires having a Succinct API key. It can be requested using this form.
        Run the Blobstream X operator with hosted proving on the Succinct platform, by running an operator script that pings the platform with proof requests at a specified cadence.
        Follow these instructions to run the operator script.
        Here are example values for the .env file:
        1. TENDERMINT_RPC_URL from the public Celestia list.
        2. SUCCINCT_RPC_URL = https://alpha.succinct.xyz/api
        3. Request for SUCCINCT_API_KEY from the Succinct team.
        4. CHAIN_ID is the chain ID of the deployed Blobstream X contract.
        5. CONTRACT_ADDRESS: Blobstream X proxy contract address.
        6. NEXT_HEADER_FUNCTION_ID & HEADER_RANGE_FUNCTION_ID: Get the functionId's from the Blobstream X contract by using the nextHeaderFunctionId and headerRangeFunctionId respectively, which are public storage variables.
        Request proofs onchain ​
        Directly request a proof via the Blobstream X contract interface. Unlike the Blobstream X operator which handles requests off-chain, requesting on-chain requires gas, but the proof will be generated and relayed by the Succinct platform.
        1. Call requestHeaderRange(uint64 _targetBlock) with the end of the range you want a commitment for.
        2. A DataCommitmentStored(uint256, uint64, uint64, bytes32) will be emitted for the requested range when it is stored in the contract. Listen to this event to know that the proof has been generated successfully.
        ',17),s=[n];function c(i,l,d,h,p,m){return t(),o("div",null,s)}const b=e(r,[["render",c]]);export{f as __pageData,b as default};
+import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Requesting data commitment ranges","description":"","frontmatter":{"prev":{"text":"Querying the Blobstream proofs","link":"/developers/blobstream-proof-queries"},"head":[["meta",{"name":"og:title","content":"Requesting data commitment ranges | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-x-requesting-data-commitment-ranges.md","filePath":"developers/blobstream-x-requesting-data-commitment-ranges.md","lastUpdated":1725992025000}'),r={name:"developers/blobstream-x-requesting-data-commitment-ranges.md"},n=a('
        Requesting data commitment ranges ​
        By default, the Blobstream X deployments on Ethereum will be updated every 4 hours, and on Arbitrum One and Base, updating every 1 hour. If you wish for the Blobstream X contract to be updated at a different cadence, then you have several different options for how to update the smart contract.
        To request proofs to be submitted to the Blobstream X contract at a different cadence, you can do one of the following:
        NOTE: The requested proof ranges cannot include blocks that were already used in a previous batch. The ranges should start from the last proven block, aka, latest_block and they should end in a block already committed by Celestia. In other words, it's the end-inclusive range defined by [latest_block, target_block] with target_block <= Celestia tip.
        Local proving ​
        To run the Blobstream X operator with local proving, follow this guide.
        Local proving allows self-generating the proofs and submitting them to an existing BlobstreamX contract. Alternatively, if a team needs a very specific cadence that starts at very specific heights, they can deploy their own BlobstreamX contract and submit proofs to it. Deployment instructions can be found in the BlobstreamX deploy documentation.
        ::: Note Requires a large cloud machine to run in a reasonable amount of time. EC2 r6a.16xlarge, i.e., 64CPU 512GB RAM, takes ~30 minutes to generate a header range proof. :::
        Request proofs from the Succinct platform ​
        NOTE: Requesting a proof from the succinct platform requires having a Succinct API key. It can be requested using this form.
        Run the Blobstream X operator with hosted proving on the Succinct platform, by running an operator script that pings the platform with proof requests at a specified cadence.
        Follow these instructions to run the operator script.
        Here are example values for the .env file:
        1. TENDERMINT_RPC_URL from the public Celestia list.
        2. SUCCINCT_RPC_URL = https://alpha.succinct.xyz/api
        3. Request for SUCCINCT_API_KEY from the Succinct team.
        4. CHAIN_ID is the chain ID of the deployed Blobstream X contract.
        5. CONTRACT_ADDRESS: Blobstream X proxy contract address.
        6. NEXT_HEADER_FUNCTION_ID & HEADER_RANGE_FUNCTION_ID: Get the functionId's from the Blobstream X contract by using the nextHeaderFunctionId and headerRangeFunctionId respectively, which are public storage variables.
        Request proofs onchain ​
        Directly request a proof via the Blobstream X contract interface. Unlike the Blobstream X operator which handles requests off-chain, requesting on-chain requires gas, but the proof will be generated and relayed by the Succinct platform.
        1. Call requestHeaderRange(uint64 _targetBlock) with the end of the range you want a commitment for.
        2. A DataCommitmentStored(uint256, uint64, uint64, bytes32) will be emitted for the requested range when it is stored in the contract. Listen to this event to know that the proof has been generated successfully.
        ',17),s=[n];function c(i,l,d,h,p,m){return t(),o("div",null,s)}const b=e(r,[["render",c]]);export{f as __pageData,b as default};
diff --git a/pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.409fcb45.lean.js b/pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.adbc6c7c.lean.js
similarity index 92%
rename from pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.409fcb45.lean.js
rename to pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.adbc6c7c.lean.js
index b8c1abc9f5..8e39c335b9 100644
--- a/pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.409fcb45.lean.js
+++ b/pr-1699/assets/developers_blobstream-x-requesting-data-commitment-ranges.md.adbc6c7c.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Requesting data commitment ranges","description":"","frontmatter":{"prev":{"text":"Querying the Blobstream proofs","link":"/developers/blobstream-proof-queries"},"head":[["meta",{"name":"og:title","content":"Requesting data commitment ranges | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-x-requesting-data-commitment-ranges.md","filePath":"developers/blobstream-x-requesting-data-commitment-ranges.md","lastUpdated":1725971357000}'),r={name:"developers/blobstream-x-requesting-data-commitment-ranges.md"},n=a("",17),s=[n];function c(i,l,d,h,p,m){return t(),o("div",null,s)}const b=e(r,[["render",c]]);export{f as __pageData,b as default};
+import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Requesting data commitment ranges","description":"","frontmatter":{"prev":{"text":"Querying the Blobstream proofs","link":"/developers/blobstream-proof-queries"},"head":[["meta",{"name":"og:title","content":"Requesting data commitment ranges | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream-x-requesting-data-commitment-ranges.md","filePath":"developers/blobstream-x-requesting-data-commitment-ranges.md","lastUpdated":1725992025000}'),r={name:"developers/blobstream-x-requesting-data-commitment-ranges.md"},n=a("",17),s=[n];function c(i,l,d,h,p,m){return t(),o("div",null,s)}const b=e(r,[["render",c]]);export{f as __pageData,b as default};
diff --git a/pr-1699/assets/developers_blobstream.md.c9e61c23.js b/pr-1699/assets/developers_blobstream.md.4afef8bd.js
similarity index 99%
rename from pr-1699/assets/developers_blobstream.md.c9e61c23.js
rename to pr-1699/assets/developers_blobstream.md.4afef8bd.js
index afc102cbb5..29d5426668 100644
--- a/pr-1699/assets/developers_blobstream.md.c9e61c23.js
+++ b/pr-1699/assets/developers_blobstream.md.4afef8bd.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as r}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/blobstream/blobstream_logo.png",f=JSON.parse('{"title":"Blobstream: Streaming modular DA to Ethereum","description":"Learn how to integrate your L2 with Blobstream","frontmatter":{"description":"Learn how to integrate your L2 with Blobstream","head":[["meta",{"name":"og:title","content":"Blobstream: Streaming modular DA to Ethereum | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream.md","filePath":"developers/blobstream.md","lastUpdated":1725971357000}'),s={name:"developers/blobstream.md"},l=r('
        Blobstream: Streaming modular DA to Ethereum ​
        Blobstream logo
        What is Blobstream? ​
        Blobstream is the first data availability solution for Ethereum that securely scales with the number of users. Formerly known as the Quantum Gravity Bridge (QGB), Blobstream relays commitments to Celestia's data root to an onchain light client on Ethereum, for integration by developers into L2 contracts. This enables Ethereum developers to build high-throughput L2s using Celestia's optimised DA layer, the first with Data Availability Sampling (DAS). Any ecosystem can deploy a Blobstream light client onchain to allow L2s and L3s to access DA from Celestia.
        An implementation of Blobstream, by Succinct, called Blobstream X, is out and will be used in the upcoming deployments. This implementation proves the validity of Celestia block headers on a target EVM chain using zero-knowledge (ZK) proofs, which allow inheriting all the security guarantees of Celestia.
        The latest implementation of Blobstream X is SP1 Blobstream, which is written in Rust for the SP1 zkVM. SP1 Blobstream offers improved performance and efficiency while maintaining the security guarantees of the original Blobstream X.
        Please note: Blobstream remains early-stage, experimental software and users should use Blobstream at their own risk.
        Implementations of Blobstream ​
        Blobstream vs. data availability committees (DACs) ​
        Decentralization and security ​
        Blobstream is built on Celestia, which uses a CometBFT-based proof-of-stake system. Blobstream shares the same security assumptions as Celestia. In contrast, data availability committees (DACs), are typically centralized or semi-centralized, relying on a specific set of entities or individuals to vouch for data availability.
        Mechanism of verification ​
        Blobstream uses data availability attestations, which are Merkle roots of the batched L2 data, to confirm that the necessary data is present on Celestia. The L2 contract on Ethereum can check directly with Blobstream if the data is published on Celestia. Similarly, a DAC would rely on attestations or confirmations from its permissioned members.
        Flexibility and scalability ​
        Blobstream is designed to offer high-throughput data availability for Ethereum L2s, aiming to strike a balance between scalability and security. It operates independently of Ethereum's gas costs, as Celestia's resource pricing is more byte-focused rather than computation-centric. On the other hand, the scalability and flexibility of a DAC would depend on its specific design and implementation.
        In summary, both Blobstream and DACs aim to ensure offchain data availability, but Blobstream offers a more decentralized, secure, and scalable solution compared to the potential centralized nature of DACs.
        What is SP1 Blobstream? ​
        SP1 Blobstream is the latest implementation of Blobstream in Rust using the SP1 zkVM.
        SP1 Blobstream is the latest implementation of Blobstream with a ZK light client that bridges Celestia’s modular DA layer to Ethereum to allow high-throughput rollups to use Celestia’s DA while settling on Ethereum.
        Optimistic or ZK rollups that settle on Ethereum, but wish to use Celestia for DA, require a mechanism for bridging Celestia’s data root to Ethereum as part of the settlement process. This data root is used during inclusion proofs to prove that particular rollup transactions were included and made available in the Celestia network.
        Bridging Celestia’s data root to Ethereum requires running a Celestia light client as a smart contract on Ethereum, to make the latest state of the Celestia chain known on Ethereum and available to rollups. SP1 Blobstream uses the latest advances in ZK proofs to generate a succinct proof that enough Celestia validators have come to consensus (according to the CometBFT consensus protocol) on a block header, and verifies this proof in the SP1 Blobstream Ethereum smart contract to update it with the latest Celestia header.
        The SP1 Blobstream ZK proof not only verifies the consensus of Celestia validators, but it also merkelizes and hashes all the data roots in the block range from the previous update to the current update, making accessible all Celestia data roots (verifiable with a Merkle inclusion proof against the stored Merkle root) to rollups.
        If you're looking to deploy SP1 blobstream to a new chain, see new Sp1 Blobstream deployments.
        Learn more at the sp1-blobstream repo.
        NOTE
        The current Blobstream deployments all use SP1 Blobstream.
        Integrate with SP1 Blobstream ​
        The following docs go over how developers can integrate SP1 Blobstream.
        You can find the repository for SP1 Blobstream along with code for:
        The first deployments of SP1 Blobstream will be maintained on the following chains: Arbitrum One, Base and Ethereum Mainnet. Every 1 hour, the prover/relayer will post an update to the Blobstream contract that will include a new data commitment range that covers a 1-hour block range from the latestBlock in the contract. On Ethereum Mainnet, the contract will be updated every 4 hours.
        How to integrate with Blobstream ​
        Integrating your L2 with Blobstream requires two components: your onchain smart contract logic, and your offchain client logic for your rollup. The next three sections cover these topics:
        Blobstream rollups ​
        More on the different ways to build a blobstream rollup can be found in the blobstream rollups documentation.
        Deployed contracts ​
        You can interact with the SP1 Blobstream contracts today. The SP1 Blobstream Solidity smart contracts are currently deployed on the following chains:
        ContractEVM networkContract addressAttested data on CelestiaLink to Celenium
        SP1 BlobstreamEthereum Mainnet0x7Cf3876F681Dbb6EdA8f6FfC45D66B996Df08fAeMainnet BetaDeployment on Celenium
        SP1 BlobstreamArbitrum One0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794Mainnet BetaDeployment on Celenium
        SP1 BlobstreamBase0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794Mainnet BetaDeployment on Celenium
        SP1 BlobstreamSepolia0xf0c6429ebab2e7dc6e05dafb61128be21f13cb1eMocha testnetDeployment on Celenium
        SP1 BlobstreamArbitrum Sepolia0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2Mocha testnetDeployment on Celenium
        SP1 BlobstreamBase Sepolia0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2Mocha testnetDeployment on Celenium
        ',39),i=[l];function n(h,c,m,b,d,p){return t(),a("div",null,i)}const g=e(s,[["render",n]]);export{f as __pageData,g as default};
+import{_ as e,o as t,c as a,Q as r}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/blobstream/blobstream_logo.png",f=JSON.parse('{"title":"Blobstream: Streaming modular DA to Ethereum","description":"Learn how to integrate your L2 with Blobstream","frontmatter":{"description":"Learn how to integrate your L2 with Blobstream","head":[["meta",{"name":"og:title","content":"Blobstream: Streaming modular DA to Ethereum | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream.md","filePath":"developers/blobstream.md","lastUpdated":1725992025000}'),s={name:"developers/blobstream.md"},l=r('
        Blobstream: Streaming modular DA to Ethereum ​
        Blobstream logo
        What is Blobstream? ​
        Blobstream is the first data availability solution for Ethereum that securely scales with the number of users. Formerly known as the Quantum Gravity Bridge (QGB), Blobstream relays commitments to Celestia's data root to an onchain light client on Ethereum, for integration by developers into L2 contracts. This enables Ethereum developers to build high-throughput L2s using Celestia's optimised DA layer, the first with Data Availability Sampling (DAS). Any ecosystem can deploy a Blobstream light client onchain to allow L2s and L3s to access DA from Celestia.
        An implementation of Blobstream, by Succinct, called Blobstream X, is out and will be used in the upcoming deployments. This implementation proves the validity of Celestia block headers on a target EVM chain using zero-knowledge (ZK) proofs, which allow inheriting all the security guarantees of Celestia.
        The latest implementation of Blobstream X is SP1 Blobstream, which is written in Rust for the SP1 zkVM. SP1 Blobstream offers improved performance and efficiency while maintaining the security guarantees of the original Blobstream X.
        Please note: Blobstream remains early-stage, experimental software and users should use Blobstream at their own risk.
        Implementations of Blobstream ​
        Blobstream vs. data availability committees (DACs) ​
        Decentralization and security ​
        Blobstream is built on Celestia, which uses a CometBFT-based proof-of-stake system. Blobstream shares the same security assumptions as Celestia. In contrast, data availability committees (DACs), are typically centralized or semi-centralized, relying on a specific set of entities or individuals to vouch for data availability.
        Mechanism of verification ​
        Blobstream uses data availability attestations, which are Merkle roots of the batched L2 data, to confirm that the necessary data is present on Celestia. The L2 contract on Ethereum can check directly with Blobstream if the data is published on Celestia. Similarly, a DAC would rely on attestations or confirmations from its permissioned members.
        Flexibility and scalability ​
        Blobstream is designed to offer high-throughput data availability for Ethereum L2s, aiming to strike a balance between scalability and security. It operates independently of Ethereum's gas costs, as Celestia's resource pricing is more byte-focused rather than computation-centric. On the other hand, the scalability and flexibility of a DAC would depend on its specific design and implementation.
        In summary, both Blobstream and DACs aim to ensure offchain data availability, but Blobstream offers a more decentralized, secure, and scalable solution compared to the potential centralized nature of DACs.
        What is SP1 Blobstream? ​
        SP1 Blobstream is the latest implementation of Blobstream in Rust using the SP1 zkVM.
        SP1 Blobstream is the latest implementation of Blobstream with a ZK light client that bridges Celestia’s modular DA layer to Ethereum to allow high-throughput rollups to use Celestia’s DA while settling on Ethereum.
        Optimistic or ZK rollups that settle on Ethereum, but wish to use Celestia for DA, require a mechanism for bridging Celestia’s data root to Ethereum as part of the settlement process. This data root is used during inclusion proofs to prove that particular rollup transactions were included and made available in the Celestia network.
        Bridging Celestia’s data root to Ethereum requires running a Celestia light client as a smart contract on Ethereum, to make the latest state of the Celestia chain known on Ethereum and available to rollups. SP1 Blobstream uses the latest advances in ZK proofs to generate a succinct proof that enough Celestia validators have come to consensus (according to the CometBFT consensus protocol) on a block header, and verifies this proof in the SP1 Blobstream Ethereum smart contract to update it with the latest Celestia header.
        The SP1 Blobstream ZK proof not only verifies the consensus of Celestia validators, but it also merkelizes and hashes all the data roots in the block range from the previous update to the current update, making accessible all Celestia data roots (verifiable with a Merkle inclusion proof against the stored Merkle root) to rollups.
        If you're looking to deploy SP1 blobstream to a new chain, see new Sp1 Blobstream deployments.
        Learn more at the sp1-blobstream repo.
        NOTE
        The current Blobstream deployments all use SP1 Blobstream.
        Integrate with SP1 Blobstream ​
        The following docs go over how developers can integrate SP1 Blobstream.
        You can find the repository for SP1 Blobstream along with code for:
        The first deployments of SP1 Blobstream will be maintained on the following chains: Arbitrum One, Base and Ethereum Mainnet. Every 1 hour, the prover/relayer will post an update to the Blobstream contract that will include a new data commitment range that covers a 1-hour block range from the latestBlock in the contract. On Ethereum Mainnet, the contract will be updated every 4 hours.
        How to integrate with Blobstream ​
        Integrating your L2 with Blobstream requires two components: your onchain smart contract logic, and your offchain client logic for your rollup. The next three sections cover these topics:
        Blobstream rollups ​
        More on the different ways to build a blobstream rollup can be found in the blobstream rollups documentation.
        Deployed contracts ​
        You can interact with the SP1 Blobstream contracts today. The SP1 Blobstream Solidity smart contracts are currently deployed on the following chains:
        ContractEVM networkContract addressAttested data on CelestiaLink to Celenium
        SP1 BlobstreamEthereum Mainnet0x7Cf3876F681Dbb6EdA8f6FfC45D66B996Df08fAeMainnet BetaDeployment on Celenium
        SP1 BlobstreamArbitrum One0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794Mainnet BetaDeployment on Celenium
        SP1 BlobstreamBase0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794Mainnet BetaDeployment on Celenium
        SP1 BlobstreamSepolia0xf0c6429ebab2e7dc6e05dafb61128be21f13cb1eMocha testnetDeployment on Celenium
        SP1 BlobstreamArbitrum Sepolia0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2Mocha testnetDeployment on Celenium
        SP1 BlobstreamBase Sepolia0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2Mocha testnetDeployment on Celenium
        ',39),i=[l];function n(h,c,m,b,d,p){return t(),a("div",null,i)}const g=e(s,[["render",n]]);export{f as __pageData,g as default};
diff --git a/pr-1699/assets/developers_blobstream.md.c9e61c23.lean.js b/pr-1699/assets/developers_blobstream.md.4afef8bd.lean.js
similarity index 91%
rename from pr-1699/assets/developers_blobstream.md.c9e61c23.lean.js
rename to pr-1699/assets/developers_blobstream.md.4afef8bd.lean.js
index 1e3f4eaaa9..f14e16c015 100644
--- a/pr-1699/assets/developers_blobstream.md.c9e61c23.lean.js
+++ b/pr-1699/assets/developers_blobstream.md.4afef8bd.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as r}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/blobstream/blobstream_logo.png",f=JSON.parse('{"title":"Blobstream: Streaming modular DA to Ethereum","description":"Learn how to integrate your L2 with Blobstream","frontmatter":{"description":"Learn how to integrate your L2 with Blobstream","head":[["meta",{"name":"og:title","content":"Blobstream: Streaming modular DA to Ethereum | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream.md","filePath":"developers/blobstream.md","lastUpdated":1725971357000}'),s={name:"developers/blobstream.md"},l=r("",39),i=[l];function n(h,c,m,b,d,p){return t(),a("div",null,i)}const g=e(s,[["render",n]]);export{f as __pageData,g as default};
+import{_ as e,o as t,c as a,Q as r}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/blobstream/blobstream_logo.png",f=JSON.parse('{"title":"Blobstream: Streaming modular DA to Ethereum","description":"Learn how to integrate your L2 with Blobstream","frontmatter":{"description":"Learn how to integrate your L2 with Blobstream","head":[["meta",{"name":"og:title","content":"Blobstream: Streaming modular DA to Ethereum | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstream.md","filePath":"developers/blobstream.md","lastUpdated":1725992025000}'),s={name:"developers/blobstream.md"},l=r("",39),i=[l];function n(h,c,m,b,d,p){return t(),a("div",null,i)}const g=e(s,[["render",n]]);export{f as __pageData,g as default};
diff --git a/pr-1699/assets/developers_blobstreamx.md.67c7a6c7.js b/pr-1699/assets/developers_blobstreamx.md.7838cfd1.js
similarity index 98%
rename from pr-1699/assets/developers_blobstreamx.md.67c7a6c7.js
rename to pr-1699/assets/developers_blobstreamx.md.7838cfd1.js
index fcfba8d630..a3826dd45c 100644
--- a/pr-1699/assets/developers_blobstreamx.md.67c7a6c7.js
+++ b/pr-1699/assets/developers_blobstreamx.md.7838cfd1.js
@@ -1 +1 @@
-import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/blobstream/Celestia_Blobstream_X1b.png",s="/docs-preview/pr-1699/img/blobstream/Celestia_Blobstream_X2b.png",g=JSON.parse('{"title":"BlobstreamX: the previous zk implementation of Blobstream","description":"What is BlobstreamX","frontmatter":{"description":"What is BlobstreamX","head":[["meta",{"name":"og:title","content":"BlobstreamX: the previous zk implementation of Blobstream | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstreamx.md","filePath":"developers/blobstreamx.md","lastUpdated":1725971357000}'),c={name:"developers/blobstreamx.md"},l=a('
        BlobstreamX: the previous zk implementation of Blobstream ​
        blobstream x draft diagram
        What is Blobstream X? ​
        Blobstream X is the previous implementation of Blobstream. It uses plonky2x to create circuits that verify the Celestia consensus and generate the corresponding proofs.
        Blobstream X is built and deployed with Succinct's protocol.
        NOTE
        The Blobstream deployments below don't use the BlobstreamX circuits.
        You can find the repository for Blobstream X along with code for:
        NOTE
        Custom ranges can be requested using the BlobstreamX contract to create proofs for specific Celestia block batches. These ranges can be constructed as [latestBlock, customTargetBlock), with latestBlock as the latest block height that was committed to by the BlobstreamX contract, and latestBlock > customTargetBlock, and customTargetBlock - latestBlock <= DATA_COMMITMENT_MAX.
        Block ranges that are before the contract's latestBlock can't be proven a second time in different batches.
        More information can be found in the requestHeaderRange(...) method.
        How Blobstream X works ​
        As shown in the diagram below, the entrypoint for updates to the Blobstream X contract is through the SuccinctGateway smart contract, which is a simple entrypoint contract that verifies proofs (against a deployed onchain verifier for the Blobstream X circuit) and then calls the BlobstreamX.sol contract to update it. Find more information about the SuccinctGateway.
        blobstream x overview diagram draft
        NOTE
        If the Blobstream X contract is not deployed on a desired chain, it needs to be deployed before it can be used by your rollup. See the deployment documentation for more details.
        Deploy Blobstream X ​
        It is possible to deploy and maintain a Blobstream x instance and have the same security guarantees.
        First, you will need to create a multisig that governs the Blobstream X contract and also the function identifiers. The function identifiers can be registered in the Succinct gateway.
        Then, check the deployment documentation for how to deploy the contract.
        Then, you will need to run a relayer, which will generate the proofs and relay them to your deployed Blobstream X contract. Check the local proving documentation for more information.
        ',18),n=[l];function i(b,m,d,h,p,u){return t(),o("div",null,n)}const B=e(c,[["render",i]]);export{g as __pageData,B as default};
+import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/blobstream/Celestia_Blobstream_X1b.png",s="/docs-preview/pr-1699/img/blobstream/Celestia_Blobstream_X2b.png",g=JSON.parse('{"title":"BlobstreamX: the previous zk implementation of Blobstream","description":"What is BlobstreamX","frontmatter":{"description":"What is BlobstreamX","head":[["meta",{"name":"og:title","content":"BlobstreamX: the previous zk implementation of Blobstream | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstreamx.md","filePath":"developers/blobstreamx.md","lastUpdated":1725992025000}'),c={name:"developers/blobstreamx.md"},l=a('
        BlobstreamX: the previous zk implementation of Blobstream ​
        blobstream x draft diagram
        What is Blobstream X? ​
        Blobstream X is the previous implementation of Blobstream. It uses plonky2x to create circuits that verify the Celestia consensus and generate the corresponding proofs.
        Blobstream X is built and deployed with Succinct's protocol.
        NOTE
        The Blobstream deployments below don't use the BlobstreamX circuits.
        You can find the repository for Blobstream X along with code for:
        NOTE
        Custom ranges can be requested using the BlobstreamX contract to create proofs for specific Celestia block batches. These ranges can be constructed as [latestBlock, customTargetBlock), with latestBlock as the latest block height that was committed to by the BlobstreamX contract, and latestBlock > customTargetBlock, and customTargetBlock - latestBlock <= DATA_COMMITMENT_MAX.
        Block ranges that are before the contract's latestBlock can't be proven a second time in different batches.
        More information can be found in the requestHeaderRange(...) method.
        How Blobstream X works ​
        As shown in the diagram below, the entrypoint for updates to the Blobstream X contract is through the SuccinctGateway smart contract, which is a simple entrypoint contract that verifies proofs (against a deployed onchain verifier for the Blobstream X circuit) and then calls the BlobstreamX.sol contract to update it. Find more information about the SuccinctGateway.
        blobstream x overview diagram draft
        NOTE
        If the Blobstream X contract is not deployed on a desired chain, it needs to be deployed before it can be used by your rollup. See the deployment documentation for more details.
        Deploy Blobstream X ​
        It is possible to deploy and maintain a Blobstream x instance and have the same security guarantees.
        First, you will need to create a multisig that governs the Blobstream X contract and also the function identifiers. The function identifiers can be registered in the Succinct gateway.
        Then, check the deployment documentation for how to deploy the contract.
        Then, you will need to run a relayer, which will generate the proofs and relay them to your deployed Blobstream X contract. Check the local proving documentation for more information.
        ',18),n=[l];function i(b,m,d,h,p,u){return t(),o("div",null,n)}const B=e(c,[["render",i]]);export{g as __pageData,B as default};
diff --git a/pr-1699/assets/developers_blobstreamx.md.67c7a6c7.lean.js b/pr-1699/assets/developers_blobstreamx.md.7838cfd1.lean.js
similarity index 92%
rename from pr-1699/assets/developers_blobstreamx.md.67c7a6c7.lean.js
rename to pr-1699/assets/developers_blobstreamx.md.7838cfd1.lean.js
index e9dbc5c8f4..800a161f69 100644
--- a/pr-1699/assets/developers_blobstreamx.md.67c7a6c7.lean.js
+++ b/pr-1699/assets/developers_blobstreamx.md.7838cfd1.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/blobstream/Celestia_Blobstream_X1b.png",s="/docs-preview/pr-1699/img/blobstream/Celestia_Blobstream_X2b.png",g=JSON.parse('{"title":"BlobstreamX: the previous zk implementation of Blobstream","description":"What is BlobstreamX","frontmatter":{"description":"What is BlobstreamX","head":[["meta",{"name":"og:title","content":"BlobstreamX: the previous zk implementation of Blobstream | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstreamx.md","filePath":"developers/blobstreamx.md","lastUpdated":1725971357000}'),c={name:"developers/blobstreamx.md"},l=a("",18),n=[l];function i(b,m,d,h,p,u){return t(),o("div",null,n)}const B=e(c,[["render",i]]);export{g as __pageData,B as default};
+import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/blobstream/Celestia_Blobstream_X1b.png",s="/docs-preview/pr-1699/img/blobstream/Celestia_Blobstream_X2b.png",g=JSON.parse('{"title":"BlobstreamX: the previous zk implementation of Blobstream","description":"What is BlobstreamX","frontmatter":{"description":"What is BlobstreamX","head":[["meta",{"name":"og:title","content":"BlobstreamX: the previous zk implementation of Blobstream | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/blobstreamx.md","filePath":"developers/blobstreamx.md","lastUpdated":1725992025000}'),c={name:"developers/blobstreamx.md"},l=a("",18),n=[l];function i(b,m,d,h,p,u){return t(),o("div",null,n)}const B=e(c,[["render",i]]);export{g as __pageData,B as default};
diff --git a/pr-1699/assets/developers_bubs-testnet.md.c168048a.js b/pr-1699/assets/developers_bubs-testnet.md.ddf17ba1.js
similarity index 98%
rename from pr-1699/assets/developers_bubs-testnet.md.c168048a.js
rename to pr-1699/assets/developers_bubs-testnet.md.ddf17ba1.js
index e7ef9b7155..7faeb9b5f7 100644
--- a/pr-1699/assets/developers_bubs-testnet.md.c168048a.js
+++ b/pr-1699/assets/developers_bubs-testnet.md.ddf17ba1.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as s}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia_Bubs_Testnet.jpg",m=JSON.parse('{"title":"Bubs testnet","description":"The first testnet built with OP Stack and Celestia.","frontmatter":{"description":"The first testnet built with OP Stack and Celestia.","next":{"text":"Deploy a smart contract on Bubs testnet","link":"/developers/deploy-on-bubs"},"head":[["meta",{"name":"og:title","content":"Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/bubs-testnet.md","filePath":"developers/bubs-testnet.md","lastUpdated":1725971357000}'),o={name:"developers/bubs-testnet.md"},i=s('
        Bubs testnet ​
        Bubs testnet
        Bubs Testnet is a the first OP Stack testnet with Celestia underneath hosted by Caldera with support from Celestia Labs. Bubs is dedicated to providing developers with an EVM-compatible execution layer to deploy their EVM applications on.
        Built with the OP Stack and Celestia ​
        The Bubs Testnet is a testnet rollup, a modified version of optimism-bedrock that uses Celestia as a data availability (DA) layer. This integration can be found in the @celestiaorg/optimism repository. The testnet is hosted by Caldera, who makes it easy to launch rollups with no code required. Bubs' data is posted to Celestia on the Mocha testnet. View the namespace for Bubs on Celestia's Mocha testnet.
        Learn more about the setup of the integration in the introduction.
        Building on Bubs ​
        Bubs Testnet provides a robust environment for developers to test their Ethereum Virtual Machine (EVM) applications. It offers an EVM-compatible execution layer, making it an ideal platform for developers looking to build and test applications in a setting that closely mirrors an OP Stack rollup on Celestia.
        Learn more at https://bubs-sepolia.hub.caldera.xyz/.
        RPC URLs ​
        Remote Procedure Call (RPC) URLs are endpoints that allow developers to interact with the blockchain. They are essential for sending transactions, querying blockchain data, and performing other interactions with the blockchain.
        For the Bubs Testnet, you can connect to the following RPC URLs:
        HTTPS ​
        • https://bubs-sepolia.rpc.caldera.xyz/http
        WSS ​
        • wss://bubs-sepolia.rpc.caldera.xyz/ws
        This URL serves as the entry point to the Bubs Testnet. You can use it in your applications to connect to the testnet and interact with the smart contracts you deploy there.
        Remember, Bubs Testnet is a testing environment!
        Bridge ​
        Bridging is a process that enables the transfer of assets between different blockchains.
        To bridge between Ethereum Sepolia and Bubs Testnet, visit the Bubs Testnet bridge.
        Faucet ​
        To visit the Bubs testnet faucet, go to https://bubs-sepolia.hub.caldera.xyz/ and click the "Faucet" tab.
        Explorer ​
        To visit the explorer, go to https://bubs-sepolia.explorer.caldera.xyz/.
        Status ​
        To see the status and uptime information for Bubs, visit the status page.
        Next steps ​
        Now that you have a better understanding of the Bubs Testnet and its integration of OP Stack and Celestia, you can start exploring its capabilities.
        ',29),n=[i];function l(h,c,p,d,u,b){return t(),a("div",null,n)}const g=e(o,[["render",l]]);export{m as __pageData,g as default};
+import{_ as e,o as t,c as a,Q as s}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia_Bubs_Testnet.jpg",m=JSON.parse('{"title":"Bubs testnet","description":"The first testnet built with OP Stack and Celestia.","frontmatter":{"description":"The first testnet built with OP Stack and Celestia.","next":{"text":"Deploy a smart contract on Bubs testnet","link":"/developers/deploy-on-bubs"},"head":[["meta",{"name":"og:title","content":"Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/bubs-testnet.md","filePath":"developers/bubs-testnet.md","lastUpdated":1725992025000}'),o={name:"developers/bubs-testnet.md"},i=s('
        Bubs testnet ​
        Bubs testnet
        Bubs Testnet is a the first OP Stack testnet with Celestia underneath hosted by Caldera with support from Celestia Labs. Bubs is dedicated to providing developers with an EVM-compatible execution layer to deploy their EVM applications on.
        Built with the OP Stack and Celestia ​
        The Bubs Testnet is a testnet rollup, a modified version of optimism-bedrock that uses Celestia as a data availability (DA) layer. This integration can be found in the @celestiaorg/optimism repository. The testnet is hosted by Caldera, who makes it easy to launch rollups with no code required. Bubs' data is posted to Celestia on the Mocha testnet. View the namespace for Bubs on Celestia's Mocha testnet.
        Learn more about the setup of the integration in the introduction.
        Building on Bubs ​
        Bubs Testnet provides a robust environment for developers to test their Ethereum Virtual Machine (EVM) applications. It offers an EVM-compatible execution layer, making it an ideal platform for developers looking to build and test applications in a setting that closely mirrors an OP Stack rollup on Celestia.
        Learn more at https://bubs-sepolia.hub.caldera.xyz/.
        RPC URLs ​
        Remote Procedure Call (RPC) URLs are endpoints that allow developers to interact with the blockchain. They are essential for sending transactions, querying blockchain data, and performing other interactions with the blockchain.
        For the Bubs Testnet, you can connect to the following RPC URLs:
        HTTPS ​
        • https://bubs-sepolia.rpc.caldera.xyz/http
        WSS ​
        • wss://bubs-sepolia.rpc.caldera.xyz/ws
        This URL serves as the entry point to the Bubs Testnet. You can use it in your applications to connect to the testnet and interact with the smart contracts you deploy there.
        Remember, Bubs Testnet is a testing environment!
        Bridge ​
        Bridging is a process that enables the transfer of assets between different blockchains.
        To bridge between Ethereum Sepolia and Bubs Testnet, visit the Bubs Testnet bridge.
        Faucet ​
        To visit the Bubs testnet faucet, go to https://bubs-sepolia.hub.caldera.xyz/ and click the "Faucet" tab.
        Explorer ​
        To visit the explorer, go to https://bubs-sepolia.explorer.caldera.xyz/.
        Status ​
        To see the status and uptime information for Bubs, visit the status page.
        Next steps ​
        Now that you have a better understanding of the Bubs Testnet and its integration of OP Stack and Celestia, you can start exploring its capabilities.
        ',29),n=[i];function l(h,c,p,d,u,b){return t(),a("div",null,n)}const g=e(o,[["render",l]]);export{m as __pageData,g as default};
diff --git a/pr-1699/assets/developers_bubs-testnet.md.c168048a.lean.js b/pr-1699/assets/developers_bubs-testnet.md.ddf17ba1.lean.js
similarity index 92%
rename from pr-1699/assets/developers_bubs-testnet.md.c168048a.lean.js
rename to pr-1699/assets/developers_bubs-testnet.md.ddf17ba1.lean.js
index de21bc163e..e7a2ed51a7 100644
--- a/pr-1699/assets/developers_bubs-testnet.md.c168048a.lean.js
+++ b/pr-1699/assets/developers_bubs-testnet.md.ddf17ba1.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as s}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia_Bubs_Testnet.jpg",m=JSON.parse('{"title":"Bubs testnet","description":"The first testnet built with OP Stack and Celestia.","frontmatter":{"description":"The first testnet built with OP Stack and Celestia.","next":{"text":"Deploy a smart contract on Bubs testnet","link":"/developers/deploy-on-bubs"},"head":[["meta",{"name":"og:title","content":"Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/bubs-testnet.md","filePath":"developers/bubs-testnet.md","lastUpdated":1725971357000}'),o={name:"developers/bubs-testnet.md"},i=s("",29),n=[i];function l(h,c,p,d,u,b){return t(),a("div",null,n)}const g=e(o,[["render",l]]);export{m as __pageData,g as default};
+import{_ as e,o as t,c as a,Q as s}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/Celestia_Bubs_Testnet.jpg",m=JSON.parse('{"title":"Bubs testnet","description":"The first testnet built with OP Stack and Celestia.","frontmatter":{"description":"The first testnet built with OP Stack and Celestia.","next":{"text":"Deploy a smart contract on Bubs testnet","link":"/developers/deploy-on-bubs"},"head":[["meta",{"name":"og:title","content":"Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/bubs-testnet.md","filePath":"developers/bubs-testnet.md","lastUpdated":1725992025000}'),o={name:"developers/bubs-testnet.md"},i=s("",29),n=[i];function l(h,c,p,d,u,b){return t(),a("div",null,n)}const g=e(o,[["render",l]]);export{m as __pageData,g as default};
diff --git a/pr-1699/assets/developers_build-whatever.md.4b64aa7d.js b/pr-1699/assets/developers_build-whatever.md.5677fdce.js
similarity index 99%
rename from pr-1699/assets/developers_build-whatever.md.4b64aa7d.js
rename to pr-1699/assets/developers_build-whatever.md.5677fdce.js
index 5dd7d799c9..004dc49fe7 100644
--- a/pr-1699/assets/developers_build-whatever.md.4b64aa7d.js
+++ b/pr-1699/assets/developers_build-whatever.md.5677fdce.js
@@ -1 +1 @@
-import{_ as d,o as l,c as r,k as t,t as i,e as p,H as e,Q as s,a as n}from"./chunks/framework.b47e54aa.js";const h="/docs-preview/pr-1699/img/da-and-validity.png";const m={name:"UrlImageButton",props:{url:String,imageSrc:String,text:String,notes:{type:String,default:""}}},b=["href"],g={class:"url-image-button"},f=["src"],y={class:"button-text"},k={key:0,class:"notes-text"};function w(c,u,o,B,T,z){return l(),r("a",{href:o.url,target:"_blank",rel:"noopener noreferrer",class:"button-link"},[t("button",g,[t("img",{src:o.imageSrc,alt:"",class:"button-icon"},null,8,f),t("span",y,i(o.text),1),o.notes?(l(),r("span",k,i(o.notes),1)):p("",!0)])],8,b)}const a=d(m,[["render",w],["__scopeId","data-v-21baf7e3"]]),_=s('
        Build whatever ​
        If you're a developer and want to know what the benefits of modular blockchains are for you, you’ve come to the right place. This page will give you the rundown on modular blockchains and their benefits for developers like you.
        This section provides various guides and tutorials that cover different options for deploying rollups on Celestia.
        Quickstart - Building on Celestia ​
        Choose a framework ​
        So, you’re ready to start experimenting and building on Celestia? Here are a few options that are currently available for developers.
        ',6),v={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},x=t("h3",{id:"rollups-as-a-service",tabindex:"-1"},[n("Rollups as a Service "),t("a",{class:"header-anchor",href:"#rollups-as-a-service","aria-label":'Permalink to "Rollups as a Service"'},"​")],-1),S=t("p",null,"Deploy your rollup with a RaaS provider.",-1),C={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},P=t("h3",{id:"smart-contracts",tabindex:"-1"},[n("Smart contracts "),t("a",{class:"header-anchor",href:"#smart-contracts","aria-label":'Permalink to "Smart contracts"'},"​")],-1),q=t("p",null,"Deploy your smart contracts on dedicated EVM-compatible rollups.",-1),A={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},V=s('
        What is a rollup? ​
        A rollup is a type of blockchain that offloads some work to a layer 1, like Celestia. Rollups host applications and process user transactions. Once those transactions get processed, they are then published to layer 1. It’s layer 1s job to order those transactions and check that they are available, at minimum.
        What is a modular blockchain? ​
        With blockchains there are more or less four core functions that they do.
        • Execution: transaction execution and state update.
        • Settlement: finality and dispute resolution.
        • Consensus: agreement on transaction ordering.
        • Data availability: prove data was published to the network.
        Modular blockchains specialize in one or two of these functions rather than doing all of them like a monolithic blockchain. You probably know about layer 1s and layer 2s. That’s the general idea.
        A typical example of a modular blockchain you might’ve heard of is a rollup. Rollups host smart contracts and execute transactions, much like any monolithic chain. But, the data of those transactions get sent to a layer 1 blockchain to carry out the remaining functions.
        If you want to brush up on your understanding of modular blockchains, head over to learn modular.
        Benefits of modular blockchains ​
        Ease of deploying a chain ​
        One of the goals of modular blockchains is to make it as easy to deploy a blockchain as a smart contract. There are a few unique ways that modular blockchains can significantly reduce the cost of deploying a new blockchain.
        1. No validator set is required. Rollups can deploy without sourcing their own set of validators or sequencers.
        2. Inherit security from the start. Rollups don’t need to build all their security from scratch.
        3. Any part of the stack can be delegated. Development time can be reduced by outsourcing functions of the rollup to external providers.
        All in all, builders will be able to outsource as much of the stack as they need. Deploying a new blockchain will be as simple as clicking a few options to initialize a production-ready rollup.
        Scaling ​
        Of course, a much higher scale is necessary if we want to support many more users. And modular blockchains use some new innovative technologies that can help us get there.
        • Data availability sampling enables modular blockchains like Celestia to scale data availability with the number of light nodes - that means more capacity for rollups.
        • Fraud and validity proofs make rollups vastly more efficient to verify. Nodes only need to verify a small proof of transaction validity (validity proof) or assume transactions are valid by default (fraud proof). This means rollups don’t require every node in the network to re-execute every transaction.
        image
        • Decoupling execution from consensus lets developers define the VM that best fits the scaling needs of their application.
        • Separating applications across multiple rollups isolates congestion. If an application congests the execution capacity of one rollup, all other rollups remain unaffected in their execution capacity.
        All these scaling properties combined make new types of applications and features possible, like onchain gaming, dynamic metadata, and ephemeral rollups, to name a few.
        Customizability ​
        By design, modular blockchains don’t lock in any feature set. They promote experimentation and customization.
        Remember how decoupling execution from consensus enables VM customizability? Well, rollups are the execution component. Applications can run on their own rollup and adjust the VM to maximize their application's performance. Developers have that flexibility because Celestia's execution logic doesn't restrict rollups.
        Basically, rollups can be customized to integrate any new or existing VM stack.
        With existing rollup frameworks, developers can run rollup testnets using the EVM or Cosmos SDK. In the future, one can imagine a variety of VMs that rollup frameworks support, providing developers with more out-of-the-box options for their applications.
        Some customizations that could be made to a rollup's VM include custom precompiles, changing transaction processing from sequential to parallel, or adding support for private smart contracts.
        All of this only scratches the surface.
        ',26),R=JSON.parse('{"title":"Build whatever","description":"Advantages of building on modular blockchains like Celestia.","frontmatter":{"description":"Advantages of building on modular blockchains like Celestia.","head":[["meta",{"name":"og:title","content":"Build whatever | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/build-whatever.md","filePath":"developers/build-whatever.md","lastUpdated":1725971357000}'),O={name:"developers/build-whatever.md"},I=Object.assign(O,{setup(c){return(u,o)=>(l(),r("div",null,[_,t("div",v,[e(a,{url:"/developers/intro-to-op-stack",imageSrc:"/build/opstack.webp",text:"OP Stack",notes:"EVM",target:"_self",alt:"OP Stack logo","aria-label":"OP Stack"}),e(a,{url:"/developers/arbitrum-integration",imageSrc:"/build/arbitrum.webp",text:"Arbitrum Orbit",notes:"EVM",target:"_self",alt:"Arbitrum logo","aria-label":"Arbitrum"}),e(a,{url:"https://github.com/Sovereign-Labs/sovereign-sdk/tree/stable/examples/demo-rollup#demo-rollup",imageSrc:"/build/sovereign.webp",text:"Sovereign SDK",notes:"Sovereign",alt:"Sovereign logo","aria-label":"Sovereign"}),e(a,{url:"https://docs.dymension.xyz/build/overview/",imageSrc:"/build/dymension.webp",text:"Dymension",alt:"Dymension logo","aria-label":"Dymension"}),e(a,{url:"https://docs.stf.xyz",imageSrc:"/build/stackr.webp",text:"Stackr",alt:"Stackr logo","aria-label":"Stackr"}),e(a,{url:"https://rollkit.dev",imageSrc:"/build/rollkit.webp",text:"Rollkit",notes:"Sovereign",alt:"Rollkit logo","aria-label":"Rollkit"})]),x,S,t("div",C,[e(a,{url:"https://altlayer.io/raas/",imageSrc:"/build/altlayer.webp",text:"AltLayer",notes:"Orbit, OP Stack",alt:"AltLayer logo","aria-label":"AltLayer"}),e(a,{url:"https://www.astria.org/",imageSrc:"/build/astria.webp",text:"Astria",alt:"Astria logo","aria-label":"Astria"}),e(a,{url:"https://www.caldera.xyz/",imageSrc:"/build/caldera.webp",text:"Caldera",notes:"Orbit, OP Stack",alt:"Caldera logo","aria-label":"Caldera"}),e(a,{url:"https://conduit.xyz/",imageSrc:"/build/conduit.webp",text:"Conduit",notes:"Orbit, OP Stack",alt:"Conduit logo","aria-label":"Conduit"}),e(a,{url:"https://www.gelato.network/",imageSrc:"/build/gelato.webp",text:"Gelato",notes:"Orbit, OP Stack",alt:"Gelato logo","aria-label":"Gelato"}),e(a,{url:"https://www.karnot.xyz/",imageSrc:"/build/karnot.webp",text:"Karnot",notes:"Starknet",alt:"Karnot logo","aria-label":"Karnot"}),e(a,{url:"https://docs.vistara.dev/",imageSrc:"/build/vistara.webp",text:"Vistara",alt:"Vistara logo","aria-label":"Vistara"}),e(a,{url:"https://www.zeeve.io/",imageSrc:"/build/zeeve.webp",text:"Zeeve",notes:"Orbit, OP Stack",alt:"Zeeve logo","aria-label":"Zeeve"})]),P,q,t("div",A,[e(a,{url:"https://bubstestnet.com/",imageSrc:"/build/caldera.webp",text:"Bubs testnet",notes:"OP Stack",alt:"Caldera logo","aria-label":"Caldera Bubs testnet"}),e(a,{url:"https://raas.gelato.network/rollups/details/public/opcelestia-raspberry",imageSrc:"/build/gelato.webp",text:"Raspberry testnet",notes:"OP Stack",alt:"Gelato logo","aria-label":"Gelato Raspberry testnet"})]),V]))}});export{R as __pageData,I as default};
+import{_ as d,o as l,c as r,k as t,t as i,e as p,H as e,Q as s,a as n}from"./chunks/framework.b47e54aa.js";const h="/docs-preview/pr-1699/img/da-and-validity.png";const m={name:"UrlImageButton",props:{url:String,imageSrc:String,text:String,notes:{type:String,default:""}}},b=["href"],g={class:"url-image-button"},f=["src"],y={class:"button-text"},k={key:0,class:"notes-text"};function w(c,u,o,B,T,z){return l(),r("a",{href:o.url,target:"_blank",rel:"noopener noreferrer",class:"button-link"},[t("button",g,[t("img",{src:o.imageSrc,alt:"",class:"button-icon"},null,8,f),t("span",y,i(o.text),1),o.notes?(l(),r("span",k,i(o.notes),1)):p("",!0)])],8,b)}const a=d(m,[["render",w],["__scopeId","data-v-21baf7e3"]]),_=s('
        Build whatever ​
        If you're a developer and want to know what the benefits of modular blockchains are for you, you’ve come to the right place. This page will give you the rundown on modular blockchains and their benefits for developers like you.
        This section provides various guides and tutorials that cover different options for deploying rollups on Celestia.
        Quickstart - Building on Celestia ​
        Choose a framework ​
        So, you’re ready to start experimenting and building on Celestia? Here are a few options that are currently available for developers.
        ',6),v={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},x=t("h3",{id:"rollups-as-a-service",tabindex:"-1"},[n("Rollups as a Service "),t("a",{class:"header-anchor",href:"#rollups-as-a-service","aria-label":'Permalink to "Rollups as a Service"'},"​")],-1),S=t("p",null,"Deploy your rollup with a RaaS provider.",-1),C={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},P=t("h3",{id:"smart-contracts",tabindex:"-1"},[n("Smart contracts "),t("a",{class:"header-anchor",href:"#smart-contracts","aria-label":'Permalink to "Smart contracts"'},"​")],-1),q=t("p",null,"Deploy your smart contracts on dedicated EVM-compatible rollups.",-1),A={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},V=s('
        What is a rollup? ​
        A rollup is a type of blockchain that offloads some work to a layer 1, like Celestia. Rollups host applications and process user transactions. Once those transactions get processed, they are then published to layer 1. It’s layer 1s job to order those transactions and check that they are available, at minimum.
        What is a modular blockchain? ​
        With blockchains there are more or less four core functions that they do.
        • Execution: transaction execution and state update.
        • Settlement: finality and dispute resolution.
        • Consensus: agreement on transaction ordering.
        • Data availability: prove data was published to the network.
        Modular blockchains specialize in one or two of these functions rather than doing all of them like a monolithic blockchain. You probably know about layer 1s and layer 2s. That’s the general idea.
        A typical example of a modular blockchain you might’ve heard of is a rollup. Rollups host smart contracts and execute transactions, much like any monolithic chain. But, the data of those transactions get sent to a layer 1 blockchain to carry out the remaining functions.
        If you want to brush up on your understanding of modular blockchains, head over to learn modular.
        Benefits of modular blockchains ​
        Ease of deploying a chain ​
        One of the goals of modular blockchains is to make it as easy to deploy a blockchain as a smart contract. There are a few unique ways that modular blockchains can significantly reduce the cost of deploying a new blockchain.
        1. No validator set is required. Rollups can deploy without sourcing their own set of validators or sequencers.
        2. Inherit security from the start. Rollups don’t need to build all their security from scratch.
        3. Any part of the stack can be delegated. Development time can be reduced by outsourcing functions of the rollup to external providers.
        All in all, builders will be able to outsource as much of the stack as they need. Deploying a new blockchain will be as simple as clicking a few options to initialize a production-ready rollup.
        Scaling ​
        Of course, a much higher scale is necessary if we want to support many more users. And modular blockchains use some new innovative technologies that can help us get there.
        • Data availability sampling enables modular blockchains like Celestia to scale data availability with the number of light nodes - that means more capacity for rollups.
        • Fraud and validity proofs make rollups vastly more efficient to verify. Nodes only need to verify a small proof of transaction validity (validity proof) or assume transactions are valid by default (fraud proof). This means rollups don’t require every node in the network to re-execute every transaction.
        image
        • Decoupling execution from consensus lets developers define the VM that best fits the scaling needs of their application.
        • Separating applications across multiple rollups isolates congestion. If an application congests the execution capacity of one rollup, all other rollups remain unaffected in their execution capacity.
        All these scaling properties combined make new types of applications and features possible, like onchain gaming, dynamic metadata, and ephemeral rollups, to name a few.
        Customizability ​
        By design, modular blockchains don’t lock in any feature set. They promote experimentation and customization.
        Remember how decoupling execution from consensus enables VM customizability? Well, rollups are the execution component. Applications can run on their own rollup and adjust the VM to maximize their application's performance. Developers have that flexibility because Celestia's execution logic doesn't restrict rollups.
        Basically, rollups can be customized to integrate any new or existing VM stack.
        With existing rollup frameworks, developers can run rollup testnets using the EVM or Cosmos SDK. In the future, one can imagine a variety of VMs that rollup frameworks support, providing developers with more out-of-the-box options for their applications.
        Some customizations that could be made to a rollup's VM include custom precompiles, changing transaction processing from sequential to parallel, or adding support for private smart contracts.
        All of this only scratches the surface.
        ',26),R=JSON.parse('{"title":"Build whatever","description":"Advantages of building on modular blockchains like Celestia.","frontmatter":{"description":"Advantages of building on modular blockchains like Celestia.","head":[["meta",{"name":"og:title","content":"Build whatever | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/build-whatever.md","filePath":"developers/build-whatever.md","lastUpdated":1725992025000}'),O={name:"developers/build-whatever.md"},I=Object.assign(O,{setup(c){return(u,o)=>(l(),r("div",null,[_,t("div",v,[e(a,{url:"/developers/intro-to-op-stack",imageSrc:"/build/opstack.webp",text:"OP Stack",notes:"EVM",target:"_self",alt:"OP Stack logo","aria-label":"OP Stack"}),e(a,{url:"/developers/arbitrum-integration",imageSrc:"/build/arbitrum.webp",text:"Arbitrum Orbit",notes:"EVM",target:"_self",alt:"Arbitrum logo","aria-label":"Arbitrum"}),e(a,{url:"https://github.com/Sovereign-Labs/sovereign-sdk/tree/stable/examples/demo-rollup#demo-rollup",imageSrc:"/build/sovereign.webp",text:"Sovereign SDK",notes:"Sovereign",alt:"Sovereign logo","aria-label":"Sovereign"}),e(a,{url:"https://docs.dymension.xyz/build/overview/",imageSrc:"/build/dymension.webp",text:"Dymension",alt:"Dymension logo","aria-label":"Dymension"}),e(a,{url:"https://docs.stf.xyz",imageSrc:"/build/stackr.webp",text:"Stackr",alt:"Stackr logo","aria-label":"Stackr"}),e(a,{url:"https://rollkit.dev",imageSrc:"/build/rollkit.webp",text:"Rollkit",notes:"Sovereign",alt:"Rollkit logo","aria-label":"Rollkit"})]),x,S,t("div",C,[e(a,{url:"https://altlayer.io/raas/",imageSrc:"/build/altlayer.webp",text:"AltLayer",notes:"Orbit, OP Stack",alt:"AltLayer logo","aria-label":"AltLayer"}),e(a,{url:"https://www.astria.org/",imageSrc:"/build/astria.webp",text:"Astria",alt:"Astria logo","aria-label":"Astria"}),e(a,{url:"https://www.caldera.xyz/",imageSrc:"/build/caldera.webp",text:"Caldera",notes:"Orbit, OP Stack",alt:"Caldera logo","aria-label":"Caldera"}),e(a,{url:"https://conduit.xyz/",imageSrc:"/build/conduit.webp",text:"Conduit",notes:"Orbit, OP Stack",alt:"Conduit logo","aria-label":"Conduit"}),e(a,{url:"https://www.gelato.network/",imageSrc:"/build/gelato.webp",text:"Gelato",notes:"Orbit, OP Stack",alt:"Gelato logo","aria-label":"Gelato"}),e(a,{url:"https://www.karnot.xyz/",imageSrc:"/build/karnot.webp",text:"Karnot",notes:"Starknet",alt:"Karnot logo","aria-label":"Karnot"}),e(a,{url:"https://docs.vistara.dev/",imageSrc:"/build/vistara.webp",text:"Vistara",alt:"Vistara logo","aria-label":"Vistara"}),e(a,{url:"https://www.zeeve.io/",imageSrc:"/build/zeeve.webp",text:"Zeeve",notes:"Orbit, OP Stack",alt:"Zeeve logo","aria-label":"Zeeve"})]),P,q,t("div",A,[e(a,{url:"https://bubstestnet.com/",imageSrc:"/build/caldera.webp",text:"Bubs testnet",notes:"OP Stack",alt:"Caldera logo","aria-label":"Caldera Bubs testnet"}),e(a,{url:"https://raas.gelato.network/rollups/details/public/opcelestia-raspberry",imageSrc:"/build/gelato.webp",text:"Raspberry testnet",notes:"OP Stack",alt:"Gelato logo","aria-label":"Gelato Raspberry testnet"})]),V]))}});export{R as __pageData,I as default};
diff --git a/pr-1699/assets/developers_build-whatever.md.4b64aa7d.lean.js b/pr-1699/assets/developers_build-whatever.md.5677fdce.lean.js
similarity index 98%
rename from pr-1699/assets/developers_build-whatever.md.4b64aa7d.lean.js
rename to pr-1699/assets/developers_build-whatever.md.5677fdce.lean.js
index fa8c93b7a4..3d1b0aa4bf 100644
--- a/pr-1699/assets/developers_build-whatever.md.4b64aa7d.lean.js
+++ b/pr-1699/assets/developers_build-whatever.md.5677fdce.lean.js
@@ -1 +1 @@
-import{_ as d,o as l,c as r,k as t,t as i,e as p,H as e,Q as s,a as n}from"./chunks/framework.b47e54aa.js";const h="/docs-preview/pr-1699/img/da-and-validity.png";const m={name:"UrlImageButton",props:{url:String,imageSrc:String,text:String,notes:{type:String,default:""}}},b=["href"],g={class:"url-image-button"},f=["src"],y={class:"button-text"},k={key:0,class:"notes-text"};function w(c,u,o,B,T,z){return l(),r("a",{href:o.url,target:"_blank",rel:"noopener noreferrer",class:"button-link"},[t("button",g,[t("img",{src:o.imageSrc,alt:"",class:"button-icon"},null,8,f),t("span",y,i(o.text),1),o.notes?(l(),r("span",k,i(o.notes),1)):p("",!0)])],8,b)}const a=d(m,[["render",w],["__scopeId","data-v-21baf7e3"]]),_=s("",6),v={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},x=t("h3",{id:"rollups-as-a-service",tabindex:"-1"},[n("Rollups as a Service "),t("a",{class:"header-anchor",href:"#rollups-as-a-service","aria-label":'Permalink to "Rollups as a Service"'},"​")],-1),S=t("p",null,"Deploy your rollup with a RaaS provider.",-1),C={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},P=t("h3",{id:"smart-contracts",tabindex:"-1"},[n("Smart contracts "),t("a",{class:"header-anchor",href:"#smart-contracts","aria-label":'Permalink to "Smart contracts"'},"​")],-1),q=t("p",null,"Deploy your smart contracts on dedicated EVM-compatible rollups.",-1),A={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},V=s("",26),R=JSON.parse('{"title":"Build whatever","description":"Advantages of building on modular blockchains like Celestia.","frontmatter":{"description":"Advantages of building on modular blockchains like Celestia.","head":[["meta",{"name":"og:title","content":"Build whatever | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/build-whatever.md","filePath":"developers/build-whatever.md","lastUpdated":1725971357000}'),O={name:"developers/build-whatever.md"},I=Object.assign(O,{setup(c){return(u,o)=>(l(),r("div",null,[_,t("div",v,[e(a,{url:"/developers/intro-to-op-stack",imageSrc:"/build/opstack.webp",text:"OP Stack",notes:"EVM",target:"_self",alt:"OP Stack logo","aria-label":"OP Stack"}),e(a,{url:"/developers/arbitrum-integration",imageSrc:"/build/arbitrum.webp",text:"Arbitrum Orbit",notes:"EVM",target:"_self",alt:"Arbitrum logo","aria-label":"Arbitrum"}),e(a,{url:"https://github.com/Sovereign-Labs/sovereign-sdk/tree/stable/examples/demo-rollup#demo-rollup",imageSrc:"/build/sovereign.webp",text:"Sovereign SDK",notes:"Sovereign",alt:"Sovereign logo","aria-label":"Sovereign"}),e(a,{url:"https://docs.dymension.xyz/build/overview/",imageSrc:"/build/dymension.webp",text:"Dymension",alt:"Dymension logo","aria-label":"Dymension"}),e(a,{url:"https://docs.stf.xyz",imageSrc:"/build/stackr.webp",text:"Stackr",alt:"Stackr logo","aria-label":"Stackr"}),e(a,{url:"https://rollkit.dev",imageSrc:"/build/rollkit.webp",text:"Rollkit",notes:"Sovereign",alt:"Rollkit logo","aria-label":"Rollkit"})]),x,S,t("div",C,[e(a,{url:"https://altlayer.io/raas/",imageSrc:"/build/altlayer.webp",text:"AltLayer",notes:"Orbit, OP Stack",alt:"AltLayer logo","aria-label":"AltLayer"}),e(a,{url:"https://www.astria.org/",imageSrc:"/build/astria.webp",text:"Astria",alt:"Astria logo","aria-label":"Astria"}),e(a,{url:"https://www.caldera.xyz/",imageSrc:"/build/caldera.webp",text:"Caldera",notes:"Orbit, OP Stack",alt:"Caldera logo","aria-label":"Caldera"}),e(a,{url:"https://conduit.xyz/",imageSrc:"/build/conduit.webp",text:"Conduit",notes:"Orbit, OP Stack",alt:"Conduit logo","aria-label":"Conduit"}),e(a,{url:"https://www.gelato.network/",imageSrc:"/build/gelato.webp",text:"Gelato",notes:"Orbit, OP Stack",alt:"Gelato logo","aria-label":"Gelato"}),e(a,{url:"https://www.karnot.xyz/",imageSrc:"/build/karnot.webp",text:"Karnot",notes:"Starknet",alt:"Karnot logo","aria-label":"Karnot"}),e(a,{url:"https://docs.vistara.dev/",imageSrc:"/build/vistara.webp",text:"Vistara",alt:"Vistara logo","aria-label":"Vistara"}),e(a,{url:"https://www.zeeve.io/",imageSrc:"/build/zeeve.webp",text:"Zeeve",notes:"Orbit, OP Stack",alt:"Zeeve logo","aria-label":"Zeeve"})]),P,q,t("div",A,[e(a,{url:"https://bubstestnet.com/",imageSrc:"/build/caldera.webp",text:"Bubs testnet",notes:"OP Stack",alt:"Caldera logo","aria-label":"Caldera Bubs testnet"}),e(a,{url:"https://raas.gelato.network/rollups/details/public/opcelestia-raspberry",imageSrc:"/build/gelato.webp",text:"Raspberry testnet",notes:"OP Stack",alt:"Gelato logo","aria-label":"Gelato Raspberry testnet"})]),V]))}});export{R as __pageData,I as default};
+import{_ as d,o as l,c as r,k as t,t as i,e as p,H as e,Q as s,a as n}from"./chunks/framework.b47e54aa.js";const h="/docs-preview/pr-1699/img/da-and-validity.png";const m={name:"UrlImageButton",props:{url:String,imageSrc:String,text:String,notes:{type:String,default:""}}},b=["href"],g={class:"url-image-button"},f=["src"],y={class:"button-text"},k={key:0,class:"notes-text"};function w(c,u,o,B,T,z){return l(),r("a",{href:o.url,target:"_blank",rel:"noopener noreferrer",class:"button-link"},[t("button",g,[t("img",{src:o.imageSrc,alt:"",class:"button-icon"},null,8,f),t("span",y,i(o.text),1),o.notes?(l(),r("span",k,i(o.notes),1)):p("",!0)])],8,b)}const a=d(m,[["render",w],["__scopeId","data-v-21baf7e3"]]),_=s("",6),v={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},x=t("h3",{id:"rollups-as-a-service",tabindex:"-1"},[n("Rollups as a Service "),t("a",{class:"header-anchor",href:"#rollups-as-a-service","aria-label":'Permalink to "Rollups as a Service"'},"​")],-1),S=t("p",null,"Deploy your rollup with a RaaS provider.",-1),C={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},P=t("h3",{id:"smart-contracts",tabindex:"-1"},[n("Smart contracts "),t("a",{class:"header-anchor",href:"#smart-contracts","aria-label":'Permalink to "Smart contracts"'},"​")],-1),q=t("p",null,"Deploy your smart contracts on dedicated EVM-compatible rollups.",-1),A={style:{display:"flex","flex-wrap":"wrap","justify-content":"center","align-items":"center","grid-template-columns":"repeat(auto-fill, minmax(150px, 1fr))",gap:"20px"}},V=s("",26),R=JSON.parse('{"title":"Build whatever","description":"Advantages of building on modular blockchains like Celestia.","frontmatter":{"description":"Advantages of building on modular blockchains like Celestia.","head":[["meta",{"name":"og:title","content":"Build whatever | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/build-whatever.md","filePath":"developers/build-whatever.md","lastUpdated":1725992025000}'),O={name:"developers/build-whatever.md"},I=Object.assign(O,{setup(c){return(u,o)=>(l(),r("div",null,[_,t("div",v,[e(a,{url:"/developers/intro-to-op-stack",imageSrc:"/build/opstack.webp",text:"OP Stack",notes:"EVM",target:"_self",alt:"OP Stack logo","aria-label":"OP Stack"}),e(a,{url:"/developers/arbitrum-integration",imageSrc:"/build/arbitrum.webp",text:"Arbitrum Orbit",notes:"EVM",target:"_self",alt:"Arbitrum logo","aria-label":"Arbitrum"}),e(a,{url:"https://github.com/Sovereign-Labs/sovereign-sdk/tree/stable/examples/demo-rollup#demo-rollup",imageSrc:"/build/sovereign.webp",text:"Sovereign SDK",notes:"Sovereign",alt:"Sovereign logo","aria-label":"Sovereign"}),e(a,{url:"https://docs.dymension.xyz/build/overview/",imageSrc:"/build/dymension.webp",text:"Dymension",alt:"Dymension logo","aria-label":"Dymension"}),e(a,{url:"https://docs.stf.xyz",imageSrc:"/build/stackr.webp",text:"Stackr",alt:"Stackr logo","aria-label":"Stackr"}),e(a,{url:"https://rollkit.dev",imageSrc:"/build/rollkit.webp",text:"Rollkit",notes:"Sovereign",alt:"Rollkit logo","aria-label":"Rollkit"})]),x,S,t("div",C,[e(a,{url:"https://altlayer.io/raas/",imageSrc:"/build/altlayer.webp",text:"AltLayer",notes:"Orbit, OP Stack",alt:"AltLayer logo","aria-label":"AltLayer"}),e(a,{url:"https://www.astria.org/",imageSrc:"/build/astria.webp",text:"Astria",alt:"Astria logo","aria-label":"Astria"}),e(a,{url:"https://www.caldera.xyz/",imageSrc:"/build/caldera.webp",text:"Caldera",notes:"Orbit, OP Stack",alt:"Caldera logo","aria-label":"Caldera"}),e(a,{url:"https://conduit.xyz/",imageSrc:"/build/conduit.webp",text:"Conduit",notes:"Orbit, OP Stack",alt:"Conduit logo","aria-label":"Conduit"}),e(a,{url:"https://www.gelato.network/",imageSrc:"/build/gelato.webp",text:"Gelato",notes:"Orbit, OP Stack",alt:"Gelato logo","aria-label":"Gelato"}),e(a,{url:"https://www.karnot.xyz/",imageSrc:"/build/karnot.webp",text:"Karnot",notes:"Starknet",alt:"Karnot logo","aria-label":"Karnot"}),e(a,{url:"https://docs.vistara.dev/",imageSrc:"/build/vistara.webp",text:"Vistara",alt:"Vistara logo","aria-label":"Vistara"}),e(a,{url:"https://www.zeeve.io/",imageSrc:"/build/zeeve.webp",text:"Zeeve",notes:"Orbit, OP Stack",alt:"Zeeve logo","aria-label":"Zeeve"})]),P,q,t("div",A,[e(a,{url:"https://bubstestnet.com/",imageSrc:"/build/caldera.webp",text:"Bubs testnet",notes:"OP Stack",alt:"Caldera logo","aria-label":"Caldera Bubs testnet"}),e(a,{url:"https://raas.gelato.network/rollups/details/public/opcelestia-raspberry",imageSrc:"/build/gelato.webp",text:"Raspberry testnet",notes:"OP Stack",alt:"Gelato logo","aria-label":"Gelato Raspberry testnet"})]),V]))}});export{R as __pageData,I as default};
diff --git a/pr-1699/assets/developers_celestia-node-key.md.93827487.js b/pr-1699/assets/developers_celestia-node-key.md.fe2dab0d.js
similarity index 98%
rename from pr-1699/assets/developers_celestia-node-key.md.93827487.js
rename to pr-1699/assets/developers_celestia-node-key.md.fe2dab0d.js
index 1e70810293..4dbc796edf 100644
--- a/pr-1699/assets/developers_celestia-node-key.md.93827487.js
+++ b/pr-1699/assets/developers_celestia-node-key.md.fe2dab0d.js
@@ -4,19 +4,19 @@ import{m as o}from"./chunks/mocha_versions.7704b055.js";import{o as p,c as t,k a
 make cel-key
        # dumps binary in current working directory, accessible via \`./cel-key\`
 make cel-key
        or
        sh
        # installs binary in GOBIN path, accessible via \`cel-key\`
 make install-key
        # installs binary in GOBIN path, accessible via \`cel-key\`
-make install-key
        For the purpose of this guide, we will use the make cel-key command.
        Steps for generating node keys ​
        To generate a key for a Celestia node, select the tab for your node type:
        TIP
        You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information
        bash
        ./cel-key add <key-name> --keyring-backend test --node.type bridge \\
+make install-key
        For the purpose of this guide, we will use the make cel-key command.
        Steps for generating node keys ​
        To generate a key for a Celestia node, select the tab for your node type:
        TIP
        You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information
        bash
        ./cel-key add <key-name> --keyring-backend test --node.type bridge \\
   --p2p.network <network>
        ./cel-key add <key-name> --keyring-backend test --node.type bridge \\
   --p2p.network <network>
        bash
        ./cel-key add <key-name> --keyring-backend test --node.type full \\
   --p2p.network <network>
        ./cel-key add <key-name> --keyring-backend test --node.type full \\
   --p2p.network <network>
        bash
        ./cel-key add <key-name> --keyring-backend test --node.type light \\
   --p2p.network <network>
        ./cel-key add <key-name> --keyring-backend test --node.type light \\
-  --p2p.network <network>
        This will load the key <key-name> into the directory of the node.
        Further flags you can use to customize your key are the following:
        • --p2p.network: Specifies which network you want the key for. Values are arabica and mocha. Please note the default network will be mocha.
        Keep in mind that your celestia-node will only pick up keys that are inside the default directory under /keys so you should make sure to point cel-key utility to the correct directory via the p2p.network or home flags if you have specified a custom directory or network other than Arabica, Mocha, or Mainnet Beta.
        Also keep in mind that if you do not specify a network with --p2p.network, the default one will always be celestia (Mainnet Beta).
        Steps for exporting node keys ​
        You can export a private key from the local keyring in encrypted and ASCII-armored format.
        bash
        ./cel-key export <key-name> --keyring-backend test --node.type bridge \\
+  --p2p.network <network>
        This will load the key <key-name> into the directory of the node.
        Further flags you can use to customize your key are the following:
        • --p2p.network: Specifies which network you want the key for. Values are arabica and mocha. Please note the default network will be mocha.
        Keep in mind that your celestia-node will only pick up keys that are inside the default directory under /keys so you should make sure to point cel-key utility to the correct directory via the p2p.network or home flags if you have specified a custom directory or network other than Arabica, Mocha, or Mainnet Beta.
        Also keep in mind that if you do not specify a network with --p2p.network, the default one will always be celestia (Mainnet Beta).
        Steps for exporting node keys ​
        You can export a private key from the local keyring in encrypted and ASCII-armored format.
        bash
        ./cel-key export <key-name> --keyring-backend test --node.type bridge \\
   --p2p.network <network>
        ./cel-key export <key-name> --keyring-backend test --node.type bridge \\
   --p2p.network <network>
        bash
        ./cel-key export <key-name> --keyring-backend test --node.type full \\
   --p2p.network <network>
        ./cel-key export <key-name> --keyring-backend test --node.type full \\
   --p2p.network <network>
        bash
        ./cel-key export <key-name> --keyring-backend test --node.type light \\
   --p2p.network <network>
        ./cel-key export <key-name> --keyring-backend test --node.type light \\
-  --p2p.network <network>
        Steps for importing node keys ​
        To import from a mnemonic, use the following command, then enter your bip39 mnemonic:
        bash
        ./cel-key add <key-name> --recover --keyring-backend test \\
+  --p2p.network <network>
        Steps for importing node keys ​
        To import from a mnemonic, use the following command, then enter your bip39 mnemonic:
        bash
        ./cel-key add <key-name> --recover --keyring-backend test \\
   --node.type bridge --p2p.network <network>
        ./cel-key add <key-name> --recover --keyring-backend test \\
   --node.type bridge --p2p.network <network>
        bash
        ./cel-key add <key-name> --recover --keyring-backend test \\
   --node.type full --p2p.network <network>
        ./cel-key add <key-name> --recover --keyring-backend test \\
@@ -56,7 +56,7 @@ import{m as o}from"./chunks/mocha_versions.7704b055.js";import{o as p,c as t,k a
 - address: celestia1wkhyhr7ngf0ayqlpnsnxg4d72hfs5453dvunm9
   name: my_celes_key
   pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A1/NsoY0RGL7Hqt4VWLg441GQKJsZ2fBUnZXipgns8oV"}'
-  type: local
        `,24),S=JSON.parse('{"title":"Create a wallet with celestia-node","description":"Use the cel-key utility to generate a wallet on celestia-node.","frontmatter":{"description":"Use the cel-key utility to generate a wallet on celestia-node.","prev":{"text":"New Blobstream X deployments","link":"/developers/blobstream-x-deploy"},"head":[["meta",{"name":"og:title","content":"Create a wallet with celestia-node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/celestia-node-key.md","filePath":"developers/celestia-node-key.md","lastUpdated":1725971357000}'),w={name:"developers/celestia-node-key.md"},P=Object.assign(w,{setup(A){return(f,D)=>(p(),t("div",null,[c,s("div",r,[y,i,s("pre",E,[s("code",null,[d,n(`
+  type: local
        `,24),S=JSON.parse('{"title":"Create a wallet with celestia-node","description":"Use the cel-key utility to generate a wallet on celestia-node.","frontmatter":{"description":"Use the cel-key utility to generate a wallet on celestia-node.","prev":{"text":"New Blobstream X deployments","link":"/developers/blobstream-x-deploy"},"head":[["meta",{"name":"og:title","content":"Create a wallet with celestia-node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/celestia-node-key.md","filePath":"developers/celestia-node-key.md","lastUpdated":1725992025000}'),w={name:"developers/celestia-node-key.md"},P=Object.assign(w,{setup(A){return(f,D)=>(p(),t("div",null,[c,s("div",r,[y,i,s("pre",E,[s("code",null,[d,n(`
 `),s("span",F,[s("span",h,"ghcr.io/celestiaorg/celestia-node:"+l(e(o)["node-latest-tag"])+" ",1),g]),n(`
 `),k])]),s("pre",u,[s("code",null,[C,n(`
 `),s("span",b,[s("span",v,"ghcr.io/celestiaorg/celestia-node:"+l(e(o)["node-latest-tag"])+" ",1),m]),n(`
diff --git a/pr-1699/assets/developers_celestia-node-key.md.93827487.lean.js b/pr-1699/assets/developers_celestia-node-key.md.fe2dab0d.lean.js
similarity index 96%
rename from pr-1699/assets/developers_celestia-node-key.md.93827487.lean.js
rename to pr-1699/assets/developers_celestia-node-key.md.fe2dab0d.lean.js
index 4b3cbf0c40..bae0084f9f 100644
--- a/pr-1699/assets/developers_celestia-node-key.md.93827487.lean.js
+++ b/pr-1699/assets/developers_celestia-node-key.md.fe2dab0d.lean.js
@@ -1,4 +1,4 @@
-import{m as o}from"./chunks/mocha_versions.7704b055.js";import{o as p,c as t,k as s,a as n,t as l,l as e,Q as a}from"./chunks/framework.b47e54aa.js";const c=a("",37),r={class:"language-bash vp-adaptive-theme"},y=s("button",{title:"Copy Code",class:"copy"},null,-1),i=s("span",{class:"lang"},"bash",-1),E={class:"shiki github-dark vp-code-dark"},d=a("",1),F={class:"line"},h={style:{color:"#E1E4E8"}},g=a("",7),k=a("",1),u={class:"shiki github-light vp-code-light"},C=a("",1),b={class:"line"},v={style:{color:"#24292E"}},m=a("",7),B=a("",1),_=a("",24),S=JSON.parse('{"title":"Create a wallet with celestia-node","description":"Use the cel-key utility to generate a wallet on celestia-node.","frontmatter":{"description":"Use the cel-key utility to generate a wallet on celestia-node.","prev":{"text":"New Blobstream X deployments","link":"/developers/blobstream-x-deploy"},"head":[["meta",{"name":"og:title","content":"Create a wallet with celestia-node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/celestia-node-key.md","filePath":"developers/celestia-node-key.md","lastUpdated":1725971357000}'),w={name:"developers/celestia-node-key.md"},P=Object.assign(w,{setup(A){return(f,D)=>(p(),t("div",null,[c,s("div",r,[y,i,s("pre",E,[s("code",null,[d,n(`
+import{m as o}from"./chunks/mocha_versions.7704b055.js";import{o as p,c as t,k as s,a as n,t as l,l as e,Q as a}from"./chunks/framework.b47e54aa.js";const c=a("",37),r={class:"language-bash vp-adaptive-theme"},y=s("button",{title:"Copy Code",class:"copy"},null,-1),i=s("span",{class:"lang"},"bash",-1),E={class:"shiki github-dark vp-code-dark"},d=a("",1),F={class:"line"},h={style:{color:"#E1E4E8"}},g=a("",7),k=a("",1),u={class:"shiki github-light vp-code-light"},C=a("",1),b={class:"line"},v={style:{color:"#24292E"}},m=a("",7),B=a("",1),_=a("",24),S=JSON.parse('{"title":"Create a wallet with celestia-node","description":"Use the cel-key utility to generate a wallet on celestia-node.","frontmatter":{"description":"Use the cel-key utility to generate a wallet on celestia-node.","prev":{"text":"New Blobstream X deployments","link":"/developers/blobstream-x-deploy"},"head":[["meta",{"name":"og:title","content":"Create a wallet with celestia-node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/celestia-node-key.md","filePath":"developers/celestia-node-key.md","lastUpdated":1725992025000}'),w={name:"developers/celestia-node-key.md"},P=Object.assign(w,{setup(A){return(f,D)=>(p(),t("div",null,[c,s("div",r,[y,i,s("pre",E,[s("code",null,[d,n(`
 `),s("span",F,[s("span",h,"ghcr.io/celestiaorg/celestia-node:"+l(e(o)["node-latest-tag"])+" ",1),g]),n(`
 `),k])]),s("pre",u,[s("code",null,[C,n(`
 `),s("span",b,[s("span",v,"ghcr.io/celestiaorg/celestia-node:"+l(e(o)["node-latest-tag"])+" ",1),m]),n(`
diff --git a/pr-1699/assets/developers_deploy-on-bubs.md.97e444d7.js b/pr-1699/assets/developers_deploy-on-bubs.md.f7abcbb6.js
similarity index 99%
rename from pr-1699/assets/developers_deploy-on-bubs.md.97e444d7.js
rename to pr-1699/assets/developers_deploy-on-bubs.md.f7abcbb6.js
index fc350cb04a..411007bccb 100644
--- a/pr-1699/assets/developers_deploy-on-bubs.md.97e444d7.js
+++ b/pr-1699/assets/developers_deploy-on-bubs.md.f7abcbb6.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Deploy a smart contract on Bubs testnet","description":"","frontmatter":{"prev":{"text":"Bubs testnet","link":"/developers/bubs-testnet"},"head":[["meta",{"name":"og:title","content":"Deploy a smart contract on Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/deploy-on-bubs.md","filePath":"developers/deploy-on-bubs.md","lastUpdated":1725971357000}'),p={name:"developers/deploy-on-bubs.md"},o=l(`
        Deploy a smart contract on Bubs testnet ​
        In this tutorial, we will deploy a smart contract to the Bubs testnet.
        Dependencies ​
        Setup ​
        First, in your $HOME directory, set up a new project folder for this tutorial and init the project with npm:
        bash
        cd $HOME
+import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Deploy a smart contract on Bubs testnet","description":"","frontmatter":{"prev":{"text":"Bubs testnet","link":"/developers/bubs-testnet"},"head":[["meta",{"name":"og:title","content":"Deploy a smart contract on Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/deploy-on-bubs.md","filePath":"developers/deploy-on-bubs.md","lastUpdated":1725992025000}'),p={name:"developers/deploy-on-bubs.md"},o=l(`
        Deploy a smart contract on Bubs testnet ​
        In this tutorial, we will deploy a smart contract to the Bubs testnet.
        Dependencies ​
        Setup ​
        First, in your $HOME directory, set up a new project folder for this tutorial and init the project with npm:
        bash
        cd $HOME
 mkdir counter-project && cd counter-project && npm init -y
        cd $HOME
 mkdir counter-project && cd counter-project && npm init -y
        Next, initialize a Foundry project with the following command:
        bash
        forge init counter_contract
        forge init counter_contract
        Create your smart contract ​
        Take a look at the Counter.sol file in your counter-project/counter_contract/src directory:
        solidity
        // SPDX-License-Identifier: UNLICENSED
 pragma solidity ^0.8.13;
diff --git a/pr-1699/assets/developers_deploy-on-bubs.md.97e444d7.lean.js b/pr-1699/assets/developers_deploy-on-bubs.md.f7abcbb6.lean.js
similarity index 81%
rename from pr-1699/assets/developers_deploy-on-bubs.md.97e444d7.lean.js
rename to pr-1699/assets/developers_deploy-on-bubs.md.f7abcbb6.lean.js
index 556e122177..7bdc57b24b 100644
--- a/pr-1699/assets/developers_deploy-on-bubs.md.97e444d7.lean.js
+++ b/pr-1699/assets/developers_deploy-on-bubs.md.f7abcbb6.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Deploy a smart contract on Bubs testnet","description":"","frontmatter":{"prev":{"text":"Bubs testnet","link":"/developers/bubs-testnet"},"head":[["meta",{"name":"og:title","content":"Deploy a smart contract on Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/deploy-on-bubs.md","filePath":"developers/deploy-on-bubs.md","lastUpdated":1725971357000}'),p={name:"developers/deploy-on-bubs.md"},o=l("",61),e=[o];function t(c,r,i,y,E,d){return a(),n("div",null,e)}const h=s(p,[["render",t]]);export{F as __pageData,h as default};
+import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Deploy a smart contract on Bubs testnet","description":"","frontmatter":{"prev":{"text":"Bubs testnet","link":"/developers/bubs-testnet"},"head":[["meta",{"name":"og:title","content":"Deploy a smart contract on Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/deploy-on-bubs.md","filePath":"developers/deploy-on-bubs.md","lastUpdated":1725992025000}'),p={name:"developers/deploy-on-bubs.md"},o=l("",61),e=[o];function t(c,r,i,y,E,d){return a(),n("div",null,e)}const h=s(p,[["render",t]]);export{F as __pageData,h as default};
diff --git a/pr-1699/assets/developers_ethereum-fallback.md.00e7ac0b.js b/pr-1699/assets/developers_ethereum-fallback.md.764773da.js
similarity index 97%
rename from pr-1699/assets/developers_ethereum-fallback.md.00e7ac0b.js
rename to pr-1699/assets/developers_ethereum-fallback.md.764773da.js
index 971d57bf75..3405930d63 100644
--- a/pr-1699/assets/developers_ethereum-fallback.md.00e7ac0b.js
+++ b/pr-1699/assets/developers_ethereum-fallback.md.764773da.js
@@ -1 +1 @@
-import{_ as a,o as l,c as r,k as e,a as t}from"./chunks/framework.b47e54aa.js";const s="/docs-preview/pr-1699/img/Celestia_ethereum-fallback.jpg",y=JSON.parse('{"title":"Ethereum fallback","description":"The DA fallback mechanism to Ethereum for rollups.","frontmatter":{"description":"The DA fallback mechanism to Ethereum for rollups.","next":{"text":"Blobstream rollups","link":"/developers/blobstream-rollups"},"prev":{"text":"Run an OP Stack devnet posting Celestia","link":"/developers/optimism"},"head":[["meta",{"name":"og:title","content":"Ethereum fallback | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/ethereum-fallback.md","filePath":"developers/ethereum-fallback.md","lastUpdated":1725971357000}'),n={name:"developers/ethereum-fallback.md"},o=e("h1",{id:"ethereum-fallback",tabindex:"-1"},[t("Ethereum fallback "),e("a",{class:"header-anchor",href:"#ethereum-fallback","aria-label":'Permalink to "Ethereum fallback"'},"​")],-1),i=e("p",null,"Ethereum fallback is a mechanism that enables Ethereum L2s (or L3s) to “fall back” to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta. This feature is currently supported by Celestia integrations with:",-1),c=e("ul",null,[e("li",null,[e("a",{href:"./arbitrum-integration#ethereum-fallback-mechanism-in-nitro"},"Arbitrum Nitro")])],-1),h=e("p",null,"In the case of Celestia downtime or temporary unavailability, L2s can fallback to posting transactions as calldata on Ethereum or another DA layer for data availability instead of posting to Celestia. This mechanism ensures users can continue to transact securely and seamlessly, preventing disruptions and helping to ensure user funds do not get stuck in the L2's bridge on Ethereum.",-1),m=e("p",null,[t("Ethereum fallback is triggered whenever the sequencer has an error sending the "),e("code",null,"PayForBlobs"),t(" transaction on Celestia. Fallback can be triggered due to a congested mempool or nonce error and can be simulated with an error such as low balance or incorrect sequence. Fallback can also be triggered in the event Blobstream stops relaying attestations.")],-1),u=e("p",null,[e("img",{src:s,alt:"Ethereum fallback"})],-1),d=[o,i,c,h,m,u];function p(b,f,k,_,g,v){return l(),r("div",null,d)}const x=a(n,[["render",p]]);export{y as __pageData,x as default};
+import{_ as a,o as l,c as r,k as e,a as t}from"./chunks/framework.b47e54aa.js";const s="/docs-preview/pr-1699/img/Celestia_ethereum-fallback.jpg",y=JSON.parse('{"title":"Ethereum fallback","description":"The DA fallback mechanism to Ethereum for rollups.","frontmatter":{"description":"The DA fallback mechanism to Ethereum for rollups.","next":{"text":"Blobstream rollups","link":"/developers/blobstream-rollups"},"prev":{"text":"Run an OP Stack devnet posting Celestia","link":"/developers/optimism"},"head":[["meta",{"name":"og:title","content":"Ethereum fallback | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/ethereum-fallback.md","filePath":"developers/ethereum-fallback.md","lastUpdated":1725992025000}'),n={name:"developers/ethereum-fallback.md"},o=e("h1",{id:"ethereum-fallback",tabindex:"-1"},[t("Ethereum fallback "),e("a",{class:"header-anchor",href:"#ethereum-fallback","aria-label":'Permalink to "Ethereum fallback"'},"​")],-1),i=e("p",null,"Ethereum fallback is a mechanism that enables Ethereum L2s (or L3s) to “fall back” to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta. This feature is currently supported by Celestia integrations with:",-1),c=e("ul",null,[e("li",null,[e("a",{href:"./arbitrum-integration#ethereum-fallback-mechanism-in-nitro"},"Arbitrum Nitro")])],-1),h=e("p",null,"In the case of Celestia downtime or temporary unavailability, L2s can fallback to posting transactions as calldata on Ethereum or another DA layer for data availability instead of posting to Celestia. This mechanism ensures users can continue to transact securely and seamlessly, preventing disruptions and helping to ensure user funds do not get stuck in the L2's bridge on Ethereum.",-1),m=e("p",null,[t("Ethereum fallback is triggered whenever the sequencer has an error sending the "),e("code",null,"PayForBlobs"),t(" transaction on Celestia. Fallback can be triggered due to a congested mempool or nonce error and can be simulated with an error such as low balance or incorrect sequence. Fallback can also be triggered in the event Blobstream stops relaying attestations.")],-1),u=e("p",null,[e("img",{src:s,alt:"Ethereum fallback"})],-1),d=[o,i,c,h,m,u];function p(b,f,k,_,g,v){return l(),r("div",null,d)}const x=a(n,[["render",p]]);export{y as __pageData,x as default};
diff --git a/pr-1699/assets/developers_ethereum-fallback.md.00e7ac0b.lean.js b/pr-1699/assets/developers_ethereum-fallback.md.764773da.lean.js
similarity index 97%
rename from pr-1699/assets/developers_ethereum-fallback.md.00e7ac0b.lean.js
rename to pr-1699/assets/developers_ethereum-fallback.md.764773da.lean.js
index 971d57bf75..3405930d63 100644
--- a/pr-1699/assets/developers_ethereum-fallback.md.00e7ac0b.lean.js
+++ b/pr-1699/assets/developers_ethereum-fallback.md.764773da.lean.js
@@ -1 +1 @@
-import{_ as a,o as l,c as r,k as e,a as t}from"./chunks/framework.b47e54aa.js";const s="/docs-preview/pr-1699/img/Celestia_ethereum-fallback.jpg",y=JSON.parse('{"title":"Ethereum fallback","description":"The DA fallback mechanism to Ethereum for rollups.","frontmatter":{"description":"The DA fallback mechanism to Ethereum for rollups.","next":{"text":"Blobstream rollups","link":"/developers/blobstream-rollups"},"prev":{"text":"Run an OP Stack devnet posting Celestia","link":"/developers/optimism"},"head":[["meta",{"name":"og:title","content":"Ethereum fallback | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/ethereum-fallback.md","filePath":"developers/ethereum-fallback.md","lastUpdated":1725971357000}'),n={name:"developers/ethereum-fallback.md"},o=e("h1",{id:"ethereum-fallback",tabindex:"-1"},[t("Ethereum fallback "),e("a",{class:"header-anchor",href:"#ethereum-fallback","aria-label":'Permalink to "Ethereum fallback"'},"​")],-1),i=e("p",null,"Ethereum fallback is a mechanism that enables Ethereum L2s (or L3s) to “fall back” to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta. This feature is currently supported by Celestia integrations with:",-1),c=e("ul",null,[e("li",null,[e("a",{href:"./arbitrum-integration#ethereum-fallback-mechanism-in-nitro"},"Arbitrum Nitro")])],-1),h=e("p",null,"In the case of Celestia downtime or temporary unavailability, L2s can fallback to posting transactions as calldata on Ethereum or another DA layer for data availability instead of posting to Celestia. This mechanism ensures users can continue to transact securely and seamlessly, preventing disruptions and helping to ensure user funds do not get stuck in the L2's bridge on Ethereum.",-1),m=e("p",null,[t("Ethereum fallback is triggered whenever the sequencer has an error sending the "),e("code",null,"PayForBlobs"),t(" transaction on Celestia. Fallback can be triggered due to a congested mempool or nonce error and can be simulated with an error such as low balance or incorrect sequence. Fallback can also be triggered in the event Blobstream stops relaying attestations.")],-1),u=e("p",null,[e("img",{src:s,alt:"Ethereum fallback"})],-1),d=[o,i,c,h,m,u];function p(b,f,k,_,g,v){return l(),r("div",null,d)}const x=a(n,[["render",p]]);export{y as __pageData,x as default};
+import{_ as a,o as l,c as r,k as e,a as t}from"./chunks/framework.b47e54aa.js";const s="/docs-preview/pr-1699/img/Celestia_ethereum-fallback.jpg",y=JSON.parse('{"title":"Ethereum fallback","description":"The DA fallback mechanism to Ethereum for rollups.","frontmatter":{"description":"The DA fallback mechanism to Ethereum for rollups.","next":{"text":"Blobstream rollups","link":"/developers/blobstream-rollups"},"prev":{"text":"Run an OP Stack devnet posting Celestia","link":"/developers/optimism"},"head":[["meta",{"name":"og:title","content":"Ethereum fallback | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/ethereum-fallback.md","filePath":"developers/ethereum-fallback.md","lastUpdated":1725992025000}'),n={name:"developers/ethereum-fallback.md"},o=e("h1",{id:"ethereum-fallback",tabindex:"-1"},[t("Ethereum fallback "),e("a",{class:"header-anchor",href:"#ethereum-fallback","aria-label":'Permalink to "Ethereum fallback"'},"​")],-1),i=e("p",null,"Ethereum fallback is a mechanism that enables Ethereum L2s (or L3s) to “fall back” to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta. This feature is currently supported by Celestia integrations with:",-1),c=e("ul",null,[e("li",null,[e("a",{href:"./arbitrum-integration#ethereum-fallback-mechanism-in-nitro"},"Arbitrum Nitro")])],-1),h=e("p",null,"In the case of Celestia downtime or temporary unavailability, L2s can fallback to posting transactions as calldata on Ethereum or another DA layer for data availability instead of posting to Celestia. This mechanism ensures users can continue to transact securely and seamlessly, preventing disruptions and helping to ensure user funds do not get stuck in the L2's bridge on Ethereum.",-1),m=e("p",null,[t("Ethereum fallback is triggered whenever the sequencer has an error sending the "),e("code",null,"PayForBlobs"),t(" transaction on Celestia. Fallback can be triggered due to a congested mempool or nonce error and can be simulated with an error such as low balance or incorrect sequence. Fallback can also be triggered in the event Blobstream stops relaying attestations.")],-1),u=e("p",null,[e("img",{src:s,alt:"Ethereum fallback"})],-1),d=[o,i,c,h,m,u];function p(b,f,k,_,g,v){return l(),r("div",null,d)}const x=a(n,[["render",p]]);export{y as __pageData,x as default};
diff --git a/pr-1699/assets/developers_feegrant-for-blobs.md.7c93aaff.js b/pr-1699/assets/developers_feegrant-for-blobs.md.84d98514.js
similarity index 99%
rename from pr-1699/assets/developers_feegrant-for-blobs.md.7c93aaff.js
rename to pr-1699/assets/developers_feegrant-for-blobs.md.84d98514.js
index e13cba531c..f046b217f4 100644
--- a/pr-1699/assets/developers_feegrant-for-blobs.md.7c93aaff.js
+++ b/pr-1699/assets/developers_feegrant-for-blobs.md.84d98514.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"FeeGrant module for blobs submission","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"FeeGrant module for blobs submission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/feegrant-for-blobs.md","filePath":"developers/feegrant-for-blobs.md","lastUpdated":1725971357000}'),o={name:"developers/feegrant-for-blobs.md"},l=e(`
        FeeGrant module for blobs submission ​
        Overview ​
        This guide provides developers with the knowledge to use the FeeGrant module on the Celestia's Mocha testnet chain for granting a data availability node's account to submit blobs without constantly funding it, enabling a third-party account to cover the transaction fees.
        Pre-requisites ​
        • celestia-node binary (celestia) installed
        • Access to a Mocha node (e.g., https://rpc.celestia-mocha.com:443)
        • Running DA Light node on Mocha testnet
        • One account with sufficient funds, the "granter"
        • One account with no funds, the "grantee"
        Introduction ​
        Each DA node contains a Celestia account that is used to pay for blobs submissions. To unify the fee payment process, the FeeGrant module allows a third-party account (granter) to pay for the fees incurred by a DA node's (grantee) account. You will need one account that will contain the funds, the granter, and another account that will be in the DA node you run to post blobs, the grantee. You will see the DA node's account once you initialize the node. Learn more about managing accounts with cel-key in create a wallet with celestia-node.
        Granting fee allowances using celestia-node ​
        To get started granting the fee allowance, you will need two separate keys to run the light node with. One to begin the FeeGrant as the granter and another to use the FeeGrant as the grantee.
        Set some variables for your accounts for the remainder of the guide:
        bash
        export GRANTER_ADDRESS=<your-granter-account-address>
+import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"FeeGrant module for blobs submission","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"FeeGrant module for blobs submission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/feegrant-for-blobs.md","filePath":"developers/feegrant-for-blobs.md","lastUpdated":1725992025000}'),o={name:"developers/feegrant-for-blobs.md"},l=e(`
        FeeGrant module for blobs submission ​
        Overview ​
        This guide provides developers with the knowledge to use the FeeGrant module on the Celestia's Mocha testnet chain for granting a data availability node's account to submit blobs without constantly funding it, enabling a third-party account to cover the transaction fees.
        Pre-requisites ​
        • celestia-node binary (celestia) installed
        • Access to a Mocha node (e.g., https://rpc.celestia-mocha.com:443)
        • Running DA Light node on Mocha testnet
        • One account with sufficient funds, the "granter"
        • One account with no funds, the "grantee"
        Introduction ​
        Each DA node contains a Celestia account that is used to pay for blobs submissions. To unify the fee payment process, the FeeGrant module allows a third-party account (granter) to pay for the fees incurred by a DA node's (grantee) account. You will need one account that will contain the funds, the granter, and another account that will be in the DA node you run to post blobs, the grantee. You will see the DA node's account once you initialize the node. Learn more about managing accounts with cel-key in create a wallet with celestia-node.
        Granting fee allowances using celestia-node ​
        To get started granting the fee allowance, you will need two separate keys to run the light node with. One to begin the FeeGrant as the granter and another to use the FeeGrant as the grantee.
        Set some variables for your accounts for the remainder of the guide:
        bash
        export GRANTER_ADDRESS=<your-granter-account-address>
 export GRANTEE_ADDRESS=<your-grantee-account-address>
 export RPC_URL=rpc.celestia-mocha.com
        export GRANTER_ADDRESS=<your-granter-account-address>
 export GRANTEE_ADDRESS=<your-grantee-account-address>
diff --git a/pr-1699/assets/developers_feegrant-for-blobs.md.7c93aaff.lean.js b/pr-1699/assets/developers_feegrant-for-blobs.md.84d98514.lean.js
similarity index 79%
rename from pr-1699/assets/developers_feegrant-for-blobs.md.7c93aaff.lean.js
rename to pr-1699/assets/developers_feegrant-for-blobs.md.84d98514.lean.js
index 620cca6590..1995f11909 100644
--- a/pr-1699/assets/developers_feegrant-for-blobs.md.7c93aaff.lean.js
+++ b/pr-1699/assets/developers_feegrant-for-blobs.md.84d98514.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"FeeGrant module for blobs submission","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"FeeGrant module for blobs submission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/feegrant-for-blobs.md","filePath":"developers/feegrant-for-blobs.md","lastUpdated":1725971357000}'),o={name:"developers/feegrant-for-blobs.md"},l=e("",54),p=[l];function t(c,r,i,E,y,d){return a(),n("div",null,p)}const g=s(o,[["render",t]]);export{h as __pageData,g as default};
+import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"FeeGrant module for blobs submission","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"FeeGrant module for blobs submission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/feegrant-for-blobs.md","filePath":"developers/feegrant-for-blobs.md","lastUpdated":1725992025000}'),o={name:"developers/feegrant-for-blobs.md"},l=e("",54),p=[l];function t(c,r,i,E,y,d){return a(),n("div",null,p)}const g=s(o,[["render",t]]);export{h as __pageData,g as default};
diff --git a/pr-1699/assets/developers_full-stack-modular-development-guide.md.3910bdad.js b/pr-1699/assets/developers_full-stack-modular-development-guide.md.766923fe.js
similarity index 99%
rename from pr-1699/assets/developers_full-stack-modular-development-guide.md.3910bdad.js
rename to pr-1699/assets/developers_full-stack-modular-development-guide.md.766923fe.js
index b4e63f8268..c77ff1ffd1 100644
--- a/pr-1699/assets/developers_full-stack-modular-development-guide.md.3910bdad.js
+++ b/pr-1699/assets/developers_full-stack-modular-development-guide.md.766923fe.js
@@ -1,4 +1,4 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Full stack modular blockchain development guide","description":"Learn to build a full stack modular dapp.","frontmatter":{"description":"Learn to build a full stack modular dapp.","head":[["meta",{"name":"og:title","content":"Full stack modular blockchain development guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/full-stack-modular-development-guide.md","filePath":"developers/full-stack-modular-development-guide.md","lastUpdated":1725971357000}'),p={name:"developers/full-stack-modular-development-guide.md"},o=l(`
        Full stack modular blockchain development guide ​
        Note
        This tutorial needs to be updated
        This guide will introduce you to modular blockchains like Celestia, explain their benefits, and show you how to build a full stack modular dapp with React, Vite, RainbowKit, Celestia, and Foundry.
        Current blockchain architectures are not scalable and face challenges around accessibility. In order for blockchains and web3 to reach mass adoption, these challenges must be addressed.
        Blockchains have evolved over time from application-specific networks like Bitcoin to shared smart contract platforms like Ethereum. This guide will cover how to build dapps on these newer, shared platforms.
        If you're interested in learning more about modular blockchains, or are new to the Celestia ecosystem, we recommend you read the build whatever page first.
        Getting started ​
        Now that you’ve had an overview of what Celestia is, let’s start building!
        The execution environment that we’ll be leveraging today is Ethermint, an EVM-compatible testnet that you will run locally for this tutorial.
        Pre-requisites ​
        Project setup ​
        To get started, create a new Foundry project:
        bash
        forge init celestia-dapp
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Full stack modular blockchain development guide","description":"Learn to build a full stack modular dapp.","frontmatter":{"description":"Learn to build a full stack modular dapp.","head":[["meta",{"name":"og:title","content":"Full stack modular blockchain development guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/full-stack-modular-development-guide.md","filePath":"developers/full-stack-modular-development-guide.md","lastUpdated":1725992025000}'),p={name:"developers/full-stack-modular-development-guide.md"},o=l(`
        Full stack modular blockchain development guide ​
        Note
        This tutorial needs to be updated
        This guide will introduce you to modular blockchains like Celestia, explain their benefits, and show you how to build a full stack modular dapp with React, Vite, RainbowKit, Celestia, and Foundry.
        Current blockchain architectures are not scalable and face challenges around accessibility. In order for blockchains and web3 to reach mass adoption, these challenges must be addressed.
        Blockchains have evolved over time from application-specific networks like Bitcoin to shared smart contract platforms like Ethereum. This guide will cover how to build dapps on these newer, shared platforms.
        If you're interested in learning more about modular blockchains, or are new to the Celestia ecosystem, we recommend you read the build whatever page first.
        Getting started ​
        Now that you’ve had an overview of what Celestia is, let’s start building!
        The execution environment that we’ll be leveraging today is Ethermint, an EVM-compatible testnet that you will run locally for this tutorial.
        Pre-requisites ​
        Project setup ​
        To get started, create a new Foundry project:
        bash
        forge init celestia-dapp
 cd celestia-dapp
        forge init celestia-dapp
 cd celestia-dapp
        Foundry has created an example smart contract located at src/Contract.sol.
        Updating the contract and tests ​
        Let's update the contracts to include a basic blog example. Create a new file in the src directory named Contract.sol with the following code:
        solidity
        // SPDX-License-Identifier: MIT
 pragma solidity ^0.8.13;
diff --git a/pr-1699/assets/developers_full-stack-modular-development-guide.md.3910bdad.lean.js b/pr-1699/assets/developers_full-stack-modular-development-guide.md.766923fe.lean.js
similarity index 92%
rename from pr-1699/assets/developers_full-stack-modular-development-guide.md.3910bdad.lean.js
rename to pr-1699/assets/developers_full-stack-modular-development-guide.md.766923fe.lean.js
index 63b5d9c177..66f59ebfa8 100644
--- a/pr-1699/assets/developers_full-stack-modular-development-guide.md.3910bdad.lean.js
+++ b/pr-1699/assets/developers_full-stack-modular-development-guide.md.766923fe.lean.js
@@ -1 +1 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Full stack modular blockchain development guide","description":"Learn to build a full stack modular dapp.","frontmatter":{"description":"Learn to build a full stack modular dapp.","head":[["meta",{"name":"og:title","content":"Full stack modular blockchain development guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/full-stack-modular-development-guide.md","filePath":"developers/full-stack-modular-development-guide.md","lastUpdated":1725971357000}'),p={name:"developers/full-stack-modular-development-guide.md"},o=l("",113),e=[o];function t(c,r,E,y,i,F){return n(),a("div",null,e)}const h=s(p,[["render",t]]);export{u as __pageData,h as default};
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Full stack modular blockchain development guide","description":"Learn to build a full stack modular dapp.","frontmatter":{"description":"Learn to build a full stack modular dapp.","head":[["meta",{"name":"og:title","content":"Full stack modular blockchain development guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/full-stack-modular-development-guide.md","filePath":"developers/full-stack-modular-development-guide.md","lastUpdated":1725992025000}'),p={name:"developers/full-stack-modular-development-guide.md"},o=l("",113),e=[o];function t(c,r,E,y,i,F){return n(),a("div",null,e)}const h=s(p,[["render",t]]);export{u as __pageData,h as default};
diff --git a/pr-1699/assets/developers_gm-portal-bubs.md.2e8017d7.js b/pr-1699/assets/developers_gm-portal-bubs.md.cd727490.js
similarity index 99%
rename from pr-1699/assets/developers_gm-portal-bubs.md.2e8017d7.js
rename to pr-1699/assets/developers_gm-portal-bubs.md.cd727490.js
index adeb862e07..a7e6d67716 100644
--- a/pr-1699/assets/developers_gm-portal-bubs.md.2e8017d7.js
+++ b/pr-1699/assets/developers_gm-portal-bubs.md.cd727490.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const p="/docs-preview/pr-1699/img/gm_contract.png",t="/docs-preview/pr-1699/img/gm_bubs.png",F=JSON.parse('{"title":"Deploying a dapp on Bubs testnet","description":"Make your own GM Portal dapp on the OP Stack.","frontmatter":{"description":"Make your own GM Portal dapp on the OP Stack.","head":[["meta",{"name":"og:title","content":"Deploying a dapp on Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/gm-portal-bubs.md","filePath":"developers/gm-portal-bubs.md","lastUpdated":1725971357000}'),e={name:"developers/gm-portal-bubs.md"},l=o(`
        Deploying a dapp on Bubs testnet ​
        First, review the Bubs testnet page and the Deploy a smart contract to Bubs testnet tutorial.
        You will need a funded account to deploy your smart contract.
        Next, clone the gm-portal from Github and start the frontend:
        bash
        cd $HOME
+import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const p="/docs-preview/pr-1699/img/gm_contract.png",t="/docs-preview/pr-1699/img/gm_bubs.png",F=JSON.parse('{"title":"Deploying a dapp on Bubs testnet","description":"Make your own GM Portal dapp on the OP Stack.","frontmatter":{"description":"Make your own GM Portal dapp on the OP Stack.","head":[["meta",{"name":"og:title","content":"Deploying a dapp on Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/gm-portal-bubs.md","filePath":"developers/gm-portal-bubs.md","lastUpdated":1725992025000}'),e={name:"developers/gm-portal-bubs.md"},l=o(`
        Deploying a dapp on Bubs testnet ​
        First, review the Bubs testnet page and the Deploy a smart contract to Bubs testnet tutorial.
        You will need a funded account to deploy your smart contract.
        Next, clone the gm-portal from Github and start the frontend:
        bash
        cd $HOME
 git clone https://github.com/jcstein/gm-portal.git
 cd gm-portal/frontend
 yarn && yarn dev
        cd $HOME
diff --git a/pr-1699/assets/developers_gm-portal-bubs.md.2e8017d7.lean.js b/pr-1699/assets/developers_gm-portal-bubs.md.cd727490.lean.js
similarity index 92%
rename from pr-1699/assets/developers_gm-portal-bubs.md.2e8017d7.lean.js
rename to pr-1699/assets/developers_gm-portal-bubs.md.cd727490.lean.js
index 862c66a069..efd815a2d1 100644
--- a/pr-1699/assets/developers_gm-portal-bubs.md.2e8017d7.lean.js
+++ b/pr-1699/assets/developers_gm-portal-bubs.md.cd727490.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const p="/docs-preview/pr-1699/img/gm_contract.png",t="/docs-preview/pr-1699/img/gm_bubs.png",F=JSON.parse('{"title":"Deploying a dapp on Bubs testnet","description":"Make your own GM Portal dapp on the OP Stack.","frontmatter":{"description":"Make your own GM Portal dapp on the OP Stack.","head":[["meta",{"name":"og:title","content":"Deploying a dapp on Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/gm-portal-bubs.md","filePath":"developers/gm-portal-bubs.md","lastUpdated":1725971357000}'),e={name:"developers/gm-portal-bubs.md"},l=o("",32),c=[l];function r(i,y,d,E,h,u){return a(),n("div",null,c)}const b=s(e,[["render",r]]);export{F as __pageData,b as default};
+import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const p="/docs-preview/pr-1699/img/gm_contract.png",t="/docs-preview/pr-1699/img/gm_bubs.png",F=JSON.parse('{"title":"Deploying a dapp on Bubs testnet","description":"Make your own GM Portal dapp on the OP Stack.","frontmatter":{"description":"Make your own GM Portal dapp on the OP Stack.","head":[["meta",{"name":"og:title","content":"Deploying a dapp on Bubs testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/gm-portal-bubs.md","filePath":"developers/gm-portal-bubs.md","lastUpdated":1725992025000}'),e={name:"developers/gm-portal-bubs.md"},l=o("",32),c=[l];function r(i,y,d,E,h,u){return a(),n("div",null,c)}const b=s(e,[["render",r]]);export{F as __pageData,b as default};
diff --git a/pr-1699/assets/developers_golang-client-tutorial.md.0dce1977.js b/pr-1699/assets/developers_golang-client-tutorial.md.727ea5e8.js
similarity index 99%
rename from pr-1699/assets/developers_golang-client-tutorial.md.0dce1977.js
rename to pr-1699/assets/developers_golang-client-tutorial.md.727ea5e8.js
index aff50fbb70..e8b785c66c 100644
--- a/pr-1699/assets/developers_golang-client-tutorial.md.0dce1977.js
+++ b/pr-1699/assets/developers_golang-client-tutorial.md.727ea5e8.js
@@ -1,4 +1,4 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Golang client library tutorial","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Golang client library tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/golang-client-tutorial.md","filePath":"developers/golang-client-tutorial.md","lastUpdated":1725971357000}'),p={name:"developers/golang-client-tutorial.md"},o=l(`
        Golang client library tutorial ​
        This section tutorial will guide you through using the most common RPC endpoints with the golang client library.
        Install dependencies and celestia-node if you have not already.
        Project setup ​
        To start, add celestia-openrpc as a dependency to your project:
        bash
        go get github.com/celestiaorg/celestia-openrpc
        go get github.com/celestiaorg/celestia-openrpc
        To use the following methods, you will need the node URL and your auth token. To get your auth token, see this guide. To run your node without an auth token, you can use the --rpc.skip-auth flag when starting your node. This allows you to pass an empty string as your auth token.
        The default URL is http://localhost:26658. If you would like to use subscription methods, such as SubscribeHeaders below, you must use the ws protocol in place of http: ws://localhost:26658.
        Submitting and retrieving blobs ​
        The blob.Submit method takes a slice of blobs and a gas price, returning the height the blob was successfully posted at.
        • The namespace can be generated with share.NewBlobNamespaceV0.
        • The blobs can be generated with blob.NewBlobV0.
        • You can use blob.NewSubmitOptions(), which has celestia-node automatically determine an appropriate gas price. To set your own gas price, use blob.NewSubmitOptions().WithGasPrice(X). The available options are WithGasPrice, WithGas, WithKeyName, WithSignerAddress, and WithFeeGranterAddress.
        The blob.GetAll method takes a height and slice of namespaces, returning the slice of blobs found in the given namespaces.
        go
        import (
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Golang client library tutorial","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Golang client library tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/golang-client-tutorial.md","filePath":"developers/golang-client-tutorial.md","lastUpdated":1725992025000}'),p={name:"developers/golang-client-tutorial.md"},o=l(`
        Golang client library tutorial ​
        This section tutorial will guide you through using the most common RPC endpoints with the golang client library.
        Install dependencies and celestia-node if you have not already.
        Project setup ​
        To start, add celestia-openrpc as a dependency to your project:
        bash
        go get github.com/celestiaorg/celestia-openrpc
        go get github.com/celestiaorg/celestia-openrpc
        To use the following methods, you will need the node URL and your auth token. To get your auth token, see this guide. To run your node without an auth token, you can use the --rpc.skip-auth flag when starting your node. This allows you to pass an empty string as your auth token.
        The default URL is http://localhost:26658. If you would like to use subscription methods, such as SubscribeHeaders below, you must use the ws protocol in place of http: ws://localhost:26658.
        Submitting and retrieving blobs ​
        The blob.Submit method takes a slice of blobs and a gas price, returning the height the blob was successfully posted at.
        • The namespace can be generated with share.NewBlobNamespaceV0.
        • The blobs can be generated with blob.NewBlobV0.
        • You can use blob.NewSubmitOptions(), which has celestia-node automatically determine an appropriate gas price. To set your own gas price, use blob.NewSubmitOptions().WithGasPrice(X). The available options are WithGasPrice, WithGas, WithKeyName, WithSignerAddress, and WithFeeGranterAddress.
        The blob.GetAll method takes a height and slice of namespaces, returning the slice of blobs found in the given namespaces.
        go
        import (
 	"bytes"
 	"context"
 	"fmt"
diff --git a/pr-1699/assets/developers_golang-client-tutorial.md.0dce1977.lean.js b/pr-1699/assets/developers_golang-client-tutorial.md.727ea5e8.lean.js
similarity index 89%
rename from pr-1699/assets/developers_golang-client-tutorial.md.0dce1977.lean.js
rename to pr-1699/assets/developers_golang-client-tutorial.md.727ea5e8.lean.js
index 7d0e285bb6..d8386114f8 100644
--- a/pr-1699/assets/developers_golang-client-tutorial.md.0dce1977.lean.js
+++ b/pr-1699/assets/developers_golang-client-tutorial.md.727ea5e8.lean.js
@@ -1 +1 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Golang client library tutorial","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Golang client library tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/golang-client-tutorial.md","filePath":"developers/golang-client-tutorial.md","lastUpdated":1725971357000}'),p={name:"developers/golang-client-tutorial.md"},o=l("",24),e=[o];function t(r,c,E,y,i,F){return n(),a("div",null,e)}const u=s(p,[["render",t]]);export{b as __pageData,u as default};
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Golang client library tutorial","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Golang client library tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/golang-client-tutorial.md","filePath":"developers/golang-client-tutorial.md","lastUpdated":1725992025000}'),p={name:"developers/golang-client-tutorial.md"},o=l("",24),e=[o];function t(r,c,E,y,i,F){return n(),a("div",null,e)}const u=s(p,[["render",t]]);export{b as __pageData,u as default};
diff --git a/pr-1699/assets/developers_integrate-celestia.md.871c3298.js b/pr-1699/assets/developers_integrate-celestia.md.cabcfa45.js
similarity index 98%
rename from pr-1699/assets/developers_integrate-celestia.md.871c3298.js
rename to pr-1699/assets/developers_integrate-celestia.md.cabcfa45.js
index b1e44f1f8c..383393fd5d 100644
--- a/pr-1699/assets/developers_integrate-celestia.md.871c3298.js
+++ b/pr-1699/assets/developers_integrate-celestia.md.cabcfa45.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Integrate Celestia for service providers","description":"Learn how service providers can integrate with the Celestia network.","frontmatter":{"description":"Learn how service providers can integrate with the Celestia network.","prev":{"text":"Integrating Cosmostation for developers","link":"/developers/cosmostation"},"head":[["meta",{"name":"og:title","content":"Integrate Celestia for service providers | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/integrate-celestia.md","filePath":"developers/integrate-celestia.md","lastUpdated":1725971357000}'),r={name:"developers/integrate-celestia.md"},n=i('
        Integrate Celestia for service providers ​
        This document is for third-party service providers, such as custodians and explorers, integrating the Celestia network.
        Getting started ​
        When getting started Celestia, we recommend checking out these resources first:
        Celestia service provider notes ​
        Celestia is a fairly standard Cosmos-SDK based chain. We use the latest version of Tendermint and the Cosmos-SDK, with only minor modifications to each. This means that we are:
        • Using the default Cosmos-SDK modules: auth, bank, distribution, staking, slashing, mint, crisis, ibchost, genutil, evidence, ibctransfer, params, gov (limited in some TBD capacities), upgrade, vesting, feegrant, capability, and payment.
        • Use the standard digital keys schemes provided by the Cosmos-SDK and Tendermint, those being secp256k1 for user transactions, and tm-ed25519 for signing and verifying consensus messages.
        While exactly which modules used is subject to change, Celestia aims to be as minimal as possible.
        Custody and key management ​
        Celestia supports many already existing key management systems, as we rely on the Cosmos-SDK and Tendermint libraries for signing and verifying transactions. Learn more in the Cosmos-SDK documentation
        RPC and querying ​
        In celestia-app, only the standard RPC endpoints for Tendermint and the Cosmos-SDK are exposed. We do not currently add or subtract any core functionality, but this could change in the future. The same goes for querying data from the chain.
        In celestia-node, the Data Availability node client, there is a JSON-RPC API that allows you to interact directly with Celestia's Data Availability layer. Learn how to use the API in this tutorial.
        Compatibility ​
        Linux, particularly Ubuntu 20.04 LTS, is the most well tested. Potentially compatible with other OSs, but they are currently untested. Some of the cryptography libraries used for erasure data are not guaranteed to work on other platforms.
        Syncing ​
        Since we utilize Tendermint and the Cosmos-SDK, syncing the chain can be performed by any method that is supported by those libraries. This includes fast-sync, state sync, and quick sync.
        Notable exceptions relative to other blockchains ​
        Relative to other Tendermint based chains, Celestia will have significantly longer blocktimes of roughly 12* seconds. The reason behind this block time is to optimize the bandwidth used by light clients that are sampling the chain, and is not because we have modified Tendermint consensus in any meaningful way. Validators will likely download/upload relatively large blocks. It should be noted that while these blocks are large, very little typical blockchain state execution is actually occurring on Celestia. Meaning that the bandwidth requirements will likely be larger than that of a typical Cosmos-SDK based blockchain full node, the computing requirements should be similar in magnitude.
        *Subject to Change
        ',21),s=[n];function o(l,d,c,h,u,m){return t(),a("div",null,s)}const b=e(r,[["render",o]]);export{g as __pageData,b as default};
+import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Integrate Celestia for service providers","description":"Learn how service providers can integrate with the Celestia network.","frontmatter":{"description":"Learn how service providers can integrate with the Celestia network.","prev":{"text":"Integrating Cosmostation for developers","link":"/developers/cosmostation"},"head":[["meta",{"name":"og:title","content":"Integrate Celestia for service providers | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/integrate-celestia.md","filePath":"developers/integrate-celestia.md","lastUpdated":1725992025000}'),r={name:"developers/integrate-celestia.md"},n=i('
        Integrate Celestia for service providers ​
        This document is for third-party service providers, such as custodians and explorers, integrating the Celestia network.
        Getting started ​
        When getting started Celestia, we recommend checking out these resources first:
        Celestia service provider notes ​
        Celestia is a fairly standard Cosmos-SDK based chain. We use the latest version of Tendermint and the Cosmos-SDK, with only minor modifications to each. This means that we are:
        • Using the default Cosmos-SDK modules: auth, bank, distribution, staking, slashing, mint, crisis, ibchost, genutil, evidence, ibctransfer, params, gov (limited in some TBD capacities), upgrade, vesting, feegrant, capability, and payment.
        • Use the standard digital keys schemes provided by the Cosmos-SDK and Tendermint, those being secp256k1 for user transactions, and tm-ed25519 for signing and verifying consensus messages.
        While exactly which modules used is subject to change, Celestia aims to be as minimal as possible.
        Custody and key management ​
        Celestia supports many already existing key management systems, as we rely on the Cosmos-SDK and Tendermint libraries for signing and verifying transactions. Learn more in the Cosmos-SDK documentation
        RPC and querying ​
        In celestia-app, only the standard RPC endpoints for Tendermint and the Cosmos-SDK are exposed. We do not currently add or subtract any core functionality, but this could change in the future. The same goes for querying data from the chain.
        In celestia-node, the Data Availability node client, there is a JSON-RPC API that allows you to interact directly with Celestia's Data Availability layer. Learn how to use the API in this tutorial.
        Compatibility ​
        Linux, particularly Ubuntu 20.04 LTS, is the most well tested. Potentially compatible with other OSs, but they are currently untested. Some of the cryptography libraries used for erasure data are not guaranteed to work on other platforms.
        Syncing ​
        Since we utilize Tendermint and the Cosmos-SDK, syncing the chain can be performed by any method that is supported by those libraries. This includes fast-sync, state sync, and quick sync.
        Notable exceptions relative to other blockchains ​
        Relative to other Tendermint based chains, Celestia will have significantly longer blocktimes of roughly 12* seconds. The reason behind this block time is to optimize the bandwidth used by light clients that are sampling the chain, and is not because we have modified Tendermint consensus in any meaningful way. Validators will likely download/upload relatively large blocks. It should be noted that while these blocks are large, very little typical blockchain state execution is actually occurring on Celestia. Meaning that the bandwidth requirements will likely be larger than that of a typical Cosmos-SDK based blockchain full node, the computing requirements should be similar in magnitude.
        *Subject to Change
        ',21),s=[n];function o(l,d,c,h,u,m){return t(),a("div",null,s)}const b=e(r,[["render",o]]);export{g as __pageData,b as default};
diff --git a/pr-1699/assets/developers_integrate-celestia.md.871c3298.lean.js b/pr-1699/assets/developers_integrate-celestia.md.cabcfa45.lean.js
similarity index 92%
rename from pr-1699/assets/developers_integrate-celestia.md.871c3298.lean.js
rename to pr-1699/assets/developers_integrate-celestia.md.cabcfa45.lean.js
index 7fc4574e8e..5ef3c7c3b0 100644
--- a/pr-1699/assets/developers_integrate-celestia.md.871c3298.lean.js
+++ b/pr-1699/assets/developers_integrate-celestia.md.cabcfa45.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Integrate Celestia for service providers","description":"Learn how service providers can integrate with the Celestia network.","frontmatter":{"description":"Learn how service providers can integrate with the Celestia network.","prev":{"text":"Integrating Cosmostation for developers","link":"/developers/cosmostation"},"head":[["meta",{"name":"og:title","content":"Integrate Celestia for service providers | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/integrate-celestia.md","filePath":"developers/integrate-celestia.md","lastUpdated":1725971357000}'),r={name:"developers/integrate-celestia.md"},n=i("",21),s=[n];function o(l,d,c,h,u,m){return t(),a("div",null,s)}const b=e(r,[["render",o]]);export{g as __pageData,b as default};
+import{_ as e,o as t,c as a,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Integrate Celestia for service providers","description":"Learn how service providers can integrate with the Celestia network.","frontmatter":{"description":"Learn how service providers can integrate with the Celestia network.","prev":{"text":"Integrating Cosmostation for developers","link":"/developers/cosmostation"},"head":[["meta",{"name":"og:title","content":"Integrate Celestia for service providers | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/integrate-celestia.md","filePath":"developers/integrate-celestia.md","lastUpdated":1725992025000}'),r={name:"developers/integrate-celestia.md"},n=i("",21),s=[n];function o(l,d,c,h,u,m){return t(),a("div",null,s)}const b=e(r,[["render",o]]);export{g as __pageData,b as default};
diff --git a/pr-1699/assets/developers_intro-to-op-stack.md.c09be10b.js b/pr-1699/assets/developers_intro-to-op-stack.md.2deb5540.js
similarity index 98%
rename from pr-1699/assets/developers_intro-to-op-stack.md.c09be10b.js
rename to pr-1699/assets/developers_intro-to-op-stack.md.2deb5540.js
index 2947a14e47..040ea1287f 100644
--- a/pr-1699/assets/developers_intro-to-op-stack.md.c09be10b.js
+++ b/pr-1699/assets/developers_intro-to-op-stack.md.2deb5540.js
@@ -1 +1 @@
-import{_ as t,o as e,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Introduction to OP Stack integration","description":"Learn about the integration of OP Stack with Celestia.","frontmatter":{"description":"Learn about the integration of OP Stack with Celestia.","prev":{"text":"Deploy a dapp on your Arbitrum rollup devnet","link":"/developers/arbitrum-dapp-deploy"},"head":[["meta",{"name":"og:title","content":"Introduction to OP Stack integration | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/intro-to-op-stack.md","filePath":"developers/intro-to-op-stack.md","lastUpdated":1725971357000}'),i={name:"developers/intro-to-op-stack.md"},r=o('
        Introduction to OP Stack integration ​
        Optimism is a low-cost and lightning-fast Ethereum L2 blockchain, built with the OP Stack.
        Celestia is a modular consensus and data availability (DA) network, built to enable anyone to easily deploy their own blockchain with minimal overhead.
        Together, they allow developers to create rollups that post data to Celestia and settle on Ethereum.
        About the integration ​
        Optimism uses Ethereum as a DA layer. Currently, settlement and DA for Optimism are on Ethereum, both onchain. op-batcher batches up rollup blocks and posts to Ethereum.
        The integration of OP Stack with Celestia underneath for DA allows rollup operators to reduce overhead that is associated with posting data as calldata on Ethereum. Instead, op-batcher batches up rollup blocks and posts them to Celestia's DA network.
        Data is managed in two ways. First, data is written to the data availability (DA) layer i.e. in this case Celestia, then the data commitment is written to the op-batcher. When reading op-node simply reads the data back from the DA layer by reading the data commitment from the op-batcher first, then reading the data from the DA layer using the data commitment. While previously op-node was reading from calldata on Ethereum, it now reads data from Celestia.
        There are a few tools involved in the data handling process. op-batcher batches up rollup blocks and posts them to Ethereum. op-geth handles execution, while op-proposer is responsible for state commitment submission.
        By using Celestia as a DA layer, existing L2s can switch from posting their data as calldata on Ethereum, to posting to Celestia. The commitment to the block is posted on Celestia, which is purpose-built for data availability. This is a more scalable than the traditional method of posting this data as calldata on monolithic chains.
        GitHub repository ​
        Find the repository for this integration at https://github.com/celestiaorg/optimism.
        WARNING
        This is a beta integration and we are working on resolving open issues.
        Category contents ​
        This category will guide you through interacting with existing OP Stack rollups with Celestia underneath, then how to start your own devnet with a modified version of optimism-bedrock that uses Celestia as a DA layer.
        Next steps ​
        Now that you understand the integration, you can start learning about the Bubs testnet, built with OP Stack and Celestia! This testnet is a great way to explore the possibilities of this integration and test your applications in a live environment.
        ',18),n=[r];function s(l,h,c,d,p,u){return e(),a("div",null,n)}const g=t(i,[["render",s]]);export{b as __pageData,g as default};
+import{_ as t,o as e,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Introduction to OP Stack integration","description":"Learn about the integration of OP Stack with Celestia.","frontmatter":{"description":"Learn about the integration of OP Stack with Celestia.","prev":{"text":"Deploy a dapp on your Arbitrum rollup devnet","link":"/developers/arbitrum-dapp-deploy"},"head":[["meta",{"name":"og:title","content":"Introduction to OP Stack integration | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/intro-to-op-stack.md","filePath":"developers/intro-to-op-stack.md","lastUpdated":1725992025000}'),i={name:"developers/intro-to-op-stack.md"},r=o('
        Introduction to OP Stack integration ​
        Optimism is a low-cost and lightning-fast Ethereum L2 blockchain, built with the OP Stack.
        Celestia is a modular consensus and data availability (DA) network, built to enable anyone to easily deploy their own blockchain with minimal overhead.
        Together, they allow developers to create rollups that post data to Celestia and settle on Ethereum.
        About the integration ​
        Optimism uses Ethereum as a DA layer. Currently, settlement and DA for Optimism are on Ethereum, both onchain. op-batcher batches up rollup blocks and posts to Ethereum.
        The integration of OP Stack with Celestia underneath for DA allows rollup operators to reduce overhead that is associated with posting data as calldata on Ethereum. Instead, op-batcher batches up rollup blocks and posts them to Celestia's DA network.
        Data is managed in two ways. First, data is written to the data availability (DA) layer i.e. in this case Celestia, then the data commitment is written to the op-batcher. When reading op-node simply reads the data back from the DA layer by reading the data commitment from the op-batcher first, then reading the data from the DA layer using the data commitment. While previously op-node was reading from calldata on Ethereum, it now reads data from Celestia.
        There are a few tools involved in the data handling process. op-batcher batches up rollup blocks and posts them to Ethereum. op-geth handles execution, while op-proposer is responsible for state commitment submission.
        By using Celestia as a DA layer, existing L2s can switch from posting their data as calldata on Ethereum, to posting to Celestia. The commitment to the block is posted on Celestia, which is purpose-built for data availability. This is a more scalable than the traditional method of posting this data as calldata on monolithic chains.
        GitHub repository ​
        Find the repository for this integration at https://github.com/celestiaorg/optimism.
        WARNING
        This is a beta integration and we are working on resolving open issues.
        Category contents ​
        This category will guide you through interacting with existing OP Stack rollups with Celestia underneath, then how to start your own devnet with a modified version of optimism-bedrock that uses Celestia as a DA layer.
        Next steps ​
        Now that you understand the integration, you can start learning about the Bubs testnet, built with OP Stack and Celestia! This testnet is a great way to explore the possibilities of this integration and test your applications in a live environment.
        ',18),n=[r];function s(l,h,c,d,p,u){return e(),a("div",null,n)}const g=t(i,[["render",s]]);export{b as __pageData,g as default};
diff --git a/pr-1699/assets/developers_intro-to-op-stack.md.c09be10b.lean.js b/pr-1699/assets/developers_intro-to-op-stack.md.2deb5540.lean.js
similarity index 92%
rename from pr-1699/assets/developers_intro-to-op-stack.md.c09be10b.lean.js
rename to pr-1699/assets/developers_intro-to-op-stack.md.2deb5540.lean.js
index 73813eaf39..86a31958b1 100644
--- a/pr-1699/assets/developers_intro-to-op-stack.md.c09be10b.lean.js
+++ b/pr-1699/assets/developers_intro-to-op-stack.md.2deb5540.lean.js
@@ -1 +1 @@
-import{_ as t,o as e,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Introduction to OP Stack integration","description":"Learn about the integration of OP Stack with Celestia.","frontmatter":{"description":"Learn about the integration of OP Stack with Celestia.","prev":{"text":"Deploy a dapp on your Arbitrum rollup devnet","link":"/developers/arbitrum-dapp-deploy"},"head":[["meta",{"name":"og:title","content":"Introduction to OP Stack integration | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/intro-to-op-stack.md","filePath":"developers/intro-to-op-stack.md","lastUpdated":1725971357000}'),i={name:"developers/intro-to-op-stack.md"},r=o("",18),n=[r];function s(l,h,c,d,p,u){return e(),a("div",null,n)}const g=t(i,[["render",s]]);export{b as __pageData,g as default};
+import{_ as t,o as e,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Introduction to OP Stack integration","description":"Learn about the integration of OP Stack with Celestia.","frontmatter":{"description":"Learn about the integration of OP Stack with Celestia.","prev":{"text":"Deploy a dapp on your Arbitrum rollup devnet","link":"/developers/arbitrum-dapp-deploy"},"head":[["meta",{"name":"og:title","content":"Introduction to OP Stack integration | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/intro-to-op-stack.md","filePath":"developers/intro-to-op-stack.md","lastUpdated":1725992025000}'),i={name:"developers/intro-to-op-stack.md"},r=o("",18),n=[r];function s(l,h,c,d,p,u){return e(),a("div",null,n)}const g=t(i,[["render",s]]);export{b as __pageData,g as default};
diff --git a/pr-1699/assets/developers_multiaccounts.md.5fe51e02.js b/pr-1699/assets/developers_multiaccounts.md.6ee7c0ad.js
similarity index 99%
rename from pr-1699/assets/developers_multiaccounts.md.5fe51e02.js
rename to pr-1699/assets/developers_multiaccounts.md.6ee7c0ad.js
index cca3aadaae..838e2ed6f2 100644
--- a/pr-1699/assets/developers_multiaccounts.md.5fe51e02.js
+++ b/pr-1699/assets/developers_multiaccounts.md.6ee7c0ad.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as e,Q as n}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"MultiAccounts feature for blobs submission","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"MultiAccounts feature for blobs submission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/multiaccounts.md","filePath":"developers/multiaccounts.md","lastUpdated":1725971357000}'),o={name:"developers/multiaccounts.md"},t=n(`
        MultiAccounts feature for blobs submission ​
        Overview ​
        By default, a celestia-node creates a key named my_celes_key during initialization. This document explains how to run a node with a different default key name and how to submit blobs using different signers.
        Running a node with a different default key name ​
        To start a Celestia node with a different default key name, use the following command:
        sh
        celestia light start --core.ip=consensus.celestia-arabica-11.com \\
+import{_ as s,o as a,c as e,Q as n}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"MultiAccounts feature for blobs submission","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"MultiAccounts feature for blobs submission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/multiaccounts.md","filePath":"developers/multiaccounts.md","lastUpdated":1725992025000}'),o={name:"developers/multiaccounts.md"},t=n(`
        MultiAccounts feature for blobs submission ​
        Overview ​
        By default, a celestia-node creates a key named my_celes_key during initialization. This document explains how to run a node with a different default key name and how to submit blobs using different signers.
        Running a node with a different default key name ​
        To start a Celestia node with a different default key name, use the following command:
        sh
        celestia light start --core.ip=consensus.celestia-arabica-11.com \\
     --p2p.network=arabica --keyring.keyname testKey
        celestia light start --core.ip=consensus.celestia-arabica-11.com \\
     --p2p.network=arabica --keyring.keyname testKey
        In this example, testKey becomes the default node key, and the node's address will change accordingly.
        Submitting blobs with a different signer/key name ​
        Option 1: Submit passing key name ​
        You can submit a blob by specifying a different key name:
        sh
        celestia blob submit 0x42690c204d39600fddd3 'gm' --key.name testKey2
        celestia blob submit 0x42690c204d39600fddd3 'gm' --key.name testKey2
        This transaction will be signed by the address associated with testKey2.
        Option 2: Submit passing signer address ​
        Alternatively, you can submit a blob by specifying the signer's address:
        sh
        celestia blob submit 0x42690c204d39600fddd3 'gm' --signer $SIGNER_ADDRESS
        celestia blob submit 0x42690c204d39600fddd3 'gm' --signer $SIGNER_ADDRESS
        Both options achieve the same result but use different inputs. The testKey2 points to SIGNER_ADDRESS in the KeyStore.
        Key management ​
        All keys and addresses must be added to the KeyStore. To create a new key, use the cel-key library:
        Creating a new key ​
        sh
        ./cel-key add testKey --keyring-backend test \\
     --node.type light --p2p.network arabica
        ./cel-key add testKey --keyring-backend test \\
diff --git a/pr-1699/assets/developers_multiaccounts.md.5fe51e02.lean.js b/pr-1699/assets/developers_multiaccounts.md.6ee7c0ad.lean.js
similarity index 89%
rename from pr-1699/assets/developers_multiaccounts.md.5fe51e02.lean.js
rename to pr-1699/assets/developers_multiaccounts.md.6ee7c0ad.lean.js
index 47fb70431f..6cd3e15b48 100644
--- a/pr-1699/assets/developers_multiaccounts.md.5fe51e02.lean.js
+++ b/pr-1699/assets/developers_multiaccounts.md.6ee7c0ad.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as e,Q as n}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"MultiAccounts feature for blobs submission","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"MultiAccounts feature for blobs submission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/multiaccounts.md","filePath":"developers/multiaccounts.md","lastUpdated":1725971357000}'),o={name:"developers/multiaccounts.md"},t=n("",28),l=[t];function p(r,i,c,d,y,h){return a(),e("div",null,l)}const E=s(o,[["render",p]]);export{b as __pageData,E as default};
+import{_ as s,o as a,c as e,Q as n}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"MultiAccounts feature for blobs submission","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"MultiAccounts feature for blobs submission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/multiaccounts.md","filePath":"developers/multiaccounts.md","lastUpdated":1725992025000}'),o={name:"developers/multiaccounts.md"},t=n("",28),l=[t];function p(r,i,c,d,y,h){return a(),e("div",null,l)}const E=s(o,[["render",p]]);export{b as __pageData,E as default};
diff --git a/pr-1699/assets/developers_node-api.md.8d88dab0.js b/pr-1699/assets/developers_node-api.md.6709e8d4.js
similarity index 98%
rename from pr-1699/assets/developers_node-api.md.8d88dab0.js
rename to pr-1699/assets/developers_node-api.md.6709e8d4.js
index a7e9c0bf74..1c0ae82b23 100644
--- a/pr-1699/assets/developers_node-api.md.8d88dab0.js
+++ b/pr-1699/assets/developers_node-api.md.6709e8d4.js
@@ -1 +1 @@
-import{_ as e,o as a,c as t,Q as r}from"./chunks/framework.b47e54aa.js";const w=JSON.parse('{"title":"Node API","description":"An overview of the celestia-node API.","frontmatter":{"description":"An overview of the celestia-node API.","head":[["meta",{"name":"og:title","content":"Node API | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/node-api.md","filePath":"developers/node-api.md","lastUpdated":1725971357000}'),o={name:"developers/node-api.md"},i=r('
        Node API ​
        The celestia-node API is made for interacting with celestia-node. There are two ways in which a user and developer can interact with the API, the RPC API and the Gateway API. View the API's documentation.
        RPC API ​
        The RPC API primarily focuses on developers and projects building on top of Celestia, who are willing to run their own DA nodes. The RPC API provides a richer set of features and a superior user experience. Unlike the Gateway API, the RPC API allows access to the internal wallet and keyring of the DA node, as well as other sensitive and administrative capabilities.
        Library ​
        The node can be used as a Golang library and designed for programmatic API access.
        RPC ​
        The RPC API is also exposed to OpenRPC(JSON-RPC 2.0) for users wanting to run their DA node as a separate DA service. It provides the same set of features as the library with an additional authentication system with different permissions levels to protect the wallet and signing + providing RPC-level DOS protection.
        RPC API tutorial ​
        The node tutorial, which uses the RPC CLI, is the recommended way to get started interacting with your Celestia node.
        Gateway API ​
        WARNING
        The gateway endpoints have been deprecated and will be removed in the future. If you would like to use them anyway, you can find more details on GitHub.
        The gateway API is a REST API which is meant to be deployed by infra providers to enable the public read-only gateway to the DA network for external users who don't want or can't run light nodes (like browsers currently) over HTTP. It has no wallet or signing functionality.
        Gateway API tutorial ​
        Check out the Prompt scavenger gateway API tutorial for more details.
        ',15),n=[i];function s(l,d,h,c,p,u){return a(),t("div",null,n)}const f=e(o,[["render",s]]);export{w as __pageData,f as default};
+import{_ as e,o as a,c as t,Q as r}from"./chunks/framework.b47e54aa.js";const w=JSON.parse('{"title":"Node API","description":"An overview of the celestia-node API.","frontmatter":{"description":"An overview of the celestia-node API.","head":[["meta",{"name":"og:title","content":"Node API | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/node-api.md","filePath":"developers/node-api.md","lastUpdated":1725992025000}'),o={name:"developers/node-api.md"},i=r('
        Node API ​
        The celestia-node API is made for interacting with celestia-node. There are two ways in which a user and developer can interact with the API, the RPC API and the Gateway API. View the API's documentation.
        RPC API ​
        The RPC API primarily focuses on developers and projects building on top of Celestia, who are willing to run their own DA nodes. The RPC API provides a richer set of features and a superior user experience. Unlike the Gateway API, the RPC API allows access to the internal wallet and keyring of the DA node, as well as other sensitive and administrative capabilities.
        Library ​
        The node can be used as a Golang library and designed for programmatic API access.
        RPC ​
        The RPC API is also exposed to OpenRPC(JSON-RPC 2.0) for users wanting to run their DA node as a separate DA service. It provides the same set of features as the library with an additional authentication system with different permissions levels to protect the wallet and signing + providing RPC-level DOS protection.
        RPC API tutorial ​
        The node tutorial, which uses the RPC CLI, is the recommended way to get started interacting with your Celestia node.
        Gateway API ​
        WARNING
        The gateway endpoints have been deprecated and will be removed in the future. If you would like to use them anyway, you can find more details on GitHub.
        The gateway API is a REST API which is meant to be deployed by infra providers to enable the public read-only gateway to the DA network for external users who don't want or can't run light nodes (like browsers currently) over HTTP. It has no wallet or signing functionality.
        Gateway API tutorial ​
        Check out the Prompt scavenger gateway API tutorial for more details.
        ',15),n=[i];function s(l,d,h,c,p,u){return a(),t("div",null,n)}const f=e(o,[["render",s]]);export{w as __pageData,f as default};
diff --git a/pr-1699/assets/developers_node-api.md.8d88dab0.lean.js b/pr-1699/assets/developers_node-api.md.6709e8d4.lean.js
similarity index 90%
rename from pr-1699/assets/developers_node-api.md.8d88dab0.lean.js
rename to pr-1699/assets/developers_node-api.md.6709e8d4.lean.js
index ccb124a180..a913a01e9e 100644
--- a/pr-1699/assets/developers_node-api.md.8d88dab0.lean.js
+++ b/pr-1699/assets/developers_node-api.md.6709e8d4.lean.js
@@ -1 +1 @@
-import{_ as e,o as a,c as t,Q as r}from"./chunks/framework.b47e54aa.js";const w=JSON.parse('{"title":"Node API","description":"An overview of the celestia-node API.","frontmatter":{"description":"An overview of the celestia-node API.","head":[["meta",{"name":"og:title","content":"Node API | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/node-api.md","filePath":"developers/node-api.md","lastUpdated":1725971357000}'),o={name:"developers/node-api.md"},i=r("",15),n=[i];function s(l,d,h,c,p,u){return a(),t("div",null,n)}const f=e(o,[["render",s]]);export{w as __pageData,f as default};
+import{_ as e,o as a,c as t,Q as r}from"./chunks/framework.b47e54aa.js";const w=JSON.parse('{"title":"Node API","description":"An overview of the celestia-node API.","frontmatter":{"description":"An overview of the celestia-node API.","head":[["meta",{"name":"og:title","content":"Node API | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/node-api.md","filePath":"developers/node-api.md","lastUpdated":1725992025000}'),o={name:"developers/node-api.md"},i=r("",15),n=[i];function s(l,d,h,c,p,u){return a(),t("div",null,n)}const f=e(o,[["render",s]]);export{w as __pageData,f as default};
diff --git a/pr-1699/assets/developers_node-tutorial.md.358f7307.js b/pr-1699/assets/developers_node-tutorial.md.79e6f899.js
similarity index 99%
rename from pr-1699/assets/developers_node-tutorial.md.358f7307.js
rename to pr-1699/assets/developers_node-tutorial.md.79e6f899.js
index c4ebb278b2..136fff07a0 100644
--- a/pr-1699/assets/developers_node-tutorial.md.358f7307.js
+++ b/pr-1699/assets/developers_node-tutorial.md.79e6f899.js
@@ -1,8 +1,8 @@
-import{c as a}from"./chunks/constants.295fc0ab.js";import{o as e,c as t,k as s,t as n,l as o,a as p,Q as l}from"./chunks/framework.b47e54aa.js";const c=l(`
        Celestia-node RPC CLI tutorial ​
        In this tutorial, we will cover how to use the celestia-node RPC API to submit and retrieve data (blobs) from the data availability layer by their namespace.
        Introduction ​
        Blobs ​
        Data is posted to Celestia's DA layer by using MsgPayForBlobs transactions to the core network. Read more about MsgPayForBlobs.
        Namespaces ​
        Celestia partitions the block data into multiple namespaces, one for every application. This allows applications to only download their data, and not the data of other applications. Read more about Namespaced Merkle trees (NMTs).
        TIP
        If you already have a running and funded node, you can skip to the RPC CLI guide section.
        WARNING
        The gateway endpoints have been deprecated and will be removed in the future. If you would like to use them anyway, you can find more details on GitHub.
        Hardware requirements ​
        The following minimum hardware requirements are recommended for running a light node:
        • Memory: 500 MB RAM (minimum)
        • CPU: Single Core
        • Disk: 50 GB SSD Storage
        • Bandwidth: 56 Kbps for Download/56 Kbps for Upload
        Setting up dependencies ​
        Install dependencies and celestia-node if you have not already.
        Instantiate a Celestia light node ​
        Now, let's instantiate a Celestia Light node:
        TIP
        RPC endpoints are exposed in all celestia-node types such as light, bridge and full nodes.
        bash
        celestia light init
        celestia light init
        bash
        celestia light init --p2p.network mocha
        celestia light init --p2p.network mocha
        bash
        celestia light init --p2p.network arabica
        celestia light init --p2p.network arabica
        Instantiating (or initializing) the node means setting up a node store on your machine. This is where the data and your keys will be stored.
        Connect to a core endpoint ​
        Let's now run the Celestia Light node with a gRPC connection to an example core endpoint. Connecting to a core endpoint provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).
        Note: You are also encouraged to find a community-run API endpoint and there are several in the Discord. This one is used for demonstration purposes. Check out the Mocha testnet page, or Arabica devnet page.
        bash
        celestia light start --core.ip <URI>
        celestia light start --core.ip <URI>
        bash
        celestia light start --core.ip <URI> --p2p.network mocha
        celestia light start --core.ip <URI> --p2p.network mocha
        bash
        celestia light start --core.ip <URI> --p2p.network arabica
        celestia light start --core.ip <URI> --p2p.network arabica
        TIP
        The --core.ip gRPC port defaults to 9090, so if you do not specify it in the command line, it will default to that port. You can add the port after the IP address or use the --core.grpc.port flag to specify another port if you prefer.
        Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.
        For example, your command along with an RPC endpoint might look like this:
        bash
        celestia light start --core.ip consensus.lunaroasis.net
        celestia light start --core.ip consensus.lunaroasis.net
        bash
        celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
        celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
        bash
        celestia light start --core.ip validator-1.celestia-arabica-11.com \\
+import{c as a}from"./chunks/constants.295fc0ab.js";import{o as e,c as t,k as s,t as n,l as o,a as p,Q as l}from"./chunks/framework.b47e54aa.js";const c=l(`
        Celestia-node RPC CLI tutorial ​
        In this tutorial, we will cover how to use the celestia-node RPC API to submit and retrieve data (blobs) from the data availability layer by their namespace.
        Introduction ​
        Blobs ​
        Data is posted to Celestia's DA layer by using MsgPayForBlobs transactions to the core network. Read more about MsgPayForBlobs.
        Namespaces ​
        Celestia partitions the block data into multiple namespaces, one for every application. This allows applications to only download their data, and not the data of other applications. Read more about Namespaced Merkle trees (NMTs).
        TIP
        If you already have a running and funded node, you can skip to the RPC CLI guide section.
        WARNING
        The gateway endpoints have been deprecated and will be removed in the future. If you would like to use them anyway, you can find more details on GitHub.
        Hardware requirements ​
        The following minimum hardware requirements are recommended for running a light node:
        • Memory: 500 MB RAM (minimum)
        • CPU: Single Core
        • Disk: 50 GB SSD Storage
        • Bandwidth: 56 Kbps for Download/56 Kbps for Upload
        Setting up dependencies ​
        Install dependencies and celestia-node if you have not already.
        Instantiate a Celestia light node ​
        Now, let's instantiate a Celestia Light node:
        TIP
        RPC endpoints are exposed in all celestia-node types such as light, bridge and full nodes.
        bash
        celestia light init
        celestia light init
        bash
        celestia light init --p2p.network mocha
        celestia light init --p2p.network mocha
        bash
        celestia light init --p2p.network arabica
        celestia light init --p2p.network arabica
        Instantiating (or initializing) the node means setting up a node store on your machine. This is where the data and your keys will be stored.
        Connect to a core endpoint ​
        Let's now run the Celestia Light node with a gRPC connection to an example core endpoint. Connecting to a core endpoint provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).
        Note: You are also encouraged to find a community-run API endpoint and there are several in the Discord. This one is used for demonstration purposes. Check out the Mocha testnet page, or Arabica devnet page.
        bash
        celestia light start --core.ip <URI>
        celestia light start --core.ip <URI>
        bash
        celestia light start --core.ip <URI> --p2p.network mocha
        celestia light start --core.ip <URI> --p2p.network mocha
        bash
        celestia light start --core.ip <URI> --p2p.network arabica
        celestia light start --core.ip <URI> --p2p.network arabica
        TIP
        The --core.ip gRPC port defaults to 9090, so if you do not specify it in the command line, it will default to that port. You can add the port after the IP address or use the --core.grpc.port flag to specify another port if you prefer.
        Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.
        For example, your command along with an RPC endpoint might look like this:
        bash
        celestia light start --core.ip consensus.lunaroasis.net
        celestia light start --core.ip consensus.lunaroasis.net
        bash
        celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
        celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
        bash
        celestia light start --core.ip validator-1.celestia-arabica-11.com \\
   --p2p.network arabica
        celestia light start --core.ip validator-1.celestia-arabica-11.com \\
   --p2p.network arabica
        Keys and wallets ​
        You can create your key for your node by running the following command from the celestia-node directory:
        TIP
        You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information
        bash
        ./cel-key add <key-name> --keyring-backend test --node.type light \\
   --p2p.network <network>
        ./cel-key add <key-name> --keyring-backend test --node.type light \\
-  --p2p.network <network>
        You can start your light node with the key created by running the following command:
        bash
        celestia light start --core.ip <URI> --keyring.keyname <key-name>
        celestia light start --core.ip <URI> --keyring.keyname <key-name>
        bash
        celestia light start --core.ip <URI> --keyring.keyname <key-name> \\
+  --p2p.network <network>
        You can start your light node with the key created by running the following command:
        bash
        celestia light start --core.ip <URI> --keyring.keyname <key-name>
        celestia light start --core.ip <URI> --keyring.keyname <key-name>
        bash
        celestia light start --core.ip <URI> --keyring.keyname <key-name> \\
   --p2p.network mocha
        celestia light start --core.ip <URI> --keyring.keyname <key-name> \\
   --p2p.network mocha
        bash
        celestia light start --core.ip <URI> --keyring.keyname <key-name> \\
   --p2p.network arabica
        celestia light start --core.ip <URI> --keyring.keyname <key-name> \\
@@ -394,4 +394,4 @@ import{c as a}from"./chunks/constants.295fc0ab.js";import{o as e,c as t,k as s,t
     ],
     0.002
   ]
-}' 127.0.0.1:26658
        1. Upon successful blob submission, the result will show the block height:
        bash
        {"jsonrpc":"2.0","result":362101,"id":1}
        {"jsonrpc":"2.0","result":362101,"id":1}
        The example transaction can be found on Celenium.
        Post an SVG as a PFB ​
        If you'd like to create your own SVG, post it to Celestia, and retrieve it, you can check out the Base64 SVG Tutorial.
        Troubleshooting ​
        If you encounter an error like:
        sh
        "rpc error: code = NotFound desc = account celestia1krkle0n547u0znz3unnln8paft2dq4z3rznv86 not found"
        "rpc error: code = NotFound desc = account celestia1krkle0n547u0znz3unnln8paft2dq4z3rznv86 not found"
        It is possible that the account you are trying to submit a PayForBlobs from doesn't have testnet tokens yet. Ensure the testnet faucet has funded your account with tokens and then try again.
        `,93),R=JSON.parse('{"title":"Celestia-node RPC CLI tutorial","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Celestia-node RPC CLI tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/node-tutorial.md","filePath":"developers/node-tutorial.md","lastUpdated":1725971357000}'),D={name:"developers/node-tutorial.md"},U=Object.assign(D,{setup(_){return(x,T)=>(e(),t("div",null,[c,s("p",null,"To set a custom node store for a light node on "+n(o(a).mochaChainId)+", you can use the following command:",1),s("div",r,[y,i,s("pre",E,[s("code",null,[s("span",d,[u,F,h,C,s("span",g,"/your-custom-path/celestia-light-"+n(o(a).mochaChainId),1)])])]),s("pre",b,[s("code",null,[s("span",q,[B,m,v,k,s("span",A,"/your-custom-path/celestia-light-"+n(o(a).mochaChainId),1)])])])]),f,s("p",null,[p("Here is an example command to retrieve the data from above, on "),s("code",null,n(o(a).arabicaChainId),1),p(":")]),w]))}});export{R as __pageData,U as default};
+}' 127.0.0.1:26658
        1. Upon successful blob submission, the result will show the block height:
        bash
        {"jsonrpc":"2.0","result":362101,"id":1}
        {"jsonrpc":"2.0","result":362101,"id":1}
        The example transaction can be found on Celenium.
        Post an SVG as a PFB ​
        If you'd like to create your own SVG, post it to Celestia, and retrieve it, you can check out the Base64 SVG Tutorial.
        Troubleshooting ​
        If you encounter an error like:
        sh
        "rpc error: code = NotFound desc = account celestia1krkle0n547u0znz3unnln8paft2dq4z3rznv86 not found"
        "rpc error: code = NotFound desc = account celestia1krkle0n547u0znz3unnln8paft2dq4z3rznv86 not found"
        It is possible that the account you are trying to submit a PayForBlobs from doesn't have testnet tokens yet. Ensure the testnet faucet has funded your account with tokens and then try again.
        `,93),R=JSON.parse('{"title":"Celestia-node RPC CLI tutorial","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Celestia-node RPC CLI tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/node-tutorial.md","filePath":"developers/node-tutorial.md","lastUpdated":1725992025000}'),D={name:"developers/node-tutorial.md"},S=Object.assign(D,{setup(_){return(x,T)=>(e(),t("div",null,[c,s("p",null,"To set a custom node store for a light node on "+n(o(a).mochaChainId)+", you can use the following command:",1),s("div",r,[y,i,s("pre",E,[s("code",null,[s("span",d,[u,F,h,C,s("span",g,"/your-custom-path/celestia-light-"+n(o(a).mochaChainId),1)])])]),s("pre",b,[s("code",null,[s("span",q,[B,m,v,k,s("span",A,"/your-custom-path/celestia-light-"+n(o(a).mochaChainId),1)])])])]),f,s("p",null,[p("Here is an example command to retrieve the data from above, on "),s("code",null,n(o(a).arabicaChainId),1),p(":")]),w]))}});export{R as __pageData,S as default};
diff --git a/pr-1699/assets/developers_node-tutorial.md.358f7307.lean.js b/pr-1699/assets/developers_node-tutorial.md.79e6f899.lean.js
similarity index 90%
rename from pr-1699/assets/developers_node-tutorial.md.358f7307.lean.js
rename to pr-1699/assets/developers_node-tutorial.md.79e6f899.lean.js
index 8811d8034c..f3f97006d9 100644
--- a/pr-1699/assets/developers_node-tutorial.md.358f7307.lean.js
+++ b/pr-1699/assets/developers_node-tutorial.md.79e6f899.lean.js
@@ -1 +1 @@
-import{c as a}from"./chunks/constants.295fc0ab.js";import{o as e,c as t,k as s,t as n,l as o,a as p,Q as l}from"./chunks/framework.b47e54aa.js";const c=l("",71),r={class:"language-bash vp-adaptive-theme"},y=s("button",{title:"Copy Code",class:"copy"},null,-1),i=s("span",{class:"lang"},"bash",-1),E={class:"shiki github-dark vp-code-dark"},d={class:"line"},u=s("span",{style:{color:"#F97583"}},"export",-1),F=s("span",{style:{color:"#E1E4E8"}}," NODE_STORE",-1),h=s("span",{style:{color:"#F97583"}},"=",-1),C=s("span",{style:{color:"#E1E4E8"}},"$HOME",-1),g={style:{color:"#9ECBFF"}},b={class:"shiki github-light vp-code-light"},q={class:"line"},B=s("span",{style:{color:"#D73A49"}},"export",-1),m=s("span",{style:{color:"#24292E"}}," NODE_STORE",-1),v=s("span",{style:{color:"#D73A49"}},"=",-1),k=s("span",{style:{color:"#24292E"}},"$HOME",-1),A={style:{color:"#032F62"}},f=l("",36),w=l("",93),R=JSON.parse('{"title":"Celestia-node RPC CLI tutorial","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Celestia-node RPC CLI tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/node-tutorial.md","filePath":"developers/node-tutorial.md","lastUpdated":1725971357000}'),D={name:"developers/node-tutorial.md"},U=Object.assign(D,{setup(_){return(x,T)=>(e(),t("div",null,[c,s("p",null,"To set a custom node store for a light node on "+n(o(a).mochaChainId)+", you can use the following command:",1),s("div",r,[y,i,s("pre",E,[s("code",null,[s("span",d,[u,F,h,C,s("span",g,"/your-custom-path/celestia-light-"+n(o(a).mochaChainId),1)])])]),s("pre",b,[s("code",null,[s("span",q,[B,m,v,k,s("span",A,"/your-custom-path/celestia-light-"+n(o(a).mochaChainId),1)])])])]),f,s("p",null,[p("Here is an example command to retrieve the data from above, on "),s("code",null,n(o(a).arabicaChainId),1),p(":")]),w]))}});export{R as __pageData,U as default};
+import{c as a}from"./chunks/constants.295fc0ab.js";import{o as e,c as t,k as s,t as n,l as o,a as p,Q as l}from"./chunks/framework.b47e54aa.js";const c=l("",71),r={class:"language-bash vp-adaptive-theme"},y=s("button",{title:"Copy Code",class:"copy"},null,-1),i=s("span",{class:"lang"},"bash",-1),E={class:"shiki github-dark vp-code-dark"},d={class:"line"},u=s("span",{style:{color:"#F97583"}},"export",-1),F=s("span",{style:{color:"#E1E4E8"}}," NODE_STORE",-1),h=s("span",{style:{color:"#F97583"}},"=",-1),C=s("span",{style:{color:"#E1E4E8"}},"$HOME",-1),g={style:{color:"#9ECBFF"}},b={class:"shiki github-light vp-code-light"},q={class:"line"},B=s("span",{style:{color:"#D73A49"}},"export",-1),m=s("span",{style:{color:"#24292E"}}," NODE_STORE",-1),v=s("span",{style:{color:"#D73A49"}},"=",-1),k=s("span",{style:{color:"#24292E"}},"$HOME",-1),A={style:{color:"#032F62"}},f=l("",36),w=l("",93),R=JSON.parse('{"title":"Celestia-node RPC CLI tutorial","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Celestia-node RPC CLI tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/node-tutorial.md","filePath":"developers/node-tutorial.md","lastUpdated":1725992025000}'),D={name:"developers/node-tutorial.md"},S=Object.assign(D,{setup(_){return(x,T)=>(e(),t("div",null,[c,s("p",null,"To set a custom node store for a light node on "+n(o(a).mochaChainId)+", you can use the following command:",1),s("div",r,[y,i,s("pre",E,[s("code",null,[s("span",d,[u,F,h,C,s("span",g,"/your-custom-path/celestia-light-"+n(o(a).mochaChainId),1)])])]),s("pre",b,[s("code",null,[s("span",q,[B,m,v,k,s("span",A,"/your-custom-path/celestia-light-"+n(o(a).mochaChainId),1)])])])]),f,s("p",null,[p("Here is an example command to retrieve the data from above, on "),s("code",null,n(o(a).arabicaChainId),1),p(":")]),w]))}});export{R as __pageData,S as default};
diff --git a/pr-1699/assets/developers_optimism-devnet.md.6da256da.js b/pr-1699/assets/developers_optimism-devnet.md.3b3f49a3.js
similarity index 99%
rename from pr-1699/assets/developers_optimism-devnet.md.6da256da.js
rename to pr-1699/assets/developers_optimism-devnet.md.3b3f49a3.js
index 440eca1dc2..a549662e7a 100644
--- a/pr-1699/assets/developers_optimism-devnet.md.6da256da.js
+++ b/pr-1699/assets/developers_optimism-devnet.md.3b3f49a3.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Optimism devnet deep dive","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Optimism devnet deep dive | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/optimism-devnet.md","filePath":"developers/optimism-devnet.md","lastUpdated":1725971357000}'),l={name:"developers/optimism-devnet.md"},o=e(`
        Optimism devnet deep dive ​
        This page is for those interested in doing a deep dive on their pre-op-plasma-celestia @celestiaorg/optimism rollups.
        Find a transaction ​
        Now, we'll check for a recent transaction on the L1 with:
        bash
        cast block latest --rpc-url localhost:8545
        cast block latest --rpc-url localhost:8545
        Output of a block that contains a transaction will look like this:
        console
        baseFeePerGas        7
+import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Optimism devnet deep dive","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Optimism devnet deep dive | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/optimism-devnet.md","filePath":"developers/optimism-devnet.md","lastUpdated":1725992025000}'),l={name:"developers/optimism-devnet.md"},o=e(`
        Optimism devnet deep dive ​
        This page is for those interested in doing a deep dive on their pre-op-plasma-celestia @celestiaorg/optimism rollups.
        Find a transaction ​
        Now, we'll check for a recent transaction on the L1 with:
        bash
        cast block latest --rpc-url localhost:8545
        cast block latest --rpc-url localhost:8545
        Output of a block that contains a transaction will look like this:
        console
        baseFeePerGas        7
 difficulty           2
 extraData            0xd883010d04846765746888676f312e32312e33856c696e7578000000000000006b3afa42dce1f87f1f07a1ef569c4d43e41738ef93c865098bfa1458645f384e2e4498bcfe4ad9353ff1913a2e16162f496fafe5b0939a6c78fb5b503248d6da01
 gasLimit             30000000
diff --git a/pr-1699/assets/developers_optimism-devnet.md.6da256da.lean.js b/pr-1699/assets/developers_optimism-devnet.md.3b3f49a3.lean.js
similarity index 89%
rename from pr-1699/assets/developers_optimism-devnet.md.6da256da.lean.js
rename to pr-1699/assets/developers_optimism-devnet.md.3b3f49a3.lean.js
index 5b7f6ec599..ab49c1d99d 100644
--- a/pr-1699/assets/developers_optimism-devnet.md.6da256da.lean.js
+++ b/pr-1699/assets/developers_optimism-devnet.md.3b3f49a3.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Optimism devnet deep dive","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Optimism devnet deep dive | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/optimism-devnet.md","filePath":"developers/optimism-devnet.md","lastUpdated":1725971357000}'),l={name:"developers/optimism-devnet.md"},o=e("",26),p=[o];function c(t,r,d,i,y,b){return a(),n("div",null,p)}const h=s(l,[["render",c]]);export{f as __pageData,h as default};
+import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Optimism devnet deep dive","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Optimism devnet deep dive | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/optimism-devnet.md","filePath":"developers/optimism-devnet.md","lastUpdated":1725992025000}'),l={name:"developers/optimism-devnet.md"},o=e("",26),p=[o];function c(t,r,d,i,y,b){return a(),n("div",null,p)}const h=s(l,[["render",c]]);export{f as __pageData,h as default};
diff --git a/pr-1699/assets/developers_optimism.md.363527ac.js b/pr-1699/assets/developers_optimism.md.d6e1e2ee.js
similarity index 93%
rename from pr-1699/assets/developers_optimism.md.363527ac.js
rename to pr-1699/assets/developers_optimism.md.d6e1e2ee.js
index 613c8bda18..fabef7e090 100644
--- a/pr-1699/assets/developers_optimism.md.363527ac.js
+++ b/pr-1699/assets/developers_optimism.md.d6e1e2ee.js
@@ -1,4 +1,4 @@
-import{c as a}from"./chunks/constants.295fc0ab.js";import{o as t,c as l,k as s,t as e,l as n,Q as o}from"./chunks/framework.b47e54aa.js";const p=o('
        Run an OP Stack rollup with Celestia underneath ​
        This guide will show you how to run your own OP Stack devnet and testnet that posts data to Celestia's Mocha testnet using roll-op and op-plasma-celestia.
        If you don't have devops experience and would like to use a Rollups as a Service (RaaS) provider, see the RaaS category in the menu.
        Dependency setup ​
        Setting up your light node ​
        Sync and fund a Celestia light node. The light node must be fully synced and funded for you to be able to submit and retrieve PayForBlobs to Mocha Testnet. This allows your rollup to post and retrieve data without any errors.
        In order to mount existing data, you must have a node store that is in the default directory:
        ',8),c={class:"vp-code-group vp-adaptive-theme"},r=o('
        ',1),i={class:"blocks"},d={class:"language-bash vp-adaptive-theme active"},u=s("button",{title:"Copy Code",class:"copy"},null,-1),h=s("span",{class:"lang"},"bash",-1),y={class:"shiki github-dark vp-code-dark"},_={class:"line"},E={style:{color:"#E1E4E8"}},g={class:"shiki github-light vp-code-light"},b={class:"line"},m={style:{color:"#24292E"}},v=o('
        bash
        $HOME/.celestia-light
        $HOME/.celestia-light
        ',1),k={class:"language-bash vp-adaptive-theme"},C=s("button",{title:"Copy Code",class:"copy"},null,-1),q=s("span",{class:"lang"},"bash",-1),f={class:"shiki github-dark vp-code-dark"},F={class:"line"},S={style:{color:"#E1E4E8"}},T={class:"shiki github-light vp-code-light"},w={class:"line"},A={style:{color:"#24292E"}},D=o(`
        By default, the node will run with the account named my_celes_key on Mocha. This is the account that needs to be funded.
        TIP
        Unless you changed your configuration, you won't have to change anything. 😎
        Deploying a devnet to Mocha ​
        See the Alt-DA x Celestia README for instructions on how to deploy a Devnet.
        TIP for macOS users
        If you are on macOS, you will need to run a venv before starting roll-op.
        sh
        cd $HOME/roll-op
+import{c as a}from"./chunks/constants.295fc0ab.js";import{o as t,c as l,k as s,t as e,l as n,Q as o}from"./chunks/framework.b47e54aa.js";const p=o('
        Run an OP Stack rollup with Celestia underneath ​
        This guide will show you how to run your own OP Stack devnet and testnet that posts data to Celestia's Mocha testnet using roll-op and op-plasma-celestia.
        If you don't have devops experience and would like to use a Rollups as a Service (RaaS) provider, see the RaaS category in the menu.
        Dependency setup ​
        Setting up your light node ​
        Sync and fund a Celestia light node. The light node must be fully synced and funded for you to be able to submit and retrieve PayForBlobs to Mocha Testnet. This allows your rollup to post and retrieve data without any errors.
        In order to mount existing data, you must have a node store that is in the default directory:
        ',8),c={class:"vp-code-group vp-adaptive-theme"},r=o('
        ',1),i={class:"blocks"},d={class:"language-bash vp-adaptive-theme active"},u=s("button",{title:"Copy Code",class:"copy"},null,-1),h=s("span",{class:"lang"},"bash",-1),y={class:"shiki github-dark vp-code-dark"},_={class:"line"},E={style:{color:"#E1E4E8"}},g={class:"shiki github-light vp-code-light"},m={class:"line"},b={style:{color:"#24292E"}},v=o('
        bash
        $HOME/.celestia-light
        $HOME/.celestia-light
        ',1),k={class:"language-bash vp-adaptive-theme"},C=s("button",{title:"Copy Code",class:"copy"},null,-1),f=s("span",{class:"lang"},"bash",-1),F={class:"shiki github-dark vp-code-dark"},q={class:"line"},A={style:{color:"#E1E4E8"}},S={class:"shiki github-light vp-code-light"},w={class:"line"},T={style:{color:"#24292E"}},D=o(`
        By default, the node will run with the account named my_celes_key on Mocha. This is the account that needs to be funded.
        TIP
        Unless you changed your configuration, you won't have to change anything. 😎
        Deploying a devnet to Mocha ​
        See the Alt-DA x Celestia README for instructions on how to deploy a Devnet.
        TIP for macOS users
        If you are on macOS, you will need to run a venv before starting roll-op.
        sh
        cd $HOME/roll-op
 python3 -m venv ./venv
 source ./venv/bin/activate
        cd $HOME/roll-op
 python3 -m venv ./venv
@@ -42,4 +42,4 @@ import{c as a}from"./chunks/constants.295fc0ab.js";import{o as t,c as l,k as s,t
 admin_account = "0xaddress"
 admin_key = "privatekey"
 p2p_sequencer_account = "0xaddress"
-p2p_sequencer_key = "privatekey"
        Your 0xaddress key must also be funded with testnet ETH. We recommend at least 10 SepoliaETH to get your chain started, but you will need more to keep it running longer.
        Congratulations ​
        Congrats! You now have an OP Stack rollup running with Celestia underneath.
        You can learn more about Alt-DA in Optimism docs.
        `,16),O=JSON.parse('{"title":"Run an OP Stack rollup with Celestia underneath","description":"Start your own rollup with op-plasma-celestia and roll-op.","frontmatter":{"description":"Start your own rollup with op-plasma-celestia and roll-op.","next":{"text":"Ethereum fallback mechanism","link":"/developers/ethereum-fallback"},"head":[["meta",{"name":"og:title","content":"Run an OP Stack rollup with Celestia underneath | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/optimism.md","filePath":"developers/optimism.md","lastUpdated":1725971357000}'),P={name:"developers/optimism.md"},V=Object.assign(P,{setup(x){return(B,M)=>(t(),l("div",null,[p,s("div",c,[r,s("div",i,[s("div",d,[u,h,s("pre",y,[s("code",null,[s("span",_,[s("span",E,"$HOME/.celestia-light-"+e(n(a).mochaChainId),1)])])]),s("pre",g,[s("code",null,[s("span",b,[s("span",m,"$HOME/.celestia-light-"+e(n(a).mochaChainId),1)])])])]),v,s("div",k,[C,q,s("pre",f,[s("code",null,[s("span",F,[s("span",S,"$HOME/.celestia-light-"+e(n(a).arabicaChainId),1)])])]),s("pre",T,[s("code",null,[s("span",w,[s("span",A,"$HOME/.celestia-light-"+e(n(a).arabicaChainId),1)])])])])])]),D]))}});export{O as __pageData,V as default};
+p2p_sequencer_key = "privatekey"
        Your 0xaddress key must also be funded with testnet ETH. We recommend at least 10 SepoliaETH to get your chain started, but you will need more to keep it running longer.
        Congratulations ​
        Congrats! You now have an OP Stack rollup running with Celestia underneath.
        You can learn more about Alt-DA in Optimism docs.
        `,16),O=JSON.parse('{"title":"Run an OP Stack rollup with Celestia underneath","description":"Start your own rollup with op-plasma-celestia and roll-op.","frontmatter":{"description":"Start your own rollup with op-plasma-celestia and roll-op.","next":{"text":"Ethereum fallback mechanism","link":"/developers/ethereum-fallback"},"head":[["meta",{"name":"og:title","content":"Run an OP Stack rollup with Celestia underneath | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/optimism.md","filePath":"developers/optimism.md","lastUpdated":1725992025000}'),P={name:"developers/optimism.md"},V=Object.assign(P,{setup(x){return(B,M)=>(t(),l("div",null,[p,s("div",c,[r,s("div",i,[s("div",d,[u,h,s("pre",y,[s("code",null,[s("span",_,[s("span",E,"$HOME/.celestia-light-"+e(n(a).mochaChainId),1)])])]),s("pre",g,[s("code",null,[s("span",m,[s("span",b,"$HOME/.celestia-light-"+e(n(a).mochaChainId),1)])])])]),v,s("div",k,[C,f,s("pre",F,[s("code",null,[s("span",q,[s("span",A,"$HOME/.celestia-light-"+e(n(a).arabicaChainId),1)])])]),s("pre",S,[s("code",null,[s("span",w,[s("span",T,"$HOME/.celestia-light-"+e(n(a).arabicaChainId),1)])])])])])]),D]))}});export{O as __pageData,V as default};
diff --git a/pr-1699/assets/developers_optimism.md.363527ac.lean.js b/pr-1699/assets/developers_optimism.md.d6e1e2ee.lean.js
similarity index 60%
rename from pr-1699/assets/developers_optimism.md.363527ac.lean.js
rename to pr-1699/assets/developers_optimism.md.d6e1e2ee.lean.js
index 87db6d243f..20d7f1eb2f 100644
--- a/pr-1699/assets/developers_optimism.md.363527ac.lean.js
+++ b/pr-1699/assets/developers_optimism.md.d6e1e2ee.lean.js
@@ -1 +1 @@
-import{c as a}from"./chunks/constants.295fc0ab.js";import{o as t,c as l,k as s,t as e,l as n,Q as o}from"./chunks/framework.b47e54aa.js";const p=o("",8),c={class:"vp-code-group vp-adaptive-theme"},r=o("",1),i={class:"blocks"},d={class:"language-bash vp-adaptive-theme active"},u=s("button",{title:"Copy Code",class:"copy"},null,-1),h=s("span",{class:"lang"},"bash",-1),y={class:"shiki github-dark vp-code-dark"},_={class:"line"},E={style:{color:"#E1E4E8"}},g={class:"shiki github-light vp-code-light"},b={class:"line"},m={style:{color:"#24292E"}},v=o("",1),k={class:"language-bash vp-adaptive-theme"},C=s("button",{title:"Copy Code",class:"copy"},null,-1),q=s("span",{class:"lang"},"bash",-1),f={class:"shiki github-dark vp-code-dark"},F={class:"line"},S={style:{color:"#E1E4E8"}},T={class:"shiki github-light vp-code-light"},w={class:"line"},A={style:{color:"#24292E"}},D=o("",16),O=JSON.parse('{"title":"Run an OP Stack rollup with Celestia underneath","description":"Start your own rollup with op-plasma-celestia and roll-op.","frontmatter":{"description":"Start your own rollup with op-plasma-celestia and roll-op.","next":{"text":"Ethereum fallback mechanism","link":"/developers/ethereum-fallback"},"head":[["meta",{"name":"og:title","content":"Run an OP Stack rollup with Celestia underneath | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/optimism.md","filePath":"developers/optimism.md","lastUpdated":1725971357000}'),P={name:"developers/optimism.md"},V=Object.assign(P,{setup(x){return(B,M)=>(t(),l("div",null,[p,s("div",c,[r,s("div",i,[s("div",d,[u,h,s("pre",y,[s("code",null,[s("span",_,[s("span",E,"$HOME/.celestia-light-"+e(n(a).mochaChainId),1)])])]),s("pre",g,[s("code",null,[s("span",b,[s("span",m,"$HOME/.celestia-light-"+e(n(a).mochaChainId),1)])])])]),v,s("div",k,[C,q,s("pre",f,[s("code",null,[s("span",F,[s("span",S,"$HOME/.celestia-light-"+e(n(a).arabicaChainId),1)])])]),s("pre",T,[s("code",null,[s("span",w,[s("span",A,"$HOME/.celestia-light-"+e(n(a).arabicaChainId),1)])])])])])]),D]))}});export{O as __pageData,V as default};
+import{c as a}from"./chunks/constants.295fc0ab.js";import{o as t,c as l,k as s,t as e,l as n,Q as o}from"./chunks/framework.b47e54aa.js";const p=o("",8),c={class:"vp-code-group vp-adaptive-theme"},r=o("",1),i={class:"blocks"},d={class:"language-bash vp-adaptive-theme active"},u=s("button",{title:"Copy Code",class:"copy"},null,-1),h=s("span",{class:"lang"},"bash",-1),y={class:"shiki github-dark vp-code-dark"},_={class:"line"},E={style:{color:"#E1E4E8"}},g={class:"shiki github-light vp-code-light"},m={class:"line"},b={style:{color:"#24292E"}},v=o("",1),k={class:"language-bash vp-adaptive-theme"},C=s("button",{title:"Copy Code",class:"copy"},null,-1),f=s("span",{class:"lang"},"bash",-1),F={class:"shiki github-dark vp-code-dark"},q={class:"line"},A={style:{color:"#E1E4E8"}},S={class:"shiki github-light vp-code-light"},w={class:"line"},T={style:{color:"#24292E"}},D=o("",16),O=JSON.parse('{"title":"Run an OP Stack rollup with Celestia underneath","description":"Start your own rollup with op-plasma-celestia and roll-op.","frontmatter":{"description":"Start your own rollup with op-plasma-celestia and roll-op.","next":{"text":"Ethereum fallback mechanism","link":"/developers/ethereum-fallback"},"head":[["meta",{"name":"og:title","content":"Run an OP Stack rollup with Celestia underneath | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/optimism.md","filePath":"developers/optimism.md","lastUpdated":1725992025000}'),P={name:"developers/optimism.md"},V=Object.assign(P,{setup(x){return(B,M)=>(t(),l("div",null,[p,s("div",c,[r,s("div",i,[s("div",d,[u,h,s("pre",y,[s("code",null,[s("span",_,[s("span",E,"$HOME/.celestia-light-"+e(n(a).mochaChainId),1)])])]),s("pre",g,[s("code",null,[s("span",m,[s("span",b,"$HOME/.celestia-light-"+e(n(a).mochaChainId),1)])])])]),v,s("div",k,[C,f,s("pre",F,[s("code",null,[s("span",q,[s("span",A,"$HOME/.celestia-light-"+e(n(a).arabicaChainId),1)])])]),s("pre",S,[s("code",null,[s("span",w,[s("span",T,"$HOME/.celestia-light-"+e(n(a).arabicaChainId),1)])])])])])]),D]))}});export{O as __pageData,V as default};
diff --git a/pr-1699/assets/developers_prompt-scavenger.md.fea07a57.js b/pr-1699/assets/developers_prompt-scavenger.md.ae717331.js
similarity index 99%
rename from pr-1699/assets/developers_prompt-scavenger.md.fea07a57.js
rename to pr-1699/assets/developers_prompt-scavenger.md.ae717331.js
index 8131a179c3..293fda62cd 100644
--- a/pr-1699/assets/developers_prompt-scavenger.md.fea07a57.js
+++ b/pr-1699/assets/developers_prompt-scavenger.md.ae717331.js
@@ -1,4 +1,4 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Prompt scavenger","description":"Learn how to interact with the Celestia Node API with this tutorial.","frontmatter":{"description":"Learn how to interact with the Celestia Node API with this tutorial.","prev":{"text":"Rust client tutorial","link":"/developers/rust-client-tutorial"},"head":[["meta",{"name":"og:title","content":"Prompt scavenger | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/prompt-scavenger.md","filePath":"developers/prompt-scavenger.md","lastUpdated":1725971357000}'),p={name:"developers/prompt-scavenger.md"},o=l(`
        Prompt scavenger ​
        Welcome to the world of Prompt Scavenger, a game where you’ll be using Celestia’s Node API and OpenAI’s GPT-3.5 to decode hidden messages scattered throughout Celestia’s blockchain. In this tutorial, we’ll be using Golang to write the code for the game.
        Through this tutorial, you’ll gain experience using Celestia’s Node API to fetch data from the blockchain, process it, and submit new transactions with that data. You’ll also learn how to integrate OpenAI’s GPT-3.5 API to generate fun responses based on the data you’ve found.
        So if you’re ready to embark on an adventure that combines blockchain technology with the power of AI, and learn some Golang along the way, let’s get started!
        Dependencies ​
        The following dependencies are needed to be installed or obtained:
        Install Celestia Node and run a light node ​
        First, install the celestia-node binary.
        Let's start by initializing our light node and funding our account with some tokens. We will be using the Arabica testnet for this tutorial.
        sh
        celestia light init --p2p.network arabica
        celestia light init --p2p.network arabica
        You will see an output ending with something looking like this:
        2024-05-22T14:15:49.554+0200	INFO	node	nodebuilder/init.go:211	NO KEY FOUND IN STORE, GENERATING NEW KEY...
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Prompt scavenger","description":"Learn how to interact with the Celestia Node API with this tutorial.","frontmatter":{"description":"Learn how to interact with the Celestia Node API with this tutorial.","prev":{"text":"Rust client tutorial","link":"/developers/rust-client-tutorial"},"head":[["meta",{"name":"og:title","content":"Prompt scavenger | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/prompt-scavenger.md","filePath":"developers/prompt-scavenger.md","lastUpdated":1725992025000}'),p={name:"developers/prompt-scavenger.md"},o=l(`
        Prompt scavenger ​
        Welcome to the world of Prompt Scavenger, a game where you’ll be using Celestia’s Node API and OpenAI’s GPT-3.5 to decode hidden messages scattered throughout Celestia’s blockchain. In this tutorial, we’ll be using Golang to write the code for the game.
        Through this tutorial, you’ll gain experience using Celestia’s Node API to fetch data from the blockchain, process it, and submit new transactions with that data. You’ll also learn how to integrate OpenAI’s GPT-3.5 API to generate fun responses based on the data you’ve found.
        So if you’re ready to embark on an adventure that combines blockchain technology with the power of AI, and learn some Golang along the way, let’s get started!
        Dependencies ​
        The following dependencies are needed to be installed or obtained:
        Install Celestia Node and run a light node ​
        First, install the celestia-node binary.
        Let's start by initializing our light node and funding our account with some tokens. We will be using the Arabica testnet for this tutorial.
        sh
        celestia light init --p2p.network arabica
        celestia light init --p2p.network arabica
        You will see an output ending with something looking like this:
        2024-05-22T14:15:49.554+0200	INFO	node	nodebuilder/init.go:211	NO KEY FOUND IN STORE, GENERATING NEW KEY...
 2024-05-22T14:15:49.564+0200	INFO	node	nodebuilder/init.go:216	NEW KEY GENERATED...
 
 NAME: my_celes_key
diff --git a/pr-1699/assets/developers_prompt-scavenger.md.fea07a57.lean.js b/pr-1699/assets/developers_prompt-scavenger.md.ae717331.lean.js
similarity index 84%
rename from pr-1699/assets/developers_prompt-scavenger.md.fea07a57.lean.js
rename to pr-1699/assets/developers_prompt-scavenger.md.ae717331.lean.js
index 30b4a0dc25..95f2d7ec9a 100644
--- a/pr-1699/assets/developers_prompt-scavenger.md.fea07a57.lean.js
+++ b/pr-1699/assets/developers_prompt-scavenger.md.ae717331.lean.js
@@ -1 +1 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Prompt scavenger","description":"Learn how to interact with the Celestia Node API with this tutorial.","frontmatter":{"description":"Learn how to interact with the Celestia Node API with this tutorial.","prev":{"text":"Rust client tutorial","link":"/developers/rust-client-tutorial"},"head":[["meta",{"name":"og:title","content":"Prompt scavenger | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/prompt-scavenger.md","filePath":"developers/prompt-scavenger.md","lastUpdated":1725971357000}'),p={name:"developers/prompt-scavenger.md"},o=l("",64),e=[o];function t(c,r,E,y,i,F){return n(),a("div",null,e)}const u=s(p,[["render",t]]);export{h as __pageData,u as default};
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Prompt scavenger","description":"Learn how to interact with the Celestia Node API with this tutorial.","frontmatter":{"description":"Learn how to interact with the Celestia Node API with this tutorial.","prev":{"text":"Rust client tutorial","link":"/developers/rust-client-tutorial"},"head":[["meta",{"name":"og:title","content":"Prompt scavenger | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/prompt-scavenger.md","filePath":"developers/prompt-scavenger.md","lastUpdated":1725992025000}'),p={name:"developers/prompt-scavenger.md"},o=l("",64),e=[o];function t(c,r,E,y,i,F){return n(),a("div",null,e)}const u=s(p,[["render",t]]);export{h as __pageData,u as default};
diff --git a/pr-1699/assets/developers_rust-client-tutorial.md.df611bd3.js b/pr-1699/assets/developers_rust-client-tutorial.md.168637c4.js
similarity index 99%
rename from pr-1699/assets/developers_rust-client-tutorial.md.df611bd3.js
rename to pr-1699/assets/developers_rust-client-tutorial.md.168637c4.js
index efff2b4037..9f0ac2f056 100644
--- a/pr-1699/assets/developers_rust-client-tutorial.md.df611bd3.js
+++ b/pr-1699/assets/developers_rust-client-tutorial.md.168637c4.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Rust client library tutorial","description":"","frontmatter":{"next":{"text":"Prompt Scavenger","link":"/developers/prompt-scavenger"},"head":[["meta",{"name":"og:title","content":"Rust client library tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/rust-client-tutorial.md","filePath":"developers/rust-client-tutorial.md","lastUpdated":1725971357000}'),p={name:"developers/rust-client-tutorial.md"},o=l(`
        Rust client library tutorial ​
        This section tutorial will guide you through using the most common RPC endpoints with Lumina's rust client library.
        Install dependencies and celestia-node if you have not already.
        Project setup ​
        To start, add celestia_rpc and celestia_types as a dependency to your project:
        bash
        cargo add celestia_rpc celestia_types
        cargo add celestia_rpc celestia_types
        To use the following methods, you will need the node URL and your auth token. To get your auth token, see this guide. To run your node without an auth token, you can use the --rpc.skip-auth flag when starting your node. This allows you to pass an empty string as your auth token.
        The default URL is http://localhost:26658. If you would like to use subscription methods, such as SubscribeHeaders below, you must use the ws protocol in place of http: ws://localhost:26658.
        Submitting and retrieving blobs ​
        The blob.Submit method takes an array of blobs and a gas price, returning the height the blob was successfully posted at.
        • The namespace can be generated with Namespace::new_v0.
        • The blobs can be generated with Blob::new.
        • You can set GasPrice::default() as the gas price to have celestia-node automatically determine an appropriate gas price.
        The blob.GetAll method takes a height and array of namespaces, returning the array of blobs found in the given namespaces.
        rust
        use celestia_rpc::{BlobClient, Client, HeaderClient, ShareClient};
+import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Rust client library tutorial","description":"","frontmatter":{"next":{"text":"Prompt Scavenger","link":"/developers/prompt-scavenger"},"head":[["meta",{"name":"og:title","content":"Rust client library tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/rust-client-tutorial.md","filePath":"developers/rust-client-tutorial.md","lastUpdated":1725992025000}'),p={name:"developers/rust-client-tutorial.md"},o=l(`
        Rust client library tutorial ​
        This section tutorial will guide you through using the most common RPC endpoints with Lumina's rust client library.
        Install dependencies and celestia-node if you have not already.
        Project setup ​
        To start, add celestia_rpc and celestia_types as a dependency to your project:
        bash
        cargo add celestia_rpc celestia_types
        cargo add celestia_rpc celestia_types
        To use the following methods, you will need the node URL and your auth token. To get your auth token, see this guide. To run your node without an auth token, you can use the --rpc.skip-auth flag when starting your node. This allows you to pass an empty string as your auth token.
        The default URL is http://localhost:26658. If you would like to use subscription methods, such as SubscribeHeaders below, you must use the ws protocol in place of http: ws://localhost:26658.
        Submitting and retrieving blobs ​
        The blob.Submit method takes an array of blobs and a gas price, returning the height the blob was successfully posted at.
        • The namespace can be generated with Namespace::new_v0.
        • The blobs can be generated with Blob::new.
        • You can set GasPrice::default() as the gas price to have celestia-node automatically determine an appropriate gas price.
        The blob.GetAll method takes a height and array of namespaces, returning the array of blobs found in the given namespaces.
        rust
        use celestia_rpc::{BlobClient, Client, HeaderClient, ShareClient};
 use celestia_types::blob::GasPrice;
 use celestia_types::{nmt::Namespace, Blob, ExtendedDataSquare};
 
diff --git a/pr-1699/assets/developers_rust-client-tutorial.md.df611bd3.lean.js b/pr-1699/assets/developers_rust-client-tutorial.md.168637c4.lean.js
similarity index 90%
rename from pr-1699/assets/developers_rust-client-tutorial.md.df611bd3.lean.js
rename to pr-1699/assets/developers_rust-client-tutorial.md.168637c4.lean.js
index 7dad95d7f0..fd5e61264b 100644
--- a/pr-1699/assets/developers_rust-client-tutorial.md.df611bd3.lean.js
+++ b/pr-1699/assets/developers_rust-client-tutorial.md.168637c4.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Rust client library tutorial","description":"","frontmatter":{"next":{"text":"Prompt Scavenger","link":"/developers/prompt-scavenger"},"head":[["meta",{"name":"og:title","content":"Rust client library tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/rust-client-tutorial.md","filePath":"developers/rust-client-tutorial.md","lastUpdated":1725971357000}'),p={name:"developers/rust-client-tutorial.md"},o=l("",21),e=[o];function t(c,r,E,y,i,F){return a(),n("div",null,e)}const u=s(p,[["render",t]]);export{h as __pageData,u as default};
+import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Rust client library tutorial","description":"","frontmatter":{"next":{"text":"Prompt Scavenger","link":"/developers/prompt-scavenger"},"head":[["meta",{"name":"og:title","content":"Rust client library tutorial | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/rust-client-tutorial.md","filePath":"developers/rust-client-tutorial.md","lastUpdated":1725992025000}'),p={name:"developers/rust-client-tutorial.md"},o=l("",21),e=[o];function t(c,r,E,y,i,F){return a(),n("div",null,e)}const u=s(p,[["render",t]]);export{h as __pageData,u as default};
diff --git a/pr-1699/assets/developers_sp1-blobstream-deploy.md.b0ce75b2.js b/pr-1699/assets/developers_sp1-blobstream-deploy.md.e4975a52.js
similarity index 98%
rename from pr-1699/assets/developers_sp1-blobstream-deploy.md.b0ce75b2.js
rename to pr-1699/assets/developers_sp1-blobstream-deploy.md.e4975a52.js
index 0255dbbd90..f784428f99 100644
--- a/pr-1699/assets/developers_sp1-blobstream-deploy.md.b0ce75b2.js
+++ b/pr-1699/assets/developers_sp1-blobstream-deploy.md.e4975a52.js
@@ -1,3 +1,3 @@
-import{_ as e,o as t,c as o,Q as s}from"./chunks/framework.b47e54aa.js";const y=JSON.parse('{"title":"New SP1 Blobstream deployments","description":"","frontmatter":{"next":{"text":"Integrate with Blobstream X contracts","link":"/developers/blobstream-contracts"},"head":[["meta",{"name":"og:title","content":"New SP1 Blobstream deployments | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/sp1-blobstream-deploy.md","filePath":"developers/sp1-blobstream-deploy.md","lastUpdated":1725971357000}'),a={name:"developers/sp1-blobstream-deploy.md"},l=s(`
        New SP1 Blobstream deployments ​
        This document provides instructions for deploying SP1 Blobstream to a new chain.
        SP1 Blobstream is the latest implementation of Blobstream in Rust using the SP1 zkVM.
        Deploying the contracts ​
        To deploy SP1 Blobstream to a new chain, follow these steps:
        1. Clone the sp1-blobstream repository:
        shell
        git clone https://github.com/succinctlabs/sp1-blobstream
+import{_ as e,o as t,c as o,Q as s}from"./chunks/framework.b47e54aa.js";const y=JSON.parse('{"title":"New SP1 Blobstream deployments","description":"","frontmatter":{"next":{"text":"Integrate with Blobstream X contracts","link":"/developers/blobstream-contracts"},"head":[["meta",{"name":"og:title","content":"New SP1 Blobstream deployments | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/sp1-blobstream-deploy.md","filePath":"developers/sp1-blobstream-deploy.md","lastUpdated":1725992025000}'),a={name:"developers/sp1-blobstream-deploy.md"},l=s(`
        New SP1 Blobstream deployments ​
        This document provides instructions for deploying SP1 Blobstream to a new chain.
        SP1 Blobstream is the latest implementation of Blobstream in Rust using the SP1 zkVM.
        Deploying the contracts ​
        To deploy SP1 Blobstream to a new chain, follow these steps:
        1. Clone the sp1-blobstream repository:
        shell
        git clone https://github.com/succinctlabs/sp1-blobstream
 cd sp1-blobstream
        git clone https://github.com/succinctlabs/sp1-blobstream
 cd sp1-blobstream
        1. Follow the deployment instructions in the sp1-blobstream README.
        2. If you're deploying on a chain where there isn't a canonical verifier listed in the SP1 contract addresses, you'll need to:
          a. Deploy your own SP1 Verifier from the sp1-contracts matching your sp1-sdk version. b. Set the SP1_VERIFIER_ADDRESS in your .env file to the address of your deployed verifier.
        3. To run the prover:
          • For local proving, set SP1_PROVER=local in your environment.
          • To use the Succinct Proving Network for remote proving, set SP1_PROVER=network.
          • We recommend an instance with 64 vCPU and 128GB of RAM for local proving.
        Note: Any whitelisting for custom provers would need to be implemented in the application's smart contracts (e.g., by using an approvedProvers mapping).
        `,9),n=[l];function r(p,c,i,d,h,b){return t(),o("div",null,n)}const u=e(a,[["render",r]]);export{y as __pageData,u as default};
diff --git a/pr-1699/assets/developers_sp1-blobstream-deploy.md.b0ce75b2.lean.js b/pr-1699/assets/developers_sp1-blobstream-deploy.md.e4975a52.lean.js
similarity index 91%
rename from pr-1699/assets/developers_sp1-blobstream-deploy.md.b0ce75b2.lean.js
rename to pr-1699/assets/developers_sp1-blobstream-deploy.md.e4975a52.lean.js
index 52aebc95a3..d3be89a062 100644
--- a/pr-1699/assets/developers_sp1-blobstream-deploy.md.b0ce75b2.lean.js
+++ b/pr-1699/assets/developers_sp1-blobstream-deploy.md.e4975a52.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as o,Q as s}from"./chunks/framework.b47e54aa.js";const y=JSON.parse('{"title":"New SP1 Blobstream deployments","description":"","frontmatter":{"next":{"text":"Integrate with Blobstream X contracts","link":"/developers/blobstream-contracts"},"head":[["meta",{"name":"og:title","content":"New SP1 Blobstream deployments | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/sp1-blobstream-deploy.md","filePath":"developers/sp1-blobstream-deploy.md","lastUpdated":1725971357000}'),a={name:"developers/sp1-blobstream-deploy.md"},l=s("",9),n=[l];function r(p,c,i,d,h,b){return t(),o("div",null,n)}const u=e(a,[["render",r]]);export{y as __pageData,u as default};
+import{_ as e,o as t,c as o,Q as s}from"./chunks/framework.b47e54aa.js";const y=JSON.parse('{"title":"New SP1 Blobstream deployments","description":"","frontmatter":{"next":{"text":"Integrate with Blobstream X contracts","link":"/developers/blobstream-contracts"},"head":[["meta",{"name":"og:title","content":"New SP1 Blobstream deployments | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/sp1-blobstream-deploy.md","filePath":"developers/sp1-blobstream-deploy.md","lastUpdated":1725992025000}'),a={name:"developers/sp1-blobstream-deploy.md"},l=s("",9),n=[l];function r(p,c,i,d,h,b){return t(),o("div",null,n)}const u=e(a,[["render",r]]);export{y as __pageData,u as default};
diff --git a/pr-1699/assets/developers_submit-data.md.506ef31e.js b/pr-1699/assets/developers_submit-data.md.7f90d09f.js
similarity index 99%
rename from pr-1699/assets/developers_submit-data.md.506ef31e.js
rename to pr-1699/assets/developers_submit-data.md.7f90d09f.js
index 624be8a9f6..38611f405a 100644
--- a/pr-1699/assets/developers_submit-data.md.506ef31e.js
+++ b/pr-1699/assets/developers_submit-data.md.7f90d09f.js
@@ -1,4 +1,4 @@
-import{_ as t,o as a,c as n,k as s,a as l,Q as e}from"./chunks/framework.b47e54aa.js";const ts=JSON.parse('{"title":"Submitting data blobs to Celestia","description":"","frontmatter":{"prev":{"text":"Blobstream rollups","link":"/developers/blobstream-rollups"},"head":[["meta",{"name":"og:title","content":"Submitting data blobs to Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/submit-data.md","filePath":"developers/submit-data.md","lastUpdated":1725971357000}'),o={name:"developers/submit-data.md"},p=e('
        Submitting data blobs to Celestia ​
        To submit data to Celestia, users submit blob transactions (BlobTx). Blob transactions contain two components, a standard Cosmos-SDK transaction called MsgPayForBlobs and one or more Blobs of data.
        Maximum blob size ​
        The maximum total blob size in a transaction is just under 2 MiB (1,973,786 bytes), based on a 64x64 share grid (4096 shares). With one share for the PFB transaction, 4095 shares remain: 1 at 478 bytes and 4094 at 482 bytes each.
        This is subject to change based on governance parameters. Learn more on the Mainnet Beta page under "Maximum bytes".
        It is advisable to submit transactions where the total blob size is significantly smaller than 1.8 MiB (e.g. 500 KiB) in order for your transaction to get included in a block quickly. If a tx contains blobs approaching 1.8 MiB then there will be no room for any other transactions. This means that your transaction will only be included in a block if it has a higher gas price than every other transaction in the mempool.
        Fee market and mempool ​
        Celestia makes use of a standard gas-priced prioritized mempool. By default, transactions with gas prices higher than that of other transactions in the mempool will be prioritized by validators.
        Fees and gas limits ​
        As of version v1.0.0 of the application (celestia-app), there is no protocol enforced minimum fee (similar to EIP-1559 in Ethereum). Instead, each consensus node running a mempool uses a locally configured gas price threshold that must be met in order for that node to accept a transaction, either directly from a user or gossiped from another node, into its mempool.
        As of version v1.0.0 of the application (celestia-app), gas is not refunded. Instead, transaction fees are deducted by a flat fee, originally specified by the user in their tx (where fees = gasLimit * gasPrice). This means that users should use an accurate gas limit value if they do not wish to overpay.
        Under the hood, fees are currently handled by specifying and deducting a flat fee. However gas price is often specified by users instead of calculating the flat fee from the gas used and the gas price. Since the state machine does not refund users for unused gas, gas price is calculated by dividing the total fee by the gas limit.
        Estimating PFB gas ​
        Generally, the gas used by a PFB transaction involves a static fixed cost and a dynamic cost based on the size of each blob in the transaction.
        NOTE
        For a general use case of a normal account submitting a PFB, the static costs can be treated as such. However, due to the description above of how gas works in the Cosmos-SDK this is not always the case. Notably, if a vesting account or the feegrant modules are used, then these static costs change.
        The fixed cost is an approximation of the gas consumed by operations outside the function GasToConsume (for example, signature verification, tx size, read access to accounts), which has a default value of 65,000 gas.
        NOTE
        The first transaction sent by an account (sequence number == 0) has an additional one time gas cost of 10,000 gas. If this is the case, this should be accounted for.
        Each blob in the PFB contributes to the total gas cost based on its size. The function GasToConsume calculates the total gas consumed by all the blobs involved in a PFB, where each blob's gas cost is computed by first determining how many shares are needed to store the blob size. Then, it computes the product of the number of shares, the number of bytes per share, and the gasPerByte parameter. Finally, it adds a static amount per blob.
        The blob.GasPerBlobByte and auth.TxSizeCostPerByte are parameters that could potentially be adjusted through the system's governance mechanisms. Hence, actual costs may vary depending on the current state of these parameters.
        Gas fee calculation ​
        The total fee for a transaction is calculated as the product of the gas limit for the transaction and the gas price set by the user:
        ',21),r={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},c={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.186ex"},xmlns:"http://www.w3.org/2000/svg",width:"34.471ex",height:"1.781ex",role:"img",focusable:"false",viewBox:"0 -705 15236 787","aria-hidden":"true"},i=e('',1),Q=[i],T=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mtext",null,"Total Fee"),s("mo",null,"="),s("mtext",null,"Gas Limit"),s("mo",null,"×"),s("mtext",null,"Gas Price")])],-1),y=s("p",null,"The gas limit for a transaction is the maximum amount of gas that a user is willing to spend on a transaction. It is determined by both a static fixed cost (FC) and a variable dynamic cost based on the size of each blob involved in the transaction:",-1),E={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},d={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.777ex"},xmlns:"http://www.w3.org/2000/svg",width:"50.774ex",height:"2.563ex",role:"img",focusable:"false",viewBox:"0 -789.6 22442.1 1132.9","aria-hidden":"true"},h=e('',1),m=[h],u=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mtext",null,"Gas Limit"),s("mo",null,"="),s("mi",null,"F"),s("mi",null,"C"),s("mo",null,"+"),s("munderover",null,[s("mo",{"data-mjx-texclass":"OP"},"∑"),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"i"),s("mo",null,"="),s("mn",null,"1")]),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"n")])]),s("mi",null,"S"),s("mi",null,"S"),s("mi",null,"N"),s("mo",{stretchy:"false"},"("),s("msub",null,[s("mi",null,"B"),s("mi",null,"i")]),s("mo",{stretchy:"false"},")"),s("mo",null,"×"),s("mi",null,"S"),s("mi",null,"S"),s("mo",null,"×"),s("mi",null,"G"),s("mi",null,"C"),s("mi",null,"P"),s("mi",null,"B"),s("mi",null,"B")])],-1),g=s("p",null,"Where:",-1),b={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},F={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"3.414ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 1509 727","aria-hidden":"true"},f=e('',1),H=[f],C=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"F"),s("mi",null,"C")])],-1),x={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},w={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.777ex"},xmlns:"http://www.w3.org/2000/svg",width:"14.695ex",height:"2.563ex",role:"img",focusable:"false",viewBox:"0 -789.6 6495.3 1132.9","aria-hidden":"true"},k=e('',1),B=[k],D=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("munderover",null,[s("mo",{"data-mjx-texclass":"OP"},"∑"),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"i"),s("mo",null,"="),s("mn",null,"1")]),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"n")])]),s("mi",null,"S"),s("mi",null,"S"),s("mi",null,"N"),s("mo",{stretchy:"false"},"("),s("msub",null,[s("mi",null,"B"),s("mi",null,"i")]),s("mo",{stretchy:"false"},")")])],-1),V={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},L={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"0.781ex",height:"1.52ex",role:"img",focusable:"false",viewBox:"0 -661 345 672","aria-hidden":"true"},A=s("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[s("g",{"data-mml-node":"math"},[s("g",{"data-mml-node":"mi"},[s("path",{"data-c":"1D456",d:"M184 600Q184 624 203 642T247 661Q265 661 277 649T290 619Q290 596 270 577T226 557Q211 557 198 567T184 600ZM21 287Q21 295 30 318T54 369T98 420T158 442Q197 442 223 419T250 357Q250 340 236 301T196 196T154 83Q149 61 149 51Q149 26 166 26Q175 26 185 29T208 43T235 78T260 137Q263 149 265 151T282 153Q302 153 302 143Q302 135 293 112T268 61T223 11T161 -11Q129 -11 102 10T74 74Q74 91 79 106T122 220Q160 321 166 341T173 380Q173 404 156 404H154Q124 404 99 371T61 287Q60 286 59 284T58 281T56 279T53 278T49 278T41 278H27Q21 284 21 287Z",style:{"stroke-width":"3"}})])])],-1),_=[A],v=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"i")])],-1),M={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},q={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"0.781ex",height:"1.52ex",role:"img",focusable:"false",viewBox:"0 -661 345 672","aria-hidden":"true"},Z=s("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[s("g",{"data-mml-node":"math"},[s("g",{"data-mml-node":"mi"},[s("path",{"data-c":"1D456",d:"M184 600Q184 624 203 642T247 661Q265 661 277 649T290 619Q290 596 270 577T226 557Q211 557 198 567T184 600ZM21 287Q21 295 30 318T54 369T98 420T158 442Q197 442 223 419T250 357Q250 340 236 301T196 196T154 83Q149 61 149 51Q149 26 166 26Q175 26 185 29T208 43T235 78T260 137Q263 149 265 151T282 153Q302 153 302 143Q302 135 293 112T268 61T223 11T161 -11Q129 -11 102 10T74 74Q74 91 79 106T122 220Q160 321 166 341T173 380Q173 404 156 404H154Q124 404 99 371T61 287Q60 286 59 284T58 281T56 279T53 278T49 278T41 278H27Q21 284 21 287Z",style:{"stroke-width":"3"}})])])],-1),P=[Z],S=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"i")])],-1),I={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},N={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.919ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 1290 727","aria-hidden":"true"},j=e('',1),G=[j],z=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"S"),s("mi",null,"S")])],-1),O={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"8.631ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 3815 727","aria-hidden":"true"},W=e('',1),J=[W],K=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"G"),s("mi",null,"C"),s("mi",null,"P"),s("mi",null,"B"),s("mi",null,"B")])],-1),U=e(`
        The gas fee is set by the user when they submit a transaction. The fee is often specified by users directly. The total cost for the transaction is then calculated as the product of the estimated gas limit and the gas price. Since the state machine does not refund users for unused gas, it's important for users to estimate the gas limit accurately to avoid overpaying.
        For more details on how gas is calculated per blob, refer to the PayForBlobs function that consumes gas based on the blob sizes. This function uses the GasToConsume function to calculate the extra gas charged to pay for a set of blobs in a MsgPayForBlobs transaction. This function calculates the total shares used by all blobs and multiplies it by the ShareSize and gasPerByte to get the total gas to consume.
        For estimating the total gas required for a set of blobs, refer to the EstimateGas function. This function estimates the gas based on a linear model that is dependent on the governance parameters: gasPerByte and txSizeCost. It assumes other variables are constant, including the assumption that the MsgPayForBlobs is the only message in the transaction. The DefaultEstimateGas function runs EstimateGas with the system defaults.
        Estimating gas programmatically ​
        Users can estimate an efficient gas limit by using this function:
        go
        import (
+import{_ as t,o as a,c as n,k as s,a as l,Q as e}from"./chunks/framework.b47e54aa.js";const ts=JSON.parse('{"title":"Submitting data blobs to Celestia","description":"","frontmatter":{"prev":{"text":"Blobstream rollups","link":"/developers/blobstream-rollups"},"head":[["meta",{"name":"og:title","content":"Submitting data blobs to Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/submit-data.md","filePath":"developers/submit-data.md","lastUpdated":1725992025000}'),o={name:"developers/submit-data.md"},p=e('
        Submitting data blobs to Celestia ​
        To submit data to Celestia, users submit blob transactions (BlobTx). Blob transactions contain two components, a standard Cosmos-SDK transaction called MsgPayForBlobs and one or more Blobs of data.
        Maximum blob size ​
        The maximum total blob size in a transaction is just under 2 MiB (1,973,786 bytes), based on a 64x64 share grid (4096 shares). With one share for the PFB transaction, 4095 shares remain: 1 at 478 bytes and 4094 at 482 bytes each.
        This is subject to change based on governance parameters. Learn more on the Mainnet Beta page under "Maximum bytes".
        It is advisable to submit transactions where the total blob size is significantly smaller than 1.8 MiB (e.g. 500 KiB) in order for your transaction to get included in a block quickly. If a tx contains blobs approaching 1.8 MiB then there will be no room for any other transactions. This means that your transaction will only be included in a block if it has a higher gas price than every other transaction in the mempool.
        Fee market and mempool ​
        Celestia makes use of a standard gas-priced prioritized mempool. By default, transactions with gas prices higher than that of other transactions in the mempool will be prioritized by validators.
        Fees and gas limits ​
        As of version v1.0.0 of the application (celestia-app), there is no protocol enforced minimum fee (similar to EIP-1559 in Ethereum). Instead, each consensus node running a mempool uses a locally configured gas price threshold that must be met in order for that node to accept a transaction, either directly from a user or gossiped from another node, into its mempool.
        As of version v1.0.0 of the application (celestia-app), gas is not refunded. Instead, transaction fees are deducted by a flat fee, originally specified by the user in their tx (where fees = gasLimit * gasPrice). This means that users should use an accurate gas limit value if they do not wish to overpay.
        Under the hood, fees are currently handled by specifying and deducting a flat fee. However gas price is often specified by users instead of calculating the flat fee from the gas used and the gas price. Since the state machine does not refund users for unused gas, gas price is calculated by dividing the total fee by the gas limit.
        Estimating PFB gas ​
        Generally, the gas used by a PFB transaction involves a static fixed cost and a dynamic cost based on the size of each blob in the transaction.
        NOTE
        For a general use case of a normal account submitting a PFB, the static costs can be treated as such. However, due to the description above of how gas works in the Cosmos-SDK this is not always the case. Notably, if a vesting account or the feegrant modules are used, then these static costs change.
        The fixed cost is an approximation of the gas consumed by operations outside the function GasToConsume (for example, signature verification, tx size, read access to accounts), which has a default value of 65,000 gas.
        NOTE
        The first transaction sent by an account (sequence number == 0) has an additional one time gas cost of 10,000 gas. If this is the case, this should be accounted for.
        Each blob in the PFB contributes to the total gas cost based on its size. The function GasToConsume calculates the total gas consumed by all the blobs involved in a PFB, where each blob's gas cost is computed by first determining how many shares are needed to store the blob size. Then, it computes the product of the number of shares, the number of bytes per share, and the gasPerByte parameter. Finally, it adds a static amount per blob.
        The blob.GasPerBlobByte and auth.TxSizeCostPerByte are parameters that could potentially be adjusted through the system's governance mechanisms. Hence, actual costs may vary depending on the current state of these parameters.
        Gas fee calculation ​
        The total fee for a transaction is calculated as the product of the gas limit for the transaction and the gas price set by the user:
        ',21),r={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},c={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.186ex"},xmlns:"http://www.w3.org/2000/svg",width:"34.471ex",height:"1.781ex",role:"img",focusable:"false",viewBox:"0 -705 15236 787","aria-hidden":"true"},i=e('',1),Q=[i],T=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mtext",null,"Total Fee"),s("mo",null,"="),s("mtext",null,"Gas Limit"),s("mo",null,"×"),s("mtext",null,"Gas Price")])],-1),y=s("p",null,"The gas limit for a transaction is the maximum amount of gas that a user is willing to spend on a transaction. It is determined by both a static fixed cost (FC) and a variable dynamic cost based on the size of each blob involved in the transaction:",-1),E={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},d={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.777ex"},xmlns:"http://www.w3.org/2000/svg",width:"50.774ex",height:"2.563ex",role:"img",focusable:"false",viewBox:"0 -789.6 22442.1 1132.9","aria-hidden":"true"},h=e('',1),m=[h],u=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mtext",null,"Gas Limit"),s("mo",null,"="),s("mi",null,"F"),s("mi",null,"C"),s("mo",null,"+"),s("munderover",null,[s("mo",{"data-mjx-texclass":"OP"},"∑"),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"i"),s("mo",null,"="),s("mn",null,"1")]),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"n")])]),s("mi",null,"S"),s("mi",null,"S"),s("mi",null,"N"),s("mo",{stretchy:"false"},"("),s("msub",null,[s("mi",null,"B"),s("mi",null,"i")]),s("mo",{stretchy:"false"},")"),s("mo",null,"×"),s("mi",null,"S"),s("mi",null,"S"),s("mo",null,"×"),s("mi",null,"G"),s("mi",null,"C"),s("mi",null,"P"),s("mi",null,"B"),s("mi",null,"B")])],-1),g=s("p",null,"Where:",-1),b={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},F={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"3.414ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 1509 727","aria-hidden":"true"},f=e('',1),H=[f],C=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"F"),s("mi",null,"C")])],-1),x={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},w={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.777ex"},xmlns:"http://www.w3.org/2000/svg",width:"14.695ex",height:"2.563ex",role:"img",focusable:"false",viewBox:"0 -789.6 6495.3 1132.9","aria-hidden":"true"},k=e('',1),B=[k],D=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("munderover",null,[s("mo",{"data-mjx-texclass":"OP"},"∑"),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"i"),s("mo",null,"="),s("mn",null,"1")]),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"n")])]),s("mi",null,"S"),s("mi",null,"S"),s("mi",null,"N"),s("mo",{stretchy:"false"},"("),s("msub",null,[s("mi",null,"B"),s("mi",null,"i")]),s("mo",{stretchy:"false"},")")])],-1),V={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},L={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"0.781ex",height:"1.52ex",role:"img",focusable:"false",viewBox:"0 -661 345 672","aria-hidden":"true"},A=s("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[s("g",{"data-mml-node":"math"},[s("g",{"data-mml-node":"mi"},[s("path",{"data-c":"1D456",d:"M184 600Q184 624 203 642T247 661Q265 661 277 649T290 619Q290 596 270 577T226 557Q211 557 198 567T184 600ZM21 287Q21 295 30 318T54 369T98 420T158 442Q197 442 223 419T250 357Q250 340 236 301T196 196T154 83Q149 61 149 51Q149 26 166 26Q175 26 185 29T208 43T235 78T260 137Q263 149 265 151T282 153Q302 153 302 143Q302 135 293 112T268 61T223 11T161 -11Q129 -11 102 10T74 74Q74 91 79 106T122 220Q160 321 166 341T173 380Q173 404 156 404H154Q124 404 99 371T61 287Q60 286 59 284T58 281T56 279T53 278T49 278T41 278H27Q21 284 21 287Z",style:{"stroke-width":"3"}})])])],-1),_=[A],v=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"i")])],-1),M={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},q={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"0.781ex",height:"1.52ex",role:"img",focusable:"false",viewBox:"0 -661 345 672","aria-hidden":"true"},Z=s("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[s("g",{"data-mml-node":"math"},[s("g",{"data-mml-node":"mi"},[s("path",{"data-c":"1D456",d:"M184 600Q184 624 203 642T247 661Q265 661 277 649T290 619Q290 596 270 577T226 557Q211 557 198 567T184 600ZM21 287Q21 295 30 318T54 369T98 420T158 442Q197 442 223 419T250 357Q250 340 236 301T196 196T154 83Q149 61 149 51Q149 26 166 26Q175 26 185 29T208 43T235 78T260 137Q263 149 265 151T282 153Q302 153 302 143Q302 135 293 112T268 61T223 11T161 -11Q129 -11 102 10T74 74Q74 91 79 106T122 220Q160 321 166 341T173 380Q173 404 156 404H154Q124 404 99 371T61 287Q60 286 59 284T58 281T56 279T53 278T49 278T41 278H27Q21 284 21 287Z",style:{"stroke-width":"3"}})])])],-1),P=[Z],S=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"i")])],-1),I={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},N={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.919ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 1290 727","aria-hidden":"true"},j=e('',1),G=[j],z=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"S"),s("mi",null,"S")])],-1),O={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"8.631ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 3815 727","aria-hidden":"true"},W=e('',1),J=[W],K=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"G"),s("mi",null,"C"),s("mi",null,"P"),s("mi",null,"B"),s("mi",null,"B")])],-1),U=e(`
        The gas fee is set by the user when they submit a transaction. The fee is often specified by users directly. The total cost for the transaction is then calculated as the product of the estimated gas limit and the gas price. Since the state machine does not refund users for unused gas, it's important for users to estimate the gas limit accurately to avoid overpaying.
        For more details on how gas is calculated per blob, refer to the PayForBlobs function that consumes gas based on the blob sizes. This function uses the GasToConsume function to calculate the extra gas charged to pay for a set of blobs in a MsgPayForBlobs transaction. This function calculates the total shares used by all blobs and multiplies it by the ShareSize and gasPerByte to get the total gas to consume.
        For estimating the total gas required for a set of blobs, refer to the EstimateGas function. This function estimates the gas based on a linear model that is dependent on the governance parameters: gasPerByte and txSizeCost. It assumes other variables are constant, including the assumption that the MsgPayForBlobs is the only message in the transaction. The DefaultEstimateGas function runs EstimateGas with the system defaults.
        Estimating gas programmatically ​
        Users can estimate an efficient gas limit by using this function:
        go
        import (
     blobtypes "github.com/celestiaorg/celestia-app/x/blob/types"
 )
 gasLimit := blobtypes.DefaultEstimateGas([]uint32{uint32(sizeOfDataInBytes)})
        import (
diff --git a/pr-1699/assets/developers_submit-data.md.506ef31e.lean.js b/pr-1699/assets/developers_submit-data.md.7f90d09f.lean.js
similarity index 99%
rename from pr-1699/assets/developers_submit-data.md.506ef31e.lean.js
rename to pr-1699/assets/developers_submit-data.md.7f90d09f.lean.js
index bd8bf349d7..6a62d568cc 100644
--- a/pr-1699/assets/developers_submit-data.md.506ef31e.lean.js
+++ b/pr-1699/assets/developers_submit-data.md.7f90d09f.lean.js
@@ -1 +1 @@
-import{_ as t,o as a,c as n,k as s,a as l,Q as e}from"./chunks/framework.b47e54aa.js";const ts=JSON.parse('{"title":"Submitting data blobs to Celestia","description":"","frontmatter":{"prev":{"text":"Blobstream rollups","link":"/developers/blobstream-rollups"},"head":[["meta",{"name":"og:title","content":"Submitting data blobs to Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/submit-data.md","filePath":"developers/submit-data.md","lastUpdated":1725971357000}'),o={name:"developers/submit-data.md"},p=e("",21),r={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},c={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.186ex"},xmlns:"http://www.w3.org/2000/svg",width:"34.471ex",height:"1.781ex",role:"img",focusable:"false",viewBox:"0 -705 15236 787","aria-hidden":"true"},i=e("",1),Q=[i],T=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mtext",null,"Total Fee"),s("mo",null,"="),s("mtext",null,"Gas Limit"),s("mo",null,"×"),s("mtext",null,"Gas Price")])],-1),y=s("p",null,"The gas limit for a transaction is the maximum amount of gas that a user is willing to spend on a transaction. It is determined by both a static fixed cost (FC) and a variable dynamic cost based on the size of each blob involved in the transaction:",-1),E={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},d={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.777ex"},xmlns:"http://www.w3.org/2000/svg",width:"50.774ex",height:"2.563ex",role:"img",focusable:"false",viewBox:"0 -789.6 22442.1 1132.9","aria-hidden":"true"},h=e("",1),m=[h],u=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mtext",null,"Gas Limit"),s("mo",null,"="),s("mi",null,"F"),s("mi",null,"C"),s("mo",null,"+"),s("munderover",null,[s("mo",{"data-mjx-texclass":"OP"},"∑"),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"i"),s("mo",null,"="),s("mn",null,"1")]),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"n")])]),s("mi",null,"S"),s("mi",null,"S"),s("mi",null,"N"),s("mo",{stretchy:"false"},"("),s("msub",null,[s("mi",null,"B"),s("mi",null,"i")]),s("mo",{stretchy:"false"},")"),s("mo",null,"×"),s("mi",null,"S"),s("mi",null,"S"),s("mo",null,"×"),s("mi",null,"G"),s("mi",null,"C"),s("mi",null,"P"),s("mi",null,"B"),s("mi",null,"B")])],-1),g=s("p",null,"Where:",-1),b={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},F={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"3.414ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 1509 727","aria-hidden":"true"},f=e("",1),H=[f],C=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"F"),s("mi",null,"C")])],-1),x={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},w={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.777ex"},xmlns:"http://www.w3.org/2000/svg",width:"14.695ex",height:"2.563ex",role:"img",focusable:"false",viewBox:"0 -789.6 6495.3 1132.9","aria-hidden":"true"},k=e("",1),B=[k],D=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("munderover",null,[s("mo",{"data-mjx-texclass":"OP"},"∑"),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"i"),s("mo",null,"="),s("mn",null,"1")]),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"n")])]),s("mi",null,"S"),s("mi",null,"S"),s("mi",null,"N"),s("mo",{stretchy:"false"},"("),s("msub",null,[s("mi",null,"B"),s("mi",null,"i")]),s("mo",{stretchy:"false"},")")])],-1),V={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},L={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"0.781ex",height:"1.52ex",role:"img",focusable:"false",viewBox:"0 -661 345 672","aria-hidden":"true"},A=s("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[s("g",{"data-mml-node":"math"},[s("g",{"data-mml-node":"mi"},[s("path",{"data-c":"1D456",d:"M184 600Q184 624 203 642T247 661Q265 661 277 649T290 619Q290 596 270 577T226 557Q211 557 198 567T184 600ZM21 287Q21 295 30 318T54 369T98 420T158 442Q197 442 223 419T250 357Q250 340 236 301T196 196T154 83Q149 61 149 51Q149 26 166 26Q175 26 185 29T208 43T235 78T260 137Q263 149 265 151T282 153Q302 153 302 143Q302 135 293 112T268 61T223 11T161 -11Q129 -11 102 10T74 74Q74 91 79 106T122 220Q160 321 166 341T173 380Q173 404 156 404H154Q124 404 99 371T61 287Q60 286 59 284T58 281T56 279T53 278T49 278T41 278H27Q21 284 21 287Z",style:{"stroke-width":"3"}})])])],-1),_=[A],v=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"i")])],-1),M={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},q={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"0.781ex",height:"1.52ex",role:"img",focusable:"false",viewBox:"0 -661 345 672","aria-hidden":"true"},Z=s("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[s("g",{"data-mml-node":"math"},[s("g",{"data-mml-node":"mi"},[s("path",{"data-c":"1D456",d:"M184 600Q184 624 203 642T247 661Q265 661 277 649T290 619Q290 596 270 577T226 557Q211 557 198 567T184 600ZM21 287Q21 295 30 318T54 369T98 420T158 442Q197 442 223 419T250 357Q250 340 236 301T196 196T154 83Q149 61 149 51Q149 26 166 26Q175 26 185 29T208 43T235 78T260 137Q263 149 265 151T282 153Q302 153 302 143Q302 135 293 112T268 61T223 11T161 -11Q129 -11 102 10T74 74Q74 91 79 106T122 220Q160 321 166 341T173 380Q173 404 156 404H154Q124 404 99 371T61 287Q60 286 59 284T58 281T56 279T53 278T49 278T41 278H27Q21 284 21 287Z",style:{"stroke-width":"3"}})])])],-1),P=[Z],S=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"i")])],-1),I={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},N={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.919ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 1290 727","aria-hidden":"true"},j=e("",1),G=[j],z=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"S"),s("mi",null,"S")])],-1),O={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"8.631ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 3815 727","aria-hidden":"true"},W=e("",1),J=[W],K=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"G"),s("mi",null,"C"),s("mi",null,"P"),s("mi",null,"B"),s("mi",null,"B")])],-1),U=e("",28);function X($,Y,ss,as,ns,es){return a(),n("div",null,[p,s("p",null,[s("mjx-container",r,[(a(),n("svg",c,Q)),T])]),y,s("p",null,[s("mjx-container",E,[(a(),n("svg",d,m)),u])]),g,s("ul",null,[s("li",null,[s("mjx-container",b,[(a(),n("svg",F,H)),C]),l(" = Fixed Cost, is a static value (65,000 gas)")]),s("li",null,[s("mjx-container",x,[(a(),n("svg",w,B)),D]),l(" = SparseSharesNeeded for the "),s("mjx-container",V,[(a(),n("svg",L,_)),v]),l("th Blob, is the number of shares needed for the "),s("mjx-container",M,[(a(),n("svg",q,P)),S]),l("th blob in the transaction")]),s("li",null,[s("mjx-container",I,[(a(),n("svg",N,G)),z]),l(" = Share Size, is the size of each share")]),s("li",null,[s("mjx-container",O,[(a(),n("svg",R,J)),K]),l(" = Gas Cost Per Blob Byte, is a parameter that could potentially be adjusted through the system's governance mechanisms.")])]),U])}const os=t(o,[["render",X]]);export{ts as __pageData,os as default};
+import{_ as t,o as a,c as n,k as s,a as l,Q as e}from"./chunks/framework.b47e54aa.js";const ts=JSON.parse('{"title":"Submitting data blobs to Celestia","description":"","frontmatter":{"prev":{"text":"Blobstream rollups","link":"/developers/blobstream-rollups"},"head":[["meta",{"name":"og:title","content":"Submitting data blobs to Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/submit-data.md","filePath":"developers/submit-data.md","lastUpdated":1725992025000}'),o={name:"developers/submit-data.md"},p=e("",21),r={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},c={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.186ex"},xmlns:"http://www.w3.org/2000/svg",width:"34.471ex",height:"1.781ex",role:"img",focusable:"false",viewBox:"0 -705 15236 787","aria-hidden":"true"},i=e("",1),Q=[i],T=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mtext",null,"Total Fee"),s("mo",null,"="),s("mtext",null,"Gas Limit"),s("mo",null,"×"),s("mtext",null,"Gas Price")])],-1),y=s("p",null,"The gas limit for a transaction is the maximum amount of gas that a user is willing to spend on a transaction. It is determined by both a static fixed cost (FC) and a variable dynamic cost based on the size of each blob involved in the transaction:",-1),E={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},d={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.777ex"},xmlns:"http://www.w3.org/2000/svg",width:"50.774ex",height:"2.563ex",role:"img",focusable:"false",viewBox:"0 -789.6 22442.1 1132.9","aria-hidden":"true"},h=e("",1),m=[h],u=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mtext",null,"Gas Limit"),s("mo",null,"="),s("mi",null,"F"),s("mi",null,"C"),s("mo",null,"+"),s("munderover",null,[s("mo",{"data-mjx-texclass":"OP"},"∑"),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"i"),s("mo",null,"="),s("mn",null,"1")]),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"n")])]),s("mi",null,"S"),s("mi",null,"S"),s("mi",null,"N"),s("mo",{stretchy:"false"},"("),s("msub",null,[s("mi",null,"B"),s("mi",null,"i")]),s("mo",{stretchy:"false"},")"),s("mo",null,"×"),s("mi",null,"S"),s("mi",null,"S"),s("mo",null,"×"),s("mi",null,"G"),s("mi",null,"C"),s("mi",null,"P"),s("mi",null,"B"),s("mi",null,"B")])],-1),g=s("p",null,"Where:",-1),b={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},F={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"3.414ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 1509 727","aria-hidden":"true"},f=e("",1),H=[f],C=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"F"),s("mi",null,"C")])],-1),x={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},w={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.777ex"},xmlns:"http://www.w3.org/2000/svg",width:"14.695ex",height:"2.563ex",role:"img",focusable:"false",viewBox:"0 -789.6 6495.3 1132.9","aria-hidden":"true"},k=e("",1),B=[k],D=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("munderover",null,[s("mo",{"data-mjx-texclass":"OP"},"∑"),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"i"),s("mo",null,"="),s("mn",null,"1")]),s("mrow",{"data-mjx-texclass":"ORD"},[s("mi",null,"n")])]),s("mi",null,"S"),s("mi",null,"S"),s("mi",null,"N"),s("mo",{stretchy:"false"},"("),s("msub",null,[s("mi",null,"B"),s("mi",null,"i")]),s("mo",{stretchy:"false"},")")])],-1),V={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},L={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"0.781ex",height:"1.52ex",role:"img",focusable:"false",viewBox:"0 -661 345 672","aria-hidden":"true"},A=s("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[s("g",{"data-mml-node":"math"},[s("g",{"data-mml-node":"mi"},[s("path",{"data-c":"1D456",d:"M184 600Q184 624 203 642T247 661Q265 661 277 649T290 619Q290 596 270 577T226 557Q211 557 198 567T184 600ZM21 287Q21 295 30 318T54 369T98 420T158 442Q197 442 223 419T250 357Q250 340 236 301T196 196T154 83Q149 61 149 51Q149 26 166 26Q175 26 185 29T208 43T235 78T260 137Q263 149 265 151T282 153Q302 153 302 143Q302 135 293 112T268 61T223 11T161 -11Q129 -11 102 10T74 74Q74 91 79 106T122 220Q160 321 166 341T173 380Q173 404 156 404H154Q124 404 99 371T61 287Q60 286 59 284T58 281T56 279T53 278T49 278T41 278H27Q21 284 21 287Z",style:{"stroke-width":"3"}})])])],-1),_=[A],v=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"i")])],-1),M={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},q={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"0.781ex",height:"1.52ex",role:"img",focusable:"false",viewBox:"0 -661 345 672","aria-hidden":"true"},Z=s("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[s("g",{"data-mml-node":"math"},[s("g",{"data-mml-node":"mi"},[s("path",{"data-c":"1D456",d:"M184 600Q184 624 203 642T247 661Q265 661 277 649T290 619Q290 596 270 577T226 557Q211 557 198 567T184 600ZM21 287Q21 295 30 318T54 369T98 420T158 442Q197 442 223 419T250 357Q250 340 236 301T196 196T154 83Q149 61 149 51Q149 26 166 26Q175 26 185 29T208 43T235 78T260 137Q263 149 265 151T282 153Q302 153 302 143Q302 135 293 112T268 61T223 11T161 -11Q129 -11 102 10T74 74Q74 91 79 106T122 220Q160 321 166 341T173 380Q173 404 156 404H154Q124 404 99 371T61 287Q60 286 59 284T58 281T56 279T53 278T49 278T41 278H27Q21 284 21 287Z",style:{"stroke-width":"3"}})])])],-1),P=[Z],S=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"i")])],-1),I={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},N={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.919ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 1290 727","aria-hidden":"true"},j=e("",1),G=[j],z=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"S"),s("mi",null,"S")])],-1),O={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.05ex"},xmlns:"http://www.w3.org/2000/svg",width:"8.631ex",height:"1.645ex",role:"img",focusable:"false",viewBox:"0 -705 3815 727","aria-hidden":"true"},W=e("",1),J=[W],K=s("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[s("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[s("mi",null,"G"),s("mi",null,"C"),s("mi",null,"P"),s("mi",null,"B"),s("mi",null,"B")])],-1),U=e("",28);function X($,Y,ss,as,ns,es){return a(),n("div",null,[p,s("p",null,[s("mjx-container",r,[(a(),n("svg",c,Q)),T])]),y,s("p",null,[s("mjx-container",E,[(a(),n("svg",d,m)),u])]),g,s("ul",null,[s("li",null,[s("mjx-container",b,[(a(),n("svg",F,H)),C]),l(" = Fixed Cost, is a static value (65,000 gas)")]),s("li",null,[s("mjx-container",x,[(a(),n("svg",w,B)),D]),l(" = SparseSharesNeeded for the "),s("mjx-container",V,[(a(),n("svg",L,_)),v]),l("th Blob, is the number of shares needed for the "),s("mjx-container",M,[(a(),n("svg",q,P)),S]),l("th blob in the transaction")]),s("li",null,[s("mjx-container",I,[(a(),n("svg",N,G)),z]),l(" = Share Size, is the size of each share")]),s("li",null,[s("mjx-container",O,[(a(),n("svg",R,J)),K]),l(" = Gas Cost Per Blob Byte, is a parameter that could potentially be adjusted through the system's governance mechanisms.")])]),U])}const os=t(o,[["render",X]]);export{ts as __pageData,os as default};
diff --git a/pr-1699/assets/developers_transaction-resubmission.md.2c716084.js b/pr-1699/assets/developers_transaction-resubmission.md.ebf49e01.js
similarity index 97%
rename from pr-1699/assets/developers_transaction-resubmission.md.2c716084.js
rename to pr-1699/assets/developers_transaction-resubmission.md.ebf49e01.js
index 7a31c94b24..c5828e1e11 100644
--- a/pr-1699/assets/developers_transaction-resubmission.md.2c716084.js
+++ b/pr-1699/assets/developers_transaction-resubmission.md.ebf49e01.js
@@ -1 +1 @@
-import{_ as e,o as s,c as n,Q as i}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Transaction resubmission","description":"This is a guide on transaction resubmission on Celestia.","frontmatter":{"description":"This is a guide on transaction resubmission on Celestia.","head":[["meta",{"name":"og:title","content":"Transaction resubmission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/transaction-resubmission.md","filePath":"developers/transaction-resubmission.md","lastUpdated":1725971357000}'),t={name:"developers/transaction-resubmission.md"},a=i('
        Transaction resubmission ​
        In cases where transactions are not included within a 75-second window, resubmission is necessary. This is especially important during network congestion, as transactions with relatively low fees may not be processed even after the network clears up.
        Regardless of whether they originate from celestia-app or celestia-node, transactions will not be re-gossiped, except in the presence of a new peer.
        Monitoring and resubmission ​
        Monitor the status of your transactions. If a transaction is not included within a 75-second window, it should be resubmitted. This can be done manually or through automated processes.
        Changes introduced in celestiaorg/celestia-core#1089 may affect transaction gossiping and inclusion speed.
        Notes ​
        • All transactions, regardless of their origin, are subject to being sorted and pruned based on fees.
        • It is the user or developer's responsibility to monitor and possibly resubmit transactions if they are not included in a 75-second window.
        ',8),o=[a];function r(c,d,l,u,h,m){return s(),n("div",null,o)}const _=e(t,[["render",r]]);export{b as __pageData,_ as default};
+import{_ as e,o as s,c as n,Q as i}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Transaction resubmission","description":"This is a guide on transaction resubmission on Celestia.","frontmatter":{"description":"This is a guide on transaction resubmission on Celestia.","head":[["meta",{"name":"og:title","content":"Transaction resubmission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/transaction-resubmission.md","filePath":"developers/transaction-resubmission.md","lastUpdated":1725992025000}'),t={name:"developers/transaction-resubmission.md"},a=i('
        Transaction resubmission ​
        In cases where transactions are not included within a 75-second window, resubmission is necessary. This is especially important during network congestion, as transactions with relatively low fees may not be processed even after the network clears up.
        Regardless of whether they originate from celestia-app or celestia-node, transactions will not be re-gossiped, except in the presence of a new peer.
        Monitoring and resubmission ​
        Monitor the status of your transactions. If a transaction is not included within a 75-second window, it should be resubmitted. This can be done manually or through automated processes.
        Changes introduced in celestiaorg/celestia-core#1089 may affect transaction gossiping and inclusion speed.
        Notes ​
        • All transactions, regardless of their origin, are subject to being sorted and pruned based on fees.
        • It is the user or developer's responsibility to monitor and possibly resubmit transactions if they are not included in a 75-second window.
        ',8),o=[a];function r(c,d,l,u,h,m){return s(),n("div",null,o)}const _=e(t,[["render",r]]);export{b as __pageData,_ as default};
diff --git a/pr-1699/assets/developers_transaction-resubmission.md.2c716084.lean.js b/pr-1699/assets/developers_transaction-resubmission.md.ebf49e01.lean.js
similarity index 91%
rename from pr-1699/assets/developers_transaction-resubmission.md.2c716084.lean.js
rename to pr-1699/assets/developers_transaction-resubmission.md.ebf49e01.lean.js
index 2e1218a362..3e86d15b39 100644
--- a/pr-1699/assets/developers_transaction-resubmission.md.2c716084.lean.js
+++ b/pr-1699/assets/developers_transaction-resubmission.md.ebf49e01.lean.js
@@ -1 +1 @@
-import{_ as e,o as s,c as n,Q as i}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Transaction resubmission","description":"This is a guide on transaction resubmission on Celestia.","frontmatter":{"description":"This is a guide on transaction resubmission on Celestia.","head":[["meta",{"name":"og:title","content":"Transaction resubmission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/transaction-resubmission.md","filePath":"developers/transaction-resubmission.md","lastUpdated":1725971357000}'),t={name:"developers/transaction-resubmission.md"},a=i("",8),o=[a];function r(c,d,l,u,h,m){return s(),n("div",null,o)}const _=e(t,[["render",r]]);export{b as __pageData,_ as default};
+import{_ as e,o as s,c as n,Q as i}from"./chunks/framework.b47e54aa.js";const b=JSON.parse('{"title":"Transaction resubmission","description":"This is a guide on transaction resubmission on Celestia.","frontmatter":{"description":"This is a guide on transaction resubmission on Celestia.","head":[["meta",{"name":"og:title","content":"Transaction resubmission | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/transaction-resubmission.md","filePath":"developers/transaction-resubmission.md","lastUpdated":1725992025000}'),t={name:"developers/transaction-resubmission.md"},a=i("",8),o=[a];function r(c,d,l,u,h,m){return s(),n("div",null,o)}const _=e(t,[["render",r]]);export{b as __pageData,_ as default};
diff --git a/pr-1699/assets/developers_wallets.md.c5fba5d1.js b/pr-1699/assets/developers_wallets.md.b2bd7cc6.js
similarity index 93%
rename from pr-1699/assets/developers_wallets.md.c5fba5d1.js
rename to pr-1699/assets/developers_wallets.md.b2bd7cc6.js
index a15e124f32..52aae353c4 100644
--- a/pr-1699/assets/developers_wallets.md.c5fba5d1.js
+++ b/pr-1699/assets/developers_wallets.md.b2bd7cc6.js
@@ -1,4 +1,4 @@
-import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as e,o as t,c,k as s,a as n,t as l,Q as o}from"./chunks/framework.b47e54aa.js";const r={data(){return{constants:p}}},hn=JSON.parse('{"title":"Wallet integrations with Celestia","description":"How you can add Celestia network parameters to wallets such as Keplr, Leap, and Cosmostation.","frontmatter":{"description":"How you can add Celestia network parameters to wallets such as Keplr, Leap, and Cosmostation.","head":[["meta",{"name":"og:title","content":"Wallet integrations with Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/wallets.md","filePath":"developers/wallets.md","lastUpdated":1725971357000}'),i=o(`
        Wallet integrations with Celestia ​
        This page covers how developers can use Keplr and React to add Celestia network parameters to wallets, and how to add custom networks to Leap and Cosmostation.
        Add Celestia network parameters to Keplr with React ​
        Before we demonstrate how to export the specific parameters for Celestia's testnets, we need to create a ReactJS component that allows us to connect directly to Keplr and pass it the network parameters.
        In the following code, we show how you can export a component that detects whether Keplr is installed and sets the network params for it:
        jsx
        // @site/src/components/AddNetworkKeplr.js
+import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as e,o as t,c,k as s,a as n,t as l,Q as o}from"./chunks/framework.b47e54aa.js";const r={data(){return{constants:p}}},hn=JSON.parse('{"title":"Wallet integrations with Celestia","description":"How you can add Celestia network parameters to wallets such as Keplr, Leap, and Cosmostation.","frontmatter":{"description":"How you can add Celestia network parameters to wallets such as Keplr, Leap, and Cosmostation.","head":[["meta",{"name":"og:title","content":"Wallet integrations with Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/wallets.md","filePath":"developers/wallets.md","lastUpdated":1725992025000}'),i=o(`
        Wallet integrations with Celestia ​
        This page covers how developers can use Keplr and React to add Celestia network parameters to wallets, and how to add custom networks to Leap and Cosmostation.
        Add Celestia network parameters to Keplr with React ​
        Before we demonstrate how to export the specific parameters for Celestia's testnets, we need to create a ReactJS component that allows us to connect directly to Keplr and pass it the network parameters.
        In the following code, we show how you can export a component that detects whether Keplr is installed and sets the network params for it:
        jsx
        // @site/src/components/AddNetworkKeplr.js
 import React from "react";
 import styles from "./Keplr.module.css";
 
@@ -146,7 +146,7 @@ import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as e,o as t,c,k as s
       </button>
     </div>
   );
-}
        We still need to pass the Celestia network parameters to the AddNetworkKeplr function:
        `,7),E={class:"vp-code-group vp-adaptive-theme"},y=o('
        ',1),d={class:"blocks"},_={class:"language-js vp-adaptive-theme active"},h=s("button",{title:"Copy Code",class:"copy"},null,-1),u=s("span",{class:"lang"},"js",-1),F={class:"shiki github-dark vp-code-dark"},A=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),C=s("span",{class:"line"},null,-1),m=o('export const MAINNET_PARAMS = {`{',1),w={class:"line"},T={style:{color:"#9ECBFF"}},b=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Celestia',")],-1),q={class:"line"},g={style:{color:"#9ECBFF"}},k={class:"line"},D={style:{color:"#9ECBFF"}},B=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),I=s("span",{class:"line"},null,-1),S=o('{<AddNetworkKeplr params={MAINNET_PARAMS}/>}',1),P={class:"shiki github-light vp-code-light"},v=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),f=s("span",{class:"line"},null,-1),N=o('export const MAINNET_PARAMS = {`{',1),R={class:"line"},x={style:{color:"#032F62"}},V=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Celestia',")],-1),M={class:"line"},K={style:{color:"#032F62"}},U={class:"line"},L={style:{color:"#032F62"}},G=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),j=s("span",{class:"line"},null,-1),H=o('{<AddNetworkKeplr params={MAINNET_PARAMS}/>}',1),O={class:"language-js vp-adaptive-theme"},W=s("button",{title:"Copy Code",class:"copy"},null,-1),J=s("span",{class:"lang"},"js",-1),Y={class:"shiki github-dark vp-code-dark"},X=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),Q=s("span",{class:"line"},null,-1),Z=o('export const MOCHA_PARAMS = {`{',1),z={class:"line"},$={style:{color:"#9ECBFF"}},ss=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Mocha testnet',")],-1),ns={class:"line"},as={style:{color:"#9ECBFF"}},ls={class:"line"},os={style:{color:"#9ECBFF"}},ps=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),es=s("span",{class:"line"},null,-1),ts=o('{<AddNetworkKeplr params={MOCHA_PARAMS}/>}',1),cs={class:"shiki github-light vp-code-light"},rs=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),is=s("span",{class:"line"},null,-1),Es=o('export const MOCHA_PARAMS = {`{',1),ys={class:"line"},ds={style:{color:"#032F62"}},_s=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Mocha testnet',")],-1),hs={class:"line"},us={style:{color:"#032F62"}},Fs={class:"line"},As={style:{color:"#032F62"}},Cs=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),ms=s("span",{class:"line"},null,-1),ws=o('{<AddNetworkKeplr params={MOCHA_PARAMS}/>}',1),Ts={class:"language-js vp-adaptive-theme"},bs=s("button",{title:"Copy Code",class:"copy"},null,-1),qs=s("span",{class:"lang"},"js",-1),gs={class:"shiki github-dark vp-code-dark"},ks=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),Ds=s("span",{class:"line"},null,-1),Bs=o('export const ARABICA_PARAMS = {`{',1),Is={class:"line"},Ss={style:{color:"#9ECBFF"}},Ps=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Arabica devnet',")],-1),vs={class:"line"},fs={style:{color:"#9ECBFF"}},Ns={class:"line"},Rs={style:{color:"#9ECBFF"}},xs=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),Vs=s("span",{class:"line"},null,-1),Ms=o('{<AddNetworkKeplr params={ARABICA_PARAMS}/>}',1),Ks={class:"shiki github-light vp-code-light"},Us=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),Ls=s("span",{class:"line"},null,-1),Gs=o('export const ARABICA_PARAMS = {`{',1),js={class:"line"},Hs={style:{color:"#032F62"}},Os=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Arabica devnet',")],-1),Ws={class:"line"},Js={style:{color:"#032F62"}},Ys={class:"line"},Xs={style:{color:"#032F62"}},Qs=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),Zs=s("span",{class:"line"},null,-1),zs=o('{<AddNetworkKeplr params={ARABICA_PARAMS}/>}',1),$s=s("p",null,"Now, we can connect to the network that you would like to use in Keplr wallet.",-1),sn=s("h2",{id:"adding-a-custom-chain-to-leap",tabindex:"-1"},[n("Adding a custom chain to Leap "),s("a",{class:"header-anchor",href:"#adding-a-custom-chain-to-leap","aria-label":'Permalink to "Adding a custom chain to Leap"'},"​")],-1),nn=s("p",null,"If you want to add a custom chain to Leap, you can do so by:",-1),an=s("ol",null,[s("li",null,"Clicking the Cosmos logo in the top corner of Leap wallet"),s("li",null,'Scrolling down and clicking "Add new chain"')],-1),ln=s("p",null,"You can then add the following parameters:",-1),on=o("
      4. Chain Name: Arabica devnet
      5. New RPC URL: https://rpc.celestia-arabica-11.com/
      6. New REST URL: https://api.celestia-arabica-11.com
      7. Address Prefix: celestia
      8. Native Denom: utia
      9. Coin Type: 118
      10. Decimals: 6
      11. Block explorer URL (optional): https://explorer.celestia-arabica-10.com
        12. ",8),pn=o('
        Now, click Add chain and you will be able to view your Arabica account balance and transactions in Leap wallet.
        You'll see that you're connected to Arabica Devnet.
        Adding a custom chain to Cosmostation ​
        Click the hamburger menu icon in the top corner of Cosmostation wallet. Scroll down and click "Add Custom Chain"
        You can then add the following parameters:
        • Custom Chain name: Mocha testnet
        • Rest URL: https://api-mocha.pops.one
        • New RPC URL: https://rpc-mocha.pops.one
        • Currency symbol: TIA
        • Address prefix: celestia
        • Denom: utia
        • Symbol image URL (optional): https://raw.githubusercontent.com/cosmos/chain-registry/master/testnets/celestiatestnet/images/celestia.svg
        • Explorer URL (optional): https://testnet.mintscan.io/celestia-testnet
        • Coin Type: 118
        • Decimals: 6
        • Gas rate Tiny: 0.1
        • Gas rate Low: 0.25
        • Gas rate Average: 0.5
        Now, click Add a custom chain and you will be able to view your Celestia account balance and transactions in Cosmostation wallet.
        Switch chains to "Mocha testnet" and you'll see that you're connected to Celestia's Mocha testnet!
        ',8);function en(tn,cn,rn,En,a,yn){return t(),c("div",null,[i,s("div",E,[y,s("div",d,[s("div",_,[h,u,s("pre",F,[s("code",null,[A,n(`
+}
        We still need to pass the Celestia network parameters to the AddNetworkKeplr function:
        `,7),E={class:"vp-code-group vp-adaptive-theme"},y=o('
        ',1),d={class:"blocks"},_={class:"language-js vp-adaptive-theme active"},h=s("button",{title:"Copy Code",class:"copy"},null,-1),u=s("span",{class:"lang"},"js",-1),F={class:"shiki github-dark vp-code-dark"},A=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),C=s("span",{class:"line"},null,-1),m=o('export const MAINNET_PARAMS = {`{',1),w={class:"line"},T={style:{color:"#9ECBFF"}},b=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Celestia',")],-1),q={class:"line"},g={style:{color:"#9ECBFF"}},k={class:"line"},D={style:{color:"#9ECBFF"}},B=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),I=s("span",{class:"line"},null,-1),P=o('{<AddNetworkKeplr params={MAINNET_PARAMS}/>}',1),S={class:"shiki github-light vp-code-light"},v=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),N=s("span",{class:"line"},null,-1),f=o('export const MAINNET_PARAMS = {`{',1),R={class:"line"},x={style:{color:"#032F62"}},V=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Celestia',")],-1),K={class:"line"},M={style:{color:"#032F62"}},U={class:"line"},L={style:{color:"#032F62"}},j=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),G=s("span",{class:"line"},null,-1),O=o('{<AddNetworkKeplr params={MAINNET_PARAMS}/>}',1),H={class:"language-js vp-adaptive-theme"},W=s("button",{title:"Copy Code",class:"copy"},null,-1),z=s("span",{class:"lang"},"js",-1),Y={class:"shiki github-dark vp-code-dark"},J=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),Q=s("span",{class:"line"},null,-1),X=o('export const MOCHA_PARAMS = {`{',1),Z={class:"line"},$={style:{color:"#9ECBFF"}},ss=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Mocha testnet',")],-1),ns={class:"line"},as={style:{color:"#9ECBFF"}},ls={class:"line"},os={style:{color:"#9ECBFF"}},ps=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),es=s("span",{class:"line"},null,-1),ts=o('{<AddNetworkKeplr params={MOCHA_PARAMS}/>}',1),cs={class:"shiki github-light vp-code-light"},rs=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),is=s("span",{class:"line"},null,-1),Es=o('export const MOCHA_PARAMS = {`{',1),ys={class:"line"},ds={style:{color:"#032F62"}},_s=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Mocha testnet',")],-1),hs={class:"line"},us={style:{color:"#032F62"}},Fs={class:"line"},As={style:{color:"#032F62"}},Cs=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),ms=s("span",{class:"line"},null,-1),ws=o('{<AddNetworkKeplr params={MOCHA_PARAMS}/>}',1),Ts={class:"language-js vp-adaptive-theme"},bs=s("button",{title:"Copy Code",class:"copy"},null,-1),qs=s("span",{class:"lang"},"js",-1),gs={class:"shiki github-dark vp-code-dark"},ks=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),Ds=s("span",{class:"line"},null,-1),Bs=o('export const ARABICA_PARAMS = {`{',1),Is={class:"line"},Ps={style:{color:"#9ECBFF"}},Ss=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Arabica devnet',")],-1),vs={class:"line"},Ns={style:{color:"#9ECBFF"}},fs={class:"line"},Rs={style:{color:"#9ECBFF"}},xs=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),Vs=s("span",{class:"line"},null,-1),Ks=o('{<AddNetworkKeplr params={ARABICA_PARAMS}/>}',1),Ms={class:"shiki github-light vp-code-light"},Us=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),Ls=s("span",{class:"line"},null,-1),js=o('export const ARABICA_PARAMS = {`{',1),Gs={class:"line"},Os={style:{color:"#032F62"}},Hs=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Arabica devnet',")],-1),Ws={class:"line"},zs={style:{color:"#032F62"}},Ys={class:"line"},Js={style:{color:"#032F62"}},Qs=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),Xs=s("span",{class:"line"},null,-1),Zs=o('{<AddNetworkKeplr params={ARABICA_PARAMS}/>}',1),$s=s("p",null,"Now, we can connect to the network that you would like to use in Keplr wallet.",-1),sn=s("h2",{id:"adding-a-custom-chain-to-leap",tabindex:"-1"},[n("Adding a custom chain to Leap "),s("a",{class:"header-anchor",href:"#adding-a-custom-chain-to-leap","aria-label":'Permalink to "Adding a custom chain to Leap"'},"​")],-1),nn=s("p",null,"If you want to add a custom chain to Leap, you can do so by:",-1),an=s("ol",null,[s("li",null,"Clicking the Cosmos logo in the top corner of Leap wallet"),s("li",null,'Scrolling down and clicking "Add new chain"')],-1),ln=s("p",null,"You can then add the following parameters:",-1),on=o("
      12. Chain Name: Arabica devnet
      13. New RPC URL: https://rpc.celestia-arabica-11.com/
      14. New REST URL: https://api.celestia-arabica-11.com
      15. Address Prefix: celestia
      16. Native Denom: utia
      17. Coin Type: 118
      18. Decimals: 6
      19. Block explorer URL (optional): https://explorer.celestia-arabica-10.com
        20. ",8),pn=o('
        Now, click Add chain and you will be able to view your Arabica account balance and transactions in Leap wallet.
        You'll see that you're connected to Arabica Devnet.
        Adding a custom chain to Cosmostation ​
        Click the hamburger menu icon in the top corner of Cosmostation wallet. Scroll down and click "Add Custom Chain"
        You can then add the following parameters:
        • Custom Chain name: Mocha testnet
        • Rest URL: https://api-mocha.pops.one
        • New RPC URL: https://rpc-mocha.pops.one
        • Currency symbol: TIA
        • Address prefix: celestia
        • Denom: utia
        • Symbol image URL (optional): https://raw.githubusercontent.com/cosmos/chain-registry/master/testnets/celestiatestnet/images/celestia.svg
        • Explorer URL (optional): https://testnet.mintscan.io/celestia-testnet
        • Coin Type: 118
        • Decimals: 6
        • Gas rate Tiny: 0.1
        • Gas rate Low: 0.25
        • Gas rate Average: 0.5
        Now, click Add a custom chain and you will be able to view your Celestia account balance and transactions in Cosmostation wallet.
        Switch chains to "Mocha testnet" and you'll see that you're connected to Celestia's Mocha testnet!
        ',8);function en(tn,cn,rn,En,a,yn){return t(),c("div",null,[i,s("div",E,[y,s("div",d,[s("div",_,[h,u,s("pre",F,[s("code",null,[A,n(`
 `),C,n(`
 `),m,n(`
 `),s("span",w,[s("span",T,"  chainId: '"+l(a.constants.mainnetChainId)+"',",1)]),n(`
@@ -155,19 +155,19 @@ import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as e,o as t,c,k as s
 `),s("span",k,[s("span",D,"  rest: '"+l(a.constants.mainnetRestUrl)+"'",1)]),n(`
 `),B,n(`
 `),I,n(`
-`),S])]),s("pre",P,[s("code",null,[v,n(`
-`),f,n(`
+`),P])]),s("pre",S,[s("code",null,[v,n(`
 `),N,n(`
+`),f,n(`
 `),s("span",R,[s("span",x,"  chainId: '"+l(a.constants.mainnetChainId)+"',",1)]),n(`
 `),V,n(`
-`),s("span",M,[s("span",K,"  rpc: '"+l(a.constants.mainnetRpcUrl)+"',",1)]),n(`
+`),s("span",K,[s("span",M,"  rpc: '"+l(a.constants.mainnetRpcUrl)+"',",1)]),n(`
 `),s("span",U,[s("span",L,"  rest: '"+l(a.constants.mainnetRestUrl)+"'",1)]),n(`
-`),G,n(`
 `),j,n(`
-`),H])])]),s("div",O,[W,J,s("pre",Y,[s("code",null,[X,n(`
+`),G,n(`
+`),O])])]),s("div",H,[W,z,s("pre",Y,[s("code",null,[J,n(`
 `),Q,n(`
-`),Z,n(`
-`),s("span",z,[s("span",$,"  chainId: '"+l(a.constants.mochaChainId)+"',",1)]),n(`
+`),X,n(`
+`),s("span",Z,[s("span",$,"  chainId: '"+l(a.constants.mochaChainId)+"',",1)]),n(`
 `),ss,n(`
 `),s("span",ns,[s("span",as,"  rpc: '"+l(a.constants.mochaRpcUrl)+"',",1)]),n(`
 `),s("span",ls,[s("span",os,"  rest: '"+l(a.constants.mochaRestUrl)+"'",1)]),n(`
@@ -185,19 +185,19 @@ import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as e,o as t,c,k as s
 `),ws])])]),s("div",Ts,[bs,qs,s("pre",gs,[s("code",null,[ks,n(`
 `),Ds,n(`
 `),Bs,n(`
-`),s("span",Is,[s("span",Ss,"  chainId: '"+l(a.constants.arabicaChainId)+"',",1)]),n(`
-`),Ps,n(`
-`),s("span",vs,[s("span",fs,"  rpc: '"+l(a.constants.arabicaRpcUrl)+"',",1)]),n(`
-`),s("span",Ns,[s("span",Rs,"  rest: '"+l(a.constants.arabicaRestUrl)+"'",1)]),n(`
+`),s("span",Is,[s("span",Ps,"  chainId: '"+l(a.constants.arabicaChainId)+"',",1)]),n(`
+`),Ss,n(`
+`),s("span",vs,[s("span",Ns,"  rpc: '"+l(a.constants.arabicaRpcUrl)+"',",1)]),n(`
+`),s("span",fs,[s("span",Rs,"  rest: '"+l(a.constants.arabicaRestUrl)+"'",1)]),n(`
 `),xs,n(`
 `),Vs,n(`
-`),Ms])]),s("pre",Ks,[s("code",null,[Us,n(`
+`),Ks])]),s("pre",Ms,[s("code",null,[Us,n(`
 `),Ls,n(`
-`),Gs,n(`
-`),s("span",js,[s("span",Hs,"  chainId: '"+l(a.constants.arabicaChainId)+"',",1)]),n(`
-`),Os,n(`
-`),s("span",Ws,[s("span",Js,"  rpc: '"+l(a.constants.arabicaRpcUrl)+"',",1)]),n(`
-`),s("span",Ys,[s("span",Xs,"  rest: '"+l(a.constants.arabicaRestUrl)+"'",1)]),n(`
+`),js,n(`
+`),s("span",Gs,[s("span",Os,"  chainId: '"+l(a.constants.arabicaChainId)+"',",1)]),n(`
+`),Hs,n(`
+`),s("span",Ws,[s("span",zs,"  rpc: '"+l(a.constants.arabicaRpcUrl)+"',",1)]),n(`
+`),s("span",Ys,[s("span",Js,"  rest: '"+l(a.constants.arabicaRestUrl)+"'",1)]),n(`
 `),Qs,n(`
-`),Zs,n(`
-`),zs])])])])]),$s,sn,nn,an,ln,s("ul",null,[s("li",null,[n("Chain Id: "),s("code",null,l(a.constants.arabicaChainId),1)]),on]),pn])}const un=e(r,[["render",en]]);export{hn as __pageData,un as default};
+`),Xs,n(`
+`),Zs])])])])]),$s,sn,nn,an,ln,s("ul",null,[s("li",null,[n("Chain Id: "),s("code",null,l(a.constants.arabicaChainId),1)]),on]),pn])}const un=e(r,[["render",en]]);export{hn as __pageData,un as default};
diff --git a/pr-1699/assets/developers_wallets.md.c5fba5d1.lean.js b/pr-1699/assets/developers_wallets.md.b2bd7cc6.lean.js
similarity index 76%
rename from pr-1699/assets/developers_wallets.md.c5fba5d1.lean.js
rename to pr-1699/assets/developers_wallets.md.b2bd7cc6.lean.js
index bb96b0371c..e26ab6265c 100644
--- a/pr-1699/assets/developers_wallets.md.c5fba5d1.lean.js
+++ b/pr-1699/assets/developers_wallets.md.b2bd7cc6.lean.js
@@ -1,4 +1,4 @@
-import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as e,o as t,c,k as s,a as n,t as l,Q as o}from"./chunks/framework.b47e54aa.js";const r={data(){return{constants:p}}},hn=JSON.parse('{"title":"Wallet integrations with Celestia","description":"How you can add Celestia network parameters to wallets such as Keplr, Leap, and Cosmostation.","frontmatter":{"description":"How you can add Celestia network parameters to wallets such as Keplr, Leap, and Cosmostation.","head":[["meta",{"name":"og:title","content":"Wallet integrations with Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/wallets.md","filePath":"developers/wallets.md","lastUpdated":1725971357000}'),i=o("",7),E={class:"vp-code-group vp-adaptive-theme"},y=o("",1),d={class:"blocks"},_={class:"language-js vp-adaptive-theme active"},h=s("button",{title:"Copy Code",class:"copy"},null,-1),u=s("span",{class:"lang"},"js",-1),F={class:"shiki github-dark vp-code-dark"},A=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),C=s("span",{class:"line"},null,-1),m=o("",1),w={class:"line"},T={style:{color:"#9ECBFF"}},b=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Celestia',")],-1),q={class:"line"},g={style:{color:"#9ECBFF"}},k={class:"line"},D={style:{color:"#9ECBFF"}},B=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),I=s("span",{class:"line"},null,-1),S=o("",1),P={class:"shiki github-light vp-code-light"},v=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),f=s("span",{class:"line"},null,-1),N=o("",1),R={class:"line"},x={style:{color:"#032F62"}},V=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Celestia',")],-1),M={class:"line"},K={style:{color:"#032F62"}},U={class:"line"},L={style:{color:"#032F62"}},G=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),j=s("span",{class:"line"},null,-1),H=o("",1),O={class:"language-js vp-adaptive-theme"},W=s("button",{title:"Copy Code",class:"copy"},null,-1),J=s("span",{class:"lang"},"js",-1),Y={class:"shiki github-dark vp-code-dark"},X=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),Q=s("span",{class:"line"},null,-1),Z=o("",1),z={class:"line"},$={style:{color:"#9ECBFF"}},ss=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Mocha testnet',")],-1),ns={class:"line"},as={style:{color:"#9ECBFF"}},ls={class:"line"},os={style:{color:"#9ECBFF"}},ps=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),es=s("span",{class:"line"},null,-1),ts=o("",1),cs={class:"shiki github-light vp-code-light"},rs=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),is=s("span",{class:"line"},null,-1),Es=o("",1),ys={class:"line"},ds={style:{color:"#032F62"}},_s=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Mocha testnet',")],-1),hs={class:"line"},us={style:{color:"#032F62"}},Fs={class:"line"},As={style:{color:"#032F62"}},Cs=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),ms=s("span",{class:"line"},null,-1),ws=o("",1),Ts={class:"language-js vp-adaptive-theme"},bs=s("button",{title:"Copy Code",class:"copy"},null,-1),qs=s("span",{class:"lang"},"js",-1),gs={class:"shiki github-dark vp-code-dark"},ks=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),Ds=s("span",{class:"line"},null,-1),Bs=o("",1),Is={class:"line"},Ss={style:{color:"#9ECBFF"}},Ps=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Arabica devnet',")],-1),vs={class:"line"},fs={style:{color:"#9ECBFF"}},Ns={class:"line"},Rs={style:{color:"#9ECBFF"}},xs=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),Vs=s("span",{class:"line"},null,-1),Ms=o("",1),Ks={class:"shiki github-light vp-code-light"},Us=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),Ls=s("span",{class:"line"},null,-1),Gs=o("",1),js={class:"line"},Hs={style:{color:"#032F62"}},Os=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Arabica devnet',")],-1),Ws={class:"line"},Js={style:{color:"#032F62"}},Ys={class:"line"},Xs={style:{color:"#032F62"}},Qs=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),Zs=s("span",{class:"line"},null,-1),zs=o("",1),$s=s("p",null,"Now, we can connect to the network that you would like to use in Keplr wallet.",-1),sn=s("h2",{id:"adding-a-custom-chain-to-leap",tabindex:"-1"},[n("Adding a custom chain to Leap "),s("a",{class:"header-anchor",href:"#adding-a-custom-chain-to-leap","aria-label":'Permalink to "Adding a custom chain to Leap"'},"​")],-1),nn=s("p",null,"If you want to add a custom chain to Leap, you can do so by:",-1),an=s("ol",null,[s("li",null,"Clicking the Cosmos logo in the top corner of Leap wallet"),s("li",null,'Scrolling down and clicking "Add new chain"')],-1),ln=s("p",null,"You can then add the following parameters:",-1),on=o("",8),pn=o("",8);function en(tn,cn,rn,En,a,yn){return t(),c("div",null,[i,s("div",E,[y,s("div",d,[s("div",_,[h,u,s("pre",F,[s("code",null,[A,n(`
+import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as e,o as t,c,k as s,a as n,t as l,Q as o}from"./chunks/framework.b47e54aa.js";const r={data(){return{constants:p}}},hn=JSON.parse('{"title":"Wallet integrations with Celestia","description":"How you can add Celestia network parameters to wallets such as Keplr, Leap, and Cosmostation.","frontmatter":{"description":"How you can add Celestia network parameters to wallets such as Keplr, Leap, and Cosmostation.","head":[["meta",{"name":"og:title","content":"Wallet integrations with Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"developers/wallets.md","filePath":"developers/wallets.md","lastUpdated":1725992025000}'),i=o("",7),E={class:"vp-code-group vp-adaptive-theme"},y=o("",1),d={class:"blocks"},_={class:"language-js vp-adaptive-theme active"},h=s("button",{title:"Copy Code",class:"copy"},null,-1),u=s("span",{class:"lang"},"js",-1),F={class:"shiki github-dark vp-code-dark"},A=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),C=s("span",{class:"line"},null,-1),m=o("",1),w={class:"line"},T={style:{color:"#9ECBFF"}},b=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Celestia',")],-1),q={class:"line"},g={style:{color:"#9ECBFF"}},k={class:"line"},D={style:{color:"#9ECBFF"}},B=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),I=s("span",{class:"line"},null,-1),P=o("",1),S={class:"shiki github-light vp-code-light"},v=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),N=s("span",{class:"line"},null,-1),f=o("",1),R={class:"line"},x={style:{color:"#032F62"}},V=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Celestia',")],-1),K={class:"line"},M={style:{color:"#032F62"}},U={class:"line"},L={style:{color:"#032F62"}},j=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),G=s("span",{class:"line"},null,-1),O=o("",1),H={class:"language-js vp-adaptive-theme"},W=s("button",{title:"Copy Code",class:"copy"},null,-1),z=s("span",{class:"lang"},"js",-1),Y={class:"shiki github-dark vp-code-dark"},J=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),Q=s("span",{class:"line"},null,-1),X=o("",1),Z={class:"line"},$={style:{color:"#9ECBFF"}},ss=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Mocha testnet',")],-1),ns={class:"line"},as={style:{color:"#9ECBFF"}},ls={class:"line"},os={style:{color:"#9ECBFF"}},ps=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),es=s("span",{class:"line"},null,-1),ts=o("",1),cs={class:"shiki github-light vp-code-light"},rs=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),is=s("span",{class:"line"},null,-1),Es=o("",1),ys={class:"line"},ds={style:{color:"#032F62"}},_s=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Mocha testnet',")],-1),hs={class:"line"},us={style:{color:"#032F62"}},Fs={class:"line"},As={style:{color:"#032F62"}},Cs=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),ms=s("span",{class:"line"},null,-1),ws=o("",1),Ts={class:"language-js vp-adaptive-theme"},bs=s("button",{title:"Copy Code",class:"copy"},null,-1),qs=s("span",{class:"lang"},"js",-1),gs={class:"shiki github-dark vp-code-dark"},ks=s("span",{class:"line"},[s("span",{style:{color:"#F97583"}},"import"),s("span",{style:{color:"#E1E4E8"}}," "),s("span",{style:{color:"#9ECBFF"}},"'@site/src/components/AddNetworkKeplr'")],-1),Ds=s("span",{class:"line"},null,-1),Bs=o("",1),Is={class:"line"},Ps={style:{color:"#9ECBFF"}},Ss=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"  chainName: 'Arabica devnet',")],-1),vs={class:"line"},Ns={style:{color:"#9ECBFF"}},fs={class:"line"},Rs={style:{color:"#9ECBFF"}},xs=s("span",{class:"line"},[s("span",{style:{color:"#9ECBFF"}},"}`"),s("span",{style:{color:"#E1E4E8"}},"}")],-1),Vs=s("span",{class:"line"},null,-1),Ks=o("",1),Ms={class:"shiki github-light vp-code-light"},Us=s("span",{class:"line"},[s("span",{style:{color:"#D73A49"}},"import"),s("span",{style:{color:"#24292E"}}," "),s("span",{style:{color:"#032F62"}},"'@site/src/components/AddNetworkKeplr'")],-1),Ls=s("span",{class:"line"},null,-1),js=o("",1),Gs={class:"line"},Os={style:{color:"#032F62"}},Hs=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"  chainName: 'Arabica devnet',")],-1),Ws={class:"line"},zs={style:{color:"#032F62"}},Ys={class:"line"},Js={style:{color:"#032F62"}},Qs=s("span",{class:"line"},[s("span",{style:{color:"#032F62"}},"}`"),s("span",{style:{color:"#24292E"}},"}")],-1),Xs=s("span",{class:"line"},null,-1),Zs=o("",1),$s=s("p",null,"Now, we can connect to the network that you would like to use in Keplr wallet.",-1),sn=s("h2",{id:"adding-a-custom-chain-to-leap",tabindex:"-1"},[n("Adding a custom chain to Leap "),s("a",{class:"header-anchor",href:"#adding-a-custom-chain-to-leap","aria-label":'Permalink to "Adding a custom chain to Leap"'},"​")],-1),nn=s("p",null,"If you want to add a custom chain to Leap, you can do so by:",-1),an=s("ol",null,[s("li",null,"Clicking the Cosmos logo in the top corner of Leap wallet"),s("li",null,'Scrolling down and clicking "Add new chain"')],-1),ln=s("p",null,"You can then add the following parameters:",-1),on=o("",8),pn=o("",8);function en(tn,cn,rn,En,a,yn){return t(),c("div",null,[i,s("div",E,[y,s("div",d,[s("div",_,[h,u,s("pre",F,[s("code",null,[A,n(`
 `),C,n(`
 `),m,n(`
 `),s("span",w,[s("span",T,"  chainId: '"+l(a.constants.mainnetChainId)+"',",1)]),n(`
@@ -7,19 +7,19 @@ import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as e,o as t,c,k as s
 `),s("span",k,[s("span",D,"  rest: '"+l(a.constants.mainnetRestUrl)+"'",1)]),n(`
 `),B,n(`
 `),I,n(`
-`),S])]),s("pre",P,[s("code",null,[v,n(`
-`),f,n(`
+`),P])]),s("pre",S,[s("code",null,[v,n(`
 `),N,n(`
+`),f,n(`
 `),s("span",R,[s("span",x,"  chainId: '"+l(a.constants.mainnetChainId)+"',",1)]),n(`
 `),V,n(`
-`),s("span",M,[s("span",K,"  rpc: '"+l(a.constants.mainnetRpcUrl)+"',",1)]),n(`
+`),s("span",K,[s("span",M,"  rpc: '"+l(a.constants.mainnetRpcUrl)+"',",1)]),n(`
 `),s("span",U,[s("span",L,"  rest: '"+l(a.constants.mainnetRestUrl)+"'",1)]),n(`
-`),G,n(`
 `),j,n(`
-`),H])])]),s("div",O,[W,J,s("pre",Y,[s("code",null,[X,n(`
+`),G,n(`
+`),O])])]),s("div",H,[W,z,s("pre",Y,[s("code",null,[J,n(`
 `),Q,n(`
-`),Z,n(`
-`),s("span",z,[s("span",$,"  chainId: '"+l(a.constants.mochaChainId)+"',",1)]),n(`
+`),X,n(`
+`),s("span",Z,[s("span",$,"  chainId: '"+l(a.constants.mochaChainId)+"',",1)]),n(`
 `),ss,n(`
 `),s("span",ns,[s("span",as,"  rpc: '"+l(a.constants.mochaRpcUrl)+"',",1)]),n(`
 `),s("span",ls,[s("span",os,"  rest: '"+l(a.constants.mochaRestUrl)+"'",1)]),n(`
@@ -37,19 +37,19 @@ import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as e,o as t,c,k as s
 `),ws])])]),s("div",Ts,[bs,qs,s("pre",gs,[s("code",null,[ks,n(`
 `),Ds,n(`
 `),Bs,n(`
-`),s("span",Is,[s("span",Ss,"  chainId: '"+l(a.constants.arabicaChainId)+"',",1)]),n(`
-`),Ps,n(`
-`),s("span",vs,[s("span",fs,"  rpc: '"+l(a.constants.arabicaRpcUrl)+"',",1)]),n(`
-`),s("span",Ns,[s("span",Rs,"  rest: '"+l(a.constants.arabicaRestUrl)+"'",1)]),n(`
+`),s("span",Is,[s("span",Ps,"  chainId: '"+l(a.constants.arabicaChainId)+"',",1)]),n(`
+`),Ss,n(`
+`),s("span",vs,[s("span",Ns,"  rpc: '"+l(a.constants.arabicaRpcUrl)+"',",1)]),n(`
+`),s("span",fs,[s("span",Rs,"  rest: '"+l(a.constants.arabicaRestUrl)+"'",1)]),n(`
 `),xs,n(`
 `),Vs,n(`
-`),Ms])]),s("pre",Ks,[s("code",null,[Us,n(`
+`),Ks])]),s("pre",Ms,[s("code",null,[Us,n(`
 `),Ls,n(`
-`),Gs,n(`
-`),s("span",js,[s("span",Hs,"  chainId: '"+l(a.constants.arabicaChainId)+"',",1)]),n(`
-`),Os,n(`
-`),s("span",Ws,[s("span",Js,"  rpc: '"+l(a.constants.arabicaRpcUrl)+"',",1)]),n(`
-`),s("span",Ys,[s("span",Xs,"  rest: '"+l(a.constants.arabicaRestUrl)+"'",1)]),n(`
+`),js,n(`
+`),s("span",Gs,[s("span",Os,"  chainId: '"+l(a.constants.arabicaChainId)+"',",1)]),n(`
+`),Hs,n(`
+`),s("span",Ws,[s("span",zs,"  rpc: '"+l(a.constants.arabicaRpcUrl)+"',",1)]),n(`
+`),s("span",Ys,[s("span",Js,"  rest: '"+l(a.constants.arabicaRestUrl)+"'",1)]),n(`
 `),Qs,n(`
-`),Zs,n(`
-`),zs])])])])]),$s,sn,nn,an,ln,s("ul",null,[s("li",null,[n("Chain Id: "),s("code",null,l(a.constants.arabicaChainId),1)]),on]),pn])}const un=e(r,[["render",en]]);export{hn as __pageData,un as default};
+`),Xs,n(`
+`),Zs])])])])]),$s,sn,nn,an,ln,s("ul",null,[s("li",null,[n("Chain Id: "),s("code",null,l(a.constants.arabicaChainId),1)]),on]),pn])}const un=e(r,[["render",en]]);export{hn as __pageData,un as default};
diff --git a/pr-1699/assets/index.md.d57eea6f.js b/pr-1699/assets/index.md.7de6d8b3.js
similarity index 96%
rename from pr-1699/assets/index.md.d57eea6f.js
rename to pr-1699/assets/index.md.7de6d8b3.js
index 417b698148..7daf93bd13 100644
--- a/pr-1699/assets/index.md.d57eea6f.js
+++ b/pr-1699/assets/index.md.7de6d8b3.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"","titleTemplate":":title","description":"","frontmatter":{"layout":"home","titleTemplate":":title","hero":{"name":"Celestia","text":"The first modular blockchain network","tagline":"Celestia is a modular data availability network that securely scales with the number of users, making it easy for anyone to launch their own blockchain.","image":{"src":"/modular.svg","alt":"Celestia"},"actions":[{"theme":"brand","text":"Build whatever","link":"/developers/build-whatever"},{"theme":"alt","text":"Introduction","link":"/learn/how-celestia-works/overview"}]},"features":[{"title":"Learn","details":"Celestia allows you to deploy your own blockchain in minutes, as easily as a smart contract.","link":"/learn/how-celestia-works/overview","icon":"🏗️"},{"title":"Run a node","details":"Access the dynamic scaling unlocked by data availability sampling, where scale increases with the number of users.","link":"/nodes/overview","icon":"📈"},{"title":"Developers","details":"Create applications using your favorite VM or define your own. Build sovereign rollups, a new type of self-governing blockchain with minimal platform risk.","link":"/developers/build-whatever","icon":"⚙️"},{"title":"Community","details":"Join the Celestia community to connect, collaborate, and contribute to the future of modular blockchains.","link":"/community/overview","icon":"🏰"}],"head":[["meta",{"name":"og:title","content":"Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1725971357000}'),i={name:"index.md"};function o(n,l,s,r,c,d){return t(),a("div")}const h=e(i,[["render",o]]);export{u as __pageData,h as default};
+import{_ as e,o as t,c as a}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"","titleTemplate":":title","description":"","frontmatter":{"layout":"home","titleTemplate":":title","hero":{"name":"Celestia","text":"The first modular blockchain network","tagline":"Celestia is a modular data availability network that securely scales with the number of users, making it easy for anyone to launch their own blockchain.","image":{"src":"/modular.svg","alt":"Celestia"},"actions":[{"theme":"brand","text":"Build whatever","link":"/developers/build-whatever"},{"theme":"alt","text":"Introduction","link":"/learn/how-celestia-works/overview"}]},"features":[{"title":"Learn","details":"Celestia allows you to deploy your own blockchain in minutes, as easily as a smart contract.","link":"/learn/how-celestia-works/overview","icon":"🏗️"},{"title":"Run a node","details":"Access the dynamic scaling unlocked by data availability sampling, where scale increases with the number of users.","link":"/nodes/overview","icon":"📈"},{"title":"Developers","details":"Create applications using your favorite VM or define your own. Build sovereign rollups, a new type of self-governing blockchain with minimal platform risk.","link":"/developers/build-whatever","icon":"⚙️"},{"title":"Community","details":"Join the Celestia community to connect, collaborate, and contribute to the future of modular blockchains.","link":"/community/overview","icon":"🏰"}],"head":[["meta",{"name":"og:title","content":"Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1725992025000}'),i={name:"index.md"};function o(n,l,s,r,c,d){return t(),a("div")}const h=e(i,[["render",o]]);export{u as __pageData,h as default};
diff --git a/pr-1699/assets/index.md.d57eea6f.lean.js b/pr-1699/assets/index.md.7de6d8b3.lean.js
similarity index 96%
rename from pr-1699/assets/index.md.d57eea6f.lean.js
rename to pr-1699/assets/index.md.7de6d8b3.lean.js
index 417b698148..7daf93bd13 100644
--- a/pr-1699/assets/index.md.d57eea6f.lean.js
+++ b/pr-1699/assets/index.md.7de6d8b3.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"","titleTemplate":":title","description":"","frontmatter":{"layout":"home","titleTemplate":":title","hero":{"name":"Celestia","text":"The first modular blockchain network","tagline":"Celestia is a modular data availability network that securely scales with the number of users, making it easy for anyone to launch their own blockchain.","image":{"src":"/modular.svg","alt":"Celestia"},"actions":[{"theme":"brand","text":"Build whatever","link":"/developers/build-whatever"},{"theme":"alt","text":"Introduction","link":"/learn/how-celestia-works/overview"}]},"features":[{"title":"Learn","details":"Celestia allows you to deploy your own blockchain in minutes, as easily as a smart contract.","link":"/learn/how-celestia-works/overview","icon":"🏗️"},{"title":"Run a node","details":"Access the dynamic scaling unlocked by data availability sampling, where scale increases with the number of users.","link":"/nodes/overview","icon":"📈"},{"title":"Developers","details":"Create applications using your favorite VM or define your own. Build sovereign rollups, a new type of self-governing blockchain with minimal platform risk.","link":"/developers/build-whatever","icon":"⚙️"},{"title":"Community","details":"Join the Celestia community to connect, collaborate, and contribute to the future of modular blockchains.","link":"/community/overview","icon":"🏰"}],"head":[["meta",{"name":"og:title","content":"Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1725971357000}'),i={name:"index.md"};function o(n,l,s,r,c,d){return t(),a("div")}const h=e(i,[["render",o]]);export{u as __pageData,h as default};
+import{_ as e,o as t,c as a}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"","titleTemplate":":title","description":"","frontmatter":{"layout":"home","titleTemplate":":title","hero":{"name":"Celestia","text":"The first modular blockchain network","tagline":"Celestia is a modular data availability network that securely scales with the number of users, making it easy for anyone to launch their own blockchain.","image":{"src":"/modular.svg","alt":"Celestia"},"actions":[{"theme":"brand","text":"Build whatever","link":"/developers/build-whatever"},{"theme":"alt","text":"Introduction","link":"/learn/how-celestia-works/overview"}]},"features":[{"title":"Learn","details":"Celestia allows you to deploy your own blockchain in minutes, as easily as a smart contract.","link":"/learn/how-celestia-works/overview","icon":"🏗️"},{"title":"Run a node","details":"Access the dynamic scaling unlocked by data availability sampling, where scale increases with the number of users.","link":"/nodes/overview","icon":"📈"},{"title":"Developers","details":"Create applications using your favorite VM or define your own. Build sovereign rollups, a new type of self-governing blockchain with minimal platform risk.","link":"/developers/build-whatever","icon":"⚙️"},{"title":"Community","details":"Join the Celestia community to connect, collaborate, and contribute to the future of modular blockchains.","link":"/community/overview","icon":"🏰"}],"head":[["meta",{"name":"og:title","content":"Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1725992025000}'),i={name:"index.md"};function o(n,l,s,r,c,d){return t(),a("div")}const h=e(i,[["render",o]]);export{u as __pageData,h as default};
diff --git a/pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.506e0c10.js b/pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.b4d6ab8b.js
similarity index 99%
rename from pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.506e0c10.js
rename to pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.b4d6ab8b.js
index 5a032be05e..35b7811cee 100644
--- a/pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.506e0c10.js
+++ b/pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.b4d6ab8b.js
@@ -1 +1 @@
-import{_ as a,o as t,c as e,Q as i}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/learn/data-availability-faq/Data-availability.png",s="/docs-preview/pr-1699/img/learn/data-availability-faq/Data-storage.png",m=JSON.parse('{"title":"Data availability FAQ","description":"Frequently asked questions related to Data Availability.","frontmatter":{"description":"Frequently asked questions related to Data Availability.","next":{"text":"Overview of TIA","link":"/learn/tia"},"head":[["meta",{"name":"og:title","content":"Data availability FAQ | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/data-availability-faq.md","filePath":"learn/how-celestia-works/data-availability-faq.md","lastUpdated":1725971357000}'),r={name:"learn/how-celestia-works/data-availability-faq.md"},l=i('
        Data availability FAQ ​
        What is data availability? ​
        Data availability answers the question, has this data been published? Specifically, a node will verify data availability when it receives a new block that is getting added to the chain. The node will attempt to download all the transaction data for the new block to verify availability. If the node can download all the transaction data, then it successfully verified data availability, proving that the block data was actually published to the network.
        Modular VS Monolithic
        As you’ll see, modular blockchains like Celestia employ other primitives that allow nodes to verify data availability more efficiently. Data availability is critical to the security of any blockchain because it ensures that anyone can inspect the ledger of transactions and verify it. Data availability becomes particularly problematic when scaling blockchains. As the blocks get bigger, it becomes impractical for normal users to download all the data, and therefore users can no longer verify the chain.
        What is the data availability problem? ​
        The problem with data availability occurs when the transaction data for a newly proposed block cannot be downloaded and verified. This type of attack by a block producer is called a data withholding attack, which sees the block producer withhold transaction data of a new block.
        Since transaction data is withheld, nodes cannot update to the latest state. Such an attack can have numerous consequences, from halting a chain to gaining the ability to steal funds. The severity of the consequences will depend on the type of blockchain (L1 or L2) and whether data availability is kept onchain or offchain. The data availability problem commonly arises around L2 scaling solutions like rollups and validiums.
        How do nodes verify data availability in Celestia? ​
        In most blockchains, nodes that verify data availability do so by downloading all transaction data for a block. If they are able to download all the data, they have verified its availability. In Celestia, light nodes have access to a new mechanism to verify data availability without needing to download all the data for a block. This new primitive for verifying data availability is called data availability sampling.
        What is data availability sampling? ​
        Data availability sampling is a mechanism for light nodes to verify data availability without having to download all data for a block. Data availability sampling (DAS) works by having light nodes conduct multiple rounds of random sampling for small portions of block data. As a light node completes more rounds of sampling for block data, it increases its confidence that data is available. Once the light node successfully reaches a predetermined confidence level (e.g. 99%) it will consider the block data as available.
        Want a simpler explanation? Check out this thread on how data availability sampling is like flipping a coin.
        What are some of the security assumptions that Celestia makes for data availability sampling? ​
        Celestia assumes that there is a minimum number of light nodes that are conducting data availability sampling for a given block size. This assumption is necessary so that a full node can reconstruct an entire block from the portions of data light nodes sampled and stored. The amount of light nodes that are needed will depend on the block size - for bigger blocks more light nodes are assumed to be running.
        A second notable assumption that is made by light nodes is that they are connected to at least one honest full node. This ensures that they can receive fraud proofs for incorrectly erasure coded blocks. If a light node is not connected to an honest full node, such as during an eclipse attack, it can’t verify that the block is improperly constructed.
        Why is block reconstruction necessary for security? ​
        In Celestia, blocks need to be erasure coded so that there is redundant data to aid the data availability sampling process. However, nodes tasked with erasure coding the data could do so incorrectly. Since Celestia uses fraud proofs to verify that erasure coding is incorrect, the full block data is needed to generate a bad encoding fraud proof.
        There could be a situation where validators only provide data to light nodes and not full nodes. If the full nodes don’t have the ability to reconstruct the full block from the portions of data stored by light nodes, they wouldn’t be able to generate a bad encoding fraud proof.
        What is data storage? ​
        Data storage is concerned with the ability to store and access past transaction data.
        Modular VS Monolithic
        Data storage and retrieval is needed for multiple purposes, such as:
        • Reading the information of a previous transaction
        • Syncing a node
        • Indexing and serving transaction data
        • Retrieving NFT information
        What is the problem around data storage? ​
        The issue with data storage is whether past transaction data can be stored and successfully retrieved at a later time. The inability to retrieve historical transaction data can cause problems, such as users being unable to access information about their past transactions or nodes that cannot sync from genesis. Luckily, the assumptions around storing and accessing past data are weak. Only a single copy of a blockchain’s history needs to be accessible for users to gain access to historical transaction data. In other words, data storage security is a 1 of N honesty assumption.
        What is the difference between data availability and data storage? ​
        Data availability is about verifying that transaction data for a new block is public and available. In contrast, data storage involves storing and accessing past transaction data from old blocks.
        Where does blockchain state fit into this? ​
        Up until now it’s been all about transaction data, but blockchain state is a related topic. The state is different from transaction data. Specifically, the state is like a current snapshot of the network, which includes information about account balances, smart contract balances, and validator set info. Problems that arise from the size of the state are different in nature than those around data availability and retrievability.
        Why doesn’t Celestia incentivize storage of historical data? ​
        Most blockchains don’t incentivize storage of data because it shouldn’t be the responsibility of a blockchain to guarantee past data will be retrievable forever. In addition, the data storage problem only requires a single party to store and provide the data for users, which is not a strong problem. As such, Celestia’s purpose is to provide a secure and scalable way to verify the availability of data. Once data has been verified as available, the job of storing and retrieving historical data is left up to other entities that require the data. Luckily, there are natural incentives for outside parties to store and serve historical data to users.
        Who may store historical data if there is no reward? ​
        There are multiple types of actors that may be likely to store historical data. Some of those include:
        • Block explorers that provide access to past transaction data.
        • Indexers that provide API queries for past data.
        • Applications or rollups that require historical data for certain processes.
        • Users that want to guarantee that they will have access to their transaction history.
        What are some things blockchains can do to provide stronger assurances of data retrievability? ​
        • Reward nodes based on the amount of transaction data they store and requests for data they serve (this is the case with some data storage blockchains, like Filecoin).
        • Publish transaction data onto a data storage blockchain that incentivizes storing and serving requests for historical data.
        ',37),n=[l];function d(h,c,b,u,f,p){return t(),e("div",null,n)}const v=a(r,[["render",d]]);export{m as __pageData,v as default};
+import{_ as a,o as t,c as e,Q as i}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/learn/data-availability-faq/Data-availability.png",s="/docs-preview/pr-1699/img/learn/data-availability-faq/Data-storage.png",m=JSON.parse('{"title":"Data availability FAQ","description":"Frequently asked questions related to Data Availability.","frontmatter":{"description":"Frequently asked questions related to Data Availability.","next":{"text":"Overview of TIA","link":"/learn/tia"},"head":[["meta",{"name":"og:title","content":"Data availability FAQ | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/data-availability-faq.md","filePath":"learn/how-celestia-works/data-availability-faq.md","lastUpdated":1725992025000}'),r={name:"learn/how-celestia-works/data-availability-faq.md"},l=i('
        Data availability FAQ ​
        What is data availability? ​
        Data availability answers the question, has this data been published? Specifically, a node will verify data availability when it receives a new block that is getting added to the chain. The node will attempt to download all the transaction data for the new block to verify availability. If the node can download all the transaction data, then it successfully verified data availability, proving that the block data was actually published to the network.
        Modular VS Monolithic
        As you’ll see, modular blockchains like Celestia employ other primitives that allow nodes to verify data availability more efficiently. Data availability is critical to the security of any blockchain because it ensures that anyone can inspect the ledger of transactions and verify it. Data availability becomes particularly problematic when scaling blockchains. As the blocks get bigger, it becomes impractical for normal users to download all the data, and therefore users can no longer verify the chain.
        What is the data availability problem? ​
        The problem with data availability occurs when the transaction data for a newly proposed block cannot be downloaded and verified. This type of attack by a block producer is called a data withholding attack, which sees the block producer withhold transaction data of a new block.
        Since transaction data is withheld, nodes cannot update to the latest state. Such an attack can have numerous consequences, from halting a chain to gaining the ability to steal funds. The severity of the consequences will depend on the type of blockchain (L1 or L2) and whether data availability is kept onchain or offchain. The data availability problem commonly arises around L2 scaling solutions like rollups and validiums.
        How do nodes verify data availability in Celestia? ​
        In most blockchains, nodes that verify data availability do so by downloading all transaction data for a block. If they are able to download all the data, they have verified its availability. In Celestia, light nodes have access to a new mechanism to verify data availability without needing to download all the data for a block. This new primitive for verifying data availability is called data availability sampling.
        What is data availability sampling? ​
        Data availability sampling is a mechanism for light nodes to verify data availability without having to download all data for a block. Data availability sampling (DAS) works by having light nodes conduct multiple rounds of random sampling for small portions of block data. As a light node completes more rounds of sampling for block data, it increases its confidence that data is available. Once the light node successfully reaches a predetermined confidence level (e.g. 99%) it will consider the block data as available.
        Want a simpler explanation? Check out this thread on how data availability sampling is like flipping a coin.
        What are some of the security assumptions that Celestia makes for data availability sampling? ​
        Celestia assumes that there is a minimum number of light nodes that are conducting data availability sampling for a given block size. This assumption is necessary so that a full node can reconstruct an entire block from the portions of data light nodes sampled and stored. The amount of light nodes that are needed will depend on the block size - for bigger blocks more light nodes are assumed to be running.
        A second notable assumption that is made by light nodes is that they are connected to at least one honest full node. This ensures that they can receive fraud proofs for incorrectly erasure coded blocks. If a light node is not connected to an honest full node, such as during an eclipse attack, it can’t verify that the block is improperly constructed.
        Why is block reconstruction necessary for security? ​
        In Celestia, blocks need to be erasure coded so that there is redundant data to aid the data availability sampling process. However, nodes tasked with erasure coding the data could do so incorrectly. Since Celestia uses fraud proofs to verify that erasure coding is incorrect, the full block data is needed to generate a bad encoding fraud proof.
        There could be a situation where validators only provide data to light nodes and not full nodes. If the full nodes don’t have the ability to reconstruct the full block from the portions of data stored by light nodes, they wouldn’t be able to generate a bad encoding fraud proof.
        What is data storage? ​
        Data storage is concerned with the ability to store and access past transaction data.
        Modular VS Monolithic
        Data storage and retrieval is needed for multiple purposes, such as:
        • Reading the information of a previous transaction
        • Syncing a node
        • Indexing and serving transaction data
        • Retrieving NFT information
        What is the problem around data storage? ​
        The issue with data storage is whether past transaction data can be stored and successfully retrieved at a later time. The inability to retrieve historical transaction data can cause problems, such as users being unable to access information about their past transactions or nodes that cannot sync from genesis. Luckily, the assumptions around storing and accessing past data are weak. Only a single copy of a blockchain’s history needs to be accessible for users to gain access to historical transaction data. In other words, data storage security is a 1 of N honesty assumption.
        What is the difference between data availability and data storage? ​
        Data availability is about verifying that transaction data for a new block is public and available. In contrast, data storage involves storing and accessing past transaction data from old blocks.
        Where does blockchain state fit into this? ​
        Up until now it’s been all about transaction data, but blockchain state is a related topic. The state is different from transaction data. Specifically, the state is like a current snapshot of the network, which includes information about account balances, smart contract balances, and validator set info. Problems that arise from the size of the state are different in nature than those around data availability and retrievability.
        Why doesn’t Celestia incentivize storage of historical data? ​
        Most blockchains don’t incentivize storage of data because it shouldn’t be the responsibility of a blockchain to guarantee past data will be retrievable forever. In addition, the data storage problem only requires a single party to store and provide the data for users, which is not a strong problem. As such, Celestia’s purpose is to provide a secure and scalable way to verify the availability of data. Once data has been verified as available, the job of storing and retrieving historical data is left up to other entities that require the data. Luckily, there are natural incentives for outside parties to store and serve historical data to users.
        Who may store historical data if there is no reward? ​
        There are multiple types of actors that may be likely to store historical data. Some of those include:
        • Block explorers that provide access to past transaction data.
        • Indexers that provide API queries for past data.
        • Applications or rollups that require historical data for certain processes.
        • Users that want to guarantee that they will have access to their transaction history.
        What are some things blockchains can do to provide stronger assurances of data retrievability? ​
        • Reward nodes based on the amount of transaction data they store and requests for data they serve (this is the case with some data storage blockchains, like Filecoin).
        • Publish transaction data onto a data storage blockchain that incentivizes storing and serving requests for historical data.
        ',37),n=[l];function d(h,c,b,u,f,p){return t(),e("div",null,n)}const v=a(r,[["render",d]]);export{m as __pageData,v as default};
diff --git a/pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.506e0c10.lean.js b/pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.b4d6ab8b.lean.js
similarity index 93%
rename from pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.506e0c10.lean.js
rename to pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.b4d6ab8b.lean.js
index c39b96008f..5307e8841b 100644
--- a/pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.506e0c10.lean.js
+++ b/pr-1699/assets/learn_how-celestia-works_data-availability-faq.md.b4d6ab8b.lean.js
@@ -1 +1 @@
-import{_ as a,o as t,c as e,Q as i}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/learn/data-availability-faq/Data-availability.png",s="/docs-preview/pr-1699/img/learn/data-availability-faq/Data-storage.png",m=JSON.parse('{"title":"Data availability FAQ","description":"Frequently asked questions related to Data Availability.","frontmatter":{"description":"Frequently asked questions related to Data Availability.","next":{"text":"Overview of TIA","link":"/learn/tia"},"head":[["meta",{"name":"og:title","content":"Data availability FAQ | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/data-availability-faq.md","filePath":"learn/how-celestia-works/data-availability-faq.md","lastUpdated":1725971357000}'),r={name:"learn/how-celestia-works/data-availability-faq.md"},l=i("",37),n=[l];function d(h,c,b,u,f,p){return t(),e("div",null,n)}const v=a(r,[["render",d]]);export{m as __pageData,v as default};
+import{_ as a,o as t,c as e,Q as i}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/learn/data-availability-faq/Data-availability.png",s="/docs-preview/pr-1699/img/learn/data-availability-faq/Data-storage.png",m=JSON.parse('{"title":"Data availability FAQ","description":"Frequently asked questions related to Data Availability.","frontmatter":{"description":"Frequently asked questions related to Data Availability.","next":{"text":"Overview of TIA","link":"/learn/tia"},"head":[["meta",{"name":"og:title","content":"Data availability FAQ | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/data-availability-faq.md","filePath":"learn/how-celestia-works/data-availability-faq.md","lastUpdated":1725992025000}'),r={name:"learn/how-celestia-works/data-availability-faq.md"},l=i("",37),n=[l];function d(h,c,b,u,f,p){return t(),e("div",null,n)}const v=a(r,[["render",d]]);export{m as __pageData,v as default};
diff --git a/pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.d71fa908.js b/pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.4a9aff1a.js
similarity index 99%
rename from pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.d71fa908.js
rename to pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.4a9aff1a.js
index 40355d8d68..b66c5995e4 100644
--- a/pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.d71fa908.js
+++ b/pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.4a9aff1a.js
@@ -1 +1 @@
-import{_ as l,o as a,c as o,k as e,a as t,Q as s}from"./chunks/framework.b47e54aa.js";const i="/docs-preview/pr-1699/img/learn/reed-solomon-encoding.png",n="/docs-preview/pr-1699/img/learn/nmt.png",r="/docs-preview/pr-1699/img/learn/celestia-app.png",g4=JSON.parse(`{"title":"Celestia's data availability layer","description":"Celestia's Data Availability layer and its key features.","frontmatter":{"description":"Celestia's Data Availability layer and its key features.","head":[["meta",{"name":"og:title","content":"Celestia's data availability layer | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/data-availability-layer.md","filePath":"learn/how-celestia-works/data-availability-layer.md","lastUpdated":1725971357000}`),T={name:"learn/how-celestia-works/data-availability-layer.md"},d=s('
        Celestia's data availability layer ​
        Celestia is a data availability (DA) layer that provides a scalable solution to the data availability problem. Due to the permissionless nature of the blockchain networks, a DA layer must provide a mechanism for the execution and settlement layers to check in a trust-minimized way whether transaction data is indeed available.
        Two key features of Celestia's DA layer are data availability sampling (DAS) and Namespaced Merkle trees (NMTs). Both features are novel blockchain scaling solutions: DAS enables light nodes to verify data availability without needing to download an entire block; NMTs enable execution and settlement layers on Celestia to download transactions that are only relevant to them.
        Data availability sampling (DAS) ​
        In general, light nodes download only block headers that contain commitments (i.e., Merkle roots) of the block data (i.e., the list of transactions).
        ',5),Q={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},h={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},c=s('',1),m=[c],p=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),g={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},x={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},u=s('',1),_=[u],w=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),f={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},b={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},k=s('',1),y=[k],v=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),L={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},M={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},H=s('',1),V=[H],S=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),C=e("p",null,[e("img",{src:i,alt:"2D Reed-Soloman (RS) Encoding"})],-1),D={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},A={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},j=s('',1),Z=[j],P=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),N=e("p",null,[t("Every light node randomly chooses a set of unique coordinates in the extended matrix and queries full nodes for the data shares and the corresponding Merkle proofs at those coordinates. If light nodes receive a valid response for each sampling query, then there is a "),e("a",{href:"https://github.com/celestiaorg/celestia-node/issues/805#issuecomment-1150081075",target:"_blank",rel:"noreferrer"},"high probability guarantee"),t(" that the whole block's data is available.")],-1),I=e("em",null,"i.e.",-1),B={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},q=s('',1),E=[q],z=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),G=e("p",null,[t("For more details on DAS, take a look at the "),e("a",{href:"https://arxiv.org/abs/1809.09044",target:"_blank",rel:"noreferrer"},"original paper"),t(".")],-1),J=e("h3",{id:"scalability",tabindex:"-1"},[t("Scalability "),e("a",{class:"header-anchor",href:"#scalability","aria-label":'Permalink to "Scalability"'},"​")],-1),F=e("p",null,"DAS enables Celestia to scale the DA layer. DAS can be performed by resource-limited light nodes since each light node only samples a small portion of the block data. The more light nodes there are in the network, the more data they can collectively download and store.",-1),O=e("em",null,"i.e.",-1),$={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},W={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},K=s('',1),U=[K],X=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),Y={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},e1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.345ex",height:"1.912ex",role:"img",focusable:"false",viewBox:"0 -833.9 1036.6 844.9","aria-hidden":"true"},t1=s('',1),a1=[t1],o1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("msup",null,[e("mi",null,"n"),e("mn",null,"2")])])],-1),s1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},l1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},i1=s('',1),n1=[i1],r1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),T1=e("h3",{id:"fraud-proofs-of-incorrectly-extended-data",tabindex:"-1"},[t("Fraud proofs of incorrectly extended data "),e("a",{class:"header-anchor",href:"#fraud-proofs-of-incorrectly-extended-data","aria-label":'Permalink to "Fraud proofs of incorrectly extended data"'},"​")],-1),d1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},Q1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},h1=s('',1),c1=[h1],m1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),p1=e("em",null,"i.e.",-1),g1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},x1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},u1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),_1=[u1],w1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),f1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},b1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},k1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),y1=[k1],v1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),L1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},M1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},H1=s('',1),V1=[H1],S1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k")])],-1),C1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},D1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},A1=s('',1),j1=[A1],Z1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),P1=e("p",null,"The downside of the standard Reed-Solomon encoding is dealing with malicious block producers that generate the extended data incorrectly.",-1),N1=e("strong",null,[t("Celestia does not require a majority of the consensus ("),e("em",null,"i.e."),t(", block producers) to be honest to guarantee data availability.")],-1),I1=e("em",null,"i.e.",-1),B1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},q1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),E1=[q1],z1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),G1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},J1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},F1=s('',1),O1=[F1],$1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),W1=e("em",null,"Fraud Proofs of Incorrectly Generated Extended Data",-1),K1=e("em",null,"i.e.",-1),U1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},X1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.345ex",height:"1.912ex",role:"img",focusable:"false",viewBox:"0 -833.9 1036.6 844.9","aria-hidden":"true"},Y1=s('',1),e4=[Y1],t4=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("msup",null,[e("mi",null,"n"),e("mn",null,"2")])])],-1),a4={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},o4={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},s4=s('',1),l4=[s4],i4=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),n4=s('
        Namespaced Merkle trees (NMTs) ​
        Celestia partitions the block data into multiple namespaces, one for every application (e.g., rollup) using the DA layer. As a result, every application needs to download only its own data and can ignore the data of other applications.
        For this to work, the DA layer must be able to prove that the provided data is complete, i.e., all the data for a given namespace is returned. To this end, Celestia is using Namespaced Merkle trees (NMTs).
        An NMT is a Merkle tree with the leafs ordered by the namespace identifiers and the hash function modified so that every node in the tree includes the range of namespaces of all its descendants. The following figure shows an example of an NMT with height three (i.e., eight data shares). The data is partitioned into three namespaces.
        Namespaced Merkle Tree
        When an application requests the data for namespace 2, the DA layer must provide the data shares D3, D4, D5, and D6 and the nodes N2, N8 and N7 as proof (note that the application already has the root N14 from the block header).
        As a result, the application is able to check that the provided data is part of the block data. Furthermore, the application can verify that all the data for namespace 2 was provided. If the DA layer provides for example only the data shares D4 and D5, it must also provide nodes N12 and N11 as proofs. However, the application can identify that the data is incomplete by checking the namespace range of the two nodes, i.e., both N12 and N11 have descendants part of namespace 2.
        For more details on NMTs, refer to the original paper.
        Building a PoS blockchain for DA ​
        Providing data availability ​
        The Celestia DA layer consists of a PoS blockchain. Celestia is dubbing this blockchain as the celestia-app, an application that provides transactions to facilitate the DA layer and is built using Cosmos SDK. The following figure shows the main components of celestia-app.
        Main components of celestia-app
        celestia-app is built on top of celestia-core, a modified version of the Tendermint consensus algorithm. Among the more important changes to vanilla Tendermint, celestia-core:
        • Enables the erasure coding of block data (using the 2-dimensional Reed-Solomon encoding scheme).
        • Replaces the regular Merkle tree used by Tendermint to store block data with a Namespaced Merkle tree that enables the above layers (i.e., execution and settlement) to only download the needed data (for more details, see the section below describing use cases).
        For more details on the changes to Tendermint, take a look at the ADRs. Notice that celestia-core nodes are still using the Tendermint p2p network.
        Similarly to Tendermint, celestia-core is connected to the application layer (i.e., the state machine) by ABCI++, a major evolution of ABCI (Application Blockchain Interface).
        The celestia-app state machine is necessary to execute the PoS logic and to enable the governance of the DA layer.
        However, the celestia-app is data-agnostic -- the state machine neither validates nor stores the data that is made available by the celestia-app.
        ',18);function r4(T4,d4,Q4,h4,c4,m4){return a(),o("div",null,[d,e("p",null,[t("To make DAS possible, Celestia uses a 2-dimensional Reed-Solomon encoding scheme to encode the block data: every block data is split into "),e("mjx-container",Q,[(a(),o("svg",h,m)),p]),t(" shares, arranged in a "),e("mjx-container",g,[(a(),o("svg",x,_)),w]),t(" matrix, and extended with parity data into a "),e("mjx-container",f,[(a(),o("svg",b,y)),v]),t(" extended matrix by applying multiple times Reed-Solomon encoding.")]),e("p",null,[t("Then, "),e("mjx-container",L,[(a(),o("svg",M,V)),S]),t(" separate Merkle roots are computed for the rows and columns of the extended matrix; the Merkle root of these Merkle roots is used as the block data commitment in the block header.")]),C,e("p",null,[t("To verify that the data is available, Celestia light nodes are sampling the "),e("mjx-container",D,[(a(),o("svg",A,Z)),P]),t(" data shares.")]),N,e("p",null,[t("Additionally, every received data share with a correct Merkle proof is gossiped to the network. As a result, as long as the Celestia light nodes are sampling together enough data shares ("),I,t(", at least "),e("mjx-container",B,[(a(),o("svg",R,E)),z]),t(" unique shares), the full block can be recovered by honest full nodes.")]),G,J,F,e("p",null,[t("This means that increasing the number of light nodes performing DAS allows for larger blocks ("),O,t(", with more transactions), while still keeping DAS feasible for resource-limited light nodes. However, in order to validate block headers, Celestia light nodes need to download the "),e("mjx-container",$,[(a(),o("svg",W,U)),X]),t(" intermediate Merkle roots.")]),e("p",null,[t("For a block data size of "),e("mjx-container",Y,[(a(),o("svg",e1,a1)),o1]),t(" bytes, this means that every light node must download "),e("mjx-container",s1,[(a(),o("svg",l1,n1)),r1]),t(" bytes. Therefore, any improvement in the bandwidth capacity of Celestia light nodes has a quadratic effect on the throughput of Celestia's DA layer.")]),T1,e("p",null,[t("The requirement of downloading the "),e("mjx-container",d1,[(a(),o("svg",Q1,c1)),m1]),t(" intermediate Merkle roots is a consequence of using a 2-dimensional Reed-Solomon encoding scheme. Alternatively, DAS could be designed with a standard ("),p1,t(", 1-dimensional) Reed-Solomon encoding, where the original data is split into "),e("mjx-container",g1,[(a(),o("svg",x1,_1)),w1]),t(" shares and extended with "),e("mjx-container",f1,[(a(),o("svg",b1,y1)),v1]),t(" additional shares of parity data. Since the block data commitment is the Merkle root of the "),e("mjx-container",L1,[(a(),o("svg",M1,V1)),S1]),t(" resulting data shares, light nodes no longer need to download "),e("mjx-container",C1,[(a(),o("svg",D1,j1)),Z1]),t(" bytes to validate block headers.")]),P1,e("p",null,[t("This is possible as "),N1,t(" Thus, if the extended data is invalid, the original data might not be recoverable, even if the light nodes are sampling sufficient unique shares ("),I1,t(", at least "),e("mjx-container",B1,[(a(),o("svg",R1,E1)),z1]),t(" for a standard encoding and "),e("mjx-container",G1,[(a(),o("svg",J1,O1)),$1]),t(" for a 2-dimensional encoding).")]),e("p",null,[t("As a solution, "),W1,t(" enable light nodes to reject blocks with invalid extended data. Such proofs require reconstructing the encoding and verifying the mismatch. With standard Reed-Solomon encoding, this entails downloading the original data, "),K1,t(", "),e("mjx-container",U1,[(a(),o("svg",X1,e4)),t4]),t(" bytes. Contrastingly, with 2-dimensional Reed-Solomon encoding, only "),e("mjx-container",a4,[(a(),o("svg",o4,l4)),i4]),t(" bytes are required as it is sufficient to verify only one row or one column of the extended matrix.")]),n4])}const x4=l(T,[["render",r4]]);export{g4 as __pageData,x4 as default};
+import{_ as l,o as a,c as o,k as e,a as t,Q as s}from"./chunks/framework.b47e54aa.js";const i="/docs-preview/pr-1699/img/learn/reed-solomon-encoding.png",n="/docs-preview/pr-1699/img/learn/nmt.png",r="/docs-preview/pr-1699/img/learn/celestia-app.png",g4=JSON.parse(`{"title":"Celestia's data availability layer","description":"Celestia's Data Availability layer and its key features.","frontmatter":{"description":"Celestia's Data Availability layer and its key features.","head":[["meta",{"name":"og:title","content":"Celestia's data availability layer | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/data-availability-layer.md","filePath":"learn/how-celestia-works/data-availability-layer.md","lastUpdated":1725992025000}`),T={name:"learn/how-celestia-works/data-availability-layer.md"},d=s('
        Celestia's data availability layer ​
        Celestia is a data availability (DA) layer that provides a scalable solution to the data availability problem. Due to the permissionless nature of the blockchain networks, a DA layer must provide a mechanism for the execution and settlement layers to check in a trust-minimized way whether transaction data is indeed available.
        Two key features of Celestia's DA layer are data availability sampling (DAS) and Namespaced Merkle trees (NMTs). Both features are novel blockchain scaling solutions: DAS enables light nodes to verify data availability without needing to download an entire block; NMTs enable execution and settlement layers on Celestia to download transactions that are only relevant to them.
        Data availability sampling (DAS) ​
        In general, light nodes download only block headers that contain commitments (i.e., Merkle roots) of the block data (i.e., the list of transactions).
        ',5),Q={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},h={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},c=s('',1),m=[c],p=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),g={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},x={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},u=s('',1),_=[u],w=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),f={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},b={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},k=s('',1),y=[k],v=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),L={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},M={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},H=s('',1),V=[H],S=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),C=e("p",null,[e("img",{src:i,alt:"2D Reed-Soloman (RS) Encoding"})],-1),D={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},A={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},j=s('',1),Z=[j],P=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),N=e("p",null,[t("Every light node randomly chooses a set of unique coordinates in the extended matrix and queries full nodes for the data shares and the corresponding Merkle proofs at those coordinates. If light nodes receive a valid response for each sampling query, then there is a "),e("a",{href:"https://github.com/celestiaorg/celestia-node/issues/805#issuecomment-1150081075",target:"_blank",rel:"noreferrer"},"high probability guarantee"),t(" that the whole block's data is available.")],-1),I=e("em",null,"i.e.",-1),B={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},q=s('',1),E=[q],z=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),G=e("p",null,[t("For more details on DAS, take a look at the "),e("a",{href:"https://arxiv.org/abs/1809.09044",target:"_blank",rel:"noreferrer"},"original paper"),t(".")],-1),J=e("h3",{id:"scalability",tabindex:"-1"},[t("Scalability "),e("a",{class:"header-anchor",href:"#scalability","aria-label":'Permalink to "Scalability"'},"​")],-1),F=e("p",null,"DAS enables Celestia to scale the DA layer. DAS can be performed by resource-limited light nodes since each light node only samples a small portion of the block data. The more light nodes there are in the network, the more data they can collectively download and store.",-1),O=e("em",null,"i.e.",-1),$={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},W={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},K=s('',1),U=[K],X=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),Y={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},e1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.345ex",height:"1.912ex",role:"img",focusable:"false",viewBox:"0 -833.9 1036.6 844.9","aria-hidden":"true"},t1=s('',1),a1=[t1],o1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("msup",null,[e("mi",null,"n"),e("mn",null,"2")])])],-1),s1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},l1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},i1=s('',1),n1=[i1],r1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),T1=e("h3",{id:"fraud-proofs-of-incorrectly-extended-data",tabindex:"-1"},[t("Fraud proofs of incorrectly extended data "),e("a",{class:"header-anchor",href:"#fraud-proofs-of-incorrectly-extended-data","aria-label":'Permalink to "Fraud proofs of incorrectly extended data"'},"​")],-1),d1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},Q1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},h1=s('',1),c1=[h1],m1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),p1=e("em",null,"i.e.",-1),g1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},x1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},u1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),_1=[u1],w1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),f1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},b1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},k1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),y1=[k1],v1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),L1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},M1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},H1=s('',1),V1=[H1],S1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k")])],-1),C1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},D1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},A1=s('',1),j1=[A1],Z1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),P1=e("p",null,"The downside of the standard Reed-Solomon encoding is dealing with malicious block producers that generate the extended data incorrectly.",-1),N1=e("strong",null,[t("Celestia does not require a majority of the consensus ("),e("em",null,"i.e."),t(", block producers) to be honest to guarantee data availability.")],-1),I1=e("em",null,"i.e.",-1),B1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},q1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),E1=[q1],z1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),G1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},J1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},F1=s('',1),O1=[F1],$1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),W1=e("em",null,"Fraud Proofs of Incorrectly Generated Extended Data",-1),K1=e("em",null,"i.e.",-1),U1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},X1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.345ex",height:"1.912ex",role:"img",focusable:"false",viewBox:"0 -833.9 1036.6 844.9","aria-hidden":"true"},Y1=s('',1),e4=[Y1],t4=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("msup",null,[e("mi",null,"n"),e("mn",null,"2")])])],-1),a4={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},o4={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},s4=s('',1),l4=[s4],i4=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),n4=s('
        Namespaced Merkle trees (NMTs) ​
        Celestia partitions the block data into multiple namespaces, one for every application (e.g., rollup) using the DA layer. As a result, every application needs to download only its own data and can ignore the data of other applications.
        For this to work, the DA layer must be able to prove that the provided data is complete, i.e., all the data for a given namespace is returned. To this end, Celestia is using Namespaced Merkle trees (NMTs).
        An NMT is a Merkle tree with the leafs ordered by the namespace identifiers and the hash function modified so that every node in the tree includes the range of namespaces of all its descendants. The following figure shows an example of an NMT with height three (i.e., eight data shares). The data is partitioned into three namespaces.
        Namespaced Merkle Tree
        When an application requests the data for namespace 2, the DA layer must provide the data shares D3, D4, D5, and D6 and the nodes N2, N8 and N7 as proof (note that the application already has the root N14 from the block header).
        As a result, the application is able to check that the provided data is part of the block data. Furthermore, the application can verify that all the data for namespace 2 was provided. If the DA layer provides for example only the data shares D4 and D5, it must also provide nodes N12 and N11 as proofs. However, the application can identify that the data is incomplete by checking the namespace range of the two nodes, i.e., both N12 and N11 have descendants part of namespace 2.
        For more details on NMTs, refer to the original paper.
        Building a PoS blockchain for DA ​
        Providing data availability ​
        The Celestia DA layer consists of a PoS blockchain. Celestia is dubbing this blockchain as the celestia-app, an application that provides transactions to facilitate the DA layer and is built using Cosmos SDK. The following figure shows the main components of celestia-app.
        Main components of celestia-app
        celestia-app is built on top of celestia-core, a modified version of the Tendermint consensus algorithm. Among the more important changes to vanilla Tendermint, celestia-core:
        • Enables the erasure coding of block data (using the 2-dimensional Reed-Solomon encoding scheme).
        • Replaces the regular Merkle tree used by Tendermint to store block data with a Namespaced Merkle tree that enables the above layers (i.e., execution and settlement) to only download the needed data (for more details, see the section below describing use cases).
        For more details on the changes to Tendermint, take a look at the ADRs. Notice that celestia-core nodes are still using the Tendermint p2p network.
        Similarly to Tendermint, celestia-core is connected to the application layer (i.e., the state machine) by ABCI++, a major evolution of ABCI (Application Blockchain Interface).
        The celestia-app state machine is necessary to execute the PoS logic and to enable the governance of the DA layer.
        However, the celestia-app is data-agnostic -- the state machine neither validates nor stores the data that is made available by the celestia-app.
        ',18);function r4(T4,d4,Q4,h4,c4,m4){return a(),o("div",null,[d,e("p",null,[t("To make DAS possible, Celestia uses a 2-dimensional Reed-Solomon encoding scheme to encode the block data: every block data is split into "),e("mjx-container",Q,[(a(),o("svg",h,m)),p]),t(" shares, arranged in a "),e("mjx-container",g,[(a(),o("svg",x,_)),w]),t(" matrix, and extended with parity data into a "),e("mjx-container",f,[(a(),o("svg",b,y)),v]),t(" extended matrix by applying multiple times Reed-Solomon encoding.")]),e("p",null,[t("Then, "),e("mjx-container",L,[(a(),o("svg",M,V)),S]),t(" separate Merkle roots are computed for the rows and columns of the extended matrix; the Merkle root of these Merkle roots is used as the block data commitment in the block header.")]),C,e("p",null,[t("To verify that the data is available, Celestia light nodes are sampling the "),e("mjx-container",D,[(a(),o("svg",A,Z)),P]),t(" data shares.")]),N,e("p",null,[t("Additionally, every received data share with a correct Merkle proof is gossiped to the network. As a result, as long as the Celestia light nodes are sampling together enough data shares ("),I,t(", at least "),e("mjx-container",B,[(a(),o("svg",R,E)),z]),t(" unique shares), the full block can be recovered by honest full nodes.")]),G,J,F,e("p",null,[t("This means that increasing the number of light nodes performing DAS allows for larger blocks ("),O,t(", with more transactions), while still keeping DAS feasible for resource-limited light nodes. However, in order to validate block headers, Celestia light nodes need to download the "),e("mjx-container",$,[(a(),o("svg",W,U)),X]),t(" intermediate Merkle roots.")]),e("p",null,[t("For a block data size of "),e("mjx-container",Y,[(a(),o("svg",e1,a1)),o1]),t(" bytes, this means that every light node must download "),e("mjx-container",s1,[(a(),o("svg",l1,n1)),r1]),t(" bytes. Therefore, any improvement in the bandwidth capacity of Celestia light nodes has a quadratic effect on the throughput of Celestia's DA layer.")]),T1,e("p",null,[t("The requirement of downloading the "),e("mjx-container",d1,[(a(),o("svg",Q1,c1)),m1]),t(" intermediate Merkle roots is a consequence of using a 2-dimensional Reed-Solomon encoding scheme. Alternatively, DAS could be designed with a standard ("),p1,t(", 1-dimensional) Reed-Solomon encoding, where the original data is split into "),e("mjx-container",g1,[(a(),o("svg",x1,_1)),w1]),t(" shares and extended with "),e("mjx-container",f1,[(a(),o("svg",b1,y1)),v1]),t(" additional shares of parity data. Since the block data commitment is the Merkle root of the "),e("mjx-container",L1,[(a(),o("svg",M1,V1)),S1]),t(" resulting data shares, light nodes no longer need to download "),e("mjx-container",C1,[(a(),o("svg",D1,j1)),Z1]),t(" bytes to validate block headers.")]),P1,e("p",null,[t("This is possible as "),N1,t(" Thus, if the extended data is invalid, the original data might not be recoverable, even if the light nodes are sampling sufficient unique shares ("),I1,t(", at least "),e("mjx-container",B1,[(a(),o("svg",R1,E1)),z1]),t(" for a standard encoding and "),e("mjx-container",G1,[(a(),o("svg",J1,O1)),$1]),t(" for a 2-dimensional encoding).")]),e("p",null,[t("As a solution, "),W1,t(" enable light nodes to reject blocks with invalid extended data. Such proofs require reconstructing the encoding and verifying the mismatch. With standard Reed-Solomon encoding, this entails downloading the original data, "),K1,t(", "),e("mjx-container",U1,[(a(),o("svg",X1,e4)),t4]),t(" bytes. Contrastingly, with 2-dimensional Reed-Solomon encoding, only "),e("mjx-container",a4,[(a(),o("svg",o4,l4)),i4]),t(" bytes are required as it is sufficient to verify only one row or one column of the extended matrix.")]),n4])}const x4=l(T,[["render",r4]]);export{g4 as __pageData,x4 as default};
diff --git a/pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.d71fa908.lean.js b/pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.4a9aff1a.lean.js
similarity index 99%
rename from pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.d71fa908.lean.js
rename to pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.4a9aff1a.lean.js
index 96bf0284a1..02d0d71dde 100644
--- a/pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.d71fa908.lean.js
+++ b/pr-1699/assets/learn_how-celestia-works_data-availability-layer.md.4a9aff1a.lean.js
@@ -1 +1 @@
-import{_ as l,o as a,c as o,k as e,a as t,Q as s}from"./chunks/framework.b47e54aa.js";const i="/docs-preview/pr-1699/img/learn/reed-solomon-encoding.png",n="/docs-preview/pr-1699/img/learn/nmt.png",r="/docs-preview/pr-1699/img/learn/celestia-app.png",g4=JSON.parse(`{"title":"Celestia's data availability layer","description":"Celestia's Data Availability layer and its key features.","frontmatter":{"description":"Celestia's Data Availability layer and its key features.","head":[["meta",{"name":"og:title","content":"Celestia's data availability layer | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/data-availability-layer.md","filePath":"learn/how-celestia-works/data-availability-layer.md","lastUpdated":1725971357000}`),T={name:"learn/how-celestia-works/data-availability-layer.md"},d=s("",5),Q={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},h={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},c=s("",1),m=[c],p=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),g={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},x={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},u=s("",1),_=[u],w=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),f={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},b={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},k=s("",1),y=[k],v=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),L={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},M={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},H=s("",1),V=[H],S=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),C=e("p",null,[e("img",{src:i,alt:"2D Reed-Soloman (RS) Encoding"})],-1),D={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},A={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},j=s("",1),Z=[j],P=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),N=e("p",null,[t("Every light node randomly chooses a set of unique coordinates in the extended matrix and queries full nodes for the data shares and the corresponding Merkle proofs at those coordinates. If light nodes receive a valid response for each sampling query, then there is a "),e("a",{href:"https://github.com/celestiaorg/celestia-node/issues/805#issuecomment-1150081075",target:"_blank",rel:"noreferrer"},"high probability guarantee"),t(" that the whole block's data is available.")],-1),I=e("em",null,"i.e.",-1),B={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},q=s("",1),E=[q],z=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),G=e("p",null,[t("For more details on DAS, take a look at the "),e("a",{href:"https://arxiv.org/abs/1809.09044",target:"_blank",rel:"noreferrer"},"original paper"),t(".")],-1),J=e("h3",{id:"scalability",tabindex:"-1"},[t("Scalability "),e("a",{class:"header-anchor",href:"#scalability","aria-label":'Permalink to "Scalability"'},"​")],-1),F=e("p",null,"DAS enables Celestia to scale the DA layer. DAS can be performed by resource-limited light nodes since each light node only samples a small portion of the block data. The more light nodes there are in the network, the more data they can collectively download and store.",-1),O=e("em",null,"i.e.",-1),$={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},W={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},K=s("",1),U=[K],X=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),Y={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},e1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.345ex",height:"1.912ex",role:"img",focusable:"false",viewBox:"0 -833.9 1036.6 844.9","aria-hidden":"true"},t1=s("",1),a1=[t1],o1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("msup",null,[e("mi",null,"n"),e("mn",null,"2")])])],-1),s1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},l1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},i1=s("",1),n1=[i1],r1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),T1=e("h3",{id:"fraud-proofs-of-incorrectly-extended-data",tabindex:"-1"},[t("Fraud proofs of incorrectly extended data "),e("a",{class:"header-anchor",href:"#fraud-proofs-of-incorrectly-extended-data","aria-label":'Permalink to "Fraud proofs of incorrectly extended data"'},"​")],-1),d1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},Q1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},h1=s("",1),c1=[h1],m1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),p1=e("em",null,"i.e.",-1),g1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},x1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},u1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),_1=[u1],w1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),f1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},b1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},k1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),y1=[k1],v1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),L1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},M1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},H1=s("",1),V1=[H1],S1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k")])],-1),C1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},D1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},A1=s("",1),j1=[A1],Z1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),P1=e("p",null,"The downside of the standard Reed-Solomon encoding is dealing with malicious block producers that generate the extended data incorrectly.",-1),N1=e("strong",null,[t("Celestia does not require a majority of the consensus ("),e("em",null,"i.e."),t(", block producers) to be honest to guarantee data availability.")],-1),I1=e("em",null,"i.e.",-1),B1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},q1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),E1=[q1],z1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),G1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},J1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},F1=s("",1),O1=[F1],$1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),W1=e("em",null,"Fraud Proofs of Incorrectly Generated Extended Data",-1),K1=e("em",null,"i.e.",-1),U1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},X1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.345ex",height:"1.912ex",role:"img",focusable:"false",viewBox:"0 -833.9 1036.6 844.9","aria-hidden":"true"},Y1=s("",1),e4=[Y1],t4=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("msup",null,[e("mi",null,"n"),e("mn",null,"2")])])],-1),a4={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},o4={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},s4=s("",1),l4=[s4],i4=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),n4=s("",18);function r4(T4,d4,Q4,h4,c4,m4){return a(),o("div",null,[d,e("p",null,[t("To make DAS possible, Celestia uses a 2-dimensional Reed-Solomon encoding scheme to encode the block data: every block data is split into "),e("mjx-container",Q,[(a(),o("svg",h,m)),p]),t(" shares, arranged in a "),e("mjx-container",g,[(a(),o("svg",x,_)),w]),t(" matrix, and extended with parity data into a "),e("mjx-container",f,[(a(),o("svg",b,y)),v]),t(" extended matrix by applying multiple times Reed-Solomon encoding.")]),e("p",null,[t("Then, "),e("mjx-container",L,[(a(),o("svg",M,V)),S]),t(" separate Merkle roots are computed for the rows and columns of the extended matrix; the Merkle root of these Merkle roots is used as the block data commitment in the block header.")]),C,e("p",null,[t("To verify that the data is available, Celestia light nodes are sampling the "),e("mjx-container",D,[(a(),o("svg",A,Z)),P]),t(" data shares.")]),N,e("p",null,[t("Additionally, every received data share with a correct Merkle proof is gossiped to the network. As a result, as long as the Celestia light nodes are sampling together enough data shares ("),I,t(", at least "),e("mjx-container",B,[(a(),o("svg",R,E)),z]),t(" unique shares), the full block can be recovered by honest full nodes.")]),G,J,F,e("p",null,[t("This means that increasing the number of light nodes performing DAS allows for larger blocks ("),O,t(", with more transactions), while still keeping DAS feasible for resource-limited light nodes. However, in order to validate block headers, Celestia light nodes need to download the "),e("mjx-container",$,[(a(),o("svg",W,U)),X]),t(" intermediate Merkle roots.")]),e("p",null,[t("For a block data size of "),e("mjx-container",Y,[(a(),o("svg",e1,a1)),o1]),t(" bytes, this means that every light node must download "),e("mjx-container",s1,[(a(),o("svg",l1,n1)),r1]),t(" bytes. Therefore, any improvement in the bandwidth capacity of Celestia light nodes has a quadratic effect on the throughput of Celestia's DA layer.")]),T1,e("p",null,[t("The requirement of downloading the "),e("mjx-container",d1,[(a(),o("svg",Q1,c1)),m1]),t(" intermediate Merkle roots is a consequence of using a 2-dimensional Reed-Solomon encoding scheme. Alternatively, DAS could be designed with a standard ("),p1,t(", 1-dimensional) Reed-Solomon encoding, where the original data is split into "),e("mjx-container",g1,[(a(),o("svg",x1,_1)),w1]),t(" shares and extended with "),e("mjx-container",f1,[(a(),o("svg",b1,y1)),v1]),t(" additional shares of parity data. Since the block data commitment is the Merkle root of the "),e("mjx-container",L1,[(a(),o("svg",M1,V1)),S1]),t(" resulting data shares, light nodes no longer need to download "),e("mjx-container",C1,[(a(),o("svg",D1,j1)),Z1]),t(" bytes to validate block headers.")]),P1,e("p",null,[t("This is possible as "),N1,t(" Thus, if the extended data is invalid, the original data might not be recoverable, even if the light nodes are sampling sufficient unique shares ("),I1,t(", at least "),e("mjx-container",B1,[(a(),o("svg",R1,E1)),z1]),t(" for a standard encoding and "),e("mjx-container",G1,[(a(),o("svg",J1,O1)),$1]),t(" for a 2-dimensional encoding).")]),e("p",null,[t("As a solution, "),W1,t(" enable light nodes to reject blocks with invalid extended data. Such proofs require reconstructing the encoding and verifying the mismatch. With standard Reed-Solomon encoding, this entails downloading the original data, "),K1,t(", "),e("mjx-container",U1,[(a(),o("svg",X1,e4)),t4]),t(" bytes. Contrastingly, with 2-dimensional Reed-Solomon encoding, only "),e("mjx-container",a4,[(a(),o("svg",o4,l4)),i4]),t(" bytes are required as it is sufficient to verify only one row or one column of the extended matrix.")]),n4])}const x4=l(T,[["render",r4]]);export{g4 as __pageData,x4 as default};
+import{_ as l,o as a,c as o,k as e,a as t,Q as s}from"./chunks/framework.b47e54aa.js";const i="/docs-preview/pr-1699/img/learn/reed-solomon-encoding.png",n="/docs-preview/pr-1699/img/learn/nmt.png",r="/docs-preview/pr-1699/img/learn/celestia-app.png",g4=JSON.parse(`{"title":"Celestia's data availability layer","description":"Celestia's Data Availability layer and its key features.","frontmatter":{"description":"Celestia's Data Availability layer and its key features.","head":[["meta",{"name":"og:title","content":"Celestia's data availability layer | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/data-availability-layer.md","filePath":"learn/how-celestia-works/data-availability-layer.md","lastUpdated":1725992025000}`),T={name:"learn/how-celestia-works/data-availability-layer.md"},d=s("",5),Q={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},h={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},c=s("",1),m=[c],p=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),g={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},x={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},u=s("",1),_=[u],w=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),f={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},b={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},k=s("",1),y=[k],v=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),L={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},M={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},H=s("",1),V=[H],S=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),C=e("p",null,[e("img",{src:i,alt:"2D Reed-Soloman (RS) Encoding"})],-1),D={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},A={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},j=s("",1),Z=[j],P=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),N=e("p",null,[t("Every light node randomly chooses a set of unique coordinates in the extended matrix and queries full nodes for the data shares and the corresponding Merkle proofs at those coordinates. If light nodes receive a valid response for each sampling query, then there is a "),e("a",{href:"https://github.com/celestiaorg/celestia-node/issues/805#issuecomment-1150081075",target:"_blank",rel:"noreferrer"},"high probability guarantee"),t(" that the whole block's data is available.")],-1),I=e("em",null,"i.e.",-1),B={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},q=s("",1),E=[q],z=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),G=e("p",null,[t("For more details on DAS, take a look at the "),e("a",{href:"https://arxiv.org/abs/1809.09044",target:"_blank",rel:"noreferrer"},"original paper"),t(".")],-1),J=e("h3",{id:"scalability",tabindex:"-1"},[t("Scalability "),e("a",{class:"header-anchor",href:"#scalability","aria-label":'Permalink to "Scalability"'},"​")],-1),F=e("p",null,"DAS enables Celestia to scale the DA layer. DAS can be performed by resource-limited light nodes since each light node only samples a small portion of the block data. The more light nodes there are in the network, the more data they can collectively download and store.",-1),O=e("em",null,"i.e.",-1),$={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},W={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},K=s("",1),U=[K],X=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),Y={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},e1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.345ex",height:"1.912ex",role:"img",focusable:"false",viewBox:"0 -833.9 1036.6 844.9","aria-hidden":"true"},t1=s("",1),a1=[t1],o1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("msup",null,[e("mi",null,"n"),e("mn",null,"2")])])],-1),s1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},l1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},i1=s("",1),n1=[i1],r1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),T1=e("h3",{id:"fraud-proofs-of-incorrectly-extended-data",tabindex:"-1"},[t("Fraud proofs of incorrectly extended data "),e("a",{class:"header-anchor",href:"#fraud-proofs-of-incorrectly-extended-data","aria-label":'Permalink to "Fraud proofs of incorrectly extended data"'},"​")],-1),d1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},Q1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},h1=s("",1),c1=[h1],m1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),p1=e("em",null,"i.e.",-1),g1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},x1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},u1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),_1=[u1],w1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),f1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},b1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},k1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),y1=[k1],v1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),L1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},M1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},H1=s("",1),V1=[H1],S1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k")])],-1),C1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},D1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},A1=s("",1),j1=[A1],Z1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),P1=e("p",null,"The downside of the standard Reed-Solomon encoding is dealing with malicious block producers that generate the extended data incorrectly.",-1),N1=e("strong",null,[t("Celestia does not require a majority of the consensus ("),e("em",null,"i.e."),t(", block producers) to be honest to guarantee data availability.")],-1),I1=e("em",null,"i.e.",-1),B1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},R1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"1.179ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 521 705","aria-hidden":"true"},q1=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mi"},[e("path",{"data-c":"1D458",d:"M121 647Q121 657 125 670T137 683Q138 683 209 688T282 694Q294 694 294 686Q294 679 244 477Q194 279 194 272Q213 282 223 291Q247 309 292 354T362 415Q402 442 438 442Q468 442 485 423T503 369Q503 344 496 327T477 302T456 291T438 288Q418 288 406 299T394 328Q394 353 410 369T442 390L458 393Q446 405 434 405H430Q398 402 367 380T294 316T228 255Q230 254 243 252T267 246T293 238T320 224T342 206T359 180T365 147Q365 130 360 106T354 66Q354 26 381 26Q429 26 459 145Q461 153 479 153H483Q499 153 499 144Q499 139 496 130Q455 -11 378 -11Q333 -11 305 15T277 90Q277 108 280 121T283 145Q283 167 269 183T234 206T200 217T182 220H180Q168 178 159 139T145 81T136 44T129 20T122 7T111 -2Q98 -11 83 -11Q66 -11 57 -1T48 16Q48 26 85 176T158 471L195 616Q196 629 188 632T149 637H144Q134 637 131 637T124 640T121 647Z",style:{"stroke-width":"3"}})])])],-1),E1=[q1],z1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k")])],-1),G1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},J1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},F1=s("",1),O1=[F1],$1=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),W1=e("em",null,"Fraud Proofs of Incorrectly Generated Extended Data",-1),K1=e("em",null,"i.e.",-1),U1={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},X1={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.345ex",height:"1.912ex",role:"img",focusable:"false",viewBox:"0 -833.9 1036.6 844.9","aria-hidden":"true"},Y1=s("",1),e4=[Y1],t4=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("msup",null,[e("mi",null,"n"),e("mn",null,"2")])])],-1),a4={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},o4={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"4.844ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 2141 1000","aria-hidden":"true"},s4=s("",1),l4=[s4],i4=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"O"),e("mo",{stretchy:"false"},"("),e("mi",null,"n"),e("mo",{stretchy:"false"},")")])],-1),n4=s("",18);function r4(T4,d4,Q4,h4,c4,m4){return a(),o("div",null,[d,e("p",null,[t("To make DAS possible, Celestia uses a 2-dimensional Reed-Solomon encoding scheme to encode the block data: every block data is split into "),e("mjx-container",Q,[(a(),o("svg",h,m)),p]),t(" shares, arranged in a "),e("mjx-container",g,[(a(),o("svg",x,_)),w]),t(" matrix, and extended with parity data into a "),e("mjx-container",f,[(a(),o("svg",b,y)),v]),t(" extended matrix by applying multiple times Reed-Solomon encoding.")]),e("p",null,[t("Then, "),e("mjx-container",L,[(a(),o("svg",M,V)),S]),t(" separate Merkle roots are computed for the rows and columns of the extended matrix; the Merkle root of these Merkle roots is used as the block data commitment in the block header.")]),C,e("p",null,[t("To verify that the data is available, Celestia light nodes are sampling the "),e("mjx-container",D,[(a(),o("svg",A,Z)),P]),t(" data shares.")]),N,e("p",null,[t("Additionally, every received data share with a correct Merkle proof is gossiped to the network. As a result, as long as the Celestia light nodes are sampling together enough data shares ("),I,t(", at least "),e("mjx-container",B,[(a(),o("svg",R,E)),z]),t(" unique shares), the full block can be recovered by honest full nodes.")]),G,J,F,e("p",null,[t("This means that increasing the number of light nodes performing DAS allows for larger blocks ("),O,t(", with more transactions), while still keeping DAS feasible for resource-limited light nodes. However, in order to validate block headers, Celestia light nodes need to download the "),e("mjx-container",$,[(a(),o("svg",W,U)),X]),t(" intermediate Merkle roots.")]),e("p",null,[t("For a block data size of "),e("mjx-container",Y,[(a(),o("svg",e1,a1)),o1]),t(" bytes, this means that every light node must download "),e("mjx-container",s1,[(a(),o("svg",l1,n1)),r1]),t(" bytes. Therefore, any improvement in the bandwidth capacity of Celestia light nodes has a quadratic effect on the throughput of Celestia's DA layer.")]),T1,e("p",null,[t("The requirement of downloading the "),e("mjx-container",d1,[(a(),o("svg",Q1,c1)),m1]),t(" intermediate Merkle roots is a consequence of using a 2-dimensional Reed-Solomon encoding scheme. Alternatively, DAS could be designed with a standard ("),p1,t(", 1-dimensional) Reed-Solomon encoding, where the original data is split into "),e("mjx-container",g1,[(a(),o("svg",x1,_1)),w1]),t(" shares and extended with "),e("mjx-container",f1,[(a(),o("svg",b1,y1)),v1]),t(" additional shares of parity data. Since the block data commitment is the Merkle root of the "),e("mjx-container",L1,[(a(),o("svg",M1,V1)),S1]),t(" resulting data shares, light nodes no longer need to download "),e("mjx-container",C1,[(a(),o("svg",D1,j1)),Z1]),t(" bytes to validate block headers.")]),P1,e("p",null,[t("This is possible as "),N1,t(" Thus, if the extended data is invalid, the original data might not be recoverable, even if the light nodes are sampling sufficient unique shares ("),I1,t(", at least "),e("mjx-container",B1,[(a(),o("svg",R1,E1)),z1]),t(" for a standard encoding and "),e("mjx-container",G1,[(a(),o("svg",J1,O1)),$1]),t(" for a 2-dimensional encoding).")]),e("p",null,[t("As a solution, "),W1,t(" enable light nodes to reject blocks with invalid extended data. Such proofs require reconstructing the encoding and verifying the mismatch. With standard Reed-Solomon encoding, this entails downloading the original data, "),K1,t(", "),e("mjx-container",U1,[(a(),o("svg",X1,e4)),t4]),t(" bytes. Contrastingly, with 2-dimensional Reed-Solomon encoding, only "),e("mjx-container",a4,[(a(),o("svg",o4,l4)),i4]),t(" bytes are required as it is sufficient to verify only one row or one column of the extended matrix.")]),n4])}const x4=l(T,[["render",r4]]);export{g4 as __pageData,x4 as default};
diff --git a/pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.8f0114bd.js b/pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.63b4aa3e.js
similarity index 98%
rename from pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.8f0114bd.js
rename to pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.63b4aa3e.js
index 14f3cc6796..a32e559503 100644
--- a/pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.8f0114bd.js
+++ b/pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.63b4aa3e.js
@@ -1 +1 @@
-import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const n="/docs-preview/pr-1699/img/learn/monolithic-modular.png",g=JSON.parse('{"title":"Monolithic vs. modular blockchains","description":"Comparison between monolithic and modular blockchains.","frontmatter":{"description":"Comparison between monolithic and modular blockchains.","head":[["meta",{"name":"og:title","content":"Monolithic vs. modular blockchains | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/monolithic-vs-modular.md","filePath":"learn/how-celestia-works/monolithic-vs-modular.md","lastUpdated":1725971357000}'),i={name:"learn/how-celestia-works/monolithic-vs-modular.md"},s=a('
        Monolithic vs. modular blockchains ​
        Blockchains instantiate replicated state machines: the nodes in a permissionless distributed network apply an ordered sequence of deterministic transactions to an initial state resulting in a common final state.
        In other words, this means that nodes in a network all follow the same set of rules (i.e., an ordered sequence of transactions) to go from a starting point (i.e., an initial state) to an ending point (i.e., a common final state). This process ensures that all nodes in the network agree on the final state of the blockchain, even though they operate independently.
        This means blockchains require the following four functions:
        • Execution entails executing transactions that update the state correctly. Thus, execution must ensure that only valid transactions are executed, i.e., transactions that result in valid state machine transitions.
        • Settlement entails an environment for execution layers to verify proofs, resolve fraud disputes, and bridge between other execution layers.
        • Consensus entails agreeing on the order of the transactions.
        • Data Availability (DA) entails making the transaction data available. Note that execution, settlement, and consensus require DA.
        Traditional blockchains, i.e. monolithic blockchains, implement all four functions together in a single base consensus layer. The problem with monolithic blockchains is that the consensus layer must perform numerous different tasks, and it cannot be optimized for only one of these functions. As a result, the monolithic paradigm limits the throughput of the system.
        Modular VS Monolithic
        As a solution, modular blockchains decouple these functions among multiple specialized layers as part of a modular stack. Due to the flexibility that specialization provides, there are many possibilities in which that stack can be arranged. For example, one such arrangement is the separation of the four functions into three specialized layers.
        The base layer consists of DA and consensus and thus, is referred to as the Consensus and DA layer (or for brevity, the DA layer), while both settlement and execution are moved on top in their own layers. As a result, every layer can be specialized to optimally perform only its function, and thus, increase the throughput of the system. Furthermore, this modular paradigm enables multiple execution layers, i.e., rollups, to use the same settlement and DA layers.
        ',9),r=[s];function l(c,h,m,d,u,p){return t(),o("div",null,r)}const b=e(i,[["render",l]]);export{g as __pageData,b as default};
+import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const n="/docs-preview/pr-1699/img/learn/monolithic-modular.png",g=JSON.parse('{"title":"Monolithic vs. modular blockchains","description":"Comparison between monolithic and modular blockchains.","frontmatter":{"description":"Comparison between monolithic and modular blockchains.","head":[["meta",{"name":"og:title","content":"Monolithic vs. modular blockchains | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/monolithic-vs-modular.md","filePath":"learn/how-celestia-works/monolithic-vs-modular.md","lastUpdated":1725992025000}'),i={name:"learn/how-celestia-works/monolithic-vs-modular.md"},s=a('
        Monolithic vs. modular blockchains ​
        Blockchains instantiate replicated state machines: the nodes in a permissionless distributed network apply an ordered sequence of deterministic transactions to an initial state resulting in a common final state.
        In other words, this means that nodes in a network all follow the same set of rules (i.e., an ordered sequence of transactions) to go from a starting point (i.e., an initial state) to an ending point (i.e., a common final state). This process ensures that all nodes in the network agree on the final state of the blockchain, even though they operate independently.
        This means blockchains require the following four functions:
        • Execution entails executing transactions that update the state correctly. Thus, execution must ensure that only valid transactions are executed, i.e., transactions that result in valid state machine transitions.
        • Settlement entails an environment for execution layers to verify proofs, resolve fraud disputes, and bridge between other execution layers.
        • Consensus entails agreeing on the order of the transactions.
        • Data Availability (DA) entails making the transaction data available. Note that execution, settlement, and consensus require DA.
        Traditional blockchains, i.e. monolithic blockchains, implement all four functions together in a single base consensus layer. The problem with monolithic blockchains is that the consensus layer must perform numerous different tasks, and it cannot be optimized for only one of these functions. As a result, the monolithic paradigm limits the throughput of the system.
        Modular VS Monolithic
        As a solution, modular blockchains decouple these functions among multiple specialized layers as part of a modular stack. Due to the flexibility that specialization provides, there are many possibilities in which that stack can be arranged. For example, one such arrangement is the separation of the four functions into three specialized layers.
        The base layer consists of DA and consensus and thus, is referred to as the Consensus and DA layer (or for brevity, the DA layer), while both settlement and execution are moved on top in their own layers. As a result, every layer can be specialized to optimally perform only its function, and thus, increase the throughput of the system. Furthermore, this modular paradigm enables multiple execution layers, i.e., rollups, to use the same settlement and DA layers.
        ',9),r=[s];function l(c,h,m,d,u,p){return t(),o("div",null,r)}const b=e(i,[["render",l]]);export{g as __pageData,b as default};
diff --git a/pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.8f0114bd.lean.js b/pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.63b4aa3e.lean.js
similarity index 92%
rename from pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.8f0114bd.lean.js
rename to pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.63b4aa3e.lean.js
index c1e7fe0bc6..7f90514669 100644
--- a/pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.8f0114bd.lean.js
+++ b/pr-1699/assets/learn_how-celestia-works_monolithic-vs-modular.md.63b4aa3e.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const n="/docs-preview/pr-1699/img/learn/monolithic-modular.png",g=JSON.parse('{"title":"Monolithic vs. modular blockchains","description":"Comparison between monolithic and modular blockchains.","frontmatter":{"description":"Comparison between monolithic and modular blockchains.","head":[["meta",{"name":"og:title","content":"Monolithic vs. modular blockchains | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/monolithic-vs-modular.md","filePath":"learn/how-celestia-works/monolithic-vs-modular.md","lastUpdated":1725971357000}'),i={name:"learn/how-celestia-works/monolithic-vs-modular.md"},s=a("",9),r=[s];function l(c,h,m,d,u,p){return t(),o("div",null,r)}const b=e(i,[["render",l]]);export{g as __pageData,b as default};
+import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const n="/docs-preview/pr-1699/img/learn/monolithic-modular.png",g=JSON.parse('{"title":"Monolithic vs. modular blockchains","description":"Comparison between monolithic and modular blockchains.","frontmatter":{"description":"Comparison between monolithic and modular blockchains.","head":[["meta",{"name":"og:title","content":"Monolithic vs. modular blockchains | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/monolithic-vs-modular.md","filePath":"learn/how-celestia-works/monolithic-vs-modular.md","lastUpdated":1725992025000}'),i={name:"learn/how-celestia-works/monolithic-vs-modular.md"},s=a("",9),r=[s];function l(c,h,m,d,u,p){return t(),o("div",null,r)}const b=e(i,[["render",l]]);export{g as __pageData,b as default};
diff --git a/pr-1699/assets/learn_how-celestia-works_overview.md.e560d4a4.js b/pr-1699/assets/learn_how-celestia-works_overview.md.42a4dc74.js
similarity index 97%
rename from pr-1699/assets/learn_how-celestia-works_overview.md.e560d4a4.js
rename to pr-1699/assets/learn_how-celestia-works_overview.md.42a4dc74.js
index 4f74f9d5bd..afa524f403 100644
--- a/pr-1699/assets/learn_how-celestia-works_overview.md.e560d4a4.js
+++ b/pr-1699/assets/learn_how-celestia-works_overview.md.42a4dc74.js
@@ -1 +1 @@
-import{_ as e,o as a,c as t,Q as r}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Introduction | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/overview.md","filePath":"learn/how-celestia-works/overview.md","lastUpdated":1725971357000}'),i={name:"learn/how-celestia-works/overview.md"},o=r('
        Introduction ​
        Celestia is a modular data availability network that securely scales with the number of users, making it easy for anyone to launch their own blockchain.
        Celestia enables the next generation of scalable blockchain architectures - modular blockchains. Celestia scales by decoupling execution from consensus and introducing a new primitive, data availability sampling.
        The former entails that Celestia is only responsible for ordering transactions and guaranteeing their data availability; this is similar to reducing consensus to atomic broadcast.
        The latter provides an efficient solution to the data availability problem by only requiring resource-limited light nodes to sample a small number of random shares from each block to verify data availability.
        Interestingly, more light nodes that participate in sampling increases the amount of data that the network can safely handle, enabling the block size to increase without equally increasing the cost to verify the chain.
        ',6),n=[o];function s(l,c,h,d,p,m){return a(),t("div",null,n)}const _=e(i,[["render",s]]);export{f as __pageData,_ as default};
+import{_ as e,o as a,c as t,Q as r}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Introduction | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/overview.md","filePath":"learn/how-celestia-works/overview.md","lastUpdated":1725992025000}'),i={name:"learn/how-celestia-works/overview.md"},o=r('
        Introduction ​
        Celestia is a modular data availability network that securely scales with the number of users, making it easy for anyone to launch their own blockchain.
        Celestia enables the next generation of scalable blockchain architectures - modular blockchains. Celestia scales by decoupling execution from consensus and introducing a new primitive, data availability sampling.
        The former entails that Celestia is only responsible for ordering transactions and guaranteeing their data availability; this is similar to reducing consensus to atomic broadcast.
        The latter provides an efficient solution to the data availability problem by only requiring resource-limited light nodes to sample a small number of random shares from each block to verify data availability.
        Interestingly, more light nodes that participate in sampling increases the amount of data that the network can safely handle, enabling the block size to increase without equally increasing the cost to verify the chain.
        ',6),n=[o];function s(l,c,h,d,p,m){return a(),t("div",null,n)}const _=e(i,[["render",s]]);export{f as __pageData,_ as default};
diff --git a/pr-1699/assets/learn_how-celestia-works_overview.md.e560d4a4.lean.js b/pr-1699/assets/learn_how-celestia-works_overview.md.42a4dc74.lean.js
similarity index 89%
rename from pr-1699/assets/learn_how-celestia-works_overview.md.e560d4a4.lean.js
rename to pr-1699/assets/learn_how-celestia-works_overview.md.42a4dc74.lean.js
index 134320c1ce..b14e754283 100644
--- a/pr-1699/assets/learn_how-celestia-works_overview.md.e560d4a4.lean.js
+++ b/pr-1699/assets/learn_how-celestia-works_overview.md.42a4dc74.lean.js
@@ -1 +1 @@
-import{_ as e,o as a,c as t,Q as r}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Introduction | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/overview.md","filePath":"learn/how-celestia-works/overview.md","lastUpdated":1725971357000}'),i={name:"learn/how-celestia-works/overview.md"},o=r("",6),n=[o];function s(l,c,h,d,p,m){return a(),t("div",null,n)}const _=e(i,[["render",s]]);export{f as __pageData,_ as default};
+import{_ as e,o as a,c as t,Q as r}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Introduction | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/overview.md","filePath":"learn/how-celestia-works/overview.md","lastUpdated":1725992025000}'),i={name:"learn/how-celestia-works/overview.md"},o=r("",6),n=[o];function s(l,c,h,d,p,m){return a(),t("div",null,n)}const _=e(i,[["render",s]]);export{f as __pageData,_ as default};
diff --git a/pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.d8853cb7.js b/pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.def776d7.js
similarity index 99%
rename from pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.d8853cb7.js
rename to pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.def776d7.js
index fc84585d02..c6bc969114 100644
--- a/pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.d8853cb7.js
+++ b/pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.def776d7.js
@@ -1 +1 @@
-import{_ as i}from"./chunks/tx-lifecycle.e01c569f.js";import{_ as n,o as a,c as o,k as e,a as t,Q as s}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/learn/consensus-da.png",K=JSON.parse('{"title":"The lifecycle of a celestia-app transaction","description":"Learn what is the lifecycle of a celestia-app transaction.","frontmatter":{"description":"Learn what is the lifecycle of a celestia-app transaction.","head":[["meta",{"name":"og:title","content":"The lifecycle of a celestia-app transaction | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/transaction-lifecycle.md","filePath":"learn/how-celestia-works/transaction-lifecycle.md","lastUpdated":1725971357000}'),r={name:"learn/how-celestia-works/transaction-lifecycle.md"},c=s('
        The lifecycle of a celestia-app transaction ​
        Users request the celestia-app to make data available by sending PayForBlobs transactions. Every such transaction consists of the identity of the sender, the data to be made available, also referred to as the message, the data size, the namespace, and a signature. Every block producer batches multiple PayForBlobs transactions into a block.
        Before proposing the block though, the producer passes it to the state machine via ABCI++, where each PayForBlobs transaction is split into a namespaced message (denoted by Msg in the figure below), i.e., the data together with the namespace ID, and an executable transaction (denoted by e-Tx in the figure below) that does not contain the data, but only a commitment that can be used at a later time to prove that the data was indeed made available.
        Thus, the block data consists of data partitioned into namespaces and executable transactions. Note that only these transactions are executed by the Celestia state machine once the block is committed.
        Lifecycle of a celestia-app Transaction
        ',5),d=e("a",{href:"./data-availability-layer"},`described in the "Celestia's data availability layer" page`,-1),h={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},T={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},Q=s('',1),p=[Q],m=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),u=e("li",null,"It splits the executable transactions and the namespaced data into shares. Every share consists of some bytes prefixed by a namespace. To this end, the executable transactions are associated with a reserved namespace.",-1),_={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},g={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},f=s('',1),x=[f],w=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),b={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},k={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},y=s('',1),v=[y],L=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),H=e("li",null,"It computes a commitment for every row and column of the extended matrix using the NMTs described above.",-1),V=e("p",null,"Thus, the commitment of the block data is the root of a Merkle tree with the leaves the roots of a forest of Namespaced Merkle subtrees, one for every row and column of the extended matrix.",-1),M=e("h2",{id:"checking-data-availability",tabindex:"-1"},[t("Checking data availability "),e("a",{class:"header-anchor",href:"#checking-data-availability","aria-label":'Permalink to "Checking data availability"'},"​")],-1),A=e("p",null,[e("img",{src:l,alt:"DA network"})],-1),C=e("p",null,[t("To enhance connectivity, the celestia-node augments the celestia-app with a separate libp2p network, "),e("em",null,"i.e."),t(", the so-called "),e("em",null,"DA network"),t(", that serves DAS requests.")],-1),D={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},S={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},I=s('',1),P=[I],N=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),j=e("p",null,[t("Note that although it is recommended, performing DAS is optional -- light nodes could just trust that the data corresponding to the commitments in the block headers was indeed made available by the Celestia DA layer. In addition, light nodes can also submit transactions to the celestia-app, i.e., "),e("code",null,"PayForBlobs"),t(" transactions.")],-1),B=e("p",null,"While performing DAS for a block header, every light node queries Celestia Nodes for a number of random data shares from the extended matrix and the corresponding Merkle proofs. If all the queries are successful, then the light node accepts the block header as valid (from a DA perspective).",-1),Z=e("p",null,"If at least one of the queries fails (i.e., either the data share is not received or the Merkle proof is invalid), then the light node rejects the block header and tries again later. The retrial is necessary to deal with false negatives, i.e., block headers being rejected although the block data is available. This may happen due to network congestion for example.",-1),q=e("p",null,[t("Alternatively, light nodes may accept a block header although the data is not available, i.e., a "),e("em",null,"false positive"),t(". This is possible since the soundness property (i.e., if an honest light node accepts a block as available, then at least one honest full node will eventually have the entire block data) is probabilistically guaranteed (for more details, take a look at the "),e("a",{href:"https://arxiv.org/abs/1809.09044",target:"_blank",rel:"noreferrer"},"original paper"),t(").")],-1),E=e("p",null,"By fine tuning Celestia's parameters (e.g., the number of data shares sampled by each light node) the likelihood of false positives can be sufficiently reduced such that block producers have no incentive to withhold the block data.",-1);function z(R,J,F,G,$,U){return a(),o("div",null,[c,e("p",null,[t("Next, the block producer adds to the block header a commitment of the block data. As "),d,t(", the commitment is the Merkle root of the "),e("mjx-container",h,[(a(),o("svg",T,p)),m]),t(" intermediate Merkle roots (i.e., one for each row and column of the extended matrix). To compute this commitment, the block producer performs the following operations:")]),e("ul",null,[u,e("li",null,[t("It arranges these shares into a square matrix (row-wise). Note that the shares are padded to the next power of two. The outcome square of size "),e("mjx-container",_,[(a(),o("svg",g,x)),w]),t(" is referred to as the original data.")]),e("li",null,[t("It extends the original data to a "),e("mjx-container",b,[(a(),o("svg",k,v)),L]),t(" square matrix using the 2-dimensional Reed-Solomon encoding scheme described above. The extended shares (i.e., containing erasure data) are associated with another reserved namespace.")]),H]),V,M,A,C,e("p",null,[t("Light nodes connect to a celestia-node in the DA network, listen to extended block headers (i.e., the block headers together with the relevant DA metadata, such as the "),e("mjx-container",D,[(a(),o("svg",S,P)),N]),t(" intermediate Merkle roots), and perform DAS on the received headers (i.e., ask for random data shares).")]),j,B,Z,q,E])}const X=n(r,[["render",z]]);export{K as __pageData,X as default};
+import{_ as i}from"./chunks/tx-lifecycle.e01c569f.js";import{_ as n,o as a,c as o,k as e,a as t,Q as s}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/learn/consensus-da.png",K=JSON.parse('{"title":"The lifecycle of a celestia-app transaction","description":"Learn what is the lifecycle of a celestia-app transaction.","frontmatter":{"description":"Learn what is the lifecycle of a celestia-app transaction.","head":[["meta",{"name":"og:title","content":"The lifecycle of a celestia-app transaction | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/transaction-lifecycle.md","filePath":"learn/how-celestia-works/transaction-lifecycle.md","lastUpdated":1725992025000}'),r={name:"learn/how-celestia-works/transaction-lifecycle.md"},c=s('
        The lifecycle of a celestia-app transaction ​
        Users request the celestia-app to make data available by sending PayForBlobs transactions. Every such transaction consists of the identity of the sender, the data to be made available, also referred to as the message, the data size, the namespace, and a signature. Every block producer batches multiple PayForBlobs transactions into a block.
        Before proposing the block though, the producer passes it to the state machine via ABCI++, where each PayForBlobs transaction is split into a namespaced message (denoted by Msg in the figure below), i.e., the data together with the namespace ID, and an executable transaction (denoted by e-Tx in the figure below) that does not contain the data, but only a commitment that can be used at a later time to prove that the data was indeed made available.
        Thus, the block data consists of data partitioned into namespaces and executable transactions. Note that only these transactions are executed by the Celestia state machine once the block is committed.
        Lifecycle of a celestia-app Transaction
        ',5),d=e("a",{href:"./data-availability-layer"},`described in the "Celestia's data availability layer" page`,-1),h={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},T={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},Q=s('',1),p=[Q],m=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),u=e("li",null,"It splits the executable transactions and the namespaced data into shares. Every share consists of some bytes prefixed by a namespace. To this end, the executable transactions are associated with a reserved namespace.",-1),_={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},g={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},f=s('',1),x=[f],w=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),b={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},k={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},y=s('',1),v=[y],L=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),H=e("li",null,"It computes a commitment for every row and column of the extended matrix using the NMTs described above.",-1),V=e("p",null,"Thus, the commitment of the block data is the root of a Merkle tree with the leaves the roots of a forest of Namespaced Merkle subtrees, one for every row and column of the extended matrix.",-1),M=e("h2",{id:"checking-data-availability",tabindex:"-1"},[t("Checking data availability "),e("a",{class:"header-anchor",href:"#checking-data-availability","aria-label":'Permalink to "Checking data availability"'},"​")],-1),A=e("p",null,[e("img",{src:l,alt:"DA network"})],-1),C=e("p",null,[t("To enhance connectivity, the celestia-node augments the celestia-app with a separate libp2p network, "),e("em",null,"i.e."),t(", the so-called "),e("em",null,"DA network"),t(", that serves DAS requests.")],-1),D={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},S={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},I=s('',1),P=[I],N=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),j=e("p",null,[t("Note that although it is recommended, performing DAS is optional -- light nodes could just trust that the data corresponding to the commitments in the block headers was indeed made available by the Celestia DA layer. In addition, light nodes can also submit transactions to the celestia-app, i.e., "),e("code",null,"PayForBlobs"),t(" transactions.")],-1),B=e("p",null,"While performing DAS for a block header, every light node queries Celestia Nodes for a number of random data shares from the extended matrix and the corresponding Merkle proofs. If all the queries are successful, then the light node accepts the block header as valid (from a DA perspective).",-1),Z=e("p",null,"If at least one of the queries fails (i.e., either the data share is not received or the Merkle proof is invalid), then the light node rejects the block header and tries again later. The retrial is necessary to deal with false negatives, i.e., block headers being rejected although the block data is available. This may happen due to network congestion for example.",-1),q=e("p",null,[t("Alternatively, light nodes may accept a block header although the data is not available, i.e., a "),e("em",null,"false positive"),t(". This is possible since the soundness property (i.e., if an honest light node accepts a block as available, then at least one honest full node will eventually have the entire block data) is probabilistically guaranteed (for more details, take a look at the "),e("a",{href:"https://arxiv.org/abs/1809.09044",target:"_blank",rel:"noreferrer"},"original paper"),t(").")],-1),E=e("p",null,"By fine tuning Celestia's parameters (e.g., the number of data shares sampled by each light node) the likelihood of false positives can be sufficiently reduced such that block producers have no incentive to withhold the block data.",-1);function z(R,J,F,G,$,U){return a(),o("div",null,[c,e("p",null,[t("Next, the block producer adds to the block header a commitment of the block data. As "),d,t(", the commitment is the Merkle root of the "),e("mjx-container",h,[(a(),o("svg",T,p)),m]),t(" intermediate Merkle roots (i.e., one for each row and column of the extended matrix). To compute this commitment, the block producer performs the following operations:")]),e("ul",null,[u,e("li",null,[t("It arranges these shares into a square matrix (row-wise). Note that the shares are padded to the next power of two. The outcome square of size "),e("mjx-container",_,[(a(),o("svg",g,x)),w]),t(" is referred to as the original data.")]),e("li",null,[t("It extends the original data to a "),e("mjx-container",b,[(a(),o("svg",k,v)),L]),t(" square matrix using the 2-dimensional Reed-Solomon encoding scheme described above. The extended shares (i.e., containing erasure data) are associated with another reserved namespace.")]),H]),V,M,A,C,e("p",null,[t("Light nodes connect to a celestia-node in the DA network, listen to extended block headers (i.e., the block headers together with the relevant DA metadata, such as the "),e("mjx-container",D,[(a(),o("svg",S,P)),N]),t(" intermediate Merkle roots), and perform DAS on the received headers (i.e., ask for random data shares).")]),j,B,Z,q,E])}const X=n(r,[["render",z]]);export{K as __pageData,X as default};
diff --git a/pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.d8853cb7.lean.js b/pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.def776d7.lean.js
similarity index 99%
rename from pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.d8853cb7.lean.js
rename to pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.def776d7.lean.js
index fec404fcf6..0a09633b5a 100644
--- a/pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.d8853cb7.lean.js
+++ b/pr-1699/assets/learn_how-celestia-works_transaction-lifecycle.md.def776d7.lean.js
@@ -1 +1 @@
-import{_ as i}from"./chunks/tx-lifecycle.e01c569f.js";import{_ as n,o as a,c as o,k as e,a as t,Q as s}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/learn/consensus-da.png",K=JSON.parse('{"title":"The lifecycle of a celestia-app transaction","description":"Learn what is the lifecycle of a celestia-app transaction.","frontmatter":{"description":"Learn what is the lifecycle of a celestia-app transaction.","head":[["meta",{"name":"og:title","content":"The lifecycle of a celestia-app transaction | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/transaction-lifecycle.md","filePath":"learn/how-celestia-works/transaction-lifecycle.md","lastUpdated":1725971357000}'),r={name:"learn/how-celestia-works/transaction-lifecycle.md"},c=s("",5),d=e("a",{href:"./data-availability-layer"},`described in the "Celestia's data availability layer" page`,-1),h={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},T={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},Q=s("",1),p=[Q],m=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),u=e("li",null,"It splits the executable transactions and the namespaced data into shares. Every share consists of some bytes prefixed by a namespace. To this end, the executable transactions are associated with a reserved namespace.",-1),_={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},g={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},f=s("",1),x=[f],w=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),b={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},k={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},y=s("",1),v=[y],L=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),H=e("li",null,"It computes a commitment for every row and column of the extended matrix using the NMTs described above.",-1),V=e("p",null,"Thus, the commitment of the block data is the root of a Merkle tree with the leaves the roots of a forest of Namespaced Merkle subtrees, one for every row and column of the extended matrix.",-1),M=e("h2",{id:"checking-data-availability",tabindex:"-1"},[t("Checking data availability "),e("a",{class:"header-anchor",href:"#checking-data-availability","aria-label":'Permalink to "Checking data availability"'},"​")],-1),A=e("p",null,[e("img",{src:l,alt:"DA network"})],-1),C=e("p",null,[t("To enhance connectivity, the celestia-node augments the celestia-app with a separate libp2p network, "),e("em",null,"i.e."),t(", the so-called "),e("em",null,"DA network"),t(", that serves DAS requests.")],-1),D={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},S={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},I=s("",1),P=[I],N=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),j=e("p",null,[t("Note that although it is recommended, performing DAS is optional -- light nodes could just trust that the data corresponding to the commitments in the block headers was indeed made available by the Celestia DA layer. In addition, light nodes can also submit transactions to the celestia-app, i.e., "),e("code",null,"PayForBlobs"),t(" transactions.")],-1),B=e("p",null,"While performing DAS for a block header, every light node queries Celestia Nodes for a number of random data shares from the extended matrix and the corresponding Merkle proofs. If all the queries are successful, then the light node accepts the block header as valid (from a DA perspective).",-1),Z=e("p",null,"If at least one of the queries fails (i.e., either the data share is not received or the Merkle proof is invalid), then the light node rejects the block header and tries again later. The retrial is necessary to deal with false negatives, i.e., block headers being rejected although the block data is available. This may happen due to network congestion for example.",-1),q=e("p",null,[t("Alternatively, light nodes may accept a block header although the data is not available, i.e., a "),e("em",null,"false positive"),t(". This is possible since the soundness property (i.e., if an honest light node accepts a block as available, then at least one honest full node will eventually have the entire block data) is probabilistically guaranteed (for more details, take a look at the "),e("a",{href:"https://arxiv.org/abs/1809.09044",target:"_blank",rel:"noreferrer"},"original paper"),t(").")],-1),E=e("p",null,"By fine tuning Celestia's parameters (e.g., the number of data shares sampled by each light node) the likelihood of false positives can be sufficiently reduced such that block producers have no incentive to withhold the block data.",-1);function z(R,J,F,G,$,U){return a(),o("div",null,[c,e("p",null,[t("Next, the block producer adds to the block header a commitment of the block data. As "),d,t(", the commitment is the Merkle root of the "),e("mjx-container",h,[(a(),o("svg",T,p)),m]),t(" intermediate Merkle roots (i.e., one for each row and column of the extended matrix). To compute this commitment, the block producer performs the following operations:")]),e("ul",null,[u,e("li",null,[t("It arranges these shares into a square matrix (row-wise). Note that the shares are padded to the next power of two. The outcome square of size "),e("mjx-container",_,[(a(),o("svg",g,x)),w]),t(" is referred to as the original data.")]),e("li",null,[t("It extends the original data to a "),e("mjx-container",b,[(a(),o("svg",k,v)),L]),t(" square matrix using the 2-dimensional Reed-Solomon encoding scheme described above. The extended shares (i.e., containing erasure data) are associated with another reserved namespace.")]),H]),V,M,A,C,e("p",null,[t("Light nodes connect to a celestia-node in the DA network, listen to extended block headers (i.e., the block headers together with the relevant DA metadata, such as the "),e("mjx-container",D,[(a(),o("svg",S,P)),N]),t(" intermediate Merkle roots), and perform DAS on the received headers (i.e., ask for random data shares).")]),j,B,Z,q,E])}const X=n(r,[["render",z]]);export{K as __pageData,X as default};
+import{_ as i}from"./chunks/tx-lifecycle.e01c569f.js";import{_ as n,o as a,c as o,k as e,a as t,Q as s}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/learn/consensus-da.png",K=JSON.parse('{"title":"The lifecycle of a celestia-app transaction","description":"Learn what is the lifecycle of a celestia-app transaction.","frontmatter":{"description":"Learn what is the lifecycle of a celestia-app transaction.","head":[["meta",{"name":"og:title","content":"The lifecycle of a celestia-app transaction | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-celestia-works/transaction-lifecycle.md","filePath":"learn/how-celestia-works/transaction-lifecycle.md","lastUpdated":1725992025000}'),r={name:"learn/how-celestia-works/transaction-lifecycle.md"},c=s("",5),d=e("a",{href:"./data-availability-layer"},`described in the "Celestia's data availability layer" page`,-1),h={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},T={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},Q=s("",1),p=[Q],m=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),u=e("li",null,"It splits the executable transactions and the namespaced data into shares. Every share consists of some bytes prefixed by a namespace. To this end, the executable transactions are associated with a reserved namespace.",-1),_={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},g={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"5.123ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 2264.4 705","aria-hidden":"true"},f=s("",1),x=[f],w=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mi",null,"k"),e("mo",null,"×"),e("mi",null,"k")])],-1),b={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},k={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"7.386ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 3264.4 705","aria-hidden":"true"},y=s("",1),v=[y],L=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"2"),e("mi",null,"k"),e("mo",null,"×"),e("mn",null,"2"),e("mi",null,"k")])],-1),H=e("li",null,"It computes a commitment for every row and column of the extended matrix using the NMTs described above.",-1),V=e("p",null,"Thus, the commitment of the block data is the root of a Merkle tree with the leaves the roots of a forest of Namespaced Merkle subtrees, one for every row and column of the extended matrix.",-1),M=e("h2",{id:"checking-data-availability",tabindex:"-1"},[t("Checking data availability "),e("a",{class:"header-anchor",href:"#checking-data-availability","aria-label":'Permalink to "Checking data availability"'},"​")],-1),A=e("p",null,[e("img",{src:l,alt:"DA network"})],-1),C=e("p",null,[t("To enhance connectivity, the celestia-node augments the celestia-app with a separate libp2p network, "),e("em",null,"i.e."),t(", the so-called "),e("em",null,"DA network"),t(", that serves DAS requests.")],-1),D={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},S={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.025ex"},xmlns:"http://www.w3.org/2000/svg",width:"2.31ex",height:"1.595ex",role:"img",focusable:"false",viewBox:"0 -694 1021 705","aria-hidden":"true"},I=s("",1),P=[I],N=e("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mn",null,"4"),e("mi",null,"k")])],-1),j=e("p",null,[t("Note that although it is recommended, performing DAS is optional -- light nodes could just trust that the data corresponding to the commitments in the block headers was indeed made available by the Celestia DA layer. In addition, light nodes can also submit transactions to the celestia-app, i.e., "),e("code",null,"PayForBlobs"),t(" transactions.")],-1),B=e("p",null,"While performing DAS for a block header, every light node queries Celestia Nodes for a number of random data shares from the extended matrix and the corresponding Merkle proofs. If all the queries are successful, then the light node accepts the block header as valid (from a DA perspective).",-1),Z=e("p",null,"If at least one of the queries fails (i.e., either the data share is not received or the Merkle proof is invalid), then the light node rejects the block header and tries again later. The retrial is necessary to deal with false negatives, i.e., block headers being rejected although the block data is available. This may happen due to network congestion for example.",-1),q=e("p",null,[t("Alternatively, light nodes may accept a block header although the data is not available, i.e., a "),e("em",null,"false positive"),t(". This is possible since the soundness property (i.e., if an honest light node accepts a block as available, then at least one honest full node will eventually have the entire block data) is probabilistically guaranteed (for more details, take a look at the "),e("a",{href:"https://arxiv.org/abs/1809.09044",target:"_blank",rel:"noreferrer"},"original paper"),t(").")],-1),E=e("p",null,"By fine tuning Celestia's parameters (e.g., the number of data shares sampled by each light node) the likelihood of false positives can be sufficiently reduced such that block producers have no incentive to withhold the block data.",-1);function z(R,J,F,G,$,U){return a(),o("div",null,[c,e("p",null,[t("Next, the block producer adds to the block header a commitment of the block data. As "),d,t(", the commitment is the Merkle root of the "),e("mjx-container",h,[(a(),o("svg",T,p)),m]),t(" intermediate Merkle roots (i.e., one for each row and column of the extended matrix). To compute this commitment, the block producer performs the following operations:")]),e("ul",null,[u,e("li",null,[t("It arranges these shares into a square matrix (row-wise). Note that the shares are padded to the next power of two. The outcome square of size "),e("mjx-container",_,[(a(),o("svg",g,x)),w]),t(" is referred to as the original data.")]),e("li",null,[t("It extends the original data to a "),e("mjx-container",b,[(a(),o("svg",k,v)),L]),t(" square matrix using the 2-dimensional Reed-Solomon encoding scheme described above. The extended shares (i.e., containing erasure data) are associated with another reserved namespace.")]),H]),V,M,A,C,e("p",null,[t("Light nodes connect to a celestia-node in the DA network, listen to extended block headers (i.e., the block headers together with the relevant DA metadata, such as the "),e("mjx-container",D,[(a(),o("svg",S,P)),N]),t(" intermediate Merkle roots), and perform DAS on the received headers (i.e., ask for random data shares).")]),j,B,Z,q,E])}const X=n(r,[["render",z]]);export{K as __pageData,X as default};
diff --git a/pr-1699/assets/learn_how-to-stake-tia.md.f5076e81.js b/pr-1699/assets/learn_how-to-stake-tia.md.68dbd46b.js
similarity index 99%
rename from pr-1699/assets/learn_how-to-stake-tia.md.f5076e81.js
rename to pr-1699/assets/learn_how-to-stake-tia.md.68dbd46b.js
index d437c1fb33..4ac76b6547 100644
--- a/pr-1699/assets/learn_how-to-stake-tia.md.f5076e81.js
+++ b/pr-1699/assets/learn_how-to-stake-tia.md.68dbd46b.js
@@ -1 +1 @@
-import{_ as e,o as a,c as t,Q as o}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/keplr.png",i="/docs-preview/pr-1699/img/leap.png",l="/docs-preview/pr-1699/img/gem.png",s="/docs-preview/pr-1699/img/keplr/keplr1.gif",n="/docs-preview/pr-1699/img/keplr/keplr2.gif",p="/docs-preview/pr-1699/img/keplr/keplr3.gif",c="/docs-preview/pr-1699/img/keplr/keplr4.gif",d="/docs-preview/pr-1699/img/leap/leap1.gif",h="/docs-preview/pr-1699/img/leap/leap2.gif",m="/docs-preview/pr-1699/img/leap/leap3.gif",w="/docs-preview/pr-1699/img/gem/gem1.gif",k="/docs-preview/pr-1699/img/gem/gem2.gif",u="/docs-preview/pr-1699/img/gem/gem3.gif",f="/docs-preview/pr-1699/img/gem/gem4.gif",C=JSON.parse('{"title":"How to stake TIA","description":"This tutorial covers how to stake TIA with Keplr, Leap, or Gem wallet","frontmatter":{"sidebar_label":"How to stake TIA","description":"This tutorial covers how to stake TIA with Keplr, Leap, or Gem wallet","head":[["meta",{"name":"og:title","content":"How to stake TIA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-to-stake-tia.md","filePath":"learn/how-to-stake-tia.md","lastUpdated":1725971357000}'),g={name:"learn/how-to-stake-tia.md"},_=o('
        How to stake TIA ​
        Celestia is a proof-of-stake blockchain based on the Cosmos SDK.
        Staking TIA as a delegator allows you to secure the Celestia network. This means that you can stake the native token TIA and vote on governance proposals.
        In this tutorial, you will learn how to stake TIA tokens via Keplr, Leap, and Gem wallets.
        Select your preferred wallet ​
        Keplr
        Leap
        Gem Wallet
        Stake TIA with Keplr wallet ​
        1️⃣ Open your Keplr browser extension ​
        Navigate to Staked and select Stake with Keplr Dashboard.
        This will open the Keplr dashboard in a new browser page.
        Keplr1
        2️⃣ Select Celestia network and search for a validator ​
        In the Keplr dashboard, select the Celestia network and pick a validator of your choice.
        Keplr1
        3️⃣ Stake your TIA tokens ​
        On the following screen enter amount of TIA tokens and select Stake.
        A Keplr popup will appear, requesting your approval for the transaction. Select Approve.
        Keplr1
        4️⃣ Confirm and manage your TIA ​
        After the transaction is confirmed, you will see the following overview dashboard where you can claim rewards, unstake, redelegate, or stake additional tokens.
        Keplr1
        Stake TIA with Leap wallet ​
        1️⃣ Open your Leap browser extension ​
        In top right select Celestia network and navigate to Stake.
        Similarly to previous step, select the +Stake button.
        Keplr1
        2️⃣ Select a validator and stake TIA ​
        On the following screen choose a validator of your choice, enter the desired amount, and click Review.
        Following that, review the transaction details and select Stake, then wait for the transaction to finalize.
        Keplr1
        3️⃣ Confirm and manage your TIA ​
        After the transaction is confirmed, you will see the following overview dashboard where you can claim rewards, unstake, redelegate, or stake additional tokens.
        Keplr1
        Stake TIA with Gem wallet ​
        1️⃣ Open your Gem Wallet app ​
        Navigate to Celestia and select Stake.
        Gem1
        2️⃣ Choose the amount of Celestia and search for a validator. ​
        Select the amount of Celestia tokens and choose a validator from the list.
        Gem2
        3️⃣ Stake your TIA tokens ​
        Review the network terms and commission, then press Confirm to proceed.
        Gem3
        4️⃣ Manage your TIA ​
        After your transaction is confirmed, you will have access to a control panel where you can claim rewards, unstake, redelegate, or stake additional tokens.
        Gem4
        ',48),b=[_];function v(y,T,A,I,S,q){return a(),t("div",null,b)}const K=e(g,[["render",v]]);export{C as __pageData,K as default};
+import{_ as e,o as a,c as t,Q as o}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/keplr.png",i="/docs-preview/pr-1699/img/leap.png",l="/docs-preview/pr-1699/img/gem.png",s="/docs-preview/pr-1699/img/keplr/keplr1.gif",n="/docs-preview/pr-1699/img/keplr/keplr2.gif",p="/docs-preview/pr-1699/img/keplr/keplr3.gif",c="/docs-preview/pr-1699/img/keplr/keplr4.gif",d="/docs-preview/pr-1699/img/leap/leap1.gif",h="/docs-preview/pr-1699/img/leap/leap2.gif",m="/docs-preview/pr-1699/img/leap/leap3.gif",w="/docs-preview/pr-1699/img/gem/gem1.gif",k="/docs-preview/pr-1699/img/gem/gem2.gif",u="/docs-preview/pr-1699/img/gem/gem3.gif",f="/docs-preview/pr-1699/img/gem/gem4.gif",C=JSON.parse('{"title":"How to stake TIA","description":"This tutorial covers how to stake TIA with Keplr, Leap, or Gem wallet","frontmatter":{"sidebar_label":"How to stake TIA","description":"This tutorial covers how to stake TIA with Keplr, Leap, or Gem wallet","head":[["meta",{"name":"og:title","content":"How to stake TIA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-to-stake-tia.md","filePath":"learn/how-to-stake-tia.md","lastUpdated":1725992025000}'),g={name:"learn/how-to-stake-tia.md"},_=o('
        How to stake TIA ​
        Celestia is a proof-of-stake blockchain based on the Cosmos SDK.
        Staking TIA as a delegator allows you to secure the Celestia network. This means that you can stake the native token TIA and vote on governance proposals.
        In this tutorial, you will learn how to stake TIA tokens via Keplr, Leap, and Gem wallets.
        Select your preferred wallet ​
        Keplr
        Leap
        Gem Wallet
        Stake TIA with Keplr wallet ​
        1️⃣ Open your Keplr browser extension ​
        Navigate to Staked and select Stake with Keplr Dashboard.
        This will open the Keplr dashboard in a new browser page.
        Keplr1
        2️⃣ Select Celestia network and search for a validator ​
        In the Keplr dashboard, select the Celestia network and pick a validator of your choice.
        Keplr1
        3️⃣ Stake your TIA tokens ​
        On the following screen enter amount of TIA tokens and select Stake.
        A Keplr popup will appear, requesting your approval for the transaction. Select Approve.
        Keplr1
        4️⃣ Confirm and manage your TIA ​
        After the transaction is confirmed, you will see the following overview dashboard where you can claim rewards, unstake, redelegate, or stake additional tokens.
        Keplr1
        Stake TIA with Leap wallet ​
        1️⃣ Open your Leap browser extension ​
        In top right select Celestia network and navigate to Stake.
        Similarly to previous step, select the +Stake button.
        Keplr1
        2️⃣ Select a validator and stake TIA ​
        On the following screen choose a validator of your choice, enter the desired amount, and click Review.
        Following that, review the transaction details and select Stake, then wait for the transaction to finalize.
        Keplr1
        3️⃣ Confirm and manage your TIA ​
        After the transaction is confirmed, you will see the following overview dashboard where you can claim rewards, unstake, redelegate, or stake additional tokens.
        Keplr1
        Stake TIA with Gem wallet ​
        1️⃣ Open your Gem Wallet app ​
        Navigate to Celestia and select Stake.
        Gem1
        2️⃣ Choose the amount of Celestia and search for a validator. ​
        Select the amount of Celestia tokens and choose a validator from the list.
        Gem2
        3️⃣ Stake your TIA tokens ​
        Review the network terms and commission, then press Confirm to proceed.
        Gem3
        4️⃣ Manage your TIA ​
        After your transaction is confirmed, you will have access to a control panel where you can claim rewards, unstake, redelegate, or stake additional tokens.
        Gem4
        ',48),b=[_];function v(y,T,A,I,S,q){return a(),t("div",null,b)}const K=e(g,[["render",v]]);export{C as __pageData,K as default};
diff --git a/pr-1699/assets/learn_how-to-stake-tia.md.f5076e81.lean.js b/pr-1699/assets/learn_how-to-stake-tia.md.68dbd46b.lean.js
similarity index 95%
rename from pr-1699/assets/learn_how-to-stake-tia.md.f5076e81.lean.js
rename to pr-1699/assets/learn_how-to-stake-tia.md.68dbd46b.lean.js
index 9cc6fec2c0..2651b30731 100644
--- a/pr-1699/assets/learn_how-to-stake-tia.md.f5076e81.lean.js
+++ b/pr-1699/assets/learn_how-to-stake-tia.md.68dbd46b.lean.js
@@ -1 +1 @@
-import{_ as e,o as a,c as t,Q as o}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/keplr.png",i="/docs-preview/pr-1699/img/leap.png",l="/docs-preview/pr-1699/img/gem.png",s="/docs-preview/pr-1699/img/keplr/keplr1.gif",n="/docs-preview/pr-1699/img/keplr/keplr2.gif",p="/docs-preview/pr-1699/img/keplr/keplr3.gif",c="/docs-preview/pr-1699/img/keplr/keplr4.gif",d="/docs-preview/pr-1699/img/leap/leap1.gif",h="/docs-preview/pr-1699/img/leap/leap2.gif",m="/docs-preview/pr-1699/img/leap/leap3.gif",w="/docs-preview/pr-1699/img/gem/gem1.gif",k="/docs-preview/pr-1699/img/gem/gem2.gif",u="/docs-preview/pr-1699/img/gem/gem3.gif",f="/docs-preview/pr-1699/img/gem/gem4.gif",C=JSON.parse('{"title":"How to stake TIA","description":"This tutorial covers how to stake TIA with Keplr, Leap, or Gem wallet","frontmatter":{"sidebar_label":"How to stake TIA","description":"This tutorial covers how to stake TIA with Keplr, Leap, or Gem wallet","head":[["meta",{"name":"og:title","content":"How to stake TIA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-to-stake-tia.md","filePath":"learn/how-to-stake-tia.md","lastUpdated":1725971357000}'),g={name:"learn/how-to-stake-tia.md"},_=o("",48),b=[_];function v(y,T,A,I,S,q){return a(),t("div",null,b)}const K=e(g,[["render",v]]);export{C as __pageData,K as default};
+import{_ as e,o as a,c as t,Q as o}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/keplr.png",i="/docs-preview/pr-1699/img/leap.png",l="/docs-preview/pr-1699/img/gem.png",s="/docs-preview/pr-1699/img/keplr/keplr1.gif",n="/docs-preview/pr-1699/img/keplr/keplr2.gif",p="/docs-preview/pr-1699/img/keplr/keplr3.gif",c="/docs-preview/pr-1699/img/keplr/keplr4.gif",d="/docs-preview/pr-1699/img/leap/leap1.gif",h="/docs-preview/pr-1699/img/leap/leap2.gif",m="/docs-preview/pr-1699/img/leap/leap3.gif",w="/docs-preview/pr-1699/img/gem/gem1.gif",k="/docs-preview/pr-1699/img/gem/gem2.gif",u="/docs-preview/pr-1699/img/gem/gem3.gif",f="/docs-preview/pr-1699/img/gem/gem4.gif",C=JSON.parse('{"title":"How to stake TIA","description":"This tutorial covers how to stake TIA with Keplr, Leap, or Gem wallet","frontmatter":{"sidebar_label":"How to stake TIA","description":"This tutorial covers how to stake TIA with Keplr, Leap, or Gem wallet","head":[["meta",{"name":"og:title","content":"How to stake TIA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/how-to-stake-tia.md","filePath":"learn/how-to-stake-tia.md","lastUpdated":1725992025000}'),g={name:"learn/how-to-stake-tia.md"},_=o("",48),b=[_];function v(y,T,A,I,S,q){return a(),t("div",null,b)}const K=e(g,[["render",v]]);export{C as __pageData,K as default};
diff --git a/pr-1699/assets/learn_paying-for-blobspace.md.61719f03.js b/pr-1699/assets/learn_paying-for-blobspace.md.06ae9c17.js
similarity index 97%
rename from pr-1699/assets/learn_paying-for-blobspace.md.61719f03.js
rename to pr-1699/assets/learn_paying-for-blobspace.md.06ae9c17.js
index 9fff30330a..f15baccd53 100644
--- a/pr-1699/assets/learn_paying-for-blobspace.md.61719f03.js
+++ b/pr-1699/assets/learn_paying-for-blobspace.md.06ae9c17.js
@@ -1 +1 @@
-import{_ as e}from"./chunks/tx-lifecycle.e01c569f.js";import{_ as a,o as t,c as o,Q as i}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Paying for blobspace","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Paying for blobspace | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/paying-for-blobspace.md","filePath":"learn/paying-for-blobspace.md","lastUpdated":1725971357000}'),s={name:"learn/paying-for-blobspace.md"},n=i('
        Paying for blobspace ​
        PayForBlobs transactions ​
        To publish data on Celestia, developers can submit PayForBlobs transactions. A PayForBlobs transaction consists of the identity of the sender, the data to be made available, the data size, the namespace, and a signature.
        Each PayForBlobs transaction is split into two parts: the blob or blobs which include the data to be made available along with the namespace, and the executable payment transaction which includes a commitment to the data.
        Both the blobs and executable payment transactions are put into the block within the appropriate namespace. The block data is extended using erasure coding and then Merkelized into a data root commitment included in the block header.
        Lifecycle of a celestia-app Transaction
        See the detailed life cycle of a Celestia transaction.
        Learn how to submit data to Celestia’s data availability layer.
        Fee market overview ​
        Celestia uses a standard gas-price prioritised mempool. This means that transactions with higher fees will be prioritised by validators. Fees are comprised of a flat fee per transaction and then a variable fee based on the size of each blob in the transaction.
        Understand how fees are calculated on Celestia in the overview on submitting PFB transactions.
        ',11),r=[n];function c(l,d,p,h,b,m){return t(),o("div",null,r)}const y=a(s,[["render",c]]);export{u as __pageData,y as default};
+import{_ as e}from"./chunks/tx-lifecycle.e01c569f.js";import{_ as a,o as t,c as o,Q as i}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Paying for blobspace","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Paying for blobspace | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/paying-for-blobspace.md","filePath":"learn/paying-for-blobspace.md","lastUpdated":1725992025000}'),s={name:"learn/paying-for-blobspace.md"},n=i('
        Paying for blobspace ​
        PayForBlobs transactions ​
        To publish data on Celestia, developers can submit PayForBlobs transactions. A PayForBlobs transaction consists of the identity of the sender, the data to be made available, the data size, the namespace, and a signature.
        Each PayForBlobs transaction is split into two parts: the blob or blobs which include the data to be made available along with the namespace, and the executable payment transaction which includes a commitment to the data.
        Both the blobs and executable payment transactions are put into the block within the appropriate namespace. The block data is extended using erasure coding and then Merkelized into a data root commitment included in the block header.
        Lifecycle of a celestia-app Transaction
        See the detailed life cycle of a Celestia transaction.
        Learn how to submit data to Celestia’s data availability layer.
        Fee market overview ​
        Celestia uses a standard gas-price prioritised mempool. This means that transactions with higher fees will be prioritised by validators. Fees are comprised of a flat fee per transaction and then a variable fee based on the size of each blob in the transaction.
        Understand how fees are calculated on Celestia in the overview on submitting PFB transactions.
        ',11),r=[n];function c(l,d,p,h,b,m){return t(),o("div",null,r)}const y=a(s,[["render",c]]);export{u as __pageData,y as default};
diff --git a/pr-1699/assets/learn_paying-for-blobspace.md.61719f03.lean.js b/pr-1699/assets/learn_paying-for-blobspace.md.06ae9c17.lean.js
similarity index 90%
rename from pr-1699/assets/learn_paying-for-blobspace.md.61719f03.lean.js
rename to pr-1699/assets/learn_paying-for-blobspace.md.06ae9c17.lean.js
index c96cf137fa..616e1211a6 100644
--- a/pr-1699/assets/learn_paying-for-blobspace.md.61719f03.lean.js
+++ b/pr-1699/assets/learn_paying-for-blobspace.md.06ae9c17.lean.js
@@ -1 +1 @@
-import{_ as e}from"./chunks/tx-lifecycle.e01c569f.js";import{_ as a,o as t,c as o,Q as i}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Paying for blobspace","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Paying for blobspace | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/paying-for-blobspace.md","filePath":"learn/paying-for-blobspace.md","lastUpdated":1725971357000}'),s={name:"learn/paying-for-blobspace.md"},n=i("",11),r=[n];function c(l,d,p,h,b,m){return t(),o("div",null,r)}const y=a(s,[["render",c]]);export{u as __pageData,y as default};
+import{_ as e}from"./chunks/tx-lifecycle.e01c569f.js";import{_ as a,o as t,c as o,Q as i}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Paying for blobspace","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Paying for blobspace | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/paying-for-blobspace.md","filePath":"learn/paying-for-blobspace.md","lastUpdated":1725992025000}'),s={name:"learn/paying-for-blobspace.md"},n=i("",11),r=[n];function c(l,d,p,h,b,m){return t(),o("div",null,r)}const y=a(s,[["render",c]]);export{u as __pageData,y as default};
diff --git a/pr-1699/assets/learn_retrievability.md.8931b632.js b/pr-1699/assets/learn_retrievability.md.d1e1d36b.js
similarity index 98%
rename from pr-1699/assets/learn_retrievability.md.8931b632.js
rename to pr-1699/assets/learn_retrievability.md.d1e1d36b.js
index 05816a49cd..729a16c8ec 100644
--- a/pr-1699/assets/learn_retrievability.md.8931b632.js
+++ b/pr-1699/assets/learn_retrievability.md.d1e1d36b.js
@@ -1 +1 @@
-import{_ as e,o as a,c as t,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Data retrievability and pruning","description":"Practices and expectations for data retrievability and pruning on Celestia.","frontmatter":{"sidebar_label":"Data retrievability and pruning","description":"Practices and expectations for data retrievability and pruning on Celestia.","head":[["meta",{"name":"og:title","content":"Data retrievability and pruning | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/retrievability.md","filePath":"learn/retrievability.md","lastUpdated":1725971357000}'),o={name:"learn/retrievability.md"},r=i('
        Data retrievability and pruning ​
        The purpose of data availability layers such as Celestia is to ensure that block data is provably published, so that applications and rollups can know what the state of their chain is, and store that data. Once the data is published, data availability layers do not inherently guarantee that historical data will be permanently stored and remain retrievable.
        In this document, we discuss the state of data retrievability and pruning in Celestia, as well as some tips for rollup developers in order to ensure that syncing new rollup nodes is possible.
        Data retrievability and pruning in celestia-node ​
        As of version v0.13.0, celestia-node has implemented a light node sampling window of 30 days, as specified in CIP-4. This means that once pruning is implemented, light nodes will now only sample blocks within a 30-day window instead of sampling all blocks from genesis. This change introduces the concept of pruning to celestia-node, where data outside of the 30-day window may not be stored by light nodes, marking a significant update in how data retrievability and storage are managed within the network (v0.13.0 release notes).
        Data blobs older than the recency window will be pruned by default on light nodes, after pruning is fully implemented, but will continue to be stored by archival nodes that do not prune data. Light nodes will be able to query historic blob data in namespaces from archival nodes, as long as archival nodes exist on the public network.
        Once pruning is fully implemented, light nodes will only perform data availability sampling for blocks within the data recency window of 30 days.
        Suggested practices for rollups ​
        Rollups may need to access historic data in order to allow new rollup nodes to reconstruct the latest state by replaying historic blocks. Once data has been published on Celestia and guaranteed to have been made available, rollups and applications are responsible for storing their historical data.
        While it is possible to continue to do this by using the GetAll API method in celestia-node on historic blocks as long as archival nodes exist on the public Celestia network, rollup developers should not rely on this as the only method to access historical data, as archival nodes serving requests for historical data for free is not guaranteed. Below are some other suggested methods to access historical data.
        • Use professional archival node or data providers. It is expected that professional infrastructure providers will provide paid access to archival nodes, where historical data can be retrieved, for example using the GetAll API method. This provides better guarantees than solely relying on free archival nodes on the public Celestia network.
        • Share snapshots of rollup nodes. Rollups could share snapshots of their data directories which can be downloaded manually by users bootstrapping new nodes. These snapshots could contain the latest state of the rollup, and/or all the historical blocks.
        • Add peer-to-peer support for historical block sync. A less manual version of sharing snapshots, where rollup nodes could implement built-in support for block sync, where rollup nodes download historical block data from each other over a peer-to-peer network. 
          • Namespace pinning. In the future, celestia-node is expected to allow nodes to choose to "pin" data from selected namespaces that they wish to store and make available for other nodes. This will allow rollup nodes to be responsible for storing their data, without needing to implement their own peer-to-peer historical block sync mechanism.
        ',11),s=[r];function n(l,d,c,h,p,u){return a(),t("div",null,s)}const f=e(o,[["render",n]]);export{g as __pageData,f as default};
+import{_ as e,o as a,c as t,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Data retrievability and pruning","description":"Practices and expectations for data retrievability and pruning on Celestia.","frontmatter":{"sidebar_label":"Data retrievability and pruning","description":"Practices and expectations for data retrievability and pruning on Celestia.","head":[["meta",{"name":"og:title","content":"Data retrievability and pruning | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/retrievability.md","filePath":"learn/retrievability.md","lastUpdated":1725992025000}'),o={name:"learn/retrievability.md"},r=i('
        Data retrievability and pruning ​
        The purpose of data availability layers such as Celestia is to ensure that block data is provably published, so that applications and rollups can know what the state of their chain is, and store that data. Once the data is published, data availability layers do not inherently guarantee that historical data will be permanently stored and remain retrievable.
        In this document, we discuss the state of data retrievability and pruning in Celestia, as well as some tips for rollup developers in order to ensure that syncing new rollup nodes is possible.
        Data retrievability and pruning in celestia-node ​
        As of version v0.13.0, celestia-node has implemented a light node sampling window of 30 days, as specified in CIP-4. This means that once pruning is implemented, light nodes will now only sample blocks within a 30-day window instead of sampling all blocks from genesis. This change introduces the concept of pruning to celestia-node, where data outside of the 30-day window may not be stored by light nodes, marking a significant update in how data retrievability and storage are managed within the network (v0.13.0 release notes).
        Data blobs older than the recency window will be pruned by default on light nodes, after pruning is fully implemented, but will continue to be stored by archival nodes that do not prune data. Light nodes will be able to query historic blob data in namespaces from archival nodes, as long as archival nodes exist on the public network.
        Once pruning is fully implemented, light nodes will only perform data availability sampling for blocks within the data recency window of 30 days.
        Suggested practices for rollups ​
        Rollups may need to access historic data in order to allow new rollup nodes to reconstruct the latest state by replaying historic blocks. Once data has been published on Celestia and guaranteed to have been made available, rollups and applications are responsible for storing their historical data.
        While it is possible to continue to do this by using the GetAll API method in celestia-node on historic blocks as long as archival nodes exist on the public Celestia network, rollup developers should not rely on this as the only method to access historical data, as archival nodes serving requests for historical data for free is not guaranteed. Below are some other suggested methods to access historical data.
        • Use professional archival node or data providers. It is expected that professional infrastructure providers will provide paid access to archival nodes, where historical data can be retrieved, for example using the GetAll API method. This provides better guarantees than solely relying on free archival nodes on the public Celestia network.
        • Share snapshots of rollup nodes. Rollups could share snapshots of their data directories which can be downloaded manually by users bootstrapping new nodes. These snapshots could contain the latest state of the rollup, and/or all the historical blocks.
        • Add peer-to-peer support for historical block sync. A less manual version of sharing snapshots, where rollup nodes could implement built-in support for block sync, where rollup nodes download historical block data from each other over a peer-to-peer network. 
          • Namespace pinning. In the future, celestia-node is expected to allow nodes to choose to "pin" data from selected namespaces that they wish to store and make available for other nodes. This will allow rollup nodes to be responsible for storing their data, without needing to implement their own peer-to-peer historical block sync mechanism.
        ',11),s=[r];function n(l,d,c,h,p,u){return a(),t("div",null,s)}const f=e(o,[["render",n]]);export{g as __pageData,f as default};
diff --git a/pr-1699/assets/learn_retrievability.md.8931b632.lean.js b/pr-1699/assets/learn_retrievability.md.d1e1d36b.lean.js
similarity index 92%
rename from pr-1699/assets/learn_retrievability.md.8931b632.lean.js
rename to pr-1699/assets/learn_retrievability.md.d1e1d36b.lean.js
index 4d6a1adf86..cd749ff6b7 100644
--- a/pr-1699/assets/learn_retrievability.md.8931b632.lean.js
+++ b/pr-1699/assets/learn_retrievability.md.d1e1d36b.lean.js
@@ -1 +1 @@
-import{_ as e,o as a,c as t,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Data retrievability and pruning","description":"Practices and expectations for data retrievability and pruning on Celestia.","frontmatter":{"sidebar_label":"Data retrievability and pruning","description":"Practices and expectations for data retrievability and pruning on Celestia.","head":[["meta",{"name":"og:title","content":"Data retrievability and pruning | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/retrievability.md","filePath":"learn/retrievability.md","lastUpdated":1725971357000}'),o={name:"learn/retrievability.md"},r=i("",11),s=[r];function n(l,d,c,h,p,u){return a(),t("div",null,s)}const f=e(o,[["render",n]]);export{g as __pageData,f as default};
+import{_ as e,o as a,c as t,Q as i}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Data retrievability and pruning","description":"Practices and expectations for data retrievability and pruning on Celestia.","frontmatter":{"sidebar_label":"Data retrievability and pruning","description":"Practices and expectations for data retrievability and pruning on Celestia.","head":[["meta",{"name":"og:title","content":"Data retrievability and pruning | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/retrievability.md","filePath":"learn/retrievability.md","lastUpdated":1725992025000}'),o={name:"learn/retrievability.md"},r=i("",11),s=[r];function n(l,d,c,h,p,u){return a(),t("div",null,s)}const f=e(o,[["render",n]]);export{g as __pageData,f as default};
diff --git a/pr-1699/assets/learn_staking-governance-supply.md.2093ea4e.js b/pr-1699/assets/learn_staking-governance-supply.md.0d21fda6.js
similarity index 99%
rename from pr-1699/assets/learn_staking-governance-supply.md.2093ea4e.js
rename to pr-1699/assets/learn_staking-governance-supply.md.0d21fda6.js
index 5e1384ec73..0a43afde4e 100644
--- a/pr-1699/assets/learn_staking-governance-supply.md.2093ea4e.js
+++ b/pr-1699/assets/learn_staking-governance-supply.md.0d21fda6.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/learn/Celestia_TIA_Inflation.png",n="/docs-preview/pr-1699/img/learn/Celestia_TIA_Allocation_at_Genesis.png",s="/docs-preview/pr-1699/img/learn/Celestia_TIA_Available_Supply.png",k=JSON.parse('{"title":"Staking, governance, & supply","description":"Learn about proof-of-stake on Celestia","frontmatter":{"description":"Learn about proof-of-stake on Celestia","head":[["meta",{"name":"og:title","content":"Staking, governance, & supply | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/staking-governance-supply.md","filePath":"learn/staking-governance-supply.md","lastUpdated":1725971357000}'),i={name:"learn/staking-governance-supply.md"},l=o('
        Staking, governance, & supply ​
        Proof-of-stake on Celestia ​
        Celestia is a proof-of-stake blockchain based on CometBFT and the Cosmos SDK. Celestia supports in-protocol delegation and will start with an initial validator set of 100.
        Staking TIA as a validator or delegator enables you to earn staking rewards from the network. Validators charge a fee to delegators which gives them a percentage of staking rewards.
        Learn how proof of stake works on Cosmos SDK chains like Celestia.
        Consensus mechanismProof-of-stake
        Blockchain frameworkCosmos SDK
        Validator set size100
        Delegation supportYes
        Learn how to stake on your own at the community dashboards.
        Inflation ​
        TIA inflation starts at 8% annually and decreases by 10% every year until it reaches the long term issuance rate of 1.5%. Exact annual inflation rates can be found in the diagram below.
        inflation diagram
        The annual provisions for inflation are calculated based on the total supply of TIA at the beginning of each year. To calculate how many TIA to issue per block, Celestia uses the block timestamp rather than the block height since the time between blocks can vary and cause actual issuance to be higher than the target.
        For an in-depth understanding, refer to ADR019.
        Decentralised governance ​
        Network parameters ​
        TIA holders (not just stakers) can propose and vote on governance proposals to change a subset of network parameters. To learn more, see a complete list of both the changeable and non-changeable parameters and their values. Additionally, learn how to submit and vote on governance proposals.
        Community pool ​
        Starting at genesis, Celestia’s community pool receives 2% of all Celestia block rewards. TIA stakers may vote to fund ecosystem initiatives as in many other Cosmos SDK chains.
        Learn how to submit a governance proposal to spend community pool funds.
        TIA allocation at genesis ​
        Celestia will have a total supply of 1,000,000,000 TIA at genesis, split across five categories described in the chart and table below.
        allocation diagram
        CategoryDescription%
        Public AllocationGenesis Drop and Incentivized Testnet: 7.41%
        Future initiatives: 12.59%        		20.00%
        R&D & EcosystemTokens allocated to the Celestia Foundation and core devs for research, development, and ecosystem initiatives including:
        - Protocol maintenance and development
        - Programs for rollup developers, infrastructure, and node operators        		26.79%
        Early Backers: Series A&BEarly supporters of Celestia19.67%
        Early Backers: SeedEarly supporters of Celestia15.90%
        Initial Core ContributorsMembers of Celestia Labs, the first core contributor to Celestia17.64%
        Unlocks ​
        Celestia’s 1 billion TIA supply at genesis will be subject to several different unlock schedules. All tokens, locked or unlocked, may be staked, but staking rewards are unlocked upon receipt and will add to the circulating supply.
        Circulating supply is defined as the amount of TIA tokens in general circulation without onchain transfer restrictions.
        Available supply is defined as the amount of TIA tokens that are either part of the circulating supply or are unlocked but subject to some form of governance to determine when the tokens are allocated. This includes the unlocked portion of the R&D & Ecosystem tokens and the tokens set aside for future initiatives.
        The definitions for circulating and available supply were adapted from Optimism’s definitions.
        supply diagram
        Unlock schedule by category is described in the table below.
        CategoryUnlock Schedule
        Public AllocationFully unlocked at launch.
        R&D & Ecosystem25.00% unlocked at launch.
        Remaining 75.00% unlocks continuously from year 1 to year 4.
        Initial Core Contributors33.33% unlocked at year 1.
        Remaining 66.67% unlocks continuously from year 1 to year 3.
        Early Backers: Seed33.33% unlocked at year 1.
        Remaining 66.67% unlocks continuously from year 1 to year 2.
        Early Backers: Series A&B33.33% unlocked at year 1.
        Remaining 66.67% unlocks continuously from year 1 to year 2.
        ',30),d=[l];function c(p,h,u,m,f,g){return t(),a("div",null,d)}const y=e(i,[["render",c]]);export{k as __pageData,y as default};
+import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/learn/Celestia_TIA_Inflation.png",n="/docs-preview/pr-1699/img/learn/Celestia_TIA_Allocation_at_Genesis.png",s="/docs-preview/pr-1699/img/learn/Celestia_TIA_Available_Supply.png",k=JSON.parse('{"title":"Staking, governance, & supply","description":"Learn about proof-of-stake on Celestia","frontmatter":{"description":"Learn about proof-of-stake on Celestia","head":[["meta",{"name":"og:title","content":"Staking, governance, & supply | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/staking-governance-supply.md","filePath":"learn/staking-governance-supply.md","lastUpdated":1725992025000}'),i={name:"learn/staking-governance-supply.md"},l=o('
        Staking, governance, & supply ​
        Proof-of-stake on Celestia ​
        Celestia is a proof-of-stake blockchain based on CometBFT and the Cosmos SDK. Celestia supports in-protocol delegation and will start with an initial validator set of 100.
        Staking TIA as a validator or delegator enables you to earn staking rewards from the network. Validators charge a fee to delegators which gives them a percentage of staking rewards.
        Learn how proof of stake works on Cosmos SDK chains like Celestia.
        Consensus mechanismProof-of-stake
        Blockchain frameworkCosmos SDK
        Validator set size100
        Delegation supportYes
        Learn how to stake on your own at the community dashboards.
        Inflation ​
        TIA inflation starts at 8% annually and decreases by 10% every year until it reaches the long term issuance rate of 1.5%. Exact annual inflation rates can be found in the diagram below.
        inflation diagram
        The annual provisions for inflation are calculated based on the total supply of TIA at the beginning of each year. To calculate how many TIA to issue per block, Celestia uses the block timestamp rather than the block height since the time between blocks can vary and cause actual issuance to be higher than the target.
        For an in-depth understanding, refer to ADR019.
        Decentralised governance ​
        Network parameters ​
        TIA holders (not just stakers) can propose and vote on governance proposals to change a subset of network parameters. To learn more, see a complete list of both the changeable and non-changeable parameters and their values. Additionally, learn how to submit and vote on governance proposals.
        Community pool ​
        Starting at genesis, Celestia’s community pool receives 2% of all Celestia block rewards. TIA stakers may vote to fund ecosystem initiatives as in many other Cosmos SDK chains.
        Learn how to submit a governance proposal to spend community pool funds.
        TIA allocation at genesis ​
        Celestia will have a total supply of 1,000,000,000 TIA at genesis, split across five categories described in the chart and table below.
        allocation diagram
        CategoryDescription%
        Public AllocationGenesis Drop and Incentivized Testnet: 7.41%
        Future initiatives: 12.59%        		20.00%
        R&D & EcosystemTokens allocated to the Celestia Foundation and core devs for research, development, and ecosystem initiatives including:
        - Protocol maintenance and development
        - Programs for rollup developers, infrastructure, and node operators        		26.79%
        Early Backers: Series A&BEarly supporters of Celestia19.67%
        Early Backers: SeedEarly supporters of Celestia15.90%
        Initial Core ContributorsMembers of Celestia Labs, the first core contributor to Celestia17.64%
        Unlocks ​
        Celestia’s 1 billion TIA supply at genesis will be subject to several different unlock schedules. All tokens, locked or unlocked, may be staked, but staking rewards are unlocked upon receipt and will add to the circulating supply.
        Circulating supply is defined as the amount of TIA tokens in general circulation without onchain transfer restrictions.
        Available supply is defined as the amount of TIA tokens that are either part of the circulating supply or are unlocked but subject to some form of governance to determine when the tokens are allocated. This includes the unlocked portion of the R&D & Ecosystem tokens and the tokens set aside for future initiatives.
        The definitions for circulating and available supply were adapted from Optimism’s definitions.
        supply diagram
        Unlock schedule by category is described in the table below.
        CategoryUnlock Schedule
        Public AllocationFully unlocked at launch.
        R&D & Ecosystem25.00% unlocked at launch.
        Remaining 75.00% unlocks continuously from year 1 to year 4.
        Initial Core Contributors33.33% unlocked at year 1.
        Remaining 66.67% unlocks continuously from year 1 to year 3.
        Early Backers: Seed33.33% unlocked at year 1.
        Remaining 66.67% unlocks continuously from year 1 to year 2.
        Early Backers: Series A&B33.33% unlocked at year 1.
        Remaining 66.67% unlocks continuously from year 1 to year 2.
        ',30),d=[l];function c(p,h,u,m,f,g){return t(),a("div",null,d)}const y=e(i,[["render",c]]);export{k as __pageData,y as default};
diff --git a/pr-1699/assets/learn_staking-governance-supply.md.2093ea4e.lean.js b/pr-1699/assets/learn_staking-governance-supply.md.0d21fda6.lean.js
similarity index 93%
rename from pr-1699/assets/learn_staking-governance-supply.md.2093ea4e.lean.js
rename to pr-1699/assets/learn_staking-governance-supply.md.0d21fda6.lean.js
index 7e70192061..bdf9b287bf 100644
--- a/pr-1699/assets/learn_staking-governance-supply.md.2093ea4e.lean.js
+++ b/pr-1699/assets/learn_staking-governance-supply.md.0d21fda6.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/learn/Celestia_TIA_Inflation.png",n="/docs-preview/pr-1699/img/learn/Celestia_TIA_Allocation_at_Genesis.png",s="/docs-preview/pr-1699/img/learn/Celestia_TIA_Available_Supply.png",k=JSON.parse('{"title":"Staking, governance, & supply","description":"Learn about proof-of-stake on Celestia","frontmatter":{"description":"Learn about proof-of-stake on Celestia","head":[["meta",{"name":"og:title","content":"Staking, governance, & supply | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/staking-governance-supply.md","filePath":"learn/staking-governance-supply.md","lastUpdated":1725971357000}'),i={name:"learn/staking-governance-supply.md"},l=o("",30),d=[l];function c(p,h,u,m,f,g){return t(),a("div",null,d)}const y=e(i,[["render",c]]);export{k as __pageData,y as default};
+import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const r="/docs-preview/pr-1699/img/learn/Celestia_TIA_Inflation.png",n="/docs-preview/pr-1699/img/learn/Celestia_TIA_Allocation_at_Genesis.png",s="/docs-preview/pr-1699/img/learn/Celestia_TIA_Available_Supply.png",k=JSON.parse('{"title":"Staking, governance, & supply","description":"Learn about proof-of-stake on Celestia","frontmatter":{"description":"Learn about proof-of-stake on Celestia","head":[["meta",{"name":"og:title","content":"Staking, governance, & supply | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/staking-governance-supply.md","filePath":"learn/staking-governance-supply.md","lastUpdated":1725992025000}'),i={name:"learn/staking-governance-supply.md"},l=o("",30),d=[l];function c(p,h,u,m,f,g){return t(),a("div",null,d)}const y=e(i,[["render",c]]);export{k as __pageData,y as default};
diff --git a/pr-1699/assets/learn_staking.md.9713419c.js b/pr-1699/assets/learn_staking.md.f13c2e81.js
similarity index 97%
rename from pr-1699/assets/learn_staking.md.9713419c.js
rename to pr-1699/assets/learn_staking.md.f13c2e81.js
index f60bcae4c2..6007896eb2 100644
--- a/pr-1699/assets/learn_staking.md.9713419c.js
+++ b/pr-1699/assets/learn_staking.md.f13c2e81.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as n}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Staking on Celestia","description":"Learn how to stake your tokens on the Celestia network.","frontmatter":{"description":"Learn how to stake your tokens on the Celestia network.","head":[["meta",{"name":"og:title","content":"Staking on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/staking.md","filePath":"learn/staking.md","lastUpdated":1725971357000}'),s={name:"learn/staking.md"},r=n('
        Staking on Celestia ​
        Engage with the Celestia network at a deeper level through staking. An essential mechanism to a proof-of-stake network, users can secure the network by delegating to a validator and receive a share of its staking rewards.
        Mainnet Beta ​
        Currently, the following staking interfaces exist for the Mainnet Beta.
        Just connect your wallet to get started!
        Mocha testnet ​
        Currently, the following staking interfaces exist for the Mocha testnet.
        Just connect your wallet to get started!
        ',10),l=[r];function i(o,h,c,p,k,d){return t(),a("div",null,l)}const m=e(s,[["render",i]]);export{g as __pageData,m as default};
+import{_ as e,o as t,c as a,Q as n}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Staking on Celestia","description":"Learn how to stake your tokens on the Celestia network.","frontmatter":{"description":"Learn how to stake your tokens on the Celestia network.","head":[["meta",{"name":"og:title","content":"Staking on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/staking.md","filePath":"learn/staking.md","lastUpdated":1725992025000}'),s={name:"learn/staking.md"},r=n('
        Staking on Celestia ​
        Engage with the Celestia network at a deeper level through staking. An essential mechanism to a proof-of-stake network, users can secure the network by delegating to a validator and receive a share of its staking rewards.
        Mainnet Beta ​
        Currently, the following staking interfaces exist for the Mainnet Beta.
        Just connect your wallet to get started!
        Mocha testnet ​
        Currently, the following staking interfaces exist for the Mocha testnet.
        Just connect your wallet to get started!
        ',10),l=[r];function i(o,h,c,p,k,d){return t(),a("div",null,l)}const m=e(s,[["render",i]]);export{g as __pageData,m as default};
diff --git a/pr-1699/assets/learn_staking.md.9713419c.lean.js b/pr-1699/assets/learn_staking.md.f13c2e81.lean.js
similarity index 90%
rename from pr-1699/assets/learn_staking.md.9713419c.lean.js
rename to pr-1699/assets/learn_staking.md.f13c2e81.lean.js
index b2934f94af..6758ac48f8 100644
--- a/pr-1699/assets/learn_staking.md.9713419c.lean.js
+++ b/pr-1699/assets/learn_staking.md.f13c2e81.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as n}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Staking on Celestia","description":"Learn how to stake your tokens on the Celestia network.","frontmatter":{"description":"Learn how to stake your tokens on the Celestia network.","head":[["meta",{"name":"og:title","content":"Staking on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/staking.md","filePath":"learn/staking.md","lastUpdated":1725971357000}'),s={name:"learn/staking.md"},r=n("",10),l=[r];function i(o,h,c,p,k,d){return t(),a("div",null,l)}const m=e(s,[["render",i]]);export{g as __pageData,m as default};
+import{_ as e,o as t,c as a,Q as n}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Staking on Celestia","description":"Learn how to stake your tokens on the Celestia network.","frontmatter":{"description":"Learn how to stake your tokens on the Celestia network.","head":[["meta",{"name":"og:title","content":"Staking on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/staking.md","filePath":"learn/staking.md","lastUpdated":1725992025000}'),s={name:"learn/staking.md"},r=n("",10),l=[r];function i(o,h,c,p,k,d){return t(),a("div",null,l)}const m=e(s,[["render",i]]);export{g as __pageData,m as default};
diff --git a/pr-1699/assets/learn_tia.md.6fd97b1e.js b/pr-1699/assets/learn_tia.md.9065ce93.js
similarity index 99%
rename from pr-1699/assets/learn_tia.md.6fd97b1e.js
rename to pr-1699/assets/learn_tia.md.9065ce93.js
index ea03972e16..f07bc31e11 100644
--- a/pr-1699/assets/learn_tia.md.6fd97b1e.js
+++ b/pr-1699/assets/learn_tia.md.9065ce93.js
@@ -1 +1 @@
-import{_ as s,o as t,c as e,k as a,a as o,Q as n}from"./chunks/framework.b47e54aa.js";const A=JSON.parse('{"title":"Overview of TIA","description":"","frontmatter":{"prev":{"text":"Data availability FAQ","link":"/learn/how-celestia-works/data-availability-faq"},"head":[["meta",{"name":"og:title","content":"Overview of TIA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/tia.md","filePath":"learn/tia.md","lastUpdated":1725971357000}'),i={name:"learn/tia.md"},r=a("h1",{id:"overview-of-tia",tabindex:"-1"},[o("Overview of TIA "),a("a",{class:"header-anchor",href:"#overview-of-tia","aria-label":'Permalink to "Overview of TIA"'},"​")],-1),l=a("h2",{id:"tia-at-a-glance",tabindex:"-1"},[o("TIA at a glance "),a("a",{class:"header-anchor",href:"#tia-at-a-glance","aria-label":'Permalink to "TIA at a glance"'},"​")],-1),d=a("thead",null,[a("tr",null,[a("th",null,"Property"),a("th",null,"Details")])],-1),c=a("tr",null,[a("td",null,"Abbreviation"),a("td",null,"TIA")],-1),h=a("tr",null,[a("td",null,"Total supply at genesis"),a("td",null,"1,000,000,000 TIA")],-1),Q=a("tr",null,[a("td",null,"Inflation schedule"),a("td",null,"8% in the first year, decreasing 10% per year until reaching an inflation floor of 1.5% annually")],-1),p=a("tr",null,[a("td",null,"Decimals"),a("td",null,"6")],-1),T=a("td",null,"Conversion",-1),m={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},u={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.186ex"},xmlns:"http://www.w3.org/2000/svg",width:"21.526ex",height:"2.14ex",role:"img",focusable:"false",viewBox:"0 -864 9514.7 946","aria-hidden":"true"},f=n('',1),g=[f],H=a("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[a("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[a("mtext",null,"1 uTIA"),a("mo",null,"="),a("mtext",null,"TIA"),a("mo",null,"×"),a("msup",null,[a("mn",null,"10"),a("mrow",{"data-mjx-texclass":"ORD"},[a("mo",null,"−"),a("mn",null,"6")])])])],-1),k=n('
        Role of TIA ​
        Paying for blobspace ​
        Celestia’s native asset, TIA, is an essential part of how developers build on the first modular blockchain network. To use Celestia for data availability, rollup developers submit PayForBlobs transactions on the network for a fee, denominated in TIA.
        Bootstrapping new rollups ​
        A core part of the Celestia vision is that deploying a blockchain should be as easy as deploying a smart contract. In the modular era, developers no longer need to issue a token to launch their own blockchain.
        Similarly to ETH on Ethereum-based rollups, developers may opt to bootstrap their chain quickly by using TIA as a gas token and currency, in addition to paying for data availability. In this mode, developers can focus on creating their application or execution layer, instead of issuing a token right away.
        Proof-of-stake ​
        As a permissionless network built with Cosmos SDK, Celestia uses proof-of-stake to secure its own consensus. Like in other Cosmos networks, any user can help secure the network by delegating their TIA to a Celestia validator for a portion of their validator’s staking rewards.
        Learn how proof-of-stake works in Cosmos.
        Decentralised governance ​
        TIA staking also allows the community to play a critical role in decentralised governance over key parts of Celestia, such as voting on network parameters through governance proposals, and governing the community pool, which receives 2% of block rewards.
        Learn more about Celestia’s decentralised governance model.
        Denominations ​
        TIA: display token ​
        TIA is the DisplayDenom that you will typically see in wallets and user interfaces.
        utia: staking denomination ​
        utia is the BondDenom and stands for "micro TIA", with 1 TIA = 1,000,000 utia. This is the native staking denomination.
        In staking operations or transactions, if no denomination is specified, utia is assumed.
        microtia: staking denomination alias ​
        microtia is the BondDenomAlias, an alias for utia.
        ',20);function b(_,w,V,y,v,x){return t(),e("div",null,[r,l,a("table",null,[d,a("tbody",null,[c,h,Q,p,a("tr",null,[T,a("td",null,[a("mjx-container",m,[(t(),e("svg",u,g)),H])])])])]),k])}const I=s(i,[["render",b]]);export{A as __pageData,I as default};
+import{_ as s,o as t,c as e,k as a,a as o,Q as n}from"./chunks/framework.b47e54aa.js";const A=JSON.parse('{"title":"Overview of TIA","description":"","frontmatter":{"prev":{"text":"Data availability FAQ","link":"/learn/how-celestia-works/data-availability-faq"},"head":[["meta",{"name":"og:title","content":"Overview of TIA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/tia.md","filePath":"learn/tia.md","lastUpdated":1725992025000}'),i={name:"learn/tia.md"},r=a("h1",{id:"overview-of-tia",tabindex:"-1"},[o("Overview of TIA "),a("a",{class:"header-anchor",href:"#overview-of-tia","aria-label":'Permalink to "Overview of TIA"'},"​")],-1),l=a("h2",{id:"tia-at-a-glance",tabindex:"-1"},[o("TIA at a glance "),a("a",{class:"header-anchor",href:"#tia-at-a-glance","aria-label":'Permalink to "TIA at a glance"'},"​")],-1),d=a("thead",null,[a("tr",null,[a("th",null,"Property"),a("th",null,"Details")])],-1),c=a("tr",null,[a("td",null,"Abbreviation"),a("td",null,"TIA")],-1),h=a("tr",null,[a("td",null,"Total supply at genesis"),a("td",null,"1,000,000,000 TIA")],-1),Q=a("tr",null,[a("td",null,"Inflation schedule"),a("td",null,"8% in the first year, decreasing 10% per year until reaching an inflation floor of 1.5% annually")],-1),p=a("tr",null,[a("td",null,"Decimals"),a("td",null,"6")],-1),T=a("td",null,"Conversion",-1),m={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},u={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.186ex"},xmlns:"http://www.w3.org/2000/svg",width:"21.526ex",height:"2.14ex",role:"img",focusable:"false",viewBox:"0 -864 9514.7 946","aria-hidden":"true"},f=n('',1),g=[f],H=a("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[a("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[a("mtext",null,"1 uTIA"),a("mo",null,"="),a("mtext",null,"TIA"),a("mo",null,"×"),a("msup",null,[a("mn",null,"10"),a("mrow",{"data-mjx-texclass":"ORD"},[a("mo",null,"−"),a("mn",null,"6")])])])],-1),k=n('
        Role of TIA ​
        Paying for blobspace ​
        Celestia’s native asset, TIA, is an essential part of how developers build on the first modular blockchain network. To use Celestia for data availability, rollup developers submit PayForBlobs transactions on the network for a fee, denominated in TIA.
        Bootstrapping new rollups ​
        A core part of the Celestia vision is that deploying a blockchain should be as easy as deploying a smart contract. In the modular era, developers no longer need to issue a token to launch their own blockchain.
        Similarly to ETH on Ethereum-based rollups, developers may opt to bootstrap their chain quickly by using TIA as a gas token and currency, in addition to paying for data availability. In this mode, developers can focus on creating their application or execution layer, instead of issuing a token right away.
        Proof-of-stake ​
        As a permissionless network built with Cosmos SDK, Celestia uses proof-of-stake to secure its own consensus. Like in other Cosmos networks, any user can help secure the network by delegating their TIA to a Celestia validator for a portion of their validator’s staking rewards.
        Learn how proof-of-stake works in Cosmos.
        Decentralised governance ​
        TIA staking also allows the community to play a critical role in decentralised governance over key parts of Celestia, such as voting on network parameters through governance proposals, and governing the community pool, which receives 2% of block rewards.
        Learn more about Celestia’s decentralised governance model.
        Denominations ​
        TIA: display token ​
        TIA is the DisplayDenom that you will typically see in wallets and user interfaces.
        utia: staking denomination ​
        utia is the BondDenom and stands for "micro TIA", with 1 TIA = 1,000,000 utia. This is the native staking denomination.
        In staking operations or transactions, if no denomination is specified, utia is assumed.
        microtia: staking denomination alias ​
        microtia is the BondDenomAlias, an alias for utia.
        ',20);function b(_,w,V,y,v,x){return t(),e("div",null,[r,l,a("table",null,[d,a("tbody",null,[c,h,Q,p,a("tr",null,[T,a("td",null,[a("mjx-container",m,[(t(),e("svg",u,g)),H])])])])]),k])}const I=s(i,[["render",b]]);export{A as __pageData,I as default};
diff --git a/pr-1699/assets/learn_tia.md.6fd97b1e.lean.js b/pr-1699/assets/learn_tia.md.9065ce93.lean.js
similarity index 97%
rename from pr-1699/assets/learn_tia.md.6fd97b1e.lean.js
rename to pr-1699/assets/learn_tia.md.9065ce93.lean.js
index 81f7f651ff..34b64690f9 100644
--- a/pr-1699/assets/learn_tia.md.6fd97b1e.lean.js
+++ b/pr-1699/assets/learn_tia.md.9065ce93.lean.js
@@ -1 +1 @@
-import{_ as s,o as t,c as e,k as a,a as o,Q as n}from"./chunks/framework.b47e54aa.js";const A=JSON.parse('{"title":"Overview of TIA","description":"","frontmatter":{"prev":{"text":"Data availability FAQ","link":"/learn/how-celestia-works/data-availability-faq"},"head":[["meta",{"name":"og:title","content":"Overview of TIA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/tia.md","filePath":"learn/tia.md","lastUpdated":1725971357000}'),i={name:"learn/tia.md"},r=a("h1",{id:"overview-of-tia",tabindex:"-1"},[o("Overview of TIA "),a("a",{class:"header-anchor",href:"#overview-of-tia","aria-label":'Permalink to "Overview of TIA"'},"​")],-1),l=a("h2",{id:"tia-at-a-glance",tabindex:"-1"},[o("TIA at a glance "),a("a",{class:"header-anchor",href:"#tia-at-a-glance","aria-label":'Permalink to "TIA at a glance"'},"​")],-1),d=a("thead",null,[a("tr",null,[a("th",null,"Property"),a("th",null,"Details")])],-1),c=a("tr",null,[a("td",null,"Abbreviation"),a("td",null,"TIA")],-1),h=a("tr",null,[a("td",null,"Total supply at genesis"),a("td",null,"1,000,000,000 TIA")],-1),Q=a("tr",null,[a("td",null,"Inflation schedule"),a("td",null,"8% in the first year, decreasing 10% per year until reaching an inflation floor of 1.5% annually")],-1),p=a("tr",null,[a("td",null,"Decimals"),a("td",null,"6")],-1),T=a("td",null,"Conversion",-1),m={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},u={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.186ex"},xmlns:"http://www.w3.org/2000/svg",width:"21.526ex",height:"2.14ex",role:"img",focusable:"false",viewBox:"0 -864 9514.7 946","aria-hidden":"true"},f=n("",1),g=[f],H=a("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[a("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[a("mtext",null,"1 uTIA"),a("mo",null,"="),a("mtext",null,"TIA"),a("mo",null,"×"),a("msup",null,[a("mn",null,"10"),a("mrow",{"data-mjx-texclass":"ORD"},[a("mo",null,"−"),a("mn",null,"6")])])])],-1),k=n("",20);function b(_,w,V,y,v,x){return t(),e("div",null,[r,l,a("table",null,[d,a("tbody",null,[c,h,Q,p,a("tr",null,[T,a("td",null,[a("mjx-container",m,[(t(),e("svg",u,g)),H])])])])]),k])}const I=s(i,[["render",b]]);export{A as __pageData,I as default};
+import{_ as s,o as t,c as e,k as a,a as o,Q as n}from"./chunks/framework.b47e54aa.js";const A=JSON.parse('{"title":"Overview of TIA","description":"","frontmatter":{"prev":{"text":"Data availability FAQ","link":"/learn/how-celestia-works/data-availability-faq"},"head":[["meta",{"name":"og:title","content":"Overview of TIA | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"learn/tia.md","filePath":"learn/tia.md","lastUpdated":1725992025000}'),i={name:"learn/tia.md"},r=a("h1",{id:"overview-of-tia",tabindex:"-1"},[o("Overview of TIA "),a("a",{class:"header-anchor",href:"#overview-of-tia","aria-label":'Permalink to "Overview of TIA"'},"​")],-1),l=a("h2",{id:"tia-at-a-glance",tabindex:"-1"},[o("TIA at a glance "),a("a",{class:"header-anchor",href:"#tia-at-a-glance","aria-label":'Permalink to "TIA at a glance"'},"​")],-1),d=a("thead",null,[a("tr",null,[a("th",null,"Property"),a("th",null,"Details")])],-1),c=a("tr",null,[a("td",null,"Abbreviation"),a("td",null,"TIA")],-1),h=a("tr",null,[a("td",null,"Total supply at genesis"),a("td",null,"1,000,000,000 TIA")],-1),Q=a("tr",null,[a("td",null,"Inflation schedule"),a("td",null,"8% in the first year, decreasing 10% per year until reaching an inflation floor of 1.5% annually")],-1),p=a("tr",null,[a("td",null,"Decimals"),a("td",null,"6")],-1),T=a("td",null,"Conversion",-1),m={class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},u={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.186ex"},xmlns:"http://www.w3.org/2000/svg",width:"21.526ex",height:"2.14ex",role:"img",focusable:"false",viewBox:"0 -864 9514.7 946","aria-hidden":"true"},f=n("",1),g=[f],H=a("mjx-assistive-mml",{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},[a("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[a("mtext",null,"1 uTIA"),a("mo",null,"="),a("mtext",null,"TIA"),a("mo",null,"×"),a("msup",null,[a("mn",null,"10"),a("mrow",{"data-mjx-texclass":"ORD"},[a("mo",null,"−"),a("mn",null,"6")])])])],-1),k=n("",20);function b(_,w,V,y,v,x){return t(),e("div",null,[r,l,a("table",null,[d,a("tbody",null,[c,h,Q,p,a("tr",null,[T,a("td",null,[a("mjx-container",m,[(t(),e("svg",u,g)),H])])])])]),k])}const I=s(i,[["render",b]]);export{A as __pageData,I as default};
diff --git a/pr-1699/assets/nodes_arabica-devnet.md.960dc284.js b/pr-1699/assets/nodes_arabica-devnet.md.5fbea086.js
similarity index 99%
rename from pr-1699/assets/nodes_arabica-devnet.md.960dc284.js
rename to pr-1699/assets/nodes_arabica-devnet.md.5fbea086.js
index 278153a201..d21512b706 100644
--- a/pr-1699/assets/nodes_arabica-devnet.md.960dc284.js
+++ b/pr-1699/assets/nodes_arabica-devnet.md.5fbea086.js
@@ -1,3 +1,3 @@
 import{A as d}from"./chunks/ArabicaVersionTags.5d1acc99.js";import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as h,o,c as r,k as e,t as a,H as s,Q as n,a as u}from"./chunks/framework.b47e54aa.js";import"./chunks/arabica_versions.1930378b.js";const b="/docs-preview/pr-1699/img/arabica-devnet.png",g={name:"ArabicaDevnetDetails",data(){return{constants:p}}},y=e("tr",null,[e("th",null,"Detail"),e("th",null,"Value")],-1),f=e("td",null,"Chain ID",-1),m=e("tr",null,[e("td",null,"Genesis hash"),e("td",null,[e("code",null,"27122593765E07329BC348E8D16E92DCB4C75B34CCCB35C640FD7A4484D4C711")])],-1),E=e("td",null,"Genesis file",-1),v=["href"],k=e("td",null,"Peers file",-1),w=["href"],_=e("tr",null,[e("td",null,"Validators"),e("td",null," 4 ")],-1);function C(l,i,c,q,t,x){return o(),r("table",null,[y,e("tr",null,[f,e("td",null,[e("code",null,a(t.constants.arabicaChainId),1)])]),m,e("tr",null,[E,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.arabicaChainId}/genesis.json`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+a(t.constants.arabicaChainId)+"/genesis.json ",9,v)])]),e("tr",null,[k,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.arabicaChainId}/peers.txt`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+a(t.constants.arabicaChainId)+"/peers.txt ",9,w)])]),_])}const A=h(g,[["render",C]]),D=n('
        Arabica devnet ​
        arabica-devnet
        Arabica devnet is a testnet from Celestia Labs that is focused exclusively on providing developers with enhanced performance and the latest upgrades for testing their rollups and applications.
        Arabica does not focus on validator or consensus-level testing, rather, that is what Mocha testnet is used for. If you are a validator, we recommend testing your validator operations on the Mocha testnet.
        Network stability and upgrades ​
        Arabica has the latest updates from all Celestia's products deployed on it, it can be subject to many changes. Therefore, as a fair warning, Arabica can break unexpectedly, but given it will be continuously updated, it is a useful way to keep testing the latest changes in the software.
        Developers can still deploy on Mocha testnet their sovereign rollups if they chose to do so, it just will always lag behind Arabica devnet until Mocha undergoes Hardfork Upgrades in coordination with Validators.
        Network details ​
        ',8),F=e("h3",{id:"software-version-numbers",tabindex:"-1"},[u("Software version numbers "),e("a",{class:"header-anchor",href:"#software-version-numbers","aria-label":'Permalink to "Software version numbers"'},"​")],-1),P=n(`
        Integrations ​
        This guide contains the relevant sections for how to connect to Arabica devnet, depending on the type of node you are running. Your best approach to participating is to first determine which node you would like to run. Each node’s guide will link to the relevant network in order to show you how to connect to them. Learn about the different endpoint types in the Cosmos SDK documentation.
        Production RPC endpoints ​
        These RPC providers are meant to be used in production environments.
        ProviderURL
        NewMetrichttps://app.newmetric.xyz/start
        NumiaFor RPC access: https://docs.numia.xyz/overview/rpc-api-access
        NumiaFor data warehouse access: https://docs.numia.xyz/overview/sql-access/chains/celestia
        Grovehttps://www.grove.city/
        Community RPC endpoints ​
        WARNING
        Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs or your own node.
        RPC endpoints and types of nodes you can run in order to participate in Arabica devnet:
        Node typeEndpoint typeEndpoint
        Consensus nodes (full)Consensus RPChttps://rpc.celestia-arabica-11.com
        APIhttps://api.celestia-arabica-11.com
        gRPCgrpc.celestia-arabica-11.com:443
        Direct endpoints with open portsOpen ports: 26656 (p2p), 26657 (RPC), 1317 (API), 9090 (GRPC)
        validator-1.celestia-arabica-11.com
        validator-2.celestia-arabica-11.com
        validator-3.celestia-arabica-11.com
        validator-4.celestia-arabica-11.com
        Data availability nodesDA Bridge Node Endpoints/dns4/da-bridge-1.celestia-arabica-11.com/tcp/2121/p2p/12D3KooWGqwzdEqM54Dce6LXzfFr97Bnhvm6rN7KM7MFwdomfm4S
        (light, bridge, full)/dns4/da-bridge-2.celestia-arabica-11.com/tcp/2121/p2p/12D3KooWCMGM5eZWVfCN9ZLAViGfLUWAfXP5pCm78NFKb9jpBtua
        /dns4/da-bridge-3.celestia-arabica-11.com/tcp/2121/p2p/12D3KooWEWuqrjULANpukDFGVoHW3RoeUU53Ec9t9v5cwW3MkVdQ
        /dns4/da-bridge-4.celestia-arabica-11.com/tcp/2121/p2p/12D3KooWLT1ysSrD7XWSBjh7tU1HQanF5M64dHV6AuM6cYEJxMPk
        --core.ip string endpointsRefer to "Direct endpoints with open ports" above
        You can find the status of these endpoints.
        Using consensus endpoints with DA nodes ​
        Data availability (DA) RPC endpoints for bridge node sync ​
        These RPC endpoints allow bridge nodes to sync blocks from the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default RPC port at 26657 to their respective DA node.
        Data availability (DA) gRPC endpoints for state access ​
        These gRPC endpoints for DA nodes provide state access for querying the chain’s state and broadcasting transactions (balances, blobs, etc.) to the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default gRPC port at 9090 to their respective DA node.
        EXAMPLE
        bash
        celestia <da_type> start –core.ip <url> -–core.grpc.port <port>
        celestia <da_type> start –core.ip <url> -–core.grpc.port <port>
        RPCs for DA nodes to initialise or start your celestia-node to Arabica devnet with can be found in the table in the "Direct endpoints with open ports" section above.
        As an example, this command will work to start a light node with state access, using default ports:
        bash
        celestia light start --p2p.network arabica \\
   --core.ip validator-1.celestia-arabica-11.com
        celestia light start --p2p.network arabica \\
-  --core.ip validator-1.celestia-arabica-11.com
        Bridge node runners
        Not all of the RPC endpoints do not guarantee the full block history. Find an archive endpoint on the community dashboard or run your own consensus node with no pruning for your bridge node.
        Arabica devnet faucet ​
        WARNING
        USING THIS FAUCET DOES NOT ENTITLE YOU TO ANY AIRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS.
        Discord ​
        You can request from Arabica devnet Faucet on the #arabica-faucet channel on Celestia's Discord server with the following command:
        text
        $request <CELESTIA-ADDRESS>
        $request <CELESTIA-ADDRESS>
        Where <CELESTIA-ADDRESS> is a celestia1****** generated address.
        NOTE
        Faucet has a limit of 10 tokens per week per address/Discord ID.
        Web ​
        The web faucet is available at https://faucet.celestia-arabica-11.com/.
        Explorers ​
        There are multiple explorers you can use for Arabica:
        Network upgrades ​
        Join our Telegram announcement channel for network upgrades.
        See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.
        `,35),B=JSON.parse('{"title":"Arabica devnet","description":"A guide to Arabica devnet.","frontmatter":{"description":"A guide to Arabica devnet.","head":[["meta",{"name":"og:title","content":"Arabica devnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/arabica-devnet.md","filePath":"nodes/arabica-devnet.md","lastUpdated":1725971357000}'),T={name:"nodes/arabica-devnet.md"},L=Object.assign(T,{setup(l){return(i,c)=>(o(),r("div",null,[D,s(A),F,s(d),P]))}});export{B as __pageData,L as default};
+  --core.ip validator-1.celestia-arabica-11.com
        Bridge node runners
        Not all of the RPC endpoints do not guarantee the full block history. Find an archive endpoint on the community dashboard or run your own consensus node with no pruning for your bridge node.
        Arabica devnet faucet ​
        WARNING
        USING THIS FAUCET DOES NOT ENTITLE YOU TO ANY AIRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS.
        Discord ​
        You can request from Arabica devnet Faucet on the #arabica-faucet channel on Celestia's Discord server with the following command:
        text
        $request <CELESTIA-ADDRESS>
        $request <CELESTIA-ADDRESS>
        Where <CELESTIA-ADDRESS> is a celestia1****** generated address.
        NOTE
        Faucet has a limit of 10 tokens per week per address/Discord ID.
        Web ​
        The web faucet is available at https://faucet.celestia-arabica-11.com/.
        Explorers ​
        There are multiple explorers you can use for Arabica:
        Network upgrades ​
        Join our Telegram announcement channel for network upgrades.
        See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.
        `,35),B=JSON.parse('{"title":"Arabica devnet","description":"A guide to Arabica devnet.","frontmatter":{"description":"A guide to Arabica devnet.","head":[["meta",{"name":"og:title","content":"Arabica devnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/arabica-devnet.md","filePath":"nodes/arabica-devnet.md","lastUpdated":1725992025000}'),T={name:"nodes/arabica-devnet.md"},L=Object.assign(T,{setup(l){return(i,c)=>(o(),r("div",null,[D,s(A),F,s(d),P]))}});export{B as __pageData,L as default};
diff --git a/pr-1699/assets/nodes_arabica-devnet.md.960dc284.lean.js b/pr-1699/assets/nodes_arabica-devnet.md.5fbea086.lean.js
similarity index 97%
rename from pr-1699/assets/nodes_arabica-devnet.md.960dc284.lean.js
rename to pr-1699/assets/nodes_arabica-devnet.md.5fbea086.lean.js
index bb8b4cfe02..da26ca3f9b 100644
--- a/pr-1699/assets/nodes_arabica-devnet.md.960dc284.lean.js
+++ b/pr-1699/assets/nodes_arabica-devnet.md.5fbea086.lean.js
@@ -1 +1 @@
-import{A as d}from"./chunks/ArabicaVersionTags.5d1acc99.js";import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as h,o,c as r,k as e,t as a,H as s,Q as n,a as u}from"./chunks/framework.b47e54aa.js";import"./chunks/arabica_versions.1930378b.js";const b="/docs-preview/pr-1699/img/arabica-devnet.png",g={name:"ArabicaDevnetDetails",data(){return{constants:p}}},y=e("tr",null,[e("th",null,"Detail"),e("th",null,"Value")],-1),f=e("td",null,"Chain ID",-1),m=e("tr",null,[e("td",null,"Genesis hash"),e("td",null,[e("code",null,"27122593765E07329BC348E8D16E92DCB4C75B34CCCB35C640FD7A4484D4C711")])],-1),E=e("td",null,"Genesis file",-1),v=["href"],k=e("td",null,"Peers file",-1),w=["href"],_=e("tr",null,[e("td",null,"Validators"),e("td",null," 4 ")],-1);function C(l,i,c,q,t,x){return o(),r("table",null,[y,e("tr",null,[f,e("td",null,[e("code",null,a(t.constants.arabicaChainId),1)])]),m,e("tr",null,[E,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.arabicaChainId}/genesis.json`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+a(t.constants.arabicaChainId)+"/genesis.json ",9,v)])]),e("tr",null,[k,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.arabicaChainId}/peers.txt`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+a(t.constants.arabicaChainId)+"/peers.txt ",9,w)])]),_])}const A=h(g,[["render",C]]),D=n("",8),F=e("h3",{id:"software-version-numbers",tabindex:"-1"},[u("Software version numbers "),e("a",{class:"header-anchor",href:"#software-version-numbers","aria-label":'Permalink to "Software version numbers"'},"​")],-1),P=n("",35),B=JSON.parse('{"title":"Arabica devnet","description":"A guide to Arabica devnet.","frontmatter":{"description":"A guide to Arabica devnet.","head":[["meta",{"name":"og:title","content":"Arabica devnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/arabica-devnet.md","filePath":"nodes/arabica-devnet.md","lastUpdated":1725971357000}'),T={name:"nodes/arabica-devnet.md"},L=Object.assign(T,{setup(l){return(i,c)=>(o(),r("div",null,[D,s(A),F,s(d),P]))}});export{B as __pageData,L as default};
+import{A as d}from"./chunks/ArabicaVersionTags.5d1acc99.js";import{c as p}from"./chunks/constants.295fc0ab.js";import{_ as h,o,c as r,k as e,t as a,H as s,Q as n,a as u}from"./chunks/framework.b47e54aa.js";import"./chunks/arabica_versions.1930378b.js";const b="/docs-preview/pr-1699/img/arabica-devnet.png",g={name:"ArabicaDevnetDetails",data(){return{constants:p}}},y=e("tr",null,[e("th",null,"Detail"),e("th",null,"Value")],-1),f=e("td",null,"Chain ID",-1),m=e("tr",null,[e("td",null,"Genesis hash"),e("td",null,[e("code",null,"27122593765E07329BC348E8D16E92DCB4C75B34CCCB35C640FD7A4484D4C711")])],-1),E=e("td",null,"Genesis file",-1),v=["href"],k=e("td",null,"Peers file",-1),w=["href"],_=e("tr",null,[e("td",null,"Validators"),e("td",null," 4 ")],-1);function C(l,i,c,q,t,x){return o(),r("table",null,[y,e("tr",null,[f,e("td",null,[e("code",null,a(t.constants.arabicaChainId),1)])]),m,e("tr",null,[E,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.arabicaChainId}/genesis.json`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+a(t.constants.arabicaChainId)+"/genesis.json ",9,v)])]),e("tr",null,[k,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.arabicaChainId}/peers.txt`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+a(t.constants.arabicaChainId)+"/peers.txt ",9,w)])]),_])}const A=h(g,[["render",C]]),D=n("",8),F=e("h3",{id:"software-version-numbers",tabindex:"-1"},[u("Software version numbers "),e("a",{class:"header-anchor",href:"#software-version-numbers","aria-label":'Permalink to "Software version numbers"'},"​")],-1),P=n("",35),B=JSON.parse('{"title":"Arabica devnet","description":"A guide to Arabica devnet.","frontmatter":{"description":"A guide to Arabica devnet.","head":[["meta",{"name":"og:title","content":"Arabica devnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/arabica-devnet.md","filePath":"nodes/arabica-devnet.md","lastUpdated":1725992025000}'),T={name:"nodes/arabica-devnet.md"},L=Object.assign(T,{setup(l){return(i,c)=>(o(),r("div",null,[D,s(A),F,s(d),P]))}});export{B as __pageData,L as default};
diff --git a/pr-1699/assets/nodes_bridge-node.md.71e96d87.js b/pr-1699/assets/nodes_bridge-node.md.40517142.js
similarity index 97%
rename from pr-1699/assets/nodes_bridge-node.md.71e96d87.js
rename to pr-1699/assets/nodes_bridge-node.md.40517142.js
index 49905397d0..a2070d0cc0 100644
--- a/pr-1699/assets/nodes_bridge-node.md.71e96d87.js
+++ b/pr-1699/assets/nodes_bridge-node.md.40517142.js
@@ -1,6 +1,6 @@
-import{_ as s,o as e,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const n="/docs-preview/pr-1699/img/nodes/BridgeNodes.png",u=JSON.parse('{"title":"Setting up a Celestia bridge node","description":"","frontmatter":{"\\\\description":"Learn how to set up your Celestia bridge node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia bridge node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/bridge-node.md","filePath":"nodes/bridge-node.md","lastUpdated":1725971357000}'),l={name:"nodes/bridge-node.md"},t=o('
        Setting up a Celestia bridge node ​
        This tutorial will go over the steps to setting up your Celestia bridge node.
        Bridge nodes connect the data availability layer and the consensus layer.
        Overview of bridge nodes ​
        A Celestia bridge node has the following properties:
        1. Import and process “raw” headers & blocks from a trusted core process (meaning a trusted RPC connection to a celestia-core node) in the Consensus network. Bridge nodes can run this core process internally (embedded) or simply connect to a remote endpoint. Bridge nodes also have the option of being an active validator in the consensus network.
        2. Validate and erasure code the “raw” blocks
        3. Supply block shares with data availability headers to light nodes in the DA network.
        bridge-node-diagram
        From an implementation perspective, Bridge nodes run two separate processes:
        1. celestia-app with celestia-core (see repo)
          • celestia-app is the state machine where the application and the proof-of-stake logic is run. celestia-app is built on Cosmos SDK and also encompasses celestia-core.
          • celestia-core is the state interaction, consensus and block production layer. celestia-core is built on Tendermint Core, modified to store data roots of erasure coded blocks among other changes (see ADRs).
        2. celestia-node (see repo)
          • celestia-node augments the above with a separate libp2p network that serves data availability sampling requests. The team sometimes refers to this as the “halo” network.
        Hardware requirements ​
        The following hardware minimum requirements are recommended for running the bridge node:
        • Memory: 16 GB RAM (minimum)
        • CPU: 6 cores
        • Disk: 10 TB SSD Storage
        • Bandwidth: 1 Gbps for Download/1 Gbps for Upload
        Setting up your bridge node ​
        The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.
        Setup the dependencies ​
        Follow the tutorial for installing the dependencies.
        Deploy the Celestia bridge node ​
        Install Celestia Node ​
        Install the celestia-node binary, which will be used to run the bridge node.
        Follow the tutorial for installing celestia-node.
        Initialize the bridge node ​
        Run the following:
        sh
        celestia bridge init --core.ip <URI>
        celestia bridge init --core.ip <URI>
        The --core.ip gRPC port defaults to 9090, so if you do not specify it in the command line, it will default to that port. You can add the port after the IP address or use the --core.grpc.port flag to specify another port if you prefer.
        Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.
        Using an RPC of your own, or one from the list on the Mocha testnet page or list on the Arabica devnet page, start your node.
        Connecting to a core endpoint with --core.ip string provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).
        Here is an example of initializing the bridge node:
        sh
        celestia bridge init --core.ip <URI>
        celestia bridge init --core.ip <URI>
        sh
        celestia bridge init --core.ip <URI> --p2p.network mocha
        celestia bridge init --core.ip <URI> --p2p.network mocha
        sh
        celestia bridge init --core.ip <URI> --p2p.network arabica
        celestia bridge init --core.ip <URI> --p2p.network arabica
        Run the bridge node ​
        Start the bridge node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):
        sh
        celestia bridge start --core.ip <URI>
        celestia bridge start --core.ip <URI>
        Here is an example of starting the bridge node on Mocha:
        sh
        celestia bridge start --core.ip rpc-mocha.pops.one:26657 --p2p.network mocha
        celestia bridge start --core.ip rpc-mocha.pops.one:26657 --p2p.network mocha
        And on Arabica:
        sh
        celestia bridge start --core.ip validator-1.celestia-arabica-11.com \\
+import{_ as s,o as e,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const n="/docs-preview/pr-1699/img/nodes/BridgeNodes.png",u=JSON.parse('{"title":"Setting up a Celestia bridge node","description":"","frontmatter":{"\\\\description":"Learn how to set up your Celestia bridge node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia bridge node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/bridge-node.md","filePath":"nodes/bridge-node.md","lastUpdated":1725992025000}'),l={name:"nodes/bridge-node.md"},t=o('
        Setting up a Celestia bridge node ​
        This tutorial will go over the steps to setting up your Celestia bridge node.
        Bridge nodes connect the data availability layer and the consensus layer.
        Overview of bridge nodes ​
        A Celestia bridge node has the following properties:
        1. Import and process “raw” headers & blocks from a trusted core process (meaning a trusted RPC connection to a celestia-core node) in the Consensus network. Bridge nodes can run this core process internally (embedded) or simply connect to a remote endpoint. Bridge nodes also have the option of being an active validator in the consensus network.
        2. Validate and erasure code the “raw” blocks
        3. Supply block shares with data availability headers to light nodes in the DA network.
        bridge-node-diagram
        From an implementation perspective, Bridge nodes run two separate processes:
        1. celestia-app with celestia-core (see repo)
          • celestia-app is the state machine where the application and the proof-of-stake logic is run. celestia-app is built on Cosmos SDK and also encompasses celestia-core.
          • celestia-core is the state interaction, consensus and block production layer. celestia-core is built on Tendermint Core, modified to store data roots of erasure coded blocks among other changes (see ADRs).
        2. celestia-node (see repo)
          • celestia-node augments the above with a separate libp2p network that serves data availability sampling requests. The team sometimes refers to this as the “halo” network.
        Hardware requirements ​
        The following hardware minimum requirements are recommended for running the bridge node:
        • Memory: 16 GB RAM (minimum)
        • CPU: 6 cores
        • Disk: 10 TB SSD Storage
        • Bandwidth: 1 Gbps for Download/1 Gbps for Upload
        Setting up your bridge node ​
        The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.
        Setup the dependencies ​
        Follow the tutorial for installing the dependencies.
        Deploy the Celestia bridge node ​
        Install Celestia Node ​
        Install the celestia-node binary, which will be used to run the bridge node.
        Follow the tutorial for installing celestia-node.
        Initialize the bridge node ​
        Run the following:
        sh
        celestia bridge init --core.ip <URI>
        celestia bridge init --core.ip <URI>
        The --core.ip gRPC port defaults to 9090, so if you do not specify it in the command line, it will default to that port. You can add the port after the IP address or use the --core.grpc.port flag to specify another port if you prefer.
        Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.
        Using an RPC of your own, or one from the list on the Mocha testnet page or list on the Arabica devnet page, start your node.
        Connecting to a core endpoint with --core.ip string provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).
        Here is an example of initializing the bridge node:
        sh
        celestia bridge init --core.ip <URI>
        celestia bridge init --core.ip <URI>
        sh
        celestia bridge init --core.ip <URI> --p2p.network mocha
        celestia bridge init --core.ip <URI> --p2p.network mocha
        sh
        celestia bridge init --core.ip <URI> --p2p.network arabica
        celestia bridge init --core.ip <URI> --p2p.network arabica
        Run the bridge node ​
        Start the bridge node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):
        sh
        celestia bridge start --core.ip <URI>
        celestia bridge start --core.ip <URI>
        Here is an example of starting the bridge node on Mocha:
        sh
        celestia bridge start --core.ip rpc-mocha.pops.one:26657 --p2p.network mocha
        celestia bridge start --core.ip rpc-mocha.pops.one:26657 --p2p.network mocha
        And on Arabica:
        sh
        celestia bridge start --core.ip validator-1.celestia-arabica-11.com \\
   --p2p.network arabica
        celestia bridge start --core.ip validator-1.celestia-arabica-11.com \\
-  --p2p.network arabica
        You can create your key for your node by following the cel-key instructions.
        Once you start the bridge node, a wallet key will be generated for you. You will need to fund that address with Testnet tokens to pay for PayForBlob transactions. You can find the address by running the following command:
        sh
        ./cel-key list --node.type bridge --keyring-backend test --p2p.network <network>
        ./cel-key list --node.type bridge --keyring-backend test --p2p.network <network>
        TIP
        You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information
        You can get testnet tokens from:
        NOTE
        If you are running a bridge node for your validator it is highly recommended to request Mocha testnet tokens as this is the testnet used to test out validator operations.
        Optional: run the bridge node with a custom key ​
        In order to run a bridge node using a custom key:
        1. The custom key must exist inside the celestia bridge node directory at the correct path (default: ~/.celestia-bridge/keys/keyring-test)
        2. The name of the custom key must be passed upon start, like so:
        sh
        celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key>
        celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key>
        sh
        celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key> \\
+  --p2p.network arabica
        You can create your key for your node by following the cel-key instructions.
        Once you start the bridge node, a wallet key will be generated for you. You will need to fund that address with Testnet tokens to pay for PayForBlob transactions. You can find the address by running the following command:
        sh
        ./cel-key list --node.type bridge --keyring-backend test --p2p.network <network>
        ./cel-key list --node.type bridge --keyring-backend test --p2p.network <network>
        TIP
        You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information
        You can get testnet tokens from:
        NOTE
        If you are running a bridge node for your validator it is highly recommended to request Mocha testnet tokens as this is the testnet used to test out validator operations.
        Optional: run the bridge node with a custom key ​
        In order to run a bridge node using a custom key:
        1. The custom key must exist inside the celestia bridge node directory at the correct path (default: ~/.celestia-bridge/keys/keyring-test)
        2. The name of the custom key must be passed upon start, like so:
        sh
        celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key>
        celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key>
        sh
        celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key> \\
   --p2p.network mocha
        celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key> \\
   --p2p.network mocha
        sh
        celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key> \\
   --p2p.network arabica
        celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key> \\
diff --git a/pr-1699/assets/nodes_bridge-node.md.71e96d87.lean.js b/pr-1699/assets/nodes_bridge-node.md.40517142.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_bridge-node.md.71e96d87.lean.js
rename to pr-1699/assets/nodes_bridge-node.md.40517142.lean.js
index 7ba0f883c4..e86a9eed4a 100644
--- a/pr-1699/assets/nodes_bridge-node.md.71e96d87.lean.js
+++ b/pr-1699/assets/nodes_bridge-node.md.40517142.lean.js
@@ -1 +1 @@
-import{_ as s,o as e,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const n="/docs-preview/pr-1699/img/nodes/BridgeNodes.png",u=JSON.parse('{"title":"Setting up a Celestia bridge node","description":"","frontmatter":{"\\\\description":"Learn how to set up your Celestia bridge node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia bridge node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/bridge-node.md","filePath":"nodes/bridge-node.md","lastUpdated":1725971357000}'),l={name:"nodes/bridge-node.md"},t=o("",53),p=[t];function r(c,i,d,y,E,h){return e(),a("div",null,p)}const b=s(l,[["render",r]]);export{u as __pageData,b as default};
+import{_ as s,o as e,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const n="/docs-preview/pr-1699/img/nodes/BridgeNodes.png",u=JSON.parse('{"title":"Setting up a Celestia bridge node","description":"","frontmatter":{"\\\\description":"Learn how to set up your Celestia bridge node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia bridge node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/bridge-node.md","filePath":"nodes/bridge-node.md","lastUpdated":1725992025000}'),l={name:"nodes/bridge-node.md"},t=o("",53),p=[t];function r(c,i,d,y,E,h){return e(),a("div",null,p)}const b=s(l,[["render",r]]);export{u as __pageData,b as default};
diff --git a/pr-1699/assets/nodes_celestia-app-commands.md.0be51395.js b/pr-1699/assets/nodes_celestia-app-commands.md.16f0c3b5.js
similarity index 99%
rename from pr-1699/assets/nodes_celestia-app-commands.md.0be51395.js
rename to pr-1699/assets/nodes_celestia-app-commands.md.16f0c3b5.js
index fb87b9458a..c06eb9373d 100644
--- a/pr-1699/assets/nodes_celestia-app-commands.md.0be51395.js
+++ b/pr-1699/assets/nodes_celestia-app-commands.md.16f0c3b5.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Helpful CLI commands","description":"Some of the most helpful celestia-app CLI commands.","frontmatter":{"description":"Some of the most helpful celestia-app CLI commands.","next":{"text":"SystemD","link":"/nodes/systemd"},"head":[["meta",{"name":"og:title","content":"Helpful CLI commands | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-commands.md","filePath":"nodes/celestia-app-commands.md","lastUpdated":1725971357000}'),p={name:"nodes/celestia-app-commands.md"},o=l(`
        Helpful CLI commands ​
        View all options:
        console
        $ celestia-appd --help
+import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Helpful CLI commands","description":"Some of the most helpful celestia-app CLI commands.","frontmatter":{"description":"Some of the most helpful celestia-app CLI commands.","next":{"text":"SystemD","link":"/nodes/systemd"},"head":[["meta",{"name":"og:title","content":"Helpful CLI commands | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-commands.md","filePath":"nodes/celestia-app-commands.md","lastUpdated":1725992025000}'),p={name:"nodes/celestia-app-commands.md"},o=l(`
        Helpful CLI commands ​
        View all options:
        console
        $ celestia-appd --help
 Start celestia-app
 
 Usage:
diff --git a/pr-1699/assets/nodes_celestia-app-commands.md.0be51395.lean.js b/pr-1699/assets/nodes_celestia-app-commands.md.16f0c3b5.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_celestia-app-commands.md.0be51395.lean.js
rename to pr-1699/assets/nodes_celestia-app-commands.md.16f0c3b5.lean.js
index ae12f4c2f2..a3f744fb79 100644
--- a/pr-1699/assets/nodes_celestia-app-commands.md.0be51395.lean.js
+++ b/pr-1699/assets/nodes_celestia-app-commands.md.16f0c3b5.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Helpful CLI commands","description":"Some of the most helpful celestia-app CLI commands.","frontmatter":{"description":"Some of the most helpful celestia-app CLI commands.","next":{"text":"SystemD","link":"/nodes/systemd"},"head":[["meta",{"name":"og:title","content":"Helpful CLI commands | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-commands.md","filePath":"nodes/celestia-app-commands.md","lastUpdated":1725971357000}'),p={name:"nodes/celestia-app-commands.md"},o=l("",84),e=[o];function t(c,r,y,E,i,F){return a(),n("div",null,e)}const g=s(p,[["render",t]]);export{u as __pageData,g as default};
+import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Helpful CLI commands","description":"Some of the most helpful celestia-app CLI commands.","frontmatter":{"description":"Some of the most helpful celestia-app CLI commands.","next":{"text":"SystemD","link":"/nodes/systemd"},"head":[["meta",{"name":"og:title","content":"Helpful CLI commands | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-commands.md","filePath":"nodes/celestia-app-commands.md","lastUpdated":1725992025000}'),p={name:"nodes/celestia-app-commands.md"},o=l("",84),e=[o];function t(c,r,y,E,i,F){return a(),n("div",null,e)}const g=s(p,[["render",t]]);export{u as __pageData,g as default};
diff --git a/pr-1699/assets/nodes_celestia-app-metrics.md.ba859d9d.js b/pr-1699/assets/nodes_celestia-app-metrics.md.0b6cb333.js
similarity index 99%
rename from pr-1699/assets/nodes_celestia-app-metrics.md.ba859d9d.js
rename to pr-1699/assets/nodes_celestia-app-metrics.md.0b6cb333.js
index 0a309372c1..6da8cd661a 100644
--- a/pr-1699/assets/nodes_celestia-app-metrics.md.ba859d9d.js
+++ b/pr-1699/assets/nodes_celestia-app-metrics.md.0b6cb333.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const m=JSON.parse('{"title":"Metrics","description":"A guide on how to monitor the health and performance of your system.","frontmatter":{"description":"A guide on how to monitor the health and performance of your system.","prev":{"text":"Troubleshooting","link":"/nodes/celestia-node-troubleshooting"},"head":[["meta",{"name":"og:title","content":"Metrics | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-metrics.md","filePath":"nodes/celestia-app-metrics.md","lastUpdated":1725971357000}'),o={name:"nodes/celestia-app-metrics.md"},l=e(`
        Metrics ​
        Metrics are a powerful tool for monitoring the health and performance of a system. Celestia provides support for metrics to make sure, as an operator, your system continues to remain up and running. Metrics can also provide critical insight into how Celestia is used and how it can be improved.
        Setup ​
        Celestia uses Prometheus to publish metrics. It can be enabled through the config.toml file.
        bash
        #######################################################
+import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const m=JSON.parse('{"title":"Metrics","description":"A guide on how to monitor the health and performance of your system.","frontmatter":{"description":"A guide on how to monitor the health and performance of your system.","prev":{"text":"Troubleshooting","link":"/nodes/celestia-node-troubleshooting"},"head":[["meta",{"name":"og:title","content":"Metrics | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-metrics.md","filePath":"nodes/celestia-app-metrics.md","lastUpdated":1725992025000}'),o={name:"nodes/celestia-app-metrics.md"},l=e(`
        Metrics ​
        Metrics are a powerful tool for monitoring the health and performance of a system. Celestia provides support for metrics to make sure, as an operator, your system continues to remain up and running. Metrics can also provide critical insight into how Celestia is used and how it can be improved.
        Setup ​
        Celestia uses Prometheus to publish metrics. It can be enabled through the config.toml file.
        bash
        #######################################################
 ###       Instrumentation Configuration Options     ###
 #######################################################
 [instrumentation]
diff --git a/pr-1699/assets/nodes_celestia-app-metrics.md.ba859d9d.lean.js b/pr-1699/assets/nodes_celestia-app-metrics.md.0b6cb333.lean.js
similarity index 92%
rename from pr-1699/assets/nodes_celestia-app-metrics.md.ba859d9d.lean.js
rename to pr-1699/assets/nodes_celestia-app-metrics.md.0b6cb333.lean.js
index e03f73dad2..b03c093df6 100644
--- a/pr-1699/assets/nodes_celestia-app-metrics.md.ba859d9d.lean.js
+++ b/pr-1699/assets/nodes_celestia-app-metrics.md.0b6cb333.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const m=JSON.parse('{"title":"Metrics","description":"A guide on how to monitor the health and performance of your system.","frontmatter":{"description":"A guide on how to monitor the health and performance of your system.","prev":{"text":"Troubleshooting","link":"/nodes/celestia-node-troubleshooting"},"head":[["meta",{"name":"og:title","content":"Metrics | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-metrics.md","filePath":"nodes/celestia-app-metrics.md","lastUpdated":1725971357000}'),o={name:"nodes/celestia-app-metrics.md"},l=e("",27),t=[l];function p(r,c,i,y,u,h){return a(),n("div",null,t)}const E=s(o,[["render",p]]);export{m as __pageData,E as default};
+import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const m=JSON.parse('{"title":"Metrics","description":"A guide on how to monitor the health and performance of your system.","frontmatter":{"description":"A guide on how to monitor the health and performance of your system.","prev":{"text":"Troubleshooting","link":"/nodes/celestia-node-troubleshooting"},"head":[["meta",{"name":"og:title","content":"Metrics | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-metrics.md","filePath":"nodes/celestia-app-metrics.md","lastUpdated":1725992025000}'),o={name:"nodes/celestia-app-metrics.md"},l=e("",27),t=[l];function p(r,c,i,y,u,h){return a(),n("div",null,t)}const E=s(o,[["render",p]]);export{m as __pageData,E as default};
diff --git a/pr-1699/assets/nodes_celestia-app-multisig.md.cf17caf2.js b/pr-1699/assets/nodes_celestia-app-multisig.md.4833031c.js
similarity index 99%
rename from pr-1699/assets/nodes_celestia-app-multisig.md.cf17caf2.js
rename to pr-1699/assets/nodes_celestia-app-multisig.md.4833031c.js
index 6814d1abcd..acc24181ae 100644
--- a/pr-1699/assets/nodes_celestia-app-multisig.md.cf17caf2.js
+++ b/pr-1699/assets/nodes_celestia-app-multisig.md.4833031c.js
@@ -1,4 +1,4 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const d=JSON.parse('{"title":"Multisig","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Multisig | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-multisig.md","filePath":"nodes/celestia-app-multisig.md","lastUpdated":1725971357000}'),p={name:"nodes/celestia-app-multisig.md"},o=l(`
        Multisig ​
        Celestia inherits support for multisig accounts from the Cosmos SDK. Multisig accounts behave similarly to regular accounts with the added requirement that a threshold of signatures is needed to authorize a transaction.
        Multisig accounts can be created from the command line or using a graphical interface such as Keplr.
        Command line ​
        bash
        #!/bin/sh
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const d=JSON.parse('{"title":"Multisig","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Multisig | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-multisig.md","filePath":"nodes/celestia-app-multisig.md","lastUpdated":1725992025000}'),p={name:"nodes/celestia-app-multisig.md"},o=l(`
        Multisig ​
        Celestia inherits support for multisig accounts from the Cosmos SDK. Multisig accounts behave similarly to regular accounts with the added requirement that a threshold of signatures is needed to authorize a transaction.
        Multisig accounts can be created from the command line or using a graphical interface such as Keplr.
        Command line ​
        bash
        #!/bin/sh
 
 # Prerequisite: prior to running this script, start a single node devnet with ./scripts/single-node.sh
 CHAIN_ID="private"
diff --git a/pr-1699/assets/nodes_celestia-app-multisig.md.cf17caf2.lean.js b/pr-1699/assets/nodes_celestia-app-multisig.md.4833031c.lean.js
similarity index 88%
rename from pr-1699/assets/nodes_celestia-app-multisig.md.cf17caf2.lean.js
rename to pr-1699/assets/nodes_celestia-app-multisig.md.4833031c.lean.js
index 6125873f90..3b367fd036 100644
--- a/pr-1699/assets/nodes_celestia-app-multisig.md.cf17caf2.lean.js
+++ b/pr-1699/assets/nodes_celestia-app-multisig.md.4833031c.lean.js
@@ -1 +1 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const d=JSON.parse('{"title":"Multisig","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Multisig | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-multisig.md","filePath":"nodes/celestia-app-multisig.md","lastUpdated":1725971357000}'),p={name:"nodes/celestia-app-multisig.md"},o=l("",7),e=[o];function t(c,r,y,E,i,F){return n(),a("div",null,e)}const u=s(p,[["render",t]]);export{d as __pageData,u as default};
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const d=JSON.parse('{"title":"Multisig","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Multisig | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-multisig.md","filePath":"nodes/celestia-app-multisig.md","lastUpdated":1725992025000}'),p={name:"nodes/celestia-app-multisig.md"},o=l("",7),e=[o];function t(c,r,y,E,i,F){return n(),a("div",null,e)}const u=s(p,[["render",t]]);export{d as __pageData,u as default};
diff --git a/pr-1699/assets/nodes_celestia-app-slashing.md.c061c14c.js b/pr-1699/assets/nodes_celestia-app-slashing.md.5b9f9df0.js
similarity index 97%
rename from pr-1699/assets/nodes_celestia-app-slashing.md.c061c14c.js
rename to pr-1699/assets/nodes_celestia-app-slashing.md.5b9f9df0.js
index 5f8e980a0b..136a1221f8 100644
--- a/pr-1699/assets/nodes_celestia-app-slashing.md.c061c14c.js
+++ b/pr-1699/assets/nodes_celestia-app-slashing.md.5b9f9df0.js
@@ -1 +1 @@
-import{_ as e,o as a,c as t,Q as i}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Jailing and Slashing on Celestia","description":"This section covers the jailing and slashing mechanics for validators in Celestia.","frontmatter":{"description":"This section covers the jailing and slashing mechanics for validators in Celestia.","head":[["meta",{"name":"og:title","content":"Jailing and Slashing on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-slashing.md","filePath":"nodes/celestia-app-slashing.md","lastUpdated":1725971357000}'),o={name:"nodes/celestia-app-slashing.md"},s=i('
        Jailing and Slashing on Celestia ​
        Slashing is a mechanism employed in proof of stake blockchains that is used to deter and punish malicious behavior. It functions by removing a percentage of a validator's stake each time they act harmfully towards the network.
        Celestia is built with the Cosmos SDK and uses the x/slashing module.
        If a validator gets slashed, delegators bonded to that validator will also have the same percentage of their delegated funds slashed.
        The following are the conditions for a validator to get jailed or slashed:
        1. Downtime: If a validator is offline for more than 25% of a rolling window of the last 5,000 blocks, they will be jailed for 1 minute. During this period, the validator is removed from the validator set temporarily, and will be unable to propose new blocks or earn rewards. After the jail period, the validator can send an unjail request to rejoin the validator set.
        2. Double signing: This is a more severe offense and results in getting slashed. If a validator engages in double signing, the validator will lose 2% of their stake and the remainder of their stake will be returned to them. The validator will be permanently removed from the validator set and will not have the ability to unjail. Delegators bonded to that validator will automatically enter the unbonding period for 21 days, and can delegate to another validator after they have been unbonded.
        For more details on the jailing and slashing parameters, refer to the celestia-app specifications page.
        ',7),n=[s];function l(r,d,h,c,p,g){return a(),t("div",null,n)}const u=e(o,[["render",l]]);export{f as __pageData,u as default};
+import{_ as e,o as a,c as t,Q as i}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Jailing and Slashing on Celestia","description":"This section covers the jailing and slashing mechanics for validators in Celestia.","frontmatter":{"description":"This section covers the jailing and slashing mechanics for validators in Celestia.","head":[["meta",{"name":"og:title","content":"Jailing and Slashing on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-slashing.md","filePath":"nodes/celestia-app-slashing.md","lastUpdated":1725992025000}'),o={name:"nodes/celestia-app-slashing.md"},s=i('
        Jailing and Slashing on Celestia ​
        Slashing is a mechanism employed in proof of stake blockchains that is used to deter and punish malicious behavior. It functions by removing a percentage of a validator's stake each time they act harmfully towards the network.
        Celestia is built with the Cosmos SDK and uses the x/slashing module.
        If a validator gets slashed, delegators bonded to that validator will also have the same percentage of their delegated funds slashed.
        The following are the conditions for a validator to get jailed or slashed:
        1. Downtime: If a validator is offline for more than 25% of a rolling window of the last 5,000 blocks, they will be jailed for 1 minute. During this period, the validator is removed from the validator set temporarily, and will be unable to propose new blocks or earn rewards. After the jail period, the validator can send an unjail request to rejoin the validator set.
        2. Double signing: This is a more severe offense and results in getting slashed. If a validator engages in double signing, the validator will lose 2% of their stake and the remainder of their stake will be returned to them. The validator will be permanently removed from the validator set and will not have the ability to unjail. Delegators bonded to that validator will automatically enter the unbonding period for 21 days, and can delegate to another validator after they have been unbonded.
        For more details on the jailing and slashing parameters, refer to the celestia-app specifications page.
        ',7),n=[s];function l(r,d,h,c,p,g){return a(),t("div",null,n)}const u=e(o,[["render",l]]);export{f as __pageData,u as default};
diff --git a/pr-1699/assets/nodes_celestia-app-slashing.md.c061c14c.lean.js b/pr-1699/assets/nodes_celestia-app-slashing.md.5b9f9df0.lean.js
similarity index 92%
rename from pr-1699/assets/nodes_celestia-app-slashing.md.c061c14c.lean.js
rename to pr-1699/assets/nodes_celestia-app-slashing.md.5b9f9df0.lean.js
index ed973ed6d0..2653cf467f 100644
--- a/pr-1699/assets/nodes_celestia-app-slashing.md.c061c14c.lean.js
+++ b/pr-1699/assets/nodes_celestia-app-slashing.md.5b9f9df0.lean.js
@@ -1 +1 @@
-import{_ as e,o as a,c as t,Q as i}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Jailing and Slashing on Celestia","description":"This section covers the jailing and slashing mechanics for validators in Celestia.","frontmatter":{"description":"This section covers the jailing and slashing mechanics for validators in Celestia.","head":[["meta",{"name":"og:title","content":"Jailing and Slashing on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-slashing.md","filePath":"nodes/celestia-app-slashing.md","lastUpdated":1725971357000}'),o={name:"nodes/celestia-app-slashing.md"},s=i("",7),n=[s];function l(r,d,h,c,p,g){return a(),t("div",null,n)}const u=e(o,[["render",l]]);export{f as __pageData,u as default};
+import{_ as e,o as a,c as t,Q as i}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Jailing and Slashing on Celestia","description":"This section covers the jailing and slashing mechanics for validators in Celestia.","frontmatter":{"description":"This section covers the jailing and slashing mechanics for validators in Celestia.","head":[["meta",{"name":"og:title","content":"Jailing and Slashing on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-slashing.md","filePath":"nodes/celestia-app-slashing.md","lastUpdated":1725992025000}'),o={name:"nodes/celestia-app-slashing.md"},s=i("",7),n=[s];function l(r,d,h,c,p,g){return a(),t("div",null,n)}const u=e(o,[["render",l]]);export{f as __pageData,u as default};
diff --git a/pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.c2b31db9.js b/pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.0555c2d4.js
similarity index 89%
rename from pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.c2b31db9.js
rename to pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.0555c2d4.js
index 6ef75e8932..982d0cf767 100644
--- a/pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.c2b31db9.js
+++ b/pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.0555c2d4.js
@@ -1 +1 @@
-import{_ as o,o as a,c as r,k as e,a as t}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Upgrade Monitor","description":"upgrade-monitor is a tool to monitor upgrades on a Celestia network.","frontmatter":{"description":"upgrade-monitor is a tool to monitor upgrades on a Celestia network.","head":[["meta",{"name":"og:title","content":"Upgrade Monitor | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-upgrade-monitor.md","filePath":"nodes/celestia-app-upgrade-monitor.md","lastUpdated":1725971357000}'),n={name:"nodes/celestia-app-upgrade-monitor.md"},s=e("h1",{id:"upgrade-monitor",tabindex:"-1"},[t("Upgrade Monitor "),e("a",{class:"header-anchor",href:"#upgrade-monitor","aria-label":'Permalink to "Upgrade Monitor"'},"​")],-1),i=e("p",null,[t("Upgrade monitor is a binary that monitors that status of upgrades on a Celestia network. See the "),e("a",{href:"https://github.com/celestiaorg/upgrade-monitor",target:"_blank",rel:"noreferrer"},"README"),t(" for instructions on how to install and use the binary.")],-1),d=[s,i];function p(c,l,m,g,u,h){return a(),r("div",null,d)}const k=o(n,[["render",p]]);export{f as __pageData,k as default};
+import{_ as o,o as a,c as r,k as e,a as t}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Upgrade Monitor","description":"upgrade-monitor is a tool to monitor upgrades on a Celestia network.","frontmatter":{"description":"upgrade-monitor is a tool to monitor upgrades on a Celestia network.","head":[["meta",{"name":"og:title","content":"Upgrade Monitor | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-upgrade-monitor.md","filePath":"nodes/celestia-app-upgrade-monitor.md","lastUpdated":1725992025000}'),n={name:"nodes/celestia-app-upgrade-monitor.md"},s=e("h1",{id:"upgrade-monitor",tabindex:"-1"},[t("Upgrade Monitor "),e("a",{class:"header-anchor",href:"#upgrade-monitor","aria-label":'Permalink to "Upgrade Monitor"'},"​")],-1),i=e("p",null,[t("Upgrade monitor is a binary that monitors that status of upgrades on a Celestia network. See the "),e("a",{href:"https://github.com/celestiaorg/upgrade-monitor",target:"_blank",rel:"noreferrer"},"README"),t(" for instructions on how to install and use the binary.")],-1),d=[s,i];function p(c,l,m,g,u,h){return a(),r("div",null,d)}const k=o(n,[["render",p]]);export{f as __pageData,k as default};
diff --git a/pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.c2b31db9.lean.js b/pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.0555c2d4.lean.js
similarity index 89%
rename from pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.c2b31db9.lean.js
rename to pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.0555c2d4.lean.js
index 6ef75e8932..982d0cf767 100644
--- a/pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.c2b31db9.lean.js
+++ b/pr-1699/assets/nodes_celestia-app-upgrade-monitor.md.0555c2d4.lean.js
@@ -1 +1 @@
-import{_ as o,o as a,c as r,k as e,a as t}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Upgrade Monitor","description":"upgrade-monitor is a tool to monitor upgrades on a Celestia network.","frontmatter":{"description":"upgrade-monitor is a tool to monitor upgrades on a Celestia network.","head":[["meta",{"name":"og:title","content":"Upgrade Monitor | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-upgrade-monitor.md","filePath":"nodes/celestia-app-upgrade-monitor.md","lastUpdated":1725971357000}'),n={name:"nodes/celestia-app-upgrade-monitor.md"},s=e("h1",{id:"upgrade-monitor",tabindex:"-1"},[t("Upgrade Monitor "),e("a",{class:"header-anchor",href:"#upgrade-monitor","aria-label":'Permalink to "Upgrade Monitor"'},"​")],-1),i=e("p",null,[t("Upgrade monitor is a binary that monitors that status of upgrades on a Celestia network. See the "),e("a",{href:"https://github.com/celestiaorg/upgrade-monitor",target:"_blank",rel:"noreferrer"},"README"),t(" for instructions on how to install and use the binary.")],-1),d=[s,i];function p(c,l,m,g,u,h){return a(),r("div",null,d)}const k=o(n,[["render",p]]);export{f as __pageData,k as default};
+import{_ as o,o as a,c as r,k as e,a as t}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Upgrade Monitor","description":"upgrade-monitor is a tool to monitor upgrades on a Celestia network.","frontmatter":{"description":"upgrade-monitor is a tool to monitor upgrades on a Celestia network.","head":[["meta",{"name":"og:title","content":"Upgrade Monitor | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-upgrade-monitor.md","filePath":"nodes/celestia-app-upgrade-monitor.md","lastUpdated":1725992025000}'),n={name:"nodes/celestia-app-upgrade-monitor.md"},s=e("h1",{id:"upgrade-monitor",tabindex:"-1"},[t("Upgrade Monitor "),e("a",{class:"header-anchor",href:"#upgrade-monitor","aria-label":'Permalink to "Upgrade Monitor"'},"​")],-1),i=e("p",null,[t("Upgrade monitor is a binary that monitors that status of upgrades on a Celestia network. See the "),e("a",{href:"https://github.com/celestiaorg/upgrade-monitor",target:"_blank",rel:"noreferrer"},"README"),t(" for instructions on how to install and use the binary.")],-1),d=[s,i];function p(c,l,m,g,u,h){return a(),r("div",null,d)}const k=o(n,[["render",p]]);export{f as __pageData,k as default};
diff --git a/pr-1699/assets/nodes_celestia-app-vesting.md.e8ca90cc.js b/pr-1699/assets/nodes_celestia-app-vesting.md.e829dc7e.js
similarity index 99%
rename from pr-1699/assets/nodes_celestia-app-vesting.md.e8ca90cc.js
rename to pr-1699/assets/nodes_celestia-app-vesting.md.e829dc7e.js
index 3adffc6281..bad464db7a 100644
--- a/pr-1699/assets/nodes_celestia-app-vesting.md.e8ca90cc.js
+++ b/pr-1699/assets/nodes_celestia-app-vesting.md.e829dc7e.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"How to create a vesting account with celestia-app","description":"Learn how to generate a vesting account using celestia-app.","frontmatter":{"description":"Learn how to generate a vesting account using celestia-app.","head":[["meta",{"name":"og:title","content":"How to create a vesting account with celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-vesting.md","filePath":"nodes/celestia-app-vesting.md","lastUpdated":1725971357000}'),l={name:"nodes/celestia-app-vesting.md"},p=o(`
        How to create a vesting account with celestia-app ​
        In this guide, we will learn how to create a vesting account using celestia-app for both a local devnet and on Mocha testnet.
        note
        The instructions for this tutorial are for a continuous vesting account, if you'd like to make a delayed vesting account, just add the --delayed flag to your vesting transaction.
        Local devnet ​
        First, download and install celestia-app, selecting the network and corresponding version that you would like to use.
        Setting up the local devnet ​
        Run the devnet ​
        Next, change into the $HOME/celestia-app directory and run the single-node-devnet script.
        bash
        cd $HOME/celestia-app
+import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"How to create a vesting account with celestia-app","description":"Learn how to generate a vesting account using celestia-app.","frontmatter":{"description":"Learn how to generate a vesting account using celestia-app.","head":[["meta",{"name":"og:title","content":"How to create a vesting account with celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-vesting.md","filePath":"nodes/celestia-app-vesting.md","lastUpdated":1725992025000}'),l={name:"nodes/celestia-app-vesting.md"},p=o(`
        How to create a vesting account with celestia-app ​
        In this guide, we will learn how to create a vesting account using celestia-app for both a local devnet and on Mocha testnet.
        note
        The instructions for this tutorial are for a continuous vesting account, if you'd like to make a delayed vesting account, just add the --delayed flag to your vesting transaction.
        Local devnet ​
        First, download and install celestia-app, selecting the network and corresponding version that you would like to use.
        Setting up the local devnet ​
        Run the devnet ​
        Next, change into the $HOME/celestia-app directory and run the single-node-devnet script.
        bash
        cd $HOME/celestia-app
 ./scripts/build-run-single-node.sh
        cd $HOME/celestia-app
 ./scripts/build-run-single-node.sh
        Save the home directory path ​
        At the top of the output, you will see a path to the "Home directory", find yours from the output (it will be unique every time):
        bash
        ./scripts/build-run-single-node.sh
 Home directory: /var/folders/_8/ljj6hspn0kn09qf9fy8kdyh40000gn/T/celestia_app_XXXXXXXXXXXXX.XV92a3qx
diff --git a/pr-1699/assets/nodes_celestia-app-vesting.md.e8ca90cc.lean.js b/pr-1699/assets/nodes_celestia-app-vesting.md.e829dc7e.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_celestia-app-vesting.md.e8ca90cc.lean.js
rename to pr-1699/assets/nodes_celestia-app-vesting.md.e829dc7e.lean.js
index 04618fd138..51c4f8b98e 100644
--- a/pr-1699/assets/nodes_celestia-app-vesting.md.e8ca90cc.lean.js
+++ b/pr-1699/assets/nodes_celestia-app-vesting.md.e829dc7e.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"How to create a vesting account with celestia-app","description":"Learn how to generate a vesting account using celestia-app.","frontmatter":{"description":"Learn how to generate a vesting account using celestia-app.","head":[["meta",{"name":"og:title","content":"How to create a vesting account with celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-vesting.md","filePath":"nodes/celestia-app-vesting.md","lastUpdated":1725971357000}'),l={name:"nodes/celestia-app-vesting.md"},p=o("",98),e=[p];function t(c,r,y,E,i,F){return a(),n("div",null,e)}const h=s(l,[["render",t]]);export{u as __pageData,h as default};
+import{_ as s,o as a,c as n,Q as o}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"How to create a vesting account with celestia-app","description":"Learn how to generate a vesting account using celestia-app.","frontmatter":{"description":"Learn how to generate a vesting account using celestia-app.","head":[["meta",{"name":"og:title","content":"How to create a vesting account with celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-vesting.md","filePath":"nodes/celestia-app-vesting.md","lastUpdated":1725992025000}'),l={name:"nodes/celestia-app-vesting.md"},p=o("",98),e=[p];function t(c,r,y,E,i,F){return a(),n("div",null,e)}const h=s(l,[["render",t]]);export{u as __pageData,h as default};
diff --git a/pr-1699/assets/nodes_celestia-app-wallet.md.47e26967.js b/pr-1699/assets/nodes_celestia-app-wallet.md.70b5fba3.js
similarity index 99%
rename from pr-1699/assets/nodes_celestia-app-wallet.md.47e26967.js
rename to pr-1699/assets/nodes_celestia-app-wallet.md.70b5fba3.js
index 65a3be6238..9ac74204fb 100644
--- a/pr-1699/assets/nodes_celestia-app-wallet.md.47e26967.js
+++ b/pr-1699/assets/nodes_celestia-app-wallet.md.70b5fba3.js
@@ -1,3 +1,3 @@
-import{_ as a,o as e,c as s,Q as t}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Create a wallet with celestia-app","description":"Learn how to generate a Celestia wallet using celestia-app.","frontmatter":{"description":"Learn how to generate a Celestia wallet using celestia-app.","head":[["meta",{"name":"og:title","content":"Create a wallet with celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-wallet.md","filePath":"nodes/celestia-app-wallet.md","lastUpdated":1725971357000}'),l={name:"nodes/celestia-app-wallet.md"},o=t(`
        Create a wallet with celestia-app ​
        For this guide, we will go over how you can generate a Celestia wallet using celestia-app.
        Prerequisites ​
        Note, you do not need to install celestia-node for this tutorial.
        Create a wallet ​
        First, create an application CLI configuration file:
        sh
        celestia-appd config keyring-backend test
        celestia-appd config keyring-backend test
        You can pick whatever wallet name you want. For our example we used "validator" as the wallet name:
        sh
        celestia-appd keys add validator --interactive
        celestia-appd keys add validator --interactive
        Save the mnemonic output as this is the only way to recover your validator wallet in case you lose it!
        To check all your wallets you can run:
        sh
        celestia-appd keys list
        celestia-appd keys list
        Fund a wallet ​
        For the public celestia address, you can fund the previously created wallet via Discord by sending this message to either the #mocha-faucet or #arabica-faucet channel:
        text
        $request celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
        $request celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
        Wait to see if you get a confirmation that the tokens have been successfully sent. To check if tokens have arrived successfully to the destination wallet run the command below replacing the public address with your own:
        sh
        celestia-appd start
+import{_ as a,o as e,c as s,Q as t}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Create a wallet with celestia-app","description":"Learn how to generate a Celestia wallet using celestia-app.","frontmatter":{"description":"Learn how to generate a Celestia wallet using celestia-app.","head":[["meta",{"name":"og:title","content":"Create a wallet with celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-wallet.md","filePath":"nodes/celestia-app-wallet.md","lastUpdated":1725992025000}'),l={name:"nodes/celestia-app-wallet.md"},o=t(`
        Create a wallet with celestia-app ​
        For this guide, we will go over how you can generate a Celestia wallet using celestia-app.
        Prerequisites ​
        Note, you do not need to install celestia-node for this tutorial.
        Create a wallet ​
        First, create an application CLI configuration file:
        sh
        celestia-appd config keyring-backend test
        celestia-appd config keyring-backend test
        You can pick whatever wallet name you want. For our example we used "validator" as the wallet name:
        sh
        celestia-appd keys add validator --interactive
        celestia-appd keys add validator --interactive
        Save the mnemonic output as this is the only way to recover your validator wallet in case you lose it!
        To check all your wallets you can run:
        sh
        celestia-appd keys list
        celestia-appd keys list
        Fund a wallet ​
        For the public celestia address, you can fund the previously created wallet via Discord by sending this message to either the #mocha-faucet or #arabica-faucet channel:
        text
        $request celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
        $request celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
        Wait to see if you get a confirmation that the tokens have been successfully sent. To check if tokens have arrived successfully to the destination wallet run the command below replacing the public address with your own:
        sh
        celestia-appd start
 celestia-appd query bank balances celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
        celestia-appd start
 celestia-appd query bank balances celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
        TIP
        Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.
        `,19),n=[o];function p(c,r,i,x,d,h){return e(),s("div",null,n)}const E=a(l,[["render",p]]);export{u as __pageData,E as default};
diff --git a/pr-1699/assets/nodes_celestia-app-wallet.md.47e26967.lean.js b/pr-1699/assets/nodes_celestia-app-wallet.md.70b5fba3.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_celestia-app-wallet.md.47e26967.lean.js
rename to pr-1699/assets/nodes_celestia-app-wallet.md.70b5fba3.lean.js
index a82453b78d..5debe475be 100644
--- a/pr-1699/assets/nodes_celestia-app-wallet.md.47e26967.lean.js
+++ b/pr-1699/assets/nodes_celestia-app-wallet.md.70b5fba3.lean.js
@@ -1 +1 @@
-import{_ as a,o as e,c as s,Q as t}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Create a wallet with celestia-app","description":"Learn how to generate a Celestia wallet using celestia-app.","frontmatter":{"description":"Learn how to generate a Celestia wallet using celestia-app.","head":[["meta",{"name":"og:title","content":"Create a wallet with celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-wallet.md","filePath":"nodes/celestia-app-wallet.md","lastUpdated":1725971357000}'),l={name:"nodes/celestia-app-wallet.md"},o=t("",19),n=[o];function p(c,r,i,x,d,h){return e(),s("div",null,n)}const E=a(l,[["render",p]]);export{u as __pageData,E as default};
+import{_ as a,o as e,c as s,Q as t}from"./chunks/framework.b47e54aa.js";const u=JSON.parse('{"title":"Create a wallet with celestia-app","description":"Learn how to generate a Celestia wallet using celestia-app.","frontmatter":{"description":"Learn how to generate a Celestia wallet using celestia-app.","head":[["meta",{"name":"og:title","content":"Create a wallet with celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app-wallet.md","filePath":"nodes/celestia-app-wallet.md","lastUpdated":1725992025000}'),l={name:"nodes/celestia-app-wallet.md"},o=t("",19),n=[o];function p(c,r,i,x,d,h){return e(),s("div",null,n)}const E=a(l,[["render",p]]);export{u as __pageData,E as default};
diff --git a/pr-1699/assets/nodes_celestia-app.md.6fd2fd36.js b/pr-1699/assets/nodes_celestia-app.md.e09a3b72.js
similarity index 82%
rename from pr-1699/assets/nodes_celestia-app.md.6fd2fd36.js
rename to pr-1699/assets/nodes_celestia-app.md.e09a3b72.js
index 67e00cfbe5..c87309b912 100644
--- a/pr-1699/assets/nodes_celestia-app.md.6fd2fd36.js
+++ b/pr-1699/assets/nodes_celestia-app.md.e09a3b72.js
@@ -4,4 +4,4 @@ import{a as o}from"./chunks/arabica_versions.1930378b.js";import{m as l}from"./c
 cd celestia-app
        cd $HOME
 rm -rf celestia-app
 git clone https://github.com/celestiaorg/celestia-app.git
-cd celestia-app
        20. `,1),d=s("p",null,"Check out to the desired version, based on the network you will use:",-1),h={class:"vp-code-group vp-adaptive-theme"},_=a('
        ',1),u={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},b=s("button",{title:"Copy Code",class:"copy"},null,-1),g=s("span",{class:"lang"},"bash",-1),E={class:"shiki github-dark vp-code-dark"},m={class:"line"},F=s("span",{style:{color:"#B392F0"}},"git",-1),C=s("span",{style:{color:"#E1E4E8"}}," ",-1),v=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),f=s("span",{style:{color:"#E1E4E8"}}," ",-1),k={style:{color:"#9ECBFF"}},T={class:"shiki github-light vp-code-light"},w={class:"line"},B=s("span",{style:{color:"#6F42C1"}},"git",-1),P=s("span",{style:{color:"#24292E"}}," ",-1),A=s("span",{style:{color:"#032F62"}},"checkout",-1),I=s("span",{style:{color:"#24292E"}}," ",-1),V={style:{color:"#032F62"}},S={class:"language-bash vp-adaptive-theme"},L=s("button",{title:"Copy Code",class:"copy"},null,-1),q=s("span",{class:"lang"},"bash",-1),D={class:"shiki github-dark vp-code-dark"},x={class:"line"},M=s("span",{style:{color:"#B392F0"}},"git",-1),N=s("span",{style:{color:"#E1E4E8"}}," ",-1),R=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),H=s("span",{style:{color:"#E1E4E8"}}," ",-1),O={style:{color:"#9ECBFF"}},$={class:"shiki github-light vp-code-light"},W={class:"line"},j=s("span",{style:{color:"#6F42C1"}},"git",-1),J=s("span",{style:{color:"#24292E"}}," ",-1),Q=s("span",{style:{color:"#032F62"}},"checkout",-1),X=s("span",{style:{color:"#24292E"}}," ",-1),K={style:{color:"#032F62"}},U={class:"language-bash vp-adaptive-theme"},Y=s("button",{title:"Copy Code",class:"copy"},null,-1),Z=s("span",{class:"lang"},"bash",-1),z={class:"shiki github-dark vp-code-dark"},G={class:"line"},ss=s("span",{style:{color:"#B392F0"}},"git",-1),es=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),as=s("span",{style:{color:"#E1E4E8"}}," ",-1),os={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ns={class:"line"},ps=s("span",{style:{color:"#6F42C1"}},"git",-1),cs=s("span",{style:{color:"#24292E"}}," ",-1),is=s("span",{style:{color:"#032F62"}},"checkout",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),ds={style:{color:"#032F62"}},hs=a('
      20. Build and install the celestia-appd binary:
        bash
        make install
        make install
      21. To check if the binary was successfully installed you can run the binary using the --help flag:
        sh
        celestia-appd --help
        celestia-appd --help
        22. ',2),_s=a('
        You will see an output with the menu for celestia-appd. Learn more on the helpful CLI commands page
        Installing a pre-built binary ​
        Installing a pre-built binary is the fastest way to get started with your Celestia consensus node. Releases after celestia-app v1.3.0 should have these binaries available.
        The steps below will download a binary file named celestia-appd. Depending on the setup that you choose during installation, the celestia-appd binary will be available at either:
        • $HOME/celestia-app-temp/celestia-appd
        • /usr/local/bin/celestia-appd
        Pre-built binaries are available for:
        • Operating systems: Darwin (Apple), Linux
        • Architectures: x86_64 (amd64), arm64
        To install the latest pre-built binary you can run this command in your terminal:
        bash
        bash -c "$(curl -sL https://docs.celestia.org/celestia-app.sh)"
        bash -c "$(curl -sL https://docs.celestia.org/celestia-app.sh)"
        Follow the instructions in the terminal output to choose your installation preferences.
        You will see an output with the menu for celestia-appd. Learn more on the helpful CLI commands page
        View the script to learn more about what it is doing.
        Ports ​
        When interacting with a consensus node, you may need to open ports on your machine to allow communication between nodes, such as bridge nodes. It is essential that specific ports are accessible. Make sure that your firewall allows connections to the correct ports.
        If you run a node on a cloud server, make sure that the ports are open on the server's firewall. If you run a node at home, make sure that your router allows connections to the correct ports.
        For example, validator ports 9090 and 26657 need to be accessible by the bridge, and port 2121 is required for P2P connections for all node types.
        The following ports are used by Celestia app nodes:
        PortProtocolAddressDescriptionEnabled by default on nodeFlag
        2121TCP/UDPlocalhostP2PtrueN/A
        9090HTTP0.0.0.0gRPCtrue--grpc.address string
        26657TCPlocalhostRPCfalse (only open to localhost)--rpc.laddr string
        ',18),vs=JSON.parse('{"title":"Install celestia-app","description":"Learn how you can build celestia-app.","frontmatter":{"description":"Learn how you can build celestia-app.","head":[["meta",{"name":"og:title","content":"Install celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app.md","filePath":"nodes/celestia-app.md","lastUpdated":1725971357000}'),us={name:"nodes/celestia-app.md"},fs=Object.assign(us,{setup(ys){return(bs,gs)=>(p(),c("div",null,[i,s("ol",null,[r,s("li",null,[d,s("div",h,[_,s("div",u,[s("div",y,[b,g,s("pre",E,[s("code",null,[s("span",m,[F,C,v,f,s("span",k,"tags/"+e(t(n)["app-latest-tag"]),1)])])]),s("pre",T,[s("code",null,[s("span",w,[B,P,A,I,s("span",V,"tags/"+e(t(n)["app-latest-tag"]),1)])])])]),s("div",S,[L,q,s("pre",D,[s("code",null,[s("span",x,[M,N,R,H,s("span",O,"tags/"+e(t(l)["app-latest-tag"]),1)])])]),s("pre",$,[s("code",null,[s("span",W,[j,J,Q,X,s("span",K,"tags/"+e(t(l)["app-latest-tag"]),1)])])])]),s("div",U,[Y,Z,s("pre",z,[s("code",null,[s("span",G,[ss,es,ts,as,s("span",os,"tags/"+e(t(o)["app-latest-tag"]),1)])])]),s("pre",ls,[s("code",null,[s("span",ns,[ps,cs,is,rs,s("span",ds,"tags/"+e(t(o)["app-latest-tag"]),1)])])])])])])]),hs]),_s]))}});export{vs as __pageData,fs as default};
+cd celestia-app
      2. `,1),d=s("p",null,"Check out to the desired version, based on the network you will use:",-1),h={class:"vp-code-group vp-adaptive-theme"},_=a('
      ',1),u={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},b=s("button",{title:"Copy Code",class:"copy"},null,-1),g=s("span",{class:"lang"},"bash",-1),m={class:"shiki github-dark vp-code-dark"},E={class:"line"},F=s("span",{style:{color:"#B392F0"}},"git",-1),C=s("span",{style:{color:"#E1E4E8"}}," ",-1),v=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),f=s("span",{style:{color:"#E1E4E8"}}," ",-1),k={style:{color:"#9ECBFF"}},T={class:"shiki github-light vp-code-light"},B={class:"line"},w=s("span",{style:{color:"#6F42C1"}},"git",-1),P=s("span",{style:{color:"#24292E"}}," ",-1),I=s("span",{style:{color:"#032F62"}},"checkout",-1),A=s("span",{style:{color:"#24292E"}}," ",-1),q={style:{color:"#032F62"}},S={class:"language-bash vp-adaptive-theme"},V=s("button",{title:"Copy Code",class:"copy"},null,-1),D=s("span",{class:"lang"},"bash",-1),x={class:"shiki github-dark vp-code-dark"},L={class:"line"},N=s("span",{style:{color:"#B392F0"}},"git",-1),R=s("span",{style:{color:"#E1E4E8"}}," ",-1),G=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),M=s("span",{style:{color:"#E1E4E8"}}," ",-1),O={style:{color:"#9ECBFF"}},J={class:"shiki github-light vp-code-light"},$={class:"line"},H=s("span",{style:{color:"#6F42C1"}},"git",-1),U=s("span",{style:{color:"#24292E"}}," ",-1),Z=s("span",{style:{color:"#032F62"}},"checkout",-1),j=s("span",{style:{color:"#24292E"}}," ",-1),z={style:{color:"#032F62"}},K={class:"language-bash vp-adaptive-theme"},Y=s("button",{title:"Copy Code",class:"copy"},null,-1),Q=s("span",{class:"lang"},"bash",-1),W={class:"shiki github-dark vp-code-dark"},X={class:"line"},ss=s("span",{style:{color:"#B392F0"}},"git",-1),es=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),as=s("span",{style:{color:"#E1E4E8"}}," ",-1),os={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ns={class:"line"},ps=s("span",{style:{color:"#6F42C1"}},"git",-1),cs=s("span",{style:{color:"#24292E"}}," ",-1),is=s("span",{style:{color:"#032F62"}},"checkout",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),ds={style:{color:"#032F62"}},hs=a('
    2. Build and install the celestia-appd binary:
      bash
      make install
      make install
    3. To check if the binary was successfully installed you can run the binary using the --help flag:
      sh
      celestia-appd --help
      celestia-appd --help
      4. ',2),_s=a('
      You will see an output with the menu for celestia-appd. Learn more on the helpful CLI commands page
      Installing a pre-built binary ​
      Installing a pre-built binary is the fastest way to get started with your Celestia consensus node. Releases after celestia-app v1.3.0 should have these binaries available.
      The steps below will download a binary file named celestia-appd. Depending on the setup that you choose during installation, the celestia-appd binary will be available at either:
      • $HOME/celestia-app-temp/celestia-appd
      • /usr/local/bin/celestia-appd
      Pre-built binaries are available for:
      • Operating systems: Darwin (Apple), Linux
      • Architectures: x86_64 (amd64), arm64
      To install the latest pre-built binary you can run this command in your terminal:
      bash
      bash -c "$(curl -sL https://docs.celestia.org/celestia-app.sh)"
      bash -c "$(curl -sL https://docs.celestia.org/celestia-app.sh)"
      Follow the instructions in the terminal output to choose your installation preferences.
      You will see an output with the menu for celestia-appd. Learn more on the helpful CLI commands page
      View the script to learn more about what it is doing.
      Ports ​
      When interacting with a consensus node, you may need to open ports on your machine to allow communication between nodes, such as bridge nodes. It is essential that specific ports are accessible. Make sure that your firewall allows connections to the correct ports.
      If you run a node on a cloud server, make sure that the ports are open on the server's firewall. If you run a node at home, make sure that your router allows connections to the correct ports.
      For example, validator ports 9090 and 26657 need to be accessible by the bridge, and port 2121 is required for P2P connections for all node types.
      The following ports are used by Celestia app nodes:
      PortProtocolAddressDescriptionEnabled by default on nodeFlag
      2121TCP/UDPlocalhostP2PtrueN/A
      9090HTTP0.0.0.0gRPCtrue--grpc.address string
      26657TCPlocalhostRPCfalse (only open to localhost)--rpc.laddr string
      ',18),vs=JSON.parse('{"title":"Install celestia-app","description":"Learn how you can build celestia-app.","frontmatter":{"description":"Learn how you can build celestia-app.","head":[["meta",{"name":"og:title","content":"Install celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app.md","filePath":"nodes/celestia-app.md","lastUpdated":1725992025000}'),us={name:"nodes/celestia-app.md"},fs=Object.assign(us,{setup(ys){return(bs,gs)=>(p(),c("div",null,[i,s("ol",null,[r,s("li",null,[d,s("div",h,[_,s("div",u,[s("div",y,[b,g,s("pre",m,[s("code",null,[s("span",E,[F,C,v,f,s("span",k,"tags/"+e(t(n)["app-latest-tag"]),1)])])]),s("pre",T,[s("code",null,[s("span",B,[w,P,I,A,s("span",q,"tags/"+e(t(n)["app-latest-tag"]),1)])])])]),s("div",S,[V,D,s("pre",x,[s("code",null,[s("span",L,[N,R,G,M,s("span",O,"tags/"+e(t(l)["app-latest-tag"]),1)])])]),s("pre",J,[s("code",null,[s("span",$,[H,U,Z,j,s("span",z,"tags/"+e(t(l)["app-latest-tag"]),1)])])])]),s("div",K,[Y,Q,s("pre",W,[s("code",null,[s("span",X,[ss,es,ts,as,s("span",os,"tags/"+e(t(o)["app-latest-tag"]),1)])])]),s("pre",ls,[s("code",null,[s("span",ns,[ps,cs,is,rs,s("span",ds,"tags/"+e(t(o)["app-latest-tag"]),1)])])])])])])]),hs]),_s]))}});export{vs as __pageData,fs as default};
diff --git a/pr-1699/assets/nodes_celestia-app.md.6fd2fd36.lean.js b/pr-1699/assets/nodes_celestia-app.md.e09a3b72.lean.js
similarity index 56%
rename from pr-1699/assets/nodes_celestia-app.md.6fd2fd36.lean.js
rename to pr-1699/assets/nodes_celestia-app.md.e09a3b72.lean.js
index e96592f667..eb504352f6 100644
--- a/pr-1699/assets/nodes_celestia-app.md.6fd2fd36.lean.js
+++ b/pr-1699/assets/nodes_celestia-app.md.e09a3b72.lean.js
@@ -1 +1 @@
-import{a as o}from"./chunks/arabica_versions.1930378b.js";import{m as l}from"./chunks/mocha_versions.7704b055.js";import{m as n}from"./chunks/mainnet_versions.1d5e6ed9.js";import{o as p,c,k as s,t as e,l as t,Q as a}from"./chunks/framework.b47e54aa.js";const i=a("",5),r=a("",1),d=s("p",null,"Check out to the desired version, based on the network you will use:",-1),h={class:"vp-code-group vp-adaptive-theme"},_=a("",1),u={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},b=s("button",{title:"Copy Code",class:"copy"},null,-1),g=s("span",{class:"lang"},"bash",-1),E={class:"shiki github-dark vp-code-dark"},m={class:"line"},F=s("span",{style:{color:"#B392F0"}},"git",-1),C=s("span",{style:{color:"#E1E4E8"}}," ",-1),v=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),f=s("span",{style:{color:"#E1E4E8"}}," ",-1),k={style:{color:"#9ECBFF"}},T={class:"shiki github-light vp-code-light"},w={class:"line"},B=s("span",{style:{color:"#6F42C1"}},"git",-1),P=s("span",{style:{color:"#24292E"}}," ",-1),A=s("span",{style:{color:"#032F62"}},"checkout",-1),I=s("span",{style:{color:"#24292E"}}," ",-1),V={style:{color:"#032F62"}},S={class:"language-bash vp-adaptive-theme"},L=s("button",{title:"Copy Code",class:"copy"},null,-1),q=s("span",{class:"lang"},"bash",-1),D={class:"shiki github-dark vp-code-dark"},x={class:"line"},M=s("span",{style:{color:"#B392F0"}},"git",-1),N=s("span",{style:{color:"#E1E4E8"}}," ",-1),R=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),H=s("span",{style:{color:"#E1E4E8"}}," ",-1),O={style:{color:"#9ECBFF"}},$={class:"shiki github-light vp-code-light"},W={class:"line"},j=s("span",{style:{color:"#6F42C1"}},"git",-1),J=s("span",{style:{color:"#24292E"}}," ",-1),Q=s("span",{style:{color:"#032F62"}},"checkout",-1),X=s("span",{style:{color:"#24292E"}}," ",-1),K={style:{color:"#032F62"}},U={class:"language-bash vp-adaptive-theme"},Y=s("button",{title:"Copy Code",class:"copy"},null,-1),Z=s("span",{class:"lang"},"bash",-1),z={class:"shiki github-dark vp-code-dark"},G={class:"line"},ss=s("span",{style:{color:"#B392F0"}},"git",-1),es=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),as=s("span",{style:{color:"#E1E4E8"}}," ",-1),os={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ns={class:"line"},ps=s("span",{style:{color:"#6F42C1"}},"git",-1),cs=s("span",{style:{color:"#24292E"}}," ",-1),is=s("span",{style:{color:"#032F62"}},"checkout",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),ds={style:{color:"#032F62"}},hs=a("",2),_s=a("",18),vs=JSON.parse('{"title":"Install celestia-app","description":"Learn how you can build celestia-app.","frontmatter":{"description":"Learn how you can build celestia-app.","head":[["meta",{"name":"og:title","content":"Install celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app.md","filePath":"nodes/celestia-app.md","lastUpdated":1725971357000}'),us={name:"nodes/celestia-app.md"},fs=Object.assign(us,{setup(ys){return(bs,gs)=>(p(),c("div",null,[i,s("ol",null,[r,s("li",null,[d,s("div",h,[_,s("div",u,[s("div",y,[b,g,s("pre",E,[s("code",null,[s("span",m,[F,C,v,f,s("span",k,"tags/"+e(t(n)["app-latest-tag"]),1)])])]),s("pre",T,[s("code",null,[s("span",w,[B,P,A,I,s("span",V,"tags/"+e(t(n)["app-latest-tag"]),1)])])])]),s("div",S,[L,q,s("pre",D,[s("code",null,[s("span",x,[M,N,R,H,s("span",O,"tags/"+e(t(l)["app-latest-tag"]),1)])])]),s("pre",$,[s("code",null,[s("span",W,[j,J,Q,X,s("span",K,"tags/"+e(t(l)["app-latest-tag"]),1)])])])]),s("div",U,[Y,Z,s("pre",z,[s("code",null,[s("span",G,[ss,es,ts,as,s("span",os,"tags/"+e(t(o)["app-latest-tag"]),1)])])]),s("pre",ls,[s("code",null,[s("span",ns,[ps,cs,is,rs,s("span",ds,"tags/"+e(t(o)["app-latest-tag"]),1)])])])])])])]),hs]),_s]))}});export{vs as __pageData,fs as default};
+import{a as o}from"./chunks/arabica_versions.1930378b.js";import{m as l}from"./chunks/mocha_versions.7704b055.js";import{m as n}from"./chunks/mainnet_versions.1d5e6ed9.js";import{o as p,c,k as s,t as e,l as t,Q as a}from"./chunks/framework.b47e54aa.js";const i=a("",5),r=a("",1),d=s("p",null,"Check out to the desired version, based on the network you will use:",-1),h={class:"vp-code-group vp-adaptive-theme"},_=a("",1),u={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},b=s("button",{title:"Copy Code",class:"copy"},null,-1),g=s("span",{class:"lang"},"bash",-1),m={class:"shiki github-dark vp-code-dark"},E={class:"line"},F=s("span",{style:{color:"#B392F0"}},"git",-1),C=s("span",{style:{color:"#E1E4E8"}}," ",-1),v=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),f=s("span",{style:{color:"#E1E4E8"}}," ",-1),k={style:{color:"#9ECBFF"}},T={class:"shiki github-light vp-code-light"},B={class:"line"},w=s("span",{style:{color:"#6F42C1"}},"git",-1),P=s("span",{style:{color:"#24292E"}}," ",-1),I=s("span",{style:{color:"#032F62"}},"checkout",-1),A=s("span",{style:{color:"#24292E"}}," ",-1),q={style:{color:"#032F62"}},S={class:"language-bash vp-adaptive-theme"},V=s("button",{title:"Copy Code",class:"copy"},null,-1),D=s("span",{class:"lang"},"bash",-1),x={class:"shiki github-dark vp-code-dark"},L={class:"line"},N=s("span",{style:{color:"#B392F0"}},"git",-1),R=s("span",{style:{color:"#E1E4E8"}}," ",-1),G=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),M=s("span",{style:{color:"#E1E4E8"}}," ",-1),O={style:{color:"#9ECBFF"}},J={class:"shiki github-light vp-code-light"},$={class:"line"},H=s("span",{style:{color:"#6F42C1"}},"git",-1),U=s("span",{style:{color:"#24292E"}}," ",-1),Z=s("span",{style:{color:"#032F62"}},"checkout",-1),j=s("span",{style:{color:"#24292E"}}," ",-1),z={style:{color:"#032F62"}},K={class:"language-bash vp-adaptive-theme"},Y=s("button",{title:"Copy Code",class:"copy"},null,-1),Q=s("span",{class:"lang"},"bash",-1),W={class:"shiki github-dark vp-code-dark"},X={class:"line"},ss=s("span",{style:{color:"#B392F0"}},"git",-1),es=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),as=s("span",{style:{color:"#E1E4E8"}}," ",-1),os={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ns={class:"line"},ps=s("span",{style:{color:"#6F42C1"}},"git",-1),cs=s("span",{style:{color:"#24292E"}}," ",-1),is=s("span",{style:{color:"#032F62"}},"checkout",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),ds={style:{color:"#032F62"}},hs=a("",2),_s=a("",18),vs=JSON.parse('{"title":"Install celestia-app","description":"Learn how you can build celestia-app.","frontmatter":{"description":"Learn how you can build celestia-app.","head":[["meta",{"name":"og:title","content":"Install celestia-app | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-app.md","filePath":"nodes/celestia-app.md","lastUpdated":1725992025000}'),us={name:"nodes/celestia-app.md"},fs=Object.assign(us,{setup(ys){return(bs,gs)=>(p(),c("div",null,[i,s("ol",null,[r,s("li",null,[d,s("div",h,[_,s("div",u,[s("div",y,[b,g,s("pre",m,[s("code",null,[s("span",E,[F,C,v,f,s("span",k,"tags/"+e(t(n)["app-latest-tag"]),1)])])]),s("pre",T,[s("code",null,[s("span",B,[w,P,I,A,s("span",q,"tags/"+e(t(n)["app-latest-tag"]),1)])])])]),s("div",S,[V,D,s("pre",x,[s("code",null,[s("span",L,[N,R,G,M,s("span",O,"tags/"+e(t(l)["app-latest-tag"]),1)])])]),s("pre",J,[s("code",null,[s("span",$,[H,U,Z,j,s("span",z,"tags/"+e(t(l)["app-latest-tag"]),1)])])])]),s("div",K,[Y,Q,s("pre",W,[s("code",null,[s("span",X,[ss,es,ts,as,s("span",os,"tags/"+e(t(o)["app-latest-tag"]),1)])])]),s("pre",ls,[s("code",null,[s("span",ns,[ps,cs,is,rs,s("span",ds,"tags/"+e(t(o)["app-latest-tag"]),1)])])])])])])]),hs]),_s]))}});export{vs as __pageData,fs as default};
diff --git a/pr-1699/assets/nodes_celestia-node-custom-networks.md.759a61e7.js b/pr-1699/assets/nodes_celestia-node-custom-networks.md.aac3b114.js
similarity index 99%
rename from pr-1699/assets/nodes_celestia-node-custom-networks.md.759a61e7.js
rename to pr-1699/assets/nodes_celestia-node-custom-networks.md.aac3b114.js
index 0ed4b67d96..084c5c6c37 100644
--- a/pr-1699/assets/nodes_celestia-node-custom-networks.md.759a61e7.js
+++ b/pr-1699/assets/nodes_celestia-node-custom-networks.md.aac3b114.js
@@ -1 +1 @@
-import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Custom networks and values","description":"Learn about custom networks and values on celestia-node.","frontmatter":{"description":"Learn about custom networks and values on celestia-node.","head":[["meta",{"name":"og:title","content":"Custom networks and values | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-custom-networks.md","filePath":"nodes/celestia-node-custom-networks.md","lastUpdated":1725971357000}'),p={name:"nodes/celestia-node-custom-networks.md"},l=n('
      Custom networks and values ​
      This section will cover importing bootstrapper IDs, chain ID, and network ID. This will allow you to import custom values for a chain that is not in the default configuration.
      If you have a custom network you can export CELESTIA_CUSTOM, which will look something like:
      bash
      export BRIDGE="/ip4/<ip-address>/tcp/2121/p2p/<node-ID>"\nexport GENESIS_HASH=<genesis-hash>\nexport NETWORK=<network-name>\nexport CELESTIA_CUSTOM="${NETWORK}:${GENESIS_HASH}:${BRIDGE}"
      export BRIDGE="/ip4/<ip-address>/tcp/2121/p2p/<node-ID>"\nexport GENESIS_HASH=<genesis-hash>\nexport NETWORK=<network-name>\nexport CELESTIA_CUSTOM="${NETWORK}:${GENESIS_HASH}:${BRIDGE}"
      Query your node ID using the RPC CLI. These values with examples would look like:
      bash
      export BRIDGE="/ip4/151.115.14.33/tcp/2121/p2p/12D3KooWKEeRtzVMPUdxYsZo2edqps6mS67n6LT5mPdULSkPSxBQ"\nexport GENESIS_HASH=580B3DFF8A7C716968161D91116A1E171F486298D582874E93714E489C9E6E88\nexport NETWORK=custom\nexport CELESTIA_CUSTOM="${NETWORK}:${GENESIS_HASH}:${BRIDGE}"
      export BRIDGE="/ip4/151.115.14.33/tcp/2121/p2p/12D3KooWKEeRtzVMPUdxYsZo2edqps6mS67n6LT5mPdULSkPSxBQ"\nexport GENESIS_HASH=580B3DFF8A7C716968161D91116A1E171F486298D582874E93714E489C9E6E88\nexport NETWORK=custom\nexport CELESTIA_CUSTOM="${NETWORK}:${GENESIS_HASH}:${BRIDGE}"
      Then, start your node with:
      bash
      celestia <node-type> start [flags...]
      celestia <node-type> start [flags...]
      ',8),e=[l];function t(c,r,E,y,i,d){return a(),o("div",null,e)}const h=s(p,[["render",t]]);export{F as __pageData,h as default};
+import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Custom networks and values","description":"Learn about custom networks and values on celestia-node.","frontmatter":{"description":"Learn about custom networks and values on celestia-node.","head":[["meta",{"name":"og:title","content":"Custom networks and values | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-custom-networks.md","filePath":"nodes/celestia-node-custom-networks.md","lastUpdated":1725992025000}'),p={name:"nodes/celestia-node-custom-networks.md"},l=n('
      Custom networks and values ​
      This section will cover importing bootstrapper IDs, chain ID, and network ID. This will allow you to import custom values for a chain that is not in the default configuration.
      If you have a custom network you can export CELESTIA_CUSTOM, which will look something like:
      bash
      export BRIDGE="/ip4/<ip-address>/tcp/2121/p2p/<node-ID>"\nexport GENESIS_HASH=<genesis-hash>\nexport NETWORK=<network-name>\nexport CELESTIA_CUSTOM="${NETWORK}:${GENESIS_HASH}:${BRIDGE}"
      export BRIDGE="/ip4/<ip-address>/tcp/2121/p2p/<node-ID>"\nexport GENESIS_HASH=<genesis-hash>\nexport NETWORK=<network-name>\nexport CELESTIA_CUSTOM="${NETWORK}:${GENESIS_HASH}:${BRIDGE}"
      Query your node ID using the RPC CLI. These values with examples would look like:
      bash
      export BRIDGE="/ip4/151.115.14.33/tcp/2121/p2p/12D3KooWKEeRtzVMPUdxYsZo2edqps6mS67n6LT5mPdULSkPSxBQ"\nexport GENESIS_HASH=580B3DFF8A7C716968161D91116A1E171F486298D582874E93714E489C9E6E88\nexport NETWORK=custom\nexport CELESTIA_CUSTOM="${NETWORK}:${GENESIS_HASH}:${BRIDGE}"
      export BRIDGE="/ip4/151.115.14.33/tcp/2121/p2p/12D3KooWKEeRtzVMPUdxYsZo2edqps6mS67n6LT5mPdULSkPSxBQ"\nexport GENESIS_HASH=580B3DFF8A7C716968161D91116A1E171F486298D582874E93714E489C9E6E88\nexport NETWORK=custom\nexport CELESTIA_CUSTOM="${NETWORK}:${GENESIS_HASH}:${BRIDGE}"
      Then, start your node with:
      bash
      celestia <node-type> start [flags...]
      celestia <node-type> start [flags...]
      ',8),e=[l];function t(c,r,E,y,i,d){return a(),o("div",null,e)}const h=s(p,[["render",t]]);export{F as __pageData,h as default};
diff --git a/pr-1699/assets/nodes_celestia-node-custom-networks.md.759a61e7.lean.js b/pr-1699/assets/nodes_celestia-node-custom-networks.md.aac3b114.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_celestia-node-custom-networks.md.759a61e7.lean.js
rename to pr-1699/assets/nodes_celestia-node-custom-networks.md.aac3b114.lean.js
index 3ccdf6c477..fd3bd9ac59 100644
--- a/pr-1699/assets/nodes_celestia-node-custom-networks.md.759a61e7.lean.js
+++ b/pr-1699/assets/nodes_celestia-node-custom-networks.md.aac3b114.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Custom networks and values","description":"Learn about custom networks and values on celestia-node.","frontmatter":{"description":"Learn about custom networks and values on celestia-node.","head":[["meta",{"name":"og:title","content":"Custom networks and values | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-custom-networks.md","filePath":"nodes/celestia-node-custom-networks.md","lastUpdated":1725971357000}'),p={name:"nodes/celestia-node-custom-networks.md"},l=n("",8),e=[l];function t(c,r,E,y,i,d){return a(),o("div",null,e)}const h=s(p,[["render",t]]);export{F as __pageData,h as default};
+import{_ as s,o as a,c as o,Q as n}from"./chunks/framework.b47e54aa.js";const F=JSON.parse('{"title":"Custom networks and values","description":"Learn about custom networks and values on celestia-node.","frontmatter":{"description":"Learn about custom networks and values on celestia-node.","head":[["meta",{"name":"og:title","content":"Custom networks and values | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-custom-networks.md","filePath":"nodes/celestia-node-custom-networks.md","lastUpdated":1725992025000}'),p={name:"nodes/celestia-node-custom-networks.md"},l=n("",8),e=[l];function t(c,r,E,y,i,d){return a(),o("div",null,e)}const h=s(p,[["render",t]]);export{F as __pageData,h as default};
diff --git a/pr-1699/assets/nodes_celestia-node-metrics.md.6d2f305e.js b/pr-1699/assets/nodes_celestia-node-metrics.md.e49bb967.js
similarity index 99%
rename from pr-1699/assets/nodes_celestia-node-metrics.md.6d2f305e.js
rename to pr-1699/assets/nodes_celestia-node-metrics.md.e49bb967.js
index b416d27450..9084431f33 100644
--- a/pr-1699/assets/nodes_celestia-node-metrics.md.6d2f305e.js
+++ b/pr-1699/assets/nodes_celestia-node-metrics.md.e49bb967.js
@@ -1,4 +1,4 @@
-import{_ as s,o as n,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"celestia-node metrics","description":"A guide on how to run metrics for your celestia-node DA instance.","frontmatter":{"description":"A guide on how to run metrics for your celestia-node DA instance.","head":[["meta",{"name":"og:title","content":"celestia-node metrics | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-metrics.md","filePath":"nodes/celestia-node-metrics.md","lastUpdated":1725971357000}'),l={name:"nodes/celestia-node-metrics.md"},e=o(`
      celestia-node metrics ​
      This tutorial is for running metrics for your celestia-node data availability instance. This tutorial will focus on running metrics for a light node.
      This tutorial assumes you have already setup your light node by following the tutorial in the celestia-node API tutorial.
      Running metrics flags ​
      You can enable the celestia-node metric flags with the following command:
      sh
      celestia <node-type> start --metrics.tls=<boolean> \\
+import{_ as s,o as n,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"celestia-node metrics","description":"A guide on how to run metrics for your celestia-node DA instance.","frontmatter":{"description":"A guide on how to run metrics for your celestia-node DA instance.","head":[["meta",{"name":"og:title","content":"celestia-node metrics | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-metrics.md","filePath":"nodes/celestia-node-metrics.md","lastUpdated":1725992025000}'),l={name:"nodes/celestia-node-metrics.md"},e=o(`
      celestia-node metrics ​
      This tutorial is for running metrics for your celestia-node data availability instance. This tutorial will focus on running metrics for a light node.
      This tutorial assumes you have already setup your light node by following the tutorial in the celestia-node API tutorial.
      Running metrics flags ​
      You can enable the celestia-node metric flags with the following command:
      sh
      celestia <node-type> start --metrics.tls=<boolean> \\
     --metrics --metrics.endpoint <URI> \\
     --p2p.network <network> --core.ip <URI>
      celestia <node-type> start --metrics.tls=<boolean> \\
     --metrics --metrics.endpoint <URI> \\
diff --git a/pr-1699/assets/nodes_celestia-node-metrics.md.6d2f305e.lean.js b/pr-1699/assets/nodes_celestia-node-metrics.md.e49bb967.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_celestia-node-metrics.md.6d2f305e.lean.js
rename to pr-1699/assets/nodes_celestia-node-metrics.md.e49bb967.lean.js
index b419432690..e0b3bc4049 100644
--- a/pr-1699/assets/nodes_celestia-node-metrics.md.6d2f305e.lean.js
+++ b/pr-1699/assets/nodes_celestia-node-metrics.md.e49bb967.lean.js
@@ -1 +1 @@
-import{_ as s,o as n,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"celestia-node metrics","description":"A guide on how to run metrics for your celestia-node DA instance.","frontmatter":{"description":"A guide on how to run metrics for your celestia-node DA instance.","head":[["meta",{"name":"og:title","content":"celestia-node metrics | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-metrics.md","filePath":"nodes/celestia-node-metrics.md","lastUpdated":1725971357000}'),l={name:"nodes/celestia-node-metrics.md"},e=o("",27),p=[e];function t(c,r,y,i,E,d){return n(),a("div",null,p)}const m=s(l,[["render",t]]);export{h as __pageData,m as default};
+import{_ as s,o as n,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"celestia-node metrics","description":"A guide on how to run metrics for your celestia-node DA instance.","frontmatter":{"description":"A guide on how to run metrics for your celestia-node DA instance.","head":[["meta",{"name":"og:title","content":"celestia-node metrics | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-metrics.md","filePath":"nodes/celestia-node-metrics.md","lastUpdated":1725992025000}'),l={name:"nodes/celestia-node-metrics.md"},e=o("",27),p=[e];function t(c,r,y,i,E,d){return n(),a("div",null,p)}const m=s(l,[["render",t]]);export{h as __pageData,m as default};
diff --git a/pr-1699/assets/nodes_celestia-node-troubleshooting.md.6134a7ab.js b/pr-1699/assets/nodes_celestia-node-troubleshooting.md.d5102d28.js
similarity index 99%
rename from pr-1699/assets/nodes_celestia-node-troubleshooting.md.6134a7ab.js
rename to pr-1699/assets/nodes_celestia-node-troubleshooting.md.d5102d28.js
index ecd9ca4434..bdc5167be1 100644
--- a/pr-1699/assets/nodes_celestia-node-troubleshooting.md.6134a7ab.js
+++ b/pr-1699/assets/nodes_celestia-node-troubleshooting.md.d5102d28.js
@@ -58,4 +58,4 @@ import{c as n}from"./chunks/constants.295fc0ab.js";import{o as p,c as t,k as s,a
 ...
      [Service]
 ...
 LimitNOFILE=1400000
-...
      NOTE
      Be cautious when increasing file descriptor limits. Setting this value too high might affect system performance. Ensure the value is appropriate for your system's capabilities.
      1. Reload daemon and restart bridge service:
      bash
      sudo systemctl daemon-reload
      sudo systemctl daemon-reload
      bash
      sudo systemctl restart celestia-bridge
      sudo systemctl restart celestia-bridge
      `,70),A=JSON.parse('{"title":"Troubleshooting","description":"A guide to troubleshooting common issues with Celestia Node.","frontmatter":{"description":"A guide to troubleshooting common issues with Celestia Node.","next":{"text":"Metrics, visualization, and alerts","link":"nodes/celestia-app-metrics"},"head":[["meta",{"name":"og:title","content":"Troubleshooting | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-troubleshooting.md","filePath":"nodes/celestia-node-troubleshooting.md","lastUpdated":1725971357000}'),b={name:"nodes/celestia-node-troubleshooting.md"},w=Object.assign(b,{setup(B){return(m,k)=>(p(),t("div",null,[r,s("p",null,[a("When interacting with celestia-node, it is important to take into account the different chain IDs for different networks. For Mainnet Beta, there is no need to declare a chain ID, as the default is "+o(l(n).mainnetChainId)+", ",1),c,a(" no "),i,a(" flag is required for Mainnet Beta.")]),s("table",null,[y,s("tbody",null,[s("tr",null,[E,s("td",null,o(l(n).mainnetChainId),1),d]),s("tr",null,[h,s("td",null,o(l(n).mochaChainId),1),F]),s("tr",null,[u,s("td",null,o(l(n).arabicaChainId),1),g])])]),C]))}});export{A as __pageData,w as default};
+...
      NOTE
      Be cautious when increasing file descriptor limits. Setting this value too high might affect system performance. Ensure the value is appropriate for your system's capabilities.
      1. Reload daemon and restart bridge service:
      bash
      sudo systemctl daemon-reload
      sudo systemctl daemon-reload
      bash
      sudo systemctl restart celestia-bridge
      sudo systemctl restart celestia-bridge
      `,70),A=JSON.parse('{"title":"Troubleshooting","description":"A guide to troubleshooting common issues with Celestia Node.","frontmatter":{"description":"A guide to troubleshooting common issues with Celestia Node.","next":{"text":"Metrics, visualization, and alerts","link":"nodes/celestia-app-metrics"},"head":[["meta",{"name":"og:title","content":"Troubleshooting | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-troubleshooting.md","filePath":"nodes/celestia-node-troubleshooting.md","lastUpdated":1725992025000}'),b={name:"nodes/celestia-node-troubleshooting.md"},w=Object.assign(b,{setup(B){return(m,k)=>(p(),t("div",null,[r,s("p",null,[a("When interacting with celestia-node, it is important to take into account the different chain IDs for different networks. For Mainnet Beta, there is no need to declare a chain ID, as the default is "+o(l(n).mainnetChainId)+", ",1),c,a(" no "),i,a(" flag is required for Mainnet Beta.")]),s("table",null,[y,s("tbody",null,[s("tr",null,[E,s("td",null,o(l(n).mainnetChainId),1),d]),s("tr",null,[h,s("td",null,o(l(n).mochaChainId),1),F]),s("tr",null,[u,s("td",null,o(l(n).arabicaChainId),1),g])])]),C]))}});export{A as __pageData,w as default};
diff --git a/pr-1699/assets/nodes_celestia-node-troubleshooting.md.6134a7ab.lean.js b/pr-1699/assets/nodes_celestia-node-troubleshooting.md.d5102d28.lean.js
similarity index 96%
rename from pr-1699/assets/nodes_celestia-node-troubleshooting.md.6134a7ab.lean.js
rename to pr-1699/assets/nodes_celestia-node-troubleshooting.md.d5102d28.lean.js
index d445866262..00ebb9c9f8 100644
--- a/pr-1699/assets/nodes_celestia-node-troubleshooting.md.6134a7ab.lean.js
+++ b/pr-1699/assets/nodes_celestia-node-troubleshooting.md.d5102d28.lean.js
@@ -1 +1 @@
-import{c as n}from"./chunks/constants.295fc0ab.js";import{o as p,c as t,k as s,a,t as o,l,Q as e}from"./chunks/framework.b47e54aa.js";const r=e("",7),c=s("em",null,"i.e.",-1),i=s("code",null,"--p2p.network string",-1),y=s("thead",null,[s("tr",null,[s("th",null,"Network"),s("th",null,"Chain ID"),s("th",null,[s("code",null,"--p2p.network string")])])],-1),E=s("td",null,"Mainnet Beta",-1),d=s("td",null,[a("not required ("),s("code",null,"--p2p.network celestia"),a(")")],-1),h=s("td",null,"Mocha",-1),F=s("td",null,[s("code",null,"--p2p.network mocha")],-1),u=s("td",null,"Arabica",-1),g=s("td",null,[s("code",null,"--p2p.network arabica")],-1),C=e("",70),A=JSON.parse('{"title":"Troubleshooting","description":"A guide to troubleshooting common issues with Celestia Node.","frontmatter":{"description":"A guide to troubleshooting common issues with Celestia Node.","next":{"text":"Metrics, visualization, and alerts","link":"nodes/celestia-app-metrics"},"head":[["meta",{"name":"og:title","content":"Troubleshooting | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-troubleshooting.md","filePath":"nodes/celestia-node-troubleshooting.md","lastUpdated":1725971357000}'),b={name:"nodes/celestia-node-troubleshooting.md"},w=Object.assign(b,{setup(B){return(m,k)=>(p(),t("div",null,[r,s("p",null,[a("When interacting with celestia-node, it is important to take into account the different chain IDs for different networks. For Mainnet Beta, there is no need to declare a chain ID, as the default is "+o(l(n).mainnetChainId)+", ",1),c,a(" no "),i,a(" flag is required for Mainnet Beta.")]),s("table",null,[y,s("tbody",null,[s("tr",null,[E,s("td",null,o(l(n).mainnetChainId),1),d]),s("tr",null,[h,s("td",null,o(l(n).mochaChainId),1),F]),s("tr",null,[u,s("td",null,o(l(n).arabicaChainId),1),g])])]),C]))}});export{A as __pageData,w as default};
+import{c as n}from"./chunks/constants.295fc0ab.js";import{o as p,c as t,k as s,a,t as o,l,Q as e}from"./chunks/framework.b47e54aa.js";const r=e("",7),c=s("em",null,"i.e.",-1),i=s("code",null,"--p2p.network string",-1),y=s("thead",null,[s("tr",null,[s("th",null,"Network"),s("th",null,"Chain ID"),s("th",null,[s("code",null,"--p2p.network string")])])],-1),E=s("td",null,"Mainnet Beta",-1),d=s("td",null,[a("not required ("),s("code",null,"--p2p.network celestia"),a(")")],-1),h=s("td",null,"Mocha",-1),F=s("td",null,[s("code",null,"--p2p.network mocha")],-1),u=s("td",null,"Arabica",-1),g=s("td",null,[s("code",null,"--p2p.network arabica")],-1),C=e("",70),A=JSON.parse('{"title":"Troubleshooting","description":"A guide to troubleshooting common issues with Celestia Node.","frontmatter":{"description":"A guide to troubleshooting common issues with Celestia Node.","next":{"text":"Metrics, visualization, and alerts","link":"nodes/celestia-app-metrics"},"head":[["meta",{"name":"og:title","content":"Troubleshooting | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-troubleshooting.md","filePath":"nodes/celestia-node-troubleshooting.md","lastUpdated":1725992025000}'),b={name:"nodes/celestia-node-troubleshooting.md"},w=Object.assign(b,{setup(B){return(m,k)=>(p(),t("div",null,[r,s("p",null,[a("When interacting with celestia-node, it is important to take into account the different chain IDs for different networks. For Mainnet Beta, there is no need to declare a chain ID, as the default is "+o(l(n).mainnetChainId)+", ",1),c,a(" no "),i,a(" flag is required for Mainnet Beta.")]),s("table",null,[y,s("tbody",null,[s("tr",null,[E,s("td",null,o(l(n).mainnetChainId),1),d]),s("tr",null,[h,s("td",null,o(l(n).mochaChainId),1),F]),s("tr",null,[u,s("td",null,o(l(n).arabicaChainId),1),g])])]),C]))}});export{A as __pageData,w as default};
diff --git a/pr-1699/assets/nodes_celestia-node-trusted-hash.md.4094be4e.js b/pr-1699/assets/nodes_celestia-node-trusted-hash.md.941c6f87.js
similarity index 99%
rename from pr-1699/assets/nodes_celestia-node-trusted-hash.md.4094be4e.js
rename to pr-1699/assets/nodes_celestia-node-trusted-hash.md.941c6f87.js
index b7a813afe4..5a36b546d6 100644
--- a/pr-1699/assets/nodes_celestia-node-trusted-hash.md.4094be4e.js
+++ b/pr-1699/assets/nodes_celestia-node-trusted-hash.md.941c6f87.js
@@ -1,3 +1,3 @@
-import{_ as s,o as a,c as e,Q as o}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Syncing a light node from a trusted hash","description":"How to sync a light node from a trusted hash.","frontmatter":{"description":"How to sync a light node from a trusted hash.","head":[["meta",{"name":"og:title","content":"Syncing a light node from a trusted hash | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-trusted-hash.md","filePath":"nodes/celestia-node-trusted-hash.md","lastUpdated":1725971357000}'),t={name:"nodes/celestia-node-trusted-hash.md"},n=o(`
      Syncing a light node from a trusted hash ​
      This guide goes over how to sync a DA light node from a trusted hash. The example is with Mainnet Beta. You will need to adjust the commands accordingly for Mocha, Arabica, or a custom network.
      WARNING
      Syncing to a trusted hash means that you will not sample the entire chain. This adds a trust assumption that you trust the history of the chain up to that point and that you trust the entity where you get the hash from. In this example, the trusted entity is a consensus endpoint or Celenium
      1. Get trusted height & hash from a consensus endpoint or Celenium.
      2. Initialize the node store
        sh
        celestia light init --p2p.network <network>
        celestia light init --p2p.network <network>
      3. Set the trusted height & hash
        1. Open your config.toml at .celestia-light/config.toml (or .celestia-light-<other-network>/config.toml)
        2. Set DASer.SampleFrom to the trusted height (e.g. SampleFrom = 123456)
      4. Run the node with the hash and flag:
      sh
      celestia light start --headers.trusted-hash <hash_of_block_n> \\
+import{_ as s,o as a,c as e,Q as o}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Syncing a light node from a trusted hash","description":"How to sync a light node from a trusted hash.","frontmatter":{"description":"How to sync a light node from a trusted hash.","head":[["meta",{"name":"og:title","content":"Syncing a light node from a trusted hash | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-trusted-hash.md","filePath":"nodes/celestia-node-trusted-hash.md","lastUpdated":1725992025000}'),t={name:"nodes/celestia-node-trusted-hash.md"},n=o(`
      Syncing a light node from a trusted hash ​
      This guide goes over how to sync a DA light node from a trusted hash. The example is with Mainnet Beta. You will need to adjust the commands accordingly for Mocha, Arabica, or a custom network.
      WARNING
      Syncing to a trusted hash means that you will not sample the entire chain. This adds a trust assumption that you trust the history of the chain up to that point and that you trust the entity where you get the hash from. In this example, the trusted entity is a consensus endpoint or Celenium
      1. Get trusted height & hash from a consensus endpoint or Celenium.
      2. Initialize the node store
        sh
        celestia light init --p2p.network <network>
        celestia light init --p2p.network <network>
      3. Set the trusted height & hash
        1. Open your config.toml at .celestia-light/config.toml (or .celestia-light-<other-network>/config.toml)
        2. Set DASer.SampleFrom to the trusted height (e.g. SampleFrom = 123456)
      4. Run the node with the hash and flag:
      sh
      celestia light start --headers.trusted-hash <hash_of_block_n> \\
     --p2p.network <network> --core.ip <consensus-node-rpc>
      celestia light start --headers.trusted-hash <hash_of_block_n> \\
     --p2p.network <network> --core.ip <consensus-node-rpc>
      For service operators ​
      If you're using multiple light nodes for similar services like tracking the same rollup, it is recommended to use the same hash and height for them all services using the same starting height.
      `,7),l=[n];function p(r,c,i,h,d,y){return a(),e("div",null,l)}const u=s(t,[["render",p]]);export{g as __pageData,u as default};
diff --git a/pr-1699/assets/nodes_celestia-node-trusted-hash.md.4094be4e.lean.js b/pr-1699/assets/nodes_celestia-node-trusted-hash.md.941c6f87.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_celestia-node-trusted-hash.md.4094be4e.lean.js
rename to pr-1699/assets/nodes_celestia-node-trusted-hash.md.941c6f87.lean.js
index 500d1ea4bb..cf2de67c35 100644
--- a/pr-1699/assets/nodes_celestia-node-trusted-hash.md.4094be4e.lean.js
+++ b/pr-1699/assets/nodes_celestia-node-trusted-hash.md.941c6f87.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as e,Q as o}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Syncing a light node from a trusted hash","description":"How to sync a light node from a trusted hash.","frontmatter":{"description":"How to sync a light node from a trusted hash.","head":[["meta",{"name":"og:title","content":"Syncing a light node from a trusted hash | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-trusted-hash.md","filePath":"nodes/celestia-node-trusted-hash.md","lastUpdated":1725971357000}'),t={name:"nodes/celestia-node-trusted-hash.md"},n=o("",7),l=[n];function p(r,c,i,h,d,y){return a(),e("div",null,l)}const u=s(t,[["render",p]]);export{g as __pageData,u as default};
+import{_ as s,o as a,c as e,Q as o}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Syncing a light node from a trusted hash","description":"How to sync a light node from a trusted hash.","frontmatter":{"description":"How to sync a light node from a trusted hash.","head":[["meta",{"name":"og:title","content":"Syncing a light node from a trusted hash | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node-trusted-hash.md","filePath":"nodes/celestia-node-trusted-hash.md","lastUpdated":1725992025000}'),t={name:"nodes/celestia-node-trusted-hash.md"},n=o("",7),l=[n];function p(r,c,i,h,d,y){return a(),e("div",null,l)}const u=s(t,[["render",p]]);export{g as __pageData,u as default};
diff --git a/pr-1699/assets/nodes_celestia-node.md.2de1eba4.js b/pr-1699/assets/nodes_celestia-node.md.b506c65d.js
similarity index 83%
rename from pr-1699/assets/nodes_celestia-node.md.2de1eba4.js
rename to pr-1699/assets/nodes_celestia-node.md.b506c65d.js
index 0f626e14a1..3c1488c542 100644
--- a/pr-1699/assets/nodes_celestia-node.md.2de1eba4.js
+++ b/pr-1699/assets/nodes_celestia-node.md.b506c65d.js
@@ -4,4 +4,4 @@ import{a as t}from"./chunks/arabica_versions.1930378b.js";import{m as l}from"./c
 cd celestia-node/
      cd $HOME
 rm -rf celestia-node
 git clone https://github.com/celestiaorg/celestia-node.git
-cd celestia-node/
      `,1),d=s("p",null,"Check out to the desired version, based on the network you will use:",-1),h={class:"vp-code-group vp-adaptive-theme"},u=o('
      ',1),_={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},b=s("button",{title:"Copy Code",class:"copy"},null,-1),g=s("span",{class:"lang"},"bash",-1),m={class:"shiki github-dark vp-code-dark"},E={class:"line"},v=s("span",{style:{color:"#B392F0"}},"git",-1),F=s("span",{style:{color:"#E1E4E8"}}," ",-1),k=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),C=s("span",{style:{color:"#E1E4E8"}}," ",-1),f={style:{color:"#9ECBFF"}},B={class:"shiki github-light vp-code-light"},T={class:"line"},w=s("span",{style:{color:"#6F42C1"}},"git",-1),I=s("span",{style:{color:"#24292E"}}," ",-1),A=s("span",{style:{color:"#032F62"}},"checkout",-1),P=s("span",{style:{color:"#24292E"}}," ",-1),S={style:{color:"#032F62"}},V={class:"language-bash vp-adaptive-theme"},N=s("button",{title:"Copy Code",class:"copy"},null,-1),x=s("span",{class:"lang"},"bash",-1),q={class:"shiki github-dark vp-code-dark"},D={class:"line"},R=s("span",{style:{color:"#B392F0"}},"git",-1),O=s("span",{style:{color:"#E1E4E8"}}," ",-1),L=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),M=s("span",{style:{color:"#E1E4E8"}}," ",-1),j={style:{color:"#9ECBFF"}},U={class:"shiki github-light vp-code-light"},$={class:"line"},H=s("span",{style:{color:"#6F42C1"}},"git",-1),J=s("span",{style:{color:"#24292E"}}," ",-1),G=s("span",{style:{color:"#032F62"}},"checkout",-1),X=s("span",{style:{color:"#24292E"}}," ",-1),Q={style:{color:"#032F62"}},Y={class:"language-bash vp-adaptive-theme"},z=s("button",{title:"Copy Code",class:"copy"},null,-1),K=s("span",{class:"lang"},"bash",-1),W={class:"shiki github-dark vp-code-dark"},Z={class:"line"},ss=s("span",{style:{color:"#B392F0"}},"git",-1),es=s("span",{style:{color:"#E1E4E8"}}," ",-1),as=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),os=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ns={class:"line"},is=s("span",{style:{color:"#6F42C1"}},"git",-1),cs=s("span",{style:{color:"#24292E"}}," ",-1),ps=s("span",{style:{color:"#032F62"}},"checkout",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),ds={style:{color:"#032F62"}},hs=o('
    4. Build the celestia binary:
      a. Standard build
      bash
      make build
      make build
      b. Experimental build
      OPTIONAL
      If you're a node operator comfortable with experimental features and seeking optimal performance with minimal RAM usage, this option is recommended for you.
      bash
      make build-jemalloc
      make build-jemalloc
      This build option enables CGO, and downloads and installs jemalloc. Learn more about the build command.
    5. Install the binary:
      bash
      make install
      make install
    6. Build the cel-key utility:
      bash
      make cel-key
      make cel-key
    7. Verify that the binary is working and check the version:
      bash
      celestia version
      celestia version
      8. ',4),us=o('
      The output will show the semantic version of celestia-node, commit hash, build date, system version, and Golang version.
      Installing a pre-built binary ​
      Installing a pre-built binary is the fastest way to get started with your Celestia data availability node. Releases after celestia-node v0.13.3 should have these binaries available.
      The steps below will download a binary file named celestia. Depending on the setup that you choose during installation, the celestia binary will be available at either:
      • $HOME/celestia-node-temp/celestia
      • /usr/local/bin/celestia
      Pre-built binaries are available for:
      • Operating systems: Darwin (Apple), Linux
      • Architectures: x86_64 (amd64), arm64
      To install the latest pre-built binary you can run this command in your terminal:
      bash
      bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"
      bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"
      Follow the instructions in the terminal output to choose your installation preferences.
      You will see an output with the menu for celestia.
      View the script to learn more about what it is doing.
      Next steps ​
      First, we recommend reading the overview of our node types, if you haven't yet.
      Now that you've installed Celestia Node, it's time to pick your node type and run your node!
      If you're planning to run a light node, we recommend the node RPC CLI tutorial.
      Upgrading your binary ​
      To upgrade your binary, you can install the latest version from the instructions above and restart your node. If you run into any issues, Refer to the troubleshooting section.
      ',18),ks=JSON.parse('{"title":"Install celestia-node","description":"Learn to build and install celestia-node.","frontmatter":{"description":"Learn to build and install celestia-node.","head":[["meta",{"name":"og:title","content":"Install celestia-node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node.md","filePath":"nodes/celestia-node.md","lastUpdated":1725971357000}'),_s={name:"nodes/celestia-node.md"},Cs=Object.assign(_s,{setup(ys){return(bs,gs)=>(i(),c("div",null,[p,s("ol",null,[r,s("li",null,[d,s("div",h,[u,s("div",_,[s("div",y,[b,g,s("pre",m,[s("code",null,[s("span",E,[v,F,k,C,s("span",f,"tags/"+e(a(n)["node-latest-tag"]),1)])])]),s("pre",B,[s("code",null,[s("span",T,[w,I,A,P,s("span",S,"tags/"+e(a(n)["node-latest-tag"]),1)])])])]),s("div",V,[N,x,s("pre",q,[s("code",null,[s("span",D,[R,O,L,M,s("span",j,"tags/"+e(a(l)["node-latest-tag"]),1)])])]),s("pre",U,[s("code",null,[s("span",$,[H,J,G,X,s("span",Q,"tags/"+e(a(l)["node-latest-tag"]),1)])])])]),s("div",Y,[z,K,s("pre",W,[s("code",null,[s("span",Z,[ss,es,as,os,s("span",ts,"tags/"+e(a(t)["node-latest-tag"]),1)])])]),s("pre",ls,[s("code",null,[s("span",ns,[is,cs,ps,rs,s("span",ds,"tags/"+e(a(t)["node-latest-tag"]),1)])])])])])])]),hs]),us]))}});export{ks as __pageData,Cs as default};
+cd celestia-node/
    2. `,1),d=s("p",null,"Check out to the desired version, based on the network you will use:",-1),h={class:"vp-code-group vp-adaptive-theme"},_=o('
    ',1),u={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},g=s("button",{title:"Copy Code",class:"copy"},null,-1),b=s("span",{class:"lang"},"bash",-1),m={class:"shiki github-dark vp-code-dark"},E={class:"line"},v=s("span",{style:{color:"#B392F0"}},"git",-1),F=s("span",{style:{color:"#E1E4E8"}}," ",-1),k=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),C=s("span",{style:{color:"#E1E4E8"}}," ",-1),f={style:{color:"#9ECBFF"}},B={class:"shiki github-light vp-code-light"},T={class:"line"},w=s("span",{style:{color:"#6F42C1"}},"git",-1),I=s("span",{style:{color:"#24292E"}}," ",-1),A=s("span",{style:{color:"#032F62"}},"checkout",-1),V=s("span",{style:{color:"#24292E"}}," ",-1),P={style:{color:"#032F62"}},S={class:"language-bash vp-adaptive-theme"},x=s("button",{title:"Copy Code",class:"copy"},null,-1),N=s("span",{class:"lang"},"bash",-1),q={class:"shiki github-dark vp-code-dark"},j={class:"line"},O=s("span",{style:{color:"#B392F0"}},"git",-1),D=s("span",{style:{color:"#E1E4E8"}}," ",-1),R=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),L=s("span",{style:{color:"#E1E4E8"}}," ",-1),M={style:{color:"#9ECBFF"}},H={class:"shiki github-light vp-code-light"},$={class:"line"},K=s("span",{style:{color:"#6F42C1"}},"git",-1),U=s("span",{style:{color:"#24292E"}}," ",-1),z=s("span",{style:{color:"#032F62"}},"checkout",-1),G=s("span",{style:{color:"#24292E"}}," ",-1),J={style:{color:"#032F62"}},Q={class:"language-bash vp-adaptive-theme"},Y=s("button",{title:"Copy Code",class:"copy"},null,-1),W=s("span",{class:"lang"},"bash",-1),X={class:"shiki github-dark vp-code-dark"},Z={class:"line"},ss=s("span",{style:{color:"#B392F0"}},"git",-1),es=s("span",{style:{color:"#E1E4E8"}}," ",-1),as=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),os=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ns={class:"line"},is=s("span",{style:{color:"#6F42C1"}},"git",-1),cs=s("span",{style:{color:"#24292E"}}," ",-1),ps=s("span",{style:{color:"#032F62"}},"checkout",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),ds={style:{color:"#032F62"}},hs=o('

  2. Build the celestia binary:

    a. Standard build

    bash
    make build
    make build

    b. Experimental build

    OPTIONAL

    If you're a node operator comfortable with experimental features and seeking optimal performance with minimal RAM usage, this option is recommended for you.

    bash
    make build-jemalloc
    make build-jemalloc

    This build option enables CGO, and downloads and installs jemalloc. Learn more about the build command.

  3. Install the binary:

    bash
    make install
    make install

  4. Build the cel-key utility:

    bash
    make cel-key
    make cel-key

  5. Verify that the binary is working and check the version:

    bash
    celestia version
    celestia version
    6. ',4),_s=o('

    The output will show the semantic version of celestia-node, commit hash, build date, system version, and Golang version.

    Installing a pre-built binary ​

    Installing a pre-built binary is the fastest way to get started with your Celestia data availability node. Releases after celestia-node v0.13.3 should have these binaries available.

    The steps below will download a binary file named celestia. Depending on the setup that you choose during installation, the celestia binary will be available at either:

    Pre-built binaries are available for:

    To install the latest pre-built binary you can run this command in your terminal:

    bash
    bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"
    bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"

    Follow the instructions in the terminal output to choose your installation preferences.

    You will see an output with the menu for celestia.

    View the script to learn more about what it is doing.

    Next steps ​

    First, we recommend reading the overview of our node types, if you haven't yet.

    Now that you've installed Celestia Node, it's time to pick your node type and run your node!

    If you're planning to run a light node, we recommend the node RPC CLI tutorial.

    Upgrading your binary ​

    To upgrade your binary, you can install the latest version from the instructions above and restart your node. If you run into any issues, Refer to the troubleshooting section.

    ',18),ks=JSON.parse('{"title":"Install celestia-node","description":"Learn to build and install celestia-node.","frontmatter":{"description":"Learn to build and install celestia-node.","head":[["meta",{"name":"og:title","content":"Install celestia-node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node.md","filePath":"nodes/celestia-node.md","lastUpdated":1725992025000}'),us={name:"nodes/celestia-node.md"},Cs=Object.assign(us,{setup(ys){return(gs,bs)=>(i(),c("div",null,[p,s("ol",null,[r,s("li",null,[d,s("div",h,[_,s("div",u,[s("div",y,[g,b,s("pre",m,[s("code",null,[s("span",E,[v,F,k,C,s("span",f,"tags/"+e(a(n)["node-latest-tag"]),1)])])]),s("pre",B,[s("code",null,[s("span",T,[w,I,A,V,s("span",P,"tags/"+e(a(n)["node-latest-tag"]),1)])])])]),s("div",S,[x,N,s("pre",q,[s("code",null,[s("span",j,[O,D,R,L,s("span",M,"tags/"+e(a(l)["node-latest-tag"]),1)])])]),s("pre",H,[s("code",null,[s("span",$,[K,U,z,G,s("span",J,"tags/"+e(a(l)["node-latest-tag"]),1)])])])]),s("div",Q,[Y,W,s("pre",X,[s("code",null,[s("span",Z,[ss,es,as,os,s("span",ts,"tags/"+e(a(t)["node-latest-tag"]),1)])])]),s("pre",ls,[s("code",null,[s("span",ns,[is,cs,ps,rs,s("span",ds,"tags/"+e(a(t)["node-latest-tag"]),1)])])])])])])]),hs]),_s]))}});export{ks as __pageData,Cs as default}; diff --git a/pr-1699/assets/nodes_celestia-node.md.2de1eba4.lean.js b/pr-1699/assets/nodes_celestia-node.md.b506c65d.lean.js similarity index 50% rename from pr-1699/assets/nodes_celestia-node.md.2de1eba4.lean.js rename to pr-1699/assets/nodes_celestia-node.md.b506c65d.lean.js index bc79d99289..d76b46b5c8 100644 --- a/pr-1699/assets/nodes_celestia-node.md.2de1eba4.lean.js +++ b/pr-1699/assets/nodes_celestia-node.md.b506c65d.lean.js @@ -1 +1 @@ -import{a as t}from"./chunks/arabica_versions.1930378b.js";import{m as l}from"./chunks/mocha_versions.7704b055.js";import{m as n}from"./chunks/mainnet_versions.1d5e6ed9.js";import{o as i,c,k as s,t as e,l as a,Q as o}from"./chunks/framework.b47e54aa.js";const p=o("",4),r=o("",1),d=s("p",null,"Check out to the desired version, based on the network you will use:",-1),h={class:"vp-code-group vp-adaptive-theme"},u=o("",1),_={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},b=s("button",{title:"Copy Code",class:"copy"},null,-1),g=s("span",{class:"lang"},"bash",-1),m={class:"shiki github-dark vp-code-dark"},E={class:"line"},v=s("span",{style:{color:"#B392F0"}},"git",-1),F=s("span",{style:{color:"#E1E4E8"}}," ",-1),k=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),C=s("span",{style:{color:"#E1E4E8"}}," ",-1),f={style:{color:"#9ECBFF"}},B={class:"shiki github-light vp-code-light"},T={class:"line"},w=s("span",{style:{color:"#6F42C1"}},"git",-1),I=s("span",{style:{color:"#24292E"}}," ",-1),A=s("span",{style:{color:"#032F62"}},"checkout",-1),P=s("span",{style:{color:"#24292E"}}," ",-1),S={style:{color:"#032F62"}},V={class:"language-bash vp-adaptive-theme"},N=s("button",{title:"Copy Code",class:"copy"},null,-1),x=s("span",{class:"lang"},"bash",-1),q={class:"shiki github-dark vp-code-dark"},D={class:"line"},R=s("span",{style:{color:"#B392F0"}},"git",-1),O=s("span",{style:{color:"#E1E4E8"}}," ",-1),L=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),M=s("span",{style:{color:"#E1E4E8"}}," ",-1),j={style:{color:"#9ECBFF"}},U={class:"shiki github-light vp-code-light"},$={class:"line"},H=s("span",{style:{color:"#6F42C1"}},"git",-1),J=s("span",{style:{color:"#24292E"}}," ",-1),G=s("span",{style:{color:"#032F62"}},"checkout",-1),X=s("span",{style:{color:"#24292E"}}," ",-1),Q={style:{color:"#032F62"}},Y={class:"language-bash vp-adaptive-theme"},z=s("button",{title:"Copy Code",class:"copy"},null,-1),K=s("span",{class:"lang"},"bash",-1),W={class:"shiki github-dark vp-code-dark"},Z={class:"line"},ss=s("span",{style:{color:"#B392F0"}},"git",-1),es=s("span",{style:{color:"#E1E4E8"}}," ",-1),as=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),os=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ns={class:"line"},is=s("span",{style:{color:"#6F42C1"}},"git",-1),cs=s("span",{style:{color:"#24292E"}}," ",-1),ps=s("span",{style:{color:"#032F62"}},"checkout",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),ds={style:{color:"#032F62"}},hs=o("",4),us=o("",18),ks=JSON.parse('{"title":"Install celestia-node","description":"Learn to build and install celestia-node.","frontmatter":{"description":"Learn to build and install celestia-node.","head":[["meta",{"name":"og:title","content":"Install celestia-node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node.md","filePath":"nodes/celestia-node.md","lastUpdated":1725971357000}'),_s={name:"nodes/celestia-node.md"},Cs=Object.assign(_s,{setup(ys){return(bs,gs)=>(i(),c("div",null,[p,s("ol",null,[r,s("li",null,[d,s("div",h,[u,s("div",_,[s("div",y,[b,g,s("pre",m,[s("code",null,[s("span",E,[v,F,k,C,s("span",f,"tags/"+e(a(n)["node-latest-tag"]),1)])])]),s("pre",B,[s("code",null,[s("span",T,[w,I,A,P,s("span",S,"tags/"+e(a(n)["node-latest-tag"]),1)])])])]),s("div",V,[N,x,s("pre",q,[s("code",null,[s("span",D,[R,O,L,M,s("span",j,"tags/"+e(a(l)["node-latest-tag"]),1)])])]),s("pre",U,[s("code",null,[s("span",$,[H,J,G,X,s("span",Q,"tags/"+e(a(l)["node-latest-tag"]),1)])])])]),s("div",Y,[z,K,s("pre",W,[s("code",null,[s("span",Z,[ss,es,as,os,s("span",ts,"tags/"+e(a(t)["node-latest-tag"]),1)])])]),s("pre",ls,[s("code",null,[s("span",ns,[is,cs,ps,rs,s("span",ds,"tags/"+e(a(t)["node-latest-tag"]),1)])])])])])])]),hs]),us]))}});export{ks as __pageData,Cs as default}; +import{a as t}from"./chunks/arabica_versions.1930378b.js";import{m as l}from"./chunks/mocha_versions.7704b055.js";import{m as n}from"./chunks/mainnet_versions.1d5e6ed9.js";import{o as i,c,k as s,t as e,l as a,Q as o}from"./chunks/framework.b47e54aa.js";const p=o("",4),r=o("",1),d=s("p",null,"Check out to the desired version, based on the network you will use:",-1),h={class:"vp-code-group vp-adaptive-theme"},_=o("",1),u={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},g=s("button",{title:"Copy Code",class:"copy"},null,-1),b=s("span",{class:"lang"},"bash",-1),m={class:"shiki github-dark vp-code-dark"},E={class:"line"},v=s("span",{style:{color:"#B392F0"}},"git",-1),F=s("span",{style:{color:"#E1E4E8"}}," ",-1),k=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),C=s("span",{style:{color:"#E1E4E8"}}," ",-1),f={style:{color:"#9ECBFF"}},B={class:"shiki github-light vp-code-light"},T={class:"line"},w=s("span",{style:{color:"#6F42C1"}},"git",-1),I=s("span",{style:{color:"#24292E"}}," ",-1),A=s("span",{style:{color:"#032F62"}},"checkout",-1),V=s("span",{style:{color:"#24292E"}}," ",-1),P={style:{color:"#032F62"}},S={class:"language-bash vp-adaptive-theme"},x=s("button",{title:"Copy Code",class:"copy"},null,-1),N=s("span",{class:"lang"},"bash",-1),q={class:"shiki github-dark vp-code-dark"},j={class:"line"},O=s("span",{style:{color:"#B392F0"}},"git",-1),D=s("span",{style:{color:"#E1E4E8"}}," ",-1),R=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),L=s("span",{style:{color:"#E1E4E8"}}," ",-1),M={style:{color:"#9ECBFF"}},H={class:"shiki github-light vp-code-light"},$={class:"line"},K=s("span",{style:{color:"#6F42C1"}},"git",-1),U=s("span",{style:{color:"#24292E"}}," ",-1),z=s("span",{style:{color:"#032F62"}},"checkout",-1),G=s("span",{style:{color:"#24292E"}}," ",-1),J={style:{color:"#032F62"}},Q={class:"language-bash vp-adaptive-theme"},Y=s("button",{title:"Copy Code",class:"copy"},null,-1),W=s("span",{class:"lang"},"bash",-1),X={class:"shiki github-dark vp-code-dark"},Z={class:"line"},ss=s("span",{style:{color:"#B392F0"}},"git",-1),es=s("span",{style:{color:"#E1E4E8"}}," ",-1),as=s("span",{style:{color:"#9ECBFF"}},"checkout",-1),os=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ns={class:"line"},is=s("span",{style:{color:"#6F42C1"}},"git",-1),cs=s("span",{style:{color:"#24292E"}}," ",-1),ps=s("span",{style:{color:"#032F62"}},"checkout",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),ds={style:{color:"#032F62"}},hs=o("",4),_s=o("",18),ks=JSON.parse('{"title":"Install celestia-node","description":"Learn to build and install celestia-node.","frontmatter":{"description":"Learn to build and install celestia-node.","head":[["meta",{"name":"og:title","content":"Install celestia-node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/celestia-node.md","filePath":"nodes/celestia-node.md","lastUpdated":1725992025000}'),us={name:"nodes/celestia-node.md"},Cs=Object.assign(us,{setup(ys){return(gs,bs)=>(i(),c("div",null,[p,s("ol",null,[r,s("li",null,[d,s("div",h,[_,s("div",u,[s("div",y,[g,b,s("pre",m,[s("code",null,[s("span",E,[v,F,k,C,s("span",f,"tags/"+e(a(n)["node-latest-tag"]),1)])])]),s("pre",B,[s("code",null,[s("span",T,[w,I,A,V,s("span",P,"tags/"+e(a(n)["node-latest-tag"]),1)])])])]),s("div",S,[x,N,s("pre",q,[s("code",null,[s("span",j,[O,D,R,L,s("span",M,"tags/"+e(a(l)["node-latest-tag"]),1)])])]),s("pre",H,[s("code",null,[s("span",$,[K,U,z,G,s("span",J,"tags/"+e(a(l)["node-latest-tag"]),1)])])])]),s("div",Q,[Y,W,s("pre",X,[s("code",null,[s("span",Z,[ss,es,as,os,s("span",ts,"tags/"+e(a(t)["node-latest-tag"]),1)])])]),s("pre",ls,[s("code",null,[s("span",ns,[is,cs,ps,rs,s("span",ds,"tags/"+e(a(t)["node-latest-tag"]),1)])])])])])])]),hs]),_s]))}});export{ks as __pageData,Cs as default}; diff --git a/pr-1699/assets/nodes_config-toml.md.cfad1001.js b/pr-1699/assets/nodes_config-toml.md.ea91864b.js similarity index 98% rename from pr-1699/assets/nodes_config-toml.md.cfad1001.js rename to pr-1699/assets/nodes_config-toml.md.ea91864b.js index 30d48f4f60..7fa807abc7 100644 --- a/pr-1699/assets/nodes_config-toml.md.cfad1001.js +++ b/pr-1699/assets/nodes_config-toml.md.ea91864b.js @@ -1 +1 @@ -import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"config.toml guide","description":"A guide to the contents of the Config.toml file.","frontmatter":{"description":"A guide to the contents of the Config.toml file.","head":[["meta",{"name":"og:title","content":"config.toml guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/config-toml.md","filePath":"nodes/config-toml.md","lastUpdated":1725971357000}'),i={name:"nodes/config-toml.md"},r=a('

    config.toml guide ​

    Pre-requisites ​

    Please, make sure that you have installed and initialized celestia-node

    Understanding config.toml ​

    After initialization, for any type of node, you will find a config.toml in the following path (default location):

    Let's break down some of the most used sections.

    Core ​

    This section is needed for the Celestia bridge node. By default, Remote = false. Still for devnet, we are going to use the remote core option and this can also be set by the command line flag --core.remote.

    P2P ​

    Bootstrap ​

    Bootstrappers help new nodes to find peers faster in the network. By default, the Bootstrapper = false and the BootstrapPeers is empty. If you want your node to be a bootstrapper, then activate Bootstrapper = true. BootstrapPeers are already provided by default during initialisation. If you want to add your own manually, you need to provide the multiaddresses of the peers.

    Mutual peers ​

    The purpose of this config is to set up a bidirectional communication. This is usually the case for Celestia bridge nodes. In addition, you need to change the field PeerExchange from false to true.

    Services ​

    TrustedHash and TrustedPeer ​

    TrustedHash is needed to properly initialize a Celestia bridge node with an already-running Remote celestia-core node. Celestia light node will take a genesis hash as the trusted one, if no hash is manually provided during initialization phase.

    TrustedPeers is the array of bridge nodes' peers that Celestia light node trusts. By default, bootstrap peers becomes trusted peers for Celestia light nodes if a user is not setting the trusted peer params in config file.

    Any Celestia bridge node can be a trusted peer for the light one. However, the light node by design can not be a trusted peer for another light node.

    ',19),n=[r];function d(s,l,c,h,u,f){return t(),o("div",null,n)}const m=e(i,[["render",d]]);export{g as __pageData,m as default}; +import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"config.toml guide","description":"A guide to the contents of the Config.toml file.","frontmatter":{"description":"A guide to the contents of the Config.toml file.","head":[["meta",{"name":"og:title","content":"config.toml guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/config-toml.md","filePath":"nodes/config-toml.md","lastUpdated":1725992025000}'),i={name:"nodes/config-toml.md"},r=a('

    config.toml guide ​

    Pre-requisites ​

    Please, make sure that you have installed and initialized celestia-node

    Understanding config.toml ​

    After initialization, for any type of node, you will find a config.toml in the following path (default location):

    Let's break down some of the most used sections.

    Core ​

    This section is needed for the Celestia bridge node. By default, Remote = false. Still for devnet, we are going to use the remote core option and this can also be set by the command line flag --core.remote.

    P2P ​

    Bootstrap ​

    Bootstrappers help new nodes to find peers faster in the network. By default, the Bootstrapper = false and the BootstrapPeers is empty. If you want your node to be a bootstrapper, then activate Bootstrapper = true. BootstrapPeers are already provided by default during initialisation. If you want to add your own manually, you need to provide the multiaddresses of the peers.

    Mutual peers ​

    The purpose of this config is to set up a bidirectional communication. This is usually the case for Celestia bridge nodes. In addition, you need to change the field PeerExchange from false to true.

    Services ​

    TrustedHash and TrustedPeer ​

    TrustedHash is needed to properly initialize a Celestia bridge node with an already-running Remote celestia-core node. Celestia light node will take a genesis hash as the trusted one, if no hash is manually provided during initialization phase.

    TrustedPeers is the array of bridge nodes' peers that Celestia light node trusts. By default, bootstrap peers becomes trusted peers for Celestia light nodes if a user is not setting the trusted peer params in config file.

    Any Celestia bridge node can be a trusted peer for the light one. However, the light node by design can not be a trusted peer for another light node.

    ',19),n=[r];function d(s,l,c,h,u,f){return t(),o("div",null,n)}const m=e(i,[["render",d]]);export{g as __pageData,m as default}; diff --git a/pr-1699/assets/nodes_config-toml.md.cfad1001.lean.js b/pr-1699/assets/nodes_config-toml.md.ea91864b.lean.js similarity index 90% rename from pr-1699/assets/nodes_config-toml.md.cfad1001.lean.js rename to pr-1699/assets/nodes_config-toml.md.ea91864b.lean.js index d244ecde5d..4c57a2d05a 100644 --- a/pr-1699/assets/nodes_config-toml.md.cfad1001.lean.js +++ b/pr-1699/assets/nodes_config-toml.md.ea91864b.lean.js @@ -1 +1 @@ -import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"config.toml guide","description":"A guide to the contents of the Config.toml file.","frontmatter":{"description":"A guide to the contents of the Config.toml file.","head":[["meta",{"name":"og:title","content":"config.toml guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/config-toml.md","filePath":"nodes/config-toml.md","lastUpdated":1725971357000}'),i={name:"nodes/config-toml.md"},r=a("",19),n=[r];function d(s,l,c,h,u,f){return t(),o("div",null,n)}const m=e(i,[["render",d]]);export{g as __pageData,m as default}; +import{_ as e,o as t,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"config.toml guide","description":"A guide to the contents of the Config.toml file.","frontmatter":{"description":"A guide to the contents of the Config.toml file.","head":[["meta",{"name":"og:title","content":"config.toml guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/config-toml.md","filePath":"nodes/config-toml.md","lastUpdated":1725992025000}'),i={name:"nodes/config-toml.md"},r=a("",19),n=[r];function d(s,l,c,h,u,f){return t(),o("div",null,n)}const m=e(i,[["render",d]]);export{g as __pageData,m as default}; diff --git a/pr-1699/assets/nodes_consensus-node.md.c0f03057.js b/pr-1699/assets/nodes_consensus-node.md.99f6268d.js similarity index 89% rename from pr-1699/assets/nodes_consensus-node.md.c0f03057.js rename to pr-1699/assets/nodes_consensus-node.md.99f6268d.js index a48fc023f4..7909ef3fdc 100644 --- a/pr-1699/assets/nodes_consensus-node.md.c0f03057.js +++ b/pr-1699/assets/nodes_consensus-node.md.99f6268d.js @@ -1,10 +1,10 @@ -import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,t as n,l as t,a,Q as o}from"./chunks/framework.b47e54aa.js";const c="/docs-preview/pr-1699/img/nodes/consensus-node.jpg",r=o('

    Consensus node ​

    This guide covers how to set up a consensus node on Celestia. Consensus nodes allow you to sync the entire blockchain history in the Celestia consensus layer.

    consensus node

    Minimum hardware requirements ​

    The following minimum hardware requirements are recommended for running a consensus node:

    Set up a consensus node ​

    The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.

    Set up the dependencies ​

    Follow the instructions on installing dependencies.

    Install celestia-app ​

    Follow the tutorial on installing celestia-app.

    Set up the P2P networks ​

    To initialize the network, pick a "node-name" that describes your node. Keep in mind that this might change if a new testnet is deployed.

    ',14),i={class:"vp-code-group vp-adaptive-theme"},d=o('
    ',1),_={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},h=s("button",{title:"Copy Code",class:"copy"},null,-1),E=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},F={class:"line"},C=o('celestia-appd init "node-name" --chain-id ',8),g={style:{color:"#9ECBFF"}},T={class:"shiki github-light vp-code-light"},b={class:"line"},m=o('celestia-appd init "node-name" --chain-id ',8),S={style:{color:"#032F62"}},v={class:"language-bash vp-adaptive-theme"},k=s("button",{title:"Copy Code",class:"copy"},null,-1),A=s("span",{class:"lang"},"bash",-1),B={class:"shiki github-dark vp-code-dark"},f={class:"line"},P=o('celestia-appd init "node-name" --chain-id ',8),q={style:{color:"#9ECBFF"}},I={class:"shiki github-light vp-code-light"},x={class:"line"},V=o('celestia-appd init "node-name" --chain-id ',8),D={style:{color:"#032F62"}},R={class:"language-bash vp-adaptive-theme"},w=s("button",{title:"Copy Code",class:"copy"},null,-1),N=s("span",{class:"lang"},"bash",-1),$={class:"shiki github-dark vp-code-dark"},M={class:"line"},O=o('celestia-appd init "node-name" --chain-id ',8),H={style:{color:"#9ECBFF"}},L={class:"shiki github-light vp-code-light"},j={class:"line"},z=o('celestia-appd init "node-name" --chain-id ',8),Q={style:{color:"#032F62"}},U=s("p",null,[a("Download the "),s("code",null,"genesis.json"),a(" file:")],-1),W={class:"vp-code-group vp-adaptive-theme"},X=o('
    ',1),G={class:"blocks"},J={class:"language-bash vp-adaptive-theme active"},K=s("button",{title:"Copy Code",class:"copy"},null,-1),Z=s("span",{class:"lang"},"bash",-1),Y={class:"shiki github-dark vp-code-dark"},ss={class:"line"},os=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),as=s("span",{style:{color:"#E1E4E8"}}," ",-1),es=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),ns=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ps={class:"line"},cs=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),is=s("span",{style:{color:"#032F62"}},"download-genesis",-1),ds=s("span",{style:{color:"#24292E"}}," ",-1),_s={style:{color:"#032F62"}},ys={class:"language-bash vp-adaptive-theme"},hs=s("button",{title:"Copy Code",class:"copy"},null,-1),Es=s("span",{class:"lang"},"bash",-1),us={class:"shiki github-dark vp-code-dark"},Fs={class:"line"},Cs=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),gs=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ts=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),bs=s("span",{style:{color:"#E1E4E8"}}," ",-1),ms={style:{color:"#9ECBFF"}},Ss={class:"shiki github-light vp-code-light"},vs={class:"line"},ks=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),As=s("span",{style:{color:"#24292E"}}," ",-1),Bs=s("span",{style:{color:"#032F62"}},"download-genesis",-1),fs=s("span",{style:{color:"#24292E"}}," ",-1),Ps={style:{color:"#032F62"}},qs={class:"language-bash vp-adaptive-theme"},Is=s("button",{title:"Copy Code",class:"copy"},null,-1),xs=s("span",{class:"lang"},"bash",-1),Vs={class:"shiki github-dark vp-code-dark"},Ds={class:"line"},Rs=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),ws=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ns=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),$s=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ms={style:{color:"#9ECBFF"}},Os={class:"shiki github-light vp-code-light"},Hs={class:"line"},Ls=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),js=s("span",{style:{color:"#24292E"}}," ",-1),zs=s("span",{style:{color:"#032F62"}},"download-genesis",-1),Qs=s("span",{style:{color:"#24292E"}}," ",-1),Us={style:{color:"#032F62"}},Ws=s("p",null,[a("Set seeds in the "),s("code",null,"$HOME/.celestia-app/config/config.toml"),a(" file:")],-1),Xs={class:"vp-code-group vp-adaptive-theme"},Gs=o('
    ',1),Js={class:"blocks"},Ks={class:"language-bash vp-adaptive-theme active"},Zs=s("button",{title:"Copy Code",class:"copy"},null,-1),Ys=s("span",{class:"lang"},"bash",-1),so={class:"shiki github-dark vp-code-dark"},oo={class:"line"},ao=o('SEEDS=$(curl -sL',6),eo={style:{color:"#9ECBFF"}},no=s("span",{style:{color:"#F97583"}},"|",-1),to=s("span",{style:{color:"#9ECBFF"}}," ",-1),lo=s("span",{style:{color:"#B392F0"}},"tr",-1),po=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),co=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $SEEDS")],-1),ro=o('sed -i.bak -e "s/^seeds *=.*/seeds = \\"$SEEDS\\"/" $HOME/.celestia-app/config/config.toml',1),io={class:"shiki github-light vp-code-light"},_o={class:"line"},yo=o('SEEDS=$(curl -sL',6),ho={style:{color:"#032F62"}},Eo=s("span",{style:{color:"#D73A49"}},"|",-1),uo=s("span",{style:{color:"#032F62"}}," ",-1),Fo=s("span",{style:{color:"#6F42C1"}},"tr",-1),Co=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),go=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $SEEDS")],-1),To=o('sed -i.bak -e "s/^seeds *=.*/seeds = \\"$SEEDS\\"/" $HOME/.celestia-app/config/config.toml',1),bo={class:"language-bash vp-adaptive-theme"},mo=s("button",{title:"Copy Code",class:"copy"},null,-1),So=s("span",{class:"lang"},"bash",-1),vo={class:"shiki github-dark vp-code-dark"},ko={class:"line"},Ao=o('SEEDS=$(curl -sL',6),Bo={style:{color:"#9ECBFF"}},fo=s("span",{style:{color:"#F97583"}},"|",-1),Po=s("span",{style:{color:"#9ECBFF"}}," ",-1),qo=s("span",{style:{color:"#B392F0"}},"tr",-1),Io=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),xo=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $SEEDS")],-1),Vo=o('sed -i.bak -e "s/^seeds *=.*/seeds = \\"$SEEDS\\"/" $HOME/.celestia-app/config/config.toml',1),Do={class:"shiki github-light vp-code-light"},Ro={class:"line"},wo=o('SEEDS=$(curl -sL',6),No={style:{color:"#032F62"}},$o=s("span",{style:{color:"#D73A49"}},"|",-1),Mo=s("span",{style:{color:"#032F62"}}," ",-1),Oo=s("span",{style:{color:"#6F42C1"}},"tr",-1),Ho=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),Lo=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $SEEDS")],-1),jo=o('sed -i.bak -e "s/^seeds *=.*/seeds = \\"$SEEDS\\"/" $HOME/.celestia-app/config/config.toml',1),zo=o(`
    bash
    # For Arabica, you can set seeds manually in the
+import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,t as n,l as t,a,Q as o}from"./chunks/framework.b47e54aa.js";const c="/docs-preview/pr-1699/img/nodes/consensus-node.jpg",r=o('
    Consensus node ​
    This guide covers how to set up a consensus node on Celestia. Consensus nodes allow you to sync the entire blockchain history in the Celestia consensus layer.
    consensus node
    Minimum hardware requirements ​
    The following minimum hardware requirements are recommended for running a consensus node:
    • Memory: 16 GB RAM
    • CPU: Quad-Core
    • Disk: 2 TB SSD Storage
    • Bandwidth: 1 Gbps for Download/1 Gbps for Upload
    Set up a consensus node ​
    The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.
    Set up the dependencies ​
    Follow the instructions on installing dependencies.
    Install celestia-app ​
    Follow the tutorial on installing celestia-app.
    Set up the P2P networks ​
    To initialize the network, pick a "node-name" that describes your node. Keep in mind that this might change if a new testnet is deployed.
    ',14),i={class:"vp-code-group vp-adaptive-theme"},d=o('
    ',1),_={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},h=s("button",{title:"Copy Code",class:"copy"},null,-1),E=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},F={class:"line"},C=o('celestia-appd init "node-name" --chain-id ',8),g={style:{color:"#9ECBFF"}},b={class:"shiki github-light vp-code-light"},T={class:"line"},m=o('celestia-appd init "node-name" --chain-id ',8),S={style:{color:"#032F62"}},v={class:"language-bash vp-adaptive-theme"},k=s("button",{title:"Copy Code",class:"copy"},null,-1),A=s("span",{class:"lang"},"bash",-1),B={class:"shiki github-dark vp-code-dark"},f={class:"line"},P=o('celestia-appd init "node-name" --chain-id ',8),q={style:{color:"#9ECBFF"}},I={class:"shiki github-light vp-code-light"},x={class:"line"},V=o('celestia-appd init "node-name" --chain-id ',8),R={style:{color:"#032F62"}},D={class:"language-bash vp-adaptive-theme"},w=s("button",{title:"Copy Code",class:"copy"},null,-1),N=s("span",{class:"lang"},"bash",-1),O={class:"shiki github-dark vp-code-dark"},$={class:"line"},M=o('celestia-appd init "node-name" --chain-id ',8),H={style:{color:"#9ECBFF"}},L={class:"shiki github-light vp-code-light"},Q={class:"line"},U=o('celestia-appd init "node-name" --chain-id ',8),j={style:{color:"#032F62"}},W=s("p",null,[a("Download the "),s("code",null,"genesis.json"),a(" file:")],-1),G={class:"vp-code-group vp-adaptive-theme"},X=o('
    ',1),z={class:"blocks"},Y={class:"language-bash vp-adaptive-theme active"},J=s("button",{title:"Copy Code",class:"copy"},null,-1),Z=s("span",{class:"lang"},"bash",-1),K={class:"shiki github-dark vp-code-dark"},ss={class:"line"},os=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),as=s("span",{style:{color:"#E1E4E8"}}," ",-1),es=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),ns=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ps={class:"line"},cs=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),is=s("span",{style:{color:"#032F62"}},"download-genesis",-1),ds=s("span",{style:{color:"#24292E"}}," ",-1),_s={style:{color:"#032F62"}},ys={class:"language-bash vp-adaptive-theme"},hs=s("button",{title:"Copy Code",class:"copy"},null,-1),Es=s("span",{class:"lang"},"bash",-1),us={class:"shiki github-dark vp-code-dark"},Fs={class:"line"},Cs=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),gs=s("span",{style:{color:"#E1E4E8"}}," ",-1),bs=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),Ts=s("span",{style:{color:"#E1E4E8"}}," ",-1),ms={style:{color:"#9ECBFF"}},Ss={class:"shiki github-light vp-code-light"},vs={class:"line"},ks=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),As=s("span",{style:{color:"#24292E"}}," ",-1),Bs=s("span",{style:{color:"#032F62"}},"download-genesis",-1),fs=s("span",{style:{color:"#24292E"}}," ",-1),Ps={style:{color:"#032F62"}},qs={class:"language-bash vp-adaptive-theme"},Is=s("button",{title:"Copy Code",class:"copy"},null,-1),xs=s("span",{class:"lang"},"bash",-1),Vs={class:"shiki github-dark vp-code-dark"},Rs={class:"line"},Ds=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),ws=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ns=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),Os=s("span",{style:{color:"#E1E4E8"}}," ",-1),$s={style:{color:"#9ECBFF"}},Ms={class:"shiki github-light vp-code-light"},Hs={class:"line"},Ls=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),Qs=s("span",{style:{color:"#24292E"}}," ",-1),Us=s("span",{style:{color:"#032F62"}},"download-genesis",-1),js=s("span",{style:{color:"#24292E"}}," ",-1),Ws={style:{color:"#032F62"}},Gs=s("p",null,[a("Set seeds in the "),s("code",null,"$HOME/.celestia-app/config/config.toml"),a(" file:")],-1),Xs={class:"vp-code-group vp-adaptive-theme"},zs=o('
    ',1),Ys={class:"blocks"},Js={class:"language-bash vp-adaptive-theme active"},Zs=s("button",{title:"Copy Code",class:"copy"},null,-1),Ks=s("span",{class:"lang"},"bash",-1),so={class:"shiki github-dark vp-code-dark"},oo={class:"line"},ao=o('SEEDS=$(curl -sL',6),eo={style:{color:"#9ECBFF"}},no=s("span",{style:{color:"#F97583"}},"|",-1),to=s("span",{style:{color:"#9ECBFF"}}," ",-1),lo=s("span",{style:{color:"#B392F0"}},"tr",-1),po=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),co=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $SEEDS")],-1),ro=o('sed -i.bak -e "s/^seeds *=.*/seeds = \\"$SEEDS\\"/" $HOME/.celestia-app/config/config.toml',1),io={class:"shiki github-light vp-code-light"},_o={class:"line"},yo=o('SEEDS=$(curl -sL',6),ho={style:{color:"#032F62"}},Eo=s("span",{style:{color:"#D73A49"}},"|",-1),uo=s("span",{style:{color:"#032F62"}}," ",-1),Fo=s("span",{style:{color:"#6F42C1"}},"tr",-1),Co=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),go=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $SEEDS")],-1),bo=o('sed -i.bak -e "s/^seeds *=.*/seeds = \\"$SEEDS\\"/" $HOME/.celestia-app/config/config.toml',1),To={class:"language-bash vp-adaptive-theme"},mo=s("button",{title:"Copy Code",class:"copy"},null,-1),So=s("span",{class:"lang"},"bash",-1),vo={class:"shiki github-dark vp-code-dark"},ko={class:"line"},Ao=o('SEEDS=$(curl -sL',6),Bo={style:{color:"#9ECBFF"}},fo=s("span",{style:{color:"#F97583"}},"|",-1),Po=s("span",{style:{color:"#9ECBFF"}}," ",-1),qo=s("span",{style:{color:"#B392F0"}},"tr",-1),Io=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),xo=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $SEEDS")],-1),Vo=o('sed -i.bak -e "s/^seeds *=.*/seeds = \\"$SEEDS\\"/" $HOME/.celestia-app/config/config.toml',1),Ro={class:"shiki github-light vp-code-light"},Do={class:"line"},wo=o('SEEDS=$(curl -sL',6),No={style:{color:"#032F62"}},Oo=s("span",{style:{color:"#D73A49"}},"|",-1),$o=s("span",{style:{color:"#032F62"}}," ",-1),Mo=s("span",{style:{color:"#6F42C1"}},"tr",-1),Ho=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),Lo=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $SEEDS")],-1),Qo=o('sed -i.bak -e "s/^seeds *=.*/seeds = \\"$SEEDS\\"/" $HOME/.celestia-app/config/config.toml',1),Uo=o(`
    bash
    # For Arabica, you can set seeds manually in the
 # \`$HOME/.celestia-app/config/config.toml\` file:
 # Comma separated list of seed nodes to connect to
 seeds = ""
    # For Arabica, you can set seeds manually in the
 # \`$HOME/.celestia-app/config/config.toml\` file:
 # Comma separated list of seed nodes to connect to
-seeds = ""
    `,1),Qo=o('Optional: Set persistent peers
    Optionally, you can set persistent peers in your config.toml file. If you set persistent peers, your node will always try to connect to these peers. This is useful when running a local devnet, for example, when you would always want to connect to the same local nodes in your devnet. In production, setting persistent peers is advised only if you are running a sentry node.
    You can get the persistent peers from the @cosmos/chain-registry repository (for Mainnet Beta) or @celestiaorg/networks repository repo (for Mocha and Arabica) with the following commands:
    ',3),Uo={class:"vp-code-group vp-adaptive-theme"},Wo=o('
    ',1),Xo={class:"blocks"},Go={class:"language-bash vp-adaptive-theme active"},Jo=s("button",{title:"Copy Code",class:"copy"},null,-1),Ko=s("span",{class:"lang"},"bash",-1),Zo={class:"shiki github-dark vp-code-dark"},Yo={class:"line"},sa=o('PERSISTENT_PEERS=$(curl -s',6),oa={style:{color:"#9ECBFF"}},aa=o('| jq -r '.peers.persistent_peers[].address' | tr '\\n' ',' | sed 's/,$/\\n/')',14),ea=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),na=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),ta={class:"shiki github-light vp-code-light"},la={class:"line"},pa=o('PERSISTENT_PEERS=$(curl -s',6),ca={style:{color:"#032F62"}},ra=o('| jq -r '.peers.persistent_peers[].address' | tr '\\n' ',' | sed 's/,$/\\n/')',14),ia=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),da=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),_a={class:"language-bash vp-adaptive-theme"},ya=s("button",{title:"Copy Code",class:"copy"},null,-1),ha=s("span",{class:"lang"},"bash",-1),Ea={class:"shiki github-dark vp-code-dark"},ua={class:"line"},Fa=o('PERSISTENT_PEERS=$(curl -sL',6),Ca={style:{color:"#9ECBFF"}},ga=s("span",{style:{color:"#F97583"}},"|",-1),Ta=s("span",{style:{color:"#9ECBFF"}}," ",-1),ba=s("span",{style:{color:"#B392F0"}},"tr",-1),ma=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),Sa=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),va=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),ka={class:"shiki github-light vp-code-light"},Aa={class:"line"},Ba=o('PERSISTENT_PEERS=$(curl -sL',6),fa={style:{color:"#032F62"}},Pa=s("span",{style:{color:"#D73A49"}},"|",-1),qa=s("span",{style:{color:"#032F62"}}," ",-1),Ia=s("span",{style:{color:"#6F42C1"}},"tr",-1),xa=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),Va=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),Da=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),Ra={class:"language-bash vp-adaptive-theme"},wa=s("button",{title:"Copy Code",class:"copy"},null,-1),Na=s("span",{class:"lang"},"bash",-1),$a={class:"shiki github-dark vp-code-dark"},Ma={class:"line"},Oa=o('PERSISTENT_PEERS=$(curl -sL',6),Ha={style:{color:"#9ECBFF"}},La=s("span",{style:{color:"#F97583"}},"|",-1),ja=s("span",{style:{color:"#9ECBFF"}}," ",-1),za=s("span",{style:{color:"#B392F0"}},"tr",-1),Qa=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),Ua=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),Wa=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),Xa={class:"shiki github-light vp-code-light"},Ga={class:"line"},Ja=o('PERSISTENT_PEERS=$(curl -sL',6),Ka={style:{color:"#032F62"}},Za=s("span",{style:{color:"#D73A49"}},"|",-1),Ya=s("span",{style:{color:"#032F62"}}," ",-1),se=s("span",{style:{color:"#6F42C1"}},"tr",-1),oe=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),ae=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),ee=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),ne=o(`
    Storage and pruning configurations ​
    Optional: Connect a consensus node to a bridge node ​
    If your consensus node is being connected to a celestia-node bridge node, you will need to enable transaction indexing and retain all block data. This can be achieved with the following settings in your config.toml.
    Enable transaction indexing ​
    toml
    indexer = "kv"
    indexer = "kv"
    Retain all block data ​
    And in your app.toml, min-retain-blocks should remain as the default setting of 0:
    toml
    min-retain-blocks = 0 # retain all block data, this is default setting
    min-retain-blocks = 0 # retain all block data, this is default setting
    Query transactions by hash ​
    To query transactions using their hash, transaction indexing must be turned on. Set the indexer to "kv" in your config.toml:
    toml
    indexer = "kv"
    indexer = "kv"
    Optional: Access historical state ​
    If you want to query the historical state — for example, you might want to know the balance of a Celestia wallet at a given height in the past — you should run an archive node with pruning = "nothing" in your app.toml. Note that this configuration is resource-intensive and will require significant storage:
    toml
    pruning = "nothing"
    pruning = "nothing"
    Save on storage requirements ​
    If you want to save on storage requirements, consider using pruning = "everything" in your app.toml to prune everything. If you select "everything" or "default", but still want to keep the block data, you can do so by not changing the default value of min-retain-blocks = 0 in your app.toml. A value of 0 for min-retain-blocks will keep all block data. This will prune snapshots of the state, but it will keep block data:
    toml
    pruning = "everything"
+seeds = ""
    `,1),jo=o('Optional: Set persistent peers
    Optionally, you can set persistent peers in your config.toml file. If you set persistent peers, your node will always try to connect to these peers. This is useful when running a local devnet, for example, when you would always want to connect to the same local nodes in your devnet. In production, setting persistent peers is advised only if you are running a sentry node.
    You can get the persistent peers from the @cosmos/chain-registry repository (for Mainnet Beta) or @celestiaorg/networks repository repo (for Mocha and Arabica) with the following commands:
    ',3),Wo={class:"vp-code-group vp-adaptive-theme"},Go=o('
    ',1),Xo={class:"blocks"},zo={class:"language-bash vp-adaptive-theme active"},Yo=s("button",{title:"Copy Code",class:"copy"},null,-1),Jo=s("span",{class:"lang"},"bash",-1),Zo={class:"shiki github-dark vp-code-dark"},Ko={class:"line"},sa=o('PERSISTENT_PEERS=$(curl -s',6),oa={style:{color:"#9ECBFF"}},aa=o('| jq -r '.peers.persistent_peers[].address' | tr '\\n' ',' | sed 's/,$/\\n/')',14),ea=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),na=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),ta={class:"shiki github-light vp-code-light"},la={class:"line"},pa=o('PERSISTENT_PEERS=$(curl -s',6),ca={style:{color:"#032F62"}},ra=o('| jq -r '.peers.persistent_peers[].address' | tr '\\n' ',' | sed 's/,$/\\n/')',14),ia=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),da=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),_a={class:"language-bash vp-adaptive-theme"},ya=s("button",{title:"Copy Code",class:"copy"},null,-1),ha=s("span",{class:"lang"},"bash",-1),Ea={class:"shiki github-dark vp-code-dark"},ua={class:"line"},Fa=o('PERSISTENT_PEERS=$(curl -sL',6),Ca={style:{color:"#9ECBFF"}},ga=s("span",{style:{color:"#F97583"}},"|",-1),ba=s("span",{style:{color:"#9ECBFF"}}," ",-1),Ta=s("span",{style:{color:"#B392F0"}},"tr",-1),ma=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),Sa=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),va=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),ka={class:"shiki github-light vp-code-light"},Aa={class:"line"},Ba=o('PERSISTENT_PEERS=$(curl -sL',6),fa={style:{color:"#032F62"}},Pa=s("span",{style:{color:"#D73A49"}},"|",-1),qa=s("span",{style:{color:"#032F62"}}," ",-1),Ia=s("span",{style:{color:"#6F42C1"}},"tr",-1),xa=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),Va=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),Ra=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),Da={class:"language-bash vp-adaptive-theme"},wa=s("button",{title:"Copy Code",class:"copy"},null,-1),Na=s("span",{class:"lang"},"bash",-1),Oa={class:"shiki github-dark vp-code-dark"},$a={class:"line"},Ma=o('PERSISTENT_PEERS=$(curl -sL',6),Ha={style:{color:"#9ECBFF"}},La=s("span",{style:{color:"#F97583"}},"|",-1),Qa=s("span",{style:{color:"#9ECBFF"}}," ",-1),Ua=s("span",{style:{color:"#B392F0"}},"tr",-1),ja=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),Wa=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),Ga=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),Xa={class:"shiki github-light vp-code-light"},za={class:"line"},Ya=o('PERSISTENT_PEERS=$(curl -sL',6),Ja={style:{color:"#032F62"}},Za=s("span",{style:{color:"#D73A49"}},"|",-1),Ka=s("span",{style:{color:"#032F62"}}," ",-1),se=s("span",{style:{color:"#6F42C1"}},"tr",-1),oe=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),ae=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),ee=o('sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \\"$PERSISTENT_PEERS\\"/" $HOME/.celestia-app/config/config.toml',1),ne=o(`
    Storage and pruning configurations ​
    Optional: Connect a consensus node to a bridge node ​
    If your consensus node is being connected to a celestia-node bridge node, you will need to enable transaction indexing and retain all block data. This can be achieved with the following settings in your config.toml.
    Enable transaction indexing ​
    toml
    indexer = "kv"
    indexer = "kv"
    Retain all block data ​
    And in your app.toml, min-retain-blocks should remain as the default setting of 0:
    toml
    min-retain-blocks = 0 # retain all block data, this is default setting
    min-retain-blocks = 0 # retain all block data, this is default setting
    Query transactions by hash ​
    To query transactions using their hash, transaction indexing must be turned on. Set the indexer to "kv" in your config.toml:
    toml
    indexer = "kv"
    indexer = "kv"
    Optional: Access historical state ​
    If you want to query the historical state — for example, you might want to know the balance of a Celestia wallet at a given height in the past — you should run an archive node with pruning = "nothing" in your app.toml. Note that this configuration is resource-intensive and will require significant storage:
    toml
    pruning = "nothing"
    pruning = "nothing"
    Save on storage requirements ​
    If you want to save on storage requirements, consider using pruning = "everything" in your app.toml to prune everything. If you select "everything" or "default", but still want to keep the block data, you can do so by not changing the default value of min-retain-blocks = 0 in your app.toml. A value of 0 for min-retain-blocks will keep all block data. This will prune snapshots of the state, but it will keep block data:
    toml
    pruning = "everything"
 min-retain-blocks = 0 # this is the default setting
    pruning = "everything"
 min-retain-blocks = 0 # this is the default setting
    Sync types ​
    Sync modeTimeNotes
    Block sync~3 weeksDownloads and executes all blocks from genesis to the tip
    State sync~1 hourDownloads a snapshot of the state then downloads and executes all blocks after that snapshot to the tip.
    Quick sync~5 hoursDownloads the data directory from a node. Time depends on your download speed because the data being downloaded can exceed 1 TB for mainnet.
    Option 1: Block sync ​
    By default, a consensus node will sync using block sync; which will request, validate and execute every block up to the head of the blockchain. This is the most secure mechanism yet the slowest (taking up to weeks depending on the height of the blockchain).
    There are two alternatives for quicker syncing.
    Option 2: State sync ​
    State sync uses light client verification to verify state snapshots from peers and then apply them. State sync relies on weak subjectivity; a trusted header (specifically the hash and height) must be provided. This can be found by querying a trusted RPC endpoint (/block). RPC endpoints are also required for retrieving light blocks. These can be found in the docs here under the respective networks or from the chain-registry.
    In $HOME/.celestia-app/config/config.toml, set
    toml
    rpc_servers = ""
 trust_height = 0
@@ -18,43 +18,43 @@ import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,t
 ###         State Sync Configuration Options        ###
 #######################################################
 [statesync]
-enable = true
    To their respective fields. At least two different rpc endpoints should be provided. The more, the greater the chance of detecting any fraudulent behavior.
    Once setup, you should be ready to start the node as normal. In the logs, you should see: Discovering snapshots. This may take a few minutes before snapshots are found depending on the network topology.
    Option 3: Quick sync ​
    Quick sync effectively downloads the entire data directory from a third-party provider meaning the node has all the application and blockchain state as the node it was copied from.
    Run the following command to quick-sync from a snapshot:
    `,33),te={class:"vp-code-group vp-adaptive-theme"},le=o('
    ',1),pe={class:"blocks"},ce={class:"language-bash vp-adaptive-theme active"},re=s("button",{title:"Copy Code",class:"copy"},null,-1),ie=s("span",{class:"lang"},"bash",-1),de={class:"shiki github-dark vp-code-dark"},_e=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),ye=o('rm -rf ~/.celestia-app/data',1),he=o('mkdir -p ~/.celestia-app/data',1),Ee=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),ue={class:"line"},Fe=s("span",{style:{color:"#9ECBFF"}},"    ",-1),Ce=s("span",{style:{color:"#B392F0"}},"egrep",-1),ge=s("span",{style:{color:"#9ECBFF"}}," ",-1),Te=s("span",{style:{color:"#79B8FF"}},"-o",-1),be={style:{color:"#9ECBFF"}},me=o('| tr -d ">")',6),Se=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),ve=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),ke={class:"shiki github-light vp-code-light"},Ae=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),Be=o('rm -rf ~/.celestia-app/data',1),fe=o('mkdir -p ~/.celestia-app/data',1),Pe=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),qe={class:"line"},Ie=s("span",{style:{color:"#032F62"}},"    ",-1),xe=s("span",{style:{color:"#6F42C1"}},"egrep",-1),Ve=s("span",{style:{color:"#032F62"}}," ",-1),De=s("span",{style:{color:"#005CC5"}},"-o",-1),Re={style:{color:"#032F62"}},we=o('| tr -d ">")',6),Ne=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),$e=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),Me={class:"language-bash vp-adaptive-theme"},Oe=s("button",{title:"Copy Code",class:"copy"},null,-1),He=s("span",{class:"lang"},"bash",-1),Le={class:"shiki github-dark vp-code-dark"},je=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),ze=o('rm -rf ~/.celestia-app/data',1),Qe=o('mkdir -p ~/.celestia-app/data',1),Ue=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),We={class:"line"},Xe=s("span",{style:{color:"#9ECBFF"}},"    ",-1),Ge=s("span",{style:{color:"#B392F0"}},"egrep",-1),Je=s("span",{style:{color:"#9ECBFF"}}," ",-1),Ke=s("span",{style:{color:"#79B8FF"}},"-o",-1),Ze={style:{color:"#9ECBFF"}},Ye=o('| tr -d ">")',6),sn=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),on=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),an={class:"shiki github-light vp-code-light"},en=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),nn=o('rm -rf ~/.celestia-app/data',1),tn=o('mkdir -p ~/.celestia-app/data',1),ln=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),pn={class:"line"},cn=s("span",{style:{color:"#032F62"}},"    ",-1),rn=s("span",{style:{color:"#6F42C1"}},"egrep",-1),dn=s("span",{style:{color:"#032F62"}}," ",-1),_n=s("span",{style:{color:"#005CC5"}},"-o",-1),yn={style:{color:"#032F62"}},hn=o('| tr -d ">")',6),En=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),un=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),Fn={class:"language-bash vp-adaptive-theme"},Cn=s("button",{title:"Copy Code",class:"copy"},null,-1),gn=s("span",{class:"lang"},"bash",-1),Tn={class:"shiki github-dark vp-code-dark"},bn=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),mn=o('rm -rf ~/.celestia-app/data',1),Sn=o('mkdir -p ~/.celestia-app/data',1),vn=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),kn={class:"line"},An=s("span",{style:{color:"#9ECBFF"}},"    ",-1),Bn=s("span",{style:{color:"#B392F0"}},"egrep",-1),fn=s("span",{style:{color:"#9ECBFF"}}," ",-1),Pn=s("span",{style:{color:"#79B8FF"}},"-o",-1),qn={style:{color:"#9ECBFF"}},In=o('| tr -d ">")',6),xn=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),Vn=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),Dn={class:"shiki github-light vp-code-light"},Rn=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),wn=o('rm -rf ~/.celestia-app/data',1),Nn=o('mkdir -p ~/.celestia-app/data',1),$n=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),Mn={class:"line"},On=s("span",{style:{color:"#032F62"}},"    ",-1),Hn=s("span",{style:{color:"#6F42C1"}},"egrep",-1),Ln=s("span",{style:{color:"#032F62"}}," ",-1),jn=s("span",{style:{color:"#005CC5"}},"-o",-1),zn={style:{color:"#032F62"}},Qn=o('| tr -d ">")',6),Un=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),Wn=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),Xn=o('
    Start the consensus node ​
    If you are running celestia-app v1.x.x:
    sh
    celestia-appd start
    celestia-appd start
    If you are running celestia-app >= v2.0.0: then you'll want to start the node with a --v2-upgrade-height that is dependent on the network. The --v2-upgrade-height flag is only needed during the v2 upgrade height so after your node has executed the upgrade (e.g. you see the log upgraded from app version 1 to 2), you don't need to provide this flag for future celestia-appd start invocations.
    sh
    celestia-appd start --v2-upgrade-height 2371495
    celestia-appd start --v2-upgrade-height 2371495
    sh
    celestia-appd start --v2-upgrade-height 2585031
    celestia-appd start --v2-upgrade-height 2585031
    sh
    celestia-appd start --v2-upgrade-height 1751707
    celestia-appd start --v2-upgrade-height 1751707
    Optional: If you would like celestia-app to run as a background process, you can follow the SystemD tutorial.
    Extra resources for consensus nodes ​
    Optional: Reset network ​
    This will delete all data folders so we can start fresh:
    sh
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app
    Optional: Configure an RPC endpoint ​
    You can configure your consensus node to be a public RPC endpoint. This allows it to accept connections from data availability nodes and serve requests for the data availability API.
    Expose RPC ​
    By default, the RPC service listens on localhost which means it can't be accessed from other machines. To make the RPC service available publicly, you need to bind it to a public IP or 0.0.0.0 (which means listening on all available network interfaces).
    You can do this by editing the config.toml file:
    sh
    sed -i 's#"tcp://127.0.0.1:26657"#"tcp://0.0.0.0:26657"#g' ~/.celestia-app/config/config.toml
    sed -i 's#"tcp://127.0.0.1:26657"#"tcp://0.0.0.0:26657"#g' ~/.celestia-app/config/config.toml
    This command replaces the localhost IP address with 0.0.0.0, making the RPC service listen on all available network interfaces.
    Note on external-address ​
    The external-address field in the configuration is used when your node is behind a NAT and you need to advertise a different address for peers to dial. Populating this field is not necessary for making the RPC endpoint public.
    sh
    EXTERNAL-ADDRESS=$(wget -qO- eth0.me)\nsed -i.bak -e "s/^external-address = ""/external-address = "$EXTERNAL-ADDRESS:26656"/" \\\n    $HOME/.celestia-app/config/config.toml
    EXTERNAL-ADDRESS=$(wget -qO- eth0.me)\nsed -i.bak -e "s/^external-address = ""/external-address = "$EXTERNAL-ADDRESS:26656"/" \\\n    $HOME/.celestia-app/config/config.toml
    Restart the node ​
    After making these changes, restart celestia-appd to load the new configurations.
    Optional: Transaction indexer configuration options ​
    This section guides you on how to configure your config.toml file in celestia-app to select which transactions to index. Depending on the application's configuration, a node operator may decide which transactions to index.
    The available options are:
    1. null: This option disables indexing. If you don't need to query transactions, you can choose this option to save space.
    2. kv (default): This is the simplest indexer, backed by key-value storage (defaults to levelDB; see DBBackend). When kv is chosen, tx.height and tx.hash will always be indexed. This option is suitable for basic queries on transactions.
    3. psql: This indexer is backed by PostgreSQL. When psql is chosen, tx.height and tx.hash will always be indexed. This option is suitable for complex queries on transactions.
    An example to set the value to kv in config.toml is:
    toml
    indexer = "kv"
    indexer = "kv"
    Remember to restart celestia-appd after making changes to the configuration to load the new settings.
    Optional: Discard ABCI responses configuration ​
    This section will guide you on how to configure your config.toml file in celestia-app to manage the storage of ABCI responses. ABCI responses are the results of executing transactions and are used for /block_results RPC queries and to reindex events in the command-line tool.
    The discard_abci_responses option allows you to control whether these responses are persisted in the state store:
    • false (default): ABCI responses are stored in the state store. This ensures that ABCI responses are available for /block_results RPC queries and for reindexing events. However, it can consume a significant amount of disk space.
    • true: ABCI responses are not stored in the state store. This can save a considerable amount of disk space, but /block_results RPC queries and event reindexing will not be available.
    An example to set the value to false in config.toml is:
    toml
    discard_abci_responses = false
    discard_abci_responses = false
    Remember to restart celestia-appd after making changes to the configuration to load the new settings.
    FAQ ​
    +2/3 committed an invalid block: wrong Block.Header.Version ​
    If you encounter an error like:
    bash
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\\nruntime/debug.Stack()\\n\\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\\npanic({0x1b91180?, 0x400153b240?})\\n\\t/usr/local/go/src/runtime/panic.go:770 +0x124\\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\\n"
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\\nruntime/debug.Stack()\\n\\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\\npanic({0x1b91180?, 0x400153b240?})\\n\\t/usr/local/go/src/runtime/panic.go:770 +0x124\\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\\n"
    then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant --v2-upgrade-height for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a celestia-appd tendermint reset-state to reset your node and start syncing from the genesis block.
    ',41),ot=JSON.parse('{"title":"Consensus node","description":"Learn how to set up a Celestia consensus node.","frontmatter":{"description":"Learn how to set up a Celestia consensus node.","outline":"deep","head":[["meta",{"name":"og:title","content":"Consensus node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/consensus-node.md","filePath":"nodes/consensus-node.md","lastUpdated":1725971357000}'),Gn={name:"nodes/consensus-node.md"},at=Object.assign(Gn,{setup(Jn){return(Kn,Zn)=>(l(),p("div",null,[r,s("div",i,[d,s("div",_,[s("div",y,[h,E,s("pre",u,[s("code",null,[s("span",F,[C,s("span",g,n(t(e).mainnetChainId),1)])])]),s("pre",T,[s("code",null,[s("span",b,[m,s("span",S,n(t(e).mainnetChainId),1)])])])]),s("div",v,[k,A,s("pre",B,[s("code",null,[s("span",f,[P,s("span",q,n(t(e).mochaChainId),1)])])]),s("pre",I,[s("code",null,[s("span",x,[V,s("span",D,n(t(e).mochaChainId),1)])])])]),s("div",R,[w,N,s("pre",$,[s("code",null,[s("span",M,[O,s("span",H,n(t(e).arabicaChainId),1)])])]),s("pre",L,[s("code",null,[s("span",j,[z,s("span",Q,n(t(e).arabicaChainId),1)])])])])])]),U,s("div",W,[X,s("div",G,[s("div",J,[K,Z,s("pre",Y,[s("code",null,[s("span",ss,[os,as,es,ns,s("span",ts,n(t(e).mainnetChainId),1)])])]),s("pre",ls,[s("code",null,[s("span",ps,[cs,rs,is,ds,s("span",_s,n(t(e).mainnetChainId),1)])])])]),s("div",ys,[hs,Es,s("pre",us,[s("code",null,[s("span",Fs,[Cs,gs,Ts,bs,s("span",ms,n(t(e).mochaChainId),1)])])]),s("pre",Ss,[s("code",null,[s("span",vs,[ks,As,Bs,fs,s("span",Ps,n(t(e).mochaChainId),1)])])])]),s("div",qs,[Is,xs,s("pre",Vs,[s("code",null,[s("span",Ds,[Rs,ws,Ns,$s,s("span",Ms,n(t(e).arabicaChainId),1)])])]),s("pre",Os,[s("code",null,[s("span",Hs,[Ls,js,zs,Qs,s("span",Us,n(t(e).arabicaChainId),1)])])])])])]),Ws,s("div",Xs,[Gs,s("div",Js,[s("div",Ks,[Zs,Ys,s("pre",so,[s("code",null,[s("span",oo,[ao,s("span",eo," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mainnetChainId)+"/seeds.txt ",1),no,to,lo,po]),a(`
+enable = true

    To their respective fields. At least two different rpc endpoints should be provided. The more, the greater the chance of detecting any fraudulent behavior.

    Once setup, you should be ready to start the node as normal. In the logs, you should see: Discovering snapshots. This may take a few minutes before snapshots are found depending on the network topology.

    Option 3: Quick sync ​

    Quick sync effectively downloads the entire data directory from a third-party provider meaning the node has all the application and blockchain state as the node it was copied from.

    Run the following command to quick-sync from a snapshot:

    `,33),te={class:"vp-code-group vp-adaptive-theme"},le=o('
    ',1),pe={class:"blocks"},ce={class:"language-bash vp-adaptive-theme active"},re=s("button",{title:"Copy Code",class:"copy"},null,-1),ie=s("span",{class:"lang"},"bash",-1),de={class:"shiki github-dark vp-code-dark"},_e=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),ye=o('rm -rf ~/.celestia-app/data',1),he=o('mkdir -p ~/.celestia-app/data',1),Ee=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),ue={class:"line"},Fe=s("span",{style:{color:"#9ECBFF"}}," ",-1),Ce=s("span",{style:{color:"#B392F0"}},"egrep",-1),ge=s("span",{style:{color:"#9ECBFF"}}," ",-1),be=s("span",{style:{color:"#79B8FF"}},"-o",-1),Te={style:{color:"#9ECBFF"}},me=o('| tr -d ">")',6),Se=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),ve=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),ke={class:"shiki github-light vp-code-light"},Ae=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),Be=o('rm -rf ~/.celestia-app/data',1),fe=o('mkdir -p ~/.celestia-app/data',1),Pe=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),qe={class:"line"},Ie=s("span",{style:{color:"#032F62"}}," ",-1),xe=s("span",{style:{color:"#6F42C1"}},"egrep",-1),Ve=s("span",{style:{color:"#032F62"}}," ",-1),Re=s("span",{style:{color:"#005CC5"}},"-o",-1),De={style:{color:"#032F62"}},we=o('| tr -d ">")',6),Ne=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),Oe=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),$e={class:"language-bash vp-adaptive-theme"},Me=s("button",{title:"Copy Code",class:"copy"},null,-1),He=s("span",{class:"lang"},"bash",-1),Le={class:"shiki github-dark vp-code-dark"},Qe=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),Ue=o('rm -rf ~/.celestia-app/data',1),je=o('mkdir -p ~/.celestia-app/data',1),We=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),Ge={class:"line"},Xe=s("span",{style:{color:"#9ECBFF"}}," ",-1),ze=s("span",{style:{color:"#B392F0"}},"egrep",-1),Ye=s("span",{style:{color:"#9ECBFF"}}," ",-1),Je=s("span",{style:{color:"#79B8FF"}},"-o",-1),Ze={style:{color:"#9ECBFF"}},Ke=o('| tr -d ">")',6),sn=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),on=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),an={class:"shiki github-light vp-code-light"},en=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),nn=o('rm -rf ~/.celestia-app/data',1),tn=o('mkdir -p ~/.celestia-app/data',1),ln=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),pn={class:"line"},cn=s("span",{style:{color:"#032F62"}}," ",-1),rn=s("span",{style:{color:"#6F42C1"}},"egrep",-1),dn=s("span",{style:{color:"#032F62"}}," ",-1),_n=s("span",{style:{color:"#005CC5"}},"-o",-1),yn={style:{color:"#032F62"}},hn=o('| tr -d ">")',6),En=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),un=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),Fn={class:"language-bash vp-adaptive-theme"},Cn=s("button",{title:"Copy Code",class:"copy"},null,-1),gn=s("span",{class:"lang"},"bash",-1),bn={class:"shiki github-dark vp-code-dark"},Tn=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),mn=o('rm -rf ~/.celestia-app/data',1),Sn=o('mkdir -p ~/.celestia-app/data',1),vn=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),kn={class:"line"},An=s("span",{style:{color:"#9ECBFF"}}," ",-1),Bn=s("span",{style:{color:"#B392F0"}},"egrep",-1),fn=s("span",{style:{color:"#9ECBFF"}}," ",-1),Pn=s("span",{style:{color:"#79B8FF"}},"-o",-1),qn={style:{color:"#9ECBFF"}},In=o('| tr -d ">")',6),xn=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),Vn=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),Rn={class:"shiki github-light vp-code-light"},Dn=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),wn=o('rm -rf ~/.celestia-app/data',1),Nn=o('mkdir -p ~/.celestia-app/data',1),On=o('SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \\',1),$n={class:"line"},Mn=s("span",{style:{color:"#032F62"}}," ",-1),Hn=s("span",{style:{color:"#6F42C1"}},"egrep",-1),Ln=s("span",{style:{color:"#032F62"}}," ",-1),Qn=s("span",{style:{color:"#005CC5"}},"-o",-1),Un={style:{color:"#032F62"}},jn=o('| tr -d ">")',6),Wn=o('aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"',1),Gn=o('tar xf celestia-snap.tar -C ~/.celestia-app/data/',1),Xn=o('

    Start the consensus node ​

    If you are running celestia-app v1.x.x:

    sh
    celestia-appd start
    celestia-appd start

    If you are running celestia-app >= v2.0.0: then you'll want to start the node with a --v2-upgrade-height that is dependent on the network. The --v2-upgrade-height flag is only needed during the v2 upgrade height so after your node has executed the upgrade (e.g. you see the log upgraded from app version 1 to 2), you don't need to provide this flag for future celestia-appd start invocations.

    sh
    celestia-appd start --v2-upgrade-height 2371495
    celestia-appd start --v2-upgrade-height 2371495
    sh
    celestia-appd start --v2-upgrade-height 2585031
    celestia-appd start --v2-upgrade-height 2585031
    sh
    celestia-appd start --v2-upgrade-height 1751707
    celestia-appd start --v2-upgrade-height 1751707

    Optional: If you would like celestia-app to run as a background process, you can follow the SystemD tutorial.

    Extra resources for consensus nodes ​

    Optional: Reset network ​

    This will delete all data folders so we can start fresh:

    sh
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app

    Optional: Configure an RPC endpoint ​

    You can configure your consensus node to be a public RPC endpoint. This allows it to accept connections from data availability nodes and serve requests for the data availability API.

    Expose RPC ​

    By default, the RPC service listens on localhost which means it can't be accessed from other machines. To make the RPC service available publicly, you need to bind it to a public IP or 0.0.0.0 (which means listening on all available network interfaces).

    You can do this by editing the config.toml file:

    sh
    sed -i 's#"tcp://127.0.0.1:26657"#"tcp://0.0.0.0:26657"#g' ~/.celestia-app/config/config.toml
    sed -i 's#"tcp://127.0.0.1:26657"#"tcp://0.0.0.0:26657"#g' ~/.celestia-app/config/config.toml

    This command replaces the localhost IP address with 0.0.0.0, making the RPC service listen on all available network interfaces.

    Note on external-address ​

    The external-address field in the configuration is used when your node is behind a NAT and you need to advertise a different address for peers to dial. Populating this field is not necessary for making the RPC endpoint public.

    sh
    EXTERNAL-ADDRESS=$(wget -qO- eth0.me)\nsed -i.bak -e "s/^external-address = ""/external-address = "$EXTERNAL-ADDRESS:26656"/" \\\n    $HOME/.celestia-app/config/config.toml
    EXTERNAL-ADDRESS=$(wget -qO- eth0.me)\nsed -i.bak -e "s/^external-address = ""/external-address = "$EXTERNAL-ADDRESS:26656"/" \\\n    $HOME/.celestia-app/config/config.toml

    Restart the node ​

    After making these changes, restart celestia-appd to load the new configurations.

    Optional: Transaction indexer configuration options ​

    This section guides you on how to configure your config.toml file in celestia-app to select which transactions to index. Depending on the application's configuration, a node operator may decide which transactions to index.

    The available options are:

    1. null: This option disables indexing. If you don't need to query transactions, you can choose this option to save space.
    2. kv (default): This is the simplest indexer, backed by key-value storage (defaults to levelDB; see DBBackend). When kv is chosen, tx.height and tx.hash will always be indexed. This option is suitable for basic queries on transactions.
    3. psql: This indexer is backed by PostgreSQL. When psql is chosen, tx.height and tx.hash will always be indexed. This option is suitable for complex queries on transactions.

    An example to set the value to kv in config.toml is:

    toml
    indexer = "kv"
    indexer = "kv"

    Remember to restart celestia-appd after making changes to the configuration to load the new settings.

    Optional: Discard ABCI responses configuration ​

    This section will guide you on how to configure your config.toml file in celestia-app to manage the storage of ABCI responses. ABCI responses are the results of executing transactions and are used for /block_results RPC queries and to reindex events in the command-line tool.

    The discard_abci_responses option allows you to control whether these responses are persisted in the state store:

    An example to set the value to false in config.toml is:

    toml
    discard_abci_responses = false
    discard_abci_responses = false

    Remember to restart celestia-appd after making changes to the configuration to load the new settings.

    FAQ ​

    +2/3 committed an invalid block: wrong Block.Header.Version ​

    If you encounter an error like:

    bash
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\\nruntime/debug.Stack()\\n\\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\\npanic({0x1b91180?, 0x400153b240?})\\n\\t/usr/local/go/src/runtime/panic.go:770 +0x124\\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\\n"
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\\nruntime/debug.Stack()\\n\\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\\npanic({0x1b91180?, 0x400153b240?})\\n\\t/usr/local/go/src/runtime/panic.go:770 +0x124\\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\\n"

    then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant --v2-upgrade-height for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a celestia-appd tendermint reset-state to reset your node and start syncing from the genesis block.

    ',41),ot=JSON.parse('{"title":"Consensus node","description":"Learn how to set up a Celestia consensus node.","frontmatter":{"description":"Learn how to set up a Celestia consensus node.","outline":"deep","head":[["meta",{"name":"og:title","content":"Consensus node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/consensus-node.md","filePath":"nodes/consensus-node.md","lastUpdated":1725992025000}'),zn={name:"nodes/consensus-node.md"},at=Object.assign(zn,{setup(Yn){return(Jn,Zn)=>(l(),p("div",null,[r,s("div",i,[d,s("div",_,[s("div",y,[h,E,s("pre",u,[s("code",null,[s("span",F,[C,s("span",g,n(t(e).mainnetChainId),1)])])]),s("pre",b,[s("code",null,[s("span",T,[m,s("span",S,n(t(e).mainnetChainId),1)])])])]),s("div",v,[k,A,s("pre",B,[s("code",null,[s("span",f,[P,s("span",q,n(t(e).mochaChainId),1)])])]),s("pre",I,[s("code",null,[s("span",x,[V,s("span",R,n(t(e).mochaChainId),1)])])])]),s("div",D,[w,N,s("pre",O,[s("code",null,[s("span",$,[M,s("span",H,n(t(e).arabicaChainId),1)])])]),s("pre",L,[s("code",null,[s("span",Q,[U,s("span",j,n(t(e).arabicaChainId),1)])])])])])]),W,s("div",G,[X,s("div",z,[s("div",Y,[J,Z,s("pre",K,[s("code",null,[s("span",ss,[os,as,es,ns,s("span",ts,n(t(e).mainnetChainId),1)])])]),s("pre",ls,[s("code",null,[s("span",ps,[cs,rs,is,ds,s("span",_s,n(t(e).mainnetChainId),1)])])])]),s("div",ys,[hs,Es,s("pre",us,[s("code",null,[s("span",Fs,[Cs,gs,bs,Ts,s("span",ms,n(t(e).mochaChainId),1)])])]),s("pre",Ss,[s("code",null,[s("span",vs,[ks,As,Bs,fs,s("span",Ps,n(t(e).mochaChainId),1)])])])]),s("div",qs,[Is,xs,s("pre",Vs,[s("code",null,[s("span",Rs,[Ds,ws,Ns,Os,s("span",$s,n(t(e).arabicaChainId),1)])])]),s("pre",Ms,[s("code",null,[s("span",Hs,[Ls,Qs,Us,js,s("span",Ws,n(t(e).arabicaChainId),1)])])])])])]),Gs,s("div",Xs,[zs,s("div",Ys,[s("div",Js,[Zs,Ks,s("pre",so,[s("code",null,[s("span",oo,[ao,s("span",eo," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mainnetChainId)+"/seeds.txt ",1),no,to,lo,po]),a(` `),co,a(` `),ro])]),s("pre",io,[s("code",null,[s("span",_o,[yo,s("span",ho," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mainnetChainId)+"/seeds.txt ",1),Eo,uo,Fo,Co]),a(` `),go,a(` -`),To])])]),s("div",bo,[mo,So,s("pre",vo,[s("code",null,[s("span",ko,[Ao,s("span",Bo," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/seeds.txt ",1),fo,Po,qo,Io]),a(` +`),bo])])]),s("div",To,[mo,So,s("pre",vo,[s("code",null,[s("span",ko,[Ao,s("span",Bo," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/seeds.txt ",1),fo,Po,qo,Io]),a(` `),xo,a(` -`),Vo])]),s("pre",Do,[s("code",null,[s("span",Ro,[wo,s("span",No," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/seeds.txt ",1),$o,Mo,Oo,Ho]),a(` +`),Vo])]),s("pre",Ro,[s("code",null,[s("span",Do,[wo,s("span",No," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/seeds.txt ",1),Oo,$o,Mo,Ho]),a(` `),Lo,a(` -`),jo])])]),zo])]),s("details",null,[Qo,s("div",Uo,[Wo,s("div",Xo,[s("div",Go,[Jo,Ko,s("pre",Zo,[s("code",null,[s("span",Yo,[sa,s("span",oa," https://raw.githubusercontent.com/cosmos/chain-registry/master/"+n(t(e).mainnetChainId)+"/chain.json ",1),aa]),a(` +`),Qo])])]),Uo])]),s("details",null,[jo,s("div",Wo,[Go,s("div",Xo,[s("div",zo,[Yo,Jo,s("pre",Zo,[s("code",null,[s("span",Ko,[sa,s("span",oa," https://raw.githubusercontent.com/cosmos/chain-registry/master/"+n(t(e).mainnetChainId)+"/chain.json ",1),aa]),a(` `),ea,a(` `),na])]),s("pre",ta,[s("code",null,[s("span",la,[pa,s("span",ca," https://raw.githubusercontent.com/cosmos/chain-registry/master/"+n(t(e).mainnetChainId)+"/chain.json ",1),ra]),a(` `),ia,a(` -`),da])])]),s("div",_a,[ya,ha,s("pre",Ea,[s("code",null,[s("span",ua,[Fa,s("span",Ca," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/peers.txt ",1),ga,Ta,ba,ma]),a(` +`),da])])]),s("div",_a,[ya,ha,s("pre",Ea,[s("code",null,[s("span",ua,[Fa,s("span",Ca," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/peers.txt ",1),ga,ba,Ta,ma]),a(` `),Sa,a(` `),va])]),s("pre",ka,[s("code",null,[s("span",Aa,[Ba,s("span",fa," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/peers.txt ",1),Pa,qa,Ia,xa]),a(` `),Va,a(` -`),Da])])]),s("div",Ra,[wa,Na,s("pre",$a,[s("code",null,[s("span",Ma,[Oa,s("span",Ha," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).arabicaChainId)+"/peers.txt ",1),La,ja,za,Qa]),a(` -`),Ua,a(` -`),Wa])]),s("pre",Xa,[s("code",null,[s("span",Ga,[Ja,s("span",Ka," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).arabicaChainId)+"/peers.txt ",1),Za,Ya,se,oe]),a(` +`),Ra])])]),s("div",Da,[wa,Na,s("pre",Oa,[s("code",null,[s("span",$a,[Ma,s("span",Ha," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).arabicaChainId)+"/peers.txt ",1),La,Qa,Ua,ja]),a(` +`),Wa,a(` +`),Ga])]),s("pre",Xa,[s("code",null,[s("span",za,[Ya,s("span",Ja," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).arabicaChainId)+"/peers.txt ",1),Za,Ka,se,oe]),a(` `),ae,a(` `),ee])])])])])]),ne,s("div",te,[le,s("div",pe,[s("div",ce,[re,ie,s("pre",de,[s("code",null,[_e,a(` `),ye,a(` `),he,a(` `),Ee,a(` -`),s("span",ue,[Fe,Ce,ge,Te,s("span",be,' ">'+n(t(e).mainnetChainId)+'.*tar" ',1),me]),a(` +`),s("span",ue,[Fe,Ce,ge,be,s("span",Te,' ">'+n(t(e).mainnetChainId)+'.*tar" ',1),me]),a(` `),Se,a(` `),ve])]),s("pre",ke,[s("code",null,[Ae,a(` `),Be,a(` `),fe,a(` `),Pe,a(` -`),s("span",qe,[Ie,xe,Ve,De,s("span",Re,' ">'+n(t(e).mainnetChainId)+'.*tar" ',1),we]),a(` +`),s("span",qe,[Ie,xe,Ve,Re,s("span",De,' ">'+n(t(e).mainnetChainId)+'.*tar" ',1),we]),a(` `),Ne,a(` -`),$e])])]),s("div",Me,[Oe,He,s("pre",Le,[s("code",null,[je,a(` -`),ze,a(` -`),Qe,a(` +`),Oe])])]),s("div",$e,[Me,He,s("pre",Le,[s("code",null,[Qe,a(` `),Ue,a(` -`),s("span",We,[Xe,Ge,Je,Ke,s("span",Ze,' ">'+n(t(e).mochaChainId)+'.*tar" ',1),Ye]),a(` +`),je,a(` +`),We,a(` +`),s("span",Ge,[Xe,ze,Ye,Je,s("span",Ze,' ">'+n(t(e).mochaChainId)+'.*tar" ',1),Ke]),a(` `),sn,a(` `),on])]),s("pre",an,[s("code",null,[en,a(` `),nn,a(` @@ -62,16 +62,16 @@ import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,t `),ln,a(` `),s("span",pn,[cn,rn,dn,_n,s("span",yn,' ">'+n(t(e).mochaChainId)+'.*tar" ',1),hn]),a(` `),En,a(` -`),un])])]),s("div",Fn,[Cn,gn,s("pre",Tn,[s("code",null,[bn,a(` +`),un])])]),s("div",Fn,[Cn,gn,s("pre",bn,[s("code",null,[Tn,a(` `),mn,a(` `),Sn,a(` `),vn,a(` `),s("span",kn,[An,Bn,fn,Pn,s("span",qn,' ">'+n(t(e).arabicaChainId)+'.*tar" ',1),In]),a(` `),xn,a(` -`),Vn])]),s("pre",Dn,[s("code",null,[Rn,a(` +`),Vn])]),s("pre",Rn,[s("code",null,[Dn,a(` `),wn,a(` `),Nn,a(` -`),$n,a(` -`),s("span",Mn,[On,Hn,Ln,jn,s("span",zn,' ">'+n(t(e).arabicaChainId)+'.*tar" ',1),Qn]),a(` -`),Un,a(` -`),Wn])])])])]),Xn]))}});export{ot as __pageData,at as default}; +`),On,a(` +`),s("span",$n,[Mn,Hn,Ln,Qn,s("span",Un,' ">'+n(t(e).arabicaChainId)+'.*tar" ',1),jn]),a(` +`),Wn,a(` +`),Gn])])])])]),Xn]))}});export{ot as __pageData,at as default}; diff --git a/pr-1699/assets/nodes_consensus-node.md.c0f03057.lean.js b/pr-1699/assets/nodes_consensus-node.md.99f6268d.lean.js similarity index 65% rename from pr-1699/assets/nodes_consensus-node.md.c0f03057.lean.js rename to pr-1699/assets/nodes_consensus-node.md.99f6268d.lean.js index fd950a4ae7..290296930e 100644 --- a/pr-1699/assets/nodes_consensus-node.md.c0f03057.lean.js +++ b/pr-1699/assets/nodes_consensus-node.md.99f6268d.lean.js @@ -1,40 +1,40 @@ -import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,t as n,l as t,a,Q as o}from"./chunks/framework.b47e54aa.js";const c="/docs-preview/pr-1699/img/nodes/consensus-node.jpg",r=o("",14),i={class:"vp-code-group vp-adaptive-theme"},d=o("",1),_={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},h=s("button",{title:"Copy Code",class:"copy"},null,-1),E=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},F={class:"line"},C=o("",8),g={style:{color:"#9ECBFF"}},T={class:"shiki github-light vp-code-light"},b={class:"line"},m=o("",8),S={style:{color:"#032F62"}},v={class:"language-bash vp-adaptive-theme"},k=s("button",{title:"Copy Code",class:"copy"},null,-1),A=s("span",{class:"lang"},"bash",-1),B={class:"shiki github-dark vp-code-dark"},f={class:"line"},P=o("",8),q={style:{color:"#9ECBFF"}},I={class:"shiki github-light vp-code-light"},x={class:"line"},V=o("",8),D={style:{color:"#032F62"}},R={class:"language-bash vp-adaptive-theme"},w=s("button",{title:"Copy Code",class:"copy"},null,-1),N=s("span",{class:"lang"},"bash",-1),$={class:"shiki github-dark vp-code-dark"},M={class:"line"},O=o("",8),H={style:{color:"#9ECBFF"}},L={class:"shiki github-light vp-code-light"},j={class:"line"},z=o("",8),Q={style:{color:"#032F62"}},U=s("p",null,[a("Download the "),s("code",null,"genesis.json"),a(" file:")],-1),W={class:"vp-code-group vp-adaptive-theme"},X=o("",1),G={class:"blocks"},J={class:"language-bash vp-adaptive-theme active"},K=s("button",{title:"Copy Code",class:"copy"},null,-1),Z=s("span",{class:"lang"},"bash",-1),Y={class:"shiki github-dark vp-code-dark"},ss={class:"line"},os=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),as=s("span",{style:{color:"#E1E4E8"}}," ",-1),es=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),ns=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ps={class:"line"},cs=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),is=s("span",{style:{color:"#032F62"}},"download-genesis",-1),ds=s("span",{style:{color:"#24292E"}}," ",-1),_s={style:{color:"#032F62"}},ys={class:"language-bash vp-adaptive-theme"},hs=s("button",{title:"Copy Code",class:"copy"},null,-1),Es=s("span",{class:"lang"},"bash",-1),us={class:"shiki github-dark vp-code-dark"},Fs={class:"line"},Cs=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),gs=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ts=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),bs=s("span",{style:{color:"#E1E4E8"}}," ",-1),ms={style:{color:"#9ECBFF"}},Ss={class:"shiki github-light vp-code-light"},vs={class:"line"},ks=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),As=s("span",{style:{color:"#24292E"}}," ",-1),Bs=s("span",{style:{color:"#032F62"}},"download-genesis",-1),fs=s("span",{style:{color:"#24292E"}}," ",-1),Ps={style:{color:"#032F62"}},qs={class:"language-bash vp-adaptive-theme"},Is=s("button",{title:"Copy Code",class:"copy"},null,-1),xs=s("span",{class:"lang"},"bash",-1),Vs={class:"shiki github-dark vp-code-dark"},Ds={class:"line"},Rs=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),ws=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ns=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),$s=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ms={style:{color:"#9ECBFF"}},Os={class:"shiki github-light vp-code-light"},Hs={class:"line"},Ls=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),js=s("span",{style:{color:"#24292E"}}," ",-1),zs=s("span",{style:{color:"#032F62"}},"download-genesis",-1),Qs=s("span",{style:{color:"#24292E"}}," ",-1),Us={style:{color:"#032F62"}},Ws=s("p",null,[a("Set seeds in the "),s("code",null,"$HOME/.celestia-app/config/config.toml"),a(" file:")],-1),Xs={class:"vp-code-group vp-adaptive-theme"},Gs=o("",1),Js={class:"blocks"},Ks={class:"language-bash vp-adaptive-theme active"},Zs=s("button",{title:"Copy Code",class:"copy"},null,-1),Ys=s("span",{class:"lang"},"bash",-1),so={class:"shiki github-dark vp-code-dark"},oo={class:"line"},ao=o("",6),eo={style:{color:"#9ECBFF"}},no=s("span",{style:{color:"#F97583"}},"|",-1),to=s("span",{style:{color:"#9ECBFF"}}," ",-1),lo=s("span",{style:{color:"#B392F0"}},"tr",-1),po=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),co=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $SEEDS")],-1),ro=o("",1),io={class:"shiki github-light vp-code-light"},_o={class:"line"},yo=o("",6),ho={style:{color:"#032F62"}},Eo=s("span",{style:{color:"#D73A49"}},"|",-1),uo=s("span",{style:{color:"#032F62"}}," ",-1),Fo=s("span",{style:{color:"#6F42C1"}},"tr",-1),Co=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),go=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $SEEDS")],-1),To=o("",1),bo={class:"language-bash vp-adaptive-theme"},mo=s("button",{title:"Copy Code",class:"copy"},null,-1),So=s("span",{class:"lang"},"bash",-1),vo={class:"shiki github-dark vp-code-dark"},ko={class:"line"},Ao=o("",6),Bo={style:{color:"#9ECBFF"}},fo=s("span",{style:{color:"#F97583"}},"|",-1),Po=s("span",{style:{color:"#9ECBFF"}}," ",-1),qo=s("span",{style:{color:"#B392F0"}},"tr",-1),Io=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),xo=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $SEEDS")],-1),Vo=o("",1),Do={class:"shiki github-light vp-code-light"},Ro={class:"line"},wo=o("",6),No={style:{color:"#032F62"}},$o=s("span",{style:{color:"#D73A49"}},"|",-1),Mo=s("span",{style:{color:"#032F62"}}," ",-1),Oo=s("span",{style:{color:"#6F42C1"}},"tr",-1),Ho=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),Lo=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $SEEDS")],-1),jo=o("",1),zo=o("",1),Qo=o("",3),Uo={class:"vp-code-group vp-adaptive-theme"},Wo=o("",1),Xo={class:"blocks"},Go={class:"language-bash vp-adaptive-theme active"},Jo=s("button",{title:"Copy Code",class:"copy"},null,-1),Ko=s("span",{class:"lang"},"bash",-1),Zo={class:"shiki github-dark vp-code-dark"},Yo={class:"line"},sa=o("",6),oa={style:{color:"#9ECBFF"}},aa=o("",14),ea=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),na=o("",1),ta={class:"shiki github-light vp-code-light"},la={class:"line"},pa=o("",6),ca={style:{color:"#032F62"}},ra=o("",14),ia=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),da=o("",1),_a={class:"language-bash vp-adaptive-theme"},ya=s("button",{title:"Copy Code",class:"copy"},null,-1),ha=s("span",{class:"lang"},"bash",-1),Ea={class:"shiki github-dark vp-code-dark"},ua={class:"line"},Fa=o("",6),Ca={style:{color:"#9ECBFF"}},ga=s("span",{style:{color:"#F97583"}},"|",-1),Ta=s("span",{style:{color:"#9ECBFF"}}," ",-1),ba=s("span",{style:{color:"#B392F0"}},"tr",-1),ma=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),Sa=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),va=o("",1),ka={class:"shiki github-light vp-code-light"},Aa={class:"line"},Ba=o("",6),fa={style:{color:"#032F62"}},Pa=s("span",{style:{color:"#D73A49"}},"|",-1),qa=s("span",{style:{color:"#032F62"}}," ",-1),Ia=s("span",{style:{color:"#6F42C1"}},"tr",-1),xa=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),Va=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),Da=o("",1),Ra={class:"language-bash vp-adaptive-theme"},wa=s("button",{title:"Copy Code",class:"copy"},null,-1),Na=s("span",{class:"lang"},"bash",-1),$a={class:"shiki github-dark vp-code-dark"},Ma={class:"line"},Oa=o("",6),Ha={style:{color:"#9ECBFF"}},La=s("span",{style:{color:"#F97583"}},"|",-1),ja=s("span",{style:{color:"#9ECBFF"}}," ",-1),za=s("span",{style:{color:"#B392F0"}},"tr",-1),Qa=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),Ua=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),Wa=o("",1),Xa={class:"shiki github-light vp-code-light"},Ga={class:"line"},Ja=o("",6),Ka={style:{color:"#032F62"}},Za=s("span",{style:{color:"#D73A49"}},"|",-1),Ya=s("span",{style:{color:"#032F62"}}," ",-1),se=s("span",{style:{color:"#6F42C1"}},"tr",-1),oe=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),ae=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),ee=o("",1),ne=o("",33),te={class:"vp-code-group vp-adaptive-theme"},le=o("",1),pe={class:"blocks"},ce={class:"language-bash vp-adaptive-theme active"},re=s("button",{title:"Copy Code",class:"copy"},null,-1),ie=s("span",{class:"lang"},"bash",-1),de={class:"shiki github-dark vp-code-dark"},_e=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),ye=o("",1),he=o("",1),Ee=o("",1),ue={class:"line"},Fe=s("span",{style:{color:"#9ECBFF"}}," ",-1),Ce=s("span",{style:{color:"#B392F0"}},"egrep",-1),ge=s("span",{style:{color:"#9ECBFF"}}," ",-1),Te=s("span",{style:{color:"#79B8FF"}},"-o",-1),be={style:{color:"#9ECBFF"}},me=o("",6),Se=o("",1),ve=o("",1),ke={class:"shiki github-light vp-code-light"},Ae=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),Be=o("",1),fe=o("",1),Pe=o("",1),qe={class:"line"},Ie=s("span",{style:{color:"#032F62"}}," ",-1),xe=s("span",{style:{color:"#6F42C1"}},"egrep",-1),Ve=s("span",{style:{color:"#032F62"}}," ",-1),De=s("span",{style:{color:"#005CC5"}},"-o",-1),Re={style:{color:"#032F62"}},we=o("",6),Ne=o("",1),$e=o("",1),Me={class:"language-bash vp-adaptive-theme"},Oe=s("button",{title:"Copy Code",class:"copy"},null,-1),He=s("span",{class:"lang"},"bash",-1),Le={class:"shiki github-dark vp-code-dark"},je=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),ze=o("",1),Qe=o("",1),Ue=o("",1),We={class:"line"},Xe=s("span",{style:{color:"#9ECBFF"}}," ",-1),Ge=s("span",{style:{color:"#B392F0"}},"egrep",-1),Je=s("span",{style:{color:"#9ECBFF"}}," ",-1),Ke=s("span",{style:{color:"#79B8FF"}},"-o",-1),Ze={style:{color:"#9ECBFF"}},Ye=o("",6),sn=o("",1),on=o("",1),an={class:"shiki github-light vp-code-light"},en=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),nn=o("",1),tn=o("",1),ln=o("",1),pn={class:"line"},cn=s("span",{style:{color:"#032F62"}}," ",-1),rn=s("span",{style:{color:"#6F42C1"}},"egrep",-1),dn=s("span",{style:{color:"#032F62"}}," ",-1),_n=s("span",{style:{color:"#005CC5"}},"-o",-1),yn={style:{color:"#032F62"}},hn=o("",6),En=o("",1),un=o("",1),Fn={class:"language-bash vp-adaptive-theme"},Cn=s("button",{title:"Copy Code",class:"copy"},null,-1),gn=s("span",{class:"lang"},"bash",-1),Tn={class:"shiki github-dark vp-code-dark"},bn=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),mn=o("",1),Sn=o("",1),vn=o("",1),kn={class:"line"},An=s("span",{style:{color:"#9ECBFF"}}," ",-1),Bn=s("span",{style:{color:"#B392F0"}},"egrep",-1),fn=s("span",{style:{color:"#9ECBFF"}}," ",-1),Pn=s("span",{style:{color:"#79B8FF"}},"-o",-1),qn={style:{color:"#9ECBFF"}},In=o("",6),xn=o("",1),Vn=o("",1),Dn={class:"shiki github-light vp-code-light"},Rn=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),wn=o("",1),Nn=o("",1),$n=o("",1),Mn={class:"line"},On=s("span",{style:{color:"#032F62"}}," ",-1),Hn=s("span",{style:{color:"#6F42C1"}},"egrep",-1),Ln=s("span",{style:{color:"#032F62"}}," ",-1),jn=s("span",{style:{color:"#005CC5"}},"-o",-1),zn={style:{color:"#032F62"}},Qn=o("",6),Un=o("",1),Wn=o("",1),Xn=o("",41),ot=JSON.parse('{"title":"Consensus node","description":"Learn how to set up a Celestia consensus node.","frontmatter":{"description":"Learn how to set up a Celestia consensus node.","outline":"deep","head":[["meta",{"name":"og:title","content":"Consensus node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/consensus-node.md","filePath":"nodes/consensus-node.md","lastUpdated":1725971357000}'),Gn={name:"nodes/consensus-node.md"},at=Object.assign(Gn,{setup(Jn){return(Kn,Zn)=>(l(),p("div",null,[r,s("div",i,[d,s("div",_,[s("div",y,[h,E,s("pre",u,[s("code",null,[s("span",F,[C,s("span",g,n(t(e).mainnetChainId),1)])])]),s("pre",T,[s("code",null,[s("span",b,[m,s("span",S,n(t(e).mainnetChainId),1)])])])]),s("div",v,[k,A,s("pre",B,[s("code",null,[s("span",f,[P,s("span",q,n(t(e).mochaChainId),1)])])]),s("pre",I,[s("code",null,[s("span",x,[V,s("span",D,n(t(e).mochaChainId),1)])])])]),s("div",R,[w,N,s("pre",$,[s("code",null,[s("span",M,[O,s("span",H,n(t(e).arabicaChainId),1)])])]),s("pre",L,[s("code",null,[s("span",j,[z,s("span",Q,n(t(e).arabicaChainId),1)])])])])])]),U,s("div",W,[X,s("div",G,[s("div",J,[K,Z,s("pre",Y,[s("code",null,[s("span",ss,[os,as,es,ns,s("span",ts,n(t(e).mainnetChainId),1)])])]),s("pre",ls,[s("code",null,[s("span",ps,[cs,rs,is,ds,s("span",_s,n(t(e).mainnetChainId),1)])])])]),s("div",ys,[hs,Es,s("pre",us,[s("code",null,[s("span",Fs,[Cs,gs,Ts,bs,s("span",ms,n(t(e).mochaChainId),1)])])]),s("pre",Ss,[s("code",null,[s("span",vs,[ks,As,Bs,fs,s("span",Ps,n(t(e).mochaChainId),1)])])])]),s("div",qs,[Is,xs,s("pre",Vs,[s("code",null,[s("span",Ds,[Rs,ws,Ns,$s,s("span",Ms,n(t(e).arabicaChainId),1)])])]),s("pre",Os,[s("code",null,[s("span",Hs,[Ls,js,zs,Qs,s("span",Us,n(t(e).arabicaChainId),1)])])])])])]),Ws,s("div",Xs,[Gs,s("div",Js,[s("div",Ks,[Zs,Ys,s("pre",so,[s("code",null,[s("span",oo,[ao,s("span",eo," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mainnetChainId)+"/seeds.txt ",1),no,to,lo,po]),a(` +import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,t as n,l as t,a,Q as o}from"./chunks/framework.b47e54aa.js";const c="/docs-preview/pr-1699/img/nodes/consensus-node.jpg",r=o("",14),i={class:"vp-code-group vp-adaptive-theme"},d=o("",1),_={class:"blocks"},y={class:"language-bash vp-adaptive-theme active"},h=s("button",{title:"Copy Code",class:"copy"},null,-1),E=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},F={class:"line"},C=o("",8),g={style:{color:"#9ECBFF"}},b={class:"shiki github-light vp-code-light"},T={class:"line"},m=o("",8),S={style:{color:"#032F62"}},v={class:"language-bash vp-adaptive-theme"},k=s("button",{title:"Copy Code",class:"copy"},null,-1),A=s("span",{class:"lang"},"bash",-1),B={class:"shiki github-dark vp-code-dark"},f={class:"line"},P=o("",8),q={style:{color:"#9ECBFF"}},I={class:"shiki github-light vp-code-light"},x={class:"line"},V=o("",8),R={style:{color:"#032F62"}},D={class:"language-bash vp-adaptive-theme"},w=s("button",{title:"Copy Code",class:"copy"},null,-1),N=s("span",{class:"lang"},"bash",-1),O={class:"shiki github-dark vp-code-dark"},$={class:"line"},M=o("",8),H={style:{color:"#9ECBFF"}},L={class:"shiki github-light vp-code-light"},Q={class:"line"},U=o("",8),j={style:{color:"#032F62"}},W=s("p",null,[a("Download the "),s("code",null,"genesis.json"),a(" file:")],-1),G={class:"vp-code-group vp-adaptive-theme"},X=o("",1),z={class:"blocks"},Y={class:"language-bash vp-adaptive-theme active"},J=s("button",{title:"Copy Code",class:"copy"},null,-1),Z=s("span",{class:"lang"},"bash",-1),K={class:"shiki github-dark vp-code-dark"},ss={class:"line"},os=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),as=s("span",{style:{color:"#E1E4E8"}}," ",-1),es=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),ns=s("span",{style:{color:"#E1E4E8"}}," ",-1),ts={style:{color:"#9ECBFF"}},ls={class:"shiki github-light vp-code-light"},ps={class:"line"},cs=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),rs=s("span",{style:{color:"#24292E"}}," ",-1),is=s("span",{style:{color:"#032F62"}},"download-genesis",-1),ds=s("span",{style:{color:"#24292E"}}," ",-1),_s={style:{color:"#032F62"}},ys={class:"language-bash vp-adaptive-theme"},hs=s("button",{title:"Copy Code",class:"copy"},null,-1),Es=s("span",{class:"lang"},"bash",-1),us={class:"shiki github-dark vp-code-dark"},Fs={class:"line"},Cs=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),gs=s("span",{style:{color:"#E1E4E8"}}," ",-1),bs=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),Ts=s("span",{style:{color:"#E1E4E8"}}," ",-1),ms={style:{color:"#9ECBFF"}},Ss={class:"shiki github-light vp-code-light"},vs={class:"line"},ks=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),As=s("span",{style:{color:"#24292E"}}," ",-1),Bs=s("span",{style:{color:"#032F62"}},"download-genesis",-1),fs=s("span",{style:{color:"#24292E"}}," ",-1),Ps={style:{color:"#032F62"}},qs={class:"language-bash vp-adaptive-theme"},Is=s("button",{title:"Copy Code",class:"copy"},null,-1),xs=s("span",{class:"lang"},"bash",-1),Vs={class:"shiki github-dark vp-code-dark"},Rs={class:"line"},Ds=s("span",{style:{color:"#B392F0"}},"celestia-appd",-1),ws=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ns=s("span",{style:{color:"#9ECBFF"}},"download-genesis",-1),Os=s("span",{style:{color:"#E1E4E8"}}," ",-1),$s={style:{color:"#9ECBFF"}},Ms={class:"shiki github-light vp-code-light"},Hs={class:"line"},Ls=s("span",{style:{color:"#6F42C1"}},"celestia-appd",-1),Qs=s("span",{style:{color:"#24292E"}}," ",-1),Us=s("span",{style:{color:"#032F62"}},"download-genesis",-1),js=s("span",{style:{color:"#24292E"}}," ",-1),Ws={style:{color:"#032F62"}},Gs=s("p",null,[a("Set seeds in the "),s("code",null,"$HOME/.celestia-app/config/config.toml"),a(" file:")],-1),Xs={class:"vp-code-group vp-adaptive-theme"},zs=o("",1),Ys={class:"blocks"},Js={class:"language-bash vp-adaptive-theme active"},Zs=s("button",{title:"Copy Code",class:"copy"},null,-1),Ks=s("span",{class:"lang"},"bash",-1),so={class:"shiki github-dark vp-code-dark"},oo={class:"line"},ao=o("",6),eo={style:{color:"#9ECBFF"}},no=s("span",{style:{color:"#F97583"}},"|",-1),to=s("span",{style:{color:"#9ECBFF"}}," ",-1),lo=s("span",{style:{color:"#B392F0"}},"tr",-1),po=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),co=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $SEEDS")],-1),ro=o("",1),io={class:"shiki github-light vp-code-light"},_o={class:"line"},yo=o("",6),ho={style:{color:"#032F62"}},Eo=s("span",{style:{color:"#D73A49"}},"|",-1),uo=s("span",{style:{color:"#032F62"}}," ",-1),Fo=s("span",{style:{color:"#6F42C1"}},"tr",-1),Co=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),go=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $SEEDS")],-1),bo=o("",1),To={class:"language-bash vp-adaptive-theme"},mo=s("button",{title:"Copy Code",class:"copy"},null,-1),So=s("span",{class:"lang"},"bash",-1),vo={class:"shiki github-dark vp-code-dark"},ko={class:"line"},Ao=o("",6),Bo={style:{color:"#9ECBFF"}},fo=s("span",{style:{color:"#F97583"}},"|",-1),Po=s("span",{style:{color:"#9ECBFF"}}," ",-1),qo=s("span",{style:{color:"#B392F0"}},"tr",-1),Io=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),xo=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $SEEDS")],-1),Vo=o("",1),Ro={class:"shiki github-light vp-code-light"},Do={class:"line"},wo=o("",6),No={style:{color:"#032F62"}},Oo=s("span",{style:{color:"#D73A49"}},"|",-1),$o=s("span",{style:{color:"#032F62"}}," ",-1),Mo=s("span",{style:{color:"#6F42C1"}},"tr",-1),Ho=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),Lo=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $SEEDS")],-1),Qo=o("",1),Uo=o("",1),jo=o("",3),Wo={class:"vp-code-group vp-adaptive-theme"},Go=o("",1),Xo={class:"blocks"},zo={class:"language-bash vp-adaptive-theme active"},Yo=s("button",{title:"Copy Code",class:"copy"},null,-1),Jo=s("span",{class:"lang"},"bash",-1),Zo={class:"shiki github-dark vp-code-dark"},Ko={class:"line"},sa=o("",6),oa={style:{color:"#9ECBFF"}},aa=o("",14),ea=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),na=o("",1),ta={class:"shiki github-light vp-code-light"},la={class:"line"},pa=o("",6),ca={style:{color:"#032F62"}},ra=o("",14),ia=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),da=o("",1),_a={class:"language-bash vp-adaptive-theme"},ya=s("button",{title:"Copy Code",class:"copy"},null,-1),ha=s("span",{class:"lang"},"bash",-1),Ea={class:"shiki github-dark vp-code-dark"},ua={class:"line"},Fa=o("",6),Ca={style:{color:"#9ECBFF"}},ga=s("span",{style:{color:"#F97583"}},"|",-1),ba=s("span",{style:{color:"#9ECBFF"}}," ",-1),Ta=s("span",{style:{color:"#B392F0"}},"tr",-1),ma=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),Sa=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),va=o("",1),ka={class:"shiki github-light vp-code-light"},Aa={class:"line"},Ba=o("",6),fa={style:{color:"#032F62"}},Pa=s("span",{style:{color:"#D73A49"}},"|",-1),qa=s("span",{style:{color:"#032F62"}}," ",-1),Ia=s("span",{style:{color:"#6F42C1"}},"tr",-1),xa=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),Va=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),Ra=o("",1),Da={class:"language-bash vp-adaptive-theme"},wa=s("button",{title:"Copy Code",class:"copy"},null,-1),Na=s("span",{class:"lang"},"bash",-1),Oa={class:"shiki github-dark vp-code-dark"},$a={class:"line"},Ma=o("",6),Ha={style:{color:"#9ECBFF"}},La=s("span",{style:{color:"#F97583"}},"|",-1),Qa=s("span",{style:{color:"#9ECBFF"}}," ",-1),Ua=s("span",{style:{color:"#B392F0"}},"tr",-1),ja=s("span",{style:{color:"#9ECBFF"}}," '\\n' ',')",-1),Wa=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"echo"),s("span",{style:{color:"#E1E4E8"}}," $PERSISTENT_PEERS")],-1),Ga=o("",1),Xa={class:"shiki github-light vp-code-light"},za={class:"line"},Ya=o("",6),Ja={style:{color:"#032F62"}},Za=s("span",{style:{color:"#D73A49"}},"|",-1),Ka=s("span",{style:{color:"#032F62"}}," ",-1),se=s("span",{style:{color:"#6F42C1"}},"tr",-1),oe=s("span",{style:{color:"#032F62"}}," '\\n' ',')",-1),ae=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"echo"),s("span",{style:{color:"#24292E"}}," $PERSISTENT_PEERS")],-1),ee=o("",1),ne=o("",33),te={class:"vp-code-group vp-adaptive-theme"},le=o("",1),pe={class:"blocks"},ce={class:"language-bash vp-adaptive-theme active"},re=s("button",{title:"Copy Code",class:"copy"},null,-1),ie=s("span",{class:"lang"},"bash",-1),de={class:"shiki github-dark vp-code-dark"},_e=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),ye=o("",1),he=o("",1),Ee=o("",1),ue={class:"line"},Fe=s("span",{style:{color:"#9ECBFF"}}," ",-1),Ce=s("span",{style:{color:"#B392F0"}},"egrep",-1),ge=s("span",{style:{color:"#9ECBFF"}}," ",-1),be=s("span",{style:{color:"#79B8FF"}},"-o",-1),Te={style:{color:"#9ECBFF"}},me=o("",6),Se=o("",1),ve=o("",1),ke={class:"shiki github-light vp-code-light"},Ae=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),Be=o("",1),fe=o("",1),Pe=o("",1),qe={class:"line"},Ie=s("span",{style:{color:"#032F62"}}," ",-1),xe=s("span",{style:{color:"#6F42C1"}},"egrep",-1),Ve=s("span",{style:{color:"#032F62"}}," ",-1),Re=s("span",{style:{color:"#005CC5"}},"-o",-1),De={style:{color:"#032F62"}},we=o("",6),Ne=o("",1),Oe=o("",1),$e={class:"language-bash vp-adaptive-theme"},Me=s("button",{title:"Copy Code",class:"copy"},null,-1),He=s("span",{class:"lang"},"bash",-1),Le={class:"shiki github-dark vp-code-dark"},Qe=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),Ue=o("",1),je=o("",1),We=o("",1),Ge={class:"line"},Xe=s("span",{style:{color:"#9ECBFF"}}," ",-1),ze=s("span",{style:{color:"#B392F0"}},"egrep",-1),Ye=s("span",{style:{color:"#9ECBFF"}}," ",-1),Je=s("span",{style:{color:"#79B8FF"}},"-o",-1),Ze={style:{color:"#9ECBFF"}},Ke=o("",6),sn=o("",1),on=o("",1),an={class:"shiki github-light vp-code-light"},en=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),nn=o("",1),tn=o("",1),ln=o("",1),pn={class:"line"},cn=s("span",{style:{color:"#032F62"}}," ",-1),rn=s("span",{style:{color:"#6F42C1"}},"egrep",-1),dn=s("span",{style:{color:"#032F62"}}," ",-1),_n=s("span",{style:{color:"#005CC5"}},"-o",-1),yn={style:{color:"#032F62"}},hn=o("",6),En=o("",1),un=o("",1),Fn={class:"language-bash vp-adaptive-theme"},Cn=s("button",{title:"Copy Code",class:"copy"},null,-1),gn=s("span",{class:"lang"},"bash",-1),bn={class:"shiki github-dark vp-code-dark"},Tn=s("span",{class:"line"},[s("span",{style:{color:"#79B8FF"}},"cd"),s("span",{style:{color:"#E1E4E8"}}," $HOME")],-1),mn=o("",1),Sn=o("",1),vn=o("",1),kn={class:"line"},An=s("span",{style:{color:"#9ECBFF"}}," ",-1),Bn=s("span",{style:{color:"#B392F0"}},"egrep",-1),fn=s("span",{style:{color:"#9ECBFF"}}," ",-1),Pn=s("span",{style:{color:"#79B8FF"}},"-o",-1),qn={style:{color:"#9ECBFF"}},In=o("",6),xn=o("",1),Vn=o("",1),Rn={class:"shiki github-light vp-code-light"},Dn=s("span",{class:"line"},[s("span",{style:{color:"#005CC5"}},"cd"),s("span",{style:{color:"#24292E"}}," $HOME")],-1),wn=o("",1),Nn=o("",1),On=o("",1),$n={class:"line"},Mn=s("span",{style:{color:"#032F62"}}," ",-1),Hn=s("span",{style:{color:"#6F42C1"}},"egrep",-1),Ln=s("span",{style:{color:"#032F62"}}," ",-1),Qn=s("span",{style:{color:"#005CC5"}},"-o",-1),Un={style:{color:"#032F62"}},jn=o("",6),Wn=o("",1),Gn=o("",1),Xn=o("",41),ot=JSON.parse('{"title":"Consensus node","description":"Learn how to set up a Celestia consensus node.","frontmatter":{"description":"Learn how to set up a Celestia consensus node.","outline":"deep","head":[["meta",{"name":"og:title","content":"Consensus node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/consensus-node.md","filePath":"nodes/consensus-node.md","lastUpdated":1725992025000}'),zn={name:"nodes/consensus-node.md"},at=Object.assign(zn,{setup(Yn){return(Jn,Zn)=>(l(),p("div",null,[r,s("div",i,[d,s("div",_,[s("div",y,[h,E,s("pre",u,[s("code",null,[s("span",F,[C,s("span",g,n(t(e).mainnetChainId),1)])])]),s("pre",b,[s("code",null,[s("span",T,[m,s("span",S,n(t(e).mainnetChainId),1)])])])]),s("div",v,[k,A,s("pre",B,[s("code",null,[s("span",f,[P,s("span",q,n(t(e).mochaChainId),1)])])]),s("pre",I,[s("code",null,[s("span",x,[V,s("span",R,n(t(e).mochaChainId),1)])])])]),s("div",D,[w,N,s("pre",O,[s("code",null,[s("span",$,[M,s("span",H,n(t(e).arabicaChainId),1)])])]),s("pre",L,[s("code",null,[s("span",Q,[U,s("span",j,n(t(e).arabicaChainId),1)])])])])])]),W,s("div",G,[X,s("div",z,[s("div",Y,[J,Z,s("pre",K,[s("code",null,[s("span",ss,[os,as,es,ns,s("span",ts,n(t(e).mainnetChainId),1)])])]),s("pre",ls,[s("code",null,[s("span",ps,[cs,rs,is,ds,s("span",_s,n(t(e).mainnetChainId),1)])])])]),s("div",ys,[hs,Es,s("pre",us,[s("code",null,[s("span",Fs,[Cs,gs,bs,Ts,s("span",ms,n(t(e).mochaChainId),1)])])]),s("pre",Ss,[s("code",null,[s("span",vs,[ks,As,Bs,fs,s("span",Ps,n(t(e).mochaChainId),1)])])])]),s("div",qs,[Is,xs,s("pre",Vs,[s("code",null,[s("span",Rs,[Ds,ws,Ns,Os,s("span",$s,n(t(e).arabicaChainId),1)])])]),s("pre",Ms,[s("code",null,[s("span",Hs,[Ls,Qs,Us,js,s("span",Ws,n(t(e).arabicaChainId),1)])])])])])]),Gs,s("div",Xs,[zs,s("div",Ys,[s("div",Js,[Zs,Ks,s("pre",so,[s("code",null,[s("span",oo,[ao,s("span",eo," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mainnetChainId)+"/seeds.txt ",1),no,to,lo,po]),a(` `),co,a(` `),ro])]),s("pre",io,[s("code",null,[s("span",_o,[yo,s("span",ho," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mainnetChainId)+"/seeds.txt ",1),Eo,uo,Fo,Co]),a(` `),go,a(` -`),To])])]),s("div",bo,[mo,So,s("pre",vo,[s("code",null,[s("span",ko,[Ao,s("span",Bo," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/seeds.txt ",1),fo,Po,qo,Io]),a(` +`),bo])])]),s("div",To,[mo,So,s("pre",vo,[s("code",null,[s("span",ko,[Ao,s("span",Bo," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/seeds.txt ",1),fo,Po,qo,Io]),a(` `),xo,a(` -`),Vo])]),s("pre",Do,[s("code",null,[s("span",Ro,[wo,s("span",No," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/seeds.txt ",1),$o,Mo,Oo,Ho]),a(` +`),Vo])]),s("pre",Ro,[s("code",null,[s("span",Do,[wo,s("span",No," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/seeds.txt ",1),Oo,$o,Mo,Ho]),a(` `),Lo,a(` -`),jo])])]),zo])]),s("details",null,[Qo,s("div",Uo,[Wo,s("div",Xo,[s("div",Go,[Jo,Ko,s("pre",Zo,[s("code",null,[s("span",Yo,[sa,s("span",oa," https://raw.githubusercontent.com/cosmos/chain-registry/master/"+n(t(e).mainnetChainId)+"/chain.json ",1),aa]),a(` +`),Qo])])]),Uo])]),s("details",null,[jo,s("div",Wo,[Go,s("div",Xo,[s("div",zo,[Yo,Jo,s("pre",Zo,[s("code",null,[s("span",Ko,[sa,s("span",oa," https://raw.githubusercontent.com/cosmos/chain-registry/master/"+n(t(e).mainnetChainId)+"/chain.json ",1),aa]),a(` `),ea,a(` `),na])]),s("pre",ta,[s("code",null,[s("span",la,[pa,s("span",ca," https://raw.githubusercontent.com/cosmos/chain-registry/master/"+n(t(e).mainnetChainId)+"/chain.json ",1),ra]),a(` `),ia,a(` -`),da])])]),s("div",_a,[ya,ha,s("pre",Ea,[s("code",null,[s("span",ua,[Fa,s("span",Ca," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/peers.txt ",1),ga,Ta,ba,ma]),a(` +`),da])])]),s("div",_a,[ya,ha,s("pre",Ea,[s("code",null,[s("span",ua,[Fa,s("span",Ca," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/peers.txt ",1),ga,ba,Ta,ma]),a(` `),Sa,a(` `),va])]),s("pre",ka,[s("code",null,[s("span",Aa,[Ba,s("span",fa," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).mochaChainId)+"/peers.txt ",1),Pa,qa,Ia,xa]),a(` `),Va,a(` -`),Da])])]),s("div",Ra,[wa,Na,s("pre",$a,[s("code",null,[s("span",Ma,[Oa,s("span",Ha," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).arabicaChainId)+"/peers.txt ",1),La,ja,za,Qa]),a(` -`),Ua,a(` -`),Wa])]),s("pre",Xa,[s("code",null,[s("span",Ga,[Ja,s("span",Ka," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).arabicaChainId)+"/peers.txt ",1),Za,Ya,se,oe]),a(` +`),Ra])])]),s("div",Da,[wa,Na,s("pre",Oa,[s("code",null,[s("span",$a,[Ma,s("span",Ha," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).arabicaChainId)+"/peers.txt ",1),La,Qa,Ua,ja]),a(` +`),Wa,a(` +`),Ga])]),s("pre",Xa,[s("code",null,[s("span",za,[Ya,s("span",Ja," https://raw.githubusercontent.com/celestiaorg/networks/master/"+n(t(e).arabicaChainId)+"/peers.txt ",1),Za,Ka,se,oe]),a(` `),ae,a(` `),ee])])])])])]),ne,s("div",te,[le,s("div",pe,[s("div",ce,[re,ie,s("pre",de,[s("code",null,[_e,a(` `),ye,a(` `),he,a(` `),Ee,a(` -`),s("span",ue,[Fe,Ce,ge,Te,s("span",be,' ">'+n(t(e).mainnetChainId)+'.*tar" ',1),me]),a(` +`),s("span",ue,[Fe,Ce,ge,be,s("span",Te,' ">'+n(t(e).mainnetChainId)+'.*tar" ',1),me]),a(` `),Se,a(` `),ve])]),s("pre",ke,[s("code",null,[Ae,a(` `),Be,a(` `),fe,a(` `),Pe,a(` -`),s("span",qe,[Ie,xe,Ve,De,s("span",Re,' ">'+n(t(e).mainnetChainId)+'.*tar" ',1),we]),a(` +`),s("span",qe,[Ie,xe,Ve,Re,s("span",De,' ">'+n(t(e).mainnetChainId)+'.*tar" ',1),we]),a(` `),Ne,a(` -`),$e])])]),s("div",Me,[Oe,He,s("pre",Le,[s("code",null,[je,a(` -`),ze,a(` -`),Qe,a(` +`),Oe])])]),s("div",$e,[Me,He,s("pre",Le,[s("code",null,[Qe,a(` `),Ue,a(` -`),s("span",We,[Xe,Ge,Je,Ke,s("span",Ze,' ">'+n(t(e).mochaChainId)+'.*tar" ',1),Ye]),a(` +`),je,a(` +`),We,a(` +`),s("span",Ge,[Xe,ze,Ye,Je,s("span",Ze,' ">'+n(t(e).mochaChainId)+'.*tar" ',1),Ke]),a(` `),sn,a(` `),on])]),s("pre",an,[s("code",null,[en,a(` `),nn,a(` @@ -42,16 +42,16 @@ import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,t `),ln,a(` `),s("span",pn,[cn,rn,dn,_n,s("span",yn,' ">'+n(t(e).mochaChainId)+'.*tar" ',1),hn]),a(` `),En,a(` -`),un])])]),s("div",Fn,[Cn,gn,s("pre",Tn,[s("code",null,[bn,a(` +`),un])])]),s("div",Fn,[Cn,gn,s("pre",bn,[s("code",null,[Tn,a(` `),mn,a(` `),Sn,a(` `),vn,a(` `),s("span",kn,[An,Bn,fn,Pn,s("span",qn,' ">'+n(t(e).arabicaChainId)+'.*tar" ',1),In]),a(` `),xn,a(` -`),Vn])]),s("pre",Dn,[s("code",null,[Rn,a(` +`),Vn])]),s("pre",Rn,[s("code",null,[Dn,a(` `),wn,a(` `),Nn,a(` -`),$n,a(` -`),s("span",Mn,[On,Hn,Ln,jn,s("span",zn,' ">'+n(t(e).arabicaChainId)+'.*tar" ',1),Qn]),a(` -`),Un,a(` -`),Wn])])])])]),Xn]))}});export{ot as __pageData,at as default}; +`),On,a(` +`),s("span",$n,[Mn,Hn,Ln,Qn,s("span",Un,' ">'+n(t(e).arabicaChainId)+'.*tar" ',1),jn]),a(` +`),Wn,a(` +`),Gn])])])])]),Xn]))}});export{ot as __pageData,at as default}; diff --git a/pr-1699/assets/nodes_decide-node.md.ce340382.js b/pr-1699/assets/nodes_decide-node.md.12527b86.js similarity index 96% rename from pr-1699/assets/nodes_decide-node.md.ce340382.js rename to pr-1699/assets/nodes_decide-node.md.12527b86.js index 6ba735b808..1961b5d8cb 100644 --- a/pr-1699/assets/nodes_decide-node.md.ce340382.js +++ b/pr-1699/assets/nodes_decide-node.md.12527b86.js @@ -1 +1 @@ -import{_ as e,o as n,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const _=JSON.parse('{"title":"Deciding which node to run","description":"Guide on helping you decide which type of node to run.","frontmatter":{"description":"Guide on helping you decide which type of node to run.","head":[["meta",{"name":"og:title","content":"Deciding which node to run | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/decide-node.md","filePath":"nodes/decide-node.md","lastUpdated":1725971357000}'),t={name:"nodes/decide-node.md"},i=a('

    Deciding which node to run ​

    Now that you have installed the basic dependencies, you can start exploring which nodes to run!

    Beginner ​

    It is highly recommended if you are a beginner to get started with running a Data-Availability light node.

    In order to get started, you can proceed to the light node section.

    You can also play around with the Data Availability API in this tutorial for posting and retrieving data with a light node.

    Advanced ​

    If you are looking to run a consensus node, please follow the tutorial for running a consensus node.

    Note that running a validator means you must also run a bridge node, which is covered in this section.

    ',9),d=[i];function r(c,h,s,l,u,p){return n(),o("div",null,d)}const f=e(t,[["render",r]]);export{_ as __pageData,f as default}; +import{_ as e,o as n,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const _=JSON.parse('{"title":"Deciding which node to run","description":"Guide on helping you decide which type of node to run.","frontmatter":{"description":"Guide on helping you decide which type of node to run.","head":[["meta",{"name":"og:title","content":"Deciding which node to run | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/decide-node.md","filePath":"nodes/decide-node.md","lastUpdated":1725992025000}'),t={name:"nodes/decide-node.md"},i=a('

    Deciding which node to run ​

    Now that you have installed the basic dependencies, you can start exploring which nodes to run!

    Beginner ​

    It is highly recommended if you are a beginner to get started with running a Data-Availability light node.

    In order to get started, you can proceed to the light node section.

    You can also play around with the Data Availability API in this tutorial for posting and retrieving data with a light node.

    Advanced ​

    If you are looking to run a consensus node, please follow the tutorial for running a consensus node.

    Note that running a validator means you must also run a bridge node, which is covered in this section.

    ',9),d=[i];function r(c,h,s,l,u,p){return n(),o("div",null,d)}const f=e(t,[["render",r]]);export{_ as __pageData,f as default}; diff --git a/pr-1699/assets/nodes_decide-node.md.ce340382.lean.js b/pr-1699/assets/nodes_decide-node.md.12527b86.lean.js similarity index 90% rename from pr-1699/assets/nodes_decide-node.md.ce340382.lean.js rename to pr-1699/assets/nodes_decide-node.md.12527b86.lean.js index c625481f4b..bd8b52148a 100644 --- a/pr-1699/assets/nodes_decide-node.md.ce340382.lean.js +++ b/pr-1699/assets/nodes_decide-node.md.12527b86.lean.js @@ -1 +1 @@ -import{_ as e,o as n,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const _=JSON.parse('{"title":"Deciding which node to run","description":"Guide on helping you decide which type of node to run.","frontmatter":{"description":"Guide on helping you decide which type of node to run.","head":[["meta",{"name":"og:title","content":"Deciding which node to run | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/decide-node.md","filePath":"nodes/decide-node.md","lastUpdated":1725971357000}'),t={name:"nodes/decide-node.md"},i=a("",9),d=[i];function r(c,h,s,l,u,p){return n(),o("div",null,d)}const f=e(t,[["render",r]]);export{_ as __pageData,f as default}; +import{_ as e,o as n,c as o,Q as a}from"./chunks/framework.b47e54aa.js";const _=JSON.parse('{"title":"Deciding which node to run","description":"Guide on helping you decide which type of node to run.","frontmatter":{"description":"Guide on helping you decide which type of node to run.","head":[["meta",{"name":"og:title","content":"Deciding which node to run | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/decide-node.md","filePath":"nodes/decide-node.md","lastUpdated":1725992025000}'),t={name:"nodes/decide-node.md"},i=a("",9),d=[i];function r(c,h,s,l,u,p){return n(),o("div",null,d)}const f=e(t,[["render",r]]);export{_ as __pageData,f as default}; diff --git a/pr-1699/assets/nodes_docker-images.md.c689a2da.js b/pr-1699/assets/nodes_docker-images.md.01970048.js similarity index 85% rename from pr-1699/assets/nodes_docker-images.md.c689a2da.js rename to pr-1699/assets/nodes_docker-images.md.01970048.js index c6bdd4945d..2b33316d08 100644 --- a/pr-1699/assets/nodes_docker-images.md.c689a2da.js +++ b/pr-1699/assets/nodes_docker-images.md.01970048.js @@ -1,59 +1,59 @@ -import{a as l}from"./chunks/arabica_versions.1930378b.js";import{m as t}from"./chunks/mocha_versions.7704b055.js";import{m as p}from"./chunks/mainnet_versions.1d5e6ed9.js";import{o as c,c as r,k as s,a,t as n,l as e,Q as o}from"./chunks/framework.b47e54aa.js";const _=o('

    🐳 Docker setup ​

    This page has instructions to run celestia-node using Docker. If you are looking for instructions to run celestia-node using a binary, please refer to the celestia-node page.

    Using Docker is the easiest way to run celestia-node for most users. Docker is a containerization platform that allows you to run celestia-node in an isolated environment.

    This means that you can run celestia-node on your machine without having to worry about installing and configuring all of the dependencies required to run the node.

    If you would like to learn more about key management in Docker, visit the Docker and cel-key section.

    The easiest way to install Docker is to use the Docker Desktop installer or Ubuntu. You can follow the instructions for your operating system.

    Prerequisites ​

    Quick start ​

    ',9),i=o('

  6. Set the network you would like to run your node on:

    bash
    export NETWORK=celestia
    export NETWORK=celestia
    bash
    export NETWORK=mocha
    export NETWORK=mocha
    bash
    export NETWORK=arabica
    export NETWORK=arabica

  7. Set the node type

    bash
    export NODE_TYPE=light
    export NODE_TYPE=light
    bash
    export NODE_TYPE=bridge
    export NODE_TYPE=bridge
    bash
    export NODE_TYPE=full
    export NODE_TYPE=full

  8. Set an RPC endpoint for either Mainnet Beta, Mocha, or Arabica using the bare URL (without http or https):

    bash
    export RPC_URL=this-is-an-rpc-url.com
    export RPC_URL=this-is-an-rpc-url.com
    9. ',3),E=s("p",null,"Run the image from the command line:",-1),y={class:"vp-code-group vp-adaptive-theme"},d=o('
    ',1),h={class:"blocks"},T={class:"language-bash vp-adaptive-theme active"},F=s("button",{title:"Copy Code",class:"copy"},null,-1),C=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},g=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),b={class:"line"},v=s("span",{style:{color:"#E1E4E8"}}," ",-1),P={style:{color:"#9ECBFF"}},k=s("span",{style:{color:"#E1E4E8"}}," ",-1),m=s("span",{style:{color:"#79B8FF"}},"\\",-1),A=o(' celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),S={class:"shiki github-light vp-code-light"},B=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),N={class:"line"},D=s("span",{style:{color:"#24292E"}}," ",-1),R={style:{color:"#032F62"}},O=s("span",{style:{color:"#24292E"}}," ",-1),I=s("span",{style:{color:"#005CC5"}},"\\",-1),V=o(' celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),f={class:"language-bash vp-adaptive-theme"},$=s("button",{title:"Copy Code",class:"copy"},null,-1),w=s("span",{class:"lang"},"bash",-1),W={class:"shiki github-dark vp-code-dark"},K=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Y={class:"line"},x=s("span",{style:{color:"#E1E4E8"}}," ",-1),M={style:{color:"#9ECBFF"}},q=s("span",{style:{color:"#E1E4E8"}}," ",-1),L=s("span",{style:{color:"#79B8FF"}},"\\",-1),H=o(' celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),U={class:"shiki github-light vp-code-light"},z=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Q={class:"line"},j=s("span",{style:{color:"#24292E"}}," ",-1),X={style:{color:"#032F62"}},J=s("span",{style:{color:"#24292E"}}," ",-1),Z=s("span",{style:{color:"#005CC5"}},"\\",-1),G=o(' celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),ss={class:"language-bash vp-adaptive-theme"},os=s("button",{title:"Copy Code",class:"copy"},null,-1),as=s("span",{class:"lang"},"bash",-1),ns={class:"shiki github-dark vp-code-dark"},es=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),ls={class:"line"},ts=s("span",{style:{color:"#E1E4E8"}}," ",-1),ps={style:{color:"#9ECBFF"}},cs=s("span",{style:{color:"#E1E4E8"}}," ",-1),rs=s("span",{style:{color:"#79B8FF"}},"\\",-1),_s=o(' celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),is={class:"shiki github-light vp-code-light"},Es=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),ys={class:"line"},ds=s("span",{style:{color:"#24292E"}}," ",-1),hs={style:{color:"#032F62"}},Ts=s("span",{style:{color:"#24292E"}}," ",-1),Fs=s("span",{style:{color:"#005CC5"}},"\\",-1),Cs=o(' celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),us=o(`

    Congratulations! You now have a celestia-node running!

    If you would like to run the node with custom flags, you can refer to the celestia-node tutorial page. Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

    Light node setup with persistent storage ​

    If you delete a container that you started above, all data will be lost. To avoid this, you can mount a volume to the container. This will allow you to persist data even after the container is deleted.

    First, you will need to create a directory on your host machine. This directory will be used to store the data for the container. Create a directory on your host machine and give it a name. For example, you can name it my-node-store:

    bash
    cd $HOME
+import{a as l}from"./chunks/arabica_versions.1930378b.js";import{m as t}from"./chunks/mocha_versions.7704b055.js";import{m as p}from"./chunks/mainnet_versions.1d5e6ed9.js";import{o as c,c as r,k as s,a,t as n,l as e,Q as o}from"./chunks/framework.b47e54aa.js";const _=o('
    🐳 Docker setup ​
    This page has instructions to run celestia-node using Docker. If you are looking for instructions to run celestia-node using a binary, please refer to the celestia-node page.
    Using Docker is the easiest way to run celestia-node for most users. Docker is a containerization platform that allows you to run celestia-node in an isolated environment.
    This means that you can run celestia-node on your machine without having to worry about installing and configuring all of the dependencies required to run the node.
    If you would like to learn more about key management in Docker, visit the Docker and cel-key section.
    The easiest way to install Docker is to use the Docker Desktop installer or Ubuntu. You can follow the instructions for your operating system.
    Prerequisites ​
    Quick start ​
    ',9),i=o('
  9. Set the network you would like to run your node on:
    bash
    export NETWORK=celestia
    export NETWORK=celestia
    bash
    export NETWORK=mocha
    export NETWORK=mocha
    bash
    export NETWORK=arabica
    export NETWORK=arabica
  10. Set the node type
    bash
    export NODE_TYPE=light
    export NODE_TYPE=light
    bash
    export NODE_TYPE=bridge
    export NODE_TYPE=bridge
    bash
    export NODE_TYPE=full
    export NODE_TYPE=full
  11. Set an RPC endpoint for either Mainnet Beta, Mocha, or Arabica using the bare URL (without http or https):
    bash
    export RPC_URL=this-is-an-rpc-url.com
    export RPC_URL=this-is-an-rpc-url.com
    12. ',3),E=s("p",null,"Run the image from the command line:",-1),y={class:"vp-code-group vp-adaptive-theme"},d=o('
    ',1),h={class:"blocks"},T={class:"language-bash vp-adaptive-theme active"},F=s("button",{title:"Copy Code",class:"copy"},null,-1),C=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},g=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),b={class:"line"},v=s("span",{style:{color:"#E1E4E8"}},"    ",-1),k={style:{color:"#9ECBFF"}},P=s("span",{style:{color:"#E1E4E8"}}," ",-1),m=s("span",{style:{color:"#79B8FF"}},"\\",-1),A=o('    celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),S={class:"shiki github-light vp-code-light"},B=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),N={class:"line"},R=s("span",{style:{color:"#24292E"}},"    ",-1),D={style:{color:"#032F62"}},O=s("span",{style:{color:"#24292E"}}," ",-1),V=s("span",{style:{color:"#005CC5"}},"\\",-1),I=o('    celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),f={class:"language-bash vp-adaptive-theme"},$=s("button",{title:"Copy Code",class:"copy"},null,-1),w=s("span",{class:"lang"},"bash",-1),Y={class:"shiki github-dark vp-code-dark"},W=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),K={class:"line"},M=s("span",{style:{color:"#E1E4E8"}},"    ",-1),x={style:{color:"#9ECBFF"}},L=s("span",{style:{color:"#E1E4E8"}}," ",-1),q=s("span",{style:{color:"#79B8FF"}},"\\",-1),H=o('    celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),U={class:"shiki github-light vp-code-light"},z=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),j={class:"line"},Q=s("span",{style:{color:"#24292E"}},"    ",-1),Z={style:{color:"#032F62"}},J=s("span",{style:{color:"#24292E"}}," ",-1),X=s("span",{style:{color:"#005CC5"}},"\\",-1),G=o('    celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),ss={class:"language-bash vp-adaptive-theme"},os=s("button",{title:"Copy Code",class:"copy"},null,-1),as=s("span",{class:"lang"},"bash",-1),ns={class:"shiki github-dark vp-code-dark"},es=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),ls={class:"line"},ts=s("span",{style:{color:"#E1E4E8"}},"    ",-1),ps={style:{color:"#9ECBFF"}},cs=s("span",{style:{color:"#E1E4E8"}}," ",-1),rs=s("span",{style:{color:"#79B8FF"}},"\\",-1),_s=o('    celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),is={class:"shiki github-light vp-code-light"},Es=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),ys={class:"line"},ds=s("span",{style:{color:"#24292E"}},"    ",-1),hs={style:{color:"#032F62"}},Ts=s("span",{style:{color:"#24292E"}}," ",-1),Fs=s("span",{style:{color:"#005CC5"}},"\\",-1),Cs=o('    celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK',1),us=o(`
    Congratulations! You now have a celestia-node running!
    If you would like to run the node with custom flags, you can refer to the celestia-node tutorial page. Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.
    Light node setup with persistent storage ​
    If you delete a container that you started above, all data will be lost. To avoid this, you can mount a volume to the container. This will allow you to persist data even after the container is deleted.
    First, you will need to create a directory on your host machine. This directory will be used to store the data for the container. Create a directory on your host machine and give it a name. For example, you can name it my-node-store:
    bash
    cd $HOME
 mkdir my-node-store
    cd $HOME
-mkdir my-node-store
    Now, you can mount this directory to the container. Before mounting a volume, you may need to set permissions for the user on the host machine by running:
    bash
    sudo chown 10001:10001 $HOME/my-node-store
    sudo chown 10001:10001 $HOME/my-node-store
    bash
    # you're good to go 😎
    # you're good to go 😎
    Initialize the node store and key ​
    In order to mount a volume to the container, you need to specify the path to the volume. When you run your container, you can specify the path to the volume using the --volume (or -v for short) flag. In this command, we'll create our key and initialize the node store, using the variables we set in the quick start section:
    bash
    # --volume == -v [local path]:[container path]
+mkdir my-node-store
    Now, you can mount this directory to the container. Before mounting a volume, you may need to set permissions for the user on the host machine by running:
    bash
    sudo chown 10001:10001 $HOME/my-node-store
    sudo chown 10001:10001 $HOME/my-node-store
    bash
    # you're good to go 😎
    # you're good to go 😎
    Initialize the node store and key ​
    In order to mount a volume to the container, you need to specify the path to the volume. When you run your container, you can specify the path to the volume using the --volume (or -v for short) flag. In this command, we'll create our key and initialize the node store, using the variables we set in the quick start section:
    bash
    # --volume == -v [local path]:[container path]
 docker run [args...] -v $HOME/my-node-store:/home/celestia \\
     celestia $NODE_TYPE init [args...]
    # --volume == -v [local path]:[container path]
 docker run [args...] -v $HOME/my-node-store:/home/celestia \\
-    celestia $NODE_TYPE init [args...]
    An example init command will look similar to below:
    `,12),gs={class:"vp-code-group vp-adaptive-theme"},bs=o('
    ',1),vs={class:"blocks"},Ps={class:"language-bash vp-adaptive-theme active"},ks=s("button",{title:"Copy Code",class:"copy"},null,-1),ms=s("span",{class:"lang"},"bash",-1),As={class:"shiki github-dark vp-code-dark"},Ss=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Bs=o('    -v $HOME/my-node-store:/home/celestia \\',1),Ns={class:"line"},Ds=s("span",{style:{color:"#E1E4E8"}},"    ",-1),Rs={style:{color:"#9ECBFF"}},Os=s("span",{style:{color:"#E1E4E8"}}," ",-1),Is=s("span",{style:{color:"#79B8FF"}},"\\",-1),Vs=o('    celestia light init --p2p.network $NETWORK',1),fs={class:"shiki github-light vp-code-light"},$s=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),ws=o('    -v $HOME/my-node-store:/home/celestia \\',1),Ws={class:"line"},Ks=s("span",{style:{color:"#24292E"}},"    ",-1),Ys={style:{color:"#032F62"}},xs=s("span",{style:{color:"#24292E"}}," ",-1),Ms=s("span",{style:{color:"#005CC5"}},"\\",-1),qs=o('    celestia light init --p2p.network $NETWORK',1),Ls={class:"language-bash vp-adaptive-theme"},Hs=s("button",{title:"Copy Code",class:"copy"},null,-1),Us=s("span",{class:"lang"},"bash",-1),zs={class:"shiki github-dark vp-code-dark"},Qs=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),js=o('    -v $HOME/my-node-store:/home/celestia \\',1),Xs={class:"line"},Js=s("span",{style:{color:"#E1E4E8"}},"    ",-1),Zs={style:{color:"#9ECBFF"}},Gs=s("span",{style:{color:"#E1E4E8"}}," ",-1),so=s("span",{style:{color:"#79B8FF"}},"\\",-1),oo=o('    celestia light init --p2p.network $NETWORK',1),ao={class:"shiki github-light vp-code-light"},no=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),eo=o('    -v $HOME/my-node-store:/home/celestia \\',1),lo={class:"line"},to=s("span",{style:{color:"#24292E"}},"    ",-1),po={style:{color:"#032F62"}},co=s("span",{style:{color:"#24292E"}}," ",-1),ro=s("span",{style:{color:"#005CC5"}},"\\",-1),_o=o('    celestia light init --p2p.network $NETWORK',1),io={class:"language-bash vp-adaptive-theme"},Eo=s("button",{title:"Copy Code",class:"copy"},null,-1),yo=s("span",{class:"lang"},"bash",-1),ho={class:"shiki github-dark vp-code-dark"},To=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Fo=o('    -v $HOME/my-node-store:/home/celestia \\',1),Co={class:"line"},uo=s("span",{style:{color:"#E1E4E8"}},"    ",-1),go={style:{color:"#9ECBFF"}},bo=s("span",{style:{color:"#E1E4E8"}}," ",-1),vo=s("span",{style:{color:"#79B8FF"}},"\\",-1),Po=o('    celestia light init --p2p.network $NETWORK',1),ko={class:"shiki github-light vp-code-light"},mo=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Ao=o('    -v $HOME/my-node-store:/home/celestia \\',1),So={class:"line"},Bo=s("span",{style:{color:"#24292E"}},"    ",-1),No={style:{color:"#032F62"}},Do=s("span",{style:{color:"#24292E"}}," ",-1),Ro=s("span",{style:{color:"#005CC5"}},"\\",-1),Oo=o('    celestia light init --p2p.network $NETWORK',1),Io=o(`
    Start the node ​
    Run the following command to start the node:
    bash
    # --volume == -v [local path]:[container path]
+    celestia $NODE_TYPE init [args...]
    An example init command will look similar to below:
    `,12),gs={class:"vp-code-group vp-adaptive-theme"},bs=o('
    ',1),vs={class:"blocks"},ks={class:"language-bash vp-adaptive-theme active"},Ps=s("button",{title:"Copy Code",class:"copy"},null,-1),ms=s("span",{class:"lang"},"bash",-1),As={class:"shiki github-dark vp-code-dark"},Ss=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Bs=o('    -v $HOME/my-node-store:/home/celestia \\',1),Ns={class:"line"},Rs=s("span",{style:{color:"#E1E4E8"}},"    ",-1),Ds={style:{color:"#9ECBFF"}},Os=s("span",{style:{color:"#E1E4E8"}}," ",-1),Vs=s("span",{style:{color:"#79B8FF"}},"\\",-1),Is=o('    celestia light init --p2p.network $NETWORK',1),fs={class:"shiki github-light vp-code-light"},$s=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),ws=o('    -v $HOME/my-node-store:/home/celestia \\',1),Ys={class:"line"},Ws=s("span",{style:{color:"#24292E"}},"    ",-1),Ks={style:{color:"#032F62"}},Ms=s("span",{style:{color:"#24292E"}}," ",-1),xs=s("span",{style:{color:"#005CC5"}},"\\",-1),Ls=o('    celestia light init --p2p.network $NETWORK',1),qs={class:"language-bash vp-adaptive-theme"},Hs=s("button",{title:"Copy Code",class:"copy"},null,-1),Us=s("span",{class:"lang"},"bash",-1),zs={class:"shiki github-dark vp-code-dark"},js=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Qs=o('    -v $HOME/my-node-store:/home/celestia \\',1),Zs={class:"line"},Js=s("span",{style:{color:"#E1E4E8"}},"    ",-1),Xs={style:{color:"#9ECBFF"}},Gs=s("span",{style:{color:"#E1E4E8"}}," ",-1),so=s("span",{style:{color:"#79B8FF"}},"\\",-1),oo=o('    celestia light init --p2p.network $NETWORK',1),ao={class:"shiki github-light vp-code-light"},no=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),eo=o('    -v $HOME/my-node-store:/home/celestia \\',1),lo={class:"line"},to=s("span",{style:{color:"#24292E"}},"    ",-1),po={style:{color:"#032F62"}},co=s("span",{style:{color:"#24292E"}}," ",-1),ro=s("span",{style:{color:"#005CC5"}},"\\",-1),_o=o('    celestia light init --p2p.network $NETWORK',1),io={class:"language-bash vp-adaptive-theme"},Eo=s("button",{title:"Copy Code",class:"copy"},null,-1),yo=s("span",{class:"lang"},"bash",-1),ho={class:"shiki github-dark vp-code-dark"},To=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Fo=o('    -v $HOME/my-node-store:/home/celestia \\',1),Co={class:"line"},uo=s("span",{style:{color:"#E1E4E8"}},"    ",-1),go={style:{color:"#9ECBFF"}},bo=s("span",{style:{color:"#E1E4E8"}}," ",-1),vo=s("span",{style:{color:"#79B8FF"}},"\\",-1),ko=o('    celestia light init --p2p.network $NETWORK',1),Po={class:"shiki github-light vp-code-light"},mo=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Ao=o('    -v $HOME/my-node-store:/home/celestia \\',1),So={class:"line"},Bo=s("span",{style:{color:"#24292E"}},"    ",-1),No={style:{color:"#032F62"}},Ro=s("span",{style:{color:"#24292E"}}," ",-1),Do=s("span",{style:{color:"#005CC5"}},"\\",-1),Oo=o('    celestia light init --p2p.network $NETWORK',1),Vo=o(`
    Start the node ​
    Run the following command to start the node:
    bash
    # --volume == -v [local path]:[container path]
 docker run [...args] -v $HOME/my-node-store:/home/celestia \\
     celestia <node-type> start [...args]
    # --volume == -v [local path]:[container path]
 docker run [...args] -v $HOME/my-node-store:/home/celestia \\
-    celestia <node-type> start [...args]
    A full start command will look similar to below.
    `,4),Vo={class:"vp-code-group vp-adaptive-theme"},fo=o('
    ',1),$o={class:"blocks"},wo={class:"language-bash vp-adaptive-theme active"},Wo=s("button",{title:"Copy Code",class:"copy"},null,-1),Ko=s("span",{class:"lang"},"bash",-1),Yo={class:"shiki github-dark vp-code-dark"},xo=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Mo=o('    -v $HOME/my-node-store:/home/celestia \\',1),qo={class:"line"},Lo=s("span",{style:{color:"#E1E4E8"}},"    ",-1),Ho={style:{color:"#9ECBFF"}},Uo=s("span",{style:{color:"#E1E4E8"}}," ",-1),zo=s("span",{style:{color:"#79B8FF"}},"\\",-1),Qo=o('    celestia light start --core.ip $RPC_URL',1),jo={class:"shiki github-light vp-code-light"},Xo=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Jo=o('    -v $HOME/my-node-store:/home/celestia \\',1),Zo={class:"line"},Go=s("span",{style:{color:"#24292E"}},"    ",-1),sa={style:{color:"#032F62"}},oa=s("span",{style:{color:"#24292E"}}," ",-1),aa=s("span",{style:{color:"#005CC5"}},"\\",-1),na=o('    celestia light start --core.ip $RPC_URL',1),ea={class:"language-bash vp-adaptive-theme"},la=s("button",{title:"Copy Code",class:"copy"},null,-1),ta=s("span",{class:"lang"},"bash",-1),pa={class:"shiki github-dark vp-code-dark"},ca=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),ra=o('    -v $HOME/my-node-store:/home/celestia \\',1),_a={class:"line"},ia=s("span",{style:{color:"#E1E4E8"}},"    ",-1),Ea={style:{color:"#9ECBFF"}},ya=s("span",{style:{color:"#E1E4E8"}}," ",-1),da=s("span",{style:{color:"#79B8FF"}},"\\",-1),ha=o('    celestia light start --core.ip $RPC_URL',1),Ta={class:"shiki github-light vp-code-light"},Fa=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Ca=o('    -v $HOME/my-node-store:/home/celestia \\',1),ua={class:"line"},ga=s("span",{style:{color:"#24292E"}},"    ",-1),ba={style:{color:"#032F62"}},va=s("span",{style:{color:"#24292E"}}," ",-1),Pa=s("span",{style:{color:"#005CC5"}},"\\",-1),ka=o('    celestia light start --core.ip $RPC_URL',1),ma={class:"language-bash vp-adaptive-theme"},Aa=s("button",{title:"Copy Code",class:"copy"},null,-1),Sa=s("span",{class:"lang"},"bash",-1),Ba={class:"shiki github-dark vp-code-dark"},Na=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Da=o('    -v $HOME/my-node-store:/home/celestia \\',1),Ra={class:"line"},Oa=s("span",{style:{color:"#E1E4E8"}},"    ",-1),Ia={style:{color:"#9ECBFF"}},Va=s("span",{style:{color:"#E1E4E8"}}," ",-1),fa=s("span",{style:{color:"#79B8FF"}},"\\",-1),$a=o('    celestia light start --core.ip $RPC_URL',1),wa={class:"shiki github-light vp-code-light"},Wa=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Ka=o('    -v $HOME/my-node-store:/home/celestia \\',1),Ya={class:"line"},xa=s("span",{style:{color:"#24292E"}},"    ",-1),Ma={style:{color:"#032F62"}},qa=s("span",{style:{color:"#24292E"}}," ",-1),La=s("span",{style:{color:"#005CC5"}},"\\",-1),Ha=o('    celestia light start --core.ip $RPC_URL',1),Ua=s("p",null,"Congratulations! You now have a node running with persistent storage.",-1),za=s("h2",{id:"video-walkthrough",tabindex:"-1"},[a("Video walkthrough "),s("a",{class:"header-anchor",href:"#video-walkthrough","aria-label":'Permalink to "Video walkthrough"'},"​")],-1),Qa=s("div",{class:"youtube-wrapper"},[s("iframe",{class:"youtube-video",title:"Running a Celestia light node",src:"https://youtube.com/embed/WFubhQc8tGk",allowfullscreen:""})],-1),ja=s("h3",{id:"_2-5-minute-version",tabindex:"-1"},[a("2.5 minute version "),s("a",{class:"header-anchor",href:"#_2-5-minute-version","aria-label":'Permalink to "2.5 minute version"'},"​")],-1),Xa=s("div",{class:"youtube-wrapper"},[s("iframe",{class:"youtube-video",title:"Running a Celestia light node",src:"https://youtube.com/embed/ROZv871Q7RM",allowfullscreen:""})],-1),Ja=s("h2",{id:"troubleshooting",tabindex:"-1"},[a("Troubleshooting "),s("a",{class:"header-anchor",href:"#troubleshooting","aria-label":'Permalink to "Troubleshooting"'},"​")],-1),Za=s("p",null,[a("For security purposes Celestia expects to interact with the your node's keys in a read-only manner. This is enforced using linux style permissions on the filesystem. Windows NTFS does not support these types of permissions. As a result the recommended path for Windows users to mount a persisted volume is to do so within WSL. You can find "),s("a",{href:"https://learn.microsoft.com/en-us/windows/wsl/install",target:"_blank",rel:"noreferrer"},"instructions for installing WSL"),a(".")],-1),pn=JSON.parse('{"title":"🐳 Docker setup","description":"Running Celestia Node using Docker.","frontmatter":{"sidebar_label":"Docker images","description":"Running Celestia Node using Docker.","head":[["meta",{"name":"og:title","content":"🐳 Docker setup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/docker-images.md","filePath":"nodes/docker-images.md","lastUpdated":1725971357000}'),Ga={name:"nodes/docker-images.md"},cn=Object.assign(Ga,{setup(sn){return(on,an)=>(c(),r("div",null,[_,s("ol",null,[i,s("li",null,[E,s("div",y,[d,s("div",h,[s("div",T,[F,C,s("pre",u,[s("code",null,[g,a(`
-`),s("span",b,[v,s("span",P,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),k,m]),a(`
+    celestia <node-type> start [...args]

    A full start command will look similar to below.

    `,4),Io={class:"vp-code-group vp-adaptive-theme"},fo=o('
    ',1),$o={class:"blocks"},wo={class:"language-bash vp-adaptive-theme active"},Yo=s("button",{title:"Copy Code",class:"copy"},null,-1),Wo=s("span",{class:"lang"},"bash",-1),Ko={class:"shiki github-dark vp-code-dark"},Mo=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),xo=o(' -v $HOME/my-node-store:/home/celestia \\',1),Lo={class:"line"},qo=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ho={style:{color:"#9ECBFF"}},Uo=s("span",{style:{color:"#E1E4E8"}}," ",-1),zo=s("span",{style:{color:"#79B8FF"}},"\\",-1),jo=o(' celestia light start --core.ip $RPC_URL',1),Qo={class:"shiki github-light vp-code-light"},Zo=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Jo=o(' -v $HOME/my-node-store:/home/celestia \\',1),Xo={class:"line"},Go=s("span",{style:{color:"#24292E"}}," ",-1),sa={style:{color:"#032F62"}},oa=s("span",{style:{color:"#24292E"}}," ",-1),aa=s("span",{style:{color:"#005CC5"}},"\\",-1),na=o(' celestia light start --core.ip $RPC_URL',1),ea={class:"language-bash vp-adaptive-theme"},la=s("button",{title:"Copy Code",class:"copy"},null,-1),ta=s("span",{class:"lang"},"bash",-1),pa={class:"shiki github-dark vp-code-dark"},ca=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),ra=o(' -v $HOME/my-node-store:/home/celestia \\',1),_a={class:"line"},ia=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ea={style:{color:"#9ECBFF"}},ya=s("span",{style:{color:"#E1E4E8"}}," ",-1),da=s("span",{style:{color:"#79B8FF"}},"\\",-1),ha=o(' celestia light start --core.ip $RPC_URL',1),Ta={class:"shiki github-light vp-code-light"},Fa=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Ca=o(' -v $HOME/my-node-store:/home/celestia \\',1),ua={class:"line"},ga=s("span",{style:{color:"#24292E"}}," ",-1),ba={style:{color:"#032F62"}},va=s("span",{style:{color:"#24292E"}}," ",-1),ka=s("span",{style:{color:"#005CC5"}},"\\",-1),Pa=o(' celestia light start --core.ip $RPC_URL',1),ma={class:"language-bash vp-adaptive-theme"},Aa=s("button",{title:"Copy Code",class:"copy"},null,-1),Sa=s("span",{class:"lang"},"bash",-1),Ba={class:"shiki github-dark vp-code-dark"},Na=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Ra=o(' -v $HOME/my-node-store:/home/celestia \\',1),Da={class:"line"},Oa=s("span",{style:{color:"#E1E4E8"}}," ",-1),Va={style:{color:"#9ECBFF"}},Ia=s("span",{style:{color:"#E1E4E8"}}," ",-1),fa=s("span",{style:{color:"#79B8FF"}},"\\",-1),$a=o(' celestia light start --core.ip $RPC_URL',1),wa={class:"shiki github-light vp-code-light"},Ya=o('docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \\',1),Wa=o(' -v $HOME/my-node-store:/home/celestia \\',1),Ka={class:"line"},Ma=s("span",{style:{color:"#24292E"}}," ",-1),xa={style:{color:"#032F62"}},La=s("span",{style:{color:"#24292E"}}," ",-1),qa=s("span",{style:{color:"#005CC5"}},"\\",-1),Ha=o(' celestia light start --core.ip $RPC_URL',1),Ua=s("p",null,"Congratulations! You now have a node running with persistent storage.",-1),za=s("h2",{id:"video-walkthrough",tabindex:"-1"},[a("Video walkthrough "),s("a",{class:"header-anchor",href:"#video-walkthrough","aria-label":'Permalink to "Video walkthrough"'},"​")],-1),ja=s("div",{class:"youtube-wrapper"},[s("iframe",{class:"youtube-video",title:"Running a Celestia light node",src:"https://youtube.com/embed/WFubhQc8tGk",allowfullscreen:""})],-1),Qa=s("h3",{id:"_2-5-minute-version",tabindex:"-1"},[a("2.5 minute version "),s("a",{class:"header-anchor",href:"#_2-5-minute-version","aria-label":'Permalink to "2.5 minute version"'},"​")],-1),Za=s("div",{class:"youtube-wrapper"},[s("iframe",{class:"youtube-video",title:"Running a Celestia light node",src:"https://youtube.com/embed/ROZv871Q7RM",allowfullscreen:""})],-1),Ja=s("h2",{id:"troubleshooting",tabindex:"-1"},[a("Troubleshooting "),s("a",{class:"header-anchor",href:"#troubleshooting","aria-label":'Permalink to "Troubleshooting"'},"​")],-1),Xa=s("p",null,[a("For security purposes Celestia expects to interact with the your node's keys in a read-only manner. This is enforced using linux style permissions on the filesystem. Windows NTFS does not support these types of permissions. As a result the recommended path for Windows users to mount a persisted volume is to do so within WSL. You can find "),s("a",{href:"https://learn.microsoft.com/en-us/windows/wsl/install",target:"_blank",rel:"noreferrer"},"instructions for installing WSL"),a(".")],-1),pn=JSON.parse('{"title":"🐳 Docker setup","description":"Running Celestia Node using Docker.","frontmatter":{"sidebar_label":"Docker images","description":"Running Celestia Node using Docker.","head":[["meta",{"name":"og:title","content":"🐳 Docker setup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/docker-images.md","filePath":"nodes/docker-images.md","lastUpdated":1725992025000}'),Ga={name:"nodes/docker-images.md"},cn=Object.assign(Ga,{setup(sn){return(on,an)=>(c(),r("div",null,[_,s("ol",null,[i,s("li",null,[E,s("div",y,[d,s("div",h,[s("div",T,[F,C,s("pre",u,[s("code",null,[g,a(` +`),s("span",b,[v,s("span",k,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),P,m]),a(` `),A])]),s("pre",S,[s("code",null,[B,a(` -`),s("span",N,[D,s("span",R,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),O,I]),a(` -`),V])])]),s("div",f,[$,w,s("pre",W,[s("code",null,[K,a(` -`),s("span",Y,[x,s("span",M,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),q,L]),a(` +`),s("span",N,[R,s("span",D,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),O,V]),a(` +`),I])])]),s("div",f,[$,w,s("pre",Y,[s("code",null,[W,a(` +`),s("span",K,[M,s("span",x,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),L,q]),a(` `),H])]),s("pre",U,[s("code",null,[z,a(` -`),s("span",Q,[j,s("span",X,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),J,Z]),a(` +`),s("span",j,[Q,s("span",Z,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),J,X]),a(` `),G])])]),s("div",ss,[os,as,s("pre",ns,[s("code",null,[es,a(` `),s("span",ls,[ts,s("span",ps,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),cs,rs]),a(` `),_s])]),s("pre",is,[s("code",null,[Es,a(` `),s("span",ys,[ds,s("span",hs,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),Ts,Fs]),a(` -`),Cs])])])])])])]),us,s("div",gs,[bs,s("div",vs,[s("div",Ps,[ks,ms,s("pre",As,[s("code",null,[Ss,a(` +`),Cs])])])])])])]),us,s("div",gs,[bs,s("div",vs,[s("div",ks,[Ps,ms,s("pre",As,[s("code",null,[Ss,a(` `),Bs,a(` -`),s("span",Ns,[Ds,s("span",Rs,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),Os,Is]),a(` -`),Vs])]),s("pre",fs,[s("code",null,[$s,a(` +`),s("span",Ns,[Rs,s("span",Ds,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),Os,Vs]),a(` +`),Is])]),s("pre",fs,[s("code",null,[$s,a(` `),ws,a(` -`),s("span",Ws,[Ks,s("span",Ys,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),xs,Ms]),a(` -`),qs])])]),s("div",Ls,[Hs,Us,s("pre",zs,[s("code",null,[Qs,a(` -`),js,a(` -`),s("span",Xs,[Js,s("span",Zs,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),Gs,so]),a(` +`),s("span",Ys,[Ws,s("span",Ks,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),Ms,xs]),a(` +`),Ls])])]),s("div",qs,[Hs,Us,s("pre",zs,[s("code",null,[js,a(` +`),Qs,a(` +`),s("span",Zs,[Js,s("span",Xs,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),Gs,so]),a(` `),oo])]),s("pre",ao,[s("code",null,[no,a(` `),eo,a(` `),s("span",lo,[to,s("span",po,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),co,ro]),a(` `),_o])])]),s("div",io,[Eo,yo,s("pre",ho,[s("code",null,[To,a(` `),Fo,a(` `),s("span",Co,[uo,s("span",go,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),bo,vo]),a(` -`),Po])]),s("pre",ko,[s("code",null,[mo,a(` +`),ko])]),s("pre",Po,[s("code",null,[mo,a(` `),Ao,a(` -`),s("span",So,[Bo,s("span",No,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),Do,Ro]),a(` -`),Oo])])])])]),Io,s("div",Vo,[fo,s("div",$o,[s("div",wo,[Wo,Ko,s("pre",Yo,[s("code",null,[xo,a(` -`),Mo,a(` -`),s("span",qo,[Lo,s("span",Ho,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),Uo,zo]),a(` -`),Qo])]),s("pre",jo,[s("code",null,[Xo,a(` +`),s("span",So,[Bo,s("span",No,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),Ro,Do]),a(` +`),Oo])])])])]),Vo,s("div",Io,[fo,s("div",$o,[s("div",wo,[Yo,Wo,s("pre",Ko,[s("code",null,[Mo,a(` +`),xo,a(` +`),s("span",Lo,[qo,s("span",Ho,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),Uo,zo]),a(` +`),jo])]),s("pre",Qo,[s("code",null,[Zo,a(` `),Jo,a(` -`),s("span",Zo,[Go,s("span",sa,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),oa,aa]),a(` +`),s("span",Xo,[Go,s("span",sa,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),oa,aa]),a(` `),na])])]),s("div",ea,[la,ta,s("pre",pa,[s("code",null,[ca,a(` `),ra,a(` `),s("span",_a,[ia,s("span",Ea,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),ya,da]),a(` `),ha])]),s("pre",Ta,[s("code",null,[Fa,a(` `),Ca,a(` -`),s("span",ua,[ga,s("span",ba,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),va,Pa]),a(` -`),ka])])]),s("div",ma,[Aa,Sa,s("pre",Ba,[s("code",null,[Na,a(` -`),Da,a(` -`),s("span",Ra,[Oa,s("span",Ia,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),Va,fa]),a(` -`),$a])]),s("pre",wa,[s("code",null,[Wa,a(` -`),Ka,a(` -`),s("span",Ya,[xa,s("span",Ma,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),qa,La]),a(` -`),Ha])])])])]),Ua,za,Qa,ja,Xa,Ja,Za]))}});export{pn as __pageData,cn as default}; +`),s("span",ua,[ga,s("span",ba,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),va,ka]),a(` +`),Pa])])]),s("div",ma,[Aa,Sa,s("pre",Ba,[s("code",null,[Na,a(` +`),Ra,a(` +`),s("span",Da,[Oa,s("span",Va,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),Ia,fa]),a(` +`),$a])]),s("pre",wa,[s("code",null,[Ya,a(` +`),Wa,a(` +`),s("span",Ka,[Ma,s("span",xa,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),La,qa]),a(` +`),Ha])])])])]),Ua,za,ja,Qa,Za,Ja,Xa]))}});export{pn as __pageData,cn as default}; diff --git a/pr-1699/assets/nodes_docker-images.md.c689a2da.lean.js b/pr-1699/assets/nodes_docker-images.md.01970048.lean.js similarity index 60% rename from pr-1699/assets/nodes_docker-images.md.c689a2da.lean.js rename to pr-1699/assets/nodes_docker-images.md.01970048.lean.js index 0ba1fdd4fa..f1fc10f8a0 100644 --- a/pr-1699/assets/nodes_docker-images.md.c689a2da.lean.js +++ b/pr-1699/assets/nodes_docker-images.md.01970048.lean.js @@ -1,49 +1,49 @@ -import{a as l}from"./chunks/arabica_versions.1930378b.js";import{m as t}from"./chunks/mocha_versions.7704b055.js";import{m as p}from"./chunks/mainnet_versions.1d5e6ed9.js";import{o as c,c as r,k as s,a,t as n,l as e,Q as o}from"./chunks/framework.b47e54aa.js";const _=o("",9),i=o("",3),E=s("p",null,"Run the image from the command line:",-1),y={class:"vp-code-group vp-adaptive-theme"},d=o("",1),h={class:"blocks"},T={class:"language-bash vp-adaptive-theme active"},F=s("button",{title:"Copy Code",class:"copy"},null,-1),C=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},g=o("",1),b={class:"line"},v=s("span",{style:{color:"#E1E4E8"}}," ",-1),P={style:{color:"#9ECBFF"}},k=s("span",{style:{color:"#E1E4E8"}}," ",-1),m=s("span",{style:{color:"#79B8FF"}},"\\",-1),A=o("",1),S={class:"shiki github-light vp-code-light"},B=o("",1),N={class:"line"},D=s("span",{style:{color:"#24292E"}}," ",-1),R={style:{color:"#032F62"}},O=s("span",{style:{color:"#24292E"}}," ",-1),I=s("span",{style:{color:"#005CC5"}},"\\",-1),V=o("",1),f={class:"language-bash vp-adaptive-theme"},$=s("button",{title:"Copy Code",class:"copy"},null,-1),w=s("span",{class:"lang"},"bash",-1),W={class:"shiki github-dark vp-code-dark"},K=o("",1),Y={class:"line"},x=s("span",{style:{color:"#E1E4E8"}}," ",-1),M={style:{color:"#9ECBFF"}},q=s("span",{style:{color:"#E1E4E8"}}," ",-1),L=s("span",{style:{color:"#79B8FF"}},"\\",-1),H=o("",1),U={class:"shiki github-light vp-code-light"},z=o("",1),Q={class:"line"},j=s("span",{style:{color:"#24292E"}}," ",-1),X={style:{color:"#032F62"}},J=s("span",{style:{color:"#24292E"}}," ",-1),Z=s("span",{style:{color:"#005CC5"}},"\\",-1),G=o("",1),ss={class:"language-bash vp-adaptive-theme"},os=s("button",{title:"Copy Code",class:"copy"},null,-1),as=s("span",{class:"lang"},"bash",-1),ns={class:"shiki github-dark vp-code-dark"},es=o("",1),ls={class:"line"},ts=s("span",{style:{color:"#E1E4E8"}}," ",-1),ps={style:{color:"#9ECBFF"}},cs=s("span",{style:{color:"#E1E4E8"}}," ",-1),rs=s("span",{style:{color:"#79B8FF"}},"\\",-1),_s=o("",1),is={class:"shiki github-light vp-code-light"},Es=o("",1),ys={class:"line"},ds=s("span",{style:{color:"#24292E"}}," ",-1),hs={style:{color:"#032F62"}},Ts=s("span",{style:{color:"#24292E"}}," ",-1),Fs=s("span",{style:{color:"#005CC5"}},"\\",-1),Cs=o("",1),us=o("",12),gs={class:"vp-code-group vp-adaptive-theme"},bs=o("",1),vs={class:"blocks"},Ps={class:"language-bash vp-adaptive-theme active"},ks=s("button",{title:"Copy Code",class:"copy"},null,-1),ms=s("span",{class:"lang"},"bash",-1),As={class:"shiki github-dark vp-code-dark"},Ss=o("",1),Bs=o("",1),Ns={class:"line"},Ds=s("span",{style:{color:"#E1E4E8"}}," ",-1),Rs={style:{color:"#9ECBFF"}},Os=s("span",{style:{color:"#E1E4E8"}}," ",-1),Is=s("span",{style:{color:"#79B8FF"}},"\\",-1),Vs=o("",1),fs={class:"shiki github-light vp-code-light"},$s=o("",1),ws=o("",1),Ws={class:"line"},Ks=s("span",{style:{color:"#24292E"}}," ",-1),Ys={style:{color:"#032F62"}},xs=s("span",{style:{color:"#24292E"}}," ",-1),Ms=s("span",{style:{color:"#005CC5"}},"\\",-1),qs=o("",1),Ls={class:"language-bash vp-adaptive-theme"},Hs=s("button",{title:"Copy Code",class:"copy"},null,-1),Us=s("span",{class:"lang"},"bash",-1),zs={class:"shiki github-dark vp-code-dark"},Qs=o("",1),js=o("",1),Xs={class:"line"},Js=s("span",{style:{color:"#E1E4E8"}}," ",-1),Zs={style:{color:"#9ECBFF"}},Gs=s("span",{style:{color:"#E1E4E8"}}," ",-1),so=s("span",{style:{color:"#79B8FF"}},"\\",-1),oo=o("",1),ao={class:"shiki github-light vp-code-light"},no=o("",1),eo=o("",1),lo={class:"line"},to=s("span",{style:{color:"#24292E"}}," ",-1),po={style:{color:"#032F62"}},co=s("span",{style:{color:"#24292E"}}," ",-1),ro=s("span",{style:{color:"#005CC5"}},"\\",-1),_o=o("",1),io={class:"language-bash vp-adaptive-theme"},Eo=s("button",{title:"Copy Code",class:"copy"},null,-1),yo=s("span",{class:"lang"},"bash",-1),ho={class:"shiki github-dark vp-code-dark"},To=o("",1),Fo=o("",1),Co={class:"line"},uo=s("span",{style:{color:"#E1E4E8"}}," ",-1),go={style:{color:"#9ECBFF"}},bo=s("span",{style:{color:"#E1E4E8"}}," ",-1),vo=s("span",{style:{color:"#79B8FF"}},"\\",-1),Po=o("",1),ko={class:"shiki github-light vp-code-light"},mo=o("",1),Ao=o("",1),So={class:"line"},Bo=s("span",{style:{color:"#24292E"}}," ",-1),No={style:{color:"#032F62"}},Do=s("span",{style:{color:"#24292E"}}," ",-1),Ro=s("span",{style:{color:"#005CC5"}},"\\",-1),Oo=o("",1),Io=o("",4),Vo={class:"vp-code-group vp-adaptive-theme"},fo=o("",1),$o={class:"blocks"},wo={class:"language-bash vp-adaptive-theme active"},Wo=s("button",{title:"Copy Code",class:"copy"},null,-1),Ko=s("span",{class:"lang"},"bash",-1),Yo={class:"shiki github-dark vp-code-dark"},xo=o("",1),Mo=o("",1),qo={class:"line"},Lo=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ho={style:{color:"#9ECBFF"}},Uo=s("span",{style:{color:"#E1E4E8"}}," ",-1),zo=s("span",{style:{color:"#79B8FF"}},"\\",-1),Qo=o("",1),jo={class:"shiki github-light vp-code-light"},Xo=o("",1),Jo=o("",1),Zo={class:"line"},Go=s("span",{style:{color:"#24292E"}}," ",-1),sa={style:{color:"#032F62"}},oa=s("span",{style:{color:"#24292E"}}," ",-1),aa=s("span",{style:{color:"#005CC5"}},"\\",-1),na=o("",1),ea={class:"language-bash vp-adaptive-theme"},la=s("button",{title:"Copy Code",class:"copy"},null,-1),ta=s("span",{class:"lang"},"bash",-1),pa={class:"shiki github-dark vp-code-dark"},ca=o("",1),ra=o("",1),_a={class:"line"},ia=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ea={style:{color:"#9ECBFF"}},ya=s("span",{style:{color:"#E1E4E8"}}," ",-1),da=s("span",{style:{color:"#79B8FF"}},"\\",-1),ha=o("",1),Ta={class:"shiki github-light vp-code-light"},Fa=o("",1),Ca=o("",1),ua={class:"line"},ga=s("span",{style:{color:"#24292E"}}," ",-1),ba={style:{color:"#032F62"}},va=s("span",{style:{color:"#24292E"}}," ",-1),Pa=s("span",{style:{color:"#005CC5"}},"\\",-1),ka=o("",1),ma={class:"language-bash vp-adaptive-theme"},Aa=s("button",{title:"Copy Code",class:"copy"},null,-1),Sa=s("span",{class:"lang"},"bash",-1),Ba={class:"shiki github-dark vp-code-dark"},Na=o("",1),Da=o("",1),Ra={class:"line"},Oa=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ia={style:{color:"#9ECBFF"}},Va=s("span",{style:{color:"#E1E4E8"}}," ",-1),fa=s("span",{style:{color:"#79B8FF"}},"\\",-1),$a=o("",1),wa={class:"shiki github-light vp-code-light"},Wa=o("",1),Ka=o("",1),Ya={class:"line"},xa=s("span",{style:{color:"#24292E"}}," ",-1),Ma={style:{color:"#032F62"}},qa=s("span",{style:{color:"#24292E"}}," ",-1),La=s("span",{style:{color:"#005CC5"}},"\\",-1),Ha=o("",1),Ua=s("p",null,"Congratulations! You now have a node running with persistent storage.",-1),za=s("h2",{id:"video-walkthrough",tabindex:"-1"},[a("Video walkthrough "),s("a",{class:"header-anchor",href:"#video-walkthrough","aria-label":'Permalink to "Video walkthrough"'},"​")],-1),Qa=s("div",{class:"youtube-wrapper"},[s("iframe",{class:"youtube-video",title:"Running a Celestia light node",src:"https://youtube.com/embed/WFubhQc8tGk",allowfullscreen:""})],-1),ja=s("h3",{id:"_2-5-minute-version",tabindex:"-1"},[a("2.5 minute version "),s("a",{class:"header-anchor",href:"#_2-5-minute-version","aria-label":'Permalink to "2.5 minute version"'},"​")],-1),Xa=s("div",{class:"youtube-wrapper"},[s("iframe",{class:"youtube-video",title:"Running a Celestia light node",src:"https://youtube.com/embed/ROZv871Q7RM",allowfullscreen:""})],-1),Ja=s("h2",{id:"troubleshooting",tabindex:"-1"},[a("Troubleshooting "),s("a",{class:"header-anchor",href:"#troubleshooting","aria-label":'Permalink to "Troubleshooting"'},"​")],-1),Za=s("p",null,[a("For security purposes Celestia expects to interact with the your node's keys in a read-only manner. This is enforced using linux style permissions on the filesystem. Windows NTFS does not support these types of permissions. As a result the recommended path for Windows users to mount a persisted volume is to do so within WSL. You can find "),s("a",{href:"https://learn.microsoft.com/en-us/windows/wsl/install",target:"_blank",rel:"noreferrer"},"instructions for installing WSL"),a(".")],-1),pn=JSON.parse('{"title":"🐳 Docker setup","description":"Running Celestia Node using Docker.","frontmatter":{"sidebar_label":"Docker images","description":"Running Celestia Node using Docker.","head":[["meta",{"name":"og:title","content":"🐳 Docker setup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/docker-images.md","filePath":"nodes/docker-images.md","lastUpdated":1725971357000}'),Ga={name:"nodes/docker-images.md"},cn=Object.assign(Ga,{setup(sn){return(on,an)=>(c(),r("div",null,[_,s("ol",null,[i,s("li",null,[E,s("div",y,[d,s("div",h,[s("div",T,[F,C,s("pre",u,[s("code",null,[g,a(` -`),s("span",b,[v,s("span",P,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),k,m]),a(` +import{a as l}from"./chunks/arabica_versions.1930378b.js";import{m as t}from"./chunks/mocha_versions.7704b055.js";import{m as p}from"./chunks/mainnet_versions.1d5e6ed9.js";import{o as c,c as r,k as s,a,t as n,l as e,Q as o}from"./chunks/framework.b47e54aa.js";const _=o("",9),i=o("",3),E=s("p",null,"Run the image from the command line:",-1),y={class:"vp-code-group vp-adaptive-theme"},d=o("",1),h={class:"blocks"},T={class:"language-bash vp-adaptive-theme active"},F=s("button",{title:"Copy Code",class:"copy"},null,-1),C=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},g=o("",1),b={class:"line"},v=s("span",{style:{color:"#E1E4E8"}}," ",-1),k={style:{color:"#9ECBFF"}},P=s("span",{style:{color:"#E1E4E8"}}," ",-1),m=s("span",{style:{color:"#79B8FF"}},"\\",-1),A=o("",1),S={class:"shiki github-light vp-code-light"},B=o("",1),N={class:"line"},R=s("span",{style:{color:"#24292E"}}," ",-1),D={style:{color:"#032F62"}},O=s("span",{style:{color:"#24292E"}}," ",-1),V=s("span",{style:{color:"#005CC5"}},"\\",-1),I=o("",1),f={class:"language-bash vp-adaptive-theme"},$=s("button",{title:"Copy Code",class:"copy"},null,-1),w=s("span",{class:"lang"},"bash",-1),Y={class:"shiki github-dark vp-code-dark"},W=o("",1),K={class:"line"},M=s("span",{style:{color:"#E1E4E8"}}," ",-1),x={style:{color:"#9ECBFF"}},L=s("span",{style:{color:"#E1E4E8"}}," ",-1),q=s("span",{style:{color:"#79B8FF"}},"\\",-1),H=o("",1),U={class:"shiki github-light vp-code-light"},z=o("",1),j={class:"line"},Q=s("span",{style:{color:"#24292E"}}," ",-1),Z={style:{color:"#032F62"}},J=s("span",{style:{color:"#24292E"}}," ",-1),X=s("span",{style:{color:"#005CC5"}},"\\",-1),G=o("",1),ss={class:"language-bash vp-adaptive-theme"},os=s("button",{title:"Copy Code",class:"copy"},null,-1),as=s("span",{class:"lang"},"bash",-1),ns={class:"shiki github-dark vp-code-dark"},es=o("",1),ls={class:"line"},ts=s("span",{style:{color:"#E1E4E8"}}," ",-1),ps={style:{color:"#9ECBFF"}},cs=s("span",{style:{color:"#E1E4E8"}}," ",-1),rs=s("span",{style:{color:"#79B8FF"}},"\\",-1),_s=o("",1),is={class:"shiki github-light vp-code-light"},Es=o("",1),ys={class:"line"},ds=s("span",{style:{color:"#24292E"}}," ",-1),hs={style:{color:"#032F62"}},Ts=s("span",{style:{color:"#24292E"}}," ",-1),Fs=s("span",{style:{color:"#005CC5"}},"\\",-1),Cs=o("",1),us=o("",12),gs={class:"vp-code-group vp-adaptive-theme"},bs=o("",1),vs={class:"blocks"},ks={class:"language-bash vp-adaptive-theme active"},Ps=s("button",{title:"Copy Code",class:"copy"},null,-1),ms=s("span",{class:"lang"},"bash",-1),As={class:"shiki github-dark vp-code-dark"},Ss=o("",1),Bs=o("",1),Ns={class:"line"},Rs=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ds={style:{color:"#9ECBFF"}},Os=s("span",{style:{color:"#E1E4E8"}}," ",-1),Vs=s("span",{style:{color:"#79B8FF"}},"\\",-1),Is=o("",1),fs={class:"shiki github-light vp-code-light"},$s=o("",1),ws=o("",1),Ys={class:"line"},Ws=s("span",{style:{color:"#24292E"}}," ",-1),Ks={style:{color:"#032F62"}},Ms=s("span",{style:{color:"#24292E"}}," ",-1),xs=s("span",{style:{color:"#005CC5"}},"\\",-1),Ls=o("",1),qs={class:"language-bash vp-adaptive-theme"},Hs=s("button",{title:"Copy Code",class:"copy"},null,-1),Us=s("span",{class:"lang"},"bash",-1),zs={class:"shiki github-dark vp-code-dark"},js=o("",1),Qs=o("",1),Zs={class:"line"},Js=s("span",{style:{color:"#E1E4E8"}}," ",-1),Xs={style:{color:"#9ECBFF"}},Gs=s("span",{style:{color:"#E1E4E8"}}," ",-1),so=s("span",{style:{color:"#79B8FF"}},"\\",-1),oo=o("",1),ao={class:"shiki github-light vp-code-light"},no=o("",1),eo=o("",1),lo={class:"line"},to=s("span",{style:{color:"#24292E"}}," ",-1),po={style:{color:"#032F62"}},co=s("span",{style:{color:"#24292E"}}," ",-1),ro=s("span",{style:{color:"#005CC5"}},"\\",-1),_o=o("",1),io={class:"language-bash vp-adaptive-theme"},Eo=s("button",{title:"Copy Code",class:"copy"},null,-1),yo=s("span",{class:"lang"},"bash",-1),ho={class:"shiki github-dark vp-code-dark"},To=o("",1),Fo=o("",1),Co={class:"line"},uo=s("span",{style:{color:"#E1E4E8"}}," ",-1),go={style:{color:"#9ECBFF"}},bo=s("span",{style:{color:"#E1E4E8"}}," ",-1),vo=s("span",{style:{color:"#79B8FF"}},"\\",-1),ko=o("",1),Po={class:"shiki github-light vp-code-light"},mo=o("",1),Ao=o("",1),So={class:"line"},Bo=s("span",{style:{color:"#24292E"}}," ",-1),No={style:{color:"#032F62"}},Ro=s("span",{style:{color:"#24292E"}}," ",-1),Do=s("span",{style:{color:"#005CC5"}},"\\",-1),Oo=o("",1),Vo=o("",4),Io={class:"vp-code-group vp-adaptive-theme"},fo=o("",1),$o={class:"blocks"},wo={class:"language-bash vp-adaptive-theme active"},Yo=s("button",{title:"Copy Code",class:"copy"},null,-1),Wo=s("span",{class:"lang"},"bash",-1),Ko={class:"shiki github-dark vp-code-dark"},Mo=o("",1),xo=o("",1),Lo={class:"line"},qo=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ho={style:{color:"#9ECBFF"}},Uo=s("span",{style:{color:"#E1E4E8"}}," ",-1),zo=s("span",{style:{color:"#79B8FF"}},"\\",-1),jo=o("",1),Qo={class:"shiki github-light vp-code-light"},Zo=o("",1),Jo=o("",1),Xo={class:"line"},Go=s("span",{style:{color:"#24292E"}}," ",-1),sa={style:{color:"#032F62"}},oa=s("span",{style:{color:"#24292E"}}," ",-1),aa=s("span",{style:{color:"#005CC5"}},"\\",-1),na=o("",1),ea={class:"language-bash vp-adaptive-theme"},la=s("button",{title:"Copy Code",class:"copy"},null,-1),ta=s("span",{class:"lang"},"bash",-1),pa={class:"shiki github-dark vp-code-dark"},ca=o("",1),ra=o("",1),_a={class:"line"},ia=s("span",{style:{color:"#E1E4E8"}}," ",-1),Ea={style:{color:"#9ECBFF"}},ya=s("span",{style:{color:"#E1E4E8"}}," ",-1),da=s("span",{style:{color:"#79B8FF"}},"\\",-1),ha=o("",1),Ta={class:"shiki github-light vp-code-light"},Fa=o("",1),Ca=o("",1),ua={class:"line"},ga=s("span",{style:{color:"#24292E"}}," ",-1),ba={style:{color:"#032F62"}},va=s("span",{style:{color:"#24292E"}}," ",-1),ka=s("span",{style:{color:"#005CC5"}},"\\",-1),Pa=o("",1),ma={class:"language-bash vp-adaptive-theme"},Aa=s("button",{title:"Copy Code",class:"copy"},null,-1),Sa=s("span",{class:"lang"},"bash",-1),Ba={class:"shiki github-dark vp-code-dark"},Na=o("",1),Ra=o("",1),Da={class:"line"},Oa=s("span",{style:{color:"#E1E4E8"}}," ",-1),Va={style:{color:"#9ECBFF"}},Ia=s("span",{style:{color:"#E1E4E8"}}," ",-1),fa=s("span",{style:{color:"#79B8FF"}},"\\",-1),$a=o("",1),wa={class:"shiki github-light vp-code-light"},Ya=o("",1),Wa=o("",1),Ka={class:"line"},Ma=s("span",{style:{color:"#24292E"}}," ",-1),xa={style:{color:"#032F62"}},La=s("span",{style:{color:"#24292E"}}," ",-1),qa=s("span",{style:{color:"#005CC5"}},"\\",-1),Ha=o("",1),Ua=s("p",null,"Congratulations! You now have a node running with persistent storage.",-1),za=s("h2",{id:"video-walkthrough",tabindex:"-1"},[a("Video walkthrough "),s("a",{class:"header-anchor",href:"#video-walkthrough","aria-label":'Permalink to "Video walkthrough"'},"​")],-1),ja=s("div",{class:"youtube-wrapper"},[s("iframe",{class:"youtube-video",title:"Running a Celestia light node",src:"https://youtube.com/embed/WFubhQc8tGk",allowfullscreen:""})],-1),Qa=s("h3",{id:"_2-5-minute-version",tabindex:"-1"},[a("2.5 minute version "),s("a",{class:"header-anchor",href:"#_2-5-minute-version","aria-label":'Permalink to "2.5 minute version"'},"​")],-1),Za=s("div",{class:"youtube-wrapper"},[s("iframe",{class:"youtube-video",title:"Running a Celestia light node",src:"https://youtube.com/embed/ROZv871Q7RM",allowfullscreen:""})],-1),Ja=s("h2",{id:"troubleshooting",tabindex:"-1"},[a("Troubleshooting "),s("a",{class:"header-anchor",href:"#troubleshooting","aria-label":'Permalink to "Troubleshooting"'},"​")],-1),Xa=s("p",null,[a("For security purposes Celestia expects to interact with the your node's keys in a read-only manner. This is enforced using linux style permissions on the filesystem. Windows NTFS does not support these types of permissions. As a result the recommended path for Windows users to mount a persisted volume is to do so within WSL. You can find "),s("a",{href:"https://learn.microsoft.com/en-us/windows/wsl/install",target:"_blank",rel:"noreferrer"},"instructions for installing WSL"),a(".")],-1),pn=JSON.parse('{"title":"🐳 Docker setup","description":"Running Celestia Node using Docker.","frontmatter":{"sidebar_label":"Docker images","description":"Running Celestia Node using Docker.","head":[["meta",{"name":"og:title","content":"🐳 Docker setup | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/docker-images.md","filePath":"nodes/docker-images.md","lastUpdated":1725992025000}'),Ga={name:"nodes/docker-images.md"},cn=Object.assign(Ga,{setup(sn){return(on,an)=>(c(),r("div",null,[_,s("ol",null,[i,s("li",null,[E,s("div",y,[d,s("div",h,[s("div",T,[F,C,s("pre",u,[s("code",null,[g,a(` +`),s("span",b,[v,s("span",k,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),P,m]),a(` `),A])]),s("pre",S,[s("code",null,[B,a(` -`),s("span",N,[D,s("span",R,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),O,I]),a(` -`),V])])]),s("div",f,[$,w,s("pre",W,[s("code",null,[K,a(` -`),s("span",Y,[x,s("span",M,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),q,L]),a(` +`),s("span",N,[R,s("span",D,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),O,V]),a(` +`),I])])]),s("div",f,[$,w,s("pre",Y,[s("code",null,[W,a(` +`),s("span",K,[M,s("span",x,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),L,q]),a(` `),H])]),s("pre",U,[s("code",null,[z,a(` -`),s("span",Q,[j,s("span",X,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),J,Z]),a(` +`),s("span",j,[Q,s("span",Z,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),J,X]),a(` `),G])])]),s("div",ss,[os,as,s("pre",ns,[s("code",null,[es,a(` `),s("span",ls,[ts,s("span",ps,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),cs,rs]),a(` `),_s])]),s("pre",is,[s("code",null,[Es,a(` `),s("span",ys,[ds,s("span",hs,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),Ts,Fs]),a(` -`),Cs])])])])])])]),us,s("div",gs,[bs,s("div",vs,[s("div",Ps,[ks,ms,s("pre",As,[s("code",null,[Ss,a(` +`),Cs])])])])])])]),us,s("div",gs,[bs,s("div",vs,[s("div",ks,[Ps,ms,s("pre",As,[s("code",null,[Ss,a(` `),Bs,a(` -`),s("span",Ns,[Ds,s("span",Rs,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),Os,Is]),a(` -`),Vs])]),s("pre",fs,[s("code",null,[$s,a(` +`),s("span",Ns,[Rs,s("span",Ds,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),Os,Vs]),a(` +`),Is])]),s("pre",fs,[s("code",null,[$s,a(` `),ws,a(` -`),s("span",Ws,[Ks,s("span",Ys,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),xs,Ms]),a(` -`),qs])])]),s("div",Ls,[Hs,Us,s("pre",zs,[s("code",null,[Qs,a(` -`),js,a(` -`),s("span",Xs,[Js,s("span",Zs,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),Gs,so]),a(` +`),s("span",Ys,[Ws,s("span",Ks,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),Ms,xs]),a(` +`),Ls])])]),s("div",qs,[Hs,Us,s("pre",zs,[s("code",null,[js,a(` +`),Qs,a(` +`),s("span",Zs,[Js,s("span",Xs,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),Gs,so]),a(` `),oo])]),s("pre",ao,[s("code",null,[no,a(` `),eo,a(` `),s("span",lo,[to,s("span",po,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),co,ro]),a(` `),_o])])]),s("div",io,[Eo,yo,s("pre",ho,[s("code",null,[To,a(` `),Fo,a(` `),s("span",Co,[uo,s("span",go,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),bo,vo]),a(` -`),Po])]),s("pre",ko,[s("code",null,[mo,a(` +`),ko])]),s("pre",Po,[s("code",null,[mo,a(` `),Ao,a(` -`),s("span",So,[Bo,s("span",No,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),Do,Ro]),a(` -`),Oo])])])])]),Io,s("div",Vo,[fo,s("div",$o,[s("div",wo,[Wo,Ko,s("pre",Yo,[s("code",null,[xo,a(` -`),Mo,a(` -`),s("span",qo,[Lo,s("span",Ho,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),Uo,zo]),a(` -`),Qo])]),s("pre",jo,[s("code",null,[Xo,a(` +`),s("span",So,[Bo,s("span",No,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),Ro,Do]),a(` +`),Oo])])])])]),Vo,s("div",Io,[fo,s("div",$o,[s("div",wo,[Yo,Wo,s("pre",Ko,[s("code",null,[Mo,a(` +`),xo,a(` +`),s("span",Lo,[qo,s("span",Ho,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),Uo,zo]),a(` +`),jo])]),s("pre",Qo,[s("code",null,[Zo,a(` `),Jo,a(` -`),s("span",Zo,[Go,s("span",sa,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),oa,aa]),a(` +`),s("span",Xo,[Go,s("span",sa,"ghcr.io/celestiaorg/celestia-node:"+n(e(p)["node-latest-tag"]),1),oa,aa]),a(` `),na])])]),s("div",ea,[la,ta,s("pre",pa,[s("code",null,[ca,a(` `),ra,a(` `),s("span",_a,[ia,s("span",Ea,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),ya,da]),a(` `),ha])]),s("pre",Ta,[s("code",null,[Fa,a(` `),Ca,a(` -`),s("span",ua,[ga,s("span",ba,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),va,Pa]),a(` -`),ka])])]),s("div",ma,[Aa,Sa,s("pre",Ba,[s("code",null,[Na,a(` -`),Da,a(` -`),s("span",Ra,[Oa,s("span",Ia,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),Va,fa]),a(` -`),$a])]),s("pre",wa,[s("code",null,[Wa,a(` -`),Ka,a(` -`),s("span",Ya,[xa,s("span",Ma,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),qa,La]),a(` -`),Ha])])])])]),Ua,za,Qa,ja,Xa,Ja,Za]))}});export{pn as __pageData,cn as default}; +`),s("span",ua,[ga,s("span",ba,"ghcr.io/celestiaorg/celestia-node:"+n(e(t)["node-latest-tag"]),1),va,ka]),a(` +`),Pa])])]),s("div",ma,[Aa,Sa,s("pre",Ba,[s("code",null,[Na,a(` +`),Ra,a(` +`),s("span",Da,[Oa,s("span",Va,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),Ia,fa]),a(` +`),$a])]),s("pre",wa,[s("code",null,[Ya,a(` +`),Wa,a(` +`),s("span",Ka,[Ma,s("span",xa,"ghcr.io/celestiaorg/celestia-node:"+n(e(l)["node-latest-tag"]),1),La,qa]),a(` +`),Ha])])])])]),Ua,za,ja,Qa,Za,Ja,Xa]))}});export{pn as __pageData,cn as default}; diff --git a/pr-1699/assets/nodes_environment.md.d3b85368.js b/pr-1699/assets/nodes_environment.md.502fd51d.js similarity index 92% rename from pr-1699/assets/nodes_environment.md.d3b85368.js rename to pr-1699/assets/nodes_environment.md.502fd51d.js index bbe5e8978c..291f24bc12 100644 --- a/pr-1699/assets/nodes_environment.md.d3b85368.js +++ b/pr-1699/assets/nodes_environment.md.502fd51d.js @@ -1,4 +1,4 @@ -import{c as a}from"./chunks/constants.295fc0ab.js";import{o as p,c as e,k as s,t as n,l as o,Q as l}from"./chunks/framework.b47e54aa.js";const t=l(`

    Development environment ​

    This page will go over setting up your development environment to run Celestia software. This environment can be used for development, building binaries, and running nodes.

    Install dependencies ​

    1. If you are on Ubuntu, first update and upgrade your OS:

      bash
      sudo apt update && sudo apt upgrade -y
      sudo apt update && sudo apt upgrade -y
      bash
      sudo yum update
      sudo yum update

    2. Install essential packages that are necessary to execute many tasks like downloading files, compiling, and monitoring the node:

      bash
      sudo apt install curl tar wget aria2 clang pkg-config libssl-dev jq build-essential \\
+import{c as a}from"./chunks/constants.295fc0ab.js";import{o as p,c as e,k as s,t as n,l as o,Q as l}from"./chunks/framework.b47e54aa.js";const t=l(`
      Development environment ​
      This page will go over setting up your development environment to run Celestia software. This environment can be used for development, building binaries, and running nodes.
      Install dependencies ​
      1. If you are on Ubuntu, first update and upgrade your OS:
        bash
        sudo apt update && sudo apt upgrade -y
        sudo apt update && sudo apt upgrade -y
        bash
        sudo yum update
        sudo yum update
      2. Install essential packages that are necessary to execute many tasks like downloading files, compiling, and monitoring the node:
        bash
        sudo apt install curl tar wget aria2 clang pkg-config libssl-dev jq build-essential \\
 git make ncdu -y
        sudo apt install curl tar wget aria2 clang pkg-config libssl-dev jq build-essential \\
 git make ncdu -y
        bash
        sudo yum install curl tar wget aria2 clang pkg-config libssl-dev jq build-essential \\
 git make ncdu -y
        sudo yum install curl tar wget aria2 clang pkg-config libssl-dev jq build-essential \\
@@ -12,7 +12,7 @@ import{c as a}from"./chunks/constants.295fc0ab.js";import{o as p,c as e,k as s,t
 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
 
 # then install wget & jq
-brew install wget && brew install jq
      Install Golang ​
      celestia-node is written in Golang so we must install Golang to build and run our node.
      `,6),c=s("p",null,"Set the version for your desired network:",-1),r={class:"vp-code-group vp-adaptive-theme"},y=l('
      ',1),E={class:"blocks"},i={class:"language-bash vp-adaptive-theme active"},d=s("button",{title:"Copy Code",class:"copy"},null,-1),F=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},g={class:"line"},h=s("span",{style:{color:"#E1E4E8"}},"ver",-1),C=s("span",{style:{color:"#F97583"}},"=",-1),b={style:{color:"#9ECBFF"}},v={class:"shiki github-light vp-code-light"},m={class:"line"},B=s("span",{style:{color:"#24292E"}},"ver",-1),_=s("span",{style:{color:"#D73A49"}},"=",-1),k={style:{color:"#032F62"}},q={class:"language-bash vp-adaptive-theme"},f=s("button",{title:"Copy Code",class:"copy"},null,-1),w=s("span",{class:"lang"},"bash",-1),$={class:"shiki github-dark vp-code-dark"},A={class:"line"},H=s("span",{style:{color:"#E1E4E8"}},"ver",-1),z=s("span",{style:{color:"#F97583"}},"=",-1),T={style:{color:"#9ECBFF"}},M={class:"shiki github-light vp-code-light"},x={class:"line"},D=s("span",{style:{color:"#24292E"}},"ver",-1),O=s("span",{style:{color:"#D73A49"}},"=",-1),S={style:{color:"#032F62"}},P={class:"language-bash vp-adaptive-theme"},I=s("button",{title:"Copy Code",class:"copy"},null,-1),N=s("span",{class:"lang"},"bash",-1),j={class:"shiki github-dark vp-code-dark"},L={class:"line"},V=s("span",{style:{color:"#E1E4E8"}},"ver",-1),U=s("span",{style:{color:"#F97583"}},"=",-1),G={style:{color:"#9ECBFF"}},Y={class:"shiki github-light vp-code-light"},Q={class:"line"},R=s("span",{style:{color:"#24292E"}},"ver",-1),J=s("span",{style:{color:"#D73A49"}},"=",-1),K={style:{color:"#032F62"}},W=l(`
    3. Download and install Golang:
      bash
      cd $HOME
+brew install wget && brew install jq

    Install Golang ​

    celestia-node is written in Golang so we must install Golang to build and run our node.

    `,6),c=s("p",null,"Set the version for your desired network:",-1),r={class:"vp-code-group vp-adaptive-theme"},y=l('
    ',1),E={class:"blocks"},i={class:"language-bash vp-adaptive-theme active"},d=s("button",{title:"Copy Code",class:"copy"},null,-1),F=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},g={class:"line"},h=s("span",{style:{color:"#E1E4E8"}},"ver",-1),C=s("span",{style:{color:"#F97583"}},"=",-1),b={style:{color:"#9ECBFF"}},v={class:"shiki github-light vp-code-light"},m={class:"line"},B=s("span",{style:{color:"#24292E"}},"ver",-1),_=s("span",{style:{color:"#D73A49"}},"=",-1),k={style:{color:"#032F62"}},q={class:"language-bash vp-adaptive-theme"},f=s("button",{title:"Copy Code",class:"copy"},null,-1),w=s("span",{class:"lang"},"bash",-1),$={class:"shiki github-dark vp-code-dark"},A={class:"line"},H=s("span",{style:{color:"#E1E4E8"}},"ver",-1),T=s("span",{style:{color:"#F97583"}},"=",-1),z={style:{color:"#9ECBFF"}},M={class:"shiki github-light vp-code-light"},x={class:"line"},D=s("span",{style:{color:"#24292E"}},"ver",-1),O=s("span",{style:{color:"#D73A49"}},"=",-1),S={style:{color:"#032F62"}},P={class:"language-bash vp-adaptive-theme"},R=s("button",{title:"Copy Code",class:"copy"},null,-1),I=s("span",{class:"lang"},"bash",-1),N={class:"shiki github-dark vp-code-dark"},j={class:"line"},V=s("span",{style:{color:"#E1E4E8"}},"ver",-1),G=s("span",{style:{color:"#F97583"}},"=",-1),L={style:{color:"#9ECBFF"}},U={class:"shiki github-light vp-code-light"},Y={class:"line"},J=s("span",{style:{color:"#24292E"}},"ver",-1),Q=s("span",{style:{color:"#D73A49"}},"=",-1),K={style:{color:"#032F62"}},X=l(`

  12. Download and install Golang:

    bash
    cd $HOME
 wget "https://golang.org/dl/go$ver.linux-amd64.tar.gz"
 sudo rm -rf /usr/local/go
 sudo tar -C /usr/local -xzf "go$ver.linux-amd64.tar.gz"
@@ -44,8 +44,8 @@ import{c as a}from"./chunks/constants.295fc0ab.js";import{o as p,c as e,k as s,t
 wget "https://golang.org/dl/go$ver.darwin-amd64.tar.gz"
 sudo rm -rf /usr/local/go
 sudo tar -C /usr/local -xzf "go$ver.darwin-amd64.tar.gz"
-rm "go$ver.darwin-amd64.tar.gz"

  13. Add your /usr/local/go/bin directory to your $PATH if you have not already:

    bash
    echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.bash_profile
+rm "go$ver.darwin-amd64.tar.gz"

  14. Add your /usr/local/go/bin directory to your $PATH if you have not already:

    bash
    echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.bash_profile
 source $HOME/.bash_profile
    echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.bash_profile
 source $HOME/.bash_profile
    bash
    echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.zshrc
 source $HOME/.zshrc
    echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.zshrc
-source $HOME/.zshrc

    TIP

    Use echo $SHELL to figure out what type of shell you are using!

  15. To verify that the correct version of Go was installed correctly run:

    bash
    go version
    go version
    16. `,3),X=s("p",null,"The output will show the version installed.",-1),ps=JSON.parse('{"title":"Development environment","description":"Learn to set up your development environment to run Celestia software.","frontmatter":{"description":"Learn to set up your development environment to run Celestia software.","head":[["meta",{"name":"og:title","content":"Development environment | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/environment.md","filePath":"nodes/environment.md","lastUpdated":1725971357000}'),Z={name:"nodes/environment.md"},es=Object.assign(Z,{setup(ss){return(as,ns)=>(p(),e("div",null,[t,s("ol",null,[s("li",null,[c,s("div",r,[y,s("div",E,[s("div",i,[d,F,s("pre",u,[s("code",null,[s("span",g,[h,C,s("span",b,'"'+n(o(a).golangNodeMainnet)+'"',1)])])]),s("pre",v,[s("code",null,[s("span",m,[B,_,s("span",k,'"'+n(o(a).golangNodeMainnet)+'"',1)])])])]),s("div",q,[f,w,s("pre",$,[s("code",null,[s("span",A,[H,z,s("span",T,'"'+n(o(a).golangNodeMocha)+'"',1)])])]),s("pre",M,[s("code",null,[s("span",x,[D,O,s("span",S,'"'+n(o(a).golangNodeMocha)+'"',1)])])])]),s("div",P,[I,N,s("pre",j,[s("code",null,[s("span",L,[V,U,s("span",G,'"'+n(o(a).golangNodeArabica)+'"',1)])])]),s("pre",Y,[s("code",null,[s("span",Q,[R,J,s("span",K,'"'+n(o(a).golangNodeArabica)+'"',1)])])])])])])]),W]),X]))}});export{ps as __pageData,es as default}; +source $HOME/.zshrc

    TIP

    Use echo $SHELL to figure out what type of shell you are using!

  16. To verify that the correct version of Go was installed correctly run:

    bash
    go version
    go version
    17. `,3),W=s("p",null,"The output will show the version installed.",-1),ps=JSON.parse('{"title":"Development environment","description":"Learn to set up your development environment to run Celestia software.","frontmatter":{"description":"Learn to set up your development environment to run Celestia software.","head":[["meta",{"name":"og:title","content":"Development environment | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/environment.md","filePath":"nodes/environment.md","lastUpdated":1725992025000}'),Z={name:"nodes/environment.md"},es=Object.assign(Z,{setup(ss){return(as,ns)=>(p(),e("div",null,[t,s("ol",null,[s("li",null,[c,s("div",r,[y,s("div",E,[s("div",i,[d,F,s("pre",u,[s("code",null,[s("span",g,[h,C,s("span",b,'"'+n(o(a).golangNodeMainnet)+'"',1)])])]),s("pre",v,[s("code",null,[s("span",m,[B,_,s("span",k,'"'+n(o(a).golangNodeMainnet)+'"',1)])])])]),s("div",q,[f,w,s("pre",$,[s("code",null,[s("span",A,[H,T,s("span",z,'"'+n(o(a).golangNodeMocha)+'"',1)])])]),s("pre",M,[s("code",null,[s("span",x,[D,O,s("span",S,'"'+n(o(a).golangNodeMocha)+'"',1)])])])]),s("div",P,[R,I,s("pre",N,[s("code",null,[s("span",j,[V,G,s("span",L,'"'+n(o(a).golangNodeArabica)+'"',1)])])]),s("pre",U,[s("code",null,[s("span",Y,[J,Q,s("span",K,'"'+n(o(a).golangNodeArabica)+'"',1)])])])])])])]),X]),W]))}});export{ps as __pageData,es as default}; diff --git a/pr-1699/assets/nodes_environment.md.d3b85368.lean.js b/pr-1699/assets/nodes_environment.md.502fd51d.lean.js similarity index 67% rename from pr-1699/assets/nodes_environment.md.d3b85368.lean.js rename to pr-1699/assets/nodes_environment.md.502fd51d.lean.js index c1df6a11be..abf031a4a5 100644 --- a/pr-1699/assets/nodes_environment.md.d3b85368.lean.js +++ b/pr-1699/assets/nodes_environment.md.502fd51d.lean.js @@ -1 +1 @@ -import{c as a}from"./chunks/constants.295fc0ab.js";import{o as p,c as e,k as s,t as n,l as o,Q as l}from"./chunks/framework.b47e54aa.js";const t=l("",6),c=s("p",null,"Set the version for your desired network:",-1),r={class:"vp-code-group vp-adaptive-theme"},y=l("",1),E={class:"blocks"},i={class:"language-bash vp-adaptive-theme active"},d=s("button",{title:"Copy Code",class:"copy"},null,-1),F=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},g={class:"line"},h=s("span",{style:{color:"#E1E4E8"}},"ver",-1),C=s("span",{style:{color:"#F97583"}},"=",-1),b={style:{color:"#9ECBFF"}},v={class:"shiki github-light vp-code-light"},m={class:"line"},B=s("span",{style:{color:"#24292E"}},"ver",-1),_=s("span",{style:{color:"#D73A49"}},"=",-1),k={style:{color:"#032F62"}},q={class:"language-bash vp-adaptive-theme"},f=s("button",{title:"Copy Code",class:"copy"},null,-1),w=s("span",{class:"lang"},"bash",-1),$={class:"shiki github-dark vp-code-dark"},A={class:"line"},H=s("span",{style:{color:"#E1E4E8"}},"ver",-1),z=s("span",{style:{color:"#F97583"}},"=",-1),T={style:{color:"#9ECBFF"}},M={class:"shiki github-light vp-code-light"},x={class:"line"},D=s("span",{style:{color:"#24292E"}},"ver",-1),O=s("span",{style:{color:"#D73A49"}},"=",-1),S={style:{color:"#032F62"}},P={class:"language-bash vp-adaptive-theme"},I=s("button",{title:"Copy Code",class:"copy"},null,-1),N=s("span",{class:"lang"},"bash",-1),j={class:"shiki github-dark vp-code-dark"},L={class:"line"},V=s("span",{style:{color:"#E1E4E8"}},"ver",-1),U=s("span",{style:{color:"#F97583"}},"=",-1),G={style:{color:"#9ECBFF"}},Y={class:"shiki github-light vp-code-light"},Q={class:"line"},R=s("span",{style:{color:"#24292E"}},"ver",-1),J=s("span",{style:{color:"#D73A49"}},"=",-1),K={style:{color:"#032F62"}},W=l("",3),X=s("p",null,"The output will show the version installed.",-1),ps=JSON.parse('{"title":"Development environment","description":"Learn to set up your development environment to run Celestia software.","frontmatter":{"description":"Learn to set up your development environment to run Celestia software.","head":[["meta",{"name":"og:title","content":"Development environment | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/environment.md","filePath":"nodes/environment.md","lastUpdated":1725971357000}'),Z={name:"nodes/environment.md"},es=Object.assign(Z,{setup(ss){return(as,ns)=>(p(),e("div",null,[t,s("ol",null,[s("li",null,[c,s("div",r,[y,s("div",E,[s("div",i,[d,F,s("pre",u,[s("code",null,[s("span",g,[h,C,s("span",b,'"'+n(o(a).golangNodeMainnet)+'"',1)])])]),s("pre",v,[s("code",null,[s("span",m,[B,_,s("span",k,'"'+n(o(a).golangNodeMainnet)+'"',1)])])])]),s("div",q,[f,w,s("pre",$,[s("code",null,[s("span",A,[H,z,s("span",T,'"'+n(o(a).golangNodeMocha)+'"',1)])])]),s("pre",M,[s("code",null,[s("span",x,[D,O,s("span",S,'"'+n(o(a).golangNodeMocha)+'"',1)])])])]),s("div",P,[I,N,s("pre",j,[s("code",null,[s("span",L,[V,U,s("span",G,'"'+n(o(a).golangNodeArabica)+'"',1)])])]),s("pre",Y,[s("code",null,[s("span",Q,[R,J,s("span",K,'"'+n(o(a).golangNodeArabica)+'"',1)])])])])])])]),W]),X]))}});export{ps as __pageData,es as default}; +import{c as a}from"./chunks/constants.295fc0ab.js";import{o as p,c as e,k as s,t as n,l as o,Q as l}from"./chunks/framework.b47e54aa.js";const t=l("",6),c=s("p",null,"Set the version for your desired network:",-1),r={class:"vp-code-group vp-adaptive-theme"},y=l("",1),E={class:"blocks"},i={class:"language-bash vp-adaptive-theme active"},d=s("button",{title:"Copy Code",class:"copy"},null,-1),F=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},g={class:"line"},h=s("span",{style:{color:"#E1E4E8"}},"ver",-1),C=s("span",{style:{color:"#F97583"}},"=",-1),b={style:{color:"#9ECBFF"}},v={class:"shiki github-light vp-code-light"},m={class:"line"},B=s("span",{style:{color:"#24292E"}},"ver",-1),_=s("span",{style:{color:"#D73A49"}},"=",-1),k={style:{color:"#032F62"}},q={class:"language-bash vp-adaptive-theme"},f=s("button",{title:"Copy Code",class:"copy"},null,-1),w=s("span",{class:"lang"},"bash",-1),$={class:"shiki github-dark vp-code-dark"},A={class:"line"},H=s("span",{style:{color:"#E1E4E8"}},"ver",-1),T=s("span",{style:{color:"#F97583"}},"=",-1),z={style:{color:"#9ECBFF"}},M={class:"shiki github-light vp-code-light"},x={class:"line"},D=s("span",{style:{color:"#24292E"}},"ver",-1),O=s("span",{style:{color:"#D73A49"}},"=",-1),S={style:{color:"#032F62"}},P={class:"language-bash vp-adaptive-theme"},R=s("button",{title:"Copy Code",class:"copy"},null,-1),I=s("span",{class:"lang"},"bash",-1),N={class:"shiki github-dark vp-code-dark"},j={class:"line"},V=s("span",{style:{color:"#E1E4E8"}},"ver",-1),G=s("span",{style:{color:"#F97583"}},"=",-1),L={style:{color:"#9ECBFF"}},U={class:"shiki github-light vp-code-light"},Y={class:"line"},J=s("span",{style:{color:"#24292E"}},"ver",-1),Q=s("span",{style:{color:"#D73A49"}},"=",-1),K={style:{color:"#032F62"}},X=l("",3),W=s("p",null,"The output will show the version installed.",-1),ps=JSON.parse('{"title":"Development environment","description":"Learn to set up your development environment to run Celestia software.","frontmatter":{"description":"Learn to set up your development environment to run Celestia software.","head":[["meta",{"name":"og:title","content":"Development environment | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/environment.md","filePath":"nodes/environment.md","lastUpdated":1725992025000}'),Z={name:"nodes/environment.md"},es=Object.assign(Z,{setup(ss){return(as,ns)=>(p(),e("div",null,[t,s("ol",null,[s("li",null,[c,s("div",r,[y,s("div",E,[s("div",i,[d,F,s("pre",u,[s("code",null,[s("span",g,[h,C,s("span",b,'"'+n(o(a).golangNodeMainnet)+'"',1)])])]),s("pre",v,[s("code",null,[s("span",m,[B,_,s("span",k,'"'+n(o(a).golangNodeMainnet)+'"',1)])])])]),s("div",q,[f,w,s("pre",$,[s("code",null,[s("span",A,[H,T,s("span",z,'"'+n(o(a).golangNodeMocha)+'"',1)])])]),s("pre",M,[s("code",null,[s("span",x,[D,O,s("span",S,'"'+n(o(a).golangNodeMocha)+'"',1)])])])]),s("div",P,[R,I,s("pre",N,[s("code",null,[s("span",j,[V,G,s("span",L,'"'+n(o(a).golangNodeArabica)+'"',1)])])]),s("pre",U,[s("code",null,[s("span",Y,[J,Q,s("span",K,'"'+n(o(a).golangNodeArabica)+'"',1)])])])])])])]),X]),W]))}});export{ps as __pageData,es as default}; diff --git a/pr-1699/assets/nodes_full-storage-node.md.3d825d2f.js b/pr-1699/assets/nodes_full-storage-node.md.27554da6.js similarity index 96% rename from pr-1699/assets/nodes_full-storage-node.md.3d825d2f.js rename to pr-1699/assets/nodes_full-storage-node.md.27554da6.js index 86434f1ea4..67e4e922e0 100644 --- a/pr-1699/assets/nodes_full-storage-node.md.3d825d2f.js +++ b/pr-1699/assets/nodes_full-storage-node.md.27554da6.js @@ -1,4 +1,4 @@ -import{_ as s,o as a,c as e,Q as o}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/nodes/full-storage-node.png",g=JSON.parse('{"title":"Setting up a Celestia full storage Node","description":"Set up a Celestia full storage node.","frontmatter":{"description":"Set up a Celestia full storage node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia full storage Node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/full-storage-node.md","filePath":"nodes/full-storage-node.md","lastUpdated":1725971357000}'),n={name:"nodes/full-storage-node.md"},t=o('

    Setting up a Celestia full storage Node ​

    This tutorial will guide you through setting up a Celestia full storage node, which is a celestia-node that doesn't connect to celestia-app (hence not a consensus node), but stores all the data.

    Overview of full storage nodes ​

    Full storage nodes are Celestia nodes that store all the data. Full storage nodes send block shares, headers, and fraud proofs to light nodes. The light nodes gossip headers, fraud proofs, and sometimes block shares, between one another.

    Full storage node

    Hardware requirements ​

    The following hardware minimum requirements are recommended for running the full storage node:

    Setting up your full storage node ​

    The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.

    Setup the dependencies ​

    You can follow the tutorial for setting up your dependencies

    Install celestia-node ​

    You can follow the tutorial for installing celestia-node

    Run the full storage node ​

    Initialize the full storage node ​

    Run the following command:

    sh
    celestia full init
    celestia full init
    sh
    celestia full init --p2p.network mocha
    celestia full init --p2p.network mocha
    sh
    celestia full init --p2p.network arabica
    celestia full init --p2p.network arabica

    Start the full storage node ​

    Start the full storage node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):

    In order for access to the ability to get/submit state-related information, such as the ability to submit PayForBlob transactions, or query for the node's account balance, a gRPC endpoint of a validator (core) node must be passed as directed below.

    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

    sh
    celestia full start --core.ip <URI>
    celestia full start --core.ip <URI>

    Using an RPC of your own, or one from the list on the Mocha testnet page or list on the Arabica devnet page, start your node.

    Connecting to a core endpoint with --core.ip string provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).

    You can create your key for your node by following the cel-key instructions

    Once you start the full storage node, a wallet key will be generated for you. You will need to fund that address with testnet tokens to pay for PayForBlob transactions. You can find the address by running the following command:

    sh
    ./cel-key list --node.type full --keyring-backend test --p2p.network <network>
    ./cel-key list --node.type full --keyring-backend test --p2p.network <network>

    TIP

    You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information

    You can get testnet tokens from:

    NOTE

    If you are running a full-storage node for your sovereign rollup, it is highly recommended to request Arabica devnet tokens as Arabica has the latest changes that can be used to test for developing your sovereign rollup. You can still use Mocha testnet as well, it is just mostly used for validator operations.

    Optional: run the full storage node with a custom key ​

    In order to run a full storage node using a custom key:

    1. The custom key must exist inside the celestia full storage node directory at the correct path (default: ~/.celestia-full/keys/keyring-test)
    2. The name of the custom key must be passed upon start, like so:
    sh
    celestia full start --core.ip <URI> \\
+import{_ as s,o as a,c as e,Q as o}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/nodes/full-storage-node.png",g=JSON.parse('{"title":"Setting up a Celestia full storage Node","description":"Set up a Celestia full storage node.","frontmatter":{"description":"Set up a Celestia full storage node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia full storage Node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/full-storage-node.md","filePath":"nodes/full-storage-node.md","lastUpdated":1725992025000}'),n={name:"nodes/full-storage-node.md"},t=o('
    Setting up a Celestia full storage Node ​
    This tutorial will guide you through setting up a Celestia full storage node, which is a celestia-node that doesn't connect to celestia-app (hence not a consensus node), but stores all the data.
    Overview of full storage nodes ​
    Full storage nodes are Celestia nodes that store all the data. Full storage nodes send block shares, headers, and fraud proofs to light nodes. The light nodes gossip headers, fraud proofs, and sometimes block shares, between one another.
    Full storage node
    Hardware requirements ​
    The following hardware minimum requirements are recommended for running the full storage node:
    • Memory: 16 GB RAM (minimum)
    • CPU: 6 cores
    • Disk: 10 TB SSD Storage
    • Bandwidth: 1 Gbps for Download/1 Gbps for Upload
    Setting up your full storage node ​
    The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.
    Setup the dependencies ​
    You can follow the tutorial for setting up your dependencies
    Install celestia-node ​
    You can follow the tutorial for installing celestia-node
    Run the full storage node ​
    Initialize the full storage node ​
    Run the following command:
    sh
    celestia full init
    celestia full init
    sh
    celestia full init --p2p.network mocha
    celestia full init --p2p.network mocha
    sh
    celestia full init --p2p.network arabica
    celestia full init --p2p.network arabica
    Start the full storage node ​
    Start the full storage node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):
    In order for access to the ability to get/submit state-related information, such as the ability to submit PayForBlob transactions, or query for the node's account balance, a gRPC endpoint of a validator (core) node must be passed as directed below.
    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.
    sh
    celestia full start --core.ip <URI>
    celestia full start --core.ip <URI>
    Using an RPC of your own, or one from the list on the Mocha testnet page or list on the Arabica devnet page, start your node.
    Connecting to a core endpoint with --core.ip string provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).
    You can create your key for your node by following the cel-key instructions
    Once you start the full storage node, a wallet key will be generated for you. You will need to fund that address with testnet tokens to pay for PayForBlob transactions. You can find the address by running the following command:
    sh
    ./cel-key list --node.type full --keyring-backend test --p2p.network <network>
    ./cel-key list --node.type full --keyring-backend test --p2p.network <network>
    TIP
    You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information
    You can get testnet tokens from:
    NOTE
    If you are running a full-storage node for your sovereign rollup, it is highly recommended to request Arabica devnet tokens as Arabica has the latest changes that can be used to test for developing your sovereign rollup. You can still use Mocha testnet as well, it is just mostly used for validator operations.
    Optional: run the full storage node with a custom key ​
    In order to run a full storage node using a custom key:
    1. The custom key must exist inside the celestia full storage node directory at the correct path (default: ~/.celestia-full/keys/keyring-test)
    2. The name of the custom key must be passed upon start, like so:
    sh
    celestia full start --core.ip <URI> \\
   --keyring.keyname <name-of-custom-key> \\
    celestia full start --core.ip <URI> \\
   --keyring.keyname <name-of-custom-key> \\
    sh
    celestia full start --core.ip <URI> \\
   --keyring.keyname <name-of-custom-key> \\
diff --git a/pr-1699/assets/nodes_full-storage-node.md.3d825d2f.lean.js b/pr-1699/assets/nodes_full-storage-node.md.27554da6.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_full-storage-node.md.3d825d2f.lean.js
rename to pr-1699/assets/nodes_full-storage-node.md.27554da6.lean.js
index c7cbe6ecbe..d368da61c1 100644
--- a/pr-1699/assets/nodes_full-storage-node.md.3d825d2f.lean.js
+++ b/pr-1699/assets/nodes_full-storage-node.md.27554da6.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as e,Q as o}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/nodes/full-storage-node.png",g=JSON.parse('{"title":"Setting up a Celestia full storage Node","description":"Set up a Celestia full storage node.","frontmatter":{"description":"Set up a Celestia full storage node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia full storage Node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/full-storage-node.md","filePath":"nodes/full-storage-node.md","lastUpdated":1725971357000}'),n={name:"nodes/full-storage-node.md"},t=o("",44),p=[t];function r(c,i,d,y,u,h){return a(),e("div",null,p)}const f=s(n,[["render",r]]);export{g as __pageData,f as default};
+import{_ as s,o as a,c as e,Q as o}from"./chunks/framework.b47e54aa.js";const l="/docs-preview/pr-1699/img/nodes/full-storage-node.png",g=JSON.parse('{"title":"Setting up a Celestia full storage Node","description":"Set up a Celestia full storage node.","frontmatter":{"description":"Set up a Celestia full storage node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia full storage Node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/full-storage-node.md","filePath":"nodes/full-storage-node.md","lastUpdated":1725992025000}'),n={name:"nodes/full-storage-node.md"},t=o("",44),p=[t];function r(c,i,d,y,u,h){return a(),e("div",null,p)}const f=s(n,[["render",r]]);export{g as __pageData,f as default};
diff --git a/pr-1699/assets/nodes_hardfork-process.md.d852b283.js b/pr-1699/assets/nodes_hardfork-process.md.b85c06e7.js
similarity index 97%
rename from pr-1699/assets/nodes_hardfork-process.md.d852b283.js
rename to pr-1699/assets/nodes_hardfork-process.md.b85c06e7.js
index 5838193e3f..3acbf1ac59 100644
--- a/pr-1699/assets/nodes_hardfork-process.md.d852b283.js
+++ b/pr-1699/assets/nodes_hardfork-process.md.b85c06e7.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as r}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Celestia hardfork process","description":"Overview of the Celestia hardfork process.","frontmatter":{"description":"Overview of the Celestia hardfork process.","head":[["meta",{"name":"og:title","content":"Celestia hardfork process | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/hardfork-process.md","filePath":"nodes/hardfork-process.md","lastUpdated":1725971357000}'),o={name:"nodes/hardfork-process.md"},i=r('
    Celestia hardfork process ​
    Blockchain networks often times need to upgrade with new features which require coordination work among the validators prior to activating the upgrades.
    This process is called a hardfork or a network upgrade. In those events, the Celestia Labs team will be coordinating with the validators on what they need to do in order to be ready for an upcoming hardfork.
    Hardforks are not backward-compatible with older versions of the network software which is why it is important that validators upgrade their software to continue validating on the network after the network upgrades.
    General process ​
    The general process can be broken down into several components:
    • Hardfork specifications and features (defined by description of features and code implementation of those features).
    • Binary used to add those features (a new binary release with those features will be provided by Celestia team in order for validators to upgrade their nodes to the new binary).
    • A block number for when the network upgrades (even if validators upgrade their binary to be hardfork ready, the network upgrade does not happen right away, but some short time in the future at a specific block number).
    • Testing of the features (happens on testnets first prior to activating on mainnet in order to ensure the network can upgrade securely).
    The two testnets where hardforks are deployed are:
    Lemongrass hardfork ​
    The Lemongrass hardfork is the first consensus layer breaking change since Celestia's Mainnet Beta genesis block. The Lemongrass hardfork includes all of the CIPs listed in CIP-17. The Lemongrass hardfork will be executed on Arabica, then Mocha, then Mainnet Beta. The hardfork will take place at an "upgrade height" that will be coordinated offline on a per-network basis. The upgrade heights will be announced in advance (see Network upgrades) to give node operators time to download and start a compatible binary prior to the upgrade height.
    • If you are a consensus node or validator operator: you will need to download and run a celestia-app binary >= v2.0.0 prior to the --v2-upgrade-height to remain on the canonical chain. You do not need to use a tool like cosmovisor to upgrade the binary at the upgrade height.
    • If you are a DA node operator, you will need to download and run a compatible celestia-node binary >= v0.16.0-rc0 prior to the upgrade height.
    NetworkChain IDDate and approximate time--v2-upgrade-height
    Arabicaarabica-112024/08/19 @ 14:00 UTC1751707
    Mochamocha-42024/08/28 @ 14:00 UTC2585031
    Mainnet Betacelestia2024/09/18 @ 14:00 UTC2371495
    ',13),s=[i];function n(d,h,l,c,p,f){return t(),a("div",null,s)}const k=e(o,[["render",n]]);export{g as __pageData,k as default};
+import{_ as e,o as t,c as a,Q as r}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Celestia hardfork process","description":"Overview of the Celestia hardfork process.","frontmatter":{"description":"Overview of the Celestia hardfork process.","head":[["meta",{"name":"og:title","content":"Celestia hardfork process | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/hardfork-process.md","filePath":"nodes/hardfork-process.md","lastUpdated":1725992025000}'),o={name:"nodes/hardfork-process.md"},i=r('
    Celestia hardfork process ​
    Blockchain networks often times need to upgrade with new features which require coordination work among the validators prior to activating the upgrades.
    This process is called a hardfork or a network upgrade. In those events, the Celestia Labs team will be coordinating with the validators on what they need to do in order to be ready for an upcoming hardfork.
    Hardforks are not backward-compatible with older versions of the network software which is why it is important that validators upgrade their software to continue validating on the network after the network upgrades.
    General process ​
    The general process can be broken down into several components:
    • Hardfork specifications and features (defined by description of features and code implementation of those features).
    • Binary used to add those features (a new binary release with those features will be provided by Celestia team in order for validators to upgrade their nodes to the new binary).
    • A block number for when the network upgrades (even if validators upgrade their binary to be hardfork ready, the network upgrade does not happen right away, but some short time in the future at a specific block number).
    • Testing of the features (happens on testnets first prior to activating on mainnet in order to ensure the network can upgrade securely).
    The two testnets where hardforks are deployed are:
    Lemongrass hardfork ​
    The Lemongrass hardfork is the first consensus layer breaking change since Celestia's Mainnet Beta genesis block. The Lemongrass hardfork includes all of the CIPs listed in CIP-17. The Lemongrass hardfork will be executed on Arabica, then Mocha, then Mainnet Beta. The hardfork will take place at an "upgrade height" that will be coordinated offline on a per-network basis. The upgrade heights will be announced in advance (see Network upgrades) to give node operators time to download and start a compatible binary prior to the upgrade height.
    • If you are a consensus node or validator operator: you will need to download and run a celestia-app binary >= v2.0.0 prior to the --v2-upgrade-height to remain on the canonical chain. You do not need to use a tool like cosmovisor to upgrade the binary at the upgrade height.
    • If you are a DA node operator, you will need to download and run a compatible celestia-node binary >= v0.16.0-rc0 prior to the upgrade height.
    NetworkChain IDDate and approximate time--v2-upgrade-height
    Arabicaarabica-112024/08/19 @ 14:00 UTC1751707
    Mochamocha-42024/08/28 @ 14:00 UTC2585031
    Mainnet Betacelestia2024/09/18 @ 14:00 UTC2371495
    ',13),s=[i];function n(d,h,l,c,p,f){return t(),a("div",null,s)}const k=e(o,[["render",n]]);export{g as __pageData,k as default};
diff --git a/pr-1699/assets/nodes_hardfork-process.md.d852b283.lean.js b/pr-1699/assets/nodes_hardfork-process.md.b85c06e7.lean.js
similarity index 81%
rename from pr-1699/assets/nodes_hardfork-process.md.d852b283.lean.js
rename to pr-1699/assets/nodes_hardfork-process.md.b85c06e7.lean.js
index 004dce6541..30ebf13add 100644
--- a/pr-1699/assets/nodes_hardfork-process.md.d852b283.lean.js
+++ b/pr-1699/assets/nodes_hardfork-process.md.b85c06e7.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as r}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Celestia hardfork process","description":"Overview of the Celestia hardfork process.","frontmatter":{"description":"Overview of the Celestia hardfork process.","head":[["meta",{"name":"og:title","content":"Celestia hardfork process | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/hardfork-process.md","filePath":"nodes/hardfork-process.md","lastUpdated":1725971357000}'),o={name:"nodes/hardfork-process.md"},i=r("",13),s=[i];function n(d,h,l,c,p,f){return t(),a("div",null,s)}const k=e(o,[["render",n]]);export{g as __pageData,k as default};
+import{_ as e,o as t,c as a,Q as r}from"./chunks/framework.b47e54aa.js";const g=JSON.parse('{"title":"Celestia hardfork process","description":"Overview of the Celestia hardfork process.","frontmatter":{"description":"Overview of the Celestia hardfork process.","head":[["meta",{"name":"og:title","content":"Celestia hardfork process | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/hardfork-process.md","filePath":"nodes/hardfork-process.md","lastUpdated":1725992025000}'),o={name:"nodes/hardfork-process.md"},i=r("",13),s=[i];function n(d,h,l,c,p,f){return t(),a("div",null,s)}const k=e(o,[["render",n]]);export{g as __pageData,k as default};
diff --git a/pr-1699/assets/nodes_ibc-relayer.md.3c1ba349.js b/pr-1699/assets/nodes_ibc-relayer.md.450545b1.js
similarity index 99%
rename from pr-1699/assets/nodes_ibc-relayer.md.3c1ba349.js
rename to pr-1699/assets/nodes_ibc-relayer.md.450545b1.js
index f5ba462b5b..2c17e042e9 100644
--- a/pr-1699/assets/nodes_ibc-relayer.md.3c1ba349.js
+++ b/pr-1699/assets/nodes_ibc-relayer.md.450545b1.js
@@ -1,4 +1,4 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"IBC relaying guide","description":"Learn how to establish IBC connections and relay packets.","frontmatter":{"description":"Learn how to establish IBC connections and relay packets.","next":{"text":"Metrics","link":"/nodes/celestia-node-metrics"},"head":[["meta",{"name":"og:title","content":"IBC relaying guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/ibc-relayer.md","filePath":"nodes/ibc-relayer.md","lastUpdated":1725971357000}'),p={name:"nodes/ibc-relayer.md"},o=l(`
    IBC relaying guide ​
    Celestia uses IBC (Inter-Blockchain Communication protocol) to enable cross-chain transfer of tokens. To support this capability it relies on relayers, processes that can be run by anyone which constantly scan for outbound packets on one chain and submits these packets alongside corresponding proofs on the destination chain. This section describes how one can setup a relayer and create new connections between chains. There are two standard implementations:
    The following guide explains how to establish IBC connections and relay packets between Mocha testnet and Cosmos hub testnet networks by using the Hermes relayer.
    Check the latest celestia-app release's go.mod for the version of ibc-go that is currently used.
    Hermes ​
    Hermes is an open-source Rust implementation of an IBC relayer released as part of the ibc-relayer-cli crate. It includes a CLI for relaying packets between Cosmos SDK chains, as well as Prometheus metrics and a REST API.
    Please follow the steps at Hermes Quick Start to install Hermes. Before proceeding, verify that Hermes is installed correctly by running hermes version.
    TIP
    Hermes currently doesn't support configuring the Tendermint CompatMode in chain config (see hermes#3623). Until that issue is resolved, please use Hermes v1.7.0+ because it falls back to Tendermint CompatMode v0.34 (see hermes#3663) which is compatible with Celestia.
    Configuration ​
    After you have successfully installed Hermes and created the necessary folders, you now have to edit config.toml and add the appropriate configurations for the chains you want to relay between.
    For this tutorial, we will be using the following chains:
    • Celestia's mocha-4 testnet
    • Cosmos Hub's theta-testnet-001 testnet
    Edit the Hermes configuration.
    bash
    vim $HOME/.hermes/config.toml
    vim $HOME/.hermes/config.toml
    toml
    [global]
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"IBC relaying guide","description":"Learn how to establish IBC connections and relay packets.","frontmatter":{"description":"Learn how to establish IBC connections and relay packets.","next":{"text":"Metrics","link":"/nodes/celestia-node-metrics"},"head":[["meta",{"name":"og:title","content":"IBC relaying guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/ibc-relayer.md","filePath":"nodes/ibc-relayer.md","lastUpdated":1725992025000}'),p={name:"nodes/ibc-relayer.md"},o=l(`
    IBC relaying guide ​
    Celestia uses IBC (Inter-Blockchain Communication protocol) to enable cross-chain transfer of tokens. To support this capability it relies on relayers, processes that can be run by anyone which constantly scan for outbound packets on one chain and submits these packets alongside corresponding proofs on the destination chain. This section describes how one can setup a relayer and create new connections between chains. There are two standard implementations:
    The following guide explains how to establish IBC connections and relay packets between Mocha testnet and Cosmos hub testnet networks by using the Hermes relayer.
    Check the latest celestia-app release's go.mod for the version of ibc-go that is currently used.
    Hermes ​
    Hermes is an open-source Rust implementation of an IBC relayer released as part of the ibc-relayer-cli crate. It includes a CLI for relaying packets between Cosmos SDK chains, as well as Prometheus metrics and a REST API.
    Please follow the steps at Hermes Quick Start to install Hermes. Before proceeding, verify that Hermes is installed correctly by running hermes version.
    TIP
    Hermes currently doesn't support configuring the Tendermint CompatMode in chain config (see hermes#3623). Until that issue is resolved, please use Hermes v1.7.0+ because it falls back to Tendermint CompatMode v0.34 (see hermes#3663) which is compatible with Celestia.
    Configuration ​
    After you have successfully installed Hermes and created the necessary folders, you now have to edit config.toml and add the appropriate configurations for the chains you want to relay between.
    For this tutorial, we will be using the following chains:
    • Celestia's mocha-4 testnet
    • Cosmos Hub's theta-testnet-001 testnet
    Edit the Hermes configuration.
    bash
    vim $HOME/.hermes/config.toml
    vim $HOME/.hermes/config.toml
    toml
    [global]
 log_level = "info"
 
 [mode.clients]
diff --git a/pr-1699/assets/nodes_ibc-relayer.md.3c1ba349.lean.js b/pr-1699/assets/nodes_ibc-relayer.md.450545b1.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_ibc-relayer.md.3c1ba349.lean.js
rename to pr-1699/assets/nodes_ibc-relayer.md.450545b1.lean.js
index a232eab12e..584e2462fe 100644
--- a/pr-1699/assets/nodes_ibc-relayer.md.3c1ba349.lean.js
+++ b/pr-1699/assets/nodes_ibc-relayer.md.450545b1.lean.js
@@ -1 +1 @@
-import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"IBC relaying guide","description":"Learn how to establish IBC connections and relay packets.","frontmatter":{"description":"Learn how to establish IBC connections and relay packets.","next":{"text":"Metrics","link":"/nodes/celestia-node-metrics"},"head":[["meta",{"name":"og:title","content":"IBC relaying guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/ibc-relayer.md","filePath":"nodes/ibc-relayer.md","lastUpdated":1725971357000}'),p={name:"nodes/ibc-relayer.md"},o=l("",61),e=[o];function t(c,r,E,y,i,F){return n(),a("div",null,e)}const u=s(p,[["render",t]]);export{h as __pageData,u as default};
+import{_ as s,o as n,c as a,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"IBC relaying guide","description":"Learn how to establish IBC connections and relay packets.","frontmatter":{"description":"Learn how to establish IBC connections and relay packets.","next":{"text":"Metrics","link":"/nodes/celestia-node-metrics"},"head":[["meta",{"name":"og:title","content":"IBC relaying guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/ibc-relayer.md","filePath":"nodes/ibc-relayer.md","lastUpdated":1725992025000}'),p={name:"nodes/ibc-relayer.md"},o=l("",61),e=[o];function t(c,r,E,y,i,F){return n(),a("div",null,e)}const u=s(p,[["render",t]]);export{h as __pageData,u as default};
diff --git a/pr-1699/assets/nodes_instantiate-testnet.md.46c96647.js b/pr-1699/assets/nodes_instantiate-testnet.md.4b062bf6.js
similarity index 99%
rename from pr-1699/assets/nodes_instantiate-testnet.md.46c96647.js
rename to pr-1699/assets/nodes_instantiate-testnet.md.4b062bf6.js
index 4c24c5be00..3a1b5008e1 100644
--- a/pr-1699/assets/nodes_instantiate-testnet.md.46c96647.js
+++ b/pr-1699/assets/nodes_instantiate-testnet.md.4b062bf6.js
@@ -1,4 +1,4 @@
-import{_ as e,o as s,c as a,Q as n}from"./chunks/framework.b47e54aa.js";const E=JSON.parse('{"title":"Celestia App network instantiation guide","description":"A guide that helps you instantiate a new testnetwork with Celestia App.","frontmatter":{"description":"A guide that helps you instantiate a new testnetwork with Celestia App.","head":[["meta",{"name":"og:title","content":"Celestia App network instantiation guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/instantiate-testnet.md","filePath":"nodes/instantiate-testnet.md","lastUpdated":1725971357000}'),o={name:"nodes/instantiate-testnet.md"},t=n(`
    Celestia App network instantiation guide ​
    This guide is for helping instantiate a new testnetwork and following the correct steps to do so with Celestia App. You should only follow this guide if you want to experiment with your own Celestia test network (testnet) or if you want to test out new features to build as a core developer.
    Hardware requirements ​
    You will need to follow hardware requirements.
    Setup dependencies ​
    You will need to setup dependencies by following the guide.
    celestia-app installation ​
    You will need to install celestia-app by following the guide.
    Spin up a Celestia testnet ​
    If you want to spin up a quick testnet with your friends, you can follow these steps. Unless otherwise noted, every step must be done by everyone who wants to participate in this testnet.
    Optional: Reset working directory ​
    If you have already initialized a working directory for celestia-appd in the past, you must clean up before reinitializing a new directory. You can do so by running the following command:
    sh
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app
    Initialize a working directory ​
    Run the following command:
    sh
    VALIDATOR_NAME=validator1
+import{_ as e,o as s,c as a,Q as n}from"./chunks/framework.b47e54aa.js";const E=JSON.parse('{"title":"Celestia App network instantiation guide","description":"A guide that helps you instantiate a new testnetwork with Celestia App.","frontmatter":{"description":"A guide that helps you instantiate a new testnetwork with Celestia App.","head":[["meta",{"name":"og:title","content":"Celestia App network instantiation guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/instantiate-testnet.md","filePath":"nodes/instantiate-testnet.md","lastUpdated":1725992025000}'),o={name:"nodes/instantiate-testnet.md"},t=n(`
    Celestia App network instantiation guide ​
    This guide is for helping instantiate a new testnetwork and following the correct steps to do so with Celestia App. You should only follow this guide if you want to experiment with your own Celestia test network (testnet) or if you want to test out new features to build as a core developer.
    Hardware requirements ​
    You will need to follow hardware requirements.
    Setup dependencies ​
    You will need to setup dependencies by following the guide.
    celestia-app installation ​
    You will need to install celestia-app by following the guide.
    Spin up a Celestia testnet ​
    If you want to spin up a quick testnet with your friends, you can follow these steps. Unless otherwise noted, every step must be done by everyone who wants to participate in this testnet.
    Optional: Reset working directory ​
    If you have already initialized a working directory for celestia-appd in the past, you must clean up before reinitializing a new directory. You can do so by running the following command:
    sh
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app
    Initialize a working directory ​
    Run the following command:
    sh
    VALIDATOR_NAME=validator1
 CHAIN_ID=testnet
 celestia-appd init $VALIDATOR_NAME --chain-id $CHAIN_ID
    VALIDATOR_NAME=validator1
 CHAIN_ID=testnet
diff --git a/pr-1699/assets/nodes_instantiate-testnet.md.46c96647.lean.js b/pr-1699/assets/nodes_instantiate-testnet.md.4b062bf6.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_instantiate-testnet.md.46c96647.lean.js
rename to pr-1699/assets/nodes_instantiate-testnet.md.4b062bf6.lean.js
index 050dfdf93e..5d7af85b02 100644
--- a/pr-1699/assets/nodes_instantiate-testnet.md.46c96647.lean.js
+++ b/pr-1699/assets/nodes_instantiate-testnet.md.4b062bf6.lean.js
@@ -1 +1 @@
-import{_ as e,o as s,c as a,Q as n}from"./chunks/framework.b47e54aa.js";const E=JSON.parse('{"title":"Celestia App network instantiation guide","description":"A guide that helps you instantiate a new testnetwork with Celestia App.","frontmatter":{"description":"A guide that helps you instantiate a new testnetwork with Celestia App.","head":[["meta",{"name":"og:title","content":"Celestia App network instantiation guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/instantiate-testnet.md","filePath":"nodes/instantiate-testnet.md","lastUpdated":1725971357000}'),o={name:"nodes/instantiate-testnet.md"},t=n("",60),l=[t];function p(i,r,c,d,h,y){return s(),a("div",null,l)}const g=e(o,[["render",p]]);export{E as __pageData,g as default};
+import{_ as e,o as s,c as a,Q as n}from"./chunks/framework.b47e54aa.js";const E=JSON.parse('{"title":"Celestia App network instantiation guide","description":"A guide that helps you instantiate a new testnetwork with Celestia App.","frontmatter":{"description":"A guide that helps you instantiate a new testnetwork with Celestia App.","head":[["meta",{"name":"og:title","content":"Celestia App network instantiation guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/instantiate-testnet.md","filePath":"nodes/instantiate-testnet.md","lastUpdated":1725992025000}'),o={name:"nodes/instantiate-testnet.md"},t=n("",60),l=[t];function p(i,r,c,d,h,y){return s(),a("div",null,l)}const g=e(o,[["render",p]]);export{E as __pageData,g as default};
diff --git a/pr-1699/assets/nodes_light-node.md.c1fa0172.js b/pr-1699/assets/nodes_light-node.md.f1dd6ad1.js
similarity index 95%
rename from pr-1699/assets/nodes_light-node.md.c1fa0172.js
rename to pr-1699/assets/nodes_light-node.md.f1dd6ad1.js
index c4e721218d..75c04957ce 100644
--- a/pr-1699/assets/nodes_light-node.md.c1fa0172.js
+++ b/pr-1699/assets/nodes_light-node.md.f1dd6ad1.js
@@ -1,6 +1,6 @@
-import{_ as s,o as a,c as e,Q as n}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/nodes/LightNodes.png",F=JSON.parse('{"title":"Setting up a Celestia light node","description":"This tutorial covers setting up a Celestia light node.","frontmatter":{"sidebar_label":"Light node","description":"This tutorial covers setting up a Celestia light node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia light node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/light-node.md","filePath":"nodes/light-node.md","lastUpdated":1725971357000}'),l={name:"nodes/light-node.md"},p=n('
    Setting up a Celestia light node ​
    This tutorial will guide you through setting up a Celestia light node, which will allow you to perform data availability sampling (DAS) on Celestia's data availability (DA) network.
    Overview of light nodes ​
    Light nodes ensure data availability. This is the most common way to interact with Celestia networks.
    light-node
    Light nodes have the following behavior:
    1. They listen for ExtendedHeaders, i.e. wrapped “raw” headers, that notify Celestia nodes of new block headers and relevant DA metadata.
    2. They perform DAS on the received headers
    Hardware requirements ​
    The following minimum hardware requirements are recommended for running a light node:
    • Memory: 500 MB RAM (minimum)
    • CPU: Single Core
    • Disk: 100 GB SSD Storage
    • Bandwidth: 56 Kbps for Download/56 Kbps for Upload
    Setting up your light node ​
    This tutorial was performed on an Ubuntu Linux 20.04 (LTS) x64 instance machine.
    Set up dependencies on the setting up environment page.
    Install celestia-node ​
    Install the celestia binary by building and installing celestia-node.
    Initialize the light node ​
    Run the following command:
    sh
    celestia light init
    celestia light init
    sh
    celestia light init --p2p.network mocha
    celestia light init --p2p.network mocha
    sh
    celestia light init --p2p.network arabica
    celestia light init --p2p.network arabica
    The output in your terminal will show the location of your node store and config. It will also show confirmation that the node store has been initialized.
    Start the light node ​
    Start the light node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):
    In order for access to the ability to get and submit state-related information, such as the ability to submit PayForBlobs transactions, or query for the node's account balance, a gRPC endpoint of a validator (core) node must be passed as directed below.
    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.
    sh
    celestia light start --core.ip rpc.celestia.pops.one --p2p.network celestia
    celestia light start --core.ip rpc.celestia.pops.one --p2p.network celestia
    sh
    celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
    celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
    sh
    celestia light start --core.ip validator-1.celestia-arabica-11.com --p2p.network arabica
    celestia light start --core.ip validator-1.celestia-arabica-11.com --p2p.network arabica
    Tip: you can replace the core.ip with a consensus node RPC endpoint from mainnet, mocha, or arabica.
    Keys and wallets ​
    You can create your key for your node by running the following command with the cel-key utility in the celestia-node directory:
    sh
    ./cel-key add <key-name> --keyring-backend test \\
+import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/nodes/LightNodes.png",F=JSON.parse('{"title":"Setting up a Celestia light node","description":"This tutorial covers setting up a Celestia light node.","frontmatter":{"sidebar_label":"Light node","description":"This tutorial covers setting up a Celestia light node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia light node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/light-node.md","filePath":"nodes/light-node.md","lastUpdated":1725992025000}'),l={name:"nodes/light-node.md"},p=e('
    Setting up a Celestia light node ​
    This tutorial will guide you through setting up a Celestia light node, which will allow you to perform data availability sampling (DAS) on Celestia's data availability (DA) network.
    Overview of light nodes ​
    Light nodes ensure data availability. This is the most common way to interact with Celestia networks.
    light-node
    Light nodes have the following behavior:
    1. They listen for ExtendedHeaders, i.e. wrapped “raw” headers, that notify Celestia nodes of new block headers and relevant DA metadata.
    2. They perform DAS on the received headers
    Hardware requirements ​
    The following minimum hardware requirements are recommended for running a light node:
    • Memory: 500 MB RAM (minimum)
    • CPU: Single Core
    • Disk: 100 GB SSD Storage
    • Bandwidth: 56 Kbps for Download/56 Kbps for Upload
    Setting up your light node ​
    This tutorial was performed on an Ubuntu Linux 20.04 (LTS) x64 instance machine.
    Set up dependencies on the setting up environment page.
    Install celestia-node ​
    Install the celestia binary by building and installing celestia-node.
    Initialize the light node ​
    Run the following command:
    sh
    celestia light init
    celestia light init
    sh
    celestia light init --p2p.network mocha
    celestia light init --p2p.network mocha
    sh
    celestia light init --p2p.network arabica
    celestia light init --p2p.network arabica
    The output in your terminal will show the location of your node store and config. It will also show confirmation that the node store has been initialized.
    Start the light node ​
    Start the light node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):
    In order for access to the ability to get and submit state-related information, such as the ability to submit PayForBlobs transactions, or query for the node's account balance, a gRPC endpoint of a validator (core) node must be passed as directed below.
    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.
    sh
    celestia light start --core.ip rpc.celestia.pops.one --p2p.network celestia
    celestia light start --core.ip rpc.celestia.pops.one --p2p.network celestia
    sh
    celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
    celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
    sh
    celestia light start --core.ip validator-1.celestia-arabica-11.com --p2p.network arabica
    celestia light start --core.ip validator-1.celestia-arabica-11.com --p2p.network arabica
    Tip: you can replace the core.ip with a consensus node RPC endpoint from mainnet, mocha, or arabica.
    Keys and wallets ​
    You can create your key for your node by running the following command with the cel-key utility in the celestia-node directory:
    sh
    ./cel-key add <key-name> --keyring-backend test \\
     --node.type light --p2p.network <network>
    ./cel-key add <key-name> --keyring-backend test \\
-    --node.type light --p2p.network <network>
    You can start your light node with the key created above by running the following command:
    sh
    celestia light start --keyring.keyname my_celes_key \\
+    --node.type light --p2p.network <network>
    You can start your light node with the key created above by running the following command:
    sh
    celestia light start --keyring.keyname my_celes_key \\
     --core.ip consensus.lunaroasis.net
    celestia light start --keyring.keyname my_celes_key \\
     --core.ip consensus.lunaroasis.net
    sh
    celestia light start --keyring.keyname my_celes_key \\
     --core.ip rpc-mocha.pops.one --p2p.network mocha
    celestia light start --keyring.keyname my_celes_key \\
@@ -10,7 +10,7 @@ import{_ as s,o as a,c as e,Q as n}from"./chunks/framework.b47e54aa.js";const o=
     --core.ip validator-1.celestia-arabica-11.com \\
     --p2p.network arabica
    Once you start the light node, a wallet key will be generated for you. You will need to fund that address with testnet tokens to pay for PayForBlob transactions.
    You can find the address using the RPC CLI or by running the following command in the celestia-node directory:
    sh
    ./cel-key list --node.type light --keyring-backend test \\
     --p2p.network <network>
    ./cel-key list --node.type light --keyring-backend test \\
-    --p2p.network <network>
    Testnet tokens ​
    You have two networks to get testnet tokens from:
    You can request funds to your wallet address using the following command in Discord:
    console
    $request <CELESTIA-ADDRESS>
    $request <CELESTIA-ADDRESS>
    Where <CELESTIA-ADDRESS> is the celestia1****** address generated when you created the wallet.
    Optional: run the light node with a custom key ​
    In order to run a light node using a custom key:
    1. The custom key must exist inside the celestia light node directory at the correct path (default: ~/.celestia-light/keys/keyring-test)
    2. The name of the custom key must be passed upon start, like so:
    sh
    celestia light start --core.ip <URI> \\
+    --p2p.network <network>
    Testnet tokens ​
    You have two networks to get testnet tokens from:
    You can request funds to your wallet address using the following command in Discord:
    console
    $request <CELESTIA-ADDRESS>
    $request <CELESTIA-ADDRESS>
    Where <CELESTIA-ADDRESS> is the celestia1****** address generated when you created the wallet.
    Optional: run the light node with a custom key ​
    In order to run a light node using a custom key:
    1. The custom key must exist inside the celestia light node directory at the correct path (default: ~/.celestia-light/keys/keyring-test)
    2. The name of the custom key must be passed upon start, like so:
    sh
    celestia light start --core.ip <URI> \\
     --keyring.keyname <name-of-custom-key> \\
    celestia light start --core.ip <URI> \\
     --keyring.keyname <name-of-custom-key> \\
    sh
    celestia light start --core.ip <URI> \\
     --keyring.keyname <name-of-custom-key> \\
@@ -20,4 +20,4 @@ import{_ as s,o as a,c as e,Q as n}from"./chunks/framework.b47e54aa.js";const o=
     --keyring.keyname <name-of-custom-key> \\
     --p2p.network mocha
    celestia light start --core.ip <URI> \\
     --keyring.keyname <name-of-custom-key> \\
-    --p2p.network mocha
    Optional: Migrate node id to another server ​
    To migrate a light node ID:
    1. You need to back up two files located in the celestia-light node directory at the correct path (default: ~/.celestia-light/keys).
    2. Upload the files to the new server and start the node.
    Optional: start light node with SystemD ​
    Follow the tutorial on setting up the light node as a background process with SystemD.
    Data availability sampling ​
    With your light node running, you can check out this tutorial on submitting PayForBlob transactions.
    `,50),t=[p];function c(r,i,y,d,E,h){return a(),e("div",null,t)}const u=s(l,[["render",c]]);export{F as __pageData,u as default};
+    --p2p.network mocha
    Optional: Migrate node id to another server ​
    To migrate a light node ID:
    1. You need to back up two files located in the celestia-light node directory at the correct path (default: ~/.celestia-light/keys).
    2. Upload the files to the new server and start the node.
    Optional: start light node with SystemD ​
    Follow the tutorial on setting up the light node as a background process with SystemD.
    Data availability sampling ​
    With your light node running, you can check out this tutorial on submitting PayForBlob transactions.
    `,50),t=[p];function c(r,i,y,d,E,h){return a(),n("div",null,t)}const u=s(l,[["render",c]]);export{F as __pageData,u as default};
diff --git a/pr-1699/assets/nodes_light-node.md.c1fa0172.lean.js b/pr-1699/assets/nodes_light-node.md.f1dd6ad1.lean.js
similarity index 67%
rename from pr-1699/assets/nodes_light-node.md.c1fa0172.lean.js
rename to pr-1699/assets/nodes_light-node.md.f1dd6ad1.lean.js
index aaa2f9af5a..52a0c26040 100644
--- a/pr-1699/assets/nodes_light-node.md.c1fa0172.lean.js
+++ b/pr-1699/assets/nodes_light-node.md.f1dd6ad1.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as e,Q as n}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/nodes/LightNodes.png",F=JSON.parse('{"title":"Setting up a Celestia light node","description":"This tutorial covers setting up a Celestia light node.","frontmatter":{"sidebar_label":"Light node","description":"This tutorial covers setting up a Celestia light node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia light node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/light-node.md","filePath":"nodes/light-node.md","lastUpdated":1725971357000}'),l={name:"nodes/light-node.md"},p=n("",50),t=[p];function c(r,i,y,d,E,h){return a(),e("div",null,t)}const u=s(l,[["render",c]]);export{F as __pageData,u as default};
+import{_ as s,o as a,c as n,Q as e}from"./chunks/framework.b47e54aa.js";const o="/docs-preview/pr-1699/img/nodes/LightNodes.png",F=JSON.parse('{"title":"Setting up a Celestia light node","description":"This tutorial covers setting up a Celestia light node.","frontmatter":{"sidebar_label":"Light node","description":"This tutorial covers setting up a Celestia light node.","head":[["meta",{"name":"og:title","content":"Setting up a Celestia light node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/light-node.md","filePath":"nodes/light-node.md","lastUpdated":1725992025000}'),l={name:"nodes/light-node.md"},p=e("",50),t=[p];function c(r,i,y,d,E,h){return a(),n("div",null,t)}const u=s(l,[["render",c]]);export{F as __pageData,u as default};
diff --git a/pr-1699/assets/nodes_mainnet.md.0230b2ce.js b/pr-1699/assets/nodes_mainnet.md.0bba5c8e.js
similarity index 99%
rename from pr-1699/assets/nodes_mainnet.md.0230b2ce.js
rename to pr-1699/assets/nodes_mainnet.md.0bba5c8e.js
index 4dd78f09bc..ff255a59f7 100644
--- a/pr-1699/assets/nodes_mainnet.md.0230b2ce.js
+++ b/pr-1699/assets/nodes_mainnet.md.0bba5c8e.js
@@ -1 +1 @@
-import{M as p}from"./chunks/MainnetVersionTags.eb9befca.js";import{c as h}from"./chunks/constants.295fc0ab.js";import{_ as m,o as s,c as r,k as e,t as o,C as n,H as a,w as c,Q as i,a as u}from"./chunks/framework.b47e54aa.js";import"./chunks/mainnet_versions.1d5e6ed9.js";const f="/docs-preview/pr-1699/img/Mainnet-Beta.png",b="/docs-preview/pr-1699/grove/grove-sandbox.png",y={name:"MainnetBetaDetails",data(){return{constants:h}}},g=e("tr",null,[e("th",null,"Detail"),e("th",null,"Value")],-1),H=e("td",null,"Chain ID",-1),k=e("tr",null,[e("td",null,"Genesis hash"),e("td",null,[e("code",null,"6BE39EFD10BA412A9DB5288488303F5DD32CF386707A5BEF33617F4C43301872")])],-1),V=e("td",null,"Genesis file",-1),w=["href"],L=e("td",null,"Peers file",-1),v=["href"],_=e("tr",null,[e("td",null,"Validators"),e("td",null," 100 ")],-1);function x(d,T,Q,l,t,F){return s(),r("table",null,[g,e("tr",null,[H,e("td",null,[e("code",null,o(t.constants.mainnetChainId),1)])]),k,e("tr",null,[V,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mainnetChainId}/genesis.json`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mainnetChainId)+"/genesis.json ",9,w)])]),e("tr",null,[L,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mainnetChainId}/peers.txt`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mainnetChainId)+"/peers.txt ",9,v)])]),_])}const M=m(y,[["render",x]]),C=i('
    Mainnet Beta ​
    Mainnet Beta
    Welcome to the guide for Celestia’s Mainnet Beta, the production network that marks the pinnacle of Celestia’s evolution since its inception in 2019. This network is where all components of the Celestia ecosystem come to life in a real-world environment.
    Mainnet Beta is the culmination of rigorous community testing, upgrades, and feedback. It serves as the platform for deploying mainnet rollups and applications.
    Network stability and upgrades ​
    Mainnet Beta is a stable network, but will still receive updates and improvements. Any changes or upgrades will be coordinated with node operators and the broader Celestia community to ensure seamless integration and minimal service interruptions.
    As we step into unexplored territories with groundbreaking technologies like data availability sampling, it's crucial to remember that Mainnet Beta remains experimental at this stage. While the network is live and functional, users may encounter occasional instability or reduced performance.
    Network details ​
    ',8),P=e("h2",{id:"software-version-numbers",tabindex:"-1"},[u("Software version numbers "),e("a",{class:"header-anchor",href:"#software-version-numbers","aria-label":'Permalink to "Software version numbers"'},"​")],-1),Z=i('
    Network parameters ​
    Full network parameters, such as max bytes, can be found in the celestia-app specifications.
    CIP-13 has been drafted to create a living document for these parameters as a part of the CIP process.
    Maximum bytes ​
    There is a hard limit on the total blob size in a transaction, which is determined by the effective maximum square size. Given that the current governance maximum square size is 64, the total blob size in a transaction must be slightly less than ~2 MiB, or 1,973,786 bytes to be exact.
    The following provides an approximation of the maximum block size:
    • The maximum square size is 64x64, which gives us 4096 shares.
    • One share is reserved for the PFB transaction, leaving us with 4095 shares.
    • The first sparse share has 478 bytes available, and the remaining sparse shares have 482 bytes each.
    This can be calculated as follows:
    ',8),E={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"68.588ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 30315.8 1000","aria-hidden":"true"},q=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mtext"},[e("path",{"data-c":"54",d:"M36 443Q37 448 46 558T55 671V677H666V671Q667 666 676 556T685 443V437H645V443Q645 445 642 478T631 544T610 593Q593 614 555 625Q534 630 478 630H451H443Q417 630 414 618Q413 616 413 339V63Q420 53 439 50T528 46H558V0H545L361 3Q186 1 177 0H164V46H194Q264 46 283 49T309 63V339V550Q309 620 304 625T271 630H244H224Q154 630 119 601Q101 585 93 554T81 486T76 443V437H36V443Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"6F",d:"M28 214Q28 309 93 378T250 448Q340 448 405 380T471 215Q471 120 407 55T250 -10Q153 -10 91 57T28 214ZM250 30Q372 30 372 193V225V250Q372 272 371 288T364 326T348 362T317 390T268 410Q263 411 252 411Q222 411 195 399Q152 377 139 338T126 246V226Q126 130 145 91Q177 30 250 30Z",transform:"translate(722,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1222,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"61",d:"M137 305T115 305T78 320T63 359Q63 394 97 421T218 448Q291 448 336 416T396 340Q401 326 401 309T402 194V124Q402 76 407 58T428 40Q443 40 448 56T453 109V145H493V106Q492 66 490 59Q481 29 455 12T400 -6T353 12T329 54V58L327 55Q325 52 322 49T314 40T302 29T287 17T269 6T247 -2T221 -8T190 -11Q130 -11 82 20T34 107Q34 128 41 147T68 188T116 225T194 253T304 268H318V290Q318 324 312 340Q290 411 215 411Q197 411 181 410T156 406T148 403Q170 388 170 359Q170 334 154 320ZM126 106Q126 75 150 51T209 26Q247 26 276 49T315 109Q317 116 318 175Q318 233 317 233Q309 233 296 232T251 223T193 203T147 166T126 106Z",transform:"translate(1611,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"6C",d:"M42 46H56Q95 46 103 60V68Q103 77 103 91T103 124T104 167T104 217T104 272T104 329Q104 366 104 407T104 482T104 542T103 586T103 603Q100 622 89 628T44 637H26V660Q26 683 28 683L38 684Q48 685 67 686T104 688Q121 689 141 690T171 693T182 694H185V379Q185 62 186 60Q190 52 198 49Q219 46 247 46H263V0H255L232 1Q209 2 183 2T145 3T107 3T57 1L34 0H26V46H42Z",transform:"translate(2111,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"20",d:"",transform:"translate(2389,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"42",d:"M131 622Q124 629 120 631T104 634T61 637H28V683H229H267H346Q423 683 459 678T531 651Q574 627 599 590T624 512Q624 461 583 419T476 360L466 357Q539 348 595 302T651 187Q651 119 600 67T469 3Q456 1 242 0H28V46H61Q103 47 112 49T131 61V622ZM511 513Q511 560 485 594T416 636Q415 636 403 636T371 636T333 637Q266 637 251 636T232 628Q229 624 229 499V374H312L396 375L406 377Q410 378 417 380T442 393T474 417T499 456T511 513ZM537 188Q537 239 509 282T430 336L329 337H229V200V116Q229 57 234 52Q240 47 334 47H383Q425 47 443 53Q486 67 511 104T537 188Z",transform:"translate(2639,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(3347,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(3875,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(4264,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(4708,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(5379.8,0)"},[e("path",{"data-c":"3D",d:"M56 347Q56 360 70 367H707Q722 359 722 347Q722 336 708 328L390 327H72Q56 332 56 347ZM56 153Q56 168 72 173H708Q722 163 722 153Q722 140 707 133H70Q56 140 56 153Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(6435.6,0)"},[e("path",{"data-c":"28",d:"M94 250Q94 319 104 381T127 488T164 576T202 643T244 695T277 729T302 750H315H319Q333 750 333 741Q333 738 316 720T275 667T226 581T184 443T167 250T184 58T225 -81T274 -167T316 -220T333 -241Q333 -250 318 -250H315H302L274 -226Q180 -141 137 -14T94 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(6824.6,0)"},[e("path",{"data-c":"31",d:"M213 578L200 573Q186 568 160 563T102 556H83V602H102Q149 604 189 617T245 641T273 663Q275 666 285 666Q294 666 302 660V361L303 61Q310 54 315 52T339 48T401 46H427V0H416Q395 3 257 3Q121 3 100 0H88V46H114Q136 46 152 46T177 47T193 50T201 52T207 57T213 61V578Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(7546.8,0)"},[e("path",{"data-c":"D7",d:"M630 29Q630 9 609 9Q604 9 587 25T493 118L389 222L284 117Q178 13 175 11Q171 9 168 9Q160 9 154 15T147 29Q147 36 161 51T255 146L359 250L255 354Q174 435 161 449T147 471Q147 480 153 485T168 490Q173 490 175 489Q178 487 284 383L389 278L493 382Q570 459 587 475T609 491Q630 491 630 471Q630 464 620 453T522 355L418 250L522 145Q606 61 618 48T630 29Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(8547,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(10047,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(10214,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(12525,0)"},[e("path",{"data-c":"29",d:"M60 749L64 750Q69 750 74 750H86L114 726Q208 641 251 514T294 250Q294 182 284 119T261 12T224 -76T186 -143T145 -194T113 -227T90 -246Q87 -249 86 -250H74Q66 -250 63 -250T58 -247T55 -238Q56 -237 66 -225Q221 -64 221 250T66 725Q56 737 55 738Q55 746 60 749Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(13136.2,0)"},[e("path",{"data-c":"2B",d:"M56 237T56 250T70 270H369V420L370 570Q380 583 389 583Q402 583 409 568V270H707Q722 262 722 250T707 230H409V-68Q401 -82 391 -82H389H387Q375 -82 369 -68V230H70Q56 237 56 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(14136.4,0)"},[e("path",{"data-c":"28",d:"M94 250Q94 319 104 381T127 488T164 576T202 643T244 695T277 729T302 750H315H319Q333 750 333 741Q333 738 316 720T275 667T226 581T184 443T167 250T184 58T225 -81T274 -167T316 -220T333 -241Q333 -250 318 -250H315H302L274 -226Q180 -141 137 -14T94 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(14525.4,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"30",d:"M96 585Q152 666 249 666Q297 666 345 640T423 548Q460 465 460 320Q460 165 417 83Q397 41 362 16T301 -15T250 -22Q224 -22 198 -16T137 16T82 83Q39 165 39 320Q39 494 96 585ZM321 597Q291 629 250 629Q208 629 178 597Q153 571 145 525T137 333Q137 175 145 125T181 46Q209 16 250 16Q290 16 318 46Q347 76 354 130T362 333Q362 478 354 524T321 597Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"39",d:"M352 287Q304 211 232 211Q154 211 104 270T44 396Q42 412 42 436V444Q42 537 111 606Q171 666 243 666Q245 666 249 666T257 665H261Q273 665 286 663T323 651T370 619T413 560Q456 472 456 334Q456 194 396 97Q361 41 312 10T208 -22Q147 -22 108 7T68 93T121 149Q143 149 158 135T173 96Q173 78 164 65T148 49T135 44L131 43Q131 41 138 37T164 27T206 22H212Q272 22 313 86Q352 142 352 280V287ZM244 248Q292 248 321 297T351 430Q351 508 343 542Q341 552 337 562T323 588T293 615T246 625Q208 625 181 598Q160 576 154 546T147 441Q147 358 152 329T172 282Q197 248 244 248Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",transform:"translate(1500,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(16747.7,0)"},[e("path",{"data-c":"D7",d:"M630 29Q630 9 609 9Q604 9 587 25T493 118L389 222L284 117Q178 13 175 11Q171 9 168 9Q160 9 154 15T147 29Q147 36 161 51T255 146L359 250L255 354Q174 435 161 449T147 471Q147 480 153 485T168 490Q173 490 175 489Q178 487 284 383L389 278L493 382Q570 459 587 475T609 491Q630 491 630 471Q630 464 620 453T522 355L418 250L522 145Q606 61 618 48T630 29Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(17747.9,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"32",d:"M109 429Q82 429 66 447T50 491Q50 562 103 614T235 666Q326 666 387 610T449 465Q449 422 429 383T381 315T301 241Q265 210 201 149L142 93L218 92Q375 92 385 97Q392 99 409 186V189H449V186Q448 183 436 95T421 3V0H50V19V31Q50 38 56 46T86 81Q115 113 136 137Q145 147 170 174T204 211T233 244T261 278T284 308T305 340T320 369T333 401T340 431T343 464Q343 527 309 573T212 619Q179 619 154 602T119 569T109 550Q109 549 114 549Q132 549 151 535T170 489Q170 464 154 447T109 429Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(19247.9,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(19414.9,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(21725.9,0)"},[e("path",{"data-c":"29",d:"M60 749L64 750Q69 750 74 750H86L114 726Q208 641 251 514T294 250Q294 182 284 119T261 12T224 -76T186 -143T145 -194T113 -227T90 -246Q87 -249 86 -250H74Q66 -250 63 -250T58 -247T55 -238Q56 -237 66 -225Q221 -64 221 250T66 725Q56 737 55 738Q55 746 60 749Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(22392.7,0)"},[e("path",{"data-c":"3D",d:"M56 347Q56 360 70 367H707Q722 359 722 347Q722 336 708 328L390 327H72Q56 332 56 347ZM56 153Q56 168 72 173H708Q722 163 722 153Q722 140 707 133H70Q56 140 56 153Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(23448.4,0)"},[e("path",{"data-c":"31",d:"M213 578L200 573Q186 568 160 563T102 556H83V602H102Q149 604 189 617T245 641T273 663Q275 666 285 666Q294 666 302 660V361L303 61Q310 54 315 52T339 48T401 46H427V0H416Q395 3 257 3Q121 3 100 0H88V46H114Q136 46 152 46T177 47T193 50T201 52T207 57T213 61V578Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(23948.4,0)"},[e("path",{"data-c":"2C",d:"M78 35T78 60T94 103T137 121Q165 121 187 96T210 8Q210 -27 201 -60T180 -117T154 -158T130 -185T117 -194Q113 -194 104 -185T95 -172Q95 -168 106 -156T131 -126T157 -76T173 -3V9L172 8Q170 7 167 6T161 3T152 1T140 0Q113 0 96 17Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(24393.1,0)"},[e("path",{"data-c":"39",d:"M352 287Q304 211 232 211Q154 211 104 270T44 396Q42 412 42 436V444Q42 537 111 606Q171 666 243 666Q245 666 249 666T257 665H261Q273 665 286 663T323 651T370 619T413 560Q456 472 456 334Q456 194 396 97Q361 41 312 10T208 -22Q147 -22 108 7T68 93T121 149Q143 149 158 135T173 96Q173 78 164 65T148 49T135 44L131 43Q131 41 138 37T164 27T206 22H212Q272 22 313 86Q352 142 352 280V287ZM244 248Q292 248 321 297T351 430Q351 508 343 542Q341 552 337 562T323 588T293 615T246 625Q208 625 181 598Q160 576 154 546T147 441Q147 358 152 329T172 282Q197 248 244 248Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"33",d:"M127 463Q100 463 85 480T69 524Q69 579 117 622T233 665Q268 665 277 664Q351 652 390 611T430 522Q430 470 396 421T302 350L299 348Q299 347 308 345T337 336T375 315Q457 262 457 175Q457 96 395 37T238 -22Q158 -22 100 21T42 130Q42 158 60 175T105 193Q133 193 151 175T169 130Q169 119 166 110T159 94T148 82T136 74T126 70T118 67L114 66Q165 21 238 21Q293 21 321 74Q338 107 338 175V195Q338 290 274 322Q259 328 213 329L171 330L168 332Q166 335 166 348Q166 366 174 366Q202 366 232 371Q266 376 294 413T322 525V533Q322 590 287 612Q265 626 240 626Q208 626 181 615T143 592T132 580H135Q138 579 143 578T153 573T165 566T175 555T183 540T186 520Q186 498 172 481T127 463Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(25893.1,0)"},[e("path",{"data-c":"2C",d:"M78 35T78 60T94 103T137 121Q165 121 187 96T210 8Q210 -27 201 -60T180 -117T154 -158T130 -185T117 -194Q113 -194 104 -185T95 -172Q95 -168 106 -156T131 -126T157 -76T173 -3V9L172 8Q170 7 167 6T161 3T152 1T140 0Q113 0 96 17Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(26337.8,0)"},[e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"36",d:"M42 313Q42 476 123 571T303 666Q372 666 402 630T432 550Q432 525 418 510T379 495Q356 495 341 509T326 548Q326 592 373 601Q351 623 311 626Q240 626 194 566Q147 500 147 364L148 360Q153 366 156 373Q197 433 263 433H267Q313 433 348 414Q372 400 396 374T435 317Q456 268 456 210V192Q456 169 451 149Q440 90 387 34T253 -22Q225 -22 199 -14T143 16T92 75T56 172T42 313ZM257 397Q227 397 205 380T171 335T154 278T148 216Q148 133 160 97T198 39Q222 21 251 21Q302 21 329 59Q342 77 347 104T352 209Q352 289 347 316T329 361Q302 397 257 397Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(27837.8,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(28004.8,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})])])],-1),D=[q],A=e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mtext",null,"Total Bytes"),e("mo",null,"="),e("mo",{stretchy:"false"},"("),e("mn",null,"1"),e("mo",null,"×"),e("mn",null,"478"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes"),e("mo",{stretchy:"false"},")"),e("mo",null,"+"),e("mo",{stretchy:"false"},"("),e("mn",null,"4094"),e("mo",null,"×"),e("mn",null,"482"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes"),e("mo",{stretchy:"false"},")"),e("mo",null,"="),e("mn",null,"1"),e("mo",null,","),e("mn",null,"973"),e("mo",null,","),e("mn",null,"786"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes")],-1),R=i('
    Please note that there isn't a precise upper bound on the maximum total blob size. It depends on several factors:
    • The maximum square size, which is determined by a governance parameter and a versioned constant.
    • The maximum bytes in a block, which is determined by a governance parameter and a hard-coded constant in CometBFT.
    • The number of shares occupied by the PFB transaction share.
    These factors can cause the maximum total blob size that can be included in one block to vary.
    See the code in celestia-app and celestia-node.
    Integrations ​
    This guide contains the relevant sections for how to connect to Mainnet Beta, depending on the type of node you are running. Your best approach to participating is to first determine which node you would like to run. Each node’s guide will link to the relevant network in order to show you how to connect to them. Learn about the different endpoint types in the Cosmos SDK documentation.
    Here is a list of options of the types of nodes you can run in order to participate in Mainnet Beta:
    Production RPC endpoints ​
    These RPC providers are meant to be used in production environments.
    ProviderURL
    NewMetrichttps://app.newmetric.xyz/start
    NumiaFor RPC access: https://docs.numia.xyz/overview/rpc-api-access
    NumiaFor data warehouse access: https://docs.numia.xyz/overview/sql-access/chains/celestia
    Grovehttps://www.grove.city/
    WARNING
    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs or your own node.
    Consensus nodes ​
    Community consensus RPC endpoints ​
    WARNING
    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs.
    • public-celestia-rpc.numia.xyz
    • celestia-rpc.mesa.newmetric.xyz
    • rpc.celestia.pops.one
    • rpc.lunaroasis.net
    • rpc.celestia.nodestake.top
    • celestia-rpc.brightlystake.com
    • celestia-rpc.spidey.services
    • rpc-celestia.contributiondao.com
    • celestia.rpc.stakin-nodes.com
    • celestia.cumulo.org.es
    • rpc-celestia.mzonder.com
    • rpc-celestia-01.stakeflow.io
    • rpc-celestia.alphab.ai
    • rpc-celestia-full.avril14th.org
    • celestia-rpc.easy2stake.com
    • celestia.rpc.kjnodes.com
    • celestia-rpc.0xcryptovestor.com
    • rpc-celestia-mainnet.trusted-point.com
    • celestia.rpc.archives.validao.xyz
    • rpc-archive.celestia.bitszn.com
    • celestia-rpc.f5nodes.com
    • celestia-rpc.chainode.tech:33373
    • rpc-celestia.staker.space
    • celestia-rpc.noders.services
    • celestia.moonli.me
    • celestia-mainnet-rpc.itrocket.net:443
    • rpc.celestia.mainnet.dteam.tech:443
    Community API endpoints ​
    • public-celestia-lcd.numia.xyz
    • celestia-rest.mesa.newmetric.xyz
    • api.celestia.pops.one
    • api.lunaroasis.net
    • api.celestia.nodestake.top
    • celestia-rpc.brightlystake.com/api
    • celestia-api.spidey.services
    • api-celestia.contributiondao.com
    • celestia.rest.stakin-nodes.com
    • celestia.api.cumulo.org.es
    • api-celestia.mzonder.com
    • api-celestia-01.stakeflow.io
    • api-celestia.alphab.ai
    • api-celestia-full.avril14th.org
    • celestia-lcd.easy2stake.com
    • celestia.api.kjnodes.com
    • api-celestia-mainnet.trusted-point.com
    • celestia.rest.archives.validao.xyz
    • api-archive.celestia.bitszn.com
    • celestia-api.f5nodes.com
    • celestia-api.chainode.tech
    • api-celestia.staker.space
    • celestia-api.noders.services
    • celestia.moonli.me/api
    • celestia-mainnet-api.itrocket.net:443
    • api.celestia.mainnet.dteam.tech:443
    Community gRPC endpoints ​
    • public-celestia-grpc.numia.xyz
    • celestia-grpc.mesa.newmetric.xyz
    • grpc.celestia.pops.one
    • grpc.lunaroasis.net:443
    • grpc.celestia.nodestake.top
    • celestia-rpc.brightlystake.com:9090
    • celestia-grpc.spidey.services
    • grpc-celestia.contributiondao.com
    • celestia.grpc.stakin-nodes.com:443
    • celestia.grpc.cumulo.org.es:443
    • grpc-celestia.mzonder.com:443
    • grpc-celestia-01.stakeflow.io:15002
    • rpc-celestia.alphab.ai:9090
    • grpc-celestia-full.avril14th.org
    • celestia.grpc.kjnodes.com:443
    • grpc-celestia-mainnet.trusted-point.com:9095
    • celestia.grpc.archives.validao.xyz:9090
    • gprc-archive.celestia.bitszn.com
    • celestia-grpc.f5nodes.com:9390
    • celestia-grpc.chainode.tech:443
    • grpc-celestia.staker.space
    • celestia-grpc.noders.services:11090
    • celestia-mainnet-grpc.itrocket.net:443
    • grpc.celestia.mainnet.dteam.tech:28090
    Community WebSocket endpoints ​
    • wss://celestia-ws.chainode.tech:33373/websocket
    • wss://celestia-mainnet-ws.itrocket.net:443/websocket
    • wss://rpc.celestia.mainnet.dteam.tech:443/websocket
    Data availability nodes ​
    Community Data availability (DA) RPC endpoints for bridge node sync ​
    These RPC endpoints allow bridge nodes to sync blocks from the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default RPC port at 26657 to their respective DA node.
    Community Data availability (DA) gRPC endpoints for state access ​
    These gRPC endpoints for DA nodes provide state access for querying the chain’s state and broadcasting transactions (balances, blobs, etc.) to the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default gRPC port at 9090 to their respective DA node.
    TIP
    bash
    celestia <da_type> start --core.ip <url> -–core.grpc.port <port>
    celestia <da_type> start --core.ip <url> -–core.grpc.port <port>
    Bridge nodes
    Not all RPC endpoints guarantee the full block history. Find an archive endpoint on the community dashboard or run your own consensus node with no pruning for your bridge node.
    RPCs for DA nodes to initialise or start your celestia-node to Mainnet Beta with:
    • public-celestia-consensus.numia.xyz
      • gRPC: port 9090
      • RPC: port 26657
    • celestia-consensus.mesa.newmetric.xyz
      • gRPC: port 9090
      • RPC: port 26657
    • rpc.celestia.pops.one
      • gRPC: port 9090
      • RPC: port 26657
    • consensus.lunaroasis.net
      • gRPC: port 9090
      • RPC: port 26657
    • rpc-celestia.alphab.ai
      • gRPC: port 9090
      • RPC: port 26657
    • celestia-mainnet-consensus.itrocket.net
      • gRPC: port 9090
      • RPC: port 26657
    • rpc.celestia.mainnet.dteam.tech
      • gRPC: port 28090
      • RPC: 28657
    • celestia-consensus-mainnet.noders.services
      • gRPC: port 9080
      • RPC: port 26557
    DA full and light nodes might have troubles connecting to the networks, so you can check out this Grafana dashboard to see health/uptime status of DA bootstrappers (now celestia network only).
    You can find the status of these endpoints.
    Archival DA RPC endpoints ​
    By default, light nodes prune recent data to save on storage space. Archival data availability (DA) nodes store the entire history of the chain without pruning any data so all data available data is retrievable. You can read more about light vs archival nodes.
    Grove archival endpoints ​
    You can provision your own Celestia Archival endpoint on Grove. Learn more about Celestia on Grove, or find the fully supported spec.
    There is a sandbox you can leverage for testing straight in your browser:
    grove-sandbox
    Explorers ​
    There are multiple explorers you can use for Mainnet Beta:
    Analytics ​
    The following websites provide analytics for Celestia:
    Network upgrades ​
    There are a few ways to stay informed about network upgrades on Mainnet Beta:
    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.
    ',50),j=JSON.parse('{"title":"Mainnet Beta","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Mainnet Beta | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/mainnet.md","filePath":"nodes/mainnet.md","lastUpdated":1725971357000}'),B={name:"nodes/mainnet.md"},G=Object.assign(B,{setup(d){return(T,Q)=>{const l=n("mjx-assistive-mml"),t=n("mjx-container");return s(),r("div",null,[C,a(M),P,a(p),Z,e("p",null,[a(t,{class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},{default:c(()=>[(s(),r("svg",E,D)),a(l,{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},{default:c(()=>[A]),_:1})]),_:1})]),R])}}});export{j as __pageData,G as default};
+import{M as p}from"./chunks/MainnetVersionTags.eb9befca.js";import{c as h}from"./chunks/constants.295fc0ab.js";import{_ as m,o as s,c as r,k as e,t as o,C as n,H as a,w as c,Q as i,a as u}from"./chunks/framework.b47e54aa.js";import"./chunks/mainnet_versions.1d5e6ed9.js";const f="/docs-preview/pr-1699/img/Mainnet-Beta.png",b="/docs-preview/pr-1699/grove/grove-sandbox.png",y={name:"MainnetBetaDetails",data(){return{constants:h}}},g=e("tr",null,[e("th",null,"Detail"),e("th",null,"Value")],-1),H=e("td",null,"Chain ID",-1),k=e("tr",null,[e("td",null,"Genesis hash"),e("td",null,[e("code",null,"6BE39EFD10BA412A9DB5288488303F5DD32CF386707A5BEF33617F4C43301872")])],-1),V=e("td",null,"Genesis file",-1),w=["href"],L=e("td",null,"Peers file",-1),v=["href"],_=e("tr",null,[e("td",null,"Validators"),e("td",null," 100 ")],-1);function x(d,T,Q,l,t,F){return s(),r("table",null,[g,e("tr",null,[H,e("td",null,[e("code",null,o(t.constants.mainnetChainId),1)])]),k,e("tr",null,[V,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mainnetChainId}/genesis.json`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mainnetChainId)+"/genesis.json ",9,w)])]),e("tr",null,[L,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mainnetChainId}/peers.txt`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mainnetChainId)+"/peers.txt ",9,v)])]),_])}const M=m(y,[["render",x]]),C=i('
    Mainnet Beta ​
    Mainnet Beta
    Welcome to the guide for Celestia’s Mainnet Beta, the production network that marks the pinnacle of Celestia’s evolution since its inception in 2019. This network is where all components of the Celestia ecosystem come to life in a real-world environment.
    Mainnet Beta is the culmination of rigorous community testing, upgrades, and feedback. It serves as the platform for deploying mainnet rollups and applications.
    Network stability and upgrades ​
    Mainnet Beta is a stable network, but will still receive updates and improvements. Any changes or upgrades will be coordinated with node operators and the broader Celestia community to ensure seamless integration and minimal service interruptions.
    As we step into unexplored territories with groundbreaking technologies like data availability sampling, it's crucial to remember that Mainnet Beta remains experimental at this stage. While the network is live and functional, users may encounter occasional instability or reduced performance.
    Network details ​
    ',8),P=e("h2",{id:"software-version-numbers",tabindex:"-1"},[u("Software version numbers "),e("a",{class:"header-anchor",href:"#software-version-numbers","aria-label":'Permalink to "Software version numbers"'},"​")],-1),Z=i('
    Network parameters ​
    Full network parameters, such as max bytes, can be found in the celestia-app specifications.
    CIP-13 has been drafted to create a living document for these parameters as a part of the CIP process.
    Maximum bytes ​
    There is a hard limit on the total blob size in a transaction, which is determined by the effective maximum square size. Given that the current governance maximum square size is 64, the total blob size in a transaction must be slightly less than ~2 MiB, or 1,973,786 bytes to be exact.
    The following provides an approximation of the maximum block size:
    • The maximum square size is 64x64, which gives us 4096 shares.
    • One share is reserved for the PFB transaction, leaving us with 4095 shares.
    • The first sparse share has 478 bytes available, and the remaining sparse shares have 482 bytes each.
    This can be calculated as follows:
    ',8),E={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"68.588ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 30315.8 1000","aria-hidden":"true"},q=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mtext"},[e("path",{"data-c":"54",d:"M36 443Q37 448 46 558T55 671V677H666V671Q667 666 676 556T685 443V437H645V443Q645 445 642 478T631 544T610 593Q593 614 555 625Q534 630 478 630H451H443Q417 630 414 618Q413 616 413 339V63Q420 53 439 50T528 46H558V0H545L361 3Q186 1 177 0H164V46H194Q264 46 283 49T309 63V339V550Q309 620 304 625T271 630H244H224Q154 630 119 601Q101 585 93 554T81 486T76 443V437H36V443Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"6F",d:"M28 214Q28 309 93 378T250 448Q340 448 405 380T471 215Q471 120 407 55T250 -10Q153 -10 91 57T28 214ZM250 30Q372 30 372 193V225V250Q372 272 371 288T364 326T348 362T317 390T268 410Q263 411 252 411Q222 411 195 399Q152 377 139 338T126 246V226Q126 130 145 91Q177 30 250 30Z",transform:"translate(722,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1222,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"61",d:"M137 305T115 305T78 320T63 359Q63 394 97 421T218 448Q291 448 336 416T396 340Q401 326 401 309T402 194V124Q402 76 407 58T428 40Q443 40 448 56T453 109V145H493V106Q492 66 490 59Q481 29 455 12T400 -6T353 12T329 54V58L327 55Q325 52 322 49T314 40T302 29T287 17T269 6T247 -2T221 -8T190 -11Q130 -11 82 20T34 107Q34 128 41 147T68 188T116 225T194 253T304 268H318V290Q318 324 312 340Q290 411 215 411Q197 411 181 410T156 406T148 403Q170 388 170 359Q170 334 154 320ZM126 106Q126 75 150 51T209 26Q247 26 276 49T315 109Q317 116 318 175Q318 233 317 233Q309 233 296 232T251 223T193 203T147 166T126 106Z",transform:"translate(1611,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"6C",d:"M42 46H56Q95 46 103 60V68Q103 77 103 91T103 124T104 167T104 217T104 272T104 329Q104 366 104 407T104 482T104 542T103 586T103 603Q100 622 89 628T44 637H26V660Q26 683 28 683L38 684Q48 685 67 686T104 688Q121 689 141 690T171 693T182 694H185V379Q185 62 186 60Q190 52 198 49Q219 46 247 46H263V0H255L232 1Q209 2 183 2T145 3T107 3T57 1L34 0H26V46H42Z",transform:"translate(2111,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"20",d:"",transform:"translate(2389,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"42",d:"M131 622Q124 629 120 631T104 634T61 637H28V683H229H267H346Q423 683 459 678T531 651Q574 627 599 590T624 512Q624 461 583 419T476 360L466 357Q539 348 595 302T651 187Q651 119 600 67T469 3Q456 1 242 0H28V46H61Q103 47 112 49T131 61V622ZM511 513Q511 560 485 594T416 636Q415 636 403 636T371 636T333 637Q266 637 251 636T232 628Q229 624 229 499V374H312L396 375L406 377Q410 378 417 380T442 393T474 417T499 456T511 513ZM537 188Q537 239 509 282T430 336L329 337H229V200V116Q229 57 234 52Q240 47 334 47H383Q425 47 443 53Q486 67 511 104T537 188Z",transform:"translate(2639,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(3347,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(3875,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(4264,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(4708,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(5379.8,0)"},[e("path",{"data-c":"3D",d:"M56 347Q56 360 70 367H707Q722 359 722 347Q722 336 708 328L390 327H72Q56 332 56 347ZM56 153Q56 168 72 173H708Q722 163 722 153Q722 140 707 133H70Q56 140 56 153Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(6435.6,0)"},[e("path",{"data-c":"28",d:"M94 250Q94 319 104 381T127 488T164 576T202 643T244 695T277 729T302 750H315H319Q333 750 333 741Q333 738 316 720T275 667T226 581T184 443T167 250T184 58T225 -81T274 -167T316 -220T333 -241Q333 -250 318 -250H315H302L274 -226Q180 -141 137 -14T94 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(6824.6,0)"},[e("path",{"data-c":"31",d:"M213 578L200 573Q186 568 160 563T102 556H83V602H102Q149 604 189 617T245 641T273 663Q275 666 285 666Q294 666 302 660V361L303 61Q310 54 315 52T339 48T401 46H427V0H416Q395 3 257 3Q121 3 100 0H88V46H114Q136 46 152 46T177 47T193 50T201 52T207 57T213 61V578Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(7546.8,0)"},[e("path",{"data-c":"D7",d:"M630 29Q630 9 609 9Q604 9 587 25T493 118L389 222L284 117Q178 13 175 11Q171 9 168 9Q160 9 154 15T147 29Q147 36 161 51T255 146L359 250L255 354Q174 435 161 449T147 471Q147 480 153 485T168 490Q173 490 175 489Q178 487 284 383L389 278L493 382Q570 459 587 475T609 491Q630 491 630 471Q630 464 620 453T522 355L418 250L522 145Q606 61 618 48T630 29Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(8547,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(10047,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(10214,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(12525,0)"},[e("path",{"data-c":"29",d:"M60 749L64 750Q69 750 74 750H86L114 726Q208 641 251 514T294 250Q294 182 284 119T261 12T224 -76T186 -143T145 -194T113 -227T90 -246Q87 -249 86 -250H74Q66 -250 63 -250T58 -247T55 -238Q56 -237 66 -225Q221 -64 221 250T66 725Q56 737 55 738Q55 746 60 749Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(13136.2,0)"},[e("path",{"data-c":"2B",d:"M56 237T56 250T70 270H369V420L370 570Q380 583 389 583Q402 583 409 568V270H707Q722 262 722 250T707 230H409V-68Q401 -82 391 -82H389H387Q375 -82 369 -68V230H70Q56 237 56 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(14136.4,0)"},[e("path",{"data-c":"28",d:"M94 250Q94 319 104 381T127 488T164 576T202 643T244 695T277 729T302 750H315H319Q333 750 333 741Q333 738 316 720T275 667T226 581T184 443T167 250T184 58T225 -81T274 -167T316 -220T333 -241Q333 -250 318 -250H315H302L274 -226Q180 -141 137 -14T94 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(14525.4,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"30",d:"M96 585Q152 666 249 666Q297 666 345 640T423 548Q460 465 460 320Q460 165 417 83Q397 41 362 16T301 -15T250 -22Q224 -22 198 -16T137 16T82 83Q39 165 39 320Q39 494 96 585ZM321 597Q291 629 250 629Q208 629 178 597Q153 571 145 525T137 333Q137 175 145 125T181 46Q209 16 250 16Q290 16 318 46Q347 76 354 130T362 333Q362 478 354 524T321 597Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"39",d:"M352 287Q304 211 232 211Q154 211 104 270T44 396Q42 412 42 436V444Q42 537 111 606Q171 666 243 666Q245 666 249 666T257 665H261Q273 665 286 663T323 651T370 619T413 560Q456 472 456 334Q456 194 396 97Q361 41 312 10T208 -22Q147 -22 108 7T68 93T121 149Q143 149 158 135T173 96Q173 78 164 65T148 49T135 44L131 43Q131 41 138 37T164 27T206 22H212Q272 22 313 86Q352 142 352 280V287ZM244 248Q292 248 321 297T351 430Q351 508 343 542Q341 552 337 562T323 588T293 615T246 625Q208 625 181 598Q160 576 154 546T147 441Q147 358 152 329T172 282Q197 248 244 248Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",transform:"translate(1500,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(16747.7,0)"},[e("path",{"data-c":"D7",d:"M630 29Q630 9 609 9Q604 9 587 25T493 118L389 222L284 117Q178 13 175 11Q171 9 168 9Q160 9 154 15T147 29Q147 36 161 51T255 146L359 250L255 354Q174 435 161 449T147 471Q147 480 153 485T168 490Q173 490 175 489Q178 487 284 383L389 278L493 382Q570 459 587 475T609 491Q630 491 630 471Q630 464 620 453T522 355L418 250L522 145Q606 61 618 48T630 29Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(17747.9,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"32",d:"M109 429Q82 429 66 447T50 491Q50 562 103 614T235 666Q326 666 387 610T449 465Q449 422 429 383T381 315T301 241Q265 210 201 149L142 93L218 92Q375 92 385 97Q392 99 409 186V189H449V186Q448 183 436 95T421 3V0H50V19V31Q50 38 56 46T86 81Q115 113 136 137Q145 147 170 174T204 211T233 244T261 278T284 308T305 340T320 369T333 401T340 431T343 464Q343 527 309 573T212 619Q179 619 154 602T119 569T109 550Q109 549 114 549Q132 549 151 535T170 489Q170 464 154 447T109 429Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(19247.9,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(19414.9,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(21725.9,0)"},[e("path",{"data-c":"29",d:"M60 749L64 750Q69 750 74 750H86L114 726Q208 641 251 514T294 250Q294 182 284 119T261 12T224 -76T186 -143T145 -194T113 -227T90 -246Q87 -249 86 -250H74Q66 -250 63 -250T58 -247T55 -238Q56 -237 66 -225Q221 -64 221 250T66 725Q56 737 55 738Q55 746 60 749Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(22392.7,0)"},[e("path",{"data-c":"3D",d:"M56 347Q56 360 70 367H707Q722 359 722 347Q722 336 708 328L390 327H72Q56 332 56 347ZM56 153Q56 168 72 173H708Q722 163 722 153Q722 140 707 133H70Q56 140 56 153Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(23448.4,0)"},[e("path",{"data-c":"31",d:"M213 578L200 573Q186 568 160 563T102 556H83V602H102Q149 604 189 617T245 641T273 663Q275 666 285 666Q294 666 302 660V361L303 61Q310 54 315 52T339 48T401 46H427V0H416Q395 3 257 3Q121 3 100 0H88V46H114Q136 46 152 46T177 47T193 50T201 52T207 57T213 61V578Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(23948.4,0)"},[e("path",{"data-c":"2C",d:"M78 35T78 60T94 103T137 121Q165 121 187 96T210 8Q210 -27 201 -60T180 -117T154 -158T130 -185T117 -194Q113 -194 104 -185T95 -172Q95 -168 106 -156T131 -126T157 -76T173 -3V9L172 8Q170 7 167 6T161 3T152 1T140 0Q113 0 96 17Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(24393.1,0)"},[e("path",{"data-c":"39",d:"M352 287Q304 211 232 211Q154 211 104 270T44 396Q42 412 42 436V444Q42 537 111 606Q171 666 243 666Q245 666 249 666T257 665H261Q273 665 286 663T323 651T370 619T413 560Q456 472 456 334Q456 194 396 97Q361 41 312 10T208 -22Q147 -22 108 7T68 93T121 149Q143 149 158 135T173 96Q173 78 164 65T148 49T135 44L131 43Q131 41 138 37T164 27T206 22H212Q272 22 313 86Q352 142 352 280V287ZM244 248Q292 248 321 297T351 430Q351 508 343 542Q341 552 337 562T323 588T293 615T246 625Q208 625 181 598Q160 576 154 546T147 441Q147 358 152 329T172 282Q197 248 244 248Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"33",d:"M127 463Q100 463 85 480T69 524Q69 579 117 622T233 665Q268 665 277 664Q351 652 390 611T430 522Q430 470 396 421T302 350L299 348Q299 347 308 345T337 336T375 315Q457 262 457 175Q457 96 395 37T238 -22Q158 -22 100 21T42 130Q42 158 60 175T105 193Q133 193 151 175T169 130Q169 119 166 110T159 94T148 82T136 74T126 70T118 67L114 66Q165 21 238 21Q293 21 321 74Q338 107 338 175V195Q338 290 274 322Q259 328 213 329L171 330L168 332Q166 335 166 348Q166 366 174 366Q202 366 232 371Q266 376 294 413T322 525V533Q322 590 287 612Q265 626 240 626Q208 626 181 615T143 592T132 580H135Q138 579 143 578T153 573T165 566T175 555T183 540T186 520Q186 498 172 481T127 463Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(25893.1,0)"},[e("path",{"data-c":"2C",d:"M78 35T78 60T94 103T137 121Q165 121 187 96T210 8Q210 -27 201 -60T180 -117T154 -158T130 -185T117 -194Q113 -194 104 -185T95 -172Q95 -168 106 -156T131 -126T157 -76T173 -3V9L172 8Q170 7 167 6T161 3T152 1T140 0Q113 0 96 17Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(26337.8,0)"},[e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"36",d:"M42 313Q42 476 123 571T303 666Q372 666 402 630T432 550Q432 525 418 510T379 495Q356 495 341 509T326 548Q326 592 373 601Q351 623 311 626Q240 626 194 566Q147 500 147 364L148 360Q153 366 156 373Q197 433 263 433H267Q313 433 348 414Q372 400 396 374T435 317Q456 268 456 210V192Q456 169 451 149Q440 90 387 34T253 -22Q225 -22 199 -14T143 16T92 75T56 172T42 313ZM257 397Q227 397 205 380T171 335T154 278T148 216Q148 133 160 97T198 39Q222 21 251 21Q302 21 329 59Q342 77 347 104T352 209Q352 289 347 316T329 361Q302 397 257 397Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(27837.8,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(28004.8,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})])])],-1),D=[q],A=e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mtext",null,"Total Bytes"),e("mo",null,"="),e("mo",{stretchy:"false"},"("),e("mn",null,"1"),e("mo",null,"×"),e("mn",null,"478"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes"),e("mo",{stretchy:"false"},")"),e("mo",null,"+"),e("mo",{stretchy:"false"},"("),e("mn",null,"4094"),e("mo",null,"×"),e("mn",null,"482"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes"),e("mo",{stretchy:"false"},")"),e("mo",null,"="),e("mn",null,"1"),e("mo",null,","),e("mn",null,"973"),e("mo",null,","),e("mn",null,"786"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes")],-1),R=i('
    Please note that there isn't a precise upper bound on the maximum total blob size. It depends on several factors:
    • The maximum square size, which is determined by a governance parameter and a versioned constant.
    • The maximum bytes in a block, which is determined by a governance parameter and a hard-coded constant in CometBFT.
    • The number of shares occupied by the PFB transaction share.
    These factors can cause the maximum total blob size that can be included in one block to vary.
    See the code in celestia-app and celestia-node.
    Integrations ​
    This guide contains the relevant sections for how to connect to Mainnet Beta, depending on the type of node you are running. Your best approach to participating is to first determine which node you would like to run. Each node’s guide will link to the relevant network in order to show you how to connect to them. Learn about the different endpoint types in the Cosmos SDK documentation.
    Here is a list of options of the types of nodes you can run in order to participate in Mainnet Beta:
    Production RPC endpoints ​
    These RPC providers are meant to be used in production environments.
    ProviderURL
    NewMetrichttps://app.newmetric.xyz/start
    NumiaFor RPC access: https://docs.numia.xyz/overview/rpc-api-access
    NumiaFor data warehouse access: https://docs.numia.xyz/overview/sql-access/chains/celestia
    Grovehttps://www.grove.city/
    WARNING
    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs or your own node.
    Consensus nodes ​
    Community consensus RPC endpoints ​
    WARNING
    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs.
    • public-celestia-rpc.numia.xyz
    • celestia-rpc.mesa.newmetric.xyz
    • rpc.celestia.pops.one
    • rpc.lunaroasis.net
    • rpc.celestia.nodestake.top
    • celestia-rpc.brightlystake.com
    • celestia-rpc.spidey.services
    • rpc-celestia.contributiondao.com
    • celestia.rpc.stakin-nodes.com
    • celestia.cumulo.org.es
    • rpc-celestia.mzonder.com
    • rpc-celestia-01.stakeflow.io
    • rpc-celestia.alphab.ai
    • rpc-celestia-full.avril14th.org
    • celestia-rpc.easy2stake.com
    • celestia.rpc.kjnodes.com
    • celestia-rpc.0xcryptovestor.com
    • rpc-celestia-mainnet.trusted-point.com
    • celestia.rpc.archives.validao.xyz
    • rpc-archive.celestia.bitszn.com
    • celestia-rpc.f5nodes.com
    • celestia-rpc.chainode.tech:33373
    • rpc-celestia.staker.space
    • celestia-rpc.noders.services
    • celestia.moonli.me
    • celestia-mainnet-rpc.itrocket.net:443
    • rpc.celestia.mainnet.dteam.tech:443
    Community API endpoints ​
    • public-celestia-lcd.numia.xyz
    • celestia-rest.mesa.newmetric.xyz
    • api.celestia.pops.one
    • api.lunaroasis.net
    • api.celestia.nodestake.top
    • celestia-rpc.brightlystake.com/api
    • celestia-api.spidey.services
    • api-celestia.contributiondao.com
    • celestia.rest.stakin-nodes.com
    • celestia.api.cumulo.org.es
    • api-celestia.mzonder.com
    • api-celestia-01.stakeflow.io
    • api-celestia.alphab.ai
    • api-celestia-full.avril14th.org
    • celestia-lcd.easy2stake.com
    • celestia.api.kjnodes.com
    • api-celestia-mainnet.trusted-point.com
    • celestia.rest.archives.validao.xyz
    • api-archive.celestia.bitszn.com
    • celestia-api.f5nodes.com
    • celestia-api.chainode.tech
    • api-celestia.staker.space
    • celestia-api.noders.services
    • celestia.moonli.me/api
    • celestia-mainnet-api.itrocket.net:443
    • api.celestia.mainnet.dteam.tech:443
    Community gRPC endpoints ​
    • public-celestia-grpc.numia.xyz
    • celestia-grpc.mesa.newmetric.xyz
    • grpc.celestia.pops.one
    • grpc.lunaroasis.net:443
    • grpc.celestia.nodestake.top
    • celestia-rpc.brightlystake.com:9090
    • celestia-grpc.spidey.services
    • grpc-celestia.contributiondao.com
    • celestia.grpc.stakin-nodes.com:443
    • celestia.grpc.cumulo.org.es:443
    • grpc-celestia.mzonder.com:443
    • grpc-celestia-01.stakeflow.io:15002
    • rpc-celestia.alphab.ai:9090
    • grpc-celestia-full.avril14th.org
    • celestia.grpc.kjnodes.com:443
    • grpc-celestia-mainnet.trusted-point.com:9095
    • celestia.grpc.archives.validao.xyz:9090
    • gprc-archive.celestia.bitszn.com
    • celestia-grpc.f5nodes.com:9390
    • celestia-grpc.chainode.tech:443
    • grpc-celestia.staker.space
    • celestia-grpc.noders.services:11090
    • celestia-mainnet-grpc.itrocket.net:443
    • grpc.celestia.mainnet.dteam.tech:28090
    Community WebSocket endpoints ​
    • wss://celestia-ws.chainode.tech:33373/websocket
    • wss://celestia-mainnet-ws.itrocket.net:443/websocket
    • wss://rpc.celestia.mainnet.dteam.tech:443/websocket
    Data availability nodes ​
    Community Data availability (DA) RPC endpoints for bridge node sync ​
    These RPC endpoints allow bridge nodes to sync blocks from the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default RPC port at 26657 to their respective DA node.
    Community Data availability (DA) gRPC endpoints for state access ​
    These gRPC endpoints for DA nodes provide state access for querying the chain’s state and broadcasting transactions (balances, blobs, etc.) to the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default gRPC port at 9090 to their respective DA node.
    TIP
    bash
    celestia <da_type> start --core.ip <url> -–core.grpc.port <port>
    celestia <da_type> start --core.ip <url> -–core.grpc.port <port>
    Bridge nodes
    Not all RPC endpoints guarantee the full block history. Find an archive endpoint on the community dashboard or run your own consensus node with no pruning for your bridge node.
    RPCs for DA nodes to initialise or start your celestia-node to Mainnet Beta with:
    • public-celestia-consensus.numia.xyz
      • gRPC: port 9090
      • RPC: port 26657
    • celestia-consensus.mesa.newmetric.xyz
      • gRPC: port 9090
      • RPC: port 26657
    • rpc.celestia.pops.one
      • gRPC: port 9090
      • RPC: port 26657
    • consensus.lunaroasis.net
      • gRPC: port 9090
      • RPC: port 26657
    • rpc-celestia.alphab.ai
      • gRPC: port 9090
      • RPC: port 26657
    • celestia-mainnet-consensus.itrocket.net
      • gRPC: port 9090
      • RPC: port 26657
    • rpc.celestia.mainnet.dteam.tech
      • gRPC: port 28090
      • RPC: 28657
    • celestia-consensus-mainnet.noders.services
      • gRPC: port 9080
      • RPC: port 26557
    DA full and light nodes might have troubles connecting to the networks, so you can check out this Grafana dashboard to see health/uptime status of DA bootstrappers (now celestia network only).
    You can find the status of these endpoints.
    Archival DA RPC endpoints ​
    By default, light nodes prune recent data to save on storage space. Archival data availability (DA) nodes store the entire history of the chain without pruning any data so all data available data is retrievable. You can read more about light vs archival nodes.
    Grove archival endpoints ​
    You can provision your own Celestia Archival endpoint on Grove. Learn more about Celestia on Grove, or find the fully supported spec.
    There is a sandbox you can leverage for testing straight in your browser:
    grove-sandbox
    Explorers ​
    There are multiple explorers you can use for Mainnet Beta:
    Analytics ​
    The following websites provide analytics for Celestia:
    Network upgrades ​
    There are a few ways to stay informed about network upgrades on Mainnet Beta:
    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.
    ',50),j=JSON.parse('{"title":"Mainnet Beta","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Mainnet Beta | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/mainnet.md","filePath":"nodes/mainnet.md","lastUpdated":1725992025000}'),B={name:"nodes/mainnet.md"},G=Object.assign(B,{setup(d){return(T,Q)=>{const l=n("mjx-assistive-mml"),t=n("mjx-container");return s(),r("div",null,[C,a(M),P,a(p),Z,e("p",null,[a(t,{class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},{default:c(()=>[(s(),r("svg",E,D)),a(l,{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},{default:c(()=>[A]),_:1})]),_:1})]),R])}}});export{j as __pageData,G as default};
diff --git a/pr-1699/assets/nodes_mainnet.md.0230b2ce.lean.js b/pr-1699/assets/nodes_mainnet.md.0bba5c8e.lean.js
similarity index 99%
rename from pr-1699/assets/nodes_mainnet.md.0230b2ce.lean.js
rename to pr-1699/assets/nodes_mainnet.md.0bba5c8e.lean.js
index a627c56195..698262dae9 100644
--- a/pr-1699/assets/nodes_mainnet.md.0230b2ce.lean.js
+++ b/pr-1699/assets/nodes_mainnet.md.0bba5c8e.lean.js
@@ -1 +1 @@
-import{M as p}from"./chunks/MainnetVersionTags.eb9befca.js";import{c as h}from"./chunks/constants.295fc0ab.js";import{_ as m,o as s,c as r,k as e,t as o,C as n,H as a,w as c,Q as i,a as u}from"./chunks/framework.b47e54aa.js";import"./chunks/mainnet_versions.1d5e6ed9.js";const f="/docs-preview/pr-1699/img/Mainnet-Beta.png",b="/docs-preview/pr-1699/grove/grove-sandbox.png",y={name:"MainnetBetaDetails",data(){return{constants:h}}},g=e("tr",null,[e("th",null,"Detail"),e("th",null,"Value")],-1),H=e("td",null,"Chain ID",-1),k=e("tr",null,[e("td",null,"Genesis hash"),e("td",null,[e("code",null,"6BE39EFD10BA412A9DB5288488303F5DD32CF386707A5BEF33617F4C43301872")])],-1),V=e("td",null,"Genesis file",-1),w=["href"],L=e("td",null,"Peers file",-1),v=["href"],_=e("tr",null,[e("td",null,"Validators"),e("td",null," 100 ")],-1);function x(d,T,Q,l,t,F){return s(),r("table",null,[g,e("tr",null,[H,e("td",null,[e("code",null,o(t.constants.mainnetChainId),1)])]),k,e("tr",null,[V,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mainnetChainId}/genesis.json`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mainnetChainId)+"/genesis.json ",9,w)])]),e("tr",null,[L,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mainnetChainId}/peers.txt`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mainnetChainId)+"/peers.txt ",9,v)])]),_])}const M=m(y,[["render",x]]),C=i("",8),P=e("h2",{id:"software-version-numbers",tabindex:"-1"},[u("Software version numbers "),e("a",{class:"header-anchor",href:"#software-version-numbers","aria-label":'Permalink to "Software version numbers"'},"​")],-1),Z=i("",8),E={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"68.588ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 30315.8 1000","aria-hidden":"true"},q=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mtext"},[e("path",{"data-c":"54",d:"M36 443Q37 448 46 558T55 671V677H666V671Q667 666 676 556T685 443V437H645V443Q645 445 642 478T631 544T610 593Q593 614 555 625Q534 630 478 630H451H443Q417 630 414 618Q413 616 413 339V63Q420 53 439 50T528 46H558V0H545L361 3Q186 1 177 0H164V46H194Q264 46 283 49T309 63V339V550Q309 620 304 625T271 630H244H224Q154 630 119 601Q101 585 93 554T81 486T76 443V437H36V443Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"6F",d:"M28 214Q28 309 93 378T250 448Q340 448 405 380T471 215Q471 120 407 55T250 -10Q153 -10 91 57T28 214ZM250 30Q372 30 372 193V225V250Q372 272 371 288T364 326T348 362T317 390T268 410Q263 411 252 411Q222 411 195 399Q152 377 139 338T126 246V226Q126 130 145 91Q177 30 250 30Z",transform:"translate(722,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1222,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"61",d:"M137 305T115 305T78 320T63 359Q63 394 97 421T218 448Q291 448 336 416T396 340Q401 326 401 309T402 194V124Q402 76 407 58T428 40Q443 40 448 56T453 109V145H493V106Q492 66 490 59Q481 29 455 12T400 -6T353 12T329 54V58L327 55Q325 52 322 49T314 40T302 29T287 17T269 6T247 -2T221 -8T190 -11Q130 -11 82 20T34 107Q34 128 41 147T68 188T116 225T194 253T304 268H318V290Q318 324 312 340Q290 411 215 411Q197 411 181 410T156 406T148 403Q170 388 170 359Q170 334 154 320ZM126 106Q126 75 150 51T209 26Q247 26 276 49T315 109Q317 116 318 175Q318 233 317 233Q309 233 296 232T251 223T193 203T147 166T126 106Z",transform:"translate(1611,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"6C",d:"M42 46H56Q95 46 103 60V68Q103 77 103 91T103 124T104 167T104 217T104 272T104 329Q104 366 104 407T104 482T104 542T103 586T103 603Q100 622 89 628T44 637H26V660Q26 683 28 683L38 684Q48 685 67 686T104 688Q121 689 141 690T171 693T182 694H185V379Q185 62 186 60Q190 52 198 49Q219 46 247 46H263V0H255L232 1Q209 2 183 2T145 3T107 3T57 1L34 0H26V46H42Z",transform:"translate(2111,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"20",d:"",transform:"translate(2389,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"42",d:"M131 622Q124 629 120 631T104 634T61 637H28V683H229H267H346Q423 683 459 678T531 651Q574 627 599 590T624 512Q624 461 583 419T476 360L466 357Q539 348 595 302T651 187Q651 119 600 67T469 3Q456 1 242 0H28V46H61Q103 47 112 49T131 61V622ZM511 513Q511 560 485 594T416 636Q415 636 403 636T371 636T333 637Q266 637 251 636T232 628Q229 624 229 499V374H312L396 375L406 377Q410 378 417 380T442 393T474 417T499 456T511 513ZM537 188Q537 239 509 282T430 336L329 337H229V200V116Q229 57 234 52Q240 47 334 47H383Q425 47 443 53Q486 67 511 104T537 188Z",transform:"translate(2639,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(3347,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(3875,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(4264,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(4708,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(5379.8,0)"},[e("path",{"data-c":"3D",d:"M56 347Q56 360 70 367H707Q722 359 722 347Q722 336 708 328L390 327H72Q56 332 56 347ZM56 153Q56 168 72 173H708Q722 163 722 153Q722 140 707 133H70Q56 140 56 153Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(6435.6,0)"},[e("path",{"data-c":"28",d:"M94 250Q94 319 104 381T127 488T164 576T202 643T244 695T277 729T302 750H315H319Q333 750 333 741Q333 738 316 720T275 667T226 581T184 443T167 250T184 58T225 -81T274 -167T316 -220T333 -241Q333 -250 318 -250H315H302L274 -226Q180 -141 137 -14T94 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(6824.6,0)"},[e("path",{"data-c":"31",d:"M213 578L200 573Q186 568 160 563T102 556H83V602H102Q149 604 189 617T245 641T273 663Q275 666 285 666Q294 666 302 660V361L303 61Q310 54 315 52T339 48T401 46H427V0H416Q395 3 257 3Q121 3 100 0H88V46H114Q136 46 152 46T177 47T193 50T201 52T207 57T213 61V578Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(7546.8,0)"},[e("path",{"data-c":"D7",d:"M630 29Q630 9 609 9Q604 9 587 25T493 118L389 222L284 117Q178 13 175 11Q171 9 168 9Q160 9 154 15T147 29Q147 36 161 51T255 146L359 250L255 354Q174 435 161 449T147 471Q147 480 153 485T168 490Q173 490 175 489Q178 487 284 383L389 278L493 382Q570 459 587 475T609 491Q630 491 630 471Q630 464 620 453T522 355L418 250L522 145Q606 61 618 48T630 29Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(8547,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(10047,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(10214,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(12525,0)"},[e("path",{"data-c":"29",d:"M60 749L64 750Q69 750 74 750H86L114 726Q208 641 251 514T294 250Q294 182 284 119T261 12T224 -76T186 -143T145 -194T113 -227T90 -246Q87 -249 86 -250H74Q66 -250 63 -250T58 -247T55 -238Q56 -237 66 -225Q221 -64 221 250T66 725Q56 737 55 738Q55 746 60 749Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(13136.2,0)"},[e("path",{"data-c":"2B",d:"M56 237T56 250T70 270H369V420L370 570Q380 583 389 583Q402 583 409 568V270H707Q722 262 722 250T707 230H409V-68Q401 -82 391 -82H389H387Q375 -82 369 -68V230H70Q56 237 56 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(14136.4,0)"},[e("path",{"data-c":"28",d:"M94 250Q94 319 104 381T127 488T164 576T202 643T244 695T277 729T302 750H315H319Q333 750 333 741Q333 738 316 720T275 667T226 581T184 443T167 250T184 58T225 -81T274 -167T316 -220T333 -241Q333 -250 318 -250H315H302L274 -226Q180 -141 137 -14T94 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(14525.4,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"30",d:"M96 585Q152 666 249 666Q297 666 345 640T423 548Q460 465 460 320Q460 165 417 83Q397 41 362 16T301 -15T250 -22Q224 -22 198 -16T137 16T82 83Q39 165 39 320Q39 494 96 585ZM321 597Q291 629 250 629Q208 629 178 597Q153 571 145 525T137 333Q137 175 145 125T181 46Q209 16 250 16Q290 16 318 46Q347 76 354 130T362 333Q362 478 354 524T321 597Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"39",d:"M352 287Q304 211 232 211Q154 211 104 270T44 396Q42 412 42 436V444Q42 537 111 606Q171 666 243 666Q245 666 249 666T257 665H261Q273 665 286 663T323 651T370 619T413 560Q456 472 456 334Q456 194 396 97Q361 41 312 10T208 -22Q147 -22 108 7T68 93T121 149Q143 149 158 135T173 96Q173 78 164 65T148 49T135 44L131 43Q131 41 138 37T164 27T206 22H212Q272 22 313 86Q352 142 352 280V287ZM244 248Q292 248 321 297T351 430Q351 508 343 542Q341 552 337 562T323 588T293 615T246 625Q208 625 181 598Q160 576 154 546T147 441Q147 358 152 329T172 282Q197 248 244 248Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",transform:"translate(1500,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(16747.7,0)"},[e("path",{"data-c":"D7",d:"M630 29Q630 9 609 9Q604 9 587 25T493 118L389 222L284 117Q178 13 175 11Q171 9 168 9Q160 9 154 15T147 29Q147 36 161 51T255 146L359 250L255 354Q174 435 161 449T147 471Q147 480 153 485T168 490Q173 490 175 489Q178 487 284 383L389 278L493 382Q570 459 587 475T609 491Q630 491 630 471Q630 464 620 453T522 355L418 250L522 145Q606 61 618 48T630 29Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(17747.9,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"32",d:"M109 429Q82 429 66 447T50 491Q50 562 103 614T235 666Q326 666 387 610T449 465Q449 422 429 383T381 315T301 241Q265 210 201 149L142 93L218 92Q375 92 385 97Q392 99 409 186V189H449V186Q448 183 436 95T421 3V0H50V19V31Q50 38 56 46T86 81Q115 113 136 137Q145 147 170 174T204 211T233 244T261 278T284 308T305 340T320 369T333 401T340 431T343 464Q343 527 309 573T212 619Q179 619 154 602T119 569T109 550Q109 549 114 549Q132 549 151 535T170 489Q170 464 154 447T109 429Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(19247.9,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(19414.9,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(21725.9,0)"},[e("path",{"data-c":"29",d:"M60 749L64 750Q69 750 74 750H86L114 726Q208 641 251 514T294 250Q294 182 284 119T261 12T224 -76T186 -143T145 -194T113 -227T90 -246Q87 -249 86 -250H74Q66 -250 63 -250T58 -247T55 -238Q56 -237 66 -225Q221 -64 221 250T66 725Q56 737 55 738Q55 746 60 749Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(22392.7,0)"},[e("path",{"data-c":"3D",d:"M56 347Q56 360 70 367H707Q722 359 722 347Q722 336 708 328L390 327H72Q56 332 56 347ZM56 153Q56 168 72 173H708Q722 163 722 153Q722 140 707 133H70Q56 140 56 153Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(23448.4,0)"},[e("path",{"data-c":"31",d:"M213 578L200 573Q186 568 160 563T102 556H83V602H102Q149 604 189 617T245 641T273 663Q275 666 285 666Q294 666 302 660V361L303 61Q310 54 315 52T339 48T401 46H427V0H416Q395 3 257 3Q121 3 100 0H88V46H114Q136 46 152 46T177 47T193 50T201 52T207 57T213 61V578Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(23948.4,0)"},[e("path",{"data-c":"2C",d:"M78 35T78 60T94 103T137 121Q165 121 187 96T210 8Q210 -27 201 -60T180 -117T154 -158T130 -185T117 -194Q113 -194 104 -185T95 -172Q95 -168 106 -156T131 -126T157 -76T173 -3V9L172 8Q170 7 167 6T161 3T152 1T140 0Q113 0 96 17Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(24393.1,0)"},[e("path",{"data-c":"39",d:"M352 287Q304 211 232 211Q154 211 104 270T44 396Q42 412 42 436V444Q42 537 111 606Q171 666 243 666Q245 666 249 666T257 665H261Q273 665 286 663T323 651T370 619T413 560Q456 472 456 334Q456 194 396 97Q361 41 312 10T208 -22Q147 -22 108 7T68 93T121 149Q143 149 158 135T173 96Q173 78 164 65T148 49T135 44L131 43Q131 41 138 37T164 27T206 22H212Q272 22 313 86Q352 142 352 280V287ZM244 248Q292 248 321 297T351 430Q351 508 343 542Q341 552 337 562T323 588T293 615T246 625Q208 625 181 598Q160 576 154 546T147 441Q147 358 152 329T172 282Q197 248 244 248Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"33",d:"M127 463Q100 463 85 480T69 524Q69 579 117 622T233 665Q268 665 277 664Q351 652 390 611T430 522Q430 470 396 421T302 350L299 348Q299 347 308 345T337 336T375 315Q457 262 457 175Q457 96 395 37T238 -22Q158 -22 100 21T42 130Q42 158 60 175T105 193Q133 193 151 175T169 130Q169 119 166 110T159 94T148 82T136 74T126 70T118 67L114 66Q165 21 238 21Q293 21 321 74Q338 107 338 175V195Q338 290 274 322Q259 328 213 329L171 330L168 332Q166 335 166 348Q166 366 174 366Q202 366 232 371Q266 376 294 413T322 525V533Q322 590 287 612Q265 626 240 626Q208 626 181 615T143 592T132 580H135Q138 579 143 578T153 573T165 566T175 555T183 540T186 520Q186 498 172 481T127 463Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(25893.1,0)"},[e("path",{"data-c":"2C",d:"M78 35T78 60T94 103T137 121Q165 121 187 96T210 8Q210 -27 201 -60T180 -117T154 -158T130 -185T117 -194Q113 -194 104 -185T95 -172Q95 -168 106 -156T131 -126T157 -76T173 -3V9L172 8Q170 7 167 6T161 3T152 1T140 0Q113 0 96 17Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(26337.8,0)"},[e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"36",d:"M42 313Q42 476 123 571T303 666Q372 666 402 630T432 550Q432 525 418 510T379 495Q356 495 341 509T326 548Q326 592 373 601Q351 623 311 626Q240 626 194 566Q147 500 147 364L148 360Q153 366 156 373Q197 433 263 433H267Q313 433 348 414Q372 400 396 374T435 317Q456 268 456 210V192Q456 169 451 149Q440 90 387 34T253 -22Q225 -22 199 -14T143 16T92 75T56 172T42 313ZM257 397Q227 397 205 380T171 335T154 278T148 216Q148 133 160 97T198 39Q222 21 251 21Q302 21 329 59Q342 77 347 104T352 209Q352 289 347 316T329 361Q302 397 257 397Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(27837.8,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(28004.8,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})])])],-1),D=[q],A=e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mtext",null,"Total Bytes"),e("mo",null,"="),e("mo",{stretchy:"false"},"("),e("mn",null,"1"),e("mo",null,"×"),e("mn",null,"478"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes"),e("mo",{stretchy:"false"},")"),e("mo",null,"+"),e("mo",{stretchy:"false"},"("),e("mn",null,"4094"),e("mo",null,"×"),e("mn",null,"482"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes"),e("mo",{stretchy:"false"},")"),e("mo",null,"="),e("mn",null,"1"),e("mo",null,","),e("mn",null,"973"),e("mo",null,","),e("mn",null,"786"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes")],-1),R=i("",50),j=JSON.parse('{"title":"Mainnet Beta","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Mainnet Beta | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/mainnet.md","filePath":"nodes/mainnet.md","lastUpdated":1725971357000}'),B={name:"nodes/mainnet.md"},G=Object.assign(B,{setup(d){return(T,Q)=>{const l=n("mjx-assistive-mml"),t=n("mjx-container");return s(),r("div",null,[C,a(M),P,a(p),Z,e("p",null,[a(t,{class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},{default:c(()=>[(s(),r("svg",E,D)),a(l,{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},{default:c(()=>[A]),_:1})]),_:1})]),R])}}});export{j as __pageData,G as default};
+import{M as p}from"./chunks/MainnetVersionTags.eb9befca.js";import{c as h}from"./chunks/constants.295fc0ab.js";import{_ as m,o as s,c as r,k as e,t as o,C as n,H as a,w as c,Q as i,a as u}from"./chunks/framework.b47e54aa.js";import"./chunks/mainnet_versions.1d5e6ed9.js";const f="/docs-preview/pr-1699/img/Mainnet-Beta.png",b="/docs-preview/pr-1699/grove/grove-sandbox.png",y={name:"MainnetBetaDetails",data(){return{constants:h}}},g=e("tr",null,[e("th",null,"Detail"),e("th",null,"Value")],-1),H=e("td",null,"Chain ID",-1),k=e("tr",null,[e("td",null,"Genesis hash"),e("td",null,[e("code",null,"6BE39EFD10BA412A9DB5288488303F5DD32CF386707A5BEF33617F4C43301872")])],-1),V=e("td",null,"Genesis file",-1),w=["href"],L=e("td",null,"Peers file",-1),v=["href"],_=e("tr",null,[e("td",null,"Validators"),e("td",null," 100 ")],-1);function x(d,T,Q,l,t,F){return s(),r("table",null,[g,e("tr",null,[H,e("td",null,[e("code",null,o(t.constants.mainnetChainId),1)])]),k,e("tr",null,[V,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mainnetChainId}/genesis.json`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mainnetChainId)+"/genesis.json ",9,w)])]),e("tr",null,[L,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mainnetChainId}/peers.txt`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mainnetChainId)+"/peers.txt ",9,v)])]),_])}const M=m(y,[["render",x]]),C=i("",8),P=e("h2",{id:"software-version-numbers",tabindex:"-1"},[u("Software version numbers "),e("a",{class:"header-anchor",href:"#software-version-numbers","aria-label":'Permalink to "Software version numbers"'},"​")],-1),Z=i("",8),E={style:{overflow:"visible","min-height":"1px","min-width":"1px","vertical-align":"-0.566ex"},xmlns:"http://www.w3.org/2000/svg",width:"68.588ex",height:"2.262ex",role:"img",focusable:"false",viewBox:"0 -750 30315.8 1000","aria-hidden":"true"},q=e("g",{stroke:"currentColor",fill:"currentColor","stroke-width":"0",transform:"scale(1,-1)"},[e("g",{"data-mml-node":"math"},[e("g",{"data-mml-node":"mtext"},[e("path",{"data-c":"54",d:"M36 443Q37 448 46 558T55 671V677H666V671Q667 666 676 556T685 443V437H645V443Q645 445 642 478T631 544T610 593Q593 614 555 625Q534 630 478 630H451H443Q417 630 414 618Q413 616 413 339V63Q420 53 439 50T528 46H558V0H545L361 3Q186 1 177 0H164V46H194Q264 46 283 49T309 63V339V550Q309 620 304 625T271 630H244H224Q154 630 119 601Q101 585 93 554T81 486T76 443V437H36V443Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"6F",d:"M28 214Q28 309 93 378T250 448Q340 448 405 380T471 215Q471 120 407 55T250 -10Q153 -10 91 57T28 214ZM250 30Q372 30 372 193V225V250Q372 272 371 288T364 326T348 362T317 390T268 410Q263 411 252 411Q222 411 195 399Q152 377 139 338T126 246V226Q126 130 145 91Q177 30 250 30Z",transform:"translate(722,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1222,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"61",d:"M137 305T115 305T78 320T63 359Q63 394 97 421T218 448Q291 448 336 416T396 340Q401 326 401 309T402 194V124Q402 76 407 58T428 40Q443 40 448 56T453 109V145H493V106Q492 66 490 59Q481 29 455 12T400 -6T353 12T329 54V58L327 55Q325 52 322 49T314 40T302 29T287 17T269 6T247 -2T221 -8T190 -11Q130 -11 82 20T34 107Q34 128 41 147T68 188T116 225T194 253T304 268H318V290Q318 324 312 340Q290 411 215 411Q197 411 181 410T156 406T148 403Q170 388 170 359Q170 334 154 320ZM126 106Q126 75 150 51T209 26Q247 26 276 49T315 109Q317 116 318 175Q318 233 317 233Q309 233 296 232T251 223T193 203T147 166T126 106Z",transform:"translate(1611,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"6C",d:"M42 46H56Q95 46 103 60V68Q103 77 103 91T103 124T104 167T104 217T104 272T104 329Q104 366 104 407T104 482T104 542T103 586T103 603Q100 622 89 628T44 637H26V660Q26 683 28 683L38 684Q48 685 67 686T104 688Q121 689 141 690T171 693T182 694H185V379Q185 62 186 60Q190 52 198 49Q219 46 247 46H263V0H255L232 1Q209 2 183 2T145 3T107 3T57 1L34 0H26V46H42Z",transform:"translate(2111,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"20",d:"",transform:"translate(2389,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"42",d:"M131 622Q124 629 120 631T104 634T61 637H28V683H229H267H346Q423 683 459 678T531 651Q574 627 599 590T624 512Q624 461 583 419T476 360L466 357Q539 348 595 302T651 187Q651 119 600 67T469 3Q456 1 242 0H28V46H61Q103 47 112 49T131 61V622ZM511 513Q511 560 485 594T416 636Q415 636 403 636T371 636T333 637Q266 637 251 636T232 628Q229 624 229 499V374H312L396 375L406 377Q410 378 417 380T442 393T474 417T499 456T511 513ZM537 188Q537 239 509 282T430 336L329 337H229V200V116Q229 57 234 52Q240 47 334 47H383Q425 47 443 53Q486 67 511 104T537 188Z",transform:"translate(2639,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(3347,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(3875,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(4264,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(4708,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(5379.8,0)"},[e("path",{"data-c":"3D",d:"M56 347Q56 360 70 367H707Q722 359 722 347Q722 336 708 328L390 327H72Q56 332 56 347ZM56 153Q56 168 72 173H708Q722 163 722 153Q722 140 707 133H70Q56 140 56 153Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(6435.6,0)"},[e("path",{"data-c":"28",d:"M94 250Q94 319 104 381T127 488T164 576T202 643T244 695T277 729T302 750H315H319Q333 750 333 741Q333 738 316 720T275 667T226 581T184 443T167 250T184 58T225 -81T274 -167T316 -220T333 -241Q333 -250 318 -250H315H302L274 -226Q180 -141 137 -14T94 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(6824.6,0)"},[e("path",{"data-c":"31",d:"M213 578L200 573Q186 568 160 563T102 556H83V602H102Q149 604 189 617T245 641T273 663Q275 666 285 666Q294 666 302 660V361L303 61Q310 54 315 52T339 48T401 46H427V0H416Q395 3 257 3Q121 3 100 0H88V46H114Q136 46 152 46T177 47T193 50T201 52T207 57T213 61V578Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(7546.8,0)"},[e("path",{"data-c":"D7",d:"M630 29Q630 9 609 9Q604 9 587 25T493 118L389 222L284 117Q178 13 175 11Q171 9 168 9Q160 9 154 15T147 29Q147 36 161 51T255 146L359 250L255 354Q174 435 161 449T147 471Q147 480 153 485T168 490Q173 490 175 489Q178 487 284 383L389 278L493 382Q570 459 587 475T609 491Q630 491 630 471Q630 464 620 453T522 355L418 250L522 145Q606 61 618 48T630 29Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(8547,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(10047,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(10214,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(12525,0)"},[e("path",{"data-c":"29",d:"M60 749L64 750Q69 750 74 750H86L114 726Q208 641 251 514T294 250Q294 182 284 119T261 12T224 -76T186 -143T145 -194T113 -227T90 -246Q87 -249 86 -250H74Q66 -250 63 -250T58 -247T55 -238Q56 -237 66 -225Q221 -64 221 250T66 725Q56 737 55 738Q55 746 60 749Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(13136.2,0)"},[e("path",{"data-c":"2B",d:"M56 237T56 250T70 270H369V420L370 570Q380 583 389 583Q402 583 409 568V270H707Q722 262 722 250T707 230H409V-68Q401 -82 391 -82H389H387Q375 -82 369 -68V230H70Q56 237 56 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(14136.4,0)"},[e("path",{"data-c":"28",d:"M94 250Q94 319 104 381T127 488T164 576T202 643T244 695T277 729T302 750H315H319Q333 750 333 741Q333 738 316 720T275 667T226 581T184 443T167 250T184 58T225 -81T274 -167T316 -220T333 -241Q333 -250 318 -250H315H302L274 -226Q180 -141 137 -14T94 250Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(14525.4,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"30",d:"M96 585Q152 666 249 666Q297 666 345 640T423 548Q460 465 460 320Q460 165 417 83Q397 41 362 16T301 -15T250 -22Q224 -22 198 -16T137 16T82 83Q39 165 39 320Q39 494 96 585ZM321 597Q291 629 250 629Q208 629 178 597Q153 571 145 525T137 333Q137 175 145 125T181 46Q209 16 250 16Q290 16 318 46Q347 76 354 130T362 333Q362 478 354 524T321 597Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"39",d:"M352 287Q304 211 232 211Q154 211 104 270T44 396Q42 412 42 436V444Q42 537 111 606Q171 666 243 666Q245 666 249 666T257 665H261Q273 665 286 663T323 651T370 619T413 560Q456 472 456 334Q456 194 396 97Q361 41 312 10T208 -22Q147 -22 108 7T68 93T121 149Q143 149 158 135T173 96Q173 78 164 65T148 49T135 44L131 43Q131 41 138 37T164 27T206 22H212Q272 22 313 86Q352 142 352 280V287ZM244 248Q292 248 321 297T351 430Q351 508 343 542Q341 552 337 562T323 588T293 615T246 625Q208 625 181 598Q160 576 154 546T147 441Q147 358 152 329T172 282Q197 248 244 248Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",transform:"translate(1500,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(16747.7,0)"},[e("path",{"data-c":"D7",d:"M630 29Q630 9 609 9Q604 9 587 25T493 118L389 222L284 117Q178 13 175 11Q171 9 168 9Q160 9 154 15T147 29Q147 36 161 51T255 146L359 250L255 354Q174 435 161 449T147 471Q147 480 153 485T168 490Q173 490 175 489Q178 487 284 383L389 278L493 382Q570 459 587 475T609 491Q630 491 630 471Q630 464 620 453T522 355L418 250L522 145Q606 61 618 48T630 29Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(17747.9,0)"},[e("path",{"data-c":"34",d:"M462 0Q444 3 333 3Q217 3 199 0H190V46H221Q241 46 248 46T265 48T279 53T286 61Q287 63 287 115V165H28V211L179 442Q332 674 334 675Q336 677 355 677H373L379 671V211H471V165H379V114Q379 73 379 66T385 54Q393 47 442 46H471V0H462ZM293 211V545L74 212L183 211H293Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"32",d:"M109 429Q82 429 66 447T50 491Q50 562 103 614T235 666Q326 666 387 610T449 465Q449 422 429 383T381 315T301 241Q265 210 201 149L142 93L218 92Q375 92 385 97Q392 99 409 186V189H449V186Q448 183 436 95T421 3V0H50V19V31Q50 38 56 46T86 81Q115 113 136 137Q145 147 170 174T204 211T233 244T261 278T284 308T305 340T320 369T333 401T340 431T343 464Q343 527 309 573T212 619Q179 619 154 602T119 569T109 550Q109 549 114 549Q132 549 151 535T170 489Q170 464 154 447T109 429Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(19247.9,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(19414.9,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(21725.9,0)"},[e("path",{"data-c":"29",d:"M60 749L64 750Q69 750 74 750H86L114 726Q208 641 251 514T294 250Q294 182 284 119T261 12T224 -76T186 -143T145 -194T113 -227T90 -246Q87 -249 86 -250H74Q66 -250 63 -250T58 -247T55 -238Q56 -237 66 -225Q221 -64 221 250T66 725Q56 737 55 738Q55 746 60 749Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(22392.7,0)"},[e("path",{"data-c":"3D",d:"M56 347Q56 360 70 367H707Q722 359 722 347Q722 336 708 328L390 327H72Q56 332 56 347ZM56 153Q56 168 72 173H708Q722 163 722 153Q722 140 707 133H70Q56 140 56 153Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(23448.4,0)"},[e("path",{"data-c":"31",d:"M213 578L200 573Q186 568 160 563T102 556H83V602H102Q149 604 189 617T245 641T273 663Q275 666 285 666Q294 666 302 660V361L303 61Q310 54 315 52T339 48T401 46H427V0H416Q395 3 257 3Q121 3 100 0H88V46H114Q136 46 152 46T177 47T193 50T201 52T207 57T213 61V578Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(23948.4,0)"},[e("path",{"data-c":"2C",d:"M78 35T78 60T94 103T137 121Q165 121 187 96T210 8Q210 -27 201 -60T180 -117T154 -158T130 -185T117 -194Q113 -194 104 -185T95 -172Q95 -168 106 -156T131 -126T157 -76T173 -3V9L172 8Q170 7 167 6T161 3T152 1T140 0Q113 0 96 17Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(24393.1,0)"},[e("path",{"data-c":"39",d:"M352 287Q304 211 232 211Q154 211 104 270T44 396Q42 412 42 436V444Q42 537 111 606Q171 666 243 666Q245 666 249 666T257 665H261Q273 665 286 663T323 651T370 619T413 560Q456 472 456 334Q456 194 396 97Q361 41 312 10T208 -22Q147 -22 108 7T68 93T121 149Q143 149 158 135T173 96Q173 78 164 65T148 49T135 44L131 43Q131 41 138 37T164 27T206 22H212Q272 22 313 86Q352 142 352 280V287ZM244 248Q292 248 321 297T351 430Q351 508 343 542Q341 552 337 562T323 588T293 615T246 625Q208 625 181 598Q160 576 154 546T147 441Q147 358 152 329T172 282Q197 248 244 248Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"33",d:"M127 463Q100 463 85 480T69 524Q69 579 117 622T233 665Q268 665 277 664Q351 652 390 611T430 522Q430 470 396 421T302 350L299 348Q299 347 308 345T337 336T375 315Q457 262 457 175Q457 96 395 37T238 -22Q158 -22 100 21T42 130Q42 158 60 175T105 193Q133 193 151 175T169 130Q169 119 166 110T159 94T148 82T136 74T126 70T118 67L114 66Q165 21 238 21Q293 21 321 74Q338 107 338 175V195Q338 290 274 322Q259 328 213 329L171 330L168 332Q166 335 166 348Q166 366 174 366Q202 366 232 371Q266 376 294 413T322 525V533Q322 590 287 612Q265 626 240 626Q208 626 181 615T143 592T132 580H135Q138 579 143 578T153 573T165 566T175 555T183 540T186 520Q186 498 172 481T127 463Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mo",transform:"translate(25893.1,0)"},[e("path",{"data-c":"2C",d:"M78 35T78 60T94 103T137 121Q165 121 187 96T210 8Q210 -27 201 -60T180 -117T154 -158T130 -185T117 -194Q113 -194 104 -185T95 -172Q95 -168 106 -156T131 -126T157 -76T173 -3V9L172 8Q170 7 167 6T161 3T152 1T140 0Q113 0 96 17Z",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mn",transform:"translate(26337.8,0)"},[e("path",{"data-c":"37",d:"M55 458Q56 460 72 567L88 674Q88 676 108 676H128V672Q128 662 143 655T195 646T364 644H485V605L417 512Q408 500 387 472T360 435T339 403T319 367T305 330T292 284T284 230T278 162T275 80Q275 66 275 52T274 28V19Q270 2 255 -10T221 -22Q210 -22 200 -19T179 0T168 40Q168 198 265 368Q285 400 349 489L395 552H302Q128 552 119 546Q113 543 108 522T98 479L95 458V455H55V458Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"38",d:"M70 417T70 494T124 618T248 666Q319 666 374 624T429 515Q429 485 418 459T392 417T361 389T335 371T324 363L338 354Q352 344 366 334T382 323Q457 264 457 174Q457 95 399 37T249 -22Q159 -22 101 29T43 155Q43 263 172 335L154 348Q133 361 127 368Q70 417 70 494ZM286 386L292 390Q298 394 301 396T311 403T323 413T334 425T345 438T355 454T364 471T369 491T371 513Q371 556 342 586T275 624Q268 625 242 625Q201 625 165 599T128 534Q128 511 141 492T167 463T217 431Q224 426 228 424L286 386ZM250 21Q308 21 350 55T392 137Q392 154 387 169T375 194T353 216T330 234T301 253T274 270Q260 279 244 289T218 306L210 311Q204 311 181 294T133 239T107 157Q107 98 150 60T250 21Z",transform:"translate(500,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"36",d:"M42 313Q42 476 123 571T303 666Q372 666 402 630T432 550Q432 525 418 510T379 495Q356 495 341 509T326 548Q326 592 373 601Q351 623 311 626Q240 626 194 566Q147 500 147 364L148 360Q153 366 156 373Q197 433 263 433H267Q313 433 348 414Q372 400 396 374T435 317Q456 268 456 210V192Q456 169 451 149Q440 90 387 34T253 -22Q225 -22 199 -14T143 16T92 75T56 172T42 313ZM257 397Q227 397 205 380T171 335T154 278T148 216Q148 133 160 97T198 39Q222 21 251 21Q302 21 329 59Q342 77 347 104T352 209Q352 289 347 316T329 361Q302 397 257 397Z",transform:"translate(1000,0)",style:{"stroke-width":"3"}})]),e("g",{"data-mml-node":"mstyle",transform:"translate(27837.8,0)"},[e("g",{"data-mml-node":"mspace"})]),e("g",{"data-mml-node":"mtext",transform:"translate(28004.8,0)"},[e("path",{"data-c":"62",d:"M307 -11Q234 -11 168 55L158 37Q156 34 153 28T147 17T143 10L138 1L118 0H98V298Q98 599 97 603Q94 622 83 628T38 637H20V660Q20 683 22 683L32 684Q42 685 61 686T98 688Q115 689 135 690T165 693T176 694H179V543Q179 391 180 391L183 394Q186 397 192 401T207 411T228 421T254 431T286 439T323 442Q401 442 461 379T522 216Q522 115 458 52T307 -11ZM182 98Q182 97 187 90T196 79T206 67T218 55T233 44T250 35T271 29T295 26Q330 26 363 46T412 113Q424 148 424 212Q424 287 412 323Q385 405 300 405Q270 405 239 390T188 347L182 339V98Z",style:{"stroke-width":"3"}}),e("path",{"data-c":"79",d:"M69 -66Q91 -66 104 -80T118 -116Q118 -134 109 -145T91 -160Q84 -163 97 -166Q104 -168 111 -168Q131 -168 148 -159T175 -138T197 -106T213 -75T225 -43L242 0L170 183Q150 233 125 297Q101 358 96 368T80 381Q79 382 78 382Q66 385 34 385H19V431H26L46 430Q65 430 88 429T122 428Q129 428 142 428T171 429T200 430T224 430L233 431H241V385H232Q183 385 185 366L286 112Q286 113 332 227L376 341V350Q376 365 366 373T348 383T334 385H331V431H337H344Q351 431 361 431T382 430T405 429T422 429Q477 429 503 431H508V385H497Q441 380 422 345Q420 343 378 235T289 9T227 -131Q180 -204 113 -204Q69 -204 44 -177T19 -116Q19 -89 35 -78T69 -66Z",transform:"translate(556,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"74",d:"M27 422Q80 426 109 478T141 600V615H181V431H316V385H181V241Q182 116 182 100T189 68Q203 29 238 29Q282 29 292 100Q293 108 293 146V181H333V146V134Q333 57 291 17Q264 -10 221 -10Q187 -10 162 2T124 33T105 68T98 100Q97 107 97 248V385H18V422H27Z",transform:"translate(1084,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"65",d:"M28 218Q28 273 48 318T98 391T163 433T229 448Q282 448 320 430T378 380T406 316T415 245Q415 238 408 231H126V216Q126 68 226 36Q246 30 270 30Q312 30 342 62Q359 79 369 104L379 128Q382 131 395 131H398Q415 131 415 121Q415 117 412 108Q393 53 349 21T250 -11Q155 -11 92 58T28 218ZM333 275Q322 403 238 411H236Q228 411 220 410T195 402T166 381T143 340T127 274V267H333V275Z",transform:"translate(1473,0)",style:{"stroke-width":"3"}}),e("path",{"data-c":"73",d:"M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z",transform:"translate(1917,0)",style:{"stroke-width":"3"}})])])],-1),D=[q],A=e("math",{xmlns:"http://www.w3.org/1998/Math/MathML"},[e("mtext",null,"Total Bytes"),e("mo",null,"="),e("mo",{stretchy:"false"},"("),e("mn",null,"1"),e("mo",null,"×"),e("mn",null,"478"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes"),e("mo",{stretchy:"false"},")"),e("mo",null,"+"),e("mo",{stretchy:"false"},"("),e("mn",null,"4094"),e("mo",null,"×"),e("mn",null,"482"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes"),e("mo",{stretchy:"false"},")"),e("mo",null,"="),e("mn",null,"1"),e("mo",null,","),e("mn",null,"973"),e("mo",null,","),e("mn",null,"786"),e("mstyle",{scriptlevel:"0"},[e("mspace",{width:"0.167em"})]),e("mtext",null,"bytes")],-1),R=i("",50),j=JSON.parse('{"title":"Mainnet Beta","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Mainnet Beta | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/mainnet.md","filePath":"nodes/mainnet.md","lastUpdated":1725992025000}'),B={name:"nodes/mainnet.md"},G=Object.assign(B,{setup(d){return(T,Q)=>{const l=n("mjx-assistive-mml"),t=n("mjx-container");return s(),r("div",null,[C,a(M),P,a(p),Z,e("p",null,[a(t,{class:"MathJax",jax:"SVG",style:{direction:"ltr",position:"relative"}},{default:c(()=>[(s(),r("svg",E,D)),a(l,{unselectable:"on",display:"inline",style:{top:"0px",left:"0px",clip:"rect(1px, 1px, 1px, 1px)","-webkit-touch-callout":"none","-webkit-user-select":"none","-khtml-user-select":"none","-moz-user-select":"none","-ms-user-select":"none","user-select":"none",position:"absolute",padding:"1px 0px 0px 0px",border:"0px",display:"block",width:"auto",overflow:"hidden"}},{default:c(()=>[A]),_:1})]),_:1})]),R])}}});export{j as __pageData,G as default};
diff --git a/pr-1699/assets/nodes_mocha-testnet.md.58edd1a9.js b/pr-1699/assets/nodes_mocha-testnet.md.0e4cf674.js
similarity index 99%
rename from pr-1699/assets/nodes_mocha-testnet.md.58edd1a9.js
rename to pr-1699/assets/nodes_mocha-testnet.md.0e4cf674.js
index a38eca36fc..7510ed12d3 100644
--- a/pr-1699/assets/nodes_mocha-testnet.md.58edd1a9.js
+++ b/pr-1699/assets/nodes_mocha-testnet.md.0e4cf674.js
@@ -1 +1 @@
-import{M as d}from"./chunks/MochaVersionTags.743560ae.js";import{c as h}from"./chunks/constants.295fc0ab.js";import{_ as p,o as s,c as i,k as e,t as o,H as a,Q as r,a as u}from"./chunks/framework.b47e54aa.js";import"./chunks/mocha_versions.7704b055.js";const m="/docs-preview/pr-1699/img/mocha.jpg",f={name:"MochaTestnetDetails",data(){return{constants:h}}},g=e("tr",null,[e("th",null,"Detail"),e("th",null,"Value")],-1),b=e("td",null,"Chain ID",-1),k=e("tr",null,[e("td",null,"Genesis hash"),e("td",null,[e("code",null,"B93BBE20A0FBFDF955811B6420F8433904664D45DB4BF51022BE4200C1A1680D")])],-1),y=e("td",null,"Genesis file",-1),_=["href"],w=e("td",null,"Peers file",-1),v=["href"],C=e("tr",null,[e("td",null,"Validators"),e("td",null," 100 ")],-1);function P(l,n,c,S,t,E){return s(),i("table",null,[g,e("tr",null,[b,e("td",null,[e("code",null,o(t.constants.mochaChainId),1)])]),k,e("tr",null,[y,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mochaChainId}/genesis.json`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mochaChainId)+"/genesis.json ",9,_)])]),e("tr",null,[w,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mochaChainId}/peers.txt`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mochaChainId)+"/peers.txt ",9,v)])]),C])}const T=p(f,[["render",P]]),R=r('
    Mocha testnet ​
    mocha-testnet
    This guide contains the relevant sections for how to connect to Mocha, depending on the type of node you are running. Mocha testnet is designed to help validators test out their infrastructure and node software. Developers are encouraged to deploy their sovereign rollups on Mocha, but we also recommend Arabica devnet for that as it is designed for development purposes.
    Mocha is a milestone in Celestia, allowing everyone to test out core functionalities on the network. Read the announcement. Your best approach to participating is to first determine which node you would like to run. Each node's guide will link to the relevant networks, to show you how to connect to them.
    You have a list of options on the types of nodes you can run to participate in Mocha:
    Consensus:
    Data Availability:
    Select the type of node you would like to run and follow the instructions on each respective page. Whenever you are asked to select the type of network you want to connect to in those guides, select Mocha to refer to the correct instructions on this page on how to connect to Mocha.
    Network details ​
    ',11),x=e("h2",{id:"software-version-numbers",tabindex:"-1"},[u("Software version numbers "),e("a",{class:"header-anchor",href:"#software-version-numbers","aria-label":'Permalink to "Software version numbers"'},"​")],-1),A=r('
    RPC for DA bridge, full, and light nodes ​
    Production RPC endpoints ​
    These RPC providers are meant to be used in production environments.
    ProviderURL
    NewMetrichttps://app.newmetric.xyz/start
    NumiaFor RPC access: https://docs.numia.xyz/overview/rpc-api-access
    NumiaFor data warehouse access: https://docs.numia.xyz/overview/sql-access/chains/celestia
    Grovehttps://www.grove.city/
    WARNING
    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs or your own node.
    Community Data availability (DA) RPC endpoints for bridge node sync ​
    These RPC endpoints allow bridge nodes to sync blocks from the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default RPC port at 26657 to their respective DA node.
    Community Data availability (DA) gRPC endpoints for state access ​
    These gRPC endpoints for DA nodes provide state access for querying the chain’s state and broadcasting transactions (balances, blobs, etc.) to the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default gRPC port at 9090 to their respective DA node.
    Bridge nodes
    Mentioned below RPC endpoints do not guarantee you the download of full blocks from them. We advise that if you are running a bridge node, that you also run a local consensus node in order to download full blocks from it.
    • public-celestia-mocha4-consensus.numia.xyz
    • mocha-4-consensus.mesa.newmetric.xyz
    • full.consensus.mocha-4.celestia-mocha.com
    • consensus-full-mocha-4.celestia-mocha.com
    • rpc-mocha.pops.one
    • celestia-testnet-consensus.itrocket.net
      • RPC port: 26657
      • gRPC port: 9090
    • rpc-celestia-testnet.cryptech.com.ua
      • gRPC: grpc-celestia-testnet.cryptech.com.ua:443
    • rpc.celestia.testnet.dteam.tech:443
      • gRPC: grpc.celestia.testnet.dteam.tech:27090
    • celestia-consensus-testnet.noders.services
      • RPC port: 26357
      • gRPC port: 9070
    Community RPC endpoints ​
    The RPC endpoint is to allow users to interact with Celestia's nodes by querying the node's state and broadcasting transactions on the Celestia network. The default port is 26657.
    • public-celestia-mocha4-consensus.numia.xyz:26657
    • mocha-4-consensus.mesa.newmetric.xyz:26657
    • rpc.celestia-mocha.com
    • celestia-testnet-rpc.f5nodes.com
    • celestia-testnet.brightlystake.com
    • rpc-celestia-mocha.architectnodes.com
    • rpc-celestia-mocha.trusted-point.com
    • rpc-celestia-testnet-01.stakeflow.io
    • mocha.celestia.rpc.cumulo.me
    • rpc-mocha-4.spidey.services
    • rpc-mocha-full.avril14th.org
    • rpc.mocha.bitszn.com
    • celestia-t-rpc.noders.services/
    • rpc-1.testnet.celestia.nodes.guru
    • rpc-2.testnet.celestia.nodes.guru
    • celestia-testnet-rpc.itrocket.net:443
    • rpc-celestia-testnet.cryptech.com.ua:443
    • rpc.celestia.testnet.dteam.tech:443
    Community API endpoints ​
    The API endpoint is to allow users to interact with the REST API in Cosmos SDK which is implemented using gRPC-gateway, which exposes gRPC endpoints as REST endpoints. This allows for communication with the node using REST calls, which can be useful if the client does not support gRPC or HTTP2. The default port is 1317.
    Community gRPC endpoints ​
    The gRPC endpoint is to allow users to interact with a Celestia Node using gRPC, a modern open-source and high-performance RPC framework. The default port is 9090. In the Cosmos SDK, gRPC is used to define state queries and broadcast transactions.
    • public-celestia-mocha4-consensus.numia.xyz:9090
    • mocha-4-consensus.mesa.newmetric.xyz:9090
    • grpc-mocha.pops.one
    • grpc.celestia-mocha.com:443
    • full.consensus.mocha-4.celestia-mocha.com:9090
    • consensus-full-mocha-4.celestia-mocha.com:9090
    • celestia-testnet-grpc.f5nodes.com
    • celestia-testnet.brightlystake.com:9390
    • grpc-celestia-mocha.architectnodes.com:1443
    • grpc-celestia-mocha.trusted-point.com:9099
    • grpc-celestia-testnet-01.stakeflow.io:16002
    • mocha.grpc.cumulo.me:443
    • grpc-mocha-4.spidey.services
    • grpc-mocha-full.avril14th.org
    • grpc.mocha.bitszn.com
    • celestia-grpc.noders.services:21090
    • grpc-1.testnet.celestia.nodes.guru:10790
    • grpc-2.testnet.celestia.nodes.guru:10790
    • celestia-testnet-grpc.itrocket.net:443
    • grpc-celestia-testnet.cryptech.com.ua:443
    • grpc.celestia.testnet.dteam.tech:27090
    Community bridge and full node endpoints ​
    The endpoints below are for bridge and full nodes only. They can be used to find bootstrapper peers in the p2p network.
    Bridge node 1:
    • da-bridge-mocha-4.celestia-mocha.com
    • bridge-mocha-4.da.celestia-mocha.com
    Bridge node 2:
    • da-bridge-mocha-4-2.celestia-mocha.com
    • bridge-mocha-4-2.da.celestia-mocha.com
    Full node 1:
    • da-full-1-mocha-4.celestia-mocha.com
    • full-1-mocha-4.da.celestia-mocha.com
    Full node 2:
    • da-full-2-mocha-4.celestia-mocha.com
    • full-2-mocha-4.da.celestia-mocha.com
    Mocha testnet faucet ​
    WARNING
    USING THIS FAUCET DOES NOT ENTITLE YOU TO ANY AIRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS.
    You can request from Mocha testnet Faucet on the #mocha-faucet channel on Celestia's Discord server with the following command:
    text
    $request <CELESTIA-ADDRESS>
    $request <CELESTIA-ADDRESS>
    Where <CELESTIA-ADDRESS> is a celestia1****** generated address.
    NOTE
    Faucet has a limit of 10 tokens per week per address/Discord ID.
    Analytics ​
    The following websites provide analytics for Mocha Testnet:
    Explorers ​
    There are several explorers you can use for Mocha:
    Network upgrades ​
    There are a few ways to stay informed about network upgrades on Mocha testnet:
    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.
    ',46),F=JSON.parse('{"title":"Mocha testnet","description":"Learn how to connect to the Mocha network.","frontmatter":{"description":"Learn how to connect to the Mocha network.","head":[["meta",{"name":"og:title","content":"Mocha testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/mocha-testnet.md","filePath":"nodes/mocha-testnet.md","lastUpdated":1725971357000}'),D={name:"nodes/mocha-testnet.md"},B=Object.assign(D,{setup(l){return(n,c)=>(s(),i("div",null,[R,a(T),x,a(d),A]))}});export{F as __pageData,B as default};
+import{M as d}from"./chunks/MochaVersionTags.743560ae.js";import{c as h}from"./chunks/constants.295fc0ab.js";import{_ as p,o as s,c as i,k as e,t as o,H as a,Q as r,a as u}from"./chunks/framework.b47e54aa.js";import"./chunks/mocha_versions.7704b055.js";const m="/docs-preview/pr-1699/img/mocha.jpg",f={name:"MochaTestnetDetails",data(){return{constants:h}}},g=e("tr",null,[e("th",null,"Detail"),e("th",null,"Value")],-1),b=e("td",null,"Chain ID",-1),k=e("tr",null,[e("td",null,"Genesis hash"),e("td",null,[e("code",null,"B93BBE20A0FBFDF955811B6420F8433904664D45DB4BF51022BE4200C1A1680D")])],-1),y=e("td",null,"Genesis file",-1),_=["href"],w=e("td",null,"Peers file",-1),v=["href"],C=e("tr",null,[e("td",null,"Validators"),e("td",null," 100 ")],-1);function P(l,n,c,S,t,E){return s(),i("table",null,[g,e("tr",null,[b,e("td",null,[e("code",null,o(t.constants.mochaChainId),1)])]),k,e("tr",null,[y,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mochaChainId}/genesis.json`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mochaChainId)+"/genesis.json ",9,_)])]),e("tr",null,[w,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mochaChainId}/peers.txt`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mochaChainId)+"/peers.txt ",9,v)])]),C])}const T=p(f,[["render",P]]),R=r('
    Mocha testnet ​
    mocha-testnet
    This guide contains the relevant sections for how to connect to Mocha, depending on the type of node you are running. Mocha testnet is designed to help validators test out their infrastructure and node software. Developers are encouraged to deploy their sovereign rollups on Mocha, but we also recommend Arabica devnet for that as it is designed for development purposes.
    Mocha is a milestone in Celestia, allowing everyone to test out core functionalities on the network. Read the announcement. Your best approach to participating is to first determine which node you would like to run. Each node's guide will link to the relevant networks, to show you how to connect to them.
    You have a list of options on the types of nodes you can run to participate in Mocha:
    Consensus:
    Data Availability:
    Select the type of node you would like to run and follow the instructions on each respective page. Whenever you are asked to select the type of network you want to connect to in those guides, select Mocha to refer to the correct instructions on this page on how to connect to Mocha.
    Network details ​
    ',11),x=e("h2",{id:"software-version-numbers",tabindex:"-1"},[u("Software version numbers "),e("a",{class:"header-anchor",href:"#software-version-numbers","aria-label":'Permalink to "Software version numbers"'},"​")],-1),A=r('
    RPC for DA bridge, full, and light nodes ​
    Production RPC endpoints ​
    These RPC providers are meant to be used in production environments.
    ProviderURL
    NewMetrichttps://app.newmetric.xyz/start
    NumiaFor RPC access: https://docs.numia.xyz/overview/rpc-api-access
    NumiaFor data warehouse access: https://docs.numia.xyz/overview/sql-access/chains/celestia
    Grovehttps://www.grove.city/
    WARNING
    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs or your own node.
    Community Data availability (DA) RPC endpoints for bridge node sync ​
    These RPC endpoints allow bridge nodes to sync blocks from the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default RPC port at 26657 to their respective DA node.
    Community Data availability (DA) gRPC endpoints for state access ​
    These gRPC endpoints for DA nodes provide state access for querying the chain’s state and broadcasting transactions (balances, blobs, etc.) to the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default gRPC port at 9090 to their respective DA node.
    Bridge nodes
    Mentioned below RPC endpoints do not guarantee you the download of full blocks from them. We advise that if you are running a bridge node, that you also run a local consensus node in order to download full blocks from it.
    • public-celestia-mocha4-consensus.numia.xyz
    • mocha-4-consensus.mesa.newmetric.xyz
    • full.consensus.mocha-4.celestia-mocha.com
    • consensus-full-mocha-4.celestia-mocha.com
    • rpc-mocha.pops.one
    • celestia-testnet-consensus.itrocket.net
      • RPC port: 26657
      • gRPC port: 9090
    • rpc-celestia-testnet.cryptech.com.ua
      • gRPC: grpc-celestia-testnet.cryptech.com.ua:443
    • rpc.celestia.testnet.dteam.tech:443
      • gRPC: grpc.celestia.testnet.dteam.tech:27090
    • celestia-consensus-testnet.noders.services
      • RPC port: 26357
      • gRPC port: 9070
    Community RPC endpoints ​
    The RPC endpoint is to allow users to interact with Celestia's nodes by querying the node's state and broadcasting transactions on the Celestia network. The default port is 26657.
    • public-celestia-mocha4-consensus.numia.xyz:26657
    • mocha-4-consensus.mesa.newmetric.xyz:26657
    • rpc.celestia-mocha.com
    • celestia-testnet-rpc.f5nodes.com
    • celestia-testnet.brightlystake.com
    • rpc-celestia-mocha.architectnodes.com
    • rpc-celestia-mocha.trusted-point.com
    • rpc-celestia-testnet-01.stakeflow.io
    • mocha.celestia.rpc.cumulo.me
    • rpc-mocha-4.spidey.services
    • rpc-mocha-full.avril14th.org
    • rpc.mocha.bitszn.com
    • celestia-t-rpc.noders.services/
    • rpc-1.testnet.celestia.nodes.guru
    • rpc-2.testnet.celestia.nodes.guru
    • celestia-testnet-rpc.itrocket.net:443
    • rpc-celestia-testnet.cryptech.com.ua:443
    • rpc.celestia.testnet.dteam.tech:443
    Community API endpoints ​
    The API endpoint is to allow users to interact with the REST API in Cosmos SDK which is implemented using gRPC-gateway, which exposes gRPC endpoints as REST endpoints. This allows for communication with the node using REST calls, which can be useful if the client does not support gRPC or HTTP2. The default port is 1317.
    Community gRPC endpoints ​
    The gRPC endpoint is to allow users to interact with a Celestia Node using gRPC, a modern open-source and high-performance RPC framework. The default port is 9090. In the Cosmos SDK, gRPC is used to define state queries and broadcast transactions.
    • public-celestia-mocha4-consensus.numia.xyz:9090
    • mocha-4-consensus.mesa.newmetric.xyz:9090
    • grpc-mocha.pops.one
    • grpc.celestia-mocha.com:443
    • full.consensus.mocha-4.celestia-mocha.com:9090
    • consensus-full-mocha-4.celestia-mocha.com:9090
    • celestia-testnet-grpc.f5nodes.com
    • celestia-testnet.brightlystake.com:9390
    • grpc-celestia-mocha.architectnodes.com:1443
    • grpc-celestia-mocha.trusted-point.com:9099
    • grpc-celestia-testnet-01.stakeflow.io:16002
    • mocha.grpc.cumulo.me:443
    • grpc-mocha-4.spidey.services
    • grpc-mocha-full.avril14th.org
    • grpc.mocha.bitszn.com
    • celestia-grpc.noders.services:21090
    • grpc-1.testnet.celestia.nodes.guru:10790
    • grpc-2.testnet.celestia.nodes.guru:10790
    • celestia-testnet-grpc.itrocket.net:443
    • grpc-celestia-testnet.cryptech.com.ua:443
    • grpc.celestia.testnet.dteam.tech:27090
    Community bridge and full node endpoints ​
    The endpoints below are for bridge and full nodes only. They can be used to find bootstrapper peers in the p2p network.
    Bridge node 1:
    • da-bridge-mocha-4.celestia-mocha.com
    • bridge-mocha-4.da.celestia-mocha.com
    Bridge node 2:
    • da-bridge-mocha-4-2.celestia-mocha.com
    • bridge-mocha-4-2.da.celestia-mocha.com
    Full node 1:
    • da-full-1-mocha-4.celestia-mocha.com
    • full-1-mocha-4.da.celestia-mocha.com
    Full node 2:
    • da-full-2-mocha-4.celestia-mocha.com
    • full-2-mocha-4.da.celestia-mocha.com
    Mocha testnet faucet ​
    WARNING
    USING THIS FAUCET DOES NOT ENTITLE YOU TO ANY AIRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS.
    You can request from Mocha testnet Faucet on the #mocha-faucet channel on Celestia's Discord server with the following command:
    text
    $request <CELESTIA-ADDRESS>
    $request <CELESTIA-ADDRESS>
    Where <CELESTIA-ADDRESS> is a celestia1****** generated address.
    NOTE
    Faucet has a limit of 10 tokens per week per address/Discord ID.
    Analytics ​
    The following websites provide analytics for Mocha Testnet:
    Explorers ​
    There are several explorers you can use for Mocha:
    Network upgrades ​
    There are a few ways to stay informed about network upgrades on Mocha testnet:
    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.
    ',46),F=JSON.parse('{"title":"Mocha testnet","description":"Learn how to connect to the Mocha network.","frontmatter":{"description":"Learn how to connect to the Mocha network.","head":[["meta",{"name":"og:title","content":"Mocha testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/mocha-testnet.md","filePath":"nodes/mocha-testnet.md","lastUpdated":1725992025000}'),D={name:"nodes/mocha-testnet.md"},B=Object.assign(D,{setup(l){return(n,c)=>(s(),i("div",null,[R,a(T),x,a(d),A]))}});export{F as __pageData,B as default};
diff --git a/pr-1699/assets/nodes_mocha-testnet.md.58edd1a9.lean.js b/pr-1699/assets/nodes_mocha-testnet.md.0e4cf674.lean.js
similarity index 97%
rename from pr-1699/assets/nodes_mocha-testnet.md.58edd1a9.lean.js
rename to pr-1699/assets/nodes_mocha-testnet.md.0e4cf674.lean.js
index 76f7a82236..391b421d6a 100644
--- a/pr-1699/assets/nodes_mocha-testnet.md.58edd1a9.lean.js
+++ b/pr-1699/assets/nodes_mocha-testnet.md.0e4cf674.lean.js
@@ -1 +1 @@
-import{M as d}from"./chunks/MochaVersionTags.743560ae.js";import{c as h}from"./chunks/constants.295fc0ab.js";import{_ as p,o as s,c as i,k as e,t as o,H as a,Q as r,a as u}from"./chunks/framework.b47e54aa.js";import"./chunks/mocha_versions.7704b055.js";const m="/docs-preview/pr-1699/img/mocha.jpg",f={name:"MochaTestnetDetails",data(){return{constants:h}}},g=e("tr",null,[e("th",null,"Detail"),e("th",null,"Value")],-1),b=e("td",null,"Chain ID",-1),k=e("tr",null,[e("td",null,"Genesis hash"),e("td",null,[e("code",null,"B93BBE20A0FBFDF955811B6420F8433904664D45DB4BF51022BE4200C1A1680D")])],-1),y=e("td",null,"Genesis file",-1),_=["href"],w=e("td",null,"Peers file",-1),v=["href"],C=e("tr",null,[e("td",null,"Validators"),e("td",null," 100 ")],-1);function P(l,n,c,S,t,E){return s(),i("table",null,[g,e("tr",null,[b,e("td",null,[e("code",null,o(t.constants.mochaChainId),1)])]),k,e("tr",null,[y,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mochaChainId}/genesis.json`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mochaChainId)+"/genesis.json ",9,_)])]),e("tr",null,[w,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mochaChainId}/peers.txt`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mochaChainId)+"/peers.txt ",9,v)])]),C])}const T=p(f,[["render",P]]),R=r("",11),x=e("h2",{id:"software-version-numbers",tabindex:"-1"},[u("Software version numbers "),e("a",{class:"header-anchor",href:"#software-version-numbers","aria-label":'Permalink to "Software version numbers"'},"​")],-1),A=r("",46),F=JSON.parse('{"title":"Mocha testnet","description":"Learn how to connect to the Mocha network.","frontmatter":{"description":"Learn how to connect to the Mocha network.","head":[["meta",{"name":"og:title","content":"Mocha testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/mocha-testnet.md","filePath":"nodes/mocha-testnet.md","lastUpdated":1725971357000}'),D={name:"nodes/mocha-testnet.md"},B=Object.assign(D,{setup(l){return(n,c)=>(s(),i("div",null,[R,a(T),x,a(d),A]))}});export{F as __pageData,B as default};
+import{M as d}from"./chunks/MochaVersionTags.743560ae.js";import{c as h}from"./chunks/constants.295fc0ab.js";import{_ as p,o as s,c as i,k as e,t as o,H as a,Q as r,a as u}from"./chunks/framework.b47e54aa.js";import"./chunks/mocha_versions.7704b055.js";const m="/docs-preview/pr-1699/img/mocha.jpg",f={name:"MochaTestnetDetails",data(){return{constants:h}}},g=e("tr",null,[e("th",null,"Detail"),e("th",null,"Value")],-1),b=e("td",null,"Chain ID",-1),k=e("tr",null,[e("td",null,"Genesis hash"),e("td",null,[e("code",null,"B93BBE20A0FBFDF955811B6420F8433904664D45DB4BF51022BE4200C1A1680D")])],-1),y=e("td",null,"Genesis file",-1),_=["href"],w=e("td",null,"Peers file",-1),v=["href"],C=e("tr",null,[e("td",null,"Validators"),e("td",null," 100 ")],-1);function P(l,n,c,S,t,E){return s(),i("table",null,[g,e("tr",null,[b,e("td",null,[e("code",null,o(t.constants.mochaChainId),1)])]),k,e("tr",null,[y,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mochaChainId}/genesis.json`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mochaChainId)+"/genesis.json ",9,_)])]),e("tr",null,[w,e("td",null,[e("a",{href:`https://github.com/celestiaorg/networks/blob/master/${t.constants.mochaChainId}/peers.txt`,target:"_blank",rel:"noopener noreferrer"}," https://github.com/celestiaorg/networks/blob/master/"+o(t.constants.mochaChainId)+"/peers.txt ",9,v)])]),C])}const T=p(f,[["render",P]]),R=r("",11),x=e("h2",{id:"software-version-numbers",tabindex:"-1"},[u("Software version numbers "),e("a",{class:"header-anchor",href:"#software-version-numbers","aria-label":'Permalink to "Software version numbers"'},"​")],-1),A=r("",46),F=JSON.parse('{"title":"Mocha testnet","description":"Learn how to connect to the Mocha network.","frontmatter":{"description":"Learn how to connect to the Mocha network.","head":[["meta",{"name":"og:title","content":"Mocha testnet | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/mocha-testnet.md","filePath":"nodes/mocha-testnet.md","lastUpdated":1725992025000}'),D={name:"nodes/mocha-testnet.md"},B=Object.assign(D,{setup(l){return(n,c)=>(s(),i("div",null,[R,a(T),x,a(d),A]))}});export{F as __pageData,B as default};
diff --git a/pr-1699/assets/nodes_overview.md.8cf8c5aa.js b/pr-1699/assets/nodes_overview.md.4223caea.js
similarity index 98%
rename from pr-1699/assets/nodes_overview.md.8cf8c5aa.js
rename to pr-1699/assets/nodes_overview.md.4223caea.js
index ca07b153f1..3ee8c6d5ab 100644
--- a/pr-1699/assets/nodes_overview.md.8cf8c5aa.js
+++ b/pr-1699/assets/nodes_overview.md.4223caea.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const v=JSON.parse('{"title":"Overview to running nodes on Celestia","description":"An overview on how to participate in the Celestia network.","frontmatter":{"description":"An overview on how to participate in the Celestia network.","head":[["meta",{"name":"og:title","content":"Overview to running nodes on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/overview.md","filePath":"nodes/overview.md","lastUpdated":1725971357000}'),n={name:"nodes/overview.md"},d=o('
    Overview to running nodes on Celestia ​
    There are many ways you can participate in the Celestia networks.
    Celestia node operators can run several options on the network.
    Consensus:
    • Validator node: This type of node participates in consensus by producing and voting on blocks.
    • Consensus node: A celestia-app full node to sync blockchain history.
    Data Availability:
    • Bridge node: This node bridges blocks between the Data-Availability network and the Consensus network.
    • Full storage node: This node stores all the data but does not connect to Consensus.
    • Light node: Light clients conduct data availability sampling on the Data Availability network.
    You can learn more about how to set up each different node by going through each tutorial guide.
    Data availability nodes ​
    Node typeMemoryCPUDiskBandwidth
    Light node500 MB RAMSingle core100 GB SSD56 Kbps
    Bridge node16 GB RAM6 cores10 TB SSD1 Gbps
    Full storage node16 GB RAMQuad-core10 TB SSD1 Gbps
    Consensus nodes ​
    Node typeMemoryCPUDiskBandwidth
    Validator16 GB RAM8 cores2 TB SSD1 Gbps
    Consensus node16 GB RAMQuad-core2 TB SSD1 Gbps
    Please provide any feedback on the tutorials and guides. If you notice a bug or issue, feel free to make a pull request or write up a Github issue!
    ',14),i=[d];function s(r,l,h,c,u,p){return t(),a("div",null,i)}const m=e(n,[["render",s]]);export{v as __pageData,m as default};
+import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const v=JSON.parse('{"title":"Overview to running nodes on Celestia","description":"An overview on how to participate in the Celestia network.","frontmatter":{"description":"An overview on how to participate in the Celestia network.","head":[["meta",{"name":"og:title","content":"Overview to running nodes on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/overview.md","filePath":"nodes/overview.md","lastUpdated":1725992025000}'),n={name:"nodes/overview.md"},d=o('
    Overview to running nodes on Celestia ​
    There are many ways you can participate in the Celestia networks.
    Celestia node operators can run several options on the network.
    Consensus:
    • Validator node: This type of node participates in consensus by producing and voting on blocks.
    • Consensus node: A celestia-app full node to sync blockchain history.
    Data Availability:
    • Bridge node: This node bridges blocks between the Data-Availability network and the Consensus network.
    • Full storage node: This node stores all the data but does not connect to Consensus.
    • Light node: Light clients conduct data availability sampling on the Data Availability network.
    You can learn more about how to set up each different node by going through each tutorial guide.
    Data availability nodes ​
    Node typeMemoryCPUDiskBandwidth
    Light node500 MB RAMSingle core100 GB SSD56 Kbps
    Bridge node16 GB RAM6 cores10 TB SSD1 Gbps
    Full storage node16 GB RAMQuad-core10 TB SSD1 Gbps
    Consensus nodes ​
    Node typeMemoryCPUDiskBandwidth
    Validator16 GB RAM8 cores2 TB SSD1 Gbps
    Consensus node16 GB RAMQuad-core2 TB SSD1 Gbps
    Please provide any feedback on the tutorials and guides. If you notice a bug or issue, feel free to make a pull request or write up a Github issue!
    ',14),i=[d];function s(r,l,h,c,u,p){return t(),a("div",null,i)}const m=e(n,[["render",s]]);export{v as __pageData,m as default};
diff --git a/pr-1699/assets/nodes_overview.md.8cf8c5aa.lean.js b/pr-1699/assets/nodes_overview.md.4223caea.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_overview.md.8cf8c5aa.lean.js
rename to pr-1699/assets/nodes_overview.md.4223caea.lean.js
index 7f9146a69f..3cf66ac754 100644
--- a/pr-1699/assets/nodes_overview.md.8cf8c5aa.lean.js
+++ b/pr-1699/assets/nodes_overview.md.4223caea.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const v=JSON.parse('{"title":"Overview to running nodes on Celestia","description":"An overview on how to participate in the Celestia network.","frontmatter":{"description":"An overview on how to participate in the Celestia network.","head":[["meta",{"name":"og:title","content":"Overview to running nodes on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/overview.md","filePath":"nodes/overview.md","lastUpdated":1725971357000}'),n={name:"nodes/overview.md"},d=o("",14),i=[d];function s(r,l,h,c,u,p){return t(),a("div",null,i)}const m=e(n,[["render",s]]);export{v as __pageData,m as default};
+import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const v=JSON.parse('{"title":"Overview to running nodes on Celestia","description":"An overview on how to participate in the Celestia network.","frontmatter":{"description":"An overview on how to participate in the Celestia network.","head":[["meta",{"name":"og:title","content":"Overview to running nodes on Celestia | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/overview.md","filePath":"nodes/overview.md","lastUpdated":1725992025000}'),n={name:"nodes/overview.md"},d=o("",14),i=[d];function s(r,l,h,c,u,p){return t(),a("div",null,i)}const m=e(n,[["render",s]]);export{v as __pageData,m as default};
diff --git a/pr-1699/assets/nodes_participate.md.cd0dcc78.js b/pr-1699/assets/nodes_participate.md.704b27c3.js
similarity index 98%
rename from pr-1699/assets/nodes_participate.md.cd0dcc78.js
rename to pr-1699/assets/nodes_participate.md.704b27c3.js
index 9e5fdb0e59..e62927415e 100644
--- a/pr-1699/assets/nodes_participate.md.cd0dcc78.js
+++ b/pr-1699/assets/nodes_participate.md.704b27c3.js
@@ -1 +1 @@
-import{A as t}from"./chunks/ArabicaVersionTags.5d1acc99.js";import{M as o}from"./chunks/MochaVersionTags.743560ae.js";import{M as r}from"./chunks/MainnetVersionTags.eb9befca.js";import{o as n,c as i,H as a,Q as e}from"./chunks/framework.b47e54aa.js";import"./chunks/arabica_versions.1930378b.js";import"./chunks/constants.295fc0ab.js";import"./chunks/mocha_versions.7704b055.js";import"./chunks/mainnet_versions.1d5e6ed9.js";const s=e('
    Participate in the Celestia networks ​
    Mainnet Beta ​
    Celestia’s Mainnet Beta is the production network for deploying mainnet rollups and applications. This marks the culmination of years of development and community testing. While the network is stable and continues to receive updates, it remains experimental and users may experience occasional instability or reduced performance.
    Compatible software versions for Mainnet Beta ​
    ',4),c=e('
    Testnets ​
    Celestia currently has two existing testnets that you can participate in:
    Arabica Devnet ​
    Arabica devnet is a devnet focused on developers who want to deploy sovereign rollups on the latest changes from Celestia's codebase. Arabica will be updated frequently and might be unstable at times given new updates. Validators won't be able to validate on Arabica as it is not designed for validators to participate.
    Compatible software versions for Arabica devnet ​
    ',5),l=e('
    Mocha testnet ​
    Mocha testnet is a testnet focused on enabling validators to test out their infrastructure by running nodes connected to the network. Developers can also deploy sovereign rollups on Mocha, it just will always be behind Arabica as Mocha upgrades are slower given they need to be done via hardforks in coordination with the validator community on Mocha.
    Compatible software versions for Mocha testnet ​
    ',3),h=e('
    Network upgrades ​
    There are a few ways to stay informed about network upgrades:
    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.
    ',4),A=JSON.parse('{"title":"Participate in the Celestia networks","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Participate in the Celestia networks | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/participate.md","filePath":"nodes/participate.md","lastUpdated":1725971357000}'),d={name:"nodes/participate.md"},P=Object.assign(d,{setup(p){return(m,f)=>(n(),i("div",null,[s,a(r),c,a(t),l,a(o),h]))}});export{A as __pageData,P as default};
+import{A as t}from"./chunks/ArabicaVersionTags.5d1acc99.js";import{M as o}from"./chunks/MochaVersionTags.743560ae.js";import{M as r}from"./chunks/MainnetVersionTags.eb9befca.js";import{o as n,c as i,H as a,Q as e}from"./chunks/framework.b47e54aa.js";import"./chunks/arabica_versions.1930378b.js";import"./chunks/constants.295fc0ab.js";import"./chunks/mocha_versions.7704b055.js";import"./chunks/mainnet_versions.1d5e6ed9.js";const s=e('
    Participate in the Celestia networks ​
    Mainnet Beta ​
    Celestia’s Mainnet Beta is the production network for deploying mainnet rollups and applications. This marks the culmination of years of development and community testing. While the network is stable and continues to receive updates, it remains experimental and users may experience occasional instability or reduced performance.
    Compatible software versions for Mainnet Beta ​
    ',4),c=e('
    Testnets ​
    Celestia currently has two existing testnets that you can participate in:
    Arabica Devnet ​
    Arabica devnet is a devnet focused on developers who want to deploy sovereign rollups on the latest changes from Celestia's codebase. Arabica will be updated frequently and might be unstable at times given new updates. Validators won't be able to validate on Arabica as it is not designed for validators to participate.
    Compatible software versions for Arabica devnet ​
    ',5),l=e('
    Mocha testnet ​
    Mocha testnet is a testnet focused on enabling validators to test out their infrastructure by running nodes connected to the network. Developers can also deploy sovereign rollups on Mocha, it just will always be behind Arabica as Mocha upgrades are slower given they need to be done via hardforks in coordination with the validator community on Mocha.
    Compatible software versions for Mocha testnet ​
    ',3),h=e('
    Network upgrades ​
    There are a few ways to stay informed about network upgrades:
    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.
    ',4),A=JSON.parse('{"title":"Participate in the Celestia networks","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Participate in the Celestia networks | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/participate.md","filePath":"nodes/participate.md","lastUpdated":1725992025000}'),d={name:"nodes/participate.md"},P=Object.assign(d,{setup(p){return(m,f)=>(n(),i("div",null,[s,a(r),c,a(t),l,a(o),h]))}});export{A as __pageData,P as default};
diff --git a/pr-1699/assets/nodes_participate.md.cd0dcc78.lean.js b/pr-1699/assets/nodes_participate.md.704b27c3.lean.js
similarity index 93%
rename from pr-1699/assets/nodes_participate.md.cd0dcc78.lean.js
rename to pr-1699/assets/nodes_participate.md.704b27c3.lean.js
index 64f3164bee..83f60de6d7 100644
--- a/pr-1699/assets/nodes_participate.md.cd0dcc78.lean.js
+++ b/pr-1699/assets/nodes_participate.md.704b27c3.lean.js
@@ -1 +1 @@
-import{A as t}from"./chunks/ArabicaVersionTags.5d1acc99.js";import{M as o}from"./chunks/MochaVersionTags.743560ae.js";import{M as r}from"./chunks/MainnetVersionTags.eb9befca.js";import{o as n,c as i,H as a,Q as e}from"./chunks/framework.b47e54aa.js";import"./chunks/arabica_versions.1930378b.js";import"./chunks/constants.295fc0ab.js";import"./chunks/mocha_versions.7704b055.js";import"./chunks/mainnet_versions.1d5e6ed9.js";const s=e("",4),c=e("",5),l=e("",3),h=e("",4),A=JSON.parse('{"title":"Participate in the Celestia networks","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Participate in the Celestia networks | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/participate.md","filePath":"nodes/participate.md","lastUpdated":1725971357000}'),d={name:"nodes/participate.md"},P=Object.assign(d,{setup(p){return(m,f)=>(n(),i("div",null,[s,a(r),c,a(t),l,a(o),h]))}});export{A as __pageData,P as default};
+import{A as t}from"./chunks/ArabicaVersionTags.5d1acc99.js";import{M as o}from"./chunks/MochaVersionTags.743560ae.js";import{M as r}from"./chunks/MainnetVersionTags.eb9befca.js";import{o as n,c as i,H as a,Q as e}from"./chunks/framework.b47e54aa.js";import"./chunks/arabica_versions.1930378b.js";import"./chunks/constants.295fc0ab.js";import"./chunks/mocha_versions.7704b055.js";import"./chunks/mainnet_versions.1d5e6ed9.js";const s=e("",4),c=e("",5),l=e("",3),h=e("",4),A=JSON.parse('{"title":"Participate in the Celestia networks","description":"","frontmatter":{"head":[["meta",{"name":"og:title","content":"Participate in the Celestia networks | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/participate.md","filePath":"nodes/participate.md","lastUpdated":1725992025000}'),d={name:"nodes/participate.md"},P=Object.assign(d,{setup(p){return(m,f)=>(n(),i("div",null,[s,a(r),c,a(t),l,a(o),h]))}});export{A as __pageData,P as default};
diff --git a/pr-1699/assets/nodes_quick-start.md.7f0ce7b8.js b/pr-1699/assets/nodes_quick-start.md.9a9eabfc.js
similarity index 97%
rename from pr-1699/assets/nodes_quick-start.md.7f0ce7b8.js
rename to pr-1699/assets/nodes_quick-start.md.9a9eabfc.js
index 5fd7e0728d..a4aa8b5db6 100644
--- a/pr-1699/assets/nodes_quick-start.md.7f0ce7b8.js
+++ b/pr-1699/assets/nodes_quick-start.md.9a9eabfc.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Quick start guide","description":"Learn how to get started and run your first node on Celestia.","frontmatter":{"description":"Learn how to get started and run your first node on Celestia.","head":[["meta",{"name":"og:title","content":"Quick start guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/quick-start.md","filePath":"nodes/quick-start.md","lastUpdated":1725971357000}'),i={name:"nodes/quick-start.md"},n=o('
    Quick start guide ​
    In this section, we show you how to get started with installing the needed libraries and packages in Celestia to help you run a node on Celestia.
    Celestia Node ​
    Install celestia-node allows you to get started with running a light node and do data availability sampling.
    Light nodes are the best nodes to test out initially if you are new to participating in Celestia.
    celestia-node client also allows you to run other types of data availability (DA) nodes like bridge and full DA storage nodes, which will be covered in later sections.
    Celestia App ​
    Install celestia-app allows you to get started running a consensus node.
    celestia-app is the software that allows you to run validator nodes and also provide RPC endpoints.
    celestia-app covers the consensus layer, while celestia-node covers the DA layer.
    Getting started ​
    As covered in the previous section, Celestia offers two different test networks, Arabica devnet and Mocha testnet.
    If you are planning to run a light node, it is recommended to use Arabica, which you will find options to connecting to in the later sections.
    If you plan on running a validator, your only option is to run your node on Mocha.
    In this quick start guide, we will go over installing both of the software clients: celestia-node and celestia-app.
    NOTE
    If you just want to run a light node, you don't need to install celestia-app and can skip that part.
    Proceed to the next section in order to get started.
    ',17),s=[n];function r(l,d,c,p,u,h){return t(),a("div",null,s)}const _=e(i,[["render",r]]);export{f as __pageData,_ as default};
+import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Quick start guide","description":"Learn how to get started and run your first node on Celestia.","frontmatter":{"description":"Learn how to get started and run your first node on Celestia.","head":[["meta",{"name":"og:title","content":"Quick start guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/quick-start.md","filePath":"nodes/quick-start.md","lastUpdated":1725992025000}'),i={name:"nodes/quick-start.md"},n=o('
    Quick start guide ​
    In this section, we show you how to get started with installing the needed libraries and packages in Celestia to help you run a node on Celestia.
    Celestia Node ​
    Install celestia-node allows you to get started with running a light node and do data availability sampling.
    Light nodes are the best nodes to test out initially if you are new to participating in Celestia.
    celestia-node client also allows you to run other types of data availability (DA) nodes like bridge and full DA storage nodes, which will be covered in later sections.
    Celestia App ​
    Install celestia-app allows you to get started running a consensus node.
    celestia-app is the software that allows you to run validator nodes and also provide RPC endpoints.
    celestia-app covers the consensus layer, while celestia-node covers the DA layer.
    Getting started ​
    As covered in the previous section, Celestia offers two different test networks, Arabica devnet and Mocha testnet.
    If you are planning to run a light node, it is recommended to use Arabica, which you will find options to connecting to in the later sections.
    If you plan on running a validator, your only option is to run your node on Mocha.
    In this quick start guide, we will go over installing both of the software clients: celestia-node and celestia-app.
    NOTE
    If you just want to run a light node, you don't need to install celestia-app and can skip that part.
    Proceed to the next section in order to get started.
    ',17),s=[n];function r(l,d,c,p,u,h){return t(),a("div",null,s)}const _=e(i,[["render",r]]);export{f as __pageData,_ as default};
diff --git a/pr-1699/assets/nodes_quick-start.md.7f0ce7b8.lean.js b/pr-1699/assets/nodes_quick-start.md.9a9eabfc.lean.js
similarity index 90%
rename from pr-1699/assets/nodes_quick-start.md.7f0ce7b8.lean.js
rename to pr-1699/assets/nodes_quick-start.md.9a9eabfc.lean.js
index c1c2e5bf30..7988023e2c 100644
--- a/pr-1699/assets/nodes_quick-start.md.7f0ce7b8.lean.js
+++ b/pr-1699/assets/nodes_quick-start.md.9a9eabfc.lean.js
@@ -1 +1 @@
-import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Quick start guide","description":"Learn how to get started and run your first node on Celestia.","frontmatter":{"description":"Learn how to get started and run your first node on Celestia.","head":[["meta",{"name":"og:title","content":"Quick start guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/quick-start.md","filePath":"nodes/quick-start.md","lastUpdated":1725971357000}'),i={name:"nodes/quick-start.md"},n=o("",17),s=[n];function r(l,d,c,p,u,h){return t(),a("div",null,s)}const _=e(i,[["render",r]]);export{f as __pageData,_ as default};
+import{_ as e,o as t,c as a,Q as o}from"./chunks/framework.b47e54aa.js";const f=JSON.parse('{"title":"Quick start guide","description":"Learn how to get started and run your first node on Celestia.","frontmatter":{"description":"Learn how to get started and run your first node on Celestia.","head":[["meta",{"name":"og:title","content":"Quick start guide | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/quick-start.md","filePath":"nodes/quick-start.md","lastUpdated":1725992025000}'),i={name:"nodes/quick-start.md"},n=o("",17),s=[n];function r(l,d,c,p,u,h){return t(),a("div",null,s)}const _=e(i,[["render",r]]);export{f as __pageData,_ as default};
diff --git a/pr-1699/assets/nodes_systemd.md.794b3b4f.js b/pr-1699/assets/nodes_systemd.md.66ed5d05.js
similarity index 99%
rename from pr-1699/assets/nodes_systemd.md.794b3b4f.js
rename to pr-1699/assets/nodes_systemd.md.66ed5d05.js
index c14ec19b5e..283a2d9156 100644
--- a/pr-1699/assets/nodes_systemd.md.794b3b4f.js
+++ b/pr-1699/assets/nodes_systemd.md.66ed5d05.js
@@ -1,4 +1,4 @@
-import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Setting up your node as a background process with SystemD","description":"Learn how to setup your node as a background process with SystemD.","frontmatter":{"description":"Learn how to setup your node as a background process with SystemD.","head":[["meta",{"name":"og:title","content":"Setting up your node as a background process with SystemD | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/systemd.md","filePath":"nodes/systemd.md","lastUpdated":1725971357000}'),e={name:"nodes/systemd.md"},p=l(`
    Setting up your node as a background process with SystemD ​
    SystemD is a daemon service useful for running applications as background processes.
    Consensus nodes ​
    If you are running a validator or consensus node, here are the steps to setting up celestia-appd as a background process.
    Start the celestia-app with SystemD ​
    SystemD is a daemon service useful for running applications as background processes.
    Create Celestia-App systemd file:
    sh
    sudo tee <<EOF >/dev/null /etc/systemd/system/celestia-appd.service
+import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Setting up your node as a background process with SystemD","description":"Learn how to setup your node as a background process with SystemD.","frontmatter":{"description":"Learn how to setup your node as a background process with SystemD.","head":[["meta",{"name":"og:title","content":"Setting up your node as a background process with SystemD | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/systemd.md","filePath":"nodes/systemd.md","lastUpdated":1725992025000}'),e={name:"nodes/systemd.md"},p=l(`
    Setting up your node as a background process with SystemD ​
    SystemD is a daemon service useful for running applications as background processes.
    Consensus nodes ​
    If you are running a validator or consensus node, here are the steps to setting up celestia-appd as a background process.
    Start the celestia-app with SystemD ​
    SystemD is a daemon service useful for running applications as background processes.
    Create Celestia-App systemd file:
    sh
    sudo tee <<EOF >/dev/null /etc/systemd/system/celestia-appd.service
 [Unit]
 Description=celestia-appd Cosmos daemon
 After=network-online.target
diff --git a/pr-1699/assets/nodes_systemd.md.794b3b4f.lean.js b/pr-1699/assets/nodes_systemd.md.66ed5d05.lean.js
similarity index 91%
rename from pr-1699/assets/nodes_systemd.md.794b3b4f.lean.js
rename to pr-1699/assets/nodes_systemd.md.66ed5d05.lean.js
index 8dc46ef6f0..e6d4d18226 100644
--- a/pr-1699/assets/nodes_systemd.md.794b3b4f.lean.js
+++ b/pr-1699/assets/nodes_systemd.md.66ed5d05.lean.js
@@ -1 +1 @@
-import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Setting up your node as a background process with SystemD","description":"Learn how to setup your node as a background process with SystemD.","frontmatter":{"description":"Learn how to setup your node as a background process with SystemD.","head":[["meta",{"name":"og:title","content":"Setting up your node as a background process with SystemD | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/systemd.md","filePath":"nodes/systemd.md","lastUpdated":1725971357000}'),e={name:"nodes/systemd.md"},p=l("",52),o=[p];function t(c,r,i,y,d,E){return a(),n("div",null,o)}const u=s(e,[["render",t]]);export{h as __pageData,u as default};
+import{_ as s,o as a,c as n,Q as l}from"./chunks/framework.b47e54aa.js";const h=JSON.parse('{"title":"Setting up your node as a background process with SystemD","description":"Learn how to setup your node as a background process with SystemD.","frontmatter":{"description":"Learn how to setup your node as a background process with SystemD.","head":[["meta",{"name":"og:title","content":"Setting up your node as a background process with SystemD | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/systemd.md","filePath":"nodes/systemd.md","lastUpdated":1725992025000}'),e={name:"nodes/systemd.md"},p=l("",52),o=[p];function t(c,r,i,y,d,E){return a(),n("div",null,o)}const u=s(e,[["render",t]]);export{h as __pageData,u as default};
diff --git a/pr-1699/assets/nodes_validator-node.md.2b9abf8d.js b/pr-1699/assets/nodes_validator-node.md.084b1069.js
similarity index 97%
rename from pr-1699/assets/nodes_validator-node.md.2b9abf8d.js
rename to pr-1699/assets/nodes_validator-node.md.084b1069.js
index 504f453235..aa0d06a478 100644
--- a/pr-1699/assets/nodes_validator-node.md.2b9abf8d.js
+++ b/pr-1699/assets/nodes_validator-node.md.084b1069.js
@@ -22,7 +22,7 @@ import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,a
 raw_log: '[]'
 timestamp: ""
 tx: null
-txhash: <tx-hash>
    You can check if the TX hash went through using the block explorer by inputting the txhash ID that was returned.
    Optional: Deploy the celestia-node ​
    Running a bridge node is critical to the Celestia network as it enables the data availability and consensus nodes to communicate with one another. It is recommended to support the data availability network, but is not required for celestia-app.
    If you are not running a bridge node, you can skip to run a validator node.
    This section describes part 2 of Celestia validator node setup: running a Celestia bridge node daemon.
    Install celestia-node ​
    You can follow the tutorial for installing celestia-node
    Initialize the bridge node ​
    Run the following:
    bash
    celestia bridge init --core.ip <URI>
    celestia bridge init --core.ip <URI>
    TIP
    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.
    If you need a list of RPC endpoints to connect to, you can find the list on the Mocha testnet page or list on the Arabica devnet page.
    Run the bridge node ​
    Run the following:
    bash
    celestia bridge start
    celestia bridge start
    Optional: start the bridge node with SystemD ​
    Follow the tutorial on setting up the bridge node as a background process with SystemD.
    You have successfully set up a bridge node that is syncing with the network.
    Run the validator node ​
    If you are running celestia-app v1.x.x:
    sh
    celestia-appd start
    celestia-appd start
    If you are running celestia-app >= v2.0.0: then you'll want to start the node with a --v2-upgrade-height that is dependent on the network. The --v2-upgrade-height flag is only needed during the v2 upgrade height so after your node has executed the upgrade (e.g. you see the log upgraded from app version 1 to 2), you don't need to provide this flag for future celestia-appd start invocations.
    sh
    celestia-appd start --v2-upgrade-height 2371495
    celestia-appd start --v2-upgrade-height 2371495
    sh
    celestia-appd start --v2-upgrade-height 2585031
    celestia-appd start --v2-upgrade-height 2585031
    sh
    celestia-appd start --v2-upgrade-height 1751707
    celestia-appd start --v2-upgrade-height 1751707
    After completing all the necessary steps, you are now ready to run a validator! In order to create your validator onchain, follow the instructions below. Keep in mind that these steps are necessary ONLY if you want to participate in the consensus.
    Pick a moniker name of your choice! This is the validator name that will show up on public dashboards and explorers. VALIDATOR_WALLET must be the same you defined previously. Parameter --min-self-delegation=1000000 defines the amount of tokens that are self delegated from your validator wallet.
    Now, connect to the network of your choice.
    You have the following option of connecting to list of networks shown below:
    Continuing the validator tutorial, here are the steps to connect your validator to Mocha:
    `,30),I={class:"language-bash vp-adaptive-theme"},P=s("button",{title:"Copy Code",class:"copy"},null,-1),V=s("span",{class:"lang"},"bash",-1),R={class:"shiki github-dark vp-code-dark"},D=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"MONIKER"),s("span",{style:{color:"#F97583"}},"="),s("span",{style:{color:"#9ECBFF"}},'"your_moniker"')],-1),N=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"VALIDATOR_WALLET"),s("span",{style:{color:"#F97583"}},"="),s("span",{style:{color:"#9ECBFF"}},'"validator"')],-1),L=s("span",{class:"line"},null,-1),O=n('celestia-appd tx staking create-validator \\',1),z=n('    --amount=1000000utia \\',1),W=n('    --pubkey=$(celestia-appd tendermint show-validator) \\',1),M=n('    --moniker=$MONIKER \\',1),U={class:"line"},$=s("span",{style:{color:"#E1E4E8"}},"    ",-1),H={style:{color:"#79B8FF"}},Y=s("span",{style:{color:"#E1E4E8"}}," ",-1),K=s("span",{style:{color:"#79B8FF"}},"\\",-1),G=n('    --commission-rate=0.1 \\',1),J=n('    --commission-max-rate=0.2 \\',1),Q=n('    --commission-max-change-rate=0.01 \\',1),X=n('    --min-self-delegation=1000000 \\',1),j=n('    --from=$VALIDATOR_WALLET \\',1),Z=n('    --keyring-backend=test \\',1),ss=n('    --fees=21000utia \\',1),as=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"    "),s("span",{style:{color:"#79B8FF"}},"--gas=220000")],-1),ns={class:"shiki github-light vp-code-light"},es=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"MONIKER"),s("span",{style:{color:"#D73A49"}},"="),s("span",{style:{color:"#032F62"}},'"your_moniker"')],-1),os=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"VALIDATOR_WALLET"),s("span",{style:{color:"#D73A49"}},"="),s("span",{style:{color:"#032F62"}},'"validator"')],-1),ts=s("span",{class:"line"},null,-1),ls=n('celestia-appd tx staking create-validator \\',1),ps=n('    --amount=1000000utia \\',1),cs=n('    --pubkey=$(celestia-appd tendermint show-validator) \\',1),rs=n('    --moniker=$MONIKER \\',1),is={class:"line"},ds=s("span",{style:{color:"#24292E"}},"    ",-1),hs={style:{color:"#005CC5"}},us=s("span",{style:{color:"#24292E"}}," ",-1),_s=s("span",{style:{color:"#005CC5"}},"\\",-1),ys=n('    --commission-rate=0.1 \\',1),gs=n('    --commission-max-rate=0.2 \\',1),Es=n('    --commission-max-change-rate=0.01 \\',1),Cs=n('    --min-self-delegation=1000000 \\',1),ms=n('    --from=$VALIDATOR_WALLET \\',1),Fs=n('    --keyring-backend=test \\',1),bs=n('    --fees=21000utia \\',1),vs=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"    "),s("span",{style:{color:"#005CC5"}},"--gas=220000")],-1),Ts=n(`
    You will be prompted to confirm the transaction:
    console
    confirm transaction before signing and broadcasting [y/N]: y
    confirm transaction before signing and broadcasting [y/N]: y
    Inputting y should provide an output similar to:
    console
    code: 0
+txhash: <tx-hash>
    You can check if the TX hash went through using the block explorer by inputting the txhash ID that was returned.
    Optional: Deploy the celestia-node ​
    Running a bridge node is critical to the Celestia network as it enables the data availability and consensus nodes to communicate with one another. It is recommended to support the data availability network, but is not required for celestia-app.
    If you are not running a bridge node, you can skip to run a validator node.
    This section describes part 2 of Celestia validator node setup: running a Celestia bridge node daemon.
    Install celestia-node ​
    You can follow the tutorial for installing celestia-node
    Initialize the bridge node ​
    Run the following:
    bash
    celestia bridge init --core.ip <URI>
    celestia bridge init --core.ip <URI>
    TIP
    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.
    If you need a list of RPC endpoints to connect to, you can find the list on the Mocha testnet page or list on the Arabica devnet page.
    Run the bridge node ​
    Run the following:
    bash
    celestia bridge start
    celestia bridge start
    Optional: start the bridge node with SystemD ​
    Follow the tutorial on setting up the bridge node as a background process with SystemD.
    You have successfully set up a bridge node that is syncing with the network.
    Run the validator node ​
    If you are running celestia-app v1.x.x:
    sh
    celestia-appd start
    celestia-appd start
    If you are running celestia-app >= v2.0.0: then you'll want to start the node with a --v2-upgrade-height that is dependent on the network. The --v2-upgrade-height flag is only needed during the v2 upgrade height so after your node has executed the upgrade (e.g. you see the log upgraded from app version 1 to 2), you don't need to provide this flag for future celestia-appd start invocations.
    sh
    celestia-appd start --v2-upgrade-height 2371495
    celestia-appd start --v2-upgrade-height 2371495
    sh
    celestia-appd start --v2-upgrade-height 2585031
    celestia-appd start --v2-upgrade-height 2585031
    sh
    celestia-appd start --v2-upgrade-height 1751707
    celestia-appd start --v2-upgrade-height 1751707
    After completing all the necessary steps, you are now ready to run a validator! In order to create your validator onchain, follow the instructions below. Keep in mind that these steps are necessary ONLY if you want to participate in the consensus.
    Pick a moniker name of your choice! This is the validator name that will show up on public dashboards and explorers. VALIDATOR_WALLET must be the same you defined previously. Parameter --min-self-delegation=1000000 defines the amount of tokens that are self delegated from your validator wallet.
    Now, connect to the network of your choice.
    You have the following option of connecting to list of networks shown below:
    Continuing the validator tutorial, here are the steps to connect your validator to Mocha:
    `,30),I={class:"language-bash vp-adaptive-theme"},P=s("button",{title:"Copy Code",class:"copy"},null,-1),V=s("span",{class:"lang"},"bash",-1),R={class:"shiki github-dark vp-code-dark"},D=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"MONIKER"),s("span",{style:{color:"#F97583"}},"="),s("span",{style:{color:"#9ECBFF"}},'"your_moniker"')],-1),N=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"VALIDATOR_WALLET"),s("span",{style:{color:"#F97583"}},"="),s("span",{style:{color:"#9ECBFF"}},'"validator"')],-1),L=s("span",{class:"line"},null,-1),O=n('celestia-appd tx staking create-validator \\',1),W=n('    --amount=1000000utia \\',1),M=n('    --pubkey=$(celestia-appd tendermint show-validator) \\',1),z=n('    --moniker=$MONIKER \\',1),U={class:"line"},Y=s("span",{style:{color:"#E1E4E8"}},"    ",-1),$={style:{color:"#79B8FF"}},H=s("span",{style:{color:"#E1E4E8"}}," ",-1),K=s("span",{style:{color:"#79B8FF"}},"\\",-1),G=n('    --commission-rate=0.1 \\',1),J=n('    --commission-max-rate=0.2 \\',1),Q=n('    --commission-max-change-rate=0.01 \\',1),j=n('    --min-self-delegation=1000000 \\',1),X=n('    --from=$VALIDATOR_WALLET \\',1),Z=n('    --keyring-backend=test \\',1),ss=n('    --fees=21000utia \\',1),as=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"    "),s("span",{style:{color:"#79B8FF"}},"--gas=220000")],-1),ns={class:"shiki github-light vp-code-light"},es=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"MONIKER"),s("span",{style:{color:"#D73A49"}},"="),s("span",{style:{color:"#032F62"}},'"your_moniker"')],-1),os=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"VALIDATOR_WALLET"),s("span",{style:{color:"#D73A49"}},"="),s("span",{style:{color:"#032F62"}},'"validator"')],-1),ts=s("span",{class:"line"},null,-1),ls=n('celestia-appd tx staking create-validator \\',1),ps=n('    --amount=1000000utia \\',1),cs=n('    --pubkey=$(celestia-appd tendermint show-validator) \\',1),rs=n('    --moniker=$MONIKER \\',1),is={class:"line"},ds=s("span",{style:{color:"#24292E"}},"    ",-1),hs={style:{color:"#005CC5"}},us=s("span",{style:{color:"#24292E"}}," ",-1),_s=s("span",{style:{color:"#005CC5"}},"\\",-1),ys=n('    --commission-rate=0.1 \\',1),gs=n('    --commission-max-rate=0.2 \\',1),Es=n('    --commission-max-change-rate=0.01 \\',1),Cs=n('    --min-self-delegation=1000000 \\',1),ms=n('    --from=$VALIDATOR_WALLET \\',1),Fs=n('    --keyring-backend=test \\',1),bs=n('    --fees=21000utia \\',1),vs=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"    "),s("span",{style:{color:"#005CC5"}},"--gas=220000")],-1),Ts=n(`
    You will be prompted to confirm the transaction:
    console
    confirm transaction before signing and broadcasting [y/N]: y
    confirm transaction before signing and broadcasting [y/N]: y
    Inputting y should provide an output similar to:
    console
    code: 0
 codespace: ""
 data: ""
 gas_used: "0"
@@ -44,7 +44,7 @@ import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,a
 raw_log: '[]'
 timestamp: ""
 tx: null
-txhash: <tx-hash>
    You should now be able to see your validator from a block explorer
    Submit your validator information ​
    After starting your node, please submit your node as a seed and peer to the networks repository.
    Optional: Transaction indexer configuration options ​
    Follow the instructions under transaction indexer configuration options to configure your config.toml file to select which transactions to index.
    Additional resources ​
    For additional resources, refer to the extra resources for consensus nodessection of the consensus node page.
    FAQ ​
    +2/3 committed an invalid block: wrong Block.Header.Version ​
    If you encounter an error like:
    bash
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\\nruntime/debug.Stack()\\n\\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\\npanic({0x1b91180?, 0x400153b240?})\\n\\t/usr/local/go/src/runtime/panic.go:770 +0x124\\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\\n"
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\\nruntime/debug.Stack()\\n\\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\\npanic({0x1b91180?, 0x400153b240?})\\n\\t/usr/local/go/src/runtime/panic.go:770 +0x124\\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\\n"
    then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant --v2-upgrade-height for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a celestia-appd tendermint reset-state to reset your node and start syncing from the genesis block.
    `,16),qs=JSON.parse('{"title":"Setting up a Celestia validator node","description":"Learn how to set up a Celestia validator node.","frontmatter":{"description":"Learn how to set up a Celestia validator node.","outline":"deep","head":[["meta",{"name":"og:title","content":"Setting up a Celestia validator node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/validator-node.md","filePath":"nodes/validator-node.md","lastUpdated":1725971357000}'),ks={name:"nodes/validator-node.md"},ws=Object.assign(ks,{setup(fs){return(As,Ss)=>(l(),p("div",null,[r,s("div",i,[d,h,s("pre",u,[s("code",null,[_,a(`
+txhash: <tx-hash>
    You should now be able to see your validator from a block explorer
    Submit your validator information ​
    After starting your node, please submit your node as a seed and peer to the networks repository.
    Optional: Transaction indexer configuration options ​
    Follow the instructions under transaction indexer configuration options to configure your config.toml file to select which transactions to index.
    Additional resources ​
    For additional resources, refer to the extra resources for consensus nodessection of the consensus node page.
    FAQ ​
    +2/3 committed an invalid block: wrong Block.Header.Version ​
    If you encounter an error like:
    bash
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\\nruntime/debug.Stack()\\n\\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\\npanic({0x1b91180?, 0x400153b240?})\\n\\t/usr/local/go/src/runtime/panic.go:770 +0x124\\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\\n"
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\\nruntime/debug.Stack()\\n\\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\\npanic({0x1b91180?, 0x400153b240?})\\n\\t/usr/local/go/src/runtime/panic.go:770 +0x124\\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\\n\\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\\n"
    then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant --v2-upgrade-height for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a celestia-appd tendermint reset-state to reset your node and start syncing from the genesis block.
    `,16),qs=JSON.parse('{"title":"Setting up a Celestia validator node","description":"Learn how to set up a Celestia validator node.","frontmatter":{"description":"Learn how to set up a Celestia validator node.","outline":"deep","head":[["meta",{"name":"og:title","content":"Setting up a Celestia validator node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/validator-node.md","filePath":"nodes/validator-node.md","lastUpdated":1725992025000}'),ks={name:"nodes/validator-node.md"},ws=Object.assign(ks,{setup(fs){return(As,Ss)=>(l(),p("div",null,[r,s("div",i,[d,h,s("pre",u,[s("code",null,[_,a(`
 `),y,a(`
 `),s("span",g,[E,s("span",C,"--chain-id="+o(t(e).mochaChainId),1),m,F]),a(`
 `),b])]),s("pre",v,[s("code",null,[T,a(`
@@ -54,15 +54,15 @@ import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,a
 `),N,a(`
 `),L,a(`
 `),O,a(`
-`),z,a(`
 `),W,a(`
 `),M,a(`
-`),s("span",U,[$,s("span",H,"--chain-id="+o(t(e).mochaChainId),1),Y,K]),a(`
+`),z,a(`
+`),s("span",U,[Y,s("span",$,"--chain-id="+o(t(e).mochaChainId),1),H,K]),a(`
 `),G,a(`
 `),J,a(`
 `),Q,a(`
-`),X,a(`
 `),j,a(`
+`),X,a(`
 `),Z,a(`
 `),ss,a(`
 `),as])]),s("pre",ns,[s("code",null,[es,a(`
diff --git a/pr-1699/assets/nodes_validator-node.md.2b9abf8d.lean.js b/pr-1699/assets/nodes_validator-node.md.084b1069.lean.js
similarity index 90%
rename from pr-1699/assets/nodes_validator-node.md.2b9abf8d.lean.js
rename to pr-1699/assets/nodes_validator-node.md.084b1069.lean.js
index 0603544a24..eeee1502ec 100644
--- a/pr-1699/assets/nodes_validator-node.md.2b9abf8d.lean.js
+++ b/pr-1699/assets/nodes_validator-node.md.084b1069.lean.js
@@ -1,4 +1,4 @@
-import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,a,t as o,l as t,Q as n}from"./chunks/framework.b47e54aa.js";const c="/docs-preview/pr-1699/img/nodes/validator.png",r=n("",19),i={class:"language-bash vp-adaptive-theme"},d=s("button",{title:"Copy Code",class:"copy"},null,-1),h=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},_=n("",1),y=n("",1),g={class:"line"},E=s("span",{style:{color:"#E1E4E8"}},"--from=$VALIDATOR_WALLET ",-1),C={style:{color:"#79B8FF"}},m=s("span",{style:{color:"#E1E4E8"}}," ",-1),F=s("span",{style:{color:"#79B8FF"}},"\\",-1),b=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"--fees=21000utia")],-1),v={class:"shiki github-light vp-code-light"},T=n("",1),k=n("",1),f={class:"line"},A=s("span",{style:{color:"#24292E"}},"--from=$VALIDATOR_WALLET ",-1),S={style:{color:"#005CC5"}},B=s("span",{style:{color:"#24292E"}}," ",-1),x=s("span",{style:{color:"#005CC5"}},"\\",-1),q=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"--fees=21000utia")],-1),w=n("",30),I={class:"language-bash vp-adaptive-theme"},P=s("button",{title:"Copy Code",class:"copy"},null,-1),V=s("span",{class:"lang"},"bash",-1),R={class:"shiki github-dark vp-code-dark"},D=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"MONIKER"),s("span",{style:{color:"#F97583"}},"="),s("span",{style:{color:"#9ECBFF"}},'"your_moniker"')],-1),N=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"VALIDATOR_WALLET"),s("span",{style:{color:"#F97583"}},"="),s("span",{style:{color:"#9ECBFF"}},'"validator"')],-1),L=s("span",{class:"line"},null,-1),O=n("",1),z=n("",1),W=n("",1),M=n("",1),U={class:"line"},$=s("span",{style:{color:"#E1E4E8"}},"    ",-1),H={style:{color:"#79B8FF"}},Y=s("span",{style:{color:"#E1E4E8"}}," ",-1),K=s("span",{style:{color:"#79B8FF"}},"\\",-1),G=n("",1),J=n("",1),Q=n("",1),X=n("",1),j=n("",1),Z=n("",1),ss=n("",1),as=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"    "),s("span",{style:{color:"#79B8FF"}},"--gas=220000")],-1),ns={class:"shiki github-light vp-code-light"},es=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"MONIKER"),s("span",{style:{color:"#D73A49"}},"="),s("span",{style:{color:"#032F62"}},'"your_moniker"')],-1),os=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"VALIDATOR_WALLET"),s("span",{style:{color:"#D73A49"}},"="),s("span",{style:{color:"#032F62"}},'"validator"')],-1),ts=s("span",{class:"line"},null,-1),ls=n("",1),ps=n("",1),cs=n("",1),rs=n("",1),is={class:"line"},ds=s("span",{style:{color:"#24292E"}},"    ",-1),hs={style:{color:"#005CC5"}},us=s("span",{style:{color:"#24292E"}}," ",-1),_s=s("span",{style:{color:"#005CC5"}},"\\",-1),ys=n("",1),gs=n("",1),Es=n("",1),Cs=n("",1),ms=n("",1),Fs=n("",1),bs=n("",1),vs=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"    "),s("span",{style:{color:"#005CC5"}},"--gas=220000")],-1),Ts=n("",16),qs=JSON.parse('{"title":"Setting up a Celestia validator node","description":"Learn how to set up a Celestia validator node.","frontmatter":{"description":"Learn how to set up a Celestia validator node.","outline":"deep","head":[["meta",{"name":"og:title","content":"Setting up a Celestia validator node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/validator-node.md","filePath":"nodes/validator-node.md","lastUpdated":1725971357000}'),ks={name:"nodes/validator-node.md"},ws=Object.assign(ks,{setup(fs){return(As,Ss)=>(l(),p("div",null,[r,s("div",i,[d,h,s("pre",u,[s("code",null,[_,a(`
+import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,a,t as o,l as t,Q as n}from"./chunks/framework.b47e54aa.js";const c="/docs-preview/pr-1699/img/nodes/validator.png",r=n("",19),i={class:"language-bash vp-adaptive-theme"},d=s("button",{title:"Copy Code",class:"copy"},null,-1),h=s("span",{class:"lang"},"bash",-1),u={class:"shiki github-dark vp-code-dark"},_=n("",1),y=n("",1),g={class:"line"},E=s("span",{style:{color:"#E1E4E8"}},"--from=$VALIDATOR_WALLET ",-1),C={style:{color:"#79B8FF"}},m=s("span",{style:{color:"#E1E4E8"}}," ",-1),F=s("span",{style:{color:"#79B8FF"}},"\\",-1),b=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"--fees=21000utia")],-1),v={class:"shiki github-light vp-code-light"},T=n("",1),k=n("",1),f={class:"line"},A=s("span",{style:{color:"#24292E"}},"--from=$VALIDATOR_WALLET ",-1),S={style:{color:"#005CC5"}},B=s("span",{style:{color:"#24292E"}}," ",-1),x=s("span",{style:{color:"#005CC5"}},"\\",-1),q=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"--fees=21000utia")],-1),w=n("",30),I={class:"language-bash vp-adaptive-theme"},P=s("button",{title:"Copy Code",class:"copy"},null,-1),V=s("span",{class:"lang"},"bash",-1),R={class:"shiki github-dark vp-code-dark"},D=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"MONIKER"),s("span",{style:{color:"#F97583"}},"="),s("span",{style:{color:"#9ECBFF"}},'"your_moniker"')],-1),N=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"VALIDATOR_WALLET"),s("span",{style:{color:"#F97583"}},"="),s("span",{style:{color:"#9ECBFF"}},'"validator"')],-1),L=s("span",{class:"line"},null,-1),O=n("",1),W=n("",1),M=n("",1),z=n("",1),U={class:"line"},Y=s("span",{style:{color:"#E1E4E8"}},"    ",-1),$={style:{color:"#79B8FF"}},H=s("span",{style:{color:"#E1E4E8"}}," ",-1),K=s("span",{style:{color:"#79B8FF"}},"\\",-1),G=n("",1),J=n("",1),Q=n("",1),j=n("",1),X=n("",1),Z=n("",1),ss=n("",1),as=s("span",{class:"line"},[s("span",{style:{color:"#E1E4E8"}},"    "),s("span",{style:{color:"#79B8FF"}},"--gas=220000")],-1),ns={class:"shiki github-light vp-code-light"},es=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"MONIKER"),s("span",{style:{color:"#D73A49"}},"="),s("span",{style:{color:"#032F62"}},'"your_moniker"')],-1),os=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"VALIDATOR_WALLET"),s("span",{style:{color:"#D73A49"}},"="),s("span",{style:{color:"#032F62"}},'"validator"')],-1),ts=s("span",{class:"line"},null,-1),ls=n("",1),ps=n("",1),cs=n("",1),rs=n("",1),is={class:"line"},ds=s("span",{style:{color:"#24292E"}},"    ",-1),hs={style:{color:"#005CC5"}},us=s("span",{style:{color:"#24292E"}}," ",-1),_s=s("span",{style:{color:"#005CC5"}},"\\",-1),ys=n("",1),gs=n("",1),Es=n("",1),Cs=n("",1),ms=n("",1),Fs=n("",1),bs=n("",1),vs=s("span",{class:"line"},[s("span",{style:{color:"#24292E"}},"    "),s("span",{style:{color:"#005CC5"}},"--gas=220000")],-1),Ts=n("",16),qs=JSON.parse('{"title":"Setting up a Celestia validator node","description":"Learn how to set up a Celestia validator node.","frontmatter":{"description":"Learn how to set up a Celestia validator node.","outline":"deep","head":[["meta",{"name":"og:title","content":"Setting up a Celestia validator node | Celestia Docs"},{"name":"og:description","content":false}]]},"headers":[],"relativePath":"nodes/validator-node.md","filePath":"nodes/validator-node.md","lastUpdated":1725992025000}'),ks={name:"nodes/validator-node.md"},ws=Object.assign(ks,{setup(fs){return(As,Ss)=>(l(),p("div",null,[r,s("div",i,[d,h,s("pre",u,[s("code",null,[_,a(`
 `),y,a(`
 `),s("span",g,[E,s("span",C,"--chain-id="+o(t(e).mochaChainId),1),m,F]),a(`
 `),b])]),s("pre",v,[s("code",null,[T,a(`
@@ -8,15 +8,15 @@ import{c as e}from"./chunks/constants.295fc0ab.js";import{o as l,c as p,k as s,a
 `),N,a(`
 `),L,a(`
 `),O,a(`
-`),z,a(`
 `),W,a(`
 `),M,a(`
-`),s("span",U,[$,s("span",H,"--chain-id="+o(t(e).mochaChainId),1),Y,K]),a(`
+`),z,a(`
+`),s("span",U,[Y,s("span",$,"--chain-id="+o(t(e).mochaChainId),1),H,K]),a(`
 `),G,a(`
 `),J,a(`
 `),Q,a(`
-`),X,a(`
 `),j,a(`
+`),X,a(`
 `),Z,a(`
 `),ss,a(`
 `),as])]),s("pre",ns,[s("code",null,[es,a(`
diff --git a/pr-1699/community/calendar.html b/pr-1699/community/calendar.html
index 2dca2a4eaf..93217e7f9a 100644
--- a/pr-1699/community/calendar.html
+++ b/pr-1699/community/calendar.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -38,8 +38,8 @@
 
 
    Appearance
    Community calendar ​
    The Celestia community calendar is available for finding all the different community call events happening in Celestia's community.
    Add the community calendar to your personal calendar to stay updated with all the events.
    Explore past community call agendas, notes, and recordings for more insights.
    - +

    Community calendar ​

    The Celestia community calendar is available for finding all the different community call events happening in Celestia's community.

    Add the community calendar to your personal calendar to stay updated with all the events.

    Explore past community call agendas, notes, and recordings for more insights.

    + \ No newline at end of file diff --git a/pr-1699/community/coc.html b/pr-1699/community/coc.html index 7cb4873124..7e8a0529ca 100644 --- a/pr-1699/community/coc.html +++ b/pr-1699/community/coc.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    Celestia.org Code of Conduct ​

    Our Pledge ​

    We as Celestia.org members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

    We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

    Our Standards ​

    Examples of behavior that contributes to a positive environment for our community include:

    • Demonstrating empathy and kindness toward other people
    • Being respectful of differing opinions, viewpoints, and experiences
    • Giving and gracefully accepting constructive feedback
    • Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
    • Focusing on what is best not just for us as individuals, but for the overall community
    • Contributing to conversations about Celestia’s technology and ecosystem

    Examples of unacceptable behavior include:

    • The use of sexualized language or imagery, and sexual attention or advances of any kind
    • Trolling, insulting or derogatory comments, and personal or political attacks
    • Public or private harassment
    • Publishing others' private information, such as a physical or email address, without their explicit permission
    • Focusing on the prices of digital assets or tokens, or where they can be purchased
    • Other conduct which could reasonably be considered inappropriate in a professional setting

    Enforcement Responsibilities ​

    Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

    Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

    Scope ​

    This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

    Enforcement ​

    Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at Celestia.org Discord. All complaints will be reviewed and investigated promptly and fairly.

    All community leaders are obligated to respect the privacy and security of the reporter of any incident.

    Enforcement Guidelines ​

    Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

    1. Correction ​

    Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

    Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

    2. Warning ​

    Community Impact: A violation through a single incident or series of actions.

    Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

    3. Temporary Ban ​

    Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

    Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

    4. Permanent Ban ​

    Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

    Consequence: A permanent ban from any sort of public interaction within the community.

    Attribution ​

    This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

    Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.

    For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

    - +

    Celestia.org Code of Conduct ​

    Our Pledge ​

    We as Celestia.org members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

    We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

    Our Standards ​

    Examples of behavior that contributes to a positive environment for our community include:

    • Demonstrating empathy and kindness toward other people
    • Being respectful of differing opinions, viewpoints, and experiences
    • Giving and gracefully accepting constructive feedback
    • Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
    • Focusing on what is best not just for us as individuals, but for the overall community
    • Contributing to conversations about Celestia’s technology and ecosystem

    Examples of unacceptable behavior include:

    • The use of sexualized language or imagery, and sexual attention or advances of any kind
    • Trolling, insulting or derogatory comments, and personal or political attacks
    • Public or private harassment
    • Publishing others' private information, such as a physical or email address, without their explicit permission
    • Focusing on the prices of digital assets or tokens, or where they can be purchased
    • Other conduct which could reasonably be considered inappropriate in a professional setting

    Enforcement Responsibilities ​

    Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

    Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

    Scope ​

    This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

    Enforcement ​

    Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at Celestia.org Discord. All complaints will be reviewed and investigated promptly and fairly.

    All community leaders are obligated to respect the privacy and security of the reporter of any incident.

    Enforcement Guidelines ​

    Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

    1. Correction ​

    Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

    Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

    2. Warning ​

    Community Impact: A violation through a single incident or series of actions.

    Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

    3. Temporary Ban ​

    Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

    Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

    4. Permanent Ban ​

    Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

    Consequence: A permanent ban from any sort of public interaction within the community.

    Attribution ​

    This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

    Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.

    For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

    + \ No newline at end of file diff --git a/pr-1699/community/foundation-delegation-program.html b/pr-1699/community/foundation-delegation-program.html index 379670599c..92e61b6fdc 100644 --- a/pr-1699/community/foundation-delegation-program.html +++ b/pr-1699/community/foundation-delegation-program.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    The Celestia Foundation Delegation Program ​

    Delegation program banner

    Objectives of the program ​

    The primary objectives of the Celestia Foundation Delegation Program are:

    • To provide a fair opportunity for Celestia’s users to join the validator set, while ensuring the validator set remains proficient, trustworthy, and dependable.
    • To maintain network stability by promoting a steady transition of validators and avoiding sudden and disruptive changes in participation.
    • To enable the Celestia Foundation to use its stake towards its mission of fostering a modular blockchain network that delivers exceptional performance.

    Foundation delegation process ​

    Program launch ​

    Prospective validators are welcome to apply to the program starting February 6, 2024. The application is designed to assess a validator’s uptime performance and contributions to the Celestia ecosystem. Of the 100 total slots in Celestia’s active validator set, up to 50 will receive delegations within the program.

    Application submissions will be reviewed by the Celestia Foundation. More details about the application and eligibility criteria are described below.

    Cohort process ​

    cohort timeline

    Every 4 months, the Celestia Foundation will distribute a portion of the Foundation’s total available stake to a cohort of validators who meet certain criteria, detailed below. Here is an overview of how the cohort process will work for Cohort 1 and what that means for future cohorts.

    Key Points ​

    • Initial Cohort (Cohort 1): 50 applicants will be accepted
      • Grading System: Applicants in Cohort 1 are divided into first, second, and third place based eligibility criteria outlined in this document.
      • Delegation Duration: This varies based on the applicant’s placement in Cohort 1. First place receives 12 months of delegation, second place receives 8 months, third place receives 4 months.
    TierPlacementDelegation DurationRenewal By Cohort
    First PlaceApplicants 1-2012 monthsCohort 4
    Second PlaceApplicants 21-358 monthsCohort 3
    Third PlaceApplicants 36-504 monthsCohort 2
    • Subsequent Cohorts (Cohorts 2-onwards):
      • After Cohort 1, open slots may be filled by Cohort 1 members up for renewals or new applicants. There will be no Tiers (e.g. First Place, Second Place, Third Place) in cohorts after Cohort 1. This structure allows for a steady flow of both existing applicants and new applicants to maintain a stable set of participants in the program.

    During this period, so long as the validator maintains high uptime and does not violate the rules of the program, the validator will receive the delegation for the duration of the cohort they are currently in.

    Eligibility criteria ​

    The minimum requirements for participation in the program are as follows:

    • Run an active mainnet validator or an active Mocha testnet validator for at least 1 month before application deadline
    • Run a bridge node (on mainnet if you are already an active mainnet validator or on Mocha testnet if not) that is connected and reporting to the Celestia Labs OTEL collector (for new applicants - on testnet, so that we can evaluate performance)
    • Not jailed or slashed in the 6 months before application deadline
    • Not associated with an exchange or custodian
    • Not in the top 10 validators by delegation power, unless it enters the top 10 as a result of the Foundation’s delegation under this program
    • Have 10% or less commission
    • Not based within the US, within any country subject to economic sanctions, or within any other prohibited jurisdiction, and successfully complete a compliance screen
    • Dedicated email address so that the Foundation can reach you in the event of emergency upgrades and fixes
    • Maintain a fully archival (non pruned) bridge node for both Mainnet Beta and Mocha if selected for the program
    • Not running your infrastructure in Hetzner or OVH

    Not adhering to any of the criteria above will automatically disqualify your application, and violating any of the criteria after you have received delegation will result in withdrawal of the delegation. A participant who loses stake due to being jailed by the protocol may reapply to the program after 2 cohort periods.

    Applicants are also expected to have reviewed Celestia docs and recommended guides on devops and monitoring setups.

    Other optional but important criteria:

    • Develop and maintain developer tooling, services, applications, and dashboards
    • Work on projects aligned with Celestia's values
    • Contribute to documentation and new guides and tutorials
    • Quality of infrastructure
    • Operated within a location that improves geolocation of the validator set

    Undelegation criteria ​

    • Getting slashed/tombstoned (cannot apply for 1 year afterwards)
    • Getting jailed more than once during the cohort’s applicable delegation period
    • Violating the Celestia.org Community Code of Conduct or engaging in harmful activities towards the network
    • Failing to upgrade your node in a timely manner (24 hours or less)
    • If necessary to protect or secure Mainnet Beta or to comply with applicable law
    • For any other reason, in the Celestia Foundation’s sole discretion

    Application ​

    The program will be divided into cohorts with applications open for new applicants and renewal of existing applicants every 4 months. Validators will be delegated for up to a year. For each cohort, the deadline to apply/be evaluated (if you are reapplying) is exactly 1 month prior to the date of being delegated to.

    Application details ​

    Before applying, be ready to share the following:

    • General info
      • Security Email
      • Validator Entity Name
      • Discord ID
      • Mark if entity or individual
      • Website if any
      • Github page of your organization
      • Team experience and roster (including Twitter + Github links)
      • Which networks you validate on mainnet + links to your validators
      • A personal statement why you should receive delegation from the Foundation (max 1500 characters)
    • Infrastructure
      • Validator address and bridge node ID on MAINNET
      • If you don't run an active mainnet validator, please provide us with validator address, bridge node ID and blobstream address on Mocha-4
      • Have you been slashed or jailed in the last 6 months on Celestia or other chains you validated on.
      • Hosting provider and Data Center location (mainnet and testnet if applicable)
      • Setup of the 2 components (validator and bridge)
        • Hardware
        • Security setup (servers, private keys)
        • Monitoring and alerting
    • Contributions
      • Please list all technical contributions for Celestia and its ecosystem
      • Please list all community contributions for Celestia and its ecosystem

    Please note, the objective of the program is to contribute to Celestia’s resilience and uptime. If you contribute a lot to the Celestia ecosystem, but your validator uptime is low, this will negatively impact your chance at selection for the program. Furthermore, merely receiving delegation from the Foundation under the program does not guarantee your placement in the active validator set.

    Get Started with the Application Form

    Cohort information ​

    The Foundation will report each cohort’s composition and the duration of their respective delegations.

    • Cohort 1: 50 Validator Seats
    • Cohort 2: 15 Validator Seats (Applications open June 1, 2024)
    • Cohort 3: 15 Validator Seats (Applications open October 1, 2024)
    • Cohort 4: 20 Validator Seats (Applications open February 1, 2025)

    IMPORTANT: Each validator selected for the program has to maintain a fully archival (non pruned) bridge node for both Mainnet Beta and Mocha.

    Feedback process ​

    Validators in the program will receive a feedback form every quarter, so the program can be continually improved.

    - +

    The Celestia Foundation Delegation Program ​

    Delegation program banner

    Objectives of the program ​

    The primary objectives of the Celestia Foundation Delegation Program are:

    • To provide a fair opportunity for Celestia’s users to join the validator set, while ensuring the validator set remains proficient, trustworthy, and dependable.
    • To maintain network stability by promoting a steady transition of validators and avoiding sudden and disruptive changes in participation.
    • To enable the Celestia Foundation to use its stake towards its mission of fostering a modular blockchain network that delivers exceptional performance.

    Foundation delegation process ​

    Program launch ​

    Prospective validators are welcome to apply to the program starting February 6, 2024. The application is designed to assess a validator’s uptime performance and contributions to the Celestia ecosystem. Of the 100 total slots in Celestia’s active validator set, up to 50 will receive delegations within the program.

    Application submissions will be reviewed by the Celestia Foundation. More details about the application and eligibility criteria are described below.

    Cohort process ​

    cohort timeline

    Every 4 months, the Celestia Foundation will distribute a portion of the Foundation’s total available stake to a cohort of validators who meet certain criteria, detailed below. Here is an overview of how the cohort process will work for Cohort 1 and what that means for future cohorts.

    Key Points ​

    • Initial Cohort (Cohort 1): 50 applicants will be accepted
      • Grading System: Applicants in Cohort 1 are divided into first, second, and third place based eligibility criteria outlined in this document.
      • Delegation Duration: This varies based on the applicant’s placement in Cohort 1. First place receives 12 months of delegation, second place receives 8 months, third place receives 4 months.
    TierPlacementDelegation DurationRenewal By Cohort
    First PlaceApplicants 1-2012 monthsCohort 4
    Second PlaceApplicants 21-358 monthsCohort 3
    Third PlaceApplicants 36-504 monthsCohort 2
    • Subsequent Cohorts (Cohorts 2-onwards):
      • After Cohort 1, open slots may be filled by Cohort 1 members up for renewals or new applicants. There will be no Tiers (e.g. First Place, Second Place, Third Place) in cohorts after Cohort 1. This structure allows for a steady flow of both existing applicants and new applicants to maintain a stable set of participants in the program.

    During this period, so long as the validator maintains high uptime and does not violate the rules of the program, the validator will receive the delegation for the duration of the cohort they are currently in.

    Eligibility criteria ​

    The minimum requirements for participation in the program are as follows:

    • Run an active mainnet validator or an active Mocha testnet validator for at least 1 month before application deadline
    • Run a bridge node (on mainnet if you are already an active mainnet validator or on Mocha testnet if not) that is connected and reporting to the Celestia Labs OTEL collector (for new applicants - on testnet, so that we can evaluate performance)
    • Not jailed or slashed in the 6 months before application deadline
    • Not associated with an exchange or custodian
    • Not in the top 10 validators by delegation power, unless it enters the top 10 as a result of the Foundation’s delegation under this program
    • Have 10% or less commission
    • Not based within the US, within any country subject to economic sanctions, or within any other prohibited jurisdiction, and successfully complete a compliance screen
    • Dedicated email address so that the Foundation can reach you in the event of emergency upgrades and fixes
    • Maintain a fully archival (non pruned) bridge node for both Mainnet Beta and Mocha if selected for the program
    • Not running your infrastructure in Hetzner or OVH

    Not adhering to any of the criteria above will automatically disqualify your application, and violating any of the criteria after you have received delegation will result in withdrawal of the delegation. A participant who loses stake due to being jailed by the protocol may reapply to the program after 2 cohort periods.

    Applicants are also expected to have reviewed Celestia docs and recommended guides on devops and monitoring setups.

    Other optional but important criteria:

    • Develop and maintain developer tooling, services, applications, and dashboards
    • Work on projects aligned with Celestia's values
    • Contribute to documentation and new guides and tutorials
    • Quality of infrastructure
    • Operated within a location that improves geolocation of the validator set

    Undelegation criteria ​

    • Getting slashed/tombstoned (cannot apply for 1 year afterwards)
    • Getting jailed more than once during the cohort’s applicable delegation period
    • Violating the Celestia.org Community Code of Conduct or engaging in harmful activities towards the network
    • Failing to upgrade your node in a timely manner (24 hours or less)
    • If necessary to protect or secure Mainnet Beta or to comply with applicable law
    • For any other reason, in the Celestia Foundation’s sole discretion

    Application ​

    The program will be divided into cohorts with applications open for new applicants and renewal of existing applicants every 4 months. Validators will be delegated for up to a year. For each cohort, the deadline to apply/be evaluated (if you are reapplying) is exactly 1 month prior to the date of being delegated to.

    Application details ​

    Before applying, be ready to share the following:

    • General info
      • Security Email
      • Validator Entity Name
      • Discord ID
      • Mark if entity or individual
      • Website if any
      • Github page of your organization
      • Team experience and roster (including Twitter + Github links)
      • Which networks you validate on mainnet + links to your validators
      • A personal statement why you should receive delegation from the Foundation (max 1500 characters)
    • Infrastructure
      • Validator address and bridge node ID on MAINNET
      • If you don't run an active mainnet validator, please provide us with validator address, bridge node ID and blobstream address on Mocha-4
      • Have you been slashed or jailed in the last 6 months on Celestia or other chains you validated on.
      • Hosting provider and Data Center location (mainnet and testnet if applicable)
      • Setup of the 2 components (validator and bridge)
        • Hardware
        • Security setup (servers, private keys)
        • Monitoring and alerting
    • Contributions
      • Please list all technical contributions for Celestia and its ecosystem
      • Please list all community contributions for Celestia and its ecosystem

    Please note, the objective of the program is to contribute to Celestia’s resilience and uptime. If you contribute a lot to the Celestia ecosystem, but your validator uptime is low, this will negatively impact your chance at selection for the program. Furthermore, merely receiving delegation from the Foundation under the program does not guarantee your placement in the active validator set.

    Get Started with the Application Form

    Cohort information ​

    The Foundation will report each cohort’s composition and the duration of their respective delegations.

    • Cohort 1: 50 Validator Seats
    • Cohort 2: 15 Validator Seats (Applications open June 1, 2024)
    • Cohort 3: 15 Validator Seats (Applications open October 1, 2024)
    • Cohort 4: 20 Validator Seats (Applications open February 1, 2025)

    IMPORTANT: Each validator selected for the program has to maintain a fully archival (non pruned) bridge node for both Mainnet Beta and Mocha.

    Feedback process ​

    Validators in the program will receive a feedback form every quarter, so the program can be continually improved.

    + \ No newline at end of file diff --git a/pr-1699/community/itn-tos.html b/pr-1699/community/itn-tos.html index 4bdbbee063..023ddd75c3 100644 --- a/pr-1699/community/itn-tos.html +++ b/pr-1699/community/itn-tos.html @@ -11,7 +11,7 @@ - + @@ -39,7 +39,7 @@

    Appearance

    SUPPLEMENTAL INCENTIVIZED TESTNET TERMS ​

    Last Revised on 1/16/2023

    Welcome to the Supplemental Terms (these "ITN Award Program Terms" or "Terms") for the Incentivized Testnet Award Program (the "ITN Award Program" or the "Program") as operated on behalf of Strange Loop Labs AG ("Company", "we" or "us"). The ITN Award Program provides eligible users of a Testnet designated by the Company the opportunity to earn rewards, which may include Celestia tokens. These Terms are supplemental to, and incorporate by reference, the broader Celestia Terms of Service ("Services Terms") available at Celestia Terms of Service.

    Defined terms used but not defined herein have the meaning set forth in the Services Terms. The Program and your participation in it is a Service as defined under the Services Terms.

    These Terms govern your ability to participate in the Program and any awards you receive from that participation, which may include Celestia tokens ("ITN Rewards").

    Please read these Terms carefully, as they include important information about your legal rights. By participating in the Program or claiming ITN Rewards, you are agreeing to these Terms. If you do not understand or agree to these Terms, please do not participate in the Program or claim ITN Rewards.

    In order to participate in the Program you must provide certain information about you. Our collection of such information, your rights with respect to such collection, and other relevant information is described in the Celestia Privacy Policy available at Celestia Privacy Policy, and is supplemented by Section 3 of these Terms.

    The Program is a discretionary Service provided by the Company, pursuant to which the Company may, in its sole discretion, provide you ITN Rewards for your successful completion of certain tasks on a Testnet designated by the Company. Please note that any such Testnet itself (as well as any other Testnets or any mainnet deployment of the Celestia Protocol) is not a Service and does not constitute an element of the Services. We do not control the Celestia Protocol and accept no liability for its operation or its deployment in any testnet or mainnet environment.

    1. General Terms ​

    1.1 You must be eighteen (18) years of age or older and capable of forming a binding contract with the Company in order to participate in the Program or receive ITN Rewards.

    1.2 You agree and acknowledge that you (a) may receive ITN Rewards for free (other than applicable taxes, if any) from your participation in the Program, (b) were not previously promised ITN Rewards, unless pursuant to a separate written agreement, and (c) took no action in anticipation of or in reliance on receiving any ITN Rewards, unless pursuant to a separate written agreement.

    1.3 Your eligibility to participate in or receive ITN Rewards from the Program is subject to our sole discretion. The complete list of actions you must complete to earn ITN Rewards may not have been described in the documentation released by us from time to time, you may not receive ITN Rewards even if you successfully complete such actions, and no documentation related to the Program entitles you to any ITN Rewards or to participate in the Program.

    1.4 You agree and acknowledge that (a) you are not a Prohibited Person, (b) you are not a U.S. Person as defined in Rule 902(k) of Regulation S under the U.S. Securities Act of 1933, as amended (the "1933 Act" or "Act"), (c) you will not use a VPN or other tool to circumvent any geoblock or other restrictions that we may have implemented for participants in the Program, and (d) you are not participating in, and have not become eligible to participate in, the Program by receiving credentials from any other person or entity. Any circumvention or violation of the above will permanently disqualify you from participation in the Program.

    1.5 You agree and acknowledge that if you are unable to claim ITN Rewards due to technical bugs, gas fees, loss of access to a Wallet or the keys thereto, or for any other reason, you will have no recourse or claim against us or any other Company Entity and that neither we nor any other Company Entity will bear any liability.

    1.6 You agree and acknowledge that claiming an ITN Reward may require reliance on or an integration with third party products (e.g., a Wallet or an unaffiliated network or blockchain) that we do not control. In the event that you are unable to access such products or integrations, or if they fail for any reason, and you are unable to participate in the Program or claim ITN Rewards, you will have no recourse or claim against us or any other Company Entity and neither we nor any other Company Entity will bear any liability.

    1.7 The Company may share identifying information and documentation with certain vendors or third-party providers who provide such identity verification and sanctions and watchlist screening services (the "Third-Party Services"). You agree that your access and use of such Third-Party Services is governed solely by the terms and conditions of such Third-Party Services, and the Company is not responsible or liable for, and make no representations as to any aspect of such Third-Party Services, including, without limitation, their content or the manner in which they handle, protect, manage or process data or any interaction between you and the provider of such Third-Party Services. You irrevocably waive any claim against the Company with respect to such Third-Party Services. We are not liable for any damage or loss caused or alleged to be caused by or in connection with your enablement, access or use of any such Third-Party Services, or your reliance on the privacy practices, data security processes or other policies of such Third-Party Services.

    2. Taxes ​

    2.1 You are responsible for the payment of all taxes associated with your participation in the Program and your receipt of ITN Rewards. You agree to provide the Company with any additional information and complete any required tax or other forms relating to your receipt of ITN Rewards. You may suffer adverse tax consequences as a result of your participation in the Program or your receipt of ITN Rewards. You hereby represent that (a) you have consulted with a tax adviser that you deem advisable in connection with your participation, or that you have had the opportunity to obtain tax advice but have chosen not to do so, (b) the Company has not provided you with any tax advice with respect to your participation, and (c) you are not relying on the Company for any tax advice.

    3. Supplemental Privacy Information ​

    We may collect information to help us determine the reliability or uptime of your activities within the Program, including through the use of telemetry or metrics endpoints to collect and analyse such information, and link this information to a unique identifier to represent your activities within the Program. We may display all of the foregoing information on a public dashboard.

    Additionally, we may collect certain information about you from Third-Party Services and may combine information we receive from you with information we obtain from Third-Party Services, including but not limited to:

    • Transaction information. Information related to transactions in your Wallet, your Wallet address, activities performed using your Wallet, tokens received by your Wallet, or transactions initiated or completed.
    • Identification information. We collect your government identification (e.g., driver’s license, passport, etc.), proof of address, biometric information, and entity formation information if applicable. By agreeing to these Terms, you consent to our use of your biometric information, and understand and agree that our use of the biometric information is necessary for the performance of these Terms and the implementation of the Services.

    We collect this information to confirm your eligibility to participate in the Program and receive ITN Rewards, comply with our legal obligations, detect and prevent fraud, and to provide you with the Program.

    Any information we receive from third-party sources will be treated in accordance with the Celestia Privacy Policy, available at Celestia Privacy Policy. We are not responsible or liable for the accuracy of the information provided to us by third parties and are not responsible for any third party’s policies or practices. See Section 9 of the Celestia Privacy Policy for more information.

    4. Certain Additional Representations ​

    4.1 Receipt of Rewards Entirely for Own Account. Your eligibility to receive ITN Rewards is made in reliance upon your representation to the Company, which by your agreement to these Terms you hereby confirm, that any ITN Rewards you receive will be for your own account, not as a nominee or agent, and not with a view to the resale or distribution of any part thereof, and that you have no present intention of selling, granting any participation in, or otherwise distributing the same. By agreeing to these Terms, you further represent that you do not presently have any contract, undertaking, agreement or arrangement with any person to sell, transfer or grant participations to such person or to any third person, with respect to any ITN Rewards. If you are agreeing to these terms on behalf of an entity, that entity has not been formed for the specific purpose of obtaining the ITN Rewards.

    4.2 Disclosure of Information. Your eligibility to receive ITN Rewards is made in reliance upon your representation to the Company, which by your agreement to these Terms you hereby confirm, that you have sufficient knowledge of and experience in business and financial matters to be able to evaluate the risks and merits of your participation in the Program and of any ITN Rewards and are able to bear the risks thereof. You hereby affirm that you have not relied on any representations or warranties made by the Company related to the Program, including, but not limited to, conversations of any kind, whether through oral or electronic communication, or any white paper.

    4.3 Compliance with United States Securities Laws. You understand that the ITN Rewards have not been, and will not be, registered under the 1933 Act or any applicable state securities laws. You acknowledge that the availability of an exemption from the registration provisions of the Securities Act and other applicable state securities laws depends upon, among other things, the bona fide nature of your intent as described in Section 4.1 above and with respect to the accuracy of your representations as expressed throughout these Terms. You understand that the ITN Rewards may be deemed "restricted securities" under applicable United States federal and state securities laws and that, pursuant to these laws, you may be restricted from transferring any ITN Rewards unless they are registered with the Securities and Exchange Commission and qualified by state authorities, or an exemption from such registration and qualification requirements is available. You acknowledge that the Company does not undertake any obligation to register or qualify the ITN Rewards for resale, and exemptions from registration and qualification may not be available or may not permit you to transfer all or any of the ITN Rewards in the amounts or at the times proposed by you. You further acknowledge that if an exemption from registration or qualification is available, such exemption may be conditioned on various requirements including, but not limited to, the time and manner of sale, the holding period for the ITN Rewards, and on other factors outside of your control, for which the Company makes no assurances and may not be able to satisfy.

    4.4 Compliance with Liechtenstein Security Law. You understand that nothing in these Terms will be deemed to constitute a prospectus of any sort in Liechtenstein or in any jurisdiction in the EU; nor does it in any way pertain to a public offering or a solicitation of an offer to buy any securities in Liechtenstein or in any jurisdiction in the EU.

    4.5 No Public Market. You understand that no public market now exists for the ITN Rewards, and that the Company has not made any assurances that a public market will ever exist for the ITN Rewards.

    4.6 No Solicitation. At no time were you presented with or solicited by any publicly issued or circulated newspaper, mail, radio, television or other form of general advertising or solicitation in connection with any invitation to participate in the Program or offer of the ITN Rewards.

    4.7 Other Applicable Laws. You hereby represent that you have satisfied yourself as to the full observance of the laws of your jurisdiction in connection with any invitation to participate in the Program, receipt of ITN Awards, and other use of these Terms, including (a) the legal requirements within your jurisdiction for participating in the Program and receiving ITN Rewards, (b) any foreign exchange restrictions applicable to such participation or receipt, (c) any governmental or other consents that may need to be obtained, and (d) the income tax and other tax consequences, if any, that may be relevant to the receipt, holding, sale, or transfer of the ITN Rewards. Your participation in the Program and continued beneficial ownership of ITN Rewards will not violate any applicable securities or other laws of your jurisdiction.

    4.8 Non-US Transaction. You are not a U.S. Person as defined in Rule 902(k) of Regulation S under the 1933 Act. The offer of the ITN Rewards to you was made in an offshore transaction (as defined in Rule 902(h) of Regulation S), no directed selling efforts (as defined in Rule 902(c) of Regulation S) were made in the United States, and you are not obtaining the ITN Rewards for the account or benefit of any U.S. Person.

    4.9 Transfer Restrictions. You will not, during the Restricted Period (as defined below) offer or sell any of the ITN Rewards (or create or maintain any derivative position equivalent thereto) in the United States, to or for the account or benefit of a U.S. Person or other than in accordance with Regulation S. The Company reserves the right to impose additional transfer restrictions with respect to the ITN Rewards in its sole discretion.

    4.10 Subsequent Sales. You will, after the expiration of the applicable Restricted Period, only offer, sell, pledge or otherwise transfer the ITN Rewards (or create or maintain any derivative position equivalent thereto) pursuant to registration under the 1933 Act or any available exemption therefrom and, in any case, in accordance with applicable state securities laws.

    4.11 Legends. You acknowledge and agree that the ITN Rewards will be deemed to bear the following legends: (a) any legend required by the securities laws of any state or country to the extent such laws are applicable to the ITN Rewards represented by the certificate so legended, and (b): the following legend (and even without such legend the following restrictions apply):

    THE ITN REWARDS HAVE NOT BEEN REGISTERED UNDER THE ACT WITH THE UNITED STATES SECURITIES AND EXCHANGE COMMISSION, AND THE COMPANY DOES NOT INTEND TO REGISTER THEM. THE ITN REWARDS HAVE BEEN OBTAINED TO HOLD FOR THE LONG TERM AND NOT WITH A VIEW TO, OR IN CONNECTION WITH, THE SALE OR DISTRIBUTION THEREFOR. PRIOR TO THE ONE YEAR ANNIVERSARY FROM THE TERMINATION OF THE ITN REWARD PROGRAM (THE "PROGRAM COMPLETION DATE" AND SUCH ONE YEAR PERIOD, THE "RESTRICTED PERIOD"), THE ITN REWARDS MAY NOT BE OFFERED OR SOLD (INCLUDING OPENING A SHORT POSITION IN SUCH ITN REWARDS) IN THE UNITED STATES OR TO U.S. PERSONS AS DEFINED BY RULE 902(k) ADOPTED UNDER THE ACT, OTHER THAN TO DISTRIBUTORS, UNLESS THE ITN REWARDS ARE REGISTERED UNDER THE ACT, OR AN EXEMPTION FROM THE REGISTRATION REQUIREMENTS OF THE ACT IS AVAILABLE. RECIPIENTS OF ITN REWARDS PRIOR TO THE ONE YEAR ANNIVERSARY OF THE PROGRAM COMPLETION DATE MAY SELL SUCH ITN REWARDS ONLY PURSUANT TO AN EXEMPTION FROM REGISTRATION UNDER THE ACT OR OTHERWISE IN ACCORDANCE WITH THE PROVISIONS OF REGULATION S OF THE ACT, OR IN TRANSACTIONS EFFECTED OUTSIDE OF THE UNITED STATES PROVIDED THEY DO NOT SOLICIT (AND NO ONE ACTING ON THEIR BEHALF SOLICITS) PURCHASERS IN THE UNITED STATES OR OTHERWISE ENGAGE(S) IN SELLING EFFORTS IN THE UNITED STATES AND PROVIDED THAT HEDGING TRANSACTIONS INVOLVING THESE ITN REWARDS MAY NOT BE CONDUCTED UNLESS IN COMPLIANCE WITH THE ACT. A HOLDER OF THE ITN REWARDS WHO IS A DISTRIBUTOR, DEALER, SUB-UNDERWRITER OR OTHER SECURITIES PROFESSIONAL, IN ADDITION, CANNOT PRIOR TO THE ONE YEAR ANNIVERSARY OF THE PROGRAM COMPLETION DATE SELL THE ITN REWARDS TO A U.S. PERSON AS DEFINED BY RULE 902(k) OF REGULATION S UNLESS THE ITN REWARDS ARE REGISTERED UNDER THE ACT OR AN EXEMPTION FROM REGISTRATION UNDER THE ACT IS AVAILABLE.

    - + \ No newline at end of file diff --git a/pr-1699/community/modular-meetup-guide.html b/pr-1699/community/modular-meetup-guide.html index 0dc7702e24..20702e76ea 100644 --- a/pr-1699/community/modular-meetup-guide.html +++ b/pr-1699/community/modular-meetup-guide.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    Modular Meetup guide ​

    These are recommended steps you can follow that can help you organize a successful Modular Meetup. You aren’t required to follow the entire checklist but it is available to help aid you in your journey to organize a Modular Meetup.

    Before the Meetup ​

    1. Determine the meetup topic and objectives.
    2. Select a suitable date and time for the event.
    3. Secure a convenient and accessible venue that can accommodate the expected number of attendees.
    4. Finalize a schedule or agenda for the event, including speakers, presentations, and activities.
    5. Prepare and send out invitations to potential attendees using various channels (email, social media, community platforms, etc.).
    6. Create and share promotional materials (graphics, blog posts, etc.) to raise awareness about the meetup.
    7. Confirm speakers, including their availability, presentation topics, and technical requirements. If you are working from a Speaker List, please reach out to Nat for any support needed on coordination with speakers.
    8. Arrange any necessary equipment, such as microphones, projectors, and whiteboards.
    9. Plan and arrange refreshments, if applicable.
    10. Prepare and print any required materials, like agendas, name tags, and feedback forms.
    11. Coordinate with volunteers or team members to help manage the event.
    12. Set up a registration system or RSVP process to track attendance.
    13. Send out reminder messages to registered attendees prior to the event.
    14. Conduct a final review of the event logistics, including venue setup, equipment functionality, and volunteer roles.

    During the Meetup ​

    1. Set up the venue, including arranging seating, preparing equipment, and displaying any promotional materials.
    2. Designate a registration area and ensure that someone is available to greet and check-in attendees.
    3. Welcome the attendees and provide an overview of the event schedule.
    4. Introduce speakers and facilitate any presentations or discussions.
    5. Encourage networking and interaction among attendees during breaks or dedicated activities.
    6. Capture the event with photos or videos for future promotions and documentation.
    7. Collect feedback from attendees using forms, online surveys, or informal conversations if needed.

    After the Meetup ​

    1. Send follow-up messages to attendees, thanking them for their participation and soliciting additional feedback.
    2. Evaluate the success of the event by reviewing feedback and assessing key performance indicators (e.g., attendance, engagement, etc.).
    3. Analyze and document lessons learned, identifying areas for improvement in future meetups.
    4. Share event highlights, photos, and key takeaways with the community through social media, blog posts, or newsletters.
    5. Connect with speakers, attendees, and volunteers to maintain and strengthen relationships.
    6. Begin planning for the next meetup, applying insights gained from the previous event to enhance the experience for future attendees.

    Logistics and guidance ​

    These are provided guidelines for different components of kickstarting a Modular Meetup to help you get started on the logistics of organizing a meetup. A lot of those guidelines are thanks to the wonderful write ups in Ethereum Meetup Support Program and Elastic Community Organizer Guides.

    Venue ​

    Selecting the perfect venue for your Modular Meetup is essential in creating a welcoming atmosphere for the Celestia community.

    1. Startup Incubators
      • Often they would have spaces for meetups.
    2. Libraries
      • Libraries can normally have spaces for meetups at little to no costs
    3. Co-working spaces:
      • Co-working spaces might be able to offer necessary equipment like microphones, projectors, and whiteboards.
    4. Restaurants:
      • Restaurants might have private rooms for larger groups of people that you can book, depending on the restaurant.
    5. Universities and Blockchain Clubs:
      • Partnering with universities and their local university clubs can offer you a lot of spaces for meetups, as well as necessary equipments if needed for giving a talk.
    6. Other options:
      • If you're having difficulty finding a venue, don't hesitate to ask for help within the Celestia community. Your fellow organizers and attendees may have valuable suggestions or connections.

    An ideal venue should offer:

    • Sufficient seating for the audience
    • A projector and screen
    • A microphone (especially for meetups with 10+ attendees)
    • Optional: A whiteboard for speakers or workshops (not always necessary, but a nice addition)

    Consider recording the event, even with a smartphone, to share with the community later. If the speaker uses a microphone, their voice will be more audible in the video. We might be able to post those recordings of the meetup talks on a meetup youtube channel after.

    Remember to negotiate on costs and seek discounts, emphasizing that your meetup benefits the community.

    Collaborate with your venue provider to explore options like borrowing recording equipment, tripods, or even having them record the event for you. Some providers may offer these services for free or at a reduced cost.

    Catering and refreshments ​

    Providing refreshments or catering for your Modular Meetup enhances the overall experience and encourages networking among attendees.

    1. Determine your budget
      • Identify the amount you can allocate for food and drinks at your event which will help you determine how much you can bring in refreshments. You can also contact the Celestia Devrel team for ideas and support. Costs for refreshments and drinks can vary depending on your location, so be mindful to be flexible on your plans according to your specific location and budget.
    2. Offer a variety of refreshments
      • If you're ordering in, pizza and finger foods work well, but you can also have more budget-friendly options for food.
      • Offering drinks like beer, soda, or lemonade are great, but water also works. Keep in mind that not everyone drinks alcohol so it’s not a requirement. But having at least water and plastic cups works well.
    3. Plan ahead
      • Order refreshments 1 or 2 days in advance and schedule delivery to avoid last-minute stress during the event.

    By following these recommendations, you'll be able to provide enjoyable refreshments for your Celestia Modular Meetup attendees while fostering a friendly and engaging atmosphere.

    Audience ​

    Understanding your audience and estimating attendance are crucial for organizing successful Modular Meetups for Celestia.

    1. Research the local tech scene:
      • Investigate the types of meetups and events popular in your area. Attend other technology-focused events to get a sense of the audience size and interests. This information will help you tailor your meetup to attract a larger audience.
    2. Assess the availability of speakers:
      • Before organizing a meetup, ensure that you have access to a pool of knowledgeable speakers. If you anticipate difficulty in securing speakers, consider joining forces with an existing meetup group or speaking at other events before launching a new group. This approach will help spread the word about your planned Modular Meetup and gauge interest. Speakers are covered in the following section with a reference to Speaker List offered by the Modular Meetup program.
    3. Establish connections with other user groups:
      • Forge relationships with other tech-focused meetup groups to mutually promote each other's events, potentially increasing attendance.
    4. Set a regular routine for your meetup:
      • Communicate how often you plan to hold meetups, whether it's monthly or quarterly, to help attendees manage their expectations and maintain their interest.
    5. Organize casual meetups:
      • If there's a gap between more formal events, arrange casual meetups at pubs or cafes to keep people engaged and connect with potential speakers for future events.
    6. Estimate the number of attendees:
      • Consider factors such as the size of your city, the popularity of the topic, and the appeal of the event description when estimating attendance.

    Speakers ​

    Securing engaging and knowledgeable speakers is key to hosting an exceptional Celestia Modular Meetup.

    1. Define your event topic
      • Determine the theme of your event, focusing on areas such as DeFi, Gaming, NFTs, coding workshops, protocol changes, rollups, data availability, or other topics relevant to the Modular ecosystem. This will help you find speakers with expertise in the chosen subject.
    2. Utilize the Speaker List provided by the Modular Meetup program
      • As a meetup organizer, you have access to a curated list of talented speakers from Celestia Labs and the broader Modular ecosystem. This valuable resource can connect you with experts who can share their knowledge with your meetup attendees.
    3. Aim for multiple speakers
      • Ideally, invite 2-3 speakers to your event, allotting 20-40 minutes per talk. Schedule short breaks between presentations to maintain audience engagement.
    4. Organize the speaker lineup
      • Discuss the topics and slides with your speakers before the event to ensure a smooth flow. Arrange the talks in a logical order, saving the most impactful presentation for last.
    5. Invite local speakers
      • For your first meetup, consider presenting an introduction to the Celestia ecosystem or a specific area of interest. Encourage local experts or enthusiasts to speak at future meetups. This approach fosters community involvement and helps build a network of potential speakers.
    6. Seek speaker referrals
      • Ask your current speakers, attendees, or other meetup organizers for referrals. Personal connections often lead to discovering new speakers with valuable insights.
    7. Leverage your meetup discussion board
      • Post a call for speakers on your meetup discussion board to reach out to potential presenters within your community. Be clear about the event theme and requirements to attract relevant speakers.
    8. Offer incentives and appreciation
      • Reward speakers with tokens of gratitude, such as T-shirts, gifts, or public recognition, to show your appreciation for their contribution to the meetup. The Celestia Labs Devrel team can help with swag logistics if needed.

    Sponsors ​

    Finding sponsors for your meetup can be challenging, but securing financial support is crucial for covering costs related to venue and refreshments.

    1. Leverage Celestia Labs' support
      • Celestia Labs may offer co-sponsorship for your meetup. However, they also encourage organizers to find local co-sponsors to help cover costs and create a more sustainable event.
    2. Offer value to your sponsors:
      • Show potential sponsors how partnering with your event will benefit them. Include their logo on event banners, mention them in the event description, and give them a shoutout at the beginning of the event. If they desire, allow them to place a rollup banner at the venue.
    3. Reach out to your network
      • Ask friends and acquaintances if they know of coworking spaces, schools, universities, or companies interested in sponsorship. A personal connection can significantly increase the chances of securing support.
    4. Approach speakers for sponsorship
      • Request speakers or their affiliated projects to contribute towards the event's expenses, such as catering costs. This can be an effective way to obtain additional funding.
    5. Create a sponsorship deck
      • Develop a compelling sponsorship deck to pitch your event to tech companies in your city or potential online sponsors. This presentation should highlight the benefits of supporting your event and showcase past successful meetups.
    6. Research local companies
      • Investigate businesses in your area that may be interested in sponsoring your event. Tailor your pitch to align with their industry and demonstrate how the meetup can benefit their company.
    7. Engage sponsors during the event
      • Allow sponsors to briefly address the audience, participate in Q&A sessions, or mention their hiring needs. Remember to avoid sales pitches, as they can negatively impact the meetup experience.
    8. Thank your sponsors
      • Express gratitude to your sponsors at the beginning and end of the meetup. Acknowledging their support encourages continued collaboration and enhances the credibility of your event.

    Communications and marketing ​

    Effectively marketing and announcing your Modular Meetup is essential for attracting attendees and ensuring a successful event.

    1. Plan your announcement
      • Announce your meetup at least two weeks prior. This gives your audience ample time to prepare and increases the likelihood of their attendance.
    2. Utilize Celestia Labs' resources
      • Celestia Labs can help co-promote your meetup on social media and Discord. They can also add your event to their online calendar, email local contacts, and share the event via their Developer Relations Team on Twitter. Don't hesitate to reach out to them for assistance.
    3. Share on social media
      • Promote your event on Twitter and any other popular social media platforms in your area. Tag speakers, sponsors, and use relevant hashtags to increase visibility.
    4. Leverage local community groups
      • Post your event in local Telegram, Discord, or other community groups relevant to your city. These groups often have many members who may be interested in attending your event.
    5. Engage speakers and the venue
      • Maintain communication with speakers and the venue to ensure any changes can be announced in advance. Trust is critical, so avoid canceling planned meetups whenever possible.
    6. Send reminders via meetup.com (optional)
      • After announcing your event, send a warm invite to your meetup group members through meetup.com. Additionally, send a reminder email one day before the event to encourage attendance.
    7. Share with friends and family
      • Invite your friends, family, and acquaintances to the meetup, as they may help spread the word or know someone interested in the event.
    8. Utilize conference groups
      • If you've attended conferences, share your meetup in the associated Telegram or social media groups, as there may be members nearby who would be interested in attending.

    Recording ​

    Recording and live-streaming your Modular Meetup can greatly benefit those who cannot attend in person and expand the reach of your event.

    1. Plan for recording
      • Consider recording your meetup to create additional learning resources and share the knowledge with a broader audience.
    2. Consider live-streaming
      • Live-streaming your event on platforms like Twitch, YouTube, or Twitter allows remote participants to watch and engage in the meetup. This can also boost your event's reach and create a sense of inclusion for those who couldn't attend in person.
    3. Coordinate with Celestia Labs
      • Celestia Labs can potentially help cover recording costs and promote recorded meetups. Reach out to them at meetups@celestia.org to discuss available options and support. They can also assist with finding local contacts for recording if you don't have one already.
    4. Utilize available resources
      • If you have a small budget, consider allocating some funds for recording and live-streaming your event. Look for local professionals or affordable equipment rentals to ensure high-quality recordings.
    5. Share recordings on Celestia Labs' channels
      • Celestia Labs can help promote recorded meetups by sharing videos in their meetups playlist on YouTube and hosting them on their website. Ensure you coordinate with Celestia Labs to provide them with the recorded video.
    6. Promote recorded content
      • Share the recordings on your social media channels and meetup group after the event. This helps attendees revisit the content and allows those who couldn't attend to learn from the talks.

    Utilizing Meetup.com platform ​

    Celestia Labs is committed to supporting your meetup efforts by helping you with meetup.com, from setting up the group to covering organizer dues. Below is a detailed overview of how Celestia Labs can assist you.

    1. Meetup.com organizer dues
      • Celestia Labs is happy to cover organizer dues for meetup.com. To get started, send an email to meetups@celestia.org and let them help you with the process.
    2. Co-organizing existing groups
      • If you already have a meetup.com group but need Celestia Labs' assistance with organizing or covering dues, email meetups@celestia.org to add one of their employees as the Organizer.
    3. Setting up groups on Meetup.com
      • Celestia Labs will help you set up your meetup group, including logos, naming, custom URLs, group description, and other essential details. They provide a unique logo for Celestia Modular Meetups, which you can use for your group.
    4. User group naming
      • Celestia Labs recommends naming your group "Celestia Modular Meetup" to encompass various aspects of the Celestia community and create a consistent brand.
    5. Custom URL for the group
      • Meetup.com allows you to create a custom URL for your user group. Celestia Labs encourages consistent URLs across regions, making it easy for people to find your meetup group.
    6. Group description
      • Celestia Labs has a standard group description to ensure consistency across all meetups. However, if you'd like to customize it, let them know.
    7. New member intake questions
      • To improve the quality of your meetups, Celestia Labs suggests a set of intake questions for new members. The answers can help you better understand their needs and interests, allowing you to plan engaging meetups.
    8. Welcome message
      • Celestia Labs provides a welcome message for new members joining your group. If you'd like to customize this message, let them know.

    Onboarding questions for community members joining a Modular Meetup ​

    1. Q1: How did you hear about this Modular Meetup?
      • Why: This information helps us understand the most effective channels for recruiting new participants to the meetup.
    2. Q2: What do you hope to gain by participating in this meetup? (e.g., networking, learning about Celestia, learning about Modularity, finding a job, etc.)
      • Why: This information helps us cater to the needs of the user group members. If most attendees are looking for networking opportunities, we can schedule casual meetups alongside informative talks.
    3. Q3: Are you currently using or planning to use Celestia, Rollkit, Celestia’s Node API or any of the rollups deployed on Celestia? Tell us all about it. We will use your response to help us better understand what talks would be most beneficial to the group.
      • Why: Responses to this question help us determine the most relevant talks for the group members. If we discover that most participants are interested in a specific area, we can tailor the talks accordingly.
    4. Q4: We love Celestia and the modular ecosystem, but we also appreciate other Web3 technologies. What other topics would you like to hear about? (e.g., Infrastructure, Data Storage, DID, MEV)
      • Why: Knowing our group participants' interests in other technical areas helps us understand what related topics would be useful and valuable to the group, which in turn helps when recruiting speakers.
    5. Q5: Would you be interested in speaking at a future meetup? We welcome 2-minute lightning talks to 1-hour deep dives. Would you be interested in hosting a meetup? If you answer yes to this question, the group organizers will contact you to follow up.
      • Why: One of the challenges in hosting regular meetups is finding speakers. We hope this question will identify people eager to share their stories and expertise with the group, making the lives of organizers easier.
    - +

    Modular Meetup guide ​

    These are recommended steps you can follow that can help you organize a successful Modular Meetup. You aren’t required to follow the entire checklist but it is available to help aid you in your journey to organize a Modular Meetup.

    Before the Meetup ​

    1. Determine the meetup topic and objectives.
    2. Select a suitable date and time for the event.
    3. Secure a convenient and accessible venue that can accommodate the expected number of attendees.
    4. Finalize a schedule or agenda for the event, including speakers, presentations, and activities.
    5. Prepare and send out invitations to potential attendees using various channels (email, social media, community platforms, etc.).
    6. Create and share promotional materials (graphics, blog posts, etc.) to raise awareness about the meetup.
    7. Confirm speakers, including their availability, presentation topics, and technical requirements. If you are working from a Speaker List, please reach out to Nat for any support needed on coordination with speakers.
    8. Arrange any necessary equipment, such as microphones, projectors, and whiteboards.
    9. Plan and arrange refreshments, if applicable.
    10. Prepare and print any required materials, like agendas, name tags, and feedback forms.
    11. Coordinate with volunteers or team members to help manage the event.
    12. Set up a registration system or RSVP process to track attendance.
    13. Send out reminder messages to registered attendees prior to the event.
    14. Conduct a final review of the event logistics, including venue setup, equipment functionality, and volunteer roles.

    During the Meetup ​

    1. Set up the venue, including arranging seating, preparing equipment, and displaying any promotional materials.
    2. Designate a registration area and ensure that someone is available to greet and check-in attendees.
    3. Welcome the attendees and provide an overview of the event schedule.
    4. Introduce speakers and facilitate any presentations or discussions.
    5. Encourage networking and interaction among attendees during breaks or dedicated activities.
    6. Capture the event with photos or videos for future promotions and documentation.
    7. Collect feedback from attendees using forms, online surveys, or informal conversations if needed.

    After the Meetup ​

    1. Send follow-up messages to attendees, thanking them for their participation and soliciting additional feedback.
    2. Evaluate the success of the event by reviewing feedback and assessing key performance indicators (e.g., attendance, engagement, etc.).
    3. Analyze and document lessons learned, identifying areas for improvement in future meetups.
    4. Share event highlights, photos, and key takeaways with the community through social media, blog posts, or newsletters.
    5. Connect with speakers, attendees, and volunteers to maintain and strengthen relationships.
    6. Begin planning for the next meetup, applying insights gained from the previous event to enhance the experience for future attendees.

    Logistics and guidance ​

    These are provided guidelines for different components of kickstarting a Modular Meetup to help you get started on the logistics of organizing a meetup. A lot of those guidelines are thanks to the wonderful write ups in Ethereum Meetup Support Program and Elastic Community Organizer Guides.

    Venue ​

    Selecting the perfect venue for your Modular Meetup is essential in creating a welcoming atmosphere for the Celestia community.

    1. Startup Incubators
      • Often they would have spaces for meetups.
    2. Libraries
      • Libraries can normally have spaces for meetups at little to no costs
    3. Co-working spaces:
      • Co-working spaces might be able to offer necessary equipment like microphones, projectors, and whiteboards.
    4. Restaurants:
      • Restaurants might have private rooms for larger groups of people that you can book, depending on the restaurant.
    5. Universities and Blockchain Clubs:
      • Partnering with universities and their local university clubs can offer you a lot of spaces for meetups, as well as necessary equipments if needed for giving a talk.
    6. Other options:
      • If you're having difficulty finding a venue, don't hesitate to ask for help within the Celestia community. Your fellow organizers and attendees may have valuable suggestions or connections.

    An ideal venue should offer:

    • Sufficient seating for the audience
    • A projector and screen
    • A microphone (especially for meetups with 10+ attendees)
    • Optional: A whiteboard for speakers or workshops (not always necessary, but a nice addition)

    Consider recording the event, even with a smartphone, to share with the community later. If the speaker uses a microphone, their voice will be more audible in the video. We might be able to post those recordings of the meetup talks on a meetup youtube channel after.

    Remember to negotiate on costs and seek discounts, emphasizing that your meetup benefits the community.

    Collaborate with your venue provider to explore options like borrowing recording equipment, tripods, or even having them record the event for you. Some providers may offer these services for free or at a reduced cost.

    Catering and refreshments ​

    Providing refreshments or catering for your Modular Meetup enhances the overall experience and encourages networking among attendees.

    1. Determine your budget
      • Identify the amount you can allocate for food and drinks at your event which will help you determine how much you can bring in refreshments. You can also contact the Celestia Devrel team for ideas and support. Costs for refreshments and drinks can vary depending on your location, so be mindful to be flexible on your plans according to your specific location and budget.
    2. Offer a variety of refreshments
      • If you're ordering in, pizza and finger foods work well, but you can also have more budget-friendly options for food.
      • Offering drinks like beer, soda, or lemonade are great, but water also works. Keep in mind that not everyone drinks alcohol so it’s not a requirement. But having at least water and plastic cups works well.
    3. Plan ahead
      • Order refreshments 1 or 2 days in advance and schedule delivery to avoid last-minute stress during the event.

    By following these recommendations, you'll be able to provide enjoyable refreshments for your Celestia Modular Meetup attendees while fostering a friendly and engaging atmosphere.

    Audience ​

    Understanding your audience and estimating attendance are crucial for organizing successful Modular Meetups for Celestia.

    1. Research the local tech scene:
      • Investigate the types of meetups and events popular in your area. Attend other technology-focused events to get a sense of the audience size and interests. This information will help you tailor your meetup to attract a larger audience.
    2. Assess the availability of speakers:
      • Before organizing a meetup, ensure that you have access to a pool of knowledgeable speakers. If you anticipate difficulty in securing speakers, consider joining forces with an existing meetup group or speaking at other events before launching a new group. This approach will help spread the word about your planned Modular Meetup and gauge interest. Speakers are covered in the following section with a reference to Speaker List offered by the Modular Meetup program.
    3. Establish connections with other user groups:
      • Forge relationships with other tech-focused meetup groups to mutually promote each other's events, potentially increasing attendance.
    4. Set a regular routine for your meetup:
      • Communicate how often you plan to hold meetups, whether it's monthly or quarterly, to help attendees manage their expectations and maintain their interest.
    5. Organize casual meetups:
      • If there's a gap between more formal events, arrange casual meetups at pubs or cafes to keep people engaged and connect with potential speakers for future events.
    6. Estimate the number of attendees:
      • Consider factors such as the size of your city, the popularity of the topic, and the appeal of the event description when estimating attendance.

    Speakers ​

    Securing engaging and knowledgeable speakers is key to hosting an exceptional Celestia Modular Meetup.

    1. Define your event topic
      • Determine the theme of your event, focusing on areas such as DeFi, Gaming, NFTs, coding workshops, protocol changes, rollups, data availability, or other topics relevant to the Modular ecosystem. This will help you find speakers with expertise in the chosen subject.
    2. Utilize the Speaker List provided by the Modular Meetup program
      • As a meetup organizer, you have access to a curated list of talented speakers from Celestia Labs and the broader Modular ecosystem. This valuable resource can connect you with experts who can share their knowledge with your meetup attendees.
    3. Aim for multiple speakers
      • Ideally, invite 2-3 speakers to your event, allotting 20-40 minutes per talk. Schedule short breaks between presentations to maintain audience engagement.
    4. Organize the speaker lineup
      • Discuss the topics and slides with your speakers before the event to ensure a smooth flow. Arrange the talks in a logical order, saving the most impactful presentation for last.
    5. Invite local speakers
      • For your first meetup, consider presenting an introduction to the Celestia ecosystem or a specific area of interest. Encourage local experts or enthusiasts to speak at future meetups. This approach fosters community involvement and helps build a network of potential speakers.
    6. Seek speaker referrals
      • Ask your current speakers, attendees, or other meetup organizers for referrals. Personal connections often lead to discovering new speakers with valuable insights.
    7. Leverage your meetup discussion board
      • Post a call for speakers on your meetup discussion board to reach out to potential presenters within your community. Be clear about the event theme and requirements to attract relevant speakers.
    8. Offer incentives and appreciation
      • Reward speakers with tokens of gratitude, such as T-shirts, gifts, or public recognition, to show your appreciation for their contribution to the meetup. The Celestia Labs Devrel team can help with swag logistics if needed.

    Sponsors ​

    Finding sponsors for your meetup can be challenging, but securing financial support is crucial for covering costs related to venue and refreshments.

    1. Leverage Celestia Labs' support
      • Celestia Labs may offer co-sponsorship for your meetup. However, they also encourage organizers to find local co-sponsors to help cover costs and create a more sustainable event.
    2. Offer value to your sponsors:
      • Show potential sponsors how partnering with your event will benefit them. Include their logo on event banners, mention them in the event description, and give them a shoutout at the beginning of the event. If they desire, allow them to place a rollup banner at the venue.
    3. Reach out to your network
      • Ask friends and acquaintances if they know of coworking spaces, schools, universities, or companies interested in sponsorship. A personal connection can significantly increase the chances of securing support.
    4. Approach speakers for sponsorship
      • Request speakers or their affiliated projects to contribute towards the event's expenses, such as catering costs. This can be an effective way to obtain additional funding.
    5. Create a sponsorship deck
      • Develop a compelling sponsorship deck to pitch your event to tech companies in your city or potential online sponsors. This presentation should highlight the benefits of supporting your event and showcase past successful meetups.
    6. Research local companies
      • Investigate businesses in your area that may be interested in sponsoring your event. Tailor your pitch to align with their industry and demonstrate how the meetup can benefit their company.
    7. Engage sponsors during the event
      • Allow sponsors to briefly address the audience, participate in Q&A sessions, or mention their hiring needs. Remember to avoid sales pitches, as they can negatively impact the meetup experience.
    8. Thank your sponsors
      • Express gratitude to your sponsors at the beginning and end of the meetup. Acknowledging their support encourages continued collaboration and enhances the credibility of your event.

    Communications and marketing ​

    Effectively marketing and announcing your Modular Meetup is essential for attracting attendees and ensuring a successful event.

    1. Plan your announcement
      • Announce your meetup at least two weeks prior. This gives your audience ample time to prepare and increases the likelihood of their attendance.
    2. Utilize Celestia Labs' resources
      • Celestia Labs can help co-promote your meetup on social media and Discord. They can also add your event to their online calendar, email local contacts, and share the event via their Developer Relations Team on Twitter. Don't hesitate to reach out to them for assistance.
    3. Share on social media
      • Promote your event on Twitter and any other popular social media platforms in your area. Tag speakers, sponsors, and use relevant hashtags to increase visibility.
    4. Leverage local community groups
      • Post your event in local Telegram, Discord, or other community groups relevant to your city. These groups often have many members who may be interested in attending your event.
    5. Engage speakers and the venue
      • Maintain communication with speakers and the venue to ensure any changes can be announced in advance. Trust is critical, so avoid canceling planned meetups whenever possible.
    6. Send reminders via meetup.com (optional)
      • After announcing your event, send a warm invite to your meetup group members through meetup.com. Additionally, send a reminder email one day before the event to encourage attendance.
    7. Share with friends and family
      • Invite your friends, family, and acquaintances to the meetup, as they may help spread the word or know someone interested in the event.
    8. Utilize conference groups
      • If you've attended conferences, share your meetup in the associated Telegram or social media groups, as there may be members nearby who would be interested in attending.

    Recording ​

    Recording and live-streaming your Modular Meetup can greatly benefit those who cannot attend in person and expand the reach of your event.

    1. Plan for recording
      • Consider recording your meetup to create additional learning resources and share the knowledge with a broader audience.
    2. Consider live-streaming
      • Live-streaming your event on platforms like Twitch, YouTube, or Twitter allows remote participants to watch and engage in the meetup. This can also boost your event's reach and create a sense of inclusion for those who couldn't attend in person.
    3. Coordinate with Celestia Labs
      • Celestia Labs can potentially help cover recording costs and promote recorded meetups. Reach out to them at meetups@celestia.org to discuss available options and support. They can also assist with finding local contacts for recording if you don't have one already.
    4. Utilize available resources
      • If you have a small budget, consider allocating some funds for recording and live-streaming your event. Look for local professionals or affordable equipment rentals to ensure high-quality recordings.
    5. Share recordings on Celestia Labs' channels
      • Celestia Labs can help promote recorded meetups by sharing videos in their meetups playlist on YouTube and hosting them on their website. Ensure you coordinate with Celestia Labs to provide them with the recorded video.
    6. Promote recorded content
      • Share the recordings on your social media channels and meetup group after the event. This helps attendees revisit the content and allows those who couldn't attend to learn from the talks.

    Utilizing Meetup.com platform ​

    Celestia Labs is committed to supporting your meetup efforts by helping you with meetup.com, from setting up the group to covering organizer dues. Below is a detailed overview of how Celestia Labs can assist you.

    1. Meetup.com organizer dues
      • Celestia Labs is happy to cover organizer dues for meetup.com. To get started, send an email to meetups@celestia.org and let them help you with the process.
    2. Co-organizing existing groups
      • If you already have a meetup.com group but need Celestia Labs' assistance with organizing or covering dues, email meetups@celestia.org to add one of their employees as the Organizer.
    3. Setting up groups on Meetup.com
      • Celestia Labs will help you set up your meetup group, including logos, naming, custom URLs, group description, and other essential details. They provide a unique logo for Celestia Modular Meetups, which you can use for your group.
    4. User group naming
      • Celestia Labs recommends naming your group "Celestia Modular Meetup" to encompass various aspects of the Celestia community and create a consistent brand.
    5. Custom URL for the group
      • Meetup.com allows you to create a custom URL for your user group. Celestia Labs encourages consistent URLs across regions, making it easy for people to find your meetup group.
    6. Group description
      • Celestia Labs has a standard group description to ensure consistency across all meetups. However, if you'd like to customize it, let them know.
    7. New member intake questions
      • To improve the quality of your meetups, Celestia Labs suggests a set of intake questions for new members. The answers can help you better understand their needs and interests, allowing you to plan engaging meetups.
    8. Welcome message
      • Celestia Labs provides a welcome message for new members joining your group. If you'd like to customize this message, let them know.

    Onboarding questions for community members joining a Modular Meetup ​

    1. Q1: How did you hear about this Modular Meetup?
      • Why: This information helps us understand the most effective channels for recruiting new participants to the meetup.
    2. Q2: What do you hope to gain by participating in this meetup? (e.g., networking, learning about Celestia, learning about Modularity, finding a job, etc.)
      • Why: This information helps us cater to the needs of the user group members. If most attendees are looking for networking opportunities, we can schedule casual meetups alongside informative talks.
    3. Q3: Are you currently using or planning to use Celestia, Rollkit, Celestia’s Node API or any of the rollups deployed on Celestia? Tell us all about it. We will use your response to help us better understand what talks would be most beneficial to the group.
      • Why: Responses to this question help us determine the most relevant talks for the group members. If we discover that most participants are interested in a specific area, we can tailor the talks accordingly.
    4. Q4: We love Celestia and the modular ecosystem, but we also appreciate other Web3 technologies. What other topics would you like to hear about? (e.g., Infrastructure, Data Storage, DID, MEV)
      • Why: Knowing our group participants' interests in other technical areas helps us understand what related topics would be useful and valuable to the group, which in turn helps when recruiting speakers.
    5. Q5: Would you be interested in speaking at a future meetup? We welcome 2-minute lightning talks to 1-hour deep dives. Would you be interested in hosting a meetup? If you answer yes to this question, the group organizers will contact you to follow up.
      • Why: One of the challenges in hosting regular meetups is finding speakers. We hope this question will identify people eager to share their stories and expertise with the group, making the lives of organizers easier.
    + \ No newline at end of file diff --git a/pr-1699/community/modular-meetup-intro.html b/pr-1699/community/modular-meetup-intro.html index e6c5dfb4b9..9f797369ee 100644 --- a/pr-1699/community/modular-meetup-intro.html +++ b/pr-1699/community/modular-meetup-intro.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    Celestia Modular Meetup program ​

    Modular Meetup Banner

    Welcome to the ultimate guide for Modular Meetup organizers! This collection of resources is designed for those enthusiastic about fostering grassroots Modular Meetups with support from Celestia around the world.

    Program description ​

    The Celestia Modular Meetup Program aims to empower meetup organizers, providing education and support, and encouraging collaboration within the Web3 ecosystem. This rapidly growing community has already achieved incredible success with the first Modular Meetup in Lisbon, and will grow from there.

    Join fellow enthusiasts, engage in enlightening discussions, and make the most of the insightful resources provided. These resources are designed to serve as a go-to playbook for meetup organizers, especially when starting your journey.

    Important info ​

    Celestia.org Community Code of Conduct ​

    The purpose of our Community Code of Conduct is to foster an inclusive, welcoming, and supportive environment for everyone participating in Celestia community events. We're all here to learn from each other, expand our skillsets, and enjoy a positive experience together.

    All meetup attendees, speakers, sponsors, and volunteers, including the event organizing team, are kindly asked to adhere to the following Code of Conduct. Organizers will respectfully enforce this code throughout the event. We genuinely appreciate the cooperation of all participants in maintaining a safe and empowering space for everyone.

    Signup form ​

    To become part of the program, please complete the registration form.

    Following the review and approval of your submission, you will receive an email confirmation and an invitation to participate in the upcoming Modular Meetup call. Furthermore, you will be granted access to the exclusive Discord channel labeled "#modular-meetup" on our Discord server. Please take note that joining our Discord is a prerequisite for channel access. It's essential to recognize that this program is tailored for dedicated organizers with a genuine interest in nurturing their local modular ecosystem community.

    Emails ​

    As a participant in the Celestia Modular Meetup Program, you can expect to receive the following emails:

    1. Welcome email with links to calendar events and Discord channel
    2. Monthly Catch-up call invites
    3. Recap emails with notes from calls

    Discord ​

    Your active participation is key to unlocking the full potential of this vibrant community. Our primary communication tool is Discord, providing an engaging platform to connect with fellow organizers:

    Materials ​

    As a meetup organizer, you'll gain access to the Celestia Modular Meetup Program's list of resources. This collection should become your trusted companion in organizing events. Drawing upon the wisdom of seasoned event organizers, this resource is available for you and your co-organizers to explore and learn.

    - +

    Celestia Modular Meetup program ​

    Modular Meetup Banner

    Welcome to the ultimate guide for Modular Meetup organizers! This collection of resources is designed for those enthusiastic about fostering grassroots Modular Meetups with support from Celestia around the world.

    Program description ​

    The Celestia Modular Meetup Program aims to empower meetup organizers, providing education and support, and encouraging collaboration within the Web3 ecosystem. This rapidly growing community has already achieved incredible success with the first Modular Meetup in Lisbon, and will grow from there.

    Join fellow enthusiasts, engage in enlightening discussions, and make the most of the insightful resources provided. These resources are designed to serve as a go-to playbook for meetup organizers, especially when starting your journey.

    Important info ​

    Celestia.org Community Code of Conduct ​

    The purpose of our Community Code of Conduct is to foster an inclusive, welcoming, and supportive environment for everyone participating in Celestia community events. We're all here to learn from each other, expand our skillsets, and enjoy a positive experience together.

    All meetup attendees, speakers, sponsors, and volunteers, including the event organizing team, are kindly asked to adhere to the following Code of Conduct. Organizers will respectfully enforce this code throughout the event. We genuinely appreciate the cooperation of all participants in maintaining a safe and empowering space for everyone.

    Signup form ​

    To become part of the program, please complete the registration form.

    Following the review and approval of your submission, you will receive an email confirmation and an invitation to participate in the upcoming Modular Meetup call. Furthermore, you will be granted access to the exclusive Discord channel labeled "#modular-meetup" on our Discord server. Please take note that joining our Discord is a prerequisite for channel access. It's essential to recognize that this program is tailored for dedicated organizers with a genuine interest in nurturing their local modular ecosystem community.

    Emails ​

    As a participant in the Celestia Modular Meetup Program, you can expect to receive the following emails:

    1. Welcome email with links to calendar events and Discord channel
    2. Monthly Catch-up call invites
    3. Recap emails with notes from calls

    Discord ​

    Your active participation is key to unlocking the full potential of this vibrant community. Our primary communication tool is Discord, providing an engaging platform to connect with fellow organizers:

    Materials ​

    As a meetup organizer, you'll gain access to the Celestia Modular Meetup Program's list of resources. This collection should become your trusted companion in organizing events. Drawing upon the wisdom of seasoned event organizers, this resource is available for you and your co-organizers to explore and learn.

    + \ No newline at end of file diff --git a/pr-1699/community/modular-meetup-toolkit.html b/pr-1699/community/modular-meetup-toolkit.html index 00541a74c4..061639dfd4 100644 --- a/pr-1699/community/modular-meetup-toolkit.html +++ b/pr-1699/community/modular-meetup-toolkit.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    Modular Meetup Toolkit ​

    Welcome to the Modular Meetups Toolkit! This kit is designed to help you run successful meetups for the Celestia community. As the first modular blockchain, Celestia offers a lot to discuss and explore. This kit includes useful resources and materials to help you plan and execute your meetups effectively.

    Celestia branding guidelines ​

    • Brand kit
      1. Includes logo files, color schemes, typography, icons and illustrations

    Sample “Introduction to Modularity” workshop presentation ​

    • Sample presentation - introduction to modularity
    • Summary: This is an overview presentation on Modular blockchains and dives deep into Celestia core technologies.
    • The sample presentation covers:
      1. What are modular blockchains?
      2. The benefits of modular over monolithic blockchains
      3. Introduction to Celestia: The first modular blockchain
      4. The concept of Data Availability Sampling
      5. Sovereign Rollups
      6. Q&A session

    Sample “Run a Celestia light node” workshop presentation ​

    • Sample presentation - run a light node
    • Summary: This is an overview presentation goes over running a Celestia light node. You can find existing video presentations for this here:
    • The sample presentation covers:
      1. What is a Celestia light node?
      2. The role of light nodes in the Celestia ecosystem
      3. Setting up a light node: hardware and software requirements
      4. Step-by-step guide on how to run a Celestia light node
      5. Troubleshooting common issues
      6. Best practices for maintaining a light node
      7. Q&A session

    Sample “Deploy a Sovereign Rollup” workshop presentation ​

    • Sample presentation - deploy a sovereign rollup
    • Summary: This is an overview presentation on deploying a sovereign rollup with Rollkit on Celestia. You can find existing video presentations for this here:
    • The sample presentation covers:
      1. What is a sovereign rollup?
      2. The role of sovereign rollups in the Celestia ecosystem
      3. Introduction to Rollkit
      4. Setting up a sovereign rollup: hardware and software requirements
      5. Q&A session

    Sample “Modular Meetup Introduction” workshop presentation ​

    Swag logistics ​

    With this Modular Meetups Organizer Kit, you’ll have everything you need to plan and execute engaging, informative, and successful meetups for the Celestia community. Happy organizing!

    - +

    Modular Meetup Toolkit ​

    Welcome to the Modular Meetups Toolkit! This kit is designed to help you run successful meetups for the Celestia community. As the first modular blockchain, Celestia offers a lot to discuss and explore. This kit includes useful resources and materials to help you plan and execute your meetups effectively.

    Celestia branding guidelines ​

    • Brand kit
      1. Includes logo files, color schemes, typography, icons and illustrations

    Sample “Introduction to Modularity” workshop presentation ​

    • Sample presentation - introduction to modularity
    • Summary: This is an overview presentation on Modular blockchains and dives deep into Celestia core technologies.
    • The sample presentation covers:
      1. What are modular blockchains?
      2. The benefits of modular over monolithic blockchains
      3. Introduction to Celestia: The first modular blockchain
      4. The concept of Data Availability Sampling
      5. Sovereign Rollups
      6. Q&A session

    Sample “Run a Celestia light node” workshop presentation ​

    • Sample presentation - run a light node
    • Summary: This is an overview presentation goes over running a Celestia light node. You can find existing video presentations for this here:
    • The sample presentation covers:
      1. What is a Celestia light node?
      2. The role of light nodes in the Celestia ecosystem
      3. Setting up a light node: hardware and software requirements
      4. Step-by-step guide on how to run a Celestia light node
      5. Troubleshooting common issues
      6. Best practices for maintaining a light node
      7. Q&A session

    Sample “Deploy a Sovereign Rollup” workshop presentation ​

    • Sample presentation - deploy a sovereign rollup
    • Summary: This is an overview presentation on deploying a sovereign rollup with Rollkit on Celestia. You can find existing video presentations for this here:
    • The sample presentation covers:
      1. What is a sovereign rollup?
      2. The role of sovereign rollups in the Celestia ecosystem
      3. Introduction to Rollkit
      4. Setting up a sovereign rollup: hardware and software requirements
      5. Q&A session

    Sample “Modular Meetup Introduction” workshop presentation ​

    Swag logistics ​

    With this Modular Meetups Organizer Kit, you’ll have everything you need to plan and execute engaging, informative, and successful meetups for the Celestia community. Happy organizing!

    + \ No newline at end of file diff --git a/pr-1699/community/overview.html b/pr-1699/community/overview.html index 0a3772c534..94a6aeaa6d 100644 --- a/pr-1699/community/overview.html +++ b/pr-1699/community/overview.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    Community overview ​

    This section will highlight all the different resources and activities for the Celestia community.

    Here you will find links to our community calendar, Code of Conduct and other community-related resources.

    - +

    Community overview ​

    This section will highlight all the different resources and activities for the Celestia community.

    Here you will find links to our community calendar, Code of Conduct and other community-related resources.

    + \ No newline at end of file diff --git a/pr-1699/community/speaker-list.html b/pr-1699/community/speaker-list.html index 748d772452..d386a3ab83 100644 --- a/pr-1699/community/speaker-list.html +++ b/pr-1699/community/speaker-list.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    Speaker list ​

    As a Modular Meetup organizer, we understand the importance of delivering engaging and informative content to your attendees. That's why we've created an exclusive Speaker List specifically tailored for organizers participating in the Modular Meetup Program. This resource gives you access to a curated selection of top-tier speakers who are passionate about Celestia and the modular ecosystem. Due to privacy, the list is not shared publicly but is accessible to participants of the Modular Meetup program when they create a meetup.

    The Speaker List features experts from Celestia Labs, as well as prominent figures from the broader Celestia and modular communities. Each individual is well-versed in various aspects of the modular ecosystem, ensuring that your meetup attendees gain valuable insights and deepen their understanding of modular blockchains.

    By joining the Modular Meetup Program, you can enjoy the benefits of our Speaker List and bring a touch of expertise to your events. The speakers can participate either in person or virtually, depending on location and timing.

    You can expect benefits from the Speaker List including high-quality presentations, interactive Q&A sessions, and knowledge-sharing opportunities facilitated by the best and brightest in the Celestia ecosystem. With our Speaker List, you'll be able to create memorable and impactful Modular Meetups that foster genuine connections and promote growth within the community.

    - +

    Speaker list ​

    As a Modular Meetup organizer, we understand the importance of delivering engaging and informative content to your attendees. That's why we've created an exclusive Speaker List specifically tailored for organizers participating in the Modular Meetup Program. This resource gives you access to a curated selection of top-tier speakers who are passionate about Celestia and the modular ecosystem. Due to privacy, the list is not shared publicly but is accessible to participants of the Modular Meetup program when they create a meetup.

    The Speaker List features experts from Celestia Labs, as well as prominent figures from the broader Celestia and modular communities. Each individual is well-versed in various aspects of the modular ecosystem, ensuring that your meetup attendees gain valuable insights and deepen their understanding of modular blockchains.

    By joining the Modular Meetup Program, you can enjoy the benefits of our Speaker List and bring a touch of expertise to your events. The speakers can participate either in person or virtually, depending on location and timing.

    You can expect benefits from the Speaker List including high-quality presentations, interactive Q&A sessions, and knowledge-sharing opportunities facilitated by the best and brightest in the Celestia ecosystem. With our Speaker List, you'll be able to create memorable and impactful Modular Meetups that foster genuine connections and promote growth within the community.

    + \ No newline at end of file diff --git a/pr-1699/developers/arbitrum-bridge.html b/pr-1699/developers/arbitrum-bridge.html index 1e6dc4e428..d764c3c888 100644 --- a/pr-1699/developers/arbitrum-bridge.html +++ b/pr-1699/developers/arbitrum-bridge.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    Bridging in and out of your Orbit rollup ​

    This guide covers how to bridge in (deposit) and bridge out (withdrawal) from your Arbitrum Orbit L3 rollup.

    This guide will cover bridging in and out of your Orbit rollup.

    Below are two example transactions, one of a deposit and one of a withdrawal:

    bridge-overview-deposit-and-withdrawal-l3

    Bridge in (deposit) to your rollup ​

    Step 1: Add your custom chain config ​

    (1a) In the Arbitrum Bridge UI, click the menu dropdown in the top right. Select Settings.

    bridge-settings

    (1b) Under Developer Mode, select Turn on testnet mode. Add your custom chain config from outputInfo.json in the root of your orbit-setup-script directory.

    add-testnet-orbit-chain

    (1c) You'll then see the chain under Live Orbit Chains:

    live-orbit-chains

    Step 2: Deposit to your Orbit rollup ​

    (2a) Choose an amount of Arbitrum Sepolia ETH to bridge into your rollup. Click Move funds to <YOUR_ROLLUP_NAME>, in this case Move funds to Arbitrum L3 Rollup. Approve the transaction in your wallet.

    bridge-in-start

    (2b) You'll then see it load in the Pending transactions tab:

    bridge-in-pending

    (2c) Shortly after, in the Settled transactions tab you can see the transaction status. Click Success.

    bridge-in-settled-txs

    (2d) View the transaction on your local instance of Blockscout for your rollup:

    bridge-in-explorer-rollup-tx

    (2e) Optionally, click See Details for an overview of your deposit:

    bridge-in-success

    (2f) From the details page, you can also see the transaction for your deposit on Arbitrum Sepolia:

    bridge-in-sepolia-tx-explorer

    Bridge out (withdrawal) from your rollup ​

    Step 1: Choose an amount to withdraw from your rollup ​

    (1a) In the Arbitrum Bridge UI, choose your origin chain to your Arbitrum L3 Rollup and the destination chain as Arbitrum Sepolia.

    bridge-out-small-screenshot

    (1b) Click Move funds to Arbitrum Sepolia and read the disclaimer, check the boxes, and click Continue.

    bridge-out-begin

    (1c) Optionally, set a reminder on your calendar so you don't forget.

    (1d) After approving the transaction in your wallet, you'll be able to see the transaction in the Pending transactions tab:

    bridge-out-pending

    After approximately two hours, you will be able to proceed to Step 2: Claim your withdrawal.

    (1e) Click See details to see an overview of your withdrawal:

    bridge-out-begin-overview

    (1f) Optionally, view the transaction on your local explorer.

    bridge-out-tx-details

    (1g) To learn more about what is going on, click the Logs tab:

    bridge-out-logs-details-1

    bridge-out-logs-explorer-2

    Step 2: Claim your withdrawal ​

    After approximately 2 hours, you will be able to claim your withdrawal.

    (2a) Head back to the bridge UI and you will have a notification to claim your withdrawal. Click Claim in the details of the transaction:

    bridge-out-claim-withdrawal

    (2b) Approve the transaction in your wallet.

    (2c) After your transaction goes through, you can see the details in the bridge UI under Settled transactions:

    bridge-out-claim-success-withdrawal

    - +

    Bridging in and out of your Orbit rollup ​

    This guide covers how to bridge in (deposit) and bridge out (withdrawal) from your Arbitrum Orbit L3 rollup.

    This guide will cover bridging in and out of your Orbit rollup.

    Below are two example transactions, one of a deposit and one of a withdrawal:

    bridge-overview-deposit-and-withdrawal-l3

    Bridge in (deposit) to your rollup ​

    Step 1: Add your custom chain config ​

    (1a) In the Arbitrum Bridge UI, click the menu dropdown in the top right. Select Settings.

    bridge-settings

    (1b) Under Developer Mode, select Turn on testnet mode. Add your custom chain config from outputInfo.json in the root of your orbit-setup-script directory.

    add-testnet-orbit-chain

    (1c) You'll then see the chain under Live Orbit Chains:

    live-orbit-chains

    Step 2: Deposit to your Orbit rollup ​

    (2a) Choose an amount of Arbitrum Sepolia ETH to bridge into your rollup. Click Move funds to <YOUR_ROLLUP_NAME>, in this case Move funds to Arbitrum L3 Rollup. Approve the transaction in your wallet.

    bridge-in-start

    (2b) You'll then see it load in the Pending transactions tab:

    bridge-in-pending

    (2c) Shortly after, in the Settled transactions tab you can see the transaction status. Click Success.

    bridge-in-settled-txs

    (2d) View the transaction on your local instance of Blockscout for your rollup:

    bridge-in-explorer-rollup-tx

    (2e) Optionally, click See Details for an overview of your deposit:

    bridge-in-success

    (2f) From the details page, you can also see the transaction for your deposit on Arbitrum Sepolia:

    bridge-in-sepolia-tx-explorer

    Bridge out (withdrawal) from your rollup ​

    Step 1: Choose an amount to withdraw from your rollup ​

    (1a) In the Arbitrum Bridge UI, choose your origin chain to your Arbitrum L3 Rollup and the destination chain as Arbitrum Sepolia.

    bridge-out-small-screenshot

    (1b) Click Move funds to Arbitrum Sepolia and read the disclaimer, check the boxes, and click Continue.

    bridge-out-begin

    (1c) Optionally, set a reminder on your calendar so you don't forget.

    (1d) After approving the transaction in your wallet, you'll be able to see the transaction in the Pending transactions tab:

    bridge-out-pending

    After approximately two hours, you will be able to proceed to Step 2: Claim your withdrawal.

    (1e) Click See details to see an overview of your withdrawal:

    bridge-out-begin-overview

    (1f) Optionally, view the transaction on your local explorer.

    bridge-out-tx-details

    (1g) To learn more about what is going on, click the Logs tab:

    bridge-out-logs-details-1

    bridge-out-logs-explorer-2

    Step 2: Claim your withdrawal ​

    After approximately 2 hours, you will be able to claim your withdrawal.

    (2a) Head back to the bridge UI and you will have a notification to claim your withdrawal. Click Claim in the details of the transaction:

    bridge-out-claim-withdrawal

    (2b) Approve the transaction in your wallet.

    (2c) After your transaction goes through, you can see the details in the bridge UI under Settled transactions:

    bridge-out-claim-success-withdrawal

    + \ No newline at end of file diff --git a/pr-1699/developers/arbitrum-dapp-deploy.html b/pr-1699/developers/arbitrum-dapp-deploy.html index 4469278a09..ccbe10b6fd 100644 --- a/pr-1699/developers/arbitrum-dapp-deploy.html +++ b/pr-1699/developers/arbitrum-dapp-deploy.html @@ -11,7 +11,7 @@ - + @@ -58,8 +58,8 @@ cast send --private-key $PRIVATE_KEY $RECEIVER --value 1ether --rpc-url $ARB_RPC_URL
    export RECEIVER=<receiver ETH address>
 cast send --private-key $PRIVATE_KEY $RECEIVER --value 1ether --rpc-url $ARB_RPC_URL

    TIP

    If you are in a different terminal than the one you set the private key in, you may need to set it again.

Update the frontend ​

Next, you will need to update a few things before you can interact with the contract on the frontend:

  1. Change the contract address on gm-portal/frontend/src/App.tsx to your contract address
  2. Match the chain info on gm-portal/frontend/src/main.tsx with the chain config of your L2
  3. If you changed the contract, update the ABI in gm-portal/frontend/GmPortal.json from gm-portal/contracts/out/GmPortal.sol/GmPortal.json. This can be done with:
bash
cd $HOME
 cp dev/gm-portal/contracts/out/GmPortal.sol/GmPortal.json dev/gm-portal/frontend
cd $HOME
-cp dev/gm-portal/contracts/out/GmPortal.sol/GmPortal.json dev/gm-portal/frontend

Interact with the frontend ​

Now, login with your wallet that you funded, and post a GM on your GM portal!

gm-arb

- +cp dev/gm-portal/contracts/out/GmPortal.sol/GmPortal.json dev/gm-portal/frontend

Interact with the frontend ​

Now, login with your wallet that you funded, and post a GM on your GM portal!

gm-arb

+ \ No newline at end of file diff --git a/pr-1699/developers/arbitrum-deploy.html b/pr-1699/developers/arbitrum-deploy.html index a77933091b..38756dab9f 100644 --- a/pr-1699/developers/arbitrum-deploy.html +++ b/pr-1699/developers/arbitrum-deploy.html @@ -11,7 +11,7 @@ - + @@ -148,8 +148,8 @@ Executor has been added to chain owners on TX: 0x97b50f60b60d0e658fdbf185969db0a0327bd0ae9e57cd65af2a7f9be0eeb5b0 Executing removeChainOwner through the UpgradeExecutor contract Transaction complete, rollup owner removed from chain owners on TX: 0x019850732270d8c436585c7921219252422228b5d0f559da0da219f0fa2b7216 -✨ Done in 58.49s.

Find your PFB on Celenium by looking at the namespace or account you posted from.

See an example blob that was posted while making this guide.

Congratulations with Celestia underneath ​

Your local Orbit rollup is now running. You'll see an outputInfo.json file in the main directory of your script folder - this contains more information about your chain, including the addresses of your chain's base contracts.

In the next guides, learn how to run a full and validating full node or bridge in and out of your rollup.

Appendix ​

Extra resources in Arbitrum documentation:

Compatibility matrix ​

ComponentVersionDetails
Nitrov2.3.1-rc.1Includes the replay binary for the WASM root 0x10c65b27d5031ce2351c719072e58f3153228887f027f9f6d65300d2b5b30152. Read the overview for overall changes.
Contractsv1.2.1-celestiaIntegrates Blobstream X functionality into nitro-contracts v1.2.1
Orbit SDKv0.8.2 Orbit SDK for Celestia DAThis is not compatible with Orbit SDK v0.8.2 or with the latest changes to nitro-contracts for the Atlas upgrade. The Orbit SDK itself is in Alpha.
celestia-nodev0.13.1This integration has only been tested with celestia-node 0.13.1 and only works with said version, and with future versions after that. Under the hood, the Nitro node uses this commit of celestia-openrpc.

Blobstream X contract deployments ​

The Orbit contracts depend on the following Blobstream X deployments. The current deployments, which can be found at 0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2 in both chains, relays headers from the Mocha-4 testnet to the chains below:

Arbitrum Sepolia ​

Base Sepolia ​

Arbitrum Sepolia additional deployments ​

ContractAddress
Bridge0x95FEA00e689e8D1CBa909836E1Ef1b941D5f21b1
SequencerInbox0x95CBDa89325db5529eAF1813E181f66B83A7d65a
Inbox0x3681Cbb0E95AB50b63F2FC524FbBcC78adEfBd33
RollupEventInbox0x61e154128b6a1400ea8090B4431B4aA1DBb80Cc4
Outbox0x5187a92539bB4A2befe1fc078745c84AB6d37171
ERC20Bridge0xD0a6699Fc7519966685181c80BF98D35aFa1fC95
SequencerInbox0x2588867F19E2DE51f90F0aB852C7Ad11228e3d83
ERC20Inbox0x6cB49605f10831749c6090AD09918bC61439bacE
ERC20RollupEventInbox0x7fC4D9A24949680faD666FeEe7cD6a100E39C4F0
ERC20Outbox0xA773e19DC9e822933A7e72Df9c87eD1578701D29
BridgeCreator0x3Bc040EAca40b91FA06cf55Ea91842FaC88b1AF4
OneStepProver00x5810F0916BAE1067Ca1efcc00AaaF30301af001c
OneStepProverMemory0xaC3427E621C6F10dC2ABdAB00188D92690503914
OneStepProverMath0xFB612fb83959b8ACD3E49540B29C93c5A67e05f1
OneStepProverHostIo0x630093954CbF19Fe4532A2edD0bD3B10dEcA7A4D
OneStepProofEntry0x53DEA3A90Fd6C82840a1f7224F799D622f142Df4
ChallengeManager0x01B5905B154F21a393F5B5a0C6d15B53a493C05e
RollupAdminLogic0xe371AFcb8437bF61bd831EF57Be7A2496D88488B
RollupUserLogic0xE24a60b758b51b0a3dA5E8F4F6ddf1cd0aFF646C
ValidatorUtils0x7973D0b475E898082dF25c1617CBce1917cFED17
ValidatorWalletCreator0xe2662ff9b41f39e63A850E50E013Ea66e60A4F37
RollupCreator0x79751B011BCc20F413a2c4E3AF019b6E2a9738B9
DeployHelper0xd2D353916B34a877793628049c99858f04123eE1

Base Sepolia additional deployments ​

ContractAddress
Bridge0xb6052122545AACD2BDda0Ca9FA56416bD968cDbc
SequencerInbox0xcd9FCa5015b5ce2B06a2266e4a5dd54D9ca39F1a
Inbox0x44B412b291fEf00398501B2cA353EA912AD0fe13
RollupEventInbox0x51D196e07a27DBA0F4461Dd6CC26108424F196f7
Outbox0x5A48aDf22f526eBD06e3e8856cFEa2490923CC55
ERC20Bridge0x9abC41fEfAe7E7543a01FA837AeC909F96147280
SequencerInbox0x8f97Cb7c643Acd7f79f3B13841b24a243dA51242
ERC20Inbox0x40f8c63e0a20B399bCd9631A22E57BB988a9400e
ERC20RollupEventInbox0x3B6e845fb9f0c8Ee4E9F6D44781f6547d9c6359a
ERC20Outbox0xc99eEA0B8e67D5b2226AB6D37882DAAf6dd7593b
BridgeCreator0xC7535F078CB3880a0FD5E54FA7A3B4EAf09b3924
OneStepProver00xf889a3174Fddd9f78E6cd250Ebf4c16F1bDd1b6a
OneStepProverMemory0x61254e43e5c1e9E801F9C56B47a9ac3EADF6d1E9
OneStepProverMath0x55527d53fdA37Dbf1924482b40AcF8625E1cAA5B
OneStepProverHostIo0x03B43F7B61Fa100611191F481Ef48aa1fc98F434
OneStepProofEntry0x89b7c7970c13BB587893a70697AD6d2A335b6A15
ChallengeManager0x04CAe899Fc0B7Ef45c529f8Bf075D54F6fB70eD9
RollupAdminLogic0x99E9D2F04352B42C18F1DA5Dd93a970F82C08aFe
RollupUserLogic0x1ae3A8DC1e7eFD37F418B2987D3DF74c5a917a8B
ValidatorUtils0x1cc4551922C069A9aDE06756BF14bF0410eA44fF
ValidatorWalletCreator0x78f8B2941ddE5a8A312814Ebd29c2E2A36f25E91
RollupCreator0x1Bb8ADd5e878b12Fa37756392642eB94C53A1Cf4
DeployHelper0x20d8153AaCC4E6D29558fa3916BfF422BEDE9B5E
- +✨ Done in 58.49s.

Find your PFB on Celenium by looking at the namespace or account you posted from.

See an example blob that was posted while making this guide.

Congratulations with Celestia underneath ​

Your local Orbit rollup is now running. You'll see an outputInfo.json file in the main directory of your script folder - this contains more information about your chain, including the addresses of your chain's base contracts.

In the next guides, learn how to run a full and validating full node or bridge in and out of your rollup.

Appendix ​

Extra resources in Arbitrum documentation:

Compatibility matrix ​

ComponentVersionDetails
Nitrov2.3.1-rc.1Includes the replay binary for the WASM root 0x10c65b27d5031ce2351c719072e58f3153228887f027f9f6d65300d2b5b30152. Read the overview for overall changes.
Contractsv1.2.1-celestiaIntegrates Blobstream X functionality into nitro-contracts v1.2.1
Orbit SDKv0.8.2 Orbit SDK for Celestia DAThis is not compatible with Orbit SDK v0.8.2 or with the latest changes to nitro-contracts for the Atlas upgrade. The Orbit SDK itself is in Alpha.
celestia-nodev0.13.1This integration has only been tested with celestia-node 0.13.1 and only works with said version, and with future versions after that. Under the hood, the Nitro node uses this commit of celestia-openrpc.

Blobstream X contract deployments ​

The Orbit contracts depend on the following Blobstream X deployments. The current deployments, which can be found at 0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2 in both chains, relays headers from the Mocha-4 testnet to the chains below:

Arbitrum Sepolia ​

Base Sepolia ​

Arbitrum Sepolia additional deployments ​

ContractAddress
Bridge0x95FEA00e689e8D1CBa909836E1Ef1b941D5f21b1
SequencerInbox0x95CBDa89325db5529eAF1813E181f66B83A7d65a
Inbox0x3681Cbb0E95AB50b63F2FC524FbBcC78adEfBd33
RollupEventInbox0x61e154128b6a1400ea8090B4431B4aA1DBb80Cc4
Outbox0x5187a92539bB4A2befe1fc078745c84AB6d37171
ERC20Bridge0xD0a6699Fc7519966685181c80BF98D35aFa1fC95
SequencerInbox0x2588867F19E2DE51f90F0aB852C7Ad11228e3d83
ERC20Inbox0x6cB49605f10831749c6090AD09918bC61439bacE
ERC20RollupEventInbox0x7fC4D9A24949680faD666FeEe7cD6a100E39C4F0
ERC20Outbox0xA773e19DC9e822933A7e72Df9c87eD1578701D29
BridgeCreator0x3Bc040EAca40b91FA06cf55Ea91842FaC88b1AF4
OneStepProver00x5810F0916BAE1067Ca1efcc00AaaF30301af001c
OneStepProverMemory0xaC3427E621C6F10dC2ABdAB00188D92690503914
OneStepProverMath0xFB612fb83959b8ACD3E49540B29C93c5A67e05f1
OneStepProverHostIo0x630093954CbF19Fe4532A2edD0bD3B10dEcA7A4D
OneStepProofEntry0x53DEA3A90Fd6C82840a1f7224F799D622f142Df4
ChallengeManager0x01B5905B154F21a393F5B5a0C6d15B53a493C05e
RollupAdminLogic0xe371AFcb8437bF61bd831EF57Be7A2496D88488B
RollupUserLogic0xE24a60b758b51b0a3dA5E8F4F6ddf1cd0aFF646C
ValidatorUtils0x7973D0b475E898082dF25c1617CBce1917cFED17
ValidatorWalletCreator0xe2662ff9b41f39e63A850E50E013Ea66e60A4F37
RollupCreator0x79751B011BCc20F413a2c4E3AF019b6E2a9738B9
DeployHelper0xd2D353916B34a877793628049c99858f04123eE1

Base Sepolia additional deployments ​

ContractAddress
Bridge0xb6052122545AACD2BDda0Ca9FA56416bD968cDbc
SequencerInbox0xcd9FCa5015b5ce2B06a2266e4a5dd54D9ca39F1a
Inbox0x44B412b291fEf00398501B2cA353EA912AD0fe13
RollupEventInbox0x51D196e07a27DBA0F4461Dd6CC26108424F196f7
Outbox0x5A48aDf22f526eBD06e3e8856cFEa2490923CC55
ERC20Bridge0x9abC41fEfAe7E7543a01FA837AeC909F96147280
SequencerInbox0x8f97Cb7c643Acd7f79f3B13841b24a243dA51242
ERC20Inbox0x40f8c63e0a20B399bCd9631A22E57BB988a9400e
ERC20RollupEventInbox0x3B6e845fb9f0c8Ee4E9F6D44781f6547d9c6359a
ERC20Outbox0xc99eEA0B8e67D5b2226AB6D37882DAAf6dd7593b
BridgeCreator0xC7535F078CB3880a0FD5E54FA7A3B4EAf09b3924
OneStepProver00xf889a3174Fddd9f78E6cd250Ebf4c16F1bDd1b6a
OneStepProverMemory0x61254e43e5c1e9E801F9C56B47a9ac3EADF6d1E9
OneStepProverMath0x55527d53fdA37Dbf1924482b40AcF8625E1cAA5B
OneStepProverHostIo0x03B43F7B61Fa100611191F481Ef48aa1fc98F434
OneStepProofEntry0x89b7c7970c13BB587893a70697AD6d2A335b6A15
ChallengeManager0x04CAe899Fc0B7Ef45c529f8Bf075D54F6fB70eD9
RollupAdminLogic0x99E9D2F04352B42C18F1DA5Dd93a970F82C08aFe
RollupUserLogic0x1ae3A8DC1e7eFD37F418B2987D3DF74c5a917a8B
ValidatorUtils0x1cc4551922C069A9aDE06756BF14bF0410eA44fF
ValidatorWalletCreator0x78f8B2941ddE5a8A312814Ebd29c2E2A36f25E91
RollupCreator0x1Bb8ADd5e878b12Fa37756392642eB94C53A1Cf4
DeployHelper0x20d8153AaCC4E6D29558fa3916BfF422BEDE9B5E
+ \ No newline at end of file diff --git a/pr-1699/developers/arbitrum-full-node.html b/pr-1699/developers/arbitrum-full-node.html index 9126a407d5..532ce01c15 100644 --- a/pr-1699/developers/arbitrum-full-node.html +++ b/pr-1699/developers/arbitrum-full-node.html @@ -11,7 +11,7 @@ - + @@ -40,8 +40,8 @@

Running a full node and/or validator ​

Prerequisites ​

Running a full node ​

To run a full node, you can follow the steps outlined in the Arbitrum docs, with the difference being that you will use this image: dfcelestia/nitro-node-dev:latest instead of the one mentioned in the Arbitrum docs.

Note that you can either use the flags in the nitro binary + the flags found in the celestia package, or you can just provide a node config.json file with the celestia-cfg for them to run it, which would look something like this:

json
docker run --rm -v "$HOME/Documents/configs/nodeConfig.json:/config.json:ro" \
   --network host celestia-nitro:v2.3.1-rc.1 --conf.file /config.json
docker run --rm -v "$HOME/Documents/configs/nodeConfig.json:/config.json:ro" \
-  --network host celestia-nitro:v2.3.1-rc.1 --conf.file /config.json

Running a full node with validation ​

The information above applies to the steps outlined to run a validating full node (validator).

Finally, note that this will require connection to a DA node, and we recommend running a Bridge node if you will be instantiating multiple rollups.

- + --network host celestia-nitro:v2.3.1-rc.1 --conf.file /config.json

Running a full node with validation ​

The information above applies to the steps outlined to run a validating full node (validator).

Finally, note that this will require connection to a DA node, and we recommend running a Bridge node if you will be instantiating multiple rollups.

+ \ No newline at end of file diff --git a/pr-1699/developers/arbitrum-integration.html b/pr-1699/developers/arbitrum-integration.html index da8ff18b50..3b5c71907c 100644 --- a/pr-1699/developers/arbitrum-integration.html +++ b/pr-1699/developers/arbitrum-integration.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Introduction to Arbitrum rollups with Celestia as DA ​

Celestia_Arbitrum

Overview ​

The integration of Celestia with Arbitrum Orbit and the Nitro tech stack marks the first external contribution to the Arbitrum Orbit protocol layer, offering developers an additional option for selecting a data availability layer alongside Arbitrum AnyTrust. The integration allows developers to deploy an Orbit Chain that uses Celestia for data availability and settles on Arbitrum One, Ethereum, or other EVM chains.

Learn more about Orbit in Arbitrum's introduction.

Key components ​

The integration of Celestia with Arbitrum orbit is possible thanks to 3 key components:

Additionally, the Ethereum fallback mechanism is a feature of the integration, which is native in Nitro.

DA provider implementation ​

The Arbitrum Nitro code has a DataAvailabilityProvider interface that is used across the codebase to store and retrieve data from a specific provider (eip4844 blobs, Anytrust, and now Celestia).

This integration implements the DataAvailabilityProvider interface for Celestia DA

Additionally, this integration comes with the necessary code for a Nitro chain node to post and retrieve data from Celestia.

The core logic behind posting and retrieving data happens in celestia.go where data is stored on Celestia and serialized into a small batch of data that gets published once the necessary range of headers (data roots) has been relayed to the BlobstreamX contract. Then the Read logic takes care of taking the deserialized Blob Pointer struct and consuming it in order to fetch the data from Celestia and additionally inform the fetcher about the position of the data on Celestia (we'll get back to this in the next section).

The following represents a non-exhaustive list of considerations when running a Batch Poster node for a chain with Celestia underneath:

  • You will need to use a consensus node RPC endpoint, you can find a list of them for Mocha
  • The Batch Poster will only post a Celestia batch to the underlying chain if the height for which it posted is in a recent range in BlobstreamX and if the verification succeeds, otherwise it will discard the batch. Since it will wait until a range is relayed, it can take several minutes for a batch to be posted, but one can always make an on-chain request for the BlobstreamX contract to relay a header promptly.

The following represents a non-exhaustive list of considerations when running a Nitro node for a chain with Celestia underneath:

  • The TendermintRpc endpoint is only needed by the batch poster, every other node can operate without a connection to a full node.
  • The message header flag for Celestia batches is 0x0c.
  • You will need to know the namespace for the chain that you are trying to connect to, but don't worry if you don't find it, as the information in the BlobPointer can be used to identify where a batch of data is in the Celestia Data Square for a given height, and thus can be used to find out the namespace as well!

Preimage Oracle Implementation ​

In order to support fraud proofs, this integration has the necessary code for a Nitro validator to populate its preimage mapping with Celestia hashes that then get "unpealed" in order to reveal the full data for a Blob. You can read more about the "Hash Oracle Trick".

The data structures and hashing functions for this can be found in the nitro/das/celestia/tree folder

You can see where the preimage oracle gets used in the fraud proof replay binary here

Something important to note is that the preimage oracle only keeps track of hashes for the rows in the Celestia data square in which a blob resides in, this way each Orbit chain with Celestia underneath does not need validators to recompute an entire Celestia Data Square, but instead, only have to compute the row roots for the rows in which it's data lives in, and the header data root, which is the binary merkle tree hash built using the row roots and column roots fetched from a Celestia node. Because only data roots that can be confirmed on Blobstream get accepted into the sequencer inbox, one can have a high degree of certainty that the canonical data root being unpealed as well as the row roots are in fact correct.

Blobstream X implementation ​

Finally, the integration only accepts batches with information that can be confirmed on BlobstreamX, which gives us a high certainty that data was made available on Celestia.

You can see how BlobstreamX is integrated into the SequencerInbox.sol contract here, which allows us to discard batches with otherwise faulty data roots, thus giving us a high degree of confidence that the data root can be safely unpacked in case of a challenge.

The Celestia and Arbitrum integration also includes Blobstream, which relays commitments to Celestia’s data root to an onchain light client on Ethereum. This allows L2 solutions that settle on Ethereum to benefit from the scalability Celestia’s data availability layer can provide.

Ethereum fallback mechanism in Nitro ​

By default in Arbitrum Nitro, the Ethereum fallback mechanism in the BatchPoster function is handling the process of storing data, with a fallback mechanism to store data onchain if the primary data availability storage fails.

The @celestiaorg/nitro integration uses the same fallback mechanism.

More information can be found on the Ethereum fallback mechanisms for Celestia, which enables Ethereum L2s (or L3s) to “fall back” to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta.

The fallback logic for Celestia DA is configurable, providing an alternative to the previous default fallback mechanism. Additionally, an ability has been added to the Arbitrum node software which allows the sequencer to call VerifyAttestation to check if a data root has been posted on Blobstream or not, before it sends the sequencer message (data pointer) to the underlying chain.

Next steps ​

In the next page, learn how to deploy an Arbitrum rollup devnet using Celestia as DA.

- +

Introduction to Arbitrum rollups with Celestia as DA ​

Celestia_Arbitrum

Overview ​

The integration of Celestia with Arbitrum Orbit and the Nitro tech stack marks the first external contribution to the Arbitrum Orbit protocol layer, offering developers an additional option for selecting a data availability layer alongside Arbitrum AnyTrust. The integration allows developers to deploy an Orbit Chain that uses Celestia for data availability and settles on Arbitrum One, Ethereum, or other EVM chains.

Learn more about Orbit in Arbitrum's introduction.

Key components ​

The integration of Celestia with Arbitrum orbit is possible thanks to 3 key components:

Additionally, the Ethereum fallback mechanism is a feature of the integration, which is native in Nitro.

DA provider implementation ​

The Arbitrum Nitro code has a DataAvailabilityProvider interface that is used across the codebase to store and retrieve data from a specific provider (eip4844 blobs, Anytrust, and now Celestia).

This integration implements the DataAvailabilityProvider interface for Celestia DA

Additionally, this integration comes with the necessary code for a Nitro chain node to post and retrieve data from Celestia.

The core logic behind posting and retrieving data happens in celestia.go where data is stored on Celestia and serialized into a small batch of data that gets published once the necessary range of headers (data roots) has been relayed to the BlobstreamX contract. Then the Read logic takes care of taking the deserialized Blob Pointer struct and consuming it in order to fetch the data from Celestia and additionally inform the fetcher about the position of the data on Celestia (we'll get back to this in the next section).

The following represents a non-exhaustive list of considerations when running a Batch Poster node for a chain with Celestia underneath:

  • You will need to use a consensus node RPC endpoint, you can find a list of them for Mocha
  • The Batch Poster will only post a Celestia batch to the underlying chain if the height for which it posted is in a recent range in BlobstreamX and if the verification succeeds, otherwise it will discard the batch. Since it will wait until a range is relayed, it can take several minutes for a batch to be posted, but one can always make an on-chain request for the BlobstreamX contract to relay a header promptly.

The following represents a non-exhaustive list of considerations when running a Nitro node for a chain with Celestia underneath:

  • The TendermintRpc endpoint is only needed by the batch poster, every other node can operate without a connection to a full node.
  • The message header flag for Celestia batches is 0x0c.
  • You will need to know the namespace for the chain that you are trying to connect to, but don't worry if you don't find it, as the information in the BlobPointer can be used to identify where a batch of data is in the Celestia Data Square for a given height, and thus can be used to find out the namespace as well!

Preimage Oracle Implementation ​

In order to support fraud proofs, this integration has the necessary code for a Nitro validator to populate its preimage mapping with Celestia hashes that then get "unpealed" in order to reveal the full data for a Blob. You can read more about the "Hash Oracle Trick".

The data structures and hashing functions for this can be found in the nitro/das/celestia/tree folder

You can see where the preimage oracle gets used in the fraud proof replay binary here

Something important to note is that the preimage oracle only keeps track of hashes for the rows in the Celestia data square in which a blob resides in, this way each Orbit chain with Celestia underneath does not need validators to recompute an entire Celestia Data Square, but instead, only have to compute the row roots for the rows in which it's data lives in, and the header data root, which is the binary merkle tree hash built using the row roots and column roots fetched from a Celestia node. Because only data roots that can be confirmed on Blobstream get accepted into the sequencer inbox, one can have a high degree of certainty that the canonical data root being unpealed as well as the row roots are in fact correct.

Blobstream X implementation ​

Finally, the integration only accepts batches with information that can be confirmed on BlobstreamX, which gives us a high certainty that data was made available on Celestia.

You can see how BlobstreamX is integrated into the SequencerInbox.sol contract here, which allows us to discard batches with otherwise faulty data roots, thus giving us a high degree of confidence that the data root can be safely unpacked in case of a challenge.

The Celestia and Arbitrum integration also includes Blobstream, which relays commitments to Celestia’s data root to an onchain light client on Ethereum. This allows L2 solutions that settle on Ethereum to benefit from the scalability Celestia’s data availability layer can provide.

Ethereum fallback mechanism in Nitro ​

By default in Arbitrum Nitro, the Ethereum fallback mechanism in the BatchPoster function is handling the process of storing data, with a fallback mechanism to store data onchain if the primary data availability storage fails.

The @celestiaorg/nitro integration uses the same fallback mechanism.

More information can be found on the Ethereum fallback mechanisms for Celestia, which enables Ethereum L2s (or L3s) to “fall back” to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta.

The fallback logic for Celestia DA is configurable, providing an alternative to the previous default fallback mechanism. Additionally, an ability has been added to the Arbitrum node software which allows the sequencer to call VerifyAttestation to check if a data root has been posted on Blobstream or not, before it sends the sequencer message (data pointer) to the underlying chain.

Next steps ​

In the next page, learn how to deploy an Arbitrum rollup devnet using Celestia as DA.

+ \ No newline at end of file diff --git a/pr-1699/developers/arbitrum-smart-contract.html b/pr-1699/developers/arbitrum-smart-contract.html index 74f3c04303..5c354fc8bb 100644 --- a/pr-1699/developers/arbitrum-smart-contract.html +++ b/pr-1699/developers/arbitrum-smart-contract.html @@ -11,7 +11,7 @@ - + @@ -170,8 +170,8 @@ status 1 transactionHash 0x8f15d6004598f0662dd673a9898dceef77be8cc28408cecc284b28d7be32307d transactionIndex 0 -type 2

Now, we can make a read call to view the state of the number variable, using the cast call command:

bash
cast call $CONTRACT_ADDRESS "number()" --rpc-url $ARB_RPC_URL
cast call $CONTRACT_ADDRESS "number()" --rpc-url $ARB_RPC_URL

The result will look similar:

bash
0x000000000000000000000000000000000000000000000000000000000000000a
0x000000000000000000000000000000000000000000000000000000000000000a

Convert the result from hexadecimal to a base 10 value with:

bash
echo $((0x000000000000000000000000000000000000000000000000000000000000000a))
echo $((0x000000000000000000000000000000000000000000000000000000000000000a))

Next steps ​

Congratulations! You've learned how to deploy a smart contract to your Arbitrum rollup devnet.

What will you build next? In our next tutorial, we will be going over how to deploy a dapp to your Arbitrum rollup.

- +type 2

Now, we can make a read call to view the state of the number variable, using the cast call command:

bash
cast call $CONTRACT_ADDRESS "number()" --rpc-url $ARB_RPC_URL
cast call $CONTRACT_ADDRESS "number()" --rpc-url $ARB_RPC_URL

The result will look similar:

bash
0x000000000000000000000000000000000000000000000000000000000000000a
0x000000000000000000000000000000000000000000000000000000000000000a

Convert the result from hexadecimal to a base 10 value with:

bash
echo $((0x000000000000000000000000000000000000000000000000000000000000000a))
echo $((0x000000000000000000000000000000000000000000000000000000000000000a))

Next steps ​

Congratulations! You've learned how to deploy a smart contract to your Arbitrum rollup devnet.

What will you build next? In our next tutorial, we will be going over how to deploy a dapp to your Arbitrum rollup.

+ \ No newline at end of file diff --git a/pr-1699/developers/blobstream-contracts.html b/pr-1699/developers/blobstream-contracts.html index dd9232d571..cf8ee87947 100644 --- a/pr-1699/developers/blobstream-contracts.html +++ b/pr-1699/developers/blobstream-contracts.html @@ -11,7 +11,7 @@ - + @@ -124,8 +124,8 @@ ) private pure returns (bool) { return true; } -}

Data structures ​

Each DataRootTuple is a tuple of block height and data root. It is analogous to a Celestia block header. DataRootTuples are relayed in batches, committed to as a DataRootTuples root (i.e. a Merkle root of DataRootTuples).

The BinaryMerkleProof is an RFC-6962-compliant Merkle proof. Since DataRootTuples are Merkleized in a binary Merkle tree, verifying the inclusion of a DataRootTuple against a DataRootTuples root requires verifying a Merkle inclusion proof.

Interface ​

The IDAOracle (Data Availability Oracle Interface) interface allows L2 contracts on Ethereum to query the BlobstreamX.sol contract for relayed DataRootTuples. The single interface method verifyAttestation verifies a Merkle inclusion proof that a DataRootTuple is included under a specific batch (indexed by batch nonce). In other words, analogously it verifies that a specific block header is included in the Celestia chain.

Querying the proof ​

To prove that the data was published to Celestia, check out the proof queries documentation to understand how to query the proofs from Celestia consensus nodes and make them usable in the Blobstream X verifier contract.

Verifying data inclusion for fraud proofs ​

A high-level overview of how a fraud-proof based L2 would interact with Blobstream can be found in the inclusion proofs documentation.

The DAVerifier library is available at blobstream-contracts/lib/verifier/DAVerifier.sol, and provides functions to verify the inclusion of individual (or multiple) shares against a DataRootTuple. The library is stateless, and allows to pass an IDAOracle interface as a parameter to verify inclusion against it.

In the DAVerifier library, we find functions that help with data inclusion verification and calculating the square size of a Celestia block. These functions work with the Blobstream X smart contract, using different proofs to check and confirm the data's availability. Let's take a closer look at these functions:

  • verifySharesToDataRootTupleRoot: This function verifies that the shares, which were posted to Celestia, were committed to by the Blobstream X smart contract. It checks that the data root was committed to by the Blobstream X smart contract and that the shares were committed to by the rows roots.
  • verifyRowRootToDataRootTupleRoot: This function verifies that a row/column root, from a Celestia block, was committed to by the Blobstream X smart contract. It checks that the data root was committed to by the Blobstream X smart contract and that the row root commits to the data root.
  • verifyMultiRowRootsToDataRootTupleRoot: This function verifies that a set of rows/columns, from a Celestia block, were committed to by the Blobstream X smart contract. It checks that the data root was committed to by the Blobstream X smart contract and that the rows roots commit to the data root.
  • computeSquareSizeFromRowProof: This function computes the Celestia block square size from a row/column root to data root binary Merkle proof. It is the user's responsibility to verify that the proof is valid and was successfully committed to using the verifyRowRootToDataRootTupleRoot() method.
  • computeSquareSizeFromShareProof: This function computes the Celestia block square size from a shares to row/column root proof. It is the user's responsibility to verify that the proof is valid and that the shares were successfully committed to using the verifySharesToDataRootTupleRoot() method.

For an overview of a demo rollup implementation, head to the next section.

- +}

Data structures ​

Each DataRootTuple is a tuple of block height and data root. It is analogous to a Celestia block header. DataRootTuples are relayed in batches, committed to as a DataRootTuples root (i.e. a Merkle root of DataRootTuples).

The BinaryMerkleProof is an RFC-6962-compliant Merkle proof. Since DataRootTuples are Merkleized in a binary Merkle tree, verifying the inclusion of a DataRootTuple against a DataRootTuples root requires verifying a Merkle inclusion proof.

Interface ​

The IDAOracle (Data Availability Oracle Interface) interface allows L2 contracts on Ethereum to query the BlobstreamX.sol contract for relayed DataRootTuples. The single interface method verifyAttestation verifies a Merkle inclusion proof that a DataRootTuple is included under a specific batch (indexed by batch nonce). In other words, analogously it verifies that a specific block header is included in the Celestia chain.

Querying the proof ​

To prove that the data was published to Celestia, check out the proof queries documentation to understand how to query the proofs from Celestia consensus nodes and make them usable in the Blobstream X verifier contract.

Verifying data inclusion for fraud proofs ​

A high-level overview of how a fraud-proof based L2 would interact with Blobstream can be found in the inclusion proofs documentation.

The DAVerifier library is available at blobstream-contracts/lib/verifier/DAVerifier.sol, and provides functions to verify the inclusion of individual (or multiple) shares against a DataRootTuple. The library is stateless, and allows to pass an IDAOracle interface as a parameter to verify inclusion against it.

In the DAVerifier library, we find functions that help with data inclusion verification and calculating the square size of a Celestia block. These functions work with the Blobstream X smart contract, using different proofs to check and confirm the data's availability. Let's take a closer look at these functions:

  • verifySharesToDataRootTupleRoot: This function verifies that the shares, which were posted to Celestia, were committed to by the Blobstream X smart contract. It checks that the data root was committed to by the Blobstream X smart contract and that the shares were committed to by the rows roots.
  • verifyRowRootToDataRootTupleRoot: This function verifies that a row/column root, from a Celestia block, was committed to by the Blobstream X smart contract. It checks that the data root was committed to by the Blobstream X smart contract and that the row root commits to the data root.
  • verifyMultiRowRootsToDataRootTupleRoot: This function verifies that a set of rows/columns, from a Celestia block, were committed to by the Blobstream X smart contract. It checks that the data root was committed to by the Blobstream X smart contract and that the rows roots commit to the data root.
  • computeSquareSizeFromRowProof: This function computes the Celestia block square size from a row/column root to data root binary Merkle proof. It is the user's responsibility to verify that the proof is valid and was successfully committed to using the verifyRowRootToDataRootTupleRoot() method.
  • computeSquareSizeFromShareProof: This function computes the Celestia block square size from a shares to row/column root proof. It is the user's responsibility to verify that the proof is valid and that the shares were successfully committed to using the verifySharesToDataRootTupleRoot() method.

For an overview of a demo rollup implementation, head to the next section.

+ \ No newline at end of file diff --git a/pr-1699/developers/blobstream-offchain.html b/pr-1699/developers/blobstream-offchain.html index 088f53903b..a1c13492d0 100644 --- a/pr-1699/developers/blobstream-offchain.html +++ b/pr-1699/developers/blobstream-offchain.html @@ -11,7 +11,7 @@ - + @@ -334,8 +334,8 @@ Header: header, }, ) -}

This outline of a Blobstream rollup isn't doing execution or state transitions induced by the transactions, however, that step would occur here. If fraud is detected, the fraud proof process will begin. The only difference between the fraud proof process of a normal optimistic rollup and a rollup that uses Blobstream for DA is that the full node would first prove the fraudulent transaction was committed to by the Sequencer using the Span in the header and before proceeding with the normal process.

More documentation ​

Proving inclusion via Blobstream ​

Blobstream inclusion proof docs and the verifier helper contracts.

Submitting block data to Celestia via light node ​

As linked above, use the Celestia light node RPC to submit the data to Celestia.

Posting headers to Ethereum ​

How headers are posted to Ethereum is entirely dependent upon how the rollup light client contracts work. For examples of interacting with the Ethereum blockchain programmatically, please see the go-ethereum book or one of the many other resources for submitting transactions or writing contracts.

- +}

This outline of a Blobstream rollup isn't doing execution or state transitions induced by the transactions, however, that step would occur here. If fraud is detected, the fraud proof process will begin. The only difference between the fraud proof process of a normal optimistic rollup and a rollup that uses Blobstream for DA is that the full node would first prove the fraudulent transaction was committed to by the Sequencer using the Span in the header and before proceeding with the normal process.

More documentation ​

Proving inclusion via Blobstream ​

Blobstream inclusion proof docs and the verifier helper contracts.

Submitting block data to Celestia via light node ​

As linked above, use the Celestia light node RPC to submit the data to Celestia.

Posting headers to Ethereum ​

How headers are posted to Ethereum is entirely dependent upon how the rollup light client contracts work. For examples of interacting with the Ethereum blockchain programmatically, please see the go-ethereum book or one of the many other resources for submitting transactions or writing contracts.

+ \ No newline at end of file diff --git a/pr-1699/developers/blobstream-proof-queries.html b/pr-1699/developers/blobstream-proof-queries.html index 48b2a2b063..e6a9b4ecf2 100644 --- a/pr-1699/developers/blobstream-proof-queries.html +++ b/pr-1699/developers/blobstream-proof-queries.html @@ -11,7 +11,7 @@ - + @@ -64,7 +64,7 @@ if err != nil { ... } - }(trpc)

The <rpc_endpoint> can be retrieved from mainnet for Celestia mainnet beta, and mocha for the Mocha testnet.

In case the reader wants to interact with an on-chain contract that can be used to verify that data was posted to Celestia, the bindings of that contract are needed.

For Blobstream, the golang bindings can be found in the following links:

text
https://github.com/succinctlabs/blobstreamx/blob/main/bindings/BlobstreamX.go
https://github.com/succinctlabs/blobstreamx/blob/main/bindings/BlobstreamX.go
text
https://github.com/succinctlabs/sp1-blobstream/blob/main/bindings/SP1Blobstream.go
https://github.com/succinctlabs/sp1-blobstream/blob/main/bindings/SP1Blobstream.go

For other languages, the corresponding smart contract bindings should be generated. Refer to abigen for more information.

Overview of the proof queries ​

To prove the inclusion of PayForBlobs (PFB) transactions, blobs or shares, committed to in a Celestia block, we use the Celestia consensus node's RPC to query for proofs that can be verified in a rollup settlement contract via Blobstream. In fact, when a PFB transaction is included in a block, it gets separated into a PFB transaction (without the blob), and the actual data blob that it carries. These two are split into shares, which are the low level constructs of a Celestia block, and saved to the corresponding Celestia block. Learn more about shares in the shares specs.

The two diagrams below summarize how a single share, which can contain a PFB transaction, or a part of the rollup data that was posted using a PFB, is committed to in Blobstream.

The share is highlighted in green. R0, R1 etc, represent the respective row and column roots, the blue and pink gradients are erasure encoded data. More details on the square layout can be found in the data square layout and data structures portion of the specs.

The Celestia square ​

Square

The commitment scheme ​

Blobstream Commitment Diagram

So to prove inclusion of a share to a Celestia block, we use Blobstream as a source of truth. In a nutshell, Blobstream attests to the data posted to Celestia in the zk-Blobstream contract via verifying a zk-proof of the headers of a batch of Celestia blocks. Then, it keeps reference of that batch of blocks using the merkleized commitment of their (dataRoot, height) resulting in a data root tuple root. Check the above diagram which shows:

  • 0: those are the shares, that when unified, contain the PFB or the rollup data blob.
  • 1: the row and column roots are the namespace merkle tree roots over the shares. More information on the NMT in the NMT specs. These commit to the rows and columns containing the above shares.
  • 2: the data roots: which are the binary merkle tree commitment over the row and column roots. This means that if you can prove that a share is part of a row, using a namespace merkle proof. Then prove that this row is committed to by the data root. Then you can be sure that that share was published to the corresponding block.
  • 3: in order to batch multiple blocks into the same commitment, we create a commitment over the (dataRoot, height) tuple for a batch of blocks, which results in a data root tuple root. It's this commitment that gets stored in the Blobstream smart contract.

So, if we're able to prove:

  • That a share is part of a row, then that row is committed to by a data root.
  • Then, prove that that data root along with its height is committed to by the data root tuple root, which gets saved to the Blobstream contract.

We can be sure that that share was committed to in the corresponding Celestia block.

In this document, we will provide details on how to query the above proofs, and how to adapt them to be sent to a rollup contract for verification.

Hands-on demonstration ​

This part will provide the details of proof generation, and the way to make the results of the proofs queries ready to be consumed by the target rollup contract.

NOTE

For the go client snippets, make sure to have the following replaces in your go.mod:

go
// go.mod
+	}(trpc)

The <rpc_endpoint> can be retrieved from mainnet for Celestia mainnet beta, and mocha for the Mocha testnet.

In case the reader wants to interact with an on-chain contract that can be used to verify that data was posted to Celestia, the bindings of that contract are needed.

For Blobstream, the golang bindings can be found in the following links:

text
https://github.com/succinctlabs/blobstreamx/blob/main/bindings/BlobstreamX.go
https://github.com/succinctlabs/blobstreamx/blob/main/bindings/BlobstreamX.go
text
https://github.com/succinctlabs/sp1-blobstream/blob/main/bindings/SP1Blobstream.go
https://github.com/succinctlabs/sp1-blobstream/blob/main/bindings/SP1Blobstream.go

For other languages, the corresponding smart contract bindings should be generated. Refer to abigen for more information.

Overview of the proof queries ​

To prove the inclusion of PayForBlobs (PFB) transactions, blobs or shares, committed to in a Celestia block, we use the Celestia consensus node's RPC to query for proofs that can be verified in a rollup settlement contract via Blobstream. In fact, when a PFB transaction is included in a block, it gets separated into a PFB transaction (without the blob), and the actual data blob that it carries. These two are split into shares, which are the low level constructs of a Celestia block, and saved to the corresponding Celestia block. Learn more about shares in the shares specs.

The two diagrams below summarize how a single share, which can contain a PFB transaction, or a part of the rollup data that was posted using a PFB, is committed to in Blobstream.

The share is highlighted in green. R0, R1 etc, represent the respective row and column roots, the blue and pink gradients are erasure encoded data. More details on the square layout can be found in the data square layout and data structures portion of the specs.

The Celestia square ​

Square

The commitment scheme ​

Blobstream Commitment Diagram

So to prove inclusion of a share to a Celestia block, we use Blobstream as a source of truth. In a nutshell, Blobstream attests to the data posted to Celestia in the zk-Blobstream contract via verifying a zk-proof of the headers of a batch of Celestia blocks. Then, it keeps reference of that batch of blocks using the merkleized commitment of their (dataRoot, height) resulting in a data root tuple root. Check the above diagram which shows:

  • 0: those are the shares, that when unified, contain the PFB or the rollup data blob.
  • 1: the row and column roots are the namespace merkle tree roots over the shares. More information on the NMT in the NMT specs. These commit to the rows and columns containing the above shares.
  • 2: the data roots: which are the binary merkle tree commitment over the row and column roots. This means that if you can prove that a share is part of a row, using a namespace merkle proof. Then prove that this row is committed to by the data root. Then you can be sure that that share was published to the corresponding block.
  • 3: in order to batch multiple blocks into the same commitment, we create a commitment over the (dataRoot, height) tuple for a batch of blocks, which results in a data root tuple root. It's this commitment that gets stored in the Blobstream smart contract.

So, if we're able to prove:

  • That a share is part of a row, then that row is committed to by a data root.
  • Then, prove that that data root along with its height is committed to by the data root tuple root, which gets saved to the Blobstream contract.

We can be sure that that share was committed to in the corresponding Celestia block.

In this document, we will provide details on how to query the above proofs, and how to adapt them to be sent to a rollup contract for verification.

Hands-on demonstration ​

This part will provide the details of proof generation, and the way to make the results of the proofs queries ready to be consumed by the target rollup contract.

NOTE

For the go client snippets, make sure to have the following replaces in your go.mod:

go
// go.mod
     github.com/cosmos/cosmos-sdk => github.com/celestiaorg/cosmos-sdk v1.18.3-sdk-v0.46.14
     github.com/gogo/protobuf => github.com/regen-network/protobuf v1.3.3-alpha.regen.1
     github.com/syndtr/goleveldb => github.com/syndtr/goleveldb v1.0.1-0.20210819022825-2ae1ddf74ef7
@@ -162,7 +162,7 @@
 		os.Exit(1)
 	}
 	fmt.Println(dcProof.Proof.String())
-}

Full example of proving that a Celestia block was committed to by Blobstream contract ​

go
package main
+}

Full example of proving that a Celestia block was committed to by Blobstream contract ​

go
package main
 
 import (
 	"context"
@@ -1162,7 +1162,7 @@
 			NumLeaves: big.NewInt(dataRootInclusionProof.Total),
 		},
 	}
-}

With the nonce being the attestation nonce, which can be retrieved using Blobstream contract events. Check below for an example. And height being the Celestia Block height that contains the rollup data, along with the blockDataRoot being the data root of the block height. Finally, dataRootInclusionProof is the Celestia block data root inclusion proof to the data root tuple root that was queried at the beginning of this page.

If the dataRoot or the tupleRootNonce is unknown during the verification:

  • dataRoot: can be queried using the /block?height=15 query (15 in this example endpoint), and taking the data_hash field from the response.
  • tupleRootNonce: can be retried via querying the data commitment stored events from the Blobstream contract and looking for the nonce attesting to the corresponding data.

Querying the proof's tupleRootNonce ​

go
	// get the nonce corresponding to the block height that contains the PayForBlob transaction
+}

With the nonce being the attestation nonce, which can be retrieved using Blobstream contract events. Check below for an example. And height being the Celestia Block height that contains the rollup data, along with the blockDataRoot being the data root of the block height. Finally, dataRootInclusionProof is the Celestia block data root inclusion proof to the data root tuple root that was queried at the beginning of this page.

If the dataRoot or the tupleRootNonce is unknown during the verification:

  • dataRoot: can be queried using the /block?height=15 query (15 in this example endpoint), and taking the data_hash field from the response.
  • tupleRootNonce: can be retried via querying the data commitment stored events from the Blobstream contract and looking for the nonce attesting to the corresponding data.

Querying the proof's tupleRootNonce ​

go
	// get the nonce corresponding to the block height that contains the PayForBlob transaction
 	// since BlobstreamX emits events when new batches are submitted, we will query the events
 	// and look for the range committing to the blob
 	// first, connect to an EVM RPC endpoint
@@ -1286,7 +1286,7 @@
 import {
     sp1blobstreamwrapper "github.com/succinctlabs/sp1-blobstream/bindings"
 } 
-// and use the `BlobstreamDataCommitmentStored` event instead.

Listening for new data commitments ​

For listening for new data commitment stored events, sequencers can use the WatchDataCommitmentStored as follows:

go
    ethClient, err := ethclient.Dial("evm_rpc")
+// and use the `BlobstreamDataCommitmentStored` event instead.

Listening for new data commitments ​

For listening for new data commitment stored events, sequencers can use the WatchDataCommitmentStored as follows:

go
    ethClient, err := ethclient.Dial("evm_rpc")
     if err != nil {
 	    return err
     }
@@ -1404,7 +1404,7 @@
         // (4) verify invalid state transition
         // (5) effects
     }
-}

Then, you can submit the fraud proof using golang as follows:

go
package main
+}

Then, you can submit the fraud proof using golang as follows:

go
package main
 
 import (
 	"context"
@@ -1878,8 +1878,8 @@
 import {
     sp1blobstreamwrapper "github.com/succinctlabs/sp1-blobstream/bindings"
 } 
-// and use the `BlobstreamDataCommitmentStored` event instead.

For the step (2), check the rollup inclusion proofs documentation for more information.

For an example BlobstreamX project that uses the above proof queries, checkout the blobstreamx-example sample project.

Conclusion ​

After creating all the proofs, and verifying them:

  1. Verify inclusion proof of the transaction to Celestia data root
  2. Prove that the data root tuple is committed to by the Blobstream X smart contract

We can be sure that the data was published to Celestia, and then rollups can proceed with their normal fraud proving mechanism.

NOTE

The above proof constructions are implemented in Solidity, and may require different approaches in other programming languages.

- +// and use the `BlobstreamDataCommitmentStored` event instead.

For the step (2), check the rollup inclusion proofs documentation for more information.

For an example BlobstreamX project that uses the above proof queries, checkout the blobstreamx-example sample project.

Conclusion ​

After creating all the proofs, and verifying them:

  1. Verify inclusion proof of the transaction to Celestia data root
  2. Prove that the data root tuple is committed to by the Blobstream X smart contract

We can be sure that the data was published to Celestia, and then rollups can proceed with their normal fraud proving mechanism.

NOTE

The above proof constructions are implemented in Solidity, and may require different approaches in other programming languages.

+ \ No newline at end of file diff --git a/pr-1699/developers/blobstream-rollups.html b/pr-1699/developers/blobstream-rollups.html index 8626741a29..fe45f382d5 100644 --- a/pr-1699/developers/blobstream-rollups.html +++ b/pr-1699/developers/blobstream-rollups.html @@ -11,7 +11,7 @@ - + @@ -40,8 +40,8 @@

Introduction to Blobstream rollups ​

Blobstream is the first data availability solution for EVM chains that securely scales with the number of users. It allows rollups to post their data on Celestia while proving their availability in the rollup settlement contract.

This document will outline a few ways to build optimistic or zk-rollups that post their data to Celestia and use Blobstream to prove that data's availability.

Concepts ​

This section will go over two constructs that can be used in building Blobstream rollups. Each with its pros and cons and the rollup developer can choose which one suits their needs better.

Note: Only the sequence of spans method can be used currently to build Blobstream rollups. The blob share commitment way still requires some tooling that will be built in the upcoming months.

Blob share commitment ​

The blob share commitment is a commitment over the data contained in the MsgPayForBlobs transaction. This commitment allows proving that the corresponding data exists on Celestia efficiently.

Blob share commitment: Proof details ​

To prove that the data corresponding to a blob share commitment was posted to Celestia using Blobstream, the following proofs need to be verified:

  1. share inclusion proof to the blob share commitment: meaning creating two merkle proofs:
    1. share merkle proof up to the subtree root corresponding to that share
    2. subtree root merkle proof to the blob share commitment
  2. blob share commitment inclusion proof to the data root tuple root: meaning four merkle proofs:
    1. subtree roots merkle proofs to the blob share commitment: to make sure the subtree roots are valid
    2. subtree roots merkle proofs up to the row roots: to prove that the subtree roots belong to a set of rows in the Celestia block
    3. row roots proofs to the data root: to prove that those rows belong to the Celestia Block
    4. data root tuple proof to the data root tuple: to prove that the Celestia block referenced by its height and data root, was committed to by Blobstream.

More details on the blob share commitment inclusion proof can be found in the commitment scheme docs and also the data square layout.

If all of these proofs are valid, then you successfully managed to prove that the data corresponding to that blob share commitment has been posted to Celestia.

NOTE

Generating/verifying blob share commitment proofs is still not supported. It still needs tooling to generate the proofs on the node side, and verifying them on the Solidity side which will be built in the upcoming months.

Blob share commitment: Compact proofs ​

There is a way to have compact proofs, when using blob share commitments, unlike the ones defined above; that allow less costly inclusion proofs. These require the ability to parse the protobuf encoded PFBs.

In fact, if the rollup project has a way to parse the protobuf encoded PFB, either in a smart contract or a zk-circuit, they will be able to create compact proofs of the rollup data.

These proofs will work as follows:

  • Parsing the PFB and taking out the blob share commitment
  • Comparing the PFB commitment to the one saved in the rollup contract
  • Proving inclusion of the PFB to the data root tuple root. This will be a compact proof since we will only be proving two shares regardless of the size of the rollup data.

More details on compact proofs can be found in ADR-011.

Blob share commitment: Pros ​

The pros of referencing rollup data using a blob share commitment:

  • Using the same commitment that exists on the PFB, without having to find another way of referencing the rollup data.
  • If the team has access to protobuf parsing, it allows for compact proof, but the parsing costs need to be investigated.

Blob share commitment: Cons ​

  • Large/expensive proofs in the case of having no way to parse the protobuf PFB encoding.
  • In the optimistic rollups construction, defined below, this requires waiting for the Celestia block to be committed to by Blobstream before saving updating the settlement contract. This might require waiting for a few hours, depending on the batches size on each chain, to finally submit the rollup update.

Given these limitations, an alternative design will be discussed in the next section.

Sequence of spans ​

An alternative way of referencing rollup data in the rollup settlement contract is using a sequence of spans.

A sequence of spans is a data pointer that allows pointing to the rollup data inside a Celestia square using its location inside the square. It can be defined using the following information:

  • height: The height of the Celestia block containing the rollup data.
  • startIndex: The index of the first share containing the rollup data.
  • dataLen: The number of shares containing the rollup data.

The startIndex and the dataLen can be queried from Celestia after the corresponding transaction gets included in a block and committed to the chain. An example of how to query them can be found in the verify command. The TxShareRange returns the start and end share of the data referenced by a transaction hash.

NOTE

If the rollup data is submitted in multiple blocks, the above sequence of spans can be generalized to include multiple blocks. For simplicity, we will stick with the data only submitted to a single Celestia block.

Sequence of spans: Proof details ​

Using sequence of spans is different from using the blob share commitment because we're referencing a location in the square, and not actual data commitment. So, the proof types and their generation are different.

Sequence of spans: Proving unavailable data ​

By construction, if the sequence of spans refers to a certain location in the square, that location is the data. This location can be in the reserved namespaces, the parity bytes, etc. What matters is that it's part of the square. So to prove that the sequence of spans is invalid, i.e., refers to data that is not available on Celestia, it is necessary and sufficient to show that the sequence of spans doesn't belong to the Celestia block, i.e., the span is out of bounds.

We could create this proof via generating a binary Merkle proof of any row/column to the Celestia data root. This proof will provide the total which is the number of rows/columns in the extended data square. This can be used to calculate the square size. The computeSquareSizeFromRowProof method in the DAVerifier library allows calculating the square size from a row proof or a share proof.

Then, we will use that information to check if the provided share index, in the header, is out of the square size bounds. In order words, we will check if the startIndex and the startIndex + dataLen are included in the range [0, 4*square_size].

NOTE

The square size is the number of rows of the original square.

For the data root, we will use a binary Merkle proof to prove its inclusion in a data root tuple root that was committed to by the Blobstream smart contract. More on this in the data root inclusion proofs section.

Sequence of spans: Proving inclusion of some data ​

The difference between using a blob share commitment and a sequence of spans is that when using a blob share commitment, an extra merkle proof is needed to prove inclusion of the share to the blob share commitment. However, in the case of a sequence of spans, only the usual inclusion proof of a share to the data root tuple root is needed. The inclusion of the share to the sequence of spans is gotten using the same proof.

In fact, proving that a share is part of the sequence of spans, i.e., part of the rollup data is done as follows:

  1. Prove that the data root tuple is committed to by the Blobstream smart contract:

    To prove the data root is committed to by the Blobstream smart contract, we will need to provide a Merkle proof of the data root tuple to a data root tuple root. This can be created using the data_root_inclusion_proof query. More on this can be found in the data root inclusion proofs documentation.

  2. Verify inclusion proof of the data to Celestia data root:

    To prove that the data is part of the data root, we will need to provide two proofs: a namespace Merkle proof of the data to a row root. This could be done via proving the shares that contain the data to the row root using a namespace Merkle proof. And, a binary Merkle proof of the row root to the data root.

    These proofs can be generated using the ProveShares query.

    More details on these proofs can be found in the transaction inclusion proof documentation.

  3. Prove that the data is in the sequence spans:

    To prove that the data is part of the rollup sequence of spans, we take the authenticated share proofs in step (2) and use the shares begin/end key to define the shares' positions in the row.

    Then, we use the row proof to get the row index in the extended Celestia square and get the index of the share in row major order:

    solidity
    uint256 shareIndexInRow = shareProof.shareProofs[0].beginKey;
 uint256 shareIndexInRowMajorOrder = shareIndexInRow + shareProof.rowProofs[0].numLeaves * shareProof.rowProofs[0].key;
    uint256 shareIndexInRow = shareProof.shareProofs[0].beginKey;
-uint256 shareIndexInRowMajorOrder = shareIndexInRow + shareProof.rowProofs[0].numLeaves * shareProof.rowProofs[0].key;

Finally, we can compare the computed index with the sequence of spans, and be sure that the data/shares is part of the rollup data.

Sequence of spans: Pros ​

  • Using a sequence of spans instead of the blob share commitment allows for simpler proofs

Sequence of spans: Cons ​

None

Optimistic rollups ​

One type of rollups that can be built with Blobstream is optimistic rollups. An optimistic rollup is a rollup that commits optimistically to a set of blocks, and allows the other parties to verify that the blocks are valid, and if they're not, they can create fraud proofs to signal that.

Celestia allows optimistic rollups to post their data on its DA layer, and to prove that the data is available using Blobstream.

To build an optimistic rollup that uses Celestia as a DA layer, the following constructions can be inspired by.

Optimistic rollups that use a sequence of spans ​

Optimistic rollups can post their data in Celestia, then in the rollup settlement contract, they can reference optimistically that data using a sequence of spans. Then, rollup full nodes can verify if that data is valid. If not, they can trigger a fraud proof.

When using a sequence of spans, triggering the data availability fraud proofs, which are different from the state transitions fraud proofs (left for the rollup to define), goes back to the following cases:

Optimistic rollups that use a sequence of spans: Pros ​

  • Not needing to verify anything at the moment of submitting the commitments to the rollup settlement contracts
  • The fraud proofs are simple and can be reduced to a single share: if, for example, a single transaction in the rollup data that was posted to Celestia is faulty, only the shares containing that transaction, which can be as minimal as a single share, need to be proven on chain and verified.

Optimistic rollups that use a sequence of spans: Cons ​

None

Optimistic rollups that use a sequence of spans: Example ​

An example optimistic rollup that uses sequence of spans to reference its data can be found in the RollupInclusionProofs. It portrays the different possible data availability proofs, constructs them and shows how to verify them.

Also, more details on querying these kinds of proofs can be found in the proof queries documentation.

Optimistic rollups that use blob share commitments ​

Another way to build a rollup is to replace the sequence of spans with a height and a blob share commitment. Then, users/rollup full nodes will be able to query that data and validate it. If the rollup data is not valid, they can create a fraud proof.

The first difference between the sequence of spans construction and the share commitment construction is having to verify that the provided blob share commitment is part of the Celestia block, referenced by its height in the moment of submitting the rollup commitments to the settlement contract. This is necessary to make sure that the commitment is part of Celestia. Otherwise, rollup sequencers can commit to random blob share commitments and there won't be a way to prove they're invalid.

The second difference is the proof types. In the case of a fraud proof, the proofs outlined in the proofs details of blob share commitment section would need to be verified to be sure that the share containing the invalid state transition is part of the rollup data. Alternatively, the rollup settlement contract would need to have a library to parse protobuf encoded PFBs, as explained in the compact proofs of blob share commitment section, to have less expensive proofs. The cost of parsing the protobuf is not included in this analysis and needs to be investigated separately.

Optimistic rollups that use blob share commitments: Pros ​

  • Using the same blob share commitment as the one saved in Celestia which gives access to existing tooling

Optimistic rollups that use blob share commitments: Cons ​

  • The proofs are expensive in the base case. And if the settlement contract is able to parse the PFBs, thorough investigations of the cost of that would need to be done.

Zk-rollups ​

Zk-rollups, aka validity rollups, can also use Celestia as a DA and Blobstream to verify that the data was posted. However, the submission process is different from the above constructions, since there are no fraud proofs, and everything should be verified when submitting the commitment to the settlement contract.

Similar to the optimistic case, the rollup settlement contract can reference the rollup data using either the sequence of spans approach or the blob share commitments. We will discuss both in this section.

Zk-rollups that use sequence of spans ​

When submitting the commitments to the rollup settlement contract, this latter will need to verify the following:

  1. Zk-proof of the state transitions, which is left for the rollup to define.
  2. Verify that the sequence of spans is valid, i.e., is part of the Celestia block referenced by its height, as described in the proof details section.
  3. Zk-proof of the rollup data to the data root. The verification process of this should accept a commitment as input so that the settlement contract makes sure it's the correct value that's being saved. The commitment can be the data root and the sequence of spans. And, when the rollup data is proven inside the circuit to the data root, the used data root is asserted to be the input one. Similarly, the data's location is asserted to be the same as the input sequence of spans. These arguments are the ones used in the sequence of spans verification in (2).

Once these are valid, the settlement contract can be sure that the rollup data was posted to Celestia, and the sequence of spans references it correctly.

Zk-rollups that use sequence of spans: Pros ​

  • The inclusion proof inside the zk-circuit is a simple proof that uses traditional merkle tree. In the case of using blob share commitment, as will be explained below, additional libraries that can be expensive to prove are required.

Zk-rollups that use sequence of spans: Cons ​

None

Zk-rollups that use blob share commitments ​

To use blob share commitments to reference rollup data in the zk-rollup settlement contract, the zk-circuits need to be able to deserialize protobuf encoded messages. Alternatively, more involved merkle proofs will need to be verified.

Protobuf deserialization inside a zk-circuit ​

One way of using the blob share commitment to reference the rollup data in zk-rollups is via using a protobuf deserialization library inside the zk-circuit. And the verification would proceed as follows:

  1. Zk-proof of the state transitions, which is left to the rollup team to define.
  2. Verify that the blob share commitment is valid using the proofs laid out in the proof details of blob share commitment section.
  3. The zk-proof verifier would take as argument the data root and the blob share commitment. Then, inside the circuit, the protobuf encoded PFB transaction will be deserialized and then verify the following:
  • The deserialized blob share commitment is the same as the one provided as input
  • The circuit will prove the inclusion of the PFB to the data root, then assert that the data root is the same as the one provided as input.

If the above conditions are valid, the rollup settlement contract can be sure that the rollup data was posted to Celestia and is correctly referenced.

Zk-rollups that use blob share commitments: Pros ​

None

Zk-rollups that use blob share commitments: Cons ​

  • This approach requires having access to a protobuf decoder inside a zk-circuit which is not straightforward to have. Also, the relative costs will need to be investigated.

Heavy merkle proofs usage ​

Similar to Protobuf deserialization inside a zk-circuit, the zk-circuit will proceed to the verification of the availability of the data. The difference is that instead of parsing the encoded protobuf, the proofs defined under the blob share commitment proof details section will need to be verified inside the zk-circuit as follows:

  1. Zk-proof of the state transitions, which is left to the rollup team to define.
  2. Verify that the blob share commitment is valid using the proofs laid out in the blob share commitment proof details section.
  3. The zk-proof verifier would take as argument the data root and the blob share commitment. Then, inside the circuit:
  • It will verify that the input blob share commitment corresponds to the rollup data.
  • Verify that the input data root commits to that blob share commitment. Check the blob share commitment proof details for more details

Once these proofs are valid, the rollup settlement contract can be sure that the rollup data was posted to Celestia and is correctly referenced.

heavy merkle proofs usage: Pros ​

None

heavy merkle proofs usage: Cons ​

  • More heavy usage of merkle proofs inside and outside the zk-circuit.

Conclusion ​

Given the above details, using the sequence of spans is the better solution in the general case as explained in the optimistic rollups that uses a sequence of spans and zk-rollups that use sequence of spans sections. The proof sizes are small and allow for greater flexibility. However, if the rollup team has different requirements, then the other designs can be explored.

FAQ ​

Should I use the Celestia transaction hash to reference the rollup data? ​

This is asked a lot since it's the most intuitive way of referencing data. However, in Celestia, referencing the data using the transaction hash is not recommended.

A transaction proof in Celestia goes back to providing an inclusion proof of the shares containing the transaction. This means if the transaction hash is used to reference data in a Celestia block, the rollup verification mechanism should do the following:

  • Verify an inclusion proof of the shares comprising the transaction up to the data root tuple root
  • Decode those shares and parse the transaction, then hash its components to generate the transaction hash
  • Verify that the generated transaction hash matches the one used to reference the data

At this level, the transaction hash is authenticated and the verification contract has the shares of the transaction. Then, the verification contract needs to take the share commitment from the parsed transaction and follow the steps outlined in the blob share commitment section.

As observed, using the transaction hash is expensive and doesn't yield any advantages over using the blob share commitment, which in turn is more expensive than using the sequence of spans.

So, unless there are more reasons to use the transaction hash to reference the rollup data, the sequence of spans approach remains better.

- +uint256 shareIndexInRowMajorOrder = shareIndexInRow + shareProof.rowProofs[0].numLeaves * shareProof.rowProofs[0].key;

Finally, we can compare the computed index with the sequence of spans, and be sure that the data/shares is part of the rollup data.

Sequence of spans: Pros ​

  • Using a sequence of spans instead of the blob share commitment allows for simpler proofs

Sequence of spans: Cons ​

None

Optimistic rollups ​

One type of rollups that can be built with Blobstream is optimistic rollups. An optimistic rollup is a rollup that commits optimistically to a set of blocks, and allows the other parties to verify that the blocks are valid, and if they're not, they can create fraud proofs to signal that.

Celestia allows optimistic rollups to post their data on its DA layer, and to prove that the data is available using Blobstream.

To build an optimistic rollup that uses Celestia as a DA layer, the following constructions can be inspired by.

Optimistic rollups that use a sequence of spans ​

Optimistic rollups can post their data in Celestia, then in the rollup settlement contract, they can reference optimistically that data using a sequence of spans. Then, rollup full nodes can verify if that data is valid. If not, they can trigger a fraud proof.

When using a sequence of spans, triggering the data availability fraud proofs, which are different from the state transitions fraud proofs (left for the rollup to define), goes back to the following cases:

Optimistic rollups that use a sequence of spans: Pros ​

  • Not needing to verify anything at the moment of submitting the commitments to the rollup settlement contracts
  • The fraud proofs are simple and can be reduced to a single share: if, for example, a single transaction in the rollup data that was posted to Celestia is faulty, only the shares containing that transaction, which can be as minimal as a single share, need to be proven on chain and verified.

Optimistic rollups that use a sequence of spans: Cons ​

None

Optimistic rollups that use a sequence of spans: Example ​

An example optimistic rollup that uses sequence of spans to reference its data can be found in the RollupInclusionProofs. It portrays the different possible data availability proofs, constructs them and shows how to verify them.

Also, more details on querying these kinds of proofs can be found in the proof queries documentation.

Optimistic rollups that use blob share commitments ​

Another way to build a rollup is to replace the sequence of spans with a height and a blob share commitment. Then, users/rollup full nodes will be able to query that data and validate it. If the rollup data is not valid, they can create a fraud proof.

The first difference between the sequence of spans construction and the share commitment construction is having to verify that the provided blob share commitment is part of the Celestia block, referenced by its height in the moment of submitting the rollup commitments to the settlement contract. This is necessary to make sure that the commitment is part of Celestia. Otherwise, rollup sequencers can commit to random blob share commitments and there won't be a way to prove they're invalid.

The second difference is the proof types. In the case of a fraud proof, the proofs outlined in the proofs details of blob share commitment section would need to be verified to be sure that the share containing the invalid state transition is part of the rollup data. Alternatively, the rollup settlement contract would need to have a library to parse protobuf encoded PFBs, as explained in the compact proofs of blob share commitment section, to have less expensive proofs. The cost of parsing the protobuf is not included in this analysis and needs to be investigated separately.

Optimistic rollups that use blob share commitments: Pros ​

  • Using the same blob share commitment as the one saved in Celestia which gives access to existing tooling

Optimistic rollups that use blob share commitments: Cons ​

  • The proofs are expensive in the base case. And if the settlement contract is able to parse the PFBs, thorough investigations of the cost of that would need to be done.

Zk-rollups ​

Zk-rollups, aka validity rollups, can also use Celestia as a DA and Blobstream to verify that the data was posted. However, the submission process is different from the above constructions, since there are no fraud proofs, and everything should be verified when submitting the commitment to the settlement contract.

Similar to the optimistic case, the rollup settlement contract can reference the rollup data using either the sequence of spans approach or the blob share commitments. We will discuss both in this section.

Zk-rollups that use sequence of spans ​

When submitting the commitments to the rollup settlement contract, this latter will need to verify the following:

  1. Zk-proof of the state transitions, which is left for the rollup to define.
  2. Verify that the sequence of spans is valid, i.e., is part of the Celestia block referenced by its height, as described in the proof details section.
  3. Zk-proof of the rollup data to the data root. The verification process of this should accept a commitment as input so that the settlement contract makes sure it's the correct value that's being saved. The commitment can be the data root and the sequence of spans. And, when the rollup data is proven inside the circuit to the data root, the used data root is asserted to be the input one. Similarly, the data's location is asserted to be the same as the input sequence of spans. These arguments are the ones used in the sequence of spans verification in (2).

Once these are valid, the settlement contract can be sure that the rollup data was posted to Celestia, and the sequence of spans references it correctly.

Zk-rollups that use sequence of spans: Pros ​

  • The inclusion proof inside the zk-circuit is a simple proof that uses traditional merkle tree. In the case of using blob share commitment, as will be explained below, additional libraries that can be expensive to prove are required.

Zk-rollups that use sequence of spans: Cons ​

None

Zk-rollups that use blob share commitments ​

To use blob share commitments to reference rollup data in the zk-rollup settlement contract, the zk-circuits need to be able to deserialize protobuf encoded messages. Alternatively, more involved merkle proofs will need to be verified.

Protobuf deserialization inside a zk-circuit ​

One way of using the blob share commitment to reference the rollup data in zk-rollups is via using a protobuf deserialization library inside the zk-circuit. And the verification would proceed as follows:

  1. Zk-proof of the state transitions, which is left to the rollup team to define.
  2. Verify that the blob share commitment is valid using the proofs laid out in the proof details of blob share commitment section.
  3. The zk-proof verifier would take as argument the data root and the blob share commitment. Then, inside the circuit, the protobuf encoded PFB transaction will be deserialized and then verify the following:
  • The deserialized blob share commitment is the same as the one provided as input
  • The circuit will prove the inclusion of the PFB to the data root, then assert that the data root is the same as the one provided as input.

If the above conditions are valid, the rollup settlement contract can be sure that the rollup data was posted to Celestia and is correctly referenced.

Zk-rollups that use blob share commitments: Pros ​

None

Zk-rollups that use blob share commitments: Cons ​

  • This approach requires having access to a protobuf decoder inside a zk-circuit which is not straightforward to have. Also, the relative costs will need to be investigated.

Heavy merkle proofs usage ​

Similar to Protobuf deserialization inside a zk-circuit, the zk-circuit will proceed to the verification of the availability of the data. The difference is that instead of parsing the encoded protobuf, the proofs defined under the blob share commitment proof details section will need to be verified inside the zk-circuit as follows:

  1. Zk-proof of the state transitions, which is left to the rollup team to define.
  2. Verify that the blob share commitment is valid using the proofs laid out in the blob share commitment proof details section.
  3. The zk-proof verifier would take as argument the data root and the blob share commitment. Then, inside the circuit:
  • It will verify that the input blob share commitment corresponds to the rollup data.
  • Verify that the input data root commits to that blob share commitment. Check the blob share commitment proof details for more details

Once these proofs are valid, the rollup settlement contract can be sure that the rollup data was posted to Celestia and is correctly referenced.

heavy merkle proofs usage: Pros ​

None

heavy merkle proofs usage: Cons ​

  • More heavy usage of merkle proofs inside and outside the zk-circuit.

Conclusion ​

Given the above details, using the sequence of spans is the better solution in the general case as explained in the optimistic rollups that uses a sequence of spans and zk-rollups that use sequence of spans sections. The proof sizes are small and allow for greater flexibility. However, if the rollup team has different requirements, then the other designs can be explored.

FAQ ​

Should I use the Celestia transaction hash to reference the rollup data? ​

This is asked a lot since it's the most intuitive way of referencing data. However, in Celestia, referencing the data using the transaction hash is not recommended.

A transaction proof in Celestia goes back to providing an inclusion proof of the shares containing the transaction. This means if the transaction hash is used to reference data in a Celestia block, the rollup verification mechanism should do the following:

  • Verify an inclusion proof of the shares comprising the transaction up to the data root tuple root
  • Decode those shares and parse the transaction, then hash its components to generate the transaction hash
  • Verify that the generated transaction hash matches the one used to reference the data

At this level, the transaction hash is authenticated and the verification contract has the shares of the transaction. Then, the verification contract needs to take the share commitment from the parsed transaction and follow the steps outlined in the blob share commitment section.

As observed, using the transaction hash is expensive and doesn't yield any advantages over using the blob share commitment, which in turn is more expensive than using the sequence of spans.

So, unless there are more reasons to use the transaction hash to reference the rollup data, the sequence of spans approach remains better.

+ \ No newline at end of file diff --git a/pr-1699/developers/blobstream-x-deploy.html b/pr-1699/developers/blobstream-x-deploy.html index 56ac87c55b..3680c76d00 100644 --- a/pr-1699/developers/blobstream-x-deploy.html +++ b/pr-1699/developers/blobstream-x-deploy.html @@ -11,7 +11,7 @@ - + @@ -210,8 +210,8 @@ # ^ This copies the verifier build to the blobstreamx folder mkdir -p build && RUST_LOG=debug cargo run --bin header_range_1024 --release build --wrapper-path verifier-build/ && mv ./target/release/header_range_1024 ./build/header_range_1024 ls build -# ^ should return something like: 0x007d0b2a2e2b013612e8.circuit 0x9039e58b2089e5f9abbb.circuit 0xce1636cfaf2bd5497c11.circuit FunctionVerifier.sol main.circuit 0x8e1ede4ce0865b41d714.circuit 0xa2140c9bde000dc5e21e.circuit 0xf6759ff933786ddacb92.circuit header_range_1024

The header_range_1024 is a specific circuit. Other circuit names can be used there. The current circuits that we have for BlobstreamX:

  • header_range_1024: skip function circuit for batches that are <= 1024 block.
  • header_range_2048: skip function circuit for batches that are <= 2048 block.
  • next_header: step function circuit.

All the deployments currently rely on two circuits: a header range circuit, either the 1024 or the 2048, depending on the frequency of the batches; The 1024 is mainly for batches that are at a ~1hr frequency and the 2048 for batches that are at a ~3-4hr frequency; and a next header circuit. So, if you're re-building the circuits, make sure to build the correct two circuits for your target deployment.

Now, if you check the build folder, you will find a file called FunctionVerifier.sol, which is the function verifier contract for your circuit that you can deploy on-chain.

Also, you will find the header_range_1024 under build folder which is the binary used to generate the proofs. It is mainly used by the operator to generate the plonky2x proofs that will be PLONK wrapped later using the generated verifier-build.

At this level, you can deploy the FunctionVerifier.sol onchain, then register it in the SuccinctGateway, then use the generated header_range_1024 circuit and the verifier to generate the proofs and submit them onchain. These steps are detailed in the previous section.

NOTE: In a scaleway instance of 64CPU and 504G RAM, the build takes ~10 minutes to complete. Make sure to run it on a beefy machine.

- +# ^ should return something like: 0x007d0b2a2e2b013612e8.circuit 0x9039e58b2089e5f9abbb.circuit 0xce1636cfaf2bd5497c11.circuit FunctionVerifier.sol main.circuit 0x8e1ede4ce0865b41d714.circuit 0xa2140c9bde000dc5e21e.circuit 0xf6759ff933786ddacb92.circuit header_range_1024

The header_range_1024 is a specific circuit. Other circuit names can be used there. The current circuits that we have for BlobstreamX:

  • header_range_1024: skip function circuit for batches that are <= 1024 block.
  • header_range_2048: skip function circuit for batches that are <= 2048 block.
  • next_header: step function circuit.

All the deployments currently rely on two circuits: a header range circuit, either the 1024 or the 2048, depending on the frequency of the batches; The 1024 is mainly for batches that are at a ~1hr frequency and the 2048 for batches that are at a ~3-4hr frequency; and a next header circuit. So, if you're re-building the circuits, make sure to build the correct two circuits for your target deployment.

Now, if you check the build folder, you will find a file called FunctionVerifier.sol, which is the function verifier contract for your circuit that you can deploy on-chain.

Also, you will find the header_range_1024 under build folder which is the binary used to generate the proofs. It is mainly used by the operator to generate the plonky2x proofs that will be PLONK wrapped later using the generated verifier-build.

At this level, you can deploy the FunctionVerifier.sol onchain, then register it in the SuccinctGateway, then use the generated header_range_1024 circuit and the verifier to generate the proofs and submit them onchain. These steps are detailed in the previous section.

NOTE: In a scaleway instance of 64CPU and 504G RAM, the build takes ~10 minutes to complete. Make sure to run it on a beefy machine.

+ \ No newline at end of file diff --git a/pr-1699/developers/blobstream-x-requesting-data-commitment-ranges.html b/pr-1699/developers/blobstream-x-requesting-data-commitment-ranges.html index 52b3bbbce6..30c71b5352 100644 --- a/pr-1699/developers/blobstream-x-requesting-data-commitment-ranges.html +++ b/pr-1699/developers/blobstream-x-requesting-data-commitment-ranges.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Requesting data commitment ranges ​

By default, the Blobstream X deployments on Ethereum will be updated every 4 hours, and on Arbitrum One and Base, updating every 1 hour. If you wish for the Blobstream X contract to be updated at a different cadence, then you have several different options for how to update the smart contract.

To request proofs to be submitted to the Blobstream X contract at a different cadence, you can do one of the following:

NOTE: The requested proof ranges cannot include blocks that were already used in a previous batch. The ranges should start from the last proven block, aka, latest_block and they should end in a block already committed by Celestia. In other words, it's the end-inclusive range defined by [latest_block, target_block] with target_block <= Celestia tip.

Local proving ​

To run the Blobstream X operator with local proving, follow this guide.

Local proving allows self-generating the proofs and submitting them to an existing BlobstreamX contract. Alternatively, if a team needs a very specific cadence that starts at very specific heights, they can deploy their own BlobstreamX contract and submit proofs to it. Deployment instructions can be found in the BlobstreamX deploy documentation.

::: Note Requires a large cloud machine to run in a reasonable amount of time. EC2 r6a.16xlarge, i.e., 64CPU 512GB RAM, takes ~30 minutes to generate a header range proof. :::

Request proofs from the Succinct platform ​

NOTE: Requesting a proof from the succinct platform requires having a Succinct API key. It can be requested using this form.

Run the Blobstream X operator with hosted proving on the Succinct platform, by running an operator script that pings the platform with proof requests at a specified cadence.

Follow these instructions to run the operator script.

Here are example values for the .env file:

  1. TENDERMINT_RPC_URL from the public Celestia list.
  2. SUCCINCT_RPC_URL = https://alpha.succinct.xyz/api
  3. Request for SUCCINCT_API_KEY from the Succinct team.
  4. CHAIN_ID is the chain ID of the deployed Blobstream X contract.
  5. CONTRACT_ADDRESS: Blobstream X proxy contract address.
  6. NEXT_HEADER_FUNCTION_ID & HEADER_RANGE_FUNCTION_ID: Get the functionId's from the Blobstream X contract by using the nextHeaderFunctionId and headerRangeFunctionId respectively, which are public storage variables.

Request proofs onchain ​

Directly request a proof via the Blobstream X contract interface. Unlike the Blobstream X operator which handles requests off-chain, requesting on-chain requires gas, but the proof will be generated and relayed by the Succinct platform.

  1. Call requestHeaderRange(uint64 _targetBlock) with the end of the range you want a commitment for.

  2. A DataCommitmentStored(uint256, uint64, uint64, bytes32) will be emitted for the requested range when it is stored in the contract. Listen to this event to know that the proof has been generated successfully.

- +

Requesting data commitment ranges ​

By default, the Blobstream X deployments on Ethereum will be updated every 4 hours, and on Arbitrum One and Base, updating every 1 hour. If you wish for the Blobstream X contract to be updated at a different cadence, then you have several different options for how to update the smart contract.

To request proofs to be submitted to the Blobstream X contract at a different cadence, you can do one of the following:

NOTE: The requested proof ranges cannot include blocks that were already used in a previous batch. The ranges should start from the last proven block, aka, latest_block and they should end in a block already committed by Celestia. In other words, it's the end-inclusive range defined by [latest_block, target_block] with target_block <= Celestia tip.

Local proving ​

To run the Blobstream X operator with local proving, follow this guide.

Local proving allows self-generating the proofs and submitting them to an existing BlobstreamX contract. Alternatively, if a team needs a very specific cadence that starts at very specific heights, they can deploy their own BlobstreamX contract and submit proofs to it. Deployment instructions can be found in the BlobstreamX deploy documentation.

::: Note Requires a large cloud machine to run in a reasonable amount of time. EC2 r6a.16xlarge, i.e., 64CPU 512GB RAM, takes ~30 minutes to generate a header range proof. :::

Request proofs from the Succinct platform ​

NOTE: Requesting a proof from the succinct platform requires having a Succinct API key. It can be requested using this form.

Run the Blobstream X operator with hosted proving on the Succinct platform, by running an operator script that pings the platform with proof requests at a specified cadence.

Follow these instructions to run the operator script.

Here are example values for the .env file:

  1. TENDERMINT_RPC_URL from the public Celestia list.
  2. SUCCINCT_RPC_URL = https://alpha.succinct.xyz/api
  3. Request for SUCCINCT_API_KEY from the Succinct team.
  4. CHAIN_ID is the chain ID of the deployed Blobstream X contract.
  5. CONTRACT_ADDRESS: Blobstream X proxy contract address.
  6. NEXT_HEADER_FUNCTION_ID & HEADER_RANGE_FUNCTION_ID: Get the functionId's from the Blobstream X contract by using the nextHeaderFunctionId and headerRangeFunctionId respectively, which are public storage variables.

Request proofs onchain ​

Directly request a proof via the Blobstream X contract interface. Unlike the Blobstream X operator which handles requests off-chain, requesting on-chain requires gas, but the proof will be generated and relayed by the Succinct platform.

  1. Call requestHeaderRange(uint64 _targetBlock) with the end of the range you want a commitment for.

  2. A DataCommitmentStored(uint256, uint64, uint64, bytes32) will be emitted for the requested range when it is stored in the contract. Listen to this event to know that the proof has been generated successfully.

+ \ No newline at end of file diff --git a/pr-1699/developers/blobstream.html b/pr-1699/developers/blobstream.html index 7d79c0ceb9..cec4c0f63e 100644 --- a/pr-1699/developers/blobstream.html +++ b/pr-1699/developers/blobstream.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Blobstream: Streaming modular DA to Ethereum ​

Blobstream logo

What is Blobstream? ​

Blobstream is the first data availability solution for Ethereum that securely scales with the number of users. Formerly known as the Quantum Gravity Bridge (QGB), Blobstream relays commitments to Celestia's data root to an onchain light client on Ethereum, for integration by developers into L2 contracts. This enables Ethereum developers to build high-throughput L2s using Celestia's optimised DA layer, the first with Data Availability Sampling (DAS). Any ecosystem can deploy a Blobstream light client onchain to allow L2s and L3s to access DA from Celestia.

An implementation of Blobstream, by Succinct, called Blobstream X, is out and will be used in the upcoming deployments. This implementation proves the validity of Celestia block headers on a target EVM chain using zero-knowledge (ZK) proofs, which allow inheriting all the security guarantees of Celestia.

The latest implementation of Blobstream X is SP1 Blobstream, which is written in Rust for the SP1 zkVM. SP1 Blobstream offers improved performance and efficiency while maintaining the security guarantees of the original Blobstream X.

Please note: Blobstream remains early-stage, experimental software and users should use Blobstream at their own risk.

Implementations of Blobstream ​

Blobstream vs. data availability committees (DACs) ​

Decentralization and security ​

Blobstream is built on Celestia, which uses a CometBFT-based proof-of-stake system. Blobstream shares the same security assumptions as Celestia. In contrast, data availability committees (DACs), are typically centralized or semi-centralized, relying on a specific set of entities or individuals to vouch for data availability.

Mechanism of verification ​

Blobstream uses data availability attestations, which are Merkle roots of the batched L2 data, to confirm that the necessary data is present on Celestia. The L2 contract on Ethereum can check directly with Blobstream if the data is published on Celestia. Similarly, a DAC would rely on attestations or confirmations from its permissioned members.

Flexibility and scalability ​

Blobstream is designed to offer high-throughput data availability for Ethereum L2s, aiming to strike a balance between scalability and security. It operates independently of Ethereum's gas costs, as Celestia's resource pricing is more byte-focused rather than computation-centric. On the other hand, the scalability and flexibility of a DAC would depend on its specific design and implementation.

In summary, both Blobstream and DACs aim to ensure offchain data availability, but Blobstream offers a more decentralized, secure, and scalable solution compared to the potential centralized nature of DACs.

What is SP1 Blobstream? ​

SP1 Blobstream is the latest implementation of Blobstream in Rust using the SP1 zkVM.

SP1 Blobstream is the latest implementation of Blobstream with a ZK light client that bridges Celestia’s modular DA layer to Ethereum to allow high-throughput rollups to use Celestia’s DA while settling on Ethereum.

Optimistic or ZK rollups that settle on Ethereum, but wish to use Celestia for DA, require a mechanism for bridging Celestia’s data root to Ethereum as part of the settlement process. This data root is used during inclusion proofs to prove that particular rollup transactions were included and made available in the Celestia network.

Bridging Celestia’s data root to Ethereum requires running a Celestia light client as a smart contract on Ethereum, to make the latest state of the Celestia chain known on Ethereum and available to rollups. SP1 Blobstream uses the latest advances in ZK proofs to generate a succinct proof that enough Celestia validators have come to consensus (according to the CometBFT consensus protocol) on a block header, and verifies this proof in the SP1 Blobstream Ethereum smart contract to update it with the latest Celestia header.

The SP1 Blobstream ZK proof not only verifies the consensus of Celestia validators, but it also merkelizes and hashes all the data roots in the block range from the previous update to the current update, making accessible all Celestia data roots (verifiable with a Merkle inclusion proof against the stored Merkle root) to rollups.

If you're looking to deploy SP1 blobstream to a new chain, see new Sp1 Blobstream deployments.

Learn more at the sp1-blobstream repo.

NOTE

The current Blobstream deployments all use SP1 Blobstream.

Integrate with SP1 Blobstream ​

The following docs go over how developers can integrate SP1 Blobstream.

You can find the repository for SP1 Blobstream along with code for:

The first deployments of SP1 Blobstream will be maintained on the following chains: Arbitrum One, Base and Ethereum Mainnet. Every 1 hour, the prover/relayer will post an update to the Blobstream contract that will include a new data commitment range that covers a 1-hour block range from the latestBlock in the contract. On Ethereum Mainnet, the contract will be updated every 4 hours.

How to integrate with Blobstream ​

Integrating your L2 with Blobstream requires two components: your onchain smart contract logic, and your offchain client logic for your rollup. The next three sections cover these topics:

Blobstream rollups ​

More on the different ways to build a blobstream rollup can be found in the blobstream rollups documentation.

Deployed contracts ​

You can interact with the SP1 Blobstream contracts today. The SP1 Blobstream Solidity smart contracts are currently deployed on the following chains:

ContractEVM networkContract addressAttested data on CelestiaLink to Celenium
SP1 BlobstreamEthereum Mainnet0x7Cf3876F681Dbb6EdA8f6FfC45D66B996Df08fAeMainnet BetaDeployment on Celenium
SP1 BlobstreamArbitrum One0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794Mainnet BetaDeployment on Celenium
SP1 BlobstreamBase0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794Mainnet BetaDeployment on Celenium
SP1 BlobstreamSepolia0xf0c6429ebab2e7dc6e05dafb61128be21f13cb1eMocha testnetDeployment on Celenium
SP1 BlobstreamArbitrum Sepolia0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2Mocha testnetDeployment on Celenium
SP1 BlobstreamBase Sepolia0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2Mocha testnetDeployment on Celenium
- +

Blobstream: Streaming modular DA to Ethereum ​

Blobstream logo

What is Blobstream? ​

Blobstream is the first data availability solution for Ethereum that securely scales with the number of users. Formerly known as the Quantum Gravity Bridge (QGB), Blobstream relays commitments to Celestia's data root to an onchain light client on Ethereum, for integration by developers into L2 contracts. This enables Ethereum developers to build high-throughput L2s using Celestia's optimised DA layer, the first with Data Availability Sampling (DAS). Any ecosystem can deploy a Blobstream light client onchain to allow L2s and L3s to access DA from Celestia.

An implementation of Blobstream, by Succinct, called Blobstream X, is out and will be used in the upcoming deployments. This implementation proves the validity of Celestia block headers on a target EVM chain using zero-knowledge (ZK) proofs, which allow inheriting all the security guarantees of Celestia.

The latest implementation of Blobstream X is SP1 Blobstream, which is written in Rust for the SP1 zkVM. SP1 Blobstream offers improved performance and efficiency while maintaining the security guarantees of the original Blobstream X.

Please note: Blobstream remains early-stage, experimental software and users should use Blobstream at their own risk.

Implementations of Blobstream ​

Blobstream vs. data availability committees (DACs) ​

Decentralization and security ​

Blobstream is built on Celestia, which uses a CometBFT-based proof-of-stake system. Blobstream shares the same security assumptions as Celestia. In contrast, data availability committees (DACs), are typically centralized or semi-centralized, relying on a specific set of entities or individuals to vouch for data availability.

Mechanism of verification ​

Blobstream uses data availability attestations, which are Merkle roots of the batched L2 data, to confirm that the necessary data is present on Celestia. The L2 contract on Ethereum can check directly with Blobstream if the data is published on Celestia. Similarly, a DAC would rely on attestations or confirmations from its permissioned members.

Flexibility and scalability ​

Blobstream is designed to offer high-throughput data availability for Ethereum L2s, aiming to strike a balance between scalability and security. It operates independently of Ethereum's gas costs, as Celestia's resource pricing is more byte-focused rather than computation-centric. On the other hand, the scalability and flexibility of a DAC would depend on its specific design and implementation.

In summary, both Blobstream and DACs aim to ensure offchain data availability, but Blobstream offers a more decentralized, secure, and scalable solution compared to the potential centralized nature of DACs.

What is SP1 Blobstream? ​

SP1 Blobstream is the latest implementation of Blobstream in Rust using the SP1 zkVM.

SP1 Blobstream is the latest implementation of Blobstream with a ZK light client that bridges Celestia’s modular DA layer to Ethereum to allow high-throughput rollups to use Celestia’s DA while settling on Ethereum.

Optimistic or ZK rollups that settle on Ethereum, but wish to use Celestia for DA, require a mechanism for bridging Celestia’s data root to Ethereum as part of the settlement process. This data root is used during inclusion proofs to prove that particular rollup transactions were included and made available in the Celestia network.

Bridging Celestia’s data root to Ethereum requires running a Celestia light client as a smart contract on Ethereum, to make the latest state of the Celestia chain known on Ethereum and available to rollups. SP1 Blobstream uses the latest advances in ZK proofs to generate a succinct proof that enough Celestia validators have come to consensus (according to the CometBFT consensus protocol) on a block header, and verifies this proof in the SP1 Blobstream Ethereum smart contract to update it with the latest Celestia header.

The SP1 Blobstream ZK proof not only verifies the consensus of Celestia validators, but it also merkelizes and hashes all the data roots in the block range from the previous update to the current update, making accessible all Celestia data roots (verifiable with a Merkle inclusion proof against the stored Merkle root) to rollups.

If you're looking to deploy SP1 blobstream to a new chain, see new Sp1 Blobstream deployments.

Learn more at the sp1-blobstream repo.

NOTE

The current Blobstream deployments all use SP1 Blobstream.

Integrate with SP1 Blobstream ​

The following docs go over how developers can integrate SP1 Blobstream.

You can find the repository for SP1 Blobstream along with code for:

The first deployments of SP1 Blobstream will be maintained on the following chains: Arbitrum One, Base and Ethereum Mainnet. Every 1 hour, the prover/relayer will post an update to the Blobstream contract that will include a new data commitment range that covers a 1-hour block range from the latestBlock in the contract. On Ethereum Mainnet, the contract will be updated every 4 hours.

How to integrate with Blobstream ​

Integrating your L2 with Blobstream requires two components: your onchain smart contract logic, and your offchain client logic for your rollup. The next three sections cover these topics:

Blobstream rollups ​

More on the different ways to build a blobstream rollup can be found in the blobstream rollups documentation.

Deployed contracts ​

You can interact with the SP1 Blobstream contracts today. The SP1 Blobstream Solidity smart contracts are currently deployed on the following chains:

ContractEVM networkContract addressAttested data on CelestiaLink to Celenium
SP1 BlobstreamEthereum Mainnet0x7Cf3876F681Dbb6EdA8f6FfC45D66B996Df08fAeMainnet BetaDeployment on Celenium
SP1 BlobstreamArbitrum One0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794Mainnet BetaDeployment on Celenium
SP1 BlobstreamBase0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794Mainnet BetaDeployment on Celenium
SP1 BlobstreamSepolia0xf0c6429ebab2e7dc6e05dafb61128be21f13cb1eMocha testnetDeployment on Celenium
SP1 BlobstreamArbitrum Sepolia0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2Mocha testnetDeployment on Celenium
SP1 BlobstreamBase Sepolia0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2Mocha testnetDeployment on Celenium
+ \ No newline at end of file diff --git a/pr-1699/developers/blobstreamx.html b/pr-1699/developers/blobstreamx.html index f602025c76..dc5f09fe27 100644 --- a/pr-1699/developers/blobstreamx.html +++ b/pr-1699/developers/blobstreamx.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

BlobstreamX: the previous zk implementation of Blobstream ​

blobstream x draft diagram

What is Blobstream X? ​

Blobstream X is the previous implementation of Blobstream. It uses plonky2x to create circuits that verify the Celestia consensus and generate the corresponding proofs.

Blobstream X is built and deployed with Succinct's protocol.

NOTE

The Blobstream deployments below don't use the BlobstreamX circuits.

You can find the repository for Blobstream X along with code for:

NOTE

Custom ranges can be requested using the BlobstreamX contract to create proofs for specific Celestia block batches. These ranges can be constructed as [latestBlock, customTargetBlock), with latestBlock as the latest block height that was committed to by the BlobstreamX contract, and latestBlock > customTargetBlock, and customTargetBlock - latestBlock <= DATA_COMMITMENT_MAX.

Block ranges that are before the contract's latestBlock can't be proven a second time in different batches.

More information can be found in the requestHeaderRange(...) method.

How Blobstream X works ​

As shown in the diagram below, the entrypoint for updates to the Blobstream X contract is through the SuccinctGateway smart contract, which is a simple entrypoint contract that verifies proofs (against a deployed onchain verifier for the Blobstream X circuit) and then calls the BlobstreamX.sol contract to update it. Find more information about the SuccinctGateway.

blobstream x overview diagram draft

NOTE

If the Blobstream X contract is not deployed on a desired chain, it needs to be deployed before it can be used by your rollup. See the deployment documentation for more details.

Deploy Blobstream X ​

It is possible to deploy and maintain a Blobstream x instance and have the same security guarantees.

First, you will need to create a multisig that governs the Blobstream X contract and also the function identifiers. The function identifiers can be registered in the Succinct gateway.

Then, check the deployment documentation for how to deploy the contract.

Then, you will need to run a relayer, which will generate the proofs and relay them to your deployed Blobstream X contract. Check the local proving documentation for more information.

- +

BlobstreamX: the previous zk implementation of Blobstream ​

blobstream x draft diagram

What is Blobstream X? ​

Blobstream X is the previous implementation of Blobstream. It uses plonky2x to create circuits that verify the Celestia consensus and generate the corresponding proofs.

Blobstream X is built and deployed with Succinct's protocol.

NOTE

The Blobstream deployments below don't use the BlobstreamX circuits.

You can find the repository for Blobstream X along with code for:

NOTE

Custom ranges can be requested using the BlobstreamX contract to create proofs for specific Celestia block batches. These ranges can be constructed as [latestBlock, customTargetBlock), with latestBlock as the latest block height that was committed to by the BlobstreamX contract, and latestBlock > customTargetBlock, and customTargetBlock - latestBlock <= DATA_COMMITMENT_MAX.

Block ranges that are before the contract's latestBlock can't be proven a second time in different batches.

More information can be found in the requestHeaderRange(...) method.

How Blobstream X works ​

As shown in the diagram below, the entrypoint for updates to the Blobstream X contract is through the SuccinctGateway smart contract, which is a simple entrypoint contract that verifies proofs (against a deployed onchain verifier for the Blobstream X circuit) and then calls the BlobstreamX.sol contract to update it. Find more information about the SuccinctGateway.

blobstream x overview diagram draft

NOTE

If the Blobstream X contract is not deployed on a desired chain, it needs to be deployed before it can be used by your rollup. See the deployment documentation for more details.

Deploy Blobstream X ​

It is possible to deploy and maintain a Blobstream x instance and have the same security guarantees.

First, you will need to create a multisig that governs the Blobstream X contract and also the function identifiers. The function identifiers can be registered in the Succinct gateway.

Then, check the deployment documentation for how to deploy the contract.

Then, you will need to run a relayer, which will generate the proofs and relay them to your deployed Blobstream X contract. Check the local proving documentation for more information.

+ \ No newline at end of file diff --git a/pr-1699/developers/bubs-testnet.html b/pr-1699/developers/bubs-testnet.html index bf19dfaf9a..f8a9c47191 100644 --- a/pr-1699/developers/bubs-testnet.html +++ b/pr-1699/developers/bubs-testnet.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Bubs testnet ​

Bubs testnet

Bubs Testnet is a the first OP Stack testnet with Celestia underneath hosted by Caldera with support from Celestia Labs. Bubs is dedicated to providing developers with an EVM-compatible execution layer to deploy their EVM applications on.

Built with the OP Stack and Celestia ​

The Bubs Testnet is a testnet rollup, a modified version of optimism-bedrock that uses Celestia as a data availability (DA) layer. This integration can be found in the @celestiaorg/optimism repository. The testnet is hosted by Caldera, who makes it easy to launch rollups with no code required. Bubs' data is posted to Celestia on the Mocha testnet. View the namespace for Bubs on Celestia's Mocha testnet.

Learn more about the setup of the integration in the introduction.

Building on Bubs ​

Bubs Testnet provides a robust environment for developers to test their Ethereum Virtual Machine (EVM) applications. It offers an EVM-compatible execution layer, making it an ideal platform for developers looking to build and test applications in a setting that closely mirrors an OP Stack rollup on Celestia.

Learn more at https://bubs-sepolia.hub.caldera.xyz/.

RPC URLs ​

Remote Procedure Call (RPC) URLs are endpoints that allow developers to interact with the blockchain. They are essential for sending transactions, querying blockchain data, and performing other interactions with the blockchain.

For the Bubs Testnet, you can connect to the following RPC URLs:

HTTPS ​

  • https://bubs-sepolia.rpc.caldera.xyz/http

WSS ​

  • wss://bubs-sepolia.rpc.caldera.xyz/ws

This URL serves as the entry point to the Bubs Testnet. You can use it in your applications to connect to the testnet and interact with the smart contracts you deploy there.

Remember, Bubs Testnet is a testing environment!

Bridge ​

Bridging is a process that enables the transfer of assets between different blockchains.

To bridge between Ethereum Sepolia and Bubs Testnet, visit the Bubs Testnet bridge.

Faucet ​

To visit the Bubs testnet faucet, go to https://bubs-sepolia.hub.caldera.xyz/ and click the "Faucet" tab.

Explorer ​

To visit the explorer, go to https://bubs-sepolia.explorer.caldera.xyz/.

Status ​

To see the status and uptime information for Bubs, visit the status page.

Next steps ​

Now that you have a better understanding of the Bubs Testnet and its integration of OP Stack and Celestia, you can start exploring its capabilities.

- +

Bubs testnet ​

Bubs testnet

Bubs Testnet is a the first OP Stack testnet with Celestia underneath hosted by Caldera with support from Celestia Labs. Bubs is dedicated to providing developers with an EVM-compatible execution layer to deploy their EVM applications on.

Built with the OP Stack and Celestia ​

The Bubs Testnet is a testnet rollup, a modified version of optimism-bedrock that uses Celestia as a data availability (DA) layer. This integration can be found in the @celestiaorg/optimism repository. The testnet is hosted by Caldera, who makes it easy to launch rollups with no code required. Bubs' data is posted to Celestia on the Mocha testnet. View the namespace for Bubs on Celestia's Mocha testnet.

Learn more about the setup of the integration in the introduction.

Building on Bubs ​

Bubs Testnet provides a robust environment for developers to test their Ethereum Virtual Machine (EVM) applications. It offers an EVM-compatible execution layer, making it an ideal platform for developers looking to build and test applications in a setting that closely mirrors an OP Stack rollup on Celestia.

Learn more at https://bubs-sepolia.hub.caldera.xyz/.

RPC URLs ​

Remote Procedure Call (RPC) URLs are endpoints that allow developers to interact with the blockchain. They are essential for sending transactions, querying blockchain data, and performing other interactions with the blockchain.

For the Bubs Testnet, you can connect to the following RPC URLs:

HTTPS ​

  • https://bubs-sepolia.rpc.caldera.xyz/http

WSS ​

  • wss://bubs-sepolia.rpc.caldera.xyz/ws

This URL serves as the entry point to the Bubs Testnet. You can use it in your applications to connect to the testnet and interact with the smart contracts you deploy there.

Remember, Bubs Testnet is a testing environment!

Bridge ​

Bridging is a process that enables the transfer of assets between different blockchains.

To bridge between Ethereum Sepolia and Bubs Testnet, visit the Bubs Testnet bridge.

Faucet ​

To visit the Bubs testnet faucet, go to https://bubs-sepolia.hub.caldera.xyz/ and click the "Faucet" tab.

Explorer ​

To visit the explorer, go to https://bubs-sepolia.explorer.caldera.xyz/.

Status ​

To see the status and uptime information for Bubs, visit the status page.

Next steps ​

Now that you have a better understanding of the Bubs Testnet and its integration of OP Stack and Celestia, you can start exploring its capabilities.

+ \ No newline at end of file diff --git a/pr-1699/developers/build-whatever.html b/pr-1699/developers/build-whatever.html index 2cfb204f47..dc0a2c93e8 100644 --- a/pr-1699/developers/build-whatever.html +++ b/pr-1699/developers/build-whatever.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Build whatever ​

If you're a developer and want to know what the benefits of modular blockchains are for you, you’ve come to the right place. This page will give you the rundown on modular blockchains and their benefits for developers like you.

This section provides various guides and tutorials that cover different options for deploying rollups on Celestia.

Quickstart - Building on Celestia ​

Choose a framework ​

So, you’re ready to start experimenting and building on Celestia? Here are a few options that are currently available for developers.

Rollups as a Service ​

Deploy your rollup with a RaaS provider.

Smart contracts ​

Deploy your smart contracts on dedicated EVM-compatible rollups.

What is a rollup? ​

A rollup is a type of blockchain that offloads some work to a layer 1, like Celestia. Rollups host applications and process user transactions. Once those transactions get processed, they are then published to layer 1. It’s layer 1s job to order those transactions and check that they are available, at minimum.

What is a modular blockchain? ​

With blockchains there are more or less four core functions that they do.

  • Execution: transaction execution and state update.
  • Settlement: finality and dispute resolution.
  • Consensus: agreement on transaction ordering.
  • Data availability: prove data was published to the network.

Modular blockchains specialize in one or two of these functions rather than doing all of them like a monolithic blockchain. You probably know about layer 1s and layer 2s. That’s the general idea.

A typical example of a modular blockchain you might’ve heard of is a rollup. Rollups host smart contracts and execute transactions, much like any monolithic chain. But, the data of those transactions get sent to a layer 1 blockchain to carry out the remaining functions.

If you want to brush up on your understanding of modular blockchains, head over to learn modular.

Benefits of modular blockchains ​

Ease of deploying a chain ​

One of the goals of modular blockchains is to make it as easy to deploy a blockchain as a smart contract. There are a few unique ways that modular blockchains can significantly reduce the cost of deploying a new blockchain.

  1. No validator set is required. Rollups can deploy without sourcing their own set of validators or sequencers.
  2. Inherit security from the start. Rollups don’t need to build all their security from scratch.
  3. Any part of the stack can be delegated. Development time can be reduced by outsourcing functions of the rollup to external providers.

All in all, builders will be able to outsource as much of the stack as they need. Deploying a new blockchain will be as simple as clicking a few options to initialize a production-ready rollup.

Scaling ​

Of course, a much higher scale is necessary if we want to support many more users. And modular blockchains use some new innovative technologies that can help us get there.

  • Data availability sampling enables modular blockchains like Celestia to scale data availability with the number of light nodes - that means more capacity for rollups.
  • Fraud and validity proofs make rollups vastly more efficient to verify. Nodes only need to verify a small proof of transaction validity (validity proof) or assume transactions are valid by default (fraud proof). This means rollups don’t require every node in the network to re-execute every transaction.

image

  • Decoupling execution from consensus lets developers define the VM that best fits the scaling needs of their application.
  • Separating applications across multiple rollups isolates congestion. If an application congests the execution capacity of one rollup, all other rollups remain unaffected in their execution capacity.

All these scaling properties combined make new types of applications and features possible, like onchain gaming, dynamic metadata, and ephemeral rollups, to name a few.

Customizability ​

By design, modular blockchains don’t lock in any feature set. They promote experimentation and customization.

Remember how decoupling execution from consensus enables VM customizability? Well, rollups are the execution component. Applications can run on their own rollup and adjust the VM to maximize their application's performance. Developers have that flexibility because Celestia's execution logic doesn't restrict rollups.

Basically, rollups can be customized to integrate any new or existing VM stack.

With existing rollup frameworks, developers can run rollup testnets using the EVM or Cosmos SDK. In the future, one can imagine a variety of VMs that rollup frameworks support, providing developers with more out-of-the-box options for their applications.

Some customizations that could be made to a rollup's VM include custom precompiles, changing transaction processing from sequential to parallel, or adding support for private smart contracts.

All of this only scratches the surface.

- +

Build whatever ​

If you're a developer and want to know what the benefits of modular blockchains are for you, you’ve come to the right place. This page will give you the rundown on modular blockchains and their benefits for developers like you.

This section provides various guides and tutorials that cover different options for deploying rollups on Celestia.

Quickstart - Building on Celestia ​

Choose a framework ​

So, you’re ready to start experimenting and building on Celestia? Here are a few options that are currently available for developers.

Rollups as a Service ​

Deploy your rollup with a RaaS provider.

Smart contracts ​

Deploy your smart contracts on dedicated EVM-compatible rollups.

What is a rollup? ​

A rollup is a type of blockchain that offloads some work to a layer 1, like Celestia. Rollups host applications and process user transactions. Once those transactions get processed, they are then published to layer 1. It’s layer 1s job to order those transactions and check that they are available, at minimum.

What is a modular blockchain? ​

With blockchains there are more or less four core functions that they do.

  • Execution: transaction execution and state update.
  • Settlement: finality and dispute resolution.
  • Consensus: agreement on transaction ordering.
  • Data availability: prove data was published to the network.

Modular blockchains specialize in one or two of these functions rather than doing all of them like a monolithic blockchain. You probably know about layer 1s and layer 2s. That’s the general idea.

A typical example of a modular blockchain you might’ve heard of is a rollup. Rollups host smart contracts and execute transactions, much like any monolithic chain. But, the data of those transactions get sent to a layer 1 blockchain to carry out the remaining functions.

If you want to brush up on your understanding of modular blockchains, head over to learn modular.

Benefits of modular blockchains ​

Ease of deploying a chain ​

One of the goals of modular blockchains is to make it as easy to deploy a blockchain as a smart contract. There are a few unique ways that modular blockchains can significantly reduce the cost of deploying a new blockchain.

  1. No validator set is required. Rollups can deploy without sourcing their own set of validators or sequencers.
  2. Inherit security from the start. Rollups don’t need to build all their security from scratch.
  3. Any part of the stack can be delegated. Development time can be reduced by outsourcing functions of the rollup to external providers.

All in all, builders will be able to outsource as much of the stack as they need. Deploying a new blockchain will be as simple as clicking a few options to initialize a production-ready rollup.

Scaling ​

Of course, a much higher scale is necessary if we want to support many more users. And modular blockchains use some new innovative technologies that can help us get there.

  • Data availability sampling enables modular blockchains like Celestia to scale data availability with the number of light nodes - that means more capacity for rollups.
  • Fraud and validity proofs make rollups vastly more efficient to verify. Nodes only need to verify a small proof of transaction validity (validity proof) or assume transactions are valid by default (fraud proof). This means rollups don’t require every node in the network to re-execute every transaction.

image

  • Decoupling execution from consensus lets developers define the VM that best fits the scaling needs of their application.
  • Separating applications across multiple rollups isolates congestion. If an application congests the execution capacity of one rollup, all other rollups remain unaffected in their execution capacity.

All these scaling properties combined make new types of applications and features possible, like onchain gaming, dynamic metadata, and ephemeral rollups, to name a few.

Customizability ​

By design, modular blockchains don’t lock in any feature set. They promote experimentation and customization.

Remember how decoupling execution from consensus enables VM customizability? Well, rollups are the execution component. Applications can run on their own rollup and adjust the VM to maximize their application's performance. Developers have that flexibility because Celestia's execution logic doesn't restrict rollups.

Basically, rollups can be customized to integrate any new or existing VM stack.

With existing rollup frameworks, developers can run rollup testnets using the EVM or Cosmos SDK. In the future, one can imagine a variety of VMs that rollup frameworks support, providing developers with more out-of-the-box options for their applications.

Some customizations that could be made to a rollup's VM include custom precompiles, changing transaction processing from sequential to parallel, or adding support for private smart contracts.

All of this only scratches the surface.

+ \ No newline at end of file diff --git a/pr-1699/developers/celestia-node-key.html b/pr-1699/developers/celestia-node-key.html index c5e841a6f7..f016a4b1f6 100644 --- a/pr-1699/developers/celestia-node-key.html +++ b/pr-1699/developers/celestia-node-key.html @@ -12,7 +12,7 @@ - + @@ -45,19 +45,19 @@ make cel-key
# dumps binary in current working directory, accessible via `./cel-key`
 make cel-key

or

sh
# installs binary in GOBIN path, accessible via `cel-key`
 make install-key
# installs binary in GOBIN path, accessible via `cel-key`
-make install-key

For the purpose of this guide, we will use the make cel-key command.

Steps for generating node keys ​

To generate a key for a Celestia node, select the tab for your node type:

TIP

You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information

bash
./cel-key add <key-name> --keyring-backend test --node.type bridge \
+make install-key

For the purpose of this guide, we will use the make cel-key command.

Steps for generating node keys ​

To generate a key for a Celestia node, select the tab for your node type:

TIP

You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information

bash
./cel-key add <key-name> --keyring-backend test --node.type bridge \
   --p2p.network <network>
./cel-key add <key-name> --keyring-backend test --node.type bridge \
   --p2p.network <network>
bash
./cel-key add <key-name> --keyring-backend test --node.type full \
   --p2p.network <network>
./cel-key add <key-name> --keyring-backend test --node.type full \
   --p2p.network <network>
bash
./cel-key add <key-name> --keyring-backend test --node.type light \
   --p2p.network <network>
./cel-key add <key-name> --keyring-backend test --node.type light \
-  --p2p.network <network>

This will load the key <key-name> into the directory of the node.

Further flags you can use to customize your key are the following:

  • --p2p.network: Specifies which network you want the key for. Values are arabica and mocha. Please note the default network will be mocha.

Keep in mind that your celestia-node will only pick up keys that are inside the default directory under /keys so you should make sure to point cel-key utility to the correct directory via the p2p.network or home flags if you have specified a custom directory or network other than Arabica, Mocha, or Mainnet Beta.

Also keep in mind that if you do not specify a network with --p2p.network, the default one will always be celestia (Mainnet Beta).

Steps for exporting node keys ​

You can export a private key from the local keyring in encrypted and ASCII-armored format.

bash
./cel-key export <key-name> --keyring-backend test --node.type bridge \
+  --p2p.network <network>

This will load the key <key-name> into the directory of the node.

Further flags you can use to customize your key are the following:

  • --p2p.network: Specifies which network you want the key for. Values are arabica and mocha. Please note the default network will be mocha.

Keep in mind that your celestia-node will only pick up keys that are inside the default directory under /keys so you should make sure to point cel-key utility to the correct directory via the p2p.network or home flags if you have specified a custom directory or network other than Arabica, Mocha, or Mainnet Beta.

Also keep in mind that if you do not specify a network with --p2p.network, the default one will always be celestia (Mainnet Beta).

Steps for exporting node keys ​

You can export a private key from the local keyring in encrypted and ASCII-armored format.

bash
./cel-key export <key-name> --keyring-backend test --node.type bridge \
   --p2p.network <network>
./cel-key export <key-name> --keyring-backend test --node.type bridge \
   --p2p.network <network>
bash
./cel-key export <key-name> --keyring-backend test --node.type full \
   --p2p.network <network>
./cel-key export <key-name> --keyring-backend test --node.type full \
   --p2p.network <network>
bash
./cel-key export <key-name> --keyring-backend test --node.type light \
   --p2p.network <network>
./cel-key export <key-name> --keyring-backend test --node.type light \
-  --p2p.network <network>

Steps for importing node keys ​

To import from a mnemonic, use the following command, then enter your bip39 mnemonic:

bash
./cel-key add <key-name> --recover --keyring-backend test \
+  --p2p.network <network>

Steps for importing node keys ​

To import from a mnemonic, use the following command, then enter your bip39 mnemonic:

bash
./cel-key add <key-name> --recover --keyring-backend test \
   --node.type bridge --p2p.network <network>
./cel-key add <key-name> --recover --keyring-backend test \
   --node.type bridge --p2p.network <network>
bash
./cel-key add <key-name> --recover --keyring-backend test \
   --node.type full --p2p.network <network>
./cel-key add <key-name> --recover --keyring-backend test \
@@ -101,8 +101,8 @@
 - address: celestia1wkhyhr7ngf0ayqlpnsnxg4d72hfs5453dvunm9
   name: my_celes_key
   pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A1/NsoY0RGL7Hqt4VWLg441GQKJsZ2fBUnZXipgns8oV"}'
-  type: local
- + type: local + \ No newline at end of file diff --git a/pr-1699/developers/deploy-on-bubs.html b/pr-1699/developers/deploy-on-bubs.html index 02d572036f..e9ecb73453 100644 --- a/pr-1699/developers/deploy-on-bubs.html +++ b/pr-1699/developers/deploy-on-bubs.html @@ -11,7 +11,7 @@ - + @@ -174,8 +174,8 @@ status 1 transactionHash 0x8f15d6004598f0662dd673a9898dceef77be8cc28408cecc284b28d7be32307d transactionIndex 0 -type 2

Now, we can make a read call to view the state of the number variable, using the cast call command:

bash
cast call $CONTRACT_ADDRESS "number()" --rpc-url $BUBS_RPC_URL
cast call $CONTRACT_ADDRESS "number()" --rpc-url $BUBS_RPC_URL

The result will look similar:

bash
0x000000000000000000000000000000000000000000000000000000000000000a
0x000000000000000000000000000000000000000000000000000000000000000a

Convert the result from hexadecimal to a base 10 value with:

bash
echo $((0x000000000000000000000000000000000000000000000000000000000000000a))
echo $((0x000000000000000000000000000000000000000000000000000000000000000a))

Next steps ​

Congratulations! You've learned how to deploy a smart contract to Bubs testnet.

What will you build next? Now, you're ready to check out the GM Portal tutorial.

- +type 2

Now, we can make a read call to view the state of the number variable, using the cast call command:

bash
cast call $CONTRACT_ADDRESS "number()" --rpc-url $BUBS_RPC_URL
cast call $CONTRACT_ADDRESS "number()" --rpc-url $BUBS_RPC_URL

The result will look similar:

bash
0x000000000000000000000000000000000000000000000000000000000000000a
0x000000000000000000000000000000000000000000000000000000000000000a

Convert the result from hexadecimal to a base 10 value with:

bash
echo $((0x000000000000000000000000000000000000000000000000000000000000000a))
echo $((0x000000000000000000000000000000000000000000000000000000000000000a))

Next steps ​

Congratulations! You've learned how to deploy a smart contract to Bubs testnet.

What will you build next? Now, you're ready to check out the GM Portal tutorial.

+ \ No newline at end of file diff --git a/pr-1699/developers/ethereum-fallback.html b/pr-1699/developers/ethereum-fallback.html index dd85055904..9d8be677ba 100644 --- a/pr-1699/developers/ethereum-fallback.html +++ b/pr-1699/developers/ethereum-fallback.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Ethereum fallback ​

Ethereum fallback is a mechanism that enables Ethereum L2s (or L3s) to “fall back” to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta. This feature is currently supported by Celestia integrations with:

In the case of Celestia downtime or temporary unavailability, L2s can fallback to posting transactions as calldata on Ethereum or another DA layer for data availability instead of posting to Celestia. This mechanism ensures users can continue to transact securely and seamlessly, preventing disruptions and helping to ensure user funds do not get stuck in the L2's bridge on Ethereum.

Ethereum fallback is triggered whenever the sequencer has an error sending the PayForBlobs transaction on Celestia. Fallback can be triggered due to a congested mempool or nonce error and can be simulated with an error such as low balance or incorrect sequence. Fallback can also be triggered in the event Blobstream stops relaying attestations.

Ethereum fallback

- +

Ethereum fallback ​

Ethereum fallback is a mechanism that enables Ethereum L2s (or L3s) to “fall back” to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta. This feature is currently supported by Celestia integrations with:

In the case of Celestia downtime or temporary unavailability, L2s can fallback to posting transactions as calldata on Ethereum or another DA layer for data availability instead of posting to Celestia. This mechanism ensures users can continue to transact securely and seamlessly, preventing disruptions and helping to ensure user funds do not get stuck in the L2's bridge on Ethereum.

Ethereum fallback is triggered whenever the sequencer has an error sending the PayForBlobs transaction on Celestia. Fallback can be triggered due to a congested mempool or nonce error and can be simulated with an error such as low balance or incorrect sequence. Fallback can also be triggered in the event Blobstream stops relaying attestations.

Ethereum fallback

+ \ No newline at end of file diff --git a/pr-1699/developers/feegrant-for-blobs.html b/pr-1699/developers/feegrant-for-blobs.html index e36566f24a..e15612416d 100644 --- a/pr-1699/developers/feegrant-for-blobs.html +++ b/pr-1699/developers/feegrant-for-blobs.html @@ -11,7 +11,7 @@ - + @@ -100,8 +100,8 @@ --broadcast-mode block \ --yes

Example: FeeGrant transaction on Mocha

Optional: Checking the granter's account ​

To confirm that the fees have been deducted from the granter's account that granted the fee allowance, run:

bash
celestia-appd query bank balances $GRANTER_ADDRESS \
 --node https://rpc.celestia-mocha.com:443 --denom utia
celestia-appd query bank balances $GRANTER_ADDRESS \
---node https://rpc.celestia-mocha.com:443 --denom utia

This output will show the remaining balance after fees have been deducted, confirming that the FeeGrant module is working as intended.

- +--node https://rpc.celestia-mocha.com:443 --denom utia

This output will show the remaining balance after fees have been deducted, confirming that the FeeGrant module is working as intended.

+ \ No newline at end of file diff --git a/pr-1699/developers/full-stack-modular-development-guide.html b/pr-1699/developers/full-stack-modular-development-guide.html index 3fcd8260ce..8ba95c7b57 100644 --- a/pr-1699/developers/full-stack-modular-development-guide.html +++ b/pr-1699/developers/full-stack-modular-development-guide.html @@ -11,7 +11,7 @@ - + @@ -930,8 +930,8 @@ && echo $PRIVATE_KEY | pbcopy
PRIVATE_KEY=$(ethermintd keys unsafe-export-eth-key mykey --keyring-backend test)
 && echo $PRIVATE_KEY | pbcopy

Now, import the private key to MetaMask and switch to that account.

Next, let’s run it on your Ethermint rollup.

To do so, first update the contractAddress variable with the contract address deployed to Ethermint:

jsx
/* src/App.jsx */
 const contractAddress = "your-ethermint-contract-address";
/* src/App.jsx */
-const contractAddress = "your-ethermint-contract-address";

Next, run the React application:

bash
npm run dev
npm run dev

When you run the app, you should now be connected to and using the Ethermint rollup.

If you imported the address that started the chain, you'll see quite a large balance.

Now give it a spin 🌀 ​

Now that you have your dapp running, go ahead and test out a new post on your Ethermint sovereign rollup. If you enjoyed this tutorial, be sure to share your example in our Discord!

- +const contractAddress = "your-ethermint-contract-address";

Next, run the React application:

bash
npm run dev
npm run dev

When you run the app, you should now be connected to and using the Ethermint rollup.

If you imported the address that started the chain, you'll see quite a large balance.

Now give it a spin 🌀 ​

Now that you have your dapp running, go ahead and test out a new post on your Ethermint sovereign rollup. If you enjoyed this tutorial, be sure to share your example in our Discord!

+ \ No newline at end of file diff --git a/pr-1699/developers/gm-portal-bubs.html b/pr-1699/developers/gm-portal-bubs.html index ca4206f587..5c9edb768c 100644 --- a/pr-1699/developers/gm-portal-bubs.html +++ b/pr-1699/developers/gm-portal-bubs.html @@ -11,7 +11,7 @@ - + @@ -58,8 +58,8 @@ cast send --private-key $PRIVATE_KEY $RECEIVER --value 1ether --rpc-url $BUBS_RPC_URL
export RECEIVER=<receiver ETH address>
 cast send --private-key $PRIVATE_KEY $RECEIVER --value 1ether --rpc-url $BUBS_RPC_URL

If you are in a different terminal than the one you set the private key in, you may need to set it again.

Update the frontend ​

Next, you will need to update a few things before you can interact with the contract on the frontend:

  1. Change the contract address on gm-portal/frontend/src/App.tsx to your contract address
  2. Match the chain info on gm-portal/frontend/src/main.tsx with the chain config of your L2
  3. If you changed the contract, update the ABI in gm-portal/frontend/GmPortal.json from gm-portal/contracts/out/GmPortal.sol/GmPortal.json. This can be done with:
bash
cd $HOME
 cp dev/gm-portal/contracts/out/GmPortal.sol/GmPortal.json dev/gm-portal/frontend
cd $HOME
-cp dev/gm-portal/contracts/out/GmPortal.sol/GmPortal.json dev/gm-portal/frontend

Interact with the frontend ​

Now, login with your wallet that you funded, and post a GM on your GM portal!

gm-bubs

Next steps ​

There are many possibilities of what could be built with this stack. These projects would be good to build on this stack:

  • onchain gaming
  • decentralized social media
  • an NFT ticketing rollup
  • Optimism on CelOPstia
  • OP Craft on Celestia
- +cp dev/gm-portal/contracts/out/GmPortal.sol/GmPortal.json dev/gm-portal/frontend

Interact with the frontend ​

Now, login with your wallet that you funded, and post a GM on your GM portal!

gm-bubs

Next steps ​

There are many possibilities of what could be built with this stack. These projects would be good to build on this stack:

  • onchain gaming
  • decentralized social media
  • an NFT ticketing rollup
  • Optimism on CelOPstia
  • OP Craft on Celestia
+ \ No newline at end of file diff --git a/pr-1699/developers/golang-client-tutorial.html b/pr-1699/developers/golang-client-tutorial.html index 27563bb512..28a4549947 100644 --- a/pr-1699/developers/golang-client-tutorial.html +++ b/pr-1699/developers/golang-client-tutorial.html @@ -11,7 +11,7 @@ - + @@ -276,8 +276,8 @@ // Fetch the EDS return client.Share.GetEDS(ctx, header) -}

API documentation ​

To see the full list of available methods, see the API documentation.

- +}

API documentation ​

To see the full list of available methods, see the API documentation.

+ \ No newline at end of file diff --git a/pr-1699/developers/integrate-celestia.html b/pr-1699/developers/integrate-celestia.html index 8a9589a160..3399988530 100644 --- a/pr-1699/developers/integrate-celestia.html +++ b/pr-1699/developers/integrate-celestia.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Integrate Celestia for service providers ​

This document is for third-party service providers, such as custodians and explorers, integrating the Celestia network.

Getting started ​

When getting started Celestia, we recommend checking out these resources first:

Celestia service provider notes ​

Celestia is a fairly standard Cosmos-SDK based chain. We use the latest version of Tendermint and the Cosmos-SDK, with only minor modifications to each. This means that we are:

  • Using the default Cosmos-SDK modules: auth, bank, distribution, staking, slashing, mint, crisis, ibchost, genutil, evidence, ibctransfer, params, gov (limited in some TBD capacities), upgrade, vesting, feegrant, capability, and payment.
  • Use the standard digital keys schemes provided by the Cosmos-SDK and Tendermint, those being secp256k1 for user transactions, and tm-ed25519 for signing and verifying consensus messages.

While exactly which modules used is subject to change, Celestia aims to be as minimal as possible.

Custody and key management ​

Celestia supports many already existing key management systems, as we rely on the Cosmos-SDK and Tendermint libraries for signing and verifying transactions. Learn more in the Cosmos-SDK documentation

RPC and querying ​

In celestia-app, only the standard RPC endpoints for Tendermint and the Cosmos-SDK are exposed. We do not currently add or subtract any core functionality, but this could change in the future. The same goes for querying data from the chain.

In celestia-node, the Data Availability node client, there is a JSON-RPC API that allows you to interact directly with Celestia's Data Availability layer. Learn how to use the API in this tutorial.

Compatibility ​

Linux, particularly Ubuntu 20.04 LTS, is the most well tested. Potentially compatible with other OSs, but they are currently untested. Some of the cryptography libraries used for erasure data are not guaranteed to work on other platforms.

Syncing ​

Since we utilize Tendermint and the Cosmos-SDK, syncing the chain can be performed by any method that is supported by those libraries. This includes fast-sync, state sync, and quick sync.

Notable exceptions relative to other blockchains ​

Relative to other Tendermint based chains, Celestia will have significantly longer blocktimes of roughly 12* seconds. The reason behind this block time is to optimize the bandwidth used by light clients that are sampling the chain, and is not because we have modified Tendermint consensus in any meaningful way. Validators will likely download/upload relatively large blocks. It should be noted that while these blocks are large, very little typical blockchain state execution is actually occurring on Celestia. Meaning that the bandwidth requirements will likely be larger than that of a typical Cosmos-SDK based blockchain full node, the computing requirements should be similar in magnitude.

*Subject to Change

- +

Integrate Celestia for service providers ​

This document is for third-party service providers, such as custodians and explorers, integrating the Celestia network.

Getting started ​

When getting started Celestia, we recommend checking out these resources first:

Celestia service provider notes ​

Celestia is a fairly standard Cosmos-SDK based chain. We use the latest version of Tendermint and the Cosmos-SDK, with only minor modifications to each. This means that we are:

  • Using the default Cosmos-SDK modules: auth, bank, distribution, staking, slashing, mint, crisis, ibchost, genutil, evidence, ibctransfer, params, gov (limited in some TBD capacities), upgrade, vesting, feegrant, capability, and payment.
  • Use the standard digital keys schemes provided by the Cosmos-SDK and Tendermint, those being secp256k1 for user transactions, and tm-ed25519 for signing and verifying consensus messages.

While exactly which modules used is subject to change, Celestia aims to be as minimal as possible.

Custody and key management ​

Celestia supports many already existing key management systems, as we rely on the Cosmos-SDK and Tendermint libraries for signing and verifying transactions. Learn more in the Cosmos-SDK documentation

RPC and querying ​

In celestia-app, only the standard RPC endpoints for Tendermint and the Cosmos-SDK are exposed. We do not currently add or subtract any core functionality, but this could change in the future. The same goes for querying data from the chain.

In celestia-node, the Data Availability node client, there is a JSON-RPC API that allows you to interact directly with Celestia's Data Availability layer. Learn how to use the API in this tutorial.

Compatibility ​

Linux, particularly Ubuntu 20.04 LTS, is the most well tested. Potentially compatible with other OSs, but they are currently untested. Some of the cryptography libraries used for erasure data are not guaranteed to work on other platforms.

Syncing ​

Since we utilize Tendermint and the Cosmos-SDK, syncing the chain can be performed by any method that is supported by those libraries. This includes fast-sync, state sync, and quick sync.

Notable exceptions relative to other blockchains ​

Relative to other Tendermint based chains, Celestia will have significantly longer blocktimes of roughly 12* seconds. The reason behind this block time is to optimize the bandwidth used by light clients that are sampling the chain, and is not because we have modified Tendermint consensus in any meaningful way. Validators will likely download/upload relatively large blocks. It should be noted that while these blocks are large, very little typical blockchain state execution is actually occurring on Celestia. Meaning that the bandwidth requirements will likely be larger than that of a typical Cosmos-SDK based blockchain full node, the computing requirements should be similar in magnitude.

*Subject to Change

+ \ No newline at end of file diff --git a/pr-1699/developers/intro-to-op-stack.html b/pr-1699/developers/intro-to-op-stack.html index c208c62a55..6d55432299 100644 --- a/pr-1699/developers/intro-to-op-stack.html +++ b/pr-1699/developers/intro-to-op-stack.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Introduction to OP Stack integration ​

Optimism is a low-cost and lightning-fast Ethereum L2 blockchain, built with the OP Stack.

Celestia is a modular consensus and data availability (DA) network, built to enable anyone to easily deploy their own blockchain with minimal overhead.

Together, they allow developers to create rollups that post data to Celestia and settle on Ethereum.

About the integration ​

Optimism uses Ethereum as a DA layer. Currently, settlement and DA for Optimism are on Ethereum, both onchain. op-batcher batches up rollup blocks and posts to Ethereum.

The integration of OP Stack with Celestia underneath for DA allows rollup operators to reduce overhead that is associated with posting data as calldata on Ethereum. Instead, op-batcher batches up rollup blocks and posts them to Celestia's DA network.

Data is managed in two ways. First, data is written to the data availability (DA) layer i.e. in this case Celestia, then the data commitment is written to the op-batcher. When reading op-node simply reads the data back from the DA layer by reading the data commitment from the op-batcher first, then reading the data from the DA layer using the data commitment. While previously op-node was reading from calldata on Ethereum, it now reads data from Celestia.

There are a few tools involved in the data handling process. op-batcher batches up rollup blocks and posts them to Ethereum. op-geth handles execution, while op-proposer is responsible for state commitment submission.

By using Celestia as a DA layer, existing L2s can switch from posting their data as calldata on Ethereum, to posting to Celestia. The commitment to the block is posted on Celestia, which is purpose-built for data availability. This is a more scalable than the traditional method of posting this data as calldata on monolithic chains.

GitHub repository ​

Find the repository for this integration at https://github.com/celestiaorg/optimism.

WARNING

This is a beta integration and we are working on resolving open issues.

Category contents ​

This category will guide you through interacting with existing OP Stack rollups with Celestia underneath, then how to start your own devnet with a modified version of optimism-bedrock that uses Celestia as a DA layer.

Next steps ​

Now that you understand the integration, you can start learning about the Bubs testnet, built with OP Stack and Celestia! This testnet is a great way to explore the possibilities of this integration and test your applications in a live environment.

- +

Introduction to OP Stack integration ​

Optimism is a low-cost and lightning-fast Ethereum L2 blockchain, built with the OP Stack.

Celestia is a modular consensus and data availability (DA) network, built to enable anyone to easily deploy their own blockchain with minimal overhead.

Together, they allow developers to create rollups that post data to Celestia and settle on Ethereum.

About the integration ​

Optimism uses Ethereum as a DA layer. Currently, settlement and DA for Optimism are on Ethereum, both onchain. op-batcher batches up rollup blocks and posts to Ethereum.

The integration of OP Stack with Celestia underneath for DA allows rollup operators to reduce overhead that is associated with posting data as calldata on Ethereum. Instead, op-batcher batches up rollup blocks and posts them to Celestia's DA network.

Data is managed in two ways. First, data is written to the data availability (DA) layer i.e. in this case Celestia, then the data commitment is written to the op-batcher. When reading op-node simply reads the data back from the DA layer by reading the data commitment from the op-batcher first, then reading the data from the DA layer using the data commitment. While previously op-node was reading from calldata on Ethereum, it now reads data from Celestia.

There are a few tools involved in the data handling process. op-batcher batches up rollup blocks and posts them to Ethereum. op-geth handles execution, while op-proposer is responsible for state commitment submission.

By using Celestia as a DA layer, existing L2s can switch from posting their data as calldata on Ethereum, to posting to Celestia. The commitment to the block is posted on Celestia, which is purpose-built for data availability. This is a more scalable than the traditional method of posting this data as calldata on monolithic chains.

GitHub repository ​

Find the repository for this integration at https://github.com/celestiaorg/optimism.

WARNING

This is a beta integration and we are working on resolving open issues.

Category contents ​

This category will guide you through interacting with existing OP Stack rollups with Celestia underneath, then how to start your own devnet with a modified version of optimism-bedrock that uses Celestia as a DA layer.

Next steps ​

Now that you understand the integration, you can start learning about the Bubs testnet, built with OP Stack and Celestia! This testnet is a great way to explore the possibilities of this integration and test your applications in a live environment.

+ \ No newline at end of file diff --git a/pr-1699/developers/multiaccounts.html b/pr-1699/developers/multiaccounts.html index 7b6daf4bd7..59810de346 100644 --- a/pr-1699/developers/multiaccounts.html +++ b/pr-1699/developers/multiaccounts.html @@ -11,7 +11,7 @@ - + @@ -42,8 +42,8 @@ --p2p.network=arabica --keyring.keyname testKey
celestia light start --core.ip=consensus.celestia-arabica-11.com \
     --p2p.network=arabica --keyring.keyname testKey

In this example, testKey becomes the default node key, and the node's address will change accordingly.

Submitting blobs with a different signer/key name ​

Option 1: Submit passing key name ​

You can submit a blob by specifying a different key name:

sh
celestia blob submit 0x42690c204d39600fddd3 'gm' --key.name testKey2
celestia blob submit 0x42690c204d39600fddd3 'gm' --key.name testKey2

This transaction will be signed by the address associated with testKey2.

Option 2: Submit passing signer address ​

Alternatively, you can submit a blob by specifying the signer's address:

sh
celestia blob submit 0x42690c204d39600fddd3 'gm' --signer $SIGNER_ADDRESS
celestia blob submit 0x42690c204d39600fddd3 'gm' --signer $SIGNER_ADDRESS

Both options achieve the same result but use different inputs. The testKey2 points to SIGNER_ADDRESS in the KeyStore.

Key management ​

All keys and addresses must be added to the KeyStore. To create a new key, use the cel-key library:

Creating a new key ​

sh
./cel-key add testKey --keyring-backend test \
     --node.type light --p2p.network arabica
./cel-key add testKey --keyring-backend test \
-    --node.type light --p2p.network arabica

Importing an existing key ​

sh
./cel-key import
./cel-key import

Learn more on the Create a wallet with celestia-node page.

Optional flags for write transactions ​

All other flags are now optional for all write transactions. This means you don't have to specify gas/fee parameters each time. The configuration can handle it for you automatically.

The default configuration applies to all write transactions, including those in the state module and blob.Submit. This simplifies the process of submitting transactions and reduces the need for manual input.

For reference, see the:

- + --node.type light --p2p.network arabica

Importing an existing key ​

sh
./cel-key import
./cel-key import

Learn more on the Create a wallet with celestia-node page.

Optional flags for write transactions ​

All other flags are now optional for all write transactions. This means you don't have to specify gas/fee parameters each time. The configuration can handle it for you automatically.

The default configuration applies to all write transactions, including those in the state module and blob.Submit. This simplifies the process of submitting transactions and reduces the need for manual input.

For reference, see the:

+ \ No newline at end of file diff --git a/pr-1699/developers/node-api.html b/pr-1699/developers/node-api.html index 3e9792ac9a..c53e03572d 100644 --- a/pr-1699/developers/node-api.html +++ b/pr-1699/developers/node-api.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Node API ​

The celestia-node API is made for interacting with celestia-node. There are two ways in which a user and developer can interact with the API, the RPC API and the Gateway API. View the API's documentation.

RPC API ​

The RPC API primarily focuses on developers and projects building on top of Celestia, who are willing to run their own DA nodes. The RPC API provides a richer set of features and a superior user experience. Unlike the Gateway API, the RPC API allows access to the internal wallet and keyring of the DA node, as well as other sensitive and administrative capabilities.

Library ​

The node can be used as a Golang library and designed for programmatic API access.

RPC ​

The RPC API is also exposed to OpenRPC(JSON-RPC 2.0) for users wanting to run their DA node as a separate DA service. It provides the same set of features as the library with an additional authentication system with different permissions levels to protect the wallet and signing + providing RPC-level DOS protection.

RPC API tutorial ​

The node tutorial, which uses the RPC CLI, is the recommended way to get started interacting with your Celestia node.

Gateway API ​

WARNING

The gateway endpoints have been deprecated and will be removed in the future. If you would like to use them anyway, you can find more details on GitHub.

The gateway API is a REST API which is meant to be deployed by infra providers to enable the public read-only gateway to the DA network for external users who don't want or can't run light nodes (like browsers currently) over HTTP. It has no wallet or signing functionality.

Gateway API tutorial ​

Check out the Prompt scavenger gateway API tutorial for more details.

- +

Node API ​

The celestia-node API is made for interacting with celestia-node. There are two ways in which a user and developer can interact with the API, the RPC API and the Gateway API. View the API's documentation.

RPC API ​

The RPC API primarily focuses on developers and projects building on top of Celestia, who are willing to run their own DA nodes. The RPC API provides a richer set of features and a superior user experience. Unlike the Gateway API, the RPC API allows access to the internal wallet and keyring of the DA node, as well as other sensitive and administrative capabilities.

Library ​

The node can be used as a Golang library and designed for programmatic API access.

RPC ​

The RPC API is also exposed to OpenRPC(JSON-RPC 2.0) for users wanting to run their DA node as a separate DA service. It provides the same set of features as the library with an additional authentication system with different permissions levels to protect the wallet and signing + providing RPC-level DOS protection.

RPC API tutorial ​

The node tutorial, which uses the RPC CLI, is the recommended way to get started interacting with your Celestia node.

Gateway API ​

WARNING

The gateway endpoints have been deprecated and will be removed in the future. If you would like to use them anyway, you can find more details on GitHub.

The gateway API is a REST API which is meant to be deployed by infra providers to enable the public read-only gateway to the DA network for external users who don't want or can't run light nodes (like browsers currently) over HTTP. It has no wallet or signing functionality.

Gateway API tutorial ​

Check out the Prompt scavenger gateway API tutorial for more details.

+ \ No newline at end of file diff --git a/pr-1699/developers/node-tutorial.html b/pr-1699/developers/node-tutorial.html index 150cb390dc..6c0665566d 100644 --- a/pr-1699/developers/node-tutorial.html +++ b/pr-1699/developers/node-tutorial.html @@ -12,7 +12,7 @@ - + @@ -39,11 +39,11 @@

Appearance

Celestia-node RPC CLI tutorial ​

In this tutorial, we will cover how to use the celestia-node RPC API to submit and retrieve data (blobs) from the data availability layer by their namespace.

Introduction ​

Blobs ​

Data is posted to Celestia's DA layer by using MsgPayForBlobs transactions to the core network. Read more about MsgPayForBlobs.

Namespaces ​

Celestia partitions the block data into multiple namespaces, one for every application. This allows applications to only download their data, and not the data of other applications. Read more about Namespaced Merkle trees (NMTs).

TIP

If you already have a running and funded node, you can skip to the RPC CLI guide section.

WARNING

The gateway endpoints have been deprecated and will be removed in the future. If you would like to use them anyway, you can find more details on GitHub.

Hardware requirements ​

The following minimum hardware requirements are recommended for running a light node:

  • Memory: 500 MB RAM (minimum)
  • CPU: Single Core
  • Disk: 50 GB SSD Storage
  • Bandwidth: 56 Kbps for Download/56 Kbps for Upload

Setting up dependencies ​

Install dependencies and celestia-node if you have not already.

Instantiate a Celestia light node ​

Now, let's instantiate a Celestia Light node:

TIP

RPC endpoints are exposed in all celestia-node types such as light, bridge and full nodes.

bash
celestia light init
celestia light init
bash
celestia light init --p2p.network mocha
celestia light init --p2p.network mocha
bash
celestia light init --p2p.network arabica
celestia light init --p2p.network arabica

Instantiating (or initializing) the node means setting up a node store on your machine. This is where the data and your keys will be stored.

Connect to a core endpoint ​

Let's now run the Celestia Light node with a gRPC connection to an example core endpoint. Connecting to a core endpoint provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).

Note: You are also encouraged to find a community-run API endpoint and there are several in the Discord. This one is used for demonstration purposes. Check out the Mocha testnet page, or Arabica devnet page.

bash
celestia light start --core.ip <URI>
celestia light start --core.ip <URI>
bash
celestia light start --core.ip <URI> --p2p.network mocha
celestia light start --core.ip <URI> --p2p.network mocha
bash
celestia light start --core.ip <URI> --p2p.network arabica
celestia light start --core.ip <URI> --p2p.network arabica

TIP

The --core.ip gRPC port defaults to 9090, so if you do not specify it in the command line, it will default to that port. You can add the port after the IP address or use the --core.grpc.port flag to specify another port if you prefer.

Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

For example, your command along with an RPC endpoint might look like this:

bash
celestia light start --core.ip consensus.lunaroasis.net
celestia light start --core.ip consensus.lunaroasis.net
bash
celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
bash
celestia light start --core.ip validator-1.celestia-arabica-11.com \
+

Celestia-node RPC CLI tutorial ​

In this tutorial, we will cover how to use the celestia-node RPC API to submit and retrieve data (blobs) from the data availability layer by their namespace.

Introduction ​

Blobs ​

Data is posted to Celestia's DA layer by using MsgPayForBlobs transactions to the core network. Read more about MsgPayForBlobs.

Namespaces ​

Celestia partitions the block data into multiple namespaces, one for every application. This allows applications to only download their data, and not the data of other applications. Read more about Namespaced Merkle trees (NMTs).

TIP

If you already have a running and funded node, you can skip to the RPC CLI guide section.

WARNING

The gateway endpoints have been deprecated and will be removed in the future. If you would like to use them anyway, you can find more details on GitHub.

Hardware requirements ​

The following minimum hardware requirements are recommended for running a light node:

  • Memory: 500 MB RAM (minimum)
  • CPU: Single Core
  • Disk: 50 GB SSD Storage
  • Bandwidth: 56 Kbps for Download/56 Kbps for Upload

Setting up dependencies ​

Install dependencies and celestia-node if you have not already.

Instantiate a Celestia light node ​

Now, let's instantiate a Celestia Light node:

TIP

RPC endpoints are exposed in all celestia-node types such as light, bridge and full nodes.

bash
celestia light init
celestia light init
bash
celestia light init --p2p.network mocha
celestia light init --p2p.network mocha
bash
celestia light init --p2p.network arabica
celestia light init --p2p.network arabica

Instantiating (or initializing) the node means setting up a node store on your machine. This is where the data and your keys will be stored.

Connect to a core endpoint ​

Let's now run the Celestia Light node with a gRPC connection to an example core endpoint. Connecting to a core endpoint provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).

Note: You are also encouraged to find a community-run API endpoint and there are several in the Discord. This one is used for demonstration purposes. Check out the Mocha testnet page, or Arabica devnet page.

bash
celestia light start --core.ip <URI>
celestia light start --core.ip <URI>
bash
celestia light start --core.ip <URI> --p2p.network mocha
celestia light start --core.ip <URI> --p2p.network mocha
bash
celestia light start --core.ip <URI> --p2p.network arabica
celestia light start --core.ip <URI> --p2p.network arabica

TIP

The --core.ip gRPC port defaults to 9090, so if you do not specify it in the command line, it will default to that port. You can add the port after the IP address or use the --core.grpc.port flag to specify another port if you prefer.

Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

For example, your command along with an RPC endpoint might look like this:

bash
celestia light start --core.ip consensus.lunaroasis.net
celestia light start --core.ip consensus.lunaroasis.net
bash
celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
bash
celestia light start --core.ip validator-1.celestia-arabica-11.com \
   --p2p.network arabica
celestia light start --core.ip validator-1.celestia-arabica-11.com \
   --p2p.network arabica

Keys and wallets ​

You can create your key for your node by running the following command from the celestia-node directory:

TIP

You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information

bash
./cel-key add <key-name> --keyring-backend test --node.type light \
   --p2p.network <network>
./cel-key add <key-name> --keyring-backend test --node.type light \
-  --p2p.network <network>

You can start your light node with the key created by running the following command:

bash
celestia light start --core.ip <URI> --keyring.keyname <key-name>
celestia light start --core.ip <URI> --keyring.keyname <key-name>
bash
celestia light start --core.ip <URI> --keyring.keyname <key-name> \
+  --p2p.network <network>

You can start your light node with the key created by running the following command:

bash
celestia light start --core.ip <URI> --keyring.keyname <key-name>
celestia light start --core.ip <URI> --keyring.keyname <key-name>
bash
celestia light start --core.ip <URI> --keyring.keyname <key-name> \
   --p2p.network mocha
celestia light start --core.ip <URI> --keyring.keyname <key-name> \
   --p2p.network mocha
bash
celestia light start --core.ip <URI> --keyring.keyname <key-name> \
   --p2p.network arabica
celestia light start --core.ip <URI> --keyring.keyname <key-name> \
@@ -435,8 +435,8 @@
     ],
     0.002
   ]
-}' 127.0.0.1:26658
  1. Upon successful blob submission, the result will show the block height:
bash
{"jsonrpc":"2.0","result":362101,"id":1}
{"jsonrpc":"2.0","result":362101,"id":1}

The example transaction can be found on Celenium.

Post an SVG as a PFB ​

If you'd like to create your own SVG, post it to Celestia, and retrieve it, you can check out the Base64 SVG Tutorial.

Troubleshooting ​

If you encounter an error like:

sh
"rpc error: code = NotFound desc = account celestia1krkle0n547u0znz3unnln8paft2dq4z3rznv86 not found"
"rpc error: code = NotFound desc = account celestia1krkle0n547u0znz3unnln8paft2dq4z3rznv86 not found"

It is possible that the account you are trying to submit a PayForBlobs from doesn't have testnet tokens yet. Ensure the testnet faucet has funded your account with tokens and then try again.

- +}' 127.0.0.1:26658
  1. Upon successful blob submission, the result will show the block height:
bash
{"jsonrpc":"2.0","result":362101,"id":1}
{"jsonrpc":"2.0","result":362101,"id":1}

The example transaction can be found on Celenium.

Post an SVG as a PFB ​

If you'd like to create your own SVG, post it to Celestia, and retrieve it, you can check out the Base64 SVG Tutorial.

Troubleshooting ​

If you encounter an error like:

sh
"rpc error: code = NotFound desc = account celestia1krkle0n547u0znz3unnln8paft2dq4z3rznv86 not found"
"rpc error: code = NotFound desc = account celestia1krkle0n547u0znz3unnln8paft2dq4z3rznv86 not found"

It is possible that the account you are trying to submit a PayForBlobs from doesn't have testnet tokens yet. Ensure the testnet faucet has funded your account with tokens and then try again.

+ \ No newline at end of file diff --git a/pr-1699/developers/optimism-devnet.html b/pr-1699/developers/optimism-devnet.html index 37e79610a6..a4700ad8dc 100644 --- a/pr-1699/developers/optimism-devnet.html +++ b/pr-1699/developers/optimism-devnet.html @@ -11,7 +11,7 @@ - + @@ -112,8 +112,8 @@ value 0 yParity 0

TIP

You are looking for a batcher transaction to the address 0xFf00000000000000000000000000000000000901.

First, remove the prefix 0xce. Now, set the input as the INPUT variable and encode it as base64:

bash
export INPUT=3500000000000000769074a923011bdda721eacc34c8a77c69c10f2b6c8e659f987e82f217a5340f
 export ENCODED_INPUT=$(echo "$INPUT" | xxd -r -p | base64)
export INPUT=3500000000000000769074a923011bdda721eacc34c8a77c69c10f2b6c8e659f987e82f217a5340f
-export ENCODED_INPUT=$(echo "$INPUT" | xxd -r -p | base64)

TIP

Remember to remove the 0xce prefix!

Find the data on Celestia ​

bash
curl -s -X POST -H "Content-Type: application/json" -H "Authorization: Bearer $CELESTIA_NODE_AUTH_TOKEN" -d '{ "id": 1, "jsonrpc": "2.0", "method": "da.Get", "params": [["$ENCODED_INPUT"], "AAAAAAAAAAAAAAAAAAAAAAAAAAECAwQFBgcICRA="]}' http://127.0.0.1:26658
curl -s -X POST -H "Content-Type: application/json" -H "Authorization: Bearer $CELESTIA_NODE_AUTH_TOKEN" -d '{ "id": 1, "jsonrpc": "2.0", "method": "da.Get", "params": [["$ENCODED_INPUT"], "AAAAAAAAAAAAAAAAAAAAAAAAAAECAwQFBgcICRA="]}' http://127.0.0.1:26658

The params are []blobs, namespace, base64-encoded.

Your result will look similar to the below!

console
{"jsonrpc":"2.0","result":["SGVsbG8gd28ybGQh"],"id":1}
{"jsonrpc":"2.0","result":["SGVsbG8gd28ybGQh"],"id":1}

Span batches ​

Span batches can be enabled by setting OP_BATCHER_BATCH_TYPE: 1 in your docker-compose.yml file.

Note that this requires the Delta activation time to be configured. For your devnet, you should set "l2GenesisDeltaTimeOffset": "0x0", in devnetL1-template.json. This will enable span batches and can be tested by grepping docker compose logs -f | grep batch_type which should include batch_type=SpanBatch and batch_type=1.

- +export ENCODED_INPUT=$(echo "$INPUT" | xxd -r -p | base64)

TIP

Remember to remove the 0xce prefix!

Find the data on Celestia ​

bash
curl -s -X POST -H "Content-Type: application/json" -H "Authorization: Bearer $CELESTIA_NODE_AUTH_TOKEN" -d '{ "id": 1, "jsonrpc": "2.0", "method": "da.Get", "params": [["$ENCODED_INPUT"], "AAAAAAAAAAAAAAAAAAAAAAAAAAECAwQFBgcICRA="]}' http://127.0.0.1:26658
curl -s -X POST -H "Content-Type: application/json" -H "Authorization: Bearer $CELESTIA_NODE_AUTH_TOKEN" -d '{ "id": 1, "jsonrpc": "2.0", "method": "da.Get", "params": [["$ENCODED_INPUT"], "AAAAAAAAAAAAAAAAAAAAAAAAAAECAwQFBgcICRA="]}' http://127.0.0.1:26658

The params are []blobs, namespace, base64-encoded.

Your result will look similar to the below!

console
{"jsonrpc":"2.0","result":["SGVsbG8gd28ybGQh"],"id":1}
{"jsonrpc":"2.0","result":["SGVsbG8gd28ybGQh"],"id":1}

Span batches ​

Span batches can be enabled by setting OP_BATCHER_BATCH_TYPE: 1 in your docker-compose.yml file.

Note that this requires the Delta activation time to be configured. For your devnet, you should set "l2GenesisDeltaTimeOffset": "0x0", in devnetL1-template.json. This will enable span batches and can be tested by grepping docker compose logs -f | grep batch_type which should include batch_type=SpanBatch and batch_type=1.

+ \ No newline at end of file diff --git a/pr-1699/developers/optimism.html b/pr-1699/developers/optimism.html index 1113597352..0ec60078bf 100644 --- a/pr-1699/developers/optimism.html +++ b/pr-1699/developers/optimism.html @@ -12,7 +12,7 @@ - + @@ -39,7 +39,7 @@

Appearance

Run an OP Stack rollup with Celestia underneath ​

This guide will show you how to run your own OP Stack devnet and testnet that posts data to Celestia's Mocha testnet using roll-op and op-plasma-celestia.

If you don't have devops experience and would like to use a Rollups as a Service (RaaS) provider, see the RaaS category in the menu.

Dependency setup ​

Setting up your light node ​

Sync and fund a Celestia light node. The light node must be fully synced and funded for you to be able to submit and retrieve PayForBlobs to Mocha Testnet. This allows your rollup to post and retrieve data without any errors.

In order to mount existing data, you must have a node store that is in the default directory:

bash
$HOME/.celestia-light-mocha-4
$HOME/.celestia-light-mocha-4
bash
$HOME/.celestia-light
$HOME/.celestia-light
bash
$HOME/.celestia-light-arabica-11
$HOME/.celestia-light-arabica-11

By default, the node will run with the account named my_celes_key on Mocha. This is the account that needs to be funded.

TIP

Unless you changed your configuration, you won't have to change anything. 😎

Deploying a devnet to Mocha ​

See the Alt-DA x Celestia README for instructions on how to deploy a Devnet.

TIP for macOS users

If you are on macOS, you will need to run a venv before starting roll-op.

sh
cd $HOME/roll-op
+

Run an OP Stack rollup with Celestia underneath ​

This guide will show you how to run your own OP Stack devnet and testnet that posts data to Celestia's Mocha testnet using roll-op and op-plasma-celestia.

If you don't have devops experience and would like to use a Rollups as a Service (RaaS) provider, see the RaaS category in the menu.

Dependency setup ​

Setting up your light node ​

Sync and fund a Celestia light node. The light node must be fully synced and funded for you to be able to submit and retrieve PayForBlobs to Mocha Testnet. This allows your rollup to post and retrieve data without any errors.

In order to mount existing data, you must have a node store that is in the default directory:

bash
$HOME/.celestia-light-mocha-4
$HOME/.celestia-light-mocha-4
bash
$HOME/.celestia-light
$HOME/.celestia-light
bash
$HOME/.celestia-light-arabica-11
$HOME/.celestia-light-arabica-11

By default, the node will run with the account named my_celes_key on Mocha. This is the account that needs to be funded.

TIP

Unless you changed your configuration, you won't have to change anything. 😎

Deploying a devnet to Mocha ​

See the Alt-DA x Celestia README for instructions on how to deploy a Devnet.

TIP for macOS users

If you are on macOS, you will need to run a venv before starting roll-op.

sh
cd $HOME/roll-op
 python3 -m venv ./venv
 source ./venv/bin/activate
cd $HOME/roll-op
 python3 -m venv ./venv
@@ -83,8 +83,8 @@
 admin_account = "0xaddress"
 admin_key = "privatekey"
 p2p_sequencer_account = "0xaddress"
-p2p_sequencer_key = "privatekey"

Your 0xaddress key must also be funded with testnet ETH. We recommend at least 10 SepoliaETH to get your chain started, but you will need more to keep it running longer.

Congratulations ​

Congrats! You now have an OP Stack rollup running with Celestia underneath.

You can learn more about Alt-DA in Optimism docs.

- +p2p_sequencer_key = "privatekey"

Your 0xaddress key must also be funded with testnet ETH. We recommend at least 10 SepoliaETH to get your chain started, but you will need more to keep it running longer.

Congratulations ​

Congrats! You now have an OP Stack rollup running with Celestia underneath.

You can learn more about Alt-DA in Optimism docs.

+ \ No newline at end of file diff --git a/pr-1699/developers/prompt-scavenger.html b/pr-1699/developers/prompt-scavenger.html index 2273f49e1e..3886ad4e8e 100644 --- a/pr-1699/developers/prompt-scavenger.html +++ b/pr-1699/developers/prompt-scavenger.html @@ -11,7 +11,7 @@ - + @@ -456,8 +456,8 @@ } log.Printf("GPT-3 response: %s\n", promptAnswer) -}

And now you have the final version of the prompt scavenger!

Run the golang script with the following command:

sh
go run main.go <nodeIP> <namespace> <prompt>
go run main.go <nodeIP> <namespace> <prompt>

For example, you could run:

sh
go run main.go ws://localhost:26658 ce1e5714 'What is a modular blockchain?'
go run main.go ws://localhost:26658 ce1e5714 'What is a modular blockchain?'

After some time, it’ll post the output of the prompt you submitted to OpenAI that you pulled from Celestia’s blockchain.

Next steps ​

With this tutorial, you were able to construct a blob, submit it to Celestia, get it back from Celestia, decode its contents, then for added bonus, submit the message to GPT-3.5.

If you're up for a challenge, you can refer to the Node API client guide and try to implement more advanced features, such as:

  • Subscribing to new prompts inside the ce1e5714 namespace, submitting each one to GPT-3.5
  • Posting the responses back to Celestia under a different namespace.
- +}

And now you have the final version of the prompt scavenger!

Run the golang script with the following command:

sh
go run main.go <nodeIP> <namespace> <prompt>
go run main.go <nodeIP> <namespace> <prompt>

For example, you could run:

sh
go run main.go ws://localhost:26658 ce1e5714 'What is a modular blockchain?'
go run main.go ws://localhost:26658 ce1e5714 'What is a modular blockchain?'

After some time, it’ll post the output of the prompt you submitted to OpenAI that you pulled from Celestia’s blockchain.

Next steps ​

With this tutorial, you were able to construct a blob, submit it to Celestia, get it back from Celestia, decode its contents, then for added bonus, submit the message to GPT-3.5.

If you're up for a challenge, you can refer to the Node API client guide and try to implement more advanced features, such as:

  • Subscribing to new prompts inside the ce1e5714 namespace, submitting each one to GPT-3.5
  • Posting the responses back to Celestia under a different namespace.
+ \ No newline at end of file diff --git a/pr-1699/developers/rust-client-tutorial.html b/pr-1699/developers/rust-client-tutorial.html index 3e6311f235..f1b7ca408f 100644 --- a/pr-1699/developers/rust-client-tutorial.html +++ b/pr-1699/developers/rust-client-tutorial.html @@ -11,7 +11,7 @@ - + @@ -208,8 +208,8 @@ .share_get_eds(&latest_header) .await .expect("Failed to get EDS from latest header") -}

API documentation ​

To see the full list of available methods, see the API documentation.

- +}

API documentation ​

To see the full list of available methods, see the API documentation.

+ \ No newline at end of file diff --git a/pr-1699/developers/sp1-blobstream-deploy.html b/pr-1699/developers/sp1-blobstream-deploy.html index e91dd77394..dfb5bc4982 100644 --- a/pr-1699/developers/sp1-blobstream-deploy.html +++ b/pr-1699/developers/sp1-blobstream-deploy.html @@ -11,7 +11,7 @@ - + @@ -40,8 +40,8 @@

New SP1 Blobstream deployments ​

This document provides instructions for deploying SP1 Blobstream to a new chain.

SP1 Blobstream is the latest implementation of Blobstream in Rust using the SP1 zkVM.

Deploying the contracts ​

To deploy SP1 Blobstream to a new chain, follow these steps:

  1. Clone the sp1-blobstream repository:
shell
git clone https://github.com/succinctlabs/sp1-blobstream
 cd sp1-blobstream
git clone https://github.com/succinctlabs/sp1-blobstream
-cd sp1-blobstream

  1. Follow the deployment instructions in the sp1-blobstream README.

  2. If you're deploying on a chain where there isn't a canonical verifier listed in the SP1 contract addresses, you'll need to:

    a. Deploy your own SP1 Verifier from the sp1-contracts matching your sp1-sdk version. b. Set the SP1_VERIFIER_ADDRESS in your .env file to the address of your deployed verifier.

  3. To run the prover:

    • For local proving, set SP1_PROVER=local in your environment.
    • To use the Succinct Proving Network for remote proving, set SP1_PROVER=network.
    • We recommend an instance with 64 vCPU and 128GB of RAM for local proving.

Note: Any whitelisting for custom provers would need to be implemented in the application's smart contracts (e.g., by using an approvedProvers mapping).

- +cd sp1-blobstream

  1. Follow the deployment instructions in the sp1-blobstream README.

  2. If you're deploying on a chain where there isn't a canonical verifier listed in the SP1 contract addresses, you'll need to:

    a. Deploy your own SP1 Verifier from the sp1-contracts matching your sp1-sdk version. b. Set the SP1_VERIFIER_ADDRESS in your .env file to the address of your deployed verifier.

  3. To run the prover:

    • For local proving, set SP1_PROVER=local in your environment.
    • To use the Succinct Proving Network for remote proving, set SP1_PROVER=network.
    • We recommend an instance with 64 vCPU and 128GB of RAM for local proving.

Note: Any whitelisting for custom provers would need to be implemented in the application's smart contracts (e.g., by using an approvedProvers mapping).

+ \ No newline at end of file diff --git a/pr-1699/developers/submit-data.html b/pr-1699/developers/submit-data.html index 1e8f1fd494..fd43a4ef61 100644 --- a/pr-1699/developers/submit-data.html +++ b/pr-1699/developers/submit-data.html @@ -11,7 +11,7 @@ - + @@ -336,8 +336,8 @@ } return err -}

RPC to a celestia-node ​

Using the JSON RPC API, submit data using the following methods:

Learn more in the celestia-node API docs.

- +}

RPC to a celestia-node ​

Using the JSON RPC API, submit data using the following methods:

Learn more in the celestia-node API docs.

+ \ No newline at end of file diff --git a/pr-1699/developers/transaction-resubmission.html b/pr-1699/developers/transaction-resubmission.html index 167f91d802..59f6b9bca4 100644 --- a/pr-1699/developers/transaction-resubmission.html +++ b/pr-1699/developers/transaction-resubmission.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Transaction resubmission ​

In cases where transactions are not included within a 75-second window, resubmission is necessary. This is especially important during network congestion, as transactions with relatively low fees may not be processed even after the network clears up.

Regardless of whether they originate from celestia-app or celestia-node, transactions will not be re-gossiped, except in the presence of a new peer.

Monitoring and resubmission ​

Monitor the status of your transactions. If a transaction is not included within a 75-second window, it should be resubmitted. This can be done manually or through automated processes.

Changes introduced in celestiaorg/celestia-core#1089 may affect transaction gossiping and inclusion speed.

Notes ​

  • All transactions, regardless of their origin, are subject to being sorted and pruned based on fees.
  • It is the user or developer's responsibility to monitor and possibly resubmit transactions if they are not included in a 75-second window.
- +

Transaction resubmission ​

In cases where transactions are not included within a 75-second window, resubmission is necessary. This is especially important during network congestion, as transactions with relatively low fees may not be processed even after the network clears up.

Regardless of whether they originate from celestia-app or celestia-node, transactions will not be re-gossiped, except in the presence of a new peer.

Monitoring and resubmission ​

Monitor the status of your transactions. If a transaction is not included within a 75-second window, it should be resubmitted. This can be done manually or through automated processes.

Changes introduced in celestiaorg/celestia-core#1089 may affect transaction gossiping and inclusion speed.

Notes ​

  • All transactions, regardless of their origin, are subject to being sorted and pruned based on fees.
  • It is the user or developer's responsibility to monitor and possibly resubmit transactions if they are not included in a 75-second window.
+ \ No newline at end of file diff --git a/pr-1699/developers/wallets.html b/pr-1699/developers/wallets.html index 49aecde8ed..b58b449bbb 100644 --- a/pr-1699/developers/wallets.html +++ b/pr-1699/developers/wallets.html @@ -12,7 +12,7 @@ - + @@ -39,7 +39,7 @@

Appearance

Wallet integrations with Celestia ​

This page covers how developers can use Keplr and React to add Celestia network parameters to wallets, and how to add custom networks to Leap and Cosmostation.

Add Celestia network parameters to Keplr with React ​

Before we demonstrate how to export the specific parameters for Celestia's testnets, we need to create a ReactJS component that allows us to connect directly to Keplr and pass it the network parameters.

In the following code, we show how you can export a component that detects whether Keplr is installed and sets the network params for it:

jsx
// @site/src/components/AddNetworkKeplr.js
+

Wallet integrations with Celestia ​

This page covers how developers can use Keplr and React to add Celestia network parameters to wallets, and how to add custom networks to Leap and Cosmostation.

Add Celestia network parameters to Keplr with React ​

Before we demonstrate how to export the specific parameters for Celestia's testnets, we need to create a ReactJS component that allows us to connect directly to Keplr and pass it the network parameters.

In the following code, we show how you can export a component that detects whether Keplr is installed and sets the network params for it:

jsx
// @site/src/components/AddNetworkKeplr.js
 import React from "react";
 import styles from "./Keplr.module.css";
 
@@ -187,7 +187,7 @@
       </button>
     </div>
   );
-}

We still need to pass the Celestia network parameters to the AddNetworkKeplr function:

js
import '@site/src/components/AddNetworkKeplr'
+}

We still need to pass the Celestia network parameters to the AddNetworkKeplr function:

js
import '@site/src/components/AddNetworkKeplr'
 
 export const MAINNET_PARAMS = {`{
   chainId: 'celestia',
@@ -241,8 +241,8 @@
   rest: 'https://api.celestia-arabica-11.com'
 }`}
 
-{<AddNetworkKeplr params={ARABICA_PARAMS}/>}

Now, we can connect to the network that you would like to use in Keplr wallet.

Adding a custom chain to Leap ​

If you want to add a custom chain to Leap, you can do so by:

  1. Clicking the Cosmos logo in the top corner of Leap wallet
  2. Scrolling down and clicking "Add new chain"

You can then add the following parameters:

  • Chain Id: arabica-11
  • Chain Name: Arabica devnet
  • New RPC URL: https://rpc.celestia-arabica-11.com/
  • New REST URL: https://api.celestia-arabica-11.com
  • Address Prefix: celestia
  • Native Denom: utia
  • Coin Type: 118
  • Decimals: 6
  • Block explorer URL (optional): https://explorer.celestia-arabica-10.com

Now, click Add chain and you will be able to view your Arabica account balance and transactions in Leap wallet.

You'll see that you're connected to Arabica Devnet.

Adding a custom chain to Cosmostation ​

Click the hamburger menu icon in the top corner of Cosmostation wallet. Scroll down and click "Add Custom Chain"

You can then add the following parameters:

  • Custom Chain name: Mocha testnet
  • Rest URL: https://api-mocha.pops.one
  • New RPC URL: https://rpc-mocha.pops.one
  • Currency symbol: TIA
  • Address prefix: celestia
  • Denom: utia
  • Symbol image URL (optional): https://raw.githubusercontent.com/cosmos/chain-registry/master/testnets/celestiatestnet/images/celestia.svg
  • Explorer URL (optional): https://testnet.mintscan.io/celestia-testnet
  • Coin Type: 118
  • Decimals: 6
  • Gas rate Tiny: 0.1
  • Gas rate Low: 0.25
  • Gas rate Average: 0.5

Now, click Add a custom chain and you will be able to view your Celestia account balance and transactions in Cosmostation wallet.

Switch chains to "Mocha testnet" and you'll see that you're connected to Celestia's Mocha testnet!

- +{<AddNetworkKeplr params={ARABICA_PARAMS}/>}

Now, we can connect to the network that you would like to use in Keplr wallet.

Adding a custom chain to Leap ​

If you want to add a custom chain to Leap, you can do so by:

  1. Clicking the Cosmos logo in the top corner of Leap wallet
  2. Scrolling down and clicking "Add new chain"

You can then add the following parameters:

  • Chain Id: arabica-11
  • Chain Name: Arabica devnet
  • New RPC URL: https://rpc.celestia-arabica-11.com/
  • New REST URL: https://api.celestia-arabica-11.com
  • Address Prefix: celestia
  • Native Denom: utia
  • Coin Type: 118
  • Decimals: 6
  • Block explorer URL (optional): https://explorer.celestia-arabica-10.com

Now, click Add chain and you will be able to view your Arabica account balance and transactions in Leap wallet.

You'll see that you're connected to Arabica Devnet.

Adding a custom chain to Cosmostation ​

Click the hamburger menu icon in the top corner of Cosmostation wallet. Scroll down and click "Add Custom Chain"

You can then add the following parameters:

  • Custom Chain name: Mocha testnet
  • Rest URL: https://api-mocha.pops.one
  • New RPC URL: https://rpc-mocha.pops.one
  • Currency symbol: TIA
  • Address prefix: celestia
  • Denom: utia
  • Symbol image URL (optional): https://raw.githubusercontent.com/cosmos/chain-registry/master/testnets/celestiatestnet/images/celestia.svg
  • Explorer URL (optional): https://testnet.mintscan.io/celestia-testnet
  • Coin Type: 118
  • Decimals: 6
  • Gas rate Tiny: 0.1
  • Gas rate Low: 0.25
  • Gas rate Average: 0.5

Now, click Add a custom chain and you will be able to view your Celestia account balance and transactions in Cosmostation wallet.

Switch chains to "Mocha testnet" and you'll see that you're connected to Celestia's Mocha testnet!

+ \ No newline at end of file diff --git a/pr-1699/hashmap.json b/pr-1699/hashmap.json index ac94e6e881..f6c361d30b 100644 --- a/pr-1699/hashmap.json +++ b/pr-1699/hashmap.json @@ -1 +1 @@ -{"community_modular-meetup-guide.md":"3d71d8e8","community_speaker-list.md":"716e09e6","community_overview.md":"aec66ec4","developers_arbitrum-dapp-deploy.md":"26b815d3","community_calendar.md":"5a6b1214","developers_blobstream-x-requesting-data-commitment-ranges.md":"409fcb45","developers_blobstream.md":"c9e61c23","developers_blobstreamx.md":"67c7a6c7","developers_bubs-testnet.md":"c168048a","readme.md":"44659d85","community_coc.md":"db13614f","developers_blobstream-x-deploy.md":"e0b78833","developers_arbitrum-integration.md":"2b72ec21","developers_ethereum-fallback.md":"00e7ac0b","developers_blobstream-contracts.md":"25c4c416","developers_arbitrum-bridge.md":"d7cda10d","community_modular-meetup-toolkit.md":"f6184c46","developers_blobstream-offchain.md":"3b490822","developers_arbitrum-full-node.md":"09e489d4","developers_gm-portal-bubs.md":"2e8017d7","developers_deploy-on-bubs.md":"97e444d7","learn_paying-for-blobspace.md":"61719f03","developers_sp1-blobstream-deploy.md":"b0ce75b2","nodes_celestia-node-trusted-hash.md":"4094be4e","developers_build-whatever.md":"4b64aa7d","developers_prompt-scavenger.md":"fea07a57","developers_blobstream-rollups.md":"580268e1","developers_optimism-devnet.md":"6da256da","developers_arbitrum-smart-contract.md":"5de83013","developers_feegrant-for-blobs.md":"7c93aaff","community_modular-meetup-intro.md":"1b04ad48","developers_integrate-celestia.md":"871c3298","developers_celestia-node-key.md":"93827487","community_foundation-delegation-program.md":"abd31332","developers_full-stack-modular-development-guide.md":"3910bdad","developers_arbitrum-deploy.md":"c142d06c","nodes_hardfork-process.md":"d852b283","nodes_bridge-node.md":"71e96d87","developers_blobstream-proof-queries.md":"21c99b59","developers_submit-data.md":"506ef31e","nodes_celestia-node.md":"2de1eba4","nodes_config-toml.md":"cfad1001","nodes_celestia-app-multisig.md":"cf17caf2","nodes_consensus-node.md":"c0f03057","nodes_decide-node.md":"ce340382","nodes_environment.md":"d3b85368","learn_how-celestia-works_transaction-lifecycle.md":"d8853cb7","learn_how-to-stake-tia.md":"f5076e81","nodes_mocha-testnet.md":"58edd1a9","index.md":"d57eea6f","nodes_overview.md":"8cf8c5aa","nodes_mainnet.md":"0230b2ce","nodes_participate.md":"cd0dcc78","nodes_quick-start.md":"7f0ce7b8","nodes_systemd.md":"794b3b4f","developers_rust-client-tutorial.md":"df611bd3","developers_node-api.md":"8d88dab0","nodes_validator-node.md":"2b9abf8d","nodes_celestia-app-wallet.md":"47e26967","nodes_celestia-app.md":"6fd2fd36","developers_node-tutorial.md":"358f7307","developers_intro-to-op-stack.md":"c09be10b","nodes_instantiate-testnet.md":"46c96647","nodes_celestia-node-custom-networks.md":"759a61e7","nodes_light-node.md":"c1fa0172","nodes_celestia-node-metrics.md":"6d2f305e","nodes_celestia-app-commands.md":"0be51395","nodes_celestia-node-troubleshooting.md":"6134a7ab","community_itn-tos.md":"23529d8e","nodes_full-storage-node.md":"3d825d2f","developers_multiaccounts.md":"5fe51e02","learn_how-celestia-works_data-availability-faq.md":"506e0c10","learn_tia.md":"6fd97b1e","learn_how-celestia-works_overview.md":"e560d4a4","nodes_celestia-app-vesting.md":"e8ca90cc","nodes_ibc-relayer.md":"3c1ba349","developers_optimism.md":"363527ac","nodes_celestia-app-metrics.md":"ba859d9d","learn_retrievability.md":"8931b632","developers_golang-client-tutorial.md":"0dce1977","nodes_celestia-app-slashing.md":"c061c14c","learn_staking-governance-supply.md":"2093ea4e","learn_staking.md":"9713419c","nodes_docker-images.md":"c689a2da","developers_transaction-resubmission.md":"2c716084","nodes_celestia-app-upgrade-monitor.md":"c2b31db9","learn_how-celestia-works_monolithic-vs-modular.md":"8f0114bd","nodes_arabica-devnet.md":"960dc284","developers_wallets.md":"c5fba5d1","learn_how-celestia-works_data-availability-layer.md":"d71fa908"} +{"readme.md":"ebe4136d","developers_intro-to-op-stack.md":"2deb5540","nodes_celestia-node-metrics.md":"e49bb967","developers_arbitrum-full-node.md":"319badbc","community_calendar.md":"f70856a8","developers_optimism-devnet.md":"3b3f49a3","developers_blobstream-x-deploy.md":"6ed5e09e","developers_ethereum-fallback.md":"764773da","community_overview.md":"fb9fd608","developers_gm-portal-bubs.md":"cd727490","developers_arbitrum-dapp-deploy.md":"4b34cdb2","developers_arbitrum-smart-contract.md":"8b7aa3c4","developers_integrate-celestia.md":"cabcfa45","developers_golang-client-tutorial.md":"727ea5e8","community_itn-tos.md":"6454438f","community_foundation-delegation-program.md":"ff7a7f05","developers_feegrant-for-blobs.md":"84d98514","developers_deploy-on-bubs.md":"f7abcbb6","developers_blobstream-rollups.md":"9c8cb137","community_modular-meetup-intro.md":"b7a491a8","developers_bubs-testnet.md":"ddf17ba1","developers_blobstreamx.md":"7838cfd1","developers_blobstream-x-requesting-data-commitment-ranges.md":"adbc6c7c","developers_blobstream-offchain.md":"fbd363f2","developers_wallets.md":"b2bd7cc6","developers_sp1-blobstream-deploy.md":"e4975a52","learn_how-celestia-works_data-availability-faq.md":"b4d6ab8b","learn_how-celestia-works_monolithic-vs-modular.md":"63b4aa3e","learn_how-to-stake-tia.md":"68dbd46b","learn_paying-for-blobspace.md":"06ae9c17","developers_arbitrum-deploy.md":"26acb828","learn_retrievability.md":"d1e1d36b","nodes_celestia-app-multisig.md":"4833031c","developers_prompt-scavenger.md":"ae717331","nodes_docker-images.md":"01970048","nodes_celestia-node-troubleshooting.md":"d5102d28","nodes_full-storage-node.md":"27554da6","nodes_celestia-node.md":"b506c65d","developers_optimism.md":"d6e1e2ee","developers_rust-client-tutorial.md":"168637c4","index.md":"7de6d8b3","nodes_config-toml.md":"ea91864b","nodes_consensus-node.md":"99f6268d","nodes_decide-node.md":"12527b86","nodes_celestia-node-trusted-hash.md":"941c6f87","nodes_arabica-devnet.md":"5fbea086","nodes_celestia-app-metrics.md":"0b6cb333","developers_blobstream-contracts.md":"06e023da","nodes_celestia-app-wallet.md":"70b5fba3","community_modular-meetup-toolkit.md":"0a2e761b","nodes_celestia-node-custom-networks.md":"aac3b114","community_speaker-list.md":"872a3b69","developers_arbitrum-bridge.md":"8c851802","community_coc.md":"de9fdd2a","developers_node-tutorial.md":"79e6f899","learn_tia.md":"9065ce93","nodes_environment.md":"502fd51d","nodes_celestia-app-upgrade-monitor.md":"0555c2d4","developers_blobstream-proof-queries.md":"19225b90","developers_blobstream.md":"4afef8bd","community_modular-meetup-guide.md":"6b50cb94","developers_arbitrum-integration.md":"fd5df284","learn_how-celestia-works_data-availability-layer.md":"4a9aff1a","nodes_celestia-app.md":"e09a3b72","nodes_celestia-app-vesting.md":"e829dc7e","learn_staking-governance-supply.md":"0d21fda6","nodes_celestia-app-commands.md":"16f0c3b5","developers_full-stack-modular-development-guide.md":"766923fe","nodes_celestia-app-slashing.md":"5b9f9df0","developers_multiaccounts.md":"6ee7c0ad","learn_how-celestia-works_overview.md":"42a4dc74","learn_how-celestia-works_transaction-lifecycle.md":"def776d7","nodes_hardfork-process.md":"b85c06e7","developers_node-api.md":"6709e8d4","learn_staking.md":"f13c2e81","developers_transaction-resubmission.md":"ebf49e01","developers_celestia-node-key.md":"fe2dab0d","nodes_light-node.md":"f1dd6ad1","nodes_bridge-node.md":"40517142","developers_submit-data.md":"7f90d09f","nodes_systemd.md":"66ed5d05","nodes_validator-node.md":"084b1069","developers_build-whatever.md":"5677fdce","nodes_mocha-testnet.md":"0e4cf674","nodes_mainnet.md":"0bba5c8e","nodes_overview.md":"4223caea","nodes_participate.md":"704b27c3","nodes_quick-start.md":"9a9eabfc","nodes_ibc-relayer.md":"450545b1","nodes_instantiate-testnet.md":"4b062bf6"} diff --git a/pr-1699/img/learn/Celestia_TIA_Allocation_at_Genesis.png b/pr-1699/img/learn/Celestia_TIA_Allocation_at_Genesis.png index 1dc9b99b9a..b2acf3c74e 100644 Binary files a/pr-1699/img/learn/Celestia_TIA_Allocation_at_Genesis.png and b/pr-1699/img/learn/Celestia_TIA_Allocation_at_Genesis.png differ diff --git a/pr-1699/index.html b/pr-1699/index.html index 83cc7c5d06..2c67395eec 100644 --- a/pr-1699/index.html +++ b/pr-1699/index.html @@ -11,7 +11,7 @@ - + @@ -39,7 +39,7 @@

Appearance

- + \ No newline at end of file diff --git a/pr-1699/learn/how-celestia-works/data-availability-faq.html b/pr-1699/learn/how-celestia-works/data-availability-faq.html index f6bb6321a0..b182e80770 100644 --- a/pr-1699/learn/how-celestia-works/data-availability-faq.html +++ b/pr-1699/learn/how-celestia-works/data-availability-faq.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Data availability FAQ ​

What is data availability? ​

Data availability answers the question, has this data been published? Specifically, a node will verify data availability when it receives a new block that is getting added to the chain. The node will attempt to download all the transaction data for the new block to verify availability. If the node can download all the transaction data, then it successfully verified data availability, proving that the block data was actually published to the network.

Modular VS Monolithic

As you’ll see, modular blockchains like Celestia employ other primitives that allow nodes to verify data availability more efficiently. Data availability is critical to the security of any blockchain because it ensures that anyone can inspect the ledger of transactions and verify it. Data availability becomes particularly problematic when scaling blockchains. As the blocks get bigger, it becomes impractical for normal users to download all the data, and therefore users can no longer verify the chain.

What is the data availability problem? ​

The problem with data availability occurs when the transaction data for a newly proposed block cannot be downloaded and verified. This type of attack by a block producer is called a data withholding attack, which sees the block producer withhold transaction data of a new block.

Since transaction data is withheld, nodes cannot update to the latest state. Such an attack can have numerous consequences, from halting a chain to gaining the ability to steal funds. The severity of the consequences will depend on the type of blockchain (L1 or L2) and whether data availability is kept onchain or offchain. The data availability problem commonly arises around L2 scaling solutions like rollups and validiums.

How do nodes verify data availability in Celestia? ​

In most blockchains, nodes that verify data availability do so by downloading all transaction data for a block. If they are able to download all the data, they have verified its availability. In Celestia, light nodes have access to a new mechanism to verify data availability without needing to download all the data for a block. This new primitive for verifying data availability is called data availability sampling.

What is data availability sampling? ​

Data availability sampling is a mechanism for light nodes to verify data availability without having to download all data for a block. Data availability sampling (DAS) works by having light nodes conduct multiple rounds of random sampling for small portions of block data. As a light node completes more rounds of sampling for block data, it increases its confidence that data is available. Once the light node successfully reaches a predetermined confidence level (e.g. 99%) it will consider the block data as available.

Want a simpler explanation? Check out this thread on how data availability sampling is like flipping a coin.

What are some of the security assumptions that Celestia makes for data availability sampling? ​

Celestia assumes that there is a minimum number of light nodes that are conducting data availability sampling for a given block size. This assumption is necessary so that a full node can reconstruct an entire block from the portions of data light nodes sampled and stored. The amount of light nodes that are needed will depend on the block size - for bigger blocks more light nodes are assumed to be running.

A second notable assumption that is made by light nodes is that they are connected to at least one honest full node. This ensures that they can receive fraud proofs for incorrectly erasure coded blocks. If a light node is not connected to an honest full node, such as during an eclipse attack, it can’t verify that the block is improperly constructed.

Why is block reconstruction necessary for security? ​

In Celestia, blocks need to be erasure coded so that there is redundant data to aid the data availability sampling process. However, nodes tasked with erasure coding the data could do so incorrectly. Since Celestia uses fraud proofs to verify that erasure coding is incorrect, the full block data is needed to generate a bad encoding fraud proof.

There could be a situation where validators only provide data to light nodes and not full nodes. If the full nodes don’t have the ability to reconstruct the full block from the portions of data stored by light nodes, they wouldn’t be able to generate a bad encoding fraud proof.

What is data storage? ​

Data storage is concerned with the ability to store and access past transaction data.

Modular VS Monolithic

Data storage and retrieval is needed for multiple purposes, such as:

  • Reading the information of a previous transaction
  • Syncing a node
  • Indexing and serving transaction data
  • Retrieving NFT information

What is the problem around data storage? ​

The issue with data storage is whether past transaction data can be stored and successfully retrieved at a later time. The inability to retrieve historical transaction data can cause problems, such as users being unable to access information about their past transactions or nodes that cannot sync from genesis. Luckily, the assumptions around storing and accessing past data are weak. Only a single copy of a blockchain’s history needs to be accessible for users to gain access to historical transaction data. In other words, data storage security is a 1 of N honesty assumption.

What is the difference between data availability and data storage? ​

Data availability is about verifying that transaction data for a new block is public and available. In contrast, data storage involves storing and accessing past transaction data from old blocks.

Where does blockchain state fit into this? ​

Up until now it’s been all about transaction data, but blockchain state is a related topic. The state is different from transaction data. Specifically, the state is like a current snapshot of the network, which includes information about account balances, smart contract balances, and validator set info. Problems that arise from the size of the state are different in nature than those around data availability and retrievability.

Why doesn’t Celestia incentivize storage of historical data? ​

Most blockchains don’t incentivize storage of data because it shouldn’t be the responsibility of a blockchain to guarantee past data will be retrievable forever. In addition, the data storage problem only requires a single party to store and provide the data for users, which is not a strong problem. As such, Celestia’s purpose is to provide a secure and scalable way to verify the availability of data. Once data has been verified as available, the job of storing and retrieving historical data is left up to other entities that require the data. Luckily, there are natural incentives for outside parties to store and serve historical data to users.

Who may store historical data if there is no reward? ​

There are multiple types of actors that may be likely to store historical data. Some of those include:

  • Block explorers that provide access to past transaction data.
  • Indexers that provide API queries for past data.
  • Applications or rollups that require historical data for certain processes.
  • Users that want to guarantee that they will have access to their transaction history.

What are some things blockchains can do to provide stronger assurances of data retrievability? ​

  • Reward nodes based on the amount of transaction data they store and requests for data they serve (this is the case with some data storage blockchains, like Filecoin).
  • Publish transaction data onto a data storage blockchain that incentivizes storing and serving requests for historical data.
- +

Data availability FAQ ​

What is data availability? ​

Data availability answers the question, has this data been published? Specifically, a node will verify data availability when it receives a new block that is getting added to the chain. The node will attempt to download all the transaction data for the new block to verify availability. If the node can download all the transaction data, then it successfully verified data availability, proving that the block data was actually published to the network.

Modular VS Monolithic

As you’ll see, modular blockchains like Celestia employ other primitives that allow nodes to verify data availability more efficiently. Data availability is critical to the security of any blockchain because it ensures that anyone can inspect the ledger of transactions and verify it. Data availability becomes particularly problematic when scaling blockchains. As the blocks get bigger, it becomes impractical for normal users to download all the data, and therefore users can no longer verify the chain.

What is the data availability problem? ​

The problem with data availability occurs when the transaction data for a newly proposed block cannot be downloaded and verified. This type of attack by a block producer is called a data withholding attack, which sees the block producer withhold transaction data of a new block.

Since transaction data is withheld, nodes cannot update to the latest state. Such an attack can have numerous consequences, from halting a chain to gaining the ability to steal funds. The severity of the consequences will depend on the type of blockchain (L1 or L2) and whether data availability is kept onchain or offchain. The data availability problem commonly arises around L2 scaling solutions like rollups and validiums.

How do nodes verify data availability in Celestia? ​

In most blockchains, nodes that verify data availability do so by downloading all transaction data for a block. If they are able to download all the data, they have verified its availability. In Celestia, light nodes have access to a new mechanism to verify data availability without needing to download all the data for a block. This new primitive for verifying data availability is called data availability sampling.

What is data availability sampling? ​

Data availability sampling is a mechanism for light nodes to verify data availability without having to download all data for a block. Data availability sampling (DAS) works by having light nodes conduct multiple rounds of random sampling for small portions of block data. As a light node completes more rounds of sampling for block data, it increases its confidence that data is available. Once the light node successfully reaches a predetermined confidence level (e.g. 99%) it will consider the block data as available.

Want a simpler explanation? Check out this thread on how data availability sampling is like flipping a coin.

What are some of the security assumptions that Celestia makes for data availability sampling? ​

Celestia assumes that there is a minimum number of light nodes that are conducting data availability sampling for a given block size. This assumption is necessary so that a full node can reconstruct an entire block from the portions of data light nodes sampled and stored. The amount of light nodes that are needed will depend on the block size - for bigger blocks more light nodes are assumed to be running.

A second notable assumption that is made by light nodes is that they are connected to at least one honest full node. This ensures that they can receive fraud proofs for incorrectly erasure coded blocks. If a light node is not connected to an honest full node, such as during an eclipse attack, it can’t verify that the block is improperly constructed.

Why is block reconstruction necessary for security? ​

In Celestia, blocks need to be erasure coded so that there is redundant data to aid the data availability sampling process. However, nodes tasked with erasure coding the data could do so incorrectly. Since Celestia uses fraud proofs to verify that erasure coding is incorrect, the full block data is needed to generate a bad encoding fraud proof.

There could be a situation where validators only provide data to light nodes and not full nodes. If the full nodes don’t have the ability to reconstruct the full block from the portions of data stored by light nodes, they wouldn’t be able to generate a bad encoding fraud proof.

What is data storage? ​

Data storage is concerned with the ability to store and access past transaction data.

Modular VS Monolithic

Data storage and retrieval is needed for multiple purposes, such as:

  • Reading the information of a previous transaction
  • Syncing a node
  • Indexing and serving transaction data
  • Retrieving NFT information

What is the problem around data storage? ​

The issue with data storage is whether past transaction data can be stored and successfully retrieved at a later time. The inability to retrieve historical transaction data can cause problems, such as users being unable to access information about their past transactions or nodes that cannot sync from genesis. Luckily, the assumptions around storing and accessing past data are weak. Only a single copy of a blockchain’s history needs to be accessible for users to gain access to historical transaction data. In other words, data storage security is a 1 of N honesty assumption.

What is the difference between data availability and data storage? ​

Data availability is about verifying that transaction data for a new block is public and available. In contrast, data storage involves storing and accessing past transaction data from old blocks.

Where does blockchain state fit into this? ​

Up until now it’s been all about transaction data, but blockchain state is a related topic. The state is different from transaction data. Specifically, the state is like a current snapshot of the network, which includes information about account balances, smart contract balances, and validator set info. Problems that arise from the size of the state are different in nature than those around data availability and retrievability.

Why doesn’t Celestia incentivize storage of historical data? ​

Most blockchains don’t incentivize storage of data because it shouldn’t be the responsibility of a blockchain to guarantee past data will be retrievable forever. In addition, the data storage problem only requires a single party to store and provide the data for users, which is not a strong problem. As such, Celestia’s purpose is to provide a secure and scalable way to verify the availability of data. Once data has been verified as available, the job of storing and retrieving historical data is left up to other entities that require the data. Luckily, there are natural incentives for outside parties to store and serve historical data to users.

Who may store historical data if there is no reward? ​

There are multiple types of actors that may be likely to store historical data. Some of those include:

  • Block explorers that provide access to past transaction data.
  • Indexers that provide API queries for past data.
  • Applications or rollups that require historical data for certain processes.
  • Users that want to guarantee that they will have access to their transaction history.

What are some things blockchains can do to provide stronger assurances of data retrievability? ​

  • Reward nodes based on the amount of transaction data they store and requests for data they serve (this is the case with some data storage blockchains, like Filecoin).
  • Publish transaction data onto a data storage blockchain that incentivizes storing and serving requests for historical data.
+ \ No newline at end of file diff --git a/pr-1699/learn/how-celestia-works/data-availability-layer.html b/pr-1699/learn/how-celestia-works/data-availability-layer.html index ece88aab2c..9d756602f5 100644 --- a/pr-1699/learn/how-celestia-works/data-availability-layer.html +++ b/pr-1699/learn/how-celestia-works/data-availability-layer.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Celestia's data availability layer ​

Celestia is a data availability (DA) layer that provides a scalable solution to the data availability problem. Due to the permissionless nature of the blockchain networks, a DA layer must provide a mechanism for the execution and settlement layers to check in a trust-minimized way whether transaction data is indeed available.

Two key features of Celestia's DA layer are data availability sampling (DAS) and Namespaced Merkle trees (NMTs). Both features are novel blockchain scaling solutions: DAS enables light nodes to verify data availability without needing to download an entire block; NMTs enable execution and settlement layers on Celestia to download transactions that are only relevant to them.

Data availability sampling (DAS) ​

In general, light nodes download only block headers that contain commitments (i.e., Merkle roots) of the block data (i.e., the list of transactions).

To make DAS possible, Celestia uses a 2-dimensional Reed-Solomon encoding scheme to encode the block data: every block data is split into k×k shares, arranged in a k×k matrix, and extended with parity data into a 2k×2k extended matrix by applying multiple times Reed-Solomon encoding.

Then, 4k separate Merkle roots are computed for the rows and columns of the extended matrix; the Merkle root of these Merkle roots is used as the block data commitment in the block header.

2D Reed-Soloman (RS) Encoding

To verify that the data is available, Celestia light nodes are sampling the 2k×2k data shares.

Every light node randomly chooses a set of unique coordinates in the extended matrix and queries full nodes for the data shares and the corresponding Merkle proofs at those coordinates. If light nodes receive a valid response for each sampling query, then there is a high probability guarantee that the whole block's data is available.

Additionally, every received data share with a correct Merkle proof is gossiped to the network. As a result, as long as the Celestia light nodes are sampling together enough data shares (i.e., at least k×k unique shares), the full block can be recovered by honest full nodes.

For more details on DAS, take a look at the original paper.

Scalability ​

DAS enables Celestia to scale the DA layer. DAS can be performed by resource-limited light nodes since each light node only samples a small portion of the block data. The more light nodes there are in the network, the more data they can collectively download and store.

This means that increasing the number of light nodes performing DAS allows for larger blocks (i.e., with more transactions), while still keeping DAS feasible for resource-limited light nodes. However, in order to validate block headers, Celestia light nodes need to download the 4k intermediate Merkle roots.

For a block data size of n2 bytes, this means that every light node must download O(n) bytes. Therefore, any improvement in the bandwidth capacity of Celestia light nodes has a quadratic effect on the throughput of Celestia's DA layer.

Fraud proofs of incorrectly extended data ​

The requirement of downloading the 4k intermediate Merkle roots is a consequence of using a 2-dimensional Reed-Solomon encoding scheme. Alternatively, DAS could be designed with a standard (i.e., 1-dimensional) Reed-Solomon encoding, where the original data is split into k shares and extended with k additional shares of parity data. Since the block data commitment is the Merkle root of the 2k resulting data shares, light nodes no longer need to download O(n) bytes to validate block headers.

The downside of the standard Reed-Solomon encoding is dealing with malicious block producers that generate the extended data incorrectly.

This is possible as Celestia does not require a majority of the consensus (i.e., block producers) to be honest to guarantee data availability. Thus, if the extended data is invalid, the original data might not be recoverable, even if the light nodes are sampling sufficient unique shares (i.e., at least k for a standard encoding and k×k for a 2-dimensional encoding).

As a solution, Fraud Proofs of Incorrectly Generated Extended Data enable light nodes to reject blocks with invalid extended data. Such proofs require reconstructing the encoding and verifying the mismatch. With standard Reed-Solomon encoding, this entails downloading the original data, i.e., n2 bytes. Contrastingly, with 2-dimensional Reed-Solomon encoding, only O(n) bytes are required as it is sufficient to verify only one row or one column of the extended matrix.

Namespaced Merkle trees (NMTs) ​

Celestia partitions the block data into multiple namespaces, one for every application (e.g., rollup) using the DA layer. As a result, every application needs to download only its own data and can ignore the data of other applications.

For this to work, the DA layer must be able to prove that the provided data is complete, i.e., all the data for a given namespace is returned. To this end, Celestia is using Namespaced Merkle trees (NMTs).

An NMT is a Merkle tree with the leafs ordered by the namespace identifiers and the hash function modified so that every node in the tree includes the range of namespaces of all its descendants. The following figure shows an example of an NMT with height three (i.e., eight data shares). The data is partitioned into three namespaces.

Namespaced Merkle Tree

When an application requests the data for namespace 2, the DA layer must provide the data shares D3, D4, D5, and D6 and the nodes N2, N8 and N7 as proof (note that the application already has the root N14 from the block header).

As a result, the application is able to check that the provided data is part of the block data. Furthermore, the application can verify that all the data for namespace 2 was provided. If the DA layer provides for example only the data shares D4 and D5, it must also provide nodes N12 and N11 as proofs. However, the application can identify that the data is incomplete by checking the namespace range of the two nodes, i.e., both N12 and N11 have descendants part of namespace 2.

For more details on NMTs, refer to the original paper.

Building a PoS blockchain for DA ​

Providing data availability ​

The Celestia DA layer consists of a PoS blockchain. Celestia is dubbing this blockchain as the celestia-app, an application that provides transactions to facilitate the DA layer and is built using Cosmos SDK. The following figure shows the main components of celestia-app.

Main components of celestia-app

celestia-app is built on top of celestia-core, a modified version of the Tendermint consensus algorithm. Among the more important changes to vanilla Tendermint, celestia-core:

  • Enables the erasure coding of block data (using the 2-dimensional Reed-Solomon encoding scheme).
  • Replaces the regular Merkle tree used by Tendermint to store block data with a Namespaced Merkle tree that enables the above layers (i.e., execution and settlement) to only download the needed data (for more details, see the section below describing use cases).

For more details on the changes to Tendermint, take a look at the ADRs. Notice that celestia-core nodes are still using the Tendermint p2p network.

Similarly to Tendermint, celestia-core is connected to the application layer (i.e., the state machine) by ABCI++, a major evolution of ABCI (Application Blockchain Interface).

The celestia-app state machine is necessary to execute the PoS logic and to enable the governance of the DA layer.

However, the celestia-app is data-agnostic -- the state machine neither validates nor stores the data that is made available by the celestia-app.

- +

Celestia's data availability layer ​

Celestia is a data availability (DA) layer that provides a scalable solution to the data availability problem. Due to the permissionless nature of the blockchain networks, a DA layer must provide a mechanism for the execution and settlement layers to check in a trust-minimized way whether transaction data is indeed available.

Two key features of Celestia's DA layer are data availability sampling (DAS) and Namespaced Merkle trees (NMTs). Both features are novel blockchain scaling solutions: DAS enables light nodes to verify data availability without needing to download an entire block; NMTs enable execution and settlement layers on Celestia to download transactions that are only relevant to them.

Data availability sampling (DAS) ​

In general, light nodes download only block headers that contain commitments (i.e., Merkle roots) of the block data (i.e., the list of transactions).

To make DAS possible, Celestia uses a 2-dimensional Reed-Solomon encoding scheme to encode the block data: every block data is split into k×k shares, arranged in a k×k matrix, and extended with parity data into a 2k×2k extended matrix by applying multiple times Reed-Solomon encoding.

Then, 4k separate Merkle roots are computed for the rows and columns of the extended matrix; the Merkle root of these Merkle roots is used as the block data commitment in the block header.

2D Reed-Soloman (RS) Encoding

To verify that the data is available, Celestia light nodes are sampling the 2k×2k data shares.

Every light node randomly chooses a set of unique coordinates in the extended matrix and queries full nodes for the data shares and the corresponding Merkle proofs at those coordinates. If light nodes receive a valid response for each sampling query, then there is a high probability guarantee that the whole block's data is available.

Additionally, every received data share with a correct Merkle proof is gossiped to the network. As a result, as long as the Celestia light nodes are sampling together enough data shares (i.e., at least k×k unique shares), the full block can be recovered by honest full nodes.

For more details on DAS, take a look at the original paper.

Scalability ​

DAS enables Celestia to scale the DA layer. DAS can be performed by resource-limited light nodes since each light node only samples a small portion of the block data. The more light nodes there are in the network, the more data they can collectively download and store.

This means that increasing the number of light nodes performing DAS allows for larger blocks (i.e., with more transactions), while still keeping DAS feasible for resource-limited light nodes. However, in order to validate block headers, Celestia light nodes need to download the 4k intermediate Merkle roots.

For a block data size of n2 bytes, this means that every light node must download O(n) bytes. Therefore, any improvement in the bandwidth capacity of Celestia light nodes has a quadratic effect on the throughput of Celestia's DA layer.

Fraud proofs of incorrectly extended data ​

The requirement of downloading the 4k intermediate Merkle roots is a consequence of using a 2-dimensional Reed-Solomon encoding scheme. Alternatively, DAS could be designed with a standard (i.e., 1-dimensional) Reed-Solomon encoding, where the original data is split into k shares and extended with k additional shares of parity data. Since the block data commitment is the Merkle root of the 2k resulting data shares, light nodes no longer need to download O(n) bytes to validate block headers.

The downside of the standard Reed-Solomon encoding is dealing with malicious block producers that generate the extended data incorrectly.

This is possible as Celestia does not require a majority of the consensus (i.e., block producers) to be honest to guarantee data availability. Thus, if the extended data is invalid, the original data might not be recoverable, even if the light nodes are sampling sufficient unique shares (i.e., at least k for a standard encoding and k×k for a 2-dimensional encoding).

As a solution, Fraud Proofs of Incorrectly Generated Extended Data enable light nodes to reject blocks with invalid extended data. Such proofs require reconstructing the encoding and verifying the mismatch. With standard Reed-Solomon encoding, this entails downloading the original data, i.e., n2 bytes. Contrastingly, with 2-dimensional Reed-Solomon encoding, only O(n) bytes are required as it is sufficient to verify only one row or one column of the extended matrix.

Namespaced Merkle trees (NMTs) ​

Celestia partitions the block data into multiple namespaces, one for every application (e.g., rollup) using the DA layer. As a result, every application needs to download only its own data and can ignore the data of other applications.

For this to work, the DA layer must be able to prove that the provided data is complete, i.e., all the data for a given namespace is returned. To this end, Celestia is using Namespaced Merkle trees (NMTs).

An NMT is a Merkle tree with the leafs ordered by the namespace identifiers and the hash function modified so that every node in the tree includes the range of namespaces of all its descendants. The following figure shows an example of an NMT with height three (i.e., eight data shares). The data is partitioned into three namespaces.

Namespaced Merkle Tree

When an application requests the data for namespace 2, the DA layer must provide the data shares D3, D4, D5, and D6 and the nodes N2, N8 and N7 as proof (note that the application already has the root N14 from the block header).

As a result, the application is able to check that the provided data is part of the block data. Furthermore, the application can verify that all the data for namespace 2 was provided. If the DA layer provides for example only the data shares D4 and D5, it must also provide nodes N12 and N11 as proofs. However, the application can identify that the data is incomplete by checking the namespace range of the two nodes, i.e., both N12 and N11 have descendants part of namespace 2.

For more details on NMTs, refer to the original paper.

Building a PoS blockchain for DA ​

Providing data availability ​

The Celestia DA layer consists of a PoS blockchain. Celestia is dubbing this blockchain as the celestia-app, an application that provides transactions to facilitate the DA layer and is built using Cosmos SDK. The following figure shows the main components of celestia-app.

Main components of celestia-app

celestia-app is built on top of celestia-core, a modified version of the Tendermint consensus algorithm. Among the more important changes to vanilla Tendermint, celestia-core:

  • Enables the erasure coding of block data (using the 2-dimensional Reed-Solomon encoding scheme).
  • Replaces the regular Merkle tree used by Tendermint to store block data with a Namespaced Merkle tree that enables the above layers (i.e., execution and settlement) to only download the needed data (for more details, see the section below describing use cases).

For more details on the changes to Tendermint, take a look at the ADRs. Notice that celestia-core nodes are still using the Tendermint p2p network.

Similarly to Tendermint, celestia-core is connected to the application layer (i.e., the state machine) by ABCI++, a major evolution of ABCI (Application Blockchain Interface).

The celestia-app state machine is necessary to execute the PoS logic and to enable the governance of the DA layer.

However, the celestia-app is data-agnostic -- the state machine neither validates nor stores the data that is made available by the celestia-app.

+ \ No newline at end of file diff --git a/pr-1699/learn/how-celestia-works/monolithic-vs-modular.html b/pr-1699/learn/how-celestia-works/monolithic-vs-modular.html index a5b5246a5c..1b5b7a097d 100644 --- a/pr-1699/learn/how-celestia-works/monolithic-vs-modular.html +++ b/pr-1699/learn/how-celestia-works/monolithic-vs-modular.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Monolithic vs. modular blockchains ​

Blockchains instantiate replicated state machines: the nodes in a permissionless distributed network apply an ordered sequence of deterministic transactions to an initial state resulting in a common final state.

In other words, this means that nodes in a network all follow the same set of rules (i.e., an ordered sequence of transactions) to go from a starting point (i.e., an initial state) to an ending point (i.e., a common final state). This process ensures that all nodes in the network agree on the final state of the blockchain, even though they operate independently.

This means blockchains require the following four functions:

  • Execution entails executing transactions that update the state correctly. Thus, execution must ensure that only valid transactions are executed, i.e., transactions that result in valid state machine transitions.
  • Settlement entails an environment for execution layers to verify proofs, resolve fraud disputes, and bridge between other execution layers.
  • Consensus entails agreeing on the order of the transactions.
  • Data Availability (DA) entails making the transaction data available. Note that execution, settlement, and consensus require DA.

Traditional blockchains, i.e. monolithic blockchains, implement all four functions together in a single base consensus layer. The problem with monolithic blockchains is that the consensus layer must perform numerous different tasks, and it cannot be optimized for only one of these functions. As a result, the monolithic paradigm limits the throughput of the system.

Modular VS Monolithic

As a solution, modular blockchains decouple these functions among multiple specialized layers as part of a modular stack. Due to the flexibility that specialization provides, there are many possibilities in which that stack can be arranged. For example, one such arrangement is the separation of the four functions into three specialized layers.

The base layer consists of DA and consensus and thus, is referred to as the Consensus and DA layer (or for brevity, the DA layer), while both settlement and execution are moved on top in their own layers. As a result, every layer can be specialized to optimally perform only its function, and thus, increase the throughput of the system. Furthermore, this modular paradigm enables multiple execution layers, i.e., rollups, to use the same settlement and DA layers.

- +

Monolithic vs. modular blockchains ​

Blockchains instantiate replicated state machines: the nodes in a permissionless distributed network apply an ordered sequence of deterministic transactions to an initial state resulting in a common final state.

In other words, this means that nodes in a network all follow the same set of rules (i.e., an ordered sequence of transactions) to go from a starting point (i.e., an initial state) to an ending point (i.e., a common final state). This process ensures that all nodes in the network agree on the final state of the blockchain, even though they operate independently.

This means blockchains require the following four functions:

  • Execution entails executing transactions that update the state correctly. Thus, execution must ensure that only valid transactions are executed, i.e., transactions that result in valid state machine transitions.
  • Settlement entails an environment for execution layers to verify proofs, resolve fraud disputes, and bridge between other execution layers.
  • Consensus entails agreeing on the order of the transactions.
  • Data Availability (DA) entails making the transaction data available. Note that execution, settlement, and consensus require DA.

Traditional blockchains, i.e. monolithic blockchains, implement all four functions together in a single base consensus layer. The problem with monolithic blockchains is that the consensus layer must perform numerous different tasks, and it cannot be optimized for only one of these functions. As a result, the monolithic paradigm limits the throughput of the system.

Modular VS Monolithic

As a solution, modular blockchains decouple these functions among multiple specialized layers as part of a modular stack. Due to the flexibility that specialization provides, there are many possibilities in which that stack can be arranged. For example, one such arrangement is the separation of the four functions into three specialized layers.

The base layer consists of DA and consensus and thus, is referred to as the Consensus and DA layer (or for brevity, the DA layer), while both settlement and execution are moved on top in their own layers. As a result, every layer can be specialized to optimally perform only its function, and thus, increase the throughput of the system. Furthermore, this modular paradigm enables multiple execution layers, i.e., rollups, to use the same settlement and DA layers.

+ \ No newline at end of file diff --git a/pr-1699/learn/how-celestia-works/overview.html b/pr-1699/learn/how-celestia-works/overview.html index daa1df0467..50e01c8f7b 100644 --- a/pr-1699/learn/how-celestia-works/overview.html +++ b/pr-1699/learn/how-celestia-works/overview.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Introduction ​

Celestia is a modular data availability network that securely scales with the number of users, making it easy for anyone to launch their own blockchain.

Celestia enables the next generation of scalable blockchain architectures - modular blockchains. Celestia scales by decoupling execution from consensus and introducing a new primitive, data availability sampling.

The former entails that Celestia is only responsible for ordering transactions and guaranteeing their data availability; this is similar to reducing consensus to atomic broadcast.

The latter provides an efficient solution to the data availability problem by only requiring resource-limited light nodes to sample a small number of random shares from each block to verify data availability.

Interestingly, more light nodes that participate in sampling increases the amount of data that the network can safely handle, enabling the block size to increase without equally increasing the cost to verify the chain.

- +

Introduction ​

Celestia is a modular data availability network that securely scales with the number of users, making it easy for anyone to launch their own blockchain.

Celestia enables the next generation of scalable blockchain architectures - modular blockchains. Celestia scales by decoupling execution from consensus and introducing a new primitive, data availability sampling.

The former entails that Celestia is only responsible for ordering transactions and guaranteeing their data availability; this is similar to reducing consensus to atomic broadcast.

The latter provides an efficient solution to the data availability problem by only requiring resource-limited light nodes to sample a small number of random shares from each block to verify data availability.

Interestingly, more light nodes that participate in sampling increases the amount of data that the network can safely handle, enabling the block size to increase without equally increasing the cost to verify the chain.

+ \ No newline at end of file diff --git a/pr-1699/learn/how-celestia-works/transaction-lifecycle.html b/pr-1699/learn/how-celestia-works/transaction-lifecycle.html index e16fdd5b16..db4e61b9ab 100644 --- a/pr-1699/learn/how-celestia-works/transaction-lifecycle.html +++ b/pr-1699/learn/how-celestia-works/transaction-lifecycle.html @@ -12,7 +12,7 @@ - + @@ -39,8 +39,8 @@

Appearance

The lifecycle of a celestia-app transaction ​

Users request the celestia-app to make data available by sending PayForBlobs transactions. Every such transaction consists of the identity of the sender, the data to be made available, also referred to as the message, the data size, the namespace, and a signature. Every block producer batches multiple PayForBlobs transactions into a block.

Before proposing the block though, the producer passes it to the state machine via ABCI++, where each PayForBlobs transaction is split into a namespaced message (denoted by Msg in the figure below), i.e., the data together with the namespace ID, and an executable transaction (denoted by e-Tx in the figure below) that does not contain the data, but only a commitment that can be used at a later time to prove that the data was indeed made available.

Thus, the block data consists of data partitioned into namespaces and executable transactions. Note that only these transactions are executed by the Celestia state machine once the block is committed.

Lifecycle of a celestia-app Transaction

Next, the block producer adds to the block header a commitment of the block data. As described in the "Celestia's data availability layer" page, the commitment is the Merkle root of the 4k intermediate Merkle roots (i.e., one for each row and column of the extended matrix). To compute this commitment, the block producer performs the following operations:

  • It splits the executable transactions and the namespaced data into shares. Every share consists of some bytes prefixed by a namespace. To this end, the executable transactions are associated with a reserved namespace.
  • It arranges these shares into a square matrix (row-wise). Note that the shares are padded to the next power of two. The outcome square of size k×k is referred to as the original data.
  • It extends the original data to a 2k×2k square matrix using the 2-dimensional Reed-Solomon encoding scheme described above. The extended shares (i.e., containing erasure data) are associated with another reserved namespace.
  • It computes a commitment for every row and column of the extended matrix using the NMTs described above.

Thus, the commitment of the block data is the root of a Merkle tree with the leaves the roots of a forest of Namespaced Merkle subtrees, one for every row and column of the extended matrix.

Checking data availability ​

DA network

To enhance connectivity, the celestia-node augments the celestia-app with a separate libp2p network, i.e., the so-called DA network, that serves DAS requests.

Light nodes connect to a celestia-node in the DA network, listen to extended block headers (i.e., the block headers together with the relevant DA metadata, such as the 4k intermediate Merkle roots), and perform DAS on the received headers (i.e., ask for random data shares).

Note that although it is recommended, performing DAS is optional -- light nodes could just trust that the data corresponding to the commitments in the block headers was indeed made available by the Celestia DA layer. In addition, light nodes can also submit transactions to the celestia-app, i.e., PayForBlobs transactions.

While performing DAS for a block header, every light node queries Celestia Nodes for a number of random data shares from the extended matrix and the corresponding Merkle proofs. If all the queries are successful, then the light node accepts the block header as valid (from a DA perspective).

If at least one of the queries fails (i.e., either the data share is not received or the Merkle proof is invalid), then the light node rejects the block header and tries again later. The retrial is necessary to deal with false negatives, i.e., block headers being rejected although the block data is available. This may happen due to network congestion for example.

Alternatively, light nodes may accept a block header although the data is not available, i.e., a false positive. This is possible since the soundness property (i.e., if an honest light node accepts a block as available, then at least one honest full node will eventually have the entire block data) is probabilistically guaranteed (for more details, take a look at the original paper).

By fine tuning Celestia's parameters (e.g., the number of data shares sampled by each light node) the likelihood of false positives can be sufficiently reduced such that block producers have no incentive to withhold the block data.

- +

The lifecycle of a celestia-app transaction ​

Users request the celestia-app to make data available by sending PayForBlobs transactions. Every such transaction consists of the identity of the sender, the data to be made available, also referred to as the message, the data size, the namespace, and a signature. Every block producer batches multiple PayForBlobs transactions into a block.

Before proposing the block though, the producer passes it to the state machine via ABCI++, where each PayForBlobs transaction is split into a namespaced message (denoted by Msg in the figure below), i.e., the data together with the namespace ID, and an executable transaction (denoted by e-Tx in the figure below) that does not contain the data, but only a commitment that can be used at a later time to prove that the data was indeed made available.

Thus, the block data consists of data partitioned into namespaces and executable transactions. Note that only these transactions are executed by the Celestia state machine once the block is committed.

Lifecycle of a celestia-app Transaction

Next, the block producer adds to the block header a commitment of the block data. As described in the "Celestia's data availability layer" page, the commitment is the Merkle root of the 4k intermediate Merkle roots (i.e., one for each row and column of the extended matrix). To compute this commitment, the block producer performs the following operations:

  • It splits the executable transactions and the namespaced data into shares. Every share consists of some bytes prefixed by a namespace. To this end, the executable transactions are associated with a reserved namespace.
  • It arranges these shares into a square matrix (row-wise). Note that the shares are padded to the next power of two. The outcome square of size k×k is referred to as the original data.
  • It extends the original data to a 2k×2k square matrix using the 2-dimensional Reed-Solomon encoding scheme described above. The extended shares (i.e., containing erasure data) are associated with another reserved namespace.
  • It computes a commitment for every row and column of the extended matrix using the NMTs described above.

Thus, the commitment of the block data is the root of a Merkle tree with the leaves the roots of a forest of Namespaced Merkle subtrees, one for every row and column of the extended matrix.

Checking data availability ​

DA network

To enhance connectivity, the celestia-node augments the celestia-app with a separate libp2p network, i.e., the so-called DA network, that serves DAS requests.

Light nodes connect to a celestia-node in the DA network, listen to extended block headers (i.e., the block headers together with the relevant DA metadata, such as the 4k intermediate Merkle roots), and perform DAS on the received headers (i.e., ask for random data shares).

Note that although it is recommended, performing DAS is optional -- light nodes could just trust that the data corresponding to the commitments in the block headers was indeed made available by the Celestia DA layer. In addition, light nodes can also submit transactions to the celestia-app, i.e., PayForBlobs transactions.

While performing DAS for a block header, every light node queries Celestia Nodes for a number of random data shares from the extended matrix and the corresponding Merkle proofs. If all the queries are successful, then the light node accepts the block header as valid (from a DA perspective).

If at least one of the queries fails (i.e., either the data share is not received or the Merkle proof is invalid), then the light node rejects the block header and tries again later. The retrial is necessary to deal with false negatives, i.e., block headers being rejected although the block data is available. This may happen due to network congestion for example.

Alternatively, light nodes may accept a block header although the data is not available, i.e., a false positive. This is possible since the soundness property (i.e., if an honest light node accepts a block as available, then at least one honest full node will eventually have the entire block data) is probabilistically guaranteed (for more details, take a look at the original paper).

By fine tuning Celestia's parameters (e.g., the number of data shares sampled by each light node) the likelihood of false positives can be sufficiently reduced such that block producers have no incentive to withhold the block data.

+ \ No newline at end of file diff --git a/pr-1699/learn/how-to-stake-tia.html b/pr-1699/learn/how-to-stake-tia.html index 1af1839ec6..86aea68742 100644 --- a/pr-1699/learn/how-to-stake-tia.html +++ b/pr-1699/learn/how-to-stake-tia.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

How to stake TIA ​

Celestia is a proof-of-stake blockchain based on the Cosmos SDK.

Staking TIA as a delegator allows you to secure the Celestia network. This means that you can stake the native token TIA and vote on governance proposals.

In this tutorial, you will learn how to stake TIA tokens via Keplr, Leap, and Gem wallets.

Select your preferred wallet ​

Keplr
Leap
Gem Wallet

Stake TIA with Keplr wallet ​

1️⃣ Open your Keplr browser extension ​

Navigate to Staked and select Stake with Keplr Dashboard.

This will open the Keplr dashboard in a new browser page.

Keplr1

2️⃣ Select Celestia network and search for a validator ​

In the Keplr dashboard, select the Celestia network and pick a validator of your choice.

Keplr1

3️⃣ Stake your TIA tokens ​

On the following screen enter amount of TIA tokens and select Stake.

A Keplr popup will appear, requesting your approval for the transaction. Select Approve.

Keplr1

4️⃣ Confirm and manage your TIA ​

After the transaction is confirmed, you will see the following overview dashboard where you can claim rewards, unstake, redelegate, or stake additional tokens.

Keplr1

Stake TIA with Leap wallet ​

1️⃣ Open your Leap browser extension ​

In top right select Celestia network and navigate to Stake.

Similarly to previous step, select the +Stake button.

Keplr1

2️⃣ Select a validator and stake TIA ​

On the following screen choose a validator of your choice, enter the desired amount, and click Review.

Following that, review the transaction details and select Stake, then wait for the transaction to finalize.

Keplr1

3️⃣ Confirm and manage your TIA ​

After the transaction is confirmed, you will see the following overview dashboard where you can claim rewards, unstake, redelegate, or stake additional tokens.

Keplr1

Stake TIA with Gem wallet ​

1️⃣ Open your Gem Wallet app ​

Navigate to Celestia and select Stake.

Gem1

2️⃣ Choose the amount of Celestia and search for a validator. ​

Select the amount of Celestia tokens and choose a validator from the list.

Gem2

3️⃣ Stake your TIA tokens ​

Review the network terms and commission, then press Confirm to proceed.

Gem3

4️⃣ Manage your TIA ​

After your transaction is confirmed, you will have access to a control panel where you can claim rewards, unstake, redelegate, or stake additional tokens.

Gem4

- +

How to stake TIA ​

Celestia is a proof-of-stake blockchain based on the Cosmos SDK.

Staking TIA as a delegator allows you to secure the Celestia network. This means that you can stake the native token TIA and vote on governance proposals.

In this tutorial, you will learn how to stake TIA tokens via Keplr, Leap, and Gem wallets.

Select your preferred wallet ​

Keplr
Leap
Gem Wallet

Stake TIA with Keplr wallet ​

1️⃣ Open your Keplr browser extension ​

Navigate to Staked and select Stake with Keplr Dashboard.

This will open the Keplr dashboard in a new browser page.

Keplr1

2️⃣ Select Celestia network and search for a validator ​

In the Keplr dashboard, select the Celestia network and pick a validator of your choice.

Keplr1

3️⃣ Stake your TIA tokens ​

On the following screen enter amount of TIA tokens and select Stake.

A Keplr popup will appear, requesting your approval for the transaction. Select Approve.

Keplr1

4️⃣ Confirm and manage your TIA ​

After the transaction is confirmed, you will see the following overview dashboard where you can claim rewards, unstake, redelegate, or stake additional tokens.

Keplr1

Stake TIA with Leap wallet ​

1️⃣ Open your Leap browser extension ​

In top right select Celestia network and navigate to Stake.

Similarly to previous step, select the +Stake button.

Keplr1

2️⃣ Select a validator and stake TIA ​

On the following screen choose a validator of your choice, enter the desired amount, and click Review.

Following that, review the transaction details and select Stake, then wait for the transaction to finalize.

Keplr1

3️⃣ Confirm and manage your TIA ​

After the transaction is confirmed, you will see the following overview dashboard where you can claim rewards, unstake, redelegate, or stake additional tokens.

Keplr1

Stake TIA with Gem wallet ​

1️⃣ Open your Gem Wallet app ​

Navigate to Celestia and select Stake.

Gem1

2️⃣ Choose the amount of Celestia and search for a validator. ​

Select the amount of Celestia tokens and choose a validator from the list.

Gem2

3️⃣ Stake your TIA tokens ​

Review the network terms and commission, then press Confirm to proceed.

Gem3

4️⃣ Manage your TIA ​

After your transaction is confirmed, you will have access to a control panel where you can claim rewards, unstake, redelegate, or stake additional tokens.

Gem4

+ \ No newline at end of file diff --git a/pr-1699/learn/paying-for-blobspace.html b/pr-1699/learn/paying-for-blobspace.html index 7e48ea2bea..88f2d3e750 100644 --- a/pr-1699/learn/paying-for-blobspace.html +++ b/pr-1699/learn/paying-for-blobspace.html @@ -12,7 +12,7 @@ - + @@ -39,8 +39,8 @@

Appearance

Paying for blobspace ​

PayForBlobs transactions ​

To publish data on Celestia, developers can submit PayForBlobs transactions. A PayForBlobs transaction consists of the identity of the sender, the data to be made available, the data size, the namespace, and a signature.

Each PayForBlobs transaction is split into two parts: the blob or blobs which include the data to be made available along with the namespace, and the executable payment transaction which includes a commitment to the data.

Both the blobs and executable payment transactions are put into the block within the appropriate namespace. The block data is extended using erasure coding and then Merkelized into a data root commitment included in the block header.

Lifecycle of a celestia-app Transaction

See the detailed life cycle of a Celestia transaction.

Learn how to submit data to Celestia’s data availability layer.

Fee market overview ​

Celestia uses a standard gas-price prioritised mempool. This means that transactions with higher fees will be prioritised by validators. Fees are comprised of a flat fee per transaction and then a variable fee based on the size of each blob in the transaction.

Understand how fees are calculated on Celestia in the overview on submitting PFB transactions.

- +

Paying for blobspace ​

PayForBlobs transactions ​

To publish data on Celestia, developers can submit PayForBlobs transactions. A PayForBlobs transaction consists of the identity of the sender, the data to be made available, the data size, the namespace, and a signature.

Each PayForBlobs transaction is split into two parts: the blob or blobs which include the data to be made available along with the namespace, and the executable payment transaction which includes a commitment to the data.

Both the blobs and executable payment transactions are put into the block within the appropriate namespace. The block data is extended using erasure coding and then Merkelized into a data root commitment included in the block header.

Lifecycle of a celestia-app Transaction

See the detailed life cycle of a Celestia transaction.

Learn how to submit data to Celestia’s data availability layer.

Fee market overview ​

Celestia uses a standard gas-price prioritised mempool. This means that transactions with higher fees will be prioritised by validators. Fees are comprised of a flat fee per transaction and then a variable fee based on the size of each blob in the transaction.

Understand how fees are calculated on Celestia in the overview on submitting PFB transactions.

+ \ No newline at end of file diff --git a/pr-1699/learn/retrievability.html b/pr-1699/learn/retrievability.html index 586afb0ef3..c7aa5d2839 100644 --- a/pr-1699/learn/retrievability.html +++ b/pr-1699/learn/retrievability.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Data retrievability and pruning ​

The purpose of data availability layers such as Celestia is to ensure that block data is provably published, so that applications and rollups can know what the state of their chain is, and store that data. Once the data is published, data availability layers do not inherently guarantee that historical data will be permanently stored and remain retrievable.

In this document, we discuss the state of data retrievability and pruning in Celestia, as well as some tips for rollup developers in order to ensure that syncing new rollup nodes is possible.

Data retrievability and pruning in celestia-node ​

As of version v0.13.0, celestia-node has implemented a light node sampling window of 30 days, as specified in CIP-4. This means that once pruning is implemented, light nodes will now only sample blocks within a 30-day window instead of sampling all blocks from genesis. This change introduces the concept of pruning to celestia-node, where data outside of the 30-day window may not be stored by light nodes, marking a significant update in how data retrievability and storage are managed within the network (v0.13.0 release notes).

Data blobs older than the recency window will be pruned by default on light nodes, after pruning is fully implemented, but will continue to be stored by archival nodes that do not prune data. Light nodes will be able to query historic blob data in namespaces from archival nodes, as long as archival nodes exist on the public network.

Once pruning is fully implemented, light nodes will only perform data availability sampling for blocks within the data recency window of 30 days.

Suggested practices for rollups ​

Rollups may need to access historic data in order to allow new rollup nodes to reconstruct the latest state by replaying historic blocks. Once data has been published on Celestia and guaranteed to have been made available, rollups and applications are responsible for storing their historical data.

While it is possible to continue to do this by using the GetAll API method in celestia-node on historic blocks as long as archival nodes exist on the public Celestia network, rollup developers should not rely on this as the only method to access historical data, as archival nodes serving requests for historical data for free is not guaranteed. Below are some other suggested methods to access historical data.

  • Use professional archival node or data providers. It is expected that professional infrastructure providers will provide paid access to archival nodes, where historical data can be retrieved, for example using the GetAll API method. This provides better guarantees than solely relying on free archival nodes on the public Celestia network.
  • Share snapshots of rollup nodes. Rollups could share snapshots of their data directories which can be downloaded manually by users bootstrapping new nodes. These snapshots could contain the latest state of the rollup, and/or all the historical blocks.
  • Add peer-to-peer support for historical block sync. A less manual version of sharing snapshots, where rollup nodes could implement built-in support for block sync, where rollup nodes download historical block data from each other over a peer-to-peer network.
    • Namespace pinning. In the future, celestia-node is expected to allow nodes to choose to "pin" data from selected namespaces that they wish to store and make available for other nodes. This will allow rollup nodes to be responsible for storing their data, without needing to implement their own peer-to-peer historical block sync mechanism.
- +

Data retrievability and pruning ​

The purpose of data availability layers such as Celestia is to ensure that block data is provably published, so that applications and rollups can know what the state of their chain is, and store that data. Once the data is published, data availability layers do not inherently guarantee that historical data will be permanently stored and remain retrievable.

In this document, we discuss the state of data retrievability and pruning in Celestia, as well as some tips for rollup developers in order to ensure that syncing new rollup nodes is possible.

Data retrievability and pruning in celestia-node ​

As of version v0.13.0, celestia-node has implemented a light node sampling window of 30 days, as specified in CIP-4. This means that once pruning is implemented, light nodes will now only sample blocks within a 30-day window instead of sampling all blocks from genesis. This change introduces the concept of pruning to celestia-node, where data outside of the 30-day window may not be stored by light nodes, marking a significant update in how data retrievability and storage are managed within the network (v0.13.0 release notes).

Data blobs older than the recency window will be pruned by default on light nodes, after pruning is fully implemented, but will continue to be stored by archival nodes that do not prune data. Light nodes will be able to query historic blob data in namespaces from archival nodes, as long as archival nodes exist on the public network.

Once pruning is fully implemented, light nodes will only perform data availability sampling for blocks within the data recency window of 30 days.

Suggested practices for rollups ​

Rollups may need to access historic data in order to allow new rollup nodes to reconstruct the latest state by replaying historic blocks. Once data has been published on Celestia and guaranteed to have been made available, rollups and applications are responsible for storing their historical data.

While it is possible to continue to do this by using the GetAll API method in celestia-node on historic blocks as long as archival nodes exist on the public Celestia network, rollup developers should not rely on this as the only method to access historical data, as archival nodes serving requests for historical data for free is not guaranteed. Below are some other suggested methods to access historical data.

  • Use professional archival node or data providers. It is expected that professional infrastructure providers will provide paid access to archival nodes, where historical data can be retrieved, for example using the GetAll API method. This provides better guarantees than solely relying on free archival nodes on the public Celestia network.
  • Share snapshots of rollup nodes. Rollups could share snapshots of their data directories which can be downloaded manually by users bootstrapping new nodes. These snapshots could contain the latest state of the rollup, and/or all the historical blocks.
  • Add peer-to-peer support for historical block sync. A less manual version of sharing snapshots, where rollup nodes could implement built-in support for block sync, where rollup nodes download historical block data from each other over a peer-to-peer network.
    • Namespace pinning. In the future, celestia-node is expected to allow nodes to choose to "pin" data from selected namespaces that they wish to store and make available for other nodes. This will allow rollup nodes to be responsible for storing their data, without needing to implement their own peer-to-peer historical block sync mechanism.
+ \ No newline at end of file diff --git a/pr-1699/learn/staking-governance-supply.html b/pr-1699/learn/staking-governance-supply.html index 8f24cab841..f4b426999f 100644 --- a/pr-1699/learn/staking-governance-supply.html +++ b/pr-1699/learn/staking-governance-supply.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Staking, governance, & supply ​

Proof-of-stake on Celestia ​

Celestia is a proof-of-stake blockchain based on CometBFT and the Cosmos SDK. Celestia supports in-protocol delegation and will start with an initial validator set of 100.

Staking TIA as a validator or delegator enables you to earn staking rewards from the network. Validators charge a fee to delegators which gives them a percentage of staking rewards.

Learn how proof of stake works on Cosmos SDK chains like Celestia.

Consensus mechanismProof-of-stake
Blockchain frameworkCosmos SDK
Validator set size100
Delegation supportYes

Learn how to stake on your own at the community dashboards.

Inflation ​

TIA inflation starts at 8% annually and decreases by 10% every year until it reaches the long term issuance rate of 1.5%. Exact annual inflation rates can be found in the diagram below.

inflation diagram

The annual provisions for inflation are calculated based on the total supply of TIA at the beginning of each year. To calculate how many TIA to issue per block, Celestia uses the block timestamp rather than the block height since the time between blocks can vary and cause actual issuance to be higher than the target.

For an in-depth understanding, refer to ADR019.

Decentralised governance ​

Network parameters ​

TIA holders (not just stakers) can propose and vote on governance proposals to change a subset of network parameters. To learn more, see a complete list of both the changeable and non-changeable parameters and their values. Additionally, learn how to submit and vote on governance proposals.

Community pool ​

Starting at genesis, Celestia’s community pool receives 2% of all Celestia block rewards. TIA stakers may vote to fund ecosystem initiatives as in many other Cosmos SDK chains.

Learn how to submit a governance proposal to spend community pool funds.

TIA allocation at genesis ​

Celestia will have a total supply of 1,000,000,000 TIA at genesis, split across five categories described in the chart and table below.

allocation diagram

CategoryDescription%
Public AllocationGenesis Drop and Incentivized Testnet: 7.41%
Future initiatives: 12.59%		20.00%
R&D & EcosystemTokens allocated to the Celestia Foundation and core devs for research, development, and ecosystem initiatives including:
- Protocol maintenance and development
- Programs for rollup developers, infrastructure, and node operators		26.79%
Early Backers: Series A&BEarly supporters of Celestia19.67%
Early Backers: SeedEarly supporters of Celestia15.90%
Initial Core ContributorsMembers of Celestia Labs, the first core contributor to Celestia17.64%

Unlocks ​

Celestia’s 1 billion TIA supply at genesis will be subject to several different unlock schedules. All tokens, locked or unlocked, may be staked, but staking rewards are unlocked upon receipt and will add to the circulating supply.

Circulating supply is defined as the amount of TIA tokens in general circulation without onchain transfer restrictions.

Available supply is defined as the amount of TIA tokens that are either part of the circulating supply or are unlocked but subject to some form of governance to determine when the tokens are allocated. This includes the unlocked portion of the R&D & Ecosystem tokens and the tokens set aside for future initiatives.

The definitions for circulating and available supply were adapted from Optimism’s definitions.

supply diagram

Unlock schedule by category is described in the table below.

CategoryUnlock Schedule
Public AllocationFully unlocked at launch.
R&D & Ecosystem25.00% unlocked at launch.
Remaining 75.00% unlocks continuously from year 1 to year 4.
Initial Core Contributors33.33% unlocked at year 1.
Remaining 66.67% unlocks continuously from year 1 to year 3.
Early Backers: Seed33.33% unlocked at year 1.
Remaining 66.67% unlocks continuously from year 1 to year 2.
Early Backers: Series A&B33.33% unlocked at year 1.
Remaining 66.67% unlocks continuously from year 1 to year 2.
- +

Staking, governance, & supply ​

Proof-of-stake on Celestia ​

Celestia is a proof-of-stake blockchain based on CometBFT and the Cosmos SDK. Celestia supports in-protocol delegation and will start with an initial validator set of 100.

Staking TIA as a validator or delegator enables you to earn staking rewards from the network. Validators charge a fee to delegators which gives them a percentage of staking rewards.

Learn how proof of stake works on Cosmos SDK chains like Celestia.

Consensus mechanismProof-of-stake
Blockchain frameworkCosmos SDK
Validator set size100
Delegation supportYes

Learn how to stake on your own at the community dashboards.

Inflation ​

TIA inflation starts at 8% annually and decreases by 10% every year until it reaches the long term issuance rate of 1.5%. Exact annual inflation rates can be found in the diagram below.

inflation diagram

The annual provisions for inflation are calculated based on the total supply of TIA at the beginning of each year. To calculate how many TIA to issue per block, Celestia uses the block timestamp rather than the block height since the time between blocks can vary and cause actual issuance to be higher than the target.

For an in-depth understanding, refer to ADR019.

Decentralised governance ​

Network parameters ​

TIA holders (not just stakers) can propose and vote on governance proposals to change a subset of network parameters. To learn more, see a complete list of both the changeable and non-changeable parameters and their values. Additionally, learn how to submit and vote on governance proposals.

Community pool ​

Starting at genesis, Celestia’s community pool receives 2% of all Celestia block rewards. TIA stakers may vote to fund ecosystem initiatives as in many other Cosmos SDK chains.

Learn how to submit a governance proposal to spend community pool funds.

TIA allocation at genesis ​

Celestia will have a total supply of 1,000,000,000 TIA at genesis, split across five categories described in the chart and table below.

allocation diagram

CategoryDescription%
Public AllocationGenesis Drop and Incentivized Testnet: 7.41%
Future initiatives: 12.59%		20.00%
R&D & EcosystemTokens allocated to the Celestia Foundation and core devs for research, development, and ecosystem initiatives including:
- Protocol maintenance and development
- Programs for rollup developers, infrastructure, and node operators		26.79%
Early Backers: Series A&BEarly supporters of Celestia19.67%
Early Backers: SeedEarly supporters of Celestia15.90%
Initial Core ContributorsMembers of Celestia Labs, the first core contributor to Celestia17.64%

Unlocks ​

Celestia’s 1 billion TIA supply at genesis will be subject to several different unlock schedules. All tokens, locked or unlocked, may be staked, but staking rewards are unlocked upon receipt and will add to the circulating supply.

Circulating supply is defined as the amount of TIA tokens in general circulation without onchain transfer restrictions.

Available supply is defined as the amount of TIA tokens that are either part of the circulating supply or are unlocked but subject to some form of governance to determine when the tokens are allocated. This includes the unlocked portion of the R&D & Ecosystem tokens and the tokens set aside for future initiatives.

The definitions for circulating and available supply were adapted from Optimism’s definitions.

supply diagram

Unlock schedule by category is described in the table below.

CategoryUnlock Schedule
Public AllocationFully unlocked at launch.
R&D & Ecosystem25.00% unlocked at launch.
Remaining 75.00% unlocks continuously from year 1 to year 4.
Initial Core Contributors33.33% unlocked at year 1.
Remaining 66.67% unlocks continuously from year 1 to year 3.
Early Backers: Seed33.33% unlocked at year 1.
Remaining 66.67% unlocks continuously from year 1 to year 2.
Early Backers: Series A&B33.33% unlocked at year 1.
Remaining 66.67% unlocks continuously from year 1 to year 2.
+ \ No newline at end of file diff --git a/pr-1699/learn/staking.html b/pr-1699/learn/staking.html index 8791290d9c..940fae4360 100644 --- a/pr-1699/learn/staking.html +++ b/pr-1699/learn/staking.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Staking on Celestia ​

Engage with the Celestia network at a deeper level through staking. An essential mechanism to a proof-of-stake network, users can secure the network by delegating to a validator and receive a share of its staking rewards.

Mainnet Beta ​

Currently, the following staking interfaces exist for the Mainnet Beta.

Just connect your wallet to get started!

Mocha testnet ​

Currently, the following staking interfaces exist for the Mocha testnet.

Just connect your wallet to get started!

- +

Staking on Celestia ​

Engage with the Celestia network at a deeper level through staking. An essential mechanism to a proof-of-stake network, users can secure the network by delegating to a validator and receive a share of its staking rewards.

Mainnet Beta ​

Currently, the following staking interfaces exist for the Mainnet Beta.

Just connect your wallet to get started!

Mocha testnet ​

Currently, the following staking interfaces exist for the Mocha testnet.

Just connect your wallet to get started!

+ \ No newline at end of file diff --git a/pr-1699/learn/tia.html b/pr-1699/learn/tia.html index 6d39dd753b..9992c35c43 100644 --- a/pr-1699/learn/tia.html +++ b/pr-1699/learn/tia.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Overview of TIA ​

TIA at a glance ​

PropertyDetails
AbbreviationTIA
Total supply at genesis1,000,000,000 TIA
Inflation schedule8% in the first year, decreasing 10% per year until reaching an inflation floor of 1.5% annually
Decimals6
Conversion1 uTIA=TIA×10−6

Role of TIA ​

Paying for blobspace ​

Celestia’s native asset, TIA, is an essential part of how developers build on the first modular blockchain network. To use Celestia for data availability, rollup developers submit PayForBlobs transactions on the network for a fee, denominated in TIA.

Bootstrapping new rollups ​

A core part of the Celestia vision is that deploying a blockchain should be as easy as deploying a smart contract. In the modular era, developers no longer need to issue a token to launch their own blockchain.

Similarly to ETH on Ethereum-based rollups, developers may opt to bootstrap their chain quickly by using TIA as a gas token and currency, in addition to paying for data availability. In this mode, developers can focus on creating their application or execution layer, instead of issuing a token right away.

Proof-of-stake ​

As a permissionless network built with Cosmos SDK, Celestia uses proof-of-stake to secure its own consensus. Like in other Cosmos networks, any user can help secure the network by delegating their TIA to a Celestia validator for a portion of their validator’s staking rewards.

Learn how proof-of-stake works in Cosmos.

Decentralised governance ​

TIA staking also allows the community to play a critical role in decentralised governance over key parts of Celestia, such as voting on network parameters through governance proposals, and governing the community pool, which receives 2% of block rewards.

Learn more about Celestia’s decentralised governance model.

Denominations ​

TIA: display token ​

TIA is the DisplayDenom that you will typically see in wallets and user interfaces.

utia: staking denomination ​

utia is the BondDenom and stands for "micro TIA", with 1 TIA = 1,000,000 utia. This is the native staking denomination.

In staking operations or transactions, if no denomination is specified, utia is assumed.

microtia: staking denomination alias ​

microtia is the BondDenomAlias, an alias for utia.

- +

Overview of TIA ​

TIA at a glance ​

PropertyDetails
AbbreviationTIA
Total supply at genesis1,000,000,000 TIA
Inflation schedule8% in the first year, decreasing 10% per year until reaching an inflation floor of 1.5% annually
Decimals6
Conversion1 uTIA=TIA×10−6

Role of TIA ​

Paying for blobspace ​

Celestia’s native asset, TIA, is an essential part of how developers build on the first modular blockchain network. To use Celestia for data availability, rollup developers submit PayForBlobs transactions on the network for a fee, denominated in TIA.

Bootstrapping new rollups ​

A core part of the Celestia vision is that deploying a blockchain should be as easy as deploying a smart contract. In the modular era, developers no longer need to issue a token to launch their own blockchain.

Similarly to ETH on Ethereum-based rollups, developers may opt to bootstrap their chain quickly by using TIA as a gas token and currency, in addition to paying for data availability. In this mode, developers can focus on creating their application or execution layer, instead of issuing a token right away.

Proof-of-stake ​

As a permissionless network built with Cosmos SDK, Celestia uses proof-of-stake to secure its own consensus. Like in other Cosmos networks, any user can help secure the network by delegating their TIA to a Celestia validator for a portion of their validator’s staking rewards.

Learn how proof-of-stake works in Cosmos.

Decentralised governance ​

TIA staking also allows the community to play a critical role in decentralised governance over key parts of Celestia, such as voting on network parameters through governance proposals, and governing the community pool, which receives 2% of block rewards.

Learn more about Celestia’s decentralised governance model.

Denominations ​

TIA: display token ​

TIA is the DisplayDenom that you will typically see in wallets and user interfaces.

utia: staking denomination ​

utia is the BondDenom and stands for "micro TIA", with 1 TIA = 1,000,000 utia. This is the native staking denomination.

In staking operations or transactions, if no denomination is specified, utia is assumed.

microtia: staking denomination alias ​

microtia is the BondDenomAlias, an alias for utia.

+ \ No newline at end of file diff --git a/pr-1699/nodes/arabica-devnet.html b/pr-1699/nodes/arabica-devnet.html index 5c01cfe9c5..ddc5d37400 100644 --- a/pr-1699/nodes/arabica-devnet.html +++ b/pr-1699/nodes/arabica-devnet.html @@ -14,7 +14,7 @@ - + @@ -43,8 +43,8 @@

Arabica devnet ​

arabica-devnet

Arabica devnet is a testnet from Celestia Labs that is focused exclusively on providing developers with enhanced performance and the latest upgrades for testing their rollups and applications.

Arabica does not focus on validator or consensus-level testing, rather, that is what Mocha testnet is used for. If you are a validator, we recommend testing your validator operations on the Mocha testnet.

Network stability and upgrades ​

Arabica has the latest updates from all Celestia's products deployed on it, it can be subject to many changes. Therefore, as a fair warning, Arabica can break unexpectedly, but given it will be continuously updated, it is a useful way to keep testing the latest changes in the software.

Developers can still deploy on Mocha testnet their sovereign rollups if they chose to do so, it just will always lag behind Arabica devnet until Mocha undergoes Hardfork Upgrades in coordination with Validators.

Network details ​

DetailValue
Chain IDarabica-11
Genesis hash27122593765E07329BC348E8D16E92DCB4C75B34CCCB35C640FD7A4484D4C711
Genesis file https://github.com/celestiaorg/networks/blob/master/arabica-11/genesis.json
Peers file https://github.com/celestiaorg/networks/blob/master/arabica-11/peers.txt
Validators 4

Software version numbers ​

SoftwareVersion
celestia-nodev0.16.0
celestia-appv2.1.2

Integrations ​

This guide contains the relevant sections for how to connect to Arabica devnet, depending on the type of node you are running. Your best approach to participating is to first determine which node you would like to run. Each node’s guide will link to the relevant network in order to show you how to connect to them. Learn about the different endpoint types in the Cosmos SDK documentation.

Production RPC endpoints ​

These RPC providers are meant to be used in production environments.

ProviderURL
NewMetrichttps://app.newmetric.xyz/start
NumiaFor RPC access: https://docs.numia.xyz/overview/rpc-api-access
NumiaFor data warehouse access: https://docs.numia.xyz/overview/sql-access/chains/celestia
Grovehttps://www.grove.city/

Community RPC endpoints ​

WARNING

Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs or your own node.

RPC endpoints and types of nodes you can run in order to participate in Arabica devnet:

Node typeEndpoint typeEndpoint
Consensus nodes (full)Consensus RPChttps://rpc.celestia-arabica-11.com
APIhttps://api.celestia-arabica-11.com
gRPCgrpc.celestia-arabica-11.com:443
Direct endpoints with open portsOpen ports: 26656 (p2p), 26657 (RPC), 1317 (API), 9090 (GRPC)
validator-1.celestia-arabica-11.com
validator-2.celestia-arabica-11.com
validator-3.celestia-arabica-11.com
validator-4.celestia-arabica-11.com
Data availability nodesDA Bridge Node Endpoints/dns4/da-bridge-1.celestia-arabica-11.com/tcp/2121/p2p/12D3KooWGqwzdEqM54Dce6LXzfFr97Bnhvm6rN7KM7MFwdomfm4S
(light, bridge, full)/dns4/da-bridge-2.celestia-arabica-11.com/tcp/2121/p2p/12D3KooWCMGM5eZWVfCN9ZLAViGfLUWAfXP5pCm78NFKb9jpBtua
/dns4/da-bridge-3.celestia-arabica-11.com/tcp/2121/p2p/12D3KooWEWuqrjULANpukDFGVoHW3RoeUU53Ec9t9v5cwW3MkVdQ
/dns4/da-bridge-4.celestia-arabica-11.com/tcp/2121/p2p/12D3KooWLT1ysSrD7XWSBjh7tU1HQanF5M64dHV6AuM6cYEJxMPk
--core.ip string endpointsRefer to "Direct endpoints with open ports" above

You can find the status of these endpoints.

Using consensus endpoints with DA nodes ​

Data availability (DA) RPC endpoints for bridge node sync ​

These RPC endpoints allow bridge nodes to sync blocks from the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default RPC port at 26657 to their respective DA node.

Data availability (DA) gRPC endpoints for state access ​

These gRPC endpoints for DA nodes provide state access for querying the chain’s state and broadcasting transactions (balances, blobs, etc.) to the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default gRPC port at 9090 to their respective DA node.

EXAMPLE

bash
celestia <da_type> start –core.ip <url> -–core.grpc.port <port>
celestia <da_type> start –core.ip <url> -–core.grpc.port <port>

RPCs for DA nodes to initialise or start your celestia-node to Arabica devnet with can be found in the table in the "Direct endpoints with open ports" section above.

As an example, this command will work to start a light node with state access, using default ports:

bash
celestia light start --p2p.network arabica \
   --core.ip validator-1.celestia-arabica-11.com
celestia light start --p2p.network arabica \
-  --core.ip validator-1.celestia-arabica-11.com

Bridge node runners

Not all of the RPC endpoints do not guarantee the full block history. Find an archive endpoint on the community dashboard or run your own consensus node with no pruning for your bridge node.

Arabica devnet faucet ​

WARNING

USING THIS FAUCET DOES NOT ENTITLE YOU TO ANY AIRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS.

Discord ​

You can request from Arabica devnet Faucet on the #arabica-faucet channel on Celestia's Discord server with the following command:

text
$request <CELESTIA-ADDRESS>
$request <CELESTIA-ADDRESS>

Where <CELESTIA-ADDRESS> is a celestia1****** generated address.

NOTE

Faucet has a limit of 10 tokens per week per address/Discord ID.

Web ​

The web faucet is available at https://faucet.celestia-arabica-11.com/.

Explorers ​

There are multiple explorers you can use for Arabica:

Network upgrades ​

Join our Telegram announcement channel for network upgrades.

See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.

- + --core.ip validator-1.celestia-arabica-11.com

Bridge node runners

Not all of the RPC endpoints do not guarantee the full block history. Find an archive endpoint on the community dashboard or run your own consensus node with no pruning for your bridge node.

Arabica devnet faucet ​

WARNING

USING THIS FAUCET DOES NOT ENTITLE YOU TO ANY AIRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS.

Discord ​

You can request from Arabica devnet Faucet on the #arabica-faucet channel on Celestia's Discord server with the following command:

text
$request <CELESTIA-ADDRESS>
$request <CELESTIA-ADDRESS>

Where <CELESTIA-ADDRESS> is a celestia1****** generated address.

NOTE

Faucet has a limit of 10 tokens per week per address/Discord ID.

Web ​

The web faucet is available at https://faucet.celestia-arabica-11.com/.

Explorers ​

There are multiple explorers you can use for Arabica:

Network upgrades ​

Join our Telegram announcement channel for network upgrades.

See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.

+ \ No newline at end of file diff --git a/pr-1699/nodes/bridge-node.html b/pr-1699/nodes/bridge-node.html index 710c9fd066..a07a4e4f5d 100644 --- a/pr-1699/nodes/bridge-node.html +++ b/pr-1699/nodes/bridge-node.html @@ -11,7 +11,7 @@ - + @@ -38,14 +38,14 @@

Appearance

Setting up a Celestia bridge node ​

This tutorial will go over the steps to setting up your Celestia bridge node.

Bridge nodes connect the data availability layer and the consensus layer.

Overview of bridge nodes ​

A Celestia bridge node has the following properties:

  1. Import and process “raw” headers & blocks from a trusted core process (meaning a trusted RPC connection to a celestia-core node) in the Consensus network. Bridge nodes can run this core process internally (embedded) or simply connect to a remote endpoint. Bridge nodes also have the option of being an active validator in the consensus network.
  2. Validate and erasure code the “raw” blocks
  3. Supply block shares with data availability headers to light nodes in the DA network.

bridge-node-diagram

From an implementation perspective, Bridge nodes run two separate processes:

  1. celestia-app with celestia-core (see repo)

    • celestia-app is the state machine where the application and the proof-of-stake logic is run. celestia-app is built on Cosmos SDK and also encompasses celestia-core.
    • celestia-core is the state interaction, consensus and block production layer. celestia-core is built on Tendermint Core, modified to store data roots of erasure coded blocks among other changes (see ADRs).

  2. celestia-node (see repo)

    • celestia-node augments the above with a separate libp2p network that serves data availability sampling requests. The team sometimes refers to this as the “halo” network.

Hardware requirements ​

The following hardware minimum requirements are recommended for running the bridge node:

  • Memory: 16 GB RAM (minimum)
  • CPU: 6 cores
  • Disk: 10 TB SSD Storage
  • Bandwidth: 1 Gbps for Download/1 Gbps for Upload

Setting up your bridge node ​

The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.

Setup the dependencies ​

Follow the tutorial for installing the dependencies.

Deploy the Celestia bridge node ​

Install Celestia Node ​

Install the celestia-node binary, which will be used to run the bridge node.

Follow the tutorial for installing celestia-node.

Initialize the bridge node ​

Run the following:

sh
celestia bridge init --core.ip <URI>
celestia bridge init --core.ip <URI>

The --core.ip gRPC port defaults to 9090, so if you do not specify it in the command line, it will default to that port. You can add the port after the IP address or use the --core.grpc.port flag to specify another port if you prefer.

Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

Using an RPC of your own, or one from the list on the Mocha testnet page or list on the Arabica devnet page, start your node.

Connecting to a core endpoint with --core.ip string provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).

Here is an example of initializing the bridge node:

sh
celestia bridge init --core.ip <URI>
celestia bridge init --core.ip <URI>
sh
celestia bridge init --core.ip <URI> --p2p.network mocha
celestia bridge init --core.ip <URI> --p2p.network mocha
sh
celestia bridge init --core.ip <URI> --p2p.network arabica
celestia bridge init --core.ip <URI> --p2p.network arabica

Run the bridge node ​

Start the bridge node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):

sh
celestia bridge start --core.ip <URI>
celestia bridge start --core.ip <URI>

Here is an example of starting the bridge node on Mocha:

sh
celestia bridge start --core.ip rpc-mocha.pops.one:26657 --p2p.network mocha
celestia bridge start --core.ip rpc-mocha.pops.one:26657 --p2p.network mocha

And on Arabica:

sh
celestia bridge start --core.ip validator-1.celestia-arabica-11.com \
+

Setting up a Celestia bridge node ​

This tutorial will go over the steps to setting up your Celestia bridge node.

Bridge nodes connect the data availability layer and the consensus layer.

Overview of bridge nodes ​

A Celestia bridge node has the following properties:

  1. Import and process “raw” headers & blocks from a trusted core process (meaning a trusted RPC connection to a celestia-core node) in the Consensus network. Bridge nodes can run this core process internally (embedded) or simply connect to a remote endpoint. Bridge nodes also have the option of being an active validator in the consensus network.
  2. Validate and erasure code the “raw” blocks
  3. Supply block shares with data availability headers to light nodes in the DA network.

bridge-node-diagram

From an implementation perspective, Bridge nodes run two separate processes:

  1. celestia-app with celestia-core (see repo)

    • celestia-app is the state machine where the application and the proof-of-stake logic is run. celestia-app is built on Cosmos SDK and also encompasses celestia-core.
    • celestia-core is the state interaction, consensus and block production layer. celestia-core is built on Tendermint Core, modified to store data roots of erasure coded blocks among other changes (see ADRs).

  2. celestia-node (see repo)

    • celestia-node augments the above with a separate libp2p network that serves data availability sampling requests. The team sometimes refers to this as the “halo” network.

Hardware requirements ​

The following hardware minimum requirements are recommended for running the bridge node:

  • Memory: 16 GB RAM (minimum)
  • CPU: 6 cores
  • Disk: 10 TB SSD Storage
  • Bandwidth: 1 Gbps for Download/1 Gbps for Upload

Setting up your bridge node ​

The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.

Setup the dependencies ​

Follow the tutorial for installing the dependencies.

Deploy the Celestia bridge node ​

Install Celestia Node ​

Install the celestia-node binary, which will be used to run the bridge node.

Follow the tutorial for installing celestia-node.

Initialize the bridge node ​

Run the following:

sh
celestia bridge init --core.ip <URI>
celestia bridge init --core.ip <URI>

The --core.ip gRPC port defaults to 9090, so if you do not specify it in the command line, it will default to that port. You can add the port after the IP address or use the --core.grpc.port flag to specify another port if you prefer.

Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

Using an RPC of your own, or one from the list on the Mocha testnet page or list on the Arabica devnet page, start your node.

Connecting to a core endpoint with --core.ip string provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).

Here is an example of initializing the bridge node:

sh
celestia bridge init --core.ip <URI>
celestia bridge init --core.ip <URI>
sh
celestia bridge init --core.ip <URI> --p2p.network mocha
celestia bridge init --core.ip <URI> --p2p.network mocha
sh
celestia bridge init --core.ip <URI> --p2p.network arabica
celestia bridge init --core.ip <URI> --p2p.network arabica

Run the bridge node ​

Start the bridge node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):

sh
celestia bridge start --core.ip <URI>
celestia bridge start --core.ip <URI>

Here is an example of starting the bridge node on Mocha:

sh
celestia bridge start --core.ip rpc-mocha.pops.one:26657 --p2p.network mocha
celestia bridge start --core.ip rpc-mocha.pops.one:26657 --p2p.network mocha

And on Arabica:

sh
celestia bridge start --core.ip validator-1.celestia-arabica-11.com \
   --p2p.network arabica
celestia bridge start --core.ip validator-1.celestia-arabica-11.com \
-  --p2p.network arabica

You can create your key for your node by following the cel-key instructions.

Once you start the bridge node, a wallet key will be generated for you. You will need to fund that address with Testnet tokens to pay for PayForBlob transactions. You can find the address by running the following command:

sh
./cel-key list --node.type bridge --keyring-backend test --p2p.network <network>
./cel-key list --node.type bridge --keyring-backend test --p2p.network <network>

TIP

You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information

You can get testnet tokens from:

NOTE

If you are running a bridge node for your validator it is highly recommended to request Mocha testnet tokens as this is the testnet used to test out validator operations.

Optional: run the bridge node with a custom key ​

In order to run a bridge node using a custom key:

  1. The custom key must exist inside the celestia bridge node directory at the correct path (default: ~/.celestia-bridge/keys/keyring-test)
  2. The name of the custom key must be passed upon start, like so:
sh
celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key>
celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key>
sh
celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key> \
+  --p2p.network arabica

You can create your key for your node by following the cel-key instructions.

Once you start the bridge node, a wallet key will be generated for you. You will need to fund that address with Testnet tokens to pay for PayForBlob transactions. You can find the address by running the following command:

sh
./cel-key list --node.type bridge --keyring-backend test --p2p.network <network>
./cel-key list --node.type bridge --keyring-backend test --p2p.network <network>

TIP

You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information

You can get testnet tokens from:

NOTE

If you are running a bridge node for your validator it is highly recommended to request Mocha testnet tokens as this is the testnet used to test out validator operations.

Optional: run the bridge node with a custom key ​

In order to run a bridge node using a custom key:

  1. The custom key must exist inside the celestia bridge node directory at the correct path (default: ~/.celestia-bridge/keys/keyring-test)
  2. The name of the custom key must be passed upon start, like so:
sh
celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key>
celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key>
sh
celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key> \
   --p2p.network mocha
celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key> \
   --p2p.network mocha
sh
celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key> \
   --p2p.network arabica
celestia bridge start --core.ip <URI> --keyring.keyname <name-of-custom-key> \
-  --p2p.network arabica

Optional: Migrate node id to another server ​

To migrate a bridge node ID:

  1. You need to back up two files located in the celestia-bridge node directory at the correct path (default: ~/.celestia-bridge/keys).
  2. Upload the files to the new server and start the node.

Optional: start the bridge node with SystemD ​

Follow the tutorial on setting up the bridge node as a background process with SystemD.

You have successfully set up a bridge node that is syncing with the network.

- + --p2p.network arabica

Optional: Migrate node id to another server ​

To migrate a bridge node ID:

  1. You need to back up two files located in the celestia-bridge node directory at the correct path (default: ~/.celestia-bridge/keys).
  2. Upload the files to the new server and start the node.

Optional: start the bridge node with SystemD ​

Follow the tutorial on setting up the bridge node as a background process with SystemD.

You have successfully set up a bridge node that is syncing with the network.

+ \ No newline at end of file diff --git a/pr-1699/nodes/celestia-app-commands.html b/pr-1699/nodes/celestia-app-commands.html index 6b1d076656..9f3544b72b 100644 --- a/pr-1699/nodes/celestia-app-commands.html +++ b/pr-1699/nodes/celestia-app-commands.html @@ -11,7 +11,7 @@ - + @@ -250,8 +250,8 @@ --commission-max-rate=0.2 \ --commission-max-change-rate=0.01 \ --min-self-delegation=1 \ - --evm-address=$EVM_ADDRESS \

You can then share your gentx JSON file on the networks repo in the respective network directory you are participating in.

- + --evm-address=$EVM_ADDRESS \

You can then share your gentx JSON file on the networks repo in the respective network directory you are participating in.

+ \ No newline at end of file diff --git a/pr-1699/nodes/celestia-app-metrics.html b/pr-1699/nodes/celestia-app-metrics.html index 2c90c2daf5..9cd60c5185 100644 --- a/pr-1699/nodes/celestia-app-metrics.html +++ b/pr-1699/nodes/celestia-app-metrics.html @@ -11,7 +11,7 @@ - + @@ -120,8 +120,8 @@ static_configs: # Point to the same endpoint that Celestia is publishing on - - targets: ["localhost:26660"]

Note, that Prometheus by default runs its server on :9090. If you are running this on the same machine as your consensus node, it will collide with gRPC which runs on the same port. To avoid this, either switch off gRPC (if it's not needed), change the gRPC port in app.toml, or run Prometheus on a different port e.g. --web.listen-address="0.0.0.0:8000"

To run the prometheus server:

bash
prometheus --config.file="$HOME/.celestia-app/config/prometheus.yml"
prometheus --config.file="$HOME/.celestia-app/config/prometheus.yml"

A prometheus server can scrape metrics from multiple nodes at once; a good way of bringing together information from many machines to one place.

To visualize the information, you can use Grafana: either with their cloud option or run the open source code yourself.

Once setup, run:

bash
grafana server
grafana server

which will begin a server on localhost:3000. If you open the url on your browser you will see the Grafana login page. Use admin for both the user and password to log in.

You will need to link the prometheus server as a data source. To do that go to "Configuration" in the sidebar and then "Data Sources". Add a new data source specifying the URL of the Prometheus instance (default at localhost:9090). Click "Save & test" to confirm.

Lastly, you will need to setup a dashboard. You can choose to do this yourself, handpicking the metrics that are important or you can simply export an existing design. Fortunately the cosmos ecosystem has conjured a "Cosmos Dashboard". On the sidebar, click "Dashboards" and then "import". Enter the following dashboard ID: 11036 and then link it to the "Prometheus" data source you just set up. Finally click the "Import" button and the "Cosmos Dashboard" should appear.

Node exporter ​

Celestia's metrics include a plethora of application specific trackers but it's also important to keep an eye on system level metrics such as memory usage and disk space. This can be best achieved by running Node Exporter. Follow the guide in the link to get set up, adding the port number to the prometheus.yml file.

Alerts ​

The final cherry on the cake is to integrate your monitoring system with a mechanism for producing alerts to warn you if your node has crashed or is no longer able to stay at the head of the chain.

Since we're already using Grafana, we can install the Grafana OnCall plugin. OnCall allows you to setup integrations. It could be a webhook or a direct integration into Telegram or Slack. You can find more information on Grafana's Docs Page.

- + - targets: ["localhost:26660"]

Note, that Prometheus by default runs its server on :9090. If you are running this on the same machine as your consensus node, it will collide with gRPC which runs on the same port. To avoid this, either switch off gRPC (if it's not needed), change the gRPC port in app.toml, or run Prometheus on a different port e.g. --web.listen-address="0.0.0.0:8000"

To run the prometheus server:

bash
prometheus --config.file="$HOME/.celestia-app/config/prometheus.yml"
prometheus --config.file="$HOME/.celestia-app/config/prometheus.yml"

A prometheus server can scrape metrics from multiple nodes at once; a good way of bringing together information from many machines to one place.

To visualize the information, you can use Grafana: either with their cloud option or run the open source code yourself.

Once setup, run:

bash
grafana server
grafana server

which will begin a server on localhost:3000. If you open the url on your browser you will see the Grafana login page. Use admin for both the user and password to log in.

You will need to link the prometheus server as a data source. To do that go to "Configuration" in the sidebar and then "Data Sources". Add a new data source specifying the URL of the Prometheus instance (default at localhost:9090). Click "Save & test" to confirm.

Lastly, you will need to setup a dashboard. You can choose to do this yourself, handpicking the metrics that are important or you can simply export an existing design. Fortunately the cosmos ecosystem has conjured a "Cosmos Dashboard". On the sidebar, click "Dashboards" and then "import". Enter the following dashboard ID: 11036 and then link it to the "Prometheus" data source you just set up. Finally click the "Import" button and the "Cosmos Dashboard" should appear.

Node exporter ​

Celestia's metrics include a plethora of application specific trackers but it's also important to keep an eye on system level metrics such as memory usage and disk space. This can be best achieved by running Node Exporter. Follow the guide in the link to get set up, adding the port number to the prometheus.yml file.

Alerts ​

The final cherry on the cake is to integrate your monitoring system with a mechanism for producing alerts to warn you if your node has crashed or is no longer able to stay at the head of the chain.

Since we're already using Grafana, we can install the Grafana OnCall plugin. OnCall allows you to setup integrations. It could be a webhook or a direct integration into Telegram or Slack. You can find more information on Grafana's Docs Page.

+ \ No newline at end of file diff --git a/pr-1699/nodes/celestia-app-multisig.html b/pr-1699/nodes/celestia-app-multisig.html index cc34f891a1..7cc68d25e2 100644 --- a/pr-1699/nodes/celestia-app-multisig.html +++ b/pr-1699/nodes/celestia-app-multisig.html @@ -11,7 +11,7 @@ - + @@ -140,8 +140,8 @@ celestia-appd tx multisign unsignedTx.json multisig \ test1sig.json test2sig.json \ --output-document signedTx.json \ - --chain-id $CHAIN_ID

Resources ​

- + --chain-id $CHAIN_ID

Resources ​

+ \ No newline at end of file diff --git a/pr-1699/nodes/celestia-app-slashing.html b/pr-1699/nodes/celestia-app-slashing.html index 0cbb24d0d1..7f1cdf3611 100644 --- a/pr-1699/nodes/celestia-app-slashing.html +++ b/pr-1699/nodes/celestia-app-slashing.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Jailing and Slashing on Celestia ​

Slashing is a mechanism employed in proof of stake blockchains that is used to deter and punish malicious behavior. It functions by removing a percentage of a validator's stake each time they act harmfully towards the network.

Celestia is built with the Cosmos SDK and uses the x/slashing module.

If a validator gets slashed, delegators bonded to that validator will also have the same percentage of their delegated funds slashed.

The following are the conditions for a validator to get jailed or slashed:

  1. Downtime: If a validator is offline for more than 25% of a rolling window of the last 5,000 blocks, they will be jailed for 1 minute. During this period, the validator is removed from the validator set temporarily, and will be unable to propose new blocks or earn rewards. After the jail period, the validator can send an unjail request to rejoin the validator set.

  2. Double signing: This is a more severe offense and results in getting slashed. If a validator engages in double signing, the validator will lose 2% of their stake and the remainder of their stake will be returned to them. The validator will be permanently removed from the validator set and will not have the ability to unjail. Delegators bonded to that validator will automatically enter the unbonding period for 21 days, and can delegate to another validator after they have been unbonded.

For more details on the jailing and slashing parameters, refer to the celestia-app specifications page.

- +

Jailing and Slashing on Celestia ​

Slashing is a mechanism employed in proof of stake blockchains that is used to deter and punish malicious behavior. It functions by removing a percentage of a validator's stake each time they act harmfully towards the network.

Celestia is built with the Cosmos SDK and uses the x/slashing module.

If a validator gets slashed, delegators bonded to that validator will also have the same percentage of their delegated funds slashed.

The following are the conditions for a validator to get jailed or slashed:

  1. Downtime: If a validator is offline for more than 25% of a rolling window of the last 5,000 blocks, they will be jailed for 1 minute. During this period, the validator is removed from the validator set temporarily, and will be unable to propose new blocks or earn rewards. After the jail period, the validator can send an unjail request to rejoin the validator set.

  2. Double signing: This is a more severe offense and results in getting slashed. If a validator engages in double signing, the validator will lose 2% of their stake and the remainder of their stake will be returned to them. The validator will be permanently removed from the validator set and will not have the ability to unjail. Delegators bonded to that validator will automatically enter the unbonding period for 21 days, and can delegate to another validator after they have been unbonded.

For more details on the jailing and slashing parameters, refer to the celestia-app specifications page.

+ \ No newline at end of file diff --git a/pr-1699/nodes/celestia-app-upgrade-monitor.html b/pr-1699/nodes/celestia-app-upgrade-monitor.html index 617d34369e..6907714632 100644 --- a/pr-1699/nodes/celestia-app-upgrade-monitor.html +++ b/pr-1699/nodes/celestia-app-upgrade-monitor.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

Appearance

Upgrade Monitor ​

Upgrade monitor is a binary that monitors that status of upgrades on a Celestia network. See the README for instructions on how to install and use the binary.

- +

Upgrade Monitor ​

Upgrade monitor is a binary that monitors that status of upgrades on a Celestia network. See the README for instructions on how to install and use the binary.

+ \ No newline at end of file diff --git a/pr-1699/nodes/celestia-app-vesting.html b/pr-1699/nodes/celestia-app-vesting.html index de6f260c51..e6f3296fb6 100644 --- a/pr-1699/nodes/celestia-app-vesting.html +++ b/pr-1699/nodes/celestia-app-vesting.html @@ -11,7 +11,7 @@ - + @@ -252,8 +252,8 @@ # <host>:<port> to Tendermint RPC interface for this chain node = "tcp://rpc-mocha.pops.one:443" # Transaction broadcasting mode (sync|async|block) -broadcast-mode = "sync"

Notes ​

Not all vesting accounts can be created with a message, some need to be set at genesis. You can learn more in the Cosmos Network documentation.

Conclusion ​

Congratulations! You've learned how to create a local devnet, create a vesting account on it, and how to make a vesting account on the Mocha testnet!

- +broadcast-mode = "sync"

Notes ​

Not all vesting accounts can be created with a message, some need to be set at genesis. You can learn more in the Cosmos Network documentation.

Conclusion ​

Congratulations! You've learned how to create a local devnet, create a vesting account on it, and how to make a vesting account on the Mocha testnet!

+ \ No newline at end of file diff --git a/pr-1699/nodes/celestia-app-wallet.html b/pr-1699/nodes/celestia-app-wallet.html index cd853fbf19..5e4f8c777e 100644 --- a/pr-1699/nodes/celestia-app-wallet.html +++ b/pr-1699/nodes/celestia-app-wallet.html @@ -11,7 +11,7 @@ - + @@ -40,8 +40,8 @@

Create a wallet with celestia-app ​

For this guide, we will go over how you can generate a Celestia wallet using celestia-app.

Prerequisites ​

Note, you do not need to install celestia-node for this tutorial.

Create a wallet ​

First, create an application CLI configuration file:

sh
celestia-appd config keyring-backend test
celestia-appd config keyring-backend test

You can pick whatever wallet name you want. For our example we used "validator" as the wallet name:

sh
celestia-appd keys add validator --interactive
celestia-appd keys add validator --interactive

Save the mnemonic output as this is the only way to recover your validator wallet in case you lose it!

To check all your wallets you can run:

sh
celestia-appd keys list
celestia-appd keys list

Fund a wallet ​

For the public celestia address, you can fund the previously created wallet via Discord by sending this message to either the #mocha-faucet or #arabica-faucet channel:

text
$request celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
$request celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Wait to see if you get a confirmation that the tokens have been successfully sent. To check if tokens have arrived successfully to the destination wallet run the command below replacing the public address with your own:

sh
celestia-appd start
 celestia-appd query bank balances celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
celestia-appd start
-celestia-appd query bank balances celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TIP

Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

- +celestia-appd query bank balances celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TIP

Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

+ \ No newline at end of file diff --git a/pr-1699/nodes/celestia-app.html b/pr-1699/nodes/celestia-app.html index 96ff335d8e..bea58ded78 100644 --- a/pr-1699/nodes/celestia-app.html +++ b/pr-1699/nodes/celestia-app.html @@ -14,7 +14,7 @@ - + @@ -47,8 +47,8 @@ cd celestia-app
cd $HOME
 rm -rf celestia-app
 git clone https://github.com/celestiaorg/celestia-app.git
-cd celestia-app

  • Check out to the desired version, based on the network you will use:

    bash
    git checkout tags/v1.13.0
    git checkout tags/v1.13.0
    bash
    git checkout tags/v2.1.2
    git checkout tags/v2.1.2
    bash
    git checkout tags/v2.1.2
    git checkout tags/v2.1.2

  • Build and install the celestia-appd binary:

    bash
    make install
    make install

  • To check if the binary was successfully installed you can run the binary using the --help flag:

    sh
    celestia-appd --help
    celestia-appd --help

    • You will see an output with the menu for celestia-appd. Learn more on the helpful CLI commands page

    Installing a pre-built binary ​

    Installing a pre-built binary is the fastest way to get started with your Celestia consensus node. Releases after celestia-app v1.3.0 should have these binaries available.

    The steps below will download a binary file named celestia-appd. Depending on the setup that you choose during installation, the celestia-appd binary will be available at either:

    • $HOME/celestia-app-temp/celestia-appd
    • /usr/local/bin/celestia-appd

    Pre-built binaries are available for:

    • Operating systems: Darwin (Apple), Linux
    • Architectures: x86_64 (amd64), arm64

    To install the latest pre-built binary you can run this command in your terminal:

    bash
    bash -c "$(curl -sL https://docs.celestia.org/celestia-app.sh)"
    bash -c "$(curl -sL https://docs.celestia.org/celestia-app.sh)"

    Follow the instructions in the terminal output to choose your installation preferences.

    You will see an output with the menu for celestia-appd. Learn more on the helpful CLI commands page

    View the script to learn more about what it is doing.

    Ports ​

    When interacting with a consensus node, you may need to open ports on your machine to allow communication between nodes, such as bridge nodes. It is essential that specific ports are accessible. Make sure that your firewall allows connections to the correct ports.

    If you run a node on a cloud server, make sure that the ports are open on the server's firewall. If you run a node at home, make sure that your router allows connections to the correct ports.

    For example, validator ports 9090 and 26657 need to be accessible by the bridge, and port 2121 is required for P2P connections for all node types.

    The following ports are used by Celestia app nodes:

    PortProtocolAddressDescriptionEnabled by default on nodeFlag
    2121TCP/UDPlocalhostP2PtrueN/A
    9090HTTP0.0.0.0gRPCtrue--grpc.address string
    26657TCPlocalhostRPCfalse (only open to localhost)--rpc.laddr string
    - +cd celestia-app

  • Check out to the desired version, based on the network you will use:

    bash
    git checkout tags/v1.13.0
    git checkout tags/v1.13.0
    bash
    git checkout tags/v2.1.2
    git checkout tags/v2.1.2
    bash
    git checkout tags/v2.1.2
    git checkout tags/v2.1.2

  • Build and install the celestia-appd binary:

    bash
    make install
    make install

  • To check if the binary was successfully installed you can run the binary using the --help flag:

    sh
    celestia-appd --help
    celestia-appd --help

    • You will see an output with the menu for celestia-appd. Learn more on the helpful CLI commands page

    Installing a pre-built binary ​

    Installing a pre-built binary is the fastest way to get started with your Celestia consensus node. Releases after celestia-app v1.3.0 should have these binaries available.

    The steps below will download a binary file named celestia-appd. Depending on the setup that you choose during installation, the celestia-appd binary will be available at either:

    • $HOME/celestia-app-temp/celestia-appd
    • /usr/local/bin/celestia-appd

    Pre-built binaries are available for:

    • Operating systems: Darwin (Apple), Linux
    • Architectures: x86_64 (amd64), arm64

    To install the latest pre-built binary you can run this command in your terminal:

    bash
    bash -c "$(curl -sL https://docs.celestia.org/celestia-app.sh)"
    bash -c "$(curl -sL https://docs.celestia.org/celestia-app.sh)"

    Follow the instructions in the terminal output to choose your installation preferences.

    You will see an output with the menu for celestia-appd. Learn more on the helpful CLI commands page

    View the script to learn more about what it is doing.

    Ports ​

    When interacting with a consensus node, you may need to open ports on your machine to allow communication between nodes, such as bridge nodes. It is essential that specific ports are accessible. Make sure that your firewall allows connections to the correct ports.

    If you run a node on a cloud server, make sure that the ports are open on the server's firewall. If you run a node at home, make sure that your router allows connections to the correct ports.

    For example, validator ports 9090 and 26657 need to be accessible by the bridge, and port 2121 is required for P2P connections for all node types.

    The following ports are used by Celestia app nodes:

    PortProtocolAddressDescriptionEnabled by default on nodeFlag
    2121TCP/UDPlocalhostP2PtrueN/A
    9090HTTP0.0.0.0gRPCtrue--grpc.address string
    26657TCPlocalhostRPCfalse (only open to localhost)--rpc.laddr string
    + \ No newline at end of file diff --git a/pr-1699/nodes/celestia-node-custom-networks.html b/pr-1699/nodes/celestia-node-custom-networks.html index ed62b37f4b..296849975a 100644 --- a/pr-1699/nodes/celestia-node-custom-networks.html +++ b/pr-1699/nodes/celestia-node-custom-networks.html @@ -11,7 +11,7 @@ - + @@ -50,8 +50,8 @@ export CELESTIA_CUSTOM="${NETWORK}:${GENESIS_HASH}:${BRIDGE}"
    export BRIDGE="/ip4/151.115.14.33/tcp/2121/p2p/12D3KooWKEeRtzVMPUdxYsZo2edqps6mS67n6LT5mPdULSkPSxBQ"
 export GENESIS_HASH=580B3DFF8A7C716968161D91116A1E171F486298D582874E93714E489C9E6E88
 export NETWORK=custom
-export CELESTIA_CUSTOM="${NETWORK}:${GENESIS_HASH}:${BRIDGE}"

    Then, start your node with:

    bash
    celestia <node-type> start [flags...]
    celestia <node-type> start [flags...]
    - +export CELESTIA_CUSTOM="${NETWORK}:${GENESIS_HASH}:${BRIDGE}"

    Then, start your node with:

    bash
    celestia <node-type> start [flags...]
    celestia <node-type> start [flags...]
    + \ No newline at end of file diff --git a/pr-1699/nodes/celestia-node-metrics.html b/pr-1699/nodes/celestia-node-metrics.html index 4126118341..6d604a1781 100644 --- a/pr-1699/nodes/celestia-node-metrics.html +++ b/pr-1699/nodes/celestia-node-metrics.html @@ -11,7 +11,7 @@ - + @@ -66,8 +66,8 @@ # To disable TLS connection celestia <node-type> start --metrics.tls=false --metrics \ --metrics.endpoint <URI> \ - --p2p.network <network> --core.ip <URI>

    Metrics endpoint design considerations ​

    At the moment, the architecture of celestia-node metrics works as specified in the following ADR #010.

    Essentially, the design considerations here will necessitate running an OpenTelemetry (OTEL) collector that connects to Celestia light node.

    For an overview of OTEL, check out the guide.

    The ADR and the OTEL docs will help you run your collector on the metrics endpoint. This will then allow you to process the data in the collector on a Prometheus server which can then be viewed on a Grafana dashboard.

    In the future, we do want to open-source some developer toolings around this infrastructure to allow for node operators to be able to monitor their data availability nodes.

    - + --p2p.network <network> --core.ip <URI>

    Metrics endpoint design considerations ​

    At the moment, the architecture of celestia-node metrics works as specified in the following ADR #010.

    Essentially, the design considerations here will necessitate running an OpenTelemetry (OTEL) collector that connects to Celestia light node.

    For an overview of OTEL, check out the guide.

    The ADR and the OTEL docs will help you run your collector on the metrics endpoint. This will then allow you to process the data in the collector on a Prometheus server which can then be viewed on a Grafana dashboard.

    In the future, we do want to open-source some developer toolings around this infrastructure to allow for node operators to be able to monitor their data availability nodes.

    + \ No newline at end of file diff --git a/pr-1699/nodes/celestia-node-troubleshooting.html b/pr-1699/nodes/celestia-node-troubleshooting.html index d683068cd4..d1c4aa9cad 100644 --- a/pr-1699/nodes/celestia-node-troubleshooting.html +++ b/pr-1699/nodes/celestia-node-troubleshooting.html @@ -12,7 +12,7 @@ - + @@ -99,8 +99,8 @@ ...
    [Service]
 ...
 LimitNOFILE=1400000
-...

    NOTE

    Be cautious when increasing file descriptor limits. Setting this value too high might affect system performance. Ensure the value is appropriate for your system's capabilities.

    1. Reload daemon and restart bridge service:
    bash
    sudo systemctl daemon-reload
    sudo systemctl daemon-reload
    bash
    sudo systemctl restart celestia-bridge
    sudo systemctl restart celestia-bridge
    - +...

    NOTE

    Be cautious when increasing file descriptor limits. Setting this value too high might affect system performance. Ensure the value is appropriate for your system's capabilities.

    1. Reload daemon and restart bridge service:
    bash
    sudo systemctl daemon-reload
    sudo systemctl daemon-reload
    bash
    sudo systemctl restart celestia-bridge
    sudo systemctl restart celestia-bridge
    + \ No newline at end of file diff --git a/pr-1699/nodes/celestia-node-trusted-hash.html b/pr-1699/nodes/celestia-node-trusted-hash.html index b8122e299d..ee91d643b8 100644 --- a/pr-1699/nodes/celestia-node-trusted-hash.html +++ b/pr-1699/nodes/celestia-node-trusted-hash.html @@ -11,7 +11,7 @@ - + @@ -40,8 +40,8 @@

    Syncing a light node from a trusted hash ​

    This guide goes over how to sync a DA light node from a trusted hash. The example is with Mainnet Beta. You will need to adjust the commands accordingly for Mocha, Arabica, or a custom network.

    WARNING

    Syncing to a trusted hash means that you will not sample the entire chain. This adds a trust assumption that you trust the history of the chain up to that point and that you trust the entity where you get the hash from. In this example, the trusted entity is a consensus endpoint or Celenium

    1. Get trusted height & hash from a consensus endpoint or Celenium.

    2. Initialize the node store

      sh
      celestia light init --p2p.network <network>
      celestia light init --p2p.network <network>

    3. Set the trusted height & hash

      1. Open your config.toml at .celestia-light/config.toml (or .celestia-light-<other-network>/config.toml)
      2. Set DASer.SampleFrom to the trusted height (e.g. SampleFrom = 123456)

    4. Run the node with the hash and flag:

    sh
    celestia light start --headers.trusted-hash <hash_of_block_n> \
     --p2p.network <network> --core.ip <consensus-node-rpc>
    celestia light start --headers.trusted-hash <hash_of_block_n> \
-    --p2p.network <network> --core.ip <consensus-node-rpc>

    For service operators ​

    If you're using multiple light nodes for similar services like tracking the same rollup, it is recommended to use the same hash and height for them all services using the same starting height.

    - + --p2p.network <network> --core.ip <consensus-node-rpc>

    For service operators ​

    If you're using multiple light nodes for similar services like tracking the same rollup, it is recommended to use the same hash and height for them all services using the same starting height.

    + \ No newline at end of file diff --git a/pr-1699/nodes/celestia-node.html b/pr-1699/nodes/celestia-node.html index d6c3942f05..8f24307065 100644 --- a/pr-1699/nodes/celestia-node.html +++ b/pr-1699/nodes/celestia-node.html @@ -14,7 +14,7 @@ - + @@ -47,8 +47,8 @@ cd celestia-node/
    cd $HOME
 rm -rf celestia-node
 git clone https://github.com/celestiaorg/celestia-node.git
-cd celestia-node/

  • Check out to the desired version, based on the network you will use:

    bash
    git checkout tags/v0.15.0
    git checkout tags/v0.15.0
    bash
    git checkout tags/v0.16.0
    git checkout tags/v0.16.0
    bash
    git checkout tags/v0.16.0
    git checkout tags/v0.16.0

  • Build the celestia binary:

    a. Standard build

    bash
    make build
    make build

    b. Experimental build

    OPTIONAL

    If you're a node operator comfortable with experimental features and seeking optimal performance with minimal RAM usage, this option is recommended for you.

    bash
    make build-jemalloc
    make build-jemalloc

    This build option enables CGO, and downloads and installs jemalloc. Learn more about the build command.

  • Install the binary:

    bash
    make install
    make install

  • Build the cel-key utility:

    bash
    make cel-key
    make cel-key

  • Verify that the binary is working and check the version:

    bash
    celestia version
    celestia version

    • The output will show the semantic version of celestia-node, commit hash, build date, system version, and Golang version.

    Installing a pre-built binary ​

    Installing a pre-built binary is the fastest way to get started with your Celestia data availability node. Releases after celestia-node v0.13.3 should have these binaries available.

    The steps below will download a binary file named celestia. Depending on the setup that you choose during installation, the celestia binary will be available at either:

    • $HOME/celestia-node-temp/celestia
    • /usr/local/bin/celestia

    Pre-built binaries are available for:

    • Operating systems: Darwin (Apple), Linux
    • Architectures: x86_64 (amd64), arm64

    To install the latest pre-built binary you can run this command in your terminal:

    bash
    bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"
    bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"

    Follow the instructions in the terminal output to choose your installation preferences.

    You will see an output with the menu for celestia.

    View the script to learn more about what it is doing.

    Next steps ​

    First, we recommend reading the overview of our node types, if you haven't yet.

    Now that you've installed Celestia Node, it's time to pick your node type and run your node!

    If you're planning to run a light node, we recommend the node RPC CLI tutorial.

    Upgrading your binary ​

    To upgrade your binary, you can install the latest version from the instructions above and restart your node. If you run into any issues, Refer to the troubleshooting section.

    - +cd celestia-node/

  • Check out to the desired version, based on the network you will use:

    bash
    git checkout tags/v0.15.0
    git checkout tags/v0.15.0
    bash
    git checkout tags/v0.16.0
    git checkout tags/v0.16.0
    bash
    git checkout tags/v0.16.0
    git checkout tags/v0.16.0

  • Build the celestia binary:

    a. Standard build

    bash
    make build
    make build

    b. Experimental build

    OPTIONAL

    If you're a node operator comfortable with experimental features and seeking optimal performance with minimal RAM usage, this option is recommended for you.

    bash
    make build-jemalloc
    make build-jemalloc

    This build option enables CGO, and downloads and installs jemalloc. Learn more about the build command.

  • Install the binary:

    bash
    make install
    make install

  • Build the cel-key utility:

    bash
    make cel-key
    make cel-key

  • Verify that the binary is working and check the version:

    bash
    celestia version
    celestia version

    • The output will show the semantic version of celestia-node, commit hash, build date, system version, and Golang version.

    Installing a pre-built binary ​

    Installing a pre-built binary is the fastest way to get started with your Celestia data availability node. Releases after celestia-node v0.13.3 should have these binaries available.

    The steps below will download a binary file named celestia. Depending on the setup that you choose during installation, the celestia binary will be available at either:

    • $HOME/celestia-node-temp/celestia
    • /usr/local/bin/celestia

    Pre-built binaries are available for:

    • Operating systems: Darwin (Apple), Linux
    • Architectures: x86_64 (amd64), arm64

    To install the latest pre-built binary you can run this command in your terminal:

    bash
    bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"
    bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"

    Follow the instructions in the terminal output to choose your installation preferences.

    You will see an output with the menu for celestia.

    View the script to learn more about what it is doing.

    Next steps ​

    First, we recommend reading the overview of our node types, if you haven't yet.

    Now that you've installed Celestia Node, it's time to pick your node type and run your node!

    If you're planning to run a light node, we recommend the node RPC CLI tutorial.

    Upgrading your binary ​

    To upgrade your binary, you can install the latest version from the instructions above and restart your node. If you run into any issues, Refer to the troubleshooting section.

    + \ No newline at end of file diff --git a/pr-1699/nodes/config-toml.html b/pr-1699/nodes/config-toml.html index 010e0065d7..ef8896af09 100644 --- a/pr-1699/nodes/config-toml.html +++ b/pr-1699/nodes/config-toml.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    config.toml guide ​

    Pre-requisites ​

    Please, make sure that you have installed and initialized celestia-node

    Understanding config.toml ​

    After initialization, for any type of node, you will find a config.toml in the following path (default location):

    • $HOME/.celestia-bridge/config.toml for bridge node
    • $HOME/.celestia-light/config.toml for light node
    • $HOME/.celestia-full/config.toml for a full DA node

    Let's break down some of the most used sections.

    Core ​

    This section is needed for the Celestia bridge node. By default, Remote = false. Still for devnet, we are going to use the remote core option and this can also be set by the command line flag --core.remote.

    P2P ​

    Bootstrap ​

    Bootstrappers help new nodes to find peers faster in the network. By default, the Bootstrapper = false and the BootstrapPeers is empty. If you want your node to be a bootstrapper, then activate Bootstrapper = true. BootstrapPeers are already provided by default during initialisation. If you want to add your own manually, you need to provide the multiaddresses of the peers.

    Mutual peers ​

    The purpose of this config is to set up a bidirectional communication. This is usually the case for Celestia bridge nodes. In addition, you need to change the field PeerExchange from false to true.

    Services ​

    TrustedHash and TrustedPeer ​

    TrustedHash is needed to properly initialize a Celestia bridge node with an already-running Remote celestia-core node. Celestia light node will take a genesis hash as the trusted one, if no hash is manually provided during initialization phase.

    TrustedPeers is the array of bridge nodes' peers that Celestia light node trusts. By default, bootstrap peers becomes trusted peers for Celestia light nodes if a user is not setting the trusted peer params in config file.

    Any Celestia bridge node can be a trusted peer for the light one. However, the light node by design can not be a trusted peer for another light node.

    - +

    config.toml guide ​

    Pre-requisites ​

    Please, make sure that you have installed and initialized celestia-node

    Understanding config.toml ​

    After initialization, for any type of node, you will find a config.toml in the following path (default location):

    • $HOME/.celestia-bridge/config.toml for bridge node
    • $HOME/.celestia-light/config.toml for light node
    • $HOME/.celestia-full/config.toml for a full DA node

    Let's break down some of the most used sections.

    Core ​

    This section is needed for the Celestia bridge node. By default, Remote = false. Still for devnet, we are going to use the remote core option and this can also be set by the command line flag --core.remote.

    P2P ​

    Bootstrap ​

    Bootstrappers help new nodes to find peers faster in the network. By default, the Bootstrapper = false and the BootstrapPeers is empty. If you want your node to be a bootstrapper, then activate Bootstrapper = true. BootstrapPeers are already provided by default during initialisation. If you want to add your own manually, you need to provide the multiaddresses of the peers.

    Mutual peers ​

    The purpose of this config is to set up a bidirectional communication. This is usually the case for Celestia bridge nodes. In addition, you need to change the field PeerExchange from false to true.

    Services ​

    TrustedHash and TrustedPeer ​

    TrustedHash is needed to properly initialize a Celestia bridge node with an already-running Remote celestia-core node. Celestia light node will take a genesis hash as the trusted one, if no hash is manually provided during initialization phase.

    TrustedPeers is the array of bridge nodes' peers that Celestia light node trusts. By default, bootstrap peers becomes trusted peers for Celestia light nodes if a user is not setting the trusted peer params in config file.

    Any Celestia bridge node can be a trusted peer for the light one. However, the light node by design can not be a trusted peer for another light node.

    + \ No newline at end of file diff --git a/pr-1699/nodes/consensus-node.html b/pr-1699/nodes/consensus-node.html index ba38367a44..5f6f418bfb 100644 --- a/pr-1699/nodes/consensus-node.html +++ b/pr-1699/nodes/consensus-node.html @@ -12,7 +12,7 @@ - + @@ -39,7 +39,7 @@

    Appearance

    Consensus node ​

    This guide covers how to set up a consensus node on Celestia. Consensus nodes allow you to sync the entire blockchain history in the Celestia consensus layer.

    consensus node

    Minimum hardware requirements ​

    The following minimum hardware requirements are recommended for running a consensus node:

    • Memory: 16 GB RAM
    • CPU: Quad-Core
    • Disk: 2 TB SSD Storage
    • Bandwidth: 1 Gbps for Download/1 Gbps for Upload

    Set up a consensus node ​

    The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.

    Set up the dependencies ​

    Follow the instructions on installing dependencies.

    Install celestia-app ​

    Follow the tutorial on installing celestia-app.

    Set up the P2P networks ​

    To initialize the network, pick a "node-name" that describes your node. Keep in mind that this might change if a new testnet is deployed.

    bash
    celestia-appd init "node-name" --chain-id celestia
    celestia-appd init "node-name" --chain-id celestia
    bash
    celestia-appd init "node-name" --chain-id mocha-4
    celestia-appd init "node-name" --chain-id mocha-4
    bash
    celestia-appd init "node-name" --chain-id arabica-11
    celestia-appd init "node-name" --chain-id arabica-11

    Download the genesis.json file:

    bash
    celestia-appd download-genesis celestia
    celestia-appd download-genesis celestia
    bash
    celestia-appd download-genesis mocha-4
    celestia-appd download-genesis mocha-4
    bash
    celestia-appd download-genesis arabica-11
    celestia-appd download-genesis arabica-11

    Set seeds in the $HOME/.celestia-app/config/config.toml file:

    bash
    SEEDS=$(curl -sL https://raw.githubusercontent.com/celestiaorg/networks/master/celestia/seeds.txt | tr '\n' ',')
+

    Consensus node ​

    This guide covers how to set up a consensus node on Celestia. Consensus nodes allow you to sync the entire blockchain history in the Celestia consensus layer.

    consensus node

    Minimum hardware requirements ​

    The following minimum hardware requirements are recommended for running a consensus node:

    • Memory: 16 GB RAM
    • CPU: Quad-Core
    • Disk: 2 TB SSD Storage
    • Bandwidth: 1 Gbps for Download/1 Gbps for Upload

    Set up a consensus node ​

    The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.

    Set up the dependencies ​

    Follow the instructions on installing dependencies.

    Install celestia-app ​

    Follow the tutorial on installing celestia-app.

    Set up the P2P networks ​

    To initialize the network, pick a "node-name" that describes your node. Keep in mind that this might change if a new testnet is deployed.

    bash
    celestia-appd init "node-name" --chain-id celestia
    celestia-appd init "node-name" --chain-id celestia
    bash
    celestia-appd init "node-name" --chain-id mocha-4
    celestia-appd init "node-name" --chain-id mocha-4
    bash
    celestia-appd init "node-name" --chain-id arabica-11
    celestia-appd init "node-name" --chain-id arabica-11

    Download the genesis.json file:

    bash
    celestia-appd download-genesis celestia
    celestia-appd download-genesis celestia
    bash
    celestia-appd download-genesis mocha-4
    celestia-appd download-genesis mocha-4
    bash
    celestia-appd download-genesis arabica-11
    celestia-appd download-genesis arabica-11

    Set seeds in the $HOME/.celestia-app/config/config.toml file:

    bash
    SEEDS=$(curl -sL https://raw.githubusercontent.com/celestiaorg/networks/master/celestia/seeds.txt | tr '\n' ',')
 echo $SEEDS
 sed -i.bak -e "s/^seeds *=.*/seeds = \"$SEEDS\"/" $HOME/.celestia-app/config/config.toml
    SEEDS=$(curl -sL https://raw.githubusercontent.com/celestiaorg/networks/master/celestia/seeds.txt | tr '\n' ',')
 echo $SEEDS
@@ -53,7 +53,7 @@
 seeds = ""
    # For Arabica, you can set seeds manually in the
 # `$HOME/.celestia-app/config/config.toml` file:
 # Comma separated list of seed nodes to connect to
-seeds = ""
    Optional: Set persistent peers

    Optionally, you can set persistent peers in your config.toml file. If you set persistent peers, your node will always try to connect to these peers. This is useful when running a local devnet, for example, when you would always want to connect to the same local nodes in your devnet. In production, setting persistent peers is advised only if you are running a sentry node.

    You can get the persistent peers from the @cosmos/chain-registry repository (for Mainnet Beta) or @celestiaorg/networks repository repo (for Mocha and Arabica) with the following commands:

    bash
    PERSISTENT_PEERS=$(curl -s https://raw.githubusercontent.com/cosmos/chain-registry/master/celestia/chain.json | jq -r '.peers.persistent_peers[].address' | tr '\n' ',' | sed 's/,$/\n/')
+seeds = ""
    Optional: Set persistent peers

    Optionally, you can set persistent peers in your config.toml file. If you set persistent peers, your node will always try to connect to these peers. This is useful when running a local devnet, for example, when you would always want to connect to the same local nodes in your devnet. In production, setting persistent peers is advised only if you are running a sentry node.

    You can get the persistent peers from the @cosmos/chain-registry repository (for Mainnet Beta) or @celestiaorg/networks repository repo (for Mocha and Arabica) with the following commands:

    bash
    PERSISTENT_PEERS=$(curl -s https://raw.githubusercontent.com/cosmos/chain-registry/master/celestia/chain.json | jq -r '.peers.persistent_peers[].address' | tr '\n' ',' | sed 's/,$/\n/')
 echo $PERSISTENT_PEERS
 sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PERSISTENT_PEERS\"/" $HOME/.celestia-app/config/config.toml
    PERSISTENT_PEERS=$(curl -s https://raw.githubusercontent.com/cosmos/chain-registry/master/celestia/chain.json | jq -r '.peers.persistent_peers[].address' | tr '\n' ',' | sed 's/,$/\n/')
 echo $PERSISTENT_PEERS
@@ -79,7 +79,7 @@
 ###         State Sync Configuration Options        ###
 #######################################################
 [statesync]
-enable = true

    To their respective fields. At least two different rpc endpoints should be provided. The more, the greater the chance of detecting any fraudulent behavior.

    Once setup, you should be ready to start the node as normal. In the logs, you should see: Discovering snapshots. This may take a few minutes before snapshots are found depending on the network topology.

    Option 3: Quick sync ​

    Quick sync effectively downloads the entire data directory from a third-party provider meaning the node has all the application and blockchain state as the node it was copied from.

    Run the following command to quick-sync from a snapshot:

    bash
    cd $HOME
+enable = true

    To their respective fields. At least two different rpc endpoints should be provided. The more, the greater the chance of detecting any fraudulent behavior.

    Once setup, you should be ready to start the node as normal. In the logs, you should see: Discovering snapshots. This may take a few minutes before snapshots are found depending on the network topology.

    Option 3: Quick sync ​

    Quick sync effectively downloads the entire data directory from a third-party provider meaning the node has all the application and blockchain state as the node it was copied from.

    Run the following command to quick-sync from a snapshot:

    bash
    cd $HOME
 rm -rf ~/.celestia-app/data
 mkdir -p ~/.celestia-app/data
 SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \
@@ -115,12 +115,12 @@
 SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \
     egrep -o ">arabica-11.*tar" | tr -d ">")
 aria2c -x 16 -s 16 -o celestia-snap.tar "https://snaps.qubelabs.io/celestia/${SNAP_NAME}"
-tar xf celestia-snap.tar -C ~/.celestia-app/data/

    Start the consensus node ​

    If you are running celestia-app v1.x.x:

    sh
    celestia-appd start
    celestia-appd start

    If you are running celestia-app >= v2.0.0: then you'll want to start the node with a --v2-upgrade-height that is dependent on the network. The --v2-upgrade-height flag is only needed during the v2 upgrade height so after your node has executed the upgrade (e.g. you see the log upgraded from app version 1 to 2), you don't need to provide this flag for future celestia-appd start invocations.

    sh
    celestia-appd start --v2-upgrade-height 2371495
    celestia-appd start --v2-upgrade-height 2371495
    sh
    celestia-appd start --v2-upgrade-height 2585031
    celestia-appd start --v2-upgrade-height 2585031
    sh
    celestia-appd start --v2-upgrade-height 1751707
    celestia-appd start --v2-upgrade-height 1751707

    Optional: If you would like celestia-app to run as a background process, you can follow the SystemD tutorial.

    Extra resources for consensus nodes ​

    Optional: Reset network ​

    This will delete all data folders so we can start fresh:

    sh
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app

    Optional: Configure an RPC endpoint ​

    You can configure your consensus node to be a public RPC endpoint. This allows it to accept connections from data availability nodes and serve requests for the data availability API.

    Expose RPC ​

    By default, the RPC service listens on localhost which means it can't be accessed from other machines. To make the RPC service available publicly, you need to bind it to a public IP or 0.0.0.0 (which means listening on all available network interfaces).

    You can do this by editing the config.toml file:

    sh
    sed -i 's#"tcp://127.0.0.1:26657"#"tcp://0.0.0.0:26657"#g' ~/.celestia-app/config/config.toml
    sed -i 's#"tcp://127.0.0.1:26657"#"tcp://0.0.0.0:26657"#g' ~/.celestia-app/config/config.toml

    This command replaces the localhost IP address with 0.0.0.0, making the RPC service listen on all available network interfaces.

    Note on external-address ​

    The external-address field in the configuration is used when your node is behind a NAT and you need to advertise a different address for peers to dial. Populating this field is not necessary for making the RPC endpoint public.

    sh
    EXTERNAL-ADDRESS=$(wget -qO- eth0.me)
+tar xf celestia-snap.tar -C ~/.celestia-app/data/

    Start the consensus node ​

    If you are running celestia-app v1.x.x:

    sh
    celestia-appd start
    celestia-appd start

    If you are running celestia-app >= v2.0.0: then you'll want to start the node with a --v2-upgrade-height that is dependent on the network. The --v2-upgrade-height flag is only needed during the v2 upgrade height so after your node has executed the upgrade (e.g. you see the log upgraded from app version 1 to 2), you don't need to provide this flag for future celestia-appd start invocations.

    sh
    celestia-appd start --v2-upgrade-height 2371495
    celestia-appd start --v2-upgrade-height 2371495
    sh
    celestia-appd start --v2-upgrade-height 2585031
    celestia-appd start --v2-upgrade-height 2585031
    sh
    celestia-appd start --v2-upgrade-height 1751707
    celestia-appd start --v2-upgrade-height 1751707

    Optional: If you would like celestia-app to run as a background process, you can follow the SystemD tutorial.

    Extra resources for consensus nodes ​

    Optional: Reset network ​

    This will delete all data folders so we can start fresh:

    sh
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app
    celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app

    Optional: Configure an RPC endpoint ​

    You can configure your consensus node to be a public RPC endpoint. This allows it to accept connections from data availability nodes and serve requests for the data availability API.

    Expose RPC ​

    By default, the RPC service listens on localhost which means it can't be accessed from other machines. To make the RPC service available publicly, you need to bind it to a public IP or 0.0.0.0 (which means listening on all available network interfaces).

    You can do this by editing the config.toml file:

    sh
    sed -i 's#"tcp://127.0.0.1:26657"#"tcp://0.0.0.0:26657"#g' ~/.celestia-app/config/config.toml
    sed -i 's#"tcp://127.0.0.1:26657"#"tcp://0.0.0.0:26657"#g' ~/.celestia-app/config/config.toml

    This command replaces the localhost IP address with 0.0.0.0, making the RPC service listen on all available network interfaces.

    Note on external-address ​

    The external-address field in the configuration is used when your node is behind a NAT and you need to advertise a different address for peers to dial. Populating this field is not necessary for making the RPC endpoint public.

    sh
    EXTERNAL-ADDRESS=$(wget -qO- eth0.me)
 sed -i.bak -e "s/^external-address = ""/external-address = "$EXTERNAL-ADDRESS:26656"/" \
     $HOME/.celestia-app/config/config.toml
    EXTERNAL-ADDRESS=$(wget -qO- eth0.me)
 sed -i.bak -e "s/^external-address = ""/external-address = "$EXTERNAL-ADDRESS:26656"/" \
-    $HOME/.celestia-app/config/config.toml

    Restart the node ​

    After making these changes, restart celestia-appd to load the new configurations.

    Optional: Transaction indexer configuration options ​

    This section guides you on how to configure your config.toml file in celestia-app to select which transactions to index. Depending on the application's configuration, a node operator may decide which transactions to index.

    The available options are:

    1. null: This option disables indexing. If you don't need to query transactions, you can choose this option to save space.
    2. kv (default): This is the simplest indexer, backed by key-value storage (defaults to levelDB; see DBBackend). When kv is chosen, tx.height and tx.hash will always be indexed. This option is suitable for basic queries on transactions.
    3. psql: This indexer is backed by PostgreSQL. When psql is chosen, tx.height and tx.hash will always be indexed. This option is suitable for complex queries on transactions.

    An example to set the value to kv in config.toml is:

    toml
    indexer = "kv"
    indexer = "kv"

    Remember to restart celestia-appd after making changes to the configuration to load the new settings.

    Optional: Discard ABCI responses configuration ​

    This section will guide you on how to configure your config.toml file in celestia-app to manage the storage of ABCI responses. ABCI responses are the results of executing transactions and are used for /block_results RPC queries and to reindex events in the command-line tool.

    The discard_abci_responses option allows you to control whether these responses are persisted in the state store:

    • false (default): ABCI responses are stored in the state store. This ensures that ABCI responses are available for /block_results RPC queries and for reindexing events. However, it can consume a significant amount of disk space.
    • true: ABCI responses are not stored in the state store. This can save a considerable amount of disk space, but /block_results RPC queries and event reindexing will not be available.

    An example to set the value to false in config.toml is:

    toml
    discard_abci_responses = false
    discard_abci_responses = false

    Remember to restart celestia-appd after making changes to the configuration to load the new settings.

    FAQ ​

    +2/3 committed an invalid block: wrong Block.Header.Version ​

    If you encounter an error like:

    bash
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\nruntime/debug.Stack()\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\npanic({0x1b91180?, 0x400153b240?})\n\t/usr/local/go/src/runtime/panic.go:770 +0x124\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\n"
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\nruntime/debug.Stack()\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\npanic({0x1b91180?, 0x400153b240?})\n\t/usr/local/go/src/runtime/panic.go:770 +0x124\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\n"

    then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant --v2-upgrade-height for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a celestia-appd tendermint reset-state to reset your node and start syncing from the genesis block.

    - + $HOME/.celestia-app/config/config.toml

    Restart the node ​

    After making these changes, restart celestia-appd to load the new configurations.

    Optional: Transaction indexer configuration options ​

    This section guides you on how to configure your config.toml file in celestia-app to select which transactions to index. Depending on the application's configuration, a node operator may decide which transactions to index.

    The available options are:

    1. null: This option disables indexing. If you don't need to query transactions, you can choose this option to save space.
    2. kv (default): This is the simplest indexer, backed by key-value storage (defaults to levelDB; see DBBackend). When kv is chosen, tx.height and tx.hash will always be indexed. This option is suitable for basic queries on transactions.
    3. psql: This indexer is backed by PostgreSQL. When psql is chosen, tx.height and tx.hash will always be indexed. This option is suitable for complex queries on transactions.

    An example to set the value to kv in config.toml is:

    toml
    indexer = "kv"
    indexer = "kv"

    Remember to restart celestia-appd after making changes to the configuration to load the new settings.

    Optional: Discard ABCI responses configuration ​

    This section will guide you on how to configure your config.toml file in celestia-app to manage the storage of ABCI responses. ABCI responses are the results of executing transactions and are used for /block_results RPC queries and to reindex events in the command-line tool.

    The discard_abci_responses option allows you to control whether these responses are persisted in the state store:

    • false (default): ABCI responses are stored in the state store. This ensures that ABCI responses are available for /block_results RPC queries and for reindexing events. However, it can consume a significant amount of disk space.
    • true: ABCI responses are not stored in the state store. This can save a considerable amount of disk space, but /block_results RPC queries and event reindexing will not be available.

    An example to set the value to false in config.toml is:

    toml
    discard_abci_responses = false
    discard_abci_responses = false

    Remember to restart celestia-appd after making changes to the configuration to load the new settings.

    FAQ ​

    +2/3 committed an invalid block: wrong Block.Header.Version ​

    If you encounter an error like:

    bash
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\nruntime/debug.Stack()\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\npanic({0x1b91180?, 0x400153b240?})\n\t/usr/local/go/src/runtime/panic.go:770 +0x124\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\n"
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\nruntime/debug.Stack()\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\npanic({0x1b91180?, 0x400153b240?})\n\t/usr/local/go/src/runtime/panic.go:770 +0x124\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\n"

    then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant --v2-upgrade-height for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a celestia-appd tendermint reset-state to reset your node and start syncing from the genesis block.

    + \ No newline at end of file diff --git a/pr-1699/nodes/decide-node.html b/pr-1699/nodes/decide-node.html index bcba35b8bf..8f07c85a4b 100644 --- a/pr-1699/nodes/decide-node.html +++ b/pr-1699/nodes/decide-node.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    Deciding which node to run ​

    Now that you have installed the basic dependencies, you can start exploring which nodes to run!

    Beginner ​

    It is highly recommended if you are a beginner to get started with running a Data-Availability light node.

    In order to get started, you can proceed to the light node section.

    You can also play around with the Data Availability API in this tutorial for posting and retrieving data with a light node.

    Advanced ​

    If you are looking to run a consensus node, please follow the tutorial for running a consensus node.

    Note that running a validator means you must also run a bridge node, which is covered in this section.

    - +

    Deciding which node to run ​

    Now that you have installed the basic dependencies, you can start exploring which nodes to run!

    Beginner ​

    It is highly recommended if you are a beginner to get started with running a Data-Availability light node.

    In order to get started, you can proceed to the light node section.

    You can also play around with the Data Availability API in this tutorial for posting and retrieving data with a light node.

    Advanced ​

    If you are looking to run a consensus node, please follow the tutorial for running a consensus node.

    Note that running a validator means you must also run a bridge node, which is covered in this section.

    + \ No newline at end of file diff --git a/pr-1699/nodes/docker-images.html b/pr-1699/nodes/docker-images.html index 8e75071f7b..a46a24536c 100644 --- a/pr-1699/nodes/docker-images.html +++ b/pr-1699/nodes/docker-images.html @@ -14,7 +14,7 @@ - + @@ -41,7 +41,7 @@

    Appearance

    🐳 Docker setup ​

    This page has instructions to run celestia-node using Docker. If you are looking for instructions to run celestia-node using a binary, please refer to the celestia-node page.

    Using Docker is the easiest way to run celestia-node for most users. Docker is a containerization platform that allows you to run celestia-node in an isolated environment.

    This means that you can run celestia-node on your machine without having to worry about installing and configuring all of the dependencies required to run the node.

    If you would like to learn more about key management in Docker, visit the Docker and cel-key section.

    The easiest way to install Docker is to use the Docker Desktop installer or Ubuntu. You can follow the instructions for your operating system.

    Prerequisites ​

    Quick start ​

    1. Set the network you would like to run your node on:

      bash
      export NETWORK=celestia
      export NETWORK=celestia
      bash
      export NETWORK=mocha
      export NETWORK=mocha
      bash
      export NETWORK=arabica
      export NETWORK=arabica

    2. Set the node type

      bash
      export NODE_TYPE=light
      export NODE_TYPE=light
      bash
      export NODE_TYPE=bridge
      export NODE_TYPE=bridge
      bash
      export NODE_TYPE=full
      export NODE_TYPE=full

    3. Set an RPC endpoint for either Mainnet Beta, Mocha, or Arabica using the bare URL (without http or https):

      bash
      export RPC_URL=this-is-an-rpc-url.com
      export RPC_URL=this-is-an-rpc-url.com

    4. Run the image from the command line:

      bash
      docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \
+

    🐳 Docker setup ​

    This page has instructions to run celestia-node using Docker. If you are looking for instructions to run celestia-node using a binary, please refer to the celestia-node page.

    Using Docker is the easiest way to run celestia-node for most users. Docker is a containerization platform that allows you to run celestia-node in an isolated environment.

    This means that you can run celestia-node on your machine without having to worry about installing and configuring all of the dependencies required to run the node.

    If you would like to learn more about key management in Docker, visit the Docker and cel-key section.

    The easiest way to install Docker is to use the Docker Desktop installer or Ubuntu. You can follow the instructions for your operating system.

    Prerequisites ​

    Quick start ​

    1. Set the network you would like to run your node on:

      bash
      export NETWORK=celestia
      export NETWORK=celestia
      bash
      export NETWORK=mocha
      export NETWORK=mocha
      bash
      export NETWORK=arabica
      export NETWORK=arabica

    2. Set the node type

      bash
      export NODE_TYPE=light
      export NODE_TYPE=light
      bash
      export NODE_TYPE=bridge
      export NODE_TYPE=bridge
      bash
      export NODE_TYPE=full
      export NODE_TYPE=full

    3. Set an RPC endpoint for either Mainnet Beta, Mocha, or Arabica using the bare URL (without http or https):

      bash
      export RPC_URL=this-is-an-rpc-url.com
      export RPC_URL=this-is-an-rpc-url.com

    4. Run the image from the command line:

      bash
      docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \
     ghcr.io/celestiaorg/celestia-node:v0.15.0 \
     celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK
      docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \
     ghcr.io/celestiaorg/celestia-node:v0.15.0 \
@@ -55,11 +55,11 @@
     ghcr.io/celestiaorg/celestia-node:v0.16.0 \
     celestia $NODE_TYPE start --core.ip $RPC_URL --p2p.network $NETWORK

    Congratulations! You now have a celestia-node running!

    If you would like to run the node with custom flags, you can refer to the celestia-node tutorial page. Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

    Light node setup with persistent storage ​

    If you delete a container that you started above, all data will be lost. To avoid this, you can mount a volume to the container. This will allow you to persist data even after the container is deleted.

    First, you will need to create a directory on your host machine. This directory will be used to store the data for the container. Create a directory on your host machine and give it a name. For example, you can name it my-node-store:

    bash
    cd $HOME
 mkdir my-node-store
    cd $HOME
-mkdir my-node-store

    Now, you can mount this directory to the container. Before mounting a volume, you may need to set permissions for the user on the host machine by running:

    bash
    sudo chown 10001:10001 $HOME/my-node-store
    sudo chown 10001:10001 $HOME/my-node-store
    bash
    # you're good to go 😎
    # you're good to go 😎

    Initialize the node store and key ​

    In order to mount a volume to the container, you need to specify the path to the volume. When you run your container, you can specify the path to the volume using the --volume (or -v for short) flag. In this command, we'll create our key and initialize the node store, using the variables we set in the quick start section:

    bash
    # --volume == -v [local path]:[container path]
+mkdir my-node-store

    Now, you can mount this directory to the container. Before mounting a volume, you may need to set permissions for the user on the host machine by running:

    bash
    sudo chown 10001:10001 $HOME/my-node-store
    sudo chown 10001:10001 $HOME/my-node-store
    bash
    # you're good to go 😎
    # you're good to go 😎

    Initialize the node store and key ​

    In order to mount a volume to the container, you need to specify the path to the volume. When you run your container, you can specify the path to the volume using the --volume (or -v for short) flag. In this command, we'll create our key and initialize the node store, using the variables we set in the quick start section:

    bash
    # --volume == -v [local path]:[container path]
 docker run [args...] -v $HOME/my-node-store:/home/celestia \
     celestia $NODE_TYPE init [args...]
    # --volume == -v [local path]:[container path]
 docker run [args...] -v $HOME/my-node-store:/home/celestia \
-    celestia $NODE_TYPE init [args...]

    An example init command will look similar to below:

    bash
    docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \
+    celestia $NODE_TYPE init [args...]

    An example init command will look similar to below:

    bash
    docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \
     -v $HOME/my-node-store:/home/celestia \
     ghcr.io/celestiaorg/celestia-node:v0.15.0 \
     celestia light init --p2p.network $NETWORK
    docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \
@@ -81,7 +81,7 @@
 docker run [...args] -v $HOME/my-node-store:/home/celestia \
     celestia <node-type> start [...args]
    # --volume == -v [local path]:[container path]
 docker run [...args] -v $HOME/my-node-store:/home/celestia \
-    celestia <node-type> start [...args]

    A full start command will look similar to below.

    bash
    docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \
+    celestia <node-type> start [...args]

    A full start command will look similar to below.

    bash
    docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \
     -v $HOME/my-node-store:/home/celestia \
     ghcr.io/celestiaorg/celestia-node:v0.15.0 \
     celestia light start --core.ip $RPC_URL
    docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \
@@ -99,8 +99,8 @@
     celestia light start --core.ip $RPC_URL
    docker run -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK \
     -v $HOME/my-node-store:/home/celestia \
     ghcr.io/celestiaorg/celestia-node:v0.16.0 \
-    celestia light start --core.ip $RPC_URL

    Congratulations! You now have a node running with persistent storage.

    Video walkthrough ​

    2.5 minute version ​

    Troubleshooting ​

    For security purposes Celestia expects to interact with the your node's keys in a read-only manner. This is enforced using linux style permissions on the filesystem. Windows NTFS does not support these types of permissions. As a result the recommended path for Windows users to mount a persisted volume is to do so within WSL. You can find instructions for installing WSL.

    - + celestia light start --core.ip $RPC_URL

    Congratulations! You now have a node running with persistent storage.

    Video walkthrough ​

    2.5 minute version ​

    Troubleshooting ​

    For security purposes Celestia expects to interact with the your node's keys in a read-only manner. This is enforced using linux style permissions on the filesystem. Windows NTFS does not support these types of permissions. As a result the recommended path for Windows users to mount a persisted volume is to do so within WSL. You can find instructions for installing WSL.

    + \ No newline at end of file diff --git a/pr-1699/nodes/environment.html b/pr-1699/nodes/environment.html index a202784416..01a8c32f91 100644 --- a/pr-1699/nodes/environment.html +++ b/pr-1699/nodes/environment.html @@ -12,7 +12,7 @@ - + @@ -39,7 +39,7 @@

    Appearance

    Development environment ​

    This page will go over setting up your development environment to run Celestia software. This environment can be used for development, building binaries, and running nodes.

    Install dependencies ​

    1. If you are on Ubuntu, first update and upgrade your OS:

      bash
      sudo apt update && sudo apt upgrade -y
      sudo apt update && sudo apt upgrade -y
      bash
      sudo yum update
      sudo yum update

    2. Install essential packages that are necessary to execute many tasks like downloading files, compiling, and monitoring the node:

      bash
      sudo apt install curl tar wget aria2 clang pkg-config libssl-dev jq build-essential \
+

    Development environment ​

    This page will go over setting up your development environment to run Celestia software. This environment can be used for development, building binaries, and running nodes.

    Install dependencies ​

    1. If you are on Ubuntu, first update and upgrade your OS:

      bash
      sudo apt update && sudo apt upgrade -y
      sudo apt update && sudo apt upgrade -y
      bash
      sudo yum update
      sudo yum update

    2. Install essential packages that are necessary to execute many tasks like downloading files, compiling, and monitoring the node:

      bash
      sudo apt install curl tar wget aria2 clang pkg-config libssl-dev jq build-essential \
 git make ncdu -y
      sudo apt install curl tar wget aria2 clang pkg-config libssl-dev jq build-essential \
 git make ncdu -y
      bash
      sudo yum install curl tar wget aria2 clang pkg-config libssl-dev jq build-essential \
 git make ncdu -y
      sudo yum install curl tar wget aria2 clang pkg-config libssl-dev jq build-essential \
@@ -53,7 +53,7 @@
 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
 
 # then install wget & jq
-brew install wget && brew install jq

    Install Golang ​

    celestia-node is written in Golang so we must install Golang to build and run our node.

    1. Set the version for your desired network:

      bash
      ver="1.22.0"
      ver="1.22.0"
      bash
      ver="1.23.0"
      ver="1.23.0"
      bash
      ver="1.23.0"
      ver="1.23.0"

    2. Download and install Golang:

      bash
      cd $HOME
+brew install wget && brew install jq

    Install Golang ​

    celestia-node is written in Golang so we must install Golang to build and run our node.

    1. Set the version for your desired network:

      bash
      ver="1.22.0"
      ver="1.22.0"
      bash
      ver="1.23.0"
      ver="1.23.0"
      bash
      ver="1.23.0"
      ver="1.23.0"

    2. Download and install Golang:

      bash
      cd $HOME
 wget "https://golang.org/dl/go$ver.linux-amd64.tar.gz"
 sudo rm -rf /usr/local/go
 sudo tar -C /usr/local -xzf "go$ver.linux-amd64.tar.gz"
@@ -85,12 +85,12 @@
 wget "https://golang.org/dl/go$ver.darwin-amd64.tar.gz"
 sudo rm -rf /usr/local/go
 sudo tar -C /usr/local -xzf "go$ver.darwin-amd64.tar.gz"
-rm "go$ver.darwin-amd64.tar.gz"

    3. Add your /usr/local/go/bin directory to your $PATH if you have not already:

      bash
      echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.bash_profile
+rm "go$ver.darwin-amd64.tar.gz"

    4. Add your /usr/local/go/bin directory to your $PATH if you have not already:

      bash
      echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.bash_profile
 source $HOME/.bash_profile
      echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.bash_profile
 source $HOME/.bash_profile
      bash
      echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.zshrc
 source $HOME/.zshrc
      echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.zshrc
-source $HOME/.zshrc

      TIP

      Use echo $SHELL to figure out what type of shell you are using!

    5. To verify that the correct version of Go was installed correctly run:

      bash
      go version
      go version

    The output will show the version installed.

    - +source $HOME/.zshrc

    TIP

    Use echo $SHELL to figure out what type of shell you are using!

  • To verify that the correct version of Go was installed correctly run:

    bash
    go version
    go version

    • The output will show the version installed.

    + \ No newline at end of file diff --git a/pr-1699/nodes/full-storage-node.html b/pr-1699/nodes/full-storage-node.html index ca10da6e56..9f06c20e90 100644 --- a/pr-1699/nodes/full-storage-node.html +++ b/pr-1699/nodes/full-storage-node.html @@ -11,7 +11,7 @@ - + @@ -38,7 +38,7 @@

    Appearance

    Setting up a Celestia full storage Node ​

    This tutorial will guide you through setting up a Celestia full storage node, which is a celestia-node that doesn't connect to celestia-app (hence not a consensus node), but stores all the data.

    Overview of full storage nodes ​

    Full storage nodes are Celestia nodes that store all the data. Full storage nodes send block shares, headers, and fraud proofs to light nodes. The light nodes gossip headers, fraud proofs, and sometimes block shares, between one another.

    Full storage node

    Hardware requirements ​

    The following hardware minimum requirements are recommended for running the full storage node:

    • Memory: 16 GB RAM (minimum)
    • CPU: 6 cores
    • Disk: 10 TB SSD Storage
    • Bandwidth: 1 Gbps for Download/1 Gbps for Upload

    Setting up your full storage node ​

    The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.

    Setup the dependencies ​

    You can follow the tutorial for setting up your dependencies

    Install celestia-node ​

    You can follow the tutorial for installing celestia-node

    Run the full storage node ​

    Initialize the full storage node ​

    Run the following command:

    sh
    celestia full init
    celestia full init
    sh
    celestia full init --p2p.network mocha
    celestia full init --p2p.network mocha
    sh
    celestia full init --p2p.network arabica
    celestia full init --p2p.network arabica

    Start the full storage node ​

    Start the full storage node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):

    In order for access to the ability to get/submit state-related information, such as the ability to submit PayForBlob transactions, or query for the node's account balance, a gRPC endpoint of a validator (core) node must be passed as directed below.

    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

    sh
    celestia full start --core.ip <URI>
    celestia full start --core.ip <URI>

    Using an RPC of your own, or one from the list on the Mocha testnet page or list on the Arabica devnet page, start your node.

    Connecting to a core endpoint with --core.ip string provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).

    You can create your key for your node by following the cel-key instructions

    Once you start the full storage node, a wallet key will be generated for you. You will need to fund that address with testnet tokens to pay for PayForBlob transactions. You can find the address by running the following command:

    sh
    ./cel-key list --node.type full --keyring-backend test --p2p.network <network>
    ./cel-key list --node.type full --keyring-backend test --p2p.network <network>

    TIP

    You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information

    You can get testnet tokens from:

    NOTE

    If you are running a full-storage node for your sovereign rollup, it is highly recommended to request Arabica devnet tokens as Arabica has the latest changes that can be used to test for developing your sovereign rollup. You can still use Mocha testnet as well, it is just mostly used for validator operations.

    Optional: run the full storage node with a custom key ​

    In order to run a full storage node using a custom key:

    1. The custom key must exist inside the celestia full storage node directory at the correct path (default: ~/.celestia-full/keys/keyring-test)
    2. The name of the custom key must be passed upon start, like so:
    sh
    celestia full start --core.ip <URI> \
+

    Setting up a Celestia full storage Node ​

    This tutorial will guide you through setting up a Celestia full storage node, which is a celestia-node that doesn't connect to celestia-app (hence not a consensus node), but stores all the data.

    Overview of full storage nodes ​

    Full storage nodes are Celestia nodes that store all the data. Full storage nodes send block shares, headers, and fraud proofs to light nodes. The light nodes gossip headers, fraud proofs, and sometimes block shares, between one another.

    Full storage node

    Hardware requirements ​

    The following hardware minimum requirements are recommended for running the full storage node:

    • Memory: 16 GB RAM (minimum)
    • CPU: 6 cores
    • Disk: 10 TB SSD Storage
    • Bandwidth: 1 Gbps for Download/1 Gbps for Upload

    Setting up your full storage node ​

    The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.

    Setup the dependencies ​

    You can follow the tutorial for setting up your dependencies

    Install celestia-node ​

    You can follow the tutorial for installing celestia-node

    Run the full storage node ​

    Initialize the full storage node ​

    Run the following command:

    sh
    celestia full init
    celestia full init
    sh
    celestia full init --p2p.network mocha
    celestia full init --p2p.network mocha
    sh
    celestia full init --p2p.network arabica
    celestia full init --p2p.network arabica

    Start the full storage node ​

    Start the full storage node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):

    In order for access to the ability to get/submit state-related information, such as the ability to submit PayForBlob transactions, or query for the node's account balance, a gRPC endpoint of a validator (core) node must be passed as directed below.

    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

    sh
    celestia full start --core.ip <URI>
    celestia full start --core.ip <URI>

    Using an RPC of your own, or one from the list on the Mocha testnet page or list on the Arabica devnet page, start your node.

    Connecting to a core endpoint with --core.ip string provides the light node with access to state queries (reading balances, submitting transactions, and other state-related queries).

    You can create your key for your node by following the cel-key instructions

    Once you start the full storage node, a wallet key will be generated for you. You will need to fund that address with testnet tokens to pay for PayForBlob transactions. You can find the address by running the following command:

    sh
    ./cel-key list --node.type full --keyring-backend test --p2p.network <network>
    ./cel-key list --node.type full --keyring-backend test --p2p.network <network>

    TIP

    You do not need to declare a network for Mainnet Beta. Refer to the chain ID section on the troubleshooting page for more information

    You can get testnet tokens from:

    NOTE

    If you are running a full-storage node for your sovereign rollup, it is highly recommended to request Arabica devnet tokens as Arabica has the latest changes that can be used to test for developing your sovereign rollup. You can still use Mocha testnet as well, it is just mostly used for validator operations.

    Optional: run the full storage node with a custom key ​

    In order to run a full storage node using a custom key:

    1. The custom key must exist inside the celestia full storage node directory at the correct path (default: ~/.celestia-full/keys/keyring-test)
    2. The name of the custom key must be passed upon start, like so:
    sh
    celestia full start --core.ip <URI> \
   --keyring.keyname <name-of-custom-key> \
    celestia full start --core.ip <URI> \
   --keyring.keyname <name-of-custom-key> \
    sh
    celestia full start --core.ip <URI> \
   --keyring.keyname <name-of-custom-key> \
@@ -48,8 +48,8 @@
   --keyring.keyname <name-of-custom-key> \
   --p2p.network arabica
    celestia full start --core.ip <URI> \
   --keyring.keyname <name-of-custom-key> \
-  --p2p.network arabica

    Optional: Migrate node id to another server ​

    To migrate a full storage node ID:

    1. You need to back up two files located in the celestia-full node directory at the correct path (default: ~/.celestia-full/keys).
    2. Upload the files to the new server and start the node.

    Optional: start the full storage node with SystemD ​

    If you would like to run the full storage node as a background process, follow the SystemD tutorial.

    With that, you are now running a Celestia full storage node.

    Stop the full storage node ​

    In order to gracefully stop the full storage node, use Control + C in the terminal window where the node is running. Be sure to only do this once as the shutdown will not be instantaneous.

    - + --p2p.network arabica

    Optional: Migrate node id to another server ​

    To migrate a full storage node ID:

    1. You need to back up two files located in the celestia-full node directory at the correct path (default: ~/.celestia-full/keys).
    2. Upload the files to the new server and start the node.

    Optional: start the full storage node with SystemD ​

    If you would like to run the full storage node as a background process, follow the SystemD tutorial.

    With that, you are now running a Celestia full storage node.

    Stop the full storage node ​

    In order to gracefully stop the full storage node, use Control + C in the terminal window where the node is running. Be sure to only do this once as the shutdown will not be instantaneous.

    + \ No newline at end of file diff --git a/pr-1699/nodes/hardfork-process.html b/pr-1699/nodes/hardfork-process.html index 3f5d06e75e..7a4fcd27de 100644 --- a/pr-1699/nodes/hardfork-process.html +++ b/pr-1699/nodes/hardfork-process.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    Celestia hardfork process ​

    Blockchain networks often times need to upgrade with new features which require coordination work among the validators prior to activating the upgrades.

    This process is called a hardfork or a network upgrade. In those events, the Celestia Labs team will be coordinating with the validators on what they need to do in order to be ready for an upcoming hardfork.

    Hardforks are not backward-compatible with older versions of the network software which is why it is important that validators upgrade their software to continue validating on the network after the network upgrades.

    General process ​

    The general process can be broken down into several components:

    • Hardfork specifications and features (defined by description of features and code implementation of those features).
    • Binary used to add those features (a new binary release with those features will be provided by Celestia team in order for validators to upgrade their nodes to the new binary).
    • A block number for when the network upgrades (even if validators upgrade their binary to be hardfork ready, the network upgrade does not happen right away, but some short time in the future at a specific block number).
    • Testing of the features (happens on testnets first prior to activating on mainnet in order to ensure the network can upgrade securely).

    The two testnets where hardforks are deployed are:

    Lemongrass hardfork ​

    The Lemongrass hardfork is the first consensus layer breaking change since Celestia's Mainnet Beta genesis block. The Lemongrass hardfork includes all of the CIPs listed in CIP-17. The Lemongrass hardfork will be executed on Arabica, then Mocha, then Mainnet Beta. The hardfork will take place at an "upgrade height" that will be coordinated offline on a per-network basis. The upgrade heights will be announced in advance (see Network upgrades) to give node operators time to download and start a compatible binary prior to the upgrade height.

    • If you are a consensus node or validator operator: you will need to download and run a celestia-app binary >= v2.0.0 prior to the --v2-upgrade-height to remain on the canonical chain. You do not need to use a tool like cosmovisor to upgrade the binary at the upgrade height.
    • If you are a DA node operator, you will need to download and run a compatible celestia-node binary >= v0.16.0-rc0 prior to the upgrade height.
    NetworkChain IDDate and approximate time--v2-upgrade-height
    Arabicaarabica-112024/08/19 @ 14:00 UTC1751707
    Mochamocha-42024/08/28 @ 14:00 UTC2585031
    Mainnet Betacelestia2024/09/18 @ 14:00 UTC2371495
    - +

    Celestia hardfork process ​

    Blockchain networks often times need to upgrade with new features which require coordination work among the validators prior to activating the upgrades.

    This process is called a hardfork or a network upgrade. In those events, the Celestia Labs team will be coordinating with the validators on what they need to do in order to be ready for an upcoming hardfork.

    Hardforks are not backward-compatible with older versions of the network software which is why it is important that validators upgrade their software to continue validating on the network after the network upgrades.

    General process ​

    The general process can be broken down into several components:

    • Hardfork specifications and features (defined by description of features and code implementation of those features).
    • Binary used to add those features (a new binary release with those features will be provided by Celestia team in order for validators to upgrade their nodes to the new binary).
    • A block number for when the network upgrades (even if validators upgrade their binary to be hardfork ready, the network upgrade does not happen right away, but some short time in the future at a specific block number).
    • Testing of the features (happens on testnets first prior to activating on mainnet in order to ensure the network can upgrade securely).

    The two testnets where hardforks are deployed are:

    Lemongrass hardfork ​

    The Lemongrass hardfork is the first consensus layer breaking change since Celestia's Mainnet Beta genesis block. The Lemongrass hardfork includes all of the CIPs listed in CIP-17. The Lemongrass hardfork will be executed on Arabica, then Mocha, then Mainnet Beta. The hardfork will take place at an "upgrade height" that will be coordinated offline on a per-network basis. The upgrade heights will be announced in advance (see Network upgrades) to give node operators time to download and start a compatible binary prior to the upgrade height.

    • If you are a consensus node or validator operator: you will need to download and run a celestia-app binary >= v2.0.0 prior to the --v2-upgrade-height to remain on the canonical chain. You do not need to use a tool like cosmovisor to upgrade the binary at the upgrade height.
    • If you are a DA node operator, you will need to download and run a compatible celestia-node binary >= v0.16.0-rc0 prior to the upgrade height.
    NetworkChain IDDate and approximate time--v2-upgrade-height
    Arabicaarabica-112024/08/19 @ 14:00 UTC1751707
    Mochamocha-42024/08/28 @ 14:00 UTC2585031
    Mainnet Betacelestia2024/09/18 @ 14:00 UTC2371495
    + \ No newline at end of file diff --git a/pr-1699/nodes/ibc-relayer.html b/pr-1699/nodes/ibc-relayer.html index 2d679acf06..41c27118f3 100644 --- a/pr-1699/nodes/ibc-relayer.html +++ b/pr-1699/nodes/ibc-relayer.html @@ -11,7 +11,7 @@ - + @@ -492,8 +492,8 @@ policy = 'allow' list = [ ['transfer', 'channel-3108'], # mocha-4 -]

    Start the relayer ​

    Start the relayer via hermes start

    Transfer ​

    The Celestia state machine is built with the IBC transfer module, allowing for the native Celestia token to be transferred to any other IBC enabled chain. Transfer can be initialized through the celestia-appd CLI. Information can be found via the help label as follows:

    bash
    celestia-appd tx ibc-transfer transfer --help
    celestia-appd tx ibc-transfer transfer --help

    Token filter ​

    The transfer module uses a token filter middleware which serves to prevent non-native Celestia tokens from being on Celestia. If a user is to try to send a token from another chain across, it will be simply rejected and the token returned back to the user.

    - +]

    Start the relayer ​

    Start the relayer via hermes start

    Transfer ​

    The Celestia state machine is built with the IBC transfer module, allowing for the native Celestia token to be transferred to any other IBC enabled chain. Transfer can be initialized through the celestia-appd CLI. Information can be found via the help label as follows:

    bash
    celestia-appd tx ibc-transfer transfer --help
    celestia-appd tx ibc-transfer transfer --help

    Token filter ​

    The transfer module uses a token filter middleware which serves to prevent non-native Celestia tokens from being on Celestia. If a user is to try to send a token from another chain across, it will be simply rejected and the token returned back to the user.

    + \ No newline at end of file diff --git a/pr-1699/nodes/instantiate-testnet.html b/pr-1699/nodes/instantiate-testnet.html index 969937f793..102abb7bfe 100644 --- a/pr-1699/nodes/instantiate-testnet.html +++ b/pr-1699/nodes/instantiate-testnet.html @@ -11,7 +11,7 @@ - + @@ -58,8 +58,8 @@ NODE_ID=$(celestia-appd tendermint show-node-id) PORT_NUMBER=26656

    Note that the default port is 26656

    Now you can run the following command to output your validator node address:

    sh
    PEER="$NODE_ID@$IP_ADDRESS:$PORT_NUMBER"
 echo $PEER
    PEER="$NODE_ID@$IP_ADDRESS:$PORT_NUMBER"
-echo $PEER

    The output is your validator node address which you can share with other validators so they can peer with you.

    Instantiate the network ​

    You can start your node by running the following command:

    sh
    celestia-appd start
    celestia-appd start

    TIP

    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

    Now you have a new Celestia testnet to play around with!

    - +echo $PEER

    The output is your validator node address which you can share with other validators so they can peer with you.

    Instantiate the network ​

    You can start your node by running the following command:

    sh
    celestia-appd start
    celestia-appd start

    TIP

    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

    Now you have a new Celestia testnet to play around with!

    + \ No newline at end of file diff --git a/pr-1699/nodes/light-node.html b/pr-1699/nodes/light-node.html index 562825552d..f813b4ec05 100644 --- a/pr-1699/nodes/light-node.html +++ b/pr-1699/nodes/light-node.html @@ -11,7 +11,7 @@ - + @@ -38,9 +38,9 @@

    Appearance

    Setting up a Celestia light node ​

    This tutorial will guide you through setting up a Celestia light node, which will allow you to perform data availability sampling (DAS) on Celestia's data availability (DA) network.

    Overview of light nodes ​

    Light nodes ensure data availability. This is the most common way to interact with Celestia networks.

    light-node

    Light nodes have the following behavior:

    1. They listen for ExtendedHeaders, i.e. wrapped “raw” headers, that notify Celestia nodes of new block headers and relevant DA metadata.
    2. They perform DAS on the received headers

    Hardware requirements ​

    The following minimum hardware requirements are recommended for running a light node:

    • Memory: 500 MB RAM (minimum)
    • CPU: Single Core
    • Disk: 100 GB SSD Storage
    • Bandwidth: 56 Kbps for Download/56 Kbps for Upload

    Setting up your light node ​

    This tutorial was performed on an Ubuntu Linux 20.04 (LTS) x64 instance machine.

    Set up dependencies on the setting up environment page.

    Install celestia-node ​

    Install the celestia binary by building and installing celestia-node.

    Initialize the light node ​

    Run the following command:

    sh
    celestia light init
    celestia light init
    sh
    celestia light init --p2p.network mocha
    celestia light init --p2p.network mocha
    sh
    celestia light init --p2p.network arabica
    celestia light init --p2p.network arabica

    The output in your terminal will show the location of your node store and config. It will also show confirmation that the node store has been initialized.

    Start the light node ​

    Start the light node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):

    In order for access to the ability to get and submit state-related information, such as the ability to submit PayForBlobs transactions, or query for the node's account balance, a gRPC endpoint of a validator (core) node must be passed as directed below.

    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

    sh
    celestia light start --core.ip rpc.celestia.pops.one --p2p.network celestia
    celestia light start --core.ip rpc.celestia.pops.one --p2p.network celestia
    sh
    celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
    celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
    sh
    celestia light start --core.ip validator-1.celestia-arabica-11.com --p2p.network arabica
    celestia light start --core.ip validator-1.celestia-arabica-11.com --p2p.network arabica

    Tip: you can replace the core.ip with a consensus node RPC endpoint from mainnet, mocha, or arabica.

    Keys and wallets ​

    You can create your key for your node by running the following command with the cel-key utility in the celestia-node directory:

    sh
    ./cel-key add <key-name> --keyring-backend test \
+

    Setting up a Celestia light node ​

    This tutorial will guide you through setting up a Celestia light node, which will allow you to perform data availability sampling (DAS) on Celestia's data availability (DA) network.

    Overview of light nodes ​

    Light nodes ensure data availability. This is the most common way to interact with Celestia networks.

    light-node

    Light nodes have the following behavior:

    1. They listen for ExtendedHeaders, i.e. wrapped “raw” headers, that notify Celestia nodes of new block headers and relevant DA metadata.
    2. They perform DAS on the received headers

    Hardware requirements ​

    The following minimum hardware requirements are recommended for running a light node:

    • Memory: 500 MB RAM (minimum)
    • CPU: Single Core
    • Disk: 100 GB SSD Storage
    • Bandwidth: 56 Kbps for Download/56 Kbps for Upload

    Setting up your light node ​

    This tutorial was performed on an Ubuntu Linux 20.04 (LTS) x64 instance machine.

    Set up dependencies on the setting up environment page.

    Install celestia-node ​

    Install the celestia binary by building and installing celestia-node.

    Initialize the light node ​

    Run the following command:

    sh
    celestia light init
    celestia light init
    sh
    celestia light init --p2p.network mocha
    celestia light init --p2p.network mocha
    sh
    celestia light init --p2p.network arabica
    celestia light init --p2p.network arabica

    The output in your terminal will show the location of your node store and config. It will also show confirmation that the node store has been initialized.

    Start the light node ​

    Start the light node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):

    In order for access to the ability to get and submit state-related information, such as the ability to submit PayForBlobs transactions, or query for the node's account balance, a gRPC endpoint of a validator (core) node must be passed as directed below.

    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

    sh
    celestia light start --core.ip rpc.celestia.pops.one --p2p.network celestia
    celestia light start --core.ip rpc.celestia.pops.one --p2p.network celestia
    sh
    celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
    celestia light start --core.ip rpc-mocha.pops.one --p2p.network mocha
    sh
    celestia light start --core.ip validator-1.celestia-arabica-11.com --p2p.network arabica
    celestia light start --core.ip validator-1.celestia-arabica-11.com --p2p.network arabica

    Tip: you can replace the core.ip with a consensus node RPC endpoint from mainnet, mocha, or arabica.

    Keys and wallets ​

    You can create your key for your node by running the following command with the cel-key utility in the celestia-node directory:

    sh
    ./cel-key add <key-name> --keyring-backend test \
     --node.type light --p2p.network <network>
    ./cel-key add <key-name> --keyring-backend test \
-    --node.type light --p2p.network <network>

    You can start your light node with the key created above by running the following command:

    sh
    celestia light start --keyring.keyname my_celes_key \
+    --node.type light --p2p.network <network>

    You can start your light node with the key created above by running the following command:

    sh
    celestia light start --keyring.keyname my_celes_key \
     --core.ip consensus.lunaroasis.net
    celestia light start --keyring.keyname my_celes_key \
     --core.ip consensus.lunaroasis.net
    sh
    celestia light start --keyring.keyname my_celes_key \
     --core.ip rpc-mocha.pops.one --p2p.network mocha
    celestia light start --keyring.keyname my_celes_key \
@@ -50,7 +50,7 @@
     --core.ip validator-1.celestia-arabica-11.com \
     --p2p.network arabica

    Once you start the light node, a wallet key will be generated for you. You will need to fund that address with testnet tokens to pay for PayForBlob transactions.

    You can find the address using the RPC CLI or by running the following command in the celestia-node directory:

    sh
    ./cel-key list --node.type light --keyring-backend test \
     --p2p.network <network>
    ./cel-key list --node.type light --keyring-backend test \
-    --p2p.network <network>

    Testnet tokens ​

    You have two networks to get testnet tokens from:

    You can request funds to your wallet address using the following command in Discord:

    console
    $request <CELESTIA-ADDRESS>
    $request <CELESTIA-ADDRESS>

    Where <CELESTIA-ADDRESS> is the celestia1****** address generated when you created the wallet.

    Optional: run the light node with a custom key ​

    In order to run a light node using a custom key:

    1. The custom key must exist inside the celestia light node directory at the correct path (default: ~/.celestia-light/keys/keyring-test)
    2. The name of the custom key must be passed upon start, like so:
    sh
    celestia light start --core.ip <URI> \
+    --p2p.network <network>

    Testnet tokens ​

    You have two networks to get testnet tokens from:

    You can request funds to your wallet address using the following command in Discord:

    console
    $request <CELESTIA-ADDRESS>
    $request <CELESTIA-ADDRESS>

    Where <CELESTIA-ADDRESS> is the celestia1****** address generated when you created the wallet.

    Optional: run the light node with a custom key ​

    In order to run a light node using a custom key:

    1. The custom key must exist inside the celestia light node directory at the correct path (default: ~/.celestia-light/keys/keyring-test)
    2. The name of the custom key must be passed upon start, like so:
    sh
    celestia light start --core.ip <URI> \
     --keyring.keyname <name-of-custom-key> \
    celestia light start --core.ip <URI> \
     --keyring.keyname <name-of-custom-key> \
    sh
    celestia light start --core.ip <URI> \
     --keyring.keyname <name-of-custom-key> \
@@ -60,8 +60,8 @@
     --keyring.keyname <name-of-custom-key> \
     --p2p.network mocha
    celestia light start --core.ip <URI> \
     --keyring.keyname <name-of-custom-key> \
-    --p2p.network mocha

    Optional: Migrate node id to another server ​

    To migrate a light node ID:

    1. You need to back up two files located in the celestia-light node directory at the correct path (default: ~/.celestia-light/keys).
    2. Upload the files to the new server and start the node.

    Optional: start light node with SystemD ​

    Follow the tutorial on setting up the light node as a background process with SystemD.

    Data availability sampling ​

    With your light node running, you can check out this tutorial on submitting PayForBlob transactions.

    - + --p2p.network mocha

    Optional: Migrate node id to another server ​

    To migrate a light node ID:

    1. You need to back up two files located in the celestia-light node directory at the correct path (default: ~/.celestia-light/keys).
    2. Upload the files to the new server and start the node.

    Optional: start light node with SystemD ​

    Follow the tutorial on setting up the light node as a background process with SystemD.

    Data availability sampling ​

    With your light node running, you can check out this tutorial on submitting PayForBlob transactions.

    + \ No newline at end of file diff --git a/pr-1699/nodes/mainnet.html b/pr-1699/nodes/mainnet.html index 5b9735876b..d9a27d8ee5 100644 --- a/pr-1699/nodes/mainnet.html +++ b/pr-1699/nodes/mainnet.html @@ -14,7 +14,7 @@ - + @@ -41,8 +41,8 @@

    Appearance

    Mainnet Beta ​

    Mainnet Beta

    Welcome to the guide for Celestia’s Mainnet Beta, the production network that marks the pinnacle of Celestia’s evolution since its inception in 2019. This network is where all components of the Celestia ecosystem come to life in a real-world environment.

    Mainnet Beta is the culmination of rigorous community testing, upgrades, and feedback. It serves as the platform for deploying mainnet rollups and applications.

    Network stability and upgrades ​

    Mainnet Beta is a stable network, but will still receive updates and improvements. Any changes or upgrades will be coordinated with node operators and the broader Celestia community to ensure seamless integration and minimal service interruptions.

    As we step into unexplored territories with groundbreaking technologies like data availability sampling, it's crucial to remember that Mainnet Beta remains experimental at this stage. While the network is live and functional, users may encounter occasional instability or reduced performance.

    Network details ​

    DetailValue
    Chain IDcelestia
    Genesis hash6BE39EFD10BA412A9DB5288488303F5DD32CF386707A5BEF33617F4C43301872
    Genesis file https://github.com/celestiaorg/networks/blob/master/celestia/genesis.json
    Peers file https://github.com/celestiaorg/networks/blob/master/celestia/peers.txt
    Validators 100

    Software version numbers ​

    SoftwareVersion
    celestia-nodev0.15.0
    celestia-appv1.13.0

    Network parameters ​

    Full network parameters, such as max bytes, can be found in the celestia-app specifications.

    CIP-13 has been drafted to create a living document for these parameters as a part of the CIP process.

    Maximum bytes ​

    There is a hard limit on the total blob size in a transaction, which is determined by the effective maximum square size. Given that the current governance maximum square size is 64, the total blob size in a transaction must be slightly less than ~2 MiB, or 1,973,786 bytes to be exact.

    The following provides an approximation of the maximum block size:

    • The maximum square size is 64x64, which gives us 4096 shares.
    • One share is reserved for the PFB transaction, leaving us with 4095 shares.
    • The first sparse share has 478 bytes available, and the remaining sparse shares have 482 bytes each.

    This can be calculated as follows:

    Total Bytes=(1×478bytes)+(4094×482bytes)=1,973,786bytes

    Please note that there isn't a precise upper bound on the maximum total blob size. It depends on several factors:

    • The maximum square size, which is determined by a governance parameter and a versioned constant.
    • The maximum bytes in a block, which is determined by a governance parameter and a hard-coded constant in CometBFT.
    • The number of shares occupied by the PFB transaction share.

    These factors can cause the maximum total blob size that can be included in one block to vary.

    See the code in celestia-app and celestia-node.

    Integrations ​

    This guide contains the relevant sections for how to connect to Mainnet Beta, depending on the type of node you are running. Your best approach to participating is to first determine which node you would like to run. Each node’s guide will link to the relevant network in order to show you how to connect to them. Learn about the different endpoint types in the Cosmos SDK documentation.

    Here is a list of options of the types of nodes you can run in order to participate in Mainnet Beta:

    Production RPC endpoints ​

    These RPC providers are meant to be used in production environments.

    ProviderURL
    NewMetrichttps://app.newmetric.xyz/start
    NumiaFor RPC access: https://docs.numia.xyz/overview/rpc-api-access
    NumiaFor data warehouse access: https://docs.numia.xyz/overview/sql-access/chains/celestia
    Grovehttps://www.grove.city/

    WARNING

    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs or your own node.

    Consensus nodes ​

    Community consensus RPC endpoints ​

    WARNING

    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs.

    • public-celestia-rpc.numia.xyz
    • celestia-rpc.mesa.newmetric.xyz
    • rpc.celestia.pops.one
    • rpc.lunaroasis.net
    • rpc.celestia.nodestake.top
    • celestia-rpc.brightlystake.com
    • celestia-rpc.spidey.services
    • rpc-celestia.contributiondao.com
    • celestia.rpc.stakin-nodes.com
    • celestia.cumulo.org.es
    • rpc-celestia.mzonder.com
    • rpc-celestia-01.stakeflow.io
    • rpc-celestia.alphab.ai
    • rpc-celestia-full.avril14th.org
    • celestia-rpc.easy2stake.com
    • celestia.rpc.kjnodes.com
    • celestia-rpc.0xcryptovestor.com
    • rpc-celestia-mainnet.trusted-point.com
    • celestia.rpc.archives.validao.xyz
    • rpc-archive.celestia.bitszn.com
    • celestia-rpc.f5nodes.com
    • celestia-rpc.chainode.tech:33373
    • rpc-celestia.staker.space
    • celestia-rpc.noders.services
    • celestia.moonli.me
    • celestia-mainnet-rpc.itrocket.net:443
    • rpc.celestia.mainnet.dteam.tech:443

    Community API endpoints ​

    • public-celestia-lcd.numia.xyz
    • celestia-rest.mesa.newmetric.xyz
    • api.celestia.pops.one
    • api.lunaroasis.net
    • api.celestia.nodestake.top
    • celestia-rpc.brightlystake.com/api
    • celestia-api.spidey.services
    • api-celestia.contributiondao.com
    • celestia.rest.stakin-nodes.com
    • celestia.api.cumulo.org.es
    • api-celestia.mzonder.com
    • api-celestia-01.stakeflow.io
    • api-celestia.alphab.ai
    • api-celestia-full.avril14th.org
    • celestia-lcd.easy2stake.com
    • celestia.api.kjnodes.com
    • api-celestia-mainnet.trusted-point.com
    • celestia.rest.archives.validao.xyz
    • api-archive.celestia.bitszn.com
    • celestia-api.f5nodes.com
    • celestia-api.chainode.tech
    • api-celestia.staker.space
    • celestia-api.noders.services
    • celestia.moonli.me/api
    • celestia-mainnet-api.itrocket.net:443
    • api.celestia.mainnet.dteam.tech:443

    Community gRPC endpoints ​

    • public-celestia-grpc.numia.xyz
    • celestia-grpc.mesa.newmetric.xyz
    • grpc.celestia.pops.one
    • grpc.lunaroasis.net:443
    • grpc.celestia.nodestake.top
    • celestia-rpc.brightlystake.com:9090
    • celestia-grpc.spidey.services
    • grpc-celestia.contributiondao.com
    • celestia.grpc.stakin-nodes.com:443
    • celestia.grpc.cumulo.org.es:443
    • grpc-celestia.mzonder.com:443
    • grpc-celestia-01.stakeflow.io:15002
    • rpc-celestia.alphab.ai:9090
    • grpc-celestia-full.avril14th.org
    • celestia.grpc.kjnodes.com:443
    • grpc-celestia-mainnet.trusted-point.com:9095
    • celestia.grpc.archives.validao.xyz:9090
    • gprc-archive.celestia.bitszn.com
    • celestia-grpc.f5nodes.com:9390
    • celestia-grpc.chainode.tech:443
    • grpc-celestia.staker.space
    • celestia-grpc.noders.services:11090
    • celestia-mainnet-grpc.itrocket.net:443
    • grpc.celestia.mainnet.dteam.tech:28090

    Community WebSocket endpoints ​

    • wss://celestia-ws.chainode.tech:33373/websocket
    • wss://celestia-mainnet-ws.itrocket.net:443/websocket
    • wss://rpc.celestia.mainnet.dteam.tech:443/websocket

    Data availability nodes ​

    Community Data availability (DA) RPC endpoints for bridge node sync ​

    These RPC endpoints allow bridge nodes to sync blocks from the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default RPC port at 26657 to their respective DA node.

    Community Data availability (DA) gRPC endpoints for state access ​

    These gRPC endpoints for DA nodes provide state access for querying the chain’s state and broadcasting transactions (balances, blobs, etc.) to the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default gRPC port at 9090 to their respective DA node.

    TIP

    bash
    celestia <da_type> start --core.ip <url> -–core.grpc.port <port>
    celestia <da_type> start --core.ip <url> -–core.grpc.port <port>

    Bridge nodes

    Not all RPC endpoints guarantee the full block history. Find an archive endpoint on the community dashboard or run your own consensus node with no pruning for your bridge node.

    RPCs for DA nodes to initialise or start your celestia-node to Mainnet Beta with:

    • public-celestia-consensus.numia.xyz
      • gRPC: port 9090
      • RPC: port 26657
    • celestia-consensus.mesa.newmetric.xyz
      • gRPC: port 9090
      • RPC: port 26657
    • rpc.celestia.pops.one
      • gRPC: port 9090
      • RPC: port 26657
    • consensus.lunaroasis.net
      • gRPC: port 9090
      • RPC: port 26657
    • rpc-celestia.alphab.ai
      • gRPC: port 9090
      • RPC: port 26657
    • celestia-mainnet-consensus.itrocket.net
      • gRPC: port 9090
      • RPC: port 26657
    • rpc.celestia.mainnet.dteam.tech
      • gRPC: port 28090
      • RPC: 28657
    • celestia-consensus-mainnet.noders.services
      • gRPC: port 9080
      • RPC: port 26557

    DA full and light nodes might have troubles connecting to the networks, so you can check out this Grafana dashboard to see health/uptime status of DA bootstrappers (now celestia network only).

    You can find the status of these endpoints.

    Archival DA RPC endpoints ​

    By default, light nodes prune recent data to save on storage space. Archival data availability (DA) nodes store the entire history of the chain without pruning any data so all data available data is retrievable. You can read more about light vs archival nodes.

    Grove archival endpoints ​

    You can provision your own Celestia Archival endpoint on Grove. Learn more about Celestia on Grove, or find the fully supported spec.

    There is a sandbox you can leverage for testing straight in your browser:

    grove-sandbox

    Explorers ​

    There are multiple explorers you can use for Mainnet Beta:

    Analytics ​

    The following websites provide analytics for Celestia:

    Network upgrades ​

    There are a few ways to stay informed about network upgrades on Mainnet Beta:

    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.

    - +

    Mainnet Beta ​

    Mainnet Beta

    Welcome to the guide for Celestia’s Mainnet Beta, the production network that marks the pinnacle of Celestia’s evolution since its inception in 2019. This network is where all components of the Celestia ecosystem come to life in a real-world environment.

    Mainnet Beta is the culmination of rigorous community testing, upgrades, and feedback. It serves as the platform for deploying mainnet rollups and applications.

    Network stability and upgrades ​

    Mainnet Beta is a stable network, but will still receive updates and improvements. Any changes or upgrades will be coordinated with node operators and the broader Celestia community to ensure seamless integration and minimal service interruptions.

    As we step into unexplored territories with groundbreaking technologies like data availability sampling, it's crucial to remember that Mainnet Beta remains experimental at this stage. While the network is live and functional, users may encounter occasional instability or reduced performance.

    Network details ​

    DetailValue
    Chain IDcelestia
    Genesis hash6BE39EFD10BA412A9DB5288488303F5DD32CF386707A5BEF33617F4C43301872
    Genesis file https://github.com/celestiaorg/networks/blob/master/celestia/genesis.json
    Peers file https://github.com/celestiaorg/networks/blob/master/celestia/peers.txt
    Validators 100

    Software version numbers ​

    SoftwareVersion
    celestia-nodev0.15.0
    celestia-appv1.13.0

    Network parameters ​

    Full network parameters, such as max bytes, can be found in the celestia-app specifications.

    CIP-13 has been drafted to create a living document for these parameters as a part of the CIP process.

    Maximum bytes ​

    There is a hard limit on the total blob size in a transaction, which is determined by the effective maximum square size. Given that the current governance maximum square size is 64, the total blob size in a transaction must be slightly less than ~2 MiB, or 1,973,786 bytes to be exact.

    The following provides an approximation of the maximum block size:

    • The maximum square size is 64x64, which gives us 4096 shares.
    • One share is reserved for the PFB transaction, leaving us with 4095 shares.
    • The first sparse share has 478 bytes available, and the remaining sparse shares have 482 bytes each.

    This can be calculated as follows:

    Total Bytes=(1×478bytes)+(4094×482bytes)=1,973,786bytes

    Please note that there isn't a precise upper bound on the maximum total blob size. It depends on several factors:

    • The maximum square size, which is determined by a governance parameter and a versioned constant.
    • The maximum bytes in a block, which is determined by a governance parameter and a hard-coded constant in CometBFT.
    • The number of shares occupied by the PFB transaction share.

    These factors can cause the maximum total blob size that can be included in one block to vary.

    See the code in celestia-app and celestia-node.

    Integrations ​

    This guide contains the relevant sections for how to connect to Mainnet Beta, depending on the type of node you are running. Your best approach to participating is to first determine which node you would like to run. Each node’s guide will link to the relevant network in order to show you how to connect to them. Learn about the different endpoint types in the Cosmos SDK documentation.

    Here is a list of options of the types of nodes you can run in order to participate in Mainnet Beta:

    Production RPC endpoints ​

    These RPC providers are meant to be used in production environments.

    ProviderURL
    NewMetrichttps://app.newmetric.xyz/start
    NumiaFor RPC access: https://docs.numia.xyz/overview/rpc-api-access
    NumiaFor data warehouse access: https://docs.numia.xyz/overview/sql-access/chains/celestia
    Grovehttps://www.grove.city/

    WARNING

    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs or your own node.

    Consensus nodes ​

    Community consensus RPC endpoints ​

    WARNING

    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs.

    • public-celestia-rpc.numia.xyz
    • celestia-rpc.mesa.newmetric.xyz
    • rpc.celestia.pops.one
    • rpc.lunaroasis.net
    • rpc.celestia.nodestake.top
    • celestia-rpc.brightlystake.com
    • celestia-rpc.spidey.services
    • rpc-celestia.contributiondao.com
    • celestia.rpc.stakin-nodes.com
    • celestia.cumulo.org.es
    • rpc-celestia.mzonder.com
    • rpc-celestia-01.stakeflow.io
    • rpc-celestia.alphab.ai
    • rpc-celestia-full.avril14th.org
    • celestia-rpc.easy2stake.com
    • celestia.rpc.kjnodes.com
    • celestia-rpc.0xcryptovestor.com
    • rpc-celestia-mainnet.trusted-point.com
    • celestia.rpc.archives.validao.xyz
    • rpc-archive.celestia.bitszn.com
    • celestia-rpc.f5nodes.com
    • celestia-rpc.chainode.tech:33373
    • rpc-celestia.staker.space
    • celestia-rpc.noders.services
    • celestia.moonli.me
    • celestia-mainnet-rpc.itrocket.net:443
    • rpc.celestia.mainnet.dteam.tech:443

    Community API endpoints ​

    • public-celestia-lcd.numia.xyz
    • celestia-rest.mesa.newmetric.xyz
    • api.celestia.pops.one
    • api.lunaroasis.net
    • api.celestia.nodestake.top
    • celestia-rpc.brightlystake.com/api
    • celestia-api.spidey.services
    • api-celestia.contributiondao.com
    • celestia.rest.stakin-nodes.com
    • celestia.api.cumulo.org.es
    • api-celestia.mzonder.com
    • api-celestia-01.stakeflow.io
    • api-celestia.alphab.ai
    • api-celestia-full.avril14th.org
    • celestia-lcd.easy2stake.com
    • celestia.api.kjnodes.com
    • api-celestia-mainnet.trusted-point.com
    • celestia.rest.archives.validao.xyz
    • api-archive.celestia.bitszn.com
    • celestia-api.f5nodes.com
    • celestia-api.chainode.tech
    • api-celestia.staker.space
    • celestia-api.noders.services
    • celestia.moonli.me/api
    • celestia-mainnet-api.itrocket.net:443
    • api.celestia.mainnet.dteam.tech:443

    Community gRPC endpoints ​

    • public-celestia-grpc.numia.xyz
    • celestia-grpc.mesa.newmetric.xyz
    • grpc.celestia.pops.one
    • grpc.lunaroasis.net:443
    • grpc.celestia.nodestake.top
    • celestia-rpc.brightlystake.com:9090
    • celestia-grpc.spidey.services
    • grpc-celestia.contributiondao.com
    • celestia.grpc.stakin-nodes.com:443
    • celestia.grpc.cumulo.org.es:443
    • grpc-celestia.mzonder.com:443
    • grpc-celestia-01.stakeflow.io:15002
    • rpc-celestia.alphab.ai:9090
    • grpc-celestia-full.avril14th.org
    • celestia.grpc.kjnodes.com:443
    • grpc-celestia-mainnet.trusted-point.com:9095
    • celestia.grpc.archives.validao.xyz:9090
    • gprc-archive.celestia.bitszn.com
    • celestia-grpc.f5nodes.com:9390
    • celestia-grpc.chainode.tech:443
    • grpc-celestia.staker.space
    • celestia-grpc.noders.services:11090
    • celestia-mainnet-grpc.itrocket.net:443
    • grpc.celestia.mainnet.dteam.tech:28090

    Community WebSocket endpoints ​

    • wss://celestia-ws.chainode.tech:33373/websocket
    • wss://celestia-mainnet-ws.itrocket.net:443/websocket
    • wss://rpc.celestia.mainnet.dteam.tech:443/websocket

    Data availability nodes ​

    Community Data availability (DA) RPC endpoints for bridge node sync ​

    These RPC endpoints allow bridge nodes to sync blocks from the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default RPC port at 26657 to their respective DA node.

    Community Data availability (DA) gRPC endpoints for state access ​

    These gRPC endpoints for DA nodes provide state access for querying the chain’s state and broadcasting transactions (balances, blobs, etc.) to the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default gRPC port at 9090 to their respective DA node.

    TIP

    bash
    celestia <da_type> start --core.ip <url> -–core.grpc.port <port>
    celestia <da_type> start --core.ip <url> -–core.grpc.port <port>

    Bridge nodes

    Not all RPC endpoints guarantee the full block history. Find an archive endpoint on the community dashboard or run your own consensus node with no pruning for your bridge node.

    RPCs for DA nodes to initialise or start your celestia-node to Mainnet Beta with:

    • public-celestia-consensus.numia.xyz
      • gRPC: port 9090
      • RPC: port 26657
    • celestia-consensus.mesa.newmetric.xyz
      • gRPC: port 9090
      • RPC: port 26657
    • rpc.celestia.pops.one
      • gRPC: port 9090
      • RPC: port 26657
    • consensus.lunaroasis.net
      • gRPC: port 9090
      • RPC: port 26657
    • rpc-celestia.alphab.ai
      • gRPC: port 9090
      • RPC: port 26657
    • celestia-mainnet-consensus.itrocket.net
      • gRPC: port 9090
      • RPC: port 26657
    • rpc.celestia.mainnet.dteam.tech
      • gRPC: port 28090
      • RPC: 28657
    • celestia-consensus-mainnet.noders.services
      • gRPC: port 9080
      • RPC: port 26557

    DA full and light nodes might have troubles connecting to the networks, so you can check out this Grafana dashboard to see health/uptime status of DA bootstrappers (now celestia network only).

    You can find the status of these endpoints.

    Archival DA RPC endpoints ​

    By default, light nodes prune recent data to save on storage space. Archival data availability (DA) nodes store the entire history of the chain without pruning any data so all data available data is retrievable. You can read more about light vs archival nodes.

    Grove archival endpoints ​

    You can provision your own Celestia Archival endpoint on Grove. Learn more about Celestia on Grove, or find the fully supported spec.

    There is a sandbox you can leverage for testing straight in your browser:

    grove-sandbox

    Explorers ​

    There are multiple explorers you can use for Mainnet Beta:

    Analytics ​

    The following websites provide analytics for Celestia:

    Network upgrades ​

    There are a few ways to stay informed about network upgrades on Mainnet Beta:

    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.

    + \ No newline at end of file diff --git a/pr-1699/nodes/mocha-testnet.html b/pr-1699/nodes/mocha-testnet.html index 69f85193e8..bbceb5bb22 100644 --- a/pr-1699/nodes/mocha-testnet.html +++ b/pr-1699/nodes/mocha-testnet.html @@ -14,7 +14,7 @@ - + @@ -41,8 +41,8 @@

    Appearance

    Mocha testnet ​

    mocha-testnet

    This guide contains the relevant sections for how to connect to Mocha, depending on the type of node you are running. Mocha testnet is designed to help validators test out their infrastructure and node software. Developers are encouraged to deploy their sovereign rollups on Mocha, but we also recommend Arabica devnet for that as it is designed for development purposes.

    Mocha is a milestone in Celestia, allowing everyone to test out core functionalities on the network. Read the announcement. Your best approach to participating is to first determine which node you would like to run. Each node's guide will link to the relevant networks, to show you how to connect to them.

    You have a list of options on the types of nodes you can run to participate in Mocha:

    Consensus:

    Data Availability:

    Select the type of node you would like to run and follow the instructions on each respective page. Whenever you are asked to select the type of network you want to connect to in those guides, select Mocha to refer to the correct instructions on this page on how to connect to Mocha.

    Network details ​

    DetailValue
    Chain IDmocha-4
    Genesis hashB93BBE20A0FBFDF955811B6420F8433904664D45DB4BF51022BE4200C1A1680D
    Genesis file https://github.com/celestiaorg/networks/blob/master/mocha-4/genesis.json
    Peers file https://github.com/celestiaorg/networks/blob/master/mocha-4/peers.txt
    Validators 100

    Software version numbers ​

    SoftwareVersion
    celestia-nodev0.16.0
    celestia-appv2.1.2

    RPC for DA bridge, full, and light nodes ​

    Production RPC endpoints ​

    These RPC providers are meant to be used in production environments.

    ProviderURL
    NewMetrichttps://app.newmetric.xyz/start
    NumiaFor RPC access: https://docs.numia.xyz/overview/rpc-api-access
    NumiaFor data warehouse access: https://docs.numia.xyz/overview/sql-access/chains/celestia
    Grovehttps://www.grove.city/

    WARNING

    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs or your own node.

    Community Data availability (DA) RPC endpoints for bridge node sync ​

    These RPC endpoints allow bridge nodes to sync blocks from the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default RPC port at 26657 to their respective DA node.

    Community Data availability (DA) gRPC endpoints for state access ​

    These gRPC endpoints for DA nodes provide state access for querying the chain’s state and broadcasting transactions (balances, blobs, etc.) to the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default gRPC port at 9090 to their respective DA node.

    Bridge nodes

    Mentioned below RPC endpoints do not guarantee you the download of full blocks from them. We advise that if you are running a bridge node, that you also run a local consensus node in order to download full blocks from it.

    • public-celestia-mocha4-consensus.numia.xyz
    • mocha-4-consensus.mesa.newmetric.xyz
    • full.consensus.mocha-4.celestia-mocha.com
    • consensus-full-mocha-4.celestia-mocha.com
    • rpc-mocha.pops.one
    • celestia-testnet-consensus.itrocket.net
      • RPC port: 26657
      • gRPC port: 9090
    • rpc-celestia-testnet.cryptech.com.ua
      • gRPC: grpc-celestia-testnet.cryptech.com.ua:443
    • rpc.celestia.testnet.dteam.tech:443
      • gRPC: grpc.celestia.testnet.dteam.tech:27090
    • celestia-consensus-testnet.noders.services
      • RPC port: 26357
      • gRPC port: 9070

    Community RPC endpoints ​

    The RPC endpoint is to allow users to interact with Celestia's nodes by querying the node's state and broadcasting transactions on the Celestia network. The default port is 26657.

    • public-celestia-mocha4-consensus.numia.xyz:26657
    • mocha-4-consensus.mesa.newmetric.xyz:26657
    • rpc.celestia-mocha.com
    • celestia-testnet-rpc.f5nodes.com
    • celestia-testnet.brightlystake.com
    • rpc-celestia-mocha.architectnodes.com
    • rpc-celestia-mocha.trusted-point.com
    • rpc-celestia-testnet-01.stakeflow.io
    • mocha.celestia.rpc.cumulo.me
    • rpc-mocha-4.spidey.services
    • rpc-mocha-full.avril14th.org
    • rpc.mocha.bitszn.com
    • celestia-t-rpc.noders.services/
    • rpc-1.testnet.celestia.nodes.guru
    • rpc-2.testnet.celestia.nodes.guru
    • celestia-testnet-rpc.itrocket.net:443
    • rpc-celestia-testnet.cryptech.com.ua:443
    • rpc.celestia.testnet.dteam.tech:443

    Community API endpoints ​

    The API endpoint is to allow users to interact with the REST API in Cosmos SDK which is implemented using gRPC-gateway, which exposes gRPC endpoints as REST endpoints. This allows for communication with the node using REST calls, which can be useful if the client does not support gRPC or HTTP2. The default port is 1317.

    Community gRPC endpoints ​

    The gRPC endpoint is to allow users to interact with a Celestia Node using gRPC, a modern open-source and high-performance RPC framework. The default port is 9090. In the Cosmos SDK, gRPC is used to define state queries and broadcast transactions.

    • public-celestia-mocha4-consensus.numia.xyz:9090
    • mocha-4-consensus.mesa.newmetric.xyz:9090
    • grpc-mocha.pops.one
    • grpc.celestia-mocha.com:443
    • full.consensus.mocha-4.celestia-mocha.com:9090
    • consensus-full-mocha-4.celestia-mocha.com:9090
    • celestia-testnet-grpc.f5nodes.com
    • celestia-testnet.brightlystake.com:9390
    • grpc-celestia-mocha.architectnodes.com:1443
    • grpc-celestia-mocha.trusted-point.com:9099
    • grpc-celestia-testnet-01.stakeflow.io:16002
    • mocha.grpc.cumulo.me:443
    • grpc-mocha-4.spidey.services
    • grpc-mocha-full.avril14th.org
    • grpc.mocha.bitszn.com
    • celestia-grpc.noders.services:21090
    • grpc-1.testnet.celestia.nodes.guru:10790
    • grpc-2.testnet.celestia.nodes.guru:10790
    • celestia-testnet-grpc.itrocket.net:443
    • grpc-celestia-testnet.cryptech.com.ua:443
    • grpc.celestia.testnet.dteam.tech:27090

    Community bridge and full node endpoints ​

    The endpoints below are for bridge and full nodes only. They can be used to find bootstrapper peers in the p2p network.

    Bridge node 1:

    • da-bridge-mocha-4.celestia-mocha.com
    • bridge-mocha-4.da.celestia-mocha.com

    Bridge node 2:

    • da-bridge-mocha-4-2.celestia-mocha.com
    • bridge-mocha-4-2.da.celestia-mocha.com

    Full node 1:

    • da-full-1-mocha-4.celestia-mocha.com
    • full-1-mocha-4.da.celestia-mocha.com

    Full node 2:

    • da-full-2-mocha-4.celestia-mocha.com
    • full-2-mocha-4.da.celestia-mocha.com

    Mocha testnet faucet ​

    WARNING

    USING THIS FAUCET DOES NOT ENTITLE YOU TO ANY AIRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS.

    You can request from Mocha testnet Faucet on the #mocha-faucet channel on Celestia's Discord server with the following command:

    text
    $request <CELESTIA-ADDRESS>
    $request <CELESTIA-ADDRESS>

    Where <CELESTIA-ADDRESS> is a celestia1****** generated address.

    NOTE

    Faucet has a limit of 10 tokens per week per address/Discord ID.

    Analytics ​

    The following websites provide analytics for Mocha Testnet:

    Explorers ​

    There are several explorers you can use for Mocha:

    Network upgrades ​

    There are a few ways to stay informed about network upgrades on Mocha testnet:

    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.

    - +

    Mocha testnet ​

    mocha-testnet

    This guide contains the relevant sections for how to connect to Mocha, depending on the type of node you are running. Mocha testnet is designed to help validators test out their infrastructure and node software. Developers are encouraged to deploy their sovereign rollups on Mocha, but we also recommend Arabica devnet for that as it is designed for development purposes.

    Mocha is a milestone in Celestia, allowing everyone to test out core functionalities on the network. Read the announcement. Your best approach to participating is to first determine which node you would like to run. Each node's guide will link to the relevant networks, to show you how to connect to them.

    You have a list of options on the types of nodes you can run to participate in Mocha:

    Consensus:

    Data Availability:

    Select the type of node you would like to run and follow the instructions on each respective page. Whenever you are asked to select the type of network you want to connect to in those guides, select Mocha to refer to the correct instructions on this page on how to connect to Mocha.

    Network details ​

    DetailValue
    Chain IDmocha-4
    Genesis hashB93BBE20A0FBFDF955811B6420F8433904664D45DB4BF51022BE4200C1A1680D
    Genesis file https://github.com/celestiaorg/networks/blob/master/mocha-4/genesis.json
    Peers file https://github.com/celestiaorg/networks/blob/master/mocha-4/peers.txt
    Validators 100

    Software version numbers ​

    SoftwareVersion
    celestia-nodev0.16.0
    celestia-appv2.1.2

    RPC for DA bridge, full, and light nodes ​

    Production RPC endpoints ​

    These RPC providers are meant to be used in production environments.

    ProviderURL
    NewMetrichttps://app.newmetric.xyz/start
    NumiaFor RPC access: https://docs.numia.xyz/overview/rpc-api-access
    NumiaFor data warehouse access: https://docs.numia.xyz/overview/sql-access/chains/celestia
    Grovehttps://www.grove.city/

    WARNING

    Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on service providers with SLAs or your own node.

    Community Data availability (DA) RPC endpoints for bridge node sync ​

    These RPC endpoints allow bridge nodes to sync blocks from the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default RPC port at 26657 to their respective DA node.

    Community Data availability (DA) gRPC endpoints for state access ​

    These gRPC endpoints for DA nodes provide state access for querying the chain’s state and broadcasting transactions (balances, blobs, etc.) to the Celestia network. For users, they will need to provide a –core.ip string from a consensus node’s URL or IP that populates a default gRPC port at 9090 to their respective DA node.

    Bridge nodes

    Mentioned below RPC endpoints do not guarantee you the download of full blocks from them. We advise that if you are running a bridge node, that you also run a local consensus node in order to download full blocks from it.

    • public-celestia-mocha4-consensus.numia.xyz
    • mocha-4-consensus.mesa.newmetric.xyz
    • full.consensus.mocha-4.celestia-mocha.com
    • consensus-full-mocha-4.celestia-mocha.com
    • rpc-mocha.pops.one
    • celestia-testnet-consensus.itrocket.net
      • RPC port: 26657
      • gRPC port: 9090
    • rpc-celestia-testnet.cryptech.com.ua
      • gRPC: grpc-celestia-testnet.cryptech.com.ua:443
    • rpc.celestia.testnet.dteam.tech:443
      • gRPC: grpc.celestia.testnet.dteam.tech:27090
    • celestia-consensus-testnet.noders.services
      • RPC port: 26357
      • gRPC port: 9070

    Community RPC endpoints ​

    The RPC endpoint is to allow users to interact with Celestia's nodes by querying the node's state and broadcasting transactions on the Celestia network. The default port is 26657.

    • public-celestia-mocha4-consensus.numia.xyz:26657
    • mocha-4-consensus.mesa.newmetric.xyz:26657
    • rpc.celestia-mocha.com
    • celestia-testnet-rpc.f5nodes.com
    • celestia-testnet.brightlystake.com
    • rpc-celestia-mocha.architectnodes.com
    • rpc-celestia-mocha.trusted-point.com
    • rpc-celestia-testnet-01.stakeflow.io
    • mocha.celestia.rpc.cumulo.me
    • rpc-mocha-4.spidey.services
    • rpc-mocha-full.avril14th.org
    • rpc.mocha.bitszn.com
    • celestia-t-rpc.noders.services/
    • rpc-1.testnet.celestia.nodes.guru
    • rpc-2.testnet.celestia.nodes.guru
    • celestia-testnet-rpc.itrocket.net:443
    • rpc-celestia-testnet.cryptech.com.ua:443
    • rpc.celestia.testnet.dteam.tech:443

    Community API endpoints ​

    The API endpoint is to allow users to interact with the REST API in Cosmos SDK which is implemented using gRPC-gateway, which exposes gRPC endpoints as REST endpoints. This allows for communication with the node using REST calls, which can be useful if the client does not support gRPC or HTTP2. The default port is 1317.

    Community gRPC endpoints ​

    The gRPC endpoint is to allow users to interact with a Celestia Node using gRPC, a modern open-source and high-performance RPC framework. The default port is 9090. In the Cosmos SDK, gRPC is used to define state queries and broadcast transactions.

    • public-celestia-mocha4-consensus.numia.xyz:9090
    • mocha-4-consensus.mesa.newmetric.xyz:9090
    • grpc-mocha.pops.one
    • grpc.celestia-mocha.com:443
    • full.consensus.mocha-4.celestia-mocha.com:9090
    • consensus-full-mocha-4.celestia-mocha.com:9090
    • celestia-testnet-grpc.f5nodes.com
    • celestia-testnet.brightlystake.com:9390
    • grpc-celestia-mocha.architectnodes.com:1443
    • grpc-celestia-mocha.trusted-point.com:9099
    • grpc-celestia-testnet-01.stakeflow.io:16002
    • mocha.grpc.cumulo.me:443
    • grpc-mocha-4.spidey.services
    • grpc-mocha-full.avril14th.org
    • grpc.mocha.bitszn.com
    • celestia-grpc.noders.services:21090
    • grpc-1.testnet.celestia.nodes.guru:10790
    • grpc-2.testnet.celestia.nodes.guru:10790
    • celestia-testnet-grpc.itrocket.net:443
    • grpc-celestia-testnet.cryptech.com.ua:443
    • grpc.celestia.testnet.dteam.tech:27090

    Community bridge and full node endpoints ​

    The endpoints below are for bridge and full nodes only. They can be used to find bootstrapper peers in the p2p network.

    Bridge node 1:

    • da-bridge-mocha-4.celestia-mocha.com
    • bridge-mocha-4.da.celestia-mocha.com

    Bridge node 2:

    • da-bridge-mocha-4-2.celestia-mocha.com
    • bridge-mocha-4-2.da.celestia-mocha.com

    Full node 1:

    • da-full-1-mocha-4.celestia-mocha.com
    • full-1-mocha-4.da.celestia-mocha.com

    Full node 2:

    • da-full-2-mocha-4.celestia-mocha.com
    • full-2-mocha-4.da.celestia-mocha.com

    Mocha testnet faucet ​

    WARNING

    USING THIS FAUCET DOES NOT ENTITLE YOU TO ANY AIRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS.

    You can request from Mocha testnet Faucet on the #mocha-faucet channel on Celestia's Discord server with the following command:

    text
    $request <CELESTIA-ADDRESS>
    $request <CELESTIA-ADDRESS>

    Where <CELESTIA-ADDRESS> is a celestia1****** generated address.

    NOTE

    Faucet has a limit of 10 tokens per week per address/Discord ID.

    Analytics ​

    The following websites provide analytics for Mocha Testnet:

    Explorers ​

    There are several explorers you can use for Mocha:

    Network upgrades ​

    There are a few ways to stay informed about network upgrades on Mocha testnet:

    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.

    + \ No newline at end of file diff --git a/pr-1699/nodes/overview.html b/pr-1699/nodes/overview.html index 3a47a18fe9..fc8edde45d 100644 --- a/pr-1699/nodes/overview.html +++ b/pr-1699/nodes/overview.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    Overview to running nodes on Celestia ​

    There are many ways you can participate in the Celestia networks.

    Celestia node operators can run several options on the network.

    Consensus:

    • Validator node: This type of node participates in consensus by producing and voting on blocks.
    • Consensus node: A celestia-app full node to sync blockchain history.

    Data Availability:

    • Bridge node: This node bridges blocks between the Data-Availability network and the Consensus network.
    • Full storage node: This node stores all the data but does not connect to Consensus.
    • Light node: Light clients conduct data availability sampling on the Data Availability network.

    You can learn more about how to set up each different node by going through each tutorial guide.

    Data availability nodes ​

    Node typeMemoryCPUDiskBandwidth
    Light node500 MB RAMSingle core100 GB SSD56 Kbps
    Bridge node16 GB RAM6 cores10 TB SSD1 Gbps
    Full storage node16 GB RAMQuad-core10 TB SSD1 Gbps

    Consensus nodes ​

    Node typeMemoryCPUDiskBandwidth
    Validator16 GB RAM8 cores2 TB SSD1 Gbps
    Consensus node16 GB RAMQuad-core2 TB SSD1 Gbps

    Please provide any feedback on the tutorials and guides. If you notice a bug or issue, feel free to make a pull request or write up a Github issue!

    - +

    Overview to running nodes on Celestia ​

    There are many ways you can participate in the Celestia networks.

    Celestia node operators can run several options on the network.

    Consensus:

    • Validator node: This type of node participates in consensus by producing and voting on blocks.
    • Consensus node: A celestia-app full node to sync blockchain history.

    Data Availability:

    • Bridge node: This node bridges blocks between the Data-Availability network and the Consensus network.
    • Full storage node: This node stores all the data but does not connect to Consensus.
    • Light node: Light clients conduct data availability sampling on the Data Availability network.

    You can learn more about how to set up each different node by going through each tutorial guide.

    Data availability nodes ​

    Node typeMemoryCPUDiskBandwidth
    Light node500 MB RAMSingle core100 GB SSD56 Kbps
    Bridge node16 GB RAM6 cores10 TB SSD1 Gbps
    Full storage node16 GB RAMQuad-core10 TB SSD1 Gbps

    Consensus nodes ​

    Node typeMemoryCPUDiskBandwidth
    Validator16 GB RAM8 cores2 TB SSD1 Gbps
    Consensus node16 GB RAMQuad-core2 TB SSD1 Gbps

    Please provide any feedback on the tutorials and guides. If you notice a bug or issue, feel free to make a pull request or write up a Github issue!

    + \ No newline at end of file diff --git a/pr-1699/nodes/participate.html b/pr-1699/nodes/participate.html index f90ead2290..ece1e9aa8b 100644 --- a/pr-1699/nodes/participate.html +++ b/pr-1699/nodes/participate.html @@ -18,7 +18,7 @@ - + @@ -45,8 +45,8 @@

    Appearance

    Participate in the Celestia networks ​

    Mainnet Beta ​

    Celestia’s Mainnet Beta is the production network for deploying mainnet rollups and applications. This marks the culmination of years of development and community testing. While the network is stable and continues to receive updates, it remains experimental and users may experience occasional instability or reduced performance.

    Compatible software versions for Mainnet Beta ​

    SoftwareVersion
    celestia-nodev0.15.0
    celestia-appv1.13.0

    Testnets ​

    Celestia currently has two existing testnets that you can participate in:

    Arabica Devnet ​

    Arabica devnet is a devnet focused on developers who want to deploy sovereign rollups on the latest changes from Celestia's codebase. Arabica will be updated frequently and might be unstable at times given new updates. Validators won't be able to validate on Arabica as it is not designed for validators to participate.

    Compatible software versions for Arabica devnet ​

    SoftwareVersion
    celestia-nodev0.16.0
    celestia-appv2.1.2

    Mocha testnet ​

    Mocha testnet is a testnet focused on enabling validators to test out their infrastructure by running nodes connected to the network. Developers can also deploy sovereign rollups on Mocha, it just will always be behind Arabica as Mocha upgrades are slower given they need to be done via hardforks in coordination with the validator community on Mocha.

    Compatible software versions for Mocha testnet ​

    SoftwareVersion
    celestia-nodev0.16.0
    celestia-appv2.1.2

    Network upgrades ​

    There are a few ways to stay informed about network upgrades:

    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.

    - +

    Participate in the Celestia networks ​

    Mainnet Beta ​

    Celestia’s Mainnet Beta is the production network for deploying mainnet rollups and applications. This marks the culmination of years of development and community testing. While the network is stable and continues to receive updates, it remains experimental and users may experience occasional instability or reduced performance.

    Compatible software versions for Mainnet Beta ​

    SoftwareVersion
    celestia-nodev0.15.0
    celestia-appv1.13.0

    Testnets ​

    Celestia currently has two existing testnets that you can participate in:

    Arabica Devnet ​

    Arabica devnet is a devnet focused on developers who want to deploy sovereign rollups on the latest changes from Celestia's codebase. Arabica will be updated frequently and might be unstable at times given new updates. Validators won't be able to validate on Arabica as it is not designed for validators to participate.

    Compatible software versions for Arabica devnet ​

    SoftwareVersion
    celestia-nodev0.16.0
    celestia-appv2.1.2

    Mocha testnet ​

    Mocha testnet is a testnet focused on enabling validators to test out their infrastructure by running nodes connected to the network. Developers can also deploy sovereign rollups on Mocha, it just will always be behind Arabica as Mocha upgrades are slower given they need to be done via hardforks in coordination with the validator community on Mocha.

    Compatible software versions for Mocha testnet ​

    SoftwareVersion
    celestia-nodev0.16.0
    celestia-appv2.1.2

    Network upgrades ​

    There are a few ways to stay informed about network upgrades:

    See the Hardfork process page to learn more about specific upgrades like the Lemongrass hardfork.

    + \ No newline at end of file diff --git a/pr-1699/nodes/quick-start.html b/pr-1699/nodes/quick-start.html index b0b4449c99..7bffa3f015 100644 --- a/pr-1699/nodes/quick-start.html +++ b/pr-1699/nodes/quick-start.html @@ -11,7 +11,7 @@ - + @@ -38,8 +38,8 @@

    Appearance

    Quick start guide ​

    In this section, we show you how to get started with installing the needed libraries and packages in Celestia to help you run a node on Celestia.

    Celestia Node ​

    Install celestia-node allows you to get started with running a light node and do data availability sampling.

    Light nodes are the best nodes to test out initially if you are new to participating in Celestia.

    celestia-node client also allows you to run other types of data availability (DA) nodes like bridge and full DA storage nodes, which will be covered in later sections.

    Celestia App ​

    Install celestia-app allows you to get started running a consensus node.

    celestia-app is the software that allows you to run validator nodes and also provide RPC endpoints.

    celestia-app covers the consensus layer, while celestia-node covers the DA layer.

    Getting started ​

    As covered in the previous section, Celestia offers two different test networks, Arabica devnet and Mocha testnet.

    If you are planning to run a light node, it is recommended to use Arabica, which you will find options to connecting to in the later sections.

    If you plan on running a validator, your only option is to run your node on Mocha.

    In this quick start guide, we will go over installing both of the software clients: celestia-node and celestia-app.

    NOTE

    If you just want to run a light node, you don't need to install celestia-app and can skip that part.

    Proceed to the next section in order to get started.

    - +

    Quick start guide ​

    In this section, we show you how to get started with installing the needed libraries and packages in Celestia to help you run a node on Celestia.

    Celestia Node ​

    Install celestia-node allows you to get started with running a light node and do data availability sampling.

    Light nodes are the best nodes to test out initially if you are new to participating in Celestia.

    celestia-node client also allows you to run other types of data availability (DA) nodes like bridge and full DA storage nodes, which will be covered in later sections.

    Celestia App ​

    Install celestia-app allows you to get started running a consensus node.

    celestia-app is the software that allows you to run validator nodes and also provide RPC endpoints.

    celestia-app covers the consensus layer, while celestia-node covers the DA layer.

    Getting started ​

    As covered in the previous section, Celestia offers two different test networks, Arabica devnet and Mocha testnet.

    If you are planning to run a light node, it is recommended to use Arabica, which you will find options to connecting to in the later sections.

    If you plan on running a validator, your only option is to run your node on Mocha.

    In this quick start guide, we will go over installing both of the software clients: celestia-node and celestia-app.

    NOTE

    If you just want to run a light node, you don't need to install celestia-app and can skip that part.

    Proceed to the next section in order to get started.

    + \ No newline at end of file diff --git a/pr-1699/nodes/systemd.html b/pr-1699/nodes/systemd.html index f3de71d3af..a3684ab86b 100644 --- a/pr-1699/nodes/systemd.html +++ b/pr-1699/nodes/systemd.html @@ -11,7 +11,7 @@ - + @@ -162,8 +162,8 @@ WantedBy=multi-user.target EOF

    If the file was created successfully you will be able to see its content:

    sh
    cat /etc/systemd/system/celestia-lightd.service
    cat /etc/systemd/system/celestia-lightd.service

    Enable and start celestia-lightd daemon:

    sh
    sudo systemctl enable celestia-lightd
 sudo systemctl start celestia-lightd
    sudo systemctl enable celestia-lightd
-sudo systemctl start celestia-lightd

    Check if daemon has been started correctly:

    sh
    sudo systemctl status celestia-lightd
    sudo systemctl status celestia-lightd

    Check daemon logs in real time:

    sh
    sudo journalctl -u celestia-lightd.service -f
    sudo journalctl -u celestia-lightd.service -f

    Now, the Celestia light node will start syncing headers. After sync is finished, light node will do Data Availability Sampling (DAS) from the bridge node.

    - +sudo systemctl start celestia-lightd

    Check if daemon has been started correctly:

    sh
    sudo systemctl status celestia-lightd
    sudo systemctl status celestia-lightd

    Check daemon logs in real time:

    sh
    sudo journalctl -u celestia-lightd.service -f
    sudo journalctl -u celestia-lightd.service -f

    Now, the Celestia light node will start syncing headers. After sync is finished, light node will do Data Availability Sampling (DAS) from the bridge node.

    + \ No newline at end of file diff --git a/pr-1699/nodes/validator-node.html b/pr-1699/nodes/validator-node.html index fcf6af9b98..86b6cb33a6 100644 --- a/pr-1699/nodes/validator-node.html +++ b/pr-1699/nodes/validator-node.html @@ -12,7 +12,7 @@ - + @@ -69,7 +69,7 @@ raw_log: '[]' timestamp: "" tx: null -txhash: <tx-hash>

    You can check if the TX hash went through using the block explorer by inputting the txhash ID that was returned.

    Optional: Deploy the celestia-node ​

    Running a bridge node is critical to the Celestia network as it enables the data availability and consensus nodes to communicate with one another. It is recommended to support the data availability network, but is not required for celestia-app.

    If you are not running a bridge node, you can skip to run a validator node.

    This section describes part 2 of Celestia validator node setup: running a Celestia bridge node daemon.

    Install celestia-node ​

    You can follow the tutorial for installing celestia-node

    Initialize the bridge node ​

    Run the following:

    bash
    celestia bridge init --core.ip <URI>
    celestia bridge init --core.ip <URI>

    TIP

    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

    If you need a list of RPC endpoints to connect to, you can find the list on the Mocha testnet page or list on the Arabica devnet page.

    Run the bridge node ​

    Run the following:

    bash
    celestia bridge start
    celestia bridge start

    Optional: start the bridge node with SystemD ​

    Follow the tutorial on setting up the bridge node as a background process with SystemD.

    You have successfully set up a bridge node that is syncing with the network.

    Run the validator node ​

    If you are running celestia-app v1.x.x:

    sh
    celestia-appd start
    celestia-appd start

    If you are running celestia-app >= v2.0.0: then you'll want to start the node with a --v2-upgrade-height that is dependent on the network. The --v2-upgrade-height flag is only needed during the v2 upgrade height so after your node has executed the upgrade (e.g. you see the log upgraded from app version 1 to 2), you don't need to provide this flag for future celestia-appd start invocations.

    sh
    celestia-appd start --v2-upgrade-height 2371495
    celestia-appd start --v2-upgrade-height 2371495
    sh
    celestia-appd start --v2-upgrade-height 2585031
    celestia-appd start --v2-upgrade-height 2585031
    sh
    celestia-appd start --v2-upgrade-height 1751707
    celestia-appd start --v2-upgrade-height 1751707

    After completing all the necessary steps, you are now ready to run a validator! In order to create your validator onchain, follow the instructions below. Keep in mind that these steps are necessary ONLY if you want to participate in the consensus.

    Pick a moniker name of your choice! This is the validator name that will show up on public dashboards and explorers. VALIDATOR_WALLET must be the same you defined previously. Parameter --min-self-delegation=1000000 defines the amount of tokens that are self delegated from your validator wallet.

    Now, connect to the network of your choice.

    You have the following option of connecting to list of networks shown below:

    Continuing the validator tutorial, here are the steps to connect your validator to Mocha:

    bash
    MONIKER="your_moniker"
+txhash: <tx-hash>

    You can check if the TX hash went through using the block explorer by inputting the txhash ID that was returned.

    Optional: Deploy the celestia-node ​

    Running a bridge node is critical to the Celestia network as it enables the data availability and consensus nodes to communicate with one another. It is recommended to support the data availability network, but is not required for celestia-app.

    If you are not running a bridge node, you can skip to run a validator node.

    This section describes part 2 of Celestia validator node setup: running a Celestia bridge node daemon.

    Install celestia-node ​

    You can follow the tutorial for installing celestia-node

    Initialize the bridge node ​

    Run the following:

    bash
    celestia bridge init --core.ip <URI>
    celestia bridge init --core.ip <URI>

    TIP

    Refer to the ports section of the celestia-node troubleshooting page for information on which ports are required to be open on your machine.

    If you need a list of RPC endpoints to connect to, you can find the list on the Mocha testnet page or list on the Arabica devnet page.

    Run the bridge node ​

    Run the following:

    bash
    celestia bridge start
    celestia bridge start

    Optional: start the bridge node with SystemD ​

    Follow the tutorial on setting up the bridge node as a background process with SystemD.

    You have successfully set up a bridge node that is syncing with the network.

    Run the validator node ​

    If you are running celestia-app v1.x.x:

    sh
    celestia-appd start
    celestia-appd start

    If you are running celestia-app >= v2.0.0: then you'll want to start the node with a --v2-upgrade-height that is dependent on the network. The --v2-upgrade-height flag is only needed during the v2 upgrade height so after your node has executed the upgrade (e.g. you see the log upgraded from app version 1 to 2), you don't need to provide this flag for future celestia-appd start invocations.

    sh
    celestia-appd start --v2-upgrade-height 2371495
    celestia-appd start --v2-upgrade-height 2371495
    sh
    celestia-appd start --v2-upgrade-height 2585031
    celestia-appd start --v2-upgrade-height 2585031
    sh
    celestia-appd start --v2-upgrade-height 1751707
    celestia-appd start --v2-upgrade-height 1751707

    After completing all the necessary steps, you are now ready to run a validator! In order to create your validator onchain, follow the instructions below. Keep in mind that these steps are necessary ONLY if you want to participate in the consensus.

    Pick a moniker name of your choice! This is the validator name that will show up on public dashboards and explorers. VALIDATOR_WALLET must be the same you defined previously. Parameter --min-self-delegation=1000000 defines the amount of tokens that are self delegated from your validator wallet.

    Now, connect to the network of your choice.

    You have the following option of connecting to list of networks shown below:

    Continuing the validator tutorial, here are the steps to connect your validator to Mocha:

    bash
    MONIKER="your_moniker"
 VALIDATOR_WALLET="validator"
 
 celestia-appd tx staking create-validator \
@@ -121,8 +121,8 @@
 raw_log: '[]'
 timestamp: ""
 tx: null
-txhash: <tx-hash>

    You should now be able to see your validator from a block explorer

    Submit your validator information ​

    After starting your node, please submit your node as a seed and peer to the networks repository.

    Optional: Transaction indexer configuration options ​

    Follow the instructions under transaction indexer configuration options to configure your config.toml file to select which transactions to index.

    Additional resources ​

    For additional resources, refer to the extra resources for consensus nodessection of the consensus node page.

    FAQ ​

    +2/3 committed an invalid block: wrong Block.Header.Version ​

    If you encounter an error like:

    bash
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\nruntime/debug.Stack()\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\npanic({0x1b91180?, 0x400153b240?})\n\t/usr/local/go/src/runtime/panic.go:770 +0x124\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\n"
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\nruntime/debug.Stack()\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\npanic({0x1b91180?, 0x400153b240?})\n\t/usr/local/go/src/runtime/panic.go:770 +0x124\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\n"

    then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant --v2-upgrade-height for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a celestia-appd tendermint reset-state to reset your node and start syncing from the genesis block.

    - +txhash: <tx-hash>

    You should now be able to see your validator from a block explorer

    Submit your validator information ​

    After starting your node, please submit your node as a seed and peer to the networks repository.

    Optional: Transaction indexer configuration options ​

    Follow the instructions under transaction indexer configuration options to configure your config.toml file to select which transactions to index.

    Additional resources ​

    For additional resources, refer to the extra resources for consensus nodessection of the consensus node page.

    FAQ ​

    +2/3 committed an invalid block: wrong Block.Header.Version ​

    If you encounter an error like:

    bash
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\nruntime/debug.Stack()\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\npanic({0x1b91180?, 0x400153b240?})\n\t/usr/local/go/src/runtime/panic.go:770 +0x124\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\n"
    2024-04-25 14:48:24 6:48PM ERR CONSENSUS FAILURE!!! err="+2/3 committed an invalid block: wrong Block.Header.Version. Expected {11 1}, got {11 2}" module=consensus stack="goroutine 214 [running]:\nruntime/debug.Stack()\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:746 +0x44\npanic({0x1b91180?, 0x400153b240?})\n\t/usr/local/go/src/runtime/panic.go:770 +0x124\ngithub.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1637 +0xd30\ngithub.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:1606 +0x26c\ngithub.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0x400065ea88, 0x3)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:2001 +0x2d8\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0x400065ea88, {{0x2b30a00, 0x400143e048}, {0x40002a61b0, 0x28}})\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:856 +0x1c8\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0x400065ea88, 0x0)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:782 +0x2c4\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart in goroutine 169\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.35.0-tm-v0.34.29/consensus/state.go:391 +0x110\n"

    then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant --v2-upgrade-height for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a celestia-appd tendermint reset-state to reset your node and start syncing from the genesis block.

    + \ No newline at end of file diff --git a/pr-1699/sitemap.xml b/pr-1699/sitemap.xml index cb92f7bc3f..844733c3fc 100644 --- a/pr-1699/sitemap.xml +++ b/pr-1699/sitemap.xml @@ -1 +1 @@ -https://docs.celestia.org/README2024-09-10T12:29:17.000Zhttps://docs.celestia.org/community/calendar2024-09-10T12:29:17.000Zhttps://docs.celestia.org/community/coc2024-09-10T12:29:17.000Zhttps://docs.celestia.org/community/foundation-delegation-program2024-09-10T12:29:17.000Zhttps://docs.celestia.org/community/itn-tos2024-09-10T12:29:17.000Zhttps://docs.celestia.org/community/modular-meetup-guide2024-09-10T12:29:17.000Zhttps://docs.celestia.org/community/modular-meetup-intro2024-09-10T12:29:17.000Zhttps://docs.celestia.org/community/modular-meetup-toolkit2024-09-10T12:29:17.000Zhttps://docs.celestia.org/community/overview2024-09-10T12:29:17.000Zhttps://docs.celestia.org/community/speaker-list2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/arbitrum-bridge2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/arbitrum-dapp-deploy2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/arbitrum-deploy2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/arbitrum-full-node2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/arbitrum-integration2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/arbitrum-smart-contract2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/blobstream-contracts2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/blobstream-offchain2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/blobstream-proof-queries2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/blobstream-rollups2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/blobstream-x-deploy2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/blobstream-x-requesting-data-commitment-ranges2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/blobstream2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/blobstreamx2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/bubs-testnet2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/build-whatever2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/celestia-node-key2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/deploy-on-bubs2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/ethereum-fallback2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/feegrant-for-blobs2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/full-stack-modular-development-guide2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/gm-portal-bubs2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/golang-client-tutorial2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/integrate-celestia2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/intro-to-op-stack2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/multiaccounts2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/node-api2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/node-tutorial2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/optimism-devnet2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/optimism2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/prompt-scavenger2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/rust-client-tutorial2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/sp1-blobstream-deploy2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/submit-data2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/transaction-resubmission2024-09-10T12:29:17.000Zhttps://docs.celestia.org/developers/wallets2024-09-10T12:29:17.000Zhttps://docs.celestia.org/2024-09-10T12:29:17.000Zhttps://docs.celestia.org/learn/how-celestia-works/data-availability-faq2024-09-10T12:29:17.000Zhttps://docs.celestia.org/learn/how-celestia-works/data-availability-layer2024-09-10T12:29:17.000Zhttps://docs.celestia.org/learn/how-celestia-works/monolithic-vs-modular2024-09-10T12:29:17.000Zhttps://docs.celestia.org/learn/how-celestia-works/overview2024-09-10T12:29:17.000Zhttps://docs.celestia.org/learn/how-celestia-works/transaction-lifecycle2024-09-10T12:29:17.000Zhttps://docs.celestia.org/learn/how-to-stake-tia2024-09-10T12:29:17.000Zhttps://docs.celestia.org/learn/paying-for-blobspace2024-09-10T12:29:17.000Zhttps://docs.celestia.org/learn/retrievability2024-09-10T12:29:17.000Zhttps://docs.celestia.org/learn/staking-governance-supply2024-09-10T12:29:17.000Zhttps://docs.celestia.org/learn/staking2024-09-10T12:29:17.000Zhttps://docs.celestia.org/learn/tia2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/arabica-devnet2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/bridge-node2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-app-commands2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-app-metrics2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-app-multisig2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-app-slashing2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-app-upgrade-monitor2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-app-vesting2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-app-wallet2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-app2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-node-custom-networks2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-node-metrics2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-node-troubleshooting2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-node-trusted-hash2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/celestia-node2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/config-toml2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/consensus-node2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/decide-node2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/docker-images2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/environment2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/full-storage-node2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/hardfork-process2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/ibc-relayer2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/instantiate-testnet2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/light-node2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/mainnet2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/mocha-testnet2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/overview2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/participate2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/quick-start2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/systemd2024-09-10T12:29:17.000Zhttps://docs.celestia.org/nodes/validator-node2024-09-10T12:29:17.000Z \ No newline at end of file +https://docs.celestia.org/README2024-09-10T18:13:45.000Zhttps://docs.celestia.org/community/calendar2024-09-10T18:13:45.000Zhttps://docs.celestia.org/community/coc2024-09-10T18:13:45.000Zhttps://docs.celestia.org/community/foundation-delegation-program2024-09-10T18:13:45.000Zhttps://docs.celestia.org/community/itn-tos2024-09-10T18:13:45.000Zhttps://docs.celestia.org/community/modular-meetup-guide2024-09-10T18:13:45.000Zhttps://docs.celestia.org/community/modular-meetup-intro2024-09-10T18:13:45.000Zhttps://docs.celestia.org/community/modular-meetup-toolkit2024-09-10T18:13:45.000Zhttps://docs.celestia.org/community/overview2024-09-10T18:13:45.000Zhttps://docs.celestia.org/community/speaker-list2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/arbitrum-bridge2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/arbitrum-dapp-deploy2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/arbitrum-deploy2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/arbitrum-full-node2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/arbitrum-integration2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/arbitrum-smart-contract2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/blobstream-contracts2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/blobstream-offchain2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/blobstream-proof-queries2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/blobstream-rollups2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/blobstream-x-deploy2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/blobstream-x-requesting-data-commitment-ranges2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/blobstream2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/blobstreamx2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/bubs-testnet2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/build-whatever2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/celestia-node-key2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/deploy-on-bubs2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/ethereum-fallback2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/feegrant-for-blobs2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/full-stack-modular-development-guide2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/gm-portal-bubs2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/golang-client-tutorial2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/integrate-celestia2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/intro-to-op-stack2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/multiaccounts2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/node-api2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/node-tutorial2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/optimism-devnet2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/optimism2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/prompt-scavenger2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/rust-client-tutorial2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/sp1-blobstream-deploy2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/submit-data2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/transaction-resubmission2024-09-10T18:13:45.000Zhttps://docs.celestia.org/developers/wallets2024-09-10T18:13:45.000Zhttps://docs.celestia.org/2024-09-10T18:13:45.000Zhttps://docs.celestia.org/learn/how-celestia-works/data-availability-faq2024-09-10T18:13:45.000Zhttps://docs.celestia.org/learn/how-celestia-works/data-availability-layer2024-09-10T18:13:45.000Zhttps://docs.celestia.org/learn/how-celestia-works/monolithic-vs-modular2024-09-10T18:13:45.000Zhttps://docs.celestia.org/learn/how-celestia-works/overview2024-09-10T18:13:45.000Zhttps://docs.celestia.org/learn/how-celestia-works/transaction-lifecycle2024-09-10T18:13:45.000Zhttps://docs.celestia.org/learn/how-to-stake-tia2024-09-10T18:13:45.000Zhttps://docs.celestia.org/learn/paying-for-blobspace2024-09-10T18:13:45.000Zhttps://docs.celestia.org/learn/retrievability2024-09-10T18:13:45.000Zhttps://docs.celestia.org/learn/staking-governance-supply2024-09-10T18:13:45.000Zhttps://docs.celestia.org/learn/staking2024-09-10T18:13:45.000Zhttps://docs.celestia.org/learn/tia2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/arabica-devnet2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/bridge-node2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-app-commands2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-app-metrics2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-app-multisig2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-app-slashing2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-app-upgrade-monitor2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-app-vesting2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-app-wallet2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-app2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-node-custom-networks2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-node-metrics2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-node-troubleshooting2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-node-trusted-hash2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/celestia-node2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/config-toml2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/consensus-node2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/decide-node2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/docker-images2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/environment2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/full-storage-node2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/hardfork-process2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/ibc-relayer2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/instantiate-testnet2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/light-node2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/mainnet2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/mocha-testnet2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/overview2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/participate2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/quick-start2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/systemd2024-09-10T18:13:45.000Zhttps://docs.celestia.org/nodes/validator-node2024-09-10T18:13:45.000Z \ No newline at end of file