Nu client 0.5.3 beta release

The Plaza
#21

Hey folks,

The Windows and Linux builds of 0.5.3-RC3 are ready to play with. The SSL issue should be fixed now.

Windows: https://nubits.com/sites/default/files/assets/nu-0.5.3-RC3-win.zip
md5: 196e4d229892dfcf45eeee30d00f0859

Linux: https://nubits.com/sites/default/files/assets/nu-0.5.3-RC3-linux.zip
md5: ca63f13d6560ff91feda2a41488d9248

Thanks for looking at these for us!

pb

Edit: Links and md5’s updated. It should really be working this time. :slight_smile:

#22

Just downloaded 0.5.3-RC3 and installed. Checked twice it is 0.5.3-RC3 and it is. However I’m still getting the unsupported protocol error on 64-bit Windows 7.

I’m using this link: https://raw.githubusercontent.com/Cybnate/NuNet-datafeed/master/Cybnate-datafeed.json. Is it something with Github? That would be annoying as it leaves a nice track record when you change something. Very transparent.

#23

On raspberry pi I am getting the same error while ./nud start . Not sure is feed related.

edit: my bad, should have ./nud --daemon . thanks @CoinGame

1 Like
#24

Nope. It’s not github. It’s us. The issue is identified and we’ll have another build out today. Sorry about that.

#25

Sorry about that, folks! I needed to rebuild some dependencies on my build box. Here are the updated links and md5’s:

Windows: https://nubits.com/sites/default/files/assets/nu-0.5.3-RC3-win.zip
md5: 196e4d229892dfcf45eeee30d00f0859

Linux: https://nubits.com/sites/default/files/assets/nu-0.5.3-RC3-linux.zip
md5: ca63f13d6560ff91feda2a41488d9248

OSX: https://nubits.com/sites/default/files/assets/nu-0.5.3-RC3-osx.zip
md5: 4895fae153d7d7808c38182554f8c8ba

Edit: Updated with OSX build.

3 Likes
#26

Hopefully everyone working with data feeds can try this build out, and we can start getting some data feed providers. I think this is one of the most important builds that we’ve had in the development lifecycle. Getting to a full release with this is very important.

1 Like
#27

Successfully imported an https datafeed without getting “unsupported protocol” error on Linux Mint 64Bit. Thanks a lot!

2 Likes
#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.