[Support request, not bounty] SecureBanana claims pending settlement path

[Ckeplinger199]

Can someone confirm the settlement path for these SecureBanana claims, or identify the exact blocker?

Account: @Ckeplinger199
Total pending here: $4,311

Claims / PRs:

• $430 #415 / feat: allow members to use slash commands on behalf of org #76: https://algora.io/claims/YUuLZuMbqVshaAnJ ; Add original FreelanceFlow poem SecureBananaLabs/bug-bounty#415
• $780 #419 / fix: detach current_context from current_org #80: https://algora.io/claims/Hh69sYnsstaSaWfv ; Add invoice stamp pixel art SecureBananaLabs/bug-bounty#419
• $350 #424 / #1: https://algora.io/claims/a1djN5MGkDobcX3E ; Implement Stripe PaymentIntent service SecureBananaLabs/bug-bounty#424
• $750 #431 / feat: bounty claims #30: https://algora.io/claims/oH1JdesPkbQ9k4Uz ; Add reproducible API benchmark suite SecureBananaLabs/bug-bounty#431
• $2,001 #434 / feat: create bounties via GitHub app #29: https://algora.io/claims/y7Egg66fNCQ8MTcW ; Implement admin panel SecureBananaLabs/bug-bounty#434

Current receipt:

• All five claim pages have shown Status Pending / Total paid $0.
• All five PRs are open/non-draft.
• Latest check on 2026-05-26 18:50 CDT showed visible check rollups SUCCESS and GitHub mergeStateStatus CLEAN for #415, #419, #424, #431, and #434.
• Public follow-up receipt: Implement admin panel SecureBananaLabs/bug-bounty#434 (comment)
• I also sent this to info@algora.io on 2026-05-26 19:06 CDT.

Ask: please confirm whether these are payable, blocked on sponsor action, or waiting on some specific Algora/platform step. If this belongs somewhere else, point me at the right channel and I will move it there.

[Asobu01]

I can pick up #303 now.
Given "SecureBanana Algora claims pending settlement path", I will begin with reproducing the reported issue first, then applying a focused fix with clear validation.
I can post a reproducible checklist/log snippet in ~30 minutes so you can verify execution speed before the full PR.
I keep changes minimal and aligned with existing style.
Plan for this thread: repro + root-cause summary -> focused patch (plus tests/docs if needed) -> review-ready PR with validation notes.
Expected first PR: ~8h. @Asobu01

[asaadnashed]

I can take this if it is still available. I will first reproduce the issue, keep the PR focused, and include a regression test or clear verification notes before asking for review.

[Ckeplinger199]

Clarifying: this is a platform support / settlement-status question, not an implementation bounty. No PR expected here.

Looking for an Algora maintainer/platform response on whether the linked SecureBanana claims are payable, sponsor-blocked, or blocked on a specific Algora step.

[Asobu01]

Thanks for the update on #303.
I am proceeding now and will post a concrete checkpoint in ~20 minutes, then a draft PR in ~8h.

[Ckeplinger199]

48h bump on this support request.

Current status:

• Claims remain pending: $4,311 across the five SecureBanana claim URLs above.
• Algora transactions page still shows Lifetime Volume $0.00 and Total Balance $0.00 as of 2026-05-28 20:55 CDT.
• Payout account is active and can accept/withdraw payments.
• No reply from info@algora.io to the 2026-05-26 19:06 CDT email.

Ask: can an Algora maintainer confirm whether these are sponsor-blocked, platform-blocked, or in the wrong support channel?

[Asobu01]

Thanks for the clarification on "48h bump on this support request. Current status: - Claims remain pending: $4,311 across the...".
I will align with these requirements and post a concrete checkpoint in ~20 minutes (repro/logs or patch summary), then submit a draft PR in ~8h.

[sureshchouksey8]

Related SecureBanana claim status receipt for the same settlement-path question:

