Inspiration
Charlize is inspired by a reagent expiration date real-world problem faced by a medical research lab in NYC I collaborate with. Those labs manage at the same time hundreds of reagents from different providers, and their expiration dates go from several months up to three years. Procurement information systems are more focused on their acquisition, and how reagents are managed after that is up to each laboratory. Regulatory agencies exercise control of expiration dates through inspections. Even though automating the expiration date management is essential, the process needs to be trustable for auditing purposes, and it implies not relying on a single centralized point of truth.
What it does
Charlize manages expiration dates of reagents in a decentralized way
How we built it
I used a combination of Remix, Hardhat, Chanlink keeper, Moralis tools, and openzeppeling contracts
Challenges we ran into
Setup of the oracle keeper, and the frontend infrastructure I chose in this case Moralis
Accomplishments that we're proud of
The configuration of the keeper, even though simple it is very powerful, and the strategy applied to reduce gas in storage and operations using logs in combination with the frontend application
What we learned
I learned about oracles, Hardhat and Moralis, ReactJS hooks.
What's next for Juan Calderon
I would like to build applications involving ERC 721 and ERC 1155, go deeper in code auditing and build L2 apps
Built With
- chainlink
- hardhat
- javascript
- metamask
- moralis
- react
Log in or sign up for Devpost to join the conversation.