Fhyujk

Why did the villain in the first Men in Black movie care about Earth's Cockroaches?

Is it possible to grant users sftp access without shell access? If yes, how is it implemented?

How to deal with possible delayed baggage?

How do you funnel food off a cutting board?

When do I have to declare that I want to twin my spell?

Picture with grey box as background

Cookies - Should the toggles be on?

Crontab: Ubuntu running script (noob)

False written accusations not made public - is there law to cover this?

Why avoid shared user accounts?

Potential client has a problematic employee I can't work with

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

Is there any risk in sharing info about technologies and products we use with a supplier?

Why would space fleets be aligned?

Do authors have to be politically correct in article-writing?

Square Root Distance from Integers

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 do you catch Smeargle in Pokemon Go?

Alien invasion to probe us, why?

Why do cars have plastic shrouds over the engine?

Can we harness potential energy?

What happens when a creature with flying blocks my non-flying attacker?

GRASS not working with QGIS 3.6

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

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

edited 2 hours ago

asbjornenge

asked 7 hours ago

asbjornengeasbjornenge

600113

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

edited 2 hours ago

asbjornenge

asked 7 hours ago

asbjornengeasbjornenge

600113

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

edited 2 hours ago

asbjornenge

asked 7 hours ago

asbjornengeasbjornenge

600113

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

edited 2 hours ago

asbjornenge

asked 7 hours ago

asbjornengeasbjornenge

600113

share|improve this question

edited 2 hours ago

asbjornenge

asked 7 hours ago

asbjornengeasbjornenge

600113

asked 7 hours ago

asbjornengeasbjornenge

600113

asked 7 hours ago

asbjornengeasbjornenge

600113

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

answered 6 hours ago

FrankFrank

864214

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  🤦‍♂️ 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
  6 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 6 hours ago

answered 6 hours ago

FrankFrank

864214

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  🤦‍♂️ 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
  6 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 6 hours ago

answered 6 hours ago

FrankFrank

864214

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  🤦‍♂️ 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
  6 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 6 hours ago

answered 6 hours ago

FrankFrank

864214

$ ./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 6 hours ago

answered 6 hours ago

FrankFrank

864214

answered 6 hours ago

FrankFrank

864214

answered 6 hours ago

FrankFrank

864214