-
Notifications
You must be signed in to change notification settings - Fork 15
Features
To exchange transactions, it is only necessary to have a pseudo, an email and a pass phrase in order to create pairs of public and private keys.
To receive the monthly Universal Dividend, it is necessary to be uniquely identified and recognised by the community. The keys require the full name, date and place of birth, and at least three other members to confirm them.
For this confirmation, they should physically look up a corresponding official piece of identification, and check that the listed full name and date and place of birth do correspond exactly to the one filled.
By default, the last selected member should be selected again.
If the server is not a bank, it should be easy to select a member which private key is locally present.
A list of previously selected members should be easily accessible.
Once a member is selected, the owned amount of money should be displayed.
It should be possible to view the individual coins, sorted by their value.
Very easily, it should be possible to list this member's incoming and outgoing transactions.
It will include authors and recipients, amount of money and date of value.
There should be 2 ways to create a transaction:
- first search for another member, then select an amount of money
- first select an amount, then search for another member
Member search can be presented as a list of members according to:
- amount of money exchanged
- number of transactions exchanged
- GPG key certification
- name, email, date or place of birth, PGP id or UDID
Money selection can be done in 2 ways:
- enter an amount and let the system select coins to approach this value
- select individual coins
Finally, sign the transaction with the pass phrase associated to your key.
This is the easiest mechanism. The transaction
Depending on the mechanism used to send the transaction, verification could be partially done already. If the emitter sent it using publication servers, then you should just check that it was accepted by some servers you consider important and reliable enough.
The only risk is that the transaction author sent to you coins he does not own. This might be coins that:
- do not exist at all
- were never his at any point
- he gave to someone else already
In all cases, due to the way a transaction is signed using a private key the author should keep secure, any transaction containing invalid coins is his responsibility and can be refused rather easily by publication servers. If the author does send an invalid transaction, the recipient should refuse it upon verification, and ask for another valid one.
A list of all members, with their email, pseudo, key id and their period of validity.