Solana transaction v1 lands on mainnet this week. Your program is about to STOP WORKING. Changes are mandatory. If your code reads, indexes, sponsors or introspects transactions, something in it is about to break, and the worst failures are silent. I just shipped auditor-skill v7.3 to solanabr @SuperteamBR official repo. So an AI agent can check your repo for every one of them. Here is what changed and what to look for. v0 → v1, the short version: • Max size 1,232 → 4,096 bytes • Compute limit, data-size limit, heap and priority fee move out of ComputeBudget instructions into the message config • Unset limits default to ZERO, not 200k CU. Omit them and the tx fails • Priority fee changes units: v0 was micro-lamports per CU, v1 is a total in lamports • ComputeBudget instructions still execute, as no-ops that set nothing • Lookup tables gone, 64 inline accounts, duplicates rejected, max 64 instructions • Base58 can't carry it. Use base64 Sending v1 is opt-in. Reading it is not. Once one v1 tx is in a block: Loud: getTransaction without maxSupportedTransactionVersion: 1 errors. getBlock fails for the entire block. Wedge: blockSubscribe emits block: null and stops advancing. Forever. Silent: every indexer that finds the priority fee by scanning ComputeBudget instructions records zero. No error. Geyser plugins before 15.1.1 downgrade v1 to v0 on the wire. Old protobuf stubs drop the config field. Dangerous: a fee sponsor or paymaster that caps fees by scanning instructions binds nothing on v1. The attacker puts the fee in the config, adds harmless no-op ComputeBudget instructions to keep your scanner happy, and you sign. Repeat until the key is empty. On-chain: a program that reads ComputeBudget instructions from the instructions sysvar to enforce a fee floor is now enforcing nothing. No sysvar or syscall exposes the v1 config. What v7.3 adds: • A vuln-class playbook: fact sheet, who-breaks matrix, per-role worksheets for readers, indexers, sponsors, programs, senders, wallets • KV-135: sponsor cap bypass and disabled ComputeBudget gates • KV-136: reader wedge and zero-budget indexing • 23 checklist items across TypeScript, backend, off-chain Rust, on-chain, deployment, testing, monitoring How to use it in five minutes, two ways: Plugin (Claude Code): 1 - /plugin marketplace add solanabr/auditor-skill 2 - /plugin install auditor 3 - /auditor:audit and tell it "scope: transaction v1 readiness" No install, any agent (Cursor, Codex, Windsurf, Claude Code): 1 - git clone the repo into your project, e.g. .claude/skills/auditor-skill 2 - Tell your agent: "Audit this repo using auditor-skill, scope: transaction v1 readiness. Load references/vuln-classes/transaction-v1.md and known-vectors 135 and 136." 3 - Read the verdicts. Every item is PASS / FAIL / N/A with the file and line It is a folder of markdown. Nothing runs, nothing phones home, delete it when you are done..

Just updated the AUDITOR SKILL on @SuperteamBR solana brasil official repo here's what v7.2 adds : Solana Foundation open-sourced the tokens codebase last month. I read it as an auditor. The corpus now covers that entire stack, on-chain and off: Token registries as identity oracles. Only the mint address is identity on Solana. Symbol, name and logo are attacker-writable, and registries pick a "primary" mint by liquidity, volume and tie-breaks. All of that is farmable. New methodology for both consumers and operators. KV-132: canonical-asset spoofing and primary-variant hijack. Seed a pool, wash the volume, become "the" USDC for every app that auto-follows the list. KV-133: risk-score farming. Public thresholds, cheap inputs. A token can be grade A on market metrics and still rug through a live freeze authority the score never looked at. KV-134: Token ACL (SRFC-37) gate-program bypass. Trust the owner pubkey you are handed instead of re-deriving it from the token account, and anyone thaws anyone. Get can_freeze wrong, and anyone freezes anyone. 44 new checklist items for the modern TS monorepo: hosted auth (Clerk), issuing scoped API keys, fail-closed risk and price feeds, Next.js 16 proxy plus CVE-2025-29927, Bun and Turborepo supply chain, Cloud Run and Terraform. Governance: CONTRIBUTING, SECURITY, PR template, and CI that fails the build when any hardcoded count, index link or version drifts. Totals: 20 checklists, 1,390 verification items, 134 known vectors, 13 protocol methodologies. Free, open source, runs in Claude Code, Cursor, Codex or any agent that reads markdown.

Last year I started @DefundsFinance . About a year later, we sold the technology. At first glance, that probably sounds like an odd decision. It certainly wasn't the original plan. Here's why. The idea behind Defunds was simple: financial infrastructure will eventually move on chain. From the beginning, the goal wasn't to tokenize an existing fund or build another DeFi protocol. It was to build the infrastructure that would allow investment funds to exist natively on chain, giving institutions and asset managers the ability to offer regulated investment products with the transparency, composability and efficiency that blockchains make possible. Over the past year I spoke with fund managers, exchanges, financial institutions and many people across the industry. Those conversations changed how I think about the problem. The biggest surprise was that technology stopped being the hard part. Regulation became the hard part. As Brazil's regulatory framework evolved, it became increasingly clear that bringing a product like this to market would require much more than good technology. It would require governance, compliance, operational structure and regulatory readiness that naturally favor established institutions. That realization forced me to rethink what success actually meant. I never started Defunds because I wanted to build another startup. I started it because I wanted this technology to reach the market. Once I looked at it through that lens, the answer became obvious. If the technology had a better chance of succeeding inside an institution already prepared for this environment, then selling it wasn't giving up on the vision. It was probably the fastest path to achieving it. At the same time, another part of my career kept growing. Most people here know me because of blockchain, but I've been developing and trading quantitative strategies since 2017. In August 2022, that became my full-time professional focus through PatrInvestments. Since then, we've surpassed a 105% cumulative return and recently raised more for a new investment vehicle. Because of that growth, my priority going forward is clear: building PatrInvestments into the asset manager we've always envisioned. That doesn't mean I'm leaving blockchain. I'll continue contributing to open source security audits, staying active in the Solana ecosystem and following what I believe is the most promising infrastructure for on chain capital markets. I'm also closely following the evolution of tokenized securities in Brazil, including the initiatives being developed by B3, Anbima and CVM. I still believe the real opportunity isn't tokenization itself. It's what happens when traditional and on chain assets share the same infrastructure and the same liquidity. That's the future I'm waiting for, and when that environment exists in Brazil, I expect I'll be building in this space again. So, what happened to Defunds? The technology is now part of an important institution in the Brazilian crypto industry. Because of an NDA, I can't share the institution's name or discuss the transaction in more detail for now. I hope I'll be able to do that in the future. Looking back, I don't think the original thesis changed at all. Only the path to get there did. To everyone who followed the project, challenged ideas, found vulnerabilities, participated in audits or simply believed in the vision, thank you. Also thanks to co founder @Mattonweb3 without all his efforts would be impossible to make it happen. I genuinely believe this isn't the end of Defunds' story. It's simply the beginning of a different one. For me, the next chapter is clear. Building PatrInvestments while continuing to follow, contribute to and believe in the future of on chain financial markets.

Breaking - Brazil stocks are comming to @DefundsFinance