[Content] Legal requirement and Terms of Use for Gateways/Bridges listed on bitshares.org (wallet.bitshares.org)

[dls-cipher]

Introduction: As we all agreed that BitShares Blockchain is the open-source platform for business/financial development, as legal representatives of bitshares.org (Move Institute and partially BitShares Blockchain Foundation through worker and legislation behind technology) we are also responsible for any product and its services hosted with bitshares.org and any of its sub-domains.

Legal: BitShares as a blockchain has one protocol that powers it and its called BTS utility token. Through computation we've created smart-contracts hard-coded to the blockchain itself and defined as SmartAssets that are being borrowed to existence using 180% (now even less) Collateral of BTS utility token. Move Institute is accepting legal responsibility for technology as it is at its core.

Issue: We have something called UIA that most of the 3rd parties, even business utilize. Without proper transparency on their liquidity on gateways that are not trustless by all means, we can't take any responsibility in legal terms for any of gateway operators and their assets (example of CEX transparency that is approved by Ministry of Finance in Thailand looks like this). As the crypto is growing, banks are building on blockchain technologies (SCB is utilizing overseas payment through RIpple in Thailand, next month adding XRP to the eBanking app and enables trading), automobile industry is integrating wallets into the car navigations, and more and more mass-adoption we can see - it's very clear that opportunity for scams/illegal activities is rising. Seen it through entire industry, not just Graphene.

Solution:

• [Create] Document for terms of use/disclaimer for wallet.bitshares.org when accessing deposit/withdrawal section. Terms of Use have to be very specific and clear what bitshares.org takes responsibility on (as mentioned above) and what is strictly responsibility of 3rd parties, and that user is accepting our terms and agree we don't take responsibility for actions of such 3rd parties, rather those parties themselves.
• [Request] Each gateway/3rd party operator that is legit will submit basic business registration details and UIA's that wants publicly listed on wallet.bitshares.org (main tabs, search will not be excluded for any asset)
• [Create] Privacy policy for wallet.bitshares.org and bitshares.org which will in details explain both legal and technology perspective on users privacy, data and what we do "collect" as part of GDPR law that is actually working and helping legitimate products/brands to protect their intellectual property.

Benefits for Gateways: Each gateway that help this movement be accepted and created as a standard will have full support, listing and project description on all bitshares.org media/info products (main website, news website, ad affiliates, etc.)

DISCLAIMER: This is not affecting anyone rather than gateways listed under deposit/withdrawal sections of wallet.bitshares.org. Whoever accept the terms will remain listed and help us spread some proper reputation for BItShares or will be removed from any domain/mention through bitshares.org for legal reasons. At the end of the day, blockchain has very small return in fees comparing to 3rd parties that are utilizing it. At least, all 3rd parties can continue just doing it in a way that cannot harm BitShares brand or reputation in the future.

There will be no KYC on endusers/named accounts.

Chee®s

[sschiessl-bcp]

What do I do with that assignment? Am 10. Juni 2019 10:18:33 schrieb "Digital (Cipher) Lucifer" <notifications@github.com>:

…

Assigned #89 to @sschiessl-bcp. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.

[dls-cipher]

@sschiessl-bcp currently nothing. As soon as @rsswlkr upload a draft, your review/input would be appreciated.

Also, for you to know and inform new gateways that TOA and some basic requirements are coming - who are being processed for listing on wallet.bitshares.org

[cloud-8]

I dont see how this is relevant to Bitshares. bitshares.org is a private domain owned by a private company, you can do what you want on that domain that is an internal decision by your company. The Bitshares protocol, this repo, bitshares-core and bitshares-UI are decentralised projects and this is not a relevant task.

[sschiessl-bcp]

I dont see how this is relevant to Bitshares. bitshares.org is a private domain owned by a private company, you can do what you want on that domain that is an internal decision by your company. The Bitshares protocol, this repo, bitshares-core and bitshares-UI are decentralised projects and this is not a relevant task.

Ultimately yes, bitshares.org owner can do what he wants. Nevertheless, it is governed by a worker, hosts the reference UI and this issue is in scope of it and I very much prefer public communication on the issue.

[cloud-8]

Ultimately yes, bitshares.org owner can do what he wants. Nevertheless, it is governed by a worker, hosts the reference UI and this issue is in scope of it and I very much prefer public communication on the issue.

Lots of workers have been executed by private companies in the past but just because that is true doesnt mean Bitshares has had jurisdiction over what those private companies post on their website.

[sschiessl-bcp]

No one said that bitshares.org will be dictated to do anything. At the moment it is a goodwill effort for the benefit of the community. What exactly bothers you?

[dls-cipher]

No one said that bitshares.org will be dictated to do anything. At the moment it is a goodwill effort for the benefit of the community. What exactly bothers you?

Point where he will be asked for legal paperwork and compliance with Terms of Use if he wants to get listed/supported by bitshares.org and his products (UI, Community UI, etc...) - that probably bother anyone with this attitude.

Also, what bothers him is the fact that Laws exists and decentralized doesn't mean Lawless by any means. So, bitshares.org and its products will be protected (not bear responsibility) for any dodgy business around. Legit ones will have no issues with this, and thats it.

Again,

Look up laws on domain ownership, responsibility by laws or please, hire a lawyer to educate you, before someone hire one to look you up and educate you from the other side of the table.

e.g. OpenLedger did full compliant with new DEX and website, with all proper privacy terms and agreements of use, which is very normal for ANY online business to have, especially financial platforms such as BitShares/businesses on top of it.

We're not centralizing here anything. bitshares.org has been giving access to it across ecosystem from the day one. Our interest here is to protect ourselves, OUR BTS Holders and our tech from regulations and authorities in the future. Any business who opposes that - is just chasing personal interest and nothing more, in my humble personal opinion.

BitShares was not built as anti-government project and please - DECENTRALIZED DOESN'T MEAN LAWLESS. It's just a term as description for the way it works, in decentralized way,

Chee®s