BOUNTY BOUNTY BOUNTY

OI! YOU THERE!!!

No not you, that guy...Yes, YOU!!!

Want some CHAN?

Submit a pull request at https://github.com/chancoin-core/chancoin which fixes one or more unit test - in particular, base_58, bloom, wallet, pow, key and miner unit tests need love. Each test fixed will get you a whopping 100 CHAN! Thats each test, as in each test case within a single unit test file.

If you feel like helping out and need some clarification on what needs doing, please just drop by our discord (link in the OP) and hit me up - I'll respond ASAP

Thanks,
Gossamer

I'm delighted to announce that Chan will be trading on NovaExchange after their reopening under new management. They won't tell me quite when it will happen but I think it will be pretty soon.

Johan and his team have been exceedingly helpful to the project. Its clear to me from our discussions that the team behind Nova is one of the most professional and tech-savvy of the handful we've dealt with in our project. We wish them the best of luck with the reopening

Gossamer

After attempting to remediate with Cryptopia for over a week, we've released a new update:

https://github.com/Chancoin-core/CHANCOIN/releases/tag/v0.15.6.0

This will rewind the chain to before the attack. Cryptopia will end up delisting us, although they haven't given us the specifics of the timeline and any plans for remediating losses due to the double-spend attack - they've been radio silent for a week. I'll try to keep everyone apprised of any updates.

In the meantime, update your clients, and invalidate the block where the attack began by running `./chancoin-cli invalidateblock 56de2e104e949bedd0b9339fb92966b0db1d51a4a723c76c198e36fbac18ee21` in the debug console.

Let me know if you have any questions, or feel free to drop by the discord.

Gossamer

As you may know, immediately after releasing a patch last night to fix a double-spending bug, the chain was attacked and many millions of double-spent coins were generated and used to suck up almost the entire buy-side book on cryptopia. Cryptopia has paused trading and we are working to get a patch out which will invalidate the block where the attacker's nonsense began. Until then, please update your clients to the latest release, available here: https://github.com/Chancoin-core/CHANCOIN/releases/tag/v0.15.4.6

https://github.com/Chancoin-core/CHANCOIN/releases/tag/v0.15.4.6
https://github.com/Chancoin-core/CHANCOIN/releases/tag/v0.15.4.6
https://github.com/Chancoin-core/CHANCOIN/releases/tag/v0.15.4.6

A short and crappy blogpost from moi about the Nightcap (formerly Cloverhash) rollout:

https://chancoin.org/blog/2018/03/07/Nightcap_is_Live.html

GPU mining is GO. Updates to the initial post in this thread are forthcoming.

Cloverhash is Live!

Thanks to the hard work of several community contributors, we have finally got Cloverhash live on mainnet! Block times are now pretty damn fast. Our contributor MangoFusion is working on a GPU implementation, but for now use the instructions in the post above (thank u for posting that, btw) to get started mining, or pop on down to the chancoin discord - linked to in the first post of this thread - for help.

Now that the massive 0.15 update is FINALLY done and rolled out, we will be taking a few days to catch our breath before announcing next steps and priorities, but here's a sneak peak: new website design, updated roadmap, paying down technical debt on our codebase and finally getting down to work on some of the end-user applications we've envisioned for the coin, such as our own crypto-enabled image board.

Thanks for everyone's continued support,
Gossamer

An update regarding the algo switch to Cloverhash -

Thanks to multipools mining Chancoin before the algo switch, the difficulty at midnight UTC on the 14th was above 3k - meaning it'll take a pretty significant amount of CPU power to find the first Cloverhash block. We're working on an sgminer implementation and several devs have come forward and offered to assist - there is currently a 7500 CHAN bounty on a complete GPU miner implementation of Clovehash, open-sourced on our github org. Should multiple people work together to make one (which looks likely) we'll do our best to make sure rewards are distributed equitably among those who contributed - but I can't promise 7.5k CHAN to an unknown number of people :^^^^)

Anyhow, we're currently trying to crack the first block - there may be some issues with the current cpuminer implementation as well - I'll let Name 1856 - who is our head wallet developer - go into details as his time allows.

Meanwhile, please jump onto our official discord (listed in the first post of this thread) if you would like to assist or would like more info.

As always, thanks for all the support of our project as well as your patience. Thanks also for overlooking the brevity of this update. Questions are welcome.

Gossamer

Cross-posting an announcement re: the new algo from our discord:

Okie-dokie - since its getting late here, here's the game plan -
Name and Barry will continue to troubleshoot to see whether a consensus on a cause/fix can be reached - at the latest, tomorrow evening US time (tomorrow morning BarryTime) we will make a decision to either apply a fix to cloverhash OR to do evasive maneuvers and patch in another algorithm
I would estimate about two weeks to get a wallet update out on cryptopia, so that plus development time (which should be relatively short for patching in a known working algo) would be plausible given the parameters of our chain presently.

I will announce further updates here (in announcements) and on bitcointalk as the situation changes
thanks as always for your patience, understanding and help in overcoming technical difficulties :heart:

Thanks,
Gossamer

-=ANNOUNCEMENT=-

So in a few hours (at Midnight on February 14th, UTC) Chancoin will switch to its new PoW algorithm, Cloverhash!

At present we have a cpuminer fork with cloverhash (aka nightcap) implemented available at https://github.com/chancoin-core/cpuminer-multi - branch 'linux'

At present, compiling for windows is left as an exercise to the reader - a windows binary is forthcoming, as is a stratum implementation and a GPU miner. Oh, and a whitepaper.

I know, I know, blah blah blah - the author of the algo, Name - yes his name is Name - is very busy right now and our policy is that our devs well-being comes first, so deal with it.

Anyhow, some instructions for how to solo mine chancoin with cloverhash follow:


How to mine Chancoin with cpuminer

Download cpuminer here: https://github.com/chancoin-core/cpuminer-multi (go to releases for prebuilt binary or build branch 'linux')
Download latest Chancoin wallet here:  https://github.com/chancoin-core/chancoin (again, go to releases)
Create an empty configuration file at ~/.chancoin/chancoin.conf
Edit the configuration file, here’s the template, fill accordingly:

rpcuser=yourusername
rpcpassword=yourpassword
rpcallowip=127.0.0.1
server=1
addnode=fnord
addnode=blah
addnode=whatever
addnode=twinklehouse

Add as many nodes as you can, change user and password, save. See thread for nodes.

From bash, enter "./cpuminer -a cloverhash -o http://127.0.0.1:RPCPORT -O RPCUSER:RPCPASSWORD"

OK - lets see how this goes. If anyone has questions pop them in here or in our _actual_ discord at https://discord.me/chancoin

We'll do our best to address any issues as they arise.

<3 Gossamer & Chancoin Team

  Hrm - well, deleting your blockchain database and re-syncing _might_ solve the issue, but let me bring this to the attention of the wallet devs to make sure I don't put my foot in my mouth here.

Thanks for your patience.

Are you running 0.15.4 ? If so, this issue should be alleviated when a block is found. The issue as I understand it is that since a block hasn't been found recently enough, the client thinks that there are missing headers when in reality the latest block is just 'behind schedule'. If not, upgrade and let us know whether this helps.


Try these:

edgar.chancoin.moe
coinminers.net
chancoin.info
name.chancoin.moe
gossamer.chancoin.moe

Let us know whether any of those work for you!

Cryptopia has completed the 0.15.4 upgrade! Phew! Thats always the most stressful bit for me. I'm following up with Tradesatoshi. Remember, don't use novaexchange, they're closing anyhow so no need to update them, and we warned everyone to get their coins out ages ago.

Now is _definitely_ the time to upgrade to 0.15.4 if you're still running an older version. At block 23500 we should see difficulty adjustment start to function normally...finally.

We've released yet another update!

Chancoin 0.15.4 squishes a small but troublesome bug and moves the difficulty readjustment activation threshold down to block 23,500.

Please upgrade as soon as possible to ensure compatibility when the diff adjustment occurs.

https://github.com/Chancoin-core/CHANCOIN/releases/tag/v0.15.4-knucklebuster

Thanks,
Gossamer

Thanks for keeping things up-to-date here. The only thing I have to add is that macOS build is forthcoming!

Oh, and block 25k only activates the diff readjustment algo (dual KGW) - not cloverhash. Thats still at 30k or Valentine's Day.

Once we get any remaining bugs squashed and ensure that exchanges will be OK with the update, our focus turns to stratum implementation and GPU miners for cloverhash.

Thanks!

I just want to clarify that we're not really re-branding as 'chancoin' since the coin was called 'chancoin' from the beginning - we're just changing the ticker symbol. But thanks Bestof for the update

I'll be posting some more updates here later tonight, US time. In the meantime thanks to everyone for their continued support and enthusiasm.

I found this set of articles fairly helpful when building my first GPU rig. Your mileage may vary:

http://www.cryptobadger.com/build-your-own-ethereum-mining-rig/

These days I find myself mostly playing mobile gacha games like Fire Emblem: Heroes or Love Live...Except on the rare occasions where I can get time away from work AND crypto...

No it is not. We're not trying to capitalize on their brand, unfortunately the project founder chose the symbol '4CHN' -  we're going to work on changing this after 0.15 is out.

Thanks for asking.

It may be slowness with the blockchain -  which is exactly what we hope to alleviate with this release.

A week has passed. I have begun to seriously consider it, as I said I would. And as of today, Name and I are working on fixing the problems with our current build, since we think it will be a bigger win overall for the project. I did not say I would immediately release a magically fixed new client, as you think I said. Thats my stance on this.

Re: "Molly"'s screed:

You (she, he, Molly) did not get banned for posting code or suggesting PoS/PoW. They got banned for shitting up the general channel with nonsense like the very post I'm quoting here.

The roadmap said possible POS before you showed up.  We're probably not doing anything even vaguely POS-y anytime soon. Deal with it.

I've probably been browsing 4Chan since before you were old enough to vote - assuming you're old enough to vote now. I really don't care. Who does care? You. Nobody else.

What 'swap' are you talking about? There was not a swap, unless by swap you mean something other than what the term is commonly used for in crypto. Which wouldn't surprise me since you appeared not to even know what DGW was yesterday.

If you had wanted to contribute to the project you could have (and would have) put in a PR like a normal person. But you didn't. How strange.

I'm sorry that your asshole is so very sore for some strange reason. But there's nothing I can do about that.



In other news, a quick blog post thanking our contributors and community, and saying a little bit about where we're going in the near future -  with an emphasis on trying to make buttblasted babies like the quoted poster understand why they should take a deep breath, consider the possibility that not every open source project is their personal army, and think before they post next time: https://www.chancoin.org/blog/2017/12/25/merry_christmas.html

Merry Christmas! XD