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

[romasalah]

Run getpeerinfo, any incoming = true?

with which socks protocol?

Inbound connections are false in socks 4 and 5. when I turned to non proxied settings, I see the cryptonite client using the port 8253 in cmd's netstat. but still no inward connections, I'm confused.

UDPATE:

it Magically worked after I locked the wallet, removed "port=8253" from cryptonite.conf. allowed a range of ports on my router, rebooted the router ad waited for 3 hours. now it show 11 connections, 3 are in.

[teosanru]

Run getpeerinfo, any incoming = true?

with which socks protocol?

Inbound connections are false in socks 4 and 5. when I turned to non proxied settings, I see the cryptonite client using the port 8253 in cmd's netstat. but still no inward connections, I'm confused.

UDPATE:

it Magically worked after I locked the wallet, removed "port=8253" from cryptonite.conf. allowed a range of ports on my router, rebooted the router ad waited for 3 hours. now it show 11 connections, 3 are in.

Configure rcport 8252

[nu1mlock]

I've got a similar problem with connections. I've enabled upnp (on both router and wallet), opened both port 8252 and 8253 (and several other ports as well to be sure) on my router and disabled Windows firewall but still only get 8 connections. I've tried it on two different routers and two different internet connections.

The only way I can get more than 8 is if I use DMZ, but I would prefer not to.

That first made me believe I had done something wrong but after opening ports for other needs, they work fine, but still can't get it to work for the wallet for some reason.

[romasalah]

Run getpeerinfo, any incoming = true?

with which socks protocol?

Inbound connections are false in socks 4 and 5. when I turned to non proxied settings, I see the cryptonite client using the port 8253 in cmd's netstat. but still no inward connections, I'm confused.

UDPATE:

it Magically worked after I locked the wallet, removed "port=8253" from cryptonite.conf. allowed a range of ports on my router, rebooted the router ad waited for 3 hours. now it show 11 connections, 3 are in.

Configure rcport 8252

it had it configured earlier. thanks. Now I want to connect my remote rig to the same client. any idea on how this can be done? I managed to connect 2 rigs on the same network using the local IP and the rpcport. should I just use the internet Ip of my client machine in my miner machine?

[romasalah]

I've got a similar problem with connections. I've enabled upnp (on both router and wallet), opened both port 8252 and 8253 (and several other ports as well to be sure) on my router and disabled Windows firewall but still only get 8 connections. I've tried it on two different routers and two different internet connections.

The only way I can get more than 8 is if I use DMZ, but I would prefer not to.

That first made me believe I had done something wrong but after opening ports for other needs, they work fine, but still can't get it to work for the wallet for some reason.

I forgot to mention that I have DMZ enabled for this machine as well. but I think that it didn't make a difference

[qwep1]

The second day I can not sync What version of the wallet and where can I download it for windows

[antantti]

There really is something wrong with the wallet/ daemon, both linux/ windows. No time to dig in right now but there is something.

Possible first aid for solo miners, try to run wallet on a rig with a powerful cpu. OC one or two cores if possible. Getting less stale shares?

edit: looks like it is qt.

[robo2]

The second day I can not sync http://picua.org/img/2017-07/15/501z4h4ymq20jzx3f89m3daiy.jpg What version of the wallet and where can I download it for windows

(Download wallet) and Full Snapshot from 2017-07-07 from mainpage

[krnlx]

There really is something wrong with the wallet/ daemon, both linux/ windows. No time to dig in right now but there is something.

Possible first aid for solo miners, try to run wallet on a rig with a powerful cpu. OC one or two cores if possible. Getting less stale shares?

i3-4130 , + CFLAGS solved all my issues except memory leaks. (I restart manually once in 24h)

[antantti]

There really is something wrong with the wallet/ daemon, both linux/ windows. No time to dig in right now but there is something.

Possible first aid for solo miners, try to run wallet on a rig with a powerful cpu. OC one or two cores if possible. Getting less stale shares?

i3-4130 , + CFLAGS solved all my issues except memory leaks. (I restart manually once in 24h)

If I had to guess it is qt.

edit: After couple of hours of testing, cryptonited does it, minor cpu usage. Qt sucks windows/ linux.

[nu1mlock]

There really is something wrong with the wallet/ daemon, both linux/ windows. No time to dig in right now but there is something.

Possible first aid for solo miners, try to run wallet on a rig with a powerful cpu. OC one or two cores if possible. Getting less stale shares?

i3-4130 , + CFLAGS solved all my issues except memory leaks. (I restart manually once in 24h)

If I had to guess it is qt.

Both cryptonited and qt crashes at least twice per 24h for me. And ever time the database gets corrupted so I have to keep an updated backup on another PC.

[antantti]

There really is something wrong with the wallet/ daemon, both linux/ windows. No time to dig in right now but there is something.

Possible first aid for solo miners, try to run wallet on a rig with a powerful cpu. OC one or two cores if possible. Getting less stale shares?

i3-4130 , + CFLAGS solved all my issues except memory leaks. (I restart manually once in 24h)

If I had to guess it is qt.

Both cryptonited and qt crashes at least twice per 24h for me. And ever time the database gets corrupted so I have to keep an updated backup on another PC.

Qt has been crashing on me. I will let cryptonited run, so far it looks good. Linux/ windows.

If solo mining, do NOT run qt. Better?

<antantti out for a couple of days>

[megainarmy]

Cut down the light, the computer rebooted, the wallet does not start correctly. Will now have to copy the file 07-07-2017 network and wait a long time to sync ((
Is it possible that the wallet has no protection from the hard shutdown ? And if so, what to do in these situations ?

On one of the rigs, the wallet just flew out without giving errors and rig stop (i found that was crash nvidia driver - i'll try to remove a little bit of overclocking)

8 connections in wallet - in my rigs, where dynamic IP! (I realized that to fight it is useless) - in this case I have about 25-30% orphans (stale blocks)  
Where static IP I have up to 45 connections in wallet. - in this case I have 5-8% stale blocks.

P.s.:
Please tell me how to use cryptonited ? How do that cryptonited install in my directory (not to c:/users/...) ?
Thank's for your patience!  

[sabercrypto]

when will there be a new pool? suprnova were not consistent always disconnecting

[barrysty1e]

when will there be a new pool? suprnova were not consistent always disconnecting

getting tired of posts like this.
ive been putting a shit-tonne of time into this, when i can afford to spare the time.
it seems a lot of people have the something for nothing attitude.

pool will be available when the code is done and testing is complete.

[barrysty1e]

For those having issues with the wallets lagging out/memory usage, whilst solo-mining against the wallet; make sure you adjust your ccminer config so -s is at 5 or 10.

When pool mining -s 1 or -s 2 is fine, however it will cause issues for any QT wallet being polled that often/quickly.
The linux daemon seems to handle it fine

[robo2]

Have somebody compiled pallas ccminer?? I am linux noob

[megainarmy]

Cryptonited game over... ( -s 2 in miner). The same crash is in cryptonite-qt.

http://prntscr.com/fwcer6

[barrysty1e]

Cryptonited game over... ( -s 2 in miner). The same crash is in cryptonite-qt.

http://prntscr.com/fwcer6

For those having issues with the wallets lagging out/memory usage, whilst solo-mining against the wallet; make sure you adjust your ccminer config so -s is at 5 or 10.

When pool mining -s 1 or -s 2 is fine, however it will cause issues for any QT wallet being polled that often/quickly.
The linux daemon seems to handle it fine

[megainarmy]

  okay. I'll try -s 10. Thank's!