That’d be a part of the opportunity costs then 
1 Like
So I’ve been running the numbers and estimating conservatively at the moment roughly 1k BKS mints you about 0.31 BKS a day (0.0132 per hour) so that’s 0.31 x 30 = 9.3 BKS a month. Using those numbers the 7500 BKS would mint for about 9.3 x 7,5 = 69,75 BKS a month. If we say the value is roughly 6$ a piece that means not minting with the 7500 BKS currently in collateral is costing me about 69,75 x 6 = 418.50$ dollar a month. Recently I’ve begun minting full time to support the protocol changes and was amazed by how much BKS I was minting.
So this is an obvious problem and I’m not sure what the solution might be seeing as everything I can think off has obvious drawbacks for Nu. Would like to know what other shareholders think off this.
Maybe it is possible to split the bks to several custodians who mint their own bks to hold and mint with the collaterals?
I like this idea and it’s the best one I could think of as well with the least drawbacks to Nu however it’s not easy to arrange. It relies on finding multiple custodians that 1. Essentially already mint full time + 2. Have already build up enough trust that we can store large amounts of BKS with them without significant counterparty risk and 3. Are willing to provide such a service for a very low fee (maybe a few% of the BKS minted?)
Also in such a case (however unlikely) that they do end up taking off with the collateral how would we salvage such a situation, would Nu repay for any BKS lost?
I won’t have problem counting you as one of them ( then simply just ask you to submit less collateral BKS) The risk in your running off is doubled though.
NuSafe has been totally used right?
Yes.
1 Like
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. 
We’ll figure it out.
1 Like
Oh god for real, damn thats inconvenient :S
@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:
53210234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c0721023c41edc461814e825a0847f9031fddf9b2610bb91992724920107f5fd07b492221029684f165042b44197bce605d81e3e9b22acb8ae677ea4ea3412307b3ff26ea6e210304571109f4e9dd3ce67133df452375597d20f583894cdd8ed09c65a3a3e3be5a21034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff55ae
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.
3 Likes
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.
2 Likes
Return BlockShares to @Dhume
Address: 8XyinfDRRytGDjvB8kmEpZVWd3fAFw2uHP
Amount: 7,500 BKS
Fee: 0.2 BKS (too low?)
Signed 0 of 3-of-5