need some official nodes.
Leave it running for a while and it should sync auto.. |
|
|
|
Do we need a list of nodes? (no conf in the zip folder)
No, leave it running for a while and it should sync. Lot of old nodes out there, but they are getting rejected now. |
|
|
|
Ok, been away for a few days... the windows qt wallet downloads on OP aren't working.
Does anyone have a link for the wallet please?
In the meantime, better start learning about keypair, requested wallet.dat but received keypair. Not to worry, time to start reading.
Refresh page, links are defo working. |
|
|
|
i love how yesterday i was a fudster for saying the new wallet crashed and corrupted my wallet.dat i got error CDB() st13exception the dev had no idea what that meant and accused me of lying now i see they are looking into a fix
hahahahaha
call spayse a fudster again but first check your code
hahahahah
i still will support this if it ever does work but for now i will not say buy. i def will not point my machines as my wallet.dat got corrupted and my wallet wont load even though error CDB() is a made up joke by me
hahahaha
btw treat your supporters better
and listen when people say they found a bug
Dude we tried to help you, you just kept spamming the same thing over and over not saying what it was related to (could have been trying to build on linux for all we knew). Others posted possible solutions after we were told. Still happy to look into it |
|
|
|
......
Because you don't release crap for 1500 btc. Simple as that. Most shitcoins have a working wallet + blockchain on release. But shut your eyes and dream on.
This is not a normal altcoin blockchain. |
|
|
|
Yes, but the devs are working on it, give them time! People can give Crypti weeks and can't give SYS team couple days?
You are missing the point. Crypti dint stick a non-working wallet to everyone and then disappeared for 12hrs. Its better to delay the product than to release a non working one. I for one would have been happier if that had been the case. Would I have moaned and bitched about it? Sure. But being unable to get out of a position which I dont want (read the wallets are still not working fine) is not something I want the syscoin developer to decide. For the love of .. You really are in total and utter FUD mode.. This is the ONLY escrow I know of where the BTC was not released as soon as the coins were delivered and coin launched (As I said that I know off, could be wrong). I think its laughable that people are moaning so much over the escrow. We have been fully transparent about everything. Moolah have been fully transparent about everything. We have not gone missing at any one point for 12 hours, the amount of FUD on BCT caused us to to move to IRC to help people. We communicated this and told people that we were there answering questions. And no I am not going to reply to any further "comments" from you. We have code to fix and test. |
|
|
|
<snip> Danosphere thanks a lot for the hard work ,Can you please make a website like eBay where I can sell all my softwares in exchange of syscoin.I dont know how to sell my softwares through your wallet's market place.
Thank you
Coles  We actually have code ready for a simple marketplace using the blockchain. Lets us just get this issue sorted and we can start showing you all the good stuff. |
|
|
|
To be honest, with 1500 BTC , which is about 700k$!! i would just take money and run. Easy money, do some pretty infographics , promise much, gather IPO and run. More then enough money for every dev. team member.
Nah, we believe in this coin.. Not going anywhere. |
|
|
|
what is current block? i stuck at 2383 about hour....
Update 8/19:
The fork yesterday was not well coordinated. Some pools updated late and we now have multiple forks. We will be doing another fork to get everyone on the correct chain by adding checkpoint blocks, and adding wallet version checks to make sure those who do not upgrade are not connected to. We are contacting pools and exchanges to prepare for this now. We are also going to try and address the "wallet relaunch and hang" issue in this update.
We will fork within 12hrs - talking to pools/exchanges now.
IF YOU ARE MINING PLEASE STOP. DO NOT SEND ANY SYSCOIN AS YOU MAY BE ON THE WRONG FORK SEND AT YOUR OWN RISK. YOU WILL BE ABLE TO SEND AFTER THE NEXT UPDATE.
|
|
|
|
|
Honestly guys.. This is crypto, forks happens, we are not happy about but are doing this to get a strong and solid network.
Solid working blockschain is our number one priority
|
|
|
|
for the sake of not losing coins/time/power (also maybe it helps dev in resolving and moving forward with tech, as they should lots of effort was put into it can tell...)
have 715.1309263 SYS UNCONFIRMED
and stuck on block # 1663
last debug.log error messages says (below)
would love to continue and I have never ever lost a single coin before, got off pool immediate for now
anyone anyone ? thanks much.. it is a principle to me that matters...
2014-08-18 14:59:53 received block 181b345cc91a946d0fb1c10a3d2d82bfd76ddb43b082f8071da6c53904d6a2f9
2014-08-18 14:59:53 GetBlockvalue of Block 1664: subsidy=12800000000, fees=0, aliasSubsidy=10804512846, offerSubsidy=131343283, certSubidy=3720930, sum=12800000000.
2014-08-18 14:59:53 ERROR: ConnectBlock() : coinbase pays too much for 1664 (actual=23739577059 vs limit=12800000000)
2014-08-18 14:59:53 InvalidChainFound: invalid block=181b345cc91a946d0fb1c10a3d2d82bfd76ddb43b082f8071da6c53904d6a2f9 height=1664 log2_work=48.534054 date=2014-08-18 02:59:54
2014-08-18 14:59:53 InvalidChainFound: current best=359357a122cf49881d2b3fb37e1edcb8224c99ca4a221d1d7678b1f46ebff2e5 height=1663 log2_work=48.534017 date=2014-08-18 02:58:16
2014-08-18 14:59:53 InvalidChainFound: invalid block=181b345cc91a946d0fb1c10a3d2d82bfd76ddb43b082f8071da6c53904d6a2f9 height=1664 log2_work=48.534054 date=2014-08-18 02:59:54
2014-08-18 14:59:53 InvalidChainFound: current best=359357a122cf49881d2b3fb37e1edcb8224c99ca4a221d1d7678b1f46ebff2e5 height=1663 log2_work=48.534017 date=2014-08-18 02:58:16
2014-08-18 14:59:53 ERROR: SetBestBlock() : ConnectBlock 181b345cc91a946d0fb1c10a3d2d82bfd76ddb43b082f8071da6c53904d6a2f9 failed
2014-08-18 14:59:53 ERROR: AcceptBlock() : AddToBlockIndex failed
2014-08-18 14:59:53 ERROR: ProcessBlock() : AcceptBlock FAILED
Have you updated to latest wallet? See OP |
|
|
|
|
Its really very simple.. We need to make the network stable.. Its as simple as that..
|
|
|
|
much transparent. such pro dev team. right now we dont know wether the devs are eating a vegimite sandwich and watching a movie or fucking working on your shitcoin? be transparent, help us. the fud will come to a halt with updates! or are all your good for is a bunch of fancy videos and keychains and litecoin hats.
SYSCOIN DEVS BE TRANSPARENT, HELP US, TELL US YOUR ACTIONS, IF ANY.
You cant win.. Some tell you to not post and work on fork, some tell you to post all the time. We are working on it.. |
|
|
|
I am just wasting time here trying to get on the correct block...
Using just:
addnode=node.syscoin.me:6369
I get:
{
"version" : 80602,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 1759,
"timeoffset" : 0,
"connections" : 3,
"proxy" : "",
"difficulty" : 53.59349095,
"testnet" : false,
"cakenet" : false,
"keypoololdest" : 1408243756,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 1.00000000,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}
Are you using the latest wallet? v0.1.1 |
|
|
|
why do you people so negotive?
Agree look at when VIA forked... Markets were closed for 24 hours. Lets let the dev's fix this fork and see where things are. They will get there... +1 |
|
|
|
I have not had an issue wit the windows wallet at all over the past 12 hours. This is what worked for me.
1. Downloaded the new wallet (i used exe file)
2. Deleted all old data in the %appdata% folder (i didn't have any coins in my wallet yet so i deleted the wallet.dat file but i don't recommend that)
Works for you precisely because of that. Educate me as to why what wallet.dat file i have determines wether or not the QT will update As posted by danospehere earlier (about 20 pages ago), there is an issue with the rescan command. So once you have coins in the wallet, it just shows you an icon and doesn't start up. IF the wallet is empty it works smoothly . Not if you clean out data folder (keep wallet.dat).. Just keep the wallet open for now. |
|
|
|
I recommend you stop publishing big lists of nodes or at least using them. Most of them are outdated and propagating them will not help.
Aye, dont use those lists please.. |
|
|
|
stuck at 2135  And tried again, stuck at 1759 with addnode=67.253.247.113:8369 addnode=node.syscoin.me:6369 I'm emailing back and forth with one of the devs - the problem is that nide is pointing to the wrong block chain - he said he'd be back to me in 20 minutes - I'll post what I get as soon as it arrives. Sent you PM. |
|
|
|
Moolah @moolah_io 12m
We have reached out to the @syscoin team in light of the recent issues. A clear timeline is crucial.
Aye, we are aware and are talking to them. |
|
|
|
Any ideas when Mintpal will restart deposits? I stupidly sent my coins there yesterday and they have been stuck in limbo since (until they re-enable deposits). Once that happens I can send my coins back to my wallet as I'm still a bit wary of them being on an exchange for so long.
When network is stable. When is that? What is dev team doing and why arent they replying here, just waiting they money? They all stop responding here. Do you plan on further buy support for those who have lost confidence in you? Ehh, you do know I am on the Dev team right? So what are you doing? Making new wallets? Making sure things work? In 24 hoiurs I haven't seen ANYTHING. U screw wallet and no fix in 24 hrs? l ol Ehh new wallet and hardfork around 9-10 hours ago.. |
|
|
|
|
Show Posts
