Test

CHANGELOG.md

@@ -1,7 +1,51 @@
+# Changelog
+
+Latest releases appear first. 
+
+## 2.3.0
+
+## What's Changed
+* feat: add alliance by @javiersuweijie in https://github.com/terra-money/core/pull/108
+* fix: ci on cosmossdk 46 by @emidev98 in https://github.com/terra-money/core/pull/111
+* feat: add cosmwasm_1_1 by @javiersuweijie in https://github.com/terra-money/core/pull/112
+* tests: added chain simulation by @javiersuweijie in https://github.com/terra-money/core/pull/113
+* fix: swagger gen by @emidev98 in https://github.com/terra-money/core/pull/116
+
+## New Contributors
+* @javiersuweijie made their first contribution in https://github.com/terra-money/core/pull/108
+
+## Chain Upgrade Details
+* Blockheight: 4711800
+* Estimated time of upgrade: 2023-04-20 5:00:00 GMT+0
+
+**Full Changelog**: https://github.com/terra-money/core/compare/v2.2.1...v2.3.0
+
+## 2.2.1
+
+**Full Changelog**: https://github.com/terra-money/core/compare/v2.1.4...v2.2.0
+
+## What's Changed
+* upgrade to cosmos-sdk v0.45.12 by @faddat in https://github.com/terra-money/core/pull/102
+
+## New Contributors
+* @faddat made their first contribution in https://github.com/terra-money/core/pull/102
+
+**Full Changelog**: https://github.com/terra-money/core/compare/v2.2.0...v2.2.1
+
+## 2.2.0
+
+### What's Changed
+* Update readme.md by @svv28 in https://github.com/terra-money/core/pull/85
+* Bump SDK and IBC  by @YunSuk-Yeo in https://github.com/terra-money/core/pull/87
+
+### New Contributors
+* @svv28 made their first contribution in https://github.com/terra-money/core/pull/85
+
 ## 2.1.0
 
 ### Improvements
 - [#52](https://github.com/terra-money/core/pull/52) Enable `PeriodicVestingAccount` creation via tx ([1](https://github.com/terra-money/cosmos-sdk/compare/v0.45.4-terra.1...terra-money:v0.45.4-terra.2)) and Implement vesting token donation feature ([2](https://github.com/terra-money/cosmos-sdk/pull/88)).
 
 ### Bug Fixes
 - [#60](https://github.com/terra-money/core/pull/60) Software Upgrade Proposal to correct an exchange vesting schedule.
+

Dockerfile

@@ -34,7 +34,8 @@ RUN set -eux &&\
 # install mimalloc for musl
 WORKDIR ${GOPATH}/src/mimalloc
 RUN set -eux &&\
-    git clone --depth 1 https://github.com/microsoft/mimalloc . &&\
+    git clone --depth 1 --branch v2.0.9 \
+        https://github.com/microsoft/mimalloc . &&\
     mkdir -p build &&\
     cd build &&\
     cmake .. &&\
@@ -56,10 +57,12 @@ RUN set -eux &&\
     wget ${WASMVM_DOWNLOADS}/checksums.txt -O /tmp/checksums.txt; \
     if [ ${BUILDPLATFORM} = "linux/amd64" ]; then \
         WASMVM_URL="${WASMVM_DOWNLOADS}/libwasmvm_muslc.x86_64.a"; \
-    # elif [ ${GOOS} = "darwin" ] -a [ ${GOARCH} = "arm64" ]; then \
-    #     WASMVM_URL="${WASMVM_DOWNLOADS}/libwasmvm.dylib"; \        
     elif [ ${BUILDPLATFORM} = "linux/arm64" ]; then \
         WASMVM_URL="${WASMVM_DOWNLOADS}/libwasmvm_muslc.aarch64.a"; \
+    # elif [ ${BUILDPLATFORM} = "darwin/amd64" ]; then \
+    #     WASMVM_URL="${WASMVM_DOWNLOADS}/libwasmvm.dylib"; \        
+    # elif [ ${BUILDPLATFORM} = "darwin/arm64" ]; then \
+    #     WASMVM_URL="${WASMVM_DOWNLOADS}/libwasmvm.dylib"; \        
     else \
         echo "Unsupported Build Platfrom ${BUILDPLATFORM}"; \
         exit 1; \

RELEASES.md

@@ -4,22 +4,20 @@ The `#validators-private` channel on discord will be used for all communications
 
 **The core team will endeavour to always make sure there is 48-72 hours notice of an impending upgrade, unless there is no alternative.**
 
-Most of our validator communications is done on the [Terra Validator Discord](https://discord.com/invite/xfZK6RMFFx). You should join, and change your server name to `nick | validator-name`, then ask a mod for permission to see the private validator channels.
+Most validator communications is done on the [Terra Validator Discord](https://discord.gg/k6DNPx5FCP). You should join, and change your server name to `nick | validator-name`, then ask a mod for permission to see the private validator channels.
 
 ## Release versioning
 
 **If a change crosses a major version number, i.e. `1.x.x -> 2.x.x` then it is definitely consensus-breaking.**
 
-In the past, some releases have been consensus-breaking but only incremented a minor version, if clearly indicated. In future we will look to be clearer. 
-
 **Only patch versions, i.e. `x.x.1 -> x.x.2`, or `1.1.0 -> 1.1.1` are guaranteed to be non-consensus breaking.**
 
 ## Scheduled upgrade via governance
 
 For a SoftwareUpgradeProposal via governance:
 
-1. Validators will be told via announcements channel when the prop is live
-2. Validators will be told via announcements channel if it passes
+1. Validators will be told via announcements channel when the prop is live.
+2. Validators will be told via announcements channel if it passes. 
 3. Validators will be told via announcements channel when the upgrade instructions are available, and the upgrade will be coordinated in the private validators channel as the target upgrade block nears.
 
 ## Emergency upgrade or security patch

SECURITY.md

@@ -6,49 +6,41 @@ The Terra core development team uses GitHub to manage feature requests and bugs.
 
 Issues added to GitHub will be triaged as they come in.
 
-Tracking of in-flight issues will be done through the Terra Core project board, but of course we reserve the right to not make a public issue if there is a security implication in doing so.
+Tracking of in-flight issues will be done through the Terra Core project board; however, the Terra core development team reserves the right to not make a public issue if there is a security implication in doing so.
 
 ## Feature request 🚀
 
-For a feature request, e.g. module inclusion, please make a GitHub issue. Clearly state your use case and what value it will bring to other users or developers on Terra.
+For a feature request, e.g. module inclusion, please make a GitHub issue. Clearly state your use case and what value it will bring to other users or developers.
 
-If it is something that can be handled by a param change, discuss it on Discord in the `#governance` channel, and consider a governance proposal.
+For chain-specific requests, governance, or parameter changes, please discuss any issues or features on the relevant chain. 
 
 ## Standard priority bug 🐛
 
 For a bug that is non-sensitive and/or operational in nature rather than a critical vulnerability, please add it as a GitHub issue.
 
-If it is not triaged in a couple of days, feel free to tag `@the-frey` or `@jakehartnell`.
-
 ## Critical bug or security issue 💥
 
-If you're here because you're trying to figure out how to notify us of a security issue, go to [Discord](https://discord.com/invite/xfZK6RMFFx), and alert the core engineers:
-
-
-- Yun `Yun#4870`
-- Paul `Paul Kim#9433`
-- Jesse ` jess#5659`
+If you're here because you're trying to figure out how to notify us of a security issue, use [this link](https://www.terra.money/bugcrowd) to submit your report
 
 Please avoid opening public issues on GitHub that contain information about a potential security vulnerability as this makes it difficult to reduce the impact and harm of valid security issues.
 
 ### Coordinated Vulnerability Disclosure Policy
 
-We ask security researchers to keep vulnerabilities and communications around vulnerability submissions private and confidential until a patch is developed. In addition to this, we ask that you:
+ The Terra core development team asks security researchers to keep vulnerabilities and communications around vulnerability submissions private and confidential until a patch is developed. In addition to this, the team asks that you:
 
-- Allow us a reasonable amount of time to correct or address security vulnerabilities.
+- Allow them 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 Terra’s network, data, or services.
+- Demonstrate good faith by not disrupting or degrading Terra’s network, data, or services. 
 
 ### Vulnerability Disclosure Process
 
-Terra uses the following disclosure process:
+The Terra core development team uses the following disclosure process:
 
 - Once a security report is received, the Terra core development team works to verify the issue.
 - Patches are prepared for eligible releases in private repositories.
-- We notify the community that a security release is coming, to give users time to prepare their systems for the update. Notifications can include Discord messages, tweets, and emails to partners and validators.
+- The Terra core development team notifies the community that a security release is coming to give users time to prepare their systems for the update. Notifications can include Discord messages, tweets, and emails to partners and validators.
 - 24 hours following this notification, the fixes are applied publicly and new releases are issued.
-- Once releases are available for Terra, we notify the community, again, through the same channels as above. We also publish a Security Advisory on Github and publish the CVE, as long as neither the Security Advisory nor the CVE include any information on how to exploit these vulnerabilities beyond what information is already available in the patch itself.
-- Once the community is notified, we will pay out any relevant bug bounties to submitters.
-- One week after the releases go out, we will publish a post with further details on the vulnerability as well as our response to it.
-
-This process can take some time. Every effort will be made to handle the bug in as timely a manner as possible. However, it's important that we follow the process described above to ensure that disclosures are handled consistently and to keep Terra and the projects running on it secure.
+- Once releases are available, the community is notified again through the same channels as above.  The Terra core development team also publishes a Security Advisory on Github and publishes the CVE, as long as neither the Security Advisory nor the CVE include any information on how to exploit these vulnerabilities beyond what information is already available in the patch itself.
+- Once the community is notified, any relevant and eligible bug bounties will be paid to submitters.
+- One week after the releases go out, a post will be published with further details on the vulnerability as well as the response to it.
+- This process can take some time. Every effort will be made to handle the bug in as timely a manner as possible. However, it's important that the process described above is followed to ensure that disclosures are handled consistently and to keep Terra and the projects running on it secure.

client/docs/config.json

@@ -2,8 +2,8 @@
   "swagger": "2.0",
   "info": {
     "title": "Terra Core Rest API",
-    "description": "Rest Interface for Terra Core v2.3.0 https://github.com/terra-money/core",
-    "version": "2.3.0"
+    "description": "Rest Interface for Terra Core v2.3.1 https://github.com/terra-money/core",
+    "version": "2.3.1"
   },
   "apis": [
     {

client/docs/swagger-ui/swagger.yaml

@@ -1,8 +1,8 @@
 swagger: '2.0'
 info:
   title: Terra Core Rest API
-  description: Rest Interface for Terra Core v2.3.0 https://github.com/terra-money/core
-  version: 2.3.0
+  description: Rest Interface for Terra Core v2.3.1 https://github.com/terra-money/core
+  version: 2.3.1
 paths:
   /terra/alliances:
     get:

go.mod

@@ -36,10 +36,10 @@ require (
 	github.com/99designs/go-keychain v0.0.0-20191008050251-8e49817e8af4 // indirect
 	github.com/99designs/keyring v1.2.1 // indirect
 	github.com/ChainSafe/go-schnorrkel v0.0.0-20200405005733-88cbf1b4c40d // indirect
-	github.com/CosmWasm/wasmvm v1.1.1 // indirect
+	github.com/CosmWasm/wasmvm v1.1.2 // indirect
 	github.com/Workiva/go-datastructures v1.0.53 // indirect
 	github.com/armon/go-metrics v0.4.1 // indirect
-	github.com/aws/aws-sdk-go v1.40.45 // indirect
+	github.com/aws/aws-sdk-go v1.44.122 // indirect
 	github.com/beorn7/perks v1.0.1 // indirect
 	github.com/bgentry/go-netrc v0.0.0-20140422174119-9fd32a8b3d3d // indirect
 	github.com/bgentry/speakeasy v0.1.1-0.20220910012023-760eaf8b6816 // indirect
@@ -57,7 +57,7 @@ require (
 	github.com/cosmos/gorocksdb v1.2.0 // indirect
 	github.com/cosmos/iavl v0.19.5 // indirect
 	github.com/cosmos/ledger-cosmos-go v0.12.2 // indirect
-	github.com/cosmos/ledger-go v0.9.2 // indirect
+	github.com/cosmos/ledger-go v0.9.3 // indirect
 	github.com/creachadair/taskgroup v0.3.2 // indirect
 	github.com/danieljoos/wincred v1.1.2 // indirect
 	github.com/davecgh/go-spew v1.1.1 // indirect
@@ -95,7 +95,7 @@ require (
 	github.com/gtank/merlin v0.1.1 // indirect
 	github.com/gtank/ristretto255 v0.1.2 // indirect
 	github.com/hashicorp/go-cleanhttp v0.5.2 // indirect
-	github.com/hashicorp/go-getter v1.6.1 // indirect
+	github.com/hashicorp/go-getter v1.7.1 // indirect
 	github.com/hashicorp/go-immutable-radix v1.3.1 // indirect
 	github.com/hashicorp/go-safetemp v1.0.0 // indirect
 	github.com/hashicorp/go-version v1.6.0 // indirect
@@ -118,7 +118,7 @@ require (
 	github.com/mimoo/StrobeGo v0.0.0-20210601165009-122bf33a46e0 // indirect
 	github.com/minio/highwayhash v1.0.2 // indirect
 	github.com/mitchellh/go-homedir v1.1.0 // indirect
-	github.com/mitchellh/go-testing-interface v1.0.0 // indirect
+	github.com/mitchellh/go-testing-interface v1.14.1 // indirect
 	github.com/mitchellh/mapstructure v1.5.0 // indirect
 	github.com/mtibben/percent v0.2.1 // indirect
 	github.com/onsi/ginkgo v1.16.4 // indirect
@@ -141,7 +141,7 @@ require (
 	github.com/syndtr/goleveldb v1.0.1-0.20210819022825-2ae1ddf74ef7 // indirect
 	github.com/tendermint/go-amino v0.16.0 // indirect
 	github.com/tidwall/btree v1.5.0 // indirect
-	github.com/ulikunitz/xz v0.5.8 // indirect
+	github.com/ulikunitz/xz v0.5.10 // indirect
 	github.com/zondax/hid v0.9.1 // indirect
 	go.etcd.io/bbolt v1.3.6 // indirect
 	go.opencensus.io v0.24.0 // indirect
@@ -166,7 +166,7 @@ require (
 )
 
 replace (
-	github.com/CosmWasm/wasmd => github.com/notional-labs/wasmd v0.30.0-sdk469.4
+	github.com/CosmWasm/wasmd => github.com/terra-money/wasmd v0.30.0-sdk469.5
 	github.com/confio/ics23/go => github.com/cosmos/cosmos-sdk/ics23/go v0.8.0
 	github.com/cosmos/cosmos-sdk => github.com/terra-money/cosmos-sdk v0.46.11-terra.rc.5
 	github.com/cosmos/ledger-cosmos-go => github.com/terra-money/ledger-terra-go v0.11.2