Rebrand to Crypto.org

cdc-Hitesh · Mar 3, 2021 · 9690636 · 9690636
1 parent 588bb7f
commit 9690636
Show file tree

Hide file tree

Showing 11 changed files with 42 additions and 37 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -2,6 +2,10 @@
 
 All notable changes to this project will be documented in this file.
 
+## v0.0.11
+- Fix 5 vulnerabilities in dependencies
+- Rebrand to Crypto.org
+
 ## v0.0.10
 - Add support for undelegate on LegacyAmino - Ledger support
 
@@ -40,4 +44,4 @@ All notable changes to this project will be documented in this file.
 
 - This library is not production-ready, do not use in production systems.
 - Do not transfer any ERC20 tokens to addresses generated by this sample code as it can cause loss of funds.
-- Crypto.com is not liable for any potential damage, loss of data/files arising from the use of the library.
+- Crypto.org is not liable for any potential damage, loss of data/files arising from the use of the library.
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -1,7 +1,7 @@
 # Code of Conduct
 
 ## Conduct
-### Contact: chain@crypto.com
+### Contact: chain@crypto.org
 
 * We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic.
 
@@ -26,7 +26,7 @@
 ## Moderation
 These are the policies for upholding our community’s standards of conduct. If you feel that a thread needs moderation, please contact the above mentioned person.
 
-1. Remarks that violate the Crypto.com Chain standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hateful manner.)
+1. Remarks that violate the Crypto.org Chain standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hateful manner.)
 
 2. Remarks that moderators find inappropriate, whether listed in the code of conduct or not, are also not allowed.
 
@@ -42,10 +42,10 @@ These are the policies for upholding our community’s standards of conduct. If
 
 8. Moderators are held to a higher standard than other community members. If a moderator creates an inappropriate situation, they should expect less leeway than others.
 
-In the Crypto.com Chain developer community we strive to go the extra step to look out for each other. Don’t just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they’re off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely.
+In the Crypto.org Chain developer community we strive to go the extra step to look out for each other. Don’t just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they’re off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely.
 
-And if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could’ve communicated better — remember that it’s your responsibility to make your fellow Crypto.com Chain developer community members comfortable. Everyone wants to get along and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust.
+And if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could’ve communicated better — remember that it’s your responsibility to make your fellow Crypto.org Chain developer community members comfortable. Everyone wants to get along and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust.
 
