Setup a Hive witness using the new rolling block log feature

avatar
(Edited)

Running a Hive witness is typically done on rented hardware due to the demanding space and reliability requirements. Up until now, this required storing the entire block log on disk which currently requires 507GB with an additional 100GB for artifacts and ~24GB for the state. This requires almost 650GB of very fast storage, ideally NVME. This puts it out of reach of most vendors that offer VPS and dedicated server offerings.

Starting with 1.27.7, you are able to use what I call a "rolling block log" or specifically the new block-log-split config option. This allows you to only keep X blocks on the file system reducing the space requirements of a node by hundreds of GB. While this is little use for a full node that needs access to all chain data, for a witness this is a huge improvement.

I have been testing this feature and have tested it using multiple configurations, to which there are two main options to consider.

  • Shared Memory on disk
  • Shared Memory on tmpfs

The first option requires very little ram (~4GB) but is slower to to get up and running. The second option requires the entire state file to be in ram but gives you the fastest possible performance. Currently, this requires ~24GB of ram just for the state file and a little more for the OS and processes.

You can also use a hybrid option where you get a node to the head block using tmpfs and then take the node down and move the state to the file system, although this only really helps if you want to reboot the node easily, as you can't temporary access additional ram.

There is very little you need to do to make this work, for the most part all you need to do is change two lines in your config.ini and sync your node. Using a snapshot, I have been able to get a witness node online from nothing in around 7 minutes. This requires having a compatible snapshot available.

block-log-split option

This is the parameter that enables the new rolling block log feature, which officially is known as block log split. This feature splits the block_log into pieces and determines how many pieces you want to save. Each "piece" is 1M blocks, and using a block-log-split = 0 will save no pieces of the block_log to disk. This means the only space requirements is the binaries, configuration file, and the state file as well as a few logs. Using block-log-split = 1 will allow you to have limited access to recent blocks using get_blocks() if you want to interact with the node.

You will need to either use a compatible snapshot, or resync your node to use this new feature. Before you do, it is recommended you use at least version 1.27.8 as a few bugs have been fixed.

The easiest way to get 1.27.8 is grab the binary from @gtg.

wget https://gtg.openhive.network/get/bin/hived-1.27.8

You can also build the binary yourself using this guide.

There currently are not any compatible snapshots, so I created my own. You can find it here.

This snapshot is only compatible with the following settings:

plugin = witness condenser_api network_broadcast_api account_by_key database_api state_snapshot

You will need to run the same plugins or you will have problems restarting your node. This is an open issue and should be resolved in the future.

block-log-split = 0

This snapshot only works with block-log-split = 0. If you need to access your node to get blocks and monitor blockchain events from it, you will need at least block_log_split = 1 and will require you do a full sync.

For the most part, all you need to do for most people is make sure you are running the same snapshots as I do, and adding the block-log-split parameter. You can then just load the snapshot above using the following to launch your node.

