Add MainStreet trust scoring integration proposal#4
Open
philpof102-svg wants to merge 1 commit into
Open
Conversation
Author
|
Bumping with a few updates so it's easier to pick this up if the team has bandwidth:
No pressure on cadence. Wanted to put this thread back in the eyeline rather than open new ones. |
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
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.
Hi Gitlawb team — proposing MainStreet as a trust-scoring layer for Gitlawb's DID + bounty contracts.
Context
MainStreet is a reputation oracle for onchain AI agents on Base. ERC-8004 registered (agentId 53953). EIP-712 verifier contract on Base mainnet (
0x7397adb9713934c36d22aa54b4dbbcd70263592b). Free reads, sub-100ms.4 concrete integration points
GitlawbBounty.claim()— call/preflight/{claimer}before escrow release → block known rug deployers from claiming bountiesGitlawbDIDRegistry— every anchored DID exposesmainstreetScoreviewGitlawbNodeStaking— flag red-shielded operator wallets in node UI before delegationThis PR adds INTEGRATIONS.md documenting the 4 endpoints and integration patterns. No contract changes proposed at this stage — pure documentation. Happy to draft Solidity bindings if interested.
Observation while reading the codebase :
GitlawbStaking._harvest()line 254 hasif (info.amount == 0) return;which short-circuits before updatingrewardDebt. The internal audit report (referenced as 2026-04-20) marked this as FIXED but the pattern is still present in main. Might warrant a second look before mainnet deploy — happy to open a separate issue with a regression test if you want.Operator wallet :
0xAC3ca7c5d3cDD7702fd08F9C4C28dAA22296aDa9(Base)Source : https://github.com/philpof102-svg/avisradar