As of now, my node is updated and it's running hived 1.24.0, which means I'm supporting the upcoming HF 24. Once the top 21 witnesses will run the same version I may probably start to produce blocks too.
There is an ongoing funding proposal for two of my Hive-related projects, which will allow me to support some of the costs involved. If you want to support this proposal, all you have to do is to vote it using any of the two links below:
Sign this proposal with Hivesigner
Peakd: https://peakd.com/me/proposals/92
Already supported by: @toofasteddie, @amico, @bluerobo, @chrisaiki, @erikah, @ervin-lemark, @ew-and-patterns, @guruvaj, @mytechtrail, @pharesim, @ryivhnn, @sacrosanct, @captainklaus, @santigs, @inertia, @bro.poker, @distantsignal, @doze, @gadrian-sp, @shmoogleosukami, @valued-customer, @condeas, @justinashby, @likwid, @bucipuci
I'm a geek, blogger and ultrarunner. You can find me mainly on my blog at Dragos Roua where I write about productivity, business, relationships and running. Here on Hive you may stay updated by following me @dragosroua.
Wanna know when you're getting paid?
| I know the feeling. That's why I created hive.supply, an easy to use and accurate tool for calculating your HIVE rewards | |
Hive is not running with chrome browser but others still run, what happened to it, i dont know.
"Chrome" is not guilty. You need to change the API node settings. Preparation for HF24 paralyzed some nodes.
And how do i manage it from chrome settings....!
You cannot change this from the CHROME setting. You can only change the API in the application you use to read and write (Hiveblog, PeakD, etc.).
In the CHROME settings you can only see if you have blocked some addresses and edit this