Skip to content

fix(reputation): the reads are public, not self-view-only + recompute throttle - #683

Closed
yggdrasilworld wants to merge 2 commits into
MergeFi:mainfrom
yggdrasilworld:fix/reputation-visibility-583
Closed

yggdrasilworld wants to merge 2 commits into
MergeFi:mainfrom
yggdrasilworld:fix/reputation-visibility-583

Conversation

@yggdrasilworld

@yggdrasilworld yggdrasilworld commented Oct 14, 2026 •

Copy link
Copy Markdown

What

Resolves #583, partially #584

Payment: Base USDC 0xD40Df5c27cEa7dd78A3c345401995c319589334e

latest/history asserted owner — a sponsor or maintainer couldn't read a
contributor's track record before assigning a bounty/team, which is the
entire point of reputation. Any authenticated user may read; only recompute
stays owner-gated.

Resolves MergeFi#583
@vercel

vercel Bot commented Oct 14, 2026

Copy link
Copy Markdown

@yggdrasilworld is attempting to deploy a commit to the chonilius' projects Team on Vercel.

A member of the Team first needs to authorize it.

The shared base carried half-written merge artifacts: an orphaned
invokeOnLockedEscrow block in escrow.service.ts, duplicated returns plus
a dead parsePagination in sponsors.controller.ts, and missing
describe/it closers in github-webhooks.service.spec.ts. Aligned each
with the intended form so the branch typechecks and its specs load.
@yggdrasilworld
yggdrasilworld deleted the fix/reputation-visibility-583 branch October 19, 2026 02:34
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.

[Regression on closed #374] reputation is still self-view-only — sponsors and maintainers can't see a contributor's track record

1 participant