Hot answers tagged

5

Yes, there are various open-source projects that you can use for this: Some examples: TzStats TzKt TezBlock


3

You can use Tplus, it's a tool that helps you manage tezos environments ( sandboxes and public nodes ) for use for development on top of Tezos.


3

You can use Tezster-CLI to set up your local sandbox environment. You can use it along with Bundle-react (Like truffle box) to deploy and test.


2

It's a bug in the tezos-packaging repository. We have fixed it in the v7.1-2 release. Can you please try again with v7.1-2 or newer? You can run wget https://github.com/serokell/tezos-packaging/releases/latest/download/tezos-client to overwrite the version you have, it should work because it downloads the latest release (where the bug is fixed).


2

If you want to create private testnets, you definitely should look at tezos-k8s. It's an easy-to-use tool to quickly deploy testnets based on the Kubernetes infrastructure. Just follow the steps given in the link. Basically, a testnet on your machine could be associated with a namespace that contains pods. Each pod stands for a (baking or not) node, and each ...


2

Yes, the old testing networks are abandoned and brand new networks are launched using the new to-be-activated protocol. For instance, Carthagenet will be deactivated on 12/12/2020. The current Delphinet test network will remain as a protocol copy of mainnet. Edonet was launched yesterday, which is using the upcoming beta 008 protocol.


1

As the error message quite clearly states, you need to stop the container and remove the lock file inside the data directory. Did you bind-mount external directories into your container or just using default storage? Please show us the entire command you used.


1

Edonet should be dead as that protocol was not chosen. I imagine tzkt simply has not shut it down yet. Edo2Net should be the current testnet.


1

The error message is meaningless for a tricky reason (a fixpoint is badly computed leading the error reporting mechanism to raises an error itself: https://gitlab.com/tezos/tezos/-/merge_requests/1376 ) Anyway, the root of your problem is probably that you don't have the right activator key. The public key of the activator is defined line 105 of src/...


Only top voted, non community-wiki answers of a minimum length are eligible