From: "Stéphane Traumat" <stephane.traumat@gmail•com>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP171 - Specs, Mock server, template project and client librairies
Date: Tue, 21 Aug 2018 23:12:47 +0200 [thread overview]
Message-ID: <CAApT8LRcC4iApEWX4QLQRFUqXPokC4e68GD48KtjxcyPXgfPcQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
Hello,
I worked on the BIP 171
<https://github.com/bitcoin/bips/blob/master/bip-0171.mediawiki> and I
created Cerise <http://www.cerise.tech/> (github
<https://github.com/straumat/cerise>) that provides the following artifacts
:
- BIP-0171 specifications <http://www.cerise.tech/#specifications>.
- A mocked BIP-0171 compliant server available online
<http://api.cerise.tech/swagger-ui.html> you can use to understand the
API and make calls.
- A mocked BIP-0171 compliant server as a Java application
<https://github.com/straumat/cerise-server-mock/> you can use to develop
your client application.
- A mocked BIP-0171 compliant server as a Docker image
<https://hub.docker.com/r/straumat/cerise-server-mock/> you can use to
develop your client application.
- A BIP-0171 library <https://github.com/straumat/cerise/> to transform
your application in a BIP-0171 server.
- A server template project
<https://github.com/straumat/cerise-server-template> to quickly write
your implementation and automatically produce your BIP-0171 server.
- A collection of client libraries <http://www.cerise.tech/#clients> to
call any BIP-0171 compliant server with your favorite language.
I made some proposal of evolutions here :
https://github.com/bitcoin/bips/wiki/Comments:BIP-0171
I hope it helps and if you have any suggestion on how I could help more,
let me know.
--
*Stéphane Traumat*
https://about.me/straumat
[-- Attachment #2: Type: text/html, Size: 3593 bytes --]
reply other threads:[~2018-08-21 21:13 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=CAApT8LRcC4iApEWX4QLQRFUqXPokC4e68GD48KtjxcyPXgfPcQ@mail.gmail.com \
--to=stephane.traumat@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