McFly.aero is a solution to the "who owns the button" problem on the air taxi market. It will use blockchain technology to give the Button to You, push for operational efficiencies, provide volumes to partners and great prices to passengers.
Today is the start of the $1.2Tn market!
20 companies work on flying cars.
6 corporations have invested in manufacturing.
Blockchain.aero Consortium will provide the complete package of technologies for the urban air taxi grid.
You will have McFly tokens to deploy and use it in your city!
You think you read this to learn about us. Instead you will realise that YOU are already one of us.
McFly.aero is for entrepreneurs and passengers — future customers of a more than a trillion dollar industry of urban air taxi flights.
Blockchain.aero Technology Consortium Members will give you technology to be used in your city. Both hardware (vehicles, chargers, components) and software (blockchain, token, smart-contracts, APIs and apps).
Local entrepreneurs and evangelists like yourselves will deploy them into a local grid of connected devices — the IoT — internet of things. Every owner of every device will get rewarded in McFly tokens every time the device is used to serve flight to a passenger. If you don’t do it, then your local government or a larger corporation will do it, but much later and you will have to pay higher fares.
McFly tokens issued on the Waves Platform are fully supported and valid. However we recommend to swap them into ERC20 McFly tokens, and the rate is always 1:1.
We will soon publish a Waves address. You send your Waves-based McFly Tokens to that address and insert a comment with your ETH wallet address as an attachment to the transaction. You will get one ERC20-type McFly on the attached ETH address, for every Waves-type McFly that you send.
There is a reserve of ERC20 McFly tokens to fully cover the circulating Waves-based McFly, so no worries here. Excess McFly tokens on Waves will be destroyed — no double accounting. There will be no more than 1800 million McFly after the Token Launch 1.2.