From: Pieter Wuille <pieter.wuille@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Deprecating Bitcoin Core's regtest-specific `setgenerate` behaviour
Date: Sun, 12 Apr 2015 07:26:12 -0700 [thread overview]
Message-ID: <CAPg+sBjNkzqTUupx5QYZ_uzMwAdY4qRc+PGR5R9qCKUxxcHx7g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
Hello everyone,
Bitcoin Core's `setgenerate` RPC call has had a special meaning for
-regtest (namely instantaneously mining a number of blocks, instead of
starting a background CPU miner).
We're planning to deprecate that overloaded behaviour, and replace it with
a separate RPC call `generate`. Is there any software or user who would
need compatibility with the old behaviour? We're generally very
conservative in changing RPC behaviour, but as this is not related to any
production functionality, we may as well just switch it.
Note that the bitcoin.org developer documentation will need to be updated.
--
Pieter
[-- Attachment #2: Type: text/html, Size: 756 bytes --]
next reply other threads:[~2015-04-12 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 14:26 Pieter Wuille [this message]
2015-04-12 22:36 ` Sean Gilligan
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=CAPg+sBjNkzqTUupx5QYZ_uzMwAdY4qRc+PGR5R9qCKUxxcHx7g@mail.gmail.com \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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