[ANN][SEM] Semux - Official Thread

[Saimabutterfly]

My account is upgraded to Full Member. Do I need to join again or you will auto upgrade me for the next week?

[1714703507]

1714703507

[1714703507]

1714703507

[1714703507]

1714703507

[usechain]

why the newest wallet don't have 3 SEM on block?
I had been download the wallet,but the mining was only 1 SEM but not 3 SEM

[kumiskura]

My account is upgraded to Full Member. Do I need to join again or you will auto upgrade me for the next week?

if everything is ok,
you do not need to register again in the future because the bot will upgrade your rank automatically.
but it would be better for you to check it again when the list is out.

[lda1000]

How many validators upgraded yet?
Stress-test is soon?

64 right now ,next will open 100 slot.

I think he means how many validators upgraded to RC5, When majority of them is on RC5 then devs can perform the 10,000 transaction per block test.

[mdodong]

Where can I see the table of participants in the company of signatures?

Current list of participants are found on page 1. This list is updated weekly.

[xibeijan]

I think SEMUX can be equal value of NEO,it is not difficult at all.just be patience and wait.

I agree.

[sanada.motokage]

I think SEMUX can be equal value of NEO,it is not difficult at all.just be patience and wait.

I agree.

Right now, I haven't seen the real novelty in technology or marketing, that's too optimistic. But the Java version mining has its original contribution, so the future is bright.

[shadowbummer]

Im getting 0 peers when I open my wallet.  Im on a fresh install of Win10 x64 using the RC5 wallet.  My IP in the debug file is correct but I get the following:

-01-05 08:29:01 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = DUPLICATE_PEER_ID, remoteIP = 127.0.0.1
18-01-05 08:29:01 [INFO]   Kernel           Found a gateway device: local address = 192.168.1.3, external address = XX.XXX.XXX.XX
18-01-05 08:29:11 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 88.80.187.200
18-01-05 08:29:12 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 45.79.68.226
18-01-05 08:29:12 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 172.104.58.70
18-01-05 08:29:12 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 139.162.66.86
18-01-05 08:29:39 [INFO]   Kernel           Shutting down GUI
18-01-05 08:29:39 [INFO]   SemuxGUI         Data refresh interrupted, exiting
18-01-05 08:29:39 [INFO]   SemuxBFT         Consensus stopped
18-01-05 08:29:39 [INFO]   PeerServer       PeerServer shut down
18-01-05 08:29:39 [INFO]   NodeManager      Node manager stopped
18-01-05 08:29:39 [INFO]   PeerClient       Shutting down PeerClient

I had a similar problem (DUPLICATE_PEER_ID), they fixed something and after re-downloading RC5 I was able to sync.
Try re-downloading rc5 from github?

Im on version 8 Update 151 (build 1.8.0_151-b12), is that the right one?

I'm on 9.0.1+11. Did you try to re-download rc5 from github?

Ok, I just re-downloaded the Semux wallet from Github, ive opened port 5161 and checked its open, im on the current version of Java script (version 8, 151), ive just completed disabled Bitdefender and I still have 0 peers and the same Disconnect message in the debug file.  Whats going on....?!!?!

[xibeijan]

I think SEMUX can be equal value of NEO,it is not difficult at all.just be patience and wait.

I agree.

Right now, I haven't seen the real novelty in technology or marketing, that's too optimistic. But the Java version mining has its original contribution, so the future is bright.

Semux is in a really good position to solve a lot of the core scaling problems faced by bitcoin and ethereum and should probably not even bother competing with smaller projects like Neo.

[michael555]

Hi,

I wasn't airdropped 20 semux for signing my bitcoin address which had 0.7 at the time of the snapshot. I verified using https://www.semux.org/btc/ and then sent it in the google form on the thread. Can you let me know what to do to claim it?

[elr01]

Was the payment made? I have not received anything since the time I'm posting with this signature.

[timas]

Download and install Java...

What??? App go to the trash!

[CosaNostra]

Hi,

I wasn't airdropped 20 semux for signing my bitcoin address which had 0.7 at the time of the snapshot. I verified using https://www.semux.org/btc/ and then sent it in the google form on the thread. Can you let me know what to do to claim it?

Give it some time maybe, btc airdrop is processed along with the signature payments afaik.

[Bavaria]

Hi,

I wasn't airdropped 20 semux for signing my bitcoin address which had 0.7 at the time of the snapshot. I verified using https://www.semux.org/btc/ and then sent it in the google form on the thread. Can you let me know what to do to claim it?

Airdrop processing every sunday afternoon. This information in the OP.

[Phash2k]

Im getting 0 peers when I open my wallet.  Im on a fresh install of Win10 x64 using the RC5 wallet.  My IP in the debug file is correct but I get the following:

-01-05 08:29:01 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = DUPLICATE_PEER_ID, remoteIP = 127.0.0.1
18-01-05 08:29:01 [INFO]   Kernel           Found a gateway device: local address = 192.168.1.3, external address = XX.XXX.XXX.XX
18-01-05 08:29:11 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 88.80.187.200
18-01-05 08:29:12 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 45.79.68.226
18-01-05 08:29:12 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 172.104.58.70
18-01-05 08:29:12 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 139.162.66.86
18-01-05 08:29:39 [INFO]   Kernel           Shutting down GUI
18-01-05 08:29:39 [INFO]   SemuxGUI         Data refresh interrupted, exiting
18-01-05 08:29:39 [INFO]   SemuxBFT         Consensus stopped
18-01-05 08:29:39 [INFO]   PeerServer       PeerServer shut down
18-01-05 08:29:39 [INFO]   NodeManager      Node manager stopped
18-01-05 08:29:39 [INFO]   PeerClient       Shutting down PeerClient

I had a similar problem (DUPLICATE_PEER_ID), they fixed something and after re-downloading RC5 I was able to sync.
Try re-downloading rc5 from github?

Im on version 8 Update 151 (build 1.8.0_151-b12), is that the right one?

I'm on 9.0.1+11. Did you try to re-download rc5 from github?

Ok, I just re-downloaded the Semux wallet from Github, ive opened port 5161 and checked its open, im on the current version of Java script (version 8, 151), ive just completed disabled Bitdefender and I still have 0 peers and the same Disconnect message in the debug file.  Whats going on....?!!?!

had the same, just restarted it some times and it worked :>

[semux]

Im getting 0 peers when I open my wallet.  Im on a fresh install of Win10 x64 using the RC5 wallet.  My IP in the debug file is correct but I get the following:

-01-05 08:29:01 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = DUPLICATE_PEER_ID, remoteIP = 127.0.0.1
18-01-05 08:29:01 [INFO]   Kernel           Found a gateway device: local address = 192.168.1.3, external address = XX.XXX.XXX.XX
18-01-05 08:29:11 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 88.80.187.200
18-01-05 08:29:12 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 45.79.68.226
18-01-05 08:29:12 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 172.104.58.70
18-01-05 08:29:12 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 139.162.66.86
18-01-05 08:29:39 [INFO]   Kernel           Shutting down GUI
18-01-05 08:29:39 [INFO]   SemuxGUI         Data refresh interrupted, exiting
18-01-05 08:29:39 [INFO]   SemuxBFT         Consensus stopped
18-01-05 08:29:39 [INFO]   PeerServer       PeerServer shut down
18-01-05 08:29:39 [INFO]   NodeManager      Node manager stopped
18-01-05 08:29:39 [INFO]   PeerClient       Shutting down PeerClient

I had a similar problem (DUPLICATE_PEER_ID), they fixed something and after re-downloading RC5 I was able to sync.
Try re-downloading rc5 from github?

Im on version 8 Update 151 (build 1.8.0_151-b12), is that the right one?

I'm on 9.0.1+11. Did you try to re-download rc5 from github?

Ok, I just re-downloaded the Semux wallet from Github, ive opened port 5161 and checked its open, im on the current version of Java script (version 8, 151), ive just completed disabled Bitdefender and I still have 0 peers and the same Disconnect message in the debug file.  Whats going on....?!!?!

had the same, just restarted it some times and it worked :>

Please ignore the DUPLICATE_PEER_ID message for now (it has been fixed in the develop branch).

For the INVALID_HANDSHAKE error, it's either because your IP is incorrect or your computer time is not synchronized. If the auto detected IP is incorrect in the log, you can try modifying the config/semux.properties file:

Code:

p2p.declaredIp = xx.xx.xx.xx

[Ratamahatta]

Hello, semux! I have just registered in your signature campaign, how can i find myself in the list of participants? and where do i have to report my messages (10 per week) ?

[angielec]

Hello, semux! I have just registered in your signature campaign, how can i find myself in the list of participants? and where do i have to report my messages (10 per week) ?

the list of participants will arrive soon. Sunday in the afternoon normally.
And you can post anywhere on the forum.

[Fabriz]

There is an exchange to get Semux ?

[JWKY]

There is an exchange to get Semux ?

please be patient
semux not yet final release