diff --git a/CHANGELOG.md b/CHANGELOG.md
index e1a367286..c27e5004f 100644
--- a/CHANGELOG.md
+++ b/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,14 +214,14 @@ 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*
@@ -225,14 +229,14 @@ on https://crypto.org/docs/getting-started/upgrade_guide.html .
## 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
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index 3a9c77b53..36ea9a2b2 100644
--- a/CODE_OF_CONDUCT.md
+++ b/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/).
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index cd81765ec..b9ee9a828 100644
--- a/CONTRIBUTING.md
+++ b/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).
diff --git a/LICENSE b/LICENSE
index 26e20c933..4b3fc5951 100644
--- a/LICENSE
+++ b/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.
diff --git a/NOTICE b/NOTICE
index c8f718e89..256eb78bc 100644
--- a/NOTICE
+++ b/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:
diff --git a/SECURITY.md b/SECURITY.md
index f73f7fb4c..9b463396e 100644
--- a/SECURITY.md
+++ b/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 [chain-security@crypto.com](mailto:chain-security@crypto.com).
+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 [chain-security@crypto.com](mailto:chain-security@crypto.com).
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).
diff --git a/app/docs/config.json b/app/docs/config.json
index 8eecee10e..6f2bcc2f8 100644
--- a/app/docs/config.json
+++ b/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"
},
diff --git a/app/docs/swagger-ui/swagger.yaml b/app/docs/swagger-ui/swagger.yaml
index a8c89c63f..c01a1a5cb 100644
--- a/app/docs/swagger-ui/swagger.yaml
+++ b/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:
diff --git a/app/docs/swagger_legacy.yaml b/app/docs/swagger_legacy.yaml
index 48f5021d5..08f7f7683 100644
--- a/app/docs/swagger_legacy.yaml
+++ b/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
diff --git a/app/state.go b/app/state.go
index 38a612f23..a244198d4 100644
--- a/app/state.go
+++ b/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 (
diff --git a/cmd/chain-maind/app/app.go b/cmd/chain-maind/app/app.go
index e00587302..c005de3b8 100644
--- a/cmd/chain-maind/app/app.go
+++ b/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,
diff --git a/default.nix b/default.nix
index b2c8102c6..93b52eb3c 100644
--- a/default.nix
+++ b/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;
diff --git a/doc/architecture/README.md b/doc/architecture/README.md
index 985f72436..27854b23e 100644
--- a/doc/architecture/README.md
+++ b/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 |
diff --git a/doc/architecture/adr-001.md b/doc/architecture/adr-001.md
index 014a8a82d..6feae16c3 100644
--- a/doc/architecture/adr-001.md
+++ b/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.
diff --git a/doc/architecture/adr-003.md b/doc/architecture/adr-003.md
index 6fe2bdcd1..fa39163c1 100644
--- a/doc/architecture/adr-003.md
+++ b/doc/architecture/adr-003.md
@@ -4,10 +4,11 @@
* 28-04-2021: Initial Draft
* 29-04-2021: Clarification of Long-term Changes
* 30-04-2021: Removed the Custom Fork
+* 06-02-2024: Rename Crypto.org Chain to Cronos POS Chain
## Context
-At this time, the Crypto.org Chain network has been live for one month and three issues that require a "hardfork" (i.e. a coordinated network upgrade due to consensus state machine-related breaking changes) have been identified:
+At this time, the Cronos POS Chain network has been live for one month and three issues that require a "hardfork" (i.e. a coordinated network upgrade due to consensus state machine-related breaking changes) have been identified:
1. Due to a bug in Cosmos SDK v0.42.*, the vesting accounts are restricted to executing one action (e.g. delegation) during their vesting period and their delegations are not tracked. This bug e.g. affects the community participants of the Crossfire incentivized testnet.
@@ -63,7 +64,6 @@ Accepted
* [fix solo machine merkle prefix casting bug](https://github.com/cosmos/ibc-go/pull/122)
* [Fix solo machine handshake verification bug](https://github.com/cosmos/ibc-go/pull/120)
* [solo machine proof height fix](https://github.com/cosmos/ibc-go/pull/123)
-* [Crypto.org Chain Intergalactic Roadmap](https://blog.crypto.com/crypto-org-chain-intergalactic-roadmap/)
* [Cosmos SDK v0.43.0-alpha1 release notes](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.43.0-alpha1)
* [NFT module on the Hub](https://github.com/cosmos/cosmos-sdk/discussions/9065)
* [IRISnet NFT module spec](https://github.com/irisnet/irismod/tree/master/modules/nft/spec)
diff --git a/doc/architecture/adr-004.md b/doc/architecture/adr-004.md
index 2a2e86a31..f6611089a 100644
--- a/doc/architecture/adr-004.md
+++ b/doc/architecture/adr-004.md
@@ -4,10 +4,11 @@
- 04-11-2021: Initial Draft
- 09-03-2022: Clarification on backwards incompatibility
+* 06-02-2024: Rename Crypto.org Chain to Cronos POS Chain
## Context
-Currently, Crypto.org Chain offers support for non-fungible tokens (NFTs) using a custom NFT module in `chain-main`. The
+Currently, Cronos POS Chain offers support for non-fungible tokens (NFTs) using a custom NFT module in `chain-main`. The
current implementation of NFT module is based on [Irismod's NFT module](https://github.com/irisnet/irismod/tree/master/modules/nft).
Given that different chains are using their custom implementation of NFT module, it is very difficult to achieve
flawless interportability of NFTs across multiple chains using IBC. At the same time, there are more usecases that need
@@ -244,7 +245,7 @@ Because current implementation of NFT module specifies `denom_name` as a unique
### Deprecation Plan
-On the release of new wrapper NFT module on Crypto.org chain, all the above messages should be considered as deprecated
+On the release of new wrapper NFT module on Cronos POS chain, all the above messages should be considered as deprecated
and will be removed in approx. 3 months via an upgrade. After the upgrade, the messages specified by Cosmos SDK's NFT
module will handle all the operations.
@@ -272,7 +273,7 @@ for free (for example, IBC support, inter-module asset support using [ADR-33](ht
### Neutral
Our current implementation is very similar to Cosmos SDK's NFT module implementation and all the usecases currently
-supported by Crypto.org Chain can easily be supported using new module.
+supported by Cronos POS Chain can easily be supported using new module.
## References
diff --git a/doc/architecture/adr-005.md b/doc/architecture/adr-005.md
index 4e147f0b9..9a927c455 100644
--- a/doc/architecture/adr-005.md
+++ b/doc/architecture/adr-005.md
@@ -1,7 +1,8 @@
-# ADR 005: Deprecate Crypto.org Chain's custom `x/supply` module
+# ADR 005: Deprecate Cronos POS Chain's custom `x/supply` module
## Changelog
* 09-03-2022: Initial draft
+* 06-02-2024: Rename Crypto.org Chain to Cronos POS Chain
## Context
@@ -49,7 +50,7 @@ For the short-term, ability to calculate liquid supply will be added in explorer
1. `x/supply` module will be marked as deprecated (this can be done by adding annotation to `.proto` files
https://github.com/protocolbuffers/protobuf/issues/1734#issuecomment-662623725).
2. Once one of the above mentioned solution for getting liquid supply is implemented, `x/supply` module will be removed
- from Crypto.org Chain.
+ from Cronos POS Chain.
## Status
diff --git a/examples/testnet_genesis.json b/examples/testnet_genesis.json
index eb7267a5a..db32aff2d 100644
--- a/examples/testnet_genesis.json
+++ b/examples/testnet_genesis.json
@@ -152,7 +152,7 @@
"supply": [],
"denom_metadata": [
{
- "description": "The native token of Crypto.org app.",
+ "description": "The native token of Cronos POS Chain app.",
"denom_units": [
{
"denom": "basetcro",
diff --git a/integration_tests/hardware_wallet/Dockerfile b/integration_tests/hardware_wallet/Dockerfile
index 2dae404be..ccff358b6 100644
--- a/integration_tests/hardware_wallet/Dockerfile
+++ b/integration_tests/hardware_wallet/Dockerfile
@@ -1,5 +1,5 @@
FROM rust:latest as BUILDER
-LABEL maintainer="chain@crypto.org"
+LABEL maintainer="chain@cronos-pos.org"
RUN apt-get update && \
apt-get -y install protobuf-compiler && \
diff --git a/integration_tests/poetry.lock b/integration_tests/poetry.lock
index d506fec66..45767c73d 100644
--- a/integration_tests/poetry.lock
+++ b/integration_tests/poetry.lock
@@ -88,7 +88,7 @@ files = [
[[package]]
name = "chainlibpy"
version = "2.2.0"
-description = "Tools for Crypto.org Chain wallet management and offline transaction signing"
+description = "Tools for Cronos POS Chain wallet management and offline transaction signing"
optional = false
python-versions = ">=3.8,<4.0"
files = [
diff --git a/proto/nft/v1/genesis.proto b/proto/nft/v1/genesis.proto
index ee0750105..6cf3317cb 100644
--- a/proto/nft/v1/genesis.proto
+++ b/proto/nft/v1/genesis.proto
@@ -1,5 +1,6 @@
// Copyright (c) 2016-2021 Shanghai Bianjie AI Technology 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)
syntax = "proto3";
package chainmain.nft.v1;
diff --git a/proto/nft/v1/nft.proto b/proto/nft/v1/nft.proto
index 40cd27eba..fd4cc04d4 100644
--- a/proto/nft/v1/nft.proto
+++ b/proto/nft/v1/nft.proto
@@ -1,5 +1,6 @@
// Copyright (c) 2016-2021 Shanghai Bianjie AI Technology 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)
syntax = "proto3";
package chainmain.nft.v1;
diff --git a/proto/nft/v1/query.proto b/proto/nft/v1/query.proto
index d4d0474be..2527a7cdc 100644
--- a/proto/nft/v1/query.proto
+++ b/proto/nft/v1/query.proto
@@ -1,5 +1,6 @@
// Copyright (c) 2016-2021 Shanghai Bianjie AI Technology 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)
syntax = "proto3";
package chainmain.nft.v1;
diff --git a/proto/nft/v1/tx.proto b/proto/nft/v1/tx.proto
index bea8afde6..a0cc6b8f6 100644
--- a/proto/nft/v1/tx.proto
+++ b/proto/nft/v1/tx.proto
@@ -1,5 +1,6 @@
// Copyright (c) 2016-2021 Shanghai Bianjie AI Technology 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)
syntax = "proto3";
package chainmain.nft.v1;
diff --git a/readme.md b/readme.md
index d7eb90bf4..b11593d21 100644
--- a/readme.md
+++ b/readme.md
@@ -1,13 +1,13 @@
- +