BOMESP exchange in Brasil

We are now listed with MTB18, MTB19, and MTB20 on the exchange! Soon we will do some promotion campaigns in Brazil.

25 BRL for our first sale:

For a long time, I didn't know how to store our MTB18, MTB19, MTB20 tokens a hardware wallet.

If you are not familiar with the Ledger hardware wallet, this is a great device that provides an additional layer of protection for your cryptoassets. If you want to access your wallet, you essentially need to connect a hardware device to the USB port on your computer and introduce a PIN number. The ethereum wallet (or Bitcoin, or others) private keys are stored on the hardware device. This is good because if your computer were somehow hacked, the intruder would not be able to access your wallet private key unless you connect and unlock the physical device with a PIN code.

There are several hardware wallets on the market, but the Ledger wallets are the coolest. Actually, the coolest wallet is one that was gifted to you at EthVC this year in Paris. Thanks Ambre!

The Ledger wallet includes a software wallet manager called "Ledger Live". This software supports all different kinds of wallets on different blockchains, and includes a long list of ERC20 tokens. Unfortunately, it does not include our MTB* tokens, and I don't know how, or if support for our tokens could be added. But you can import a wallet into Metamask, and add the custom tokens manually. You don't get to see our lovely token icons, but otherwise the functionality is the same.

In a nutshell, all you have to do is select "Connect Hardware Wallet" from the Metamask main menu, connect the wallet un unlock the Ethereum app on the device, and select the wallet you want to control from Metamask.

The first time I tried to do this, I was unable to send tokens outside of the wallet. This is because you need to enable "contract data" support from the settings menu of the ethereum app on the ledger wallet. Also you should be up-to-date on the ledger firmware and ethereum app.

Here is a good article that describes in detail the process.


Vinduino check

I realized today that the moisture sensors on the Cabernet Sauvignon vinduino are incorrectly cabled (?!) and needed to be checked:

Calibrating the Vinduino sensors

Now they are looking good (after 15:00 GMT). See if you can spot the change.


We have some new rsync backups from our openvino servers! Badly needed....all that matters is the data. But now we have copies.

Alvaro Gandía and Luis Rovello from came to visit this morning and share their vision about future wine models!

Everything is flowering at Costaflores Organic Vineyard.

Updated Blockchain nodes

Jordi finished rebuilding echo, our initial blockchain node, and made the udpates to accommodate Vinoblocks. Now we have four nodes up and running for testing.

....and I managed to pull off the battery terminal connector on the Cabernet Sauvignon that sensor group is out of commission until I can solder it back on. 

Otherwise, I setup the backup initial backup scripts for OpenBravo. Luckily we didn't lose any information over the past days without a backup. 

INTA presentation

Today I made a short (10 minute) presentation of Openvino at an INTA event in Mendoza. 

The rest of the day was spent working on the vinophonics motorized slider controller and the vinoblock update with Jordi Estapé Canal.

Recently we had to recover our ethereum nodes, due to file system corruption on one of our virtualized servers. We were able to reconnect the nodes, and added a new prototype vinoblock node at Costaflores.



Vinophonics?...we will find out!

Here is where we it starts.

WineLab @ FabLab

On Saturday, we got to visit the amazing WineLab program at FabLab in Barcelona. Surely, we will be borrowing and sharing ideas with WineLab in the future.

This is an example of a new post on the new server, after having imported the backup copy of the previous server.

Visit to Valldaura

Today Mike Barrow met with Jonathan Minchin, director of the

We look forward to many collaborations with Jonathan and his team to develop help develop vineyard robotics.

Over the weekend, we installed a RasperryWeatherPi and Vinduino at Baussitges. We have some issues pending with the LoRa link between the two stations, but otherwise, all went well. Coincidentally, or maybe accidentally, after installing the weather vanes on the solar panel tower, the solar array stopped working properly and Baussitges is now in the dark. Oops. 

This weekend, we are installing sensors (vinduino and RaspberryWeatherPi) in the Pyrnees at This is 2000Ha forest from which we will be extracting organic cork for future vintages, and where we are evaluating the feasibility of planting an experimental Torrontés vineyard on the hillside of a previous, pre-phylloxera vineyard (Clot de la Vinya).


"hotel" - the Baussitges Vinduino LoRa gateway and RasberryWeatherPi.

View from la Llosa

Building the LoRa gateway in the offices in Terrassa.

Joaquin Jimenez building the "Clot de la Vinya" vinduino node.

Currently, data received from vinduinos and sensor stations is being stored in a DB service. Vinduinos and sensor stations send the data collected to Bravo node ( where the DB is allocated (PostgreSQL 8.3.x server). This database is used by the website ( to display the data for the user to check. A structure similar to the one shown in the following figure:

With this proposal I want to change this strucuture in order to replace the database with a Side Chain (Ethereum private network) solution. This proposal will integrate the database part of the project into the blockchain, and thanks to that, this project is going to based on a full-blockchain backend (not really common). Having a full-blockchain backend contributes highly to transparency and immutability. As OpenVino is an open-vineyard, transparency is crucial. The new structure is going to follow this structure (extended description of internal side chain design in the 'Blockchain storage proposal'):
Apart from that, this migration will also allow the future introduction of the validator figure, explained in the initial 'Blockchain storage proposal'. Adding this figure will increase the value of the project by giving the opportunity to:
  1. Prove that data collected and stored is correct and no negligence is committed during the sensor to bravo communication.
  2. Control that data stored has no outlier and that everything is working correctly during the Growing the grapes process.
  3. Add a new feature to allow users interaction with the vineyard via and App that leads them to improve their wine and blockchain knowledge.
This initial proposal will only include the part of storing the data in the blockchain. This decision was made because after making a first approach to the problem with the 'Blockchain storage proposal', I have realised that there might be several problems when it comes to using Blockchain as a Database because it is not as optimized as an SQL DB and this could lead to a slower response time which is undesirable. So in this first step of the Side Chain Development, I'm going to implement the data storage part of the side chain solution and load tests are going to be executed in order to check if the system proposed response time is acceptable or not. In case of not being acceptable a second iteration is going to be done adding a DB to store utility indexes in order to reduce the response time of queries and searches and other optimizations.
For this project to be done, a private Ethereum Network and a Database Server (in case of reaching the second iteration) must be given.  The raspberry in charge of inserting data to the blockchain will have to own a pair of private/public keys. I will also need a clear specification of the data extracted with the sensors and its treatment. Communication with the website development team might be necessary in order to make both developments fit.
After having finished the first part of the proposal, a blockchain database system will have been deployed and documentation for its integration with the sensors/vinduinos and the website will be given. Once finished and accepted, the validation part of the Side Chain proposal will begin (defined as a new project). This part might alter the first smart contracts given but a full migration will be included and previous functionalities won't be changed.
The development of this Side chain data storage feature is being started today and tomorrow it is planned to have already defined the requirements. Communication with team members might be necessary in order to establish quality and performance requirements.