Pages:
Author

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

hero member
Activity: 554
Merit: 500
Crypto Enthusiast
full member
Activity: 182
Merit: 100
https://www.minep.it/pool/SYS/

That's the least spammy I can make it  Undecided
newbie
Activity: 6
Merit: 0
That is strange, yesterday the new wallet worked   very well, but now i experience same problem again, it is stuck  in tray.... only me having this problem?

I have that problem sometimes, and sometimes it works fine. (I have v0.1.3)
hero member
Activity: 556
Merit: 500
That is strange, yesterday the new wallet worked   very well, but now i experience same problem again, it is stuck  in tray.... only me having this problem?

for me is exact the opposite, yesterday with version 1.2 i needed additionally the peer.dat and the node list to make it work, just downloaded the 1.3 version and deleted the app folder (wallet.dat backup!) and all is working fine without additional steps here.
sr. member
Activity: 434
Merit: 250
That is strange, yesterday the new wallet worked   very well, but now i experience same problem again, it is stuck  in tray.... only me having this problem?
full member
Activity: 196
Merit: 100
WARNING: I say "F*CK". A Lot.
Samsung and Crucial for me. Because of http://www.xtremesystems.org/forums/showthread.php?271063-SSD-Write-Endurance-25nm-Vs-34nm

Ahh, that would defo do it alright.. (Totally off syscoin topic but).. We were looking into using for SQL server in one of the places I did some work. Not a good idea with current tech lvl..

Some SSDs are better than others. I've been running highly-loaded Oracle DBs on pairs of Plextor 256GB SSDs in a Linux/MD RAID1 for over a year - no problems at all (these are automatically SMART-checked every 5 minutes).
newbie
Activity: 47
Merit: 0
Ahh, that would defo do it alright.. (Totally off syscoin topic but).. We were looking into using for SQL server in one of the places I did some work. Not a good idea with current tech lvl..

Some SSDs are better than others. I've been running highly-loaded Oracle DBs on pairs of Plextor 256GB SSDs in a Linux/MD RAID1 for over a year - no problems at all (these are automatically SMART-checked every 5 minutes).
full member
Activity: 196
Merit: 100
WARNING: I say "F*CK". A Lot.
Hope you don't mind. I copy-pasted a snippet of your post into the ticket I have at Cryptsy. I also included the direct link to your post, so they can see the entirety.

-edit-
I made a typo. Fixed.

Reg cryptsy.. Dont think they updated to latest (could be wrong).. We have contacted them about this.

If it was me I would not send coins there atm..

This would def cause and issue if they didn't upgrade. All your coins will be there once they do though. If Cryptsy (or anyone else) is having problem getting the right chain in moving from 0.1.2 to 0.1.3 (this is not a major issue there have just been small reports of this and none for the past 5hrs to my knowledge) then please follow these steps (got btc38 back on track last night):
- close Syscoin
- clear you local data dir (except for wallet.dat, and .conf - backup wallet.dat)
- clear recycle bin**
- Grab this peers.dat and add it to your Syscoin data dir -> https://dl.dropboxusercontent.com/u/25508862/peers.dat
- open Syscoin

That should get anyone having syncing issues (not many of which have been reported) back on track.

Also it was a small but important change in Syscoin 0.1.3 the minTx amount was lowered from 1.00 to 0.01 to be more friendly for mining pools which use fractional payouts for pool fees- listening to the community.

We are looking for a longer term solution to this problem related to "rogue blocks" negatively impacting the client. This is a top priority for the team, we have all of our available resources working on this but we're looking for help to expedite a solution and don't have funding yet. Because of this lifeforce pool has generously offered a 250k SYS bounty to help expedite a solution and the team is matching this for a total 500k SYS bounty for anyone who can help us resolve the "ConnectBlock:: coinbase pays too much" error in a manner that neither hangs nor terminates the client. This is roughly ~1200usd. We have a working interim solution in place but need something long term. We are putting together a thorough brief on this to provide interested developers with "what we know" of the matter and will post this shortly.
legendary
Activity: 1036
Merit: 1001
Syscoin- Changing the way people do business.
Reg cryptsy.. Dont think they updated to latest (could be wrong).. We have contacted them about this.

If it was me I would not send coins there atm..

This would def cause and issue if they didn't upgrade. All your coins will be there once they do though. If Cryptsy (or anyone else) is having problem getting the right chain in moving from 0.1.2 to 0.1.3 (this is not a major issue there have just been small reports of this and none for the past 5hrs to my knowledge) then please follow these steps (got btc38 back on track last night):
- close Syscoin
- clear you local data dir (except for wallet.dat, and .conf - backup wallet.dat)
- clear recycle bin**
- Grab this peers.dat and add it to your Syscoin data dir -> https://dl.dropboxusercontent.com/u/25508862/peers.dat
- open Syscoin

That should get anyone having syncing issues (not many of which have been reported) back on track.

Also it was a small but important change in Syscoin 0.1.3 the minTx amount was lowered from 1.00 to 0.01 to be more friendly for mining pools which use fractional payouts for pool fees- listening to the community.

We are looking for a longer term solution to this problem related to "rogue blocks" negatively impacting the client. This is a top priority for the team, we have all of our available resources working on this but we're looking for help to expedite a solution and don't have funding yet. Because of this lifeforce pool has generously offered a 250k SYS bounty to help expedite a solution and the team is matching this for a total 500k SYS bounty for anyone who can help us resolve the "ConnectBlock:: coinbase pays too much" error in a manner that neither hangs nor terminates the client. This is roughly ~1200usd. We have a working interim solution in place but need something long term. We are putting together a thorough brief on this to provide interested developers with "what we know" of the matter and will post this shortly.
full member
Activity: 196
Merit: 100
WARNING: I say "F*CK". A Lot.
Good idea, with the small send. That's what I had been doing for the past 2 days, everywhere. Every few hours, I'd halt any sizable transferring plans and send a small SYS deposit to everyplace, just to see which ones would PING.

Until I can get my local wallet a bit more solid, I can't keep doing that. My next step is to dig up and old dual core laptop and throw some XP SP3 on it, just for the SYS wallet. Maybe that will work for me.

Reg cryptsy.. Dont think they updated to latest (could be wrong).. We have contacted them about this.

If it was me I would not send coins there atm..

all good i felt somehting may be odd there due to price so sent just 3 as a test Wink
legendary
Activity: 924
Merit: 1000
Reg cryptsy.. Dont think they updated to latest (could be wrong).. We have contacted them about this.

If it was me I would not send coins there atm..

all good i felt somehting may be odd there due to price so sent just 3 as a test Wink

The problem for us is that exchanges lists us without actually contacting us..
We do ask for a proper contact person, and/or other details so we can communicate any updates and changes..
Impossible for us to manage without.
legendary
Activity: 1526
Merit: 1000
the grandpa of cryptos
Reg cryptsy.. Dont think they updated to latest (could be wrong).. We have contacted them about this.

If it was me I would not send coins there atm..

all good i felt somehting may be odd there due to price so sent just 3 as a test Wink
legendary
Activity: 924
Merit: 1000
Reg cryptsy.. Dont think they updated to latest (could be wrong).. We have contacted them about this.

If it was me I would not send coins there atm..
full member
Activity: 196
Merit: 100
WARNING: I say "F*CK". A Lot.
They tell me they have their wallet down for maintenance. I've had a quarter million SYS en-route there since 10 hours ago. When it didn't even show as Pending at the bottom of the balances page, I dropped them a ticket to look into the issue before people get hostile.

Indeed. However, you can't get SYS into Cryptsy right now. I have had a ticket in there for that very problem since about 9 hours ago.

Have you seen SYS at Cryptsy? #gonenuts

just sent coins there. why its not coming ?
newbie
Activity: 24
Merit: 0
Indeed. However, you can't get SYS into Cryptsy right now. I have had a ticket in there for that very problem since about 9 hours ago.

Have you seen SYS at Cryptsy? #gonenuts

Yeah saw that they had disabled the wallets. Are they just behind with the update or ?
legendary
Activity: 1526
Merit: 1000
the grandpa of cryptos
Indeed. However, you can't get SYS into Cryptsy right now. I have had a ticket in there for that very problem since about 9 hours ago.

Have you seen SYS at Cryptsy? #gonenuts

just sent coins there. why its not coming ?
full member
Activity: 196
Merit: 100
WARNING: I say "F*CK". A Lot.
Indeed. However, you can't get SYS into Cryptsy right now. I have had a ticket in there for that very problem since about 9 hours ago.

Have you seen SYS at Cryptsy? #gonenuts
full member
Activity: 196
Merit: 100
WARNING: I say "F*CK". A Lot.
I took it to  PM, since YES it's mostly off topic. Unless the wallet software is incompatible with SSD hardware (most extremely unlikely).

... (Totally off syscoin topic but)...
legendary
Activity: 924
Merit: 1000
I've gone beyond the norm. I was a tester for some engineers who were designing them back in the '90s.
They don't make them today like they used to back then. But, they do have about 4x the capacity of the ones we were playing with at the time.

Align them, reserve some unused space (about 20% of total capacity set aside), trim, bios correct, no indexing, etc.

What's killing them is the systems are one 22 hours a day if not all 24 hours and the continuous multithread reads and writes and erases.

My SSDs pretty much HAVE been disposable. I've destroyed over a dozen in the past 4 months. It's beginning to kinda suck.

I can relate to that! Running a 1gb ssd here also. I can't wait for the price of the ssd's to drop to the point where they are disposable.  Cool

Have you followed the norms for setting them up? Have a few myself and they run fine.
Just make sure you don't ever fill them up.

When they initially started coming out, they did kinda suck alright. (Looking at you here OCZ)

Ahh, that would defo do it alright.. (Totally off syscoin topic but).. We were looking into using for SQL server in one of the places I did some work. Not a good idea with current tech lvl..
full member
Activity: 196
Merit: 100
WARNING: I say "F*CK". A Lot.
I've gone beyond the norm. I was a tester for some engineers who were designing them back in the '90s.
They don't make them today like they used to back then. But, they do have about 4x the capacity of the ones we were playing with at the time.

Align them, reserve some unused space (about 20% of total capacity set aside), trim, bios correct, no indexing, etc.

What's killing them is the systems are on 22 hours a day if not all 24 hours and the continuous multithread reads and writes and erases.

-edit-
in addition to the built in 256MB cache, I have an external DDR5 RAM cache of 2GB, which helps with some of the wear.

My SSDs pretty much HAVE been disposable. I've destroyed over a dozen in the past 4 months. It's beginning to kinda suck.

I can relate to that! Running a 1gb ssd here also. I can't wait for the price of the ssd's to drop to the point where they are disposable.  Cool

Have you followed the norms for setting them up? Have a few myself and they run fine.
Just make sure you don't ever fill them up.

When they initially started coming out, they did kinda suck alright. (Looking at you here OCZ)
Pages:
Jump to: