So far transaction 1 and 3 are confirmed already although they might now show up in the blockexplorer. You can verify the transaction in the console of the BKS wallet. You can use the ‘gettransaction’ command to see the ammount send and the confirmations.
@jooize I think the problem is that BKS splits them up into 1 BKS chunks. So a 1300 BKS transaction is 1300 x 1 BKS send. I’m not sure why it dous this. My wallet also crashes after i’ve send it and I have to reboot it.
Edit: The others are starting to get confirmations to now, I think I am filling up the blocks to the brim haha
I ran this to add the multisig address to the wallet. (I’ll have to revise the instructions I made that use createmultisig. Never mind, I had chosen that there for the reason of not adding it.)
They are still unconfirmed in my wallet aswell… very weird. The ammount has been deducded from my wallet and they both show up in my transaction list…?
Sounds like they failed to propagate, perhaps because your wallet crashed. I don’t know what to do about that. I think I did a rescan once for that, but I’m not sure.
I updated my previous post with better confirmation of the transactions.
I was about to suggest getrawtransaction and then sendrawtransaction, but the problem is the debug window input box can’t handle the length, and I’m not sure that works via a terminal shell either.
For now shall we go ahead with signing the BTC transaction I made? I wont have alot of time the coming days would like to get Nusafe running before that. All is set up on my end.
I wonder what happens if you start wallet with the argument -rescan. If the transaction isn’t propagated anywhere it should either not be broadcast again and you can try sending a new transaction, or it figures out that it hasn’t been sent and tries to rebroadcast it. I believe the former is the case.