search

windingtree / wt-hackathon

WT Hackathon repository
https://windingtree.com/hacktravel-london-2019
11 stars 27 forks source link

WT Hackathon #1 Prizes #13

Closed AugustoL closed 5 years ago

AugustoL commented 5 years ago

25 ETH will be distributed among teams, 4 teams that submitted their hacks on time and followed the rules will be selected by the judges.

4 Prizes of 5 ETH to the selected team by judges. 1 Prize of 5 ETH to a team chosen by the public.

gitcoinbot commented 5 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 25.0 ETH (5157.54 USD @ $206.3/ETH) attached to it as part of the Winding Tree fund.

gitcoinbot commented 5 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work has been started.

These users each claimed they can complete the work by 4 months, 1 week ago. Please review their action plans below:

1) vignesh17 has started work.

What is the base for this hackathon? Is there a theme for the proposal of the project? Can we choose the team mates?

Learn more on the Gitcoin Issue Details page.

2) ligi has started work.

Write code leveraging the liquidity.network to make paying for accommodation supplements more pleasant.

Learn more on the Gitcoin Issue Details page.

3) ianjianliang has started work.

Integration of Trabble's ChatBot with Winding Tree's repository, enabling automation of booking and payments seamlessly through chat, without any need for technical development.

Learn more on the Gitcoin Issue Details page.

4) umerrasheed has started work.

Wipu Hotel Cross-Sell. A person is trying book a hotel on Winding Tree for their next trip. As they are a typical busy entrepreneur, they multitasking, say … parking their car. Preferred hotel isn’t available, so user has to go back & manually search again to find affiliated partners. Result: Lots of back-and-forth, customer frustration, waste of time, distraction (can’t park).

Solutions: Hotel Cross-Sell support on top of WT

Learn more on the Gitcoin Issue Details page.

5) skylarweaver has started work.

WT-Hackathon-Emergency-Shelter WindingTree Hackathon in Prague Oct 24th-25th, 2018.

Team Name: Emergency Shelter Team Members: Dennison Bertram - dennison@dennisonbertram.com (github: crazyrabbitLTC) Skylar Weaver - weaver.skylar@gmail.com (github: skylarweaver)

Project Description: Across the world, the increasing frequency and intensity of natural and human made disasters in the form of SuperStorms, Earthquakes and war means an increasing number of people are left homeless and in urgent need of emergency shelter.

Problem: While emergency organizations try to address the most dire of circumstances, they are frequently resource stretched and unable to meet every emergency housing crises on the globe.

By leveraging the Winding Tree Hotel index, Emergency Shelter seeks to tap into a global pool of volunteers willing to open their doors to assist those in need and solve the problem of emergency housing in emergency situations.

Solution: Emergency Shelter is a meta-contract building on-top of the WindingTree Hotel Index. Currently the WindingTree hotel index deploys new instances of Hotel Contracts, complete with a manager address and URI for the data feed. The Emergency shelter Contract takes a novel approach by calling the WindingTree Hotel index to create a new hotel contract instance which is managed, rather than by a "manager" by the Emergency Shelter contract itself.

By doing so, Emergency Shelter creates "Hotel Instances" to represent emergencies, abtrascting the scope of an entire emergency under one "Hotel Instance" to be indexed and returned by the WindingTree API. Volunteers then submit "Shelters" directly to the Emergency Shelter contract which registeres and associates each "shelter" by "emergency".

This nature of this abstraction keeps the WindingTree Hotel Index uncluttered while centralizing Emergency offerings and solving several unique challanges:

Emergency "Shelter" accomodations will rarely, if ever, be submitted with metadata that meets the standards of the WindingTree Hotel Index: Shelters will rarely include more than a simple contact info and basic description- no photos, amenities, or swimming pool offerings.

WindingTree Hotel Index assumes that the hotel manager (the ETH responsible for managing the deployed Hotel Contract) will be an interested and motivated manager. With Emergency Shelter, this job is delegated to the manager of the "Emergency" which will most likely be an interested and motivated individual or Aid organization. In the Hotel Contract URI the "Emergency Manager" can keep relevant information up-to-date in a centrazlied format regarding emergency.

