bsc icon indicating copy to clipboard operation
bsc copied to clipboard

BSC is a lost cause

Open kaber2 opened this issue 4 years ago • 112 comments

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)

kaber2 avatar Nov 16 '21 17:11 kaber2

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.

mcoelho80 avatar Nov 16 '21 17:11 mcoelho80

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.

abarath94 avatar Nov 16 '21 18:11 abarath94

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.

m-e-r-k-l-e-root avatar Nov 16 '21 19:11 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.

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

mcoelho80 avatar Nov 16 '21 19:11 mcoelho80

Where are the developers?

mcoelho80 avatar Nov 16 '21 19:11 mcoelho80

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

ghost avatar Nov 16 '21 20:11 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)

ghost avatar Nov 17 '21 00:11 ghost

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

cyberskycat avatar Nov 17 '21 04:11 cyberskycat

damn BSC repo is on fire

MhaiRuMhaiShee avatar Nov 17 '21 05:11 MhaiRuMhaiShee

image

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

AwesomeMylaugh avatar Nov 17 '21 07:11 AwesomeMylaugh

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?

tsarv775 avatar Nov 17 '21 07:11 tsarv775

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.

dgdeivid avatar Nov 17 '21 11:11 dgdeivid

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.

BSCAwsNode

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)

RumeelHussainbnb avatar Nov 17 '21 12:11 RumeelHussainbnb

Just go to Fantom already, jeez

diegoxter avatar Nov 17 '21 14:11 diegoxter

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

havsar avatar Nov 18 '21 11:11 havsar

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.

Aser2019 avatar Nov 18 '21 14:11 Aser2019

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.

ghost avatar Nov 18 '21 15:11 ghost

BASED BASED BASED

willhamilton24 avatar Nov 18 '21 18:11 willhamilton24

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

0xarkin avatar Nov 18 '21 18:11 0xarkin

Come on Build on Bitcoin. The future is there!

22388o avatar Nov 18 '21 19:11 22388o

BSC has always been the definition of a rug chain

zimbabwean-inflation avatar Nov 18 '21 19:11 zimbabwean-inflation

"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.

rssnyder avatar Nov 18 '21 19:11 rssnyder

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

shreyaspapi avatar Nov 18 '21 19:11 shreyaspapi

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.

kaber2 avatar Nov 18 '21 19:11 kaber2

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

Blackglade avatar Nov 18 '21 20:11 Blackglade

But CZ bought a Mini Van

cryptobeaver avatar Nov 18 '21 20:11 cryptobeaver

BSC? More like BDC.

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

nathanjessen avatar Nov 18 '21 20:11 nathanjessen

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$.

pefka avatar Nov 18 '21 21:11 pefka