not approved

PeakChain Cardano Car Wallet Device

$358,300.00 Requested
Ideascale logo View on ideascale
Community Review Results (1 reviewers)
Impact / Alignment
Feasibility
Auditability
Solution

Create a hardware device that allows cars to connect to the Cardano blockchain. This would be done in a decentralized way by submitting transactions, including car data and managing the vehicle wallet

Problem:

At the moment, no hardware devices allow cars to securely communicate with the Cardano blockchain, transmit sensitive data, as well as manage a wallet.

Yes Votes:
₳ 46,243,562
No Votes:
₳ 113,198,938
Votes Cast:
222

  • download
  • download
  • download

[IMPACT] Please describe your proposed solution.

1- Connected Car Market Size

Vehicles are increasingly becoming IoT devices with internet capabilities, including greater connectivity. The expected size of the connected car fleet industry is expected to grow from worldwide 200 million units in 2021, to over 800 million in 2035 [1].

In addition, the global connected car market swelled to 65 billion USD in 2021. Meanwhile, the market is expected to expand to approximately 121 billion USD by 2025. [1]

2- Connected Car Privacy and Security Challenges, as well as Blockchain's Role

The increasing connectivity of vehicles constitutes a rising privacy and security problem. After all, vehicles connect solely to centralized servers – including manufacturers' servers.

Plus, the increasing connectivity of vehicles is opening up the problem of a broader "attack area" for malicious actors. Hence, a car could be hacked from the wireless to CAN Bus [2].

The automotive and mobility sector is aware of these issues. Hence, several articles and research papers were published to address this issue, emphasizing the role of the Blockchain in ensuring secure, private IoT vehicles [3] [4] [5].

3- Connected Car Blockchain Solutions MUST be real Web3 solutions

Blockchain solutions for the automotive sector must be real Web3 decentralized solutions. More specifically, there should be no involvement from centralized servers in the vehicle data transmitted to the Blockchain.

Unfortunately, currently, several Blockchain solutions claim to be real Web3 solutions when this simply isn't the case. In reality, these solutions are Web2 centralized but packaged in Web3 marketing. Centralized entities manage these tools.

Using comprehensive and real-life examples, Moxie Marlinspike discusses the issue with the blockchain industry in a recent blog post [6].

On the opposite side of the coin, PeakChain is working on developing a real Web3 automotive solution. Ultimately, through the solution, car data could neither be impacted by by centralized servers nor managed by centralized entities.

4- Features of PeakChain Hardware wallet:

But, to realize the above, we are focusing on a hardware device with car connectivity while offering the below functionalities:

· The car connects to the hardware directly through a dedicated OBD2 port; this port exists in almost every car.

· The hardware is connected to the internet through an embedded sim card .

· Our hardware is connected exclusively with the Cardano Blockchain by submitting transactions. There is no server in the middle connected to our hardware.

· The hardware retrieves sensitive data from the vehicle like vehicle speed, the time, engine RPM etc.

· Data is obtained in a raw output in a special CAN Bus format.

· This data is decoded in a human-readable format using embedded software.

· The hardware runs a full Cardano node and a wallet.

· Upon trip completion, the hardware submits a transaction to the Cardano blockchain, including the previously retrieved vehicle data's metadata.

This hardware will allow many Web3 mobility solutions on Cardano to merge. Check the following section to discover the PeakChain hardware component's application domains.

References

[1] strategy&, Part oft he PwC network, "Digital Auto Report 2021, acceleration towards the new normal "- volume1 https://www.strategyand.pwc.com/de/en/industries/automotive/digital-auto-report-2021/strategyand-digital-auto-report-2021-vol1.pdf

[2] Sen Nie, Ling Liu, and Yuefeng Du. Free-fall: hacking tesla from wireless to can bus. Briefing, Black Hat USA, pages 1–16, 2017.

[3] A. Dorri, M. Steger, S. S. Kanhere and R. Jurdak, "BlockChain: A Distributed Solution to Automotive Security and Privacy," in IEEE Communications Magazine, vol. 55, no. 12, pp. 119-125, Dec. 2017, doi: 10.1109/MCOM.2017.1700879.

