We changed our privacy policy. Read more.

Hot answers tagged

9

Disclaimer - i'm the author of the project below I've put together a toolkit that allows you to run a locally sandboxed tezos chain for development, together with liquidity & tzscan preinstalled. You can check it out here. If you have any questions, or the readme isn't clear, i'd be happy to clarify any details!.


6

Which protocol is indicated in: tezos-client -A <your-node> rpc get /chains/main/blocks/head/header It is likely that it switched to protocol 002 (instead of 003), and that your client does not include the bake command for 002. It is hardcoded in the sources (since there were no votes at the time) that, after a given number of blocks, the node should ...


3

You can use the sandboxed baker using the tezos-baker-alpha binary. To do so, run ./tezos-baker-alpha -P 18731 run with local node /path/to/generated/data_dir where both the node's rpc and generated data directory should be logged in the sandobxed node logs. I recommend using a persistent and static data directory to avoid copy/pasting the path at each run. ...


2

In sandboxed mode, if you want to change the default parameters (balances, time between blocks, blocks per voting period, …) you can edit the sandbox-parameters.json file (located at the root of the repository).


2

DUH: tezos-client activate protocol PsddFKi32cMJ2qPjf43Qv5GDWLDPZb3T3bF6fLKiF5HtvHNU7aP with fitness 24 and key dictator and parameters ../mysandbox.json


2

Accounts are pre-created in Sandboxed mode, this shows how to find the secret keys: $ grep SECRET src/bin_client/tezos-init-sandboxed-client.sh export BOOTSTRAP1_SECRET="unencrypted:edsk3gUfUPyBSfrS9CCgmCiQsTCHGkviBDusMxDJstFtojtc1zcpsh" export BOOTSTRAP2_SECRET="unencrypted:edsk39qAm1fiMjgmPkw1EgQYkMzkJezLNewd7PLNHTkr6w9XA2zdfo" export BOOTSTRAP3_SECRET="...


2

Accounts are pre-created in Sandboxed mode, this shows how to find the secret keys: $ grep SECRET src/bin_client/tezos-init-sandboxed-client.sh export BOOTSTRAP1_SECRET="unencrypted:edsk3gUfUPyBSfrS9CCgmCiQsTCHGkviBDusMxDJstFtojtc1zcpsh" export BOOTSTRAP2_SECRET="unencrypted:edsk39qAm1fiMjgmPkw1EgQYkMzkJezLNewd7PLNHTkr6w9XA2zdfo" export BOOTSTRAP3_SECRET="...


2

Interesting that docker would send the end-of-file to the sandbox. I'll look into a nicer solution but for now, with recent versions of flextesa, you can start the mini-net with --until-level option which is not interactive. E.g. --until-level 20_000_000 should last a couple of years :)


2

You can also use tezos-sandbox mini-net to run full network sandboxes with bakers, endorsers, etc. → https://tezos.gitlab.io/developer/flextesa.html & tezos-sandbox mini-net --help


2

You can use an address "KT1..." or "KT1...%entry_point". The chain is then in charge of type checking and converting to the contract type.


1

The error means that a nonce commitment should have been included in the block, but it was not (or the other way around, it was included, but it was not expected to be included). See here for details: http://tezos.gitlab.io/whitedoc/proof_of_stake.html#random-seed. In sandbox mode, a nonce commitment should be included every 4 blocks, as far as I understand. ...


1

You can open emacs in the same terminal as you ran: eval `./src/bin_client/tezos-init-sandboxed-client.sh 1` When running this script, a path corresponding to the sandbox tezos-client (it looks like /tmp/tezos-tmp-client.XXXXXXX/bin) is added to the PATH env variable. Alternatively, you may want to use the following command (with the correct path) in ...


1

After you initialize the sandboxed client, running which tezos-client command will give you the absolute path for the sandboxed client. In Emacs you can then set the variable michelson-client-command to this path.


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