Token authentication complete
This article is an addition to previous one and this is a redesign of token authentication based on proof-of-pay concept. The principle is simple, You are registered if you have payed min sum of the token.
Benefits
- Anonimity.
You can’t track payment history of NVS record.
The user can change it’s public key every time.
There is no user data, only token id. - Easier client application.
Client does not need blockchain.
Terms
Token.id — Token.time-Token.sig-Token.address.
Token.time — Unixtime token creation time.
Token.sig — Signature(Node.pub , time + address + Node.nonce)
Token.address — Payment address.
Token.burn — After this time (seconds) token will burn.
Burned token — Token is burned after BURN TIME period.
Legal Token — Token, payed at least one time and with balance >= TOKEN_MIN_SUM. Can not be burned.
Registered token — The token is placed in a free users slot and directory and other stuff is created, user is joined (registered) to node.
Joined User — The user which has registered token.
Workflow
- Service Node issues every second new token with Token.id
- User sees token, remembers Token.id and Token.address as a part of Token.id
- User makes payment to Token.address in TIME < Token.burn or else token gets burned.
- After payment is made the token becomes LEGAL TOKEN.
- After user checks LEGAL TOKEN the token automatically becomes REGISTERED TOKEN. The user becomes joined (registered) user and all needed infrastructure for user is created.
