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

Support built-in restrictions for component combination #56

Open
crypto-vincent opened this issue Jun 18, 2024 · 0 comments
Open

Support built-in restrictions for component combination #56

crypto-vincent opened this issue Jun 18, 2024 · 0 comments
Labels
bug Something isn't working priority: high

Comments

@crypto-vincent
Copy link
Contributor

Summary

It would be helpful to have a system to restrict which components combination can be passed as parameter to a system. This is to avoid cases where a malicious actor could use in the same transactiom a Game's data in combination with another unrelated game's metadata. Making the whole system logic running on bogus assumptions.

Details

An good example of this can be found in the Tic-Tac-Toe blog example:
https://blog.magicblock.gg/bolt-tic-tac-toe/

In this example: If a malicious actor passes a Grid component in combination with an unrelated Players component, a user could effectively play someone else's game.

@notdanilo notdanilo added bug Something isn't working priority: high labels Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority: high
Projects
None yet
Development

No branches or pull requests

2 participants