Wine-backed Cryptoassets
- Mike Tango Bravo
The section describes the creation of the wine-backed cryptoassets.
Why are we doing this?
We want to use the market to decide the price of our wine, and by doing so, open a debate about the value of wine.
We want to create an easy metaphor for the understanding of cryptoassets.
To accomplish these two primary objectives, we need:
A platform to enable people to buy, sell, and redeem our cryptoassets.
A very simple and elegant explanation of the process.
What is cryptocurrency or cryptoasset?
How does the token lifecycle work?
How do I get a vintage token? (MTB18)
Who buys vintage tokens?
People interested in immediate wine delivery:
Importers
Distributors
Drinkers
Deferred wine delivery:
Cryptocurrency traders
Future speculation on an increased price.
Novelty buyers.
People or companies gifting wine to others (friends, customers, loyalty programs, etc.).
Current cryptocurrency users who are looking for a more stable parking space for their assets.
Exisisting wine supply-chain
How does it work?
Someone interested in acquiring an MTB18 token connects to the VCO (Vintage Coin Offering) landing page. This page describes the project and the process.
The page instructs the user on how to install the google/firefox metamask plugin and create/import a wallet.
We ask the user, "Do you already own ETH?" If the answer is YES, we give them instructions for sending ether against the VCO smart contract.
If the answer is NO (the user does not currently own ETH), we give them the option of buying ETH.
The Vintage Coin Offering (VCO)
The first VCO took place on the 6th of May, 2018. This date is important because it is at the beginning of May, when the 2018 wine making campaign finished, i.e. the wine fermentation has mostly finished, and we have a clear idea about how the vintage will look and how much wine there is. In other words, by early May, we have the wine in the tanks, though they still need time to evolve. And, not coincidentally, it is Mica Vera's birthday.
Functional requirements for the Landing Page
Req | P | Definition | Owner | Notes |
|---|---|---|---|---|
4.1.1 |
| Domain vco.costaflores.com |
|
|
4.1.2 |
| Open-Source app link to github |
|
|
4.1.3 |
| Explanation for MTBxx token |
|
|
4.1.4 |
| Countdown ticker to moment of sale is open |
|
|
4.1.5 |
| Photo and description of team members |
|
|
4.1.6 |
| Link to openvino wiki |
|
|
4.1.7 |
| Link to Social networks (twitter, medium, telegram) |
|
|
4.1.8 |
| Connection to the smart contract to show amount available for purchase, amount sold |
|
|
4.1.9 |
| Link to video tutorial on how to use 3rd party systems to buy and manage token. |
|
|
Functional Requirements for Token creation contract
Req | P | Definition | Owner | Notes |
|---|---|---|---|---|
4.2.1 |
| ERC20 Token on the Ethereum platform |
|
|
4.2.2 |
| Ticker Name: MIKETANGOBRAVO18 |
|
|
4.2.3 |
| Ticker Symbol: MTB18 |
|
|
4.2.4 |
| Decimals of precision: 18 |
|
|
4.2.5 |
| Total Supply: to be defined once harvest is finished. |
|
|
Functional requirements for crowdsale contract
Req | P | Definition | Owner | Notes |
|---|---|---|---|---|
4.3.1 |
| Token crowdsale contract: Capped, Finalizable and Pausable |
|
|
4.3.2 |
| Total cap in ether to raise: to be defined once harvest is finished. |
|
|
4.3.3 |
| Total token cap to create: to be defined once harvest is finished. |
|
|
4.3.4 |
| Initial token fund balance: to be defined once harvest is finished. |
|
|
Functional requirements for the shopping cart (obsolete)
Req | P | Definition | Owner | Notes |
|---|---|---|---|---|
4.4.1 | 1 | Sell physical products (boxes of 6 bottles of wine), and virtual products (wine tokens). We |
|
|
4.4.2 | 1 | Capture the following data from customers: Name, Address, e-mail, Fiscal ID, Wallet ID, Language, purchases. |
|
|
4.4.3 | 1 | Present specific production description fields: Text about the wine, weight, packaging information. |
|
|
4.4.4 | 1 | The shop should be localized for Argentina, to cover Argentina taxes, etc. Tienda localizada en Argentina, con sus impuestos, su idioma y su moneda, pero con varios idiomas disponibles como inglés, portugués, francés. |
|
|
4.4.5 | 1 | The customer should be able to select the languages: English, Spanish, Portuguese, and French. Poder mostrar precios con 2 decimales (por ejemplo para ARS, EUR, USD, etc) o 6 o más decimales (por ejemplo el BTC, etc) |
|
|
4.4.6 | 1 | The customer should be able to select the reference currencies ARS, EUR, USD, to see the approximate equivalent price for the products, although the price for products is defined in ARS. |
|
|
4.4.7 | 1 | Payment can be made in BTC and ETH, deposited into HD wallets. |
|
|
4.4.8 | 1 | Payment for wine vintages =>2018 will be only in MTB* tokens. |
|
|
4.4.9 | 1 | Payment for tokens and current vintages using credit cards with Mercadopago |
|
|
4.4.10 | 2 | Payment for tokens and current vintages using Argentine paypal linked to Organic Costaflores S.A. |
|
|
4.4.11 | 1 | Wine tokens should be for sale to any country in the world. |
|
|
4.4.12 | 1 | Wine bottles (boxes of 6) should be restricted to countries where the wine is available (Argentina, India, Brasil, EU) |
|
|
4.4.13 | 1 | The checkout process should be as simple as possible (few number of clicks). |
|
|
4.4.14 | 1 | shop.costaflores.com should comply with the GDPR rules. |
|
|
4.4.15 | 1 | shop.costaflores.com must require that customers have asserted they are legal to buy wine in their country. |
|
|
4.4.16 | 1 | shop.costaflores.com should follow the Costaflores look and feel. |
|
|
4.4.17 | 1 | Data collected in 4.4.2, including data related to the purchase transaction (time, date, etc.) must be synchronized with Openbravo. |
|
|
4.4.18 | 1 | The site should work properly, both on web and smartphones. |
|
|
4.4.19 | 1 | Data collected (Name, email, language) should integrate with constant contact for the newsletter. |
|
|