Pinned Tweet
Just released spragga - a rust implementation of the SprayList data structure - a scalable concurrent priority queue with relaxed ordering semantics.
- 🚀 42+ million operations/sec single-threaded
- 🛡️ Maintains 66K+ ops/sec even at 16 threads
github.com/maschad/spragga
.@a16zFrontier went looking for crypto's AI opportunity in payments. It found it somewhere else.
@cc_crowley says the companies building agents had a more basic worry than payments: what stops the agent from doing something nobody approved?
We've heard the same thing at Eco. It's why we built Sauce. You set where funds can go, how much can move, and what has to come back. The transaction enforces those rules as it executes. If they don't hold, nothing moves.
Teams need control over their agents before they can let them move money at scale. Onchain, Eco Sauce already gives them that. Watch our CEO @rynesaxe explain how on @thinkingcrypto.
chadnehemiah.eth retweeted
Suspending the member for six sittings is excessive. But I recognise this as the Government flexing the power of its majority.
They won’t be in gov. forever. And when the tables turn, I hope we govern with more fairness, restraint & respect for democracy than they demonstrate…
The Government used its majority in the House of Representatives to secure the suspension of Member of Parliament for St Andrew South Western Dr Angela Brown Burke for six sittings.
The motion, which condemned her conduct towards Speaker Juliet Holness, was passed after a lengthy debate on Tuesday night, during which Opposition members challenged its fairness and disputed the allegation that Brown-Burke had made physical contact with the Speaker.
jamaicaobserver.com/2026/11/…
Arc x Eco: Programmable Money with Sauce SDK teapaw.org/i/broadcasts/2mdqBZWek…
Stablecoins don’t work.
At least, not the way dollars do. When a company wires a supplier $1M, it doesn’t matter which bank sent it.
USDC on @Base and USDC on @Ethereum are convertible, not interchangeable. Pay an Ethereum-based supplier in USDC on Base, and that money is unusable to them.
Citi forecasts $1.9T in stablecoins by 2030, but warns that extreme fragmentation “will mean stablecoins are inherently non-fungible, illiquid, and counterintuitive to mass adoption.”
For that forecast to happen, a dollar sent has to be a dollar received, on any chain.
citigroup.com/global/insight…
chadnehemiah.eth retweeted
Jamaicans are just natural poets and storyteller man.....are we sure Shakespeare wasn't Jamaican?
What if your onchain transactions could think?
Sauce makes its decisions inside the transaction, so execution never waits on slow offchain systems. Combine swaps, lending, price checks, and more across 100+ protocols into one workflow that settles as a single transaction.
Learn more during the live workshop hosted by @Arc:
Arc x @Eco: Programmable Money with Sauce SDK.
Join @samconnerone and Shahrukh Rao, Head of Product at Eco, on Nov 18 at 10 AM ET for a conversation on stablecoin payments, treasury and AI agent examples.
Learn how to get started with Sauce on Arc, followed by a live Q&A.
RSVP: community.arc.io/public/even…
The Python community has lost one of its early contributors. 🕊️
Guido van Rossum, Python's creator, announced the passing of Tim Peters at the age of 74.
Peters was Python's second real user, creator of Timsort, author of the Zen of Python (PEP 20), and a member of the Python Software Foundation board for 13 years.
His contributions will live on in the Python ecosystem.
Rest in peace, Tim Peters. ❤️
You can give a coding agent the rules for an onchain transaction in plain English, and nothing settles unless every step follows them.
We asked an agent to swap 10 $USDC for $WETH and deposit it to @aave on a Base fork.
Using the eco-sauce skill, it wrote our slippage and deadline rules into the transaction as onchain checks. A short swap or a missed deadline fails the swap and the deposit together, and the $USDC stays put.
It compared 23 pools and chose the one that paid the most after estimated fees. Then it handed back the code with a trace of each step.
Read the article below to learn how to use Eco Sauce SDK with your coding agent.
What has the blockchain era been missing?
Eco CEO @rynesaxe says it’s transactions that run as full programs against the rules you give them.
Deploy the transaction, meet your requirements, all or nothing.
That’s Sauce:
chadnehemiah.eth retweeted
Barbados Prime Minister Mia Mottley warns that there’s a humanitarian crisis in Cuba: unless we all make sure that Cubans have access to basic food and energy, “we put at risk people's lives, from babies to elderly people.”
chadnehemiah.eth retweeted
One person. One agentic SEO skill with hundreds of tools and checks built in. 28x more daily search clicks for @Eco in a little over a year.
Fortune, Yahoo Finance, and even arXiv research have cited our articles, and dozens of companies have asked to be featured.
None of it was easy. All of it is replicable. Here’s how you can do it too.
I started by pulling apart every component that drives SEO growth. You’ll never know the algorithm for certain, but there’s a ton of tooling and research that gets you close. Lean on search and GEO tools like @ahrefs, @gauge_sh, @Google Search Console, and @Bing Webmaster Tools.
Backlinks, internal linking, orphan pages, content structure, search intent, answer-first formatting, freshness and fact accuracy, cannibalization between your own pages, and whether AI search actually cites you. There are so many variables, and the hard part is isolating which one actually moved your clicks.
Then, you test workflows to find articles that work. Early on it’s a high volume, trial and error game. Refresh or merge what’s decaying.
Most of these SEO and GEO tools have APIs or MCPs. Wire them in and your agents pull the data and run the audits themselves.
The most important part is having your agents monitor wins and losses, and making sure every audit produces an insight the next article builds on.
Once the skill runs faster than a human can, each loop finishes sooner and the next article starts smarter. Keep publishing, keep auditing, and it compounds. Use loops.
Ammm @conductor_build you may wanna upgrade your Virtuoso Message List key
1
8
247
The market moves between the moment you build a transaction and the moment it lands.
What can you do about that?
Eco CEO @rynesaxe talks Sauce with @lateniteonchain:
Tuesday Market Edition- The Calm before the storm? Live w/Eco, Nearkat and Morrow teapaw.org/i/broadcasts/1nJOLQMvL…
Sauce SDK lets your coding agent write onchain actions as programs. It automates swaps, deposits, and other DeFi actions together, checks each result along the way, and runs the whole sequence in one transaction.
The new tutorial from @SlavaOnChain shows how, using a swap into a lending deposit as the example:
✅ Plan: the agent compares options and picks the route that nets the most after fees.
✅ Compile: it turns the plan into SauceScript with your limits and deadline built in.
✅ Test: it runs a test to shows exactly what would happen before anything goes live.
✅ Run: every step executes atomically, and each one can use what the step before it actually returned.
chadnehemiah.eth retweeted
I am thoroughly exhausted by the intellectual gymnastics and extraordinary moral cowardice that emerge whenever Africans and people of African descent raise the question of reparations for slavery and colonialism.
Every time we discuss the transatlantic slave trade, someone rushes to remind us that Europeans were not the only people who enslaved Africans. There was the Arab slave trade, they say. Africans sold other Africans, they insist, as though they have just unearthed some extraordinary historical revelation capable of absolving Europe of centuries of organized human exploitation.
And what exactly is the argument here? That because several people participated in a crime, none of them should be held accountable? That the involvement of an African merchant somehow diminished the suffering of the African who was sold? What a spectacular bankruptcy of moral reasoning.
Yes, some Africans participated in the slave trade. Some African monarchs, merchants and elites profited from the trafficking of human beings. These are historical realities that deserve serious examination. We can even discuss the Afro-Brazilian returnees who settled along the West African coast. Some were formerly enslaved Africans who had obtained their freedom in Brazil, returned to Africa and subsequently participated in the very trade that had once deprived them of their own liberty. Joaquim d’Almeida, for example, was enslaved in Brazil, obtained his freedom, returned to West Africa and became a slave trader. Francisco Félix de Souza, a Brazilian-born merchant, built an immense commercial enterprise around the trafficking of enslaved Africans from Ouidah.
We can examine the royal families, merchant dynasties and political institutions that benefited from this commerce. We can investigate the fortunes accumulated, the properties acquired and the privileges transmitted across generations. I have absolutely no objection to holding African historical actors accountable for their participation in slavery. But now that we have identified some of the sellers, can we please return to the people who were SOLD? Can we talk about their descendants?
Can we talk about the millions of human beings whose bodies became commercial merchandise, whose children were born into captivity and whose descendants were subsequently denied access to land, education, property, political equality and economic opportunity for centuries?
The participation of an African king in the slave trade does not absolve the European merchant who purchased human beings, the shipowner who transported them, the banker who financed the enterprise, the plantation owner who extracted their labor or the governments that legalized and protected the entire system for centuries.
And then comes my favorite exhibition of historical illiteracy, the claim that Europeans today cannot be expected to pay for the sins of their ancestors. How convenient!
Apparently, nations can inherit the wealth of their ancestors, the institutions of their ancestors, the territories acquired by their ancestors, the commercial advantages secured by their ancestors and the accumulated prosperity produced by centuries of exploitation. Oh they can even compensate the slave owners for freeing their slaves. But the moment we discuss the obligations attached to that inheritance, history suddenly becomes irrelevant. You can inherit the estate, but apparently the debts buried beneath its foundations must remain with the dead.
What an extraordinary understanding of justice!
chadnehemiah.eth retweeted
Former Prime Minister PJ Patterson has slammed the Holness administration’s decision to abstain from voting on the United Nations resolution calling for an end to the embargo against Cuba as “an abominable betrayal which history will never forget”.
jamaicaobserver.com/2026/10/…
chadnehemiah.eth retweeted
Hi @arc Community ,
When @arc announced that @Eco's Sauce SDK is live on Arc, we didn't wait. We got to work right away.
On day one, we integrated Sauce into Trivo. A buy only went through if the price was at or below the limit you set. But we didn't stop there.
On day two, we connected a bot. Now all you do is pick your target price for cirBTC and sign the order, with no gas. When the price hits your level, the Trivo bot executes the buy for you and your Basket is bought automatically. No need to sit in front of the screen.
Your USDC always stays in your own Pot, and you can withdraw it anytime. Price protection is enforced by the transaction itself, not the bot: if the condition isn't met, nothing is sent.
We built it all on Arc mainnet, in Arc Studio.
We loved this system so much that we've decided to bring it to FlowFi too. ))
What should come next: sell limits or laddered buys?
🔗 Try it: trivo-arc.vercel.app
⚙️ Code: github.com/sekuler/trivo-arc
✅ First bot-executed buy onchain: explorer.arc.io/tx/0x8d05df3…
@samconnerone @bobbilee
Arc 🤝 @Eco
Eco’s Sauce SDK is live on Arc and coming soon to Arc Studio.
Build stablecoin flows with:
→ Price limits
→ Minimum amounts
→ Approved destinations
The flow executes only when every condition is met. No custom smart contracts to deploy.
Try Sauce: docs.eco.com/sdk-reference/s…





























