Mobile client

[Robert-Steiner]

Not done yet but I can already be reviewed.

What is done:

• Implement the participant state machine
  • The participant state machine keeps the state of the participant
• Implement the client state machine
  • The client state machine keeps the participant state machine, proxy, local/global model and has the logic to perform requests.
• Make the participant configurable
  • The secret key, the certificate and the maskconfig should be configurable.
• Make the client configurable
  • The url should be configurable.
• Implement the mobile client
  • The mobile client contains the client state, the tokio runtime and the local/global model.
• a runnable example

I actually wanted to create a PR for each module Participant, ClientState and MobileClient. However, when I implemented the ClientState struct, I had to change a lot on the participant struct and it got a bit messy. For this reason, I packed everything in one PR. If you want I can also create a new PR for each module.

My suggestion would be that we keep the old client/participant for now and just add the mobile client to the repository and first test if the mobile approach works

[little-dude]

Maybe we could use the EncryptKeyPair for this now.

[janpetschexain]

SigningKeyPair

[Robert-Steiner]

Ah true, I will change it

[Robert-Steiner]

Shall we do the same with

ephm_pk: SumParticipantEphemeralPublicKey,
ephm_sk: SumParticipantEphemeralSecretKey,

in Participant<Sum> and Participant<Sum2> as well?

[janpetschexain]

looks good! i'm happy to help with the ffi parts.

[janpetschexain]

SigningKeyPair

[Robert-Steiner]

@finiteprods @little-dude @janpetschexain
ready for review🙂

changes since the last review

• implemented the function new_secret_key to make it easier for a user to generate a new secret key
• implemented the FFI (currently, it is living in a separate repository)
• made the rustls feature of reqwest configurable on the xaynet crate (we had issues compiling reqwest on android due to openssl therefore we switched to rustls)
• moved the mobile client example into the example folder

Note:
The new participant/client struct and the new mobile client are still in an early stage. For that reason, the documentation of the mobile client is hidden. However, the new participant/client struct is a starting point for a unified client state machine that works on desktop, web(wasm) and mobile.

[little-dude]

This is great 👍. We should clean the commit history up before merging. I don't know if you prefer to address https://github.com/xaynetwork/xaynet/pull/471/files#r462925062 now or later in a follow-up PR. I'm fine with both.

[Robert-Steiner]

I removed the Option, implemented impl Into<Participant<Sum2>> for Participant<Sum> and renamed the method next of the mobile client to perform_task

@little-dude
I agree, it's okay if I spuash the PR?

[little-dude]

Nice, I think this is an improvement 👍

@little-dude I agree, it's okay if I squash the PR?

Sure or just splitting it in a bunch of self-contained commits works as well 👍