Bitcoin Forum
May 03, 2024, 02:28:20 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 [207] 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 ... 355 »
  Print  
Author Topic: [ANN] Syscoin - Business on the Blockchain - LAUNCHED!  (Read 490169 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic. (109 posts by 1+ user deleted.)
sannisinas
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile WWW
August 18, 2014, 07:22:25 AM
 #4121

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.

1714703300
Hero Member
*
Offline Offline

Posts: 1714703300

View Profile Personal Message (Offline)

Ignore
1714703300
Reply with quote  #2

1714703300
Report to moderator
1714703300
Hero Member
*
Offline Offline

Posts: 1714703300

View Profile Personal Message (Offline)

Ignore
1714703300
Reply with quote  #2

1714703300
Report to moderator
1714703300
Hero Member
*
Offline Offline

Posts: 1714703300

View Profile Personal Message (Offline)

Ignore
1714703300
Reply with quote  #2

1714703300
Report to moderator
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, which will follow the rules of the network no matter what miners do. Even if every miner decided to create 1000 bitcoins per block, full nodes would stick to the rules and reject those blocks.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714703300
Hero Member
*
Offline Offline

Posts: 1714703300

View Profile Personal Message (Offline)

Ignore
1714703300
Reply with quote  #2

1714703300
Report to moderator
1714703300
Hero Member
*
Offline Offline

Posts: 1714703300

View Profile Personal Message (Offline)

Ignore
1714703300
Reply with quote  #2

1714703300
Report to moderator
1714703300
Hero Member
*
Offline Offline

Posts: 1714703300

View Profile Personal Message (Offline)

Ignore
1714703300
Reply with quote  #2

1714703300
Report to moderator
aragoon
Sr. Member
****
Offline Offline

Activity: 295
Merit: 250


View Profile
August 18, 2014, 07:24:30 AM
 #4122

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
sanworld
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
August 18, 2014, 07:25:05 AM
 #4123

Is the wallet working fine guys ?
yoyotu
Member
**
Offline Offline

Activity: 61
Merit: 10


View Profile
August 18, 2014, 07:26:52 AM
 #4124


"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
Luxasd
Sr. Member
****
Offline Offline

Activity: 504
Merit: 253



View Profile
August 18, 2014, 07:29:30 AM
 #4125

Is the wallet working fine guys ?

Works fine here.
sushipooo
Member
**
Offline Offline

Activity: 84
Merit: 10


View Profile
August 18, 2014, 07:35:37 AM
 #4126


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

Cannabis Coin CANN - Smoke a <////////////>~ and start thinking positive. Join the movement ---> https://bitcointalk.org/index.php?topic=661885.0
awais3344
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250


View Profile
August 18, 2014, 07:36:35 AM
 #4127

blockchain sync stuck at 1663 blocks now

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
NEOSCOIN
  +POD Developers +Active Community - V2 Coming Soon! Live In-App Trading, Live Pool Stats - IRC - Arbitrush Anonymous System soon!! NEOSCOIN
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
t-minus
Full Member
***
Offline Offline

Activity: 210
Merit: 100


View Profile
August 18, 2014, 07:36:57 AM
 #4128

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.
t-minus
Full Member
***
Offline Offline

Activity: 210
Merit: 100


View Profile
August 18, 2014, 07:37:21 AM
 #4129

blockchain sync stuck at 1663 blocks now

ur on wrong fork man

awais3344
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250


View Profile
August 18, 2014, 07:39:08 AM
 #4130

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?

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
NEOSCOIN
  +POD Developers +Active Community - V2 Coming Soon! Live In-App Trading, Live Pool Stats - IRC - Arbitrush Anonymous System soon!! NEOSCOIN
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
t-minus
Full Member
***
Offline Offline

Activity: 210
Merit: 100


View Profile
August 18, 2014, 07:40:44 AM
 #4131

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
danosphere (OP)
Legendary
*
Offline Offline

Activity: 1036
Merit: 1001


Syscoin- Changing the way people do business.


View Profile WWW
August 18, 2014, 07:41:27 AM
 #4132


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.

Syscoin: Business on the Blockchain. - Buy and sell goods and services, send encrypted messages and more all secured by the blockchain.
Syscoin Website | Syscoin Whitepaper | Syscoin Team Price Peg
yoyotu
Member
**
Offline Offline

Activity: 61
Merit: 10


View Profile
August 18, 2014, 07:42:22 AM
 #4133


"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.
danosphere (OP)
Legendary
*
Offline Offline

Activity: 1036
Merit: 1001


Syscoin- Changing the way people do business.


View Profile WWW
August 18, 2014, 07:43:01 AM
 #4134


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.

Syscoin: Business on the Blockchain. - Buy and sell goods and services, send encrypted messages and more all secured by the blockchain.
Syscoin Website | Syscoin Whitepaper | Syscoin Team Price Peg
sushipooo
Member
**
Offline Offline

Activity: 84
Merit: 10


View Profile
August 18, 2014, 07:46:04 AM
 #4135


"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

Cannabis Coin CANN - Smoke a <////////////>~ and start thinking positive. Join the movement ---> https://bitcointalk.org/index.php?topic=661885.0
prix
Hero Member
*****
Offline Offline

Activity: 750
Merit: 511


View Profile
August 18, 2014, 07:48:46 AM
 #4136

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.
awais3344
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250


View Profile
August 18, 2014, 07:50:32 AM
 #4137

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.

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
NEOSCOIN
  +POD Developers +Active Community - V2 Coming Soon! Live In-App Trading, Live Pool Stats - IRC - Arbitrush Anonymous System soon!! NEOSCOIN
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Lordoftherigs
Sr. Member
****
Offline Offline

Activity: 313
Merit: 250


View Profile
August 18, 2014, 07:51:15 AM
 #4138

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.

Raw-H
Sr. Member
****
Offline Offline

Activity: 324
Merit: 250


View Profile
August 18, 2014, 07:52:44 AM
Last edit: August 18, 2014, 12:44:59 PM by Raw-H
 #4139

dont use
awais3344
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250


View Profile
August 18, 2014, 07:52:48 AM
 #4140

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?

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
NEOSCOIN
  +POD Developers +Active Community - V2 Coming Soon! Live In-App Trading, Live Pool Stats - IRC - Arbitrush Anonymous System soon!! NEOSCOIN
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Pages: « 1 ... 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 [207] 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 ... 355 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!