Bump github.com/crypto-org-chain/cronos from 0.6.0-testnet to 0.7.1-rc0 in /example

[dependabot]

Bumps github.com/crypto-org-chain/cronos from 0.6.0-testnet to 0.7.1-rc0.

Release notes

Sourced from github.com/crypto-org-chain/cronos's releases.

v0.7.1-rc0

v0.7.1-rc0 is the first release candidate of v0.7.1, which is a bug fix version based on v0.7.0, the main bug fixes and improvements are:

• Fix tx missing issue when exceeding block gas limit in post-0.7 blocks.
• Add command patch-unlucky-tx to patch block data for the above issue, only for post-0.7 blocks, please use the command in v0.6.x to patch pre-0.7 blocks.
• Fix tendermint duplicated tx issue which causes wrong tx RPC results.
• Add command reindex-duplicated-tx to patch block data for the duplicated tx issue, it works for all blocks(both pre and post v0.7 upgrade).
• Support new mempool implementation released in tendermint v0.34.20-rc0
• Enable jemalloc allocator in rocksdb backend.
• Improve portability of the released binaries.

v0.7.0

Note: v0.7.x should only be used after the upgrade height 2693800

v0.7.0 is a major breaking upgrade from 0.6.x, it introduces EIP-1559 implementation, significant performance improvements and many json-rpc bug fixes.

Upgrade Plan Name

The plan name for mainnet upgrade should be v0.7.0.

New Config Items

Existing v0.6.x node should add these config items into app.toml before upgrade:

[json-rpc]
feehistory-cap = 100
logs-cap = 10000
block-range-cap = 10000
http-timeout="30s"
http-idle-timeout="120s"
[evm]
max-tx-gas-wanted=500000

New JSON-RPC APIs

The new apis are under json-rpc namespace cronos, need to be enabled in the json-rpc.api config item.

• cronos_getTransactionReceiptsByBlock(BlockNumberOrHash) -> List[Receipt]
• cronos_replayBlock(BlockNumberOrHash, bool) -> List[Receipt]

Major Changes

• New feemarket module to support EIP-1559 and dynamic fee transactions.
• Refactor EVM StateDB implementation, improve performance of contract execution significantly.
• Support batching multiple eth txs in a cosmos tx.

Full Changelogs

Dependency Updates

... (truncated)

Changelog

Sourced from github.com/crypto-org-chain/cronos's changelog.

Changelog

Unreleased

State Machine Breaking

• cronos#695 Implement ADR-007, generic events format with indexed params.
• cronos#728 Upgrade gravity bridge latest bugfix, including multi attestation processing and double spend check.
• cronos#742 Add upgrade handler for v0.8.0-gravity-alpha2.
• cronos#750 Add upgrade handler for v0.8.0-gravity-alpha3.
• cronos#769 Prevent cancellation function to be called outside the scope of the contract that manage it.
• cronos#775 Support turnbridge transaction.
• cronos#781 Add prune command.
• cronos#830 Upgrade gravity bridge for latest bugfixes, patching two important DOS vulnerabilities
• cronos#834 Remove unsafe experimental flag.

Bug Fixes

• #814 Fix prometheus metrics.
• #833 Fix rollback command.

Improvements

• #813 Tune up rocksdb options.
• #779 Add config iavl-lazy-loading to enable lazy loading of iavl store.

Jan 04, 2023

v1.0.2

State Machine Breaking

• #802 Update ibc-go to v5.2.0.

December 14, 2022

v1.0.1

Improvements

• #781 Add prune command.
• #790 Update cosmos-sdk to v0.46.7, it fix a migration issue which affects pending proposals's votes during upgrade, it also adds the config entries for file streamer.

Nov 22, 2022

v1.0.0

Improvements

... (truncated)

Commits

• 0d15321 Problem: release workflow don't permission to create release (#569)
• 76e9440 Problem: (0.7.x)tendermint could include duplicated tx which mess up the tx i...
• 75c2672 Problem: failed tx are ignored in json-rpc apis (backport #502) (#503)
• cdfe53c Problem: fix reindex duplicated command fail when indexed tx is nil (#548)
• 32645d3 Problem: 0.7.x fix-unlucky-tx command does not include concurrency and null i...
• 5c66cd8 Problem: no command to patch the duplicated tx situation (#522)
• 5de290b Problem: no command to patch missing transactions between v0.7.0 and v0.7.1 (...
• fa61791 Problem: recent improvements in gomod2nix are not used (backport #518) (#525)
• 47dfa99 Problem: gravity bridge test timeout occationally (backport #528) (#529)
• abfd210 Problem: dirty check github action plugin don't work anymore (backport #519) ...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.