Jon Cursi

HVAC companies do their best revenue during heat waves and cold snaps. They also lose the most leads during those exact same weeks. The phone lines are slammed, the website gets traffic but nobody converts, and every missed call goes straight to a competitor.

THEY DID IT. The SEC and CFTC just dropped a landmark document that officially classifies crypto assets. They're actually telling us which crypto assets are securities and which ones aren't - by name! THIS IS SOMETHING GENSLER REFUSED TO DO (he focused on prosecuting crypto out of existence) This rule doc gives crypto many of the benefits of the clarity bill - it lifts us out of the gray market - it gives every asset a path. It's almost like the Clarity act just passed by way of regulator. (of course, the actual clarity act will harden all this into legislation and make it irreversible in the event we get another Gensler, we still want it) This rule says there's 5 categories for crypto assets: 1) Digital Commodities - assets tied to a functional, decentralized crypto system (e.g., BTC, ETH, SOL, XRP, ADA, DOGE). Not securities. (yes, they name them on page 14) 2) Digital Collectibles - NFTs, meme coins, artwork tokens, in-game items. Not securities (fractionalized collectibles may be an exception). 3) Digital Tools - membership tokens, credentials, domain names (e.g., ENS). Not securities. 4) Stablecoins - payment stablecoins under the GENIUS Act are not securities. Other stablecoins, it depends. 5) Digital Securities - tokenized versions of traditional securities. Like tokenized stocks. Always securities. Amazing! This makes so much sense I can't believe it's coming from a regulator. No more enforcement threats to Ethereum developers and crypto exchanges. How about the Howey test? More common sense! If an issuer makes specific promises of managerial efforts from which buyers expect profits, the offering is a security until those promises are fulfilled. Then it's a commodity. The asset itself was never the security, the deal around it was. (E.g. XRP was a security pre launch, became a commodity after). How about stuff like staking and mining? Mining? Not a securities transaction. Staking? Also not a securities transaction, that includes custodial and liquid staking even with LSTs! How about wrapping BTC? Not a securities transaction. Airdrops? NOT SECURITIES. NO MORE GEO BANS PROTECTING AMERICANS from free airdrops. Remember this is a joint doc from the SEC and CFTC, They're actually cooperating on this, no internal strife, this is binding to both. SEC regulates $80-100 trillion assets CFTC regulates $5-10 trillion assets Both of the world's largest capital markets are showing us that crypto assets are here to stay and they're welcome alongside traditional assets. Every country will follow. This is the biggest move toward legitimacy I've seen in all my time in crypto. Maybe bigger than the genius act since is covers all crypto assets. Well done @MichaelSelig and @SECPaulSAtkins. And especially well done to the indefatigable @HesterPeirce. Her fingerprints are all over this, couldn't have happened without her eight years of principles-based curiosity.

So far they are 100% openclaw but I’m about to embark on the process of converting them into AlphaClaw to make my current agent-specific management easier. I saw you added web terminal and Slack support recently which rounds out the feature set I was looking for! ☺️ The step after that would be some type of meta / fleet level view but TBD on how it’ll be done. I’d imagine many people are working on this but couldn’t find anything OSS’ed yet. I’m mainly looking for the master view to be informational - like are the agents online, what activities have they been doing (time stamped high level feed), what jobs do they have scheduled, etc. It would be a total bonus to trigger actions from within the meta view like AC version updates, OC updates, git syncs, etc - but honestly not a big deal to just one-click from meta view into an agent-specific AC view and do it there!

@joncursi @openclaw i see! are they a mix of openclaw and alphaclaw instances? what kind of jobs would you like to perform from the master view?

AlphaClaw 0.8.0 🐺 control your mac via @openclaw from any VPS using Chrome's new DevTools MCP AlphaClaw is the easiest way to run self-managed openclaw in the cloud. one-click deploy, no cli wrestling. 🦞 2026.3.13 base github.com/chrysb/alphacl…

@_pgauthier Actually the article is pretty great! From a security lense, I agree that atoms > bits from here on out and Ledger is uniquely positioned to expand and benefit. Given our conversation here, I chuckled when I got to the line: “distinguishing a human from an AI is existential” 😅

@joncursi These are my thoughts. I am more than happy for AI to do the writing. What did you think of the content and what I am saying ? (this is me typing now 😅)

@chrysb @openclaw I have a small but growing number of openclaw instances that I manage for myself, friends, and family. They run in different contexts with different operators. It’s hard to run tech support on them all without a “master view”, so that’s what I’m trying to synthesize 🤔

@joncursi @openclaw why do you have different instances instead of a single OpenClaw instance with multiple agents?

AlphaClaw is amazing for single-claw setups. I’m dreaming of a cross-claw version of it, aka fleet dashboard which is effectively multi tenant. Eg if you want to see all the scheduled tasks for all claws in the fleet it would be able to show that - almost like plugging multiple emails into Google Calendar to see it all in one view. You could pull the data out from each alphaclaw periodically but I think that won’t scale to large (5+) fleets. That’s why I’m thinking about alphaclaw being able to push the data out rather than trying to pull it in. - imagine a periodic heartbeat that might push high level stats like online, OC version, AC version, VM metrics - imagine events feeding a cross-claw activity feed (CRUD for messages, crons) - pushed at the time of creation/deletion/update of the message/cron

@joncursi @openclaw what kind of messages? when would they be triggered?

