Attestcoin integration summary

The short version

A user creates a PortfolioSignal event on Ethereum Sepolia. Affest treats that event as an observation, not as permission to move assets. The worker waits for the source block to be attested, builds the official proof, and sends it to Creditcoin.

Ethereum Sepolia event
  -> Attestcoin attestation and proof
  -> Creditcoin proof verification
  -> Affest strategy limits
  -> approved or automatic portfolio action

What the proof gate checks

Creditcoin verifies the Attestcoin proof through the BlockProver path. Affest then checks the source receipt and event data before the strategy manager records any action.

• The source chain is Ethereum Sepolia with Attestcoin chain key 1.
• The source transaction succeeded.
• The event came from the configured PortfolioSignalEmitter.
• The event signature, user, asset, amount, and signal type match the strategy.
• The source event has not already been used.

Why this matters

The worker and an AI agent can find a signal, explain it, and prepare a rebalance. Neither one can turn an unverified message into permission to move funds. Creditcoin enforces the user's asset allowlist, amount limits, allocation rules, expiry, pause state, and replay protection.

What is real and what is limited

The proof builder uses the official @gluwa/usc-sdk, and verification runs through the official Creditcoin BlockProver precompile. The CC3 exchange adapter is a labelled 1:1 demo adapter because a supported testnet DEX route and liquidity were not confirmed. Attestcoin verification is not mocked.

For event fields, proof-builder details, and replay keys, read Proofs. For addresses and network settings, read Chains and contracts.