Author

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

full member
Activity: 286
Merit: 115
January 13, 2018, 12:37:52 PM
How large is the Semux blockchain?
I was able to create a Semux wallet but I did not fully sync the blockchain.
Is my Semux wallet address eligible for the BTC airdrop or must I fully sync first?

Thanks


I waited a long time for my coins and then i realised that in the corner of the wallet they sync... and my wallet was some days behind... so i let them sync and get my coins...
Always let the Wallet sync!  Smiley
member
Activity: 71
Merit: 12
January 13, 2018, 12:27:36 PM
How large is the Semux blockchain?
I was able to create a Semux wallet but I did not fully sync the blockchain.
Is my Semux wallet address eligible for the BTC airdrop or must I fully sync first?

Thanks


I waited a long time for my coins and then i realised that in the corner of the wallet they sync... and my wallet was some days behind... so i let them sync and get my coins...
full member
Activity: 193
Merit: 100
January 13, 2018, 10:33:56 AM
I am interested in how to mine the Semux,and wonder what's the point of semux better than others.
You can't mining, only get in Airdrop, or will be validator.
newbie
Activity: 6
Merit: 0
January 13, 2018, 10:21:42 AM
How large is the Semux blockchain?
I was able to create a Semux wallet but I did not fully sync the blockchain.
Is my Semux wallet address eligible for the BTC airdrop or must I fully sync first?

Thanks
newbie
Activity: 13
Merit: 0
January 13, 2018, 09:33:07 AM
I am interested in how to mine the Semux,and wonder what's the point of semux better than others.
member
Activity: 96
Merit: 10
January 13, 2018, 09:07:51 AM
My wallet is installed on Windows 64. The wallet fails, why?

Message:Syncing:stopped

Make sure your wallet is just correct with window system 64 bit. What I have to do is download latest version, backup my wallet.dta file (from old folder).Then copying it into the new folder, then running the new wallet again. Then everything will be ok.



My wallet is just correct with window system 64 bit. The wallet software is the latest version.
debug.log:

18-01-13 18:14:15 [INFO]   Kernel           Semux/v1.0.0-rc.5/Windows/amd64
18-01-13 18:14:15 [INFO]   Kernel           System booting up: networkId = 0, networkVersion = 4, coinbase = 91fb4796cea29f708528f72a44239e4a8cd11b3c
18-01-13 18:14:16 [INFO]   Kernel           Computer: manufacturer = Gigabyte Technology Co., Ltd., model = H81M-D2
18-01-13 18:14:16 [INFO]   Kernel           OS: name = Microsoft Windows 7 SP1 build 7601
18-01-13 18:14:16 [INFO]   Kernel           CPU: processor = Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz, cores = 2 / 4
18-01-13 18:14:16 [INFO]   Kernel           Memory: total = 3986 MB, available = 1052 MB, swap total = 20478 MB, swap available = 19253 MB
18-01-13 18:14:17 [INFO]   Kernel           Network: name = Teredo Tunneling Pseudo-Interface, ip = []
18-01-13 18:14:17 [INFO]   Kernel           Network: name = Realtek PCIe GBE Family Controller, ip = [192.168.1.124]
18-01-13 18:14:17 [INFO]   Kernel           Network: name = Microsoft ISATAP Adapter, ip = []
18-01-13 18:14:17 [INFO]   Kernel           Java: version = 1.8.0_102, xms = 1820 MB
18-01-13 18:14:17 [INFO]   Kernel           Latest block number = 0
18-01-13 18:14:17 [INFO]   PeerClient       Use IP address: 127.0.0.1
18-01-13 18:14:17 [INFO]   PeerClient       Starting IP refresh thread
18-01-13 18:14:17 [INFO]   NodeManager      Node manager started
18-01-13 18:14:17 [INFO]   PeerServer       Starting peer server: address = 0.0.0.0:5161
18-01-13 18:14:18 [INFO]   SemuxBFT         Consensus started
18-01-13 18:14:18 [INFO]   SemuxBFT         Entered new_height: height = 1, # validators = 4
18-01-13 18:14:18 [INFO]   PeerClient       New IP address detected: 127.0.0.1 => 211.97.167.33
18-01-13 18:14:28 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 88.80.187.200
18-01-13 18:14:28 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 45.79.68.226
18-01-13 18:14:29 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 172.104.58.70
18-01-13 18:14:29 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 139.162.66.86



Message:Syncing:stopped

Why?





