Migrate to DuniterPy usage

DuniterPy

Transition plan

• Set Python 3.5 as requirements as DuniterPy 0.52 requires Python 3.5 (DuniterPy 0.60 will requires Python 3.6)
• Keep same behaviours for the commands and the authentication

Endpoint/GET

• replace GET methods
• Make the code asynchronous
• replace peer document endpoint management

Commands

• cert:
  • replace document generation
  • replace sign and post method
• keep amount behaviour with authentication
• tx:
  • replace document generation
  • replace sign and post method
  • multi-output
  • #178 (closed): intermediaries transactions: infinite loop because of already proceed tx for intermediaries tx.
• generate_auth_file

Authentication

• scrypt
• duniterpy#71 (closed): add seedhex authentication in DuniterPy: seed in an hexadecimal base with str type
• Ğannonce format (PubSec)
• (E)WIF (format compatible with Silkaj 0.6)
• #173 (closed): Following ticket to implement other methods

Cleaning

• get rid of no longer needed functions
• auth.py: cleaning done. Improvements possible, but later with #77 (closed), and #173 (closed)
• #177 (closed): network_tools.py: remove check_port(), refactor best_node(), parse_endpoint(s)()
• #176 (closed): crypto_tools.py

---

Code to move to/to implement in DuniterPy

• Authentication methods:
  • duniterpy#51 (closed), duniterpy#52 (closed): WIF/EWIF
  • gannonce format: PubSec: duniterpy#51 (closed)
• #176 (closed): pubkey checksum

I think this is really important to go on duniterpy asap, probably even before 0.4.0. Silkaj is gaining a lot of new features and the more you wait, the less chance there is that you use duniterpy one day.

And currently @Tortue95 and @jytou are adding a lot of interesting features in Silkaj which would be useful in duniterpy, because then sakia could benefits from it ! Currently, everything you are doing will have to be done twice (WIF, etc...) :(

If needed, I could give you some help.

Created by: jytou

So should we just move pure API stuff to the duniterpy project and have a dependency on the project, and keep everything that is command line here? Or move everything there altogether? I didn't have a look at the duniterpy project yet.

Duniterpy is only about API stuff. BMA requesting, multiple wallet format handling... All command line stuff should remain on silkaj !

Let's see how Duniter client API evolve.

changed milestone to %0.6.0

changed the description

changed milestone to %0.8.0

mentioned in issue #93 (closed)

changed title from Use Duniter-python-api to Use DuniterPy

changed the description

changed milestone to %0.7.0

assigned to @moul

changed the description

marked the checklist item Set Python 3.5 as requirements as DuniterPy 0.50 requires Python 3.5 (DuniterPy 0.60 will requires Python 3.6) as completed

marked the checklist item replace get methods as completed

changed the description

changed the description

changed the description

changed the description

changed the description

changed the description

changed the description

changed the description

changed the description

changed the description

changed the description

marked the checklist item tx: as completed

marked the checklist item replace document generation as completed

changed the description

changed title from Use DuniterPy to Migrate to DuniterPy usage

changed the description

changed the description

changed the description

changed the description

changed the description