LP-0021: Blockchain and Zone Wallet and SDK - #122
Draft
fryorcraken wants to merge 11 commits into
Draft
Conversation
Covers LEZ + blockchain asset ownership/transfer, token program support, staking, chain<->zone bridging, multi-zone/sequencer config, multi-account (incl. public/private LEZ accounts), a developer SDK with wallet-selection/approval flow, watch addresses, and testnet 0.3 support, with adoption metrics modeled on the lambda-prize forward plan's V0.3 testnet framework.
✅ Validation passedA reviewer will assess against the prize criteria. Automated check. See solution template and TERMS. |
Generic on-chain activity cannot be traced back to the wallet software that produced it, so the previous metrics measured nothing specific to a challenger's submission. Replace them with traction attributable to the wallet itself: 10 independent third-party SDK integrations with genuine commit history, 100 repo stars, 100 on-chain inscriptions via a designated zone, and 20 Discord + 20 Twitter/X testimonials. All are required and evaluation is discretionary, with commit and account histories inspected, per the forward plan's ETH-Global-style criteria. Framed as the first tranche, with a follow-up LP expected.
fryorcraken
changed the title
fryorcraken
changed the title
- Testimonial mini app: reference SDK integration that inscribes "I use this wallet" on both the blockchain and the official Logos zone. Doubles as the canonical example for third-party devs and the tool that produces the adoption criteria's on-chain inscriptions. - Name the official zone by sequencer endpoint rather than a number: zones are identified by ChannelId/endpoint, not sequentially, so there is no zone number to cite. Testnet 0.3 endpoint TBC at open. - Discretionary UX-quality criterion, per the forward plan's "volume + usability/UX signal" dimension. - No mandatory external services: any third-party service (e.g. price API) must be disclosed, disableable, and non-essential. - Adopt the Supportability requirements from PR #67 (cross-platform build, mkLogosModule, module catalog publishing), since that template change is not yet merged and so is not inherited.
Above the live build-LP bands (L = $1,200, XL ~ $2,000) to reflect that this prize couples a large build with a first adoption tranche requiring sustained ecosystem outreach, not just delivery.
Requests testnet funds from both the Logos blockchain and LEZ faucets with SDK-driven account selection. Unified app preferred; a split is allowed if the faucet backends differ enough to contort one flow. Gives the SDK a second worked example and gives the 100 inscribers a supported way to fund accounts on both layers before inscribing.
fryorcraken
commented
Aug 10, 2026
- Retitle to "Blockchain and Zone Wallet and SDK" (+ README table). - Drop token minting; scope token program to owning/transferring from public and private accounts. - Say "private and public accounts" rather than "shielded balances". - Testimonial mini app: specify a LEZ smart contract holds the testimonials; custom text, optional username, and a unique identifier per LP submission. - SDK covers smart contract interactions, not just transfers. - Move module-catalog publishing from Supportability to Usability. - Wallet state survives network drops. - External-services criterion covers analytics: opt-in only. - Adoption: rename section, retitle intro to traction attributable to a submission, note it applies in addition to FURPS, allow custom inscription text, encourage screenshots with X testimonials. - Remove the Out of Scope section. - Drop the duplicated RISC0_DEV_MODE video criterion from Supportability. The narrated demo stays in Submission Requirements since the README mandates one for every prize.
If remote data persistence is needed for reliability (backup, cross-device recovery), it must use Logos Storage rather than a centralised provider, with client-side encryption.
Replace nine prose em-dashes with commas, colons, parentheses, or sentence breaks, keeping only the two Resources list separators that match the convention in other prize files. Demote one reflexive three-item list to two.
- SDK integrations 10 -> 15, with at least 3 non-trivial apps that exist to do something other than demonstrate the SDK. - Inscriptions 100 -> 250, from at least 250 distinct accounts. - Add a sustained-activity criterion: inscriptions must span at least 2 months with 50+ in each month, so a single burst does not qualify. Verifiable from chain data via the submission's unique identifier. - Testimonials 20 -> 50 on each of Discord and Twitter/X. - Note in Evaluation Process that a submission cannot qualify before the two-month adoption window has elapsed.
fryorcraken
changed the title
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
1 participant
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.
Fixes logos-co/ecosystem#194
Summary
Adds
prizes/LP-0021.md— a λPrize for a unified wallet and developer SDK spanning the Logos blockchain and Logos Execution Zones, plus the README table entry.Wallet. Own, send, and receive assets on both the blockchain and LEZ, across public and private accounts. Token program (own/transfer, no minting), staking/unstaking/reward claims, bidirectional chain↔zone bridging, multi-zone and per-zone sequencer configuration, multiple accounts on both layers, and watch-only addresses. Targets testnet 0.3.
SDK. Lets third-party dApps request account access, read state, and propose transfers and smart contract interactions — with a wallet-selection and approval flow so nothing is signed without the user choosing an account and seeing what they are approving.
Reference mini apps. Two SDK integrations that double as worked examples:
Privacy posture. No mandatory external services — anything third-party (price APIs, analytics) must be disclosed, disableable, and opt-in, with the wallet fully functional without it. Any remote persistence must use Logos Storage with client-side encryption.
Adoption criteria. Deliberately measures traction attributable to a submission, rather than generic on-chain activity — which cannot be traced back to the wallet software that produced it. All are required, in addition to the FURPS criteria, and all are judged discretionarily with commit and account histories inspected:
Prize: $6,000. Above the live build-LP bands (L = $1,200, XL ≈ $2,000) because this couples a large build with an adoption push requiring sustained ecosystem outreach.
Notes for reviewers
ChannelId(a 32-byte Ed25519 public key) and self-register on first use; for clients a zone is just its sequencer endpoint. The prize names the official testnet zone ashttps://testnet.lez.logos.coand flags that the 0.3 endpoint is confirmed at open.mkLogosModule, and module-catalog publishing are written in directly, since template: require Mac + Linux build support #67 is not yet merged and so is not inherited from the template. Expect overlap once it lands.Test plan
prizes/LP-0021.mdrenders cleanly on GitHub