|
the reward is low and also no refferal bonus.
no one will bite for this. yiu must add refferal bonus to attract airdrop hunters.
|
|
|
|
|
The project has an impressive team. I think this is an interesting offer for investors.
let's see how it will work in the future. but I am ready to support the project now.
|
|
|
|
# Proof of Participation Email Address used for creating your Bitwings Account: hillman493@gmail.comCompleted Required Tasks?: Yes Completed Additional Tasks?: Yes Joined @bitwingsairdrop on Telegram?: Yes Telegram Username: @kikomode Ethereum (ERC-20) Wallet Address: 0x3889c0704C4CFf191A4471e0d036Cd45BbEC430c |
|
|
|
|
Applying for Signature Campaign
User: hillman321
Position to Apply: Full Member
Posts Start: 277
Address: 3QZ4JE8ToJmsccrqcipVcfNcLUswJ9z7wS
Still Available?
|
|
|
|
Signature campaign## Rules
1. This event starts from July 1, 2018 until December 23, 2018.
3. Participant requirements:
- Registered before June 25, 2018;
- Have 10+ merits;
- Follow @semuxproject on Twitter;
- Make at least one new post every week (we measure your activity point on Sunday);
- No spam/multi-account.
4. The rewards will be proportionally distributed to participants based on their merit scores (capped at 500):
- The reward allocation is 20,000 SEM per week;
- Payments are processed on Sunday.
5. We reserve the right to modify or cancel this event at any time. We reserve the right to refuse participants for any reason.
## How to participate?
1. Put your Semux wallet address in the `Location` field of your BitcoinTalk profile
2. Wear the signature listed at https://bitcointalk.org/index.php?topic=2159012.0
3. Follow @semuxproject on Twitter
4. Sign up at https://goo.gl/forms/39bP7CDRiCg58mgh1 Finally the good news.  i hope the next good news is new exchange site.. i hate the current exchange... |
|
|
|
it's for sure timezone problem
but my time zone is correct & syncronize. by the way i'm from Philippines, this is my clock settings try to use microsft server.. really i don't know it's strange what do you mean microsft server? i have this kind of problem too whenever i tried to sync my wallet from different ISP and using different PC. no idea what is going on,but until now i did not find the problem and can not fix it. (it was like something blocked me or some stuff like that) your also from the Philippines? |
|
|
|
it's for sure timezone problem
but my time zone is correct & syncronize. by the way i'm from Philippines, this is my clock settings try to use microsft server.. really i don't know it's strange what do you mean microsft server? |
|
|
|
it's for sure timezone problem
but my time zone is correct & syncronize. by the way i'm from Philippines, this is my clock settings  |
|
|
|
go in panel control windows
date and time
set you right timezone
go to internet time and set "syncrhonized with internet time server"
reboot
reopen wallet
i already tried that, still no luck  any other solution? it's strange.. have you the last wallet? database update 30 march... try if can help https://1drv.ms/u/s!AjKjtIq1Y-7Tii9QRAELq1owPNZI i'm using last month database 4gb of blocks size.. still not working..  |
|
|
|
go in panel control windows
date and time
set you right timezone
go to internet time and set "syncrhonized with internet time server"
reboot
reopen wallet
i already tried that, still no luck any other solution? |
|
|
|
Can someone help me. i can sync my wallet this is my debug file. some said my time is wrong & my ip.. but its not. 2018-05-29T13:27:54+0800 INFO PubSub PubSub service started
2018-05-29T13:28:03+0800 INFO Kernel Semux/v1.2.0-cba85a7/Windows/amd64
2018-05-29T13:28:03+0800 INFO Kernel System booting up: network = mainnet, networkVersion = 0, coinbase = 32ee07c7833d6916360b0eda4d224283852ce58e
2018-05-29T13:28:04+0800 INFO Kernel Computer: manufacturer = BIOSTAR Group, model = Hi-Fi A70U3P
2018-05-29T13:28:04+0800 INFO Kernel OS: name = Microsoft Windows 7 SP1 build 7601
2018-05-29T13:28:19+0800 INFO Kernel CPU: processor = AMD A4-6300 APU with Radeon(tm) HD Graphics , cores = 1 / 2
2018-05-29T13:28:20+0800 INFO Kernel Memory: total = 8112 MB, available = 4056 MB, swap total = 8110 MB, swap available = 7845 MB
2018-05-29T13:28:20+0800 INFO Kernel Disk: name = \\.\PHYSICALDRIVE0, size = 476937 MB
2018-05-29T13:28:20+0800 INFO Kernel Network: name = Realtek PCIe GBE Family Controller #2, ip = [192.168.254.100]
2018-05-29T13:28:20+0800 INFO Kernel Network: name = Microsoft ISATAP Adapter #2, ip = []
2018-05-29T13:28:20+0800 INFO Kernel Network: name = TAP-Windows Adapter V9, ip = []
2018-05-29T13:28:20+0800 INFO Kernel Network: name = Microsoft ISATAP Adapter, ip = []
2018-05-29T13:28:20+0800 INFO Kernel Network: name = Microsoft ISATAP Adapter #3, ip = []
2018-05-29T13:28:20+0800 INFO Kernel Network: name = Kaspersky Security Data Escort Adapter, ip = []
2018-05-29T13:28:20+0800 INFO Kernel Java: version = 10.0.1, xmx = 3392 MB
2018-05-29T13:28:21+0800 INFO Kernel Latest block number = 0
2018-05-29T13:28:21+0800 INFO PeerClient Use IP address: 127.0.0.1
2018-05-29T13:28:21+0800 INFO PeerClient Starting IP refresh thread
2018-05-29T13:28:21+0800 INFO NodeManager Node manager started
2018-05-29T13:28:21+0800 INFO PeerServer Starting peer server: address = 0.0.0.0:5161
2018-05-29T13:28:22+0800 INFO PeerClient New IP address detected: 127.0.0.1 => 180.191.115.192
2018-05-29T13:28:23+0800 INFO SemuxBft Consensus started
2018-05-29T13:28:23+0800 INFO SemuxBft Entered new_height: height = 1, # validators = 4
2018-05-29T13:28:26+0800 DEBUG SemuxChannelInitializer New outbound channel: remoteAddress = 159.203.147.157:5161
2018-05-29T13:28:26+0800 DEBUG ChannelManager Channel added: remoteAddress = 159.203.147.157:5161
2018-05-29T13:28:27+0800 DEBUG SemuxP2pHandler P2P handler active, cid = 0
2018-05-29T13:28:27+0800 DEBUG SemuxChannelInitializer New outbound channel: remoteAddress = 167.99.16.150:5161
2018-05-29T13:28:27+0800 DEBUG ChannelManager Channel added: remoteAddress = 167.99.16.150:5161
2018-05-29T13:28:27+0800 DEBUG SemuxP2pHandler Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 159.203.147.157
2018-05-29T13:28:27+0800 DEBUG ChannelManager Channel removed: remoteAddress = 159.203.147.157:5161
2018-05-29T13:28:27+0800 DEBUG SemuxP2pHandler P2P handler inactive, cid = 0
2018-05-29T13:28:27+0800 DEBUG SemuxP2pHandler P2P handler active, cid = 1
2018-05-29T13:28:27+0800 DEBUG SemuxChannelInitializer New outbound channel: remoteAddress = 35.201.187.136:5161
2018-05-29T13:28:27+0800 DEBUG ChannelManager Channel added: remoteAddress = 35.201.187.136:5161
2018-05-29T13:28:28+0800 DEBUG SemuxP2pHandler P2P handler active, cid = 2
2018-05-29T13:28:28+0800 DEBUG SemuxP2pHandler Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 167.99.16.150
2018-05-29T13:28:28+0800 DEBUG ChannelManager Channel removed: remoteAddress = 167.99.16.150:5161
2018-05-29T13:28:28+0800 DEBUG SemuxP2pHandler P2P handler inactive, cid = 1
2018-05-29T13:28:28+0800 DEBUG SemuxP2pHandler Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 35.201.187.136
2018-05-29T13:28:28+0800 DEBUG ChannelManager Channel removed: remoteAddress = 35.201.187.136:5161
2018-05-29T13:28:28+0800 DEBUG SemuxP2pHandler P2P handler inactive, cid = 2
2018-05-29T13:28:28+0800 DEBUG SemuxChannelInitializer New outbound channel: remoteAddress = 172.104.98.36:5161
2018-05-29T13:28:28+0800 DEBUG ChannelManager Channel added: remoteAddress = 172.104.98.36:5161
2018-05-29T13:28:28+0800 DEBUG SemuxP2pHandler P2P handler active, cid = 3
2018-05-29T13:28:28+0800 DEBUG SemuxP2pHandler Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 172.104.98.36
2018-05-29T13:28:28+0800 DEBUG ChannelManager Channel removed: remoteAddress = 172.104.98.36:5161
2018-05-29T13:28:28+0800 DEBUG SemuxP2pHandler P2P handler inactive, cid = 3
2018-05-29T13:28:28+0800 DEBUG SemuxChannelInitializer New outbound channel: remoteAddress = 139.162.48.46:5161
2018-05-29T13:28:28+0800 DEBUG ChannelManager Channel added: remoteAddress = 139.162.48.46:5161
2018-05-29T13:28:29+0800 DEBUG SemuxP2pHandler P2P handler active, cid = 4
2018-05-29T13:28:29+0800 DEBUG SemuxChannelInitializer New outbound channel: remoteAddress = 172.105.213.51:5161
2018-05-29T13:28:29+0800 DEBUG ChannelManager Channel added: remoteAddress = 172.105.213.51:5161
2018-05-29T13:28:29+0800 DEBUG SemuxP2pHandler Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 139.162.48.46
2018-05-29T13:28:29+0800 DEBUG ChannelManager Channel removed: remoteAddress = 139.162.48.46:5161
2018-05-29T13:28:29+0800 DEBUG SemuxP2pHandler P2P handler inactive, cid = 4
2018-05-29T13:28:29+0800 DEBUG SemuxP2pHandler P2P handler active, cid = 5
2018-05-29T13:28:29+0800 DEBUG SemuxP2pHandler Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 172.105.213.51
2018-05-29T13:28:29+0800 DEBUG ChannelManager Channel removed: remoteAddress = 172.105.213.51:5161
2018-05-29T13:28:29+0800 DEBUG SemuxP2pHandler P2P handler inactive, cid = 5
2018-05-29T13:28:29+0800 DEBUG SemuxChannelInitializer New outbound channel: remoteAddress = 168.235.75.241:5161
2018-05-29T13:28:29+0800 DEBUG ChannelManager Channel added: remoteAddress = 168.235.75.241:5161
2018-05-29T13:28:30+0800 DEBUG SemuxP2pHandler P2P handler active, cid = 6
2018-05-29T13:28:30+0800 DEBUG SemuxP2pHandler Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 168.235.75.241
2018-05-29T13:28:30+0800 DEBUG ChannelManager Channel removed: remoteAddress = 168.235.75.241:5161
2018-05-29T13:28:30+0800 DEBUG SemuxP2pHandler P2P handler inactive, cid = 6
|
|
|
|
Scum. Two years only words.... Many words.... I see rebranding, and change roadmap.
We launched our spot exchange on May 13, 2018. Happy to hear you out if you'd like to elaborate. Our story is in the original post on this thread. Our roadmap is on our main site here: https://wcex.com. I have 20,000XT from referrals which I got last December. How many of these people do you think would remember do this verification you guys just came up with, after how many months? It's unfair to for us to promote your project and we end up losing all our referrals just like that |
|
|
|
|
love the concept of the project. can't wait for the whitepaper
|
|
|
|
Is there a easy way to update the wallet. i can't update my wallet is not syncing, even the new wallet, i disable my firewall, anti virus & also run safe mode to sync my wallet.. still no luck.. please help
copy your debug file to here ,let's check if any problems of your wallet together, the easy way to change another computer and with different OS. Thank you for your help. this is my debug file 2018-03-11T07:33:57+0800 INFO Kernel Semux/v1.0.1-27d00eb/Windows/amd64
2018-03-11T07:33:57+0800 INFO Kernel System booting up: network = mainnet, networkVersion = 0, coinbase = f4f56649b1f871644e6d8e4243ad5f1d0dec1566
2018-03-11T07:33:58+0800 INFO Kernel Computer: manufacturer = BIOSTAR Group, model = Hi-Fi A70U3P
2018-03-11T07:33:58+0800 INFO Kernel OS: name = Microsoft Windows 7 SP1 build 7601
2018-03-11T07:34:14+0800 INFO Kernel CPU: processor = AMD A4-6300 APU with Radeon(tm) HD Graphics , cores = 1 / 2
2018-03-11T07:34:14+0800 INFO Kernel Memory: total = 8112 MB, available = 4593 MB, swap total = 8110 MB, swap available = 7952 MB
2018-03-11T07:34:15+0800 INFO Kernel Disk: name = \\.\PHYSICALDRIVE0, size = 476937 MB
2018-03-11T07:34:15+0800 INFO Kernel Network: name = Realtek PCIe GBE Family Controller #2, ip = [192.168.254.103]
2018-03-11T07:34:15+0800 INFO Kernel Network: name = Kaspersky Security Data Escort Adapter, ip = []
2018-03-11T07:34:15+0800 INFO Kernel Network: name = Microsoft ISATAP Adapter #2, ip = []
2018-03-11T07:34:15+0800 INFO Kernel Network: name = Microsoft ISATAP Adapter, ip = []
2018-03-11T07:34:15+0800 INFO Kernel Java: version = 9.0.4, xmx = 3828 MB
2018-03-11T07:34:16+0800 INFO Kernel Latest block number = 0
2018-03-11T07:34:16+0800 INFO PeerClient Use IP address: 127.0.0.1
2018-03-11T07:34:16+0800 INFO PeerClient Starting IP refresh thread
2018-03-11T07:34:17+0800 INFO NodeManager Node manager started
2018-03-11T07:34:17+0800 INFO PeerServer Starting peer server: address = 0.0.0.0:5161
2018-03-11T07:34:18+0800 INFO SemuxBft Consensus started
2018-03-11T07:34:18+0800 INFO SemuxBft Entered new_height: height = 1, # validators = 4
2018-03-11T07:34:18+0800 INFO PeerClient New IP address detected: 127.0.0.1 => 180.191.114.160
2018-03-11T07:34:22+0800 INFO SemuxP2pHandler Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 35.226.132.132
2018-03-11T07:34:23+0800 INFO SemuxP2pHandler Received DISCONNECT message: reason = INVALID_HANDSHAKE, remoteIP = 35.201.187.136 |
|
|
|
|
Is there a easy way to update the wallet. i can't update my wallet is not syncing, even the new wallet, i disable my firewall, anti virus & also run safe mode to sync my wallet.. still no luck.. please help
|
|
|
|
When will semux be listed at exchanges? I'm believe on exchange i could have a chance to get sem a little cheaper. why my wallet is not sync? how can i sync it?
Wallet works fine on my pc. I don't get it why mine is not working. i already disable my firewall & anti virus my system is uptodate. why my wallet is not sync? how can i sync it?
try to open the port 5161 in your firewall. I instantly get synced with over 100 peers! The network is quite active - though it is not that used at the moment. Exchange Listings are coming soon, afaik still not working  |
|
|
|
|
why my wallet is not sync? how can i sync it?
|
|
|
|
|
how to get my bounty coin on referrals?
|
|
|
|
|
Show Posts
