FLOT BKS Operations (buy side)

jooize 2016-02-12 03:15:23 UTC #104

Updated to include all transactions.

foreach file in blockshares-*.txt ; do ; grep '"value" : 1.0,' $file | wc -l ; done

foreach file in blockshares-*.txt ; do ; grep '97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH' $file | wc -l ; done

Confirmed ~~four~~ five transactions with 1300 BKS and one with 1000 BKS to 97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH. They have over 50 confirmations.

These I get the following with:

No information available about transaction (code -5)

NuSafe - First operating period and Bi-weekly collateral report

Dhume 2016-02-12 03:17:21 UTC #105

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…?

jooize 2016-02-12 03:31:36 UTC #106

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.

@Dhume: Does the following work?

getrawtransaction 2132089afd412cd9a6c8fae0f45893fcb75d160b39eaa3f040cb9f95856f82de

<RawTransaction5>

getrawtransaction 435a81157fe546245e98e4ae3ea01123750cdf518be7c08d01286b9e52a2fef4

<RawTransaction6>

Copy–paste them into one of these sites: (triple-click to select the transaction)

Dhume 2016-02-12 04:07:58 UTC #107

Dousnt that only work for Bitcoin?

jooize 2016-02-12 04:08:33 UTC #108

D’oh!

Dhume 2016-02-12 04:08:47 UTC #109

jooize 2016-02-12 04:11:28 UTC #110

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.

Dhume 2016-02-12 04:12:15 UTC #111

Ye I just tried that as well (code -22) again.

This is very peculiar though, the procedure was exactly the same as with the other transactions. Why would this be in limbo?

mhps 2016-02-12 04:18:58 UTC #112

because someone with even one share can mint and vote. @sigmike

Dhume 2016-02-12 04:20:00 UTC #113

I just send another 0.1 BKS to test and it went though and already has a confirmation…

Dhume 2016-02-12 04:28:45 UTC #114

I guess we have to ask @sigmike whats going.

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.

jooize 2016-02-12 04:32:31 UTC #115

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.

Want to try that? Make a backup first.

Dhume 2016-02-12 04:33:55 UTC #116

Sure, how do you start it with the -rescan argument?

jooize 2016-02-12 04:34:57 UTC #117

Windows, OS X, or Linux?

Dhume 2016-02-12 04:35:08 UTC #118

Windows

jooize 2016-02-12 04:37:20 UTC #119

Create a shortcut to BCExchange.exe.
Right-click the shortcut and click Properties.
Under the tab Shortcut, in the field Target, add -rescan (with a space before) to the end after any quotation mark.
Click OK.
Open the shortcut.

Dhume 2016-02-12 04:44:02 UTC #120

Thanks! Interesting the balance gained the 2300 that was supposed to be send. The transactions still show up as uncofirmed transaction in my history. Shall I try resending them with the sendrawtransaction command?

Still no confirmation I think they completely failed to register or something. A new transaction might be best no?

jooize 2016-02-12 04:52:11 UTC #121

Okay!

I don’t think it’s possible, as the input box doesn’t handle the length of the raw transaction. If you’re comfortable with the risk that the transactions might go through later, you can send new transactions. If you’re not comfortable with that (the risk being FLOT having to return the funds), you could send all coins to yourself to prevent them to ever go through if some node received a transaction and didn’t propagate it further until later (which seems extremely unlikely, especially as it should be likely you’ll spend at least one of all those inputs in a new transaction).

I suggest new transactions!

Dhume 2016-02-12 04:56:26 UTC #122

I’m sending new transactions will update with new Tx id’s

Yes! the first transaction has gotten confirmed!

Tx 7 - 1300 : c1140633e756463ec8ef04ebca7d62dc50a21b5b0d8ebeacf0343916ed3a6f87

Tx 8 - 1000 : 98fbb98f2250930a2e66da12398821d0b5ef2060ccaff705970e444e30acf4ba

jooize 2016-02-12 05:26:03 UTC #123

grep '97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH' blockshares-getrawtransaction-verbose-c1140633e756463ec8ef04ebca7d62dc50a21b5b0d8ebeacf0343916ed3a6f87.txt | wc -l

grep '"value" : 1.0,' blockshares-getrawtransaction-verbose-c1140633e756463ec8ef04ebca7d62dc50a21b5b0d8ebeacf0343916ed3a6f87.txt | wc -l

grep '97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH' blockshares-getrawtransaction-verbose-98fbb98f2250930a2e66da12398821d0b5ef2060ccaff705970e444e30acf4ba.txt | wc -l

grep '"value" : 1.0,' blockshares-getrawtransaction-verbose-98fbb98f2250930a2e66da12398821d0b5ef2060ccaff705970e444e30acf4ba.txt | wc -l

6 confirmations.

FLOT BTC Operations (buy side)