[ANN][XCN] Cryptonite - NEW Thread | 1st mini-blockchain coin | Bounties!

[d5000]

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.   

Just tested this latest windows wallet, old laptop with mobile connection synced in 20 minutes from scratch. 

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.

[chrysophylax]

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.    

Just tested this latest windows wallet, old laptop with mobile connection synced in 20 minutes from scratch.  

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

[pallas]

About the "many gpu" issues of the miner, I will look into it ;-)

[chrysophylax]

About the "many gpu" issues of the miner, I will look into it ;-)

You are one in a million mate ...

Thanks for that.

Working on the compiles later tonight also, still can't get them sorted under both Fedora 27/28 x64 (due to many other factors - especially the updated gcc) and CentOS 7 x64, so we can start testing Obsidian (our stratum) properly under our new environment (Pyroxene (theMINE)).

#crysx

[susutao83]

This is very impressive. But I would like more detail informations. How i can get the roadmap of this pj?

[tbearhere]

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.    

Just tested this latest windows wallet, old laptop with mobile connection synced in 20 minutes from scratch.  

Try the core version.

I will keep on syncing it though. 

[e.nexus]

About the "many gpu" issues of the miner, I will look into it ;-)

You are one in a million mate ...

Thanks for that.

Working on the compiles later tonight also, still can't get them sorted under both Fedora 27/28 x64 (due to many other factors - especially the updated gcc) and CentOS 7 x64, so we can start testing Obsidian (our stratum) properly under our new environment (Pyroxene (theMINE)).

#crysx

A fix has been applied for Fedora 28.

The configure options will be:  ./configure CPPFLAGS="-std=c++11 -fPIC" --disable-hardening --with-incompatible-bdb --disable-tests

[chrysophylax]

About the "many gpu" issues of the miner, I will look into it ;-)

You are one in a million mate ...

Thanks for that.

Working on the compiles later tonight also, still can't get them sorted under both Fedora 27/28 x64 (due to many other factors - especially the updated gcc) and CentOS 7 x64, so we can start testing Obsidian (our stratum) properly under our new environment (Pyroxene (theMINE)).

#crysx

A fix has been applied for Fedora 28.

The configure options will be:  ./configure CPPFLAGS="-std=c++11 -fPIC" --disable-hardening --with-incompatible-bdb --disable-tests

I'll check this out later tonight when I am able to ...

it won't be long into the compile to see if it all works, though if that is the only setting that is required, then it won't be difficult to change it manually if need be.

Now for the GPU limitation in the miner pallas has, and we will be set

CentOS 7 x64 is still giving us headaches with compilation, so if there is something that needs to be set there also, it would be greatly appreciated also.

All the help currently is much appreciated.

#crysx

[e.nexus]

About the "many gpu" issues of the miner, I will look into it ;-)

You are one in a million mate ...

Thanks for that.

Working on the compiles later tonight also, still can't get them sorted under both Fedora 27/28 x64 (due to many other factors - especially the updated gcc) and CentOS 7 x64, so we can start testing Obsidian (our stratum) properly under our new environment (Pyroxene (theMINE)).

#crysx

A fix has been applied for Fedora 28.

The configure options will be:  ./configure CPPFLAGS="-std=c++11 -fPIC" --disable-hardening --with-incompatible-bdb --disable-tests

I'll check this out later tonight when I am able to ...

it won't be long into the compile to see if it all works, though if that is the only setting that is required, then it won't be difficult to change it manually if need be.

Now for the GPU limitation in the miner pallas has, and we will be set

CentOS 7 x64 is still giving us headaches with compilation, so if there is something that needs to be set there also, it would be greatly appreciated also.

All the help currently is much appreciated.

#crysx

There were also changes to the code for boost1.66 so you'll need a new clone.
I'll have a look at centos tonight.

[pallas]

New blockchain snapshot:

https://mega.nz/#!8IwTmIYC!zsfCcTsqRFy8WnGkBfNYuY2ZjPi8TT5SCRKz6wJvWsg

[chrysophylax]

About the "many gpu" issues of the miner, I will look into it ;-)

You are one in a million mate ...

Thanks for that.

Working on the compiles later tonight also, still can't get them sorted under both Fedora 27/28 x64 (due to many other factors - especially the updated gcc) and CentOS 7 x64, so we can start testing Obsidian (our stratum) properly under our new environment (Pyroxene (theMINE)).

#crysx

A fix has been applied for Fedora 28.

The configure options will be:  ./configure CPPFLAGS="-std=c++11 -fPIC" --disable-hardening --with-incompatible-bdb --disable-tests

I'll check this out later tonight when I am able to ...

it won't be long into the compile to see if it all works, though if that is the only setting that is required, then it won't be difficult to change it manually if need be.

Now for the GPU limitation in the miner pallas has, and we will be set

CentOS 7 x64 is still giving us headaches with compilation, so if there is something that needs to be set there also, it would be greatly appreciated also.

All the help currently is much appreciated.

#crysx

There were also changes to the code for boost1.66 so you'll need a new clone.
I'll have a look at centos tonight.

Already done - and compiles well ...

Thanks for that.

The wallet compiles well in Fedora 28 x64 and works perfectly, but because of the screen, the wallet and font are tiny. The wallet can't be resized (as with a huge amount of them I found out) on a 4K screen. Not complaining, just a fact I thought I would share. Almost nothing can be done from what I can see about it, unless the screen resolution is lowered, which defeats the purpose of having a 4K Screen in the first place.

CentOS 7 x64 compile would be awesome, which would allow us to build and test our stratum (Obsidian) against it.

I wonder if similar configure commands would be required to compile? Though CentOS 7 x64 has older versions of gcc and boost (not to mention OpenSSL crippling) which would probably fail. I haven't tried and I am running out of time to try tonight. Maybe tomorrow.

This will open a new area of functionality for XCN in the backend, especially for us, so we will keep working on it.

Being one of the CWI-Supported Coins, we will also have it on the CWI-WebSite when the section of the website is completed later this year.

Have a good one.

#crysx

[e.nexus]

About the "many gpu" issues of the miner, I will look into it ;-)

You are one in a million mate ...

Thanks for that.

Working on the compiles later tonight also, still can't get them sorted under both Fedora 27/28 x64 (due to many other factors - especially the updated gcc) and CentOS 7 x64, so we can start testing Obsidian (our stratum) properly under our new environment (Pyroxene (theMINE)).

#crysx

A fix has been applied for Fedora 28.

The configure options will be:  ./configure CPPFLAGS="-std=c++11 -fPIC" --disable-hardening --with-incompatible-bdb --disable-tests

I'll check this out later tonight when I am able to ...

it won't be long into the compile to see if it all works, though if that is the only setting that is required, then it won't be difficult to change it manually if need be.

Now for the GPU limitation in the miner pallas has, and we will be set

CentOS 7 x64 is still giving us headaches with compilation, so if there is something that needs to be set there also, it would be greatly appreciated also.

All the help currently is much appreciated.

#crysx

There were also changes to the code for boost1.66 so you'll need a new clone.
I'll have a look at centos tonight.

Already done - and compiles well ...

Thanks for that.

The wallet compiles well in Fedora 28 x64 and works perfectly, but because of the screen, the wallet and font are tiny. The wallet can't be resized (as with a huge amount of them I found out) on a 4K screen. Not complaining, just a fact I thought I would share. Almost nothing can be done from what I can see about it, unless the screen resolution is lowered, which defeats the purpose of having a 4K Screen in the first place.

CentOS 7 x64 compile would be awesome, which would allow us to build and test our stratum (Obsidian) against it.

I wonder if similar configure commands would be required to compile? Though CentOS 7 x64 has older versions of gcc and boost (not to mention OpenSSL crippling) which would probably fail. I haven't tried and I am running out of time to try tonight. Maybe tomorrow.

