Namespace Pinning Issue 2830 Celestiaorg Celestia Node Github

Namespace Pinning Issue 2830 Celestiaorg Celestia Node Github We should support the ability to allow nodes to "pin" namespaces, so that they automatically download all the data in that namespace, and also advertise themselves on the network that they have pinned that namespace, so other nodes that are querying for data by namespace can download that data. Golang implementation of celestia's data availability node types (light | full | bridge). the celestia node types described above comprise the celestia data availability (da) network.

Namespace Celestia App Specifications Contribute to celestiaorg celestia node development by creating an account on github. Celestia's blocks are sharded with namespaces in a way that you can access only a specific part of a block over the network from the full node. similarly, some nodes can only store specific parts of the block and not all the parts for reasons like disk usage optimization. Problem there is no way for a user to override the namespaceversion of their blob when using celestia node's gateway api endpoint for submit pfb. Iirc celestia node doesn't want to adopt the existing celestia app namespace type because of performance reasons. if that's the case, celestia node can define a new type namespace: []byte in this repo and convert back and forth using from and bytes.

Panic Addrfactory Issue 232 Celestiaorg Celestia Node Github Problem there is no way for a user to override the namespaceversion of their blob when using celestia node's gateway api endpoint for submit pfb. Iirc celestia node doesn't want to adopt the existing celestia app namespace type because of performance reasons. if that's the case, celestia node can define a new type namespace: []byte in this repo and convert back and forth using from and bytes. I think for better dev ux we should also modify the celestia node rpc so that it rejects pfbs with invalid namespaces that will be rejected by the consensus network? eg invalid namespace version, or does not have 22 leading zeros. When interacting with a celestia 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. 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. A new namespace version must be introduced if the namespace format changes in a backwards incompatible way. below we explain supported user specifiable namespace versions, however, we note that celestia may utilize other namespace versions for internal use.