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

SPIKE: Is it feasible to block default wasmd messages w/o forking the whole wasmd repo? (If so, that could cut out a lot of debt) #31

Closed
2 tasks
Tracked by #13
jonathanpberger opened this issue Jun 21, 2024 · 3 comments
Assignees

Comments

@jonathanpberger
Copy link

jonathanpberger commented Jun 21, 2024

As SL
We want to see if blocking default wasmd is feasible given our time/budget
Bc that would let us un-fork, and make on going dev't way easier

Tasks

Preview Give feedback
@Reecepbcups
Copy link
Member

Reecepbcups commented Jun 29, 2024

yes

@jonathanpberger jonathanpberger changed the title SPIKE: can we block default wasmd messages w/o forking the whole wasmd repo? (If so, that could cut out a lot of debt) SPIKE: Is it feasible to block default wasmd messages w/o forking the whole wasmd repo? (If so, that could cut out a lot of debt) Jul 15, 2024
@jonathanpberger
Copy link
Author

@pharr117 pls timebox ~1-2hrs to research the level of effort. Looking for "don't bother" or "hmm...maybe." If the latter, let's start to hone in on 1 person-week? 1 person-month? 1-person-year? Order-of-magnitude is close enough.

@joelsmith-2019
Copy link
Member

Took ~1 day to implement the change. Still yet to be tested.

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

No branches or pull requests

4 participants