mirror of
https://github.com/logos-co/lambda-prize.git
synced 2026-08-27 17:41:17 +00:00
LP-0021, LP-0022: note planned program source-verification registry
A separate, not-yet-written λPrize will cover a registry mapping deployed program bytecode to source. Note it near the smart-contract approval-decoding criterion and in Resources: the wallet MAY use it if available by submission time, but it is not a requirement since the registry LP doesn't exist yet. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
4718cce9d2
commit
e5bf8f25fe
+2
-1
@@ -34,7 +34,7 @@ Logos Execution Zones (LEZ) are the programmable environment where Logos dApps r
|
||||
- [ ] Provide a module/SDK usable by other Logos modules and third-party dApps to query balances, request account access, and request transfers and smart contract interactions.
|
||||
- [ ] Provide a Logos Basecamp app GUI with local build instructions and loadable assets.
|
||||
- [ ] Logos Basecamp modules are published to a module catalog: a fork of [`logos-modules-release-base`](https://github.com/logos-co/logos-modules-release-base), publishing releases via [`logos-modules-release-action`](https://github.com/logos-co/logos-modules-release-action). The catalog's `logos-repo.json` URL must be included in the submission so evaluators can install the module through the package-manager UI / `lgpd`.
|
||||
- [ ] Account selection and transaction approval prompts clearly identify the requesting dApp, the target account, and (for transactions) the asset, amount, and destination. **For smart-contract interactions** (including token approvals), the prompt must show a human-readable summary of the call's effects — assets/approvals granted or moved and to which program/account — not just raw calldata, so the user can catch unexpected outflows or unlimited approvals before signing.
|
||||
- [ ] Account selection and transaction approval prompts clearly identify the requesting dApp, the target account, and (for transactions) the asset, amount, and destination. **For smart-contract interactions** (including token approvals), the prompt must show a human-readable summary of the call's effects — assets/approvals granted or moved and to which program/account — not just raw calldata, so the user can catch unexpected outflows or unlimited approvals before signing. A separate λPrize for a program source-verification registry (bytecode-to-source, not yet written) is planned; if available by the time of submission, the wallet MAY use it to show verified source for a program being called, but this is not required.
|
||||
- [ ] **UX quality.** The wallet must be polished, functional, and usable by a non-expert: coherent navigation across accounts, comprehensible transaction previews, and clear error/pending states. This is judged against overall impression rather than a checklist: evaluators will use the wallet as a normal user would.
|
||||
|
||||
### Reliability
|
||||
@@ -129,6 +129,7 @@ The following policies apply to all prizes (see [evaluation policies](../README.
|
||||
- [LP-0013](LP-0013.md) — Token program improvements (authorities)
|
||||
- [LP-0014](LP-0014.md) — Token program improvements (ATAs + wallet tooling)
|
||||
- [LP-0022](LP-0022.md) — Combined blockchain + zone wallet (follow-up)
|
||||
- A λPrize for a program source-verification registry (bytecode-to-source) is planned but not yet written. If it lands before this prize is submitted, the wallet MAY use it to show verified source for called programs; not a requirement.
|
||||
|
||||
## Potential for Subsequent λ Prizes
|
||||
|
||||
|
||||
+2
-1
@@ -37,7 +37,7 @@ Logos' architecture separates a base blockchain from programmable execution zone
|
||||
|
||||
- [ ] The SDK continues to be usable by other Logos modules and third-party dApps to query balances, request account access, and request transfers and smart contract interactions, now across the blockchain and multiple zones.
|
||||
- [ ] The Basecamp app GUI and CLI are extended to cover blockchain accounts, staking, bridging, and multi-zone/sequencer configuration.
|
||||
- [ ] Account selection and transaction approval prompts clearly identify the requesting dApp, the target account (including which chain/zone), and (for transactions) the asset, amount, and destination. **For smart-contract interactions** (including token approvals, staking, and bridging), the prompt must show a human-readable summary of the call's effects — assets/approvals granted or moved and to which program/account — not just raw calldata, so the user can catch unexpected outflows or unlimited approvals before signing.
|
||||
- [ ] Account selection and transaction approval prompts clearly identify the requesting dApp, the target account (including which chain/zone), and (for transactions) the asset, amount, and destination. **For smart-contract interactions** (including token approvals, staking, and bridging), the prompt must show a human-readable summary of the call's effects — assets/approvals granted or moved and to which program/account — not just raw calldata, so the user can catch unexpected outflows or unlimited approvals before signing. A separate λPrize for a program source-verification registry (bytecode-to-source, not yet written) is planned; if available by the time of submission, the wallet MAY use it to show verified source for a program being called, but this is not required.
|
||||
- [ ] **UX quality.** The extended wallet must remain polished and usable by a non-expert across chains and zones: coherent navigation, comprehensible transaction previews (including bridge and staking flows), and clear error/pending states. This is judged against overall impression rather than a checklist: evaluators will use the wallet as a normal user would.
|
||||
|
||||
### Reliability
|
||||
@@ -133,6 +133,7 @@ The following policies apply to all prizes (see [evaluation policies](../README.
|
||||
- [LP-0021](LP-0021.md) — LEZ zone wallet and SDK (prerequisite)
|
||||
- [LP-0013](LP-0013.md) — Token program improvements (authorities)
|
||||
- [LP-0014](LP-0014.md) — Token program improvements (ATAs + wallet tooling)
|
||||
- A λPrize for a program source-verification registry (bytecode-to-source) is planned but not yet written. If it lands before this prize is submitted, the wallet MAY use it to show verified source for called programs; not a requirement.
|
||||
|
||||
## Potential for Subsequent λ Prizes
|
||||
|
||||
|
||||
Reference in New Issue
Block a user