From: Shane Jonas <jonas.shane@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Add OpenRPC Service Discovery To JSON-RPC Services
Date: Wed, 3 Apr 2019 13:48:24 -0700 [thread overview]
Message-ID: <CA+1vstqKjj5yE=zRRe=ZX+1ynTH2ox8kfLGyBr5HyrzmfnW_mA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Similar to how Bitcion has BIPs to normalize bitcoin wallets, this is a
proposal to normalize the Bitcoin RPC Interface.
Just one example of the problems that arise: If a client doesn't provide
getblock or doesn't work in the same way it will have
unintended consequences .
Having a standard described interfaces lets you generate documentation,
generate RPC clients, test interfaces, across implementations.
Here is the proposal:
https://github.com/bitcoin/bips/pull/776
Here is just an example of what something like that would look like for
Bitcoin:
https://github.com/bitcoin/bips/pull/776#issuecomment-479649785
[-- Attachment #2: Type: text/html, Size: 2248 bytes --]
reply other threads:[~2019-04-03 20:48 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='CA+1vstqKjj5yE=zRRe=ZX+1ynTH2ox8kfLGyBr5HyrzmfnW_mA@mail.gmail.com' \
--to=jonas.shane@gmail$(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