<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>MultiChain Developer Q&amp;A - Recent questions tagged encrypted-wallet</title>
<link>https://www.multichain.com/qa/tag/encrypted-wallet</link>
<description>Powered by Question2Answer</description>
<item>
<title>I have encrypted a running node's wallet - node stop syncing</title>
<link>https://www.multichain.com/qa/11330/i-have-encrypted-a-running-nodes-wallet-node-stop-syncing</link>
<description>&lt;p&gt;Hi,&lt;/p&gt;&lt;p&gt;I have encrypted a running node's wallet (&lt;span style=&quot;font-family:courier new,courier,monospace&quot;&gt;encryptwallet&lt;/span&gt;) and now the node is stop syncing with the network.&lt;/p&gt;&lt;p&gt;The debug messages are:&lt;/p&gt;&lt;p&gt;2018-10-17 13:23:59 mchn: Sending minimal parameter set to xx.xx.xx.xx:yyyy&lt;br&gt;2018-10-17 13:23:59 mchn: Internal error: Connection address not found in the wallet&lt;br&gt;2018-10-17 13:23:59 receive version message: /MultiChain:0.1.0.9/: version 70002, blocks=85076, us=my.ip.address:49969, peer=545&lt;br&gt;2018-10-17 13:23:59 mchn: Internal error: Connection address not found in the wallet&lt;br&gt;2018-10-17 13:23:59 ProcessMessage(verack, 321 bytes) FAILED peer=545&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;getinfo:&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;font-family:courier new,courier,monospace&quot;&gt;{&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;version&quot; : &quot;1.0.6&quot;,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;nodeversion&quot; : 10006901,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;protocolversion&quot; : 10009,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;chainname&quot; : &quot;CHAN1&quot;,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;description&quot; : &quot;...&quot;,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;protocol&quot; : &quot;multichain&quot;,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;port&quot; : yyyy,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;setupblocks&quot; : 60,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;nodeaddress&quot; : &quot;CHAN1@192.168.100.11:7269&quot;,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;burnaddress&quot; : &quot;fXXXXXXY1mXXXXXXtNXXXXXXYJXXXXXXbMXyzT&quot;,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;incomingpaused&quot; : false,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;miningpaused&quot; : false,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;walletversion&quot; : 60000,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;balance&quot; : 0.00000000,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;walletdbversion&quot; : 2,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;reindex&quot; : false,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;blocks&quot; : 85025,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;timeoffset&quot; : 0,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;connections&quot; : 0,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;proxy&quot; : &quot;&quot;,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;difficulty&quot; : 0.00000006,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;testnet&quot; : false,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;keypoololdest&quot; : 1539779127,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;keypoolsize&quot; : 1,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;unlocked_until&quot; : 0,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;paytxfee&quot; : 0.00000000,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;relayfee&quot; : 0.00000000,&lt;br&gt;&amp;nbsp; &amp;nbsp; &quot;errors&quot; : &quot;&quot;&lt;br&gt;}&lt;/span&gt;&lt;/p&gt;&lt;p&gt;It is stop working at that block height (when I encrypted the wallet), the network height now is&amp;nbsp;85076&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description>
<guid isPermaLink="true">https://www.multichain.com/qa/11330/i-have-encrypted-a-running-nodes-wallet-node-stop-syncing</guid>
<pubDate>Wed, 17 Oct 2018 13:30:32 +0000</pubDate>
</item>
<item>
<title>Alternative to unlocking an encrypted wallet</title>
<link>https://www.multichain.com/qa/173/alternative-to-unlocking-an-encrypted-wallet</link>
<description>Sorry - I know that this is Q&amp;amp;A, but I can't find an appropriate place for feature requests, so here goes...&lt;br /&gt;
&lt;br /&gt;
Unlocking the wallet for a period of time is one of the biggest security flaws with the bitcoin daemon. Once the wallet is unlocked then any process on an authorised machine can connect and issue send instructions until such stage as the wallet is locked again.&lt;br /&gt;
&lt;br /&gt;
Just a thought, but how about appending the wallet password as an optional parameter to the JSON RPC calls that require an encrypted wallet to be unlocked. Assuming the implementation used SSL for RPC calls the password can be transmitted to the daemon securely and used to unlock it solely for that method call.</description>
<guid isPermaLink="true">https://www.multichain.com/qa/173/alternative-to-unlocking-an-encrypted-wallet</guid>
<pubDate>Tue, 29 Sep 2015 11:54:53 +0000</pubDate>
</item>
</channel>
</rss>