Don

There are tests for the main protocol and some unit tests for features, but we should try to get this up to a nice standard of testing and rustdoc Also...

Magi as a sequencer

1

# Description Determine what needs to be done to use magi as a sequencer. # Additional info The original op-node is incredibly unreliable, with panics and null pointers in most...

- docker images previously not exposed

Maybe full node that is returning commitments

We are reimplementing a bunch of stuff `near-fetch` already has - Ideally we just contribute work there (unless they're using incompatible runtimes), but we should try to reach a sovereign...

Push da-rpc-go to the go pkgs repo

1

blocks https://github.com/near/rollup-data-availability/issues/30 blocks https://github.com/near/rollup-data-availability/issues/29 Also needs to do this on CI pull request merge. ```[tasklist] ### Tasks ```

We want to keep the light client a black box and apply extensions to its capabilities with near DA. At its current state, we write the extensions onto it. Expose...

Right now the unit tests for FFI & the DA client make real rpc queries, we ought to mock them and return the data ready for testing in CI blocks...

It's relatively easy to do, we don't quite need it right now and introduces actor complexity for submitting headers, proofs and such.

**Is your feature request related to a problem? Please describe.** For non-NEAR natives, creating an account's a slight entry barrier. It would be helpful if we ran a `near-cli-rs` docker...