Not for now, is too complicated to set other fork now, specially when our head tech cryptocoderz is very busy wit other projects, besides we had a super virtual campaign to check how many people use this features and we are not happy with the number of participants, but we focus in other things more according with our initial philosophy of make a coin that every one can use , and regarding the demands of usability we are working in a software that is much more usefull than a masternode and will be the icon and flag of the tattoocoin project.

 is almost ready as i told days ago we are with the final test .
Official faucet is ready too i will post the link very soon and new explorers from cryptoguru are being built.

http://www.cryptoconverter.rocks/

I guess I must have been to late to the party lol.
I'll just go back to what I was doing.
Anyone wanting to sell ESP hit me up!!

How to mine?
Fire up your preferred miner with the following parameters (replace WALLET with your wallet address):

How to set different difficulty?
You can use the parameter d=? in your password to set the desired difficulty, good for nicehash etc.

Explorer
https://hexpool.com/explorer/INSN

A dollar shouldn't be too hard to achieve and is just a matter of time.  INSN at a dollar each will still not be in the top 100 on coinmarketcap.com  That proves how undervalued INSN is at the moment.  INSN is easily a top 100 if not top 50 crypto currency. 

oh, here is your issue, nobt wallet running only on any Windows x32. you will need to install VirtualBox-5.1.22-115126-Win and setup any Win version with 32 bit. and you good to go with any coins wallet.

Hit my first stake for 100k ECA. I'm hoping one day we can see move development in this coin and possibly a future. Going to require more work from the dev. I'll keep staking.

No, there is no such happening, what is nobt wallet version you are using/OS?

Dev Team Update — Week of July 24
Hey everyone! I just wanted to give a quick update on what the dev team has been working on. Our team has grown quite a lot over the last week, and people have been ramping up on the existing code base and our proposed architecture. Some of the devs have been on vacation, so we’re hoping to have a “hackathon” this upcoming weekend to really make some headway into a prototype and at least have some basic workflows working.
On Friday, we met and discussed some of the outstanding questions regarding the community, fairness in voting, and the optimal way to launch. We agree that limiting the maximum/minimum payouts initially is a good idea until we reach equilibrium in the float pool. We also had very interesting discussions about how votes should be weighed, how to incentivize people to vote on claims, and minimum votes required to pay out. We are leaning against weighing votes — that could devolve into an oligarchy type situation. Those with the biggest policies, the most reputation, or otherwise the greatest vote weights could be in a position of tremendous power. We want to avoid introducing this unfairness and really let the community evolve organically. We are also leaning towards policyholders paying a small fee in UMC with that paid out to users voting on their claim. This fee will be used to pay people to vote on the claim. We like this idea for two reasons. A) It incentivizes people to vote on claims which have fewer votes — this means they get a bigger piece of the fee than a vote that has many votes. Avoiding a flat payout encourages participation distributed across claims. B) It will discourage people from submitting fraudulent claims — they would have to pay the fee and, if their fraud was discovered, they would lose their policy entirely.
In the same vein of community growth and reaching a consensus, we want the community to have a forum for discussion for each claim. We want theme to share information and allow their expertise in certain areas to show.
We also want to prevent users from submitting duplicate claims, or submitting duplicate evidence across accounts. We’re thinking of having a “similarity score” between two claims based on the parameters submitted when making a claim (amount, area, day of occurrence etc.) and the data they submit (receipt, video, photo) and giving that information to users.
The team is really excited to build this product and get something working and able to be used by the community quickly. We want to surface as much information as possible to let the community reach a consensus in a fair and reasonable manner, and build on this system going forward.