public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Stéphane Traumat" <stephane.traumat@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BIP171 - Mocked implementation, generated specs, live API and 16 clients libs
Date: Wed, 1 Aug 2018 10:08:55 +0200	[thread overview]
Message-ID: <CAApT8LTr1Qq4cDpRJdk25t6gGLgEg47_VgGj=xPUBNTsj4ufNw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]

I just released CERISE (website <http://www.cerise.tech/> & github
<https://github.com/straumat/cerise>) a project with the following
artifacts :

   -

   A mocked server implementation to start developing clients :
   https://github.com/straumat/cerise.
   -

   A live & documented API to understand and directly calls the methods :
   http://api.cerise.tech/docs.
   -

   Specifications of the four methods : Enumerating supported currency-pair
   tokens
   <http://www.cerise.tech/specifications/0.3-SNAPSHOT/supportedCurrencyPairTokensAPI.html>
   , Currency-pair information
   <http://www.cerise.tech/specifications/0.3-SNAPSHOT/currencyPairInformationAPI.html>
   , Current exchange rate
   <http://www.cerise.tech/specifications/0.3-SNAPSHOT/currentExchangeRateAPI.html>
    & Historical exchange rates
   <http://www.cerise.tech/specifications/0.3-SNAPSHOT/historicalExchangeRatesAPI.html>
   .
   -

   16 client librairies for various langages (Java, PHP, c++, Rusty,
   Ruby….) : http://www.cerise.tech/#clients.
   -

   and i’m working on a template project to allow developers to quickly
   build a BIP171 compliant server without having to worrying about parameters
   validation, security, rest mechanics… will be done in september.

-- 
*Stéphane Traumat*
https://about.me/straumat

[-- Attachment #2: Type: text/html, Size: 5404 bytes --]

                 reply	other threads:[~2018-08-01  8:09 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='CAApT8LTr1Qq4cDpRJdk25t6gGLgEg47_VgGj=xPUBNTsj4ufNw@mail.gmail.com' \
    --to=stephane.traumat@gmail.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