Repository navigation
Conversation
✅ Validation passedA reviewer will assess against the prize criteria. Automated check. See solution template and TERMS. |
fryorcraken
approved these changes
Nov 4, 2026
| - [ ] **Deployer vs third-party entries**: the registry may hold both an entry from the program's own deployer and entries from third parties. The deployer's entry must be signed by the account that deployed the program, and clients must be able to tell it apart from a third-party entry without trusting an off-chain service. Either way, source verification (below) should be used to confirm the recorded claim actually matches the deployed program. The demo must show an unauthorised attempt to create a deployer entry being rejected. | ||
| - [ ] **Update**: only the original registering author may update an existing entry (version, IDL pointer, description). Authorship transfer is optional; if implemented, it must require signatures from both parties. | ||
| - [ ] **IDL publishing**: the IDL is stored on **Logos Storage**. | ||
| - [ ] **IDL format and tooling**: IDLs use the [LEZ IDL format](https://github.com/jzaki/lez-prog-call/blob/main/idl.md) (`lez-idl`). An IDL is generated from a program's source rather than written by hand, so anyone can regenerate it from the recorded source and commit and check that it matches the published one byte for byte. Tooling, whether the submission's own or existing tooling it builds on, must be able to: |
Collaborator
There was a problem hiding this comment.
I assume this should point to spel once ready?
Collaborator
Author
There was a problem hiding this comment.
Since spel needed a rewrite, and I'd already implemented separate concerns for lez v0.4 tooling, it'd be less clear mapping things back into spel.
- The wallet cli has a program call added
lez-prog-callis more about encoding lez prog params and making the wallet call (does what it says on the tin)- recently re-added generating an updated idl, without extra syntactic sugar (so far)
- the tui in jz-progs which uses above, will become part of scaffold
When logos-co owns lez-prog-call, then above can be lez-call idl to generate the guest program's idl for lez v0.4
Collaborator
There was a problem hiding this comment.
That link throws 404 for me
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.
No description provided.