FLOT BKS Operations (buy side)

Liquidity
#12

A fairer way is to give FLOT some extra commission out of the expenses of NuSafe. On the other hand, FLOT motions also dictate that each of us abide by motions passed by shareholders.

Anyway, I’m still using the same key:
034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff

#13

Public Key for BKS operations:

0304571109f4e9dd3ce67133df452375597d20f583894cdd8ed09c65a3a3e3be5a

#14

0234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c07

#15

Thank you all for you swift replies! Now we only need @cryptog pub key to create the BKS address.

#16

Sorry for the delay.

023c41edc461814e825a0847f9031fddf9b2610bb91992724920107f5fd07b4922

#17

Generated with Cointoolkit:
BKS multisig address 97vgjUf9ccmRoyuKRoJgaPAmPA4HhjQd1R.
Does that work (never tried that before!)?

edit: I forgot to put the pubkeys of this BKS multisig address in lexicographical order. They are in order of appearance.
That renders this multisig address unusable or at least not very reliably usable unless the order of the pubkeys is the same when creating transactions.
Sorry for that.

#18

If you use the createmultisig and addmultisig RPCs to generate the multisig address then you use “P2SH multisig” and the current limit is 1-of-12, 2-of-10, 3-of-8 or 4-of-6.

This limit can be increased to 15-of-15 without a change in the protocol because it’s enforced when transactions are relayed, not when they’re included in a block.

You can find the explanation about the limits here:

2 Likes
#19

What’s up here? We have @woodstockmerkle @mhps @jooize @cryptog and @dysconnect. If we also use @Dhume then we can do a 4-of-6 to do what @sigmike said:

1 Like
#20

I urge all involved parties to speeding up this process.
Nu is in the face of Bitcoin’s recent volatility selling a lot of NBT - taking all the BTC volatility risk once more.

@woodstockmerkle, @mhps, @jooize, @cryptog and @dysconnect, please proceed with the BKS multisig that is required for NuSafe

Nu needs to allow @Dhume hedging volatility for at least some of the T4 funds.

#21

'What is the next thing to do?

1 Like
#22

I think we just need the inputs to send back the test amount we got, but since we had no block explorer and nobody with the client at the time, we stalled.

I’m synchronizing the blockchain at the moment.

#23

why not blindly send from the to-address for an amount smaller than the original sent amount less fees? if the tx got through the original sent tx must have worked.

#24

Right, good point. I’ll go look in the thread again if we have the transaction ID.

We don’t. @Dhume: Do you have it? Or both. If I recall correctly there were two test transactions made. One to each address that was created (lexicographically ordered and not).

#25

I am ready to sign any valid tx.

#26

We need @dhume’s pub key to make the 4-of-6 createmultisig and addmultisig rpc commands work right?

#27

Dhume’s first address (FLOT PM)

There should be 1 BKS at the address.

addmultisigaddress 3 '["023c41edc461814e825a0847f9031fddf9b2610bb91992724920107f5fd07b4922", "0234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c07", "0304571109f4e9dd3ce67133df452375597d20f583894cdd8ed09c65a3a3e3be5a", "034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff", "029684f165042b44197bce605d81e3e9b22acb8ae677ea4ea3412307b3ff26ea6e"]'

9CXZXhnhp8HBx12Zr6JJmJmTm8qQWrsR6r

listunspent 9CXZXhnhp8HBx12Zr6JJmJmTm8qQWrsR6r

[
]

getreceivedbyaddress 9CXZXhnhp8HBx12Zr6JJmJmTm8qQWrsR6r

0.0

Verify (redeem script).

masterOfDisaster’s first address

There should be 1 BKS at the address.

addmultisigaddress 3 '["034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff", "0304571109f4e9dd3ce67133df452375597d20f583894cdd8ed09c65a3a3e3be5a", "0234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c07", "029684f165042b44197bce605d81e3e9b22acb8ae677ea4ea3412307b3ff26ea6e", "023c41edc461814e825a0847f9031fddf9b2610bb91992724920107f5fd07b4922"]'

97vgjUf9ccmRoyuKRoJgaPAmPA4HhjQd1R

listunspent 97vgjUf9ccmRoyuKRoJgaPAmPA4HhjQd1R

[
]

getreceivedbyaddress 97vgjUf9ccmRoyuKRoJgaPAmPA4HhjQd1R

0.0

Verify (redeem script).

masterOfDisaster’s “To add some confusion” address (FLOT PM)

Lexicographically ordered 3-of-5 address.

There should be 1 BKS at the address.

addmultisigaddress 3 '["0234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c07", "023c41edc461814e825a0847f9031fddf9b2610bb91992724920107f5fd07b4922", "029684f165042b44197bce605d81e3e9b22acb8ae677ea4ea3412307b3ff26ea6e", "0304571109f4e9dd3ce67133df452375597d20f583894cdd8ed09c65a3a3e3be5a", "034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff"]'

97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH

Verify (redeem script).

listunspent 97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH

[
]

getreceivedbyaddress 97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH

0.0

GitHub doesn’t force HTTPS by the way. We shouldn’t sign when served over HTTP.

#28

This was the transaction I send of 1 BKS.

8a5d9c19af910cc3b62faf97c554a78d1cb5d95c0c49013883061383b0243faa

#29

If I understand that right, both outputs are singlesig addresses.

Try sending an insignificant amount to 97zQy9VWLYcM6BeYGBv7bEJpRdxAy5cvEH.

#30

Well the ammount was send to: 9CXZXhnhp8HBx12Zr6JJmJmTm8qQWrsR6r but ended up in the address you see in the transaction ID. I’ve send 0.10 BKS to the address you mentioned.

#31

Hmkay. Great! Could I have the transaction ID for that one as well?