Thanks for reminding people

Development Update!

As promised Syscoin v0.1.5.1 which includes 2 important marketplace bugfixes:
* Fixes the "11" or "88" price bug
* Fixed issues that previously existed with offeraccept/offerpay. Offernew now *requires* a receive address and it can be a non-wallet address (aka a proxy address). It can also be an alias.

https://github.com/syscoin/syscoin/releases/tag/0.1.5.1

Blog post coming tomorrow with more news!!! Due to the litigation this week some of our roadmap date have shifted slightly- we'll be posting a detailed update on this as well as other news about what's going on with Syscoin and things that are on the horizon.

Very nice!! And as stated before we are working on getting 0.1.5.1 out before Monday which patches the issue that @sphericon is currently using a workaround for (cause he's sharp like that ). Unfortunately we were booked last week with legal process work which was mandatory.

We are going to have to delay Blockmarket's Beta release due to the legal roadblock we hit this Friday (and are now past and advancing to the next stage) but the work doesn't stop for us! We're still cracking on with Blockmarket, Mobile Apps, and the big thing is Syscoin Wallet V2. At the moment the next week is "clear" for us in terms of legal work distracting us from SYS development so we should be able to make up for lost time last week. We should be able to release the beta next week/end.

Blog post coming up before Monday, roadmap will be updated as well to reflect change caused by the hearing we had to prep for Friday 11/28. The bitcoins were NOT delivered per the order so we will be moving to full proceedings. Thanks again everyone for your patience and support! We appreciate every bit of it, we have real faith in digital currencies and want to see the future of them grow and not be stifled by incidents of huge losses that go unaccounted for, that's what our litigation is all about.

We have an official donation address in my signature, please don't be fooled by scammers trying to pretend they are collecting funds on our behalf! Also our legal fund it separate from the mintpaljustice.com fund but both cases speak to the same larger goal of accountability in the digital currency space.

It was a public hearing and we've been advised not to comment, so we'll let one of the many public or reporters that attended report on what they witnessed. Sorry I can't provide anything further, just abiding by the advice from counsel.

In terms of development @JohnDorien has already verified that @sphericon's marketplace works well and another member of the team (prob me) will be working on secondary validation today, once complete the bounty will be released to him (nice work!). Mobile apps ARE on the horizon, I will check in with the whole "Apple Approvals" process today.

As mentioned before- our focus this week has been the legal case, now that we're through the hearing that occurred today (the full case is still not over) we can refocus on development efforts. We did not call the hearing today so there is no way we could have known / included it in our roadmap, it was initiated by the other party.

Def not a case of bad news that needs to be edited or anything just abiding by the advice of our legal team. There were journalists present at the hearing

Pulse check is in regards to the roadmap item - just referring to an internal checkin the team did last weekend on the progress of the V2 wallet. In regards to that we are a bit behind but have the foundation almost completed. During review we realized duplicity between the libraries we were bulding for Blockmarket Beta (the library being syscoin-api) and the ability to leverage the native RPC interface. After discussion we decided to refactor the Blockmarket's SyscoinService so that it can be reused in the V2 wallet (and a variety of other projects- it is open source like all of our work). All of our projects use AngularJS on the front end so that we have maximum reusability across components and utility libraries we develop.

In regards to Blockmarket Beta this weekend (30th) we have not officially updated the roadmap yet but it is likely that this date may slip a bit due to litigation priorities taking precedence this week. In the interest of keeping investors informed we have temporarily refocused our efforts on litigation as Ryan Kennedy/Moopay LTD has filed an application to which we must respond and attend.

Make no mistake that our future remains unchanged, we are pushing forward with the roadmap; if the litigation which is due before the weekend ends up pushing the delivery dates of Blockmarket Beta a bit then we will communicate that as soon as we're sure but we will still deliver Blockmarket Beta as the next thing coming from the team in short order, and then the V2/wwwallet after that!

We have pushed some fixes related to offers/marketplace to master (price issue) but we have not rebuilt the binaries (.app and .exe)- we will have new binaries that address issues identified with offers this weekend. Big thanks to @sphericon who is currently leading the pack in terms of the bounty set out by @kamronk and the community!! I encourage everyone to try out what @sphericon has made and if it looks solid we will award him the bounty after confirming with @kamronk   and if there are bugs at the Syscoin-level, we'll fix em!

Help us! Donate to our legal fund so that we can see this thing all the way through (this is directed at the community not just you Zee), we haven't gotten much love from the community yet with the help- lets not let this guy get away. Please donate to our legal fund 17DoGVyLwWQBwmCYUn14QXQowvoAKXqBpE (BTC). ALL donations will go to the legal battle.

I think we need some community pressure on LocalBitcoins to cooperate. They are trying to withhold data from the investigation even though we have a court order and an injunction- essentially helping facilitate this theft. Get at them on twitter/facebook/email and ask them to cooperate, and provide the details (specifically all deposit addresses) for the LemonadeDev account allegedly used by Ryan to liquidate thousands of bitcoin. Disclosing deposit addresses isn't like asking for banking info, or even personal info for that matter- but they won't cooperate.


We pushed this fix to master already but we have not rebuilt the release binaries. Will try to do that this week but unfortunately some legal issues have come up that take precendence as we're not willing to let our 750btc "vanish". That can do a lot to grow this coin, and we're pursuing it aggresively. Help us out! 

Update from me too- I was trying to pass on some helpful info to @Sphericon last night but we're on pretty opposite schedules. Still going to chat him and help him out so that we can make his next release even better Syscoin Team is 100% willing and waiting to work with community to answer questions / help / get more awesome apps and websites, etc built on top of the Syscoin service infrastructure.

Please be patient- again I reiterate the software is a community Beta. Please keep in mind while the community works on a desktop marketplace app, the TEAM is working on a web-based marketplace app and translations are coming too.

I was speaking with @cryptobum on IRC about translations yesterday night. I'm guessing we'll have an IRC thread up soon if we don't already and the team will of course contribute via the SYS bounty fund! 

Love to see the community helping out, this is what we need esp when we're not able to work at full capacity until we get our funding back- we're still pushing forward! ... I was up last night with @sidhujag battling RPC CORS errors. Hate. CORS.

Other HTML/JS devs feel my pain  nothing we can't figure out; we always do!

This is the answer to your question, but I can understand how only seeing:


Can be confusing and "too complicated" for average users. This is a beta, please keep that in mind. These types of usability and experience issues can be addressed in further releases.

All you need to do is create a new text file, called "syscoin.conf" in the folder you quoted above. Follow @sphericon's instructions from there and you should be all set!

If there are people having issues completing the offer payflow (this applies to console level commands) please explicitly pass the seller address to offernew rather than omitting it (docs currently display it as optional).

If you pass an address this will workaround an error discovered which offerpay returns an error for offer created from a wallet that contains multiple receive addresses. I'm working with @sphericon to help with any other issues that devs like himself and others may run into.

We're working listening to feedback on this and if issues are discovered which block marketplace usage we will issue a patch release ASAP.  

More progress: OP pool list updated, roadmap updated (http://syscoin.org/roadmap), website pools updated as well. Expect blog post tomorrow.

Also made more progress on V2 wallet tonight. And team is donated 200k to http://www.reddit.com/r/SysCoin/comments/2mivgx/325000_sys_bounty_for_the_first_desktop/
(tx: e10e1bba9386b618808e49e405a0b90e59c375543a00c62b4609f3d330a5da61)

Total coder porn keep up the good work! There's going to be a whole lot of Syscoin goodies coming down the pike looking at what the community is working on plus the various items the team is working on- roadmap update tonight to better communicate exactly what that means

DONATIONS TOWARD BOUNTY:


^^^ Wanted to keep this at the forefront. @JohnDorien has been doing great work and we were able to get over some critical hurdles last night on the new wallet we're working on which should help keep it on-schedule for delivery. I haven't updated the roadmap yet I'll do that tonight along with posting some technical info on the wallet- it's not just improved because of the MUCH richer user experience but its also improved because we're designing it in such a way that it will auto-update both itself (GUI) and even the daemon [phase2] using Syscoin's data service. No more needing to worry about updating your wallet or if you have the latest version- it'll do that for you!  

Also things are moving positively on the legal front! We're over the major "legal hump" at this point imo which should free up more developer time to push forward with the new wallet and our other initiatives. Roadmap will be updated tonight to more clearly communicate the next steps for Syscoin, again apologies for the delay we just reviewed some of the near-term targets based on budgets and availability and have new dates for the various milestones and even some new milestones to add!

@j4ce1 thanks I saw https://github.com/syscoin/syscoin/issues/34- this is a quick issue to fix we'll release a patch-fix for this ASAP. I'm working on Syscoin'd blockmarket (https://github.com/syscoin/blockmarket) this weekend, it'll be another front end in addition to that built at syscoin.market for users to interact with Syscoin Marketplace features.

Had some legal stuff chew up time this weekend.


There were already multiple coins working on decentralized markets. Competition is a good thing. The Moolah battle is about more than just Syscoin's funds its about accountability in crypto. In that same vein its about budgeting- we planned things against a certain budget, that budget is now gone. We're working on moving the coin features forward but with no funding and and a parallel legal battle things take time. The legal costs are coming out of our pocket- funded by our dayjobs- which are not developing Syscoin.

We've been working on this for almost a year at this point. We raised funds and had a lot going for us then we got ripped off. There is a still a TON of potential in this tech and we're working to push it forward. We're doing our best given the hand we've been dealt. As has been stated before we all work fulltime jobs, the presale funding was to be used to hire developers which we were doing; once the funding "vanished", so were most the additional devs. Now its mostly back to the core team, and our limited hours until we recoup our funds from Moolah. Until then we're keeping things moving albeit at a slower pace than we'd prefer.

Openbazaar was around while we were developing SYS, and looking at BitBay I'm not really concerned; def not a rebranded SYS if you look at their website it claims the only thing ready on launch is wallets. Everything is claimed to be in development / planned - including the decentralized markets. They're working on decentralized markets and other stuff, like many other coins are doing. We've done it, we need to dress it better and that's our current focus (both for Syscoin Markets themselves and the Syscoin Wallet as a whole).

For those efforts, all devs are needed including coderboo and myself. Coding during the hours which are available after work. Much of my time after work is taken up by legal. Also remember we're working on new features which need to be designed before they are built/released, and we have a number of private repositories in which we're doing work in order to protect our ideas before they are released fully. You can already see Syscoin Assets in alpha (publicly) in our Github repo coderboo has been working on that, and there are several features already in our core app that aren't properly useable for "average joe" users- rest of the team is focused right now on usability, games, and mobile apps. The features are there at the core level!

Great work! This is like another version of the Blockmarket the team is working on- this is exactly the type of stuff we have been hoping devs would catch on and start building stuff with- great job @sphericon!

We'll have a news blog post up tonight, meant to post yesterday but got tied up in other higher priority SYS issues! The 0.1.5 client is the official wallet and we'll have a blog post up tonight with that and other news! Stay tuned!

HELL YES and great work to @JohnDorien who has put a lot of time and effort into SYYK


Going to be honest - we think the entire shipment of shirts and hats were stopped by Customs for some reason. It was shipped out of the UK but no one has received their hats or shirts, not even me What's puzzling is that it seems no one in the UK even got their swag... maybe someone who is more familiar with international mail originating from the UK can help us out but it was all sent out- we have an invoice for the physical goods as well as the shipping, and that's the last we saw of it. We did not pay for tracking on each package as that wasn't in the budget (and glad we did given the current budget situation).

We are still trying to figure out where the goods went. That stuff wasn't the most expensive but it was still a substantial amount of money to order, package, and ship. The fact that no one has received them and we have no idea where they went after being handed off to the post is very frustrating. Anyone on the boards work for the Royal Mail?

When we get our bitcoins back we'll reorder and reship if need be, right now the focus is definitely on the legal stuff and the development stuff but I did want to let people know we are aware of the situation- I've worked on this for almost a year now and I don't even have a shirt to show for it (I'm in Maryland)!   We'll get all this taken care of as soon as possible (hopefully the packages just start showing up).

Agree with you totally and I think that it might be worth discussing this type of data-entity as its entirely own new-service. It really depends how much people use it but you're familiar with the updating issue we were discussing the other day, maybe having a different service (rather than the generic "data") service that is tailored for this use case from both a design and cost perspective would be better suited? I know this is getting into details you and I were chatting about but I wanted to share that with the community to get their thoughts.

Also the encryption piece is key- I want to increase the priority of multi-sig encryption using Syscoin keys. What this means is essentially you could encrypt the data and only you could decrypt (w/ SYS keys) - or you could use multisig encryption which still has some design nuances to be worked out but it would allow you to encrypt your data so that instead of only "you" being able to decrypt it, you, Joe, and Sue could call decrypt using SYS keys via SYS multisig encryption.

And I agree with you re: Syscore (this is a port of Bitcore to Syscoin, it is a full blockchain client built using only Javascript; We've ported the core send/receive stuff into SYS but the SYS services haven't been ported into JS yet, on our list of todos).

Interested on what people think about this (storing data using data service or should there be a new service in Syscoin specifically for social data? Also priority of encryption / community demand for multisig encryption?)

Great work @JohnDorien! You know you have the full support of the team These legal beartraps may have slowed us down but have not stopped us! I've been rearranging the management load internally @SYS so that I have more time to work with people like @JohnDorien and also @sphericon (who is building a marketplace using SYS tech).

Great work!! This is what we mean (was as in the official team) when we say we don't want to build certain products ourselves because its stealing opportunities from other developers. If a need isn't filled soon enough of course we'll act to fill it (thus the work being done towards Syscoin Blockmarket) but there are so many other opportunities and potential when it comes to Syscoin tech. GREAT WORK.

And this is just the beginning  Looking forward to what's coming!

^^^ Good advice

Need to market this better and show a video that or something like that which demo's the "dark" features so people know of them and know they work- that would make this coin HUGE. Everyone I've mentioned this too doesn't eve know about it yet, we need some marketing! It sounds like we already have some solid features from what @dogedarkdev posted.