Technical Track

9/22

Regroup Meeting

Agenda

Recap

Business

Technical

Get initial things ready

Development: BAckend 

1. Can we add Postgres or sequel lite, step it up now for further development? 
2. Can we leverage your API
3. We can create a token pool but cant mint NFT yet 
4. Store it all in FF free database?
5. How are nodes/entities treated in Firefly?  Technically, do you have 1 node per project or Multiple nodes in a project? 
6. Wallet - ff creates its own blockchain wallet? or need to create an external wallet to support the token end
   ?

9/20

Nicko

Mona - 

1. NFT portion - use a token pool that FF has. Can you explain token pool, what stage 1155? applicable still . Thin extension to NF VS NFT. Can create pools, in the meantime we can set a unique ... to track ownership.  Hoping FF will have tech lower Levels we need to focus on upper layers of tech stack
2. A token pool allocates unique IDs to track donor to recipient, minting and transfer happen with that ID. That id is unique for the asset class, each thing inside has an index. The pool represents class, Index represents items. 
3.   integer id represents different types of 

ETH connect - Earlier code, just a more user-friendly web interface in front of Ethereum. Provides functionality - internal utilities.  system governance issues handled.  We should not have to worry about it.  

ERV 1155, or just FF, if the connector is sufficient, we should mainly deal with FF. That layer should  be done for us

CLI - FF API  is where e will build app to build token pool mint and transfer.  FF creates, soon mints,s, and transfer all on the FF API.  1155 is it good enough?  Yes we think so. 

Bare Bottoms:

Next Steps:

Download FF CLI

Start a FF Environment, and explore API

Start by the backend, what does the app need to do and build against ff API. 

Big constructs: Messaging and DAta

Reference piece a data between token and message. Get transfers down _ data flow= points of hand off with proof of real-world asset, take for of message with data points mapped out. ,. 

API calls - FF goal is to develop the business logic of the problem trying to solve ( interface user mgt... )  build all of it today except the token part. 

Do we need to solve identity registering 

Business id done for Friday

Backend side - complete first then we can plugin API 

Many member network

Agenda:

Intro

Hardik - described where we are in the project. 

Discuss Email

Hi. I'm catching up with James Barry and Bill in person as Taekion are a partner.

My understanding is that you are interested in the RocksDB implementation we've open-sourced under Apache but haven't had time to contribute to Hyperledger Sawtooth core.

I gather from talking to James that you aren't interested in using this unless it is contributed.

It would be great to have a call to discuss this. Please choose a time that works for you using calendly.com/duncanjw

Best
--

Duncan Johnston-Watt

CEO, BTP

@duncanjw

+44 777 190 2653
calendly.com/duncanjw
linkedin.com/in/duncanjohnstonwatt 

9/17 

Nicko - Question At end of the chain how does the donor know what he received? He will be able to track the donation thru the QR code as well as digital pictures.  A Picture IS taken at each transfer. QR represents the unique id associated w/ transaction. The Collection of NFT's (IPFS) hash will be stored and used as a link. Each picture's hash links back to the QR code.  Donor generates the first instance of QR code.

Is this feasible? YES 

NFT will be stored on a local database.

Still working on tokens, NFT ARE NOT READY TO BE used out of the box. Is there a way to do this in a different way w/o nfts?

Upload a blob,  Store Image, and store hash. The payload can be transferred to other members of the network. Roll them up into transaction ID.  Can we make a collection of these Blobs? 

No concept of the collection, but generate a topic within firefly. it defines a narrowing ordering system. Topics get assigned to several messages and need to be processed in order. Donation run in Parrelle by topics, an end to end joining messages in a certain order

1. Upload an image and get data id
2. Send a message with tx id. Nodes that are part of the network can query by topic. 
3. The message does not associate with a topic until it is sent (set the topic) Donor
4.  Driver uploads message under a topic he can be sure it is the right topic with QR code or is embedded into the QR code. 
5. Scan QR code and take a picture, send a message,...HERE IS THE NEXT ISSUE IN THE TOPIC 

TECHNICAL

Be stored in a Database

1. What Database
2. How does it plug in (reaCT, FIREFLY/)
3. Firefly has its own database, you can query FF database. can't write to it. Postgres Sequel Lite (no SQL ) Create their own data structure and what rights they have. These permissions responsibilities are good for FF's database,  Uses whatever database works for you.
4. Backend app will listen for the event (WebSocket) so when nodes broadcast, that is how backend. can use WebSocket or hooks
5. Frontend....Backend... Databaseplement The database has records that represent the entirety of the event. Store the "NFTS" successful when aLL THREE HASHES ARE BROADCASTED.  The f/u Implentent end compilation of the "NFTS".

Digital Images can be transferred into an NFT, not available in D2R release 1

Token pools -  Feasible to set up a smart contract to mint the NFT after all three pictures are broadcast to the network. The photo gets minted to NFT with the Hash that it creates. We can upload to an infura node.  QR code is a different NFT. How do you prove it ? What is an NFT and where is it useful. Have an asset (digital Twin or Digital assets) who owns it, prove It on-chain.  Transfer event of NFT until it reached the final destination. 1 nft for the donation or an NFT for each digital picture.

Proof of ownership

Pan out - photo linked to QR code and topic. The donor will create the first photo which creates the asset. We could transfer NFT

Dynamic NFT's Chainlink demo - logo changed to show the weather where the physical item was.

How did we get here?  Idea was to prove Providence of the donation but can we also make it proof of ownership. Have QR code on the product - evident in every photo (QR Code). 

Each time NFT transfers, the next photo stores data or hash, we put metadata that is an external pointer as proof of transfer (can look it up) solve for proof of ownership by looking at the flow. NFT has Meta data of transfer time with the matching photo.

The donor has 1 nft (proof of ownership) metadata in NFT that can be associated metadata with a transfer. If I am transferring an nft from me to you we can associate data with that transfer (on chain) Take a photo at step 1, get hash and ipfs address, associate that data with the transfer process. Prove it on the blockchain. Also look up on IPFS, state of thing when it was handed off. View on IPFS and the only NFT is the first on. Transfer - must provide picture at handoff that becomes part of the NFT in the metadata.   Minteing them on IPFS has

Next step for a demo

1. The hopeful token will finish soon and we can build on that. Today we can code * token connector, reference implementation.  Sort thru smart contract. Off the shelf, the solution will meet our needs.  Not use NFT use firefly to upload images and send that data to members grouped into a topic.  We can write that app today and then improve code when NFT capabilities are out. 

DEMO is up and running. Which is the best representative document set up. Create using this link TOKEN CONNECTOR Build a separate app for the token connector. 

 https://github.com/hyperledger-labs/firefly-tokens-erc1155

Option 1 - tokens will be ready let's start building Yes 

Option 2 - build today with what's available. Nah 

The project end date is November 5th, we are willing to work on a token solution.

HOMEWORK
https://github.com/hyperledger-labs/firefly-tokens-erc1155

1. 1155 Ethereum protocol - does it need our needs, we can use the token connector as is.
2. Set up a Monday meeting to regroup!

Great Team work!!!

Agenda 

Brief Presentation

Questions and Answer

9/1 Hardik joined FireFly and mentioned the Bug Fix of Mona. He will incorporate it into their Documentation.

https://github.com/accordproject/hlf-cicero-contract

https://www.meetup.com/Hyperledger-Bangalore/events/280318418/

Business Process definition:
NFT -  How will NFT is transferred correctly _ erc721 contract  (compares photos Before and after)

STEPS one

Contract
Image
Hosting

To Do

Build Interface 

USE Case

Princeton

• Enroll Participants
  The project manager enrolled as an Admin
  Transporter Donors and Recipients enrolled by Admin or directly thru a website 
•  Track Donations
  
  

. 

Enter as a Lab https://labs.hyperledger.org/

Media1.mp4

◦Is available as an instance of Sawtooth chain on a single node (Dev); with the ability to:

◦create key-pairs

◦create assets

◦Transfer assets ( accept or reject the asset)

◦ Explorer , a  view-able tracking of the current holder of the asset from the current front-end interface.

TODO

Create three user interfaces that attach to the backend 

Backend Blockchain that can track giving chain donations from recipient to donor.