[4] J. Halabi and H. Artail, "A Lightweight Synchronous Cryptographic Hash Chain Solution to Securing the Vehicle CAN bus," 2018 IEEE International Multidisciplinary Conference on Engineering Technology (IMCET), 2018, pp. 1-6, doi: 10.1109/IMCET.2018.8603057.

[5] Falco, G., & Siegel, J.E. (2020). Assuring Automotive Data and Software Integrity Employing Distributed Hash Tables and Blockchain. ArXiv, abs/2002.02780.

[6] Moxie Marlinspike, "My first impressions of web3", https://moxie.org/2022/01/07/web3-first-impressions.html, "Jan 07, 2022".

[IMPACT] Please describe how your proposed solution will address the Challenge that you have submitted it in.

Mobility, as a sector, is one of the largest and fastest-growing by market size and user numbers. However, the hardware as mentioned above will help unlock innumerable mobility solutions for exclusive use on the Cardano Blockchain.

Ultimately, this will increase demand for the Cardano blockchain: by increasing retail users and enhancing the adoption of Cardano by automotive manufacturers and mobility service providers.

What follows are some of the application domains of the PeakChain hardware component.

1- Remote Software Update:

Given the rapid digitalization and proliferation of vehicle connectivity, the number of ECUs (Electronic Control Units) embedded in each Car is growing at a significant pace.

ECUs contain software that should be continuously maintained and updated. That way, fix bugs can be applied while features can be enhanced.

The firmware update process could be done by driving to a service center and flashing the software manually, or through a remote software update.

The remote software update represents one of the biggest security challenges in the automotive industry.

Similar to Tesla, one current solution is using a VPN. Still, the long-term solution should be by connecting cars to the Blockchain using a dedicated device and performing the updates in a decentralized way.

Thus, a hardware component with vehicle connectivity and which receives ECU update instructions through blockchain transactions, but without a centralized manufacturer server in use, is integral. This approach will reduce the malicious actors' attack surface.

2- Insurance

Car Insurance companies are willing to offer customizable insurance contracts based on their customers' driving behavior. Nonetheless, such driving behavior contains sensitive content that should be collected directly from the car, like speed, braking behavior, etc..,

Hence, a hardware device is needed to collect these sensitive data directly from the vehicle, hash it and transmit it securely to the Blockchain.

Just the allowed actors could decode the driving data existing in the Blockchain using their private keys.

3- Electric Vehicles

The proliferation of electric vehicles is incredibly fast. Still, all data is managed in a centralized manner – examples of these include the car manufacturers' or charging station service providers' servers. Obviously, though, all vehicle data should be managed by the charging service provider platforms for charging electric cars.

To help enable a smooth charging user experience, automatic vehicle charging should be adapted based on the customer's need and their typical preferred journey habits. Consequently, the car should interact with other IoT devices like a smart home. Special hardware embedded in the car is, in this use case, essential for secure and private data communication through the Blockchain

4- Car-sharing Services

Carsharing services are increasing rapidly. In 2019, the car-sharing market size exceeded USD 2.5 billion and is expected to surpass USD 9 billion by 2026 [1].

Central entities (huge companies) manage payments, contracts, and customer/car data. Potentially, users could be tracked and have their data abused.

But, to address security and privacy issues, customers must communicate, transact with the vehicle and pay it in a peer to peer way.

The customer's driving behaviour and travel trajectory should be kept private and protected from malicious actors willing to manipulate or abuse the customer or the car data. Hence, using block solutions as a base, carshasing services and cars must maintain communication with the customers and Blockchain. This would be done by deploying dedicated hardware fully decentralized, privately and securely.

With all above in mind, We will implement this use case in our proposal submitted in fund 9**:**

PeakChain Car-Sharing Platform

<https://cardano.ideascale.com/c/idea/414199>

5- Fleet Management

Fleet Management services were estimated to increase worldwide from around 13 Billion dollars in 2017 to around 28 Billion dollars in 2022 [2]

Especially logistic companies must monitor their fleets to reduce fuel consumption and optimize driving behavior and trajectory. Fleet management data of all kinds is essential for the development of a business and should remain confidential. Security or privacy concerns in a company's fleet management of data could significantly impact competitiveness.

Also, there is the need to manage the fleet data through the Blockchain using special hardware embedded in the vehicles—this hardware will be capable of retrieving and transmitting the needed data.

We will implement this use case in our proposal submitted in fund 9:

PeakChain Fleet_Management Platform

<https://cardano.ideascale.com/c/idea/414216>

6- Ridesharing/Ride-hailing services (like Uber)

The market size of ridesharing services is increasing worldwide. The figures have stemmed from about 58 billion USD in 2021 to an expected 185 billion USD in 2026 [3].

However, like car-sharing and fleet management services, users should control their data completely. The data retrieved from the car and trajectory of the travel and costs should remain confidential and not open to the abuse or manipulation of others. In addition, the payment should occur peer to peer between the client and the car.

As mentioned earlier, there is a need for a hardware device connected to the vehicle to ensure the secure management of customer and car data using the Blockchain. This further assures a secure peer-to-peer payment between the customer and the car using the car wallet and customer wallet through a Cardano Native token.

We will implement this use case in our proposal submitted in fund 9:

PeakChain Uber on Cardano

<https://cardano.ideascale.com/c/idea/414255>

References

[1] P. W. Wadhwani and P. Saha, "Car sharing market size by model (P2P, station-based, free-floating), by business model (round trip, one way), by application (business, private), industry analysis report, regional outlook, application potential, price trend, competitive market share & forecast, 2020–2026," Global Market Insights, Pune, India, Tech. Rep., Apr. 2020. [Online]. Available: https://www.gminsights.com/industry- analysis/carsharing-market

[2] https://www.prnewswire.com/news-releases/fleet-management-market-2017-2022---focus-on-operations-information-risk-vehicle-maintenance--leasing-safety--compliance-300524424.html

[3] https://www.marketsandmarkets.com/Market-Reports/mobility-on-demand-market-198699113.html#:~:text=%5B221%20Pages%20Report%5D%20The%20global,USD%20185.1%20billion%20by%202026

[IMPACT] What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?

1.Main Challenges:

There are three main challenges

  • Presently, many startups are merging without any recognized, formal and established legal entity offering full transparency. Consequently, team members sometimes have no experience in the market in which they are operating, meaning they have unproven experience.
  • Most innovative projects fail to deliver on time and have an excessive time to market.
  • Most projects focus on delivering features, often choosing to skip software quality assurance efforts, assuming that the cost of quality is higher than the cost of non-conformance.

2.Our Strategy to mitigate the risks:

2.1. Building Trust:

  • Our expert team has significant experience, working on Connected Car Projects in the automobile industry for extensive periods.
  • We are a transparent legal entity, a company called PeakSoft GmbH based in Wuppertal, Germany. For many years, we have been dedicated to delivering software development and software quality/test automation solutions.
  • For more information about PeakSoft GmbH, the company forming PeakChain, please check our website: <https://peak-soft.de/>
  • For more information about the company legal information, please check this link: <https://peak-soft.de/impressum/>

2.2. Short Time to Market:

  • Our Strategy is to build and deliver high-tech, effective solutions through an incremental agile process. Our team, collectively, possesses technical and management experience
  • We have developed an initial prototype with the infrastructure we need to succeed. In this way, we can concentrate on building impactful features and accelerating our deliveries.
  • Agile Software Development methods will be used to manage our project, in particular with a focus on Scrum. Sprint period iteration will last two weeks Agile Software Development methods will decrease time to market while accelerating the pace of development by focusing on delivering plug-and-play features within short increments, without having a detrimental outcome on quality.

2.3. "Highly" Prioritizing Quality

  • Short time to market doesn't mean delivering features and hindering quality. We are ISTQB Certified, offering outstanding experience in software quality assurance and test automation. Consequently, quality will be our main focus.

  • We plan to utilize ISTQB as a standard to ensure our quality. A dedicated test concept containing details of the software quality assurance process will be formed in the project.

    [FEASIBILITY] Please provide a detailed plan, including timeline and key milestones for delivering your proposal.

Please check all acceptance criteria of the project, roadmap, team, and budget under this Link:

<u>FEASIBILITY SPREADSHEET</u>

https://docs.google.com/spreadsheets/d/1pk8xGbfz8IZmsrSJpeQIe7NxUDALWY-D/edit?usp=sharing&ouid=115765945842863689790&rtpof=true&sd=true

[FEASIBILITY] Please provide a detailed budget breakdown.

Please check all acceptance criteria of the project, roadmap, team, and budget under this Link:

<u>FEASIBILITY SPREADSHEET</u>

https://docs.google.com/spreadsheets/d/1pk8xGbfz8IZmsrSJpeQIe7NxUDALWY-D/edit?usp=sharing&ouid=115765945842863689790&rtpof=true&sd=true

[FEASIBILITY] Please provide details of the people who will work on the project.

1.PeakChain Team:

Below is a list of all employees of PeakSoft GmbH. All team members are living and working in Germany:

• Oussama Benmahmoud

  • CEO and Co-Founder of PeakSoft GmbH
  • Industrial Engineer
  • Project Management and Software Quality Assurance
  • +5 years Experience in Connected Car Projects by Volkswagen
  • +8 years experience in Software Quality and Test Automation
  • Plutus Pioneer
  • LinkedIn: <https://www.linkedin.com/in/oussama-benmahmoud-43693926/>
  • Twitter: @Oussbenma

• Abderrahim Issaoui

  • CTO and Co-Founder of PeakSoft GmbH
  • +10 years experience as a Software Engineer
  • Plutus Pioneer
  • Experience as Lead Frontend Developer
  • LinkedIn: <https://www.linkedin.com/in/abderrahim-issaoui-b3149227/>
  • Twitter: @AbderrahimAiss

• Habib Mokni

  • Software Engineer
  • Frontend Developer
  • Linkedin: <https://www.linkedin.com/in/habibmokni/>

• Mohammed Abdelali

  • Electronic and Communication Engineer
  • Software Quality Assurance Specialist
  • +5 years Experience in Connected Car Projects by Volkswagen
  • +8 years experience in Software Quality
  • Linkedin: <https://www.linkedin.com/in/mohammed-abdelali-290b7b101/>

• Neyla Issaoui

  • Project Management Office
  • Responsible for Administration, Accounting and Coordination Tasks
  • LinkedIn: <https://www.linkedin.com/in/neyla-issaoui-266534199/>

• Ramla Mahjoub

  • Project Management Office
  • Responsible for Administration, Accounting and Coordination Tasks
  • LinkedIn: <https://www.linkedin.com/in/ramla-mahjoub-25a1843b/>

2. Project Roles:

2.1. Project Management:

• Oussama Benmahmoud

o Certified Project Management Professional (PMP)®

o Certified ITIL® - IT Service Management - Foundation Level

o Certified Professional Scrum Master™ I (PSM I)

o Certified Professional Scrum Master™ I (PSM I)

2.2. Plutus Blockchain Development

  • Abderrahim Issaoui: Plutus Pioneer
  • Oussama Benmahmoud: Plutus Pioneer

2.3. Frontend Development

• Abderrahim Issaoui

  • Lead Frontend Engineer
  • More than 10 years of experience in Software Development Projects
  • Experience as Lead Frontend Development
  • Professional Scrum Master (PSM1)
  • Microsoft Certified Professional
  • CCNA 1 & CCNA 2
  • Microsoft Technology Associate: Software Development Fundamentals

• Habib Mokni

o Frontend Engineer

2.4. Connected Car Hardware Components and integration:

• Mohammed Abdelali

<u>More than 5 years of experience in Connected Car Projects with Volkswagen</u>

• Oussama Benmahmoud

<u>More than 5 years of experience in Connected Car Projects with Volkswagen</u>

2.5. Software Quality Assurance:

• Mohammed Abdelali:

o More than 8 years of experience experience in Software Quality Assurance

o Certified ISTQB Foundation Level

• Oussama Benmahmoud

  • More than 8 years of experience experience in Software Quality Assurance
  • Certified:
  • <u>ISTQB Foundation Level</u>
  • <u> ISTQB® Certified Tester – Foundation Level, Extension Agile Tester</u>
  • <u>ISTQB® Certified Tester – Advanced Level – Test Analyst</u>
  • <u>ISTQB® Certified Tester – Advanced Level – Technical Test Analyst</u>

2.6. Administration, Accounting and Coordination Tasks

• Neyla Issaoui

• Ramla Mahjoub

[FEASIBILITY] If you are funded, will you return to Catalyst in a later round for further funding? Please explain why / why not.

We will return to catalyst in later rounds for further funding to implement further features of the hardware

[AUDITABILITY] Please describe what you will measure to track your project's progress, and how will you measure these?

1.Using Agile Software Development Methods:

  • Agile Software Development methods will be used to manage our project, in particular with a focus on Scrum. Sprint period iteration will last two weeks
  • Agile Software Development methods will decrease the time to market and accelerate the development pace. This will be achieved by focusing on delivering plug-and-play features within short increments without detrimentally impacting quality.
  • Scrum will significantly increase the transparency and auditability of the project progress status and its deliverables.
  • A Scrum board will be created in Atlassian JIRA Tool to track the project's progress.
  • Product Backlog, including the planned tasks in user stories, will also be created in Atlassian JIRA Tool.
  • After the Sprint Review meeting, a Sprint Reports will be created, including relevant KPIs and the accomplished user stories

2.Defining clear acceptance criteria for the project components and deliverables:

We have ideated and subsequently implemented clear acceptance criteria. Within these criteria, we will successfully deliver within six months the first product increment.

Consequently, acceptance criteria will be reworked in the form of user stories and entered in the product backlog as to-dos.

Please check all acceptance criteria of the project, roadmap, team, and budget under this Link:

<u>FEASIBILITY SPREADSHEET</u>

https://docs.google.com/spreadsheets/d/1pk8xGbfz8IZmsrSJpeQIe7NxUDALWY-D/edit?usp=sharing&ouid=115765945842863689790&rtpof=true&sd=true

[AUDITABILITY] What does success for this project look like?

As described in the previous Section, "Auditability", we have ideated and subsequently implemented clear acceptance criteria. Within these criteria, we will successfully deliver within 6 months the first product increment.

Consequently, acceptance criteria will be reworked in the form of user stories and entered in the product backlog as to-dos.

Success criteria mean effectively completing the stories outlined in each sprint and delivering the first increment of the product, as well as successfully fulfilling all described acceptance criteria.

Please check all acceptance criteria of the project, roadmap, team, and budget under this Link:

<u>FEASIBILITY SPREADSHEET</u>

https://docs.google.com/spreadsheets/d/1pk8xGbfz8IZmsrSJpeQIe7NxUDALWY-D/edit?usp=sharing&ouid=115765945842863689790&rtpof=true&sd=true

If you would like to read a summary of our projects, please check our medium publication:

<https://medium.com/peakchain>

To prove our commitment and engagement, and our contribution on the cardano network and its decentralization, we are running a staking pool called: PeakChain Pool, Ticker [PKCP]

For more information about our staking pool, please check its website:

<https://www.peakchain-pool.com/>

[AUDITABILITY] Please provide information on whether this proposal is a continuation of a previously funded project in Catalyst or an entirely new one.

New Proposal

Community Reviews (1)

Comments

close

Playlist

  • EP2: epoch_length

    Authored by: Darlington Kofa

    3m 24s
    Darlington Kofa
  • EP1: 'd' parameter

    Authored by: Darlington Kofa

    4m 3s
    Darlington Kofa
  • EP3: key_deposit

    Authored by: Darlington Kofa

    3m 48s
    Darlington Kofa
  • EP4: epoch_no

    Authored by: Darlington Kofa

    2m 16s
    Darlington Kofa
  • EP5: max_block_size

    Authored by: Darlington Kofa

    3m 14s
    Darlington Kofa
  • EP6: pool_deposit

    Authored by: Darlington Kofa

    3m 19s
    Darlington Kofa
  • EP7: max_tx_size

    Authored by: Darlington Kofa

    4m 59s
    Darlington Kofa
0:00
/
~0:00