As an admin, I want Trust Through Transparency best practices for *Pushed 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:

clarify and make accessible to the end user all Events, even if they are just for developer purposes

Perhaps we could link to the events on etherscan that the bountyindex contract implements in the activyt feed on the bounty detail page.

We'll also want to follow the best practice around 'show a compact versions of the hashes but always show the initial and end parts' and 'always prepend the “0x” to indicate that it’s a hash' and 'allow users to expand the full address/hash ' here

Definition of Done

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

allow users to subscribe-to, unsubscribe-from or temporarily mute certain events

it may make sense to allow a user to 'watch' an issue and receive email updates... or we can link to twitter.com/gitcoinfeed so they can see whats happening