Topic: ⚒ Syscoin -Blockchain Scalability, Trustless Interoperability for ERC20 projects - page 169. (Read 501963 times)
June 08, 2016, 10:46:26 AM
This wallet 2.0 from OP its for windows ? I have windows.
June 08, 2016, 08:29:53 AM
Can see 6 transactions at 6.78 kB in the memory pool that haven't moved now for several blocks, which are being mined empty. Perhaps the majority mining pools have some rather greedy settings? If so, this is not good for the average user which has no clue what 'fee' needs to be put on it, as the core wallet allows either fee free transactions or transactions with a small fee automatically calculated.
https://syscoin.slack.com/messages/bugs/
Not on slack. Can you post it here?
June 08, 2016, 08:22:30 AM
Can see 6 transactions at 6.78 kB in the memory pool that haven't moved now for several blocks, which are being mined empty. Perhaps the majority mining pools have some rather greedy settings? If so, this is not good for the average user which has no clue what 'fee' needs to be put on it, as the core wallet allows either fee free transactions or transactions with a small fee automatically calculated.
https://syscoin.slack.com/messages/bugs/
June 08, 2016, 08:09:57 AM
Can see 6 transactions at 6.78 kB in the memory pool that haven't moved now for several blocks, which are being mined empty. Perhaps the majority mining pools have some rather greedy settings? If so, this is not good for the average user which has no clue what 'fee' needs to be put on it, as the core wallet allows either fee free transactions or transactions with a small fee automatically calculated.
June 08, 2016, 08:07:50 AM
decred and waves had also problems with yobit....
June 08, 2016, 07:22:49 AM
Hi all. Guys i have a problem with one transaction on Yobit exchange. Its not confirmed around one month now. My tickets to their support not have any sense. May be you can help me here? Anyway ty.
June 08, 2016, 04:02:14 AM
Restored wallet.dat, updated conf with extra nodes from github. Removed peers.dat. Not allowing incoming connections.
Will the new wallet reject SYS1 connections? I wonder if there was some interference from that. Otherwise it is beginning to look like I can't send coins from the conversion. I'll leave the coins sat there for a while. Would be useful if someone could confirm an empty mempool.
BTW, my transaction appeared to show up in debug window as 1.5kB. 3 inputs, one output.
Will the new wallet reject SYS1 connections? I wonder if there was some interference from that. Otherwise it is beginning to look like I can't send coins from the conversion. I'll leave the coins sat there for a while. Would be useful if someone could confirm an empty mempool.
BTW, my transaction appeared to show up in debug window as 1.5kB. 3 inputs, one output.
June 08, 2016, 02:57:14 AM
Anyone know why this transaction is not confirming?
280961735df81c7f95bbed31e862c914e62825ab419ee6a94c316de85ff48457
Lots of empty blocks being mined.
280961735df81c7f95bbed31e862c914e62825ab419ee6a94c316de85ff48457
Lots of empty blocks being mined.
So what is going on? Tried zapwallettxes and send with a fee. Booted into windows, updated to latest wallet from syscoin.org, restored pre conversion wallet.dat and send again. No confirmation. Yet I have seen massive fee free transactions go through quickly.
Latest txId:
d742569bf44bd0138f41994b52cd7f8dd65c46e01a416cbdb71286e6b42ea5f1
Note: originally tried sending on linux built from latest release tag source.
I've update the conf file with a few extra nodes from github. Yes, the transactions where broadcast through the best part of 8 nodes, but the transaction didn't show up again after zapwallettxes (I would have thought another node would have re-broadcast it)
June 07, 2016, 08:37:50 PM
Anyone know why this transaction is not confirming?
280961735df81c7f95bbed31e862c914e62825ab419ee6a94c316de85ff48457
Lots of empty blocks being mined.
280961735df81c7f95bbed31e862c914e62825ab419ee6a94c316de85ff48457
Lots of empty blocks being mined.
So what is going on? Tried zapwallettxes and send with a fee. Booted into windows, updated to latest wallet from syscoin.org, restored pre conversion wallet.dat and send again. No confirmation. Yet I have seen massive fee free transactions go through quickly.
Latest txId:
d742569bf44bd0138f41994b52cd7f8dd65c46e01a416cbdb71286e6b42ea5f1
Note: originally tried sending on linux built from latest release tag source.
June 07, 2016, 08:31:05 PM
Had this wallet synced when it was released, then got "Couldn't connect to best block." Now having trouble getting it synced, gets stuck. Anyone have a recent blockchain snapshot, or a bootstrap for SYS? Thanks,
did you use the syscoin.conf file with nodes provided? You using the latest wallet from May 8? It shouldn't give you the best block error unless your using the one from May 1.Same was on my side. Please use the wallet from May 8.
If I try to sync from scratch, using the May 8 wallet, and the .conf, it get to block 1696 and stops. If I close & relaunch, I get the best block error...
June 07, 2016, 07:49:55 PM
Anyone know why this transaction is not confirming?
280961735df81c7f95bbed31e862c914e62825ab419ee6a94c316de85ff48457
Lots of empty blocks being mined.
280961735df81c7f95bbed31e862c914e62825ab419ee6a94c316de85ff48457
Lots of empty blocks being mined.
So what is going on? Tried zapwallettxes and send with a fee. Booted into windows, updated to latest wallet from syscoin.org, restored pre conversion wallet.dat and send again. No confirmation. Yet I have seen massive fee free transactions go through quickly.
Latest txId:
d742569bf44bd0138f41994b52cd7f8dd65c46e01a416cbdb71286e6b42ea5f1
Note: originally tried sending on linux built from latest release tag source.
June 07, 2016, 01:15:19 PM
Syscoin price is rising on poloniex 
June 07, 2016, 01:03:46 PM
Had this wallet synced when it was released, then got "Couldn't connect to best block." Now having trouble getting it synced, gets stuck. Anyone have a recent blockchain snapshot, or a bootstrap for SYS? Thanks,
did you use the syscoin.conf file with nodes provided? You using the latest wallet from May 8? It shouldn't give you the best block error unless your using the one from May 1.Same was on my side. Please use the wallet from May 8.
If I try to sync from scratch, using the May 8 wallet, and the .conf, it get to block 1696 and stops. If I close & relaunch, I get the best block error...
June 07, 2016, 11:49:38 AM
Anyone know why this transaction is not confirming?
280961735df81c7f95bbed31e862c914e62825ab419ee6a94c316de85ff48457
Lots of empty blocks being mined.
280961735df81c7f95bbed31e862c914e62825ab419ee6a94c316de85ff48457
Lots of empty blocks being mined.
June 07, 2016, 09:06:03 AM
Had this wallet synced when it was released, then got "Couldn't connect to best block." Now having trouble getting it synced, gets stuck. Anyone have a recent blockchain snapshot, or a bootstrap for SYS? Thanks,
did you use the syscoin.conf file with nodes provided? You using the latest wallet from May 8? It shouldn't give you the best block error unless your using the one from May 1.Same was on my side. Please use the wallet from May 8.
Please link to the wallet on 8 May. Because at the github I can only see the version of 1 May.
This is the version of May 8? Because at the github it is written on May 1. : https://github.com/syscoin/syscoin2/releases/tag/2.0
June 07, 2016, 03:25:22 AM
Had this wallet synced when it was released, then got "Couldn't connect to best block." Now having trouble getting it synced, gets stuck. Anyone have a recent blockchain snapshot, or a bootstrap for SYS? Thanks,
did you use the syscoin.conf file with nodes provided? You using the latest wallet from May 8? It shouldn't give you the best block error unless your using the one from May 1.Same was on my side. Please use the wallet from May 8.
June 07, 2016, 02:17:42 AM
Had this wallet synced when it was released, then got "Couldn't connect to best block." Now having trouble getting it synced, gets stuck. Anyone have a recent blockchain snapshot, or a bootstrap for SYS? Thanks,
did you use the syscoin.conf file with nodes provided? You using the latest wallet from May 8? It shouldn't give you the best block error unless your using the one from May 1. June 06, 2016, 09:52:52 PM
Had this wallet synced when it was released, then got "Couldn't connect to best block." Now having trouble getting it synced, gets stuck. Anyone have a recent blockchain snapshot, or a bootstrap for SYS? Thanks,
June 04, 2016, 06:01:17 PM
Has anyone managed to get merge mining working with p2pool? My logs are jam packed with the same repeating error......
Sorry I don't have more info on p2pool, what is the error you're receiving?
Debug log is completely full of this:
2016-06-03 13:46:44 keypool return 2
2016-06-03 13:46:45 keypool reserve 2
2016-06-03 13:46:45 keypool return 2
2016-06-03 13:46:46 keypool reserve 2
2016-06-03 13:46:46 keypool return 2
2016-06-03 13:46:47 keypool reserve 2
2016-06-03 13:46:47 keypool return 2
2016-06-03 13:46:48 keypool reserve 2
2016-06-03 13:46:48 keypool return 2
2016-06-03 13:46:49 keypool reserve 2
2016-06-03 13:46:49 keypool return 2
2016-06-03 13:46:51 keypool reserve 2
2016-06-03 13:46:51 keypool return 2
2016-06-03 13:46:52 keypool reserve 2
2016-06-03 13:46:52 keypool return 2
2016-06-03 13:46:53 keypool reserve 2
2016-06-03 13:46:53 keypool return 2
2016-06-03 13:46:54 keypool reserve 2
2016-06-03 13:46:54 keypool return 2
2016-06-03 13:46:55 keypool reserve 2
2016-06-03 13:46:55 keypool return 2
conf file is right (I merge mine a couple of other coins) & it's the latest version built from git running on Ubuntu 64bit. I've also not seen a single payment since I started merge mining it, so something ain't right somewhere. I noticed an issue had been raised in github from someone with the same problem, it was only after seeing it that I realised I had the same issue.
Any ideas?
No - it's the latest p2pool version.
Ok so the NOMP based pools used "target" instead of "_target" and sigwo convinced me to change it.. however p2pool still uses "_target" it looks like maybe it should remain "_target" and the NOMP pools should change their code to work properly.
https://github.com/syscoin/syscoin2/blob/master/src/rpcmining.cpp#L923
update that line to "_target" and compile syscoin2 and try again. I've updated the issue https://github.com/syscoin/syscoin2/issues/81
I will update this line back to _target in syscoin 2.1 so 2.1 should work OOTB.
June 04, 2016, 05:41:42 PM
Do you have build instructions for Ubuntu. I tried to build Sycoin on Ubuntu 16 using this:
It builds but I get a Segfault when I run it. There is not much in the debug.log but the problem seems to be with Berkeley db:
I tried on an Ubuntu 14 machine, the VM I use to build Bitcoin with:
I can wait for the PPA to be complete and leave my coins on Bittrex but like to build my own binaries. Thanks!
There seems to be issue with that version because bdb 5.1 is used but you need 4.8 unless you build with compatibility mode.. the Ubuntu build instructions on github talk about this I believeCode:
./autogen.sh && ./configure --with-gui=qt5 --with-incompatible-bdb && make
It builds but I get a Segfault when I run it. There is not much in the debug.log but the problem seems to be with Berkeley db:
Code:
CDBEnv::Open: LogDir=/home/dev/.syscoin/database ErrorFile=/home/dev/.syscoin/db.log
I tried on an Ubuntu 14 machine, the VM I use to build Bitcoin with:
Code:
./autogen.sh && ./configure --with-gui=qt4 && make
but I get a compile error:Code:
In file included from /usr/include/qt4/QtNetwork/QNetworkRequest:1:0,
from qt/acceptandpayofferlistpage.cpp:21:
/usr/include/qt4/QtNetwork/qnetworkrequest.h:56:7: error: forward declaration of ‘class QSslConfiguration’
class QSslConfiguration;
^
qt/acceptandpayofferlistpage.cpp:385:27: error: ‘QSslSocket’ has not been declared
conf.setPeerVerifyMode(QSslSocket::VerifyNone);
^
qt/acceptandpayofferlistpage.cpp:386:21: error: ‘QSsl’ has not been declared
conf.setProtocol(QSsl::TlsV1_0);
I am using the code from the master branch: https://github.com/syscoin/syscoin2from qt/acceptandpayofferlistpage.cpp:21:
/usr/include/qt4/QtNetwork/qnetworkrequest.h:56:7: error: forward declaration of ‘class QSslConfiguration’
class QSslConfiguration;
^
qt/acceptandpayofferlistpage.cpp:385:27: error: ‘QSslSocket’ has not been declared
conf.setPeerVerifyMode(QSslSocket::VerifyNone);
^
qt/acceptandpayofferlistpage.cpp:386:21: error: ‘QSsl’ has not been declared
conf.setProtocol(QSsl::TlsV1_0);
I can wait for the PPA to be complete and leave my coins on Bittrex but like to build my own binaries. Thanks!
https://github.com/syscoin/syscoin2/blob/master/doc/build-unix.md
Jump to: