From 764cd4533c55620e35a2ff57ef447f7b9955620b Mon Sep 17 00:00:00 2001 From: Hsuan Lee Date: Sat, 13 Oct 2018 13:27:14 +0800 Subject: Complete onboarding flow --- .github/ISSUE_TEMPLATE/bug-report.md | 7 +- .../ISSUE_TEMPLATE/support-request-or-question.md | 2 +- CONTRIBUTING.md | 51 -- LICENSE | 2 +- MISSION.md | 14 - README.md | 10 +- USER_AGREEMENT.md | 179 ----- app/404.html | 2 +- app/_locales/cs/messages.json | 40 +- app/_locales/de/messages.json | 38 +- app/_locales/en/messages.json | 95 ++- app/_locales/es/messages.json | 34 +- app/_locales/fr/messages.json | 18 +- app/_locales/hn/messages.json | 2 +- app/_locales/ht/messages.json | 864 ++++++++++----------- app/_locales/it/messages.json | 32 +- app/_locales/ja/messages.json | 22 +- app/_locales/ko/messages.json | 4 +- app/_locales/nl/messages.json | 28 +- app/_locales/ph/messages.json | 18 +- app/_locales/pt/messages.json | 24 +- app/_locales/ru/messages.json | 34 +- app/_locales/sl/messages.json | 28 +- app/_locales/th/messages.json | 22 +- app/_locales/tr/messages.json | 38 +- app/_locales/vi/messages.json | 16 +- app/_locales/zh_CN/messages.json | 32 +- app/_locales/zh_TW/messages.json | 41 +- app/error.html | 2 +- app/home.html | 2 +- app/images/arrow-popout.svg | 2 +- app/images/arrow-right.svg | 2 +- app/images/caret-left.svg | 2 +- app/images/caret-right.svg | 71 +- app/loading.html | 2 +- app/manifest.json | 2 +- app/notification.html | 2 +- app/phishing.html | 7 + app/popup.html | 2 +- app/scripts/README.md | 2 +- app/scripts/background.js | 51 +- app/scripts/contentscript.js | 12 +- app/scripts/controllers/blacklist.js | 6 +- app/scripts/controllers/currency.js | 4 + app/scripts/controllers/detect-tokens.js | 2 +- .../network/createMetamaskMiddleware.js | 2 +- app/scripts/controllers/network/enums.js | 4 +- app/scripts/controllers/network/network.js | 9 +- app/scripts/controllers/token-rates.js | 19 + app/scripts/controllers/transactions/README.md | 4 +- app/scripts/controllers/transactions/index.js | 6 +- app/scripts/inpage.js | 4 +- app/scripts/lib/get-first-preferred-lang-code.js | 2 +- app/scripts/lib/message-manager.js | 10 +- app/scripts/lib/migrator/index.js | 2 +- app/scripts/lib/notification-manager.js | 12 +- app/scripts/lib/personal-message-manager.js | 12 +- app/scripts/lib/resolver.js | 71 ++ app/scripts/lib/setupMetamaskMeshMetrics.js | 2 +- app/scripts/lib/typed-message-manager.js | 12 +- app/scripts/metamask-controller.js | 22 +- app/scripts/migrations/005.js | 2 +- app/scripts/migrations/006.js | 2 +- app/scripts/migrations/007.js | 2 +- app/scripts/migrations/008.js | 2 +- app/scripts/migrations/009.js | 2 +- app/scripts/migrations/010.js | 2 +- app/scripts/migrations/011.js | 2 +- app/scripts/migrations/012.js | 2 +- app/scripts/migrations/013.js | 2 +- app/scripts/migrations/014.js | 2 +- app/scripts/migrations/015.js | 2 +- app/scripts/migrations/016.js | 2 +- app/scripts/migrations/017.js | 2 +- app/scripts/migrations/018.js | 2 +- app/scripts/migrations/019.js | 2 +- app/scripts/migrations/020.js | 2 +- app/scripts/migrations/021.js | 2 +- app/scripts/migrations/022.js | 2 +- app/scripts/migrations/023.js | 2 +- app/scripts/migrations/026.js | 2 +- app/scripts/popup-core.js | 2 +- app/scripts/ui.js | 5 +- app/unsupport.html | 2 +- development/README.md | 2 +- development/announcer.js | 2 +- development/index.html | 2 +- development/mock-dev.js | 6 +- development/states/conf-tx.json | 2 +- development/states/first-time.json | 2 +- development/test.html | 2 +- development/ui-dev.js | 4 +- docs/QA_Guide.md | 4 +- docs/README.md | 2 +- docs/bumping_version.md | 4 +- docs/development-visualization.md | 2 +- docs/extension_description/en.txt | 8 +- docs/multi_vault_planning.md | 4 +- docs/porting_to_new_environment.md | 50 +- docs/publishing.md | 6 +- docs/state_dump.md | 4 +- docs/team.md | 18 +- docs/translating-guide.md | 10 +- docs/video_script.txt | 16 +- mascara/example/app/index.html | 2 +- mascara/proxy/index.html | 8 +- mascara/src/app/buy-ether-widget/index.js | 2 +- mascara/src/app/first-time/breadcrumbs.js | 2 +- mascara/src/app/first-time/buy-ether-screen.js | 4 +- mascara/src/app/first-time/confirm-seed-screen.js | 2 - .../src/app/first-time/create-password-screen.js | 4 +- .../src/app/first-time/import-account-screen.js | 2 +- mascara/src/app/first-time/index.css | 112 ++- mascara/src/app/first-time/notice-screen.js | 5 - mascara/src/app/first-time/seed-screen.js | 4 +- mascara/src/app/first-time/unique-image-screen.js | 2 - mascara/src/background.js | 12 +- mascara/src/ui.js | 4 +- notices/README.md | 2 +- notices/archive/notice_0.md | 44 +- notices/archive/notice_2.md | 6 +- notices/archive/notice_3.md | 2 +- notices/archive/notice_4.md | 4 +- old-ui/app/accounts/import/index.js | 2 +- old-ui/app/accounts/import/json.js | 2 +- old-ui/app/components/account-export.js | 2 +- old-ui/app/components/app-bar.js | 2 +- old-ui/app/components/buy-button-subview.js | 2 +- old-ui/app/components/network.js | 4 +- old-ui/app/config.js | 4 +- old-ui/app/css/index.css | 99 ++- old-ui/app/css/lib.css | 2 +- old-ui/app/first-time/init-menu.js | 4 +- old-ui/app/keychains/hd/create-vault-complete.js | 4 +- old-ui/app/new-ui-annoucement.js | 8 +- old-ui/app/unlock.js | 2 +- old-ui/example.js | 8 +- old-ui/lib/lost-accounts-notice.js | 2 +- package-lock.json | 5 + test/data/mock-state.json | 20 +- test/e2e/beta/from-import-beta-ui.spec.js | 6 +- test/e2e/beta/metamask-beta-ui.spec.js | 8 +- test/e2e/metamask.spec.js | 8 +- test/integration/lib/first-time.js | 117 +++ test/integration/mocks/badVault2.json | 2 +- test/lib/migrations/002.json | 2 +- test/lib/migrations/004.json | 2 +- .../unit/app/controllers/infura-controller-test.js | 6 +- .../app/controllers/metamask-controller-test.js | 14 +- .../unit/app/controllers/network-contoller-test.js | 4 +- .../controllers/transactions/tx-controller-test.js | 2 +- test/unit/development/sample-changelog.md | 36 +- test/unit/development/sample-manifest.json | 4 +- ui/app/app.js | 1 - ui/app/components/account-export.js | 2 +- ui/app/components/card/index.scss | 3 +- .../confirm-detail-row/index.scss | 6 +- .../confirm-page-container-summary/index.scss | 2 +- .../confirm-page-container-header/index.scss | 2 +- ui/app/components/dropdowns/components/dropdown.js | 6 +- .../dropdowns/tests/network-dropdown.test.js | 2 +- ui/app/components/export-text-container/index.scss | 2 +- .../loading-screen/loading-screen.component.js | 2 +- .../cancel-transaction-gas-fee/index.scss | 2 +- .../modals/confirm-remove-account/index.scss | 4 +- ui/app/components/modals/deposit-ether-modal.js | 13 +- ui/app/components/modals/modal.js | 11 +- ui/app/components/page-container/index.scss | 9 +- .../token-list/token-list-placeholder/index.scss | 2 +- .../components/pages/confirm-add-token/index.scss | 4 +- .../confirm-transaction-base.component.js | 3 +- .../connect-hardware/connect-screen.js | 8 +- .../pages/create-account/import-account/json.js | 8 +- ui/app/components/pages/settings/index.scss | 10 +- .../components/pages/settings/info-tab/index.scss | 14 +- .../pages/settings/info-tab/info-tab.component.js | 7 +- .../settings-tab/settings-tab.component.js | 33 +- .../settings-tab/settings-tab.container.js | 3 - ui/app/components/pages/unlock-page/index.scss | 16 +- .../pages/unlock-page/unlock-page.component.js | 12 +- ui/app/components/selected-account/index.scss | 4 +- ui/app/components/sender-to-recipient/index.scss | 4 +- ui/app/components/tabs/tab/index.scss | 2 +- .../components/text-field/text-field.component.js | 2 +- .../components/transaction-activity-log/index.scss | 15 +- .../tests/transaction-activity-log.util.test.js | 2 +- ui/app/components/transaction-breakdown/index.scss | 7 +- .../transaction-breakdown-row/index.scss | 4 +- ui/app/components/transaction-list-item/index.scss | 23 +- ui/app/css/itcss/components/account-dropdown.scss | 3 +- ui/app/css/itcss/components/buttons.scss | 4 +- ui/app/css/itcss/components/confirm.scss | 2 +- ui/app/css/itcss/components/currency-display.scss | 22 +- ui/app/css/itcss/components/editable-label.scss | 4 +- ui/app/css/itcss/components/loading-overlay.scss | 2 +- ui/app/css/itcss/components/menu.scss | 4 +- ui/app/css/itcss/components/modal.scss | 12 +- ui/app/css/itcss/components/new-account.scss | 155 +++- ui/app/css/itcss/components/newui-sections.scss | 9 +- ui/app/css/itcss/components/request-signature.scss | 2 +- ui/app/css/itcss/components/sections.scss | 3 +- ui/app/css/itcss/components/send.scss | 156 +++- ui/app/css/itcss/components/simple-dropdown.scss | 16 +- ui/app/css/itcss/components/tab-bar.scss | 4 +- ui/app/css/itcss/components/tooltip.scss | 656 +++++++++++++++- ui/app/css/itcss/components/welcome-screen.scss | 10 +- ui/app/css/itcss/generic/index.scss | 18 +- ui/app/css/itcss/settings/variables.scss | 3 +- ui/app/keychains/hd/create-vault-complete.js | 4 +- ui/app/reducers.js | 2 +- ui/app/reducers/metamask.js | 4 +- ui/app/select-app.js | 19 +- ui/app/welcome-screen.js | 8 +- ui/example.js | 8 +- ui/index.html | 2 +- ui/lib/lost-accounts-notice.js | 2 +- 216 files changed, 2542 insertions(+), 1710 deletions(-) delete mode 100644 CONTRIBUTING.md delete mode 100644 MISSION.md delete mode 100644 USER_AGREEMENT.md create mode 100644 app/scripts/lib/resolver.js create mode 100644 test/integration/lib/first-time.js diff --git a/.github/ISSUE_TEMPLATE/bug-report.md b/.github/ISSUE_TEMPLATE/bug-report.md index 69dffc7b..c7034464 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.md +++ b/.github/ISSUE_TEMPLATE/bug-report.md @@ -1,6 +1,6 @@ --- name: Bug Report -about: Using MetaMask, but it's not working as you expect? +about: Using DekuSan, but it's not working as you expect? --- @@ -29,7 +29,12 @@ If applicable, add screenshots to help explain your problem. **Browser details (please complete the following information):** - OS: [e.g. OS X, Windows] - Browser [e.g. chrome, safari] +<<<<<<< HEAD - MetaMask Version [e.g. 5.0.2] +======= + - DekuSan Version [e.g. 4.9.0] + - Old UI or New / Beta UI? +>>>>>>> Complete onboarding flow **Additional context** Add any other context about the problem here. diff --git a/.github/ISSUE_TEMPLATE/support-request-or-question.md b/.github/ISSUE_TEMPLATE/support-request-or-question.md index aeb31af2..7b20a3a0 100644 --- a/.github/ISSUE_TEMPLATE/support-request-or-question.md +++ b/.github/ISSUE_TEMPLATE/support-request-or-question.md @@ -1,6 +1,6 @@ --- name: Support Request or Question -about: Have a question about how to use MetaMask? +about: Have a question about how to use DekuSan? --- diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index 63d19c63..00000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,51 +0,0 @@ -# Welcome to MetaMask! - -If you're submitting code to MetaMask, there are some simple things we'd appreciate you doing to help us stay organized! - -### Finding the right project - -Before taking the time to code and implement something, feel free to open an issue and discuss it! There may even be an issue already open, and together we may come up with a specific strategy before you take your precious time to write code. - -There are also plenty of open issues we'd love help with. Search the [`good first issue`](https://github.com/MetaMask/metamask-extension/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) label, or head to Gitcoin and earn ETH for completing projects we've posted bounties on. - -If you're picking up a bounty or an existing issue, feel free to ask clarifying questions on the issue as you go about your work. - -### Submitting a pull request -When you're done with your project / bugfix / feature and ready to submit a PR, there are a couple guidelines we ask you to follow: - -- [ ] **Test it**: For any new programmatic functionality, we like unit tests when possible, so if you can keep your code cleanly isolated, please do add a test file to the `tests` folder. -- [ ] **Add to the CHANGELOG**: Help us keep track of all the moving pieces by adding an entry to the [`CHANGELOG.md`](https://github.com/MetaMask/metamask-extension/blob/develop/CHANGELOG.md) with a link to your PR. -- [ ] **Meet the spec**: Make sure the PR adds functionality that matches the issue you're closing. This is especially important for bounties: sometimes design or implementation details are included in the conversation, so read carefully! -- [ ] **Close the issue**: If this PR closes an open issue, add the line `Fixes #$ISSUE_NUMBER`. Ex. For closing issue 418, include the line `Fixes #418`. If it doesn't close the issue but addresses it partially, just include a reference to the issue number, like `#418`. -- [ ] **Keep it simple**: Try not to include multiple features in a single PR, and don't make extraneous changes outside the scope of your contribution. All those touched files make things harder to review ;) -- [ ] **PR against `develop`**: Submit your PR against the `develop` branch. This is where we merge new features so they get some time to receive extra testing before being pushed to `master` for production. If your PR is a hot-fix that needs to be published urgently, you may submit a PR against the `master` branch, but this PR will receive tighter scrutiny before merging. -- [ ] **Get reviewed by a core contributor**: Make sure you get a `:thumbsup`, `:+1`, or `LGTM` from a user with a `Member` badge before merging. - -And that's it! Thanks for helping out. - -### Developing inside a node_modules folder - -First make sure you are comfortable with [how require works](https://github.com/maxogden/art-of-node#how-require-works) in node. - -We recommend creating a folder somewhere manually called `node_modules`. For example in `~/code/node_modules`. Clone all of your git copies of modules that you want to work on into here, so for example: - -- `~/code/node_modules/dat` -- `~/code/node_modules/hyperdrive` - -When you run `npm install` inside of `~/code/node_modules/dat`, dat will get its own copy of `hyperdrive` (one if its dependencies) inside `~/code/node_modules/dat/node_modules`. However, if you encounter a bug in hyperdrive that you need to fix, but you want to test your fix in dat, you want dat to use your git copy of hyperdrive at `~/code/node_modules/hyperdrive` and not the npm copy of hyperdrive at `~/code/node_modules/dat/node_modules/hyperdrive`. - -How do you get dat to use the git copy of hyperdrive? Just delete the npm copy! - -``` -rm -rf ~/code/node_modules/dat/node_modules/hyperdrive -``` - -Now when you run dat, and it tries to `require('hyperdrive')` it first looks in its own `node_modules` folder at `~/code/node_modules/dat/node_modules` but doesnt find hyperdrive. So it goes up to `~/code/node_modules` and finds `hyperdrive` there and uses that one, your git copy. - -If you want to switch back to an npm copy, just run `npm install` inside `~/code/node_modules/dat/` and npm will download any missing modules into `~/code/node_modules/dat/node_modules` but wont touch anything in `~/code/node_modules`. - -This might seem a bit complicated at first, but is simple once you get the hang of it. Here are some rules to help you get started: - -- Never make any meaningful edits to code inside an "npm-managed" node_modules folder (such as `~/code/node_modules/dat/node_modules`), because when you run `npm install` inside those folders it could inadvertently delete all of your edits when installing an updated copy of a module. This has happened to me many times, so I just always use my git copy and delete the npm copy (as described above) to make edits to a module. -- You should never need to run any npm commands in terminal when at your "manually managed"" node_modules folder at `~/code/node_modules`. Never running npm commands at that folder also prevents npm from accidentally erasing your git copies of modules -- The location of your "manually managed" node_modules folder should be somewhere isolated from your normal require path. E.g. if you put it at `~/node_modules`, then when you run `npm install dat` at `~/Desktop` npm might decide to erase your git copy of dat at `~/node_modules/dat` and replace it with a copy from npm, which could make you lose work. Putting your manually managed `node_modules` folder in a sub-folder like `~/code` gets it "out of the way" and prevents accidents like that from happening. diff --git a/LICENSE b/LICENSE index bbed2e24..c69bcf94 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2018 MetaMask +Copyright (c) 2018 DEXON Foundation Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/MISSION.md b/MISSION.md deleted file mode 100644 index 9045828b..00000000 --- a/MISSION.md +++ /dev/null @@ -1,14 +0,0 @@ -# MetaMask Philosophy - -## Mission - -Making it safe and easy for the most people to use the decentralized web to the greatest degree that is empowering to them. - -## Vision - -To realize the highest goals achievable for the human race with the twin powers of peer to peer networks and cryptography. To empower users to hold and use their own keys on these new networks as securely and intelligibly as possible, enabling a new world of peer to peer agreements and economies, in hopes that we may collectively overcome the many great problems that we face together, through the power of strong cooperation. - -## Strategy - -We provide software for users to manage accounts, for sites to easily propose actions to users, and for users to coherently review actions before approving them. We build on this rapidly evolving set of protocols with the goal of empowering the most people to the greatest degree, and aspire to continuously evolve our offering to pursue that goal. - diff --git a/README.md b/README.md index 3d3decc1..3b74ea60 100644 --- a/README.md +++ b/README.md @@ -20,11 +20,11 @@ If you're a web dapp developer, we've got two types of guides for you: ### New Dapp Developers - We recommend this [Learning Solidity](https://karl.tech/learning-solidity-part-1-deploy-a-contract/) tutorial series by Karl Floersch. -- We wrote a (slightly outdated now) gentle introduction on [Developing Dapps with Truffle and MetaMask](https://medium.com/metamask/developing-ethereum-dapps-with-truffle-and-metamask-aa8ad7e363ba). +- We wrote a (slightly outdated now) gentle introduction on [Developing Dapps with Truffle and DekuSan](https://medium.com/metamask/developing-ethereum-dapps-with-truffle-and-metamask-aa8ad7e363ba). ### Current Dapp Developers -- If you have a Dapp, and you want to ensure compatibility, [here is our guide on building MetaMask-compatible Dapps](https://github.com/MetaMask/faq/blob/master/DEVELOPERS.md) +- If you have a Dapp, and you want to ensure compatibility, [here is our guide on building DekuSan-compatible Dapps](https://github.com/DekuSan/faq/blob/master/DEVELOPERS.md) ## Building locally @@ -82,14 +82,14 @@ To write tests that will be run in the browser using QUnit, add your test files - [How to add custom build to Chrome](./docs/add-to-chrome.md) - [How to add custom build to Firefox](./docs/add-to-firefox.md) - [How to develop a live-reloading UI](./docs/ui-dev-mode.md) -- [How to add a new translation to MetaMask](./docs/translating-guide.md) +- [How to add a new translation to DekuSan](./docs/translating-guide.md) - [Publishing Guide](./docs/publishing.md) -- [The MetaMask Team](./docs/team.md) +- [The DekuSan Team](./docs/team.md) - [How to develop an in-browser mocked UI](./docs/ui-mock-mode.md) - [How to live reload on local dependency changes](./docs/developing-on-deps.md) - [How to add new networks to the Provider Menu](./docs/adding-new-networks.md) - [How to manage notices that appear when the app starts up](./docs/notices.md) -- [How to port MetaMask to a new platform](./docs/porting_to_new_environment.md) +- [How to port DekuSan to a new platform](./docs/porting_to_new_environment.md) - [How to use the TREZOR emulator](./docs/trezor-emulator.md) - [How to generate a visualization of this repository's development](./docs/development-visualization.md) diff --git a/USER_AGREEMENT.md b/USER_AGREEMENT.md deleted file mode 100644 index c485edd1..00000000 --- a/USER_AGREEMENT.md +++ /dev/null @@ -1,179 +0,0 @@ -# Terms of Use # - -**THIS AGREEMENT IS SUBJECT TO BINDING ARBITRATION AND A WAIVER OF CLASS ACTION RIGHTS AS DETAILED IN SECTION 13. PLEASE READ THE AGREEMENT CAREFULLY.** - -_Our Terms of Use have been updated as of September 5, 2016_ - -## 1. Acceptance of Terms ## - -MetaMask provides a platform for managing Ethereum (or "ETH") accounts, and allowing ordinary websites to interact with the Ethereum blockchain, while keeping the user in control over what transactions they approve, through our website located at[ ](http://metamask.io)[https://metamask.io/](https://metamask.io/) and browser plugin (the "Site") — which includes text, images, audio, code and other materials (collectively, the “Content”) and all of the features, and services provided. The Site, and any other features, tools, materials, or other services offered from time to time by MetaMask are referred to here as the “Service.” Please read these Terms of Use (the “Terms” or “Terms of Use”) carefully before using the Service. By using or otherwise accessing the Services, or clicking to accept or agree to these Terms where that option is made available, you (1) accept and agree to these Terms (2) consent to the collection, use, disclosure and other handling of information as described in our Privacy Policy and (3) any additional terms, rules and conditions of participation issued by MetaMask from time to time. If you do not agree to the Terms, then you may not access or use the Content or Services. - -## 2. Modification of Terms of Use ## - -Except for Section 13, providing for binding arbitration and waiver of class action rights, MetaMask reserves the right, at its sole discretion, to modify or replace the Terms of Use at any time. The most current version of these Terms will be posted on our Site. You shall be responsible for reviewing and becoming familiar with any such modifications. Use of the Services by you after any modification to the Terms constitutes your acceptance of the Terms of Use as modified. - - - -## 3. Eligibility ## - -You hereby represent and warrant that you are fully able and competent to enter into the terms, conditions, obligations, affirmations, representations and warranties set forth in these Terms and to abide by and comply with these Terms. - -MetaMask is a global platform and by accessing the Content or Services, you are representing and warranting that, you are of the legal age of majority in your jurisdiction as is required to access such Services and Content and enter into arrangements as provided by the Service. You further represent that you are otherwise legally permitted to use the service in your jurisdiction including owning cryptographic tokens of value, and interacting with the Services or Content in any way. You further represent you are responsible for ensuring compliance with the laws of your jurisdiction and acknowledge that MetaMask is not liable for your compliance with such laws. - -## 4 Account Password and Security ## - -When setting up an account within MetaMask, you will be responsible for keeping your own account secrets, which may be a twelve-word seed phrase, an account file, or other locally stored secret information. MetaMask encrypts this information locally with a password you provide, that we never send to our servers. You agree to (a) never use the same password for MetaMask that you have ever used outside of this service; (b) keep your secret information and password confidential and do not share them with anyone else; (c) immediately notify MetaMask of any unauthorized use of your account or breach of security. MetaMask cannot and will not be liable for any loss or damage arising from your failure to comply with this section. - -## 5. Representations, Warranties, and Risks ## - -### 5.1. Warranty Disclaimer ### - -You expressly understand and agree that your use of the Service is at your sole risk. The Service (including the Service and the Content) are provided on an "AS IS" and "as available" basis, without warranties of any kind, either express or implied, including, without limitation, implied warranties of merchantability, fitness for a particular purpose or non-infringement. You acknowledge that MetaMask has no control over, and no duty to take any action regarding: which users gain access to or use the Service; what effects the Content may have on you; how you may interpret or use the Content; or what actions you may take as a result of having been exposed to the Content. You release MetaMask from all liability for you having acquired or not acquired Content through the Service. MetaMask makes no representations concerning any Content contained in or accessed through the Service, and MetaMask will not be responsible or liable for the accuracy, copyright compliance, legality or decency of material contained in or accessed through the Service. - -### 5.2 Sophistication and Risk of Cryptographic Systems ### - -By utilizing the Service or interacting with the Content or platform in any way, you represent that you understand the inherent risks associated with cryptographic systems; and warrant that you have an understanding of the usage and intricacies of native cryptographic tokens, like Ether (ETH) and Bitcoin (BTC), smart contract based tokens such as those that follow the Ethereum Token Standard (https://github.com/ethereum/EIPs/issues/20), and blockchain-based software systems. - -### 5.3 Risk of Regulatory Actions in One or More Jurisdictions ### - -MetaMask and ETH could be impacted by one or more regulatory inquiries or regulatory action, which could impede or limit the ability of MetaMask to continue to develop, or which could impede or limit your ability to access or use the Service or Ethereum blockchain. - -### 5.4 Risk of Weaknesses or Exploits in the Field of Cryptography ### - -You acknowledge and understand that Cryptography is a progressing field. Advances in code cracking or technical advances such as the development of quantum computers may present risks to cryptocurrencies and Services of Content, which could result in the theft or loss of your cryptographic tokens or property. To the extent possible, MetaMask intends to update the protocol underlying Services to account for any advances in cryptography and to incorporate additional security measures, but does not guarantee or otherwise represent full security of the system. By using the Service or accessing Content, you acknowledge these inherent risks. - -### 5.5 Volatility of Crypto Currencies ### - -You understand that Ethereum and other blockchain technologies and associated currencies or tokens are highly volatile due to many factors including but not limited to adoption, speculation, technology and security risks. You also acknowledge that the cost of transacting on such technologies is variable and may increase at any time causing impact to any activities taking place on the Ethereum blockchain. You acknowledge these risks and represent that MetaMask cannot be held liable for such fluctuations or increased costs. - -### 5.6 Application Security ### - -You acknowledge that Ethereum applications are code subject to flaws and acknowledge that you are solely responsible for evaluating any code provided by the Services or Content and the trustworthiness of any third-party websites, products, smart-contracts, or Content you access or use through the Service. You further expressly acknowledge and represent that Ethereum applications can be written maliciously or negligently, that MetaMask cannot be held liable for your interaction with such applications and that such applications may cause the loss of property or even identity. This warning and others later provided by MetaMask in no way evidence or represent an on-going duty to alert you to all of the potential risks of utilizing the Service or Content. - -## 6. Indemnity ## - -You agree to release and to indemnify, defend and hold harmless MetaMask and its parents, subsidiaries, affiliates and agencies, as well as the officers, directors, employees, shareholders and representatives of any of the foregoing entities, from and against any and all losses, liabilities, expenses, damages, costs (including attorneys’ fees and court costs) claims or actions of any kind whatsoever arising or resulting from your use of the Service, your violation of these Terms of Use, and any of your acts or omissions that implicate publicity rights, defamation or invasion of privacy. MetaMask reserves the right, at its own expense, to assume exclusive defense and control of any matter otherwise subject to indemnification by you and, in such case, you agree to cooperate with MetaMask in the defense of such matter. - -## 7. Limitation on liability ## - -YOU ACKNOWLEDGE AND AGREE THAT YOU ASSUME FULL RESPONSIBILITY FOR YOUR USE OF THE SITE AND SERVICE. YOU ACKNOWLEDGE AND AGREE THAT ANY INFORMATION YOU SEND OR RECEIVE DURING YOUR USE OF THE SITE AND SERVICE MAY NOT BE SECURE AND MAY BE INTERCEPTED OR LATER ACQUIRED BY UNAUTHORIZED PARTIES. YOU ACKNOWLEDGE AND AGREE THAT YOUR USE OF THE SITE AND SERVICE IS AT YOUR OWN RISK. RECOGNIZING SUCH, YOU UNDERSTAND AND AGREE THAT, TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, NEITHER METAMASK NOR ITS SUPPLIERS OR LICENSORS WILL BE LIABLE TO YOU FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY OR OTHER DAMAGES OF ANY KIND, INCLUDING WITHOUT LIMITATION DAMAGES FOR LOSS OF PROFITS, GOODWILL, USE, DATA OR OTHER TANGIBLE OR INTANGIBLE LOSSES OR ANY OTHER DAMAGES BASED ON CONTRACT, TORT, STRICT LIABILITY OR ANY OTHER THEORY (EVEN IF METAMASK HAD BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES), RESULTING FROM THE SITE OR SERVICE; THE USE OR THE INABILITY TO USE THE SITE OR SERVICE; UNAUTHORIZED ACCESS TO OR ALTERATION OF YOUR TRANSMISSIONS OR DATA; STATEMENTS OR CONDUCT OF ANY THIRD PARTY ON THE SITE OR SERVICE; ANY ACTIONS WE TAKE OR FAIL TO TAKE AS A RESULT OF COMMUNICATIONS YOU SEND TO US; HUMAN ERRORS; TECHNICAL MALFUNCTIONS; FAILURES, INCLUDING PUBLIC UTILITY OR TELEPHONE OUTAGES; OMISSIONS, INTERRUPTIONS, LATENCY, DELETIONS OR DEFECTS OF ANY DEVICE OR NETWORK, PROVIDERS, OR SOFTWARE (INCLUDING, BUT NOT LIMITED TO, THOSE THAT DO NOT PERMIT PARTICIPATION IN THE SERVICE); ANY INJURY OR DAMAGE TO COMPUTER EQUIPMENT; INABILITY TO FULLY ACCESS THE SITE OR SERVICE OR ANY OTHER WEBSITE; THEFT, TAMPERING, DESTRUCTION, OR UNAUTHORIZED ACCESS TO, IMAGES OR OTHER CONTENT OF ANY KIND; DATA THAT IS PROCESSED LATE OR INCORRECTLY OR IS INCOMPLETE OR LOST; TYPOGRAPHICAL, PRINTING OR OTHER ERRORS, OR ANY COMBINATION THEREOF; OR ANY OTHER MATTER RELATING TO THE SITE OR SERVICE. - -SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF CERTAIN WARRANTIES OR THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES. ACCORDINGLY, SOME OF THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. - -## 8. Our Proprietary Rights ## - -All title, ownership and intellectual property rights in and to the Service are owned by MetaMask or its licensors. You acknowledge and agree that the Service contains proprietary and confidential information that is protected by applicable intellectual property and other laws. Except as expressly authorized by MetaMask, you agree not to copy, modify, rent, lease, loan, sell, distribute, perform, display or create derivative works based on the Service, in whole or in part. MetaMask issues a license for MetaMask, found [here](https://github.com/MetaMask/metamask-plugin/blob/master/LICENSE). For information on other licenses utilized in the development of MetaMask, please see our attribution page at: [https://metamask.io/attributions.html](https://metamask.io/attributions.html) - -## 9. Links ## - -The Service provides, or third parties may provide, links to other World Wide Web or accessible sites, applications or resources. Because MetaMask has no control over such sites, applications and resources, you acknowledge and agree that MetaMask is not responsible for the availability of such external sites, applications or resources, and does not endorse and is not responsible or liable for any content, advertising, products or other materials on or available from such sites or resources. You further acknowledge and agree that MetaMask shall not be responsible or liable, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with use of or reliance on any such content, goods or services available on or through any such site or resource. - -## 10. Termination and Suspension ## - -MetaMask may terminate or suspend all or part of the Service and your MetaMask access immediately, without prior notice or liability, if you breach any of the terms or conditions of the Terms. Upon termination of your access, your right to use the Service will immediately cease. - -The following provisions of the Terms survive any termination of these Terms: INDEMNITY; WARRANTY DISCLAIMERS; LIMITATION ON LIABILITY; OUR PROPRIETARY RIGHTS; LINKS; TERMINATION; NO THIRD PARTY BENEFICIARIES; BINDING ARBITRATION AND CLASS ACTION WAIVER; GENERAL INFORMATION. - -## 11. No Third Party Beneficiaries ## - -You agree that, except as otherwise expressly provided in these Terms, there shall be no third party beneficiaries to the Terms. - -## 12. Notice and Procedure For Making Claims of Copyright Infringement ## - -If you believe that your copyright or the copyright of a person on whose behalf you are authorized to act has been infringed, please provide MetaMask’s Copyright Agent a written Notice containing the following information: - -· an electronic or physical signature of the person authorized to act on behalf of the owner of the copyright or other intellectual property interest; - -· a description of the copyrighted work or other intellectual property that you claim has been infringed; - -· a description of where the material that you claim is infringing is located on the Service; - -· your address, telephone number, and email address; - -· a statement by you that you have a good faith belief that the disputed use is not authorized by the copyright owner, its agent, or the law; - -· a statement by you, made under penalty of perjury, that the above information in your Notice is accurate and that you are the copyright or intellectual property owner or authorized to act on the copyright or intellectual property owner's behalf. - -MetaMask’s Copyright Agent can be reached at: - -Email: copyright [at] metamask [dot] io - -Mail: - -Attention: - -MetaMask Copyright ℅ ConsenSys - -49 Bogart Street - -Brooklyn, NY 11206 - -## 13. Binding Arbitration and Class Action Waiver ## - -PLEASE READ THIS SECTION CAREFULLY – IT MAY SIGNIFICANTLY AFFECT YOUR LEGAL RIGHTS, INCLUDING YOUR RIGHT TO FILE A LAWSUIT IN COURT - -### 13.1 Initial Dispute Resolution ### - -The parties shall use their best efforts to engage directly to settle any dispute, claim, question, or disagreement and engage in good faith negotiations which shall be a condition to either party initiating a lawsuit or arbitration. - -### 13.2 Binding Arbitration ### - -If the parties do not reach an agreed upon solution within a period of 30 days from the time informal dispute resolution under the Initial Dispute Resolution provision begins, then either party may initiate binding arbitration as the sole means to resolve claims, subject to the terms set forth below. Specifically, all claims arising out of or relating to these Terms (including their formation, performance and breach), the parties’ relationship with each other and/or your use of the Service shall be finally settled by binding arbitration administered by the American Arbitration Association in accordance with the provisions of its Commercial Arbitration Rules and the supplementary procedures for consumer related disputes of the American Arbitration Association (the "AAA"), excluding any rules or procedures governing or permitting class actions. - -The arbitrator, and not any federal, state or local court or agency, shall have exclusive authority to resolve all disputes arising out of or relating to the interpretation, applicability, enforceability or formation of these Terms, including, but not limited to any claim that all or any part of these Terms are void or voidable, or whether a claim is subject to arbitration. The arbitrator shall be empowered to grant whatever relief would be available in a court under law or in equity. The arbitrator’s award shall be written, and binding on the parties and may be entered as a judgment in any court of competent jurisdiction. - -The parties understand that, absent this mandatory provision, they would have the right to sue in court and have a jury trial. They further understand that, in some instances, the costs of arbitration could exceed the costs of litigation and the right to discovery may be more limited in arbitration than in court. - -### 13.3 Location ### - -Binding arbitration shall take place in New York. You agree to submit to the personal jurisdiction of any federal or state court in New York County, New York, in order to compel arbitration, to stay proceedings pending arbitration, or to confirm, modify, vacate or enter judgment on the award entered by the arbitrator. - -### 13.4 Class Action Waiver ### - -The parties further agree that any arbitration shall be conducted in their individual capacities only and not as a class action or other representative action, and the parties expressly waive their right to file a class action or seek relief on a class basis. YOU AND METAMASK AGREE THAT EACH MAY BRING CLAIMS AGAINST THE OTHER ONLY IN YOUR OR ITS INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS OR REPRESENTATIVE PROCEEDING. If any court or arbitrator determines that the class action waiver set forth in this paragraph is void or unenforceable for any reason or that an arbitration can proceed on a class basis, then the arbitration provision set forth above shall be deemed null and void in its entirety and the parties shall be deemed to have not agreed to arbitrate disputes. - -### 13.5 Exception - Litigation of Intellectual Property and Small Claims Court Claims ### - -Notwithstanding the parties' decision to resolve all disputes through arbitration, either party may bring an action in state or federal court to protect its intellectual property rights ("intellectual property rights" means patents, copyrights, moral rights, trademarks, and trade secrets, but not privacy or publicity rights). Either party may also seek relief in a small claims court for disputes or claims within the scope of that court’s jurisdiction. - -### 13.6 30-Day Right to Opt Out ### - -You have the right to opt-out and not be bound by the arbitration and class action waiver provisions set forth above by sending written notice of your decision to opt-out to the following address: MetaMask ℅ ConsenSys, 49 Bogart Street, Brooklyn NY 11206 and via email at support@metamask.io. The notice must be sent within 30 days of September 6, 2016 or your first use of the Service, whichever is later, otherwise you shall be bound to arbitrate disputes in accordance with the terms of those paragraphs. If you opt-out of these arbitration provisions, MetaMask also will not be bound by them. - -### 13.7 Changes to This Section ### - -MetaMask will provide 60-days’ notice of any changes to this section. Changes will become effective on the 60th day, and will apply prospectively only to any claims arising after the 60th day. - -For any dispute not subject to arbitration you and MetaMask agree to submit to the personal and exclusive jurisdiction of and venue in the federal and state courts located in New York, New York. You further agree to accept service of process by mail, and hereby waive any and all jurisdictional and venue defenses otherwise available. - -The Terms and the relationship between you and MetaMask shall be governed by the laws of the State of New York without regard to conflict of law provisions. - -## 14. General Information ## - -### 14.1 Entire Agreement ### - -These Terms (and any additional terms, rules and conditions of participation that MetaMask may post on the Service) constitute the entire agreement between you and MetaMask with respect to the Service and supersedes any prior agreements, oral or written, between you and MetaMask. In the event of a conflict between these Terms and the additional terms, rules and conditions of participation, the latter will prevail over the Terms to the extent of the conflict. - -### 14.2 Waiver and Severability of Terms ### - -The failure of MetaMask to exercise or enforce any right or provision of the Terms shall not constitute a waiver of such right or provision. If any provision of the Terms is found by an arbitrator or court of competent jurisdiction to be invalid, the parties nevertheless agree that the arbitrator or court should endeavor to give effect to the parties' intentions as reflected in the provision, and the other provisions of the Terms remain in full force and effect. - -### 14.3 Statute of Limitations ### - -You agree that regardless of any statute or law to the contrary, any claim or cause of action arising out of or related to the use of the Service or the Terms must be filed within one (1) year after such claim or cause of action arose or be forever barred. - -### 14.4 Section Titles ### - -The section titles in the Terms are for convenience only and have no legal or contractual effect. - -### 14.5 Communications ### - -Users with questions, complaints or claims with respect to the Service may contact us using the relevant contact information set forth above and at communications@metamask.io. - -## 15 Related Links ## - -**[Terms of Use](https://metamask.io/terms.html)** - -**[Privacy](https://metamask.io/privacy.html)** - -**[Attributions](https://metamask.io/attributions.html)** diff --git a/app/404.html b/app/404.html index 8a6df9d7..672b99ef 100644 --- a/app/404.html +++ b/app/404.html @@ -1,6 +1,6 @@ - MetaMask + DekuSan - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + diff --git a/app/loading.html b/app/loading.html index 71403a5a..f042046a 100644 --- a/app/loading.html +++ b/app/loading.html @@ -4,7 +4,7 @@ - MetaMask Loading + DekuSan Loading