[Passed] NuSafe - An 30k hedge of Tier 4 funds in USD

Then we should return the funds.

Yes please do you can use the following address: 8XyinfDRRytGDjvB8kmEpZVWd3fAFw2uHP

1 Like

I suppose nobody has a super convenient tool for crafting multisig BlockShare transactions? We may need to create one since there’s one input per BKS and I’m not a robot like @masterOfDisaster. :cold_sweat:

We’ll figure it out.

1 Like

Oh god for real, damn thats inconvenient :S

I tried the redeem script here but my browser hangs when loading the script.

@Dhume, did you ever get your BKS back?
My understanding that the contract has not ended, if you didn’t get your BKS back.

If you didn’t get your collateral back, what about the fee of quarterly 900 NBT?
It should be easy to find your payments somewhere in the books.
Oh no wait, it’s all ultra transparently written in the blockchain.

1 Like

I have not received my BKS back yet.

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)

Redeem script:


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.

1 Like

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

Address: 8XyinfDRRytGDjvB8kmEpZVWd3fAFw2uHP
Amount: 7,500 BKS
Fee: 0.2 BKS (too low?)

Signed 0 of 3-of-5



(@jooize) @cryptog @mhps @woodstockmerkle @dysconnect

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

@dysconnect Thanks.

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.

Can someone running a BCE node get the newest per kb fee? Thanks. @Cybnate

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,