This will open a new area of functionality for XCN in the backend, especially for us, so we will keep working on it.

Being one of the CWI-Supported Coins, we will also have it on the CWI-WebSite when the section of the website is completed later this year.

Have a good one.

#crysx

I added a fix for centOS 7. If it's not merged you can see in the pull reqs. Same config options as Fedora works.

[drays]

Hi guys

sorry is I am beating dead horse here, but anyway - is there a AMD GPU Windows miner for this coin? I tried to use Claymore's one (version taken from latest Nicehash miner), but it doesn't seem to work with suprnova.
All other miners are seemingly supporting Nvidia only. Am I missing something?

[e.nexus]

Many developers create new coins only to seek their private interests, and hope that Cryptonite is not.

XCN is 4 years old and the developers aren't paid.

[e.nexus]

The wallet compiles well in Fedora 28 x64 and works perfectly, but because of the screen, the wallet and font are tiny. The wallet can't be resized (as with a huge amount of them I found out) on a 4K screen. Not complaining, just a fact I thought I would share. Almost nothing can be done from what I can see about it, unless the screen resolution is lowered, which defeats the purpose of having a 4K Screen in the first place.

HighDPI scaling support was added in the wallet's Qt updates.

You can try starting the gui from a console with: QT_SCALE_FACTOR=2 ./cryptonite-qt

[e.nexus]

Many developers create new coins only to seek their private interests, and hope that Cryptonite is not.

XCN is 4 years old and the developers aren't paid.

Paid, what did you imply, e.nexus?
XCN has amazing, creative ideas which can be further developed that in turn will boost the project to the Moon.
By now, XCN has gone far distance from its beginning 4 years ago.

I imply that it's not a new coin and the developers aren't seeking their own private interests.

[chrysophylax]

The wallet compiles well in Fedora 28 x64 and works perfectly, but because of the screen, the wallet and font are tiny. The wallet can't be resized (as with a huge amount of them I found out) on a 4K screen. Not complaining, just a fact I thought I would share. Almost nothing can be done from what I can see about it, unless the screen resolution is lowered, which defeats the purpose of having a 4K Screen in the first place.

HighDPI scaling support was added in the wallet's Qt updates.

You can try starting the gui from a console with: QT_SCALE_FACTOR=2 ./cryptonite-qt

Thanks again mate ...

This works quite effectively in the HiRes deoartment, and is easily assigned a scipt for execution. I could not find any of these details anywhere, which is why docs are important, but in saying that, I admit I didn't delve too deep in any docs to find if this is anywhere.

CentOS 7 x64 works perfectly compiling under the same commandline options, so we hope all functionality runs smooth also. The daemon will be setup in the Pyroxene platform over the weekend and theMINE pool will be setup for alpha testing in the coming days after that.

A lot more work ahead for us in the coming week, which includes all this mentioned.

If there is some way that can overcome the GPU limitation in the miner, then we will also have theFARM testing the pool at a higher capacity.

Thanks again,

#crysx

[sekker]

Hi guys

sorry is I am beating dead horse here, but anyway - is there a AMD GPU Windows miner for thin coin? I tried to use Claymore's one (version taken from latest Nicehash miner), but it doesn't seem to work with suprnova.
All other miners are seemingly supporting Nvidia only. Am I missing something?

we dont have a AMD miner yet, latest not work at suprnova. we are researching someone for doing and it is in our bounty program #2 post of the thread.
sorry.

#sekker

[tbearhere]

New blockchain snapshot:

https://mega.nz/#!8IwTmIYC!zsfCcTsqRFy8WnGkBfNYuY2ZjPi8TT5SCRKz6wJvWsg

Thanks pallas..giving it a try.

EDIT: That worked...all synced up. Thx pallas. 

[br@indr@in]

Hi Pallas,

just a litte hint: In the news from today it was announced that on Novaexchange they have problems with the integration of the Cryptonite wallet (->"XCN - There are integration issues between the XCN wallet and Nova.").

Best regards:

#br@indr@in