Nguyen Nhu Viet
Nguyen Nhu Viet
Hey @massi-ag Currently, there are no plans in having a c++ sdk for testground. If you still want to use your c++ binary for testing - then you can wrap...
Hi @Boruson Can you please provide more info on this question? Thanks in advance
running into issues CLI command to start: ``` celestia light start --p2p.network mocha --core.grpc.host grpc-mocha.pops.one --core.rpc.host https://rpc-mocha.pops.one/ --core.rpc.port 443 ``` Then I try to `celestia state account-address --token $CEL_AUTH_TOKEN` Which...
```bash $ celestia light start --p2p.network mocha --core.grpc.host grpc-mocha.pops.one --core.rpc.host full.consensus.mocha-4.celestia-mocha.com $ export CEL_AUTH_TOKEN=$(celestia light auth admin --p2p.network mocha) $ celestia state account-address --token $CEL_AUTH_TOKEN ``` both endpoints are not...
``` celestia light start --p2p.network mocha --core.grpc.host consensus-full-mocha-4.celestia-mocha.com --core.rpc.host rpc-mocha.pops.one --core.rpc.port 443 --core.rpc.https # or celestia light start --p2p.network mocha --core.grpc.host consensus-full-mocha-4.celestia-mocha.com --core.rpc.host rpc.celestia-mocha.com --core.rpc.port 443 --core.rpc.https ``` produces these...
@ramin ``` celestia light start --p2p.network mocha --core.grpc.host grpc-mocha.pops.one --core.rpc.host rpc.celestia-mocha.com --core.rpc.https --core.rpc.port 443 ``` produces this error ``` celestia state balance --token $CEL_AUTH_TOKEN --node.store ~/.celestia-light-mocha-4/ { "result": "post failed:...
> @Bidon15 Do you still want this PR for BNs ? We will be removing need for rpc flag for FNs and LNs in v0.14.0, but likely not for BNs...
Yes, the follow-up is here https://github.com/celestiaorg/celestia-node/pull/3359
In addition, we have found that straight after auto-scaling process is complete -> some test pods can be killed on the first run, but not (which means the whole setup...
So some sample use-cases can be the following: 1. I want to submit blobs through typical DevX without the keyring backend hosted in my app env. 2. Any 3rd party...