Ninjastic
PostEdited versionsQuotes to this post
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][XCN] Cryptonite - NEW Thread | 1st mini-blockchain coin | Bounties!
by
chrysophylax
on 04/07/2018, 06:15:52 UTC
Quote from: d5000 on July 03, 2018, 10:58:05 PM
Quote from: antantti on July 03, 2018, 09:13:21 PM
Quote from: tbearhere on July 03, 2018, 10:49:09 AM
Still syncing the wallet. I may take another 3-4 weeks to fully sync.  At 8 hrs. a day. I don't know why it's taking so long. Already been 2 weeks.  Tongue  Smiley
Just tested this latest windows wallet, old laptop with mobile connection synced in 20 minutes from scratch.  Cool
As far as I read here, it syncs fast when you start from scratch and download a fresh (mini-)blockchain. If you want to sync from a previous state, the wallet may download all blocks between your last "local block" and the current block height, which can take a while if you connected to the network long ago. However, it only should store the last mini-blockchain permanently.

Some pages ago I meant I had read a fix or workaround for this "problem" (which isn't really a problem because you help validate while you sync). A rough workaround is obviously to delete the old blockchain data and sync from scratch again.

We still cannot compile under Fedora 27/28 x64 - or CentOS 7 x64 for that matter ...

The code is based primarily on the older gcc libraries, and Debian/Ubuntu based distros, so it is always difficult to compile properly under RHEL based systems (usually in a sandboxed and static format for our servers). So even to test this sync and blockchain (let alone support a pool) is always going to be a challenge for us.

This means that this information that you are supplying with regards to blockchain, sync, nodes lists, and others, are quite important to us when we eventually do get through the compilation issues.

@pallas - FYI. The miner that I referred to earlier refuses to load - PERIOD. It will run, but as soon as it starts to mine, there is NO allocation of GPU to ANY GPU in theBEAST. The smaller 5GPU system has no issues. So whatever the issue here, if the miner will not assimilate the use of 13GPU's to even start, then there is no way we can set it to just work with 1GPU, no matter what I have done to get it started. The miner just does not move past the initialization stage when it 'sees' the system has 13GPU, even when -d 0 (or any other GPU) is forced.

Any way of fixing this mate?

#crysx