[SYS] SYSCOIN [Unofficial] - Due to censorship & secrecy on Official thread. - page 2.

blurryeyed

full member

Activity: 670

Merit: 120

TIME TO BAN THE YOBIT SCAM!!

Quote from: Gaglam on June 17, 2019, 05:57:06 AM

Quote

Censoring comments on github is just sad - yet another example of how badly BCF are treating Syscoin users. The terrible transition to the broken v4 wallet looks to have upset a lot of users if the price is anything to go by - more hard dumping on exchanges with the price approaching another all time low with only 3btc's worth of buy orders on Bittrex now - nobody wants it.

Well, why would anybody want it? It has ZERO usecase. Tell me why anybody should use sys and what for?

There was an opportunity for Syscoin with the market place thing a few years ago I think, but that soon fizzled out with the lack of marketing & development, I don't think they ever got it working properly & even if they did I don't know of a single person who uses it. The partnership with the Peermountain scammers was the final nail in the coffin, ever since they got involved with them the shit has hit the fan - $millions deficit, massive losses, mad crazy censorship, devs getting banned, buggy wallets, etc, etc.....

The Syscoin team are now waking up long dormant accounts to use on their thread in an effort to convince whoever is left that everything is fine:

https://bitcointalksearch.org/topic/m.51499450

Fact is though there are only 60 wallets that are using the buggy v4 protocol according to the official blockchain explorer:

https://chainz.cryptoid.info/sys/#!network

With 90% of blocks extracted all going to the same wallet address:

https://chainz.cryptoid.info/sys/#!extraction

The masternode count has dropped more than 600 in a few weeks to ~1000 & all of those are on the v3 wallets:

https://masternodes.online/currencies/SYS/

Yet according to BCF the transition to v4 was a huge success & everything is working wonderful. I can't believe they didn't delete my posts on their thread yet, but then again, they didn't update their OP to link to the new wallets yet either - maybe the whole team have been banned & they can't change their own thread anymore.....LULZ.

Gaglam

sr. member

Activity: 390

Merit: 250

Quote

Censoring comments on github is just sad - yet another example of how badly BCF are treating Syscoin users. The terrible transition to the broken v4 wallet looks to have upset a lot of users if the price is anything to go by - more hard dumping on exchanges with the price approaching another all time low with only 3btc's worth of buy orders on Bittrex now - nobody wants it.

Well, why would anybody want it? It has ZERO usecase. Tell me why anybody should use sys and what for?

IconFirm

hero member

Activity: 1438

Merit: 574

Always ask questions. #StandWithHongKong

Quote from: blurryeyed on June 15, 2019, 05:01:20 PM

Quote from: IconFirm on June 08, 2019, 10:27:05 AM

It's funny how they don't even bother updating their thread with links to the new wallet, or even announce it for that matter, they must be very unsure about weather it actually works or not. You'd have thought that they'd be shouting from the rooftops about it, but nothing.

The v4 wallet is completely borked, that's why they didn't announce it yet. They are deleting complaints from angry users about their crappy wallet releases from their github repo too: https://github.com/syscoin/syscoin/issues/336

4 releases so far & it's still not working.....LOL At least they are consistent with their censorship across all platforms.

Censoring comments on github is just sad - yet another example of how badly BCF are treating Syscoin users. The terrible transition to the broken v4 wallet looks to have upset a lot of users if the price is anything to go by - more hard dumping on exchanges with the price approaching another all time low with only 3btc's worth of buy orders on Bittrex now - nobody wants it.

blurryeyed

full member

Activity: 670

Merit: 120

TIME TO BAN THE YOBIT SCAM!!

Quote from: IconFirm on June 08, 2019, 10:27:05 AM

It's funny how they don't even bother updating their thread with links to the new wallet, or even announce it for that matter, they must be very unsure about weather it actually works or not. You'd have thought that they'd be shouting from the rooftops about it, but nothing.

The v4 wallet is completely borked, that's why they didn't announce it yet. They are deleting complaints from angry users about their crappy wallet releases from their github repo too: https://github.com/syscoin/syscoin/issues/336

4 releases so far & it's still not working.....LOL At least they are consistent with their censorship across all platforms.

IconFirm

hero member

Activity: 1438

