Help us test Nubits v2.1.0

Exactly that!
The blocks still need to be verified by the wallet application, but not downloaded from other Nu network peers.

Weak subjectivity at its finest. We can compile the source code and download directly from peers, but it takes a lot of time and effort. Or we can download from trusted Nu sources both the client and the blockchain. Shouldnā€™t we offer this bootstrap service? In some ways itā€™s also like a check pointing process.

They are not the same. Modified source code will compile and run. Modified blockchain will cause a re-download from scratch as I understand, as long as the network you see is good.

So you donā€™t need to trust the source of bootstrap file if you have trusted peers.

1 Like

true, so the burden of trust is even less for the boot strap than for the client software. All the more reason why we should offer a direct download, or something.

1 Like

right. for those paranoids an official sha256 can be provided

1 Like

Would be good, a full blockchain download took me almost 48h with V2.1.x. Maybe we can setup a torrent as the traffic to host these files might be high and expensive. We could even use something like Joystream later (when out of alpha), to pay users for seeding the files.

1 Like

+1

Until we have bootstrap files:
would you consider uploading the bare blockchain files somewhere?
Compressing might save some space.
And of course the Nu wallet needs to be exited - but why do I tell you that? :wink:

It would help big time being able to run nud 2.1.0 on my RaPi2, because of the low RAM requirements.
Downloading it on my RaPi2 will take some more days:

Sun Jan 17 17:59:29 UTC 2016
nud getinfo | grep blocks
    "blocks" : 205501,
Mon Jan 18 10:24:05 UTC 2016
nud getinfo | grep blocks
    "blocks" : 264482,

60,000 blocks in 16 hours or roughly 90,000 per day if the download speed stays the same.

@cybnate were you able to run Nu (QT) on mint in the meantime?

Will send you a PM

Havenā€™t tried yet, just have it running for 5 consecutive days. When no issues, I might give it a go over the weekend now Iā€™ve just managed to copy the files to another instance of Nu without downloading them from scratch.

I just had a crash of the Nu wallet application (v2.1.0; Windows x64 version).

The last lines of the debug.log are:

2016-01-19 16:24:04 ProcessBlock: ORPHAN BLOCK, prev=64d1ad696a6d92868b22
2016-01-19 16:27:52 BlockMap cleanup: 13447 removed
2016-01-19 16:28:29 received block f29e447af3ce559758e52a3989ad3ab1e070099c5fdc3d851d03b060b00c65d6
2016-01-19 16:28:30 Committing 4 changed transactions to coin database...
2016-01-19 16:28:30 SetBestChain: new best=f29e447af3ce559758e52a3989ad3ab1e070099c5fdc3d851d03b060b00c65d6  height=708240  log2_trust=39.804072  moneysupply(S)=826284469.3315  moneysupply(B)=3218302.5095  tx=1444556  date=2016-01-19 15:44:48 progress=0.004960
2016-01-19 16:28:30 ProcessBlock: ACCEPTED
2016-01-19 16:28:30 BlockMap cleanup: 25592 removed
2016-01-19 16:28:30 accepted liquidity info from BA9tumP4zyM1g2M8ZNieD2iAnMgdVPuQe3
2016-01-19 16:28:30 NotifyLiquidityChanged
2016-01-19 16:28:30 accepted liquidity info from BA9tumP4zyM1g2M8ZNieD2iAnMgdVPuQe3
2016-01-19 16:28:30 NotifyLiquidityChanged
2016-01-19 16:28:30 accepted liquidity info from BA9tumP4zyM1g2M8ZNieD2iAnMgdVPuQe3
2016-01-19 16:28:30 NotifyLiquidityChanged
2016-01-19 16:28:30 accepted liquidity info from BA9tumP4zyM1g2M8ZNieD2iAnMgdVPuQe3
2016-01-19 16:28:30 NotifyLiquidityChanged
2016-01-19 16:28:30 accepted liquidity info from BEU9G1YCwCtaVa3mMPvX4NcqKngbA2jJ7C
2016-01-19 16:28:30 NotifyLiquidityChanged
2016-01-19 16:28:30 accepted liquidity info from B8DZADD7UrMkzEmTWyvn2cEoxcnog1D8MK
2016-01-19 16:28:30 NotifyLiquidityChanged
2016-01-19 16:28:30 received block 853983cdd706b77cbfdc38a1ec8b5e1d0252e7c6a05706ee095f0849a86963a0
2016-01-19 16:28:30 ProcessBlock: ORPHAN BLOCK, prev=3576dad533799658f21f
2016-01-19 16:28:36 BlockMap cleanup: 16764 removed
2016-01-19 16:28:36 accepted liquidity info from BEbkDnBh71ZaXHXkr63HXP4bMda9m9BN7B
2016-01-19 16:28:36 NotifyLiquidityChanged
2016-01-19 16:28:36 accepted liquidity info from BEbkDnBh71ZaXHXkr63HXP4bMda9m9BN7B
2016-01-19 16:28:36 NotifyLiquidityChanged
2016-01-19 16:28:36 received block 951d8555bd7fc86b8ede537c7cd59705b14dd41a3ddba14c822456b70eda439b
2016-01-19 16:28:36 ProcessBlock: ORPHAN BLOCK, prev=2fc8460256e553791689
2016-01-19 16:28:44 BlockMap cleanup: 10442 removed
2016-01-19 16:28:44 received block 2fc8460256e55379168917bce72ec6f8c89d01150643bb6226a7021d97be2f11
2016-01-19 16:28:44 ProcessBlock: ORPHAN BLOCK, prev=1fcb0eb47b89df02bb4b
2016-01-19 16:28:52 BlockMap cleanup: 25517 removed
2016-01-19 16:28:52 accepted liquidity info from BEU9G1YCwCtaVa3mMPvX4NcqKngbA2jJ7C
2016-01-19 16:28:52 NotifyLiquidityChanged
2016-01-19 16:28:52 received block 3b4a221d58cba3797e934b35c9bd4533aaed670392e00ce18c1a73164a6a3644
2016-01-19 16:28:53 ProcessBlock: ORPHAN BLOCK, prev=853983cdd706b77cbfdc
2016-01-19 16:28:59 BlockMap cleanup: 16969 removed
2016-01-19 16:28:59 accepted liquidity info from BA9tumP4zyM1g2M8ZNieD2iAnMgdVPuQe3
2016-01-19 16:28:59 NotifyLiquidityChanged
2016-01-19 16:28:59 received block 64d1ad696a6d92868b22bead81d0c9bcd0ff99f1442dc5cb4710bf81fdf72ff8
2016-01-19 16:29:00 Committing 7 changed transactions to coin database...
2016-01-19 16:29:00 SetBestChain: new best=64d1ad696a6d92868b22bead81d0c9bcd0ff99f1442dc5cb4710bf81fdf72ff8  height=708241  log2_trust=39.804073  moneysupply(S)=826284509.3315  moneysupply(B)=3218302.5095  tx=1444558  date=2016-01-19 15:47:26 progress=0.004960
2016-01-19 16:29:00 Committing 3 changed transactions to coin database...
2016-01-19 16:29:00 SetBestChain: new best=3576dad533799658f21fe2f62c31187be27fa8d39c3f7a83c38da314a7c7fde9  height=708242  log2_trust=39.804074  moneysupply(S)=826284549.3315  moneysupply(B)=3218302.5095  tx=1444560  date=2016-01-19 15:47:49 progress=0.004960
2016-01-19 16:29:01 Committing 3 changed transactions to coin database...
2016-01-19 16:29:01 SetBestChain: new best=853983cdd706b77cbfdc38a1ec8b5e1d0252e7c6a05706ee095f0849a86963a0  height=708243  log2_trust=39.804076  moneysupply(S)=826284589.3315  moneysupply(B)=3218302.5095  tx=1444562  date=2016-01-19 15:47:07 progress=0.004960
2016-01-19 16:29:03 Committing 3 changed transactions to coin database...
2016-01-19 16:29:03 SetBestChain: new best=3b4a221d58cba3797e934b35c9bd4533aaed670392e00ce18c1a73164a6a3644  height=708244  log2_trust=39.804077  moneysupply(S)=826284629.3315  moneysupply(B)=3218302.5095  tx=1444564  date=2016-01-19 15:49:22 progress=0.004960
2016-01-19 16:33:57 Flushed 8355 addresses to peers.dat  114ms
2016-01-19 16:40:40 ProcessBlock: ACCEPTED
2016-01-19 16:40:41 BlockMap cleanup: 529034 removed
2016-01-19 16:40:41 ResendWalletTransactions()
2016-01-19 16:40:54 

I donā€™t see any differences in memory usage than the previous version
(win7 64)

I just fired it up on my win7 64-Bit machine (the x64 version):

332.228 k RAM equals approximately 324 MB RAM. I donā€™t know how much it consumed before.
The RaPi version consumes even less - unless you sync a blockchain with that one, which I currently do and the RAM consumption is increasing each minute.

Remark - the RaPi2 has 1 GB RAM, so 84.3% mean over 800 MB RAM consumption.

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
 4939 pi        20   0 1045m 821m 3056 S 100.4 84.3   1690:39 nud

Thatā€™s why I restart it from time to time (which I did just now). After a fresh start itā€™s like this:

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
 7843 pi        20   0  375m 163m 8052 S 195.3 16.8   3:02.40 nud

And yes, itā€™s really running and syncing the blockchain:

