youyou_
|
|
March 09, 2018, 04:23:21 AM |
|
i have already spreaded this group invite link to chinese community ,happy communcation in telegram guys .
|
|
|
|
crimealone
|
|
March 09, 2018, 04:30:37 AM |
|
Is there any update now? the new version was released , update the new version as quickly as possible. My friend told me that the new version of the wallet is not stable, it can not be synchronized, is it like this? When I use this version is 1.0, it also has this problem, sometimes not synchronized It's better than the last version.
|
|
|
|
Kenway
|
|
March 09, 2018, 04:54:56 AM |
|
Is there any update now? the new version was released , update the new version as quickly as possible. My friend told me that the new version of the wallet is not stable, it can not be synchronized, is it like this? When I use this version is 1.0, it also has this problem, sometimes not synchronized It's better than the last version. semux community should provide your support to dev ,better to use last version ,if there are some bugs ,dev will find and fix .
|
|
|
|
bitdealer91
|
|
March 09, 2018, 05:23:22 AM |
|
Is there any update now? the new version was released , update the new version as quickly as possible. My friend told me that the new version of the wallet is not stable, it can not be synchronized, is it like this? When I use this version is 1.0, it also has this problem, sometimes not synchronized It's better than the last version. semux community should provide your support to dev ,better to use last version ,if there are some bugs ,dev will find and fix . I installed the latest version of the wallet, the synchronization went without any problems. No errors found.
|
|
|
|
roflwaffle
Newbie
Offline
Activity: 42
Merit: 0
|
|
March 09, 2018, 07:09:54 AM |
|
I have noticed a trend recently.
While there have not been more public pools, there have been a surge of private pools
there are not enough public pools, and as consequence, they are over voted.
So folks are starting private pools to control number of votes for best payouts.
If you're currently voting for an over-voted public pool, might be worth joining in to a private pool to maximize payouts.
As for new version.. many bugs have been fixed, and there have not been any new bugs reported. If you are seeing bugs, please report them (there is a bug bounty)
|
|
|
|
Phash2k
|
|
March 09, 2018, 07:43:16 AM |
|
As for decentralization my Pool "Phash" is paying out regularly to all voters with a fee of 7% + dev fee! I might set up another one, when there is the need for it.
I am not hosted on vultr to gain some diversity for the validators
|
Crypto-Beratung und Hilfe bei allen möglichen Crypto-Projekten oder Problemen! https://phash.de
|
|
|
dreamhouse
|
|
March 09, 2018, 08:12:06 AM |
|
where is it trading? want to sell it...
That's funny. I am actually in the same boat. mainly due to the fact that I never tried to find out where It was trading lol. The last I heard was that Semux was $2.5 Visit Semux Discord channel... # tradingno exchange for it? this one I heard for some time, still no exchange??
|
|
|
|
U
|
|
March 09, 2018, 08:35:28 AM |
|
WTS 30K PM if interested.
|
Bitcoin Ethereum TERA
|
|
|
pirangueiro
|
|
March 09, 2018, 08:54:19 AM |
|
Now way, the new wallet stop syncing.
3-09T09:47:25+0100 INFO SemuxSync Syncing started, best known block = 129920 2018-03-09T09:47:28+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 45.56.49.74 2018-03-09T09:47:39+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.17 2018-03-09T09:47:40+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.13 2018-03-09T09:47:47+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.238.157.46 2018-03-09T09:47:51+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 46.72.10.236
|
|
|
|
Phash2k
|
|
March 09, 2018, 08:56:14 AM |
|
Now way, the new wallet stop syncing.
3-09T09:47:25+0100 INFO SemuxSync Syncing started, best known block = 129920 2018-03-09T09:47:28+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 45.56.49.74 2018-03-09T09:47:39+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.17 2018-03-09T09:47:40+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.13 2018-03-09T09:47:47+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.238.157.46 2018-03-09T09:47:51+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 46.72.10.236
do you have 2 wallets on the same IP? Close the old one
|
Crypto-Beratung und Hilfe bei allen möglichen Crypto-Projekten oder Problemen! https://phash.de
|
|
|
pirangueiro
|
|
March 09, 2018, 09:07:36 AM |
|
Now way, the new wallet stop syncing.
3-09T09:47:25+0100 INFO SemuxSync Syncing started, best known block = 129920 2018-03-09T09:47:28+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 45.56.49.74 2018-03-09T09:47:39+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.17 2018-03-09T09:47:40+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.13 2018-03-09T09:47:47+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.238.157.46 2018-03-09T09:47:51+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 46.72.10.236
do you have 2 wallets on the same IP? Close the old one Yes, 2 Wallets installed. But i so started the new one.
|
|
|
|
borderline
|
|
March 09, 2018, 10:27:04 AM |
|
Now way, the new wallet stop syncing.
3-09T09:47:25+0100 INFO SemuxSync Syncing started, best known block = 129920 2018-03-09T09:47:28+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 45.56.49.74 2018-03-09T09:47:39+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.17 2018-03-09T09:47:40+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.13 2018-03-09T09:47:47+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.238.157.46 2018-03-09T09:47:51+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 46.72.10.236
do you have 2 wallets on the same IP? Close the old one Yes, 2 Wallets installed. But i so started the new one. 2 wallet.data files? if yes use the last opened.. wait for full synch and after copy the other wallet.data file and reopen wallet
|
|
|
|
mdodong
|
|
March 09, 2018, 10:46:32 AM |
|
where is it trading? want to sell it...
That's funny. I am actually in the same boat. mainly due to the fact that I never tried to find out where It was trading lol. The last I heard was that Semux was $2.5 Visit Semux Discord channel... # tradingno exchange for it? this one I heard for some time, still no exchange?? Exchange listing is put on hold until necessary code are put into place. Please see the GitHub discussion below regarding the matter: https://github.com/semuxproject/semux/issues/621
|
|
|
|
Mercedes
|
|
March 09, 2018, 10:48:25 AM |
|
where is it trading? want to sell it...
That's funny. I am actually in the same boat. mainly due to the fact that I never tried to find out where It was trading lol. The last I heard was that Semux was $2.5 Visit Semux Discord channel... # tradingno exchange for it? this one I heard for some time, still no exchange?? Exchange listing is put on hold until necessary code are put into place. Please see the GitHub discussion below regarding the matter: https://github.com/semuxproject/semux/issues/621hold a monment ,all cryptos dropped ,this is not the right now to hit exchange ,waitting for the bull market is better.
|
|
|
|
iuhkymt
Newbie
Offline
Activity: 39
Merit: 0
|
|
March 09, 2018, 11:10:27 AM |
|
Is there any update now? the new version was released , update the new version as quickly as possible. My friend told me that the new version of the wallet is not stable, it can not be synchronized, is it like this? When I use this version is 1.0, it also has this problem, sometimes not synchronized It's better than the last version. New version of SEMUX wallet works well. I like this one and hope it will keep good performance for a long time before new wallet published.
|
|
|
|
Kenrich
|
|
March 09, 2018, 11:13:05 AM |
|
Is there any update now? the new version was released , update the new version as quickly as possible. My friend told me that the new version of the wallet is not stable, it can not be synchronized, is it like this? When I use this version is 1.0, it also has this problem, sometimes not synchronized It's better than the last version. New version of SEMUX wallet works well. I like this one and hope it will keep good performance for a long time before new wallet published. my new wallet really work fine ,never stuck one block ,maybe it's your network problem . new wallet UI look nice .
|
|
|
|
Phash2k
|
|
March 09, 2018, 11:47:21 AM |
|
didn't download the local client yet, but will take a look today
|
Crypto-Beratung und Hilfe bei allen möglichen Crypto-Projekten oder Problemen! https://phash.de
|
|
|
pirangueiro
|
|
March 09, 2018, 12:06:50 PM |
|
Now way, the new wallet stop syncing.
3-09T09:47:25+0100 INFO SemuxSync Syncing started, best known block = 129920 2018-03-09T09:47:28+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 45.56.49.74 2018-03-09T09:47:39+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.17 2018-03-09T09:47:40+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.13 2018-03-09T09:47:47+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.238.157.46 2018-03-09T09:47:51+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 46.72.10.236
do you have 2 wallets on the same IP? Close the old one Yes, 2 Wallets installed. But i so started the new one. 2 wallet.data files? if yes use the last opened.. wait for full synch and after copy the other wallet.data file and reopen wallet Do not work. it seems to be a java problem. A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_UNCAUGHT_CXX_EXCEPTION (0xe06d7363) at pc=0x7683c54f, pid=896, tid=0x00000d5c # # JRE version: Java(TM) SE Runtime Environment (8.0_161-b12) (build 1.8.0_161-b12) # Java VM: Java HotSpot(TM) Client VM (25.161-b12 mixed mode windows-x86 ) # Problematic frame: # C [KERNELBASE.dll+0xc54f] # # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows #
|
|
|
|
borderline
|
|
March 09, 2018, 12:18:20 PM |
|
Now way, the new wallet stop syncing.
3-09T09:47:25+0100 INFO SemuxSync Syncing started, best known block = 129920 2018-03-09T09:47:28+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 45.56.49.74 2018-03-09T09:47:39+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.17 2018-03-09T09:47:40+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.13 2018-03-09T09:47:47+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.238.157.46 2018-03-09T09:47:51+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 46.72.10.236
do you have 2 wallets on the same IP? Close the old one Yes, 2 Wallets installed. But i so started the new one. 2 wallet.data files? if yes use the last opened.. wait for full synch and after copy the other wallet.data file and reopen wallet Do not work. it seems to be a java problem. A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_UNCAUGHT_CXX_EXCEPTION (0xe06d7363) at pc=0x7683c54f, pid=896, tid=0x00000d5c # # JRE version: Java(TM) SE Runtime Environment (8.0_161-b12) (build 1.8.0_161-b12) # Java VM: Java HotSpot(TM) Client VM (25.161-b12 mixed mode windows-x86 ) # Problematic frame: # C [KERNELBASE.dll+0xc54f] # # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows # i never see this error before... only think you can do is delete database folder and retry.. but i think too many peers error are not connect to this one.. maybe try first to reinstall java
|
|
|
|
yadan86
|
|
March 09, 2018, 12:26:17 PM |
|
Now way, the new wallet stop syncing.
3-09T09:47:25+0100 INFO SemuxSync Syncing started, best known block = 129920 2018-03-09T09:47:28+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 45.56.49.74 2018-03-09T09:47:39+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.17 2018-03-09T09:47:40+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.225.220.13 2018-03-09T09:47:47+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 104.238.157.46 2018-03-09T09:47:51+0100 INFO SemuxP2pHandler Received DISCONNECT message: reason = TOO_MANY_PEERS, remoteIP = 46.72.10.236
do you have 2 wallets on the same IP? Close the old one Yes, 2 Wallets installed. But i so started the new one. 2 wallet.data files? if yes use the last opened.. wait for full synch and after copy the other wallet.data file and reopen wallet Do not work. it seems to be a java problem. A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_UNCAUGHT_CXX_EXCEPTION (0xe06d7363) at pc=0x7683c54f, pid=896, tid=0x00000d5c # # JRE version: Java(TM) SE Runtime Environment (8.0_161-b12) (build 1.8.0_161-b12) # Java VM: Java HotSpot(TM) Client VM (25.161-b12 mixed mode windows-x86 ) # Problematic frame: # C [KERNELBASE.dll+0xc54f] # # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows # i never see this error before... only think you can do is delete database folder and retry.. but i think too many peers error are not connect to this one.. maybe try first to reinstall java Failed to write core dump. Minidumps are not enabled by default on client versions of Windowsyou are not enable Minidumps ,you can fix this problem https://stackoverflow.com/questions/18459037/how-to-enable-minidumps-in-java-for-windowsthe easy way is reintall he newest version jre
|
|
|
|
|