Skip to content

fix: make solana caip compliant again#7930

Merged
NeOMakinG merged 3 commits intodevelopfrom
solana-caip
Oct 14, 2024
Merged

fix: make solana caip compliant again#7930
NeOMakinG merged 3 commits intodevelopfrom
solana-caip

Conversation

@NeOMakinG
Copy link
Copy Markdown
Collaborator

Description

I initially used spl as assetNamespace which is for reference wrong (#7925 (comment)) as CAIP19 defined the assetNamespace as token

In this PR I replaced every spl occurrences by token

Issue (if applicable)

n/a

Risk

No risk

High Risk PRs Require 2 approvals

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

Testing

  • Turn the solana flag on and verify that Solana assets are working fine (SOl, MEW, JUP...)

Engineering

n/a

Operations

n/a

  • 🏁 My feature is behind a flag and doesn't require operations testing (yet)

Screenshots (if applicable)

image
image
image
image

@NeOMakinG NeOMakinG requested a review from a team as a code owner October 14, 2024 12:59
@NeOMakinG NeOMakinG mentioned this pull request Oct 14, 2024
1 task
Copy link
Copy Markdown
Contributor

@gomesalexandre gomesalexandre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Couldn't find any stale spl references in project

@NeOMakinG NeOMakinG enabled auto-merge (squash) October 14, 2024 15:19
@NeOMakinG NeOMakinG merged commit 5429570 into develop Oct 14, 2024
@NeOMakinG NeOMakinG deleted the solana-caip branch October 14, 2024 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants