@JaredKaragen
Would love to see this compiled from the new 2.4.3. Looking forward to it!
Me too. |
|
|
|
Spoke too soon. It was syncing to that, but now it's showing 174843 again. I really can't figure it out.
cli 1.4.5 or 2.0? 2.0, of course. |
|
|
|
Well, all coins are in the new wallet, so far so good.  Daemon synced to 167000, but is always telling something like Sync data returned a new top block candidate: 167000 -> 17xxxx. Now I'm syncing in my laptop, and daemon does show correct top block! What's going on? Having a hard time understanding, are you getting the correct or incorrect top block height? If it is the incorrect height, you will need to clear your data for the daemon. should be in First turn off your daemon, then navigate to the daemon files which should be located in C:\ProgramData\intensecoin in that folder, delete the folder labeled Imdb. This will allow you to resync. Turn the daemon back on and you are good to go. OK, that solved it! Deleted everything and it's now syncing again to 167xxx block! Spoke too soon. It was syncing to that, but now it's showing 174843 again. I really can't figure it out. |
|
|
|
Well, all coins are in the new wallet, so far so good. Daemon synced to 167000, but is always telling something like Sync data returned a new top block candidate: 167000 -> 17xxxx. Now I'm syncing in my laptop, and daemon does show correct top block! What's going on? Having a hard time understanding, are you getting the correct or incorrect top block height? If it is the incorrect height, you will need to clear your data for the daemon. should be in First turn off your daemon, then navigate to the daemon files which should be located in C:\ProgramData\intensecoin in that folder, delete the folder labeled Imdb. This will allow you to resync. Turn the daemon back on and you are good to go. OK, that solved it! Deleted everything and it's now syncing again to 167xxx block! |
|
|
|
Well, all coins are in the new wallet, so far so good. Daemon synced to 167000, but is always telling something like Sync data returned a new top block candidate: 167000 -> 17xxxx. Now I'm syncing in my laptop, and daemon does show correct top block! What's going on? Having a hard time understanding, are you getting the correct or incorrect top block height? If it is the incorrect height, you will need to clear your data for the daemon. should be in First turn off your daemon, then navigate to the daemon files which should be located in C:\ProgramData\intensecoin in that folder, delete the folder labeled Imdb. This will allow you to resync. Turn the daemon back on and you are good to go. I have intense wallet installed in 2 computers, desktop and laptop. On desktop it tries to sync to block 17xxxx, on laptop all seems fine, it's trying to sync to block 167035. I'll try to delete those files from desktop and start again. |
|
|
|
Well, all coins are in the new wallet, so far so good. Daemon synced to 167000, but is always telling something like Sync data returned a new top block candidate: 167000 -> 17xxxx. Now I'm syncing in my laptop, and daemon does show correct top block! What's going on? |
|
|
|
Well, all coins are in the new wallet, so far so good. Daemon synced to 167000, but is always telling something like Sync data returned a new top block candidate: 167000 -> 17xxxx. |
|
|
|
I started intensecoind.exe from 2.0.0 wallet after importing keys and it's saying It'll sync 174417 blocks.
What's going on here?
use cli 1.4.5 & *.bat file intensecoind.exe --add-exclusive-node 140.82.9.90:48772 --add-exclusive-node 62.48.164.60:48772 --add-exclusive-node 5.249.27.162:48772I did use those parameters, but are you saying I need 1.4.5 to properly sync?? If you are using the 2.0 wallet, it will sync just fine. You just need to make sure that you set those parameters. I did use those -add-exclusive-node. Tryed to use 1.4.5 intensecoind.exe, gives a ton of errors. Should I just delete blockchain files? 1.4.5 version doesn't work, I've been trying all day with no succes. Where did you find 2.0.0? Here https://github.com/valiant1x/intensecoin/releases/ |
|
|
|
I started intensecoind.exe from 2.0.0 wallet after importing keys and it's saying It'll sync 174417 blocks.
What's going on here?
use cli 1.4.5 & *.bat file intensecoind.exe --add-exclusive-node 140.82.9.90:48772 --add-exclusive-node 62.48.164.60:48772 --add-exclusive-node 5.249.27.162:48772I did use those parameters, but are you saying I need 1.4.5 to properly sync?? If you are using the 2.0 wallet, it will sync just fine. You just need to make sure that you set those parameters. I did use those -add-exclusive-node. Tryed to use 1.4.5 intensecoind.exe, gives a ton of errors. Should I just delete blockchain files? |
|
|
|
I started intensecoind.exe from 2.0.0 wallet after importing keys and it's saying It'll sync 174417 blocks.
What's going on here?
use cli 1.4.5 & *.bat file intensecoind.exe --add-exclusive-node 140.82.9.90:48772 --add-exclusive-node 62.48.164.60:48772 --add-exclusive-node 5.249.27.162:48772I did use those parameters, but are you saying I need 1.4.5 to properly sync?? |
|
|
|
|
I started intensecoind.exe from 2.0.0 wallet after importing keys and it's saying It'll sync 174417 blocks.
What's going on here?
|
|
|
|
|
I am curious too.
They started shipping yesterday, right?
|
|
|
|
I am using a Ryzen 1600 on Windows 10 and I am getting much better performance on cryptogone's C++ miner vs. the Java miner. I'm using only 8 of 12 threads. I'm using the avx2 version.
Not me with my Ryzen 7 1700. The hashrate is roughly the same. Also, does the java miner have a dev fee? |
|
|
|
|
So, are we on track for tomorrow's fork?
When can we start mining again?
|
|
|
|
Nice. This is faster on Intel CPU's than Java miner. Not so on Ryzen. Could it be more optimized for Ryzen architecture? |
|
|
|
They aren't ASICS! They are FPGA's!
There's a BIG difference. There are no ASIC's that mine Aeon.
I give up.
So they mine Aeon @ 40 Kh/s @ 60W, but the important thing is to accurately name the technology inside them. You must be a fun guy at parties. |
|
|
|
|
Of course.
And as I said, this happened after the attack to Intense Coin that led to its mining shutdown.
Pay attention, devs.
|
|
|
|
There are no cryptonight light ASICS. Please educate yourself on the difference. If ASICS were mining Aeon it would be 200mhs by now
Yes there is. Baikal Giant-N is one of them, maybe others mining secretly. Network hashrate was 22 Mh/s some days ago, now it is 47 Mh/s. Sure, 25 Mh/s in a couple of days, all CPU and GPU's, I presume. Intense coin blockchain suffered a 51% attack because devs neglected to update POW shortly after monero. After that, Aeon network hashrate doubled. Maybe Aeon devs want to suffer next 51% attack... Just kill ASIC mining with Aeon7 POW. |
|
|
|
|
Well, network hashrate DOUBLED in a week.
Of course ASIC's are mining.
|
|
|
|
With this new v7, it make win10system running lagging when mining. Anyone?
With XMR-Stak 2.4, no it doesn't. |
|
|
|
|
Show Posts