tail ~/.nu/debug.log
2016-01-21 12:08:46 received block 2b2f09b4c05b16dc8b21a899ae70662864050e06962134d92326fe328dab78e8
2016-01-21 12:08:47 SetBestChain: new best=2b2f09b4c05b16dc8b21a899ae70662864050e06962134d92326fe328dab78e8  height=394648  log2_trust=39.094131  moneysupply(S)=1004071280.849  moneysupply(B)=4672942.3474  tx=803237  date=2015-06-13 14:59:57 progress=0.002753
2016-01-21 12:08:47 ProcessBlock: ACCEPTED
2016-01-21 12:08:47 received block c1658e523fa3b89941d553a07d3e8812bc47d8789b5762fc4103b6b95b6ceb05
2016-01-21 12:08:47 SetBestChain: new best=c1658e523fa3b89941d553a07d3e8812bc47d8789b5762fc4103b6b95b6ceb05  height=394649  log2_trust=39.094135  moneysupply(S)=1004071320.849  moneysupply(B)=4672942.3474  tx=803239  date=2015-06-13 15:02:24 progress=0.002753
2016-01-21 12:08:47 ProcessBlock: ACCEPTED
2016-01-21 12:08:47 received block 047b660da7bd23faadea3781b17e200a89fed2a0d7af8ed36d9aecf598c97607
2016-01-21 12:08:47 SetBestChain: new best=047b660da7bd23faadea3781b17e200a89fed2a0d7af8ed36d9aecf598c97607  height=394650  log2_trust=39.094138  moneysupply(S)=1004071360.849  moneysupply(B)=4672942.3474  tx=803241  date=2015-06-13 15:04:47 progress=0.002753
2016-01-21 12:08:47 ProcessBlock: ACCEPTED
2016-01-21 12:08:47 received block 3a784db424045d9dffbf48617f7ba173244abfc8cacf56646fcda318fdc9eaeb

just go to sleep :stuck_out_tongue:
and let it run some days. At first ram is much less, then it rises!

Am I getting on your nerves? :stuck_out_tongue:

I had some time to catch up with 2.1 today. Iā€™m unable to reproduce the problem with the client hanging on the load screen on Windows 64, Ubuntu 32 or Ubuntu 64.

So to gather a list of the final user issues it was

  • client freezing on ā€œdone loadingā€ screen.
  • slow syncing of blockchain on 2.1

Iā€™m unable to reproduce the first issue, and it doesnā€™t appear that everyone is having the same issue. It could be due to local configuration or environmental. But it appears that once the data dir is cleared users are able to sync fine, so thereā€™s a potential fix. Iā€™m not really sure what to do about this. Given a clean environment the software operates as it should with the conversion and continuing to sync.

@sigmike has already explained the reasoning for the second issue. It shouldnā€™t be much of a problem though, as weā€™ll be able to provide a bootstrap file through download or torrents. Meaning people can download the whole blockchain at the max speed their internet connection will allow. Then all the client has to do is verify its contents.

Other than those issues the proposed improvements have been confirmed by myself and others from the community. The RAM usaged is cut by almost 50% in most cases. The new database and blockchain conversion is working successfully. The bootstrap file works in helping to quickly download a large portion of the blockchain for the client to verify instead of downloading from peers. There are many little aesthetic improvements to the client and some added functionality (such as quick access to debug.log from the config menu.).

There are many changes in this release and Iā€™m sure I was not able to test every little bit but, core functionality and targeted improvements for this release seem acceptable to me.

Given these results from my own testing, and feedback from the community I feel that moving forward with a 2.1 release would be okay at this point. @JordanLee and @sigmike, and the communities thoughts would be appreciated.

4 Likes

@CoinGame Could you provide explicit instructions as to what you mean by clearing the data directory?

Thinking it might be a synch issue, I let the client run for 4 straight days while stuck on the ā€œDone loadingā€ splash screen and was never able to get a GUI. OS is Ubuntu 14 32-bit.

Backing up your wallet files, deleting the .nu data directory, and starting from a brand new data dir. Starting the client will recreate the data directory, and then you can turn off the client to replace the wallet files with the ones you backed up. Itā€™s what resolved the issue for Cybnate.

1 Like

Can someone upload a mainnet bootstrap file please?

I am starting RC8 on a 64bit Ubuntu on the testnet with the bootstrap file. debug.log shows that nud is downloading 2014-08-xxx . With a 400MB bootstrap file shouldnā€™t nud start with some time in 2015? @sigmike

I will produce a 2.1 bootstrap file this week. Maybe tomorrow, but for sure this week. As well as setting up a torrent and direct download.

4 Likes

I am trying RC8 in win7 64 and it looks good. 430MB RAM but stuck at ā€œ5 weeks behindā€