python main.py --recipient BXKidrUiYNgRmDeDX61k6CASEJ2HjM8pUF --amount 0.1
Added multisig address to client, label = FLOT NBT multisig
T8pMQPDTW5P33Kr7uEsAT7g818PyM54zvY
Trying git pull...I’ve set an rpc port in nu.conf. This works for NuBot broadcasting liquidity with it.
The address formed begins with a T. Is that a testnet NSR address?
I still don’t have a clue how the script works.
Where does the script get the address (in my case “T8pMQPDTW5P33Kr7uEsAT7g818PyM54zvY”) from?
I don’t find any reference in any config for it.
I can confirm that “T8pMQPDTW5P33Kr7uEsAT7g818PyM54zvY” has been added to the (NSR) wallet automatically:
nud getaddressesbyaccount "FLOT NBT multisig"
[
"T8pMQPDTW5P33Kr7uEsAT7g818PyM54zvY"
]It seems to be a multisig NSR address:
nud validateaddress T8pMQPDTW5P33Kr7uEsAT7g818PyM54zvY
{
"isvalid" : true,
"address" : "T8pMQPDTW5P33Kr7uEsAT7g818PyM54zvY",
"ismine" : true,
"isscript" : true,
"script" : "multisig",
"addresses" : [
"SaRJkX5obxAsNxScezV6BhZt2GLLi4tvf6",
"ScL2JE6szuPJuNrmabKeVsHTf1QFjr45Fb",
"SVjDFMbAiiDNx2pbjdV54EZbGnbbZRMxEM",
"STWwZ6S5rssGUoAoqCTaF3boSo3aQYDU4v",
"SkG2BQ6syxGouBydd5CfU2mgamq5ZjxW3W"
],
"sigsrequired" : 3,
"account" : "FLOT NBT multisig"
}I digged deeper.
You guessed right with the NSR port and I’ve learned something about the nu wallet RPC:
the RPC port in nu.conf is the port to access the NSR wallet.
The RPC port to access the NBT wallet is incremented by 1.
I’ve adjusted git-multisig/config.py accordingly and ran the script again:
python main.py --recipient BXKidrUiYNgRmDeDX61k6CASEJ2HjM8pUF --amount 0.1
Added multisig address to client, label = FLOT NBT multisig
Multisig address seems valid.
Trying git pull...
Already up-to-date.
Updating address snapshot...
[master bc04355] 1448361280.89
1 file changed, 1 insertion(+), 1 deletion(-)
Counting objects: 7, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 354 bytes, done.
Total 4 (delta 1), reused 0 (delta 0)
To git@github.com:Lamz0rNewb/flot-operations.git
19974a1..bc04355 master -> master
Done.
This is your transaction hex:
01000000403d545602bb2a539844c41f845d68a66baeb26765572af93801f0f3ca46f1f85c0e6edf610000000000fffffffffdd47933815da84323e55aa139e59cd355c26984bb5a6f3ff9eb5b0e12b8daad0100000000ffffffff02e80300000000000017a91426c6f88ca8a0a47b6a015eac69c442b12f715e9f873c0f00000000000017a914f35b24f264597d66ba8c366a5005824bb6a06138870000000042Interestingly the NuBot config contains the RPC port that should target the NSR wallet; I bet NuBot internally increments that 
Sorry for all the trouble my lack of knowledge causes!
If you click on the top right of my link, you can see I added all the modes necesary for FLOT operations, so for BTC you could use either version. I have made a few improvements but each one is free to use the best workflow for them.
One feature that would be neat in this toolkit: taking a WIF, extracting the private key, then being able to use that to generate a new WIF of a different coin.
As much as I’ve walked thru the WIF format (and the cointoolkit code), I don’t quite understand why WIFs aren’t directly usable between coins – where exactly the coin ID is incorporated into the WIF in some way.
The use case would be: for anyone who already has a private key, to generate the “like” private key in another coin. Similar to the custom seed / brainwallet idea, it makes for less secrets to remember / record.
Edit: I wrote too soon. I see the current version has “This is a 64 char hex private key” which can serve this function
I have been adding more functions, you have full support to do what you originally wanted following these steps:
@JordanLee motion f99ddf406a32d39be7d614c13dc1ce63c96e4003 passed on Block #613,827 (13 Nov 2015 16:35:29) sets 14 days maximum as the time to allow new members to join FLOT by passing a motion.
That period ends Friday, 27 November 2015, 16:35:39. Around 24h from now.
@crypto_coiner motion is currently 1,748 votes out of 5,000. Even if every block from now until the period ends (24h = around 1440 blocks) votes for that motion, it will not pass in time.
Definitive FLOT voted members: @cryptog, @Dhume, @dysconnect, @jooize, @masterOfDisaster, @mhps, @ttutdxh, @woodstockmerkle
Would like to hear thoughts from other FLOT members and shareholders about @crypto_coiner joining us at a later date? Maybe @crypto_coiner could be the first to form the FLOT reserve team. This would be a backup group with members that can take over current FLOT members incase emergencies, personal situations or other events (for example underperformance) take place that require a FLOT member to step down. So FLOT has people ready to jump in to guarantee enough man power.
Other than that good to see we can start the next step in FLOT proceedings. So with the current amount of members in mind 7 in total how should we divide this over 3 crypto’s we need to manage? And also how many signers do we want for every currency to release funds.
I messed up with the list (sorry @jooize) while ordering alphabetically.
We are 8, now is corrected.
And I didn’t notice 
So 5 man NBT group, 5 man NSR group and 8 man BTC group?
Yes, what should we use for BTC, a 6 of 8 multisig, 5 of 8?
Hmm…I’d say 5 of 8 even though 6 of 8 is obviously safer I expect the times when we really need to quickly access our BTC the defend the peg (major NBT selling) those few hours extra that last signature could take could be crucial to maintaining our peg.
Without having evaluated it much, 5 of 8 seems safe enough and sounds like a good compromise like Dhume says.
+1
Would it help to create an overview will all pub keys per person and currency? And maybe store it on a gist as well to have a backup in case this forum is down?
If this sounds beneficial, I’m going to do it unless somebody beats me to it.
Will be afk for some hours…
Would welcome such role
Great synoptical overview.
Will make myself available in a more prepared way next time needed.
Looking forward to that occasion!
I will welcome a FLOT reserve team creation.
FLOT is comprised of 8 members. We need more multisig nodes to foster the decentralization of Nu.
@crypto_coiner would be certainly the first member of such a reserve team.
I’d join a reserve team if it just means I’m an understudy.