Author

Topic: [SYNX] Syndicate | Business Management Platform | NEW BETA v1.0.1.7 RELEASED! | - page 104. (Read 235769 times)

sr. member
Activity: 346
Merit: 251
Do it right or don't do it at all.
not getting any connections on latest wallet
debug.log:


any suggestions?

.conf is pretty much copied and pasted from op, minor changes being username and password. folder contents deleted before wallet opened

if u have any nodes in the conf file.. remove them and see if that works for you..

same result except that it only tries to connect to 141.134.226.132:9999
in debug console run this:  addnode 173.199.124.83 add

if u hop on slack it'll be alot easier.. plz pm dev if you dont have an invite already
legendary
Activity: 1050
Merit: 1000
not getting any connections on latest wallet
debug.log:


any suggestions?

.conf is pretty much copied and pasted from op, minor changes being username and password. folder contents deleted before wallet opened

if u have any nodes in the conf file.. remove them and see if that works for you..

same result except that it only tries to connect to 141.134.226.132:9999
sr. member
Activity: 346
Merit: 251
Do it right or don't do it at all.
not getting any connections on latest wallet
debug.log:


any suggestions?

.conf is pretty much copied and pasted from op, minor changes being username and password. folder contents deleted before wallet opened

if u have any nodes in the conf file.. remove them and see if that works for you..
legendary
Activity: 1050
Merit: 1000
not getting any connections on latest wallet
debug.log:
Code:
2016-08-04 17:02:13 init message: Done loading
2016-08-04 17:02:13 GUI: QObject::connect: Cannot connect (null)::showProgress(QString,int) to BitcoinGUI::showProgress(QString,int)
2016-08-04 17:02:13 GUI: QObject::connect: No such signal OptionsModel::transactionFeeChanged(CAmount)
2016-08-04 17:02:13 GUI: QObject::connect:  (receiver name: 'SendCoinsDialog')
2016-08-04 17:02:13 1 addresses found from DNS seeds
2016-08-04 17:02:13 dnsseed thread exit
2016-08-04 17:02:14 connect() to 141.134.226.132:9999 failed after select(): No route to host
2016-08-04 17:02:18 connect() to 141.134.226.132:9999 failed after select(): No route to host
2016-08-04 17:02:18 connect() to 159.203.253.102:9999 failed after select(): Connection refused
2016-08-04 17:02:19 connect() to 192.241.215.173:9999 failed after select(): Connection refused
2016-08-04 17:02:20 connect() to 192.241.237.60:9999 failed after select(): Connection refused
2016-08-04 17:02:20 connect() to 162.243.130.27:9999 failed after select(): Connection refused
2016-08-04 17:02:21 connect() to 162.243.131.87:9999 failed after select(): Connection refused
2016-08-04 17:02:21 connect() to 141.134.226.132:9999 failed after select(): No route to host
2016-08-04 17:02:22 connect() to 104.131.145.170:9999 failed after select(): Connection refused
2016-08-04 17:02:24 connect() to 141.134.226.132:9999 failed after select(): No route to host
2016-08-04 17:02:28 connect() to 141.134.226.132:9999 failed after select(): No route to host
2016-08-04 17:02:31 connect() to 141.134.226.132:9999 failed after select(): No route to host
2016-08-04 17:02:34 connect() to 45.55.179.6:9999 failed after select(): Connection refused
2016-08-04 17:02:35 connect() to 141.134.226.132:9999 failed after select(): No route to host
2016-08-04 17:02:39 connect() to 141.134.226.132:9999 failed after select(): No route to host
2016-08-04 17:02:43 connect() to 141.134.226.132:9999 failed after select(): No route to host
2016-08-04 17:02:46 connect() to 198.199.100.4:9999 failed after select(): Connection refused
2016-08-04 17:02:46 connect() to 141.134.226.132:9999 failed after select(): No route to host
2016-08-04 17:02:46 connect() to 107.170.247.240:9999 failed after select(): Connection refused
2016-08-04 17:02:47 connect() to 162.243.0.171:9999 failed after select(): Connection refused
2016-08-04 17:02:48 connect() to 162.243.62.235:9999 failed after select(): Connection refused
2016-08-04 17:02:49 connect() to 107.170.232.206:9999 failed after select(): Connection refused
2016-08-04 17:02:49 connect() to 141.134.226.132:9999 failed after select(): No route to host
2016-08-04 17:02:50 socket recv error 104
2016-08-04 17:02:54 connect() to 141.134.226.132:9999 failed after select(): No route to host

any suggestions?

.conf is pretty much copied and pasted from op, minor changes being username and password. folder contents deleted before wallet opened
hero member
Activity: 2128
Merit: 520
No Site, No Whitepaper, No news blog.
No sneak-peaks, no detailed roadmap.

Why should bittrex add, if there's nothing to go on.

I am fine with waiting, all ya'all should be focussed on the things above.
Those things above would also help add buy support and keep the price up.

The price will remain up due to buy support and with the help of the community rolling-up their sleeves and working like a community.. instead of just bitching about more exchanges at the moment..

Anyone willing to support the efforts o drive this project forward - within his/her capacity - is welcomed to do so..

this statement is clear the project will still proceeding just needed some time the exchange will help but community support will help most.
good luck guys.
sr. member
Activity: 1120
Merit: 255
C-cex is coming this week if not will come in next 1-3 weeks definitely.
sr. member
Activity: 346
Merit: 251
Do it right or don't do it at all.
No Site, No Whitepaper, No news blog.
No sneak-peaks, no detailed roadmap.

Why should bittrex add, if there's nothing to go on.

I am fine with waiting, all ya'all should be focussed on the things above.
Those things above would also help add buy support and keep the price up.

The price will remain up due to buy support and with the help of the community rolling-up their sleeves and working like a community.. instead of just bitching about more exchanges at the moment..

Anyone willing to support the efforts o drive this project forward - within his/her capacity - is welcomed to do so..
full member
Activity: 190
Merit: 100
CryptoDetective
No Site, No Whitepaper, No news blog.
No sneak-peaks, no detailed roadmap.

Why should bittrex add, if there's nothing to go on.

I am fine with waiting, all ya'all should be focussed on the things above.
Those things above would also help add buy support and keep the price up.
hero member
Activity: 1302
Merit: 540
i can't believe it no bittrex yet
waiting still mate holding may synx first while trexx still on the process hope we can get there so the long wait will be paid off
good luck mate and hope for the best of this project.
full member
Activity: 253
Merit: 101
KEK
 i can't believe it no bittrex yet
full member
Activity: 896
Merit: 100
PredX - AI-Powered Prediction Market
Sneak peak

Quote
# Intro

Here it is: don't be rude please, i write this mostly during my lunch break today to safe some time during the next couple of setups.

# Notes and features
* it is currently only tested on a vultr VPS and Ubuntu 16.04 (smallest is good for up to 8 nodes)
* porting to 14.04 is probably not too hard, but no priority for me
* this script doesnt care about the controller side of things
* installs 1-100 (or more!) masternodes in parallel on one machine, with individual config and data
* compilation is currently from source, ubuntu packages on the way
* some security hardening is done, including firewalling and a separate user
* automatic startup for all masternode daemons
* ipv6 enabled, tor/onion will follow
* this script needs to run as root, the masternodes will and should not!

# What do i need to do after running this script?
**0)** Download and tun this script on your VPS instance

**1)** change the amount of masternodes you want to install/configure at the top of the script ("eg SYNX_MNODE_AMOUNT=3")

**2)** Add your masternode private key to the configuration file(s) located at ```/etc/synx/synx_n${NUMBER_OF_NODE}.conf```
For example, when installing three masternodes:
```
* writing config file /etc/synx/synx_n1.conf
* writing config file /etc/synx/synx_n2.conf
* writing config file /etc/synx/synx_n3.conf
```

**3)** run ```/usr/local/bin/restart_masternodes.sh``` to activate the services permanently.
   Individual masternode data directories are located in ```/var/lib/synx/synx${NUMBER_OF_NODE}```

**4)** subsequently, you should only work as user and not ```root```. The default user acc is ```synx```.
   Change to this user with the command "su synx" (loged in as root)

# Todo
* rewrite for config templates and support DNET, DASH
* document the vultr signup and setup procedure
* currently not fully idempotent, be careful when running it often
* provide a delete / uninstall flag
* create a logfile


Looking good!! Thank you, It's very appreciated!!
full member
Activity: 896
Merit: 100
PredX - AI-Powered Prediction Market
Dev, i have problem.. Then my wallet synced it show almost 100k balance, i send 5 coins transaction. But it wasn't deposited on www.coinexchange.io.
I saw 131 coins transaction in explorer http://blockexplorer.syndicatelabs.org/address/SjFfm3RLEzTHUoGtizTWJiKBVBdugSCSKg.
Then i trying to sync wallet from first block it doesnt connect to any nodes. Please help!

Please PM me your email so I can invite you to the Slack channel.

This issue would be easier to resolve if we were conversing in real time!

We need to get to the bottom of this!!
legendary
Activity: 1050
Merit: 1000

qmake -qt=qt5 USE_UPNP=- STATIC=1 USE_O3=1

thanks but same result
Code:
~/tmp/SyndicateQT $ qmake -qt=qt5 USE_UPNP=- STATIC=1 USE_O3=1
Project MESSAGE: Building with DBUS (Freedesktop notifications) support
Project MESSAGE: Building O3 optimization flag
Project MESSAGE: Building without UPNP support
lrelease error: Unexpected tag at ~/tmp/SyndicateQT/src/qt/locale/bitcoin_de.ts:19:29

edit:
changed
Code:
Copyright © 2009-2014 Die Bitcoin Entwickler
Copyright © 2012-2014 Die NovaCoin Entwickler
Copyright © 2016 Die Syndicate Entwickler

to
Code:
Copyright © 2009-2014 Die Bitcoin Entwickler
Copyright © 2012-2014 Die NovaCoin Entwickler
Copyright © 2016 Die Syndicate Entwickler


in src/qt/locale/bitcoin_de.ts compiling now
sr. member
Activity: 474
Merit: 252
Sneak peak

