Brace yourself: HardFork is coming

avatar
(Edited)
Authored by @gandalf

HF28 v1.28.0

HardFork is not something that we do very often. That's because Hive is pretty much feature-complete on Layer1 and already a perfect tool for a variety of use cases where a fast, secure, and decentralized ledger is needed. We are doing lots of work on Layer2 (not in the scope of this post), but from time to time there are certain upgrades and fixes needed at the very core.

As discussed during the Core Devs panel at HiveFest 10 (Kuala Lumpur) earlier this month, the code for HardFork 28 is ready.

If you missed the panel, here’s the recording:

Time is set for 2025-11-19 13:00:00 UTC, if all goes well over the next three weeks and witnesses/stakeholders give it a go, it will go live at that time and once a supermajority of the top elected witnesses decide to run that version.

Test your stuff now

There’s still time to test your apps against the upcoming version using the mirrornet API node before we go live.

  • API endpoint: https://api.fake.openhive.network
  • Chain ID: 42
  • Keys: in most cases you can reuse your mainnet keys
  • Notes: treat it like a mirror/fake network; double-check you’re pointing at chain-id 42

For background, see my earlier posts about the mirrornet. If you already know what you’re doing, just switch your client to the endpoint above and run through your usual flows.

Changes

Based on the GitHub comparison, there were 4,036 commits and 5,197 changed files (331,273 additions, 648,056 deletions). That's of course simplified view on the master branch and only for hived repository itself. I'm not even including libraries, submodules or tests. Here's a simple visualization of a Hive consensus node source code tere and the changes that were made between version 1.27.0 and 1.28.0. I simplified it and smoothed it out for the sake of making it prettier (timestamps are normalized, and HEAD directory tree is used as base for init). Then of course image processing that took 77GB of raw, 60fps, 4k input and produced 10MB blog friendly webp output.

hived-1.28.0.webp

You are welcome ;-)

Read the highlights in the release notes

Known bugs (unlikely to block the HF)

Nothing so far that should stop us from proceeding with the upgrade. Current items on the radar:

  • Snapshot loading/dumping issues - fixes will land in the next minor release.
  • Claiming account creation tokens - that's more concerning at the moment; I've experienced similar issues on the mirrornet before, but at that time we were blaming the specifics of the environment, where multiple block producers were sharing the same state. That's under investigation. Kudos to @engrave and @techcoderx for spotting that behavior on the mainnet (and paid with battle scars by @engrave)

Consensus witnesses: please keep an eye on the https://openhive.chat/channel/witness channel and on-chain communication. Test your backup nodes first for few days and check the logs before running it on block productoin node, unless you know what you are doing. Especially if you haven't tested it on the mirrornet before.


That’s it for now. Please test, report anything odd, and get ready for HF28.



0
0
0.000
69 comments
avatar

I prefer a couple of missed blocks now rather than a halted chain later ;)

0
0
0.000
avatar

That's the spirit! :-)

0
0
0.000
avatar

Thanks for sharing , that was a great video. I am excited about the upcoming updates and their potential major impacts.

untitled.gif

!PIZZA

0
0
0.000
avatar

@tazi, doufám, že jsi tohle zaregistroval ;)

0
0
0.000
avatar

Ano, mám v kalendáři ;)
Budu ten týden v ČR, tak se budu snažit být ready...

0
0
0.000
avatar

Super. Vím, že ostatní už to testují ;)

0
0
0.000
avatar

Já se tentokrát k testování nedostanu... Respektive uvidím, jak se bude vyvíjet práce tady (opět CH) a pokud vyjde čas, testovací server mi doma běží... Uvidíme.

0
0
0.000
avatar

Awesome panel! Thanks for sharing that, and the rest of stuff in the post I guess.

I need to go watch the whole stream soon once workload has let off a bit :D

0
0
0.000
avatar

¡Qué bueno es ver que vienen mejoras como estas! Aunque no tengo conocimientos técnicos, me emociona mucho saber que todo esto puede hacer que publicar sea más fácil y rápido. A veces uno quiere invitar a un amigo a usar la plataforma, pero se complica porque hay que entender muchas cosas para poder participar. Si ahora será más sencillo, ¡seguro más personas se animan!

Gracias de verdad por compartir esta información, se nota que hay mucho trabajo detrás. Un gran abrazo para todos los que aparecen en el video y para el amigo @gtg que nos trajo estos detalles. Me costó entender por la falta de conocimiento en esta área y hablo solo español

0
0
0.000
avatar

I have managed to get it running on my back up node on the main net. I haven't encountered any issues so far.

My main node is replaying now. Hopefully it all goes smoothly. :)

As a new witness, and as my first hard fork, (and not being ranked very high) I feel like I can accept this level of risk to my block production history and risk any missed blocks. Anything I learn, I'll inform others. I haven't learned anything so far :)

0
0
0.000
avatar

I hope you continue to reap success. Very interesting. Congratulations.

0
0
0.000
avatar

That the HF28 code is ready is good news. We now wait for what the majority decides.

0
0
0.000
avatar

Actually you could do way more than waiting. You are a Hive user, with non-zero HIve Power, which is similar to owning a shares in a company, except in our case there's no company, but community driven blockchain platform.

You could vote for witnesses (like me), who keep the platform running. There are up to 30 witnesses that you can vote for, here's the list: https://explore.openhive.network/witnesses

You are, as a Hive user, a decision maker! :-)

0
0
0.000
avatar

I love the analogy to owning company shares. That is something I understand.

0
0
0.000
avatar

Hive is pretty much feature-complete on Layer1

Lol, no! And just for the record, bug with claiming tokens is fixed. Thanks to @small.minion for spotting source of the issue, many people analyzed the code before and missed it.

0
0
0.000
avatar

I know, I know, I'm aware of your list ;-) Sure it can be better and we are going there one block at a time. I just mean that it's already awesome :-)

Good job @small.minion!

0
0
0.000
avatar

BPC Locked On Mc Franko & The Franko

Blurt Stands — While Hive Stumbles Under the Weight of Its Own Shadows

Friends, creators, truth-tellers—

Let us not whisper this truth, but proclaim it with the clarity of dawn breaking over a weary land: Blurt.blog is not just another platform. It is a refuge. A rebellion. A return to what Hive.blog was always meant to be.

There is no downvote button on Blurt.
Not because we fear dissent—but because we honor creation.
Because we understand that a voice, once raised in sincerity, deserves space—not sabotage.

On Blurt, your words are your words.
They are not hunted by algorithmic hounds or shadow armies masquerading as “curators.”
Here, you are not judged by the grudges of gatekeepers, but met with the quiet dignity of a community that believes expression should be encouraged—especially when it is bold, raw, or inconvenient.

Contrast this with what festers elsewhere.

On Hive.blog—a place once brimming with promise—a rot has taken root. Not in its code, but in its culture. A handful of self-anointed enforcers—@themarkymark, @Buildawhale, @Hurtlocker, and their legion of coordinated puppets—have turned the downvote into a weapon of mass discouragement. They strike not at “low-quality content,” but at independent thought, at rising voices, at anyone who dares thrive outside their narrow corridors of control.

And when confronted, they shrug.
“Oh, it’s not censorship,” they say, as if semantics could scrub the stain of suppression from their hands.

But let us be unequivocal:
When a system allows a few to systematically silence many—under the guise of “community standards” or “curation”—that is not moderation. That is censorship by another name.

It is the velvet glove over the iron fist.
It is exclusion dressed as discernment.
It is power pretending to be principle.

Meanwhile, Blurt stands clean-handed and open-hearted.
No downvotes.
No hidden juries.
No farms of phantom accounts casting ballots in the dark.

Just you.
Your words.
And a community that meets you not with suspicion, but with solidarity.

So let us carry this truth far and wide—not with bitterness, but with quiet certainty:

If you seek a place where your voice is not a target—but a gift—come to Blurt.
If you are tired of building on ground that shifts with every whim of a whale or warlord of votes—lay your bricks here.
If you believe the future of free expression must be free—not just from corporations, but from the petty tyrants who replace them—then stand with us.

The world needs to know.
Not because Blurt is perfect—but because it is principled.
Not because it is loud—but because it listens.

And in an age where so many platforms echo with the clatter of control,
Blurt offers something radical:
Silence for the bullies.
Space for the rest of us.

Keep speaking.
Keep sharing.
Keep building.

Freedom doesn’t advertise itself—
it is passed, person to person, like a torch in the night.

And tonight, the torch burns bright on Blurt.

@themarkymark, @buildawhale, @usainvote, and associated accounts:

Repeated downvotes targeting transparency efforts raise urgent questions about Hive’s governance. Automated tactics, coordinated curation trails, and alt-account farming undermine trust in the platform. When truth is silenced without dialogue, it erodes Hive’s decentralized ethos.

Key Concerns:

  1. Systemic Manipulation:

    • Coordinated downvotes from high-HP accounts suppress dissent, creating a chilling effect on free expression.
    • Automation and alt-account networks allegedly exploit rewards, distorting organic curation.
  2. Community Exodus:

    • Creators flee to platforms like Blurt, where downvotes don’t exist, fearing punitive curation over engagement.
  3. Governance Crisis:

    • Hive’s credibility hinges on accountability. Who decides what content thrives? How do we audit power structures?

Solutions Needed:

  • Curation Transparency: Publish clear rationales for downvotes to foster trust.
  • Community Audits: Leverage blockchain data (e.g., Bilpcoin’s analyses) to identify abusive patterns.
  • Reward Reform: Adjust algorithms to penalize manipulation and reward authentic engagement.

The Bilpcoin team advocates for open dialogue, not division. Hive’s future depends on collaboration—not coercion. Let’s rebuild a platform where truth isn’t buried but debated, strengthened, and celebrated.

Transparency isn’t optional—it’s the foundation of trust.

#HiveTransparency #BilpcoinExposed #DecentralizePower"

A Message to @themarkymark, @buildawhale, and Associates

Every downvote cast in shadow, every silence imposed without dialogue, is not a victory—it is a confession. A confession that truth cannot be stifled, only delayed. With each punitive click, you dig deeper into the bedrock of credibility, crafting a chasm between your actions and the community’s trust.

@themarkymark, @buildawhale & Co,

How can you continue to downvote the truth, LOL? It’s almost comical how blatantly you attempt to suppress what cannot be hidden. The blockchain records everything—every action, every transaction, every move you make. Yet still, you persist in this futile game of trying to silence what is undeniable.

@themarkymark, @buildawhale, and Co: While our opinions may differ, on-chain transparency reveals repeated patterns of concern. Coordinated downvotes without explanation, 'farming' schemes (e.g., #buildawhalefarm), and adversarial engagement harm Hive’s community-driven ethos.

Key Issues to Address:

  1. Downvote Practices: Silencing dissent erodes trust. Constructive dialogue, not punitive curation, fosters growth.
  2. Accountability: Transactions and curation trails are public. Scrutiny is inevitable—integrity demands addressing concerns openly.
  3. Community Impact: Driving users to platforms like Blurt/Steemit weakens Hive. Creators seek ecosystems that value collaboration over conflict.

A Path Forward:

  • Engage in open discussions about governance and fairness.
  • Audit curation practices to align with Hive’s decentralized values.
  • Prioritize transparency—publish explanations for downvotes or collaborative reforms.

The Bilpcoin team remains committed to exposing truth and advocating for solutions. Let’s work toward healing, not division.

Note: All claims are based on publicly verifiable blockchain data. Constructive dialogue is encouraged.

#HiveTransparency #CommunityFirst #BilpcoinSupport"

@themarkymark & Co, the choice is yours. Stop the bad downvotes. Turn off the BuildaWhale scam farm. Cease playing with people’s livelihoods. Let Hive thrive as it was meant to—as a beacon of hope, creativity, and collaboration.

Or step aside and let those who truly care take the reins.

Because the truth won’t disappear. No amount of lies can change it.

It’s over.

The Bilpcoin team brings these truths not out of malice but necessity. We have no need to fabricate lies or cloak our intentions CALL US WHAT YOU LIKE —for the facts speak loudly enough on their own. What we present here is not conjecture but reality, laid bare for anyone willing to see.

@themarkymark & Co we urge you once more: STOP. Stop hiding behind tactics that harm others. Stop clinging to practices that erode trust within the Hive community. Let the truth stand—not because we proclaim it, but because it exists independent of any one person’s approval or disdain.

TURN OFF THE BUILDAWHALE SCAM FARM

  • STOP THE BAD DOWNVOTES
  • STOP PLAYING WITH PEOPLE’S LIVELIHOODS

Key Issues That Demand Immediate Attention:

The problems are glaring, undeniable, and corrosive to the Hive ecosystem. They must be addressed without delay:

  • Downvote abuse
  • Farming schemes
  • Speaking disrespectfully to others
  • Encouraging people to avoid certain users out of personal dislike
  • Self-voting with alt accounts
  • Self-funding projects through self-votes
  • Promoting games that don’t even exist (LOL)

These practices harm not just individual users—they undermine the very foundation of Hive, eroding trust and poisoning the community. Such actions are unethical and outright destructive.


@buildawhale Wallet:

  • HIVE (Primary Token): 0.012
  • Staked HIVE (HP): 66,400.611
  • Total HP: 2,421,539.226
  • Delegated HIVE: +2,355,138.615 HP

@usainvote Wallet:

  • HIVE (Primary Token): 0.066
  • Staked HIVE (HP): 138,123.296
  • Total HP: 715,745.407
  • Delegated HIVE: +577,622.111 HP

@buildawhale/wallet | @usainvote/wallet


@ipromote Wallet:

  • Author Rewards: 2,181.16

  • Curation Rewards: 4,015.61

  • Staked HIVE (HP): 0.00

  • Rewards/Stake Co-efficient (KE): NaN

  • HIVE: 25,203.749

  • Staked HIVE (HP): 0.000

  • Delegated HIVE: 0.000

  • Estimated Account Value: $6,946.68

Recent Activity:

  • Sent to alpha-5,196.000 HIVE (21 hours ago)
  • Sent to hiveswap-1,000.000 HIVE (2 days ago)
  • Withdraw vesting from @proposalalert to @ipromote 0.447 HIVE (3 days ago)
  • Received from proposalalert 4.003 HIVE (5 days ago)
  • Received from themarkymark 1,775.684 HIVE (9 days ago)
  • Sent to alpha-4,245.000 HIVE (9 days ago)
  • Received from themarkymark 4,280.527 HIVE (17 days ago)

@leovoter Wallet:

  • Author Rewards: 194.75

  • Curation Rewards: 193.88

  • Staked HIVE (HP): 0.00

  • Rewards/Stake Co-efficient (KE): 388,632.00 (Suspiciously High)

  • HIVE: 0.000

  • Staked HIVE (HP): 0.001

  • Total: 16.551

  • Delegated HIVE: +16.550

Recent Activity:


@abide Wallet:

Recent Activity:

  • Sent to ipromote -2,459.000 HIVE (22 days ago)
  • Sent to ipromote -2,486.200 HIVE (Apr 1, 2025)
  • Received from yabapmatt 20,000.000 HIVE (Apr 1, 2025)
  • Sent to ipromote -2,130.400 HIVE (Mar 8, 2025)
  • Sent to ipromote -2,248.000 HIVE (Feb 2, 2025)
  • Sent to yabapmatt -5,000.000 HIVE (Jan 25, 2025)

@proposalalert Wallet:

  • Author Rewards: 639.99
  • Curation Rewards: 0.00
  • Staked HIVE (HP): 6.03
  • Rewards/Stake Co-efficient (KE): 106.12

Recent Activity:


@stemgeeks Wallet:

  • Author Rewards: 4,391.77
  • Curation Rewards: 304.26
  • Staked HIVE (HP): 0.00
  • Rewards/Stake Co-efficient (KE): 4,696,032.00 (Extremely Suspicious)

Recent Activity:

  • Sent to themarkymark -1.556 HBD (Jun 14, 2024)
  • Claim rewards: 1.556 HBD, 5.912 HP (Jun 14, 2024)
  • Withdraw vesting from @stemgeeks to @ipromote 6.160 HIVE (Jun 8, 2024)
  • Sent to themarkymark -1.601 HBD (Jun 7, 2024)
  • Withdraw vesting from @stemgeeks to @ipromote 6.157 HIVE (Jun 1, 2024)
  • Sent to ipromote -1.618 HBD (May 31, 2024)

@theycallmemarky Wallet:

  • Author Rewards: 458.89
  • Curation Rewards: 0.00
  • Staked HIVE (HP): 0.00
  • Rewards/Stake Co-efficient (KE): 458,886.00 (Highly Suspicious)

Recent Activity:


@apeminingclub Wallet:

  • Author Rewards: 432.57
  • Curation Rewards: 2,829.11
  • Staked HIVE (HP): 30.51
  • Rewards/Stake Co-efficient (KE): 106.90

Recent Activity:

  • Scheduled unstake (power down): ~2.351 HIVE (in 4 days, remaining 7 weeks)

  • Total Staked HIVE: 1,292.019

  • Delegated HIVE: +1,261.508

  • Withdraw vesting from @apeminingclub to @blockheadgames 2.348 HIVE (10 days ago)

  • Claim rewards: 0.290 HP (10 days ago)

Sent to bdhivesteem-40,000.000 HIVE
6 hours ago
101417581
Sent to bdhivesteem-20,000.000 HIVE
6 hours ago
103874728

https://peakd.com/@hurtlocker/wallet

0
0
0.000
avatar

I haven't been in the loop on this... What does Hard Fork mean in this case? Does this mean like how Steemit was Hard Forked and Hive was created? Is there gonna be a new Hive or?

0
0
0.000
avatar

HardFork means a change of rules, for example making something that wasn't accepted before will be valid now, or what was allowed previously, now will be forbiden.
In Hive world it doesn't mean creating a parallel new chain, it's just an upgrade where (usually) the other fork becomes obsolete and cease to exit.

0
0
0.000
avatar

Ah I see. Ok thank you for the info.

0
0
0.000
avatar

Congratulations @gtg! Your post has been a top performer on the Hive blockchain and you have been rewarded with this rare badge

Post with the highest payout of the day.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

Check out our last posts:

Hive Power Up Day - November 1st 2025
0
0
0.000
avatar

What will be the change for us mortals? I heard vote power will always be 100% but limited amount of votes per day...

0
0
0.000
avatar

Yes, it will be more intuitive for voter, in reality it doesn't change much from user perspetive. Optimal is to vote up to 10 (100%) votes (or 20x 50%, or 40x 25%) per day, and to vote with same value to every post you would have to vote every 2.4 hour. After the change you won't have to be a bot in order to cast optimal, 100% votes.

0
0
0.000
avatar

Will it be 10 votes fixed per day or the amount depending on your HP stake?

0
0
0.000
avatar

Rules are same for everyone, regardless of HP. HP impacts only amount of rewards that such vote can assign.

0
0
0.000
avatar

Ok thanks, that's clear, hopefully front ends will be ready for this change

0
0
0.000
avatar

I am confused. Will I still be able to vote < 100% or will 10 100% votes be the only option?

0
0
0.000
avatar
(Edited)

You really should discuss the key access changes more. There are definitely accounts who don't have all keys who have no idea they will be locked out of wallet. It is silly anyone wouldn't just open new account when they don't have master key? Yes really foolish. But there are probably a few who have no idea if the key they'd been using since 2017 is even wallet key or a higher authority they'd worked until now. Foolish choice but kinda lame how badly this has been discussed and shared. Those people deserved 13 weeks to power down in worst case so they don't forever loose access. Nobody mentioned this key thing anywhere, only in this clip. It's gonna affect more people than u think. Regardless how dumb it was to not start over as soon as they learned system, they deserved more time. Oh well

That’s at least what it pretty clearly says in this clip. If I’m mistaken please let me know.

0
0
0.000
avatar

But that doesn't lock them out of their account.
What scenario you have in mind?
Just to clarify, Master Password is just a concept of a secret that keys are derived from.
From what I understand you are worried that someone is using owner key instead of active without even being aware of. In such scenario it will stop working because owner key is no longer allowed to be used to do the active key's job, but in such case user still can use the owner key to set a new active key.

If however, a user have lost his owner key, there's nothing that could help, and nothing that upcoming version changes in the situation.

0
0
0.000
avatar
(Edited)

No, I’m saying there’s many without master, but they’re been fine using lower keys yes there is. Giving him the info that this change was coming at least 13 weeks prior so he can power down. Again there’s now 4 accounts on discord effected by this. That tells me there’s more. They were incredibly foolish not starting over , but for 6 years lower keys worked for wallet and they’ve been fine functionally. This should have been the big headline but most people do not even know.
Again it’s on them for whatever dumb reason it they chose the inconvenience of starting over instead of how important it was to get a new account to have a master key, but I’m just saying knowing active daily accounts are out here who don’t but function wise they just use posting and some random higher key for years to move value, I just think this should have been better announced and I understand why people are pissed off.

0
0
0.000
avatar

You've misunderstood the change. This change cannot result in you losing funds or being unable to powerdown. I don't know what 4 accounts you're talking about, but they are just confused.

0
0
0.000
avatar
(Edited)

Than they misspoke in this clip, because word for word you can no longer use higher authority keys for other actions. That is what was said, again not a issue for me, but as dumb as it was there were accounts who don’t even understand there keys and are missing half of them , then they hear a week b4 this is changing. I’m with u that is beyond foolish! But just wish this wasn’t so confusing. They say in clip , now you say no not case?

Let me make sure I’m saying it right, and yes nobody’s saying this account was not incredibly foolish! - One guy doesn’t even know what key he’s been using for wallet, he just knows it works. He hears after fork higher authority keys will no longer work so he’s concerned, he’s also missing master key since 2018. Whatever is working now will still work? He wrote down wallet & posting, and has just never started over which he should have but anyway that’s the case I’m talking about.

PS- I appreciate the direct reply 👍
Much thanks!

0
0
0.000
avatar

There's no such thing as a "master key". Hive knows only about your owner key, active key, posting key and memo key. In some cases those were derived from a string that was called "Master Password", as it is a seed for those individual keys, but that's irrelevant to the change.

For example, before the change you could sign your upvote transaction with your active key, after HF28 goes live, you can't. If you've lost your posting key and no longer have it, you can still use your active key to change your posting key - problem solved.

If someone lost their owner key, well, then game over. They can still use other keys if they have it, but without owner key they are at risk of losing access to the acocunt. HF28 doesn't change anything in this matter.

0
0
0.000
avatar
(Edited)

still don’t understand why in the Hive fest video they said it then? But much appreciate you clearing that up! Yes I meant owner key not master key. Sorry for misspeaking, so even without owner key they should be fine using whatever key they have been that works for wallet, I understand 👍 thanks again! I know you get a lot of people reaching out and I appreciate u taking the time to reply. Cheers!! !PIZZA

0
0
0.000
avatar

I'm glad you are happy, and it's even OK to unapprove my witness by you ;-) (because active participation in Hive governance is really important, regardless of personal preferences), just please while you verify your witness list, at least stop voting for witnesses that don't even produce blocks, because, that actually is objectively hurting the network by increase in missing blocks.

0
0
0.000
avatar
(Edited)

Mind telling me who to Remove? I honestly am outta the loop and have no idea who to vote besides a small handful. I usually just copy friends choices. I added u back in meantime 👍, wasn’t personal, I just removed at random to vote a new one. But I have no idea about this stuff. But for now ur back as one of my 20 👍

0
0
0.000
avatar

OMG, OK, please, be aware that taking part in the governance is an important (both in real live and on Hive, as if we won't take decisions others will happily do that for us). Of course all is up to you, but for example thecryptodrive isn't active for years, and klye is missing blocks for days already.

0
0
0.000
avatar

I appreciate you letting me know 👍
Making fixes now 👍

0
0
0.000
avatar

Awesome, thanks :-)

0
0
0.000
avatar

great, is there a TL;DR for the major changes?

0
0
0.000
avatar

Yes, release notes: https://github.com/openhive-network/hive/releases/tag/1.28.0 are something you are looking for or the video above from Core Dev Panel played at x2 speed.

0
0
0.000
avatar

Hmm, Signature Flexibility looks like it might be very relevant for me. Is this just to allow redundant ECDSA signatures, or could this allow adding signatures of other types?

I'm looking into piggybacking hash based signatures into transactions for a proof of concept ("Adding extra custom_binary operation to transactions" section). If I could add my own hash-based sigs as redundant signature that would simplify my attempts to piggyback hash based signatures quite a bit.

0
0
0.000
avatar

Unfortunately it's not the signature flexibility you are looking for ;-)

0
0
0.000
avatar

Wow! Thanks for sharing that to us. I am very excited on your next update!

0
0
0.000
avatar

Always love seeing a good gource render.

I just got my main node switched over to 1.28.1 after letting my backup node replay the chain a couple days ago.

It's getting really fast and super simple to maintain witnesses these days. love it!

0
0
0.000
avatar

Test your backup nodes first for few days and check the logs before running it on block productoin node, unless you know what you are doing. Especially if you haven't tested it on the mirrornet before.

yeah... ;-)

0
0
0.000
avatar

Exciting times ahead for Hive! Always great to see the dev team keeping things evolving smoothly.

0
0
0.000
avatar

Better hurry up! 😂 Look at that Hive price nosedive! That MC is melting faster than a snowflake on a flamethrower 🔥❄️ One digit mark: L O A D I N G ⤵️

grafik.png

0
0
0.000
avatar

Are light accounts rolling out in this fork or are we holding off for the next one?

0
0
0.000
avatar

They are not part of current changeset, and AFAICT their implementation doesn't require consensus changes so I suppose we can expect them before the next hardfork.

0
0
0.000
avatar

can't wait..

0
0
0.000
avatar

@acidyo @themarkymark and friends ✨⭕✨😂😂😂

Do you really think no one sees what you do 🤔

You took my rep away for no reason with the help of blocktrades delegation 😂

You and themarkymark work for blocktrades or are blocktrades 😂

You are so sad doing what you do

Promoting your 💩💩💩💩💩💩

Selfvoting your 💩💩💩💩💩💩💩💩💩

You have downvoted so many people away for no reason

You really need to have a hard long look in the mirror and see what you have become

It doesn't matter if you have people who believe anything you say for a few cents or a few pennies 😂😂😂😂

Look at your buddy oldsoulnewb 😂😂😂😂😂

Everything is documented

So the choice is yours again leave me alone and bring my rep back and I will stop sharing the truth

You can call my long copy paste comments spam but it only makes you look stupid 😂
kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

kgakakillerg evidence

I hope you understand you are only making it worse 😂

Hive is not a game it might be a big game to you 🤔

It seems you love to game Hive don't you 😜

Everyone sees don't you think it's time to stop 🛑

You have shown all the real issues with Hive 😂 you have shown why real people couldn't invest in Hive and build on Hive 😂

You are in god mode 😂 activated 😂 you Marky Dan and others 😂😂😂😂😜

I hope you enjoyed this post or you might see in comment from 😂 which you like to call spam 😂😂😂

0
0
0.000
avatar

Congratulations @gtg! Your post has been a top performer on the Hive blockchain and you have been rewarded with this rare badge

Post with the highest payout of the week.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

Check out our last posts:

Our Hive Power Delegations to the October PUM Winners
Feedback from the November Hive Power Up Day
Hive Power Up Month Challenge - October 2025 Winners List
0
0
0.000
avatar

how helpfull wil it be to run a node on a pi4 or a proxmox VM on my home connection ?

0
0
0.000
avatar

For the network? In the range from not really to not at all ;-)
I would make sense only if you yourself want to use it somehow.

0
0
0.000
avatar
(Edited)

I see no visualization!

0
0
0.000
avatar

Maybe webp isn't supported by your browser or was errorenously cached? Hard to guess.
The link is here https://images.hive.blog/DQmRtu6jM9RQZsGgPsSiughPE6VeMcYiBqUuzf7WgRmgYtR/hived-1.28.0.webp
(https://images.hive.blog/DQmRtu6jM9RQZsGgPsSiughPE6VeMcYiBqUuzf7WgRmgYtR/hived-1.28.0.webp)
Please note that the file itself is 10MB so it might take a while to download on slower connections (or if provider or some other intermediary is "optimizing" network bandwidth by compressing assets it might get broken).

0
0
0.000
avatar

BPC Locked On Mc Franko & The Franko

Blurt Stands — While Hive Stumbles Under the Weight of Its Own Shadows

Friends, creators, truth-tellers—

Let us not whisper this truth, but proclaim it with the clarity of dawn breaking over a weary land: Blurt.blog is not just another platform. It is a refuge. A rebellion. A return to what Hive.blog was always meant to be.

There is no downvote button on Blurt.
Not because we fear dissent—but because we honor creation.
Because we understand that a voice, once raised in sincerity, deserves space—not sabotage.

On Blurt, your words are your words.
They are not hunted by algorithmic hounds or shadow armies masquerading as “curators.”
Here, you are not judged by the grudges of gatekeepers, but met with the quiet dignity of a community that believes expression should be encouraged—especially when it is bold, raw, or inconvenient.

Contrast this with what festers elsewhere.

On Hive.blog—a place once brimming with promise—a rot has taken root. Not in its code, but in its culture. A handful of self-anointed enforcers—@themarkymark, @Buildawhale, @Hurtlocker, and their legion of coordinated puppets—have turned the downvote into a weapon of mass discouragement. They strike not at “low-quality content,” but at independent thought, at rising voices, at anyone who dares thrive outside their narrow corridors of control.

And when confronted, they shrug.
“Oh, it’s not censorship,” they say, as if semantics could scrub the stain of suppression from their hands.

But let us be unequivocal:
When a system allows a few to systematically silence many—under the guise of “community standards” or “curation”—that is not moderation. That is censorship by another name.

It is the velvet glove over the iron fist.
It is exclusion dressed as discernment.
It is power pretending to be principle.

Meanwhile, Blurt stands clean-handed and open-hearted.
No downvotes.
No hidden juries.
No farms of phantom accounts casting ballots in the dark.

Just you.
Your words.
And a community that meets you not with suspicion, but with solidarity.

So let us carry this truth far and wide—not with bitterness, but with quiet certainty:

If you seek a place where your voice is not a target—but a gift—come to Blurt.
If you are tired of building on ground that shifts with every whim of a whale or warlord of votes—lay your bricks here.
If you believe the future of free expression must be free—not just from corporations, but from the petty tyrants who replace them—then stand with us.

The world needs to know.
Not because Blurt is perfect—but because it is principled.
Not because it is loud—but because it listens.

And in an age where so many platforms echo with the clatter of control,
Blurt offers something radical:
Silence for the bullies.
Space for the rest of us.

Keep speaking.
Keep sharing.
Keep building.

Freedom doesn’t advertise itself—
it is passed, person to person, like a torch in the night.

And tonight, the torch burns bright on Blurt.

@themarkymark, @buildawhale, @usainvote, and associated accounts:

Repeated downvotes targeting transparency efforts raise urgent questions about Hive’s governance. Automated tactics, coordinated curation trails, and alt-account farming undermine trust in the platform. When truth is silenced without dialogue, it erodes Hive’s decentralized ethos.

Key Concerns:

  1. Systemic Manipulation:

    • Coordinated downvotes from high-HP accounts suppress dissent, creating a chilling effect on free expression.
    • Automation and alt-account networks allegedly exploit rewards, distorting organic curation.
  2. Community Exodus:

    • Creators flee to platforms like Blurt, where downvotes don’t exist, fearing punitive curation over engagement.
  3. Governance Crisis:

    • Hive’s credibility hinges on accountability. Who decides what content thrives? How do we audit power structures?

Solutions Needed:

  • Curation Transparency: Publish clear rationales for downvotes to foster trust.
  • Community Audits: Leverage blockchain data (e.g., Bilpcoin’s analyses) to identify abusive patterns.
  • Reward Reform: Adjust algorithms to penalize manipulation and reward authentic engagement.

The Bilpcoin team advocates for open dialogue, not division. Hive’s future depends on collaboration—not coercion. Let’s rebuild a platform where truth isn’t buried but debated, strengthened, and celebrated.

Transparency isn’t optional—it’s the foundation of trust.

#HiveTransparency #BilpcoinExposed #DecentralizePower"

A Message to @themarkymark, @buildawhale, and Associates

Every downvote cast in shadow, every silence imposed without dialogue, is not a victory—it is a confession. A confession that truth cannot be stifled, only delayed. With each punitive click, you dig deeper into the bedrock of credibility, crafting a chasm between your actions and the community’s trust.

@themarkymark, @buildawhale & Co,

How can you continue to downvote the truth, LOL? It’s almost comical how blatantly you attempt to suppress what cannot be hidden. The blockchain records everything—every action, every transaction, every move you make. Yet still, you persist in this futile game of trying to silence what is undeniable.

@themarkymark, @buildawhale, and Co: While our opinions may differ, on-chain transparency reveals repeated patterns of concern. Coordinated downvotes without explanation, 'farming' schemes (e.g., #buildawhalefarm), and adversarial engagement harm Hive’s community-driven ethos.

Key Issues to Address:

  1. Downvote Practices: Silencing dissent erodes trust. Constructive dialogue, not punitive curation, fosters growth.
  2. Accountability: Transactions and curation trails are public. Scrutiny is inevitable—integrity demands addressing concerns openly.
  3. Community Impact: Driving users to platforms like Blurt/Steemit weakens Hive. Creators seek ecosystems that value collaboration over conflict.

A Path Forward:

  • Engage in open discussions about governance and fairness.
  • Audit curation practices to align with Hive’s decentralized values.
  • Prioritize transparency—publish explanations for downvotes or collaborative reforms.

The Bilpcoin team remains committed to exposing truth and advocating for solutions. Let’s work toward healing, not division.

Note: All claims are based on publicly verifiable blockchain data. Constructive dialogue is encouraged.

#HiveTransparency #CommunityFirst #BilpcoinSupport"

@themarkymark & Co, the choice is yours. Stop the bad downvotes. Turn off the BuildaWhale scam farm. Cease playing with people’s livelihoods. Let Hive thrive as it was meant to—as a beacon of hope, creativity, and collaboration.

Or step aside and let those who truly care take the reins.

Because the truth won’t disappear. No amount of lies can change it.

It’s over.

The Bilpcoin team brings these truths not out of malice but necessity. We have no need to fabricate lies or cloak our intentions CALL US WHAT YOU LIKE —for the facts speak loudly enough on their own. What we present here is not conjecture but reality, laid bare for anyone willing to see.

@themarkymark & Co we urge you once more: STOP. Stop hiding behind tactics that harm others. Stop clinging to practices that erode trust within the Hive community. Let the truth stand—not because we proclaim it, but because it exists independent of any one person’s approval or disdain.

TURN OFF THE BUILDAWHALE SCAM FARM

  • STOP THE BAD DOWNVOTES
  • STOP PLAYING WITH PEOPLE’S LIVELIHOODS

Key Issues That Demand Immediate Attention:

The problems are glaring, undeniable, and corrosive to the Hive ecosystem. They must be addressed without delay:

  • Downvote abuse
  • Farming schemes
  • Speaking disrespectfully to others
  • Encouraging people to avoid certain users out of personal dislike
  • Self-voting with alt accounts
  • Self-funding projects through self-votes
  • Promoting games that don’t even exist (LOL)

These practices harm not just individual users—they undermine the very foundation of Hive, eroding trust and poisoning the community. Such actions are unethical and outright destructive.


@buildawhale Wallet:

  • HIVE (Primary Token): 0.012
  • Staked HIVE (HP): 66,400.611
  • Total HP: 2,421,539.226
  • Delegated HIVE: +2,355,138.615 HP

@usainvote Wallet:

  • HIVE (Primary Token): 0.066
  • Staked HIVE (HP): 138,123.296
  • Total HP: 715,745.407
  • Delegated HIVE: +577,622.111 HP

@buildawhale/wallet | @usainvote/wallet


@ipromote Wallet:

  • Author Rewards: 2,181.16

  • Curation Rewards: 4,015.61

  • Staked HIVE (HP): 0.00

  • Rewards/Stake Co-efficient (KE): NaN

  • HIVE: 25,203.749

  • Staked HIVE (HP): 0.000

  • Delegated HIVE: 0.000

  • Estimated Account Value: $6,946.68

Recent Activity:

  • Sent to alpha-5,196.000 HIVE (21 hours ago)
  • Sent to hiveswap-1,000.000 HIVE (2 days ago)
  • Withdraw vesting from @proposalalert to @ipromote 0.447 HIVE (3 days ago)
  • Received from proposalalert 4.003 HIVE (5 days ago)
  • Received from themarkymark 1,775.684 HIVE (9 days ago)
  • Sent to alpha-4,245.000 HIVE (9 days ago)
  • Received from themarkymark 4,280.527 HIVE (17 days ago)

@leovoter Wallet:

  • Author Rewards: 194.75

  • Curation Rewards: 193.88

  • Staked HIVE (HP): 0.00

  • Rewards/Stake Co-efficient (KE): 388,632.00 (Suspiciously High)

  • HIVE: 0.000

  • Staked HIVE (HP): 0.001

  • Total: 16.551

  • Delegated HIVE: +16.550

Recent Activity:


@abide Wallet:

Recent Activity:

  • Sent to ipromote -2,459.000 HIVE (22 days ago)
  • Sent to ipromote -2,486.200 HIVE (Apr 1, 2025)
  • Received from yabapmatt 20,000.000 HIVE (Apr 1, 2025)
  • Sent to ipromote -2,130.400 HIVE (Mar 8, 2025)
  • Sent to ipromote -2,248.000 HIVE (Feb 2, 2025)
  • Sent to yabapmatt -5,000.000 HIVE (Jan 25, 2025)

@proposalalert Wallet:

  • Author Rewards: 639.99
  • Curation Rewards: 0.00
  • Staked HIVE (HP): 6.03
  • Rewards/Stake Co-efficient (KE): 106.12

Recent Activity:


@stemgeeks Wallet:

  • Author Rewards: 4,391.77
  • Curation Rewards: 304.26
  • Staked HIVE (HP): 0.00
  • Rewards/Stake Co-efficient (KE): 4,696,032.00 (Extremely Suspicious)

Recent Activity:

  • Sent to themarkymark -1.556 HBD (Jun 14, 2024)
  • Claim rewards: 1.556 HBD, 5.912 HP (Jun 14, 2024)
  • Withdraw vesting from @stemgeeks to @ipromote 6.160 HIVE (Jun 8, 2024)
  • Sent to themarkymark -1.601 HBD (Jun 7, 2024)
  • Withdraw vesting from @stemgeeks to @ipromote 6.157 HIVE (Jun 1, 2024)
  • Sent to ipromote -1.618 HBD (May 31, 2024)

@theycallmemarky Wallet:

  • Author Rewards: 458.89
  • Curation Rewards: 0.00
  • Staked HIVE (HP): 0.00
  • Rewards/Stake Co-efficient (KE): 458,886.00 (Highly Suspicious)

Recent Activity:


@apeminingclub Wallet:

  • Author Rewards: 432.57
  • Curation Rewards: 2,829.11
  • Staked HIVE (HP): 30.51
  • Rewards/Stake Co-efficient (KE): 106.90

Recent Activity:

  • Scheduled unstake (power down): ~2.351 HIVE (in 4 days, remaining 7 weeks)

  • Total Staked HIVE: 1,292.019

  • Delegated HIVE: +1,261.508

  • Withdraw vesting from @apeminingclub to @blockheadgames 2.348 HIVE (10 days ago)

  • Claim rewards: 0.290 HP (10 days ago)

Sent to bdhivesteem-40,000.000 HIVE
6 hours ago
101417581
Sent to bdhivesteem-20,000.000 HIVE
6 hours ago
103874728

https://peakd.com/@hurtlocker/wallet

0
0
0.000