Add submission for bounty ergoplatform/ergo#1870 - #75
Open
Ergologica wants to merge 1 commit into
Open
Conversation
Added submission details for bounty ID ergoplatform/ergo#1870, including contributor information, work link, and status.
Contributor
Submission triage
|
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.
Re-files the reservation for ergoplatform/ergo#1870 - "Consider slicing by height in /boxes/unspent" (500 SigUSD).
Work is implemented and submitted upstream as ergoplatform/ergo#2458 (open, awaiting review). Status stays
in-progressuntil that PR merges;expected_completionset to 2026-09-30.This replaces #57 (originally filed 2026-08-02), which the scheduled triage of 2026-08-28 closed with
invalid-json. The JSON in that PR parses cleanly and its branch merges clean againstmain, so the label most likely came from a transient HTTP failure inread_submission, where any fetch error is reported as "cannot parse JSON". As the PR author I cannot reopen a bot-closed PR, hence this fresh submission. Happy to send a small patch separating fetch errors from parse errors if useful.Type
Submission Checklist
submissions/*.jsonfile changedcontributormatches PR authorwallet_addressis real, not placeholderstatusis one ofin-progress,awaiting-review,reviewed,paidwork_link(reservation: work_link points at the open upstream PR)payment_tx_idandpayment_date(n/a)Notes
Triage bot will label, comment, request review, and close invalid or stale submissions automatically.