BSC is a lost cause

[kaber2]

Guys, seriously, WTF. This is a blockchain with supposedly billions of value, yet it is governed and developed like the project of a stoned teenager.

I've rarely seen something handled so unprofessionally.

• There is no code review, patches are simply committed, in most cases even without a proper description of what they do or what problem they try to solve
• There doesn't appear to be any reasonable testing process in place. Every update appears to make things worse.
• There is zero responding to bug reports. Hundreds of people report non syncing nodes or nodes falling out of sync. Response from the "developers" - zero.
• There is no beta testing, stuff is thrown over the fence. Features like diffsync are declared "stable" by decrete, even though hundreds of people reporting the opposite indicated otherwise.
• The developers apparently don't have a freaking clue of what it is they are building. The "feature" to disable P2P Tx broadcast must be the most stupid idea I've seen in a long time. If people actually use this completely braindead feature, your network will become highly centralized and many nodes will experience issues with non executing Txs. How the phrack are Txs going to be propagated within the network without nodes actually doing that?
• This "fix" is, on top, just a stab in the dark. There is zero indication that the quite low unexecuted Tx rate of BSC has any responsibility in the current situation. Ethereum has 20 fold the amount of Txs flying around without the slightest problem.
• As someone else already wrote, the root cause of the problem is that you mindlessly increased the blocksize and reduced the blocktime without doing the actual work required.

Overall, there is only one conclusion. Binance wanted a quick hack to make some money, but is not willing to expand even modest resources to make this thing actually work. Given that they've made billions from this, this is absurd and a huge abuse of the trust (and money) people put in this.

You have proven to be incompetent of leading, developing and governing this. Just be honest and trash it without more people wasting their time and money.

(written by a 4k BNB holder, considering dumping this garbage)

[mcoelho80]

I'm tired of trying to keep my node synced. Even with NVME, 196Gb RAM, all possible configurations and sync modes, my node losts sync VERY quickly.

[abarath94]

Guys, seriously, WTF. This is a blockchain with supposedly billions of value, yet it is governed and developed like the project of a stoned teenager.

I've rarely seen something handled so unprofessionally.

• There is no code review, patches are simply committed, in most cases even without a proper description of what they do or what problem they try to solve
• There doesn't appear to be any reasonable testing process in place. Every update appears to make things worse.
• There is zero responding to bug reports. Hundreds of people report non syncing nodes or nodes falling out of sync. Response from the "developers" - zero.
• There is no beta testing, stuff is thrown over the fence. Features like diffsync are declared "stable" by decrete, even though hundreds of people reporting the opposite indicated otherwise.
• The developers apparently don't have a freaking clue of what it is they are building. The "feature" to disable P2P Tx broadcast must be the most stupid idea I've seen in a long time. If people actually use this completely braindead feature, your network will become highly centralized and many nodes will experience issues with non executing Txs. How the phrack are Txs going to be propagated within the network without nodes actually doing that?
• This "fix" is, on top, just a stab in the dark. There is zero indication that the quite low unexecuted Tx rate of BSC has any responsibility in the current situation. Ethereum has 20 fold the amount of Txs flying around without the slightest problem.
• As someone else already wrote, the root cause of the problem is that you mindlessly increased the blocksize and reduced the blocktime without doing the actual work required.

Overall, there is only one conclusion. Binance wanted a quick hack to make some money, but is not willing to expand even modest resources to make this thing actually work. Given that they've made billions from this, this is absurd and a huge abuse of the trust (and money) people put in this.

You have proven to be incompetent of leading, developing and governing this. Just be honest and trash it without more people wasting their time and money.

(written by a 4k BNB holder, considering dumping this garbage)

I literally can't agree more. The state of the node is simply horrible. We are trying to create a DAPP with real time data, but with the current state it is not possible. At least Ethereum is working like a charm since two weeks, without any irregular activities. If they can't fix the problems, BSC is a lost cause, and developers are going to switch to another chain. At the current state, I can't recommend developers to work with BSC.

[m-e-r-k-l-e-root]

Roughly a year ago I was able to run bsc geth nodes on literally some of the cheapest VPS's (<$20/mo) I could find with relatively decent specs (ah, the good old days). Now I'm paying thousands a month for dedicated hardware just to keep my infra running smoothly. While some of this can be contributed to network growth, most of it is due to what appears to be ineptitude in regard to the developers of this project.

[mcoelho80]

