discussed in hangout 3:
It'd be great if the wallet can display important info (1),
not every user will check forum, social media and so on :-(
Such a (text) field should be self-containable, that means, should not require the user to start the browser to read all. E.g. to make it less possible to trace the user and his wallet (IP, ...)
Who can generate text to be displayed in the wallet?
E.g. the community and/or the current project devs can create multisig adresses, so it will be assured no spam and such gets through. And the text to be displayed is queried from the blockchain then
(1) e.g. new polls, challenges, important upgrades, ...
Could maybe have the client monitor a burn address and parse the OP_Return data sent in transactions to said address? Would allow anyone to make a message though..
in case there would be a fork (there were 2 recently) a solution with this feature working over the blockchain would not work :-(
e.g. telling them that they are actually on a fork
How difficult can this be? We already have a ticker and active info on the the wallet GUI. Is there anyway we could utilise this.
I'm not a coder so I can't help with it but, I believe this could be a solution..
An idea was brought up in the 17th hangout - por/pos difficulty being incredibly low (< 1.0) is somewhat an indicator of your client being on a fork, right?
What if a message popped up stating "Warning: Difficulty low, check you're running the latest version." or something? Could help catch anyone that's running an older client.
Yeah thats a really good idea, I like that. We could probably say, if the client is synced to the best block, in prod, and completely booted, and diff is < 1, show the Red banner warning in the client with the message. If diff rises > 1, remove the banner.
Plus one; I support this idea.
Please consider adding a flag to represent this situation also for headless wallet as a reply to "getmininginfo" (?) . Though the discussed solution is based on diff only, in future the condition might get more complex. It'd be best to create the "placeholder" now.
Also it would be only fair for ppl using RPC based wallet remote controls to benefit from the same logic.
Alerts could be done easy using existing "message things". But will break when forking. The user will not see messages from the other fork.
The message could be loaded as soon as the transaction is received using normal tx propagation mechanism. Nodes still receive transaction even when on fork. The tx should have higher fees to propagate faster and further.
Since the mentioned scenario where a fork makes trouble seems to "hinder this", we can split this up, see:
so we can focus on the "feature" itself.
See also:
There already exists an alert protocol that can be used to broadcast a message. It must be tested and documented.
Maybe UI changed, so the alerts are visible at the bottom text. Ideally there should be a feed style window, with data pulled from blockchain messages, alert protocol and polls.
Created separate feature request: #613
I tried to send "Alert" on testnet, (testnet private key is public...) and it worked. The alert text appears in
But once the popup bubble fades, the text is no longer show in the gui. In BitcoinGUI::setNumBlocks, the function to get alerts is called, but the output is assigned but not used.
Who tf made that gui code? It is horrible, model-view mixed with adhoc calls to core and scattered to multiple files.
this done and closeable? @tomasbrod @denravonska
Can we test it one more time in testnet, plz?
MOTD are, in general, not appropriate. The rest has been resolved already. Closing.
Most helpful comment
There already exists an alert protocol that can be used to broadcast a message. It must be tested and documented.
Maybe UI changed, so the alerts are visible at the bottom text. Ideally there should be a feed style window, with data pulled from blockchain messages, alert protocol and polls.
Created separate feature request: #613