Tier 4 Fund Management Discussion

[dysconnect]

Thanks. I’ve revisited the nu docs and saw that it wouldn’t work consistently. In your cases perhaps it’s because the transaction is still in the mempool or for some other weird quirk. I’ll check more carefully; nu isn’t totally consistent with Bitcoin.

For the meantime, @masterofdisaster please update to the newest git-multisig (now does not require the newest git). Thanks for your patience and sorry for the inconvenience!

[masterOfDisaster]

Will do!
…but not right now…

Thank you for your patience and help!
It would be much less convenient and reliable to forge transactions manually.

[dysconnect]

The newest version of git-multisig does not rely on txindex=1 anymore, so nobody has to reindex their blockchain. I’ll update the guide shortly.

[jooize]

Could you link to the guide. (72 posts back now) That’s the guide, right?

[dysconnect]

There’s a link in the first post of the other thread; I’ll aim to put stuff in a readme file too.

[jooize]

Put the post in README.md, maybe.

@jooize When you need to use the scripts, you can restart Nu.app with the argument “-server”. Like “/path/nu -server”. You don’t have to do it now, but it’s probably a good idea to make a shortcut that runs with -server by default.

Do you know a good way of doing that? Can I modify the .app package?

Shortcuts… in OS X, aliases. Can they have arguments like in Windows…

How do I pass command line arguments to Dock items?

Sweet! Follow #2 and replace Firefox with Nu, basically.

How do I pass command line arguments to Dock items?

Has to be repeated every update. Could we have this in the official build so one only has to edit the shell script to add arguments? It’s hardcoded at /Applications/Nu.app now though. Is the app’s path given to the script? https://stackoverflow.com/questions/4774054/reliable-way-for-a-bash-script-to-get-the-full-path-to-itself

[ttutdxh]

Who will be in the NSR group?
Is every FLOT member ready to start testing with the BTC multisig?

[dysconnect]

The motions of @dhume and @crypto_coiner are still hanging there, so we’re short of people for the NSR group. Unless of course the overlap is 3 people. For BTC, do you think we can use https://coinb.in?

[cryptog]

It seem that i will be in the nsr group.
So i need to create a nsr pubkey?

[masterOfDisaster]

I will post an NSR pubkey as well.
Should we create a new thread to separate the topics a little bit?

[mhps]

This problem is still not solved. The script keeps asking for username and password at “…” I gave up after feeding it u/p more than 20 times. Any idea @dysconnect ?

I haved tried to run python main.py --recipient BXKidrUiYNgRmDeDX61k6 CASEJ2HjM8pUF --amount 0.12. The scripts starts but asked rpcusername and pword many times like this

Enter username for jsonrpc at 127.0.0.1:14002: xxx Enter password for flotty in jsonrpc at 127.0.0.1:14002: Multisig address seems valid. Snapshot of BqyRzFtWXDmjxrYpyJD42MLE5xc8FrB4js not found on disk. Trying to fetch online... Newest remote snapshot for BqyRzFtWXDmjxrYpyJD42MLE5xc8FrB4js found at: dc-tcs Updating address snapshot... Enter username for jsonrpc at 127.0.0.1:14002: xxx Enter password for flotty in jsonrpc at 127.0.0.1:14002:
…

By the way what is the role of github in the signing process? Back when peershares was developed github turned most potential helping community members away.

[dysconnect]

Using git(hub) is optional and only used to publish the tracked balance of the address. Later I may also try to do the signing bit over git. It’s possible to use bitbucket or even alternative channels to do the same thing, depending on actual need and how easy it is to retrieve the snapshots from the server.

I prefer using git as it is a convenient standard and will try to support diverse needs such as a hatred for github; over the long term there should be multiple alternative channels other than blockexplorer to retrieve unspent outputs.

About that problem, I’ve only encountered it when the RPC username and password don’t match nu.conf. Try to check that the settings in config.py match all rpc-related settings (port, username, password) in the same custom nu.conf that you’ve loaded.

[mhps]

This problem is still not solved. The script keeps asking for username and password

I figured it out. A special character (#) in the password must have caused the rpc url to fail. Unless quoting or escape chars can be used with http, rpc password had better stick to alphanumerics here.
Output

Multisig address seems valid.
Updating address snapshot…
Done.

This is your transaction hex:
010000007109545602bb2a539844c41f845d68a66baeb26765572af93801f0f3ca46f1f85c0e6edf
610000000000fffffffffdd47933815da84323e55aa139e59cd355c26984bb5a6f3ff9eb5b0e12b8
daad0100000000ffffffff02b00400000000000017a91426c6f88ca8a0a47b6a015eac69c442b12f
715e9f87740e00000000000017a914f35b24f264597d66ba8c366a5005824bb6a061388700000000
42

[masterOfDisaster]

Well done, @dysconnect!
I pulled the latest master of git-multisig and tried again:

python main.py --recipient BXKidrUiYNgRmDeDX61k6CASEJ2HjM8pUF --amount 0.1
Added multisig address to client, label = FLOT NBT multisig
Address does not match given public keys (note that order matters)
Trying git pull...
Warning: Permanently added the RSA host key for IP address '192.30.252.130' to the list of known hosts.
Already up-to-date.

Updating address snapshot...
[master 89a3d07] 1448352430.94
 1 file changed, 1 insertion(+), 1 deletion(-)
Counting objects: 11, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (8/8), 672 bytes, done.
Total 8 (delta 2), reused 0 (delta 0)
To git@github.com:Lamz0rNewb/flot-operations.git
   0684083..89a3d07  master -> master
Done.

This is your transaction hex:
01000000ae1a545602bb2a539844c41f845d68a66baeb26765572af93801f0f3ca46f1f85c0e6edf610000000000fffffffffdd47933815da84323e55aa139e59cd355c26984bb5a6f3ff9eb5b0e12b8daad0100000000ffffffff02e80300000000000017a91426c6f88ca8a0a47b6a015eac69c442b12f715e9f873c0f00000000000017a914f35b24f264597d66ba8c366a5005824bb6a06138870000000053

Updating the github repo worked:

Lamz0rNewb/flot-operations/blob/master/BqyRzFtWXDmjxrYpyJD42MLE5xc8FrB4js/unspent

ninjaedit: Discourse seems to cache embedded github contents. In real the blockcount is at 627911

[dysconnect]

Great, thanks for testing. This line is still a bit off though:

Address does not match given public keys (note that order matters)

Can you check that the address BqyRz… is in your wallet with label/account name “FLOT NBT multisig”?

[masterOfDisaster]

Can you check that the address BqyRz… is in your wallet with label/account name “FLOT NBT multisig”?

Checked that. Wasn’t there. I wasn’t aware of the need for that.
Fixed it:

nud -unit=B setaccount BqyRzFtWXDmjxrYpyJD42MLE5xc8FrB4js 'FLOT NBT multisig'

Now it looks like this:

python main.py --recipient BXKidrUiYNgRmDeDX61k6CASEJ2HjM8pUF --amount 0.1
Added multisig address to client, label = FLOT NBT multisig
Address does not match given public keys (note that order matters)
Trying git pull...
Already up-to-date.

Updating address snapshot...
[master 3eda25c] 1448356263.27
 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
   89a3d07..3eda25c  master -> master
Done.

This is your transaction hex:
01000000a629545602bb2a539844c41f845d68a66baeb26765572af93801f0f3ca46f1f85c0e6edf610000000000fffffffffdd47933815da84323e55aa139e59cd355c26984bb5a6f3ff9eb5b0e12b8daad0100000000ffffffff02e80300000000000017a91426c6f88ca8a0a47b6a015eac69c442b12f715e9f873c0f00000000000017a914f35b24f264597d66ba8c366a5005824bb6a06138870000000053

Better now - I don’t thin so…?
The output is pretty much the same…

Wait - I shouldn’t have needed to add the multisig address manually to the wallet, right?
It was not there until after I added it… but the script still seems to not recognize the multisig address.

[dysconnect]

I’m guessing that you’ve set the RPC port to a Nushares port. It should be a Nubits port - likely still 14002 by default.

If that doesn’t work, find this block of code in chainutils.py:

 try:
     s = rpc_server.addmultisigaddress(config.SIGN_THRESHOLD, config.PUBKEYS, config.ACCOUNT)
     print "Added multisig address to client, label =", config.ACCOUNT
     if s == config.ADDRESS:
         print "Multisig address seems valid."
     else:
         print "Address does not match given public keys (note that order matters)"

Add this line after the “s = …” line:

 print s

And see the output.

[masterOfDisaster]

 python main.py --recipient BXKidrUiYNgRmDeDX61k6CASEJ2HjM8pUF --amount 0.1
Added multisig address to client, label = FLOT NBT multisig
T8pMQPDTW5P33Kr7uEsAT7g818PyM54zvY
Trying git pull...

set the RPC port to a Nushares port. It should be a Nubits port - likely still 14002 by default

I’ve set an rpc port in nu.conf. This works for NuBot broadcasting liquidity with it.

[dysconnect]

The address formed begins with a T. Is that a testnet NSR address?

[masterOfDisaster]

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:
01000000403d545602bb2a539844c41f845d68a66baeb26765572af93801f0f3ca46f1f85c0e6edf610000000000fffffffffdd47933815da84323e55aa139e59cd355c26984bb5a6f3ff9eb5b0e12b8daad0100000000ffffffff02e80300000000000017a91426c6f88ca8a0a47b6a015eac69c442b12f715e9f873c0f00000000000017a914f35b24f264597d66ba8c366a5005824bb6a06138870000000042

Interestingly 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!