[ANN][SEM] Semux - Official Thread

[GMule]

Does anyone know if network need re-sync after upgrade to rc5, or can I just copy over?

[1714891506]

1714891506

[1714891506]

1714891506

[1714891506]

1714891506

[leoirssi]

Does anyone know if network need re-sync after upgrade to rc5, or can I just copy over?

You need to resync

[vingaard]

Week 5 participants:

https://www.semux.org/assets/week5.txt

Thanks 

Here we go!!!... next stop 5th airdrop!!! 

Good work Dev 

[GMule]

Does anyone know if network need re-sync after upgrade to rc5, or can I just copy over?

You need to resync

Thanks.

I also see there are xmx tuning in RC5, can someone point me to were and what the values are set?

[premium_domainer]

Does anyone know if network need re-sync after upgrade to rc5, or can I just copy over?

You need to resync

No you don't need to rescync.

I just put my database folder and my wallet data and it was working with no problem. I always check first like this way.

[leoirssi]

Does anyone know if network need re-sync after upgrade to rc5, or can I just copy over?

You need to resync

No you don't need to rescync.

I just put my database folder and my wallet data and it was working with no problem. I always check first like this way.

There were some complaints on Discord that it doesn't work with the old database...so just to be on the safe side I recommend you to delete old databse and do a full resync.

[Messier81]

Semux v1.0.0-rc.5 released, https://github.com/semuxproject/semux/releases

What's the deadline to update to rc.5?

It's not mandatory but very recommended. Dev is waiting for enough validators to upgrade and will do another stress test. Please update as soon as possible.

Can't wait for stress test!  10,000 txs/block here we come! (I hope)  

10,000 txs/block Wow this is impressive! How big are the blocks? 2M?

Currently dev has increased the block size to 2MB to test if the network can handle increased transaction. Once enough validators upgrade to RC5 a series of network stress test will be conducted.

I'm unable to sync with RC5 and I'm stuck with RC3 unable to upgrade.

Please fix the bug:

https://github.com/semuxproject/semux/issues/373

[GMule]

Does anyone know if network need re-sync after upgrade to rc5, or can I just copy over?

You need to resync

No you don't need to rescync.

I just put my database folder and my wallet data and it was working with no problem. I always check first like this way.

Would there be any harm in trying this do you think?  I can see the obvious benefits...

[leoirssi]

Semux v1.0.0-rc.5 released, https://github.com/semuxproject/semux/releases

What's the deadline to update to rc.5?

It's not mandatory but very recommended. Dev is waiting for enough validators to upgrade and will do another stress test. Please update as soon as possible.

Can't wait for stress test!  10,000 txs/block here we come! (I hope)  

10,000 txs/block Wow this is impressive! How big are the blocks? 2M?

Currently dev has increased the block size to 2MB to test if the network can handle increased transaction. Once enough validators upgrade to RC5 a series of network stress test will be conducted.

I'm unable to sync with RC5 and I'm stuck with RC3 unable to upgrade.

Please fix the bug:

https://github.com/semuxproject/semux/issues/373

Are you sure that there is no other semux wallet running on your machine?

Try this:
1. close Semux RC.3
2. check if there is no semux running with command below:

Code:

sudo ps aux | grep semux

3. download and run RC5 and post here the result.

I'm running rc5 on Ubuntu 16.04.3 without any issues.

[Messier81]

Thanks, but I'm 1000000% sure the aren't any other instances running.

[leoirssi]

Thanks, but I'm 1000000% sure the aren't any other instances running.

Try to update your system and Java:

Code:

apt-get update && apt-get upgrade

[Messier81]

Thanks, but I'm 1000000% sure the aren't any other instances running.

Try to update your system and Java:

Code:

apt-get update && apt-get upgrade

Java is up to date

ii  oracle-java9-installer                     9.0.1-1~webupd8~0                            amd64        Oracle Java(TM) Development Kit (JDK) 9
ii  oracle-java9-set-default                 9.0.1-1~webupd8~0                            amd64        Set Oracle JDK 9 as default Java


09:55:57.804 [INFO]   PeerClient       Starting IP refresh thread
09:55:57.937 [INFO]   NodeManager      Node manager started
09:55:58.141 [INFO]   PeerServer       Starting peer server: address = 0.0.0.0:5161
09:55:58.202 [INFO]   SemuxBFT         Consensus started
09:55:58.204 [INFO]   SemuxBFT         Entered new_height: height = 1, # validators = 4
09:55:58.239 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = DUPLICATE_PEER_ID
09:55:58.608 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE
09:55:59.363 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE
09:56:00.097 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE
09:56:00.587 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE


As I'm saying RC5 is broken for me. RC3 works fine. I can go to my rc3 dir, start it and it works. When I stop it and go to RC5 dir, start it, then it's stuck with the above error.

[leoirssi]

Thanks, but I'm 1000000% sure the aren't any other instances running.

Try to update your system and Java:

Code:

apt-get update && apt-get upgrade

Java is up to date

ii  oracle-java9-installer                     9.0.1-1~webupd8~0                            amd64        Oracle Java(TM) Development Kit (JDK) 9
ii  oracle-java9-set-default                 9.0.1-1~webupd8~0                            amd64        Set Oracle JDK 9 as default Java


09:55:57.804 [INFO]   PeerClient       Starting IP refresh thread
09:55:57.937 [INFO]   NodeManager      Node manager started
09:55:58.141 [INFO]   PeerServer       Starting peer server: address = 0.0.0.0:5161
09:55:58.202 [INFO]   SemuxBFT         Consensus started
09:55:58.204 [INFO]   SemuxBFT         Entered new_height: height = 1, # validators = 4
09:55:58.239 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = DUPLICATE_PEER_ID
09:55:58.608 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE
09:55:59.363 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE
09:56:00.097 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE
09:56:00.587 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE


As I'm saying RC5 is broken for me. RC3 works fine. I can go to my rc3 dir, start it and it works. When I stop it and go to RC5 dir, start it, then it's stuck with the above error.

Hm not sure how it works with Java9...

Works fine with version 8.

openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-8u151-b12-0ubuntu0.16.04.2-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)

I think devs will have take a look at this.

[BigShoe99]

i need understanding on how the BTC airdrops is being disbursed? Anyone

[sprinkles]

Rewards are dropping steadily whilst the community grows nicely.
Have gone from 169 SEM > 116 SEM > 102 SEM > 79 SEM since the sig campaign started.

[premium_domainer]

Does anyone know if network need re-sync after upgrade to rc5, or can I just copy over?

You need to resync

No you don't need to rescync.

I just put my database folder and my wallet data and it was working with no problem. I always check first like this way.

Would there be any harm in trying this do you think?  I can see the obvious benefits...

The only thing is important to you is the wallet.data. If you are making a back-up for it, you can do anything you want. Risk-free.

[lda1000]

i need understanding on how the BTC airdrops is being disbursed? Anyone

There was a snapshot taken of all balances on height #480000. You need to sign your Semux address with your btc address that had a balance on that height and you're going to get SEM.

[mdodong]

Rewards are dropping steadily whilst the community grows nicely.
Have gone from 169 SEM > 116 SEM > 102 SEM > 79 SEM since the sig campaign started.

This is expected since we are getting more participants and the bounty is fixed. This will help spreading the coin and getting more attention to the project.

[lda1000]

Rewards are dropping steadily whilst the community grows nicely.
Have gone from 169 SEM > 116 SEM > 102 SEM > 79 SEM since the sig campaign started.

Number of accounts grew from less than 1k to over 4k recently

http://semuxchain.info/accounts/

more people are joining which is of course awesome

[mdodong]

Thanks, but I'm 1000000% sure the aren't any other instances running.

Try to update your system and Java:

Code:

apt-get update && apt-get upgrade

Java is up to date

ii  oracle-java9-installer                     9.0.1-1~webupd8~0                            amd64        Oracle Java(TM) Development Kit (JDK) 9
ii  oracle-java9-set-default                 9.0.1-1~webupd8~0                            amd64        Set Oracle JDK 9 as default Java


09:55:57.804 [INFO]   PeerClient       Starting IP refresh thread
09:55:57.937 [INFO]   NodeManager      Node manager started
09:55:58.141 [INFO]   PeerServer       Starting peer server: address = 0.0.0.0:5161
09:55:58.202 [INFO]   SemuxBFT         Consensus started
09:55:58.204 [INFO]   SemuxBFT         Entered new_height: height = 1, # validators = 4
09:55:58.239 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = DUPLICATE_PEER_ID
09:55:58.608 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE
09:55:59.363 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE
09:56:00.097 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE
09:56:00.587 [INFO]   SemuxP2pHandler  Received DISCONNECT msg, reason = INVALID_HANDSHAKE


As I'm saying RC5 is broken for me. RC3 works fine. I can go to my rc3 dir, start it and it works. When I stop it and go to RC5 dir, start it, then it's stuck with the above error.

Start fresh with RC5. Download a new copy, delete the old database folder, restart pc and start resync from block #0.