Closed stefanionescu closed 5 years ago
QM internally uses a Node Manager Contract for storing the public keys of participant nodes and their other info. This is very much required to support some of the features of QM and you cant prevent it from getting deployed. This contract is deployed only one time and the rest of the transactions you see are each node registering their info in this contract.
Due to the very immutability nature of blockchain, you cant undeploy/delete contracts or transactions from chain.
So you say 6 deployed contracts are normal behaviour when starting up the network?
Nevermind, now I got it
I bootstrapped a 3 nodes development network, deployed some contracts to it and then executed 'docker-compose down'
After doing docker-compose up again, I see that there are a couple of contracts already deployed to the network without me doing anything.
Are these the contracts that I previously deployed, and if so, how do I cleanly start the network again after deploying contracts and bringing it down?