[ANN][SEM] Semux - Official Thread

[jztxeno]

Rc2 currently appears to be running relatively stable, and the concurrency of 5000txs is not a small number. Since it can be successfully passed, it is proved that this scheme is feasible.At least for now, few projects can do that.

Yes we are happy that the network is able to handle 5000tx per block. Ultimately we want to be able to handle more than that and this can be achieved once we have more upscale validators.

Is there any particular reason behind having only 64 validators at max? Wouldn't the network be more stable with more?

[CosaNostra]

Rc2 currently appears to be running relatively stable, and the concurrency of 5000txs is not a small number. Since it can be successfully passed, it is proved that this scheme is feasible.At least for now, few projects can do that.

Yes we are happy that the network is able to handle 5000tx per block. Ultimately we want to be able to handle more than that and this can be achieved once we have more upscale validators.

Let me get this straight please.
Basically if the wallet was working without crashing during stress test than my vps configuration is sufficient?

[crimealone]

Rc2 currently appears to be running relatively stable, and the concurrency of 5000txs is not a small number. Since it can be successfully passed, it is proved that this scheme is feasible.At least for now, few projects can do that.

Yes we are happy that the network is able to handle 5000tx per block. Ultimately we want to be able to handle more than that and this can be achieved once we have more upscale validators.

Let me get this straight please.
Basically if the wallet was working without crashing during stress test than my vps configuration is sufficient?

Based on my experience, V with 2cpu, 4GB and 100M is sufficient to handle 5000 tx per block. But maybe not enough for 10000 tx.

[mdodong]

Is there any particular reason behind having only 64 validators at max? Wouldn't the network be more stable with more?

Fewer validators would mean fewer propagation needed to reach concensus(2/3). This is not yet final since we will all base it on the results of the RC tests.

[aknataga]

What is the issue exactly?

We dumped 8000 transactions in one block for stress test.

Many validator were unable to handle such load. The network had trouble with propagating the block within 10 seconds, and thus got stuck.

RC2 will be released on Saturday to address issue!

Semux v1.0.0-rc.2

1. This version is not backward compatible. Please do NOT copy database folder from previous version.
2. Please keep your wallet open if you're a validator; the network will resume when 2/3+ validators are upgraded.

https://github.com/semuxproject/semux/releases

Upgraded , works great!

[ourgot]

Very good, I will buy it.I will always be concerned about the progress of the project, sem will be on the moon. Each round of testing is conducted in an orderly manner.

I am running a client and everything is fine.

[zhongzy]

Very good, I will buy it.I will always be concerned about the progress of the project, sem will be on the moon. Each round of testing is conducted in an orderly manner.

I am running a client and everything is fine.

i am also keep watching this project closely alought i have a little coins, but really happy when i see dev is working hard on project behind.

[tradingdisaster]

Devs: with only 64 validator nodes, would an attack by first spamming the network with tx's and then dDOSing a handful of validators not lead to the remaining validators getting overwhelmed and crash? It seems a rather vulnerable setup, esp considering a validator node needs 8GB RAM to handle 5K tx. Even on an expensive VPS, there would not be a lot of room for additional load.

Or am I wrong?

[zeepaw]

upgrade to rc.2, works and smoothly succes for semux 

[ELE.ZYK]

upgrade to rc.2, works and smoothly succes for semux 

yes ,also work fine for me ,hope dev process rc test as qucik as possible ,i am waitting for main network.

[mdodong]

Devs: with only 64 validator nodes, would an attack by first spamming the network with tx's and then dDOSing a handful of validators not lead to the remaining validators getting overwhelmed and crash? It seems a rather vulnerable setup, esp considering a validator node needs 8GB RAM to handle 5K tx. Even on an expensive VPS, there would not be a lot of room for additional load.

Or am I wrong?

This is definitely a possibility regardless if we are using 64 or 100 validators. Validators need to have sufficient bandwidth, RAM and processing power to handle large amount of transactions and the recent and ongoing RC tests are going to expose these vulnerabilities. With these vulnerabilities exposed our Devs can work out a solution to prevent these problems from happening before we go on mainnet.

[wiredideas]

Devs: with only 64 validator nodes, would an attack by first spamming the network with tx's and then dDOSing a handful of validators not lead to the remaining validators getting overwhelmed and crash? It seems a rather vulnerable setup, esp considering a validator node needs 8GB RAM to handle 5K tx. Even on an expensive VPS, there would not be a lot of room for additional load.

Or am I wrong?

This is definitely a possibility regardless if we are using 64 or 100 validators. Validators need to have sufficient bandwidth, RAM and processing power to handle large amount of transactions and the recent and ongoing RC tests are going to expose these vulnerabilities. With these vulnerabilities exposed our Devs can work out a solution to prevent these problems from happening before we go on mainnet.

Hackers spamming the network with TX's and DDOSing validators I think is the only major stumbling block left here. If dev can put a countermeasure on this then the road ahead is clear for us to travel.

[xibeijan]

RC2 is still broken for me..

All I get is

11/13 19:22:51 [client-0] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE
11/13 19:22:51 [client-1] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE
11/13 19:22:52 [client-2] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE
11/13 19:22:52 [client-3] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE
11/13 19:22:53 [client-4] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE
11/13 19:26:50 [client-5] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE

Someone please have a look into this?

[mdodong]

RC2 is still broken for me..

All I get is

11/13 19:22:51 [client-0] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE
11/13 19:22:51 [client-1] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE
11/13 19:22:52 [client-2] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE
11/13 19:22:52 [client-3] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE
11/13 19:22:53 [client-4] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE
11/13 19:26:50 [client-5] INFO SemuxP2pHandler - Received DISCONNECT msg, reason = INVALID_HANDSHAKE

Someone please have a look into this?

visit us on Discord for faster response.

[wiredideas]

Semux Network is looking good now. Double clicked on Semux to launch it, it syncs with the network for a couple of minutes then all is well, worked like a charm every time. 

[tigermonkey]

Ungraded from RC1 to RC2. Tried to copy the database from RC1 to RC2 to save sync time, but it failed (invalid block). After resyncing the chain database,  it works.

[chichidori]

Ungraded from RC1 to RC2. Tried to copy the database from RC1 to RC2 to save sync time, but it failed (invalid block). After resyncing the chain database,  it works.

Just to be safe when a new update about the wallet comes up always start with a fresh sync or its better to start all over again rather than importing the database from the previous build. just don`t forget to back up your wallet every time.

[Phash2k]

upgrade for it is not compatible with older versions!

[0verseer]

Ungraded from RC1 to RC2. Tried to copy the database from RC1 to RC2 to save sync time, but it failed (invalid block). After resyncing the chain database,  it works.

Dev said it before, update it but don't copy the database from the old one.

[mcall]

   I  think  the wallet  (Latest release: Semux v1.0.0-rc.2 ) is better than  before.  I cannot find my semux coin in V1.0.0-rc.1. i cannot find any reason. When I downloaded  v1.0.0-rc.2  it appears. New wallet  donot appear java. It likes a real wallet.