Hlib Kanunnikov

Results 126 issues of Hlib Kanunnikov

## Context The purpose of `share.CacheAvailability` is to keep track of DataRoots that were already sampled, not to redo this again. The introduced `EDSStore` tracks state on its own and...

area:shares

## Context To serve data over the wire the CAR format is chosen, so we need to have a utility that packs the namespaced data into the CAR. ## Implemenation...

area:shares

## Context We want FN/BNs to serve data by namespace as a whole. For that, we need to read Merkle proofs while getting data by namespace so that requestors can...

area:shares

## Context The empty block is valid and small EDS. It can happen in the early stage of the network. Its body is constant, and to avoid transferring it over...

area:shares

## Context Once EDSStore is implemented, we should add it to the DI on the Node in `node/share` module. ## Refs Depends on #1107

area:shares

At a high level, we have validation and verification. * [Validation](https://github.com/celestiaorg/celestia-node/blob/main/header/header.go#L112) checks the integrity of all the fields in the deserialized header. Essentially comparing correspondence between RawHeader, Commit, and ValidatorSet...

documentation

Prototype of the new storage for edses - edsfile and optimized roundtrip less ipldv2 protocol TODO: - edsfile - [x] Blockstore over EDSFile - [x] Support for Col sample reads...

## Problem We have to specify `node.store` flag every time we want to do an RPC request, but it should be possible to detect running instance automatically. I am currently...

good first issue

Introduces Shwap page that points to [the CIP](https://github.com/celestiaorg/CIPs/pull/77). This PR integrates it nicely with mdbook engine like it is a local document in the node. It integrates multiple mdbook preprocessors...

kind:docs
specs

After deep discussions with @jbowen93 about https://github.com/celestiaorg/celestia-node/issues/3129, the Astria team figured that there was a bug on their side, causing LNs to be spammed with ~1k req/s, subsequently causing RAM...

area:rpc