Quote from: rudolfaxl on March 14, 2017, 04:23:16 AM

Wait news parkingchain!

Release of ParkingChain is still a month or two away, best I can do at the moment is what I posted above, no big changes to that.

Quote from: ParkByte on March 04, 2017, 06:59:24 PM

**DISCLAIMER: All information here is not final, is not an update, is still in planning so can change from time to time and is only thinking on paper Roll Eyes

**

I do understand your concerns and no details are finalized as to the new token, there is also the PKB premine that I have to consider. My current thinking is to fork PKB over to a smart contract chain like ETH (same one as PKC), burning the PKB premine in the process then at a certain stage of the PKC sale (fixed on quantity of PKC not a time limit) once we have sold X number of PKC token's reward all current PKB balance holders with a ratio of x:x PKC's.

Both PKB and PKC should be seen as two different projects, there is so much involved in PKC though I have tried to give a basic outline below -

PKC is aimed at getting away from exclusive parking contracts and giving the consumer choice - the operational side consumers will never really see. In the UK, local governments put out tenders and service providers all bid to get that one contract for say 5 years. They do this 5 year period to save money when changing enforcement systems, parking attendants now need a mobile device to check digital tickets - changing systems can be costly.

The design of the actual ParkingChain (not the tokens) is for it to be Autonomous - Running on a smart contract - Database Nodes get paid by the smart contract to be online based on a ratio of Uptime, Requests and Space Used - Operators pay directly into the Autonomous Smart Contract to Read/Write into the ParkingChain (which pays the Nodes) - There will likely have to be trusted 99% up-time master-nodes to manage the data.

PKC will centralize data from all sources into a decentralized database into a standardized format, whether it is from Mobile Provider 1 or 2, a On-Street Machine or some other method. This data is then used by one existing enforcement system, operators can now switch provider or offer multiple providers with no costly equipment changes, new training etc.

Whilst all this information is in a decentralized database it was also suggested that we should also create a cloud based parking machine. It really is a great idea - it is what we were creating for PKB so to keep it simple and to enhance the value of using PKC this will come as an opensource SDK - an environment to access PKC data and create a virtual parking machine in Android/iOS/Windows/Linux and development of a universal upgrade board for physical parking machines using the PKM SDK potentially creating a few digital currency ATM's in the process - there are millions of unattended payment machines around, even if they are limited to £1/$1 a time.

A good example of a centralised parking database on a national level is https://nationaalparkeerregister.nl/uploads/media/Interface_Description_v7.0.pdf, we are transforming that into a decentralized database, using blockchain technology and making it global - with loads of extra's.

Ultimately, the PKM SDK will default to PKB as its currency - PKC is used by the operators for storing the transaction data in a centralized-decentralized database for back office use.

I have to admit this is a really ambitious plan and has taken months of planning to get to where it is, I just now need to finalize all the details and publish it, there is so much and I want to get it all right first time so we can move straight into the crowdsale.

**DISCLAIMER: All information here is not final, is not an update, is still in planning so can change from time to time and is only thinking on paper Roll Eyes

**