Nu client 0.5.3 beta release

The Plaza
#28

Here’s the OSX client …
https://nubits.com/sites/default/files/assets/nu-0.5.3-RC3-osx.zip
md5: 4895fae153d7d7808c38182554f8c8ba

Enjoy!

#29

Is this a stable release? I mean can I safely use for minting as well?

1 Like
#30

Yup! Mint away, and use a feed if you’d like.

1 Like
#31

Can confirm that my experimental datafeed via Github is now working witn Win7-64 bits. Feel free to try it out, copy or have a look: https://raw.githubusercontent.com/Cybnate/NuNet-datafeed/master/Cybnate-datafeed.json

If you use it, it will overwrite your own settings unless you keep all the boxes (Custodian, Park Rates, Votes) unticked in your wallet. It should make a sound and very briefly show 'Fetching feed, please wait"

Don’t have the signatures figured out yet. Will look at that over the weekend.

Edit: had a quick look.
Signing address: ShTrp9wbgnhZudk4eYXtBtcMyeBziGzUpc
Signature URL: https://raw.githubusercontent.com/Cybnate/NuNet-datafeed/master/Cybnate-datafeed.txt
Can verify message in the client with ‘Verify message’, but datafeed functionality says: Datafeed signature check failed
Some weird invisible characters at work? Have copied and signed the raw feed of the json file from the browser. Any ideas?

1 Like
#32

I use the link: https://discuss.nubits.com/c/nushares/data-feeds
and got this:
The initial download failed with the following error:
Data feed size exceeds limit (10240 bytes)

#33

That address doesn’t lead to a validly formatted data feed, but to a subforum here…

#34

@Cybnate can you share what string you’re signing the message with?

#35

@miner you must supply it the raw github link.

https://raw.githubusercontent.com/Cybnate/NuNet-datafeed/master/Cybnate-datafeed.json

It should work using the link above.

#36

Tested on Win 7. It is working. Nice job!
I ll try signing later on.

1 Like
#37

By the way, my current nu data feed. https://raw.githubusercontent.com/cryptog/nu_data_feed/master/cryptog_nu_data_feed.json

1 Like
#38

I’m using the raw output from the json in Chrome browser and ‘select all’ and paste into sign message window of the wallet.

Here is the output as I capture it (without start and end message) and how the wallet is signing and verifying it:
-start–
{
“custodians” : [
{
“address” : “BTgryZQ1dQNJYMjm74K3ajdRnDfsCjh3c3”,
“amount” : 499.0
},
{
“address” : “BB1eCrqde2g5vWTH7RsaBJ8NWTUF2D8ogq”,
“amount” : 1.0
}
],
“parkrates” : [
{
“unit” : “B”,
“rates” : [
{
“blocks” : 8192,
“rate” : 0.0000
},
{
“blocks” : 16384,
“rate” : 0.0000
},
{
“blocks” : 32768,
“rate” : 0.0000
},
{
“blocks” : 65536,
“rate” : 0.0000
},
{
“blocks” : 131072,
“rate” : 0.0000
},
{
“blocks” : 262144,
“rate” : 0.0000
},
{
“blocks” : 524288,
“rate” : 0.0000
},
{
“blocks” : 1048576,
“rate” : 0.04984105
},
{
“blocks” : 2097152,
“rate” : 0.09968211
},
{
“blocks” : 4194304,
“rate” : 0.23923705
}
]
}
],
“motions” : [
“1ce96336ac866c29cbcbf0908b0752b0065a3af4”,
“bda115840291067ba0814032f0c93d4d5900a5cf”
]
}
----end—

Hope that helps, I haven’t tried other browsers or formatting tricks yet. Will play a bit more over the weekend. But apparently a straightforward copy and paste doesn’t seem to work for some reason.

Signature URL - how one exactly constructs that?
#39

My fault. It seems I didn’t explain the signature process very well in the documentation. I’m heading home and will update it.

I think what you’re missing is that the NSR address has to be part of the signature, in front of the feed info.

#40

Thanks. the data feed size error is gone.
But what does it fetch and where I can see the data?
What should I fill in the other two blank columns?

Please consider me as a noob and ELI5.

#41

you can see the data inside the fields [custodian votes, motion votes and parking rate votes] of your client.

#42

Miner you can see the data that it’s downloading by viewing the link in your browser. Also, as @cryptog said you can view the votes in your client the same way you would view votes that you’ve added yourself.

#43

Thanks. Now I got it.

#44

This is my signature. https://raw.githubusercontent.com/cryptog/nu_data_feed/master/signature.txt Can you clarify about the NSR address that you must put inside the signature?

#45

The signature check is very sensitive to content change, even white space or different line endings. All these intermediaries (the browser, copy/pasting, etc.) may alter the content.

I recommend using the the RPC commands instead to provide data feeds.

For example here is a batch script for windows that dumps your vote and signs it:

"C:\Program Files\Nu\daemon\nud.exe" getvote >"c:\MyDataFeed\vote.json"
"C:\Program Files\Nu\daemon\nud.exe" signmessage SedtEJa1dm6pSLagYXKvw5Sef3iH9VfwXC <"c:\MyDataFeed\vote.json" >"c:\MyDataFeed\vote.json.signature"

Replace the NSR address and the paths and save this to DumpVote.bat somewhere on your computer. Then you can just run it to dump your vote and the signature.

The Nu client must be running with RPC enabled (i.e. having server=1 and an rpcuser and rpcpassword in your nu.conf).

You can even add votenotify=c:\Path\To\DumpVote.bat to nu.conf to make the client dump your vote each time you modify it.

1 Like
Signature URL - how one exactly constructs that?
#46

After figuring out that I did get inconsistent signatures, it occured to be a problem with the datafeed itself as published on Github. Obviously I managed to hide some additional characters in there which were not taken when copied for signing. After I used the output of getvotes from NUD and added that into my feed and signed it, it worked. Thanks @sigmike

Please check out my datafeed here: [Discontinued] Cybnate's Nu datafeed - BETA

1 Like
#47

Tks for the tip. It worked like a charm.