-The enforcement policies listed above apply to all official Crypto.com Chain venues. For other projects adopting the Crypto.com Chain Code of Conduct, please contact the maintainers of those projects for enforcement. If you wish to use this code of conduct for your own project, consider explicitly mentioning your moderation policy or making a copy with your own moderation policy so as to avoid confusion.
+The enforcement policies listed above apply to all official Crypto.org Chain venues. For other projects adopting the Crypto.org Chain Code of Conduct, please contact the maintainers of those projects for enforcement. If you wish to use this code of conduct for your own project, consider explicitly mentioning your moderation policy or making a copy with your own moderation policy so as to avoid confusion.
 
 * Adapted from the the [Rust Code of Conduct](https://www.rust-lang.org/en-US/conduct.html), the [Node.js Policy on Trolling](http://blog.izs.me/post/30036893703/policy-on-trolling) as well as the [Contributor Covenant v1.3.0](http://contributor-covenant.org/version/1/3/0/).
diff --git a/CONTRIBUTION.md b/CONTRIBUTION.md
@@ -1,20 +1,20 @@
 # Contributing
 
-Thank you for your interest in contributing to Crypto.com Chain Node.js Library. We try to make the process of contribution easy for you. But still there are some guidelines we need you to follow.
+Thank you for your interest in contributing to Crypto.org Chain Node.js Library. We try to make the process of contribution easy for you. But still there are some guidelines we need you to follow.
 
 ## Code of Conduct
 
 All contributors are expected to follow our [Code of Conduct](./CODE_OF_CONDUCT.md).
 
 ## Feature Requests
 
-Feature requests are welcomed. You should post your request as [Github issues](https://github.com/crypto-com/chain-nodelib/issues/new) first. In an issue, please describe what your request is, the expected behaviour and how it will benefit you and/or other users.
+Feature requests are welcomed. You should post your request as [Github issues](https://github.com/crypto-com/chain-jslib/issues/new) first. In an issue, please describe what your request is, the expected behaviour and how it will benefit you and/or other users.
 
-Crypto.com Chain and its surrounding products are under active development. We may not be able to respond to your feature request issue promptly. However, you are free to submit a pull request by following the guidelines and we are happy to review it. Please check the [Working of issues](#working-on-issues) section for more details.
+Crypto.org Chain and its surrounding products are under active development. We may not be able to respond to your feature request issue promptly. However, you are free to submit a pull request by following the guidelines and we are happy to review it. Please check the [Working of issues](#working-on-issues) section for more details.
 
 ## Bug Reports
 
-Bug reports should be posted as [Github issues](https://github.com/crypto-com/chain-nodelib/issues/new). In an issue, please describe what you did, what you expected, and what happened instead.
+Bug reports should be posted as [Github issues](https://github.com/crypto-com/chain-jslib/issues/new). In an issue, please describe what you did, what you expected, and what happened instead.
 
 If you think that you have identified an issue that might compromise its users' security, please do not open a public issue on GitHub. Instead, we ask you to refer to [security policy](./SECURITY.md).
 

diff --git a/LICENSE b/LICENSE
@@ -1,3 +1,4 @@
+  Copyright 2021, CRO Protocol Labs ("Crypto.org"). 
   Copyright 2018 - 2020, Foris Limited ("Crypto.com"). 
 
    Licensed under the Apache License, Version 2.0 (the "License");

diff --git a/README.md b/README.md
@@ -1,14 +1,14 @@
-# Crypto.com Chain JS library
+# Crypto.org Chain JS library
 
 ## Warning
 
-Crypto.com Chain and this library is currently in the alpha development phase and subjects to changes. Before proceeding, please be aware of the following:
+Crypto.org Chain and this library is currently in the alpha development phase and subjects to changes. Before proceeding, please be aware of the following:
 
 - This library is not production-ready, do not use in production systems.
 
 - Do not transfer any ERC20 tokens to addresses generated by this sample code as it can cause loss of funds.
 
-- Crypto.com is not liable for any potential damage, loss of data/files arising from the use of the library.
+- Crypto.org is not liable for any potential damage, loss of data/files arising from the use of the library.
 
 ## 1. Quick Guide
 

diff --git a/SECURITY.md b/SECURITY.md
@@ -1,20 +1,20 @@
 ## Coordinated Vulnerability Disclosure Policy
-We ask security researchers to keep vulnerabilities and communications around vulnerability submissions private and confidential until a patch is developed to protect the people using Crypto.com’s protocols. In addition to this, we ask that you:
+We ask security researchers to keep vulnerabilities and communications around vulnerability submissions private and confidential until a patch is developed to protect the people using Crypto.org’s protocols. In addition to this, we ask that you:
 
 - Allow us a reasonable amount of time to correct or address security vulnerabilities.
 - Avoid exploiting any vulnerabilities that you discover.
-- Demonstrate good faith by not disrupting or degrading Crypto.com’s data or services.
+- Demonstrate good faith by not disrupting or degrading Crypto.org’s data or services.
 
 ## Vulnerability Disclosure Process
-Once we receive a vulnerability report, Crypto.com will take these steps to address it:
+Once we receive a vulnerability report, Crypto.org will take these steps to address it:
 
-1. Crypto.com will confirm receipt of the vulnerability report within 5 business days. The timing of our response may depend on when a report is submitted. As our daily operations are distributed in time zones across the globe, response times may vary. If you have not received a response to a vulnerability report from us within 5 business days, we encourage you to follow up with us again for a response.
-2. Crypto.com will investigate and validate the security issue submitted to us as quickly as we can, usually within 10 business days of receipt. Submitting a thorough report with clear steps to recreate the vulnerability and/or a proof-of-concept will move the process along in a timely manner.
-3. Crypto.com will acknowledge the bug, and make the necessary code changes to patch it. Some issues may require more time than others to patch, but we will strive to patch each vulnerability as quickly as our resources and development process allow.
-4. Crypto.com will publicly release the security patch for the vulnerability, and acknowledge the security fix in the release notes once the issue has been resolved. Public release notes can reference to the person or people who reported the vulnerability, unless they wish to stay anonymous.
+1. Crypto.org will confirm receipt of the vulnerability report within 5 business days. The timing of our response may depend on when a report is submitted. As our daily operations are distributed in time zones across the globe, response times may vary. If you have not received a response to a vulnerability report from us within 5 business days, we encourage you to follow up with us again for a response.
+2. Crypto.org will investigate and validate the security issue submitted to us as quickly as we can, usually within 10 business days of receipt. Submitting a thorough report with clear steps to recreate the vulnerability and/or a proof-of-concept will move the process along in a timely manner.
+3. Crypto.org will acknowledge the bug, and make the necessary code changes to patch it. Some issues may require more time than others to patch, but we will strive to patch each vulnerability as quickly as our resources and development process allow.
+4. Crypto.org will publicly release the security patch for the vulnerability, and acknowledge the security fix in the release notes once the issue has been resolved. Public release notes can reference to the person or people who reported the vulnerability, unless they wish to stay anonymous.
 
 ## Contact Us
-If you find a security issue, you can contact our team directly at [chain-security@crypto.com](mailto:chain-security@crypto.com).
+If you find a security issue, you can contact our team directly at [chain-security@crypto.org](mailto:chain-security@crypto.org).
 
 The following key can be used to communicate sensitive information to this email address:
 

diff --git a/docs/themes/src/default/layouts/default.hbs b/docs/themes/src/default/layouts/default.hbs
@@ -9,20 +9,20 @@
       name="viewport"
       content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0"
     />
-    <title>{{#ifCond model.name '==' project.name}}Crypto.com Chain Node.js Library {{project.name}}{{else}}{{model.name}} | Crypto.com Chain Node.js Library {{project.name}}{{/ifCond}}</title>
+    <title>{{#ifCond model.name '==' project.name}}Crypto.org Chain Node.js Library {{project.name}}{{else}}{{model.name}} | Crypto.org Chain Node.js Library {{project.name}}{{/ifCond}}</title>
     <meta name="theme-color" content="#f7f9fa" />
-    <meta name="title" content="Crypto.com Chain" />
-    <meta name="author" content="Crypto.com Chain" />
-    <meta name="publisher" content="Crypto.com Chain" />
-    <meta property="og:title" content="Crypto.com Chain" />
+    <meta name="title" content="Crypto.org Chain" />
+    <meta name="author" content="Crypto.org Chain" />
+    <meta name="publisher" content="Crypto.org Chain" />
+    <meta property="og:title" content="Crypto.org Chain" />
     <meta
       property="og:description"
-      content="Crypto.com Chain is a privacy-protecting public blockchain that empowers the future of payments in cryptocurrency. It powers the QR Code payment solution of Crypto.com Pay and drives the mass adoption of cryptocurrency worldwide. View the whitepaper and documentation via our open-sourced Github organization."
+      content="Crypto.org Chain is a public blockchain that empowers the future of payments in cryptocurrency. It powers the QR Code payment solution of Crypto.com Pay and drives the mass adoption of cryptocurrency worldwide. View the whitepaper and documentation via our open-sourced Github organization."
     />
-    <meta property="og:site_name" content="Crypto.com Chain" />
-    <meta property="og:image" content="https://chain.crypto.com/crypto-com-chain.png" />
+    <meta property="og:site_name" content="Crypto.org Chain" />
+    <meta property="og:image" content="https://chain.crypto.org/og-image.png" />
     <meta property="og:type" content="website" />
-    <meta property="og:url" content="https://chain.crypto.com" />
+    <meta property="og:url" content="https://chain.crypto.org" />
     <meta property="og:locale" content="en" />
     <link rel="icon" href="{{relativeURL "assets/images/favicon.png"}}" type="image/x-icon" />
     <link rel="stylesheet" href="{{relativeURL "assets/css/main.css"}}">

diff --git a/docs/themes/src/default/partials/footer.hbs b/docs/themes/src/default/partials/footer.hbs
@@ -14,7 +14,7 @@
     </div>
 
     <div class="copyright">
-        Copyright © 2018 - 2020 Crypto.com. All rights reserved.
+        Copyright © 2021 Crypto.org. All rights reserved.
     </div>
 </footer>
 

diff --git a/docs/themes/src/default/partials/header.hbs b/docs/themes/src/default/partials/header.hbs
@@ -3,8 +3,8 @@
         <div class="container">
             <div id="tsd-search" data-index="{{relativeURL "assets/js/search.json"}}" data-base="{{relativeURL "./"}}">
                 <a href="{{relativeURL "index.html"}}" class="title">
-                    <img src="{{relativeURL "assets/images/logo.svg"}}" alt="Crypto.com Chain" class="non-desktop-hide" />
-                    <img src="{{relativeURL "assets/images/logo-icon.svg"}}" alt="Crypto.com Chain" class="desktop-hide">
+                    <img src="{{relativeURL "assets/images/logo.svg"}}" alt="Crypto.org Chain" class="non-desktop-hide" />
+                    <img src="{{relativeURL "assets/images/logo-icon.svg"}}" alt="Crypto.org Chain" class="desktop-hide">
                 </a>
 
                 <div class="tsd-search-input">

diff --git a/lib/src/core/cro.ts b/lib/src/core/cro.ts
@@ -56,7 +56,7 @@ export const CroSDK = function (configs: InitConfigurations) {
 
 export class CroNetwork {
     public static Testnet: Network = {
-        defaultNodeUrl: 'https://testnet-croeseid.crypto.com',
+        defaultNodeUrl: 'https://testnet-croeseid.crypto.org',
         chainId: 'testnet-croeseid-2',
         addressPrefix: 'tcro',
         validatorAddressPrefix: 'tcrocncl',

diff --git a/package.json b/package.json
@@ -1,8 +1,8 @@
 {
   "name": "@crypto-com/chain-jslib",
-  "version": "0.0.10",
-  "description": "Crypto.com Chain JavaScript library",
-  "author": "Crypto.com <chain@crypto.com>",
+  "version": "0.0.11",
+  "description": "Crypto.org Chain JavaScript library",
+  "author": "Crypto.org <chain@crypto.org>",
   "license": "Apache-2.0",
   "main": "lib/dist/index.js",
   "files": [