Author

Topic: [ANN][SEM] Semux - Official Thread - page 381. (Read 694145 times)

member
Activity: 131
Merit: 18
November 14, 2017, 04:52:20 PM
This Project Rocks!

Waiting for the VM to bei powered up

Great project! VM next year?

Early 2018: First release with Semux BFT consensus
TBA: Second release with Semux virtual machine
TBA: Third release with Semux smart contract
newbie
Activity: 74
Merit: 0
November 14, 2017, 01:32:44 PM
This Project Rocks!

Waiting for the VM to bei powered up

Great project! VM next year?
full member
Activity: 532
Merit: 102
November 14, 2017, 01:03:44 PM
This Project Rocks!

Waiting for the VM to bei powered up
full member
Activity: 352
Merit: 104
SquidCoin.cash
November 14, 2017, 12:08:03 PM
I would like to see good news from the development team. Lately, there have been a lot of software changes. I see a good team work.
full member
Activity: 532
Merit: 102
November 14, 2017, 10:31:50 AM
I think we should be able to update the wallet in the old wallet,it's more easy and convenient for the user to do it.
why we choose this way to update?
allow the wallet develop,I think this project would be more successful than other project.

just use the upgraded version - the blockchain is no longer compatible with v RC1
hero member
Activity: 666
Merit: 500
November 14, 2017, 07:17:51 AM
dear dev, any news on the upcoming airdrop please?
full member
Activity: 560
Merit: 112
November 14, 2017, 06:14:28 AM
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.

I do software, so I know how usually strangers coming in and proposing "simple solutions" is a reason to face-palm, so forgive me if I am talking nonsense...

In such a situation, I would either have a couple of "dark validator nodes" that light up once others go down (latencies and throughput should be measurable) or have a large pool of nodes and have them switch on and off in a random fashion so the mean is 64 active validators.

Both make it harder keeping a sustained dDOS going. In your current setup, I'd be afraid of knock-on effects of a percentage of the validators getting taken out.

Thank you for the feedback.

We are taking all proposals into consideration in making sure we ship a stable network once we go live.

Please check our github page and see if you'll be interested to contribute. We are looking to expand our team and are very much open for qualified contributors. 

full member
Activity: 307
Merit: 100
0xb58D6E68944e195420843fA98c4A3481a5914282
November 14, 2017, 06:05:01 AM
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.

I do software, so I know how usually strangers coming in and proposing "simple solutions" is a reason to face-palm, so forgive me if I am talking nonsense...

In such a situation, I would either have a couple of "dark validator nodes" that light up once others go down (latencies and throughput should be measurable) or have a large pool of nodes and have them switch on and off in a random fashion so the mean is 64 active validators.

Both make it harder keeping a sustained dDOS going. In your current setup, I'd be afraid of knock-on effects of a percentage of the validators getting taken out.
hero member
Activity: 843
Merit: 1004
November 14, 2017, 05:48:48 AM
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.

Can't right now  Please  paste my message into your discord window?

Quote
INVALID_HANDSHAKE"
This means the other peer failed to validate your handshake message, either signature or timestamp or IP is incorrect.


I thought I should make a quote. Have you checked all this?
full member
Activity: 560
Merit: 112
November 14, 2017, 05:23:52 AM
RC2 is still broken for me..

All I get is

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.

Can't right now  Please  paste my message into your discord window?

What's your set up?
VPS or Home PC? OS, Java version?

Also make sure date and time is updated.
legendary
Activity: 1232
Merit: 1001
November 14, 2017, 04:27:47 AM
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.

Can't right now  Please  paste my message into your discord window?
sr. member
Activity: 541
Merit: 250
November 14, 2017, 03:08:37 AM
I think we should be able to update the wallet in the old wallet,it's more easy and convenient for the user to do it.
why we choose this way to update?
allow the wallet develop,I think this project would be more successful than other project.
That's a good idea. As far as I know, many updates are mandatory, and direct updates may be bug.
full member
Activity: 162
Merit: 100
November 14, 2017, 03:03:13 AM
I think we should be able to update the wallet in the old wallet,it's more easy and convenient for the user to do it.
why we choose this way to update?
allow the wallet develop,I think this project would be more successful than other project.
full member
Activity: 292
Merit: 100
November 14, 2017, 02:53:04 AM
   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.
full member
Activity: 480
Merit: 106
November 14, 2017, 02:34:51 AM
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.
full member
Activity: 532
Merit: 102
November 14, 2017, 12:55:12 AM
upgrade for it is not compatible with older versions!
legendary
Activity: 1694
Merit: 1003
November 14, 2017, 12:45:25 AM
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.
full member
Activity: 158
Merit: 100
November 14, 2017, 12:30:26 AM
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.
full member
Activity: 756
Merit: 101
November 13, 2017, 10:41:11 PM
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.  Smiley


full member
Activity: 560
Merit: 112
November 13, 2017, 06:47:35 PM
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.
Jump to: