Inspiration
The need to automatically check-in for Kickback: https://gitcoin.co/issue/wearekickback/app/201/3765
What it does
Creates a permanent highly reliable way to provide evidence that you were in a specific location at a specific time.
How I built it
IPFS and Ethereum used to lock an image wit metadata baked into the JPEG file about the location/event and the location it was taken. A Content Identifier (CID) is generated that is a hash of the image w/ metadata that is then locked into a blockchain by the same account as the one associated with a kickback stake. Thus the user also signs a proof that they are the one that took this image and when specifically as proof they should get their kickback stake without the need for any other checkin. In the event of a dispute, this can be used as evidence to reference.
What the picture needs to include:
- A screen at the event that displays:
- A Clock that proves a timestamp
- An event Name
- A time rotating code generated by a 2FA application displayed, cycled every 30 seconds
What an organizer can do to audit:
- Manually verify that the image metadata matches the data on the screen for time and place
- Based on the timestamp they can verify the 2FA code displayed matches what the algorithm produced at this time. this is very very difficult to fake
- Based on the blocktime of the image CID being locked in, they can verify that with some assurance* no one could have communicated this 2FA code to someone to generate a fake image of this remotely
NOTE: this is not fail-safe, but would take a *lot of work to try and curcumvent
Challenges I ran into
Accomplishments that I'm proud of
What I learned
What's next for Proof-of-Attendance plugin for Kickback
Built With
- blockchain
- ethereum
- ipfs
- jpeg
- plug-in
- solidity
- vue
Log in or sign up for Devpost to join the conversation.