Hey guys sorry, been lots going on internally!
What about longterm... would it be technically possible to implement some system that wipes old blockchain data, say once a year. This way keeping the wallet nice and small?
I'm not on my personal machine at the moment so I don't have the syscoin daemon handy to check the commands but I believe there is a block-height expiration on each setdata (data storage request), and that is used for expiration. Longer you want to store something for (and larger) the higher the fees. Let me double check this once I'm home (will be a few hrs).
Ok so you have already developed a thin wallet? Is there going to be focus on design factors wth a sleek wallet?
We have not
already developed a thin wallet. This is something we've discussed internally and have identified open source examples to reference in this sense so this may be easier to implement than expected. We'll still do our full due diligence as always. Miners would need to run the full wallet, but a thin wallet could be beneficial for others that aren't mining.
And final question, is the marketplace completely decentralized? And is it possible to trace funds to ip? Or is there some kind of anonymity? Sorry for all the questions im just checking what my 15btc will get me.
Marketplace is fully decentralized via the blockchain. Is it possible to trace funds to an IP? Maybe? There is no anonymity currently built into Syscoin (not that it can't be added...) but right now it is not currently implemented nor is it a high priority roadmap feature. We're looking to focus on decentralizing financial services/systems and features to support that (escrow, reputation, etc). Once we are done with those types of features we can focus on more fringe features like anon, but anon is not the core focus of Syscoin. Developers who build on top of Syscoin can of course introduce their own anon/mixing. The team may consider adding this down the line if there is a strong call for it, but Syscoin is flexible enough for devs to layer this on without it having to be "native" to Syscoin. Having native anon would quickly turn off mainstream markets to Syscoin, and those are the target demographic we're shooting for here in the long term; so gotta be careful with that.
EDIT: also, wth the trading if title deeds or certs, whats stopping people from just uploading a random word document and saying it's the certificate? The middle man is there to check if the document is legit, thats why we have brokers. Im sorry if some of these questions are already answered.
You need to be a certificate issuer to issue certs. A word document may constitute a certificate between two parties- its really up to what the issuing party will honor. If a word document is the form of contract between two parties, this would be totally valid. If you were to issue a certificate that just had a bunch of garbage in it rather than the contents expected, the receiver would contact you to resolve the issue. It wouldn't make sense for certificate issuers to issue garbage certificates, receivers would know immediately and its all trackable via the blockchain so the integrity of the certificate issuer would come into question at that point imo.
Maybe you can elaborate on this use case a bit? Imagine I'm a yacht dealership and you bought a yacht from me. You can see i've issued yacht titles to many other buyers and the format of them. Then all the sudden I issue you a cert with entirely different content. Not only would this not make sense for me as a cert issuer because I'm sending you this I'm saying
its a valid certificate from me which I honor (as a cert issuer, and certs can always be tied back to the issuer), but you as the receiver could immediately see the contents (garbage) and the discrepancy as compared to other certs... just wouldn't make sense unless the issuer
wants problems.
Again I'm not at home so I can't dig into the syscoin commands and code right now for better answers, but from memory thats the best I can do
And do we have an ETA on the escrow system?
None that we want to call out now. We just started working on this a few days ago in earnest. We have other major features which we're hardening prior to release. We're building apps and websites to help support the Syscoin ecosystem and demo its capabilities and services as well in parallel. Extremely busy.
Would be good to see some more progress tho, it seems were seeing a load of marketing and flashy design but no real code or sample wallet.
There is a video of sample certs in action on the OP. As well as a quick screengrab from the daemon showing all the commands currently completed. We were going to release a video of offers (marketplace) just using the daemon as with certs but we decided to try and build a WebUI frontend first and then demo that as it will be more meaningful to users who aren't developers and developers alike. Releasing code before we launch Syscoin wouldn't make a bunch of sense so I'm not entirely sure what you mean by that? Also called this out on an earlier page we aren't doing any "beta wallet" program as we're just way too busy getting ready for launch on August16, and managing a beta programing incurs significant overhead.
We also mentioned on an earlier page all of these features are complete in the daemon but we're working on getting them displayed all nice and pretty in the QT Wallet. We'll try to post some pics of the wallet when we get a chance as soon as we have something we're comfortable releasing in that regard. We still have 3 weeks remember and we're working on a lot of different things right now all geared towards the launch.
If I discover any of my replies need correction once I'm home and have the client/code in front of me I'll do so.
Main question: why would I buy now, if I can buy cheper on the exchange after the launch?
That is your assumption (that you can buy it cheaper on exchange after launch). You're free to wait and find out.