As per the attached file, the Phase 1 application has been tested and is now in the final stages. Set-up of the product release is currently underway. Research into the applicability of Cardano's new technology for Phase 2 is underway.

As per the attached file, the Phase 1 application has been tested and is now in the final stages. Set-up of the product release is currently underway. Research into the applicability of Cardano's new technology for Phase 2 is underway.

Development progress.

Work on Phase 1 of the Izanami project is progressing well.

■Integration of mobile app and newly created back-end: in progress.

■Examine the current app overview: complete Achievements: 100%.

■Building the app in the local environment: completed -Merchant app: completed -Member apps: completed

■Recheck user flow: complete. Merchant apps: completed Member apps: complete

■Determination of areas for modification: complete Merchant app: complete Member apps: complete

■Calling APIs in newly created back-ends: complete Merchant app: complete Member apps: complete

■Testing back-end flows: in progress Merchant app: in progress Member apps: in progress

■Consultation/confirmation of testing environment: complete Re-consultation in progress

■Updating of system construction diagrams: complete

■Database and source code updates: complete (Addition of management process for shop (terminal ID) and app ID information)

■Investigation of coupon functions: ongoing

■Investigation into the scope of modification of the coupon function: in progress

■Setting up a test environment for the coupon function: in progress

■Meetings with shops to introduce the social experiment

＊Details of progress are also reported in this article 🔽 https://sipo.tokyo/?p=22435

Development progress.

Work on Phase 1 of the Izanami project is progressing well.

■Integration of mobile app and newly created back-end: in progress.

■Examine the current app overview: complete Achievements: 100%.

■Building the app in the local environment: completed -Merchant app: completed -Member apps: completed

■Recheck user flow: complete. Merchant apps: completed Member apps: complete

■Determination of areas for modification: complete Merchant app: complete Member apps: complete

■Calling APIs in newly created back-ends: complete Merchant app: complete Member apps: complete

■Testing back-end flows: in progress Merchant app: in progress Member apps: in progress

■Consultation/confirmation of testing environment: complete Re-consultation in progress

■Updating of system construction diagrams: complete

■Database and source code updates: complete (Addition of management process for shop (terminal ID) and app ID information)

■Investigation of coupon functions: ongoing

■Investigation into the scope of modification of the coupon function: in progress

■Setting up a test environment for the coupon function: in progress

■Meetings with shops to introduce the social experiment

＊Details of progress are also reported in this article 🔽 https://sipo.tokyo/?p=22435

Development Tasks September 5 - December 5

Analysis of technical requirements Smart contract development Database development KMS development API development Integration with blockchain Schedule development Integration testing Operational tasks Infrastructure Setup System testing

"■Problem:.

1. there is a difference between the business logic of the current point system and the business logic of the new point system requirements. Details are: 1. 　The current system has only 3 levels of redemption and points can be exchanged between merchants, but the new system will allow points to be exchanged according to the level of the merchant. 　Expiration date: The current system has a fixed expiration date at the end of the current year, but the new point system will allow the expiration date to be set by the level globe. 　The TCC and PointDevice systems are managed by a third party service and are not accessible. We have not been able to determine how the TCC and PointDevice systems can be linked. 2. We have not been able to determine how the TCC and PointDevice systems can be linked, and these are the only results we have at this time, but the scope is so large that we have not been able to determine other impacts.

Possible Response Methods: Response Method 1:. As a way to replace systems managed by third-party services, copy the logic of PointDevice and create a NewSymonsPoint with the same logic. Copy the logic of TCC and create a TCC with the same logic. => Check the impact on other apps. => Redirect endpoint apps to the new system. => Avoid using third-party services. => Apply new request logic for levels, expiration dates, etc. => Migrate point data to the blockchain. Support Method 2:. Create a NewSymonsPoint with information from the current system. => Migrate points data to the blockchain. => Third party services will continue to manage the logic and off-chain data."

Development Tasks September 5 - December 5

Analysis of technical requirements Smart contract development Database development KMS development API development Integration with blockchain Schedule development Integration testing Operational tasks Infrastructure Setup System testing

"■Problem:.

1. there is a difference between the business logic of the current point system and the business logic of the new point system requirements. Details are: 1. 　The current system has only 3 levels of redemption and points can be exchanged between merchants, but the new system will allow points to be exchanged according to the level of the merchant. 　Expiration date: The current system has a fixed expiration date at the end of the current year, but the new point system will allow the expiration date to be set by the level globe. 　The TCC and PointDevice systems are managed by a third party service and are not accessible. We have not been able to determine how the TCC and PointDevice systems can be linked. 2. We have not been able to determine how the TCC and PointDevice systems can be linked, and these are the only results we have at this time, but the scope is so large that we have not been able to determine other impacts.

Possible Response Methods: Response Method 1:. As a way to replace systems managed by third-party services, copy the logic of PointDevice and create a NewSymonsPoint with the same logic. Copy the logic of TCC and create a TCC with the same logic. => Check the impact on other apps. => Redirect endpoint apps to the new system. => Avoid using third-party services. => Apply new request logic for levels, expiration dates, etc. => Migrate point data to the blockchain. Support Method 2:. Create a NewSymonsPoint with information from the current system. => Migrate points data to the blockchain. => Third party services will continue to manage the logic and off-chain data."

Started development

Prepare specifications for Plan A Database and table definitions Server installation API programming

Started development

Prepare specifications for Plan A Database and table definitions Server installation API programming weekly meeting

A research volatility team has been established and is currently working on the project, as well as collaborating with the IOG.

A research volatility team has been established and is currently working on the project, as well as collaborating with the IOG.

This month we established a research and development team to begin learning about and evaluating the Cardano development environment. We are also in the process of initiating communication with IOG and awaiting a response.

Next month, we begin design work on Plan A of the Izanami project.

This month, a research and development team was established to begin learning and evaluating the Cardano development environment. Learn about EUTXO, Plutus and Haskell

Requirement definition with development team

Meeting with Akihabara, Chiyoda-ku, Tokyo

A meeting will be held with the Marlow team.

Meetings with ward councillors in Chiyoda Ward, Tokyo, to introduce the project's demonstrations began.