[Page: 2] Here you can see all published posts ordered by the date of publication.
Hello BitCar aficionados!
This article follows on from our previous Tec2 Article, where we introduced Rowan, Will and highlighted some of the frontend challenges. We are happy to report that the team has been working fast and furious (no pun intended!) on the platform, to meet some significant milestones, as outlined below.
Front-end Development
Previously, we outlined how one of the challenges […]
Ready, set, burn! BitCar has completed its final token burn, successfully burning 36,000,000 BITCAR tokens on the 26th September.
What is a Token Burn?
A token burn means sending the tokens to be burned to a public address, from which those particular tokens can never be spent because the private keys of such an address is unobtainable. Click here to find the transaction details about the BitCar […]
Hello BitCar enthusiasts!
This article follows on from our last #BitCarTEC 2 article, which focused upon the backend architecture and progress to date. Since that article was released, the team has grown to include a dedicated front-end developer (Rowan) and a Chief Product Officer (Will). Part of Will’s role will be to provide more consistent updates and a link between our technical team and the […]
At BitCar we are very happy to welcome our new members to the team! Read on to find out more.
William ‘Will’ Foster
William joins the team as the Chief Product Officer. He brings a distinct blend of technical and business knowledge to the BitCar team, having worked in the IT industry for over 15 years, across a variety of roles including full-stack software engineer and software development […]
Dear BitCar Community,
BitCar Pte Ltd is pleased to provide the first major update since the ICO completed in Q2 2018.
Important BitCar releases will be lodged ONLY on our website at Bitcar.io. This major announcement has been verified on the blockchain using the world’s first ever blockchain App (which the founders proudly made in 2015 called Uproov.com, enter this EzyID to verify this release […]
Hello BitCar community!
Continuing from the previous #BitCarTEC article, today we spoke to Alejandro, our newest backend developer who you all met in July. We sat down to talk about his progress on the platform, what he’s done and what challenges he faced along the way.
Alejandro explained that several components and third parties are considered in the platform’s architecture design, these are: UI […]
Hello BitCar enthusiasts.
Today we present you with some of the technical challenges that we and many other blockchain projects currently face. We are looking for your innovative and clever ideas!
With this new series of blog posts, we hope not only to engage in the process of becoming more transparent about what we are doing but also to get some positive feedback from the community. Hopefully, […]
BitCar Token Burn has commenced
BitCar successfully burned a total of 151,577,871 tokens during the scheduled token burn on the 31st July. Approximately 60 per cent of the initial public sale amount of 250M tokens have been burned, significantly reducing the number of coins in circulation.
Founders will volunteer to burn approximately 50 % of their tokens from the remaining 236,936,631 tokens […]
Token burn to take place before the end of July
BitCar Confirms Token Burn
The team at BitCar are pleased to announce the close of our token distribution. A huge thank you to all of our global team that helped with the success of the Token Sale from start to finish! From the Token Sale we sold a total of 98,422,129 BITCAR tokens, with the SGD 9.24M Token Sale completed on 20 April 2018.
Token Burn […]
BitCar Token Burn!
Ladies and Gentlemen, start your engines. The BitCar team are ready to burn some tokens! Mark it down in your calendars as the first token burn will commence on 31 July UTC 7.00 AM.
The community will see on the blockchain from the BITCAR Token Contract an amount of 151,577,871 BITCAR being burned forever! These being the unsold token from the Token Sale earlier this year.
We […]