Did you make sure you've the MS V C++ 2010 Redistributable Package installed?  Or maybe its a firewall thing?

full member
Activity: 480
Merit: 106
sr. member
Activity: 434
Merit: 250
January 13, 2018, 07:15:27 AM
My wallet is installed on Windows 64. The wallet fails, why?

Message:Syncing:stopped

Make sure your wallet is just correct with window system 64 bit. What I have to do is download latest version, backup my wallet.dta file (from old folder).Then copying it into the new folder, then running the new wallet again. Then everything will be ok.



My wallet is just correct with window system 64 bit. The wallet software is the latest version.
debug.log:

18-01-13 18:14:15 [INFO]   Kernel           Semux/v1.0.0-rc.5/Windows/amd64
18-01-13 18:14:15 [INFO]   Kernel           System booting up: networkId = 0, networkVersion = 4, coinbase = 91fb4796cea29f708528f72a44239e4a8cd11b3c
18-01-13 18:14:16 [INFO]   Kernel           Computer: manufacturer = Gigabyte Technology Co., Ltd., model = H81M-D2
18-01-13 18:14:16 [INFO]   Kernel           OS: name = Microsoft Windows 7 SP1 build 7601
18-01-13 18:14:16 [INFO]   Kernel           CPU: processor = Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz, cores = 2 / 4
18-01-13 18:14:16 [INFO]   Kernel           Memory: total = 3986 MB, available = 1052 MB, swap total = 20478 MB, swap available = 19253 MB
18-01-13 18:14:17 [INFO]   Kernel           Network: name = Teredo Tunneling Pseudo-Interface, ip = []
18-01-13 18:14:17 [INFO]   Kernel           Network: name = Realtek PCIe GBE Family Controller, ip = [192.168.1.124]
18-01-13 18:14:17 [INFO]   Kernel           Network: name = Microsoft ISATAP Adapter, ip = []
18-01-13 18:14:17 [INFO]   Kernel           Java: version = 1.8.0_102, xms = 1820 MB
18-01-13 18:14:17 [INFO]   Kernel           Latest block number = 0
18-01-13 18:14:17 [INFO]   PeerClient       Use IP address: 127.0.0.1
18-01-13 18:14:17 [INFO]   PeerClient       Starting IP refresh thread
18-01-13 18:14:17 [INFO]   NodeManager      Node manager started
18-01-13 18:14:17 [INFO]   PeerServer       Starting peer server: address = 0.0.0.0:5161
18-01-13 18:14:18 [INFO]   SemuxBFT         Consensus started
18-01-13 18:14:18 [INFO]   SemuxBFT         Entered new_height: height = 1, # validators = 4
18-01-13 18:14:18 [INFO]   PeerClient       New IP address detected: 127.0.0.1 => 211.97.167.33
18-01-13 18:14:28 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 88.80.187.200
18-01-13 18:14:28 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 45.79.68.226
18-01-13 18:14:29 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 172.104.58.70
18-01-13 18:14:29 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 139.162.66.86



Message:Syncing:stopped

Why?





i check my debut log ,there is different line with you .

18-01-02 00:37:04 [INFO]   SemuxBFT         Entered propose: height = 100254, view = 0, primary = false, # connected validators = 1 + 0
18-01-02 00:37:04 [INFO]   Kernel          Found a gateway device: local address = 192.168.1.107, external address = 122.233.224.4


check you network and firewall , maybe should need dev to check.
legendary
Activity: 1241
Merit: 1005
..like bright metal on a sullen ground.
January 13, 2018, 07:08:22 AM
Is the 0.5 voting fee and 1000 delegate registration fee paid to validators, or is it burned?

1000 delegate fee is burned, but will be returned when main net launches.
Low coin supply means high price! Do not give this coin away for under $5 (maybe even $10)...

Is it the same on the main net?  Main net delegate registration = burned coins?  Won't that potentially destroy a lot of supply?  Or do you think not many will try to be a delegate.

Yes, except on mainnet they are burned for good. There has to be a cost for registering as a delegate, otherwise someone could flood the network with delegates, among other things. There's around 100 million supply, with 100 validator spots, so even if 1000 people register as delegates (I doubt it will ever be that high) that would still only be a thousandth of one percent of total supply burned.
full member
Activity: 286
Merit: 115
full member
Activity: 798
Merit: 116
January 13, 2018, 05:52:57 AM
Is the 0.5 voting fee and 1000 delegate registration fee paid to validators, or is it burned?

1000 delegate fee is burned, but will be returned when main net launches.
Low coin supply means high price! Do not give this coin away for under $5 (maybe even $10)...

Is it the same on the main net?  Main net delegate registration = burned coins?  Won't that potentially destroy a lot of supply?  Or do you think not many will try to be a delegate.

it's a fee.. but it's better for all, less supply
full member
Activity: 201
Merit: 100
January 13, 2018, 05:30:00 AM
My wallet is installed on Windows 64. The wallet fails, why?

Message:Syncing:stopped

Make sure your wallet is just correct with window system 64 bit. What I have to do is download latest version, backup my wallet.dta file (from old folder).Then copying it into the new folder, then running the new wallet again. Then everything will be ok.



My wallet is just correct with window system 64 bit. The wallet software is the latest version.
debug.log:

18-01-13 18:14:15 [INFO]   Kernel           Semux/v1.0.0-rc.5/Windows/amd64
18-01-13 18:14:15 [INFO]   Kernel           System booting up: networkId = 0, networkVersion = 4, coinbase = 91fb4796cea29f708528f72a44239e4a8cd11b3c
18-01-13 18:14:16 [INFO]   Kernel           Computer: manufacturer = Gigabyte Technology Co., Ltd., model = H81M-D2
18-01-13 18:14:16 [INFO]   Kernel           OS: name = Microsoft Windows 7 SP1 build 7601
18-01-13 18:14:16 [INFO]   Kernel           CPU: processor = Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz, cores = 2 / 4
18-01-13 18:14:16 [INFO]   Kernel           Memory: total = 3986 MB, available = 1052 MB, swap total = 20478 MB, swap available = 19253 MB
18-01-13 18:14:17 [INFO]   Kernel           Network: name = Teredo Tunneling Pseudo-Interface, ip = []
18-01-13 18:14:17 [INFO]   Kernel           Network: name = Realtek PCIe GBE Family Controller, ip = [192.168.1.124]
18-01-13 18:14:17 [INFO]   Kernel           Network: name = Microsoft ISATAP Adapter, ip = []
18-01-13 18:14:17 [INFO]   Kernel           Java: version = 1.8.0_102, xms = 1820 MB
18-01-13 18:14:17 [INFO]   Kernel           Latest block number = 0
18-01-13 18:14:17 [INFO]   PeerClient       Use IP address: 127.0.0.1
18-01-13 18:14:17 [INFO]   PeerClient       Starting IP refresh thread
18-01-13 18:14:17 [INFO]   NodeManager      Node manager started
18-01-13 18:14:17 [INFO]   PeerServer       Starting peer server: address = 0.0.0.0:5161
18-01-13 18:14:18 [INFO]   SemuxBFT         Consensus started
18-01-13 18:14:18 [INFO]   SemuxBFT         Entered new_height: height = 1, # validators = 4
18-01-13 18:14:18 [INFO]   PeerClient       New IP address detected: 127.0.0.1 => 211.97.167.33
18-01-13 18:14:28 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 88.80.187.200
18-01-13 18:14:28 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 45.79.68.226
18-01-13 18:14:29 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 172.104.58.70
18-01-13 18:14:29 [INFO]   SemuxP2pHandler  Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 139.162.66.86



Message:Syncing:stopped

Why?



jr. member
Activity: 111
Merit: 2
January 13, 2018, 05:18:24 AM
Is there an official trade thread for SEM ?
full member
Activity: 266
Merit: 100
January 13, 2018, 03:32:09 AM
Is the 0.5 voting fee and 1000 delegate registration fee paid to validators, or is it burned?

1000 delegate fee is burned, but will be returned when main net launches.
Low coin supply means high price! Do not give this coin away for under $5 (maybe even $10)...

Is it the same on the main net?  Main net delegate registration = burned coins?  Won't that potentially destroy a lot of supply?  Or do you think not many will try to be a delegate.
newbie
Activity: 93
Merit: 0
January 13, 2018, 02:59:00 AM
I already downloaded semux wallet and start some bounties.
newbie
Activity: 42
Merit: 0
January 13, 2018, 02:11:52 AM

Noticed that I didn’t get a payout from semuxpool_com2 today. Only from _com.
Didn’t get a double pay yesterday.
Do you need to wait until the wrongly payed out amount is accounted for again, From the other double payments I mean?

Pm’ed you my address.

Bad config on new code push.  Fixed now, payments all caught up.

Thanks for letting me know!
jr. member
Activity: 125
Merit: 6
January 13, 2018, 01:43:24 AM
怎么更新钱包啊?
full member
Activity: 276
Merit: 103
January 13, 2018, 12:08:41 AM
semuxpool_com and semuxpool_com2 update:
payouts for last ~24 hours went out.

Bug in validator code caused semuxpool_com2 to pay out 2 times (until it ran out of SEM).  Working on fix now Cheesy

There were only a few addresses that did not meet minimum payout for the day, most voters were paid out.


Actually i wouldn't mind once a week payout as well. Ark delegates do once a week payout.

Ok, moving to once every few days, then once per week.

I want to get as many payouts as possible before mainnet launches, to work out any issues in pool code Cheesy
Testing is mostly done on testnet, but good to vet it as much as possible before mainnet launch.  Want this as solid as possible before mainnet/open source release.

As for the flipping of current mainnet to the real mainnet on jan 20th, I'll have to figure out what to do.  I need to make sure votes are captured for final blocks when mainnet switch happens, as I think that information gets lost.

Today's payments went out.  Next payment will be on the 15th, then the 19th/20th prior to mainnet launch.
After mainnet launches, fees are low enough that paying out daily/weekly doesn't much matter, but it sounds like people prefer weekly.

semuxpool_com2 came across a bug in semux code where validator state breaks, so it did not forge as many blocks as it should have today.  Have restarted pool and resync'd database, so it should be ok going forward.


Noticed that I didn’t get a payout from semuxpool_com2 today. Only from _com.
Didn’t get a double pay yesterday.
Do you need to wait until the wrongly payed out amount is accounted for again, From the other double payments I mean?

Pm’ed you my address.
Are you voting for one or both?
sr. member
Activity: 476
Merit: 266
January 12, 2018, 11:10:08 PM
semuxpool_com and semuxpool_com2 update:
payouts for last ~24 hours went out.

Bug in validator code caused semuxpool_com2 to pay out 2 times (until it ran out of SEM).  Working on fix now Cheesy

There were only a few addresses that did not meet minimum payout for the day, most voters were paid out.


Actually i wouldn't mind once a week payout as well. Ark delegates do once a week payout.

Ok, moving to once every few days, then once per week.

I want to get as many payouts as possible before mainnet launches, to work out any issues in pool code Cheesy
Testing is mostly done on testnet, but good to vet it as much as possible before mainnet launch.  Want this as solid as possible before mainnet/open source release.

As for the flipping of current mainnet to the real mainnet on jan 20th, I'll have to figure out what to do.  I need to make sure votes are captured for final blocks when mainnet switch happens, as I think that information gets lost.

Today's payments went out.  Next payment will be on the 15th, then the 19th/20th prior to mainnet launch.
After mainnet launches, fees are low enough that paying out daily/weekly doesn't much matter, but it sounds like people prefer weekly.

semuxpool_com2 came across a bug in semux code where validator state breaks, so it did not forge as many blocks as it should have today.  Have restarted pool and resync'd database, so it should be ok going forward.


Noticed that I didn’t get a payout from semuxpool_com2 today. Only from _com.
Didn’t get a double pay yesterday.
Do you need to wait until the wrongly payed out amount is accounted for again, From the other double payments I mean?

Pm’ed you my address.
newbie
Activity: 42
Merit: 0
January 12, 2018, 10:23:44 PM
semuxpool_com and semuxpool_com2 update:
payouts for last ~24 hours went out.

Bug in validator code caused semuxpool_com2 to pay out 2 times (until it ran out of SEM).  Working on fix now Cheesy

There were only a few addresses that did not meet minimum payout for the day, most voters were paid out.


Actually i wouldn't mind once a week payout as well. Ark delegates do once a week payout.

Ok, moving to once every few days, then once per week.

I want to get as many payouts as possible before mainnet launches, to work out any issues in pool code Cheesy
Testing is mostly done on testnet, but good to vet it as much as possible before mainnet launch.  Want this as solid as possible before mainnet/open source release.

As for the flipping of current mainnet to the real mainnet on jan 20th, I'll have to figure out what to do.  I need to make sure votes are captured for final blocks when mainnet switch happens, as I think that information gets lost.

Today's payments went out.  Next payment will be on the 15th, then the 19th/20th prior to mainnet launch.
After mainnet launches, fees are low enough that paying out daily/weekly doesn't much matter, but it sounds like people prefer weekly.

semuxpool_com2 came across a bug in semux code where validator state breaks, so it did not forge as many blocks as it should have today.  Have restarted pool and resync'd database, so it should be ok going forward.
Jump to: