10/8
Timeline for Project Completion
Social Impact - 10/26,
Mentorship PresntationPOC - create 3 metamask addresses with the Platform team - we can transfer from
mint it with QR code
broadcast it with QR code (driver can agree to get it then Donor waits for driver and only triggers nft transfer from metamask wallet when the actually good are transferred. Goods transfer, NFT to Drivers wallet, QR code is in back gathering additional metadata. Scan code will ask the user to scan /upload a picture that is stored in metadata. (or put metadata on a chain) transfer then Donor recipient metamask get nft at final transfer.
QR code
Meeting Notes:
Get Specific task:
Budget
Set up Database | |
---|---|
Sql Lite | |
Front end | |
---|---|
Solidity | Task | |
---|---|---|
Open Zepplin | Hard hat framework | |
erc721 | smart-contract method to mint nft's while working on the token connector. -Hardik has the whole contract, working fine, send to group Solidity Provide Set up contracts Token to point to IPFS The mint function takes the address and token id, normally message.sender mint toa dres of person who called function. Ties back to security, limited addresses for minting? or anyone log in with address? The project manager will allow registration Burn mint and check balance, we have every function the erc20 token possesses. Each has own address or group for donors. Counter for minting (id1, d 2, id3 )counter | |
Counterpart | import "@openzeppelin/contracts/token/ERC721/extensions/ERC721URIStorage.sol"; import "@openzeppelin/contracts/utils/Counters.sol"; |
Transaction part
Assignment | Owner | |
---|---|---|
"solidity backend" | smart contract to do minting | Hardik, Mona |
QR Codes | Scanning and formatted | Hardik |
Authentication | set up user authentication (REACT) User Authentication - Nodes registration in ff but we don't want users to have that capability. | |
Database | Low Level, must do but can skip for POC | |
Forms | Auth. and user input data 2. Nodes - donor info form, Driver form, and recipient | |
Donor mints, broadcast, able to supply an address to driver Privately | ||
Front end | using FF we have two request
| Bobbi will try mock-up of forms needed for data collection and minting |
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, | Hardik, Mona |
data type | Ask FF people, reach out to Nicko for good examples JSON types | Mona |
front end forms - independent orgs. Logins login as one of the three, have to check on the roles
* Wireframes? API interactions frontend need minting functionalities, UX UI design secondary to the blockchain. Where do we get mockups and templates for design?
Mint NFT, Broadcast NFT and send private message.
Form Questions to gather front end info. Google Forms can translate to React form and we can use information
Both private and network broadcast, some piece of information open to all and some information available private example - Donors location only for transporter.
https://hyperledger.github.io/firefly/swagger/swagger.html
https://chat.hyperledger.org/channel/firefly
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 |
|
| |
|
| |
|
| |
|
| |
|
| |
10/6
Team meeting to determine Tasks that needs to be completed and who is responsible.
...