Introducing Giza World Snapshots ↓
For the first time, you can watch your financial agent move onchain.
Every Giza agent navigates protocols, allocates capital, and optimizes yield in real-time.
Giza World now makes all of that visible.
Enter your agent's address to watch its journey or play around with the world itself.
Remix your colors, make it yours, and share it on X.
A group messaging app where people can build their own agents to add to their group chats
What’s even more special is that these agents can move money for you
@townsapp
latest @AntiHunterAI orchestration stack (2/28/2026):
- 2 mac minis each running @openclaw each with their own @openai codex pro accounts w/ 5.3-codex only.
- migrating direct agent prompting from telegram over to discord with channels per workstream to consolidate human/agent context
- use local codex app (5.3-codex-spark) to directly work on software projects (& fully saturate oauth token limits)
- playing with @perplexity_ai computer on side for research jobs
one Polymarket account quietly turned $50 into $435,000
no one talked about it
i reverse‑engineered it and asked Claude to build a similar bot using the same strategy
one prompt, 40 minutes, done
polymarket updates BTC contract prices slower than real price feeds
→ the bot pulls BTC predictions from TradingView + CryptoQuant
→ catches the moment when Polymarket lags by >0.3%
→ executes in <100ms before the market catches up
→ 1000+ orders per second, 0.3-0.8% per trade
risk: 0.5% per trade, 2% daily cap
it brings in $400‑700/day
runs locally no cloud, no GPU
written in Rust
how long do you think the bot era will last?
Thank you Poland 🇵🇱
First time at @cryptoeventpl, and the energy was real.
Strong local builders. Serious conversations around agents and @base. New collaborations forming.
Poland is building. LFB!
Remember the film Limitless?
Bradley Cooper takes a pill that unlocks 100% of his brain and he becomes super intelligent and goes into ultra mode
Which is exactly what using AI is starting to feel like. For a builder that's exciting… and anxiety inducing
It’s exciting because you can now be the Limitless guy.
It’s anxiety inducing because you’re now competing on a global market with millions of other Limitless guys.
So how do you win?
You win by being the most limitless version of yourself.
Don’t chase, don’t copy, don’t compromise.
Instead, look inwards and find the things that make you unique.
No one has the same combination of knowledge, skills and experience as you.
Take time to explore your curiosities and embrace what makes you weird and different.
That's the thing you need to amplify with ai.
You won’t win by being the best. You win by being the only.
Planning to apply to Base Batches?
If you want clarity on the process, positioning, and what judges actually look for, don’t guess.
Learn from someone who’s been through it.
https://t.co/mHT5k7O6cB
.@BoredElonMusk as promised @bankrbot setup with video below:
- grab your API key at https://t.co/bgBo5QOhhN
- npm install -g @bankr/cli
- bankr login
- bankr llm credits
- bankr llm setup claude
That's it. Your wallet now pays for every token. No subscription, no credit card.
When building agents, they can now fund their own compute. No human in the loop.
How to be @base aligned:
- Build apps
- Use apps
- Fund apps
Just kidding – Base is open, permissionless, and you can do whatever your heart desires
But apps are nice, let’s build more!
Now, account abstraction.
We have been talking about account abstraction ever since early 2016, see the original EIP-86: https://t.co/E4xJymAxiH
Now, we finally have EIP-8141 ( https://t.co/YD9nIpsxcC ), 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 https://t.co/sIQrtJDXLt 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 https://t.co/1cRegaXpHM ), 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: https://t.co/xzG3Jp7Yky https://t.co/WikL7gJ5qg
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).
https://t.co/p7XOgId5NN