search

mastercoin-MSC / masterchest-wallet

Masterchest Wallet
MIT License
15 stars 13 forks source link

Critical - Send payment & Cancel buttons are disabled #25

Closed ripper234 closed 10 years ago

ripper234 commented 10 years ago

I just placed a buy order from 1Q7soqFvsSkhNy5GdVw1oSm9KVpgzHA9Zk. I see open order in my wallet with status "Pending":

image

However I do not see it on masterchest.info. Also as of the time of this reporting, I do not see any bitcoin transaction that touches this address on blockchain.info.

So, my conclusion is that my transaction was not broadcast for some reason. When I right-click on the offer, I cannot cancel or send payment - both are grayed out:

image

The debug logs say the transaction was sent:

DEBUG: Beginning accept (buy) transaction

DEBUG: Requesting passphrase DEBUG: Validating recipient address DEBUG: Calling library: mlib.encodeaccepttx, bitcoin_con, 143jwThfaFtBYxyTfRtjBZrt3i1fuF1udo, 1Q7soqFvsSkhNy5GdVw1oSm9KVpgzHA9Zk, 2, 10000000 DEBUG: Raw transaction hex: 0100000001457ba6a3f567f030b7b2208ac95a5604fc9ddebe61cb6678bf1f4f61e6d60bee0000000000ffffffff04d0300e00000000001976a914216d0d8c64e081c3d0d71d9263a003cc279ac8a688ac70170000000000001976a914946cb2e08075bcbaf157e47bcb67eb2b2339d24288ac70170000000000001976a914fd97ccfbfb5a002280814326ba5ec426c6dd8e7f88ace02e00000000000047512103099ef03a9d4ef797fced855d3df47d1e16ecf8906798c502af28631bf406aa4821022991943753bd89b34a3058629f98ba37826b1f56a1632a5db019705078739e9c52ae00000000 DEUBG: Unlocking wallet DEUBG: Attempting signing DEUBG: Attempting broadcast

DEUBG: Transaction sent - 1748ac1857457fe73ea68a1bba901def4240e54b59f105505be78953188027e1

DEBUG: Ending accept (buy) transaction

When I restart Masterchest Wallet, the order still shows up, and I still cannot click 'cancel' or 'send payment'

ripper234 commented 10 years ago

I'm not sure what happened here, but I think this one is invalid - I probablly reported this before waiting for a block. I did expect to see the transaction on blockchain.info even before it was included in a block, and didn't see it back then - so I thought something was wrong on the sending side.

Closing as invalid.