Open zherring opened 4 years ago
gitcoinbot
commented
4 years ago Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 0.001 ETH (0.15 USD @ $147.72/ETH) attached to it.
gitcoinbot
commented
4 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 2 years, 2 months ago. Please review their action plans below:
1) viraja1 has started work.
Will work on UX + Open Finance Experimentation 2) owans has started work.
Working on prototypes for UX & open finance 3) man-jain has started work.
Will put up an easy ux for defi work 4) pakokrew has started work.
Mooni is a simple solution for end-users, marketplaces or DAOs to cash out cryptos in fiat directly to a bank account. 5) kadenzipfel has started work.
I will create a protocol to easily insure user's defi positions.
Learn more on the Gitcoin Issue Details page.
gitcoinbot
commented
4 years ago Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work for 0.001 ETH (0.12 USD @ $121.41/ETH) has been submitted by:
@connoroday please take a look at the submitted work:
gitcoinbot
commented
4 years ago Issue Status: 1. Open 2. Cancelled
The funding of 0.001 ETH (0.13 USD @ $127.78/ETH) attached to this issue has been cancelled by the bounty submitter
gitcoinbot
commented
4 years ago ⚡️ A tip worth 15.00000 DAI (15.0 USD @ $1.0/DAI) has been granted to @man-jain for this issue from @connoroday. ⚡️
Nice work @man-jain! Your tip has automatically been deposited in the ETH address we have on file.
gitcoinbot
commented
4 years ago ⚡️ A tip worth 15.00000 DAI (15.0 USD @ $1.0/DAI) has been granted to @kadenzipfel for this issue from @connoroday. ⚡️
Nice work @kadenzipfel! Your tip has automatically been deposited in the ETH address we have on file.
gitcoinbot
commented
4 years ago ⚡️ A tip worth 15.00000 DAI (15.0 USD @ $1.0/DAI) has been granted to @owans for this issue from @connoroday. ⚡️
Nice work @owans! Your tip has automatically been deposited in the ETH address we have on file.
gitcoinbot
commented
4 years ago ⚡️ A tip worth 15.00000 DAI (15.0 USD @ $1.0/DAI) has been granted to @viraja1 for this issue from @connoroday. ⚡️
Nice work @viraja1! Your tip has automatically been deposited in the ETH address we have on file.
gitcoinbot
commented
4 years ago ⚡️ A tip worth 15.00000 DAI (15.0 USD @ $1.0/DAI) has been granted to @owans for this issue from @connoroday. ⚡️
Nice work @owans! Your tip has automatically been deposited in the ETH address we have on file.
Important Update
The Submission Form is now live! Subit your UX Experiment
About This Bounty
Open Finance is, by definition, open to everyone. It’s an opt-in economy, and the potential only grows as more people discover use, and store value in the Ethereum network. It’s an exciting tool for freedom at a time of global instability. The biggest hurdle for Open Finance, ultimately, is that it isn’t very usable for normal people. Change starts with experimentation, exploration, and research, and that’s why we’re funding this design exploration prompt.
Challenge
This isn’t meant to be bullet-proof solutions. We want to reward rapid experimentation and creative thinking. These should be out-of-the-box creative experiments that solve some of the stickiest, clunkiest problems within Open Finance. Problems like…
Splitting payouts across multiple ETH addresses
Handling multiple, asynchronous transactions
Event-handling for failed transactions
Unclear token swapping patterns
Failed transaction patterns
This is a choose your own adventure prompt: Whatever interactions that explain not just the immediate actions being taken, but the why, and how
We’re looking for creative explorations of what’s possible building on Ethereum. Motion prototypes, codepens, wireframes, etc. We’re not asking for production-ready code, or super-polished designs (although those couldn’t hurt). Get creative, have fun, and explore what’s possible with Open Finance.
The Format
Each submission should come with two components. 1. The Problem Statement It won’t be self-evident the problem that you’re solving, in most cases. You need to come with a fully-formed idea of what the problem is that you’re solving and why it’s important to solve it. Words, screen-shots, even diagrams; help us understand what you’re solving and /why/ it’s important.
2. The Solution Self-explanatory. We encourage participants to submit writing, sketches, UI designs, and/or prototypes in any form. Everyone is welcome to submit a solution to the prompt, regardless of fidelity or technical implementation.
Example
The Problem Splitting a payment between multiple addresses is tedious and difficult in most wallet settings today.
The Solution Figma Clickable Link
Evaluation Criteria
Submissions will be evaluated based on the following criteria: Novelty: Does this pattern provide a new or improved approach? Usability: Can we expect users to accomplish the desired task? Flexibility: Can this pattern be applied to a wide range of applications? Implementation / Fidelity: How much time and effort went in to the submission? How thorough is the exploration of the problem and how impressive is the execution and presentation of the solution?
Token(s) of Appreciation
The Bounties and Rimble teams will be judging each submission based on the evaluation criteria throughout the week to determine which submissions will be accepted and/or might be eligible for additional prizes.
The top 10 entries get 15 DAI token of appreciate. We wish we could give everyone something, but have to cap the budget somewhere.
Everyone gets the “Designing the Future” NFT we had especially minted for this Hackathon.
Eligibility for the UX Best-in-Show Bounty
Projects pushed beyond the experiment phase listed above are eligible to submit to the UX Best-in-Show bounty (7ETH).
UX Project submitting to the Best-in-Show need to meet the following criteria to be considered…
1. Documentation Thorough documentation of problem statements, existing solutions, and edge cases. 2. Research Usability tests with target DeFi user base - these sessions should be recorded, with high-level summaries included noting the research impacted the final solution. 3. Portability These solutions need to be flexible and work within multiple contexts (mobile, desktop). Bonus points if you collaborate with an engineer to make it a web component.