NO! Use the lexicographically ordered one to be consistent in how we create addresses.
At least that’s how I think we should do it.
We should try sending from that first too, though.
1 Like
Fair enought I will send it to: 97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH (the address created by MoD)
1 Like
NOT YET! We haven’t sent from it.
1 Like
No need to hurry.
Imagine something goes pear-shaped, because it hasn’t been tested thoroughly!
Let’s not mess this up, please!
It’s a way to important step towards getting rid of BTC volatility.
Right, well I’ve already send 1300 BKS (the maximum transaction size) so there should be enough on the address to test it with 
Aight. I’m working on a transaction.
<removed>
Verify and check with B&C Explorer that the input transactions don’t include more than specified in outputs so we don’t spend a massive amount as fee, then sign.
Also, hurray! I manually created a transaction using multiple inputs.
Wait, who’s BlockShare was that again? That transaction sends it to Dhume, but it’s masterOfDisaster’s BlockShare.
Here’s one that returns 0.99 BKS to the origin address of the second transaction to the multisig address.
01000000b7b0bc56025c4a3bb4eb32e3e06efbe306acbda53afafbe03e23cceb83c2a9f70907904de901000000f9004830450221008cee1db4c82ed0b82fe5d9733469836c42c221d2f3b4ccdd38e3078854002b0a02206bc8e42b6362b6728e61d79f09df93b539e94d75b7b1d6da01b64b88917aa511014cad53210234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c0721023c41edc461814e825a0847f9031fddf9b2610bb91992724920107f5fd07b492221029684f165042b44197bce605d81e3e9b22acb8ae677ea4ea3412307b3ff26ea6e210304571109f4e9dd3ce67133df452375597d20f583894cdd8ed09c65a3a3e3be5a21034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff55aeffffffff291282d6c6945160d983fea99ae3d1eea73dc9d88ebfbb5b668622414289235001000000f900483045022100c26b349b1e5acbe74913340daa797178a78ecfd1918728c0b814acb58eab8b0102205be1bcd3ae95f1528562b778f8598fed66d39d3635e2750ef94bdc038685ce13014cad53210234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c0721023c41edc461814e825a0847f9031fddf9b2610bb91992724920107f5fd07b492221029684f165042b44197bce605d81e3e9b22acb8ae677ea4ea3412307b3ff26ea6e210304571109f4e9dd3ce67133df452375597d20f583894cdd8ed09c65a3a3e3be5a21034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff55aeffffffff01ac260000000000001976a914813bd2e6ed08d30fbd58217bfedb99a3570856d388ac0000000038
Verify and check with B&C Explorer that the input transactions don’t include more than specified in outputs so we don’t spend a massive amount as fee, then sign.
1 Like
The input transactions ammount to 1 BKS
@mhps, @dysconnect, @woodstockmerkle and @cryptog please sign the above transaction.
Edit: the transaction of 1300 BKS to the multisig has gone though and has 33 confirmations, it hasn’t shown up in the blockexplorer yet though. Txid: 395d42d340fdde3309d777e0bf0d1a2ca13c93d70782d3f3c3e3c4281ab8ea5b
Can confirm the transaction in the BKS wallet though.
Edit: Just to clarify this is the last test transaction before we secure the colleteral, please sign Jooize’s last post.
1 Like
Not sure why this is not being signed, 3 of the 4 we need have been online several times in the last few hours but didn’t sign? I don’t have a lot of time the coming days so it would be really nice if we could wrap this up tonight.
@dysconnect, @woodstockmerkle, @cryptog and @mhps If you read this please sign the above post by @jooize.
I’m not able to sign at the moment but will do so within the next 12 hours or so.
1 Like
i don’t completely understand this.
this is one of the inputs https://bcblockexplorer.com/transactions/e94d900709f7a9c283ebcc233ee0fbfa3aa5bdac06e3fb6ee0e332ebb43b4a5c the 8Ss and 97z output are correct, right?
The point is to check that I haven’t included an input like the 1300 BKS one and then try to spend only 0.99 BKS, making the fee like 1299.01 BKS. 
Does that explain it?
Cointoolkit usually does that for us.
it still has
normal?
That’s exactly it. Because Cointoolkit can’t retreive BlockShare inputs and present their values we get “Not available” and have to manually verify them.
Signed 3 of 3/5.
I am on mobile.
01000000b7b0bc56025c4a3bb4eb32e3e06efbe306acbda53afafbe03e23cceb83c2a9f70907904de901000000fd8b01004830450221008cee1db4c82ed0b82fe5d9733469836c42c221d2f3b4ccdd38e3078854002b0a02206bc8e42b6362b6728e61d79f09df93b539e94d75b7b1d6da01b64b88917aa51101483045022100e901df68456d6d81281902f03c2811ee54044dd5d2d5483439e6e3824600938302200de9242a873fa4d35dd5ddb164148879daa0ae574e50002f1d8227c1ff5336a401483045022100db31f00dbf3aea7c74908e41e25ec5f7d645fa39848bed95f49059fe50e9b7b2022035d91558d08df82c4a1e458636d46c39c013a0563a4d87aa244d8469e7648d19014cad53210234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c0721023c41edc461814e825a0847f9031fddf9b2610bb91992724920107f5fd07b492221029684f165042b44197bce605d81e3e9b22acb8ae677ea4ea3412307b3ff26ea6e210304571109f4e9dd3ce67133df452375597d20f583894cdd8ed09c65a3a3e3be5a21034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff55aeffffffff291282d6c6945160d983fea99ae3d1eea73dc9d88ebfbb5b668622414289235001000000fd8b0100483045022100c26b349b1e5acbe74913340daa797178a78ecfd1918728c0b814acb58eab8b0102205be1bcd3ae95f1528562b778f8598fed66d39d3635e2750ef94bdc038685ce1301483045022100848f2a30ca7ec3440b4fbe2932341820f60a023bb4e37b5036c7c528de16c4d802205a6063307fd545503cc71963aaef24a00fb8186078dddc493dc1cd0c25f41635014830450221008705c9f369e3f94177d6fde10875c48347a0ff8dbae4b71f072b2cb6c5989f3002204a7a355b308cb1429d07ac9617e3d7cc5521cd592463e6570783df9dc620fdf1014cad53210234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c0721023c41edc461814e825a0847f9031fddf9b2610bb91992724920107f5fd07b492221029684f165042b44197bce605d81e3e9b22acb8ae677ea4ea3412307b3ff26ea6e210304571109f4e9dd3ce67133df452375597d20f583894cdd8ed09c65a3a3e3be5a21034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff55aeffffffff01ac260000000000001976a914813bd2e6ed08d30fbd58217bfedb99a3570856d388ac0000000038
PS: Cannot broadcast
2 Likes
Broadcasted: 931ee594f2524c6d2d928dda237ee522f4dc19328b6b5688559da4c725de003c
Provided it worked for me this time.
1 Like
awesome guys! Seeing as the transaction was succeful, I am sending the colleteral to the address. Will post Txid’s here!
1 Like
Holy shit. HUGE transaction! 462394 byte.
getrawtransaction 395d42d340fdde3309d777e0bf0d1a2ca13c93d70782d3f3c3e3c4281ab8ea5b
<HugeRawTransaction>
decoderawtransaction <HugeRawTransaction>
TX decode failed (code -22)
I recommend not pasting the raw transaction into the post. Firefox kept complaining about unresponsive script, and we better not add almost half a megabyte to the thread anyway.
How can we confirm that we have the funds? By spending! 
But I don’t know how to get the inputs. On second thought that might take forever to do manually if there are so many as to reach that size.
Alright 7500 BKS has been send to: 97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH
I had to make 6 transactions since you can send roughly 1300 BKS max in 1 transaction.
Tx 1 - 1300 BKS : 395d42d340fdde3309d777e0bf0d1a2ca13c93d70782d3f3c3e3c4281ab8ea5b
Tx 2 - 1300 BKS : 2718c0780c9517a4385adad2619e280bb7ecfbc6a41298c3f778387dd1164530
Tx 3 - 1300 BKS : cce88839389884ecbdeb4cf3ddb4d3cdec4ff7c86a846e69e1c958e31e23da60
Tx 4 - 1300 BKS : d0a9a76603e511ce7b2aaee720769715632ae0a0b36195de7fb6e6855d25768d
Tx 5 - 1300 BKS : 2132089afd412cd9a6c8fae0f45893fcb75d160b39eaa3f040cb9f95856f82de
Tx 6 - 1000 BKS : 435a81157fe546245e98e4ae3ea01123750cdf518be7c08d01286b9e52a2fef4
So far transaction 1 and 3 are confirmed already although they might now show up in the blockexplorer. You can verify the transaction in the console of the BKS wallet. You can use the ‘gettransaction’ command to see the ammount send and the confirmations.
@jooize I think the problem is that BKS splits them up into 1 BKS chunks. So a 1300 BKS transaction is 1300 x 1 BKS send. I’m not sure why it dous this. My wallet also crashes after i’ve send it and I have to reboot it.
Edit: The others are starting to get confirmations to now, I think I am filling up the blocks to the brim haha 
I ran this to add the multisig address to the wallet. (I’ll have to revise the instructions I made that use createmultisig. Never mind, I had chosen that there for the reason of not adding it.)
addmultisigaddress 3 '["0234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c07", "023c41edc461814e825a0847f9031fddf9b2610bb91992724920107f5fd07b4922", "029684f165042b44197bce605d81e3e9b22acb8ae677ea4ea3412307b3ff26ea6e", "0304571109f4e9dd3ce67133df452375597d20f583894cdd8ed09c65a3a3e3be5a", "034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff"]'
97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH
gettransaction 395d42d340fdde3309d777e0bf0d1a2ca13c93d70782d3f3c3e3c4281ab8ea5b
Invalid or non-wallet transaction id (code -5)