-
Сейчас в go-cyber есть команда
```
cyber query rank is-exist [from] [to] [account] [flags]
```
Эта команда проверяет наличие киберлинка с адреса конкретного нейрона без учета времени, когда эт…
-
### Update
This issue is superseded by two byproduct issues which propose new changes to address the original problems outlined in this issue:
- https://github.com/celestiaorg/celestia-app/issue…
-
Currently, we are creating the share commitments by taking a normal merkle root over the nmt subtree roots. We should use an nmt over the subtree roots as well.
-
RON ops certainly have some redundancy. The op specifier consists of four UUIDs: type, object, event and location ids, which may be derived from each other in many cases.
Indeed, having the objec…
-
## Overview
### Use case
As an on-chain lightclient I would like to verify blob inclusion against the `dataHash` (data availability root) tracked in celestia-core commit headers.
For example,…
-
with #137, we are now using the rust sequencer. however, the transaction verification was removed to be done with this task.
Summary:
- when pulling transactions from DA in the conductor, we need to …
-
I'm reading over the overview draft (really exciting!) and I'd like to brainstorm how containers fit into this model. Right now we have them as a part of composition:
> Bindmount libraries into con…
vsoch updated
3 years ago
-
Hi,
I have a question about the API. When it comes to proving, in Go implementation I can see [those](https://github.com/celestiaorg/nmt/blob/master/proof.go#L361) methods:
```go
// VerifyNamespace…
-
In the sequencer block, we need an NMT namespaced by `VM ID` so that rollups can easily prove inclusion of transactions that belong to them.
-
Based on [this](https://github.com/celestiaorg/celestia-node/issues/2377) we may run in a situation when shares will be out of order in the dataSquare. In this case, we will not be able to compute the…