1. Add new issue template
2. config project

The gas fee used by the current precompiled contract interface is set by the developer for testing convenience, and will need to be adjusted to a suitable value based on the economic model.

System information

Geth version: geth version
CL client & version: e.g. lighthouse/nimbus/[email protected]
OS & Version: Windows/Linux/OSX
Commit hash : (if develop)

Expected behaviour

Actual behaviour

Steps to reproduce the behaviour

Backtrace

[backtrace]

When submitting logs: please submit them as text and not screenshots.

Summary of Bug

panic when run mechaind.

Version

Steps to Reproduce

Screenshots

Additional context

cased by gov init

claim the test ZKME tokens on Testnet by the faucet

• mechain
• storage provider
• blockscout
• js-sdk
• web ui

Deploy mechain nodes and sp nodes, write documents about deploy progress.

1. core concept in object about seal: https://docs.bnbchain.org/bnb-greenfield/core-concept/data-storage/simple-storage-service/?h=seal#object_1
2. user guide: https://docs.bnbchain.org/bnb-greenfield/getting-started/greenfield-command/?h=seal#uploaddownload-files, can skip the waiting seal progress
3. seal address in sp config files: https://docs.bnbchain.org/bnb-greenfield/storage-provider/run-book/run-local-SP-network/?h=seal#quickly-setup-local-greenfield-blockchain-network
4. details in upload file: also has been writed in lark doc
5. cosmos & evmos gas: https://digitalpulse.larksuite.com/wiki/ElMDw7nNNidr1nkdzCRuGfAFstc
6. gas and fee on greenfield:https://docs.bnbchain.org/bnb-greenfield/core-concept/billing-payment/
7. cosmos-gas-fee: https://docs.cosmos.network/main/learn/beginner/gas-fees

E2E implement and test crosschain mirror nft

Rationale

When debugging the "upload object" function, I wanted to use the original greenfield-js-sdk to see how it performs the step-by-step upload. However, I encountered another issue where the greenfield-js-sdk cannot initiate transactions on mechain. I attempted to use the greenfield-js-sdk to initiate a transfer transaction (https://github.com/bnb-chain/greenfield-js-sdk/blob/d1b742a/examples/nodejs-file-management/transfer.js), but it failed with an error message. I'm a bit confused as to why mechain-cmd or mechaind (the executable file compiled from mechain) can initiate transactions, but the greenfield-js-sdk cannot. Could it be that they use different signature methods? So, the question I need to confirm is whether we have made any modifications to the signature method of mechain, which is causing the greenfield-js-sdk to be unable to initiate transactions on mechain.

I believe this issue requires urgent attention and immediate resolution because without the js-sdk and related tools, we cannot proceed with the relevant applications. Of course, we can still initiate transfer transactions using the precompiled interface for contract compilation. I just provided an example to illustrate the problem of the greenfield-js-sdk not functioning properly.

import ethsecp256k1 , eip712 and crypto/hd from mechain-cosmos-sdk
fix ethsecp256k1.PubKey type conflict

###fix upgrade handler and types
The current code must use the latest upgrade handler to perform business logic, without the need to perform version checks on the client.

run app/ante/handler_options_test.go test TestValidateHandlerOptions

Currently, there are three sets of gas fee calculation logic: cosmos/evmos/greenfield. These three sets of billing logic need to be unified into one set.

succeed to create object, upload object, download object, etc.

The bytecode of the contract deployed cannot be queried using eth_getCode.

• token icons
• add info on https://chainlist.org/

fix: add app.Appconfig in both startalone and in-process mode
fix: change aevmos/BNB to azkme

when run setTag command:
./build/mechain-cmd --home ./deployment/local --passwordfile ./deployment/local/testkey/password.txt object setTag --tags='[{"key":"key1","value":"value1"},{"key":"key2","value":"value2"}]' gnfd://mechain/random_file
encountered the following error：

By using golang to call precompiled contracts, relevant interface tests are automated

implement regular apis for storage precompile

• merge greenfield modules except bridge, resolve compilation issues.
• fix mechian-cosmos-sdk unit tests.
• setup a 3-nodes cluster successfully.

evmos officially released a serious vulnerability caused by calling the precompiled contract in the contract. In the past two days, I figured out the entire reason why the vulnerability occurred. I wrote a simple document analysis. If you are interested, you can learn more about it through the following document.
Note: Currently there are no precompiled contracts in our system, so this vulnerability does not exist. It’s just that you need to avoid this problem if you write a precompiled contract later.

https://lcq.notion.site/Transaction-execution-not-accounting-for-all-state-transition-after-interaction-with-precompiles-a1b58333fb604d2ebc29efc0f14e4e3d?pvs=4

1. fix mechain unit tests