Migrate from BMA to GVA

New client API implementation GVA with GraphQL:

• RFC
• Forum post
• Forum post about Duniter module
• DuniterPy ticket

Plan

• Update to DuniterPy 0.61 which implements GraphQL
• duniterpy.api.Client is used for BMA and GVA. When closing one, it closes the other one. We shouldn't keep both in parallel for now. May be something to search within the singleton to have two separated clients instances.
• Keep in parallel BMA/GVA? Probably not.

Network layer

• Use DuniterPy’s GVAEndpoint
• Endpoint definition:
  • Use port regex from DuniterPy (redefine it in DuniterPy)
  • Add ability to pass and endpoint
  • #223 (closed), #354: Make optional to have a click context
  • Handle Gtest
  • Use ipaddress to separated host from ipv4 which seems not separable from regex matching
  • Rename -p/--peer option to -e/--endpoint?

Commands

Simple

Replace BMA by GVA in simple commands regarding network requests:

• balance
  • #209: One query for multiple balances
  • currency string not found in params nor blocks (CurrencySymbol())
  • Merge tables into one table
    • Separation (Textable fonctionnality) between "tables" to improve readability?
  • One query for multiple identities: identities query
  • handle pending tx?
  • balance difference between CS/Silkaj calculation <−> GVA?
  • New ticket: display balance of UDs and UTXO from tx (SIG, LOCKED)
• argos
• info
• blocks

Complex

Replace BMA by GVA in complex commands with websocket (subscription) and document emission:

• diffi
• history
• tx
• id
• wot
• cert
• membership