I should have revised my comment to be more constructive. What I’m trying to say is that prose full of “—“ is the quickest tell that the content was AI generated top to bottom. Just a note to keep in mind for the future - if you want it to appear human, tell the LLM that “—“, aka emdashes, are banned from its output.

@joncursi Thank you

@chrysb Love that we can avoid SSH for the common tasks, but often the agent does need you to SSH in to install libs (eg ffmpeg, playwright, etc). Thoughts on supporting a web-based terminal / shell experience in alphaclaw? Would make this the one-stop-shop.

9/ full file browser lets you inspect your workspace and and make changes without SSHing. also surfaces git state.

introducing 🐺 AlphaClaw, the ultimate setup harness for @openclaw. open-source, self-managed, free-to-use, with no lock-in. AlphaClaw makes OpenClaw setup and maintenance easier by providing an elegant GUI that wraps OpenClaw's CLI. 📅 Google Workspace OAuth & pubsub built in w/ gog-cli 🔄 Auto-backup to GitHub 🧱 Prompt hardening reduces agent drift 🩺 Drift Doctor analyzes your prompts and workspace for drift 💬 Telegram multi-topic workspace setup wizard 📂 Full file browser and editor, no SSH needed 🐕 Watchdog auto-detects crashes, self-heals gateway 🛠️ Manage env vars from the UI 🔑 Manage model keys & OAuth visually 🪝 Webhook creator & inspector with replay & debug 📊 Token usage & cost analytics built in ⬆️ One-click updates, no redeploy needed 📦 Import existing setup from GitHub i didn't build alphaclaw to replace openclaw or compete with it. openclaw is the best user-owned AI agent framework out there and more people should be able to use it without wrestling a CLI for two hours. there are so many managed "deploy your AI in seconds" product. but they lock you into their platform. if they pivot, shut down, or jack up pricing, your agent goes with it. alphaclaw gives you that same one-click simplicity, but everything runs on your infra with your data. no proprietary backend. no config hostage. if railway disappears tomorrow, you still have a standard openclaw instance backed up to your own github repo. everything alphaclaw does, you could do manually. it's just automation and UI on top of the real thing. outgrow it? disagree with its opinions? eject. your openclaw instance is still a standard openclaw instance. to make it convenient, i’ve created both a one-click deploy template on railway and render to start quickly. make sure you have 8GB of ram on your instance. look forward to your feedback and to building this out with the @openclaw community! 🦞 github.com/chrysb/alphacl… feature deep-dive in the 🧵

Always do - just trying to understand how to manage openclaw version updates when alphaclaw is in play. If alphaclaw wants to control the openclaw version (it pins it to specific versions), does that mean I should never ask the claw to update itself, and instead wait for alphaclaw to push a new release -> update / restart Docker container? Basically, stay on alphaclaw's cadence instead of my own?

@joncursi @openclaw read the changelog - I always ask my agent to review the new release and evaluate risk and benefit of updating.

psa: @openclaw 2026.3.8 just dropped. some highlights worth knowing: 🆕 openclaw backup create and openclaw backup verify. local state archives with config-only mode. good habit to have. 🆕 brave web search now has an "llm-context" mode that returns grounding snippets instead of raw results. 🔧 cron jobs no longer all fire at once after a restart. they stagger now. if your agent was doing weird burst behavior after reboots, that's fixed. 🔧 telegram DM deduplication. if you were getting double replies in DMs, fixed. 🔧 config writes no longer wipe secret values from runtime cache. if you've ever had API keys "disappear" until you restarted, that was this. 🔧 gateway now validates config before restarting. bad config won't crash your gateway anymore, it just refuses to start and tells you why. also a bunch of security fixes worth updating for (browser SSRF, teams auth bypass, skills path traversal).

@chrysb @openclaw In isolated cloud VMs (digital ocean)

@joncursi @openclaw do your coding agents run locally on your machine, or in the cloud?

@chrysb @openclaw I’m experimenting with a software engineer assistant. Given Anthropic doesn’t want OAuth tokens inside of 3rd party software, but I want to use opus, I say “spin up Claude code and do X”. It uses ACP to spawn a CC CLI session and do the work, and reports back.

@joncursi @openclaw always read the changelog! no guarantee that an openclaw update won't break some aspect of alphaclaw. the latest version of alphaclaw will always be pinned to the last version of openclaw it's been verified to support it's on my list to check out acp. what's your setup like?

@AskVenice Is the monthly VVV burn from open market purchases, or from the treasury? cc @ErikVoorhees

The latest $VVV burn has been executed. This is our largest burn to date. 🔥 VVV is the the capital asset of Venice, with a monthly buy-and-burn mechanism and on the road to becoming deflationary

@chrysb @openclaw Thoughts on how the new backup system will work in conjunction with alphaclaw’s git backup system?

@chrysb @openclaw Totally - glad that Slack, etc. are the roadmap. I'll definitely be kicking the tires on this more in the coming weeks. Great work!

@joncursi @openclaw absolutely. one man show right now with a full-time startup i run, so i'll do what i can! open source hopefully attracts some folks to contribute and help with this slack would be next on the list

@chrysb @openclaw Thanks! I ran an import and it seems to work well! I see that it brings the files over - curious about the SQLite database though. Does a pre-existing openclaw instance contain valuable info in the SQLite database (memories and such?), or is that derived from the files?

@joncursi @openclaw there’s an experimental import function - tho everyone’s implementations vary wildly, it does its best attempt but still might need manual intervention to get it all up and running