All, I am very sorry for the aggravation and frustration. I apologize to those that were not paid for multiple submissions. We will make this right. I have already sent coins to three individuals that contacted me with the correct wallet address from their multiple submissions (96cf3921c1946f87d019df827bf1b5a59fb2488fd46d0c12b1c6c48de2d40025).

I was not aware that Alex had asked people to submit multiple times. It would also seem that there could have been some nefarious third party skimming BCT for signatures and submitting new entries using your profile link. I must admit this is not something we anticipated. However, we have learned from our mistakes and will do better next time. I also want to apologize as I was not fully read in on the intricacies of this situation - as you know the signature campaign was Alex's responsibility but he left Intense, and SlowGrowth planned to fulfill these duties instead. However, SlowGrowth has been swamped with RL matters, leaving our clueless dev (me) to try and figure this out. I did not do very well apparently

If your payment was excluded or not made because of 'intentional multiple submissions', please PM me the CORRECT wallet address (as you have multiple listed and I am not sure which is correct) and I will pay you according to your rank.

Thanks for your patience.

Sure, I will elaborate: anyone that submitted multiple entries, with multiple wallets, and/or multiple ranks, was deemed sneaky. You also put a '0' in front of your member ID in addition to supplying multiple wallets. Putting a 0 at the front of your member ID is 100% a manual process... and I can imagine it would only be done to fool the system.

There were also some users that purposely encoded the user ID part of the member URL, again to look different in the database, but it's the same member in the end.

Our system would not even allow you to submit multiple times with the same wallet ID, as it would say 'You're already in but we updated your information, thanks'. If a duplicate BCT profile URL was inputted, the system would alert you 'Sorry, but that Bitcointalk profile was already used.' -- these items in combination seem pretty straight forward to indicate: don't purposely tamper with submissions to be listed multiple times in the database.  

Okay folks I wrote some code to query Bitcointalk and check rank, number of posts, blah blah, and hand filtered some sneaky users in the data. All in all, 66 people were paid for the last round. Congratulations and thanks for participating!

Please feel free to view the data for the payments and submissions here: https://docs.google.com/spreadsheets/d/1JJWxX-YF4gQucFNFTzzx9_KVOZKRyrWfa--ca2swxCo/edit?usp=sharing

Yes, you can absolutely do that now, although we  are planning to add integration to allow the 'new' wallet to open 'old' wallet files. But if you want seed restoration NOW for your existing coins, that's your only option. And seed restoration will not be available for pre-XMR rebase imported wallets because they weren't generated in a way that is compatible with mnemonic seeds.

your old address works fine, do nothing

You will need to resync but it only takes 1-3 hours at most with the new client, and this will become faster once more new clients are up and running on the network.

I apologize for not explaining things more clearly. Fortunately, nothing NEEDS to be migrated, and this is why a lack of information was provided. You can always keep using your old, non-word-seed recovery friendly wallets if you want. And until we push an update requiring a hardfork for ring CT or other new features (probably in 2-3 months), you won't be required to even update the software.

I am happy to report that Monero works better out of the box on Linux, Mac and even ARM distros without requiring dependencies. Their deployment process, like all of the codebase, is just more mature than BCN.


Sure, there are no specific requirements listed if I recall correctly

No problem, you can change it now, as our agreement was only to hold it until the end of the round.

There will be no lost coins, the blockchains are 1:1 compatible. What is not to like about the dev team recognizing a mechanism to improve our product? Crypto is rapidly changing, I am sure you know that, and adaptability and flexibility are absolutely imperative. The news post emphasized that the rebase made sense from many perspectives, rather than being solely related to the VPN. In any case, when you are developing massive and complex software, requirements change over time.

I want to stress that this is a very good thing for the coin, it opens a lot of doors for us and helps future proof our products.

Thanks for your feedback darkrise, we appreciate your support. I'll mention the list to the team and see what they think. I apologize but I'm not familiar with typical bounty procedures.

My apologies Crate but it won't happen since we are rebasing to a completely different GUI wallet in the near future. However, Monero also offers integrated addresses, which include the payment ID right in the 'address'.

It means the Intense console and graphical interfaces will be changing, and a lot of behind the scenes pieces will be updated to work more smoothly. It means we will have increased compatibility with exchanges, pools and other third parties. It means the ITNS code is being hugely upgraded and improved, and we're very excited. Outside of that I do not have any information to add beyond what was stated in the news post, but we'll update you as things evolve.


The team is continuing to work on pursuing additional exchanges. I don't have any updates to provide you as nothing is certain yet. The news as of now is: "still no news". We will report as soon as something is guaranteed. It may be easier with the XMR rebase, but these talks are not on hold until the rebase is complete.


Use the --data-dir argument when launching the software. E.g. --data-dir f:\intensecoin

My apologies again, SlowGrowth has been very busy with real life matters (emergency). We really appreciate your guys' patience. Please do not worry, the entries are still recorded in the database, and bounties will be paid. Thank you.

Hi all, Alex or Slowgrowth will post an update on the signature campaign soon. We have not forgotten about this but the team members are busy with some other matters at the moment. Thanks for your patience.

It's quite a challenge to integrate third-party GPU miners with the wallet, mostly because the majority of anti-viruses and browsers block mining software from downloading or executing. This could really interfere with the usage and adoption of our products. That is why only a proprietary CPU miner is included with the wallet in its current form.

In the future we may look more closely into integrating GPU miners but for the time being, we are comfortable only including a proprietary CPU miner. Especially because there are many different GPU miners available, and people like to use certain ones, and often configure them in different ways. Anything we bundle with the software would have to be a "one size fits all" solution and lack configurability, again meaning most miners would use third-party apps anyway.

We acknowledge that this delay was not something we were pleased about, either. But please look at the big picture. In the end, we will have a much more successful product, and additional products (the browser extension will be here in 2 months at most). ITNS still has plenty of things to be happy about, and much to look forward to. The team is in it for the long haul, and you better believe we are executing buy orders right now 

Interesting idea. The wallets already offer options for password encryption so adding 2FA might be overkill.


--

Official pool update (http://intensecoin.com/pool/): Pool payout frequency reduced to once every 2 hours to reduce transaction issues for users. If users inputs in their wallets are comprised of only very small amounts of coins, it becomes a challenge to send large amounts of coins in one transaction later.