Quote from: celobr32 on November 05, 2017, 09:45:48 PM

Quote from: hodlor1 on November 05, 2017, 07:58:25 AM

Bitcoin Resilience

Background

In recent months it has become self-evident that bitcoin mining is extremely centralized.
While the greater community shows almost no interest in the 2X fork, the threat of using said
centralized hashrate to disrupt the core chain to the benefit of 2X or BCash for a long period of time remains real.

An ASIC resistant PoW alternative where ASIC miners are not able to slow down progress must be available for the community.
(And Equihash forks with premine and consensus rules changes are clearly not it, sorry)

Cuckoo Cycle

We've picked the most ASIC resistant algorithm we could find:
https://github.com/tromp/cuckoo

Commitment to zero disruption to core chain

We will fork on the same block as 2X does. This serves a double purpose:
1. Services are already suspending activities because of the 2X fork
2. If the core chain is attacked (reorg, wipeout, double spends, ), this is the time to offer the alternative
"Magic bytes" are changed so Resilience nodes will not connect to core nodes

Details

Algorithm: Cuckoo Cycle: 42-cycle with a graph size of 2^30 (2^20 on testnet)
Premine: No.
Added Difficulty retarget: Emergency only
Two-Way Replay Protection: Yes
Intended for GPU mining.

Contribute

This project is done by volunteers, and we need your help!
If you're interested in supporting this project, please join our slack:
Invite Link

Projects and sources

Node: https://github.com/hodlor1/bitcoin/tree/resilience
Pool implementation: https://github.com/hodlor1/ckpool
Miner implementation: https://github.com/hodlor1/sgminer
(Miner is provided as reference implementation as is not fully optimized)

! Status !
Public testnet is available and running, and everything released so far is intended for developers and other possible contributors.
We will release binaries as we get closer to fork time.

How do you mine? algorithm? pool?

Algorithm: Cuckoo Cycle