Julien/documentation improvement
This commit is contained in:
parent
e61de64474
commit
f4e07221f1
@ -36,8 +36,15 @@ originating a contract the delegate is not set by default.
|
||||
If you already own contracts that are delegatable you can change
|
||||
the delegate with the command ``set delegate``.
|
||||
|
||||
|
||||
Notice that, by default, an originated account is not *delegatable*,
|
||||
which means that you can't change the delegate once the contract is
|
||||
originated, even if you initially set a delegate.
|
||||
To be able to change the delegate latter, add the
|
||||
``--delegatable`` flag.
|
||||
|
||||
Notice that only implicit accounts can be delegates, so your delegate
|
||||
must by a *tz1* address.
|
||||
must be a *tz1* address.
|
||||
|
||||
Funds in implicit accounts which are not registered as delegates
|
||||
do not participate in baking.
|
||||
|
@ -92,7 +92,7 @@ The preferred way to set up your Ledger is to install the `Ledger
|
||||
Manager extension
|
||||
<https://chrome.google.com/webstore/detail/ledger-manager/beimhnaefocolcplfimocfiaiefpkgbf>`_
|
||||
on a Chrome browser.
|
||||
On Linux makes sure you correctly set up your `udev` rules as explained
|
||||
On Linux make sure you correctly set up your `udev` rules as explained
|
||||
`here <https://github.com/obsidiansystems/ledger-app-tezos#udev-rules-linux-only>`_.
|
||||
Connect your ledger, unlock it and go the dashboard.
|
||||
In the Ledger Manager enable `developer items` in the bottom right,
|
||||
@ -172,7 +172,7 @@ operations.
|
||||
For example we could have a set up with two nodes, a private one
|
||||
connected uniquely with a public one.
|
||||
The public node runs on a VPS, connects normally to the network and
|
||||
keeps a up to date state of the network while the private node runs at
|
||||
keeps an up to date state of the network while the private node runs at
|
||||
your home and is in charge of injecting and signing operations with a
|
||||
hardware wallet.
|
||||
|
||||
@ -254,7 +254,7 @@ guaranteed authenticity and integrity.
|
||||
This set up **does not guarantee confidentiality**, an evesdropper can
|
||||
see the transactions that you sign but on a public blockchain this is
|
||||
less of a concern.
|
||||
You can still use the ``https`` scheme or the tunnel to encrypt you
|
||||
You can still use the ``https`` scheme or the tunnel to encrypt your
|
||||
traffic.
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user