user5285: technical question for securing the pledge with hardware wallet.
Is it possible to have the pledged secured with ledger nano and not having to sign pool updates with it?
I mean, just have the ledger address as second owner for that purpose and every pool update, or actions signed just with normal keys?
Thank you!

user4302: Any wallet that is registered as an "owner" wallet (a.k.a. pledge wallet) must witness any submission of a pool certificate, even if the certificate is being submitted for a minor update. If the certificate is submitted without the witness of a (currently) pledged wallet, then that wallet will be removed from "pledge" status the following epoch.
In other words, all owners and/or operators of a pool must witness pool updates, or their wallet(s) will loose pledge status.

user5286: If you follow the steps below and register as a Pledge wallet you must sign as a witness for any pool update transaction. No way around that.
You'll need to do a few things to set up the 2nd pledge wallet:

Set up your Ledger, delegate, make sure you do this 2 epochs before any pledge changes
Install this to interface with your Ledger
Export your staking keys
Copy your stake.vkey to your cold env and update your stake pool registration certificate. Make sure you have these flags sent in:


--pool-reward-account-verification-key-file [LEDGER-STAKE].vkey 
--pool-owner-stake-verification-key-file [NON-LEDGER-STAKE].vkey 
--pool-owner-stake-verification-key-file [LEDGER-STAKE].vkey \


Copy your pool.cert back to block producer and prep a new multi-signature transaction
You'll need 4 witnesses:
node.skey
[LEDGER-STAKE].hwsfile
stake.skey
payment.skey
Submit the transaction


5285: <p>technical question for securing the pledge with hardware wallet.</p>
<p>Is it possible to have the pledged secured with ledger nano and not having to sign pool updates with it?</p>
<p>I mean, just have the ledger address as second owner for that purpose and every pool update, or actions signed just with normal keys?</p>
<p>Thank you!</p>
 4302: <p>Any wallet that is registered as an &quot;owner&quot; wallet (a.k.a. pledge wallet) <em>must</em> witness any submission of a pool certificate, even if the certificate is being submitted for a minor update. If the certificate is submitted without the witness of a (currently) pledged wallet, then that wallet will be removed from &quot;pledge&quot; status the following epoch.</p>
<p>In other words, all owners and/or operators of a pool must witness pool updates, or their wallet(s) will loose pledge status.</p>
 5286: <p>If you follow the steps below and register as a Pledge wallet you must sign as a witness for any pool update transaction. No way around that.</p>
<p>You'll need to do a few things to set up the 2nd pledge wallet:</p>
<ol>
<li>Set up your Ledger, delegate, make sure you do this 2 epochs before any pledge changes</li>
<li>Install <a href="https://github.com/vacuumlabs/cardano-hw-cli" rel="nofollow noreferrer">this</a> to interface with your Ledger</li>
<li>Export your staking keys</li>
<li>Copy your stake.vkey to your cold env and update your stake pool registration certificate. Make sure you have these flags sent in:</li>
</ol>
<blockquote>
<p>--pool-reward-account-verification-key-file [LEDGER-STAKE].vkey <br />
--pool-owner-stake-verification-key-file [NON-LEDGER-STAKE].vkey <br />
--pool-owner-stake-verification-key-file [LEDGER-STAKE].vkey \</p>
</blockquote>
<ol start="5">
<li>Copy your pool.cert back to block producer and prep a new multi-signature transaction</li>
<li>You'll need 4 witnesses:
node.skey
[LEDGER-STAKE].hwsfile
stake.skey
payment.skey</li>
<li>Submit the transaction</li>
</ol>
