We are now listed with MTB18, MTB19, and MTB20 on the bomesp.com.br 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.
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 interblend.org came to visit this morning and share their vision about future wine models!
Everything is flowering at Costaflores Organic Vineyard.
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 vinduino...so 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.
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.
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.
Today Mike Barrow met with Jonathan Minchin, director of the romi-project.eu.
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 Bausstiges.com. 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.
Joaquín Jiménez 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 (10.112.48.22) where the DB is allocated (PostgreSQL 8.3.x server). This database is used by the website (costaflores.com) to display the data for the user to check. A structure similar to the one shown in the following figure:
- Prove that data collected and stored is correct and no negligence is committed during the sensor to bravo communication.
- Control that data stored has no outlier and that everything is working correctly during the Growing the grapes process.
- Add a new feature to allow users interaction with the vineyard via and App that leads them to improve their wine and blockchain knowledge.