Roughly a year ago I was able to run bsc geth nodes on literally some of the cheapest VPS's (<$20/mo) I could find with relatively decent specs (ah, the good old days). Now I'm paying thousands a month for dedicated hardware just to keep my infra running smoothly. While some of this can be contributed to network growth, most of it is due to what appears to be ineptitude in regard to the developers of this project.

Where is your server located? Are you experiencing lost of sync? What HW do you have?

[mcoelho80]

Where are the developers?

[ghost]

There isn't. They also spoiled the Light Client, which since version 1.1.3 does not work properly....

[ghost]

Hello everybody.

I wanna repeat here my suggesion at least as a temporary solution:

what if developers limit amount of transactions per block like 300-400 (sorted by gas price), so blockchain speed would be reduced and every node could sync?

It is a simple and efficient solution. And it could be implemented in a few hours and stabilaze a situation at least for a while, so developers have time to think and maybe figure out of something more elegant.

(written by a 0.34 BNB holder, dumped 66% of this garbage already)

[ratthakorn2509]

Ratthakorn99@gmail.com

[ratthakorn2509]

Ratthakorn99@gmail.com

[cyberskycat]

i suggest issue a new chain named bsc pro and next year issue bsc pro max and then everyone can synced easily.

[MhaiRuMhaiShee]

damn BSC repo is on fire

[AwesomeMylaugh]

is that normal?I have wait for 3 days! could sb helps me plz

[tsarv775]

I can't agree more. I have many full nodes running there and now all of them are unable to sync. Each of these servers costs me $800 per month (previously only $200), then you told me that I need faster bandwidth and disk which means the cost will keep rising at a very exaggerated rate. My boss even thought I spent all these money in nightclub because of the goddamn BSC! We've been telling you to check the shitty BSC code and solve these problems as so many node maintainers are puzzled by it. However, your answer was just that the growing BSC data requires the update of hardwares. WTF??? You just fuxked up all these, it's gonna be the beginning of BSC's failure. Even such a simple issue can't be solved, what else the fuxking shit you can do, huh?

[dgdeivid]

In my case, the problem I have is that I have gone from an average time of obtaining the new blocks of 1-2 seconds to 7-30 seconds.

[RumeelHussainbnb]

I choose AWS to build my node, it is located at eu-west, the instance I choose is m5.zn.3xlarge 12vCPU, 48GB memory, the instance monted with a 2TB ssd, volume type is General Purpose SSD(gp3), IOPS is 8k, 250Mb/s throughput, the networking upto 25Gigabit. The latest version is v1.1.3 when I set up the node. I just use the default config from the latest release.

The performance seems fine, there will be few blocks lag some time, but I have backup nodes when I need pruning. My robot will choose the syncd one to call. The performance metrics can be check from logs, the mgasps is around 50 to 100, I have run the node for about two weeks, now the storage comes to 1.6T, possibly need prune soon.

Guys, seriously, WTF. This is a blockchain with supposedly billions of value, yet it is governed and developed like the project of a stoned teenager.

I've rarely seen something handled so unprofessionally.

• There is no code review, patches are simply committed, in most cases even without a proper description of what they do or what problem they try to solve
• There doesn't appear to be any reasonable testing process in place. Every update appears to make things worse.
• There is zero responding to bug reports. Hundreds of people report non syncing nodes or nodes falling out of sync. Response from the "developers" - zero.
• There is no beta testing, stuff is thrown over the fence. Features like diffsync are declared "stable" by decrete, even though hundreds of people reporting the opposite indicated otherwise.
• The developers apparently don't have a freaking clue of what it is they are building. The "feature" to disable P2P Tx broadcast must be the most stupid idea I've seen in a long time. If people actually use this completely braindead feature, your network will become highly centralized and many nodes will experience issues with non executing Txs. How the phrack are Txs going to be propagated within the network without nodes actually doing that?
• This "fix" is, on top, just a stab in the dark. There is zero indication that the quite low unexecuted Tx rate of BSC has any responsibility in the current situation. Ethereum has 20 fold the amount of Txs flying around without the slightest problem.
• As someone else already wrote, the root cause of the problem is that you mindlessly increased the blocksize and reduced the blocktime without doing the actual work required.

Overall, there is only one conclusion. Binance wanted a quick hack to make some money, but is not willing to expand even modest resources to make this thing actually work. Given that they've made billions from this, this is absurd and a huge abuse of the trust (and money) people put in this.

You have proven to be incompetent of leading, developing and governing this. Just be honest and trash it without more people wasting their time and money.

(written by a 4k BNB holder, considering dumping this garbage)

[diegoxter]

Just go to Fantom already, jeez

[havsar]

We created a Telegram group for BSC Node discussions, feel free to join and share experience https://t.me/joinchat/zXCza2tQN0tjYzM0

[Aser2019]

Hello, we doubled the server resources and still we have problem in syncing and transactions broadcasting, some of TX is done and some not. Really there is BUG in BSC they have to fix it before its too late. I really think in leave this network and use other network.

[ghost]

i suggest issue a new chain named bsc pro and next year issue bsc pro max and then everyone can synced easily.

It might be a good idea. Since the majority of transactions are stupid games, no one would even notice.

[willhamilton24]

BASED BASED BASED

[ghost]

come on Avalanche guys, https://github.com/ava-labs/avalanchego

[22388o]

Come on Build on Bitcoin. The future is there!

[zimbabwean-inflation]

BSC has always been the definition of a rug chain

[rssnyder]

"dummies, use this coin" and "code bad" comments are not really helpful in a code repository issue. If you want to have a real conversation about the state of BSC stop commenting nonsense.

[shreyaspapi]

Guys, seriously, WTF. This is a blockchain with supposedly billions of value, yet it is governed and developed like the project of a stoned teenager.

I've rarely seen something handled so unprofessionally.

• There is no code review, patches are simply committed, in most cases even without a proper description of what they do or what problem they try to solve
• There doesn't appear to be any reasonable testing process in place. Every update appears to make things worse.
• There is zero responding to bug reports. Hundreds of people report non syncing nodes or nodes falling out of sync. Response from the "developers" - zero.
• There is no beta testing, stuff is thrown over the fence. Features like diffsync are declared "stable" by decrete, even though hundreds of people reporting the opposite indicated otherwise.
• The developers apparently don't have a freaking clue of what it is they are building. The "feature" to disable P2P Tx broadcast must be the most stupid idea I've seen in a long time. If people actually use this completely braindead feature, your network will become highly centralized and many nodes will experience issues with non executing Txs. How the phrack are Txs going to be propagated within the network without nodes actually doing that?
• This "fix" is, on top, just a stab in the dark. There is zero indication that the quite low unexecuted Tx rate of BSC has any responsibility in the current situation. Ethereum has 20 fold the amount of Txs flying around without the slightest problem.
• As someone else already wrote, the root cause of the problem is that you mindlessly increased the blocksize and reduced the blocktime without doing the actual work required.

Overall, there is only one conclusion. Binance wanted a quick hack to make some money, but is not willing to expand even modest resources to make this thing actually work. Given that they've made billions from this, this is absurd and a huge abuse of the trust (and money) people put in this.

You have proven to be incompetent of leading, developing and governing this. Just be honest and trash it without more people wasting their time and money.

(written by a 4k BNB holder, considering dumping this garbage)

I agree

[kaber2]

Hello, we doubled the server resources and still we have problem in syncing and transactions broadcasting, some of TX is done and some not. Really there is BUG in BSC they have to fix it before its too late. I really think in leave this network and use other network.

I'm running 15 nodes on 64 Core EPYC 7702P CPUs with 512GB RAM and 2 Intel SSDPE2KX020T8 NVMe in RAID0 configuration with 40GBe network connection each. At any point in time, roughly 1/3 of my nodes has fallen out of sync and need to be manually massaged to sync up again.

This most certainly has nothing to do with hardware specs, you can't get much faster than that. The BSC developers fucked up, but are apparently not the least bit interested in debugging and fixing the problem. Their lack of reaction is just a big fat middle finger.

[Blackglade]

I hear running a node on Algorand is pretty easy: https://developer.algorand.org/docs/run-a-node/setup/install/

[cryptobeaver]

But CZ bought a Mini Van

[nathanjessen]

BSC? More like BDC.

Also, is anyone working on a BSC Cash fork, or BSC CZ's Vision?

[pefka]

this "software" is a piece of shit. They thought that if they thoughtlessly copied the Ethereum blockchain, they could change something there. In fact, it turned out to be a cheap fake, like a Chinese "iphone" on an android for 90$.

[fomotrader]

setting up avalance node today me thinks

[Kellytom]

Come to Terra. Real World. Real performance.

[ascendantlogic]

Someone needs to lock this thread as the shilling army has arrived.

[ghost]

Im no expert in geth by any means, but back earlier this year i was doing a tour de force of the various chains. With one goal- test the json RPC getPastEvents. Event logs were already a heavy lift on mainnet nodes, and I wanted to know how these accelerated block speeds, (and if I remember correctly BSC's additional shadow blocks inbetween the normal ones for validators) affected it.

During my BSC test, I ran into https://github.com/binance-chain/bsc/issues/113 in which I found https://github.com/binance-chain/bsc/blob/b67a129e5bdd2774c9493f505d1a83f1e0a215c4/eth/filters/filter.go#L151-L153 just pasted on top of the normal geth code. This was understandable, but still a red flag as getPastEvents is technically part of the JSON_RPC standard.

The comments alone were very telling. as BennytheDev Stated

If you perform a getPastEvents using web3 on a contract with fully enabled features from block 0, you will see what I mean roundabout at that block height. Things get looked up pretty fast and suddenly slowing incredibly down.

When you plot that, you will see exponential growth, which is bad and needs to be addressed. Just putting stronger hardware will only help for so long until the entire things comes to a halt. So going the optimization route is imho the way to go (we are using already some really powerful metal and still run into tons of issues).

It seems BSC is crushing itself under its own weight and is a ticking timebomb. It made me wonder if BSC's attempts at co-opting geth to run at these higher loads was fundementally flawed, and that in fact ethereum itself is getting away with this 'bad code' since it doesn't run at this scale. Something that would require a deep rethinking about the design of P2P communication channels, both for Tx's and logs, and, well everything else to bring these quadratic scales into at least linear time. Anyways, doesn't seem trivial to me, hope the team finds a way to solve it in time

[mehranhydary]

Haven't laughed this hard in a long time ahahaha

[BigCheeseTC]

Guys, seriously, WTF. This is a blockchain with supposedly billions of value, yet it is governed and developed like the project of a stoned teenager.

I've rarely seen something handled so unprofessionally.

• There is no code review, patches are simply committed, in most cases even without a proper description of what they do or what problem they try to solve
• There doesn't appear to be any reasonable testing process in place. Every update appears to make things worse.
• There is zero responding to bug reports. Hundreds of people report non syncing nodes or nodes falling out of sync. Response from the "developers" - zero.
• There is no beta testing, stuff is thrown over the fence. Features like diffsync are declared "stable" by decrete, even though hundreds of people reporting the opposite indicated otherwise.
• The developers apparently don't have a freaking clue of what it is they are building. The "feature" to disable P2P Tx broadcast must be the most stupid idea I've seen in a long time. If people actually use this completely braindead feature, your network will become highly centralized and many nodes will experience issues with non executing Txs. How the phrack are Txs going to be propagated within the network without nodes actually doing that?
• This "fix" is, on top, just a stab in the dark. There is zero indication that the quite low unexecuted Tx rate of BSC has any responsibility in the current situation. Ethereum has 20 fold the amount of Txs flying around without the slightest problem.
• As someone else already wrote, the root cause of the problem is that you mindlessly increased the blocksize and reduced the blocktime without doing the actual work required.

Overall, there is only one conclusion. Binance wanted a quick hack to make some money, but is not willing to expand even modest resources to make this thing actually work. Given that they've made billions from this, this is absurd and a huge abuse of the trust (and money) people put in this.

You have proven to be incompetent of leading, developing and governing this. Just be honest and trash it without more people wasting their time and money.

(written by a 4k BNB holder, considering dumping this garbage)

Exactly why developers will build elsewhere, like Cosmos & Juno with interoperable smart contracts.

[jakerockland]

I'm here for the memez.

[PapaBuidl]

kek surprise, Binance chain is actually a shitty cashgrab. Go figure

Come to Avalanche, sers. That's a real chain, not this excuse of an EVM copycat.

And remember! We're in it for the tek

[neirenoir]

Honestly, looking at the state of open issues raised in this repo that haven't seen any reply from the devs in a while is pretty telling. If any node operators that are not CZ in disguise are here reading this, I would recommend a hard fork of the network, or at least "threatening" with a hard fork so Binance starts caring again.

At risk of sounding like a shill, running BSC as an Avalanche subnet could be a quick way to scale it without changing much of the code, as the C-chain is already pretty much geth. Chances are Ava Labs could even fund the development if validators are really willing to migrate.

[DIGITALCRIMINAL]

Stop developing for the Binance Scam Chain, just stop

[StayFoolisj]

It's time to make a ruckus, boys

[0xBeau]

looks like its time to build on polygon eh lads?

[Xn4m3d]

avalanche will take the lead np

[MiwokeWP]

Come on Avalanche ;)