Merit: 574

Always ask questions. #StandWithHongKong

@bontol72: As you only post about Syscoin I presume you are part of their "team" - which one are you?

IconFirm

hero member

Activity: 1438

Merit: 574

Always ask questions. #StandWithHongKong

Quote from: bontol72 on June 06, 2019, 02:12:41 AM

Quote from: blurryeyed on June 05, 2019, 06:17:59 PM

Over 200 masternodes have "gone" within the last few days.

Either BCF are cashing out their nodes or they're swapping them over to the unreleased v4 wallet without telling anyone, sneaky fackers.

Syscoin 4 Conversion from Syscoin 3
https://medium.com/@bittyjohn1954/syscoin-4-conversion-from-syscoin-3-1288c5027d45

New explorer:
https://chainz.cryptoid.info/sys/

It's funny how they don't even bother updating their thread with links to the new wallet, or even announce it for that matter, they must be very unsure about weather it actually works or not. You'd have thought that they'd be shouting from the rooftops about it, but nothing.

bontol72

sr. member

Activity: 285

Merit: 251

Quote from: blurryeyed on June 05, 2019, 06:17:59 PM

Over 200 masternodes have "gone" within the last few days.

Either BCF are cashing out their nodes or they're swapping them over to the unreleased v4 wallet without telling anyone, sneaky fackers.

Syscoin 4 Conversion from Syscoin 3
https://medium.com/@bittyjohn1954/syscoin-4-conversion-from-syscoin-3-1288c5027d45

New explorer:
https://chainz.cryptoid.info/sys/

blurryeyed

full member

Activity: 670

Merit: 120

TIME TO BAN THE YOBIT SCAM!!

Over 200 masternodes have "gone" within the last few days.

Either BCF are cashing out their nodes or they're swapping them over to the unreleased v4 wallet without telling anyone, sneaky fackers.

xbiv2

full member

Activity: 560

Merit: 111

Quote from: IconFirm on June 04, 2019, 07:07:38 AM

Sorry, but it it does work - you're doing something wrong & refuse to accept any help offered for some reason.

Please don't post in big red letters, thanks.

no, it is not working
syncronisation stuck on 364430 block
same with bitcoin cash and bitcoia SV
this is new way for SCAMing to prevent selling

IconFirm

hero member

Activity: 1438

Merit: 574

Always ask questions. #StandWithHongKong

Quote from: ?? on ??

Quote from: IconFirm on June 02, 2019, 03:09:22 PM

That log is from last week - was it started using the commands I suggested?
Was it done with a fresh blockchain download?
Did you use the conf I suggested?
Can you post the startup log & the user agent log?

I need more up-to-date info in order to be able to help you.

the client from github is not working, *snip*

Sorry, but it it does work - you're doing something wrong & refuse to accept any help offered for some reason.

Please don't post in big red letters, thanks.

IconFirm

hero member

Activity: 1438

Merit: 574

Always ask questions. #StandWithHongKong

That log is from last week - was it started using the commands I suggested?
Was it done with a fresh blockchain download?
Did you use the conf I suggested?
Can you post the startup log & the user agent log?

I need more up-to-date info in order to be able to help you.

xbiv2

full member

Activity: 560

Merit: 111

Quote from: IconFirm on May 31, 2019, 12:30:30 PM

Quote from: xbiv2 on May 30, 2019, 07:14:19 AM

Quote from: IconFirm on May 30, 2019, 03:12:21 AM

@xbiv2: Again, you're not using the latest version - the version in your screen shot shows v3.1.3. It is also exactly the same screen shot you posted earlier, I've no idea why you have reposted it, but you need to post the latest screen from the latest v3.2.0. You also need to post a log file as I requested earlier after starting the wallet with the commands I gave you earlier.

Im using thisone:
https://github.com/syscoin/syscoin/releases/tag/3.2.0.0

Then post a screen shot of your v3.2.0.0 node together with a log please.

Code:

2019-05-28 04:21:44 ThreadSocketHandler -- removing node: peer=776 addr=104.207.144.109:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:21:45 CMasternodeSync::ProcessTick -- nTick 376 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:21:46 Peer=777 is stalling block download, disconnecting
2019-05-28 04:21:46 ThreadSocketHandler -- removing node: peer=777 addr=51.15.66.51:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:21:46 receive version message: /Syscoin Core:3.1.2/: version 70224, blocks=538251, us=1.46.104.112:15497, peer=781
2019-05-28 04:21:47 receive version message: /Syscoin Core:3.1.2/: version 70224, blocks=538251, us=1.46.104.112:61830, peer=782
2019-05-28 04:21:48 Peer=778 is stalling block download, disconnecting
2019-05-28 04:21:48 ThreadSocketHandler -- removing node: peer=778 addr=139.59.245.7:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:21:48 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538251, us=1.46.104.112:24981, peer=783
2019-05-28 04:21:49 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538251, us=1.46.104.112:43200, peer=784
2019-05-28 04:21:50 Peer=779 is stalling block download, disconnecting
2019-05-28 04:21:50 ThreadSocketHandler -- removing node: peer=779 addr=142.93.34.182:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:21:50 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538251, us=202.91.18.227:12654, peer=785
2019-05-28 04:21:50 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538251, us=1.46.104.112:13505, peer=786
2019-05-28 04:21:51 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538251, us=1.46.104.112:59091, peer=787
2019-05-28 04:21:51 CMasternodeSync::ProcessTick -- nTick 377 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:21:51 CMasternodeSync::ProcessTick -- nTick 377 nRequestedMasternodeAssets 0 -- requesting sporks from peer=781
2019-05-28 04:21:51 CMasternodeSync::ProcessTick -- nTick 377 nRequestedMasternodeAssets 0 -- requesting sporks from peer=782
2019-05-28 04:21:51 CMasternodeSync::ProcessTick -- nTick 377 nRequestedMasternodeAssets 0 -- requesting sporks from peer=783
2019-05-28 04:21:51 CMasternodeSync::ProcessTick -- nTick 377 nRequestedMasternodeAssets 0 -- requesting sporks from peer=784
2019-05-28 04:21:51 CMasternodeSync::ProcessTick -- nTick 377 nRequestedMasternodeAssets 0 -- requesting sporks from peer=785
2019-05-28 04:21:51 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538251, us=1.46.104.112:56726, peer=788
2019-05-28 04:21:52 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538251, us=1.46.104.112:13125, peer=789
2019-05-28 04:21:52 Peer=780 is stalling block download, disconnecting
2019-05-28 04:21:52 ThreadSocketHandler -- removing node: peer=780 addr=144.202.72.144:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:21:53 receive version message: /Syscoin Core:3.1.4/: version 70226, blocks=538251, us=1.46.104.112:23022, peer=790
2019-05-28 04:21:53 ThreadSocketHandler -- removing node: peer=790 addr=104.238.177.112:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:21:53 receive version message: /Syscoin Core:3.1.4/: version 70226, blocks=538251, us=1.46.104.112:23492, peer=791
2019-05-28 04:21:53 receive version message: /Syscoin Core:3.1.4/: version 70226, blocks=538251, us=1.46.104.112:64525, peer=792
2019-05-28 04:21:54 Peer=781 is stalling block download, disconnecting
2019-05-28 04:21:54 ThreadSocketHandler -- removing node: peer=781 addr=159.69.1.25:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:21:54 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538251, us=1.46.104.112:56483, peer=793
2019-05-28 04:21:56 Peer=782 is stalling block download, disconnecting
2019-05-28 04:21:56 ThreadSocketHandler -- removing node: peer=782 addr=159.89.96.223:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:21:57 CMasternodeSync::ProcessTick -- nTick 378 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:21:58 Peer=783 is stalling block download, disconnecting
2019-05-28 04:21:58 ThreadSocketHandler -- removing node: peer=783 addr=195.201.33.199:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:00 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538252, us=1.46.104.112:37360, peer=794
2019-05-28 04:22:00 Peer=784 is stalling block download, disconnecting
2019-05-28 04:22:01 ThreadSocketHandler -- removing node: peer=784 addr=51.15.120.190:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:03 Peer=785 is stalling block download, disconnecting
2019-05-28 04:22:03 ThreadSocketHandler -- removing node: peer=785 addr=45.32.197.6:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:03 CMasternodeSync::ProcessTick -- nTick 379 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:22:05 Peer=786 is stalling block download, disconnecting
2019-05-28 04:22:05 ThreadSocketHandler -- removing node: peer=786 addr=149.28.165.229:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:07 Peer=787 is stalling block download, disconnecting
2019-05-28 04:22:07 ThreadSocketHandler -- removing node: peer=787 addr=202.182.100.105:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:09 Peer=788 is stalling block download, disconnecting
2019-05-28 04:22:09 ThreadSocketHandler -- removing node: peer=788 addr=157.230.20.127:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:09 CMasternodeSync::ProcessTick -- nTick 380 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:22:11 Peer=789 is stalling block download, disconnecting
2019-05-28 04:22:11 ThreadSocketHandler -- removing node: peer=789 addr=159.69.120.53:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:13 Peer=791 is stalling block download, disconnecting
2019-05-28 04:22:13 ThreadSocketHandler -- removing node: peer=791 addr=167.99.32.92:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:15 Peer=792 is stalling block download, disconnecting
2019-05-28 04:22:15 ThreadSocketHandler -- removing node: peer=792 addr=168.61.102.25:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:16 CMasternodeSync::ProcessTick -- nTick 381 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:22:17 Peer=793 is stalling block download, disconnecting
2019-05-28 04:22:17 ThreadSocketHandler -- removing node: peer=793 addr=173.212.227.122:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:22 CMasternodeSync::ProcessTick -- nTick 382 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:22:23 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538252, us=1.46.104.112:49543, peer=796
2019-05-28 04:22:27 Peer=794 is stalling block download, disconnecting
2019-05-28 04:22:27 ThreadSocketHandler -- removing node: peer=794 addr=178.128.210.92:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:28 CMasternodeSync::ProcessTick -- nTick 383 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:22:28 CMasternodeSync::ProcessTick -- nTick 383 nRequestedMasternodeAssets 0 -- requesting sporks from peer=796
2019-05-28 04:22:34 CMasternodeSync::ProcessTick -- nTick 384 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:22:39 socket recv error Пpoгpaммa нa вaшeм xocт-кoмпьютepe paзopвaлa ycтaнoвлeннoe пoдключeниe. (10053)
2019-05-28 04:22:39 ThreadSocketHandler -- removing node: peer=795 addr=185.205.210.142:43686 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:40 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538252, us=1.46.104.112:30194, peer=797
2019-05-28 04:22:41 CMasternodeSync::ProcessTick -- nTick 385 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:22:41 CMasternodeSync::ProcessTick -- nTick 385 nRequestedMasternodeAssets 0 -- requesting sporks from peer=797
2019-05-28 04:22:41 receive version message: /Syscoin Core:3.1.4/: version 70226, blocks=538252, us=1.46.104.112:33125, peer=798
2019-05-28 04:22:43 Peer=796 is stalling block download, disconnecting
2019-05-28 04:22:43 ThreadSocketHandler -- removing node: peer=796 addr=54.241.155.231:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:45 Peer=797 is stalling block download, disconnecting
2019-05-28 04:22:45 ThreadSocketHandler -- removing node: peer=797 addr=173.249.48.8:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:47 CMasternodeSync::ProcessTick -- nTick 386 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:22:47 CMasternodeSync::ProcessTick -- nTick 386 nRequestedMasternodeAssets 0 -- requesting sporks from peer=798
2019-05-28 04:22:48 receive version message: /Syscoin Core:3.1.3/: version 70225, blocks=538252, us=202.91.18.227:46279, peer=799
2019-05-28 04:22:50 Peer=798 is stalling block download, disconnecting
2019-05-28 04:22:50 ThreadSocketHandler -- removing node: peer=798 addr=34.219.154.55:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:53 CMasternodeSync::ProcessTick -- nTick 387 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:22:53 CMasternodeSync::ProcessTick -- nTick 387 nRequestedMasternodeAssets 0 -- requesting sporks from peer=799
2019-05-28 04:22:54 receive version message: /Syscoin Core:3.1.0/: version 70222, blocks=538252, us=202.91.18.227:13685, peer=800
2019-05-28 04:22:55 receive version message: /Syscoin Core:3.1.4/: version 70226, blocks=538252, us=1.46.104.112:43634, peer=801
2019-05-28 04:22:56 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538252, us=1.46.104.112:49212, peer=802
2019-05-28 04:22:57 Peer=799 is stalling block download, disconnecting
2019-05-28 04:22:57 ThreadSocketHandler -- removing node: peer=799 addr=45.32.122.207:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:58 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538252, us=1.46.104.112:18505, peer=803
2019-05-28 04:22:58 receive version message: /Syscoin Core:3.1.4/: version 70226, blocks=538252, us=1.46.104.112:64335, peer=804
2019-05-28 04:22:59 Peer=800 is stalling block download, disconnecting
2019-05-28 04:22:59 ThreadSocketHandler -- removing node: peer=800 addr=45.76.205.182:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:22:59 CMasternodeSync::ProcessTick -- nTick 388 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:22:59 CMasternodeSync::ProcessTick -- nTick 388 nRequestedMasternodeAssets 0 -- requesting sporks from peer=802
2019-05-28 04:22:59 CMasternodeSync::ProcessTick -- nTick 388 nRequestedMasternodeAssets 0 -- requesting sporks from peer=803
2019-05-28 04:22:59 CMasternodeSync::ProcessTick -- nTick 388 nRequestedMasternodeAssets 0 -- requesting sporks from peer=804
2019-05-28 04:23:01 Peer=801 is stalling block download, disconnecting
2019-05-28 04:23:01 ThreadSocketHandler -- removing node: peer=801 addr=103.14.141.211:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:23:02 receive version message: /Syscoin Core:3.1.3/: version 70225, blocks=538252, us=1.46.104.112:53130, peer=805
2019-05-28 04:23:03 receive version message: /Syscoin Core:3.1.4/: version 70226, blocks=538252, us=1.46.104.112:10941, peer=806
2019-05-28 04:23:03 Peer=802 is stalling block download, disconnecting
2019-05-28 04:23:03 ThreadSocketHandler -- removing node: peer=802 addr=116.203.47.153:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:23:04 receive version message: /Syscoin Core:3.1.4/: version 70226, blocks=538252, us=1.46.104.112:10620, peer=807
2019-05-28 04:23:05 Peer=803 is stalling block download, disconnecting
2019-05-28 04:23:05 ThreadSocketHandler -- removing node: peer=803 addr=95.216.221.234:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:23:05 CMasternodeSync::ProcessTick -- nTick 389 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:23:07 Peer=804 is stalling block download, disconnecting
2019-05-28 04:23:07 ThreadSocketHandler -- removing node: peer=804 addr=217.69.1.32:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:23:09 Peer=805 is stalling block download, disconnecting
2019-05-28 04:23:09 ThreadSocketHandler -- removing node: peer=805 addr=104.207.130.139:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:23:10 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538252, us=1.46.104.112:62804, peer=808
2019-05-28 04:23:11 receive version message: /Syscoin Core:3.2.0/: version 70227, blocks=538252, us=1.46.104.112:35442, peer=809
2019-05-28 04:23:12 Peer=806 is stalling block download, disconnecting
2019-05-28 04:23:12 ThreadSocketHandler -- removing node: peer=806 addr=104.207.140.242:8369 nRefCount=1 fInbound=0 fMasternode=0
2019-05-28 04:23:12 CMasternodeSync::ProcessTick -- nTick 390 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2019-05-28 04:23:12 CMasternodeSync::ProcessTick -- nTick 390 nRequestedMasternodeAssets 0 -- requesting sporks from peer=809
2019-05-28 04:23:12 receive version message: /Syscoin Core:3.1.0/: version 70222, blocks=538252, us=1.46.104.112:47426, peer=810
2019-05-28 04:23:13 receive version message: /Syscoin Core:3.1.4/: version 70226, blocks=538252, us=1.46.104.112:16088, peer=811
2019-05-28 04:23:14 receive version message: /Syscoin Core:3.1.4/: version 70226, blocks=538252, us=1.46.104.112:44221, peer=812

IconFirm

hero member

Activity: 1438

Merit: 574

Always ask questions. #StandWithHongKong

Quote from: xbiv2 on May 30, 2019, 07:14:19 AM

Quote from: IconFirm on May 30, 2019, 03:12:21 AM

@xbiv2: Again, you're not using the latest version - the version in your screen shot shows v3.1.3. It is also exactly the same screen shot you posted earlier, I've no idea why you have reposted it, but you need to post the latest screen from the latest v3.2.0. You also need to post a log file as I requested earlier after starting the wallet with the commands I gave you earlier.

Im using thisone:
https://github.com/syscoin/syscoin/releases/tag/3.2.0.0

Then post a screen shot of your v3.2.0.0 node together with a log please.

xbiv2

full member

Activity: 560

Merit: 111

Quote from: IconFirm on May 30, 2019, 03:12:21 AM

@xbiv2: Again, you're not using the latest version - the version in your screen shot shows v3.1.3. It is also exactly the same screen shot you posted earlier, I've no idea why you have reposted it, but you need to post the latest screen from the latest v3.2.0. You also need to post a log file as I requested earlier after starting the wallet with the commands I gave you earlier.

Im using thisone:
https://github.com/syscoin/syscoin/releases/tag/3.2.0.0
windows64
the screen shows version of connected to me node
it shows heades is syncronised, but blocks syncronisation stuck on 364430 block

IconFirm

hero member

Activity: 1438

Merit: 574

Always ask questions. #StandWithHongKong

@xbiv2: Again, you're not using the latest version - the version in your screen shot shows v3.1.3. It is also exactly the same screen shot you posted earlier, I've no idea why you have reposted it, but you need to post the latest screen from the latest v3.2.0. You also need to post a log file as I requested earlier after starting the wallet with the commands I gave you earlier.

I'm trying to help you, but unless you are willing to help yourself & accept advice you're wasting both our time.

@blurry:

Quote from: blurryeyed on May 29, 2019, 03:32:09 AM

Either they don't like offers of help for their users or they don't want anyone knowing their dev has been banned....or both & they're just censorship crazy....lol

I'm pretty sure it's both.....

xbiv2

full member

Activity: 560

Merit: 111

Quote from: blurryeyed on May 29, 2019, 03:32:09 AM

Either they don't like offers of help for their users or they don't want anyone knowing their dev has been banned....or both & they're just censorship crazy....lol

@xbiv2: Pretty sure the wallet works fine, you must be doing something wrong. I wouldn't worry though, you're better off not getting involved with this lot anyway.

wallet is not worck
syncronisation stuck on 364430 block

https://github.com/syscoin/syscoin/releases/tag/3.2.0.0
windows64

blurryeyed

full member

Activity: 670

Merit: 120

TIME TO BAN THE YOBIT SCAM!!

Another deleted post from the debt ridden BCF thread:

Quote from: xbiv2 on May 27, 2019, 05:45:00 AM

Quote from: bstr156 on May 26, 2019, 10:22:53 PM

Quote from: xbiv2 on May 26, 2019, 08:36:42 PM

Quote from: xbiv2 on May 15, 2019, 06:22:23 PM

https://github.com/syscoin/syscoin/releases/tag/3.2.0.0
windows64
syncronisation stuck on 364430 block
what the problem?

WHEN WE GET WORKING CLIENT?

You must mean "WHEN I GET CLIENT WORKING?", because the client works fine for me and thousands of others. Visit Discord #Help channel if you haven't: https://discord.gg/RkK2AXD

You might need to -reindex or something simple like that.

THISONE:
https://github.com/syscoin/syscoin/releases/tag/3.2.0.0 (windows64)
IS NOT WORKING, syncronisation STARTED FOR ZERO (0 is future price of this scam)
syncronisation stuck on 364430 block

@xbiv2: You won't get any help here because the Syscoin dev sidhujag has been banned from Bitcointalk:

https://bpip.org/profile.aspx?p=sidhujag

...plus they don't care about users here. You're better off using the unofficial thread where the OP has already offered to help you:

https://bitcointalksearch.org/topic/m.51091559

Good luck.

Either they don't like offers of help for their users or they don't want anyone knowing their dev has been banned....or both & they're just censorship crazy....lol

@xbiv2: Pretty sure the wallet works fine, you must be doing something wrong. I wouldn't worry though, you're better off not getting involved with this lot anyway.

Topic: [SYS] SYSCOIN [Unofficial] - Due to censorship & secrecy on Official thread. - page 2. (Read 21682 times)