Skip to content

chore: mark FLUID permit as unsupported#847

Merged
shoom3301 merged 1 commit intomainfrom
fix/fluid-permit
Feb 17, 2025
Merged

chore: mark FLUID permit as unsupported#847
shoom3301 merged 1 commit intomainfrom
fix/fluid-permit

Conversation

@shoom3301
Copy link
Contributor

No description provided.

@shoom3301 shoom3301 requested review from a team February 17, 2025 11:52
@shoom3301 shoom3301 self-assigned this Feb 17, 2025
@shoom3301 shoom3301 merged commit 5954e2c into main Feb 17, 2025
4 checks passed
@shoom3301 shoom3301 deleted the fix/fluid-permit branch February 17, 2025 11:52
@github-actions github-actions bot locked and limited conversation to collaborators Feb 17, 2025
Copy link
Contributor

@anxolin anxolin left a comment

Choose a reason for hiding this comment

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

@shoom3301 can you add some context. The description is empty

"0x6f40d4a6237c257fff2db00fa0510deeecd303eb": {
"type": "eip-2612",
"version": "1",
"type": "unsupported",
Copy link
Contributor

Choose a reason for hiding this comment

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

I guess this is related to https://cowservices.slack.com/archives/C0361CDG8GP/p1739786487403269, but I didn't get why it was detected as 2612 token, and manually changed later to unsupported

Copy link
Collaborator

Choose a reason for hiding this comment

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

It's possible their version was updated and/or some other change in their token implementation changed for which the permit script is not able to handle it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants