Author

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

legendary
Activity: 1036
Merit: 1001
Syscoin- Changing the way people do business.

Sir, just ignore some posts, they are posted by competitors of this coin, or someone want to buy this coin at a lower price even some boring guys ect.

Thanks, I'm aware and appreciate the encouragement.

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. These are being resolved now if they aren't resolved already. The team has a list of items to work on. We have additional devs helping us out for FREE at the moment because they can see the code and understand the potential here soon as these bugs are ironed out.
Send an alert out on the network with link to the wallet update, so people have no choice but to pay attention.  You did update the alert keys, so you should be able to do it.

Agree, 100%. I was stuck trying to solve these issues related to the unique aspects of SYS like regenerated mining fees. This is a great suggestion we should have done this and will in the future.

DEVS:

please do not release again until it is working solid.  get a group of testers outside of your small dev group.  i volunteer test test wallets, and i'm sure many others from the IRC with good intentions would do so as well.  seems your sample size is too small to detect these issue before you pushed out these wallets.  i recommend more thorough testing, even if it means further delays.  best to do it right, not do it fast.

just my 2c.

Yep, will will do this and leverage this approach on a tesnet as we did with the fix today. The fix didn't address the wallet rescan bug which is an issue already logged in github, but it fixed the major problem related to coinbase mismatches.

Request withdrawal, deposits and trading to be completely disabled on all exchanges. Request all pools to stop mining.

Take 24-48 hours to inform and confirm everyone has the most updated wallet, once confirmed request everything to open again.

Viacoin dev did that and had all problems fixed pretty quick.

We didn't have that much time. Based on the error it was a critical issue that would prevent people from mining thus we had to act immediately, especially so shortly after the launch. I agree in practice though future issues should be handled with a larger time window. Even though we gave pools 3hrs (at the least) to prep for the fork and another hour after the actual wallet was released some of the larger pools were slow to upgrade... 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.

In the future we'll be more prepared this was just a very critical bug we needed to address ASAP. Not something any team wants to deal with but something we had to do.

Can you please comment on the linux wallet issues we have? A lot of people updated their wallet or like me just started over but the block is stuck on 1663 and error occur.

Yes linux wallets are working please make sure you are connecting to nodes that are running the correct version/fork. Use connect= if needed to force to a proper node. Also, the network is saturated and needs more nodes on the right version - another reason for very slow sync for linux users. Pools are up and running though so the linux build will work. People in IRC are passing around the correct nodes to connect to and we have also tweeted the pools that have stood up on the right fork for miners. If there are still linux issues in a few hours, we'll followup and address. My linux node took about 15min just to start syncing and it had plenty of peers prior to the update today.

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

These are not huge issues to address- dns seeds (we have them need to add more, its already in the code); wallet UI- something we already spoke to PRE launch, updates are coming this week. Blockchain - the forks will be resolved soon if they aren't already.

Obviously you realized that you were whining defensively, but it's in your favor that you've adjusted here and responded appropriately.

I'll admit I was being defensive. Hard not to be in my position but I understand the communities frustration. I'm not ignoring it or calling anyone in the community derogatory names (not saying you are, others have).

how does one go about using the marketplace anyways.

The marketplace uses the "offer" commands. This is intended for devs to build on as business opportunities for them (of course once we iron out the smaller wallet issues listed above). Remember all services cost fees so if you want to play with these for free - use the testnet. In the console type "help" you'll see a number of "offer" commands. These commands are used to list/view/buy items on the Syscoin blockchain. If you type "offernew help" for example it will tell you how to create an offer, after which you will need to activate it before it can be purchased by others using "offeractivate".

We have a boilerplate market for devs started (https://github.com/syscoin/sysmarket) who want to start building on this- we are happy to take pull requests related to this front-end to bootstrap people and get them going. It uses the Syscoin JSON RPC and admittedly lacks documentation which we will add over this week. We're also adding more functionality to the QT wallet itself related to the market, but the QT wallet is intended to be a "reference client" so it just mirrors the daemon commands.
full member
Activity: 210
Merit: 100
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
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?
full member
Activity: 210
Merit: 100
blockchain sync stuck at 1663 blocks now

ur on wrong fork man

full member
Activity: 210
Merit: 100
I dont understand what the big deal is... forks happen on most coins, as long as people get on the right fork then their good. If not then its their own fault and their coins will be worthless lol.
sr. member
Activity: 308
Merit: 250
blockchain sync stuck at 1663 blocks now
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.
sr. member
Activity: 504
Merit: 253
Is the wallet working fine guys ?

Works fine here.
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
newbie
Activity: 18
Merit: 0
Is the wallet working fine guys ?
sr. member
Activity: 295
Merit: 250
Request withdrawal, deposits and trading to be completely disabled on all exchanges. Request all pools to stop mining.

Take 24-48 hours to inform and confirm everyone has the most updated wallet, once confirmed request everything to open again.

Viacoin dev did that and had all problems fixed pretty quick.

+1
newbie
Activity: 26
Merit: 0
Professional response: Apology for launch problems and detailing the steps taken to make sure similar problems don't happen later.

Unprofessional response:  Defensive whining.

Which end of the spectrum does this response lean toward?

"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.

Can you please comment on the linux wallet issues we have? A lot of people updated their wallet or like me just started over but the block is stuck on 1663 and error occur.

sr. member
Activity: 420
Merit: 250
Professional response: Apology for launch problems and detailing the steps taken to make sure similar problems don't happen later.

Unprofessional response:  Defensive whining.

Which end of the spectrum does this response lean toward?

"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.

Obviously you realized that you were whining defensively, but it's in your favor that you've adjusted here and responded appropriately.

sr. member
Activity: 258
Merit: 250
how does one go about using the marketplace anyways.
full member
Activity: 210
Merit: 100
relaunch? the wallet is working for me, im even mining too lol. what is wrong now besides future updates?
hero member
Activity: 952
Merit: 500
Request withdrawal, deposits and trading to be completely disabled on all exchanges. Request all pools to stop mining.

Take 24-48 hours to inform and confirm everyone has the most updated wallet, once confirmed request everything to open again.

Viacoin dev did that and had all problems fixed pretty quick.
legendary
Activity: 1036
Merit: 1001
Syscoin- Changing the way people do business.
Professional response: Apology for launch problems and detailing the steps taken to make sure similar problems don't happen later.

Unprofessional response:  Defensive whining.

Which end of the spectrum does this response lean toward?

"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.
hero member
Activity: 658
Merit: 500
DEVS:

please do not release again until it is working solid.  get a group of testers outside of your small dev group.  i volunteer test test wallets, and i'm sure many others from the IRC with good intentions would do so as well.  seems your sample size is too small to detect these issue before you pushed out these wallets.  i recommend more thorough testing, even if it means further delays.  best to do it right, not do it fast.

just my 2c.
full member
Activity: 213
Merit: 101
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. These are being resolved now if they aren't resolved already. The team has a list of items to work on. We have additional devs helping us out for FREE at the moment because they can see the code and understand the potential here soon as these bugs are ironed out.
Send an alert out on the network with link to the wallet update, so people have no choice but to pay attention.  You did update the alert keys, so you should be able to do it.
legendary
Activity: 1098
Merit: 1000
Angel investor.
Transparency:

I have deleted all of the FUD, lies, misinformation, and spam from earlier pages. They were being posted by the same 5 users. This is a huge project, some people don't seems to understand that- if you think the syscoin commands (via help) are the "same as almost all coins"... you are incorrect. Please compare the command lists and you will clearly see this.



Regarding hiring devs/PMS (project managers) etc- yes we fully plan on doing this. We don't have any funding at the moment as we're waiting for things to really be "sound" on the network before we get ANY BITCOINS FROM THE PRESALE. We used about 15BTC on Mintpal to provide buy support, the remaining 234.5 were returned to Moolah this morning as soon as I was aware of the issues and we immediately got to work.

We spent about 18hrs fixing this issue today. I realize there are still wallet relaunch/crash issues but this does NOT lose your coins or data. You may need to resync at the worst; this is related to a bug with RESCAN command which we will fix. I have not said this was flawless at all. People seem to think we have 1500btc and "we could have done so much better with that much money".... we have no money. Moolah has it. They will hold it til this is all right. I didn't need to send back the BTC this AM- it was the right thing to do.

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. These are being resolved now if they aren't resolved already. The team has a list of items to work on. We have additional devs helping us out for FREE at the moment because they can see the code and understand the potential here soon as these bugs are ironed out.

Our next big push will be to upgrade the codebase to the 0.9.2 bitcoin codebase as it brings many improvements (in building and testing as well). We will also port any appropriate Litecoin/Namecoin fixes into Syscoin. Despite all the FUDing today and the issues, we are still here to make this a success- there are plenty of very coherent and salient posts from other users about what happens with new innovative product launches- even from megamillion dollar companies like Microsoft (remember windows vista?). We are 6 devs with zero funding at the moment aside from what our dayjobs provide. Soon as the client is stabilized to the satisfaction of the community (our work is not done) we'll have the BTC from Moolah and can work to hire a fulltime team to move this forward in parallel with us.

I've apologized multiple times for the issues yesterday and today. The only thing we can do as a team is to rapidly improve the wallet over this week- which we will do.

Sir, just ignore some posts, they are posted by competitors of this coin, or someone want to buy this coin at a lower price even some boring guys ect.
Jump to: