The situation is rather weird. Is it not community-driven? Further there is no formal announcement about kai.

Yescrypt family:

R8: Bitzeny
R16: Yenten
R32: Wavi (but it is too new)

I have a proposal of a lock period of 15 days after mining. In the past, it was abysmal to set a hard lock of a year, but 7 - 15 days is rather optimal to keep the price stable and worthwhile.

In general, I know that it is to make users hold this coin for a long enough time. Do anyone agree?

What are the differences between this and HODLcoin? Any specialties or interesting points?

I just fpimd this coin and it is really good that it utilises a new algo yescryptR32.

I hope that it may succeed.

As Bitcoin is a member of the family of Cryptonight, it is also seriously affected by the latest ASIC machines. For details, all can check the following link:

http://cryptomining-blog.com/9538-baikal-giant-n-the-first-cryptonight-asic-miner/
http://cryptomining-blog.com/9546-cryptonight-asic-miner-from-bitmain-as-well-the-antminer-x3/
http://cryptomining-blog.com/9552-pinidea-rr-200-cryptonight-asic-miner-coming-next/

However, for the general practice, we have to choose either following the practice of other members like Monero to create a hard fork to switch a little bit or allowing the ASIC to decimate all our miners at all.

Do we have a consensus now?

I am partially new in this coin community. Would this coin connect the reward to the real coal price and change every day?

Like https://tradingeconomics.com/commodity/coal, the price now is around 99.4 and if the mining reward is 1/10, ie 9.94 COAL, then there is much a brighter future as it is O2O.

It is my two penny to increase the usefulness of this coin.

Can you explain more about what UTXO is and how it works.

yes, around 13.00 BBP .....

I clearly did not encrypt at all and it is clearly unlocked.

I have a problem in association my Rosetta@Home CPID with biblepay. Please help me!!!!

"Results": "Unable to sign CPID 22837abf367a5e .......... "

How to solve it? I have already joined Biblepay team as well.....

I would like to know my wallet pending balance in your pool.

9EjqJupi4u5NCXN8o6u6oXGARW9vGTGJfiQekQ4LPPZCBpr6Eio9vCfg1eYhw34rZDEfHVUVmSC6SUb TWYbZGWTDAJHjjdt

Hopefully it's not late.

My XMR address:
43ArPosSaXF1AiqBazgGf7bwBST57CieeADUrWWzqFFf7YV9bNjmpaH4HsBaxBwgv9XDdmnvt4JePTm rqoXEe91KCB6cb8C

Now all the pools are as follows:

http://tychecash.labbinarymining.com/ is still on the wrong chain and they are mining the block 8132.
http://tyc.revientaicos.com/ is still showing the network as the Blockchain Height: 5952
https://tyc.cryptomineros.com/ still stops at all and only a message "We are stopping this pool while waiting for a fix for the synchronization issue." is displayed.
https://tyc.dreampool.info/ probably closes in future and even actively rejects any connections.
Unfortunately, Blockchain would not be synced. we have lost some blocks.
" We are very sorry. Pool was temporarily closed and some other pools have the same problem.
we will try to find your coin mined.

Tychecoin from bitcointalk.org said "Reset your pools". so we will try with the new wallet.
But we can't promise to keep your coin mined.

Blockchain was back to before the accident. It seems all your unpaid coins are disappeared.
Pool will be closed soon. That's a sad news. I'm very depressed about it and very sorry "

Then is the coin fit for pool-mining?

It is very confusing as I have spent all my machine computation on your coin and it does not show in my wallet. Further, as I have mined through the pool and hope that the chain is not orphaned, I do not want to make all my valuable computation power wasted for nothing.

Add nodes.....

If possible, please send me some.... As I always have to travel to China or even those worst Asian countries like Bahrain, North Korea, the internet censorship is very severe and VPN is a must to have a freedom of surfing the Internet. If you really wanna give up, please pm me and send me some ITNS.

Is it really a dead project?

Does this work? It always leads to Error 404.......