KlausT's ccminer-cryptonight is running really nicely for me. https://github.com/KlausT/ccminer-cryptonight/releases

For anyone interested, alpha version of new wallet available for download here. Please note this is an ALPHA release and is only appropriate for those with an interest in testing a potentially buggy and unstable product. Send all bugs to me directly via DM on Slack - please not here on BCT as it is more cumbersome to monitor.



*link updated 8/31 0300 UTC with fixed version to address crash upon startup for some users

In other news, the pool has been running well following some code updates. I sent out ALL compensation payments from the launch day fork a couple days ago, so everyone should be paid. Alex and I feel good about where the coin is at right now and hopefully you do, too. It seems we are finally out of the weeds of initial struggles getting established.

Thanks for your patience and support. Please join us on Slack, Twitter, Reddit and Facebook if you haven't already!

There was a 20-30 minute period of downtime today while logs were cleared and some things updated. Sorry!  

Hi all, spent several hours today working on the pool and coin code. New test code has been deployed to the pool server. It is expected to significantly improve stability and issues with payments. However, it is still experimental, so please use hashing power with extreme prudence. Git commit coming soon.

I'll address all of your PMs soon as all of my time was consumed with the aforementioned today. 

I do see your address in the original pool payment system, but it's only 320 coins. Did you solo mine the rest? We are only able to compensate for whatever was earned in the pool, since we have record of those earnings. Otherwise we can't 'trace' the blockchain of what went where due to the ring signature anonymous nature of CryptoNote. PM me or DM me @intense-valiant on slack to finish this convo please.


My apologies, Linux binaries still need to be rebuilt for the latest source. I'll jump on it tomorrow!


Hey, PM me or DM me on slack (@intense-valiant) your wallet address for confirmation and we'll get it sorted. As a reminder, we DELAYED payments to people that haven't verified their identities since if you ever shared your wallet address, it was possible for someone else to claim your payout. Hope that makes sense.


Hi lupanar, yes, please PM me your original wallet address with proof that you own it (or DM @intense-valiant on slack), otherwise you will have to wait for the reason stated above.


Hey oslak, from reading your other post, it looks like you accidentally deleted the wallet file. Can you recover it from the recycle bin? Please try claiming all bounties if you haven't yet as that's free INT!

Hi, please re-download the latest version of the wallet as this is outdated. You will be stuck on block 573 until you update. Where did you download that from?

CoinStalker, I do want to add the repair option from Monero into our wallet and the option to export/import private keys so we can try to prevent issues like this in the future. Please DM me on slack @intense-valiant and I can try to manually repair your wallet until such options are available.


My apologies, Linux binaries still need to be rebuilt for the latest source. I'll jump on it tomorrow!

Hi all, PMs replied to  


Hey AltsBoom, please note it is 2^-19 x 10^-8. Here's a screenshot of the Excel formula, and a printout of it:




kollom, I'm sorry I really would like to help you but I can't say I completely understand your issue. It looks like based on your prior screenshot you were mining on a non-Intense hosted pool - therefore only the pool owner can help you. If you had coins marked for payout but they never came, or you had them then they disappeared, it was due to the pool you were mining on forking. This is something I mentioned as a potential consequence of unstable pool code. Either way, I would strongly suggest contacting the support for the pool you were mining at.

Haven't heard from you yet... How did you contact me?  

For some reason mods deleted my previous post, here it is again..


  Best laugh of the day, thank you bryan


I would recommend a different fork as we experienced issues with zone117x's fork, but that is indeed how to start! You will need a Linux system and to compile our coin on the system, and run a daemon and wallet. Most of the pool forks have READMEs to follow on how to get them running. Follow their README and follow ours and you will have built binaries capable of running a pool!

[mod note: removed response to spam post]

Font made slightly larger to enhance readability vs standard posts from the community:

Yes, as noted by many, our pool is DEAD again. Perhaps this was actually something best left alone. The code update that got the pool running again appeared promising, but clearly we still have issues. We did warn you that this pool was still considered experimental so hopefully that bought us some understanding from you all.  I've spent the last several hours trying to debug things without having great success. There are many moving parts between the pool, the daemon, the wallet, etc.

I'm going to reiterate at this point that pool operations may be something best left to the pros. The Intense hosted pool forked around block 1509 because it, once again, produced a bad payment transaction. Anyone now mining on other pools, or solo, will be moving aside our pool fork - which got up to block 1591, but the bad transaction in 1509 means nobody else will 'recognize' those coins in the blockchain.

I'm really sorry for anyone that used hashing power from blocks 1509 to 1591 on our pool because those blocks are more than likely never going to confirm due to the bad transaction. I did put another request out to the dev that helped rectify the pool previously, so perhaps he can be of assistance again.

At this time the smart thing is for the Intense team to adopt our previous position and say, "We are clearly not good at hosting a pool and need to move on to other things."

I'll try to reinstate the pool if I hear back from the other dev but please don't count on mining at the Intense hosted/sponsored pool.

We originally did plan to abandon the INTENSE hosted and sponsored pool as it was just a massive headache..

But I am a perfectionist and couldn't leave it alone. I submitted some troubleshooting inquiries to more experienced minds. Luckily one great individual came through. It was a hail mary pass to the endzone! Please consider donating to clintar@github if you're grateful for the pool working again.

I was also hoping to get it working so we wouldn't have to reimburse people for TWO failed pool payments. As you know we are reimbursing for anyone that pool mined on the original genesis block before the relaunch (Alex is posting details on that shortly, but here's the website for that). Now we do not have to also reimburse for the second pool dying, as I verified all payments are working properly.

I'm really happy to have this back on track. I will be getting some much needed sleep tonight. And my office will be very warm from my two video cards hashing away at the pool - without interruption. Hopefully. Lol.

Sorry SD, we are no longer operating a pool. That was an Intense operated 0 fee pool. Due to numerous issues with payment processing we have pulled the plug on that. Hopefully a real pool operator comes along soon to offer pool mining options.

You can ignore this error, it's because there are still a few lingering nodes on the network with the original genesis block ID. Your client will not sync with them. It's just warning you that there is some 'confusion' in the syncing. As long as you see 'SYNCHRONIZED OK' in green text in the daemon,  or '*** You are now synchronized with the network and can now start simplewallet ***', you have nothing to worry about.


Announcement coming by this evening with a page to reclaim those coins, as long as they were from pool mining. If you solo mined we have no way to keep track of your balance - the Ring signatures of cryptonote means we can't trace transactions in the blockchain. However, we have database records from the pool of all balances and payouts, and that is exactly what will be reimbursed.

Hey all, as stated, new pool is up and running: www.intensecoin.com/pool2

The IP is the same for the new pool, but ports are different - 4444, 6666 and 9999

Payouts from old pool will occur after all transactions mature (about block 1070).

If you're struggling to find a GPU miner, look for XMR mining guides since we use the same backbone (CryptoNote).

Hey everyone,

As you have all noted, the pool is NOT reliable. Please consider looking into other options for mining. I am working on it now, so the pool is down. It was a waste of hashing power to have it running while defunct, since no blocks were forming. I'll bring it back up after I have addressed the bug in question which is periodically stalling the pool.

We really didn't want the 0 fee pool to be the focal point of our VPN coin... But it is how most people are mining and it seems to be of great interest to all, so this is taking priority.

If you're not already in Slack, please join us using the link from page1 as things are much more up to date!

Fixed, sorry about that. FYI, some mac users are reporting issues running the binaries - please obtain MacPorts and then run `sudo port install boost` to rectify.


Pending balances in the pool will not register until the block you were mining has fully matured, which takes 40-60 minutes.

Hi everyone, a long overdue reply here from the dev. I have been busy fixing things, maybe breaking things , recompiling and handling support in Slack. Thanks very much to the community members that have been echoing messages from Slack to here.

First, I'm not sure if it was already clearly stated that the pool payments from the original chain were recovered and all payments will be reimbursed. Every single one. Nobody will lose any of the coins they already mined when it's all said and done. As long as you possess your original wallet address - just the address, doesn't matter if you still have the wallet file. If you don't have it anymore, we'll still figure something out to make things right.

There has been a lot of criticism, and rightly so. Unfortunately, this is technology we are dealing with, and while it is not perfect, the humans behind it (me and alexius) are even less perfect. Mistakes were made and lessons were learned. This is my first cryptocoin launch, and many of the mistakes trace back to sheer inexperience.

You all deserve answers and I'll try to walk you through the series of events and my perspective.

I want to address concerns about lost revenue from mining. I would like to point out that when the decision to reset the blockchain occurred, the pool was - once again - stalled. From the pool's inception this morning when we launched, we experienced difficulties with the pool. It is based on an open source codebase for many cryptonote pools but it required tweaking to work properly with INT. These bugs were not visible in small-scale testing with only one miner, and without kilohashes of mining power. In any case, poor code in the payment processing lead to many pool server restarts, which somehow created some bad and corrupt payment transactions. This required manual intervention and resulted in 30+ min of non-accepted blocks on a couple different occasions. There were some forks occurring while the pool was stalled. In any case, the blockchain would have required manual manipulation in one form or another. If it's any consolation, it appeared most pool mining clients did restart as soon as the pool went up again on the new chain. From the moment the pool on the new chain went live, we jumped from 85 blocks to 135 blocks in only several minutes time. So if you were paying for mining services or running your own rigs, hopefully you only missed the time that the pool was down while I was recompiling the code for a new block, and of course the time that the pool was stalled.

We also are offering the pool with 0 fee as a courtesy and to engage the community. No profits are made from this pool or any of the hours of troubleshooting that went into it. However we would strongly encourage someone to setup another pool, and in fact we would prefer that so the entire blockchain isn't controlled by one pool!


Sure, let's talk about the decision to restart the chain immediately as opposed to waiting. I felt it was necessary to restart the chain as soon as absolutely possible rather than delaying it, as any time spent on the old chain would be more time people wasted mining senselessly - on a chain that would be abandoned. I was under the impression, based on heavy engagement in the Slack community, that nearly everyone was using the pool to mine. Many people were mentioning how solo mining was not practical due to the high difficulty and the fact that the pool was so rapidly pumping blocks out. I could also see the astronomical 600+ kH/sec hash rate on our pool. I knew people were spending good money to mine our coin. I wanted them up and running again as soon as possible. And I knew that the pool would continue to mine as it was after I restarted the chain. I am a people-pleaser, and I like to deliver things as soon as possible. It just made sense to me to get it going again now rather than later, especially as it seemed most interested parties would not be affected (since pool mining would auto restart on the new chain).

Was it the right decision? Perhaps not! Alexius89-2 is in a 12 hour different timezone than me and I had to make a decision. So I did. In retrospect, it could have been different, and I'm sorry it wasn't. We're doing everything we can to make things right for everyone involved.

And since you mentioned "devs already had their miners set up" - sure, I had a miner going, at 5 kH/sec. That's less than 1% of our pool hashing power. It's negligible. I wish I could say I had more than that in the pool, but I just don't have those kind of resources. My goal in getting things immediately up and running again was to address the interests of everyone, not just "the devs".

1. We will definitely reimburse all payments as they were made from the pool. I am not certain yet if we can see all unconfirmed (pending) balances -- more time will be needed to analyze the database.

2. Sure, although as long as people didn't delete their wallet files, the 'old' addresses from previous chain still work just fine on the new chain. Sorry if there was some confusion about this. I'm still using my old address from the original chain.

3. We are doing the best we can to own this, and I think your point is very reasonable. We have no problem paying all restitutions from our pocket.

Much was learned today - about community engagement, problem resolution, and communication. I can confidently say I did my best, and I gave it my all... and I'll continue to do that while I'm privileged to be a developer on this project.

We are very excited for the future of Intense, especially due to how much community interest there is. This is a project we are immensely passionate about, and we couldn't have anticipated so much support from the community.
Virtual private networks (VPNs) interacting with the blockchain, in the manner we proposed, is almost unheard of. Let's forge into unknown territory together... it probably won't be painless, but it will be better than day 1 was.  

Don't forget to follow us on Twitter, Facebook, Reddit and join our Slack channel!!!

Hello all,

What a wild ride this has been...

If you are a newcomer, you need not read this post.

If you have already downloaded the INT wallet or miner, you will need to unfortunately re-download. My sincere apologies for the troubles.

I have re-uploaded the Windows miner and GUI wallet and am working on compiling and uploading the rest.

After you re-download, you need to delete your data directory -- on Windows, this is %userprofile%\appdata\roaming\intensecoin, on linux and Mac, it's ~/.intensecoin

After you re-open the daemon or miner, you will need to most likely point it to a seed node with the correct blockchain by using this command:

I did go ahead and update the difficulty configuration for the ports per your recommendations, thanks! I want to hold off on restarting the pool, though, which is required to load the new configuration, as every time I restart it people get very excited here.  


Pool was down because I took it down. It was stalled due to some bad txns in the blockchain. Pool isn't being DDoS'd yet


I'm sorry, I really don't know what to tell you other than to try a different miner. There aren't many GPU miners that work on cryptonight. I can only endorse the one built into the tool, and cpuminer-multi by tpruvot as I know both work. It looks like you're trying CCminer - I think ccminer has issues with cryptonight.