search

gridcoin-community / Gridcoin-Tasks

Gridcoin community tasks repository
https://gridcoin.us
MIT License
24 stars 5 forks source link

328 GRC bounty: notify user in the wallet about important issues (new mandatory version, ...) #167

Closed skcin closed 3 years ago

skcin commented 6 years ago

Issue by Erkan-Yilmaz Wednesday Sep 13, 2017 at 10:47 GMT Originally opened as https://github.com/Erkan-Yilmaz/Gridcoin-tasks/issues/161

We've an open issue since 13 months (August 2016) :-(


This is a feature we need with each update/upgrade for Gridcoin:


Current discussed approaches are:

  1. monitoring a burn address
  2. making an "alert"
  3. 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:


The bounty will be paid out to that person that:

  1. sends a merge request to the offical repo that works AND
  2. 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...


Thanks

skcin commented 6 years ago

Comment by Erkan-Yilmaz Wednesday Sep 13, 2017 at 14:08 GMT


grctest commented 6 years ago

monitoring a burn address

If an user is on a fork, they'll never see a transaction hitting this burn address unless it was sent ahead of time (or if the messenger forced themselves to join a forked chain to send the message) - the problem then becomes who would be authorized to send notices to this burn address? A spam problem would likely occur.

making an "alert"

Emergency alerts are already possible, not utilized by Rob (only person capable of doing so).

We could implement something simple like:

If (Difficulty < 0.5) { alert("You may need to upgrade your client!");}

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) :-(

Yeah, let's not implement 'unsafe' functionality if we can avoid it..

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?)

The security of the network is the absolute priority, without it the security of the individual is irrelevant.

If you would like to sponsor this issue, please send your GRCs to address (this resides in my wallet):

I feel that this kind of fundraising is inappropriate and borderline begging. If you desire a feature to be implemented then either program it or fund its development yourself; if you lack both the programming capabilities and the funding to pay devs, then creating a foundation poll within the Gridcoin client as it's the established process for requesting funds to be paid to developers for a feature (rather than requesting users send you funds for a feature which may never be implemented).

tomasbrod commented 6 years ago

My PR https://github.com/gridcoin/Gridcoin-Research/pull/693 applies to this task. #177 would be better, but this is all I got.

jring-o commented 4 years ago

What is going on with this issue?

It will be closed in 7 days if there is no update.

jamescowens commented 4 years ago

@iFoggz is working on a PR that willl address this issue.

barton2526 commented 3 years ago

This is possibly fulfilled with the new update check

jamescowens commented 3 years ago

I believe it has.

towstone commented 3 years ago

Can someone confirm who the bounty should go to? I'd like to see if we can close another one.

towstone commented 3 years ago

Bounty paid: TX ID: 56b549ca8617e7be98e45bc1353081282b59721071ae775b0b5b2d56b0dabca0 TX ID: ddf6c2d00cef29e9a97ed9cf1a64d6e707f48ff652dba8f62e86e4f6afd80bf9 Can this be closed?

jamescowens commented 3 years ago

Yep. Thanks!