public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Stikkan83 <stikkan83@protonmail•com>
To: "bitcoin-dev@lists•linuxfoundation.org"
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] POW - Miner's choice?
Date: Wed, 15 Nov 2017 14:59:45 -0500	[thread overview]
Message-ID: <9F5Nn3Qq7o0CLHPD22ictAEX5uwWGpk8uZhdwfP0BaTCKULM5jYOSL_tLU7JVIF1nax0CMpi1UGerVH50Cjf-_A-4n8rz6GoZlGsyc__lyg=@protonmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

hello list,

would it be possible to have two available POW mining algorithms (like
for example "Double-SHA256" and "Cuckoo Cycle"), and let the miner
choose which one to use for POW?

the two algorithms would have independent difficulties, and after each
difficulty period, the difficulty would be adjusted to aim for 50/50
distribution of the two algorithms (in addition to aim for 10 minutes
block time).

this could be done by only adjusting up difficulty for the algorithm
used in most blocks last period, or only adjusting down difficulty for
the algorithm with the least number of blocks last period (depending
on whether the combined difficulty was to be adjusted up or down).  or
maybe a more sophisticated variant, where both difficulties are
adjusted, based on the relative difference of the number of blocks
where they are used.

the main motivation for this would be:

- increase mining distribution
- continue mining even when one type of miners suddenly jump to mine a
  more profitable altcoin.

not sure if this has been proposed (and rejected) before, but I can't
remember seeing it discussed.

would probably require a hard fork.

SA

[-- Attachment #2: Type: text/html, Size: 1612 bytes --]

                 reply	other threads:[~2017-11-15 20:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='9F5Nn3Qq7o0CLHPD22ictAEX5uwWGpk8uZhdwfP0BaTCKULM5jYOSL_tLU7JVIF1nax0CMpi1UGerVH50Cjf-_A-4n8rz6GoZlGsyc__lyg=@protonmail.com' \
    --to=stikkan83@protonmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox