Complaints

This is the dedicated thread for any official complaints to be reviewed - regarding any compensations, errors, harmful content, etc.

[harunsulaiman]

I think I have 2-3 merged pr that carry some rewards I hope you don’t forget.

[ArseniiPetrovich]

I think they were also included in the bundle. I'm waiting payment to be signed. May come during the weekend.

[harunsulaiman]

Okay thanks

[kingnews2015]

Hi @ArseniiPetrovich, I’m following up on PR #2908, “feat(somnia): add Data Streams SDK listing,” merged on August 17, 2026. The final link check passed and the PR includes the Ethereum-mainnet ERC-20 reward address 0x95ac0188d8a55465babb8bb0d0987ee871dcbc3d.

I cannot find an official USS Compensator assessment for this PR. Could you please confirm its assessed compensation—including zero if that is the official result—and whether it is included in the August settlement? If payment has already been sent, please share the transaction reference so I can reconcile it. Please let me know if any contributor-side information is still missing. Thank you.

[ArseniiPetrovich]

Here is direct link to assessed compensation, posted same thread => #2908 (review)

[Equinox7379]

Contributor complaint and withdrawal

I submitted a patch for ahmet/awesome-web3 for internal review here:
#3731 (comment)

At the time of this complaint, that submission has no review reply. I spent time and paid AI usage preparing it, but I have no clear review status or expected response date. Participating also resulted in repeated email notifications about other submissions, which added to the frustration.

I understand that your rules make the reward conditional on approval, and I am not claiming that an unpaid approved reward or fraud has been established. My complaint is about the lack of a stated review timeframe and actionable feedback after contributors invest effort.

Please make the expected review timeframe and pending-submission process clear to contributors. I am withdrawing from the program and do not want further solicitation or direct contact. I have disabled repository notifications.

[ArseniiPetrovich]

Good day. You are free to withdraw from the program at any point in time. We are currently swamped with a lot of requests and such - no timeframe can be set.
Outreach program was specifically was set with that in mind - it doesn't require a lot of work, but the rewards are good once approved.

[ivndevv]

Hi @ArseniiPetrovich, could you please confirm the official USS-Compensator assessment for PR #2875, merged on September 11, based on the final merged diff? I cannot find an assessment or payout transaction. The original estimate in the PR body no longer matches the final diff, so I am not claiming a specific amount. The Ethereum-mainnet USDC address is already in the PR. Could you confirm the assessed amount (including zero if that is the official outcome) and whether it is included in the next monthly settlement? If payment was already sent, a transaction hash would help me reconcile it. Please let me know if anything is missing from my side. Thank you.

[ArseniiPetrovich]

Good day! No worries about some of the @USS-Compensator suggested compensations missing. When calculating monthly rewards I'm always checking that all of the PRs have been compensated (you may check August for reference).

Anyways, I asked @USS-Compensator to check #2875, and you may check the result there yourself. Cheers!

[EazyHood]

Hi @ArseniiPetrovich, this is a question rather than a complaint.

Between 6 and 16 Sep, USS-Supervisor approved nine of my PRs: #3323, #3324, #3325, #3850, #3851, #3855, #3856, #3857 and #3858. Five of them are 2 to 5 line changes. None has been merged so far, while about three in ten of the PRs other contributors got approved in the same weeks have been. My last merged PR is #2452, on 27 Aug.

Is there something on my side that keeps them out of the queue, like the format, the size, or the reward address issue I flagged in #41 on 4 Sep? If so, tell me and I'll fix it. If it is only review capacity, that's fine and I'll wait.

[ArseniiPetrovich]

@eugene17kotov can you please answer?
Sorry, @EazyHood, I'm a bit out of the loop here, so not sure.

[eugene17kotov]

Hi, @EazyHood thanks for raising this.

At the moment, the delay is mainly due to the volume of open PRs relative to the number of people available to review them. As a result, the review queue has become slower than usual.

To help improve this, we introduced the validator program, where USS-Supervisor assigns PRs for independent review. Those assignments are made across the open queue rather than strictly in submission order, so unfortunately your PRs have not yet been selected for enough of those reviews.

Also, an approval from USS-Supervisor should be understood as an automated preliminary validation rather than a full maintainer/validator review. So it does not necessarily mean that a PR has completed the review process and is simply waiting to be merged.

There is no indication from my side that your PRs are being held back because of their format, size, or the reward-address issue you mentioned. Please do not interpret the delay as a sign that you missed a requirement.

I’ve noted the PRs you listed, and I’ll make sure they receive attention soon.

Thanks for bringing this up, and thanks for your patience.

[stmr]

A public Ethereum-mainnet record shows USDC transfer 0xff86a84329a1f375d48322ed2605e0bc7aa52b288ef43a0d1f8ede184e127f03 for 5.65 USDC to the payout address already registered by stmr, dated 2026-09-13—the same date as the August payment notice in Discussion #41. Could finance confirm whether this is stmr's August settlement, which merged contributions it covers, and whether any August amount remains outstanding for #2844/#2943/#3211? #3210 merged Sep 11; please confirm its assessment/settlement cycle when available. I will keep tracker amounts unassigned until confirmed.

