Home Funds overview Fund6 F6: Developer ecosystem

ID: #600049 | Status:

Complete

Share this on Twitter Share this on Facebook Share this on LinkedIn Share this on Reddit

CPU/IOT development for fact data

Problem

To reduce the noise to society caused by data whose authenticity cannot be proven

-data can be super easily modified and processed by AI-

Solution

Aim to develop blockchain-compatible CPUs for IOT devices by using them to generate data that can prove the authenticity of the fact

Completed outcome

Download report

Total to date

This is the total amount allocated to CPU/IOT development for fact data.

$80,000

Total funds requested

Distributed: $80,000

Remaining: $0

Complete

In Progress

To be completed

427

Total Votes

₳193M

Votes Yes

₳49.5M

Votes No

About this idea

If you'd like to check our project in Japanese, please access the following URL.
日本語の資料は下記をご覧ください。
https://docs.google.com/document/d/1KwSrQjq3eZDpjeaNBh6XF782p81KQi5jSvHHr8j6-Rs/

Overall
Cardano is working towards realizing our vision of creating a decentralized, fair and smart society through blockchain technology.

How will blockchain become useful to society?

Assuming the need to ensure scalability and sustainability, blockchain is providing a means to solve various social issues by adding value to and preserving data through functions such as NFT and smart contracts, in addition to ADA (as a cryptocurrency).

Blockchain-compatible CPUs for IOT aims to help maximize the advantages of blockchain when it comes into use in an increasingly digital society.

Because it can be expanded by blockchain-optimized CPUs for IOT.

If the reliability of the data is not ensured (relying on the trust of the organization or person handling the data), it becomes inefficient or impossible to determine the authenticity of the data.

"Authentic data," which is a requirement for the establishment of smart contracts, can be provided for Oracle, the scenes in which it can be used will expand. Then, we will create an environment for data and token economy.

We plan to proceed in phases with the part where we can demonstrate the case.

This budget has been prepared for Phase 1 below.

Phases

Phase1 10months

To research IOT device internal processing and CPU specification requirements and to provide some docs

- To create data (measurements, images, videos etc) by running a private chain in a hypothetical IOT device.

- Total 7 patterns 101.5month/pattern

→ technical verification - Processing on CPU side-

・Activating a private chain

・Activation of the private chain and each sensor

Phase2. 10-12months

To develop a smartphone application to manage IOT devices and cross-chain.

- A smartphone browser application that connects IOT data to the public chain

- To find a solution to link NFTs of private chains to NFTs of public chains

→ technical verification - Processing on the IOT side-

・Connect each sensor to the CPU and collect data

・Control of each sensor

・Connection to the application

Phase3. 3-4months

To storage of oracle data and to develop data usage environment

-To store data with NFT in the cloud, and create a verification environment with data access rights management.

→ technical verification - Processing on the public chain side and cloud storage

・Issuance of NFT

・Proof of registration of activation terminal

・Proof of data recording

・Proof of data ownership

・Data storage

・Data access rights management

・Use of data by applications

Phase4. 6-8months

To start planning and production of CPU and IOT devices after the above steps

Budget

This budget has been prepared for only Phase 1 below.

-technical verification

$56,000-

※$8,000/pattern x 7

※1engineer $80/hour

※1pattern 100hours

-documentation

＄3,000-

-hardware/softwear/misc

＄2,000-

-project site development

＄3,000-

-Tax 20%

＄16,000-
In Japan, all cryptocurrncy exchanges are subject to 20% Miscellaneous income taxes.

-Total

＄80,000-

Teams

Project Management x 1

Softwear Engineer x 1 / Blockchanin Engineer x 1

Hardwear Engineer x 1 (depends on the status)

Special thanks for "RANKT pool RANKET2" at YouTube

He presented the core of this project in English.

https://youtu.be/KCp-27ik4jQ

"RANKT pool RANKET2" 's YouTube channel

https://www.youtube.com/channel/UC4eoRQ0wQltd_LV-PTuB8lw

*Basically this cannel have introduced the appeal of Cardano in Japanese.

Monthly report

NB: Monthly reporting was deprecated from January 2024 and replaced fully by the Milestones Program framework. Learn more here

December 24, 2022 Progress report

Status:

On track: No

Estimated completion date: -

Evidence

https://drive.google.com/open?id=1iRNTlZDR88mKVd56Fit26Yy8aDMnJQ5E

Summary

This month, we made progress on two main types of tasks. Event Team： Preparing lectures and exhibits for the private event, which our partner organized Documentation Team: Writing the closed report 　The event team gave a talk on blockchain and exhibited solutions at an event hosted by a global semiconductor company earlier this month. 　The audience at the event was from industries that still need to become familiar with blockchain and found the technology and applicability exciting. 　Many semiconductor companies were present at the event, which contributed to publicizing our project and raising awareness about the Cardano Foundation and Catalyst. 　The Documentation Team continues to prepare to publish the project's findings on the web as a well-developed document. Although adjustments could not be made in time for the submission date of this Monthly Report, most of the document writing has been completed, and we expect to be able to release the document by end of this year. We will discuss the details of this matter in a closed report that will be submitted shortly.

November 24, 2022 Progress report

Status:

On track: No

Estimated completion date: -

Evidence

https://drive.google.com/open?id=1Dvoi2YM0VV_-2UfM6HKYV5wYoZeEvKrG

Summary

This month, we made progress on four main types of tasks. 1. Software team: Exploring secure firmware update methods 2. Hardware team: Investigation of CPU specifications that are highly compatible with blockchain 3. Documentation team: Writing public documentation of project results 4. Event team: Preparation of lectures and exhibits for company-sponsored events 　The software team continued to work on the technical verification of "the activation of the private chain and each sensor" to be included in the project KPI from last month. 　In our solution, IoT edge devices collect sensor information that is supposed to work only with authenticated firmware. This purpose is to counteract possible malfunctions caused by hacking by malicious firmware, electrical noise, or other physical phenomena. 　　There are various methods to address this issue, and we have procured and begun evaluating a device called secure flash memory. This device is designed primarily to store highly confidential data, such as encryption keys securely, and is equipped with many more security features than ordinary flash memory on the market. We want to utilize this device to realize an edge device infrastructure that can be securely updated and operated. 　The hardware team continued to work on the project's next phase, the realization of a custom SoC. In parallel with our investigation of general peripheral controllers, we began functional verification of TIMER, WDT, and PWM. Including these functions above are practically indispensable, as they are often used in embedded system development. 　The Documentation Team continues to prepare to publish the project's findings on the web as well-documented documents. We are working to improve and expand the documentation and are making final adjustments to make it available to the public. 　The event team has been working on the preparation of presentation materials and exhibits for a presentation to be given at an event hosted by a global semiconductor company early next month. This month, our team allocated significant resources to this task. 　Since many companies will be present at the event, we will try to do our part to promote the project and help raise Cardano's profile.

October 22, 2022 Progress report

Status:

On track: No

Estimated completion date: -

Evidence

https://drive.google.com/open?id=1wddlgKoCL7I7L6I-amMkyX7JncZeCKqW

Summary

This month, the project made progress on three main types of tasks. 1. Software team: How to realize a secure device network other than TCP/IP 2. Hardware team: Investigation of CPU specifications that are highly compatible with blockchain 3. Documentation Team: Writing a public document of the project results The software team continued to work on the technical validation of the "activation of the private chain and each sensor" to be included in the project KPI from last month. Specifically, this month's work focused on verifying a non-TCP/IP solution for the secure network segment the device is configured to operate on. In our proposed solution, IoT edge devices that collect sensor information transmit sensor data to a data storage server via an IoT Gateway. Communication specifications for IoT edge devices vary. For example, some support Linux capable of network communication. In contrast, others do not support TCP/IP network communication by default such as the Arduino UNO. We have decided to prioritize Arduino UNO class devices in developing our proposed solution. We have tested methods other than TCP/IP for communication between IoT edge devices and IoT Gateways. Arduino UNO does not support TCP/IP network communication by default. We have been examining ways to communicate between IoT edge devices and IoT Gateways using methods other than TCP/IP. The current candidates are RS-422/485 and CAN2.0. These communication standards are multi-drop rather than point-to-point, so multiple devices can be connected to the bus and communicate with each other. These devices also have advantages over Ethernet standards regarding communication distance, device cost, and CPU utilization. However, they are unsuitable for video streaming applications due to their lower communication speed. Currently, we are testing the operation of the communication standard conversion program on the IoT Gateway. The essential process has been achieved, but there are still some processing problems, so we continue to work on implementation. The hardware team continued to work on the project's next phase, the realization of a custom SoC. We evaluate the existing CPU IP cores using the procured FPGA board for SoC development. Currently, we are verifying UART, SPI, and I2C for peripheral controllers. These communication standards are expected in embedded systems, and many sensor devices support them. We will continue to check SPI and I2C operation. The Documentation Team continues to prepare to publish the project's findings on the web as well-maintained documents. We are working to improve and expand the documentation and are making final adjustments for the release.

September 23, 2022 Progress report

Status:

On track: No

Estimated completion date: -

Evidence

https://drive.google.com/open?id=1rvz8Wp0WB3L81b7HODPwGM308gVRonB3

Summary

This time, the project made progress on three main types of tasks. 1. Software team : Technical verification of the function to store sensor data in a tamper-proof state 2. Hardware team : Procurement of a CPU development environment that is highly com patible with blockchain 3. Documentation Team : Writing public documents of project results The software team continued to work on the technical verification of "activation o f the private chain and each sensor" to be included in the project KPI. This month's specific work will be on encryption and authentication of inter-dev ice communication. In the solution we envision, only authorized IoT edge devices that collect sensor information will be able to join the proprietary network managed by the IoT Gatewa y and communicate with each other. We have conducted a technical verification of this functionality using gRPC's Cr edintial API. The server and client application were run on a Linux machine, and we were able to verify the operation of a simple authentication function. However, not all IoT edge devices have powerful CPUs and plenty of memory to run Linux. Our target devices are mainly RTOS or OS-less devices, so we need to carefu lly consider the amount of computation required by gRPC for encryption and authent ication. The hardware team continued to work on the next phase of the project, the implem entation of a custom SoC. The team received the FPGA board for SoC development tha t was procured last month and is currently evaluating the existing CPU IP cores. T he SoC we want to realize requires a high-speed cryptographic processor and a peri pheral controller for security communication, so we are working on design specific ations for these components. The Documentation Team continues to prepare to publish the findings of the proje ct on the web as well-designed documents. The acquisition of a dedicated domain na me and server operations have been coordinated, and the team is currently making final adjustments for the release of the documents.

July 23, 2022 Progress report

Status:

On track: No

Estimated completion date: -

June 12, 2022 Progress report

Status:

On track: No

Estimated completion date: 11/30/2022

May 26, 2022 Progress report

Status:

On track: No

Estimated completion date: 11/30/2022

April 20, 2022 Progress report

Status:

On track: No

Estimated completion date: 11/30/2022

March 25, 2022 Progress report

Status:

On track: No

Estimated completion date: 11/30/2022

Team

・development of smart contract

・web application development

・design/development/production of CPU and IOT devices

Osamu TAKAHASHI

Shigeo Haga

Website:https://sites.google.com/view/birthcertificatefordata/

All funds

CPU/IOT development for fact data

Problem

Solution

Completed outcome

Total to date

About this idea

Monthly report

December 24, 2022 Progress report

November 24, 2022 Progress report

October 22, 2022 Progress report

September 23, 2022 Progress report

July 23, 2022 Progress report

June 12, 2022 Progress report

May 26, 2022 Progress report

April 20, 2022 Progress report

March 25, 2022 Progress report

Team

Thank you for subscribing