Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to send transaction #32

Open
miketsl opened this issue Jan 8, 2017 · 3 comments
Open

Failed to send transaction #32

miketsl opened this issue Jan 8, 2017 · 3 comments

Comments

@miketsl
Copy link

miketsl commented Jan 8, 2017

Hi,
Been using mSIGNA for a while, and generally love it. Recently I am running into a bit of a problem with it though. When I go to send a new transaction, I sign it like usual, it shows up on the top of the transaction tab as "unsent". I have a connection with the network,...and no matter what I do, it never sends the transaction.

When this first started happening, I was able to close mSIGNA, and open it again, delete the transaction, then resend it, and sign it. It would work for 1 transaction before doing the same thing. Now this "trick" doesn't work anymore.

I have a few btc trapped in the wallet :/

I tried to recover the wallet by exporting private keys, and importing into MutliBit. But multibit, after going through all the blockchain to "recover" the wallet, has the balance listed as 0btc. There is definitely a balance in the mSIGNA.

Does anyone have any suggestions on how to get mSIGNA to send out a transaction successfully or at least, how to transfer the balance into another wallet?

Any help appreciated.

@Leone32
Copy link

Leone32 commented Nov 28, 2017

Hi Miketsl,
InMy opinion the "trick" you mentioned, it didn't work the First time

L32

@kittykoins
Copy link

I had a similar issue and was unable to sync properly or send transaction from mSigma. Transaction failed to confirm in mSigna despite having thousands of confirmations on the blockchain. Every time I would try to send a transaction mSigna would crash. I spent 3 weeks upgrading schemas, rebuilding vaults, and syncing transactions. Version 0.10.6 specifically stated that it would fix the situation yet still failed.

After 3 weeks of dealing with mSigna's bugs I tried to get the private keys out so I could sweep the keys. It's extremely difficult to get the private keys for each address without knowing the derivation path. In the end I generated a transaction with mSigna and had to broadcast it to the blockchain manually. This method worked perfectly for me and I safely got all my bitcoins and Bitcoin Cash out of the corrupted mSigna software.

I highly suggest finding a new wallet option ASAP and NEVER use mSigna again. mSigna is unstable, poorly supported, bug-ridden, and a danger to your Bitcoins!

  1. Create backup of vault file
  2. Disconnect from node/localhost
  3. Determine appropriate fee to ensure transaction is approved by blockchain. Example site: https://estimatefee.com/
  4. Create 'Send' transaction using different wallet address
  5. Enable 'Coin Control' option and select coin
  6. Send full amount of specified coin minus the fee, make sure 0 funds remain to prevent bitcoin being sent to 'Change Address'
  7. Sign transaction
  8. Export 'Raw' transaction to clipboard
  9. Broadcast 'Raw' transaction to blockchain with online tool or node CLI. Example site: https://blockchain.info/pushtx
  10. Monitor new wallet for transaction to be confirmed
  11. Repeat with all coins
  12. Once all transactions are confirmed destroy your mSigna vaults and don't ever use mSigna again.

@MrChriZ
Copy link

MrChriZ commented Jan 13, 2020

Thanks Kitty Coin this was very useful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants