Hive HardFork 28 Jump Starter Kit

avatar
(Edited)
Authored by @gandalf

This is a copy–paste friendly guide to get a Hive consensus node running for HF28.

Simple recipes for:

  • seed node
  • witness node
  • exchange / personal wallet node
  • basic API node
  • Docker version of all of the above

Assumptions / pre-requisites

To keep the recipes dead simple, I assume:

Hardware (minimum reasonable):

  • x86-64 CPU (*)
  • 8 GB RAM
  • 1 TB fast SSD / NVMe

Single-core CPU performance matters most during the initial replay/resync, and later for keeping up with the head block. The more RAM you have, the more data Linux can keep in the page cache, which means less pressure on your storage.

The required size of the shared memory file (where the node state lives) has dropped significantly, so we no longer recommend forcing it into RAM via tmpfs. In most cases it's enough to keep it on disk and let the kernel’s page cache do its job, especially on systems with plenty of RAM. You can still use tmpfs as an optional optimization if you really want to squeeze out every bit of replay/resync performance.

(*) Others are just out of scope now

Software

  • OS: Ubuntu 24.04 LTS
  • User: local user hive
    • uid = 1000
    • HOME = /home/hive
  • Data dir: /home/hive/datadir
  • We use:
    • screen to keep hived running
    • lbzip2 for compressed snapshots
    • docker if you follow the Docker section
  • Ports (adjust firewall / security groups):
    • 2001 – P2P (seed)
    • 8090, 8091 – WebSocket / HTTP APIs

What these recipes can run

Same binary, different config:

  • Seed node – helps the P2P network, no special plugins.
  • Witness node – produces blocks, keeps the surface small.
  • Exchange / wallet node – uses history plugin to track deposits/withdrawals for chosen accounts.
  • Basic API node – serves simple RPC like get_block, broadcasts transactions, tracks the head block.

The role is decided by config.ini (plugins, tracked accounts, witness name, private key, etc.), not by different binaries.
A snapshot may already contain extra data (like history for tracked accounts), but if you remove the related plugins or tracked accounts from config.ini, that data simply won’t be used.

Part 1 – native binary (non-Docker) recipes

Recipe 1 – One-time prep (run as hive user)

# create basic tree
mkdir -pv ~/datadir/{blockchain,snapshot} ~/bin

Recipe 2 – Get sample config

Start from the "exchange" config and then tweak it for your node's desired role (seed / witness / wallet / API).

wget https://gtg.openhive.network/get/snapshot/exchange/example-exchange-config.ini \
  -O ~/datadir/config.ini

Later you might want to:

  • disable plugin = ... entries you don’t need
    (adding new plugin entries may require a replay)
  • remove tracked accounts you don’t need
    (mainly for exchange / wallet-style nodes)
    (adding new tracked accounts will require a replay)
  • set witness and private-key if you run this node as a witness
  • tweak API bind addresses and ports for your setup
  • change the location of the shared memory file or comments / history databases
  • adjust how block_log is split to match your storage preferences

Recipe 3 – Download Hive 1.28.3 binaries

wget https://gtg.openhive.network/get/bin/hived-1.28.3 -nc -P ~/bin
wget https://gtg.openhive.network/get/bin/cli_wallet-1.28.3 -nc -P ~/bin
chmod u+x ~/bin/{hived,cli_wallet}-1.28.3

Recipe 4 – Put shared_memory on tmpfs (optional, advanced)

shared_memory.bin is hot. Putting it in RAM can speed up replay and reduce SSD wear, but if it’s gone (for example after a reboot) or corrupted, you will need to start over with replay or load a snapshot. Treat this as an optional optimization, not the default.

  1. Enable tmpfs path in config:
sed -i '/^# shared-file-dir/s/^# //' ~/datadir/config.ini
# or manually uncomment line: shared-file-dir = "/run/hive"
  1. Prepare /run/hive (run as root):
sudo mkdir -p /run/hive
sudo chown -Rc hive:hive /run/hive
sudo mount -o remount,size=12G /run

Please note that aside from shared_memory.bin, Hive now also uses a comments-rocksdb-storage directory for part of the state. By default this lives alongside shared memory in the shared-file-dir (on disk), but if you move shared-file-dir to /run/hive, both shared_memory.bin and comments-rocksdb-storage will live in RAM.

Recipe 5 – Use existing block_log (faster start)

You can either:

  • use your existing block_log (recommended), or
  • download a public one (huge, but can save replay time in some setups)
wget https://gtg.openhive.network/get/blockchain/block_log -nc -P ~/datadir/blockchain
wget https://gtg.openhive.network/get/blockchain/block_log.artifacts -nc -P ~/datadir/blockchain

