Author

Topic: [ANN] Syscoin - Business on the Blockchain - LAUNCHED! - page 148. (Read 490229 times)

sr. member
Activity: 391
Merit: 250
The new wallet is not working for me on Windows 8 - it gets as far as saying something like 'loading addresses' and then just disappears.

The same here on Windows 7. It places an icon on the taskbar which doesn't do anything , and the main window doesn't show up at all. Nice crappy software this is.
sr. member
Activity: 308
Merit: 250
if you run the client and then close. then try to run again, it says loading addresses then never starts. its showing in system tray tho. windows 8.1
member
Activity: 75
Merit: 10
When they are active in bittrex and mintpal?
full member
Activity: 213
Merit: 101
then the network was completely saturated with clients looking for nodes leading to the fork issues as the connected to pools that didn't upgrade.
Update protocol version and minimum protocol version in version.h so that nodes running the new version automatically disconnect nodes running the old version.

Code:
static const int PROTOCOL_VERSION = 70002;

// disconnect from peers older than this proto version
static const int MIN_PEER_PROTO_VERSION = 70002;
sr. member
Activity: 295
Merit: 250
full member
Activity: 224
Merit: 100
I've been watching Syscoin from the very beginning (although I didn't invest in the IPO).

I have to say that most of you guys are impatient, quick to judge idiots. People here witnessed only hundreds of identical launches of Bitcoin/Litecoin clones, where devs were only capable of adding 10 lines of code and changing a few variables. SysCoin is one of the first altcoins with a completely new set of features on top of the basic Litecoin code (I mean seriously, even the mining part has been improved). Do you guys realise how complicated is it to even make a coin merge-mineable with everything else? I didn't expect the launch to be smooth, a big software project always will contain a handful of bugs.

But what's wrong with this world is you, people who're constantly trolling here. You didn't even bother to read the [ANN] or check the Syscoin website. Most of you have no idea who's on the dev team (while all info was on the website for weeks). You can't even do simple math. I've seen countless kids in every thread here, the behaviour pattern is 100% the same. What a bunch of clinical idiots this forum became Grin




I don't think you have any idea what's happened here - people who actually did buy this coin (not guys like you who are parachuting in from a high horse with no stake in the issue whatsoever) were misled about the capability of this team and the quality of the work. The weekend-long ordeal of this untested, haphazard launch was far below minimum standards for *any* coin launch. It is one of the worst I've ever seen. People had a right to expect a lot more out of a 1500BTC project. At the very least, this team massively overpromised what they could deliver and misrepresented their capabilities.

They're STILL overpromising: They promised to band aid the wallet within a day, and people are *STILL* reporting problems on this very page. A solid wallet was supposed to be released on the 16th, Saturday. It's Monday, with no end in sight. And no confidence that even when a fix is announced that there wont be other, potentially more serious, hidden problems.
sr. member
Activity: 378
Merit: 250
The new wallet is not working for me on Windows 8 - it gets as far as saying something like 'loading addresses' and then just disappears.
sr. member
Activity: 308
Merit: 250
syncs now. now, I need to know this

what about the people that has their coins stuck at 0/6 confirmations  Undecided I sent 100 coins, they were confirmed 1. so i sent 300k in the second minute and they are stuck. i got the 100 coins tho. what should we do now? I suppose they are gone.
sr. member
Activity: 313
Merit: 250
blockchain sync stuck at 1663 blocks now

ur on wrong fork man

i deleted everything and added nodes from the first thread link.

can you give me correct nodes?

I deleted everything and added nodes from a paste bin link, not sure where it is now tho, the link that is. but here is my list.

addnode=68.110.119.91
addnode=99.249.255.234
addnode=91.134.53.161
addnode=50.72.149.56
addnode=207.68.212.54
addnode=23.240.55.44
addnode=76.115.198.51
addnode=54.72.229.220
addnode=24.186.111.60
addnode=93.77.104.84
addnode=96.242.181.7
addnode=206.63.230.236
addnode=99.242.230.163
addnode=37.59.18.108
addnode=86.159.199.211
addnode=67.253.247.113
addnode=24.147.192.252
addnode=72.239.177.162
addnode=98.220.3.187
addnode=86.31.116.79
addnode=71.95.186.175
addnode=58.169.222.80
addnode=198.50.132.91
addnode=37.187.71.108
addnode=71.163.67.32
addnode=23.234.223.141
addnode=70.173.167.3
addnode=78.46.22.103
addnode=31.220.4.41
addnode=146.115.133.109
addnode=70.29.206.168
addnode=174.110.195.255
addnode=62.210.122.161
addnode=96.27.68.140
addnode=198.15.127.242
addnode=194.79.23.168
addnode=67.173.41.36
addnode=68.231.192.15
addnode=82.46.101.131
addnode=75.91.157.247


deleted everything, wallet.dat as well, deleted the folder, redownloaded, put your nodes, still stuck on 1663.(4 hours ago)

Man, I think the wallet is connecting to some other blockchain and I have no clue why?

Put this in syscoin.conf file and delete what is there.

addnode=76.25.201.234:8369
addnode=67.253.247.113:8369
addnode=node.syscoin.me:6369

Open syscoin folder.

Delete everything but the syscoin.conf and wallet.dat file.

Open syscoin program again. Everything will sync and you should be on the latest block.

full member
Activity: 224
Merit: 100
I salute SYS for returning the 250BTC portion of the escrow so that Moolah has the entire escrow. As far as your latest update:

- get help from all the smart C++ devs we can, we already have several helping us thanks to the potential of this project. They will be compensated once we have funds to compensate them with.

In other words, the core team did not have any hard-core C++ devs?

- addressing the issues with wallet rescan crash which is affecting some users
- increasing the amount of DNSseeds we have because the network gets hammered more than we expected when resyncs are flying around
- making sure the merged mining works as something to do with tx messages appears to be preventing that
- addressing anything that might come up with using services- no issues have been reported yet but we already know we need some form of getServiceCost() command prior to using a service; issue has been logged in github.
- We need to get a better process with pool operators to avoid these forks when updates need to roll out - as today
- We plan on upgrading the codebase to bitcoin 0.9.2 (this is not easy) as it has many improvements, better packaging and testing tools
- Complete the automated test suite which is a challenge on a p2p network where assertions are dependent on confirmations (that is what cakenet is for)


Given all the wildcards, I think MOOLAH should withold the escrow until
1) an independent review led by a team of completely independent developers, perhaps selected by Moolah, independently review the code and certify there are no hidden bugs that will come back to bite people later
2) the leadership team is reorganised with developers/project managers that are vetted (Proof Of *Real* Developer) who have a clean history that affirms they'd never release a broken Litecoin-clone code/network like this.



That is the shortlist of things we must address ASAP. Beyond that, we have a roadmap of features and will have a better build/release process for these moving forward:


Of course, we're addressing the initial higher-priority issues first.


I think a revised roadmap needs to be prepared and put in the hands of a team the market will have confidence in. Right now, the only reason the market price is hovering above the ICO price is because Moolah has affirmed that it will not release the escrow as long as the wallet remains broken. I'd argue that it should also not be released until there's confidence there's a team in place that wont release more broken code and empty promises in the future. That's when the price will soar toward where it should've been at this point. Until then, we're looking at stagnation and uncertainty about code quality, even if you manage to band aid this depressing launch.

jr. member
Activity: 52
Merit: 2
I've been watching Syscoin from the very beginning (although I didn't invest in the IPO).

I have to say that most of you guys are impatient, quick to judge idiots. People here witnessed only hundreds of identical launches of Bitcoin/Litecoin clones, where devs were only capable of adding 10 lines of code and changing a few variables. SysCoin is one of the first altcoins with a completely new set of features on top of the basic Litecoin code (I mean seriously, even the mining part has been improved). Do you guys realise how complicated is it to even make a coin merge-mineable with everything else? I didn't expect the launch to be smooth, a big software project always will contain a handful of bugs.

But what's wrong with this world is you, people who're constantly trolling here. You didn't even bother to read the [ANN] or check the Syscoin website. Most of you have no idea who's on the dev team (while all info was on the website for weeks). You can't even do simple math. I've seen countless kids in every thread here, the behaviour pattern is 100% the same. What a bunch of clinical idiots this forum became Grin

sr. member
Activity: 308
Merit: 250
now will choose 1-2 other nodes to test one by one.
sr. member
Activity: 308
Merit: 250
blockchain sync stuck at 1663 blocks now

ur on wrong fork man

i deleted everything and added nodes from the first thread link.

can you give me correct nodes?

I deleted everything and added nodes from a paste bin link, not sure where it is now tho, the link that is. but here is my list.

addnode=68.110.119.91
addnode=99.249.255.234
addnode=91.134.53.161
addnode=50.72.149.56
addnode=207.68.212.54
addnode=23.240.55.44
addnode=76.115.198.51
addnode=54.72.229.220
addnode=24.186.111.60
addnode=93.77.104.84
addnode=96.242.181.7
addnode=206.63.230.236
addnode=99.242.230.163
addnode=37.59.18.108
addnode=86.159.199.211
addnode=67.253.247.113
addnode=24.147.192.252
addnode=72.239.177.162
addnode=98.220.3.187
addnode=86.31.116.79
addnode=71.95.186.175
addnode=58.169.222.80
addnode=198.50.132.91
addnode=37.187.71.108
addnode=71.163.67.32
addnode=23.234.223.141
addnode=70.173.167.3
addnode=78.46.22.103
addnode=31.220.4.41
addnode=146.115.133.109
addnode=70.29.206.168
addnode=174.110.195.255
addnode=62.210.122.161
addnode=96.27.68.140
addnode=198.15.127.242
addnode=194.79.23.168
addnode=67.173.41.36
addnode=68.231.192.15
addnode=82.46.101.131
addnode=75.91.157.247


deleted everything, wallet.dat as well, deleted the folder, redownloaded, put your nodes, still stuck on 1663.(4 hours ago)

Man, I think the wallet is connecting to some other blockchain and I have no clue why?
sr. member
Activity: 324
Merit: 250
sr. member
Activity: 313
Merit: 250
stuck at 1663.

Moonriver, did you add the nodes?  Try that.


if you are on the wrong fork:
1. close your wallet
2. go to your data dir and wipe everyting BUT peers.dat, wallet.dat and the .conf file
3. put this file in that folder: https://mega.co.nz/#!HFMQSIrJ!g6BGdCv48RT11sgFOTsFiFbjoiR7DvrCum8kMw7EpH0
4. reopen wallet and wait for sync + connections
bootstrap.dat has the blocks in it. What about the peers? I cant get any connection to the wallet.

Put this in syscoin.conf file and delete what is there.

addnode=76.25.201.234:8369
addnode=67.253.247.113:8369
addnode=node.syscoin.me:6369

Now my wallet wont open  Cry
Can I just get a refund now? Its been 36hrs and still so many issues.

No refund. If people would just read and follow the instructions that are posted on every page you would be up and running already. When Mintpal goes live with deposits just send your coins there and dump into the walls.

Go to task manager and kill syscoin-qt.exe

Go to the start menu and type run and hit enter then type %APPDATA% and hit enter

Open syscoin folder.

Delete everything but the syscoin.conf and wallet.dat file.

Open syscoin program again. Everything will sync and you should be on the latest block.

Finally Smiley This worked, wallet synced and running.

sr. member
Activity: 308
Merit: 250
what about the people that has their coins stuck at 0/6 confirmations  Undecided I sent 100 coins, they were confirmed 1. so i sent 300k in the second minute and they are stuck. i got the 100 coins tho. what should we do now? I suppose they are gone.
hero member
Activity: 750
Merit: 511
blockchain sync stuck at 1663 blocks now
ur on wrong fork man
i deleted everything and added nodes from the first thread link.
can you give me correct nodes?

