|
A double pow is pretty original. The first of many, probably. Opens up double pow with the whole spectrum of algos out there, then triple pow no doubt. Then double or triple with shielded addresses, then a double pow dag. Ah shitcoins. The gift that keeps on giving.
|
|
|
|
ChessCoins will be transferred to the BSC via this exchange.
This is additional, I take it, POS mainchain will keep existing, no? |
|
|
|
A switch from Blake2b to Blake 3 demonstrates a performance boost through its speed and efficiency and prevents ASIC miners from dominating
Blake3 is literally asics, just a different coin. Also, this thing has to be gpu insider mined, no way this has Ghashes on cpu only, with a Ryzen coughing up only 50Kh. |
|
|
|
Having studied the features of Karlsen (KLS), I believe that this coin does not have a serious future. Even if KLS is listed on some exchanges, it’s unlikely that this coin will take off. There is a lot of competition in the cryptocurrency market, promotion requires a lot of money, which the developers do not have, judging by their website and information about the project available on the Internet.
Idk man, pools are picking it up, hashrate is making a killing, first kaspa clone steering away from asics. Sure, speculative at this point, but even kaspa isn't user/time tried and tested like BTC. It definitely fills a niche. Going to be fun to see a first listing. |
|
|
|
|
What is everyone expecting of a new shitcoin; a high capital glossy enterprise? It's copy paste space, kas didn't start out 'amazing' either, neither did all other caught on coins. Just have fun mining.
|
|
|
|
|
Nicely done. Chain sync is a disaster, though.
|
|
|
|
|
If anyone wants to sync this coin, which is a total disaster with either no conf file or regular conf settings, getpeerinfo, copy 1 peer ip/port, put in your conf file connect=ip:port and listen=0.
When synced up to tip, revert to normal settings (listen=1, server=1, daemon=1).
|
|
|
|
|
Oldie but goodie, still have a working wallet/chain. POW diff, however, is a potential problem for double spends (not that anyone cares, given the price). Perhaps fork to auxpow.
|
|
|
|
10 years huh
Network could use more nodes. files.hobomap.info has the chain for download. If on Ubuntu, best use wine to run the .exe. btcpop.co still works too. If xeggex is crazy enough to add the coin, you definitely will want some. |
|
|
|
|
Haha, nice. Too bad, had a nice vibe to it. Pool still works, network is up. Who cares if the copy paster rugpulled. Not sure if there was a hidden premine though.
|
|
|
|
looks like it's over
no more buy orders
Not over until the fat blockchain lady sings. |
|
|
|
We want to list your token on our CoinCasso Exchange 🤖
Could I get a contact of the listing specialist? 🔎
you can message me here Don't tell them it's open source and anyone can list it...  Have a well final month of 2022 all. |
|
|
|
|
DM'ed windows version 1.4.2.1 staking in sync with other versions/explorer now.
|
|
|
|
|
Thanks for the effort. v1.4 running fine as usual.
|
|
|
|
|
Perhaps it's something simple, such as version number, that makes client clusters compete over the longest chain. The explorer is probably running v1.4. Not a stake wallet expert though.
Edit, I ran my wallet with -rescan and now stake in sync with the explorer on v1.4
No need to download the chain again.
|
|
|
|
The latest github win release, v1.5.1 I started running 2 days ago was staking smaller than usual amounts and when syncing the previous release showed these as invalid, so it was staking on either its own fork or a bunch of new clients. Now running v1.4 with 11 connections and normal stake amounts.
Sorry... we haven't changed anything in the coin rewards code... the blockchain has no bugs and there are no forks either... you can't create new blocks since version 1.4.1 before you have the blockchain is fully synchronized... No problem. Pretty sure the chain was synced, that's why I'm posting here. Had it running in between 24-36 hours, rewards like 0.004 each (usually 0.1'ish). Anyway, thought I'd mention it. |
|
|
|
|
The latest github win release, v1.5.1 I started running 2 days ago was staking smaller than usual amounts and when syncing the previous release showed these as invalid, so it was staking on either its own fork or a bunch of new clients. Now running v1.4 with 11 connections and normal stake amounts.
|
|
|
|
|
Show Posts
