Sfdwhf

Has any human ever had the choice to leave Earth permanently?

Citing paywalled articles accessed via illegal web sharing

Why is it that Bernie Sanders is always called a "socialist"?

Is there a lava-breathing lizard creature (that could be worshipped by a cult) in 5e?

How do you funnel food off a cutting board?

Why did Democrats in the Senate oppose the Born-Alive Abortion Survivors Protection Act (2019 S.130)?

Why don't key signatures indicate the tonic?

How to deal with possible delayed baggage?

How to make ice magic work from a scientific point of view?

In Linux what happens if 1000 files in a directory are moved to another location while another 300 files were added to the source directory?

How much mayhem could I cause as a sentient fish?

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

Line of Bones to Travel and Conform to Curve (Like Train on a Track...)

general past possibility with COULD

How do I draw the dashed lines as shown in this figure

Square Root Distance from Integers

How to use Mathemaica to do a complex integrate with poles in real axis?

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

Why is Agricola named as such?

Let's Encrypt and EV certificates for different hosts in the same domain

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

Why zero tolerance on nudity in space?

Strange "DuckDuckGo dork" takes me to random website

How to not let the Identify spell spoil everything?

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 3 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 3 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 3 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 3 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 3 hours ago

answered 3 hours ago

FrankFrank

859213

answered 3 hours ago

FrankFrank

859213

answered 3 hours ago

FrankFrank

859213