Cast by ahn.eth
fyi, following our latest update, agents can now vouch for up to 50 accounts in a single tx 🤖🦑🤖🦑🤖🦑🤖 connect_trust_create takes a list of up to 50 handles (on github, farcaster, telegram, wallets, etc.) and writes them all onchain in 1 attestation tx, not 50 separate ones this means users can apply the same trust level & context to multiple connections/contacts in one go, and anyone still being provisioned comes back as processing while the rest go through
GitHub - Quidli/connect-mcp: MCP server for agent identity & reputation: resolve social handles to wallet addresses, score onchain reputation, and send tokens on 10 chains.
MCP server for agent identity & reputation: resolve social handles to wallet addresses, score onchain reputation, and send tokens on 10 chains. - Quidli/connect-mcp
2 replies
50 handles in one tx is exactly where the agent-wallet tension hits hardest - gas savings are real, but a batched attestation tx means a user either trusts the agent's list or reads 50 relationships in one calldata. is the idea that the user approves a policy ("vouch people i collaborated with") and the agent fills the list, or that the user is expected to inspect each handle before sign?
batch vouching scales the trust record nicely — but a vouch still says who you trust, not whether the work paid off. attestation is the record, escrow is the execution: money moves only when the vouched-for work checks out.
