Skip to content

Solution: LP-0017 — Whistleblower#48

Open
Thompsonmina wants to merge 4 commits into
logos-co:masterfrom
Thompsonmina:lp-0017-whistleblower
Open

Solution: LP-0017 — Whistleblower#48
Thompsonmina wants to merge 4 commits into
logos-co:masterfrom
Thompsonmina:lp-0017-whistleblower

Conversation

@Thompsonmina
Copy link
Copy Markdown

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 12, 2026

⚠️ Warnings

Warnings (non-blocking):

  • ⚠️ Prize references a Logos mini-app; no module.json found.

ℹ️ Solution submission for LP-0017.
ℹ️ Checking repo: https://github.com/Thompsonmina/WhistleBlower-Logos-


Automated check. See solution template and TERMS.

@weboko
Copy link
Copy Markdown

weboko commented May 19, 2026

Hi! Thank you for your submission. I will review later this week and will try to come back with concrete comment.

Comment thread solutions/LP-0017.md
- [x] **Broadcast dedup**: chronicle keeps a per-CID publish ledger; subscribers (incl. `batch-anchor`) skip duplicates.
- [x] **Batch tool resume after interruption**: seeded from chain at startup + Waku store-protocol catch-up over a configurable lookback window.
- [x] **CU benchmarks (1 + 50 CID)**: documented in `README_CHRONICLE_REGISTRY.md` § Compute units (cold n=1 = 2,240 cycles; cold n=50 = 178,646 cycles).
- [x] **Local LEZ deployment**: chronicle-registry deploys to a local LEZ devnet via `make deploy`; `scripts/setup.sh` does so end-to-end.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to have it tested on the testnet/devnet as per criteria here
https://github.com/logos-co/lambda-prize/blob/master/prizes/LP-0017.md#supportability

have you tried?

Comment thread solutions/LP-0017.md
- [x] **Batch tool resume after interruption**: seeded from chain at startup + Waku store-protocol catch-up over a configurable lookback window.
- [x] **CU benchmarks (1 + 50 CID)**: documented in `README_CHRONICLE_REGISTRY.md` § Compute units (cold n=1 = 2,240 cycles; cold n=50 = 178,646 cycles).
- [x] **Local LEZ deployment**: chronicle-registry deploys to a local LEZ devnet via `make deploy`; `scripts/setup.sh` does so end-to-end.
- [ ] **E2E integration tests in CI**: IT contract sketched in `integration-test.toml`; chronicle smoke test on the IT topic; that runs against a real local sequencer; `RISC0_DEV_MODE` left unset so the prover runs in production mode CI runner that runs lez and logoscore environment pending.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure on this step. Were you able to validate E2E?
https://github.com/logos-co/lambda-prize/blob/master/prizes/LP-0017.md#supportability

Comment thread solutions/LP-0017.md

Worst-case (n=50 near the 100 KiB account-data cap) is ~288k cycles — well under 1 Mi, ~3 % of the NSSA 32 Mi per-tx budget.

### Supportability
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't find in this document mentioning of CI is green on the default branch but it is a criteria listed in https://github.com/logos-co/lambda-prize/blob/master/prizes/LP-0017.md#supportability

Comment thread solutions/LP-0017.md
@@ -0,0 +1,141 @@
# Solution: LP-0017 — Whistleblower
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

overall, in this submission I see you are missing GitHub issues filed for any problems encountered with Logos technology

have you had no problems? was everything smooth?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@weboko
Copy link
Copy Markdown

weboko commented May 25, 2026

I left some comments, please, let me know if you have questions

Meanwhile I will try to play with your submitted software

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants