Skip to content

JhiNResH/maiat-protocol

v0.1.2 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Affected surfaces

auth breaking_upgrade

Summary

AI summary

updateTokenScore() now requires five parameters and redeployment is required.

Full changelog

🛡️ Trust Score Hardening

Seed Protection (Contract)

  • TrustScoreOracle: new DataSource enum (NONE/SEED/API/COMMUNITY/VERIFIED)
  • TrustGateHook.beforeSwap(): rejects swaps where token score is from seed data
  • Requires redeploymentupdateTokenScore() now takes 5 params

Weight Alignment

  • Shared scoring-constants.ts — single source of truth for trust weights (0.5/0.3/0.2)
  • computeAgentTrustScore() and trust API use shared constants

isStale Timestamp Logic

  • isStale() returns true if score > 24h old (replaces always-false placeholder)
  • Trust API response includes trust.isStale boolean

Other

  • Restored /swap page (trust-gated swap UI)
  • Version aligned with @jhinresh/[email protected]

Tests: 62/62 Foundry ✅ · 54/54 Vitest ✅

Breaking Changes

  • `TrustGateHook.beforeSwap()` rejects swaps with seed-derived token scores; `updateTokenScore()` signature changed to require five parameters, necessitating redeployment of the contract.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track JhiNResH/maiat-protocol

Get notified when new releases ship.

Sign up free

About JhiNResH/maiat-protocol

Trust infrastructure for the agent economy. 4 tools: agent trust scores (18K+ agents indexed)

All releases →

Beta — feedback welcome: [email protected]