xbiv2
|
|
June 02, 2019, 06:28:06 PM |
|
@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.0Then post a screen shot of your v3.2.0.0 node together with a log please. 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 (OP)
|
|
June 02, 2019, 08: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.
|
|
|
|
IconFirm (OP)
|
|
June 04, 2019, 12:07:38 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.
|
|
|
|
xbiv2
|
|
June 05, 2019, 04:56:16 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
|
|
|
|
blurryeyed
Full Member
Offline
Activity: 670
Merit: 120
TIME TO BAN THE YOBIT SCAM!!
|
|
June 05, 2019, 11: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.
|
|
|
|
|
IconFirm (OP)
|
|
June 08, 2019, 03:27:05 PM |
|
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.
|
|
|
|
IconFirm (OP)
|
|
June 13, 2019, 08:15:40 AM |
|
@bontol72: As you only post about Syscoin I presume you are part of their "team" - which one are you?
|
|
|
|
blurryeyed
Full Member
Offline
Activity: 670
Merit: 120
TIME TO BAN THE YOBIT SCAM!!
|
|
June 15, 2019, 10:01:20 PM |
|
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/3364 releases so far & it's still not working.....LOL At least they are consistent with their censorship across all platforms.
|
|
|
|
IconFirm (OP)
|
|
June 16, 2019, 03:16:31 PM |
|
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/3364 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.
|
|
|
|
Gaglam
|
|
June 17, 2019, 10:57:06 AM |
|
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?
|
|
|
|
blurryeyed
Full Member
Offline
Activity: 670
Merit: 120
TIME TO BAN THE YOBIT SCAM!!
|
|
June 19, 2019, 05:30:12 PM |
|
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://bitcointalk.org/index.php?topic=1466445.msg51499450#msg51499450Fact 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
|
|
June 20, 2019, 08:54:04 AM |
|
Meanwhile, the huge success dropped below 600 sats
|
|
|
|
Gaglam
|
|
June 20, 2019, 05:54:36 PM |
|
Charts don't lie
|
|
|
|
IconFirm (OP)
|
|
June 20, 2019, 07:04:12 PM Last edit: June 20, 2019, 07:16:27 PM by IconFirm |
|
Charts don't lie Indeed they don't & neither do the numbers which everyone can see. @mendez12: I created this thread for members who have been censored from posting on the official thread, which you clearly have not. Your account has recently woken from a long period of inactivity to start posting on behalf of the BCF team & you are very obviously a shill account. Please keep your shilling to the official censored thread & use your real account if you wish to post here again. If anyone knows who the person is who had their posts deleted from the Syscoin repo, could they please point him/her to this thread - I'd be very interested to hear what they have to say about the matter. It's sad to see what such a promising project has degenerated into.. the devs really should not censor any constructive criticism as they have in their own thread.
Hi cryptographist. Yes, it's been steadily getting worse & worse over the last year I'm afraid - no project has ever succeeded using such tactics & it is usaually a sure sign that all is not well & end users will get screwed eventually.
|
|
|
|
IconFirm (OP)
|
|
June 21, 2019, 03:44:56 PM |
|
Thought I'd check out the latest financial reports from BCF to see if they're doing any better - they're not. Company deficit has risen to $12,667,881 from $12,315,218 which is up by ~$350,000 from three months ago, while company losses have risen to $1,154,541 from $801,878 - again another ~$350,000 increase - coincidence? Again the auditor expresses his concern about the future of BCF: The Company’s condensed consolidated interim financial statements at March 31, 2019 indicate an accumulated deficit of $12,667,881 and a comprehensive loss of $1,154,541 during the six-month period. The Company currently does not have any significant continuing sources of revenues and the Company will be reliant on its ability to monetize the Company’s sales pipeline to continue operations. The uncertainty regarding the future sources of revenue or cash flow indicate the existence of material uncertainties that cast significant doubt about the Company’s ability to continue as a going concern. Interestingly, the very last paragraph of the report states that Daniel Wasyluk resigned as President of the Company on May 30, 2019 - seems to be some seat swapping going on at BCF for some reason..... Source: https://webfiles.thecse.com/sedar_filings/00031166/1905301959275471.pdfSyscoin market continues to crumble & is now approaching the half sat value with no sign of stopping. The end is nigh?
|
|
|
|
Gaglam
|
|
June 22, 2019, 08:28:35 AM |
|
The syscoin shillers said that only the good coins will survive the 2018/2019 bear market. Seems like sys is not among those "good" coins.
|
|
|
|
blurryeyed
Full Member
Offline
Activity: 670
Merit: 120
TIME TO BAN THE YOBIT SCAM!!
|
|
June 23, 2019, 03:05:59 PM |
|
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.
I said this in jest, but I'm actually beginning to think this might actually be the case....lol Price is almost nothing now too.
|
|
|
|
IconFirm (OP)
|
|
June 24, 2019, 08:26:36 PM |
|
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.
I said this in jest, but I'm actually beginning to think this might actually be the case....lol Price is almost nothing now too. They do tend to forget about their own thread tbh, sometimes for months, but it is strange that they are being so quiet - especially after supposedly such a "successful" launch of their new wallet that there's only ~60 of, with ~54 of them being owned by the same person/organisation.......lol I know the dev sidhujag is banned, but I can't see the whole team getting themselves banned - I'll look into it.
|
|
|
|
IconFirm (OP)
|
|
June 28, 2019, 06:40:01 PM |
|
Well, Syscoin gestapo didn't hang around deleting my post: A reply of yours, quoted below, was deleted by the starter of a self-moderated topic. There are no rules of self-moderation, so this deletion cannot be appealed. Do not continue posting in this topic if the topic-starter has requested that you leave. You can create a new topic if you are unsatisfied with this one. If the topic-starter is scamming, post about it in Scam Accusations. They're trying really hard to hide their financial trainwreck, even though it's in the public domain. At least we know someone in the team isn't banned now.....
|
|
|
|
|