From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Cc: Inaba <admin@eclipsemc•com>, kinlo@triplemining•com
Subject: [Bitcoin-development] Please review: getmemorypool (BIP 22) revision
Date: Fri, 11 May 2012 15:33:53 +0000 [thread overview]
Message-ID: <201205111533.55960.luke@dashjr.org> (raw)
I have finally got around to revising the BIP 22 draft, and would appreciate
further review: https://en.bitcoin.it/wiki/BIP_0022
I believe this revision addresses Geir's last email in March, as well as some
practical problems some pools recently came across.
To summarize the changes from the last revision in March:
- The submitblock(<data>, <params>) method is renamed to getmemorypool
- Requesting a job now uses getmemorypool(<params>) to provide client
capabilities and other information to the server
- Longpolls use a parameter in the getmemorypool request, not necessarily a
separate URI
- The client can inform the server of its own size and sigop requirements in
advance
- The client can request detailed transaction data from the server, necessary
to sanely manipulate the transactions included in the final block without
discarding fees or making the block invalid due to not having enough
- With both client and server support, blocks can be proposed before wasting
time mining them, to ensure they are otherwise valid
- Servers can be arranged into single logical services, with failover and load
balancing (similar to the getwork X-Host-List and X-Switch-To extensions).
You can see the full diff here:
https://en.bitcoin.it/w/?title=BIP_0022&action=historysubmit&diff=26408&oldid=25544
Luke
reply other threads:[~2012-05-11 15:34 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=201205111533.55960.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=admin@eclipsemc$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=kinlo@triplemining$(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