After encrypting wallet and others

Question

Hello, Multichain.

I think there is something to check.

 

1. After encrypting admin's wallet with "encryptwallet", the admin node cannot mine a new block and others do not too. I attached log at below.

 

2. The chain-description in param.dat could not be longer than 93 chars. At the comment, it could have 256 chars. 

 

* param.dat

default

 

* error log

2017-11-02 08:46:49 mchn: Internal error: Connection address not found in the wallet 2017-11-02 08:46:49 ProcessMessage(verack, 318 bytes) FAILED peer=26 2017-11-02 08:46:50 MultiChainMiner: Block Found - 0065cfe4b72a6baa5ac00813c681c9e36a7011df7a2ed6ef6baf512c7c79af88, prev: 00e9c6580dc37a6eeebd5b7e558bc0a05ccc7398a890523fc7b0c4b86460cb5a, height: 34, txs: 1 2017-11-02 08:46:50 mchn: Block signature not found 2017-11-02 08:46:50 ERROR: MultiChainMiner : ProcessNewBlock, block not accepted 2017-11-02 08:46:50 mchn: Sending minimal parameter set to 192.168.10.82:6831 2017-11-02 08:46:50 mchn: Internal error: Connection address not found in the wallet 2017-11-02 08:46:50 receive version message: /MultiChain:0.1.0.9/: version 70002, blocks=34, us=192.168.10.81:49712, peer=27 2017-11-02 08:46:50 mchn: Connection from 1SLqRTmk62CrgKxMZ8WF6d4pCMe36mCyMnpNBj received on peer=27 in verack 2017-11-02 08:46:50 mchn: Internal error: Connection address not found in the wallet 2017-11-02 08:46:50 ProcessMessage(verack, 318 bytes) FAILED peer=27 201

 

 

Answer 1

That's right. If a node needs the private key corresponding to a wallet address for ongoing automatic activities, such as mining, then you cannot use encryptwallet, because that prevents the node from accessing the key when it needs it. This is explain on the API page:

In a permissioned blockchain, MultiChain will also require the wallet to be unlocked before it can connect to other nodes, or sign blocks that it has mined.

As for the character limit in the description, we can see this problem and will look into it – thanks for letting us know.