Repository navigation
Prize specs: 'release early' instead of 'ship early' - #170
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Validation passedA reviewer will assess against the prize criteria. Automated check. See solution template and TERMS. |
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.
Replaces "ship early" with "release early" in the sustained-adoption sentence ("Builders are encouraged to … early and start accruing …") of:
prizes/LP-0018.mdprizes/LP-0021.mdprizes/LP-0022.mdprizes/LP-0023.mdThe rest of the sentence is unchanged. LP-0001 is handled separately in #152.
Remaining 'ship' wording (not changed)
Whole-word, case-insensitive search for ship / ships / shipped / shipping across
prizes/*.md,README.mdandTERMS.md. No hits inREADME.mdorTERMS.md.prizes/LP-0017.md:44: "Note that decentralised sequencers for zones are not yet shipped: the zone SDK approach requires a single designated actor to perform consensus inscription, which affects the trust model."prizes/LP-0018.md:30: "It also ships a reusable Basecamp SDK/module so other Basecamp apps and modules can discover and use those files locally."prizes/LP-0021.md:22: "Scoping this first prize to a single zone lets a winning team ship a complete, adoption-ready wallet quickly, rather than being blocked on blockchain-level features (staking, bridging, multi-zone config) that are only needed once a base of zone-side users and dApps already exists."prizes/LP-0021.md:72: "10 third-party developers have each shipped a functional Logos Basecamp app (a ui type Logos module, per the module-catalog requirement above) that uses the Wallet Provider SDK."prizes/LP-0022.md:78: "That covers a different team, and the LP-0021 winning team shipping a wallet/SDK not descended from their own merged LP-0021 solution."prizes/LP-0022.md:81: "5 third-party developers, independent of each other and of the submitting team, have each shipped a functional Logos Basecamp app (a ui type Logos module, per the module-catalog requirement above) that uses the blockchain, staking, bridging, or multi-zone additions from this prize's SDK extension (not merely the LP-0021 zone SDK)."prizes/LP-0023.md:22: "Each tool that needs this information ends up shipping its own hardcoded list, and those lists drift apart."prizes/LP-0023.md:73: "Each must ship as a Logos UI Module, publicly hosted on a mainstream forge (GitHub, GitLab, Codeberg, etc.) with a clear, genuine commit history: development spread over time by a real contributor, not a single bulk import."prizes/LP-0023.md:86: "A submission may implement something similar, omit it, or make the trusted set user-configurable, but if it ships one, the list must be user-inspectable and overridable."🤖 Generated with Claude Code