Quote
# Intro

Here it is: don't be rude please, i write this mostly during my lunch break today to safe some time during the next couple of setups.

# Notes and features
* it is currently only tested on a vultr VPS and Ubuntu 16.04 (smallest is good for up to 8 nodes)
* porting to 14.04 is probably not too hard, but no priority for me
* this script doesnt care about the controller side of things
* installs 1-100 (or more!) masternodes in parallel on one machine, with individual config and data
* compilation is currently from source, ubuntu packages on the way
* some security hardening is done, including firewalling and a separate user
* automatic startup for all masternode daemons
* ipv6 enabled, tor/onion will follow
* this script needs to run as root, the masternodes will and should not!

# What do i need to do after running this script?
**0)** Download and tun this script on your VPS instance

**1)** change the amount of masternodes you want to install/configure at the top of the script ("eg SYNX_MNODE_AMOUNT=3")

**2)** Add your masternode private key to the configuration file(s) located at ```/etc/synx/synx_n${NUMBER_OF_NODE}.conf```
For example, when installing three masternodes:
```
* writing config file /etc/synx/synx_n1.conf
* writing config file /etc/synx/synx_n2.conf
* writing config file /etc/synx/synx_n3.conf
```

**3)** run ```/usr/local/bin/restart_masternodes.sh``` to activate the services permanently.
   Individual masternode data directories are located in ```/var/lib/synx/synx${NUMBER_OF_NODE}```

**4)** subsequently, you should only work as user and not ```root```. The default user acc is ```synx```.
   Change to this user with the command "su synx" (loged in as root)

# Todo
* rewrite for config templates and support DNET, DASH
* document the vultr signup and setup procedure
* currently not fully idempotent, be careful when running it often
* provide a delete / uninstall flag
* create a logfile

sr. member
Activity: 474
Merit: 252
Code:
~/tmp/SyndicateQT $ qmake
Project MESSAGE: Building with DBUS (Freedesktop notifications) support
Project MESSAGE: Building with UPNP support
lrelease error: Unexpected tag at ~/tmp/SyndicateQT/src/qt/locale/bitcoin_de.ts:19:29

any thoughts?
qmake -qt=qt5 USE_UPNP=- STATIC=1 USE_O3=1
legendary
Activity: 1050
Merit: 1000
Code:
~/tmp/SyndicateQT $ qmake
Project MESSAGE: Building with DBUS (Freedesktop notifications) support
Project MESSAGE: Building with UPNP support
lrelease error: Unexpected tag at ~/tmp/SyndicateQT/src/qt/locale/bitcoin_de.ts:19:29

any thoughts?
hero member
Activity: 521
Merit: 500
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 ERROR: AcceptToMemoryPool : coinstake as individual tx
2016-08-03 17:27:57 No valid UPnP IGDs found
2016-08-03 17:27:57 upnp thread exit
2016-08-03 17:27:57 1 addresses found from DNS seeds
2016-08-03 17:27:57 dnsseed thread exit
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:58 GUI: QSslSocket: cannot call unresolved function SSLv23_client_method
2016-08-03 17:27:58 GUI: QSslSocket: cannot call unresolved function SSL_CTX_new
2016-08-03 17:27:58 GUI: QSslSocket: cannot call unresolved function SSL_library_init
2016-08-03 17:27:58 GUI: QSslSocket: cannot call unresolved function ERR_get_error
2016-08-03 17:27:58 GUI: QSslSocket: cannot call unresolved function ERR_get_error
2016-08-03 17:27:58 GUI: QSslSocket: cannot call unresolved function SSLv23_client_method
2016-08-03 17:27:58 GUI: QSslSocket: cannot call unresolved function SSL_CTX_new
2016-08-03 17:27:58 GUI: QSslSocket: cannot call unresolved function SSL_library_init
2016-08-03 17:27:58 GUI: QSslSocket: cannot call unresolved function ERR_get_error
2016-08-03 17:27:58 GUI: QSslSocket: cannot call unresolved function ERR_get_error
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::showProgress(QString,int) to BitcoinGUI::showProgress(QString,int)
2016-08-03 17:27:58 GUI: QObject::connect: No such signal OptionsModel::transactionFeeChanged(CAmount)
2016-08-03 17:27:58 GUI: QObject::connect:  (receiver name: 'SendCoinsDialog')
2016-08-03 17:27:58 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
2016-08-03 17:27:59 GUI: QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
hero member
Activity: 521
Merit: 500
Dev, i have problem.. Then my wallet synced it show almost 100k balance, i send 5 coins transaction. But it wasn't deposited on www.coinexchange.io.
I saw 131 coins transaction in explorer http://blockexplorer.syndicatelabs.org/address/SjFfm3RLEzTHUoGtizTWJiKBVBdugSCSKg.
Then i trying to sync wallet from first block it doesnt connect to any nodes. Please help!
hero member
Activity: 521
Merit: 500
WoW, that prices on exchanges!!! Waiting for c-cex or bittrex. Good luck dev!
sr. member
Activity: 1120
Merit: 255
Any news from bittrex? what was their last answer?
Jump to: