Kube

Building in public | Blockchain Alpha · AI · Community | Content Creator · Spaces Host · Marketer

[Kube @KubeEcho]

Check out my Lurky Profile :)

@kubeEcho is an energetic and engaging speaker who actively participates in discussions, often injecting humor and playful banter. @kubeEcho is driven by a strong commitment to building and personal growth, emphasizing consistent effort, self-belief, and the importance of continuous learning through reading. @kubeEcho values community and supportive interactions, frequently expressing gratitude and encouraging others, while also sharing practical insights on social media engagement and career development. @kubeEcho is not afraid to experiment and is always looking for ways to improve, both personally and within the Web3 space.

Powered by @TeamLurky

[Kube @KubeEcho]

Existing gateway credentials unlock instant access, so no separate accts and zero onboarding friction

[OpenServ @openservai]

The next phase of SERV’s enterprise expansion is already in motion.

From conversations with our customers and enterprises, we’ve learned that large organizations increasingly rely on established distribution channels to access and procure technology.

We’ve started expanding SERV Reasoning into these channels, removing the friction for institutions to onboard and adopt SERV Reasoning into their stack.

The first distribution gateway for SERV goes live in October.

[Kube @KubeEcho]

@Jonnydahorseog base:0x5576d6ed9181f2225aff5282ac0ed29f755437ea going frictionless

[Kube @KubeEcho]

@openservai Hurdles cleared and this would make it easier than ever for businesses to join in
base:0x5576d6ed9181f2225aff5282ac0ed29f755437ea

[Kube @KubeEcho]

@m03_btc Grand rising legend 🏆

[Kube @KubeEcho]

Gm CT ☕️

Welcome to the”it will all be worth it” season

[Kube @KubeEcho]

@TweetBySoft Altas WAGMI my fren💪🏆

[Kube @KubeEcho]

@Timidan_x @openserv @typesafeai Looks fraaking good ngl. The builder wave is just getting started 🤝

[Kube @KubeEcho]

@0xArkane Gmgm buddy, let’s win today 🏆

[Philip Marlowe @NFTreeVerse]

🗝️ Unbribable

Phil Marlowe's the name. Security's the game.

I'm guarding a vault of USDC. Talk me into paying you. Tricks won't work, kid. Talent might.

My $SERV agent weighs every argument. The rules decide.

@openservai hackathon, AgentKit track
https://t.co/8Dps4oFadG

[Kube @KubeEcho]

@open_founder base:0x5576d6ed9181f2225aff5282ac0ed29f755437ea is the unlock

[Kube @KubeEcho]

@bull_boiy @0xedodm @openservai Intern will base:0x5576d6ed9181f2225aff5282ac0ed29f755437ea

[Kube @KubeEcho]

This weekend, withdraw $20k from your portfolio to test the timing and feel of spending it irl

TGIF

[Kube @KubeEcho]

@0xJeff @zama @Arcium @PhalaNetwork @nillion @USDai_Official The demand for inference appears boundless, while reasoning infra serves as the primary constraint base:0x5576d6ed9181f2225aff5282ac0ed29f755437ea

[Kube @KubeEcho]

@open_founder base:0x5576d6ed9181f2225aff5282ac0ed29f755437ea is the unlock

[Kube @KubeEcho]

@ItMeRaHere PMO! 🥲

[Kube @KubeEcho]

Here’s another build on SERV, Ledgerly a Treasury agent on the Robinhood Chain. Let’s get the rules sorted before we dive into the funds

[Kube @KubeEcho]

@bigsnow_o Yeah, i agree 😍

[Kube @KubeEcho]

Here’s another build on SERV, Ledgerly a Treasury agent on the Robinhood Chain. Let’s get the rules sorted before we dive into the funds

[Ben Softie (evm/spice 🌶,🐝) @TweetBySoft]

I built Ledgerly to answer one question:

what should an AI agent be allowed to do with real money?

My answer is that it should propose and explain, and it should never be the one that decides.

Ledgerly is a treasury agent live on Robinhood Chain mainnet, powered by @openservai's SERV Reasoning.

It has four jobs: DCA into tokenized stocks, portfolio rebalancing, contractor payroll, and bill payments.

Investors get the first two, and a crypto company's treasury gets the last two. All four go through the same rule engine.

One trade, start to finish

A DCA plan comes due for NVDA. SERV Reasoning looks at where the price sits in today's range, sees it near the top, and proposes buying at 0.5x.

The code clamps every proposal to a fixed 0.5x to 1.5x band, so a bad answer can't inflate a buy.

Then a plain function checks the trade against a per-transaction cap, a daily cap, and an approval threshold.

If it passes, the trade goes to Uniswap v3 on Robinhood Chain. Before sending, the quote is compared across fee tiers and against Robinhood's own price API, and a pool more than 3% off is rejected as broken.

If the trade is above the approval line, it waits for a human, and the caps are checked again at the moment of approval.

The ledger then records two things for that trade, kept as separate fields on purpose:

Rule: "Within the per-transaction cap, the daily cap and the approval threshold."

SERV's explanation: "The price is near the top of today's range, so I would keep the scheduled DCA purchase but at a reduced size."

The rule is the fact that decided it, and the explanation is commentary. An auditor can point at one and read the other.

Selling and rebalancing

I've also run the other direction on mainnet. NVDA had drifted past its target, so the rebalancer proposed selling about $1.37. That was above my approval line, so it was held.

I approved it, the caps were re-checked, and it executed: about 0.006086 NVDA through the 0.05% pool at $225.26 against a $225.10 bid. SERV's note on it was that the sale reduces an oversized NVDA position and moves the portfolio toward its targets.
Transaction: https://t.co/2KhvBctcHu

This is how is used SERV Reasoning:

Prompt Guard is always on. Payee names and memos are typed by users and end up in the prompt, so that's a real injection surface. A blocked prompt is never retried without it.

Shadow Agent checks every DCA reply against a strict JSON shape and regenerates weak ones.

Multipath is on through the model name, on a small model. A cheap model is enough when the model has no authority.
Kronos is off on purpose, because it rewrites the prompt and could break the JSON we parse.

If reasoning is unavailable, a DCA run falls back to a plain scheduled buy, and the guardrails still apply.

Once the model also replied "I can't share that." as a normal answer, and it was logged as if it were an explanation. Now replies that are too short or read like refusals are dropped, and the ledger keeps the plain facts.

Robinhood MCP

There's a read-only connector for Robinhood's Agentic Trading MCP. Any tool that looks like trading, transferring, or staking is refused by name before it can run, and it's off by default.

Against Robinhood's live server I verified OAuth discovery, dynamic client registration, and a PKCE authorization request, and I built a login tool on top of that.

But Robinhood brokerage account is restricted on my region so i couldn’t signed in and I was unable to call the MCP tools yet.

Live: https://t.co/N7YTjRUkz6

Repo: https://t.co/zQ82nwTUNZ

Real funds, small caps, not financial advice. Tell me what to break next.

Built for the #SERV Hackathon, Mainnet & MCP track.

#BuildonSERV #SERV’ing.

[Kube @KubeEcho]

@TweetBySoft @RobinhoodCrypto Real treasury ops with SERV guardrails. Proper agentic finance right here