As an admin, I want Trust Through Transparency best practices for *Writing Data* implemented at Gitcoin, so I can be sure that users can trust our site.

[owocki]

Refers

Web3 Design Principles

See Also

#796
#797
#798
#799
#800
#801

How to Implement here:

I think that the following best practices can / should be implemented at Gitcoin:

[Permanence] clarify actions that are irreversible

the most irreversable action on gitcoin is the bounty payout.. so we could maybe put some sort of UI element here that signifies that

[Value] clarify actions that involve money or value

This is important for example when a user submits their ETH /tokens to the blockchain at gitcoin.co/new or when they pay out the submission

[Privacy] clarify actions that could potentially lead to user identification

This is important for example when a user submits their email address to the blockchain at gitcoin.co/new

clarify suggested values for gas price and how to overwrite the Tx (∞link 9.Gas Price and Transaction Reversals)

we already mostly do this.. yay!

manage Transaction wait time (∞link > 6.Time/Wait Management)

we already mostly do this.. yay!

Definition of Done

The above 4 best practices are implemented in a way that makes sense for Gitcoin. Pls allow for 1-2 rounds of feedback on designs before moving into implementation / coding.

[gitcoinbot]

This issue now has a funding of 0.251 ETH (95.65 USD @ $381.06/ETH) attached to it.

• If you would like to work on this issue you can claim it here.
• If you've completed this issue and want to claim the bounty you can do so here
• Questions? Get help on the Gitcoin Slack
• $2484.56 more Funded OSS Work Available at: https://gitcoin.co/explorer

[gitcoinbot]

Work has been started on the 0.251 ETH (121.98 USD @ $485.98/ETH) funding by:

1. @john-brunelle

Please work together and coordinate delivery of the issue scope. Gitcoin doesn't know enough about everyones skillsets / free time to say who should work on what, but we trust that the community is smart and well-intentioned enough to work together. As a general rule; if you start work first, youll be at the top of the above list ^^, and should have 'dibs' as long as you follow through.

On the above list? Please leave a comment to let the funder (@owocki) and the other parties involved what you're working, with respect to this issue and your plans to resolve it. If you don't leave a comment, the funder may expire your submission at their discretion.

• Learn more on the gitcoin issue page
• Questions? Get help on the Gitcoin Slack
• $3170.49 more Funded OSS Work Available at: https://gitcoin.co/explorer

[gitcoinbot]

@andylim99 are you still working on this issue?

[gitcoinbot]

@andylim99 are you still working on this issue?

[gitcoinbot]

@andylim99 are you still working on this issue?

[gitcoinbot]

@andylim99 are you still working on this issue?

• warning 1 (3 days)
• warning 2 (6 days)
• auto removal (10 days)

[owocki]

removing bounty hunter from this issue due to non-responsiveness

[ConnorChristie]

@owocki Are you still looking for someone to work on this?

[owocki]

yessir

[pmespresso]

Would love to take this on. @ConnorChristie down to coordinate/cooperate?

[gitcoinbot]

@rav8815 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• warning (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

Issue Status: 1. Open 2. Expired

---

The funding of 0.251 ETH (131.09 USD @ $522.28/ETH) attached to this issue has been cancelled by the bounty submitter

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $24,843.83 more funded OSS Work available on the Gitcoin Issue Explorer