I have only one actual node (with 1962 height):
67.253.247.113:8369

Don't use an old nodes.
member
Activity: 84
Merit: 10

"Defensive whining?". Please. We've already apologized many, many, many times. Already detailed steps being taken to make sure similar problems don't happen later but let me expand on it- with the current team we have, and no funding, and no plans to dump (to get funding), we are planning on:
- get help from all the smart C++ devs we can, we already have several helping us thanks to the potential of this project. They will be compensated once we have funds to compensate them with.
- addressing the issues with wallet rescan crash which is affecting some users
- increasing the amount of DNSseeds we have because the network gets hammered more than we expected when resyncs are flying around
- making sure the merged mining works as something to do with tx messages appears to be preventing that
- addressing anything that might come up with using services- no issues have been reported yet but we already know we need some form of getServiceCost() command prior to using a service; issue has been logged in github.
- We need to get a better process with pool operators to avoid these forks when updates need to roll out - as today
- We plan on upgrading the codebase to bitcoin 0.9.2 (this is not easy) as it has many improvements, better packaging and testing tools
- Complete the automated test suite which is a challenge on a p2p network where assertions are dependent on confirmations (that is what cakenet is for)

That is the shortlist of things we must address ASAP. Beyond that, we have a roadmap of features and will have a better build/release process for these moving forward:


Of course, we're addressing the initial higher-priority issues first.

The features is too faraway.Just do the basic quick,as wallet SYNC,wallet UI,blockchain...
Otherwise you will lose your supporter,Even if you do better later,Because they had gone away.

wallet offline ... investigating blockchain issues. @BittrexExchange

refresh your browser dude, it's been online at bittrex for at least a few hours now.
refresh your browser bro, The wallet been disabled at bittrex now.
lol I see it has
legendary
Activity: 1036
Merit: 1001
Syscoin- Changing the way people do business.

People did not pay attention to our announcements throughout the day about the fork so many were very slow to update their client leading to multiple forks.

So, you expect people to sit here all day and read this thread for updates instead of setting up a blog or mailing list to keep people updated about wtf is going on?

We have a mailing list AND an affiliate list for pools. They were messaged about the fork.
member
Activity: 61
Merit: 10

"Defensive whining?". Please. We've already apologized many, many, many times. Already detailed steps being taken to make sure similar problems don't happen later but let me expand on it- with the current team we have, and no funding, and no plans to dump (to get funding), we are planning on:
- get help from all the smart C++ devs we can, we already have several helping us thanks to the potential of this project. They will be compensated once we have funds to compensate them with.
- addressing the issues with wallet rescan crash which is affecting some users
- increasing the amount of DNSseeds we have because the network gets hammered more than we expected when resyncs are flying around
- making sure the merged mining works as something to do with tx messages appears to be preventing that
- addressing anything that might come up with using services- no issues have been reported yet but we already know we need some form of getServiceCost() command prior to using a service; issue has been logged in github.
- We need to get a better process with pool operators to avoid these forks when updates need to roll out - as today
- We plan on upgrading the codebase to bitcoin 0.9.2 (this is not easy) as it has many improvements, better packaging and testing tools
- Complete the automated test suite which is a challenge on a p2p network where assertions are dependent on confirmations (that is what cakenet is for)

That is the shortlist of things we must address ASAP. Beyond that, we have a roadmap of features and will have a better build/release process for these moving forward:


Of course, we're addressing the initial higher-priority issues first.

The features is too faraway.Just do the basic quick,as wallet SYNC,wallet UI,blockchain...
Otherwise you will lose your supporter,Even if you do better later,Because they had gone away.

wallet offline ... investigating blockchain issues. @BittrexExchange

refresh your browser dude, it's been online at bittrex for at least a few hours now.
refresh your browser bro, The wallet been disabled at bittrex now.
Jump to: