StampChat/stamp

Stamp Proposal: Stamp Handles and Usernames

Opened this issue · 0 comments

Purpose

To provide user's identity and a market place for handles within Stamp and/or Logos

Target audience

Support channels (1-1, 1-n), public communication, searcheable handles & user identities.

How it works

Register a handle

A user can register a handle onto a server (e.g. stampchat.io). To avoid mass-registration, a subscription may apply for handle registration, the user must renew before it is expired so that they can maintain the handle. Alternatively, a minimum deposit may requires to maintain the subscription. This works much like a domain registration. Handles are searchable on the Stampchat client, or can be accessed directly on the Stamp website, such as stampchat.io/nghiacc, or @nghiacc.stampchat.io. Handles are different with usernames - see further below.

Transfer a handle

A user can transfer a handle to another by sending a transaction with a specific message to a new user. The ability to transfer handle from one to another will create a handle market so that it works like domain name. This can only be achieved if the network can validate valid handle (Option 1.2).

Assign a handle

A handle maybe assigned from one user to many others, so that the support team can response to high load support requests. There should be some identity showing the support personnel handling the chat

Renew a subscription

After a period of time, the user must renew the handles in order to use it. Expired handles will be recollected 1 year after expired, and other users can register again.

Usernames

Similar to handles with some differences:

  • Username registration does not requires a subscription - alternatively, a username with a minimum balance can be classified as active
  • Username is not transferrable
  • In chat client, there would be different visual indicators between usernames and handles
  • The username can be accessed on the Stamp website via: stampchat.io/user/nghiacc or @nghiacc.user.stampchat.io