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

fix(protocol): Correct decoding (TKO-03) #15582

Merged
merged 1 commit into from
Jan 26, 2024
Merged

fix(protocol): Correct decoding (TKO-03) #15582

merged 1 commit into from
Jan 26, 2024

Conversation

adaki2004
Copy link
Contributor

image

Copy link

vercel bot commented Jan 26, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
bridge-ui-v2-a6 ✅ Ready (Inspect) Visit Preview Jan 26, 2024 6:16am

Copy link
Contributor

@Brechtpd Brechtpd left a comment

Choose a reason for hiding this comment

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

General question: do we need recall? It seems like a complex thing, also complex to test, and a source of multiple bugs presumably also because it's hard to test and not being used.

So do we think it is just a nice to have? Do we think it's something critical that will actually be used? I'm just trying to find out if this feature makes sense from a risk/reward point of view because the bridge itself is so critical for security, the reward really needs to be worth the risk.

@dantaik dantaik added this pull request to the merge queue Jan 26, 2024
Merged via the queue into alpha-6 with commit dc46b27 Jan 26, 2024
12 of 14 checks passed
@dantaik dantaik deleted the correct_decoding branch January 26, 2024 13:55
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