Tjyylli

Why are the books in the Game of Thrones citadel library shelved spine inwards?

After checking in online, how do I know whether I need to go show my passport at airport check-in?

Is using an 'empty' metaphor considered bad style?

How do I prevent a homebrew Grappling Hook feature from trivializing Tomb of Annihilation?

Should I reinstall Linux when changing the laptop's CPU?

Why does photorec keep finding files after I have filled the disk free space as root?

A starship is travelling at 0.9c and collides with a small rock. Will it leave a clean hole through, or will more happen?

Why do neural networks need so many training examples to perform?

How to not let the Identify spell spoil everything?

Why don't key signatures indicate the tonic?

Play Zip, Zap, Zop

Does Skippy chunky peanut butter contain trans fat?

"We can't save the customer" error after Migration - Magento 2.3

Why would space fleets be aligned?

What makes papers publishable in top-tier journals?

Does dispel magic end a master's control over their undead?

"on its way" vs. "in its way"

I have trouble understanding this fallacy: "If A, then B. Therefore if not-B, then not-A."

How does Leonard in "Memento" remember reading and writing?

What to look for when criticizing poetry?

GRASS not working with QGIS 3.6

Square Root Distance from Integers

Python Pandas - difference between 'loc' and 'where'?

Building an exterior wall within an exterior wall for insulation

Issues resetting the ledger HWM

2

I'm trying to reset the ledger baking application HWM (high watermark) to prepare it for the reset zeronet.

Trying the ledger tz1 addr I get:

./tezos-signer set ledger high watermark for "ledger://<tz1...>" to 0

Error:

  No Ledger found for <tz1...>

Trying the animal name thing I get:

./tezos-signer set ledger high watermark for "ledger://<animal>/ed25519/0'/0'" to 0

Error:

  Ledger Application level error (set_high_watermark): Conditions of use not satisfied

Getting the HWM works, but only for the animal uri 🤷‍♂️

ledger high-watermark

share|improve this question

asked 4 hours ago

asbjornengeasbjornenge

600112

add a comment | 

2

I'm trying to reset the ledger baking application HWM (high watermark) to prepare it for the reset zeronet.

Trying the ledger tz1 addr I get:

./tezos-signer set ledger high watermark for "ledger://<tz1...>" to 0

Error:

  No Ledger found for <tz1...>

Trying the animal name thing I get:

./tezos-signer set ledger high watermark for "ledger://<animal>/ed25519/0'/0'" to 0

Error:

  Ledger Application level error (set_high_watermark): Conditions of use not satisfied

Getting the HWM works, but only for the animal uri 🤷‍♂️

ledger high-watermark

share|improve this question

asked 4 hours ago

asbjornengeasbjornenge

600112

add a comment | 

I'm trying to reset the ledger baking application HWM (high watermark) to prepare it for the reset zeronet.

Trying the ledger tz1 addr I get:

./tezos-signer set ledger high watermark for "ledger://<tz1...>" to 0

Error:

  No Ledger found for <tz1...>

Trying the animal name thing I get:

./tezos-signer set ledger high watermark for "ledger://<animal>/ed25519/0'/0'" to 0

Error:

  Ledger Application level error (set_high_watermark): Conditions of use not satisfied

Getting the HWM works, but only for the animal uri 🤷‍♂️

ledger high-watermark

share|improve this question

asked 4 hours ago

asbjornengeasbjornenge

600112

./tezos-signer set ledger high watermark for "ledger://<tz1...>" to 0

Error:

  No Ledger found for <tz1...>

./tezos-signer set ledger high watermark for "ledger://<animal>/ed25519/0'/0'" to 0

Error:

  Ledger Application level error (set_high_watermark): Conditions of use not satisfied

share|improve this question

asked 4 hours ago

asbjornengeasbjornenge

600112

share|improve this question

asked 4 hours ago

asbjornengeasbjornenge

600112

asked 4 hours ago

asbjornengeasbjornenge

600112

asked 4 hours ago

asbjornengeasbjornenge

600112

1 Answer
1

active

oldest

votes

3

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.

The other possibility may be that the ledger connected isn't correctly authorized to make such an action, though I'm not certain this is a requirement to run set ledger high watermark. So you may have to do:

$ ./tezos-client authorize ledger to bake for <SIGNATURE>

share|improve this answer

edited 2 hours ago

answered 3 hours ago

FrankFrank

859213

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  🤦‍♂️ 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!!
  
  – asbjornenge
  3 hours ago
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "698"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f618%2fissues-resetting-the-ledger-hwm%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

3

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.

The other possibility may be that the ledger connected isn't correctly authorized to make such an action, though I'm not certain this is a requirement to run set ledger high watermark. So you may have to do:

$ ./tezos-client authorize ledger to bake for <SIGNATURE>

share|improve this answer

edited 2 hours ago

answered 3 hours ago

FrankFrank

859213

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  🤦‍♂️ 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!!
  
  – asbjornenge
  3 hours ago
  

  
  
  
  

add a comment | 

3

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.

The other possibility may be that the ledger connected isn't correctly authorized to make such an action, though I'm not certain this is a requirement to run set ledger high watermark. So you may have to do:

$ ./tezos-client authorize ledger to bake for <SIGNATURE>

share|improve this answer

edited 2 hours ago

answered 3 hours ago

FrankFrank

859213

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  🤦‍♂️ 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!!
  
  – asbjornenge
  3 hours ago
  

  
  
  
  

add a comment | 

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.

The other possibility may be that the ledger connected isn't correctly authorized to make such an action, though I'm not certain this is a requirement to run set ledger high watermark. So you may have to do:

$ ./tezos-client authorize ledger to bake for <SIGNATURE>

share|improve this answer

edited 2 hours ago

answered 3 hours ago

FrankFrank

859213

$ ./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'

share|improve this answer

edited 2 hours ago

answered 3 hours ago

FrankFrank

859213

answered 3 hours ago

FrankFrank

859213

answered 3 hours ago

FrankFrank

859213