Hi,
Just a suggestion. Please put clearly marked links to your source code. I had trouble finding it with a cursory look. Currently trying to compile and sync.
Thanks will get a direct link on the site
Hi there, is this for the Markets client or QT? Both are at my github. github.com/dzimbeck
The markets client (which contains all peg logic in Python) is also there in the Halo github with Bitmessage. It has a link to the obfuscated source code and so does our main site bitbay.market
This is for my project. :-
https://bitcointalksearch.org/topic/xequium-social-network-alpha-testing-now-5141975 I intend to add support for all actively used and developed coins/assets.
I see, your project looks pretty ambitious. Well if all of it is going to be open source then I can recommend how you would go about doing decentralized "servers" because we have a design for it that is pretty bullet proof. The cool thing about crypto is almost everything can be client side other than the database where data that doesn't belong on the blockchain is stored. (although it can be hashed on the blockchain at predefined intervals if you want to keep it's integrity)
Also it's probably a good idea to make everything web based(except of course your full nodes). This is something I've learned over the past 5 years of development that end users won't really appreciate what's under the hood. They just want a viable product (even when something as serious as their own security is concerned)
Is your solution similar to this:
https://zeronet.io/ ?
Another question now that Cryptopia went fucked is there any place where is possible to acquire some BAYs
without going trough this bullshit KYC procedure?
All listed markets on
https://coinmarketcap.com/currencies/bitbay/#marketsrequires KYC.
Thanks.
Hi so one way to acquire BAY is just use our markets. There is a coins for cash template and if you let people know you want to buy they can either acquire them for you or sell direct. You can even do a custom contract. That's the advantage of P2P markets is sellers and buyers. Just remember to let our community know either here or one slack about the contract.
Also the solution for the web markets is pretty simple but I haven't seen a system like it yet. Zeronet probably doesn't let data expire or is best for serving static pages. In that case github would be fine for serving pages for free.
As for the web markets and any decentralized site, my solution has a few steps.
* All major logic is run client side in javascript. Because users should validate their own transactions and verify data and prices
* Blockchain data can be verified client side on chainz and other services as well as with nodes running the site directly
* External data can be scraped from third parties like coinmarketcap
*Nodes that run markets do so voluntarily. They share the data with a master/slave system and it is not blockchain based.
*If the master node (the node that updates the database from slaves) goes offline a new one is automatically selected
*A user connecting connects to any of the nodes or several and that's OK for trivial data. Just make sure all nodes sync with master
*All user data has an expiration date, even personal data and its ALL encrypted using their private key therefore if the master node messes
with this data it will not be able to be decrypted! Nobody has access but the user
*Messages P2P is end to end encrypted again preventing tampering
*All requests and messages are signed with private key making SSL not as important and login much safer
*Messages with expiration date vary (from months to years depending on data type)
*Images can be stored on sites like IMGUR with a bundle of API keys used client side or anonymous pastebins
*Publicly shared data (such as offers) share a common decryption key and are signed by users making tampering almost impossible
*Master nodes that tamper with data will obviously be replaced by slaves who prove it was tampered (perhaps using master signature of hash)
*DDOS is stopped easily by traffic limits per node or progressive POW or "proof of time locked funds per KB" the more messages sent.
*Database size is contained by the fact that most data is trivial, users can back up data and hash it, nodes may also archive with hash
The above system lets anyone join without the concern of data issues or trust. It also allows anyone to serve the data with big servers.
It's possible that Zeronet, IPFS or even DPOS databases have a design close enough to the above but some of the things in the required specs are pretty specific. If this is designed by our team we can probably open source it and increase contributors to our github.
I've not had the time to research any alternatives but if they can do the above with a few modifications that saves us a lot of work.
If for whatever reason, any trust of nodes serving is involved a list can be periodically updated on github by reputation. Also stakers can potentially vote them in or out and even give them incentive by a stake donation so I don't see those things as issues for trivial data.
Contracts can at least have very important info backed up on chain by a hash or a small encryption of minimal critical data(for example a disposable key). If you really wanted to be fancy, use stenography to store data into images on 3rd party services
And thats it, I think the design itself is pretty simple... it just needs to be coded and I really dont want to have any of the above features missing (except perhaps a variation in how nodes group together or something)
Hopefully this makes sense.
