Design a dashboard for B.Protocol’s liquidations data

[yaronvel]

Type

Design/ Dashboard

Bounty Prize

$1000 (in USDC over polygon)

Context

• B.Protocol is a liquidation engine for DeFi lending platforms, using user-based backstop liquidity pools to handle liquidations in scale.
• B.Protocol is working on a new dataset that will enable its community and users to follow liquidations made by the protocol across its multi-chain integrations.
• We are looking for a clear and attractive design for the dashboard that will be easy to grasp and follow both for professional users and newbies.

Description

The dashboard should make useful information accessible to end users and lending platforms.
Useful information could include:

1. TVL (amount of deposits) per token
2. Liquidations history
3. Backstop imbalance over time
4. PNL
5. Ratio between backstop size and system debt

The bounty scope is only for the graphical design. The implementation and data collection will be done separately.

Links that could help the bounty participant

The dune analytic dashboard by Liquity is an elegant example for how statistical data is made accessible.

[gitcoinbot]

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

---

This issue now has a funding of 1000.0 USDC (1000.0 USD @ $1.0/USDC) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin's Discord
• $5,172,740.73 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

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

---

Work has been started.

These users each claimed they can complete the work by 5 months, 2 weeks ago.
Please review their action plans below:

1) 0xkylin has started work.

I will create a dashboard as per the instructions.
2) wakilahmadomary has started work.

Hello, Dear
I would like to work on your project. I have developed several React apps, Nextjs and worked on some of dapp frontends and dashboard.
My action plan, if I am chosen for this task would be as follows:

• Create wireframes on Figma or any other design tools. and share a link, where we can communicate feedback and decide on the design.
• After the wireframes are approved, start developing a React application.
• Host the web app where ever the team asks for.
• After work is finished and the team is satisfied, provide all the payment details and get the bounty :)
  3) manapixels has started work.

Streamlined existing design with data requested (the Medium articles were really well written! A lot of new concepts, but I managed to get a brief understand of how the backstop works and what is required. If I misunderstood something and got something wrongly translated to the UI, let me know. More than willing to work with the team to get things iterated :)
4) lessthen-eth has started work.

I will design a user interface for B.protocol liquidation dashboard
5) imanueljnr has started work.

I will design the dashboard, UI elements and kits for B.Protocol
6) juanuxui has started work.

Design A Dashboard For B.Protocol’s Liquidations Data
7) barszczewskii has started work.

Will submit a liquity analytics dashboard, composed in figma with specific attention payed toward source material and currently existing pages.

Learn more on the Gitcoin Issue Details page.

[gitcoinbot]

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

---

Work for 1000.0 USDC (1000.0 USD @ $1.0/USDC) has been submitted by:

1. @sholance
2. @manapixels
3. @frizly
4. @wakilahmadomary
5. @shelabh
6. @barszczewskii

@yaronvel please take a look at the submitted work:

• PR by @barszczewskii
• PR by @shelabh
• PR by @WakilAhmadOmary
• PR by @frizly
• PR by @manapixels
• PR by @sholance

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin's Discord
• $4,584,604.47 more funded OSS Work available on the Gitcoin Issue Explorer

[tonybarski]

Any status on the review process?

[WakilAhmadOmary]

I glad to receiving this Email. What should I do?

…

On Sun, Mar 27, 2022, 11:20 PM barszczewskii ***@***.***> wrote: Any status on the review process? — Reply to this email directly, view it on GitHub <#42 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXW6HFFLLFCHXJ2NCUZY6P3VCCUWBANCNFSM5PHXVCBA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[WakilAhmadOmary]

Please send me the result On Mon, Mar 28, 2022, 3:53 PM Wakil Ahmad omari ***@***.***> wrote:

…

I glad to receiving this Email. What should I do? On Sun, Mar 27, 2022, 11:20 PM barszczewskii ***@***.***> wrote: > Any status on the review process? > > — > Reply to this email directly, view it on GitHub > <#42 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AXW6HFFLLFCHXJ2NCUZY6P3VCCUWBANCNFSM5PHXVCBA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[WakilAhmadOmary]

What's going on? On Mon, Mar 28, 2022, 9:13 PM Wakil Ahmad omari ***@***.***> wrote:

…

Please send me the result On Mon, Mar 28, 2022, 3:53 PM Wakil Ahmad omari ***@***.***> wrote: > I glad to receiving this Email. > > What should I do? > > > On Sun, Mar 27, 2022, 11:20 PM barszczewskii ***@***.***> > wrote: > >> Any status on the review process? >> >> — >> Reply to this email directly, view it on GitHub >> <#42 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AXW6HFFLLFCHXJ2NCUZY6P3VCCUWBANCNFSM5PHXVCBA> >> . >> You are receiving this because you were mentioned.Message ID: >> ***@***.***> >> >

[WakilAhmadOmar]

Hello On Mon, Mar 28, 2022, 9:14 PM WakilAhmadOmary ***@***.***> wrote:

…

Please send me the result On Mon, Mar 28, 2022, 3:53 PM Wakil Ahmad omari ***@***.***> wrote: > I glad to receiving this Email. > > What should I do? > > > On Sun, Mar 27, 2022, 11:20 PM barszczewskii ***@***.***> > wrote: > >> Any status on the review process? >> >> — >> Reply to this email directly, view it on GitHub >> < #42 (comment) >, >> or unsubscribe >> < https://github.com/notifications/unsubscribe-auth/AXW6HFFLLFCHXJ2NCUZY6P3VCCUWBANCNFSM5PHXVCBA > >> . >> You are receiving this because you were mentioned.Message ID: >> ***@***.***> >> > — Reply to this email directly, view it on GitHub <#42 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AND6DJ56TICIRHNOGNVFODDVCHOUZANCNFSM5PHXVCBA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>