The block_log is very large (hundreds of GB), so downloading it can take many hours.
If you already have a block_log, definitely reuse it for upgrades.
If you don’t have one yet, with the current improvements it’s usually better to just let the node sync from the P2P network instead of downloading a fresh block_log file from a single source.

Recipe 6 – Use snapshot (fastest way to state)

Snapshot = ready-made node state from another machine.

wget https://gtg.openhive.network/get/snapshot/exchange/latest.tar.bz2 -O - \
  | lbzip2 -dc \
  | tar xvC ~/datadir/snapshot
  • Snapshot name in this recipe: latest
    (it will end up in ~/datadir/snapshot/latest)

Make sure:

  • your block_log is at least as fresh as the snapshot
  • your hived-1.28.3 and config.ini are compatible with it
    (plugins, tracked accounts, etc.)

Here compatible means: your config does not require any extra plugins or tracked accounts that were not used when the snapshot was created
(for example, using new account-history-rocksdb-track-account-range entries that weren’t present when the snapshot was made).
Having fewer plugins or a subset of tracked accounts is fine.

Recipe 7 – Adjust for specific roles

All roles use the same data dir and binary, just different config.ini.

Seed node

In ~/datadir/config.ini:

  • make sure P2P port is open and public:
p2p-endpoint = 0.0.0.0:2001

You can now start hived using Recipe 8.

Witness node

In ~/datadir/config.ini:

witness = "yourwitnessname"
private-key = 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Keep it clean and simple: comment out or remove non-essential plugins (APIs, history, etc.).

Then start hived using Recipe 8.

Exchange / personal wallet node

In ~/datadir/config.ini:

Example config.ini you've downloaded in Recipe 2 is good enough as long as your desired account(s) are already tracked.

If so, use Recipe 8a.

If you need to add any new tracked accounts to the list of tracked accounts using format:

account-history-rocksdb-track-account-range = ["mytrackedaccount","mytrackedaccount"]

you simply cannot use that snapshot anymore. In that case you must rebuild the state from scratch using your block_log (no --load-snapshot), use Recipe 8b.

Basic API node (bots, simple apps)

  • Start from example-exchange-config.ini.
  • Disable anything you don’t need (like detailed history for accounts you don’t care about).
  • Make sure HTTP/WebSocket bind addresses are what you want:
webserver-http-endpoint = 0.0.0.0:8090
webserver-ws-endpoint   = 0.0.0.0:8091

Then start hived using Recipe 8a.

Recipe 8 – Start hived (native binary)

8a) Start from snapshot (if your config is compatible)

screen -S hived
~/bin/hived-1.28.3 -d ~/datadir --load-snapshot=latest

Detach from screen with: Ctrl+a, then d
Reattach with: screen -r hived

8b) Start with replay from block_log (no snapshot)

If you don’t use a snapshot and just want to rebuild state from your block_log:

screen -S hived
~/bin/hived-1.28.3 -d ~/datadir --replay

Detach from screen with: Ctrl+a, then d
Reattach with: screen -r hived

8c) Resync from scratch (no snapshot, no block_log)

WARNING: this removes your local blockchain data (don't do that unless you want to download everything again from the P2P network).
If you are upgrading, see Recipe 9.

Before you "start from scratch", double-check your directory tree. If you really want a clean resync, make sure there are no leftovers in your data dir, especially in ~/datadir/blockchain/. Old files (like a previous monolithic block_log) can still occupy a lot of space even if they’re no longer used. When you’re sure you don’t need them anymore, rm -rf ~/datadir/blockchain/* gives you a truly empty blockchain directory to start from.

screen -S hived
~/bin/hived-1.28.3 -d ~/datadir --resync

Detach from screen with: Ctrl+a, then d
Reattach with: screen -r hived

If there is no existing state or block_log, running hived without --load-snapshot and without --replay will also effectively start resync from scratch.

Recipe 9 – Upgrading from older version to 1.28.3

Assuming you already run a node laid out like this:

  1. Stop your current hived.
  2. Keep your existing data dir (~/datadir), especially blockchain/block_log.
  3. Update binaries using Recipe 3 (download hived-1.28.3 and cli_wallet-1.28.3).
  4. Optionally download latest snapshot using Recipe 6 if you are going to use it instead of replay.

Then choose one of these paths:

  • If you use snapshots: start with Recipe 8a (--load-snapshot=latest).
  • If you don’t use snapshots but have a block_log: start with Recipe 8b (--replay).
  • If you don’t have a usable block_log (unlikely when you are upgrading): let the node sync from P2P, i.e. go with Recipe 8c (--resync).

In all cases, you reuse the same config.ini (adjusted as needed for your role).

Some upgrades don’t require replay (for example, certain bug-fix releases within the same 1.28.x line – please refer to the release notes for details).
In such case it's enough to just stop your current hived-1.28.0 and start it with hived-1.28.3 to resume its operations.
But make sure you don't use any of --load-snapshot, --force-replay, or --resync.

Part 2 – Docker recipe (Hive 1.28.3)

Same idea as Part 1, just wrapped in a container.

All assumptions from Part 1 still apply (same ~/datadir, same config.ini, optional block_log and snapshot).
Additionally we assume:

  • Docker is installed and user hive can run docker.

Recipe 10 – Run Hive 1.28.3 in Docker

Most common Docker run (seed + basic API), using your existing /home/hive/datadir from Part 1:

docker run \
  -e HIVED_UID=$(id -u) \
  -p 2001:2001 \
  -p 8090:8090 \
  -p 8091:8091 \
  -v /home/hive/datadir:/home/hived/datadir \
  hiveio/hive:1.28.3 \
  --set-benchmark-interval=100000 \
  --load-snapshot=latest \
  --replay

What this does:

  • runs image hiveio/hive:1.28.3
  • maps your host /home/hive/datadir to /home/hived/datadir inside the container
  • exposes ports 2001, 8090, 8091 from the container to the host
  • uses your user ID inside the container (HIVED_UID=$(id -u)) so files created by hived are owned by hive on the host
  • tells hived to:
    • use /home/hived/datadir/snapshot/latest as the snapshot (--load-snapshot=latest)
    • rebuild state, combining snapshot and block_log as needed (--replay)
    • report periodic benchmark info (--set-benchmark-interval=100000)

You still need:

  • config.ini inside /home/hive/datadir (on the host)
  • block_log, andblock_log.artifacts (unless pruned) and snapshot, exactly like in the bare-metal recipes

For simpler cases:

  • if you don’t want to use a snapshot, drop --load-snapshot=latest (keep --replay or --force-replay if you want a full replay from block_log)
  • if you already have a healthy state and just want to restart, drop both --load-snapshot=latest and --replay

Adjust ports / extra flags to match your intended role (seed / witness / exchange / wallet / API), using the same config.ini rules as in Part 1.

TL;DR – "Complete simple recipe" (native binary)

If you just want one long paste (native binary, default config, download block_log, use snapshot):

screen -S hived
mkdir -pv ~/datadir/{blockchain,snapshot} ~/bin

wget https://gtg.openhive.network/get/bin/hived-1.28.3 -nc -P ~/bin
wget https://gtg.openhive.network/get/bin/cli_wallet-1.28.3 -nc -P ~/bin

chmod u+x ~/bin/{hived,cli_wallet}-1.28.3

wget https://gtg.openhive.network/get/blockchain/block_log -nc -P ~/datadir/blockchain
wget https://gtg.openhive.network/get/blockchain/block_log.artifacts -nc -P ~/datadir/blockchain
wget https://gtg.openhive.network/get/snapshot/exchange/latest.tar.bz2 -O - | \
  lbzip2 -dc | tar xvC ~/datadir/snapshot

# that will overwrite your config
wget https://gtg.openhive.network/get/snapshot/exchange/example-exchange-config.ini \
  -O ~/datadir/config.ini

~/bin/hived-1.28.3 -d ~/datadir --load-snapshot=latest

Estimated times (very rough)

  • Sync from scratch – long (a day, or two)
  • Replay with existing block_log – roughly half that
  • Load snapshot (existing block_log or pruned) – up to an hour

Congratulations, you have your Hive HF28 node running (or at least a copy-paste away).

hivepressure dev witness-category hive doc faq
0
0
0.000
34 comments
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

0
0
0.000
Reply
avatar

Hope you catch the 1st block at hf28

0
0
0.000
Reply
avatar

Haha, thanks, but no need, I did that for THE FORK (when the Hive was born) so I'm more than happy with this kind of achievements ;-)

0
0
0.000
Reply
avatar

Hoping that more stuff be build on Hive.

0
0
0.000
Reply
avatar

This is an excellent and very clear guide for setting up a Hive HF28 node. The step-by-step recipes for different node types (seed, witness, wallet, API) are especially helpful, and I appreciate the tips on snapshots, block_log reuse, and Docker setup. Great work making it easy for both beginners and experienced users to get a node running efficiently!

0
0
0.000
Reply
avatar

That sounds sooooo fake

0
0
0.000
Reply
avatar

I really like the video; I wish I could create something like that. However, my skills lie more in vegetables and gardening. Good luck to everyone involved in the ranking.

0
0
0.000
Reply
avatar

Will we feel the HF? I mean will there be halt to the dApps?

0
0
0.000
Reply
avatar

Can you feel it? ;-)

0
0
0.000
Reply
avatar

Huh? is it done? LOL didn't felt anything

0
0
0.000
Reply
avatar

See? :-) flawless victory! ;-)

0
0
0.000
Reply
avatar

countdown is gone, so it already happened. cheers man!

smooth HF

image.png

0
0
0.000
Reply
avatar

So. When explosion?

0
0
0.000
Reply
avatar

I'm sorry to disappoint you.. ;-)

0
0
0.000
Reply
avatar
(Edited)

Came to watch the fireworks but all I got was, it works.

Good job, everyone.

0
0
0.000
Reply
avatar

Seems all your testing worked well!

I still think to run such docker on a Synology RS1619xs+

Do you see any issues?

Might need a SSD or NVME - but it is black week

0
0
0.000
Reply
avatar

Wow!

Performance report (total). Blocks: 101240373. Elapsed time: 42386318 ms (real), 51344322 ms (cpu). Memory usage: 12638244 (current), 13218128 (peak) kilobytes. Free space in SHM: 4181002 kilobytes.

42386 seconds is 11 hours and a bit short of 47 minutes. For a replay from scratch to over 101M, no RAM disk, 8GB SHM and block log on an external USB-C HDD.
Looks like number of blocks grows but the time to replay shrinks :o)

0
0
0.000
Reply
avatar

I have an interesting one, resync from scratch with checkpoint at 101M
exact same hardware, same software, same datacenter, same rack, same switch
and even sync started at the exact same time
68315 2025-11-20T10:39:31.750 database.cpp:5937 apply_hardfork ] HARDFORK 28 at block 101319928
vs
65696 2025-11-20T09:55:52.858 database.cpp:5937 apply_hardfork ] HARDFORK 28 at block 101319928
Full resync took 18-19 hours more or less.. but the thing is that the difference is so big:
43m39s (4%)

Two facotors that comes to my mind: difference between wear of disks (those are far from being bran new, so it might be significant at this point), and the other - difference in "luck" when it comes to finding optimal peers.

0
0
0.000
Reply
avatar

Update to myself: I just ran replay on those two machines and it was:
58553
vs
58266
So still one is consistently slower, but by a very small amount (just 4m47s = 0.5%)

0
0
0.000
Reply
avatar
(Edited)

Sorry

0
0
0.000
Reply
avatar

You’re posting a price rant under a technical guide for running a Hive node. That’s off-topic and doesn’t add anything to the discussion.

Hive is an opt-in, stake-based system where content is evaluated by upvotes and downvotes by design. That’s how it has worked from the start.

If you don’t like how this chain works or where it’s going, that’s entirely your choice, but then the straightforward option is to use a different platform, not to hang around here trying to spoil it for people who are actually building and running infrastructure.

0
0
0.000
Reply
avatar

With 8GB of physical RAM it might be better to move the comments-rocksdb-storage back to a regular drive from the ramdisk, but it's hard to tell without testing. The physical size of shared memory plus the comments db is about 10GB.

0
0
0.000
Reply
avatar

Witness:

3.9G    /run/hive/comments-rocksdb-storage
3.8G    /run/hive/shared_memory.bin
7.7G    total

Exchange:

1.6G    /run/hive/account-history-rocksdb-storage
3.9G    /run/hive/comments-rocksdb-storage
4.9G    /run/hive/shared_memory.bin
11G total

Could be, I've tested it, but on machines with bigger amount of RAM. As long as the kernel has enough memory you don't even need to explicitly tie shared_memory.bin to RAM, as it will handle cache pretty well. As for the rocksdb (both account history in case of exchanges, and comments for all the nodes), it usually makes a better use of that memory than "wasting" it for database storage. To a large extent it depends on a performance ratio between RAM and storage.

0
0
0.000
Reply
avatar

Interesting. I'm seeing 4.1G for comments (and more for shared_memory but I have a few extra plugins so that's explainable). Not sure why.

0
0
0.000
Reply
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

0
0
0.000
Reply
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)

#bilpcoin

0
0
0.000
Reply
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)

#bilpcoin exposed #buildawhalescam #buildawhalefarm #themarkymarkscam #themarkymarkfarm #hurtlockerscam #hurtlockerfarm #acidyoscam #acidyofarm #jacobtothescam #hivepopescam

0
0
0.000
Reply