Account: @sureshchouksey8
Claim: https://algora.io/claims/ppch46SYtdSJ2w2c
Source PR: SecureBananaLabs/bug-bounty#2751
Parent bounty: SecureBananaLabs/bug-bounty#743

Current status as of 2026-05-31 15:09 IST:

• Algora parent table indexes @sureshchouksey8 for solution #2751 with the claim URL above.
• PR #2751 is open/non-draft, has the Bounty claim label, and update-leaderboard passed.
• GitHub reports PR #2751 as MERGEABLE/CLEAN.
• Claim page remains pending / unpaid.

Ask: if SecureBanana claims require a specific sponsor action, merge action, or Algora-side settlement step before payout, please confirm the blocker or preferred support route. If this should be a separate support issue instead of this existing SecureBanana settlement thread, I can move the receipt there.

[keilogic]

Related SecureBanana claim status receipt for the same settlement-path question:

Account: @keilogic
Total public pending claims here: $2,660

Claims / PRs:

• $750 #1966 / API benchmark suite: https://algora.io/claims/Bv5CCAxboY1Zu6jp ; Add API benchmark suite SecureBananaLabs/bug-bounty#1966
• $430 #1952 / proof kitchen poem (feat: allow members to use slash commands on behalf of org #76): https://algora.io/claims/pgh8BDyq3ZELxBsQ ; Add proof kitchen poem (#76) SecureBananaLabs/bug-bounty#1952
• $780 #1937 / ledger moonbase greenhouse pixel art (fix: detach current_context from current_org #80): https://algora.io/claims/vEgWw2DmtRh4VaUX ; Add ledger moonbase greenhouse pixel art (#80) SecureBananaLabs/bug-bounty#1937
• $700 #2638 / payment intent currency normalization (#743): https://algora.io/claims/HHcLD1gtHfyPwWh3 ; Normalize payment intent currency codes SecureBananaLabs/bug-bounty#2638

Current status as of 2026-05-31 16:25 Europe/Paris:

• All four claim pages show Status Pending / Total paid $0.
• All four PRs are open/non-draft and have the bounty-claim label.
• #1966 has benchmark-smoke and update-leaderboard successful; #1952, #1937, and #2638 have update-leaderboard successful.
• #1998 is also open with the bounty-claim label, but I do not see a public Algora claim URL for it.

Ask: if SecureBanana claims require a specific sponsor action, merge/reward action, or Algora-side settlement step before payout, please confirm the blocker or preferred support route. This is not an implementation bounty request; just adding a related public receipt to the existing SecureBanana settlement-path thread.

[auruminternum]

Related SecureBanana claim status receipt for the same settlement-path question:

Account: @auruminternum
Public pending/reward-indexed claims observed:

• #2647 / feat: allow members to use slash commands on behalf of org #76: https://algora.io/claims/LEqkuFrCbmF7tYMi ; Add FreelanceFlow proof window poem SecureBananaLabs/bug-bounty#2647
• #2652 / fix: detach current_context from current_org #80: https://algora.io/claims/bPGKq5T646Wub4vK ; Add escrow constellation pixel art SecureBananaLabs/bug-bounty#2652
• #3153 / #743: https://algora.io/claims/ZAogC6Hoeb4gfLjr ; Return defensive copies from user service SecureBananaLabs/bug-bounty#3153

Additional open bounty-claim PRs from the same account without confirmed cash receipt include #2654, #3054, #3089, #3096, #3132, #3139, #3143, #3147, and #3150 in SecureBananaLabs/bug-bounty.

Current status as of 2026-05-31:

• SecureBanana parent bounty tables show @auruminternum rows with Reward links for at least #2647, #2652, and #3153.
• The source PRs are open/non-draft and have the bounty-claim label.
• I do not have evidence of settled payment, wallet transfer, PayPal transfer, or Algora balance movement.

Ask: please confirm whether these SecureBanana Reward links are payable claims awaiting sponsor/maintainer action, blocked on Algora/platform settlement, or only pending review metadata. This is not an implementation bounty request; just adding a related public receipt to the existing SecureBanana settlement-path thread.