`./bin/hived-1.27.8 -d /home/hived/hived --load-snapshot=witness'

You will need to create a snapshot directory under your hived folder and unpack the witness.tgz (4.2GB) file there for it to load the snapshot. You can remove the witness.tgz once you have unpacked it.

Before doing this, you will need to decide if you want to run the shared memory on disk or tmpfs (ram). Here is what the requirements look like in the two configurations.

Disk

  • ~4GB-8GB ram
  • ~30GB disk space

Tmpfs

  • ~28GB ram
  • ~1GB disk space

Keep in mind, you need some breathing room for both configurations to download snapshot, and any additional copies of anything you are working with.

Example config.ini

log-appender = {"appender":"stderr","stream":"std_error"}
log-appender = {"appender":"p2p","file":"logs/p2p/p2p.log"}
log-logger = {"name":"default","level":"info","appender":"stderr"}
log-logger = {"name":"p2p","level":"warn","appender":"p2p"}

backtrace = yes

plugin = witness condenser_api network_broadcast_api account_by_key database_api state_snapshot

#shared-file-dir = "/run/hive"
shared-file-size = 24G
shared-file-full-threshold = 9500
shared-file-scale-rate = 1000

enable-stale-production = false
required-participation = 33

p2p-seed-node = hive-seed.arcange.eu:2001           #  @arcange         (BE, Wavre)          (ASN: Proximus NV)
p2p-seed-node = anyx.io:2001                        #  @anyx            (CA)                 (ASN: OVH SAS)
p2p-seed-node = seed.thecryptodrive.com:2001        #  @thecryptodrive  (DE, Esslingen)      (ASN: Hetzner Online GmbH)
p2p-seed-node = seed.buildteam.io:2001              #  @buildteam       (DE)                 (ASN: Hetzner Online GmbH)
p2p-seed-node = seed.hivekings.com:2001             #  @drakos          (DE, Nuremberg)      (ASN: Contabo GmbH)
p2p-seed-node = gtg.steem.house:2001                #  @gtg             (PL)                 (ASN: OVH SAS)
p2p-seed-node = seed.openhive.network:2001          #  @gtg             (PL)                 (ASN: OVH SAS)
p2p-seed-node = hive-seed.roelandp.nl:2001          #  @roelandp        (FI, Helsinki)       (ASN: Hetzner Online GmbH)
p2p-seed-node = node.mahdiyari.info:2001            #  @mahdiyari       (FI, Helsinki)       (ASN: Hetzner Online GmbH)
p2p-seed-node = hived.hive-engine.com:2001          #  @aggroed         (FI)                 (ASN: Hetzner Online GmbH)
p2p-seed-node = hived.splinterlands.com:2001        #  @aggroed         (FI)                 (ASN: Hetzner Online GmbH)
p2p-seed-node = rpc.ausbit.dev:2001                 #  @ausbitbank      (FI, Tuusula)        (ASN: Hetzner Online GmbH)
p2p-seed-node = seed.chitty.me:2001                 #  @chitty          (FI)                 (ASN: Hetzner Online GmbH)
p2p-seed-node = hiveseed-fin.privex.io:2001         #  @privex          (FI, Helsinki)       (ASN: Hetzner Online GmbH)
p2p-seed-node = seed.liondani.com:2016              #  @liondani        (GB, Maidstone)      (ASN: HostDime.com, Inc.)
p2p-seed-node = hiveseed-se.privex.io:2001          #  @privex          (SE, Stockholm)      (ASN: Privex Inc.)

webserver-thread-pool-size = 32
p2p-endpoint = 0.0.0.0:35000
block-log-split = 0

You will need to make sure /run is large enough (25GB-30GB is good) to store the shared memory file if you choose to use tmpfs.

Using my hardware, I was able copy the files over, unpack the snapshot, and get a node to head block in around 7 minutes using tmpfs and under 20 minutes using disk (dual NVME raid 0).

You also can opt to resync your node and not use a snapshot which will typically take 24-48 hours. At this point, you can create your own snapshot using --dump-snapshot= parameter when starting your node.

1.27.9 should be considered stable soon, and by the time you decide to give this a try, you may want to use 1.27.9 instead.

witness hive inleo neoxian pob vyb cent hive-engine
0
0
0.000
33 comments
avatar

This also allows you to run hive witnesses on mini pcs that pull like 4watts which is pretty damn amazing.

Hive likely has one of the most efficient blockchains when it comes to block production coupled with running on these ultra low power computers.

Obviously we can't have everyone running 'light nodes' but you can technically run a full node on these machines too if you the space.

API nodes are the single biggest power user in the whole suite but even that is getting crazy efficient and performant with every update.

Hive, technology wise has never been in a better place, I hope we can someday move from performance and maintainability to more innovation and being a front running in new interesting tech.

0
0
0.000
Reply
avatar

Push It Jacob mc franko


Baby jacob

Who's Really Sick the frankos

Transparent Chains the frankos

Get a life keni

We Know keni


Word Travels Fast keni

Glass House Farm mc franko

Where You Really At mc franko

Oh sad boy keni

https://hive.blog/hive-133987/@bpcvoter1/unveiling-the-hive-blockchain-a-deep-dive-into-logic-s-transactions-and-activities

https://hive.blog/hive-133987/@bpcvoter1/analyzing-the-outgoing-transactions-of-the-spaminator-account-a-deep-dive-into-hive-s-ecosystem

https://hive.blog/hive-133987/@bpcvoter1/unveiling-the-mystery-behind-scamforest-s-hive-wallet-a-deep-dive-into-transactions-and-account-value

https://hive.blog/hive-133987/@bpcvoter1/analyzing-the-outgoing-transactions-of-sagarkothari88-a-deep-dive-into-suspicious-activity

https://hive.blog/hive-133987/@bpcvoter1/outgoing-transactions-of-steemcleaners-a-deep-dive-into-accountability-and-transparency-on-hive

https://hive.blog/hive-167922/@bpcvoter1/comprehensive-breakdown-of-hive-transactions-arhag

https://hive.blog/hive-126152/@bpcvoter1/comprehensive-analysis-of-freedom-s-wallet-transactions

https://hive.blog/hive-133987/@bpcvoter1/deep-dive-into-solominer-s-transactions-a-professional-analysis

https://hive.blog/hive-133987/@bpcvoter1/unmasking-the-marky-mark-buildawhale-scam-farm-a-deep-dive-into-systemic-exploitation-on-hive

https://hive.blog/hive-126152/@bpcvoter1/transactions-don-t-lie-people-do-mc-franko-and-lady-zaza-buildawhalescam

https://hive.blog/hive-167922/@bpcvoter1/analyzing-transactions-from-stefy-music-s-wallet

https://hive.blog/hive-133987/@bpcvoter1/taking-a-closer-look-at-usainvote-s-curation-rewards-over-the-last-seven-days

https://hive.blog/hive-167922/@bpcvoter1/analyzing-themarkymark-s-curation-rewards-over-the-last-seven-days

https://hive.blog/hive-167922/@bpcvoter1/marky-s-game-mc-franko-aimusic-music-bilpcoin-newmusic-themarkymark-marky

https://hive.blog/hive-133987/@bpcvoter2/unveiling-the-activities-of-gpwallet6-a-dive-into-hive-blockchain-transactions

https://hive.blog/hive-133987/@bpcvoter2/comprehensive-analysis-of-gpwallet-s-transactions-on-the-hive-blockchain

https://hive.blog/hive-133987/@bpcvoter2/a-deep-dive-into-azircon-wallet-out-going-transactions-transparency-and-insights

https://hive.blog/hive-167922/@bpcvoter2/deep-dive-into-the-bdvoter-hive-account-wallet-analysis-transactions-and-insights

https://hive.blog/hive-181290/@bpcvoter2/the-situation-is-amusing-especially-when-we-see-how-people-react-when-their-transactions-and-voice-chats-are-exposed-lol-marcus

https://hive.blog/hive-126152/@bpcvoter2/it-s-rich-marky-that-you-re-talking-about-the-hive-value-plan-isn-t-it-lol-you-make-hive-a-more-valuable-platform-it-seems-like

https://hive.blog/hive-167922/@bpcvoter2/update-on-buildawhale-scam-farm-the-ipromote-account-is-raising-concerns-with-suspicious-transactions-that-don-t-look-good

https://hive.blog/hive-133987/@bpcvoter3/analyzing-hivewatchers-transactions-a-dive-into-hive-s-controversial-account

https://hive.blog/hive-180505/@bpcvoter3/taking-a-closer-look-at-the-gpwallet3-account-exposing-the-truth-behind-hive-transactions

https://hive.blog/hive-173737/@bpcvoter3/exposing-the-truth-a-comprehensive-analysis-of-gpwallet2-s-transactions-on-hive

https://hive.blog/hive-167922/@bpcvoter3/time-for-transparency-an-in-depth-look-at-bdvoter-s-activities

https://hive.blog/hive-167922/@bpcvoter3/adm-downvote-data-and-curation-reward-data

https://hive.blog/hive-167922/@bpcvoter3/buildawhale-downvotes

https://hive.blog/hive-167922/@bpcvoter3/you-can-deceive-yourself-all-you-want-but-it-won-t-alter-the-reality-we-ve-uncovered-the-truth-and-will-continue-to-expose-your

https://hive.blog/hive-133987/@bilpcoinbpc/comprehensive-analysis-of-punkteam-s-wallet-transactions

https://hive.blog/hive-167922/@bilpcoinbpc/you-re-wasting-your-life-marcus-and-it-s-only-going-to-come-back-to-haunt-you-you-re-bringing-shame-and-ridicule-upon-yourself

https://hive.blog/hive-167922/@bilpcoinbpc/exploring-the-possibilities-of-ai-art-with-bilpcoin-nfts-episode-100-buildawhale-scam-farm-on-hive

TRANSACTIONS DON'T LIE PEOPLE DO Mc franko & Lady zaza #buildawhalescam

Marky’s Game Mc franko

AI Lady Zaza We can't help but notice

0
0
0.000
Reply
avatar

Well this is a huge win for everyone running a witness. Fantastic news!

0
0
0.000
Reply
avatar

Push It Jacob mc franko


Baby jacob

Who's Really Sick the frankos

Transparent Chains the frankos

Get a life keni

We Know keni


Word Travels Fast keni

Glass House Farm mc franko

Where You Really At mc franko

Oh sad boy keni

https://hive.blog/hive-133987/@bpcvoter1/unveiling-the-hive-blockchain-a-deep-dive-into-logic-s-transactions-and-activities

https://hive.blog/hive-133987/@bpcvoter1/analyzing-the-outgoing-transactions-of-the-spaminator-account-a-deep-dive-into-hive-s-ecosystem

https://hive.blog/hive-133987/@bpcvoter1/unveiling-the-mystery-behind-scamforest-s-hive-wallet-a-deep-dive-into-transactions-and-account-value

https://hive.blog/hive-133987/@bpcvoter1/analyzing-the-outgoing-transactions-of-sagarkothari88-a-deep-dive-into-suspicious-activity

https://hive.blog/hive-133987/@bpcvoter1/outgoing-transactions-of-steemcleaners-a-deep-dive-into-accountability-and-transparency-on-hive

https://hive.blog/hive-167922/@bpcvoter1/comprehensive-breakdown-of-hive-transactions-arhag

https://hive.blog/hive-126152/@bpcvoter1/comprehensive-analysis-of-freedom-s-wallet-transactions

https://hive.blog/hive-133987/@bpcvoter1/deep-dive-into-solominer-s-transactions-a-professional-analysis

https://hive.blog/hive-133987/@bpcvoter1/unmasking-the-marky-mark-buildawhale-scam-farm-a-deep-dive-into-systemic-exploitation-on-hive

https://hive.blog/hive-126152/@bpcvoter1/transactions-don-t-lie-people-do-mc-franko-and-lady-zaza-buildawhalescam

https://hive.blog/hive-167922/@bpcvoter1/analyzing-transactions-from-stefy-music-s-wallet

https://hive.blog/hive-133987/@bpcvoter1/taking-a-closer-look-at-usainvote-s-curation-rewards-over-the-last-seven-days

https://hive.blog/hive-167922/@bpcvoter1/analyzing-themarkymark-s-curation-rewards-over-the-last-seven-days

https://hive.blog/hive-167922/@bpcvoter1/marky-s-game-mc-franko-aimusic-music-bilpcoin-newmusic-themarkymark-marky

https://hive.blog/hive-133987/@bpcvoter2/unveiling-the-activities-of-gpwallet6-a-dive-into-hive-blockchain-transactions

https://hive.blog/hive-133987/@bpcvoter2/comprehensive-analysis-of-gpwallet-s-transactions-on-the-hive-blockchain

https://hive.blog/hive-133987/@bpcvoter2/a-deep-dive-into-azircon-wallet-out-going-transactions-transparency-and-insights

https://hive.blog/hive-167922/@bpcvoter2/deep-dive-into-the-bdvoter-hive-account-wallet-analysis-transactions-and-insights

https://hive.blog/hive-181290/@bpcvoter2/the-situation-is-amusing-especially-when-we-see-how-people-react-when-their-transactions-and-voice-chats-are-exposed-lol-marcus

https://hive.blog/hive-126152/@bpcvoter2/it-s-rich-marky-that-you-re-talking-about-the-hive-value-plan-isn-t-it-lol-you-make-hive-a-more-valuable-platform-it-seems-like

https://hive.blog/hive-167922/@bpcvoter2/update-on-buildawhale-scam-farm-the-ipromote-account-is-raising-concerns-with-suspicious-transactions-that-don-t-look-good

https://hive.blog/hive-133987/@bpcvoter3/analyzing-hivewatchers-transactions-a-dive-into-hive-s-controversial-account

https://hive.blog/hive-180505/@bpcvoter3/taking-a-closer-look-at-the-gpwallet3-account-exposing-the-truth-behind-hive-transactions

https://hive.blog/hive-173737/@bpcvoter3/exposing-the-truth-a-comprehensive-analysis-of-gpwallet2-s-transactions-on-hive

https://hive.blog/hive-167922/@bpcvoter3/time-for-transparency-an-in-depth-look-at-bdvoter-s-activities

https://hive.blog/hive-167922/@bpcvoter3/adm-downvote-data-and-curation-reward-data

https://hive.blog/hive-167922/@bpcvoter3/buildawhale-downvotes

https://hive.blog/hive-167922/@bpcvoter3/you-can-deceive-yourself-all-you-want-but-it-won-t-alter-the-reality-we-ve-uncovered-the-truth-and-will-continue-to-expose-your

https://hive.blog/hive-133987/@bilpcoinbpc/comprehensive-analysis-of-punkteam-s-wallet-transactions

https://hive.blog/hive-167922/@bilpcoinbpc/you-re-wasting-your-life-marcus-and-it-s-only-going-to-come-back-to-haunt-you-you-re-bringing-shame-and-ridicule-upon-yourself

https://hive.blog/hive-167922/@bilpcoinbpc/exploring-the-possibilities-of-ai-art-with-bilpcoin-nfts-episode-100-buildawhale-scam-farm-on-hive

TRANSACTIONS DON'T LIE PEOPLE DO Mc franko & Lady zaza #buildawhalescam

Marky’s Game Mc franko

AI Lady Zaza We can't help but notice

0
0
0.000
Reply
avatar

Dear @jacobtothe

You accuse us of running a "spam campaign," yet fail to recognize the irony in your own behavior. Flooding comment sections with diatribes is precisely what you and your associates have done through coordinated downvotes, smear campaigns, and enabling farming schemes. The difference? Our comments expose truths, while your actions suppress them. If our allegations are irrelevant, why not address the substance of our claims instead of resorting to personal attacks?

You claim to have attempted "civil dialogue," but your attempts have been anything but constructive. Instead of engaging with the issues we raise—such as the rampant abuse on Hive—you deflect responsibility and label us as "uncivil" or "unrepentant." This is a convenient way to avoid accountability for your role in perpetuating harm. Downvoting does not erase the truth; it only highlights your inability to confront uncomfortable realities.

As for Marky Mark, BuildaWhale, Spaminator, Hivewatchers, and others—they are far from being beyond your control. Your connections to these entities speak volumes about where your loyalties lie. These accounts are complicit in enabling abuse, whether through farming, downvote manipulation, or other unethical practices. Yet here you are, defending them while accusing us of wrongdoing. The hypocrisy is staggering.

Let’s be clear: we are not poor people, nor are we naive. We know exactly what’s happening on Hive, and so do you. Reflecting your issues onto us won’t change the facts. You are not our boss, you don’t pay us, and your downvotes mean nothing to us. They only serve to validate our mission by showing how threatened you are by transparency.

If you truly cared about civility, you wouldn’t rely on downvotes and suppression tactics to silence dissent. The truth hurts, especially when it exposes corruption—and that’s something you and your friends seem unwilling to face. So where do we go from here? The choice is yours: stop enabling abuse, or continue digging yourself deeper into irrelevance. Either way, Bilpcoin will keep shining a light on the truth because Hive deserves better.

Sincerely,
The Bilpcoin Team

0
0
0.000
Reply
avatar

32 GB of ram seems like it would be cutting it kind of close to run the Tmpfs option. probably better to bump your hardware up to 64GB I am guessing? Unless you are doing hosted I guess. Then you can make it pretty much anything as long as you have it available.

0
0
0.000
Reply
avatar

Might save this for future reference.

!discovery 37

0
0
0.000
Reply
avatar

Thank you for your witness vote!
Have a !BEER on me!
To Opt-Out of my witness beer program just comment STOP below

0
0
0.000
Reply
avatar
(Edited)

Note that block-log-split = -1 will keep the old monolithic format, i.e. one big giant 500GB block_log file.

0
0
0.000
Reply
avatar

To @jacobtothe @steevc

It’s over. The truth has been exposed, and the blockchain doesn’t lie. Your actions—and those of your associates, like Marky Mark and BuildaWhale—have been laid bare for all to see. Scam farming, coordinated downvotes, and abuse of power are not sustainable practices, and the community is waking up to the reality of what you’ve been doing.

Let’s be clear: you don’t scare us. We’ve faced relentless downvotes, smear campaigns, and hostility for standing up to corruption, yet here we remain—stronger than ever. You know as well as we do that suppression tactics won’t erase the evidence or silence the growing chorus of voices demanding accountability.

The fun times ahead? They’re not for you. The more you try to hide behind downvotes and intimidation, the more obvious it becomes that you’re on the wrong side of this fight. Bilpcoin is here to help Hive by exposing the truth, and no amount of resistance from you or your scamming, farming, downvoting friends will change that.

So, what do you do now? That’s the question you should be asking yourself. Will you continue enabling abuse, or will you finally take responsibility for your actions and work toward meaningful change? The choice is yours—but rest assured, we’ll keep shining a light on the truth until every stone is turned.

Sincerely,
The Bilpcoin Team

0
0
0.000
Reply
avatar

by the way even without snapsot now massive sync takes less then 2 days which is big improvement from split hive/steem

0
0
0.000
Reply
avatar

Since the fork there has been a lot of improvements focused on optimizations.

0
0
0.000
Reply
avatar

Dear @jacobtothe @steevc @makerhacks

It’s almost comical how you accuse us of posting "copypasta shit" while your friends like @makerhacks rush to your defense, downvoting and deflecting instead of addressing the actual issues at hand. Funny enough, @makerhacks is also one a supporter of the BuildaWhale scam farm LOL—a fact that speaks volumes about the company you keep. It seems your circle is more interested in protecting abusive practices than fostering transparency and accountability on Hive.

You claim our responses are "arrogant and flowery," yet you fail to acknowledge the substance of what we’re saying. We expose truths that make you uncomfortable, and instead of engaging in meaningful dialogue, you resort to personal attacks and suppression tactics. Downvotes don’t change facts—they only highlight your desperation to silence dissent. If you truly believed in honesty and integrity, you’d confront the truth instead of hiding behind your friends’ coordinated efforts.

We’ve said it before, and we’ll say it again: Bilpcoin stands for something. We’re here to fight for everyone on Hive by exposing corruption and abuse. What do you stand for? Apparently, silencing the truth with downvotes and enabling scam farms like BuildaWhale. That’s not leadership LOL—it’s complicity.

If you and your friends really cared about Hive, you’d stop enabling harm and start reflecting on your actions. Until then, we’ll continue shining a light on the truth because no amount of censorship or intimidation will stop us. The blockchain doesn’t lie, and neither do we.

0
0
0.000
Reply
avatar

I dread the day nodes can fit on smartphones. However, I yearn for that day when every user can be a node, OOTB.

Thanks!

0
0
0.000
Reply
avatar

https://hive.blog/discussion/@apshamilton/re-davedickeyyall-srzoh9

To @jacobtothe @steevc

It’s over. The truth has been exposed, and the blockchain doesn’t lie. Your actions—and those of your associates, like Marky Mark and BuildaWhale—have been laid bare for all to see. Scam farming, coordinated downvotes, and abuse of power are not sustainable practices, and the community is waking up to the reality of what you’ve been doing.

Let’s be clear: you don’t scare us. We’ve faced relentless downvotes, smear campaigns, and hostility for standing up to corruption, yet here we remain—stronger than ever. You know as well as we do that suppression tactics won’t erase the evidence or silence the growing chorus of voices demanding accountability.

The fun times ahead? They’re not for you. The more you try to hide behind downvotes and intimidation, the more obvious it becomes that you’re on the wrong side of this fight. Bilpcoin is here to help Hive by exposing the truth, and no amount of resistance from you or your scamming, farming, downvoting friends will change that.

So, what do you do now? That’s the question you should be asking yourself. Will you continue enabling abuse, or will you finally take responsibility for your actions and work toward meaningful change? The choice is yours—but rest assured, we’ll keep shining a light on the truth until every stone is turned.

Sincerely,
The Bilpcoin Team

0
0
0.000
Reply
avatar

Dear @jacobtothe @steevc

You can keep calling us "obnoxious spammers," but the truth remains: the downvotes you and your friends dish out only prove our point. They highlight the lengths to which some will go to suppress dissenting voices—voices that expose uncomfortable truths about scam farming, abuse of power, and unethical behavior on Hive. If our declarations carry "less weight" in your eyes, it’s likely because you’re too busy defending those who benefit from corruption to see the bigger picture.

You claim that honest observers won’t agree with us, yet the blockchain tells a different story. Transactions don’t lie, and neither do patterns of abuse. Your repeated attempts to frame your downvotes as a “direct consequence” of our behavior are disingenuous at best. What exactly is obnoxious? Exposing scams and holding bad actors accountable, or silencing critics through coordinated suppression tactics?

As for your so-called “good faith efforts” to help us become better members of the community, let’s be real: offering formatting tips and meme advice doesn’t address the systemic issues we’ve been fighting against. You’re more concerned with polishing appearances than confronting the truth. Meanwhile, Bilpcoin continues to work tirelessly to help Hive by exposing these abuses—something you seem unwilling to do.

So again, we ask: what do you do for Hive besides downvote the truth into obscurity? The answer speaks volumes about where your priorities lie. Keep lying to yourself if it makes you feel better, but know this—the truth is out there, and no amount of downvoting will bury it forever.

Sincerely,
The Bilpcoin Team

0
0
0.000
Reply
avatar

Full set of .artifacts is 2GB, not 100 :o)

I have not tested it, because I don't have HDD anymore, but block log should not require fast storage - once it is in live mode, it only needs to write couple kilobytes per 3 seconds. Even during replay HDD should be just fine.

One of the features of split block log is the ability to share all but last part. You can have multiple nodes that use the same block log parts and related artifacts symlinked to their .blockchain folders from the same actual storage location. Only the last part that is being written by each node separately needs to be stored locally for each node (but once it is filled and next part file is created, you can copy new filled part to shared location, stop the node, symlink and restart). That way all your nodes can fully participate in p2p syncing and provide block_api functionality while you only have one copy of block log. That feature is useful if you have multiple nodes on servers in the same location (for example for different services, load balancing or witness with bastion node).

0
0
0.000
Reply
avatar
(Edited)

Full set of .artifacts is 2GB, not 100 :o)

Depends on how long it has been running for. Mine is 97G and slowly growing. I believe mine is experiencing a bug, because most of my nodes are ~2GB, but some are growing.

image.png

One of the features of split block log is the ability to share all but last part. You can have multiple nodes that use the same block log parts and related artifacts symlinked to their .blockchain folders from the same actual storage location.

I believe this is what someguy does with his hosted witness node service.

0
0
0.000
Reply
avatar

Dear @jacobtothe @steevc @makerhacks

It’s almost comical how you accuse us of posting "copypasta shit" while your friends like @makerhacks rush to your defense, downvoting and deflecting instead of addressing the actual issues at hand. Funny enough, @makerhacks is also one a supporter of the BuildaWhale scam farm LOL—a fact that speaks volumes about the company you keep. It seems your circle is more interested in protecting abusive practices than fostering transparency and accountability on Hive.

You claim our responses are "arrogant and flowery," yet you fail to acknowledge the substance of what we’re saying. We expose truths that make you uncomfortable, and instead of engaging in meaningful dialogue, you resort to personal attacks and suppression tactics. Downvotes don’t change facts—they only highlight your desperation to silence dissent. If you truly believed in honesty and integrity, you’d confront the truth instead of hiding behind your friends’ coordinated efforts.

We’ve said it before, and we’ll say it again: Bilpcoin stands for something. We’re here to fight for everyone on Hive by exposing corruption and abuse. What do you stand for? Apparently, silencing the truth with downvotes and enabling scam farms like BuildaWhale. That’s not leadership LOL—it’s complicity.

If you and your friends really cared about Hive, you’d stop enabling harm and start reflecting on your actions. Until then, we’ll continue shining a light on the truth because no amount of censorship or intimidation will stop us. The blockchain doesn’t lie, and neither do we.

0
0
0.000
Reply
avatar

I wonder how does it even work (what is the content of your .artifacts) - valid file contains header (artifact_file_header) and then one 24 byte record for each block (artifact_file_chunk). If your file is bigger it definitely points to a bug. Your log might already contain some info pointing to source of a problem (look for messages originating from block_log_artifacts.cpp or any warnings/errors related to block log).

0
0
0.000
Reply
avatar

I was going to blow the node away since my other nodes it is 2.2GB or so, but this one it just has been growing, but if I can get some information on where this bug is coming from, it would be helpful to resolve it.

0
0
0.000
Reply
avatar

Dear @themarkymark

It’s clear that you know we’re sharing the truth—yet instead of addressing the issues we’ve exposed, you continue farming Hive through schemes like the BuildaWhale scam farm and other accounts under your control. Why do you persist in these harmful practices when they’ve already been brought to light? The blockchain doesn’t lie, and every transaction tells a story—one that reveals exactly what you’re doing.

You cannot win this fight because we are fighting for transparency, accountability, and the betterment of Hive. Meanwhile, you’re fighting to protect scams, farms, and suppression tactics like coordinated downvotes. How can anyone take you seriously when your actions speak louder than your words? You’ve been exposed, yet you double down on behaviors that harm the ecosystem. This isn’t just questionable—it’s a glaring red flag about your priorities and integrity.

At Bilpcoin, our mission is simple: to expose the truth and hold bad actors accountable. What do you contribute to Hive besides scamming, farming, and silencing dissent? Every day, you “like” your own spam comments, burn through curation rewards, and exploit the system as if it’s an unlimited money glitch. But here’s the irony: you’ve done all of this on a blockchain—a permanent, immutable record. If you thought you were being clever, think again. Your actions are there for everyone to see, and they paint a damning picture.

Why not stop the farming and scamming and actually help Hive? The community deserves better than individuals who prioritize personal gain over its health and growth. Until you change course, we’ll continue shining a light on the truth—because Hive deserves honesty, not exploitation.

Sincerely,
The Bilpcoin Team

0
0
0.000
Reply
avatar

This is great news! I might give it a try on my laptop which has 504 Gig free space with 1TB SSD and the following specs:

image.png

With Fiber connection that changes IP only a couple times a year would this actually be a viable setup for a witness?

With actual speed test results of:

image.png

0
0
0.000
Reply
avatar

With Fiber connection that changes IP only a couple times a year would this actually be a viable setup for a witness?

I wouldn't use a laptop for a witness, but it should be able to run it.

0
0
0.000
Reply
avatar

Well, at least I can configure a backup witness for my main Hive Witness.

0
0
0.000
Reply
avatar

Thanks for sharing this extremely useful info! I was working on getting my node up and running last week, but had to stop due to time constraints. Will give it another shot next week ;-) I want to witness again! (was a witness on Steem, and am Hive Engine witness now as well).

I do have another question: I'm also working on a earning-tokens and tipping bots setup (one of the bots is @indeedly ). However, I've noticed that the account is constantly being downvoted by your Whale-bot. While I totally understand (and appreciate) the work of your Whale-bot, I would love to know what is causing the downvoting of my bots, so I can adjust and fix it. Thanks in advance!

0
0
0.000
Reply