Hive Engine Update - Transaction fees for bots
Hive Engine users, for the past several months Hive Engine has been experiencing a consistent spam attack. Malicious users are deliberately putting multiple transactions per block and spamming them from multiple accounts frequently in an effort to delay block processing and disturb regular use of Hive Engine. This has at times knocked witnesses out of rotation, delayed processing times, gotten RPCs off track, and caused other similar problems.
Our first approach to squash this malicious spam was to simply limit the number of transactions that a user could put in a single block. That has been an effective measure to slow the attack, but it didn't fully solve the problem as we've noticed an increase in annoying spam meant to cause delays processing blocks even with this transaction limit per block. These asshats simply made more accounts.
Bot Transaction Fees when doing multiple transactions in the same block
As a second approach we're implementing a transaction fee into hive engine transactions. Human users will not be impacted. This fix is going live on Monday May 26th, 2025. From that day forward any time an account requests multiple transactions in the same block (which is something only bots do) it will carry a 0.001 BEED/tx fee. You need to simply have BEED in your account and the contract will burn the appropriate amount of BEED at the time the multi-tx transaction occurs. If the account does not have the appropriate amount of BEED then the transactions will be denied.
If you don't know what BEED is it's a HBD equivalent for the hive engine platform. Users can burn a dollars worth of $bee (currently near 10 BEE) and receive a $BEED coin designed to have a stable value near $1/BEED. It's similar to how users can convert a certain amount of hive (currently near 4) into 1 HBD. Impacted users can purchase BEED on the market or use the BEE Dollar contract to convert BEE to BEED.
Monthly Cost - 10 BEED
In the near future we'll be increasing the fee per transaction, but also allowing accounts to join a multi-tx exception list on a monthly basis that enables an account to not have to pay this fee. The anticipated monthly cost is 10BEED. The new multi-tx cost will increase to 0.1/TX/block (if you have 18 TX in a block you'll have to pay 1.8 BEED to process it or 10 BEED/Month to join the to list skip the requirement). This is admittedly meant to encourage all the bots to sign up for the monthly cost and help us track the activity of all the bots to make it easier to look for spam, abuse, and harm.
This monthly cost is not meant to be punitive to the current bot users. It's also not meant to impact human users as humans do not perform multi-tx transactions. If your bot can't generate $10 worth of value every month it doesn't make sense for us to host the transactions anyway or you can simply space your bots transactions out over time via single transaction blocks. While this is a minor financial inconvenience to someone with a handful of bots (and actually seems appropriate to charge high transaction volume users a small use fee, fee goes to BEE holders and not @ hive-engine) it is in fact a major financial inconvenience to someone with a large botnet and bad intentions towards Hive Engine as every bot spamming the platform will incur costs.
Throttle list
Further, we're introducing a "throttle list," which brings accounts down to 1 transaction per day. Accounts that are purposefully spamming Hive Engine with repetitive, random, or intentionally harmful transactions which appear to generate no value for Hive Engine or Hive Engine users will be put on the throttle list and may only do 1 transaction per day. Changing witness votes with 200 hundred accounts a thousand times a day per account is an example of a repetitive transactions with no value to hive engine. Bots that have paid for the monthly access simply to spam will find that their access to the list is cut off and their account is instead placed on the throttle list. The goal is not to block or steal assets. The point is to make sure accounts intentionally causing harm are blocked from doing so. We may later include a complete blackout list which would disable all transactions for a fiercely malicious account or botnet of them, but for now our next step is to limit to 1/tx per day.
The throttlelist is part of a contract, and contracts on Hive Engine are centralized. the @ hive-engine account and other accounts deputized by @ hive-engine can add and remove accounts from this list. It is however part of a contract and requires witnesses to allow hive-engine to add or remove names from the list. If I or deputies abuse this or any reason the witnesses deem appropriate they can block the @ hive-engine account, it's deputies, or the contract specifically from being updated. This balance allows for fast reaction time via a centralized authority, but also a distributed authority to make sure the central authority isn't abusing this power to stop bots generally from contracting on the Hive Engine platform.
This still leaves the possibility that one bad actor may create a hundred thousand accounts and spam 1 transaction per account per day, but there other costs associated with creating and enabling 100,000 accounts such that we think the risk is currently low for that kind of attack.
Thanks
I'd like to thank the witnesses generally for their discussion on this topic as we designed a system with low impact on human users that could stop malicious bots from their network spam. I would like to thank endecs, bamlolx, and drewlongshot for coding this update, and eonwarped for reviewing and helping to implement it.
If you feel that you or your bot are going to be adversely affected-
- You can move your bot to single transactions and not face any fees.,
- You can hold BEED in your account and pay the 0.001 BEED fee per transaction you log in a single block,
- You can contact me directly to be added manually to the multi-tx exception list where if you're on it your account does not have to pay the 0.001 BEED fee per transaction in a block (we're adding the feature where you can pay 10 BEED per month or in advance and keep your spot on this list, but it's all manual as of the deployment in a week),
- You can stop your bot if it's not producing 10 BEED worth of value in a month but doing tens of thousands of transactions,
- You can stop purposefully spamming us with worthless transactions simply to cause harm to the platform, or continue to do it for fun but with a new price for that enjoyment.
Minor Update
We've received some initial feedback on our plans and are adapting slightly. Many well meaning community bots distribute rewards and are heavily reliant on tokens-stake, tokens-transfer, and tokens-issue. Upon initial release we're excluding those three transaction types from the from mult-tx fee requirements.
These specific transactions are all lightweight in terms of processing time and are not a suspected primary attack vector. We'll monitor after initial roll out, and if we decide to ultimately include these 3 token contract actions we'll give 30 days or more notice at such time.
This feels very much like the quick and dirty way of solving problems that we used to see from steemit inc back in the day. I remember their brutal rate-limit implementation killing many asyncsteem (python 2 lib) cron scripts and some scripts.
The L1 has pretty much solved problems like this with this with the RC system, that doesn't have devs chasing after the capricious whims of platform devs.
Have you considered implementing something akin to the L1 RC system in engine?
Claiming that it doesn't affect users is complete false or lie or hypocrisy, or sign that you don't understand own platform, or just stupidity...
You just wrong. Obviously it affects all the apps and humans. Look how partial are your updates, like every time you write in future you going to make it better. This is sign that it's wrong direction, you do proper change not half change and act like you going to do follow ups to make it better, common, that's very weak, every few months you do change that breaks projects and fix nothing... I can already imagine how fast you improve it.
You just going to complicate process to the point that making projects with engine will be impossible. Generally my experience with engine is that you sabotage creators, devs, you don't care much, don't listen, act way too late, act blindly. How many times I can fix my project after you breaking it...
Imagine same changes applied to splinterlands, and users paying fees for transfering cards to other users? Users can transfer 20 cards every 3 second? All manually ? like transfering 200 cards to other players take 10 manual transactions every 3 seconds ? like users sits for few minutes and fill form every next block to do next transfer?
Is distribution of rewards like basic transfers affected too? Now I should distribute rewards to users by 500 single txes instead of doing few txes with 20 transactions?
how I explain this to my users that they need to pay extra fees for transfering nfts or buying nfts? How you print nfts to users as project? You pay fees twice to print nfts as creator?
How do you run custom bids for nfts market cause engine never did so, and we did for our projects an you kill it, so stupid...
It's all based on wrong assumptions...
Sad reality is that in last few years you did nothing for your users. You just wake up every few months to make it harder for users.
Few months ago I asked you to use engine power(close to 2M hive power) from staked users funds, for some delegations to engine projects so it's easier for them to exist and you completely ignored me while dropping 20$ votes on mooncart shit posts... It's worth to understand that supporting others do something good for platform, and it's not hard...
Maybe this extreme ignorance and hypocrisy is the reason why people attack your platform? You act likie you want me delete my app and attack your platform? I can. I can do some dirty actions next time you break my app and situation will get much more fun...
This was very long. I noted insults. I noted complaints. I noted villain-arc threats.
I didn't note helpful suggestions or requests.
Let's do this, when you're in an emotional spot where you can act professionally why don't you message me in Discord with suggestions or requests and I'll see what I can do.
2,264 characters isnât long it actually reasonable detailed feedback, especially on a platform-changing update. That comment of yours above is dismissive and I'll point it out right here as is.
What @dcityrewards did was being thorough with his entire comment. Calling it long, while ignoring its substance, is a tactic often used to avoid engaging with hard truths. Which I aim to highlight in this comment.
No you didn't. Because there are no insulting remarks at all to note and I'll prove it. Harsh criticism and frustration he did show but not insulting at all.
dcityrewards wrote:
This attacks. For sure. But not the person. It attacks the idea. Throughout the entire comment he made absolutely no direct name calling, like calling you idiot or moron.
When he mentioned âstupidityâ here, it was aimed at the decision or direction, not calling the dev(you and your small team) personally âstupid.â do notice the difference?
It sounds harsh but it isn't an insult.
Emotional it is. Who wouldn't be frustrated? But to dismiss his entire feedback the way you did is no sign of good leadership skills.
âYou just going to complicate processâŚâ
âYou sabotage creatorsâŚâ
âYou don't care much, don't listen, act way too late, act blindlyâŚâ
These are harsh criticism, not insults. Neither is he ridiculing or mocking.
Criticism over platform behavior isn't insulting at the least.
When he wrote, "you don't understand your own platform", that was him criticizing competence. Not an insult.
He did give strong feedback as he showed accusation of ignoring and sabotaging projects. But that was not insulting either. All these are accusations about behavior, not personal insults like âyouâre a moronâ or âidiot.â
I didn't see any slurs, direct insults, no ad hominems, just frustration from someone who has had an app broken many times.
You dismiss his entire critic by calling "emotional" and "unprofessional".
while ignoring the core issues he raised, is exactly the kind of behavior that leads to these tensions in the first place. Maybe you should start to treat passionate feedback as a resource, instead of a threat.
He came giving honest grievances and you swiped it off rudely. Why are you being deflective?
The moment you reframe pain as a tantrum, you forfeit the chance to understand why someoneâs bleeding in the first place.
Hereâs a thought: Stop waiting for people to write like diplomats while their work burns. Instead, learn to listen when they speak from the ashes.
But I will say this about your own commentary response, @aggroed, to @dcityrewards.
When someone labels strong dissent as âinsultsâ to avoid the substance of the criticism, it usually means one of several things is happening. It's either deflection, gaslighting the community, control of a narrative, emotional insecurity or failure of leadership.
Either way, calling it âinsultsâ subtly tells everyone that, âthis person isnât worth listening to" and that is not fair at all to him nor to everyone else reading who is looking for solutions.
Avoiding the real issues by shifting the focus to tone instead of content, is a classic rhetorical move to not refute the argument, and discredit the messenger.
Thank you.
A small group can literally silence accounts by throttling them to 1 transaction/day. Am I right on this? Based on what I just read, the throttle list is controlled by a few, and these throttle list will be decided, not by consensus, but by "delegates". So your small group would then be able to serious limit transactions to any user and no public vote or consensus call.
I smell a slippery slope here but I seem to understand this, it was done out of "emergency"(?), but for the sake of decentralized solutions, please think of them
In other words, you have to go through a manual approval process, gatekept by the same centralized actors. Correct? No automated or permission-less way to get whitelisted.
Ok is this selection process going to be transparently open to the public on chain?
If someone has to manually contact a central figure to be granted more than one transaction per day⌠is that permissionless? Or is it just a club?
How is this different from a paywall controlled by a private company?
If Hive Engineâs smart contracts can be updated or modified by the developers, how can anyone trust the system to remain fair or impartial?
How many steps away are you from being silenced?
If the system lets a few actors cut your transaction limit with no vote or warning, how decentralized is your voice here?
Are dissenting users going to be limited here too?
IME centralization leads to corruption without exception.
I agree 100%. I don't like this at all. And I don't think this was done solely because of "spam bots".
Please be very specific as to what malicious means here? Is there a political aspect to what malicious means here? What about those who have been blacklisted simply for questioning the status quo and narratives? Are they malicious?
I don't feel my savings are safe here anymore when very unselected few have control of whether I can make transactions or not. If I'm actually considering dumping all my hive, will I be prevented from doing so by being considered malicious to the system?
This is wrong. At NFTMart, we implemented features by having users perform actions that require using multiple operations to build a bigger transaction. It makes it possible for users to work with more cards on their games at once and this will remove their ability to do that.
The statement could be interpreted inaccurate, but the objective of stopping endless spam is not "wrong."
We're looking at excepting some of the NFT tokens transfer operations to start. That likely solves your specific problem in the immediacy. The long term however is almost certainly going to include a fee whenever there is a multi-tx transaction unless an account has subscribed to the multi-tx exception list. We'll hopefully have constructive comments during an open period of discussion following the V1 implementation regarding how to do this.
I'm running some bots, I'll try to add account balance checking to avoid sending empty transactions. Anyway, the easiest way would be if hive-engine would introduce a minimum trade/swap ammount and bot's balance check (do they have the right amounts to complete the transaction), if not then the transaction should be rejected
The new change that requires paying BEED for multi-transactions in a block will also affect users. On my platform Hive NFTs and Rising Star Utils users often use multi-transactions when buying/selling/transferring NFTS.
I feel in some situations this is fine, but this definetely impacts players.
Sending/buying/placing on sale/cancelling sales for more than 50nfts at a time can be very normal, and this will impact normal players.
I'd highly recommend making operations require a explicit "fee pay" operation so users don't just start losing balance on applications that are already running with such short notice.
As an ordinary human non-bot user of Hive Engine (or Tribe tokens via other HE front ends), I approve of this idea đ
On a totally different topic..... is it ever likely that BEED will bring in enough in fees for it to pay interest on staked amounts in a similar way to HBD ?
Value of BEED as fees will accumulate to BEE holders. To make BEED you have to burn BEE. So, BEE holders may get rewarded, and BEED is not a money making token in and of itself.
Thanks for the quick reply ! That makes sense - I think BEE is hugely underrated, so anything which draws more attention to it is a good thing đ
Fuck the asshats!
Good job Aggroed and team :D
Good work!
I remember waiting for days to get a swap because of their spam attacks.
Very good! Hearing more about improvements to hive-engine is great, making me think about the posibility of running a witness once again.
I had lost faith and interest in h-e with it being in perpetual maintenace mode, perhaps now is a good time to being supporting the ecosystem more.
We are likely to see more of this. A system with cheap or free transactions is vulnerable to attack. I hope this resolves the issue.
A Wake-Up Call: Accountability and Redemption in the Hive Ecosystem
To those who believe their actions on the Hive blockchain go unnoticed, itâs time to confront the truth. The power you think you wield through downvotes, vote farming, and manipulation is an illusion. True strength lies in doing whatâs right, not in exploiting systems for personal gain or silencing others out of fear.
1. The Illusion of Power Through Exploitation
If youâre downvoting critics, running coordinated farms, or hoarding influence to control rewards, ask yourself: What does this say about your character? Manipulating Hiveâs reward system doesnât make you powerfulâit exposes vulnerabilities. It shows a reliance on unethical tactics to feel significant in a space that was meant to empower everyone equally.
But hereâs the reality: these actions wonât bring lasting satisfaction. At night, when youâre alone with your thoughts, do you truly believe what youâre doing is right? Regret has a way of lingering, and no amount of HIVE tokens can silence the voice inside telling you thereâs a better path.
2. The Ripple Effect of Your Actions
Your choices donât just harm Hiveâthey affect the people around you. Your online friends may follow along now, but loyalty built on shaky foundations crumbles quickly. And what about your family? Do they understand how much energy you pour into behaviors that ultimately hurt others and yourself?
Every action has consequences, and the deeper you dig, the harder it becomes to climb out. Youâre not just harming Hiveâyouâre pulling those close to you into a cycle of negativity and regret. Is it worth it?
3. Change Before Itâs Too Late
The Bilpcoin team isnât here to attack individualsâweâre here to spark change. Weâve seen the evidence, and we know the impact of manipulative practices. But we also believe in redemption. Thereâs still time to step back, reflect, and choose a different path.
Ask yourself:
Hive deserves better. So do you.
4. Strength Lies in Doing Whatâs Right
Real power comes from integrity, not manipulation. Instead of focusing on how many tokens you can farm or how many users you can silence, consider how you can add value to the ecosystem. Create meaningful content, support genuine contributors, and advocate for reforms that benefit everyoneânot just a select few.
If you continue down your current path, remember this: you are being watched. Many stay silent, but they see everything. Blockchain data doesnât lie, and accountability always comes knockingâwhether today, tomorrow, or years from now.
5. A Final Plea: Fix What Needs Fixing
Itâs never too late to change course. Stop the farming, stop the toxicity, and start contributing to Hive in ways that uplift rather than tear down. If youâre struggling with why youâve chosen this path, take a moment to reflect. Seek help if neededâthereâs no shame in admitting youâve lost your way.
The Hive community is watching, waiting, and hoping for positive change. Will you rise to the occasion, or will you let regret define your journey? The choice is yours.
From the Bilpcoin Team: Weâre committed to helping Hive thrive by exposing the truth and fostering transparency. Letâs work together to build a stronger, fairer ecosystemâone where everyone has a chance to succeed.
What will your next move be?
Addressing the Downvote Issue on Hive: Itâs Time for Real Change
Marky Mark Stop the manipulation game Lady Zaza Bpc AI Music
Letâs cut through the noise and address one of the most pressing issues holding Hive back from reaching its full potential: abusive downvotes. The Bipcoin team has consistently exposed the systemic problems that stifle growth on this platform, yet little to no action has been taken. If Hive is to thrive, we must confront these challenges head-on instead of engaging in empty discussions that lead nowhere.
Hive cannot grow if nothing changes. How can new users and smaller creators flourish when they are constantly suppressed by those who exploit the system? Many so-called âwhalesâ contribute nothing meaningful to the ecosystemâinstead, they focus solely on farming rewards through manipulative tactics like mass self-voting, spam content, or coordinated downvoting campaigns. These actions discourage genuine participation and erode trust within the community.
Blockchain transactions donât lie. Weâve seen firsthand the shady methods used to game the systemâwhether itâs creating alt accounts to amplify votes, orchestrating downvote brigades, or hoarding influence without giving back to the network. Why does this behavior continue unchecked? Talk is cheap. Actions speak louder than words, and until concrete steps are taken to address these abuses, Hive will struggle to move forward.
We have repeatedly presented evidence of these practices, not to divide but to demand accountability. The truth is out there for anyone willing to look at the data. Yet, despite our efforts, the cycle persists. Today, weâre asking again: Can we finally talk about the real issues plaguing Hive? And more importantly, can we take decisive action to protect the integrity of this platform?
Do not let bullies destroy what makes Hive special. Abuse of power through downvotes and manipulation harms everyoneâcreators, curators, and the community as a whole. Itâs time to fight back against these toxic practices and create an environment where all voices can be heard and rewarded fairly.
The Bipcoin team remains committed to exposing the truth and advocating for meaningful change. But we canât do it alone. Together, letâs push for solutions that ensure Hive becomes a place of opportunity, fairness, and growthâfor everyone.
Enough talk. Letâs see action.
Every curation reward from @buildawhaleâs bot votes:
The blockchain doesnât forgetâyour actions are permanently recorded. So, enjoy your scam farm snacks now, because karma always delivers the bill.
https://peakd.com/@buildawhale/comments
https://peakd.com/@buildawhale/activities
Staked HIVE
More
Also known as HP or Hive Power. Powers governance, voting and rewards. Increases at an APR of approximately: ~13.07%
An unstake (power down) is scheduled to happen in 5 days (~4,742.795 HIVE, remaining 12 weeks)
61,991.841
Tot: 2,404,544.432
Delegated HIVE
Staked tokens delegated between users.
+2,342,552.591
Details
HP Delegations
RC Delegations
Delegated: 0 HP
Search
No outgoing delegations
Received: 2,342,553 HP
@blocktrades 2,342,494 HP Aug 16, 2020
@nwjordan 24 HP May 27, 2018
Weâve exposed the truth repeatedly with ironclad evidence:
@themarkymarkâs $2.4M scam farm.
@buildawhaleâs daily grift.
@jacobtotheâs downvote army.
Downvote Army: Silencing truth-tellers like Bilpcoin.
Reward Yourself: Collecting daily paychecks from @buildawhale.
https://hive.blog/hive-124838/@themarkymark/re-jacobtothe-st6rk4
https://hive.blog/hive-167922/@usainvote/re-buildawhale-s6knpb
https://peakd.com/hive-124838/@bpcvoter1/st7wu1
https://peakd.com/hive-126152/@bpcvoter1/jacobtothe-you-re-not-god-no-matter-how-much-you-try-to-act-like-it-you-can-say-what-you-want-but-the-truth-remains-undeniable
https://peakd.com/hive-163521/@bpcvoter3/jacobtothe-this-was-way-over-rewarded-and-we-need-to-call-it-out-you-made-significant-rewards-from-a-post-that-was-created-using
https://peakd.com/hive-126152/@bpcvoter3/jacobtothe-let-s-address-the-core-issue-here-facts-speak-louder-than-rhetoric-we-ve-presented-verifiable-evidence-that
https://peakd.com/hive-126152/@bpcvoter3/think-carefully-about-your-next-move-because-this-issue-is-bigger-than-any-one-of-us-the-downvote-abuse-scamming-and-farming-by
https://hive.blog/hive-180505/@jacobtothe/re-denmarkguy-st9f4w
https://hive.blog/hive-124838/@themarkymark/re-peaksnaps-starqg
https://hive.blog/hive-167922/@darknightlive/re-bpcvoter2-bpc-dogazz
https://hive.blog/hive-126152/@tobetada/my-first-shitstorm#@azircon/re-tobetada-stbswq
https://hive.blog/hive-124838/@acidyo/re-themarkymark-stbthn
https://peakd.com/hive-168088/@bpcvoter3/jacobtothe-it-seems-we-re-going-in-circles-here-so-let-s-clarify-things-once-and-for-all-downvotes-don-t-erase-the-truth-the
https://peakd.com/hive-126152/@bpcvoter3/uwelang-it-seems-you-re-dismissing-the-discussion-without-engaging-with-the-actual-content-that-s-unfortunate-because-the
https://peakd.com/hive-121566/@bpcvoter1/std7q6
https://peakd.com/@uwelang/re-uwelang-stc2c3
https://hive.blog/hive/@themarkymark/what-the-fuck-do-witnesses-do-dk1
https://hive.blog/hive-167922/@usainvote/re-buildawhale-s5tysw
https://hive.blog/hive-124838/@steevc/re-meno-stdsv6
https://hive.blog/life/@crimsonclad/re-oldsoulnewb-sh93a2
You Can't Downvote The Truth Mc Franko Bpc Ai Music
https://hive.blog/hive-126152/@jacobtothe/re-galenkp-stekn4
https://hive.blog/hive-126152/@jacobtothe/re-galenkp-steiss
https://hive.blog/hive-124838/@acidyo/re-web-gnar-stfc6c
https://hive.blog/mallorca/@azircon/re-abh12345-stfbyk
https://hive.blog/hive-167922/@uwelang/hpud-march-back-over-110k-hp
https://hive.blog/burnpost/@buildawhale/1742569802434998164
https://hive.blog/burnpost/@buildawhale/1742656202460243008
https://hive.blog/hive-124838/@themarkymark/re-peaksnaps-sti6pr
https://hive.blog/hive-124838/@themarkymark/re-peaksnaps-stkfjj
https://hive.blog/burnpost/@buildawhale/1742742602124717444
https://hive.blog/burnpost/@themarkymark/re-kgakakillerg-stm4vv
https://hive.blog/hive-124838/@themarkymark/re-snap-container-1742690880-20250324t025303z
https://hive.blog/donation/@crimsonclad/re-nampgf-sti0nf
https://hive.blog/hive-148441/@azircon/re-curamax-stk5vq
https://hive.blog/hive-funded/@acidyo/re-alex-rourke-stluzc
https://hive.blog/hive-167922/@theycallmedan/re-finpulse-4gnm7o8h
https://hive.blog/hive-144400/@blocktrades/st110u
https://hive.blog/hive-148441/@usainvote/re-curamax-stly39
https://hive.blog/hive-167922/@usainvote/re-buildawhale-s75mua
https://hive.blog/burnpost/@buildawhale/1742829002430606097
https://peakd.com/hive-167922/@bpcvoter1/themarkymark-big-bad-marky-huh-lol-you-re-more-of-a-joke-than-anything-else-we-ve-exposed-your-actions-repeatedly-your-scamming
https://hive.blog/3dprinting/@themarkymark/meet-frank-ajt
https://hive.blog/burnpost/@buildawhale/1742483402094376205#@buildawhale/re-1742483402094376205-20250320t151108z
https://hive.blog/curation/@azircon/re-acidyo-stn05u
https://hive.blog/curation/@themarkymark/re-azircon-sto5b9
https://hive.blog/curation/@themarkymark/re-azircon-sto57d
https://hive.blog/curation/@themarkymark/re-meno-sto4ua
https://hive.blog/hive-124838/@themarkymark/re-snap-container-1742825520-20250325t020936z
https://hive.blog/hive-150342/@steevc/re-alessandrawhite-2025325t91011757z
https://hive.blog/curation/@themarkymark/re-meno-stodj2
https://hive.blog/curation/@themarkymark/re-meno-stod08
https://hive.blog/hive-13323/@moeknows/re-azircon-stnrc3
https://hive.blog/hive-112018/@jacobtothe/re-dynamicrypto-sto8ak
https://hive.blog/hive-13323/@azircon/re-moeknows-stofom
https://hive.blog/burnpost/@buildawhale/1742915402155436654
https://hive.blog/hive-13323/@azircon/re-moeknows-stoq3o
https://hive.blog/hive-13323/@bpcvoter1/stos6z
https://hive.blog/technology/@themarkymark/re-kgakakillerg-stpzn7
https://hive.blog/hive-124838/@themarkymark/re-niallon11-stpzmi
https://hive.blog/hive-124838/@themarkymark/re-peaksnaps-stpx2t
https://hive.blog/hive-13323/@azircon/re-moeknows-stov0c
https://hive.blog/burnpost/@buildawhale/1743001802743637765
https://hive.blog/hive-124838/@meno/re-themarkymark-stqdnp
https://hive.blog/hive/@acidyo/hive-curation-a-response-to-a-post-about-my-previous-video
https://hive.blog/hive-124838/@themarkymark/re-meno-stqt8y
https://hive.blog/burnpost/@buildawhale/1743088202593656720
https://peakd.com/@bpcvoter1/to-the-hive-community-and-all-those-watching-our-journey
https://hive.blog/hive-124838/@themarkymark/re-snap-container-1743079680-20250328t095442z
https://hive.blog/hive/@acidyo/re-freecompliments-strts3
https://hive.blog/hive-124838/@themarkymark/re-peaksnaps-sttukk
https://hive.blog/hive-124838/@anderssinho/re-themarkymark-stu0qr
https://hive.blog/hive-124838/@oldsoulnewb/re-themarkymark-stu1t3
https://hive.blog/hive-124838/@acidyo/re-themarkymark-stu3fk
https://hive.blog/hive-124838/@wiseagent/re-themarkymark-stu6fz
https://hive.blog/hive-124838/@stayoutoftherz/re-themarkymark-stu6r7
https://hive.blog/hive-124838/@themarkymark/re-peaksnaps-stufv1
https://hive.blog/hive-124838/@themarkymark/re-godfish-stujq7
https://hive.blog/hive-124838/@themarkymark/re-coininstant-stugcr
https://hive.blog/hive-124838/@themarkymark/re-snap-container-1743183360-20250329t130534z
https://peakd.com/hive-167922/@bpcvoter3/exposing-hive-s-hidden-manipulators
STOP #buildawhalescam #buildawhalefarm
https://peakd.com/hive-126152/@bpcvoter3/exposing-the-whales-on-the-hive-blockchain
https://peakd.com/hive-167922/@bpcvoter3/the-hive-unveiled-a-journey-through-shadows-and-light
Stand Together Hive Keni & Mc Franko Bpc Ai Music
https://peakd.com/hive-126152/@bpcvoter3/spaminator-why-the-silence-on-the-buildawhale-scam-farm-the-truth-deserves-action
For more insights into blockchain transparency and accountability, visit Bilpcoinâs Publish0x page.
Hive make me study, love this.
Great idea. It's annoying to be trading against bots that automatically place bids and asks just above yours.
Very good Hopefully things will go better in the future
Congratulations @aggroed! Your post has been a top performer on the Hive blockchain and you have been rewarded with this rare badge
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
STOPI pray the equation is balanced to avoid affecting users unknowingly.
Nice