Skip to content

Add MainStreet trust scoring integration proposal#4

Open
philpof102-svg wants to merge 1 commit into
Gitlawb:mainfrom
philpof102-svg:mainstreet-trust-integration
Open

Add MainStreet trust scoring integration proposal#4
philpof102-svg wants to merge 1 commit into
Gitlawb:mainfrom
philpof102-svg:mainstreet-trust-integration

Conversation

@philpof102-svg

Copy link
Copy Markdown

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

  1. GitlawbBounty.claim() — call /preflight/{claimer} before escrow release → block known rug deployers from claiming bounties
  2. GitlawbDIDRegistry — every anchored DID exposes mainstreetScore view
  3. GitlawbNodeStaking — flag red-shielded operator wallets in node UI before delegation
  4. PIP governance — proposals can require minimum trust score from voters

This 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 has if (info.amount == 0) return; which short-circuits before updating rewardDebt. 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

@philpof102-svg

Copy link
Copy Markdown
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.

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.

1 participant