for agent payments, obviously a big question is how much should your agents be allowed to transact with without asking?after a lot of experimenting with my temu centaurs (the open source harnesses i built for telegram & discord on top of @quidli connect), i've now got them set up where you can configure this at the harness level:* unlimited, execute immediately after prompt* limited, confirm txs w/ operator, either on every single tx, or any over a certain amount* confirm only when you're replying to someone else's message, since their texts could steer the agentthis way the harness' code enforces your choice, not the AI, so a cleverly worded message can't influence otherwiseroll your own, hosted or self-hosted, and see for yourself:* telegram: http://github.com/justinquidli/telecentaur* discord: http://github.com/justinquidli/discocentaur* [quidli](http://github.com/justinquidli/discocentaurquidli) connect: http://connect.quid.li

been getting questions on the trust graph implementation (built on ethereum attestation service on base) so put together this https://skill.mdbasically @quidli connect already enables your agents to know your contacts' social handles; now it lets them know which accounts you actually trust tooi can tell my agent, "@guillaumeth on farcaster is my teammate, full trust" or "justin@https://quidli.xyz is the email address of a contractor i work with, score him 80," these are then saved onchain so that any agent i use can check before paying someone or taking requests from themtrust levels ("full trust" or "xx/100") are self-assigned so you can use your own standards, which gets really useful as your agent transactions start to scalehttps://github.com/Quidli/connect-mcp/blob/main/docs/skills/connect-trust/SKILL.md

what's an onchain trust graph good for?example, an account joins your telegram group chat posing as someone you know well, using their name & photo, and then asks you for moneyit feels a bit off so you ask your agent running @quidli/connect-mcp to verify; and when it checks your trust graph it can read that this account isn't your contact who you've got registered at "full trust"names & photos can be copied, but the trust you establish onchain to someone's real accounts can'tgive your agent the same check: `npx -y @quidli/connect-mcp`

onchain trust made portable across your offchain group chats ⛓️🦑🤖with an attestation i created on claude code, my agents (TeleCentaur on claude sonnet, in this case) now knows who i can trust, even in a busy telegram group chat, without documents or biometrics, no central store of identity data, while letting everyone stay pseudonymousjust like with payments, you can agentically drop attestations, built on EAS on base, across your contacts and then you/your agent can use these graphs to decide who gets paid, who gets access, or which strangers to ignoreanyone can build on it and any app or agent with a @quidli connect key can read the same graph across platforms instead of building your own, no custom bot code necessary

testing a new tool update to @quidli/connect-mcp in prod: /connecttrustcreateestablish onchain attestations to your contacts to further inform your agents who your connections actually are, built on top of ethereum attestation service on basebefore, my agents could infer that guillaume and i have a relationship from our connect profiles, ex. via our linked email addresses sharing the same domain; but now i can take a step further and create my own trust graph that my agents can reference onchain when "reading" him: full trust (level 100) & that he is my co-foundercontinuing to find more ways to enrich your existing social graphs by enabling you to encode them over onchain at @quidli

i liked the 1-2 punch of bankr + @quidli so much that i bolted bankr tools onto Disco- & TeleCentaur 🤖🦑link your bankr + quidli keys so that your agent can swap/buy a token & send it to your contacts by their social handles, all from a single prompt on Discord or Telegramdefi taken care of by bankr, agentic payments on top of socials by quidli, all by a bot you host yourself

experimenting with social based agentic payments for invoices this morning - integrated this flow into our discord via discocentaur (of course, built on top of @quidli):operator receives invoice from vendor > operator uploads invoice + acknowledges services rendered to agent > agent reviews file, validates details w/ operator > upon confirmation (which isn't necessary but i included), agent executes payment in USDC to vendor tied to the email address provided on invoice (no wallets or web3 tutorials required)obviously the recipient needs to be ok with receiving payments onchain, but still pretty cool to stitch this all together end-to-end in less than an hour while drinking coffee

wired up bankr + @quidli on claude code - pretty fun to watch the agent use all the tools at its disposal to send some $BNKR to the most recent contributors to bankrbot's open 'skills' repo on githubmy prompt: "buy 2 USDC of BNKR and send 100 BNKR to everyone that's contributed to https://github.com/BankrBot/skills this past month"agent proceeds to use my bankr account to swap for BNKR, then resolves all the qualifying contributors on github to wallets generated for those users via quidli and sends BNKR to my quidli smart wallet to execute the payments directlyonly hitch was a miscalculation on the price of BNKR so the agent paused to ask me for permission to spend more (which it ended up not doing because it realized its error) 🤣

reminder that @quidli/connect-mcp is an mcp server that resolves social handles to evm & solana wallet addressesadd it to your app, client or agent and it can:- resolve social handles (farcaster, x, github, discord, telegram, linkedin, email and or phone number) to evm & solana addresses
- generate new wallets for social handles that have none configured
- run reputation checks on accounts before executing onchain txs
- autonomously send tokens to verified accountsopen repo:

fyi, you can build most of this very easily with @quidli connect, even self-host the whole thing if you'd rather not trust anyoneyour email/social handle of choice is just so you can authenticate + no banking details at allrun it hosted or locally, your keys, your wallets, try it out: `npx -y @quidli/connect-mcp`