Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert avail DA to use quick start guide #484

Open
4 tasks
Tracked by #483
MSevey opened this issue Oct 8, 2024 · 3 comments
Open
4 tasks
Tracked by #483

Convert avail DA to use quick start guide #484

MSevey opened this issue Oct 8, 2024 · 3 comments
Assignees

Comments

@MSevey
Copy link
Contributor

MSevey commented Oct 8, 2024

Tasks

  1. needs-triage
@MSevey MSevey self-assigned this Oct 8, 2024
@MSevey
Copy link
Contributor Author

MSevey commented Oct 8, 2024

Update Run Avail Light Node

Updated the docs on local branch to reference avail documentation.
Running light client with availup
Lock in turing testnet
Seems that you can just submit blocks and don't need to fund an address?

Try moving right to quickstart

@MSevey
Copy link
Contributor Author

MSevey commented Oct 8, 2024

Quick Start vs GM

It seems that the main difference from a tutorial perspective between the quick start and GM is how the go-da interface is used.
Quick start works for nodes that integrate go-da directly, i.e. local da and celestia node.
GM is needed for avail because avail light clients don't have go-da integrated directly, but use avail-da implementation of go-da.

@MSevey
Copy link
Contributor Author

MSevey commented Oct 8, 2024

Update

The tutorial needs to be updated to make it more clear that you need to be running an Avail Light Client and the Avail DA server.

The DA tutorial section could use an overview page that explains this as well and how some DAs like celestia can integrate go-da directly, vs other DAs that need a DA server to proxy the interface.

Running the avail tutorial against the Turing testnet gives DA submission errors rollkit/avail-da#57

Running locally is a pain.... lots of nodes to run, long install times...

I've made some updates on a branch to the avail tutorials to track some of these changes but waiting to push them until I have it working either locally or on Turing testnet.

Need to confirm if the DA submission issues are just with the Turing testnet.
If they are with local as well, then we should remove any reference to local development and just use the turing testnet for simplicity.
EDIT: running locally is too much of a pain. Managing multiple nodes. Rollkit should only deal with testnets

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant