...
How does it work for a first time drinker:
The drinker buys a bottle of wine. This can be through the traditional channel (purchased at a restaurant in fiat, for example), or by exchanging winecoins for bottles that are shipped to the drinker's home.
The drinker reads a "click-bait" phrase on the back label, such as: "if you drink this bottle, you own it, see the QR code or URL for details."
The drinker is directed to the OpenVino site, which explains the program.
The drinker needs to input personal information to register with
First and Last (names)
email address
Legal address
Birthdate
ID number (DNI, passport number, etc.)
username
password
location (ask to capture location)
profile picture or avatar
The site directs the drinker to read the
unique identifier from the bottle.
The site then directs the drinker to take a selfie, and answer 5 multiple choice questions.
Finally, the site shows the drinker a confirmation that they are now shareholders in the company.
Drinkers receive a welcome email explaining more details about the company, the program, etc. - providing further instructions to provide a token wallet address.
The actual transfer of OpenVino tokens is performed manually, by the OpenVino team, once the drinker registration data is validated.
For recurring drinkers, the process is similar, but the drinker is already registered and doesn't need to repeat the registration process.
This initially is done with a responsive site, but all functions should eventually be folded into an independent app with a built-in wallet.
OpenVino WebApp
The YDIYOI OpenVino WebApp allows us to do the following OpenVino operations:
Scan the QR code on the bottle
Take a selfie.
Answer questions or star ratings.
Provide personal information for user registration
Capture location.
Input the unique codes from the bottle.
Create a username, password, and avatar image (this is data shared with the winery)
OpenVino App - management backend
The data collected in the OpenVino WebApp should be stored in a database maintained on an OpenVino server. A user interface for this database should allow an authenticated and authorized OpenVino admin user to:
...
The OpenVino admin should have the capacity to change any of the drinker information and status fields, as well as delete drinker profiles or create new ones manually.
Functional requirements for the OpenVino YDIYOI site:
Req | P | Definition | Owner | Notes |
5.1.1 | 1 | Scan QR code on bottle. The QR code should take the reader to the WebApp site, and begin the registration process with the bottle serial number. If the user has already registered, the option to login should be provided. A "keep me logged in" option should be available. | ||
5.1.2 | 2 | Input a specific numerical identifier that is hidden in the bottle | ||
5.1.3 | 1 | Register the user information in an OpenVino database for OpenVino token issuance.
| ||
5.1.4 | 1 | Take a photo, and ask 5 questions about the drinking experience. | ||
5.1.5 | 3 | Send OpenVino tokens to a wallet address. (this will be done manually initially) | ||
5.1.6 | 1 | Ask for permission to use location services. | ||
5.1.7 | 1 | Create user credentials, password reset, username (to be shared with the winery), avatar image. | ||
5.1.8 | 1 | Allow users to update their information. If information is updated, a manual check needs to be performed by the backoffice to insure that legal requirements are still met for the shares. | ||
5.1.9 | 1 | The user should be able to add/modify the address of an ERC20 compatible wallet for receiving the OpenVino tokens. |