Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Precompile contract verification #7778

Closed
bulbazavr1024 opened this issue Jun 23, 2023 · 5 comments
Closed

Precompile contract verification #7778

bulbazavr1024 opened this issue Jun 23, 2023 · 5 comments
Labels
waiting on feedback Waiting for original opener to respond if bug is fixed

Comments

@bulbazavr1024
Copy link

Describe your issue here.

Environment

  • Deployment type: Docker-compose:
  • Elixir & Erlang/OTP versions (elixir -version): latest
  • Node JS version (node -v):
  • Operating System: ubuntu 22.0.4
  • Blockscout Version/branch/commit: master
  • Archive node type && version: Geth

@vbaranov Hey! I want to add precompile contract code to blockscout.
I have chain, that implement Cosmos core logic and Geth EVM. (e.x. EVMOS). There is deployed precompile contract to address
0x1559000000000000000000000000000000000001 in Cosmos.
EXTCODESIZE == 0, and this contract hasn't deploy transaction emitted to EVM part.
How can I add contract source code manually ?

If I try to INSERT it to smart_contracts table I receive ERROR: insert or update on table "smart_contracts" violates foreign key constraint "smart_contracts_address_hash_fkey"

But I have address 0x1559000000000000000000000000000000000001 in addresses table
image

What is the best practice of it ?

@sl1depengwyn
Copy link
Collaborator

I think the best way to do this is to pass path to your genesis/chain spec via CHAIN_SPEC_PATH env
But, if this is not applicable to you by any reason, you need to insert contract bytecode to contract_code column in addresses table

@bulbazavr1024
Copy link
Author

@sl1depengwyn Thanks! Will try in a short time

@sl1depengwyn sl1depengwyn added the waiting on feedback Waiting for original opener to respond if bug is fixed label Jun 30, 2023
@vbaranov
Copy link
Member

@bulbazavr1024 did the last suggestion resolve the issue?

@bulbazavr1024
Copy link
Author

@vbaranov Hey! Sorry for the delay.
I was on vacation and couldn't check it. I will give you an answer tomorrow

@vbaranov
Copy link
Member

@bulbazavr1024 I am closing this. Please let us know, if the issue is still reproducible on your side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting on feedback Waiting for original opener to respond if bug is fixed
Projects
None yet
Development

No branches or pull requests

3 participants