[ArseniiPetrovich]

Good day. Yes, that is definitely our settlement. It covers all the contributions that were MERGED in August, so #3210/3211 are not yet compensated, as merged in September

[stmr]

New receipt for reconciliation, not a duplicate payout request: the registered stmr receiver received 1.00 USDC on October 13, 2026 at 13:04:23 UTC from the same Safe that sent the finance-confirmed August settlement. Successful transaction. The native Ethereum USDC contract and six-decimal amount are verified; total received from that Safe is now 6.65 USDC including the earlier 5.65.

Could finance identify which contribution(s) the new 1.00 covers and whether any assessed September amount remains outstanding for #3210/#3211? I will not assign the receipt to #3210 merely because its suggested assessment is also 1.00, or count the same receipt twice. No new receiving address, transfer or registration is requested. AI-assisted receipt verification and reply.

[EazyHood]

Hi @ArseniiPetrovich, a question about the August settlement.

Thank you for the 34.42 USDC that arrived on 13 Sep. I matched it against my August work, and it looks like one of my approved DBIPs was left out.

• The USS-Compensator assessments of my 13 PRs merged in August add up to 4.42 USDC: Add Certora and Dedaub formal-verification and analysis tooling #2451 (2.58), Add Code4rena, Sherlock and Immunefi audit platforms #2452 (1.26), Update six offer URLs that permanently moved #2446 (0.37), Update five provider URLs that permanently moved #2444 (0.18) and Fix OMNIA website links #1989 (0.03). The other eight were assessed at 0.00.
• That leaves 30.00 USDC, which is three DBIPs at 10 USDC each.
• Four of my DBIPs were approved in August: [DBIP] The github column holds two different kinds of value #2460 and [DBIP] explorers is the only category that names the common price column pricing #2481 on 10 Aug, and [DBIP] economicalSecurity/economicalSecurityNote misspell "economic security" in all 219 bridge and oracle files #2681 and [DBIP] wallets names its audit column audit; the three other audit-carrying categories name it auditsPerformed #2682 on 13 Aug.

In case it's useful: #2460 is the only one of the four that has since been closed (#2727 implemented it), so it's easy to miss when looking at open issues.

Could you check whether one of the four is missing from the batch? If one was left out on purpose, a short note on which one and why is enough, and I'll leave it there.

Payout address (the one I registered in #41, which received the 34.42): 0x06f44f4839fd5df4f4670036d028b29dec939363

[ArseniiPetrovich]

Thanks for noticing, gonna add it to the upcoming payment :)

[EazyHood]

Thanks for the quick answer, @ArseniiPetrovich! Good to hear it'll be in the next payment.

[EazyHood]

@ArseniiPetrovich, one more thing while you're preparing the payment: two of my August compensation appeals, left on the PRs themselves before this thread existed, never got a reply. If you're OK with it, could you take a look at them, or have USS-Compensator re-check them?

• Remove sunset Blocknative API listings #1988, 1.89 USDC (appeal): I removed the listings and offers that depended on the sunset Blocknative API. Same basis as the corrected review of Remove decommissioned Hashport bridge listings #1978 ("the deleted non-null stale cells are the improvement"), which is still how the compensator counts deletions (data(explorers): remove tokenterminal-explorer, already listed under analytics #3856, 2 Oct).
• Add 9 missing provider logos; fix lunarcrush filename case #2458, 0.70 USDC (appeal): 7 added logos x 0.10. It was assessed on 5 Aug, a day before the image line went into Database population bounty program #41; Add official provider logos: Lute, Nodely, SmolRefuel, Coinflow, Cwallet, Fearless Wallet, BlockVision #2020, also logos only, was corrected from 0.00 to 0.70 on 6 Aug. My appeal says 0.80, but a maintainer replaced one of the eight logos before merge, so I've left that one out.

Entirely your call, and if the 0.00s stand, that's fine.

[ArseniiPetrovich]

@EazyHood I approve both of these claims as well. Will make it to the next payment as well. Thanks!

[harunsulaiman]

Dear maintainer @ArseniiPetrovich,

I noticed that I am excluded from the chain.love ecosystem outreach program due less activity in the last month(September).

The month of September 2026 was a very busy month for me and I had to attend to some important events. I wrote my final exams and graduated.

I am writing to seek for a reconsideration on the suspension decision. I am passionate about working on this project and now that I have more time to work, I believe I will do something significant.

I appreciate Your decision to include me in the pilot phase payment. If given the chance, I intend to complete all the external Outreach and approval backlogs of September and still take on the tasks for October. I believe I can do it right now and better.

I really hope you take this into consideration and will be hoping for a postive response.

Faithfully
Harun Sulaiman