sovereign-labs / sov-rollup-starter Goto Github PK

View Code? Open in Web Editor NEW

16.0 3.0 4.0 423 KB

License: Apache License 2.0

Rust 68.82% Makefile 9.73% Shell 21.45%

sov-rollup-starter's Introduction

This package is a convenient starting point for building a rollup using the Sovereign SDK:

The repo structure:

crates/stf: The STF is derived from the Runtime and is used in the rollup and provers crates.
crates/provers: This crate is responsible for creating proofs for the STF.
crates/rollup: This crate runs the STF and offers additional full-node functionalities.

How to run the sov-rollup-starter:

1. Change the working directory:

$ cd crates/rollup/

2. If you want to run a fresh rollup, clean the database:

$ make clean-db

3. Start the rollup node:

This will compile and start the rollup node:

$ cargo run --bin node

4. Submit a token creation transaction to the `bank` module:

$ make test-create-token

5. Wait for the transaction to be submitted.

$ make wait-ten-seconds

6. Test if token creation succeeded:

$ make test-bank-supply-of

7. The output of the above script:

$ curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"bank_supplyOf","params":{"token_address":"sov1zdwj8thgev2u3yyrrlekmvtsz4av4tp3m7dm5mx5peejnesga27svq9m72"},"id":1}' http://127.0.0.1:12345
{"jsonrpc":"2.0","result":{"amount":1000},"id":1}

How to run the sov-rollup-starter using celestia-da:

1. Change the working directory:

$ cd crates/rollup/

2. If you want to run a fresh rollup, clean the database:

$ make clean

3. Start the Celestia local docker service:

$ make start

4. Start the rollup node with the feature flag building with the celestia adapter:

This will compile and start the rollup node:

$ cargo run --bin node --no-default-features --features celestia_da

5. Submit a token creation transaction to the `bank` module:

Using CELESTIA=1 will enable the client to be built with Celestia support and submit the test token

$ CELESTIA=1 make test-create-token

6. Test if token creation succeeded:

$ make test-bank-supply-of

7. The output of the above script:

$ curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"bank_supplyOf","params":{"token_address":"sov1zdwj8thgev2u3yyrrlekmvtsz4av4tp3m7dm5mx5peejnesga27svq9m72"},"id":1}' http://127.0.0.1:12345
{"jsonrpc":"2.0","result":{"amount":1000},"id":1}

sov-rollup-starter's People

Contributors

Stargazers

Watchers

Forkers

btcleet orchidtexture cryptomaestro2888 nitro-svm

sov-rollup-starter's Issues

Risc0 patch for `sha2` crate is unused

The Risc0 patch for sha2 inside Cargo.toml files is unused. This is evident in the generated Cargo.lock files, which place the patched version of sha2 in the [[patch.unused]] section.

Failed to compile

Hey,

Trying to run this repo as mentioned in the README:

➜ cargo run --bin node
    Updating git repository `https://github.com/neysofu/risc0-hotfixes`
    Updating crates.io index
    Updating git repository `https://github.com/Sovereign-Labs/sovereign-sdk.git`
    Updating git repository `https://github.com/eigerco/celestia-node-rs.git`
    Updating git repository `https://github.com/Sovereign-Labs/nmt-rs.git`
    Updating git repository `https://github.com/eigerco/celestia-tendermint-rs.git`
    Updating git repository `https://github.com/penumbra-zone/jmt.git`
error: failed to select a version for `tendermint`.
    ... required by package `celestia-types v0.1.0 (https://github.com/eigerco/celestia-node-rs.git?rev=66b7c6c#66b7c6cd)`
    ... which satisfies git dependency `celestia-types` of package `celestia-rpc v0.1.0 (https://github.com/eigerco/celestia-node-rs.git?rev=66b7c6c#66b7c6cd)`
    ... which satisfies git dependency `celestia-rpc` of package `sov-celestia-adapter v0.3.0 (https://github.com/Sovereign-Labs/sovereign-sdk.git?rev=13e4077c329ff14954b32e3180d43a6d86fa3172#13e4077c)`
    ... which satisfies git dependency `sov-celestia-adapter` of package `sov-rollup-starter v0.3.0 (/home/rakan/Work/Sovereign/sov-rollup-starter/crates/rollup)`
versions that meet the requirements `*` are: 0.32.0

the package `celestia-types` depends on `tendermint`, with features: `instant` but `tendermint` does not have these features.
 It has an optional dependency with that name, but that dependency uses the "dep:" syntax in the features table, so it does not have an implicit feature with that name.


failed to select a version for `tendermint` which could resolve this conflict

I'll try to look into this but thought i would report this error as well.

`mock_da` feature is required to run tests for `sov-rollup-starter`

The feature mock_da is enabled by default in the sov-rollup-starter template. When trying to change the default feature to celestia_da, it would result in various compile errors in the test crate.

Some adjustments should be made so that disabling mock_da won't result in compile failure of the tests. For example, the tests can require the sov-mock-da crate non-optionally, or mock tests are made to only compile behind cfg flag if the mock_da feature is enabled.

Test `Celestia` setup in CI

We should test the Celestia setup the same way we test MockDa

sovereign-labs / sov-rollup-starter Goto Github PK

sov-rollup-starter's Introduction

The repo structure:

How to run the sov-rollup-starter:

1. Change the working directory:

2. If you want to run a fresh rollup, clean the database:

3. Start the rollup node:

4. Submit a token creation transaction to the bank module:

5. Wait for the transaction to be submitted.

6. Test if token creation succeeded:

7. The output of the above script:

How to run the sov-rollup-starter using celestia-da:

1. Change the working directory:

2. If you want to run a fresh rollup, clean the database:

3. Start the Celestia local docker service:

4. Start the rollup node with the feature flag building with the celestia adapter:

5. Submit a token creation transaction to the bank module:

6. Test if token creation succeeded:

7. The output of the above script:

sov-rollup-starter's People

Contributors

Stargazers

Watchers

Forkers

sov-rollup-starter's Issues

Recommend Projects

Recommend Topics

Recommend Org

4. Submit a token creation transaction to the `bank` module:

5. Submit a token creation transaction to the `bank` module: