...
...
Determine next steps:
*Strikethrough indicates Completion of Task
10/12
GET Developers STARTED: Firefly creates a signing address on the bc for you. Not on Mainnet, on our FF instance.
Issues for Developers |
---|
Assignment | Owner | Comments |
Database issues | Postgres or sequel lite, |
|
| leverage your API |
|
| Create Token pool for NFT |
create P[RESENTATIONScreate the Platform team - we can transfer from mint it with QR code |
| QR code |
|
Front end | POC hosting each node on a tab . Donor tab | Registration, Donor Transporter Recipient Page |
| Solidity | pLocal -private ipfs upload, Docker named volume no server ff start, same data will be there. ff reset of ff remove will clear out data. |
---|
Token Connector |
| token or requests of firefly endpoint to retrieve date |
erc721 Change how we mint nft : Not using FF creates post requests to create the data, get back data-id that will reference image (w/in ff) the reference is what we will use. I'm Local stack in the private IPFS | smart-contract method to mint nft's | Set up contracts Token to point to IPFS, Use Firefly IPfs, upload file to ff, it will put it on IPFS, OPen to Giving chain consortium 9 HASH IPFS and w/ HTTP or FF API CIDHAsh of content identifier, the value returned might be hash returned in code or in data table in FF database and keep track of all data items. We need a way to link back to the image. If we feed is into the solidity contract, would we need URL of where the image is hosted. URL each member GE IS HOSTED. NFT will get minted with ID of Image |
Authentication
|
| set up user authentication (REACT) User Authentication - Nodes registration in ff but we don't want users to have that capability. |
|
| ff is private not using public, means with in-network, Public doesn't mean public to the entire world.n |
Forms
|
| Auth. and user input data
1.(register usr name, donation address)
2. Nodes - donor info form, Driver form, and recipient
|
Broadcast | Both private and network broadcast, some piece of information open to all and some information available private example - Donors location only for transporter. |
Donor mints, broadcast, able to supply an address to driver Privately |
Creation of Datatype |
| Data type, play with API. FF's blockchain network lets you create data type, fill out info about the data type. Every time we make a donation |
test run |
| interact with stack, show screenshots, |
data type |
| Ask FF people, reach out to Nicko for good examples JSON types |
Issues for Developers
The FireFly project focusses focuses on: | Task |
- Providing a great developer API and experience
| - CLI to get you running in minutes
- Explorer UI as first class project component
- APIs that abstract hard constructs into simple actions
- REST APIs for your private history of participation in the network
- Events built for web and microservice developers
|
- Pluggability for implementations of multi-party system infrastructure
| - Blockchains, off-chain data exchange, identity, compute etc.
- Microservice runtime architecture, embracing a variety of tech stacks
|
- Making proven multi-party system patterns easy for new projects to adopt
| - On-chain/off-chain coordination
- Multi-party business processes
- Tokens - NFTs, value transfer, and common trade patterns like atomic swaps
|
- Providing developer friendly access to custom transactions+events in the underlying platforms
| - Easy submission of transactions
- Reliable access to events
- Plugins customized to each blockchain protocol: Fabric, Ethereum, Corda
|
- Visibility and control on the flow of data a multi-party system
| - Network map backed by pluggable identity
- Private audit of participation in a local pluggable database
- Easy pinning of proofs on data exchange to the blockchain
|
...
Timeline for Project Completion
Social Impact - 10/26,
Mentorship Presentation
November 17th at 5 pm CET (11 am EST).
The FireFly project focusses on: | Task | Completed |
- Providing a great developer API and experience
| - CLI to get you running in minutes
- Explorer UI as first class project component
- APIs that abstract hard constructs into simple actions
- REST APIs for your private history of participation in the network
- Events built for web and microservice developers
|
|
- Pluggability for implementations of multi-party system infrastructure
| - Blockchains, off-chain data exchange, identity, compute etc.
- Microservice runtime architecture, embracing a variety of tech stacks
|
|
- Making proven multi-party system patterns easy for new projects to adopt
| - On-chain/off-chain coordination
- Multi-party business processes
- Tokens - NFTs, value transfer, and common trade patterns like atomic swaps
|
|
- Providing developer friendly access to custom transactions+events in the underlying platforms
| - Easy submission of transactions
- Reliable access to events
- Plugins customized to each blockchain protocol: Fabric, Ethereum, Corda
|
|
- Visibility and control on the flow of data a multi-party system
| - Network map backed by pluggable identity
- Private audit of participation in a local pluggable database
- Easy pinning of proofs on data exchange to the blockchain
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
...