We've an open issue in the bugtracker since 13 months (August 2016) :-(
This is a feature we need with each update/upgrade for Gridcoin:
- currently we do this - manually - over the existing communication media, but:
- this is slow
- may not reach everyone
Current discussed approaches are:
- monitoring a burn address
- making an "alert"
- in case none of the mentioned/coming ideas work:
- think about an option that is "unsafe" but works (e.g. activate in options, but tells clearly: "some of your data may leak for this feature to work correctly" or so) :-(
If you would like to sponsor this issue, please send your GRCs to address (this resides in my wallet):
As public sponsor your name will be listed in all related announcements:
- e.g. you could also come to IRC and tell me in private beforehand how much you will donate, it might be hard to get your details otherwise. My IRC nick is: Erkan_Yilmaz
- You can of course also donate anonymously.
Current sponsors:
- 150 GRC (by
)
- 100 GRC anonymous donation
- 78.04 GRC (by @tomasbrod)
The bounty will be paid out to that person that:
- sends a merge request to the offical repo that works AND
- is implemented in Gridcoin also:
- about 2.: e.g. option3 ("unsafe impl.") above might not be accepted?
- needs discussion: security of network vs. security of individual (personally, "security of individual" is more important to me: I added option3 only so we can "move forward" with the issue. Also, I link to the fork warning which seems so far to prevent the issue going forward?)
- if option3 would be selected: after discussion also needs voting on community? but if it is per default off AND gives user clear info about consequences when enabling: then probably not...
More bounties for Gridcoin can be found here.
Originally posted here.
Erkan (find me on IRC and twitter)
