⚒ Syscoin -Blockchain Scalability, Trustless Interoperability for ERC20 projects

[cryptohunter]

Is the yobit syscoin market for real? i see their wallet in maintenance but is this just a temp issue

what have the devs here heard from yobit about when the wallet will go live again.

[sidhujag]

Is the yobit syscoin market for real? i see their wallet in maintenance but is this just a temp issue

what have the devs here heard from yobit about when the wallet will go live again.

afaik they have been live trading sys 2 post fork even though they were told not to.

[IconFirm]

I'm having issues upgrading my masternodes & sentinal to the latest version. When I enter the command:

Code:

bash <(curl -sL doublesharp.com/sys-masternode)

..and answer yes to the upgrade questions, everything seems to work untill this error is shown:

Code:

error: cannot open .git/FETCH_HEAD: Permission denied

fatal: Unable to create '/home/blah/syscoin/.git/index.lock': Permission denied
---------------------------------------------------------------------------------------
    __________________  ___________
  _/ __ \_  __ \_  __ \/  _ \_  __ \
  \  ___/|  | \/|  | \(  <_> )  | \/
   \___  >__|   |__|   \____/|__|
       \/
---------------------------------------------------------------------------------------
Unable to checkout https://www.github.com/syscoin/syscoin/tree/master, please make sure it exists.

Is there a problem with git, or am I doing something wrong?

Thanks.

EDIT:

Fixed. I manually downloaded the script & ran it instead - all updated now.

EDIT2:

Spoke too soon. Since upgrading I'm seeing "SENTINEL_PING_EXPIRED" on my QT wallet. The VPS masternode is fully sync'd & running with no errors, but sentinel logs show:

Code:

[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.
[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.

I also notice there are no v3.0.6 nodes showing in my QT peers list (apart from my masternode IP which I added to my QT conf) or on the Syscoin block explorer network tab:

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

..so maybe an issue with the new sentinel &/or wallet?

[cryptohunter]

Is the yobit syscoin market for real? i see their wallet in maintenance but is this just a temp issue

what have the devs here heard from yobit about when the wallet will go live again.

afaik they have been live trading sys 2 post fork even though they were told not to.

damn that would explain the bargain prices there

thanks for answer

[IconFirm]

Is the yobit syscoin market for real? i see their wallet in maintenance but is this just a temp issue

what have the devs here heard from yobit about when the wallet will go live again.

afaik they have been live trading sys 2 post fork even though they were told not to.

damn that would explain the bargain prices there

thanks for answer

Yeah, stay well away from that place.

[Jcga]

Hi guyz,
just sharing this return of experience from Sys masternoding with Masterminer.tech after a big month of using this service.
1st of all, super thx, easy to set up plus zero worries about maintenance, updates etc. A MN running h24 at it's best.

Thx to regularity i have noticed my rank in the sys rich list has increased which is a very good sign.

Pooling coming up, starting nowadays, check it out !


Website => https://masterminer.tech/

Telegram group => https://t.me/joinchat/HL9uVRK4iDSI6y0Y_VCYjg

[classicsucks]

So, finally I got my coins out of Poloniex.  I have absolutely no doubt that this would not have happened if those in the same situation as myself hadn't started to hound both Poloniex, Blockchain Inc & the Syscoin "team" to get it sorted or else. I've informed my solicitor & no further action will be taken, but this whole affair has left a very nasty after taste, especially considering the attitude of some people claiming to be the SCMT & sebastian1234 of Blockchain Foundry Inc himself, who's secrecy & refusal to answer basic questions has left me in considerable doubt about this whole project.

I've said all along that the idea & devs are good & have been aware of sidhujag & his work since the Devcoin days, which was my main reason for investing in Syscoin, but I'm more than a little concerned about the attitude of the people surrounding him & the use of noob/fake accounts by certain individuals to insult Syscoin users who's crime was to ask the wrong kind of questions.

I've now added a couple of masternodes & will play it by ear - I hope my faith in this project is isn't misguided.

You have stated your point and we have answered you several times but you consistently remove my responses from your quotes, leaving only your complaints.

I understand the frustration you have had with Poloniex and we also wanted the wallet updated as soon as possible.

Poloniex is a pile of sh*t, everybody knows this. It's not the fault of the Syscoin team. However, the Syscoin team pushed out a horrible update to the code, which created an upgrade nightmare. It took me 2 days of dicking around to get the blockchain up to date and the wallet balance recognized. It was truly awful having that sinking feeling of "well I guess my coins are gone". Team, please don't ever do this again!

 

[IconFirm]

A VPS is cheaper - $10 a month.

Still getting this error with the v3.0.6 wallet:

Since upgrading I'm seeing "SENTINEL_PING_EXPIRED" on my QT wallet. The VPS masternode is fully sync'd & running with no errors, but sentinel logs show:

Code:

[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.
[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.

..so maybe an issue with the new sentinel &/or wallet?

Anyone else got this problem with the new wallet?

[CoinEraser]

So, finally I got my coins out of Poloniex.

I am very happy to read that. Finally Poloniex managed to update the wallet and enable withdraws again. Because of Poloniex do not lose your faith in the project. I've been a Syscoin holder since day one of the project and I'm always positively surprised how well Syscoin is continue developing. Anyway, the main thing is you have your Syscoins back. That's the most important thing first. Have fun with your masternode. 

[sidhujag]

A VPS is cheaper - $10 a month.

Still getting this error with the v3.0.6 wallet:

Since upgrading I'm seeing "SENTINEL_PING_EXPIRED" on my QT wallet. The VPS masternode is fully sync'd & running with no errors, but sentinel logs show:

Code:

[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.
[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.

..so maybe an issue with the new sentinel &/or wallet?

Anyone else got this problem with the new wallet?

i dont think any of that code has changed maybe you should turn on debug in the conf file to see whats happening.

[sebastien1234]

Syscoin creator & CIO of Blockchain Foundry Inc. Sebastian Schepis unveils a sneak peek of Blockmarket 3.0, announces release date of June 25th, 2018 & introduces the most flexible & affordable tokenization platform in existence today.

Reference:
https://twitter.com/syscoin/status/1010155037396553728

What does it really mean, Sebastien1234?
Will Smart contracts and token-crowd-fund platform will be integrated into Syscoin network and its services?

Hardened smart-contracts have been with the Syscoin protocol since its creation, in 2014. Token crowdfunding capabilities were already integrated to Syscoin 3.0, upon the recent launch.

Blockmarket 3.0 will provide you an easy-to-use portal to create those tokens, with just a few mouse clicks. With Blockmarket Desktop 3.0, Syscoin becomes the cryptocurrency with the easiest and quickest platform to create your own token without requiring expensive Blockchain developers.

[cabbage55]

You will need to hold in the syscoin blockmarket wallet and have an alias. New wallet should be released soon.

[sebastien1234]

A VPS is cheaper - $10 a month.

Still getting this error with the v3.0.6 wallet:

Since upgrading I'm seeing "SENTINEL_PING_EXPIRED" on my QT wallet. The VPS masternode is fully sync'd & running with no errors, but sentinel logs show:

Code:

[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.
[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.

..so maybe an issue with the new sentinel &/or wallet?

Anyone else got this problem with the new wallet?

Our Slack Syscoin community is your best bet for troubleshooting support, join the #masternodes channel. To get an invite to our slack, please follow instructions at http://join.syscoin.org.

[sidhujag]

A VPS is cheaper - $10 a month.

Still getting this error with the v3.0.6 wallet:

Since upgrading I'm seeing "SENTINEL_PING_EXPIRED" on my QT wallet. The VPS masternode is fully sync'd & running with no errors, but sentinel logs show:

Code:

[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.
[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.

..so maybe an issue with the new sentinel &/or wallet?

Anyone else got this problem with the new wallet?

i dont think any of that code has changed maybe you should turn on debug in the conf file to see whats happening.

hmm justins script for updating masternodes was broken and caused this issue if you used his script (doublesharp) then try it again i would clean the syscoin and sentinel dirs to be safe it will know what to do.

[IconFirm]

A VPS is cheaper - $10 a month.

Still getting this error with the v3.0.6 wallet:

Since upgrading I'm seeing "SENTINEL_PING_EXPIRED" on my QT wallet. The VPS masternode is fully sync'd & running with no errors, but sentinel logs show:

Code:

[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.
[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.

..so maybe an issue with the new sentinel &/or wallet?

Anyone else got this problem with the new wallet?

i dont think any of that code has changed maybe you should turn on debug in the conf file to see whats happening.

hmm justins script for updating masternodes was broken and caused this issue if you used his script (doublesharp) then try it again i would clean the syscoin and sentinel dirs to be safe it will know what to do.

Hi sidhujag,

Yes, I was beginning to think that actually - I did use the script to update.

I gave up troubleshooting the issue & reinstalled my masternodes using the script & everything is working again, including sentinel, although I'm not sure if the script I used was the updated one or the previous broken one as I done it about 7 hours ago at the time of writing this post. Do you think I should re-install them again just to make sure - or can I simply re-run the updated script to save time/hassle?

Thanks for letting me know sidhujag, thought I was going mad there for a minute!  

[masterminer.tech]

You're absolutely correct. It is $5/month cheaper to host it yourself.

But you'll have to deal with the problems you're currently facing (maintenance and upgrade). And may even miss a reward too if your node is down for too long.
You can literally buy few months worth of hosting with masterminer with that reward and forget this headache 

A VPS is cheaper - $10 a month.

Still getting this error with the v3.0.6 wallet:

Since upgrading I'm seeing "SENTINEL_PING_EXPIRED" on my QT wallet. The VPS masternode is fully sync'd & running with no errors, but sentinel logs show:

Code:

[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.
[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.

..so maybe an issue with the new sentinel &/or wallet?

Anyone else got this problem with the new wallet?

[sebastien1234]

https://twitter.com/syscoin/status/1011458165005783046

From Syscoin's Twitter:

We are proud to present the #Syscoin community with #Blockmarket Desktop 3.0!
#StayTuned for a more in-depth blog post tomorrow
Download Blockmarket Desktop 3.0 Now!
https://github.com/syscoin/blockmarket-desktop-public/releases/tag/3.0.0

[Absholom]

I can see that this platform keeps on progressing. Version 3.0 is perfect for new investors. Keep it up!

[IconFirm]

A VPS is cheaper - $10 a month.

Still getting this error with the v3.0.6 wallet:

Since upgrading I'm seeing "SENTINEL_PING_EXPIRED" on my QT wallet. The VPS masternode is fully sync'd & running with no errors, but sentinel logs show:

Code:

[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.
[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.

..so maybe an issue with the new sentinel &/or wallet?

Anyone else got this problem with the new wallet?

i dont think any of that code has changed maybe you should turn on debug in the conf file to see whats happening.

hmm justins script for updating masternodes was broken and caused this issue if you used his script (doublesharp) then try it again i would clean the syscoin and sentinel dirs to be safe it will know what to do.

Hi sidhujag,

Yes, I was beginning to think that actually - I did use the script to update.

I gave up troubleshooting the issue & reinstalled my masternodes using the script & everything is working again, including sentinel, although I'm not sure if the script I used was the updated one or the previous broken one as I done it about 7 hours ago at the time of writing this post. Do you think I should re-install them again just to make sure - or can I simply re-run the updated script to save time/hassle?

Thanks for letting me know sidhujag, thought I was going mad there for a minute!  

Update:

I ended up doing another fresh install of my masternodes with the newer script, as trying to upgrade using the script broke things again. Everything is working again now, but I think there is still a problem with the script.

[sidhujag]

A VPS is cheaper - $10 a month.

Still getting this error with the v3.0.6 wallet:

Since upgrading I'm seeing "SENTINEL_PING_EXPIRED" on my QT wallet. The VPS masternode is fully sync'd & running with no errors, but sentinel logs show:

Code:

[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.
[Errno 111] Connection refused
Cannot connect to syscoind. Please ensure syscoind is running and the JSONRPC port is open to Sentinel.

..so maybe an issue with the new sentinel &/or wallet?

Anyone else got this problem with the new wallet?

i dont think any of that code has changed maybe you should turn on debug in the conf file to see whats happening.

hmm justins script for updating masternodes was broken and caused this issue if you used his script (doublesharp) then try it again i would clean the syscoin and sentinel dirs to be safe it will know what to do.

Hi sidhujag,

Yes, I was beginning to think that actually - I did use the script to update.

I gave up troubleshooting the issue & reinstalled my masternodes using the script & everything is working again, including sentinel, although I'm not sure if the script I used was the updated one or the previous broken one as I done it about 7 hours ago at the time of writing this post. Do you think I should re-install them again just to make sure - or can I simply re-run the updated script to save time/hassle?

Thanks for letting me know sidhujag, thought I was going mad there for a minute!  

Update:

I ended up doing another fresh install of my masternodes with the newer script, as trying to upgrade using the script broke things again. Everything is working again now, but I think there is still a problem with the script.

thanks there is an issue for this see if you can provide some more insight into it so the developer of it can fix: https://github.com/syscoin/syscoin/issues/231.

 3 hours ago he did a fix did you try less than 3 hrs ago?