I'm sorry but if the info changed from what you submitted, there's no way to rectify that. How would we know to look under a different name? As mentioned before, making exceptions and manual changes for 1200+ people just is not plausible.

I really appreciate everyone's understanding on this. I'm sorry some people were missed.

Airdrop payments are going out now (finally!). All payments were sent with the payment ID
My sincere apologies for the day-ish delay. It's going to take some time for all 23 payments to go out because I have to wait for a block confirmation before I can send the next payment (funds locked due to change). all payments sent

We decided to pay those whose Facebook likes could not be validated, as it was not stated in the original airdrop requirements, and probably only a few people saw my message to remove the privacy features. This is reflected in the payment sheet - should_be_paid is set to YES even for users that failed the Facebook checks.

In total, 1227 people applied. 565 of those people were found to be valid submissions. I appreciate the feedback about publishing the list first to rectify problems, but we already had a couple staff members crosscheck a good amount of randomly sampled entries to ensure things were on track. Sorting through 600 possible messages about how entries were wrongly validated for reason XYZ is just not plausible. You can view all of the information here.

Hi all, my apologies the payments were not sent by 2/28 as promised. I have a couple people on our team verifying the list, because from the way it looks right now, only 20% of the applicants will actually be paid. A very large number of people either inputted invalid Slack/Discord info, or their Facebook profiles were either a) not public for viewing likes b) did not like us or b) did not have 100 friends. I believe the extra time spent verifying these results will ensure fairness and reduce issues. I'll update you as soon as possible.


The verifications were definitely run by being logged in to an account.

No. The airdrop list is only a list of wallet IDs that submitted, nothing more. Every single person in the list needs to actually qualify per the rules on the OP.


Good point


The airdrop list is only a list of wallet IDs that submitted, nothing more. Every single person in the list needs to actually qualify per the rules on the OP.


Hi, thanks for doing that. As long as the other requirements are met you're all set.


You used FB

A quick heads up to anyone that used their Facebook for the FB or Twitter requirement of the airdrop: if you do not have the pages visible that you have liked, or your friends, we cannot validate that you have met requirements. We will run the check again on 2/28 but if you don't have the information visible, it's impossible for us to know if you actually liked us or have enough friends (100).

To check if your FB profile is set correctly, log out of your FB account and visit your FB profile link with `/likes` on the end. e.g.  https://www.facebook.com/zuck/likes. If you cannot see IntenseCoin listed in the likes, or you cannot see your number of friends on your main profile page, your privacy settings are too restrictive and will not allow you to qualify for the airdrop.

Xmas airdrop campaign finished! We ended with 1,227 applications (2.5mil ITNS distribution). View the final list of wallets here: https://intensecoin.com/airdrop-submissions/

Payments will be sent Feb 21 to Feb 28 as described in the original post.

Thanks for your interest!

Thanks so much for your support and 'big picture' perspective, canibalgb.

Upgrading to beta is up to you, this is all detailed in our news post: https://intensecoin.com/2018/02/12/new-daemon-and-wallet-in-beta/

Yes you can export pvt keys in new wallet

In the current scheme of POW crypto, pools are necessary for mining. It's inefficient and cumbersome to have everyone mining solo.

Monero has been discussing possible revision of the POW algo to deter ASICs (and NiceHash). We are following this closely and may follow suit if XMR institutes changes. In the meantime there is nothing that can be done. Even if the pools 'ban' NH or do not open difficulty ports to accommodate NH, it's still trivially easy for someone to operate a private pool and point NH at it.

I spoke with Vlad and he raised a valid point. Even if we post a screenshot or picture of the premine wallets, since those images can be easily forged, it doesn't really offer any reassurance or create trust. Our goal is to establish and maintain user trust based upon our actions and the products of our work. I know that's probably not the answer you wanted but as with all considerations in this project, we are focused on the long term and big picture.

Unfortunately a tracking (or view) key only shows incoming transactions, so it's not super useful. The premine wallets only have 1-2 incoming TXs.

I've inquired with our security lead (Vlad) to determine a smart and secure way to demonstrate that these funds are intact. I'll follow up after I hear from him.

Also, forgot to mention above, the pool was updated yesterday:

The pool software was upgraded and improved to be better, faster and stronger, which means more blocks! Thanks for your continued support and patience. Issues with disconnects and timeouts should be resolved. Fee reduced to 1.75%.

We're in the process of devising a serverless approach to accommodate the new rebase software for a PPLNS pool.

Hi all, I have been asked by a few people to come here and post because people think I am gone or dumping coins or something   Quite the contrary! First, please see my news post from this hour, our XMR rebase beta is now public and ready for testing:

https://intensecoin.com/2018/02/12/new-daemon-and-wallet-in-beta/

As others have observed, we have been more active than ever on Github with daily commits:




And that does not even begin to acknowledge how much internal work and development is ongoing for the VPN. I've been swamped with the rebase while Lukas, Vlad and Miguel are all working very hard on our VPN and Browser Extension (BE).

The products will come, but it's going to take time. That's on our roadmap.

In any case, ThePigWee will be here to chat and represent ITNS while our devs continue diligent work on the backbone of Intense Coin, which is our VPN and BE. I'm very happy to have him on board and he is in close communication with the devs. Don't be afraid to ask him questions!

In fact I can take full credit for the idea... and I'm the founder  

If it was not for the VPN project requiring the use of integrated addresses, which we only came to the conclusion of as a team because it's the only encrypted method of on-chain communication that readily exists, we probably would not have rebased. But as was discussed already elsewhere, the rebase offers significant advantages in many areas. Monero has dozens of developers contributing to a great codebase. The decision to rebase is not unusual, as many other coins have taken a similar route. Please also appreciate that our development team worked extensively to ensure the rebase is occurring without a hardfork. It's really only a POSITIVE thing! Glass half full not empty 

Fusion transactions: they allow consolidation of small inputs in your wallet so you can send larger transactions (for example, try to send 500,000 coins at once when all of your wallet balance comprises tiny 20-30 ITNS payments from a pool). Without this feature you will experience some limitations for TX size and anonymity/mixin level. While the feature is safe to use, I'm not sure if it's completely enabled, as it was disabled in the past. 1.4.2 was in progress before we switched to focusing on the XMR rebase.

In short, it's not fully tested in terms of being enabled, but you're welcome to try it if you want. The 1.4.2 release was only pushed to add the ability to export secret keys in plaintext.

Try again please, this is just network issues on your end, but I also reduced the file size of the Linux appimage to 291mb

Good memes about ITNS mooning and lambos



Update RE XMR rebase - sync appears to be finally stable (it was falling off after periods of time due to issues with fees and TX sizes), pool APIs are communicating properly with the daemon. Both legacy CLI and GUI clients were updated this evening to include a mechanism to export secret keys, which can then be used to import the "old" ITNS wallet into the new XMR-based wallet. Mind that any "old" ITNS wallets imported into the "new" XMR-based software will NOT be able to be restored via 25 word seed, as they were not generated in a word seed compatible fashion. You must make a new wallet in 1.4.2.1 or later (pre-release at the moment) to take advantage of word-based seed restoration.

Exchange expansion is a work in progress, we will announce news when it's ready


Yes, backup your wallet - in MULTIPLE PLACES! - and you will be able to restore your address and balance fine. See Vlad's post about backing up your wallet: https://intensecoin.com/2018/01/18/how-to-backup-your-intense-coin-wallet/


See post above, you should always definitely have MULTIPLE backups of your wallet available!!

There is no possibility of losing your funds unless you start messing with the pre-release wallet, since we are still considering it to be strictly alpha at this point. Just wait until we officially announce information about a release version of the new wallet, which will include migration instructions.

Hi, if you filled out the airdrop form for the XMas airdrop, you're all set. No other airdrops are available right now.

LOL.. Discord does look a bit flashy, although I had never thought of it the way you described. Can't unsee it now 

The requests for a Telegram are really getting pressing! I reached out to @soapboxhero and @SlowGrowth to ask about the feasibility of this. We are hesitant to add another social media platform because it's already challenging to maintain communications on our existing 3-4 platforms (Reddit, Discord, Slack, BCT - not to mention FB/Twitter!)

No, although you are encouraged to!