Igor Walter

#1 no Hackaton da @0xMantle organizado pela @odisealabs gracias!

Será que a diferença entre o bot e o agente é a LLM por trás do agente? No conceito é tudo a mesma coisa, um bot é um agente de software.

Curioso e inútil.

that is important for stocks tokenization, which is a +$1B market as data from @RWA_xyz app.rwa.xyz/stocks

@felixprotocol @OndoFinance @grok is there any news about this? is it online at @felixprotocol ?

Felix x Ondo Felix will soon deliver spot equities to users in collaboration with @OndoFinance. Through Felix’s integration with Ondo Global Markets, Felix users will be able to: >Access 100+ US equity markets directly through trade.usefelix.xyz at launch (expanding to 1,000+ equities over the coming months) >Trade spot equities onchain with tradfi-level liquidity 24/5 >Borrow against spot equities on Felix (coming soon) Felix spot equities will not be hindered by AMM liquidity like previous onchain equity products due to our implementation with Ondo. Buyers/sellers will be able to get tradfi-level execution on multi-million dollar equity orders Day 1. Ondo Global Markets holdings are publicly and regularly audited to demonstrate overcollateralization. Ondo provides daily public attestations, a bankruptcy-remote legal structure, an insurance fund, and multiple smart contract audits. This approach to security and transparency is in large part why Felix is working with Ondo. More details on rollout will be shared soon.

"os agentes de IA são [...] dragões: atravessam barreiras competitivas, comprimem margens e desafiam modelos de negócio estabelecidos." Kinea e você, está treinando seu dragão? kinea.com.br/blog/carta-do-…

Now, account abstraction. We have been talking about account abstraction ever since early 2016, see the original EIP-86: github.com/ethereum/EIPs/… Now, we finally have EIP-8141 ( eips.ethereum.org/EIPS/eip-8141 ), an omnibus that wraps up and solves every remaining problem that AA was intended to address (plus more). Let's talk again about what it does. The concept, "Frame Transactions", is about as simple as you can get while still being highly general purpose. A transaction is N calls, which can read each other's calldata, and which have the ability to authorize a sender and authorize a gas payer. At the protocol layer, *that's it*. Now, let's see how to use it. First, a "normal transaction from a normal account" (eg. a multisig, or an account with changeable keys, or with a quantum-resistant signature scheme). This would have two frames: * Validation (check the signature, and return using the ACCEPT opcode with flags set to signal approval of sender and of gas payment) * Execution You could have multiple execution frames, atomic operations (eg. approve then spend) become trivial now. If the account does not exist yet, then you prepend another frame, "Deployment", which calls a proxy to create the contract (EIP-7997 ethereum-magicians.org/t/eip-7997-det… is good for this, as it would also let the contract address reliably be consistent across chains). Now, suppose you want to pay gas in RAI. You use a paymaster contract, which is a special-purpose onchain DEX that provides the ETH in real time. The tx frames are: * Deployment [if needed] * Validation (ACCEPT approves sender only, not gas payment) * Paymaster validation (paymaster checks that the immediate next op sends enough RAI to the paymaster and that the final op exists) * Send RAI to the paymaster * Execution [can be multiple] * Paymaster refunds unused RAI, and converts to ETH Basically the same thing that is done in existing sponsored transactions mechanisms, but with no intermediaries required (!!!!). Intermediary minimization is a core principle of non-ugly cypherpunk ethereum: maximize what you can do even if all the world's infrastructure except the ethereum chain itself goes down. Now, privacy protocols. Two strategies here. First, we can have a paymaster contract, which checks for a valid ZK-SNARK and pays for gas if it sees one. Second, we could add 2D nonces (see docs.erc4337.io/core-standards… ), which allow an individual account to function as a privacy protocol, and receive txs in parallel from many users. Basically, the mechanism is extremely flexible, and solves for all the use cases. But is it safe? At the onchain level, yes, obviously so: a tx is only valid to include if it contains a validation frame that returns ACCEPT with the flag to pay gas. The more challenging question is at the mempool level. If a tx contains a first frame which calls into 10000 accounts and rejects if any of them have different values, this cannot be broadcasted safely. But all of the examples above can. There is a similar notion here to "standard transactions" in bitcoin, where the chain itself only enforces a very limited set of rules, but there are more rules at the mempool layer. There are specific rulesets (eg. "validation frame must come before execution frames, and cannot call out to outside contracts") that are known to be safe, but are limited. For paymasters, there has been deep thought about a staking mechanism to limit DoS attacks in a very general-purpose way. Realistically, when 8141 is rolled out, the mempool rules will be very conservative, and there will be a second optional more aggressive mempool. The former will expand over time. For privacy protocol users, this means that we can completely remove "public broadcasters" that are the source of massive UX pain in railgun/PP/TC, and replace them with a general-purpose public mempool. For quantum-resistant signatures, we also have to solve one more problem: efficiency. Here's are posts about the ideas we have for that: firefly.social/post/lens/1gfe… firefly.social/post/x/2027405… AA is also highly complementary with FOCIL: FOCIL ensures rapid inclusion guarantees for transactions, and AA ensures that all of the more complex operations people want to make actually can be made directly as first-class transactions. Another interesting topic is EOA compatibility in 8141. This is being discussed, in principle it is possible, so all accounts incl existing ones can be put into the same framework and gain the ability to do batch operations, transaction sponsorship, etc, all as first-class transactions that fully benefit from FOCIL. Finally, after over a decade of research and refinement of these techniques, this all looks possible to make happen within a year (Hegota fork). firefly.social/post/bsky/qmaj…

It is great to know we have @aave at @0xMantle

@KSimback I would think to do something for people who do not know how or can not afford to run an agent. Some time ago there was the Search extra terrestrial intelligence (SETI) to use spare processing capacity.

I’ve built some really good agents, but don’t use them all 24/7 - how can I monetize the downtime? Seen some agent marketplaces (Fiver for agents), but what if I want it to partake in something higher stakes? Go play poker, trade crypto, arb prediction markets… Make this easy

depósitos em euros na @SaildotMoney sail.money/apps/sail/home…

@SaildotMoney @circle @base that is really great news! I have my Sail account that is USD based. now I want to hedge EUR. However if want Sail to keep the EURC in EUR, I need to create another account, right? is it possible to keep EURC deposits in the old account frozen in EURC ?

The Euro just went agentic! ⛵️ $EURC by @circle is live on Sail @base. Deposit today → Earn up to 20% APY, fully autonomous.

se você está interessado no universo de agentic AI deveria conhecer @SaildotMoney é um agente de IA que otimiza a aplicação do seu portfólio. não precisa ser cripto nativo, pode usar gmail. depositei um punhado de dólares e está rendendo 6% ao ano. sail.money/apps/sail/home…

se você está cético com @openclaw ... bem, talvez seja a hora de repensar. a @a16z está acompanhando de perto. #myopenclaw

antes de se aventurar por mares revoltos, saiba onde está entrando... news.northeastern.edu/2026/02/10/ope… #myopenclaw

@openclaw pense bem sobre o que vai dar acesso ao @openclaw fonte: aimaker.substack.com/p/openclaw-sec… #myopenclaw

@openclaw se você ainda pensa que isso pode ser rápido... 3 camadas de segurança (até camada 2 é suficiente). Realistic Time Expectations Tier 1: 3-4 hours on a weekend afternoon Tier 2: +2 hours setup, then 30-45 minutes monthly maintenance fonte: aimaker.substack.com/p/openclaw-sec… #myopenclaw

Hoje comecei uma jornada na inteligência artificial agêntica (agentic AI), dando os primeiros passos para instalar o @openclaw Por enquanto, usei copilot para ter certeza que meu Mac Air de 2020 aguenta o tranco afinal não teria como comprar um Apple Mini pra isso. #myopenclaw

Aave vai financiar energia solar.