Improve submission screening to catch decorative contracts#286
Merged
Conversation
Focus the client-contract integration check on whether the contracts are actually the source of truth for the game, not just whether they are called. Add concrete red flags for decorative integrations: optimistic state updates, off-chain state management, mismatched on-chain models, and fire-and-forget calls. Revise the edge case for "contracts are called but don't drive the game" to clarify the key test: would the game break if contracts were removed? This catches cases where a submission forks a starter repo (or any repo), calls the starter contracts as a side effect, but runs the actual game entirely off-chain via WebSocket, client memory, or external servers. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Strengthened the
Client-Contract Integrationscreening check to focus on whether contracts are actually the source of truth for the game, not just whether they are called. This catches submissions where the real game runs off-chain (WebSocket server, client memory) while the contracts are called as a side effect.Changes
This catches cases like PR #281 (Contagion) where a fork of a starter repo calls starter functions but runs the actual game entirely via WebSocket server.
🤖 Generated with Claude Code