It’s definitely not recommended to run two clients using the same addresses at the same time. The way that the protocol is designed is that it protects against nodes attempting to mint across multiple chains. When your clients are running, both of your clients will find a block at the same time with the same stake. If for some reason the blocks that you are solving are different for any reason—maybe one client has received notification of a transaction that the other one hasn’t yet received—then both blocks will be rejected when they are submitted and you’ll lose your block reward.
In the transactions list on your client, you would see the same “dashed line square” icon for a block that is rejected by the network that you would on a truly “orphaned” block (meaning that you sent it to the network but another block had already been accepted).
We’re going to look into improving this visually in the UI (differentiate the icons), but in the mean time you should be able to look in the debug.log file in your application directory to find instances where the block was rejected because it was submitted twice.
Does this help?
