Bitcoin Forum
May 12, 2024, 07:46:22 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Universal Warning System  (Read 1353 times)
dave111223 (OP)
Legendary
*
Offline Offline

Activity: 1190
Merit: 1001


View Profile WWW
March 13, 2013, 12:32:16 PM
Last edit: March 13, 2013, 01:09:59 PM by dave111223
 #1

I think there should be some kind of universal warning system which broadcasts emergency warnings such as the recent blockchain fork.

How it could work:

1) Have a domain setup with simple JSON service with a few simple fields such as, alert status, alert message, more info link
2) A small select/vetted number of developers and community members would have access to update the status/alert message
3) Bitcoin client software could be coded to the check the warning system and show alerts.

Something like this:


For example I use Electrum, I received some bitcoins right around the time of the fork, in Electrum it was showing 6+ confirms, so I transferred out some money to the sender.  When I later heard about the fork and potential double spends on transactions with less than 11+ confirms I just about shit myself.  Luckily there was no double spend, but we can't really expect all users, merchants etc...to be constantly monitoring the forums and IRC to know whether they should trust the confirmed transactions in their wallets.

I think the main argument against this might be "What if the alert system got hacked or abused"....well at the end of the day what's the worst that could happen?  Users see a "See sexy p0rn click here" type of message for a few hours?  But if you compare this risk, to the risk of users being totally unaware of major network issue; I'd prefer to have the warning system.

If I get some feed back that people think this could be a good idea, and some devs would consider integrating it I'd be happy to setup and maintain the warning service.
1715543182
Hero Member
*
Offline Offline

Posts: 1715543182

View Profile Personal Message (Offline)

Ignore
1715543182
Reply with quote  #2

1715543182
Report to moderator
1715543182
Hero Member
*
Offline Offline

Posts: 1715543182

View Profile Personal Message (Offline)

Ignore
1715543182
Reply with quote  #2

1715543182
Report to moderator
1715543182
Hero Member
*
Offline Offline

Posts: 1715543182

View Profile Personal Message (Offline)

Ignore
1715543182
Reply with quote  #2

1715543182
Report to moderator
Even if you use Bitcoin through Tor, the way transactions are handled by the network makes anonymity difficult to achieve. Do not expect your transactions to be anonymous unless you really know what you're doing.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715543182
Hero Member
*
Offline Offline

Posts: 1715543182

View Profile Personal Message (Offline)

Ignore
1715543182
Reply with quote  #2

1715543182
Report to moderator
gyverlb
Hero Member
*****
Offline Offline

Activity: 896
Merit: 1000



View Profile
March 13, 2013, 12:38:17 PM
 #2

Just propagate the message broadcasted on the Bitcoin network to lightweight clients too (Bitcoin-qt displayed a warning about the network split when it happened).

I suppose it's only a matter of adding the public key used for such messages to Electrum and add support for these broadcasts in the Electrum<->Electrum server protocol.

P2pool tuning guide
Trade BTC for €/$ at bitcoin.de (referral), it's cheaper and faster (acts as escrow and lets the buyers do bank transfers).
Tip: 17bdPfKXXvr7zETKRkPG14dEjfgBt5k2dd
K1773R
Legendary
*
Offline Offline

Activity: 1792
Merit: 1008


/dev/null


View Profile
March 13, 2013, 12:41:48 PM
 #3

Just propagate the message broadcasted on the Bitcoin network to lightweight clients too (Bitcoin-qt displayed a warning about the network split when it happened).

I suppose it's only a matter of adding the public key used for such messages to Electrum and add support for these broadcasts in the Electrum<->Electrum server protocol.
well it took some time until gavin did it and another ~15 until ppl saw it

[GPG Public Key]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
dave111223 (OP)
Legendary
*
Offline Offline

Activity: 1190
Merit: 1001


View Profile WWW
March 13, 2013, 12:48:05 PM
 #4

If the message is broadcast across the bitcoin network itself then doesn't it run the risk that if the network is misbehaving then the message may never arrive?

It's kind of like twitter tweeting that their network is down...(ie no one is going to see the tweet anyway)?
flyingkiwiguy
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 17, 2013, 04:01:37 PM
 #5

I think there should be some kind of universal warning system which broadcasts emergency warnings such as the recent blockchain fork.

There is. See https://en.bitcoin.it/wiki/Alerts

However you need to be running a Bitcoin client that will accept and publish the alert. Since not everyone all the time is running such a client I just implemented an email relay service:

https://en.bitcoin.it/wiki/Alerts_mailing_list

Regards,
Gary
K1773R
Legendary
*
Offline Offline

Activity: 1792
Merit: 1008


/dev/null


View Profile
March 17, 2013, 05:18:32 PM
 #6

nice service Wink

[GPG Public Key]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
jim618
Legendary
*
Offline Offline

Activity: 1708
Merit: 1066



View Profile WWW
March 17, 2013, 09:30:00 PM
Last edit: March 17, 2013, 09:45:17 PM by jim618
 #7

Just propagate the message broadcasted on the Bitcoin network to lightweight clients too (Bitcoin-qt displayed a warning about the network split when it happened).

I suppose it's only a matter of adding the public key used for such messages to Electrum and add support for these broadcasts in the Electrum<->Electrum server protocol.

There is a slight problem with showing the Bitcoin-QT alerts in lightweight clients as you will often get a message like 'URGENT: Upgrade required' but of course that may not be actionable to the lightweight client user.

If there was a tag for 'network' alerts versus 'bitcoind' alerts we could distinguish them. It could just be a Twitter style tag that was guaranteed to be only in the 'network' alerts. '#URGENT' would probably do it - if you are broadcasting an alert to absolutely everybody it is almost certainly time critical.

The alerts are available in bitcoinj for instance but so far they aren't shown in MultiBit as they can be quite confusing to the end user.

MultiBit HD   Lightweight desktop client.                    Bitcoin Solutions Ltd   Bespoke software. Consultancy.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!