Doc: small fixes
This commit is contained in:
parent
c1ea259dd9
commit
7d681f66e3
@ -327,13 +327,11 @@ For instance:
|
|||||||
$ tezos-client rpc get /chains/main/blocks/head/metadata
|
$ tezos-client rpc get /chains/main/blocks/head/metadata
|
||||||
"protocol": "Ps9mPmXaRzmzk35gbAYNCAw6UXdE2qoABTHbN2oEEc1qM7CwT9P"
|
"protocol": "Ps9mPmXaRzmzk35gbAYNCAw6UXdE2qoABTHbN2oEEc1qM7CwT9P"
|
||||||
|
|
||||||
|
|
||||||
We now have the possibility to send transactions to the sandboxed network.
|
We now have the possibility to send transactions to the sandboxed network.
|
||||||
As the genesis block used to initialize the sandboxed network differs from the
|
As the genesis block used to initialize the sandboxed network differs from the
|
||||||
one used in Alphanet and Zeronet, it is not possible to use the faucet to obtain
|
one used in Alphanet and Zeronet, it is not possible to activate
|
||||||
free Tezzies. However, we can use the preconfigured accounts.
|
accounts obtained from the faucet. However, we can use the
|
||||||
|
preconfigured accounts which can be listed with:
|
||||||
Let's check the list of existing accounts:
|
|
||||||
|
|
||||||
::
|
::
|
||||||
|
|
||||||
@ -346,34 +344,30 @@ Let's check the list of existing accounts:
|
|||||||
bootstrap2: tz1gjaF81ZRRvdzjobyfVNsAeSC6PScjfQwN (unencrypted sk known)
|
bootstrap2: tz1gjaF81ZRRvdzjobyfVNsAeSC6PScjfQwN (unencrypted sk known)
|
||||||
bootstrap1: tz1KqTpEZ7Yob7QbPE4Hy4Wo8fHG8LhKxZSx (unencrypted sk known)
|
bootstrap1: tz1KqTpEZ7Yob7QbPE4Hy4Wo8fHG8LhKxZSx (unencrypted sk known)
|
||||||
|
|
||||||
We can run the following command to transfer some Tezzies from one account to
|
We can run the following command to transfer some Tez from one account to
|
||||||
another:
|
another:
|
||||||
|
|
||||||
::
|
::
|
||||||
|
|
||||||
shell1~$ tezos-client transfer 42 from bootstrap1 to bootstrap2
|
$ tezos-client transfer 42 from bootstrap1 to bootstrap2 &
|
||||||
...
|
...
|
||||||
Waiting for the operation to be included...
|
Waiting for the operation to be included...
|
||||||
|
|
||||||
|
You will notice that this command doesn't terminate (hence the ``&``),
|
||||||
However, we need one more step to include the transaction in the
|
as usual it is waiting for the network to include the transaction in a
|
||||||
chain, we need somebode to bake it in a block.
|
block.
|
||||||
To do so, we can run the following command in a new shell (``shell2``):
|
Given that we are in a sandbox we need to bake a block ourselves and
|
||||||
|
we can do so with the following command:
|
||||||
|
|
||||||
::
|
::
|
||||||
|
|
||||||
shell2~$ tezos-client bake for bootstrap1
|
$ tezos-client bake for bootstrap1
|
||||||
|
|
||||||
If the previous transaction is valid, the operation is baked and included in the
|
|
||||||
chain. We obtain the following output in ``shell1``:
|
|
||||||
|
|
||||||
::
|
|
||||||
|
|
||||||
shell1~$ ...
|
|
||||||
Operation found in block: BKt5P9WuUcG5CioQbpn13gUiCWEWCEdcG6JGzNFrCHrHtLHVfh8 (pass: 3, offset: 0)
|
|
||||||
This sequence of operations was run:
|
|
||||||
...
|
|
||||||
|
|
||||||
|
If the previous transaction is valid, the operation is included in the
|
||||||
|
chain and the transfer terminates returning the usual ticket.
|
||||||
|
Note that the ``bake for`` command of the client is exclusively for
|
||||||
|
testing purposes, all baking should be done using the ``tezos-baker``
|
||||||
|
binary.
|
||||||
|
|
||||||
|
|
||||||
Tune protocol alpha parameters
|
Tune protocol alpha parameters
|
||||||
|
Loading…
Reference in New Issue
Block a user