Problemi con la reimpostazione del libro mastro HWM
1 risposta
- voti
-
- 2019-02-27
L'indirizzo del libromastro richiestoperil comando
set ledger high watermark
è quelloelencatotramiteil comando:$ ./tezos-client list connected ledgers Found a Tezos Baking 1.5.0 (commit v1.4.3-21-gf3071161) application running on Ledger Nano S at [0001:001d:00]. To use keys at BIP32 path m/44'/1729'/0'/0' (default Tezos key path), use one of tezos-client import secret key ledger_<username> "ledger://<animal>/ed25519/0'/0'" tezos-client import secret key ledger_<username> "ledger://<animal>/secp256k1/0'/0'" tezos-client import secret key ledger_<username> "ledger://<animal>/P-256/0'/0'
Quindi la seconda cosa che haiprovato èilmetodo corretto:
$ ./tezos-client set ledger high watermark for "ledger://<animal>/ed25519/0'/0'" to 0
Detto questo,l'errore che ricevi di solito significa chenon hai confermato conil libromastrofisico che lamodifica dellafiligrana è consentita. In altreparole,potrestinon averpremutoilpulsante sul libromastroper confermare lamodifica. Sì,c'è una conferma fisica sul libromastronecessariapermodificareil limitemassimo. Questopresumibilmente èperimpedire a qualcuno con accesso alla shell senza accessofisico al libromastro di causare una doppia cottura/approvazione.
The ledger address required for the
set ledger high watermark
command is what is listed via the command:$ ./tezos-client list connected ledgers Found a Tezos Baking 1.5.0 (commit v1.4.3-21-gf3071161) application running on Ledger Nano S at [0001:001d:00]. To use keys at BIP32 path m/44'/1729'/0'/0' (default Tezos key path), use one of tezos-client import secret key ledger_<username> "ledger://<animal>/ed25519/0'/0'" tezos-client import secret key ledger_<username> "ledger://<animal>/secp256k1/0'/0'" tezos-client import secret key ledger_<username> "ledger://<animal>/P-256/0'/0'
So the second thing you tried is the correct method:
$ ./tezos-client set ledger high watermark for "ledger://<animal>/ed25519/0'/0'" to 0
That said, the error you are receiving usually means you haven't confirmed with the physical ledger that the watermark change is allowed. In other words, you may not have pressed the button on the ledger to confirm the change. Yes, there is a physical confirmation on the ledger required to change the high watermark. This is presumably to prevent someone with shell access without physical access to the ledger to cause double baking/endorsing.
-
♂️era sicuramente la conformazionefisica Avresti dovuto vedermiprendere apugniil comandoe correre atutta velocità dallamia scrivania alla sala serverper confermare Grazie !!♂️ it was the physical conformation for sure You should have seen me punching in the command and running full speed from my desk to the server room to confirm Thanks!!
- 1
- 2019-02-27
- asbjornenge
-
Cordiali saluti,"autorizza libromastro a cuocere"non è richiestoperché "impostafiligrana alta del registro"funzioniFYI `authorize ledger to bake` is not required for `set ledger high watermark` to work
- 0
- 2019-02-28
- Elliot Cameron
-
Grazie @ElliotCameron,ho rimosso quelpezzo di risposta.Thanks @ElliotCameron, I removed that piece of the answer.
- 0
- 2019-02-28
- Frank
Stoprovando a reimpostare l'applicazione di cottura a libromastro HWM (high watermark)perprepararlaperil ripristino di zeronet.
Provandoil ledgertz1 addr ottengo:
Provandoilnome dell'animale ottengo:
Ottenere l'HWMfunziona,ma soloper l'URI animale ♂️