8000 Mismatch in ABI Metadata Version for Ink! v6 (Generates Version 5 Instead of 6) · Issue #2505 · use-ink/ink · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Mismatch in ABI Metadata Version for Ink! v6 (Generates Version 5 Instead of 6) #2505

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom
Closed
AlexD10S opened this issue May 14, 2025 · 1 comment · Fixed by #2507
Closed

Mismatch in ABI Metadata Version for Ink! v6 (Generates Version 5 Instead of 6) #2505

AlexD10S opened this issue May 14, 2025 · 1 comment · Fixed by #2507
Assignees
@davidsemakula @AlexD10S

Comments

@AlexD10S
Copy link
Contributor
AlexD10S commented May 14, 2025 •
edited
Loading

Reported by @sinzii while working on support for Dedot in ink! v6.

According to the documentation https://use.ink/docs/v6/basics/metadata/ink/#version, the generated metadata should use ABI version 6. However, when creating a new contract using the current toolchain, the generated flipper.json metadata still reports version 5.

Steps to Reproduce:

  1. Run cargo contract new flipper
  2. Run cargo contract build --release
  3. Open the generated target/ink/flipper.json, the metadata shows "version": 5

Proposed Fix

After investigation, it appears the cause is in the https://github.com/use-ink/ink/blob/master/crates/metadata/src/lib.rs#L76, where the constant:

const METADATA_VERSION: u64 = 5;

likely needs to be updated to:

const METADATA_VERSION: u64 = 6;

Should I go ahead and submit a PR with this change? Or am I missing something else?

@davidsemakula Would appreciate any clarification before proceeding.
@davidsemakula
Copy link
Collaborator

Should I go ahead and submit a PR with this change?

@AlexD10S Yes

@AlexD10S AlexD10S mentioned this issue May 16, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@davidsemakula davidsemakula

@AlexD10S AlexD10S

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: update metadata version use-ink/ink
2 participants
@davidsemakula @AlexD10S
0