From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Cc: poolowners@list•pfoe.be, sirahlst@gmail•com,
kinlo@triplemining•com, Con Kolivas <kernel@kolivas•org>
Subject: [Bitcoin-development] GBT 2.0 wishlist
Date: Tue, 29 Apr 2014 19:14:59 +0000 [thread overview]
Message-ID: <201404291915.00239.luke@dashjr.org> (raw)
Let's try to get GBT 2.0 off the ground finally.. :)
Here's some wishlist items/ideas:
- Extremely low bandwidth use (binary protocol, with compression support)
- UDP-based transport protocol? (so message order need not be preserved at the
expense of latency)
- Ability to instruct miners to insert (username,hash-of-username,hash-of-
options-array,hash-of-both,etc) in coinbase at a given position (this
enables cheaper proof-of-work auditing of a pool's rewards; it can just
save/publish shares meeting higher targets and anyone can verify the shares
were found by a given username/hash)
- Always encrypted (once by the server), with optional authentication via
CA/namecoin/URI
- Incrementing "precommit id" so miners can precommit to settings without
needing a new/custom coinbase
- Multiple clients should share bandwidth on a LAN (similar to slush's stratum
proxy)
- Convey prevblock as block header so we can follow blockchains securely.
- Fee logic: pools can claim as much coinbase distribution as they require
(with hint from miner); miners are expected to ensure subsidy + transaction
fees tally up to the required total; any fees beyond requires total may be
distributed as the miner wishes. Potentially, pools could allow 50% (or
similar) participation allowing a miner to use multiple pools at the same
time.
Rather than polluting the main development mailing list with what is sure to
have quite a bit of discussion, I have asked kinlo (who hosts the poolowners
mailing list) to provide a dedicated list for this purpose. Interested parties
should please subscribe via http://list.pfoe.be/mailman/listinfo/gbt2 and send
replies to gbt2@list•pfoe.be (once a draft BIP is ready, the main dev mailing
list will be once again CC'd).
Luke
reply other threads:[~2014-04-29 19:15 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=201404291915.00239.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=kernel@kolivas$(echo .)org \
--cc=kinlo@triplemining$(echo .)com \
--cc=poolowners@list$(echo .)pfoe.be \
--cc=sirahlst@gmail$(echo .)com \
/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