Following on that, when associating shelters by emergency, the emergency manager can remove from the WindingTree Hotel Index ALL of the availible shelters at the end of an emergency by simply deleting the associated Hotel Contract. As it is the nature of emergencies that individauls feel highly motivated at the outset but then lose interest as time goes on, if individuals were to directly register their shelter with the WindingTree Hotel index, the majority would most likely fail to delete their listing at the end of an emergency which would result in polution of the Hotel Index by zombie listings which would be impossible to delete,alter or manage.

Difficulties: In the process of developing the Emergency Shelter smart contract, we discovered an problem and suggested a solution to the WindingTree Team. As currently written, the WT-Index contract does not return the address of a Hotel Contract once createn, meaning there is not a secure way to programatically be sure at creation time, the address of the hotel created. This is important to fully implement the functionality of deleting a Hotel Instance contract from the WindingTree Database, in this case, when an emergency has passed, as the smart contract is not aware of the address of the Hotel Contract that it directly manages.

What we Learned: To create Emergency-Shelter required diving into the WindingTree contracts to understand the shape and format of WindingTree's database. We learned the way in which WindingTree is organized and have some suggestions as to how the system usability and security can be improved. In particualar it would be very helpful in our opinion if WindingTree expands support for 3rd party solidity contracts that can interact with the core WindingTree contract base. This would open up many possiblites for a richer more dynamic smart-contract controlled travel ecosystem.

Notes: Ropsten Deployment of WindingTree Contracts: 0x933198455e38925bccb4bfe9fb59bac31d00b4d3 (For deployment of EmergencyShelter Contract)

Learn more on the Gitcoin Issue Details page.

6) afklblockchain has started work.

AFKL Blockchain on airline integration

Learn more on the Gitcoin Issue Details page.

7) wurducius has started work.

no time xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Learn more on the Gitcoin Issue Details page.

8) crazyrabbitltc has started work.

WT-Hackathon-Emergency-Shelter

WindingTree Hackathon in Prague Oct 24th-25th, 2018.

Team Name: Emergency Shelter

Team Members:

Dennison Bertram - dennison@dennisonbertram.com (github: crazyrabbitLTC) Skylar Weaver - weaver.skylar@gmail.com (github: skylarweaver)

Project Description:

Across the world, the increasing frequency and intensity of natural and human made disasters in the form of SuperStorms, Earthquakes and war means an increasing number of people are left homeless and in urgent need of emergency shelter.

Problem:

While emergency organizations try to address the most dire of circumstances, they are frequently resource stretched and unable to meet every emergency housing crises on the globe.

By leveraging the Winding Tree Hotel index, Emergency Shelter seeks to tap into a global pool of volunteers willing to open their doors to assist those in need and solve the problem of emergency housing in emergency situations.

Solution:

Emergency Shelter is a meta-contract building on-top of the WindingTree Hotel Index. Currently the WindingTree hotel index deploys new instances of Hotel Contracts, complete with a manager address and URI for the data feed. The Emergency shelter Contract takes a novel approach by calling the WindingTree Hotel index to create a new hotel contract instance which is managed, rather than by a "manager" by the Emergency Shelter contract itself.

By doing so, Emergency Shelter creates "Hotel Instances" to represent emergencies, abtrascting the scope of an entire emergency under one "Hotel Instance" to be indexed and returned by the WindingTree API. Volunteers then submit "Shelters" directly to the Emergency Shelter contract which registeres and associates each "shelter" by "emergency".

This nature of this abstraction keeps the WindingTree Hotel Index uncluttered while centralizing Emergency offerings and solving several unique challanges:

Emergency "Shelter" accomodations will rarely, if ever, be submitted with metadata that meets the standards of the WindingTree Hotel Index: Shelters will rarely include more than a simple contact info and basic description- no photos, amenities, or swimming pool offerings.

WindingTree Hotel Index assumes that the hotel manager (the ETH responsible for managing the deployed Hotel Contract) will be an interested and motivated manager. With Emergency Shelter, this job is delegated to the manager of the "Emergency" which will most likely be an interested and motivated individual or Aid organization. In the Hotel Contract URI the "Emergency Manager" can keep relevant information up-to-date in a centrazlied format regarding emergency.

Following on that, when associating shelters by emergency, the emergency manager can remove from the WindingTree Hotel Index ALL of the availible shelters at the end of an emergency by simply deleting the associated Hotel Contract. As it is the nature of emergencies that individauls feel highly motivated at the outset but then lose interest as time goes on, if individuals were to directly register their shelter with the WindingTree Hotel index, the majority would most likely fail to delete their listing at the end of an emergency which would result in polution of the Hotel Index by zombie listings which would be impossible to delete,alter or manage.

Difficulties:

In the process of developing the Emergency Shelter smart contract, we discovered an problem and suggested a solution to the WindingTree Team. As currently written, the WT-Index contract does not return the address of a Hotel Contract once createn, meaning there is not a secure way to programatically be sure at creation time, the address of the hotel created. This is important to fully implement the functionality of deleting a Hotel Instance contract from the WindingTree Database, in this case, when an emergency has passed, as the smart contract is not aware of the address of the Hotel Contract that it directly manages.

What we Learned:

To create Emergency-Shelter required diving into the WindingTree contracts to understand the shape and format of WindingTree's database. We learned the way in which WindingTree is organized and have some suggestions as to how the system usability and security can be improved. In particualar it would be very helpful in our opinion if WindingTree expands support for 3rd party solidity contracts that can interact with the core WindingTree contract base. This would open up many possiblites for a richer more dynamic smart-contract controlled travel ecosystem.

Notes:

Ropsten Deployment of WindingTree Contracts: 0x933198455e38925bccb4bfe9fb59bac31d00b4d3 (For deployment of EmergencyShelter Contract)

Presentation Slides:

https://github.com/crazyrabbitLTC/WT-Hackathon-Emergency-Shelter/blob/master/WT-HACKATHON.pdf

Learn more on the Gitcoin Issue Details page.

9) mccallofthewild has started work.

I will participate in the hackathon to the best of my ability

Learn more on the Gitcoin Issue Details page.

10) ftc95 has started work.

I will utilize my programming and problem solving skills to solve the issues.

Learn more on the Gitcoin Issue Details page.

11) omidmahboubian has started work.

done. (https://github.com/crazyrabbitLTC/WT-Hackathon-Emergency-Shelter)

Learn more on the Gitcoin Issue Details page.

AugustoL commented 5 years ago

@afklblockchain @ligi @wurducius @skylarweaver can you submit your work on gitcoin and I can send you your prizes?

You can see how to do it here: https://gitcoin.co/how/contributor

gitcoinbot commented 5 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 25.0 ETH (5381.92 USD @ $215.28/ETH) has been submitted by:

  1. @wurducius
  2. @crazyrabbitLTC
  3. @afklblockchain
  4. @omidmahboubian

@AugustoL please take a look at the submitted work:

AugustoL commented 5 years ago

@ligi @afklblockchain @wurducius @skylarweaver I can't make the payment till the bug https://github.com/gitcoinco/web/issues/2840 is fixed

gitcoinbot commented 5 years ago

⚡️ A tip worth 10.00000 ETH (1810.24 USD @ $181.02/ETH) has been granted to @skylarweaver for this issue from @AugustoL. ⚡️

Nice work @skylarweaver! Your tip has automatically been deposited in the ETH address we have on file.

gitcoinbot commented 5 years ago

⚡️ A tip worth 5.00000 ETH (905.12 USD @ $181.02/ETH) has been granted to @afklblockchain for this issue from @AugustoL. ⚡️

Nice work @afklblockchain! To redeem your tip, login to Gitcoin at https://gitcoin.co/explorer and select 'Claim Tip' from dropdown menu in the top right, or check your email for a link to the tip redemption page.

gitcoinbot commented 5 years ago

⚡️ A tip worth 5.00000 ETH (905.12 USD @ $181.02/ETH) has been granted to @ligi for this issue from @AugustoL. ⚡️

Nice work @ligi! Your tip has automatically been deposited in the ETH address we have on file.

gitcoinbot commented 5 years ago

⚡️ A tip worth 5.00000 ETH (905.12 USD @ $181.02/ETH) has been granted to @wurducius for this issue from @AugustoL. ⚡️

Nice work @wurducius! Your tip has automatically been deposited in the ETH address we have on file.

gitcoinbot commented 5 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

The funding of 25.0 ETH (4525.6 USD @ $181.02/ETH) attached to this issue has been approved & issued.

AugustoL commented 5 years ago

@ligi @afklblockchain @wurducius @skylarweaver payments done, thx for the hacks! see you next hackathon!