[EoghanH]

All of the comments advising the solution is to pump their bags by developing for their personal chain of choice is a little bit out there.

FWIW I opted against developing for BSC as I've been around long enough to see massive exchanges rise and fall - and as much as I do think Binance are likely to stick around for the long term, I have no interest in tying the longevity of a blockchain to a company whose business interests can often take their attention elsewhere.

The incentivisation on BSC seems to always be towards the general public, rather than the stakeholders who are holding the chain together. It was bizarre to see that as the value of BNB rose and the network gained more popularity, that Binance opted to decrease gas prices. Dusting was always an issue on BSC, but became endemic following this.

Bizarrely, BNB itself seems to have staged a miraculous recovery lately - but the strangest part is that the BSC ecosystem does not seem to be sharing in that recovery at all. Staple tokens remain dumped, or continue to bleed out.

Not here to try and sell you on a different chain - the reason we're seeing such fierce competition in the L1 (and L0/L2) space lately has been thanks to the hard work put in by everyone on their own chains of choice, and their dedication towards seeing them all improve. If validators and developers actually listened to the masses of unpumped bags demanding they focus their attention towards their personal chains of choice, we'd get literally nowhere.

Here's hoping things improve for you all soon, especially given the time, resources, and effort you've all put towards it.

[BinanceG11]

I believe every project will have their own issues as they grow and especially BSC has reached another milestone achieving 2 million daily active addresses and with a peak of 14 million transactions processed in 24 hours (ATH from Nov 17). Main differentiator is they take note of feedback and continue to improve as they grow, but i do agree that there should be more transparency of upcoming changes and upgrades which could help set the right expectations. Do take a moment to go through this. https://twitter.com/BinanceChain/status/1461420946925834240.

https://github.com/binance-chain/bsc/issues/502

[DiveInto]

I can't agree more. I have many full nodes running there and now all of them are unable to sync. Each of these servers costs me $800 per month (previously only $200), then you told me that I need faster bandwidth and disk which means the cost will keep rising at a very exaggerated rate. My boss even thought I spent all these money in nightclub because of the goddamn BSC! We've been telling you to check the shitty BSC code and solve these problems as so many node maintainers are puzzled by it. However, your answer was just that the growing BSC data requires the update of hardwares. WTF??? You just fuxked up all these, it's gonna be the beginning of BSC's failure. Even such a simple issue can't be solved, what else the fuxking shit you can do, huh?

curious why you are running full BSC nodes, are you a validator, or your are running the nodes for your own business to query data from?

[huangyisan]

I'm tired of trying to keep my node synced. Even with NVME, 196Gb RAM, all possible configurations and sync modes, my node losts sync VERY quickly.

Yes, We have the same issue. No matter how powerful our ec2 are, we always behind more blocks. Catch me if you can ?

[cryptobeaver]

Cool! But you should try Avalanche ;)

Sent from my iPad

On Nov 18, 2021, at 17:51, fomotrader @.***> wrote:

 setting up avalance node today me thinks

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[zhongfu]

at risk of sounding like a shill, I shall note that my nodes running on (relatively cheap) consumer hardware has been doing reasonably well at keeping up with chain head for the past couple of months

nothing too crazy either: I've spent maybe $450 or so on my crappiest node, which is a Skull Canyon NUC with 64 gigs of RAM and a 2TB SATA SSD

so it's kind of weird that people spending more than what my hardware costs every month are having issues keeping sync. maybe it's since many of them are running nodes on VMs (reasonable, I guess), or on networked storage like AWS EBS -- even io2 -- or the equivalent for Azure/GCP (not a great idea imo, they typically claim "single-digit millisecond latency")

I do agree with the rest of the criticism though. increasing the block gas limit as a response to blocks being full is probably not the best idea, and doing it repeatedly seems, for the lack of a better term, quite delusional

I can also confirm that many of the peers on my nodes seem to be off sync by at least 250 blocks at times -- up to half when the blocks are full and hitting 100M gas/block -- which is, well, suboptimal if all of your peers end up being behind chain head, even if your nodes can catch up

(and for everyone else recommending fantom/avax/terra/cosmos/polygon: I get it, you guys want to shill your bags, but there are better places for you to do that and it's not on this issue tracker)