From: rhavar@protonmail.com
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Creating smaller testnet blocks
Date: Sun, 08 Jul 2018 13:30:23 -0400 [thread overview]
Message-ID: <6hUO7HfwD3i4TbS3m1ohDXH7wxywr-7XBnbWJubbctzNm9--tZmLypqf9lWEVEpPiPws81CQHZGQa8ztJ5qyVMZ_59jd9_JlXPPHPw4JPoM=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
More of a shower-thought, but I am currently working on a bitcoin wallet that is designed to handle "free pressure" properly (e.g. CPFP aware, transaction merging, automated progressive fee bumping, etc) and one kind of annoying thing is that there really is no fee market on testnet.
I was thinking it would be cool if tesnet blocks were a bit smaller, so they didn't just mine the entire mempool each block. A full-blown softfork on testnet seems overkill, but just changing the default mining maxBlockWeight to something like 50% of the current mempool weight would help test things and help wallet developers fixing things like "stuck transactions" and what not. (And of course some miners will not use the default, but it's not really a big deal..)
-Ryan
[-- Attachment #2: Type: text/html, Size: 1055 bytes --]
reply other threads:[~2018-07-08 17:30 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='6hUO7HfwD3i4TbS3m1ohDXH7wxywr-7XBnbWJubbctzNm9--tZmLypqf9lWEVEpPiPws81CQHZGQa8ztJ5qyVMZ_59jd9_JlXPPHPw4JPoM=@protonmail.com' \
--to=rhavar@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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