Problem: Crypto.org Chain is renamed to Cronos POS Chain

CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## Unreleased
+
+- [#1029](https://github.com/crypto-org-chain/chain-main/pull/1029) Rename Crypto.org Chain to Cronos POS Chain
+
 *Dec 6, 2023*
 
 ## v4.2.8
@@ -127,7 +131,7 @@ A small fix on top of `v4.0.0` and upgrade to Cosmos SDK v0.46.4.
 
 ## v4.0.0
 
-This is the release of Crypto.org Chain's `v4.0.0`. It contains following changes (when compared with `v3`):
+This is the release of Cronos POS Chain's `v4.0.0`. It contains following changes (when compared with `v3`):
 
 ## Added
 
@@ -210,29 +214,29 @@ The upgraded Cosmos SDK version contains a fix for the upgrade non-determinism i
 that was discovered during upgrade testing.
 
 *WARNING*: DO NOT upgrade to this binary yet; instructions are going to be published later
-on https://crypto.org/docs/getting-started/upgrade_guide.html .
+on https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide .
 
 *September 7, 2021*
 
 ## v3.1.1
 This version is identical to the v3.1.0, but updated the ibc-go dependency to 1.1.0.
 *WARNING*: DO NOT upgrade to this binary yet; instructions are going to be published later
-on https://crypto.org/docs/getting-started/upgrade_guide.html .
+on https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide .
 
 
 *September 2, 2021*
 
 ## v3.1.0
 This version is identical to the v3.0.1, but updated the Cosmos SDK dependency to 0.44.0 which contains a consensus-breaking security patch.
 *WARNING*: DO NOT upgrade to this binary yet; instructions are going to be published later
-on https://crypto.org/docs/getting-started/upgrade_guide.html .
+on https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide .
 
 *August 26, 2021*
 
 ## v3.0.1
 This version is identical to the v3.0.0, but updated the IBC dependency to 1.0.1 which contains a security patch.
 *WARNING*: DO NOT upgrade to this binary yet; instructions are going to be published later
-on https://crypto.org/docs/getting-started/upgrade_guide.html .
+on https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide .
 
 *August 23, 2021*
 
@@ -243,7 +247,7 @@ and breaking changes. For more details, please see the [Cosmos SDK](https://gith
 and [ibc-go](https://github.com/cosmos/ibc-go/releases/tag/v1.0.0) release notes.
 In addition to that, it also uses Tendermint v0.34.12.
 *WARNING*: DO NOT upgrade to this binary yet; instructions are going to be published later
-on https://crypto.org/docs/getting-started/upgrade_guide.html .
+on https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide .
 
 *August 6, 2021*
 
@@ -269,7 +273,7 @@ This version is based on Cosmos SDK 0.42.6 and Tendermint 0.34.11 which, among o
 ## v2.0.1
 This released version is the same as v2.0.0, but contains an upgrade-critical fix.
 NOTE that the upgrade plan name is still expected to be "v2.0.0".
-*WARNING*: please follow the upgrade instructions described here: https://crypto.org/docs/getting-started/upgrade_guide.html#the-canis-major-upgrade-guide-v1-to-v2-0-0
+*WARNING*: please follow the upgrade instructions described here: https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide#the-canis-major-upgrade-guide-v1-to-v2-0-0
 
 ### Bug Fixes
 - [552](https://github.com/crypto-org-chain/chain-main/pull/552) NFT module store initialized after upgrade
@@ -278,7 +282,7 @@ NOTE that the upgrade plan name is still expected to be "v2.0.0".
 
 ## v2.0.0
 This pre-release version contains the scope of [ADR-003](https://github.com/crypto-org-chain/chain-main/blob/master/doc/architecture/adr-003.md) for the mainnet upgrade. It also upgrades to the latest version of Tendermint (0.34.10).
-*WARNING*: please follow the upgrade instructions described here: https://crypto.org/docs/getting-started/upgrade_guide.html#the-canis-major-upgrade-guide-v1-to-v2-0-0
+*WARNING*: please follow the upgrade instructions described here: https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide#the-canis-major-upgrade-guide-v1-to-v2-0-0
 
 ### Breaking changes
 - [516](https://github.com/crypto-org-chain/chain-main/pull/516) NFT module added

CODE_OF_CONDUCT.md

@@ -1,7 +1,7 @@
 # Code of Conduct
 
 ## Conduct
-### Contact: chain@crypto.org
+### Contact: chain@cronos-pos.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.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.)
+1. Remarks that violate the Cronos POS 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.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.
+In the Cronos POS 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.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.
+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 Cronos POS 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.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.
+The enforcement policies listed above apply to all official Cronos POS Chain venues. For other projects adopting the Cronos POS 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 [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/).

CONTRIBUTING.md

@@ -1,7 +1,7 @@
 # Contributing
 
 Thank you for your interest in contributing to Chain! The goal of the chain-main repository is to develop the implementation
-of Crypto.org Chain to best power its network use cases in payments, finance and digital assets.
+of Cronos POS Chain to best power its network use cases in payments, finance and digital assets.
 Good places to start are this document and [the official documentation](https://github.com/crypto-org-chain/chain-docs). If you have any questions, feel free to ask on [Discord](https://discord.gg/pahqHz26q4).
 
 All work on the code base tries to adhere to the "Development Process" described in [The Collective Code Construction Contract (C4)](https://rfc.zeromq.org/spec/42/#24-development-process).

LICENSE

@@ -1,4 +1,5 @@
-  Copyright 2018-present Crypto.org
+  Copyright 2023-present Cronos Labs
+  Copyright 2018-2023 Crypto.org
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

NOTICE

@@ -1,5 +1,6 @@
-Crypto.org Chain
-Copyright 2018-present Crypto.org
+Cronos POS Chain
+Copyright 2023-present Cronos Labs
+Copyright 2018-2023 Crypto.org
 
 This project contains portions of code derived from the following libraries:
 

SECURITY.md

@@ -1,19 +1,19 @@
 ## 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.org’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 Cronos Labs’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.org’s data or services.
+- Demonstrate good faith by not disrupting or degrading Cronos Labs’s data or services.
 
 ## Vulnerability Disclosure Process
-Once we receive a vulnerability report, Crypto.org will take these steps to address it:
+Once we receive a vulnerability report, Cronos Labs will take these steps to address it:
 
-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.
+1. Cronos Labs 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. Cronos Labs 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. Cronos Labs 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. Cronos Labs 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 report it on the [Crypto.com HackerOne Bug Bounty Program](https://hackerone.com/crypto) or you can contact our team directly at [[email protected]](mailto:[email protected]).
+If you find a security issue, you can report it on our partner Crypto.com's bug reporting channel: [HackerOne Bug Bounty Program](https://hackerone.com/crypto) or you can contact the team directly at [[email protected]](mailto:[email protected]).
 To communicate sensitive information, you can use the latest key in the 
 [cryptocom's Keybase account](https://keybase.io/cryptocom/pgp_keys.asc) or use its [chat functionality](https://keybase.io/cryptocom/chat).

app/docs/config.json

@@ -1,7 +1,7 @@
 {
   "swagger": "2.0",
   "info": {
-    "title": "Crypto.org Chain - Legacy REST and gRPC Gateway docs",
+    "title": "Cronos POS Chain - Legacy REST and gRPC Gateway docs",
     "description": "A REST interface for state queries, legacy transactions",
     "version": "1.0.0"
   },

app/docs/swagger-ui/swagger.yaml

@@ -1,6 +1,6 @@
 swagger: '2.0'
 info:
-  title: Crypto.org Chain - Legacy REST and gRPC Gateway docs
+  title: Cronos POS Chain - Legacy REST and gRPC Gateway docs
   description: A REST interface for state queries, legacy transactions
   version: 1.0.0
 paths:

app/docs/swagger_legacy.yaml

@@ -30,7 +30,7 @@ tags:
     description: Query app version
 schemes:
   - https
-host: mainnet.crypto.org
+host: rpc.mainnet.crypto.org
 securityDefinitions:
   kms:
     type: basic

app/state.go

@@ -1,5 +1,6 @@
 // Copyright 2016 All in Bits, Inc (licensed under the Apache License, Version 2.0)
-// Modifications Copyright (c) 2021-present Crypto.org (licensed under the Apache License, Version 2.0)
+// Modifications Copyright (c) 2021-2023 Crypto.org (licensed under the Apache License, Version 2.0)
+// Modifications Copyright (c) 2023-present Cronos Labs (licensed under the Apache License, Version 2.0)
 package app
 
 import (

cmd/chain-maind/app/app.go

@@ -63,7 +63,7 @@ func NewRootCmd() (*cobra.Command, params.EncodingConfig) {
 
 	rootCmd := &cobra.Command{
 		Use:   "chain-maind",
-		Short: "Crypto.org Chain app",
+		Short: "Cronos POS Chain app",
 		PersistentPreRunE: func(cmd *cobra.Command, _ []string) error {
 			// set the default command outputs
 			cmd.SetOut(cmd.OutOrStdout())
@@ -150,9 +150,9 @@ func initRootCmd(rootCmd *cobra.Command, encodingConfig params.EncodingConfig) {
 				"bank": map[string]interface{}{
 					"denom_metadata": []interface{}{
 						map[string]interface{}{
-							"name":        "Crypto.org Chain",
+							"name":        "Cronos POS Chain",
 							"symbol":      "CRO",
-							"description": "The native token of Crypto.org Chain.",
+							"description": "The native token of Cronos POS Chain.",
 							"denom_units": []interface{}{
 								map[string]interface{}{
 									"denom":    config.BaseCoinUnit,

default.nix

@@ -84,8 +84,8 @@ buildGoApplication rec {
 
   doCheck = false;
   meta = with lib; {
-    description = "Official implementation of the Crypto.org blockchain protocol";
-    homepage = "https://crypto.org/";
+    description = "Official implementation of the Cronos POS blockchain protocol";
+    homepage = "https://cronos-pos.org/";
     license = licenses.asl20;
     mainProgram = "chain-maind" + stdenv.hostPlatform.extensions.executable;
     platforms = platforms.all;

doc/architecture/README.md

@@ -1,6 +1,6 @@
 # Architecture Decision Records (ADR)
 
-This is a location to record all high-level architecture decisions in the Crypto.org Chain implementation.
+This is a location to record all high-level architecture decisions in the Cronos POS Chain implementation.
 
 You can read more about the ADR concept in this [blog post](https://product.reverb.com/documenting-architecture-decisions-the-reverb-way-a3563bb24bd0#.78xhdix6t).
 
@@ -31,4 +31,4 @@ To suggest an ADR, please make use of the [ADR template](./adr-template.md) prov
 | [002](./adr-002.md) | Subscriptions in CosmWasm | Accepted |
 | [003](./adr-003.md) | Canis Major (1st Network Upgrade Scope of Breaking Changes) | Accepted |
 | [004](./adr-004.md) | Transition to Cosmos SDK's NFT module | Proposed |
-| [005](./adr-005.md) | Deprecate Crypto.org Chain's custom `x/supply` module | Proposed |
+| [005](./adr-005.md) | Deprecate Cronos POS Chain's custom `x/supply` module | Proposed |

doc/architecture/adr-001.md

@@ -4,12 +4,13 @@
 * 05-03-2021: Initial Draft
 * 08-03-2021: Updated Backwards-compatibility Comments
 * 26-04-2021: Added More Consequence Comments
+* 06-02-2024: Rename Crypto.org Chain to Cronos POS Chain
 
 ## Context
 
-Crypto.org Chain logic may need to be extended to support new digital asset and financial use cases
+Cronos POS Chain logic may need to be extended to support new digital asset and financial use cases
 in the near future. 
-In the initial implementation, Crypto.org Chain logic is extensible through three different mechanisms:
+In the initial implementation, Cronos POS Chain logic is extensible through three different mechanisms:
 
 1. Cryptographic commitments and multi-signatures: 
 through the existing and future (e.g. BIP-340) signature verification mechanisms, 
@@ -93,7 +94,7 @@ Accepted
 ## Consequences
 
 ### Positive
-* Any mainstream programming language can be potentially used to extend Crypto.org Chain
+* Any mainstream programming language can be potentially used to extend Cronos POS Chain
 without "hard fork" upgrades.
 * One may leverage Rust verification tooling in development (e.g. MIRAI or Creusot).
 * "WASM" as a compilation target is fairly mature and supported across the industry.