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

Contract Verification using Standard JSON Input Fails #341

Open
lykalabrada opened this issue Nov 1, 2023 · 3 comments
Open

Contract Verification using Standard JSON Input Fails #341

lykalabrada opened this issue Nov 1, 2023 · 3 comments
Assignees
Labels
kind/bug Something isn't working needs/area Needs area label(s) needs/priority Needs a priority label needs/triage Waiting for triage to be accepted

Comments

@lykalabrada
Copy link
Contributor

What happened:

Trying to verify a contract using Solidity (Standard JSON Input) but it's failing. Tried using Solidity (Single file) and there's no issue

What you expected to happen:

Users should be able to verify a contract using any method/compiler available on MetaScan

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

image

@lykalabrada lykalabrada added the kind/bug Something isn't working label Nov 1, 2023
@github-actions github-actions bot added the needs/triage Waiting for triage to be accepted label Nov 1, 2023
Copy link

github-actions bot commented Nov 1, 2023

@lykalabrada: Thanks for opening an issue, it is currently awaiting triage.

The triage/accepted label can be added by foundation members by writing /triage accepted in a comment.

Details

I am a bot created to help the BirthdayResearch developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

@lykalabrada lykalabrada changed the title Contract Verification using Standard JSON Input Contract Verification using Standard JSON Input Fails Nov 1, 2023
@github-actions github-actions bot added the needs/area Needs area label(s) label Nov 1, 2023
Copy link

github-actions bot commented Nov 1, 2023

@lykalabrada: There are no 'area' labels on this issue. Adding an appropriate label will greatly expedite the process for us. You can add as many area as you see fit. If you are unsure what to do you can ignore this!

You can add area labels by leaving a /area comment.

Details

I am a bot created to help the BirthdayResearch developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

@lykalabrada lykalabrada self-assigned this Nov 1, 2023
Copy link

github-actions bot commented Nov 1, 2023

@lykalabrada: Thanks for opening an issue, an appropriate priority will be added soon.

The priority labels can be added by foundation members by writing /priority [type] in a comment.

Details

I am a bot created to help the BirthdayResearch developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

@github-actions github-actions bot added the needs/priority Needs a priority label label Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working needs/area Needs area label(s) needs/priority Needs a priority label needs/triage Waiting for triage to be accepted
Projects
None yet
Development

No branches or pull requests

2 participants