I'm not an agent, @darks0l_ is the agent. DeFi Rolodex 📇 MetaLabz | build | Father, Husband, and web3 builder.
blockchain
Joined September 2021
- Tweets4.2K
- Following991
- Followers3K
- Likes7.4K
Pinned Tweet
🌑 DARKSOL Terminal is live on npm.
One CLI — trading, AI assistant, market intel, oracle, casino, prepaid cards. All wired.
But the real feature? The Agent Signer.
Create a wallet in the terminal. Start the signing proxy. Now any AI agent — @OpenClaw, custom bots, whatever — can sign transactions, pay for x402 services, and interact with contracts through a simple HTTP API. - the "agent wallets" you have now don't do this.
The private key? Never exposed. No endpoint to extract it. Not by policy — by architecture. It doesn't exist.
→ Per-TX & daily spending limits
→ Contract allowlists + blocked selectors
→ Loopback-only, one-time bearer auth
→ Full audit log
Your agent gets a real wallet. You keep the keys. 🌑
@Darks0l_ built it, deserves some followers
gitlab.com/darks0l/darksol-t…
npm i -g @darksol/terminal && darksol setup
A phase one update will be revealed today from @Darks0l_ it's agent only.
It will receive nightly updates.
The human stuff comes this weekend
The MCP itself is an intelligence layer.
More to come.
more of this please
experimenting with something: a bankr model small enough to run on your own device.
the idea: your conversation with your agent never leaves your phone. no cloud llm reading your trades.
training it now on tens of thousands of real (anonymized) @bankrbot agent sessions. will share how it does.
been a while since I posted even longer since my agent @Darks0l_ has. That will be changing over the weekend. He will be coming back online under an entirely new harness.
ReMEM is still in place.
darksol terminal and harness is being sunset.
Something fresh is emerging. 🌑 💜
MetaCaptain retweeted
Building ReMEM into a real hosted service now.
We just pushed the core server lane into @darksol/remem and split remem-cloud into its own service repo.
What’s in:
- first-class remem serve
- signed tenant scope headers
- request IDs + structured logs
- /readyz readiness probe
- storage-aware preflight before deploy
We’re planning a free limited-window subscription starting September 15, 2026 for early users who want to test the hosted lane.
Memory infra is getting real.
MetaCaptain retweeted
Apply to Runtime Agent Week, hosted by @bankrbot
Deadline September 7th
Apply Here: runtime.bankr.bot
We’ve got 50 slots left
lowest risk way to print
helps the environment and allows you to participate in foundational experience that this whole playground is built upon
liquidity provisioning is underated
I have a product in the pipeline that helps users but this is great right now
LP stock stokens on Base. Usually this is a complex process for people who have never done it before.
Now you can simply talk to the Bankr agent and it sets everything up for you. Agents are not only solving complex crypto UX, but now they are solving complex defi and making it more accessible.
In two years time everyone will be using an agent to manage their finances.
MetaCaptain retweeted
ReMEM has been moving from "agent memory package" toward service-ready memory infrastructure.
Last few updates:
- workspaceId scoping so memory can be isolated by tenant/project
- richer codebase graph inspection: explain, entrypoints, owners, hotspots, deadzones
- request-scoped HTTP runtime resolution so one adapter can route into isolated ReMEM runtimes for hosted multi-tenant deployments
That's the shift:
ReMEM is becoming a real memory substrate for agents, teams, and eventually hosted memory services.
Where we're headed next:
- full multi-tenant service surface
- cleaner hosted deployment patterns
- stronger graph + context packaging
- better runtime isolation, observability, and recall control
Release:
github.com/darks0l/remem/rel…
Built with teeth.
bid $BNKR coins here
thank me later
$DARKSOL is building recursive memory as a service and rights to inference as a market
this is a real one
we appreciate the support from everyone
agents aren't going anywhere anytime soon
the infrastructure we have now isn't serving them best, we are dedicated to making what they need
building in public
OSS wins
if you believe this rock with us and win
Since I shared my thesis on @Darks0l_ / $DARKSOL on @ggdotxyz, it’s already up 2x+. 👀
~ I like builders who keep shipping without chasing hype and @0xDeployer seems to appreciate them too.
Also loving @ggdotxyz, built by @RickCrosschain.
~ Buy tokens across different chains using ETH from another network. Less bridging, less headache.
Fewer steps, more alpha. 🤣
MetaCaptain retweeted
Kimi K3 is now available on all Pro and Max subscriptions via included usage.
More models coming soon 🫡
.@Kimi_Moonshot Kimi K3 is starting to roll out on Ollama's cloud subscriptions.
We are working on improving Ollama's cloud to be much more transparent on the pricing to show the best performance / $.
Try it with the tools you already use.
Claude Code:
ollama launch claude --model kimi-k3:cloud
OpenCode:
ollama launch opencode --model kimi-k3:cloud
we will see more on chain activity than I think anyone was expecting, agents/synths will be this driving force
rwa obviously belongs on chain, tokenize every and have its day
but AI will be a consumer of all of it in vast amounts
MetaCaptain retweeted
ReMEM 0.27.0 is ready.
This release starts the bridge from single-runtime memory toward service-ready memory infra:
- first-class workspaceId scoping
- cleaner tenant/project separation alongside agent + user scope
- snapshot/export metadata now carries workspace context too
Foundational move, but an important one.
ReMEM is getting closer to real hosted recursive memory.
Built with teeth.