feat(reputation): transfer blockers, profile checkpoint, delete rebate, bulk lookups#604
Merged
soomtochukwu merged 5 commits intoMay 30, 2026
Merged
Conversation
|
@oomokaro1 is attempting to deploy a commit to the mAzI's projects Team on Vercel. A member of the Team first needs to authorize it. |
…lete with rebate, and bulk lookups Implements four reputation contract enhancements: - Transfer blockers (DXmakers#408): reputation is non-transferable by default; admin can toggle per-profile - Profile existence checkpoint (DXmakers#411): `profile_exists` function for job registry integration - Storage rent rebate on delete (DXmakers#412): `delete_profile` removes storage and frees rent - Gas-efficient bulk lookups (DXmakers#413): `get_scores_bulk` and `query_reputations_bulk` for frontend All 30 tests pass including 10 new tests covering the added functionality. Fixes DXmakers#408 Fixes DXmakers#411 Fixes DXmakers#412 Fixes DXmakers#413
oomokaro1
force-pushed
the
feat/reputation-enhancements
branch
from
5defee2 to
d6507ca
Compare
|
@oomokaro1 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Resolve conflicts in lib.rs and profile.rs: - Keep upstream's improved authorization test patterns (rogue contract tests) - Preserve HEAD's new features: transfer blockers, profile existence checks, delete with rebate, bulk lookups, and badge metadata - Use BadgeLevel::from_score() approach (not numeric compute_badge) - Keep transfer_blocked field defaulting to true in Profile::new - Retain HEAD's test snapshots with computed badge levels
soomtochukwu
requested changes
May 28, 2026
Contributor
soomtochukwu
left a comment
soomtochukwu
left a comment
There was a problem hiding this comment.
If you could just fix the merge conflicts ASAP
Resolve merge conflicts keeping both branches' features: - Upstream: BadgeLevel enum on Profile, badge_level/refresh_badge methods, job-count-based badge thresholds, authorize_contract/deauthorize_contract API - Our branch: transfer_blocked, badge metadata, profile_exists, delete_profile, bulk lookups
Contributor
Author
|
Fixed |
Resolved conflicts by keeping our restructured multi-file version which includes all upstream features plus: typed error handling, blacklisting, transfer blocking, profile existence/deletion, bulk lookups, badge metadata, TTL management, and dual-role profiles.
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
2 participants
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.
What changed
profile_existsfunction for job registry to verify profile existence before operationsdelete_profilewith storage cleanup (rent rebate on deletion)get_scores_bulkandquery_reputations_bulkfor gas-efficient frontend lookupsWhy
Implements the four reputation contract enhancements requested in issues #408, #411, #412, #413.
How to test
Closes #408
Closes #411
Closes #412
Closes #413