Planetmint inside the wallet

[puria]

convert into zencode

[albertolerda]

The current implementation was just a way to "make some experiments", now the goal is to store transactions on a distributed ledger (planetmint). For this we use the planetmint package inside restroom-mw .
All transfer come from and are sent to a central account (fixed in the keys of a particular instance of zenflows-wallet)
There must be a way to:

• send tokens to an account (if the request has a valid signature)
• remove tokens for an account (aka send to the central account, if the request has a valid signature)
• get the balance of an account at a specific timestamp
• get the list of transaction to e from a specific account (orderd by time), for this it is possible that we need some custom javascript

Those are the feature currently supported by zenflows-wallet

Moreover we must provide

• a docker image to deploy the new wallet
• being able to manage more than one type of token

[matteo-cristino]

I need a small clarification. This is what i have understood in order to implement the first point

1. The front-end sign a request and send it to the wallet (through the proxy);
2. The wallet verifies the request signature contained in the header of the request;
3. The wallet creates a planetmint transaction with a certain amount and then transfer this tx to the receiver;

My question is what keyring is used to sign the planetmint tx? Does the wallet have a keyring?

[albertolerda]

I would say that we use different keyring based on the direction

• zenflows to user, with a keyring stored on zenflows-proxy (instance specific)
• user to zenflows, has to be the frontend that creates the transaction