I was just going to read through this thread. I lost interest in the coin once the dev team really messed up the launch. Now I see all sorts of wallet issues? And then this guys quote above me LOL brightest of the bright. Glad I didnt bother to get involved with this coin. If the dev team cant handle a launch, its okay, but not for me.
Most useless FUD I've ever seen lol Yeah I thought the same but didn't want to reply- feck it it's Friday. Newbie account...  |
|
|
|
The mac wallet is not syncing. Please advise!
Also how do you use peer.dat file with the client?
All wallets are indeed syncing as long as you have the most recent version. You should not need to change it, just close it, clear the data (except for the wallet.dat) and restart it, if it does not work, come on #syscoin on IRC and someone should be able to help you  Well mintpal recentlly became a headache We've realized the Mac wallet DOES suffer the same issue as the Win wallet regarding loading UI elements in certain conditions. We'll have a new build up soon to address this for Mac users as well. In the interim we are working on updates to bring these back without hanging issues and in a more functional form. Working on a block explorer and richlist too just need the funding and it'll be up we got the same team that built the Cloakcoin explorer which we think is quite nice. Just as a transparency reminder- in the interest of clean information for new and current investors we will be locking this thread tomorrow afternoon and creating a new, clean thread. We will link the threads together so everyone can follow the entire story. We will also have clear guidelines for the new thread regarding posts that will be deleted immediately (large fonts, absurd colors, name calling, etc). Thanks. |
|
|
|
Syscoin is really one of those coins I dont check prices minutely. I made some money swing trading but I am holding most of my coins.
Same here; I hadn't followed Syscoin before the launch but heard that things weren't going so well and took a punt at below the ICO price (followed by a bit of churning). As a software engineer myself, it was clear to me that that the problems stemmed from lack of production-scale testing and that they'd have fixes within a few days. The coin has some excellent features and gives us hints of the DACs (distributed autonomous corporations) that are surely in our economic future. I'm going to hold for a bit. This was exactly the case. It is hard with such a small bootstrapped team to test at the scale we really learned we needed to- lesson learned. We're working hard on getting a bunch of stuff done this weekend which may lead to another release- testing is still be done on this new build so stay tuned. Also I want to stand up a simple swag shop using SysMarket on github so people can see how this can work "outside the wallet". Also the team can use the SYS earned from selling swag for development! |
|
|
|
The new Mac wallet is not syncing, any ideas, I used chrome browser.
Give this peers.dat a shot I use it since it seems to always work for me at least - https://dl.dropboxusercontent.com/u/25508862/peers.datyes as per your instructions
aliasnew "/d/GOLD.bit"
then get error code
Error Code -4 means you have insufficient funds to activate an alias. We are aware that the user experience here could be improved and will prioritize it. In function most developers will be leveraging APIs that are currently being called directly by end users to first see if an alias is available [aliasfilter/aliasscan], then call new+activate if the appropriate funds are available and the alias is also available. Developers could then earn a small fee for providing this and of course a web based (or otherwise) user experience for end users. This may have been addressed earlier...
I created an Alias on a previous version of the wallet.
After deleting all but my wallet.dat to use the new wallet my alias has disappeared.
Any way to get it back?
Thanks
Are you not seeing it in the wallet interface? If you go to console and type "aliaslist" what do you see? Should be there via console but pls let us know if not. so since people are mad [i also used to be] can devs finally use funds to raise the price?!
I think they still ahven't received any.. They're waiting on Moolah to give the Ok to give like 200BTCs.. Doubt they'll raise the price now. Free markets do as they wish. This is true, we haven't received any funds yet. Hopefully a dev or the syscoin team can get a web site up with the market place. More coins are launching their market place over next weeks using OpenBazaar. They have lower coin count, lower market cap, can get more attention to their coin when price goes up. Of course this coin is more long term and directed towards serious people and not just price chasers. So take your time and do it right but make sure you have something out soon for people to use and list things for sale.
I know for a fact there are developers working on top of the Syscoin API to build markets right now they've been in IRC asking question about the flows. We also have an 80% complete boilerplate market using angularJS+nodeJS here -> https://github.com/syscoin/sysmarket and we have a quick connector for the JSON-RPC using NodeJS here -> https://github.com/syscoin/node-syscoin to jumpstart devs. We are working on our own market as well but are focusing on some core improvement and development process guidelines first as the team is growing quickly.
In other news we have escalated the recent Windows test build to a release candidate and it is now available via the OP. It removed the interfaces for markets/aliases as they were causing issues loading for Windows only. The functionality in console is unchanged by this and this is a non-mandatory but probably helpful update. The Mac Wallet has not changed and retains market/alias tabs- haven't had any issues reports in this environment. |
|
|
|
opens very fast and reopens after closing and after a reboot...100%
 The team/SnipSnoop have wasted many hours supporting the borked one that hangs. Few more confirmations and it goes to OP! |
|
|
|
What addnodes or config file are we supposed to use with the latest wallet?
Anybody know the answer to this? The wallet should load without this but here is a peers.dat file I keep handy since it almost always works: https://dl.dropboxusercontent.com/u/25508862/peers.datI've just pulled the latest SRC from github and built. but I still get errors.
{
"version" : 80602,
"protocolversion" : 70004,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 5169,
"timeoffset" : 0,
"connections" : 28,
"proxy" : "",
"difficulty" : 0.00024414,
"testnet" : false,
"cakenet" : false,
"keypoololdest" : 1408244855,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}
Any guesses ?
Try my peers file. Clean your chain data completely and then drop in my peers and fire it back up, should be good.
We have a new windows wallet build to address the "hang" issue. Please backup your wallet before testing this out. This is still 0.1.3, we have disabled loading of offers and aliases in the QT UI for now as it was the cause of the hang (only in windows). We will reinstate these sections as soon as we can, we are still waiting for fund release. Windows 0.1.3 Wallet EXE [fixes hang issue]: https://mega.co.nz/#!zFxHiLwR!OP6xg_5zZyh1mq5KdOwXw5LDbcLp-3b23WQIrA4ra2QWill move this new wallet to OP after some more windows ppl verify. We are moving away from using "installers" as they are too invasive. |
|
|
|
i have been having same issues as most where the wallet doesnt open back up when closed...i found that if i delete the log files it works...i noticed the debug.log file that is generated has an incorrect time stamp...it is logging 1 hour behind realtime...i moved my system clock back 1 hour to match and everything works fine
Lol, you might solveed the problem for devs:) Whoa what? We'll try this- thanks. The log can get big no doubt... I wonder if that has a major impact on loading. Seems these reports only come from windows thus far. If any mac users have seen this please let us know! |
|
|
|
Adding to website now. We are working to get another WIN build that doesn't require admin priv escalation- will post it up as soon as we have it.
|
|
|
|
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. |
|
|
|
Syscoin is entirely independent from Moolah. They are our valued partner and we are working with them closely but we are autonomous.
LOL. They just control your money and the devs that know what they're doing. But you're entirely independent. Moolah does have the funds. They also have very talented developers which we will be working with moving forward as well as other valuable assets. They are one of the biggest players in the crypto space - especially outside of the US. None of the Moolah developers were involved in fixing the issues related to our launch. We coordinated very closely with an awesome pool operator who also works for Moolah but that is it. The Syscoin team handled all of these issues internally. |
|
|
|
The third instance is the miners of course. But mining profitability is garbage at the current price.
Regenerated service fees are coming back for miners, the rewards will be much higher soon (based on service usage; this isn't a fixed number). |
|
|
|
If I decide to bet 0.1 BTC that this coin won't get back to 700 satoshi this year will Moolah escrow me? I am serious about this.
Betting 5 Bitcoin on top of your 0.1 BTC. Betting 100BTC that there's one person behind most of these troll accounts. You would lose 100BTC, a lot of shaky investors that had a lot of hope in this coin, and backed by Lord-Moolah himself put a lot of faith into the investment. I thought it was a rushed/overpriced NEM so I avoided the IPO. Dodged a bullet but really feel sorry for all those that had so much faith. Good luck everyone. You guys can easily do this over at https://www.betmoose.com/bets - send it to the dev and have him act as the 'Yes' bet to incentivize him  ^^ Great idea, we have wasted a lot of time on FUD  but we should have funding here in the next day once the discussion with Moolah is complete. danosphere, snipsnoopWhy does the wallet need an administrator password for run? I hope you will fix it in the next version. Previous version of the wallet and other my wallets run successfully without requesting administrator rights. From exe: <assemblyIdentity version="2.0.2.0" processorArchitecture="X86" type="win32" name="Syscoin QT"></assemblyIdentity>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="requireAdministrator" uiAccess="false"></requestedExecutionLevel>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
Thank you- this is a good question. The win QT build was moved to QT5 in these latest builds and maybe in that transition the contributor missed something or this was added by accident. We will address this, test and reissue a binary ASAP. +1 for DEV Syscoin Moolahcoin now have future,:-):-):-)
Typo. Syscoin is entirely independent from Moolah. They are our valued partner and we are working with them closely but we are autonomous. Wanted to clarify this point as some people were saying Moolah had taken over Syscoin- this is not the case. We are discussing long term partnerships with them involving and related to the presale BTC and will issue a statement once complete. Syscoin is going to be successful and we're both committed to seeing that through. Notice: In the interest of current and future investors, we will be locking this thread in the next day or two and moving to a new thread with more clear information about Syscoin, its roadmap, team, how to get help, etc. This thread has just gotten too long. This will remain open for now until we have the new thread ready. We will backlink this thread from the new one for transparency. Thanks.Now that stuff is up and running right we want to have a clean thread. |
|
|
|
After upgrading to the new wallet which came out earlier today adressing the pool issue the wallet is crashing again, i have to restart it manually.
A Blockchain redownload did not help either.
I guess I'll drop the Pool until you guys fix your issues and can release a stable version - it just makes no sense like it is right now.
Please join #syspools FREENODE IRC. All info for pool ops is there, as well as a script to handle this situation. Thanks. |
|
|
|
|
DEV UPDATE:
- We have fixed the requires issues and pools are updating now.
- We are agreeable to Moolah's terms and will be releasing a more detailed statement later today.
- We are building the new wallets now. THEY ARE NOT YET AVAILABLE FOR DOWNLOAD.
You can pull from git master branch if you know how to build yourself. Latest version if 0.1.3, no fork required.
|
|
|
|
DEV UPDATE- At 6PM GMT, is the blockchain in a working state? DDOS attacks on the blockchain at this time will be taken in to account.
This issue was fixed last night and is being verified by Syscoin.me, so far this fix looks good. - At 6PM GMT, is the QT wallet in a functional state for the majority of users? It does not need to expose the full daemon feature set.
This is also looking good, rescan fix addresses many hanging wallet issues. - At 6PM GMT, are 3 out of 4 core services available on the main net, via the daemon?
All 4 core services are working and verified tested on the mainnet. Tested via console. - At 6PM GMT, if all 4 services are not on the main net, is the missing service available on the testnet, via the daemon?
No missing or non functional services out of the four core. - Does the wallet require a full rescan on each launch? If so, is this something that can be fixed in a timely fashion?
Appears fixed, waiting on confirmation. - Can the wallet be opened without causing data corruption on each launch? If isolated issues are being reported, what is the plan for deploying a fix?
Appears fixed, waiting on confirmation. We will post an update as soon as we have confirmation INTERNALLY at which point we'll contact pools to upgrade. And of course Moolah will independently verify all of these points.
|
|
|
|
Only 2% of premine is for dev fund. And that = 40mil. 1% is for bounties = 20mil. Total 60mil. I already mentioned the accounts were currently combined. 20mil is used for bounties over the next YEARS. No one here reads  A fix for block-lock, sendmany bug, merged-mining, and rescan/corruption issues has been put together for pool partners to test.Why have the 59 mil coins been moved? to bittrex of course. Get out of here with your clonecoin dev FUD. Ok so we were testing stuff AS PEOPLE SHOULD KNOW. And I moved my wallet as we needed to setup a staging environment locally; forgot this would change addresses. You all need to calm down. I've put the "old wallet" back up. Notice how there is no SEND on it via the block explorer. Speechless. ALL THE FUNDS ARE RIGHT HERE PEOPLE.Also many in this thread lack mathematical skills. Please do your own math before trusting their numbers. |
|
|
|
Only 2% of premine is for dev fund. And that = 40mil. 1% is for bounties = 20mil. Total 60mil. I already mentioned the accounts were currently combined. 20mil is used for bounties over the next YEARS. No one here reads A fix for block-lock, sendmany bug, merged-mining, and rescan/corruption issues has been put together for pool partners to test.Why have the 59 mil coins been moved? Nothing has moved. |
|
|
|
|
Show Posts
