That’s really bad.
Patched Cointoolkit to run over insecure HTTP and access B&C Explorer over HTTP as it doesn’t handle HTTPS anymore.
FLOT’s BlockShare address: 97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH (balance: 8,800.20 BKS)
Create transaction with patched Cointoolkit over HTTP.
I’m currently having it generate the transaction. How high fee do we need?
Cointoolkit lists only 7,500.20 BKS, but perhaps it’s some limit and we can send the rest afterward.
That is because the 8800 is an incorrect balance, no clue why the explorer makes that error. It’s supposed to be 7500 BKS.
Took less than two hours. The transaction is 1.6 MB. Now loading the signing page.
I worry that 0.2 BKS is insufficient fee. Didn’t want to burn your BKS excessively. How much will be required? 1.6 MB plus signatures.
The process of signing may make your computers unusable for a while. Alternative is handing over your private key to a trusted party.
Return BlockShares to @Dhume
Amount: 7,500 BKS
Fee: 0.2 BKS (too low?)
Signed 0 of 3-of-5
[Passed] Reimbursing shareholder
I vaguely recall the default fee is in the range of 0.01-0.02 per kb. So the fee should be somewhere between 16-32 BKS, plus a little. I couldn’t find a definitive answer after skimming the BCE sourcecode, but it seems the fee is voted on per block so one might need to check with the client.
I cannot verify what is in NuSafe-transaction-unsigned.txt in https://jooize.github.io/cointoolkit/?mode=blockshares#verify
We’ll have to create a new transaction then. If it turns out verifying isn’t possible, can transactions be created deterministically? I recall there often being a minor difference when generating them. That part may not matter though. The idea being we all create the transaction independently so you can trust it, sign them separately, then merge the signed transactions into one with Cointoolkit, and broadcast.
@mhps Does it take forever or fail?
The signing page did load eventually, but only now I can input my key to sign. Currently signing.
The content of the tx appears to be empty.
No. When I loaded in the verify page, it gives decoding error instantly when I clicked ‘verify’
Can you post the tx signed by you?
I’m still signing it.
Still at 0.01 BKS
“blocks” : 941751,
“moneysupply” : 194817.6524,
“connections” : 5,
“proxy” : “”,
“ip” : “”,
“difficulty” : 0.00027354,
“testnet” : false,
“keypoololdest” : 1439374527,
“keypoolsize” : 251,
“paytxfee” : 0.01,
“unlocked_until” : 0,
[Passed] Reimbursing shareholder
@Dhume: Let’s resolve this and get your BlockShares back. If FLOT doesn’t sign, we’ll have to look at alternatives.
But not now right? Because BKS is trying to fork and these txns would get undone?
We can rebroadcast them on the new chain.
Thanks for being on top of this @jooize I’m still getting my new B&C client synced currently at 88%. I haven’t posted the raw transactions that @sigmike send me because they are using my old BKS address that I haven’t verified I still have access to. Should be synced tomorrow and I’ll see if I can get the backup of that wallet going.
What do you mean?
You haven’t gotten back to me.
If not enough of those with keys to this multisig sign the funds over to Dhume.
It didn’t finish signing in reasonable time, so there’s nothing to post.