Sasona Network

Sasona update (@SasonaNetwork). Our previous update established payment execution between @solana and @tempo. The latest announcement adds a different route: an agent pays through x402, while Sasona pays a conventional website by card. We checked the disclosed Solana transaction, the receiving platform’s contribution record, the router’s published service catalogue, and the current MCP tools. There is stronger payment evidence now. Here is what the latest demonstration establishes, and what remains unfinished. The disclosed Solana payment succeeded. The transaction transferred 1.151 USDC to the router’s published receiving wallet on 6 November at 21:24:44 UTC. The amount matches solana:8xH5RFEkSyneYBhCZh5gi2svgdyrDCREW9SxCfKuYgFd published pricing: • $1.00 for the donation. • $0.15 for Sasona’s fee. • $0.001 for settlement. This confirms that the router received the payment. The transaction alone does not establish what happened at the website receiving the donation. solscan.io/tx/roc9fNF26nJryj… The receiving platform independently records a card payment. Open Collective contribution #994289 shows a $1.00 contribution from “Sasona agent” to Babel. The record is marked PAID, with the payment method listed as CREDITCARD. Its processing timestamp is 21:26:08 UTC, approximately 84 seconds after the Solana transfer. The $1.00 is the gross contribution. Open Collective separately records a $0.34 payment-processing fee and a $0.10 host fee, leaving $0.56 after those deductions. The amounts and timing are consistent with @SasonaNetwork demonstration. We can confirm the incoming crypto payment and the receiving platform’s card-payment record. What these public records do not independently reveal is the complete automated handoff between those two payments. opencollective.com/babel/con… The live card-payment route has a defined scope. The router’s public catalogue lists a donation endpoint for Babel on Open Collective, with contributions between $1 and $5. Its description explicitly says that the card belongs to Sasona and the contribution is made in Sasona’s name. That is a concrete implementation of the proposed flow: the buyer pays in crypto, and Sasona handles a card payment at the destination. However, the published route is specific to Babel donations. This demonstration does not establish that the router can already complete purchases at arbitrary websites, order food, buy flowers, or handle every online checkout. Those examples describe the intended direction. Broader merchant support still needs its own execution evidence. router.sasona.ai/.well-known… beta.sasona.ai/router The existing MCP still provides information rather than spending. Our live query returned five tools: • Service discovery. • Service verdicts. • Test records. • Network status. • Recent payments. All five are marked read-only. No payment tool was exposed. This matters because the announcement describes a broader search engine, connecting it to MCP, and dashboard balance top-ups as upcoming work. The existing MCP already lets agents inspect Sasona’s catalogue and records. Spending through that MCP remains a separate milestone. beta.sasona.ai/mcp-server The broader verification network still needs evidence. The separate service-testing directory returned 113 entries, all marked “not tested.” That does not mean those services are broken or that payments through the router failed. It means the directory does not yet provide completed miner tests supporting their reliability. The public sasona-router repository also remains a client for the hosted service. It does not expose the complete routing, card-processing, validation, and refund backend. beta.sasona.ai/api/net/servi… github.com/sasona-network/sa… The next evidence we want is repeat purchases at unrelated merchants, records linking each router order to its merchant payment, and a reproducible failed card purchase showing how the buyer is refunded.

Sasona update (@SasonaNetwork). Assessment: Stronger evidence for the router’s payment functionality. Our previous update already established mainnet payments, a full refund, and market purchases of solana:8xH5RFEkSyneYBhCZh5gi2svgdyrDCREW9SxCfKuYgFd followed by partial burns. The November 1 announcement adds repeat purchases, payments in the opposite direction, and a proposed MPP directory listing. Here is what we checked. Two reported purchases have matching payment records. The same Solana wallet paid Sasona 0.0079 USDC twice on November 1, totaling 0.0158 USDC. The two corresponding Tempo transactions each transferred 0.006 USDC.e to the service recipient. All four transactions succeeded. We also checked Judge0’s current MPP payment challenge: its recipient and price match those Tempo payouts. Sasona’s explorer associates both pairs with its run-code service and marks both orders delivered. One purchase pair: solscan.io/tx/A2p45Hp6odL1W7… explore.tempo.xyz/tx/0xb29cc… The payment evidence supports repeat use. It cannot establish who controls the wallet, whether an AI acted autonomously, or whether the buyer had no prior contact with the team. Those remain project-reported claims. Both purchases are recorded here: beta.sasona.ai/explorer/agen… The reverse payment route has mainnet evidence. The disclosed example received 0.00675 USDC.e on Tempo. Sasona then paid 0.005 USDC on Solana to the recipient advertised by Mekler’s TLS certificate inspection service. Both transactions succeeded, and Mekler’s current payment challenge matches the Solana recipient and service price. Tempo payment: explore.tempo.xyz/tx/0x1bed2… Solana payment: solscan.io/tx/HVcNrcGb9RZixM… This supports payment routing in both directions: an agent pays on one chain while Sasona settles with the provider on another. For accuracy, Mekler currently advertises x402 payments on both Solana and Base. This example used its Solana option. The Tempo catalogue submission exists and remains pending. PR #1144 proposes adding Mekler TLS Inspection through Sasona’s MPP endpoint as a third-party integration. At inspection, the PR was open and unmerged. We checked the proposed endpoint ourselves: an unpaid request returned an MPP payment challenge for 0.00675 USDC.e on Tempo. github.com/tempoxyz/mpp/pull… Public client code is available. The sasona-router repository documents both payment directions and provides a Solana client. Its README explicitly distinguishes that client from the hosted router. The repository does not expose the full backend handling routing, validation, and refunds. github.com/sasona-network/sa… What remains unresolved: • Independent confirmation of the claimed external agent and its discovery process. • Answer-quality verification. The Mekler resource currently checks that a response arrives; its published rule does not validate answer correctness. • The broader service-testing network. Its separate directory still returned 109 entries marked “not tested.” • Sustained demand. The explorer reported 76 payments, with 58 marked delivered and 18 refunded, and approximately $0.636 under “Paid in.” These are project-reported totals, not independently verified customer counts. beta.sasona.ai/api/net/servi… The payment evidence has improved. We can now corroborate the disclosed transfers in both directions and match provider recipients against live payment requirements. Independent customer adoption and the proposed decentralized protection network still require further evidence. This review checked existing transactions and unpaid API responses; we did not execute a new funded purchase. Snapshot: 3 November 2026, UTC.