Closing as won't do. @Wondertan and I discussed synchronously and it doesn't make sense to expose this struct. We did briefly discuss a blob module that would have a simplified API: Get and Put but the node team will explore that separately.

Context

https://github.com/celestiaorg/celestia-node/pull/1526/files#r1092112081

Question

Should celestia-node offer an endpoint that returns share sequences?

Details

At the moment, celestia-node has endpoints to return raw share data or parsed blob data. Is there a use case where a client would want share sequences (the intermediate stage between raw share data and parsed blob data)? If users need it, they could trivially parse raw share data into share sequences using the sequence start indicator.

Context

https://github.com/celestiaorg/celestia-node/pull/1526/files#r1092112081

Question

Should celestia-node offer an endpoint that returns share sequences?

Details

At the moment, celestia-node has endpoints to return raw share data or parsed blob data. Is there a use case where a client would want share sequences (the intermediate stage between raw share data and parsed blob data)? If users need it, they could trivially parse raw share data into share sequences using the sequence start indicator.

feat: bump arabica chain-id and genesis hash (#1645)

Overview

Checklist

• [ ] New and updated code has appropriate documentation
• [ ] New and updated code has new and/or updated testing
• [ ] Required CI checks are passing
• [ ] Visual proof for any user facing features like CLI or documentation updates
• [ ] Linked issues closed with keywords

chore(nodebuilder/p2p): Update Arabica kaarina peerID (#1650)

fix(core/listener): Only broadcast datahash if core node is not syncing (#1652)

Fixes a bug found in implementation of datahash broadcasting in bridge nodes -- now bridge nodes will only broadcast a hash if its connected core node is synced up.

nodebuilder: make proxy constructors private in all modules (#1643)

fix(share/discovery): decouple peer discovery from event processing (#1639)

Overview

Starting to listen to subscriptions async will help us to avoid any blocking in the case when we will not have the needed amount of FNs and will be blocked in FindPeers.

Checklist

• [x] New and updated code has appropriate documentation
• [x] New and updated code has new and/or updated testing
• [x] Required CI checks are passing
• [x] Visual proof for any user facing features like CLI or documentation updates
• [x] Linked issues closed with keywords

Co-authored-by: rene 41963722+renaynay@users.noreply.github.com

fix(libs/header/sync): Make ranges.Add thread-safe (#1649)

chore: upgrade to celestia-app 0.12.0-rc4 (#1648)

Upgrade to celestia-app 0.12.0-rc4 to unblock #1526

Co-authored-by: Hlib Kanunnikov hlibwondertan@gmail.com

Merge branch 'main' into rp/fix-namespaced-data

chore(deps): Bump actions/cache from 3.2.3 to 3.2.4 (#1316)

Bumps actions/cache from 3.2.3 to 3.2.4.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps actions/cache from 3.2.3 to 3.2.4.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

We don't want to upgrade to nmt 0.13.0 until this is resolved https://github.com/celestiaorg/celestia-node/pull/1651

I am also starting tests via "Run Test" in codelens. I'm only running one test at a time. Do you see historical test output if you scroll up in the bottom pane?

if we wanted to get a little fancy, we could also modify an existing "fuzzing" integration test that is already generating random block data, to also test reconstruction.

I'm concerned the existing "fuzzing" test that tests reconstruction doesn't actually generate pay for blob txs here

chore: rename reconstruct to merge