Cover image via U.Today Disclaimer: The opinions expressed by our writers are their own and do not represent the views of U.Today. The financial and market information provided on U.Today is intended for informational purposes only. U.Today is not liable for any financial losses incurred while trading cryptocurrencies. Conduct your own research by contacting financial experts before making any investment decisions. We believe that all content is accurate as of the date of publication, but certain offers mentioned may no longer be available.
Dogecoin cofounder Billy Markus, who goes by "Shibetoshi Nakamoto" on X, reacted to recent reports that the world's largest publicly traded company holding Bitcoin, Strategy, may sell a portion of its BTC holdings, about $1.25 billion.
Strategy holds 847,363 BTC as of June 22. If the Bitcoin treasury company were to raise $1.25 billion through Bitcoin sales, it might need to sell about 20,800 BTC at current prices, equivalent to about 2.5% of its 847,363 BTC holdings.
However, the news that Strategy might sell a portion of its massive BTC stash has generated reactions from a large part of the crypto community, including Dogecoin co-founder Billy Markus.
HOT Stories
In an X post, Markus shared a short video clip that had a compilation of tweets from Strategy Chairman and Bitcoin advocate Michael Saylor urging holders never to sell their Bitcoin.
This itself attracted comments from the Dogecoin community, as an X user pointed out Markus' well-known decision to sell his DOGE holdings years ago.
You Might Also Like
Markus, who co-founded Dogecoin in 2013, sold all of his DOGE holdings in 2015 after being laid off from his job. He liquidated his entire crypto portfolio for about $10,000 to pay rent and cover basic living expenses. This amount was equivalent to what a used Honda Civic would cost at that time.
Despite the recurring jokes and discussions, Markus maintains a lighthearted attitude toward the decision. This is seen with Markus posting a meme GIF that basically said "I'm fine" in response to the X user who recalled this decision.
Strategy to sell Bitcoin?In a recent press release, Strategy announced that its Board of Directors has authorized a BTC Monetization Program under which the company may sell BTC from time to time for three primary purposes.
You Might Also Like
First, to generate up to $1.25 billion to fund the USD Reserve; second, to additionally fund preferred stock dividends and interest expenses as they become payable or to replenish the USD Reserve after such payments. Third, to additionally fund repurchases of Digital Credit Securities or Class A common stock.
As stated in the release, the BTC Monetization Program does not obligate Strategy to sell any BTC, fund any dividend payment or interest expense through BTC sales, or repurchase any securities.
The BTC Monetization Program will have no fixed expiration date and may be modified, suspended, or terminated at any time.
As promised, the leading US crypto exchange Coinbase has dramatically increased the number of coins supported on its platform. The company just added Stellar (XLM), a few weeks after the long-rumored debut of XRP.
So which coins will land the coveted Coinbase listing next?
Back in December, Coinbase revealed it’s taking a hard look at 31 additional cryptocurrencies. The platform now supports Bitcoin, Ethereum, XRP, Litecoin, Bitcoin Cash, Stellar, Ethereum Classic, Zcash, 0x, Basic Attention Token and USD Coin.
That leaves 28 coins on Coinbase’s list of prospects.
Coinbase Pro, the company’s professional trading platform, already supports a handful of the coins on the list above: Civic, Dai, District0x, Golem, Loom, Decentraland and Zcash.
A wrath of class-action lawsuits hit a number of major cryptocurrency firms on Friday with the likes of Binance CEO Changpeng ‘CZ’ Zhao and Civic’s Vinny Lingham being accused of selling unregistered securities to US investors.
As reported by OffShoreAlert, a total of 11 complaints were filed against of 42 parties across the entire cryptocurrency industry.
Other firms included in the lawsuit aside from Binance include: BitMEX operator HDR Global Trading, Tron, Civic and Kyber Network.
The complaint against Binance states: “Binance and the Issuers wrongfully engaged in millions of transactions—including the solicitation, offer, and sale of securities—without registering the Tokens as securities, and without Binance registering with the SEC as an exchange or broker-dealer.
Just recorded this. Will be released tomorrow morning. CZ articulated a lot of what is happening at Binance, including a glimpse into potential plans for a DAO…make sure to listen tomorrow! https://t.co/4DtOXW7SBt
— Pomp 🌪 (@APompliano) April 4, 2020
“As a result, investors were not informed of the significant risks inherent in these investments, as federal and state securities laws require.”
The Securities and Exchange Commission has been clamping down on cryptocurrency firms over the past two years, slapping EOS with a $24 million fine over its $4 billion Initial Coin Offering (ICO) in 2018.
It also issued fines to two other ICO’s, Airfox and Paragon, with both companies having to refund investors more than $10 million in late 2018.
For more news, guides and cryptocurrency analysis, read here.
Disclaimer: The views and opinions expressed by the author should not be considered as financial advice. We do not give advice on financial products.
Several juggernauts of the crypto-industry were named in a class action lawsuit for the alleged sale of unregistered securities. Those mentioned include Binance, BitMEX, Tron, Block.one, Kyber Network, and KuCoin, among dozens of others.
Crypto’s Biggest Companies Face Class-Action Lawsuits According to OffShoreAlert, 11 class action lawsuits were filed against 42 defendants in the Southern District of New York Court on April 3 for the sale of unregistered securities. The lawsuits have separately named industry giants such as Binance, BitMEX operator HDR Global Trading, Tron, Civic, Block.one, Kyber Network, Status, Bibox, Quantstamp, and KuCoin.
Apart from companies, the lawsuit also named several of their executives. Changpeng Zhao of Binance, Brendan Blumer and Larimer of Block.one (EOS), Vinny Lingham of Civic, and Arthur Hayes of BitMEX, to name a few.
All of the lawsuits were brought by Roche Freedman LLP, a law firm based in New York and Miami. The law firm is famous in the crypto industry for representing the estate of Dave Kleiman in its lawsuit against Craig Wright.
Judgement Day for ICO Issuers? Since 2017, ICO investors have collectively lost hundreds of millions of dollars after their investments lost 80% or more of their value. Under law, U.S. investors are entitled to a certain degree of transparency through financial disclosures mandated by the Securities Exchange Commission.
Advertisement
During the mania, the crypto entrepreneurs who raised these millions often overlooked the legal implications. Cryptocurrency was an entirely new asset. Many played it fast and loose, and made off with huge sums of money with little accountability. A large number of these companies failed.
But, the handful that succeeded were wildly successful, and these are likely the ones worth suing. For these companies, their success might be catching up with them.
Legality of ICOs in Question The lawsuits were filed on behalf of several individuals, including Chase Williams, Alexander Clifford, Eric Lee, and William Zhang, but also include “all others similarly situated.” That is, other people who invested in these projects.
The plaintiffs have alleged that all of the 11 companies included in the lawsuit violated federal securities laws. These companies unlawfully created and issued securities, circumventing regulations through the use of tokens. Exchanges were also implicated for their role in selling these assets to investors in the United States.
What’s surprising is that it’s not just companies. The executives and directors of these industry juggernauts were also named. However, it’s expected that most of the companies included in the lawsuit will outright dismiss the assertions.
But, dismissing all the claims might be difficult. This case is not without precedent.
A judge in the Southern District of New York recently ruled that the tokens issued by Telegram were securities and should have been registered with the U.S. Securities and Exchange Commission. The Commission itself has said many times in the past that most ICOs are assumed to be securities, until proven otherwise. The burden of proof rests on the issuers.
Nevertheless, this lawsuit will put U.S. courts to the test. The 42 defendants named in the case reside in 16 different countries, many of which are lightly regulated. To further complicate matters, some of these companies do not even have bank accounts or established offices, making enforcement a herculean task.
Decentralization is a tenet in the world of Bitcoin. As such, the courts in New York may find it difficult to pin these companies down if they are found culpable.
Disclosure: This article was edited by Priyeshu Garg. For more information on how we create and review content, see our Editorial Policy.
Russia is considering a plan to direct confiscated cryptocurrency into a special fund, with proceeds from its use allocated to social initiatives.
Yevgeny Masharov, a member of the Public Chamber of the Russian Federation, expressed support for the proposal, which is part of a broader effort to define crypto as property under criminal law.
Masharov told TASS that seized digital assets should “work for the benefit of the state” rather than remain dormant.
The proposed fund would hold confiscated cryptocurrency, allowing it to grow in value over time. Revenue generated from these assets could be directed toward social, environmental, and educational projects.
The initiative aligns with a bill submitted by Russia’s Ministry of Justice and the Investigative Committee that seeks to classify cryptocurrency as property and material evidence.
Masharov emphasized the importance of removing illicit crypto holdings from circulation while ensuring they serve a constructive purpose. He also expressed willingness to facilitate discussions between law enforcement, tax authorities, and the crypto industry to develop a unified stance on the matter.
If enacted, the proposal could create a structured approach for handling digital assets linked to criminal activity while integrating them into Russia’s broader financial system.
Trusted Editorial content, reviewed by leading industry experts and seasoned editors. Ad Disclosure
Czech Prime Minister Petr Fiala barely held on to power this week. His Civic Democratic Party faced a no‑confidence vote on June 18 after opposition parties seized on a $45 million Bitcoin donation that landed in the Ministry of Justice. The motion fell short by seven votes, leaving Fiala’s government intact but shaken.
Opposition United Over Bitcoin Gift According to reports, ANO, SPD and the Pirates joined forces to challenge the government after Tomáš Jiřikovský, a convicted drug dealer and weapons offender, transferred 1 billion CZK (roughly 470 Bitcoin) to the justice ministry on May 27.
They sold the coins almost immediately, sparking questions about why law enforcement wasn’t involved first. The no‑confidence motion drew 94 votes in favor but needed 101 to pass. Debate ran for more than 24 hours in parliament, and tensions ran high as MPs traded accusations.
💰🇨🇿 Czech Gov’t Faces No-Confidence Vote Over Bitcoin Scandal
Opposition triggers a no-confidence vote after a $45M bitcoin payment from an ex-convict.
Though unlikely to pass, the move could hurt PM Fiala’s coalition ahead of October elections. pic.twitter.com/LAk6JLgwG1
— PiQ (@PiQSuite) June 12, 2025
Justice Minister Steps Down Based on reports from České Noviny, Pavel Blažek resigned as justice minister on May 30 amid claims he knew about the donation before it arrived. His departure opened the door for Eva Decroix, sworn in on June 10 by President Petr Pavel, to lead the ministry.
Decroix has promised an independent probe and said her team will cooperate fully with investigators. She set a firm tone in her first statement, promising transparency and clear answers for a public eager to trust its leaders again.
BTCUSD trading at $105,107 on the 24-hour chart: TradingView Crypto Concerns Grow Globally This episode has tapped into broader worries about public officials and digital money. Similar issues have popped up elsewhere. US President Donald Trump has made headlines for profiting from a long list of crypto ventures.
Argentine President Javier Milei still faces questions over his role in the Libra token scandal. In each case, the mix of high‑value tokens and political office has stirred debate about ethics and oversight.
Image: Chainalysis Next Moves For Government Fiala admitted that mistakes were made and told supporters the gift “shook public confidence” in his party. He blamed the opposition for resorting to “dirt‑throwing” and “lies” on social media.
Still, critics say the probe must go beyond political finger‑pointing. If inquiries turn up illegal steps or cover‑ups, more resignations could follow—possibly changing the make‑up of Fiala’s slim majority. With parliamentary elections due in October, every move now will be watched closely.
Featured image from The Conversation, chart from TradingView
Editorial Process for bitcoinist is centered on delivering thoroughly researched, accurate, and unbiased content. We uphold strict sourcing standards, and each page undergoes diligent review by our team of top technology experts and seasoned editors. This process ensures the integrity, relevance, and value of our content for our readers.
Sign Up for Our Newsletter! For updates and exclusive offers enter your email.
Christian is a senior news writer/editor, crypto analyst, marketing professional, and virtual operations assistant with leadership experience in local and international media. Fueled by a passion for writing, cryptocurrency, and digital marketing, he helps create compelling content while supporting teams behind the scenes. He is also comfortable working graveyard shifts and adapting to flexible schedules. Off-screen, he's a social media enthusiast and movie buff who's constantly intrigued by the size of the universe.
Russia may soon take a major step toward formalizing its crypto economy. Evgeny Masharov, a member of the Russian Civic Chamber, has suggested the country establish its own crypto bank. Speaking to state media, Masharov argued that such a bank would help bring “shadow transactions” into the legal system, boost federal tax revenues, and reduce fraud linked to unregulated crypto activity. The idea of a crypto bank follows the example of Belarus, which is already working on building its own crypto-focused banking framework.
Crypto Miners at the Center of the Debate The proposal also directly targets Russia’s crypto mining industry, which remains one of the largest in the world despite regional restrictions. Currently, miners in Russia lack official infrastructure to convert their digital earnings into local currency, pushing many toward unregulated markets.
Source: X Masharov said a state-backed crypto bank would provide miners with a secure and legal way to sell their mined assets, addressing one of the industry’s most pressing challenges. “This will solve a number of current problems,” he noted, including limiting criminal activity that exploits gaps in existing regulation.
From Ban to Banking: Russia’s Changing Stance If approved, the move could mark a shift in Russia’s stance on digital assets. While the government banned crypto payments in 2022, it has gradually opened the door to limited use cases, such as permitting crypto products for accredited investors and even floating a ruble-backed stablecoin earlier this year.
Analysts say that a regulated crypto bank could further integrate digital assets into Russia’s financial system while still allowing the government to maintain oversight. With the Russian crypto industry projected to generate nearly $4 billion in annual revenue by 2026, the debate over how to regulate and support the sector is becoming harder to ignore.
JUST IN: Russian State Duma Deputy Anton Tkachev proposed creating a strategic #Bitcoin reserve in Russia, RIA Novosti reports 🇷🇺 pic.twitter.com/PlwSp24RvF
— Bitcoin Magazine (@BitcoinMagazine) December 9, 2024
Why It Matters Beyond Russia Globally, Russia would not be alone in exploring crypto banking solutions. Countries like Kazakhstan and the United Arab Emirates have experimented with creating regulated hubs for miners and digital asset firms.
If Moscow follows through, it could signal a broader shift: governments seeking to tighten control over crypto flows while also embracing the sector’s economic potential.
Disclaimer The information discussed by Altcoin Buzz is not financial advice. This is for educational, entertainment and informational purposes only. Any information or strategies are thoughts and opinions relevant to accepted levels of risk tolerance of the writer/reviewers, and their risk tolerance may be different from yours.
We are not responsible for any losses that you may incur as a result of any investments directly or indirectly related to the information provided. Bitcoin and other cryptocurrencies are high-risk investments, so please do your due diligence.
Today, we're proud to announce that Civic Nexus passed Google's Cloud Application Security Assessment (CASA) Tier 2 certification.
An authorized third-party lab tested our platform against key security requirements mandated by the App Defense Alliance's Tier 2 standard, which is based on OWASP ASVS v4.0, and found no high-risk vulnerabilities. The App Defense Alliance, led by Google, Meta, and Microsoft, administers this assessment.
CASA Tier 2 evaluates application security controls across 14 critical security categories. Independent assessors examined our API security, access controls, data handling practices, cryptographic implementations, and authentication flows. They mapped our code against common weakness enumerations with high exploit potential and verified compliance with OWASP ASVS Level 2 requirements. This is the same framework Google uses to evaluate applications requesting access to restricted user data in its own ecosystem.
Why This Matters for Civic Nexus UsersSupply chain security has become central to enterprise risk management. Organizations now face requirements to verify the security posture of every vendor in their technology stack. Independent certifications provide the documentation security teams need. CASA Tier 2 gives clients concrete evidence for stakeholder reviews and audit requirements.
AI workflow platforms sit at a critical point in the security chain. A vulnerability in the platform affects every connected system and every piece of data flowing through automated workflows. So, the stakes are high. Civic Nexus's CASA certification confirms we built our platform to withstand scrutiny from independent security experts applying industry-standard testing methods.
Companies evaluating workflow automation platforms can request details about our security practices and how CASA certification supports their vendor assessment process.
What Independent Testing ValidatesWorkflow automation creates risk. Every API connection, every data exchange, every system integration represents a potential entry point. When organizations connect Civic Nexus to their critical business systems, they need to know the platform coordinating their workflows has been independently validated.
Third-party validation matters because vendor security assessments have become mandatory for enterprises operating in regulated industries. Security teams need documentation for their compliance audits and vendor risk reviews. CASA Tier 2 provides an official Letter of Validation (LoV), serving as concrete evidence of independent testing rather than self-certification.
For Civic, the assessment process took several months. Our engineering and security teams enhanced secure coding practices, strengthened continuous security testing, and refined threat modeling processes. The lab conducted Dynamic Application Security Testing (DAST), reviewed our source code for vulnerabilities using Static Application Security Testing (SAST), and validated our defenses against the OWASP Top 10 and beyond.
At Civic, security reviews happen throughout our development lifecycle. We integrate testing from design through deployment, then monitor continuously and update defenses as threats evolve. CASA certification validates this practice rather than creating it.
Ready to learn more about our approach to security?
Try it out now or take a look at Civic Nexus security and review our approach to protecting automated workflows.
Most small teams and consultants don’t struggle with ideas. They struggle with execution.
They see the promise of automation and agentic AI, but the path from concept to something that reliably runs in production still feels heavier than it should. Infrastructure decisions arrive too early. Hosting costs climb before value shows up. Setup work lands on the same few technical people who already carry too much of the load.
That gap between intent and reality is exactly what this new partnership aims to close.
Today, Civic and lttle.cloud are announcing a partnership designed to make it easier, cheaper, and more approachable to run real automation workflows using Civic Nexus.
This isn’t about adding another platform.
It’s about removing friction.
What lttle.cloud brings to the tablelttle.cloud offers programmatic, usage-based hosting built for small teams and consultants that want to own their automation infrastructure without becoming cloud experts.
In practical terms, it gives users a one-click way to launch n8n without standing up servers, configuring Linux, or paying for infrastructure that sits idle. You pay for what you use. When workflows run, resources wake up. When they stop, costs drop back down.
For small teams and consultants experimenting with automation or scaling carefully, that model matters. Hosting costs stay proportional to value, not to server uptime.
This partnership allows you to start for free. You get end-to-end automation, all in one stack.
Where Civic Nexus fits inCivic Nexus takes responsibility for what usually happens after infrastructure comes online.
Once n8n runs on lttle.cloud, Nexus orchestrates setup, configuration, and ongoing maintenance. It handles the work that typically falls between tools. It brings structure to how workflows get deployed, monitored, and updated over time.
Instead of juggling hosting, configuration, and orchestration as separate concerns, small teams and consultants move from click to deploy straight into a system designed to manage complexity quietly in the background.
The experience feels simpler because it actually is.
Why this partnership exists
For Civic, this marks the first publicly announced Nexus partner integration.
This concrete example shows how Civic Nexus works alongside other platforms. It illustrates what orchestration looks like when infrastructure and workflows align, and it establishes a reference point for future partnerships built around the same principle.
For users, the value shows up quickly.
Instead of making big infrastructure commitments up front, small teams and consultants can start small and scale as value becomes clear. Automation comes online without expensive monthly servers or specialized setup work that only a few people understand. Workflows run in an environment where data stays under your control, hosted efficiently, and coordinated through a single orchestration layer rather than scattered across tools and scripts.
This approach works especially well for marketing leaders, operations small teams and consultants, and analysts who want to move from experimentation into repeatable execution without turning every idea into an engineering project.
Who this is forThis partnership serves small teams and consultants that want to own their automation workflows without owning unnecessary complexity.
It works for organizations just starting their automation journey and for experienced small teams and consultants looking to reduce friction and cost. It supports experimentation, iteration, and growth without locking small teams and consultants into heavy infrastructure decisions upfront.
Most importantly, it meets leaders where they are. Curious. Practical. Focused on results.
Use case in action: The meeting follow-up nobody wants to ownLet’s put it all together with an example.
Here’s one you may feel familiar with: meetings that don’t end with results, just good intentions.
In these meetings, notes get taken. Decisions get made. Action items sound clear in the moment. Then everyone moves on, and those next steps slowly drift across inboxes, docs, and tools until no one is quite sure who owns what anymore.
It’s a familiar pattern, and it’s exactly the kind of small, repeatable problem this setup handles well.
With Civic Nexus and lttle.cloud, follow-up work becomes part of the system instead of something people have to remember to do.
Here’s what that looks like in practice.
As soon as a meeting ends, a system activates quietly in the background. First, n8n spins up on lttle.cloud, gathering notes, identifying action items, and routing next steps based on structure the team has already defined. Then Civic Nexus orchestrates the workflow, keeping instructions and logic consistent even as inputs change over time.
Tasks land inside the tools small teams and consultants already use, with clear ownership attached from the start. Follow-ups happen naturally, without reminders, escalation, or the low-grade anxiety that something important was missed.
Of course, this isn’t the only way small teams and consultants could try to solve the problem.
Some reach for a personalized GPT. It can summarize notes well, but it still depends on someone remembering to prompt it after every meeting. Others wire together a managed automation platform, gaining convenience up front while accepting ongoing subscriptions and limited flexibility. A cloud provider workflow can handle the task too, though it brings more setup and infrastructure decisions than most small teams and consultants want for something this simple. Custom code solves it as well, but only by pulling engineers into building and maintaining yet another internal system.
Each of those paths works. None of them quite fits.
This partnership sits in a different middle ground.
The workflow doesn’t wait for a person to kick it off. It runs on its own. Infrastructure wakes up only when the work needs to happen, then fades back into the background. Costs stay aligned with actual usage instead of always-on servers. The logic remains visible and easy to adjust as the team evolves, rather than locked inside brittle scripts or sprawling prompts.
What changes isn’t just how the task runs.
It’s who has to think about it.
A small but persistent drain on attention turns into something dependable, quiet, and shared by the system instead of the people.
How to get startedGetting started is easy.
Try it for free to get end-to-end automation, all in one stack.
Here’s what you can look forward to: spinning up n8n on lttle.cloud with one click, connecting it to Civic Nexus, then, defining the workflow you want to run. Nexus handles the orchestration and maintenance as it runs in the background.
Because infrastructure only activates when workflows execute, small teams and consultants can experiment without worrying about idle costs. Because logic lives in visible workflows, changes stay easy to make and easy to understand.
You don’t need to get everything right on day one.
You just need a place to start.
Frequently asked questionsWhat problem does the Civic and lttle.cloud partnership solve?
It reduces the cost and complexity that often slow automation and AI workflow adoption by combining usage-based hosting with centralized orchestration.
Do small teams and consultants need cloud or DevOps expertise to use this setup?
No. lttle.cloud handles hosting through one-click deployment, while Civic Nexus manages setup and maintenance so small teams and consultants can focus on workflows rather than infrastructure.
How does this approach help control costs?
Infrastructure runs only when workflows execute, which keeps costs tied to actual usage instead of always-on servers.
Can this support production-level workflows?
Yes. The integration has been tested with Civic Nexus, documented clearly, and designed to support reliable workflows over time.
Local AI agents are crossing a critical threshold. They are no longer toys, demos, or side projects. They are becoming operators with real access to real systems, and the security models around them are dangerously underdeveloped.
Today, we are introducing Civic Nexus for OpenClaw, which will help you add a protective layer when you connect docs, tools and data to OpenClaw. Civic Nexus provides authentication on a clean machine without authorizing OpenClaw to access your accounts. We remind users that they should never log into Civic Nexus on the machine where OpenClaw is operating.
Together with emerging infrastructure like Cloudflare’s Moltworker and other collaborative deployments, Civic Nexus helps developers experiment with powerful AI agents with more tools to mitigate risk.
Why use secure tool orchestration with OpenClaw?Interest in OpenClaw has surged because it represents a major shift in how AI assistants operate.
OpenClaw runs locally, integrates deeply with your system, and connects directly to messaging apps, files, and local tools. Over time, it retains context across sessions, allowing it to build a persistent understanding of how you work.
That persistence is also where the risk begins.
To function effectively, OpenClaw often requires access to credentials, APIs, messaging platforms, payment tools, and private data. Without clear boundaries, a single assistant session can accumulate permissions that span your password manager, financial accounts, internal documents, and communication channels.
This creates several concrete risks:
Tool access that silently persists beyond its intended usePrompt injection that triggers unintended tool executionAgents chaining tools in unsafe or unexpected sequencesNo clear way to audit, revoke, or constrain what the assistant can do once connectedWhen an AI assistant effectively operates as a super admin, mistakes and exploits scale quickly.
This is an enormous problem.
Civic Nexus as an authorization primitiveCivic Nexus introduces a missing primitive for local AI agents: a centralized, revocable authorization layer that sits between the assistant and supported third-party tools.
Instead of OpenClaw connecting directly to your apps, OpenClaw requests access through Civic Nexus. Permissions to use third-party tools are evaluated and enforced in one place, under your control.
You decide what the assistant can access and how it can use those tools.
How Civic Nexus for OpenClaw worksAt runtime, the interaction looks like this:
OpenClaw will call into Nexus and call a specific MCP serverNexus will check whether OpenClaw is authorizedIf OpenClaw is not authorized, it will ask the user to authorize on behalf of OpenClawOnce the user grants access, OpenClaw has access to that MCP serverAll authorization decisions happen outside the language model. The model cannot modify its own permissions during execution, as long as the user has not logged into Nexus on the host machine. Please review specifics in our docs.
Example workflowImagine you want an AI agent to:
Find prospect email addresses using Hunter.io or FindymailEnrich contact data by searching LinkedIn and company databasesCreate CRM records in Salesforce, HubSpot, or PipedriveGenerate personalized outreach and send via email or SlackThroughout the workflow, Civic Nexus ensures data quality through guardrails that:
Require email validation before adding contacts to your CRMEnforce domain restrictions to only prospect within target industriesFilter out personal emails that don't match business domain patternsCap batch operations to prevent accidental bulk data importsWhat control does Civic Nexus give you?Adding Civic Nexus introduces a dedicated orchestration layer that governs how OpenClaw interacts with tools, data, and external systems that the user has configured in Nexus.
At a high level, this gives you four critical controls.
Centralized, revocable tool authorization. You remain the human in the loop. You explicitly grant and revoke access to third-party apps from a single console. These rules are configured in a separate environment from OpenClaw, and therefore OpenClaw is only allowed to consume the tools and authorizations of your choosing. Civic Nexus securely stores access tokens using encryption, and revocation takes effect immediately. No hidden or lingering permissions remain active in the background, one of the riskiest aspects of using OpenClaw.
Protection against prompt injection and unintended execution can be set up by the user. After the user sets up proper guardrails, Civic Nexus enforces tool access at the protocol level, not through prompts.
Hard limits through parameter presets. You can define some immutable parameters that act as hard constraints with MCP servers. The language model cannot override them during execution, preventing runaway automation or unexpected costs. An example would be adding the Slack MCP server to OpenClaw, and limiting use to one specific channel.
Reduced attack surface through scoped toolkits. Toolkits let you group MCP servers into focused sets designed for specific workflows. Instead of exposing every available tool, you give OpenClaw a constrained environment tailored to the task. This improves reliability while reducing confusion and risk.
Who should use Civic Nexus for OpenClaw?Civic Nexus is designed for developers and teams who are:
Experimenting with local AI agents that interact with real systemsConnecting OpenClaw to messaging, payments, or internal toolsConcerned about credential sprawl and persistent agent permissionsLooking for a practical human-in-the-loop control model for AI workflowsHow do I get started?If you are ready to experiment with OpenClaw and want stronger guarantees around security and control, review our Terms of Service to understand your responsibilities, then try Civic Nexus for OpenClaw in our docs.
We are excited about where personalized AI is heading, and we believe access control will define whether these systems earn long-term trust. Civic Nexus is our contribution to building agents that are powerful without being reckless.
Drop us a note and let us know what you’re working on!
You navigate through config directories, manually edit .env files, and double-check that nothing sensitive ends up committed to version control. Then you restart services and hope the connections hold. Every time you add a new tool, you repeat the cycle. The steps work, but each one is an opportunity to introduce drift, expose credentials, or misconfigure something that won't surface until the agent is already running against real data. For most developers, this friction feels like a fixed cost of working with a powerful local agent.
It isn't.
If OpenClaw is already running, you can install Civic Nexus entirely from the Console Dashboard. No local file edits. No service restarts. The entire flow takes under two minutes.
If OpenClaw is not running, you can search for hosted OpenClaw 1-minute installs.
Setting up a safer environmentOperating OpenClaw with confidence comes from setting up the right environment for your experiments. Civic Nexus is only one part of creating the system.
As you build your environment, be sure to address the following questions:
Can I easily connect it to tools? (connectivity)Can I prove what it did? (auditability)Can I limit what it touches? (access control)Can I shut it down if something goes wrong? (revocation)How to set it upOpen your OpenClaw Console Dashboard in the browser.
Navigate to Config, then Environment. Find the option labeled Shell env and enable it. This tells OpenClaw to read environment variables directly from the dashboard instead of from local configuration files.
Switch to the Vars tab and add two new variables.
Replace YOUR_ACCOUNT_ID with your Civic account ID and your-access-token with your Nexus access token. Save the configuration. Note: You can get the full profile URL from app.civic.com > Install. And you can get the access token by choosing to generate token in the same Install section under MCP URL
Same for the access token, by choosing to generate token in the same Install section under MCP URL
You haven't touched a single local file.
Now switch to the OpenClaw chat interface and run this command.
OpenClaw will detect the environment variables, connect to Nexus, register the MCP hub, and install the available tools automatically. When the confirmation appears, verify that everything landed correctly by asking the assistant to list its available tools.
Your Nexus-powered tools will appear in the workspace. That's the whole setup, and nothing on your local machine changed to make it happen.
Why this approach mattersThe default approach for connecting OpenClaw to external tools involves editing .env files directly on the host machine. That path carries familiar risks. Credentials surface in Git history. Developers hardcode them into files that travel across machines, sit alongside active projects, and end up in places they were never meant to reach.
Builders experimenting with OpenClaw have found workarounds worth knowing. Running the agent in a dedicated VM or container limits the blast radius. Using a clean machine that stays separate from your primary accounts adds another layer. Cloudflare's Moltworker offers a self-hosted path for isolating agent infrastructure more completely. These approaches work, and many developers use them in combination.
Connecting OpenClaw to Civic Nexus through the Console Dashboard approaches the problem from a different direction. Those workarounds build containment around OpenClaw. Civic Nexus removes the exposure before containment becomes necessary. Credentials never enter local files, so there is nothing to contain. Authorization lives in a separate environment from OpenClaw's runtime, and the model cannot modify its own permissions during execution. That separation holds whether you run on a clean machine, inside a VM, or on your primary workstation. No lingering access, no configuration drift.
Frequently asked questionsDo I need to restart OpenClaw after saving the environment variables?
No. After you enable Shell env, OpenClaw reads the variables directly from the dashboard. The clawhub install civic-nexus command handles the connection without requiring a restart.
What if I already have a CIVIC_URL or CIVIC_TOKEN defined in a local .env file?
The dashboard variables take precedence once you enable Shell env. If you want to remove the local variables to keep things clean, you can do so without affecting the running instance.
Can I use multiple Nexus profiles with a single OpenClaw instance?
Yes. The profile parameter in the CIVIC_URL variable controls which profile OpenClaw connects to. Swap profiles by updating that value in the dashboard. No local file edits required.
Is this approach appropriate for production use?
Civic Nexus stores access tokens with encryption, and all authorization decisions happen outside the language model. One critical rule applies. Do not log into Civic Nexus on the machine where OpenClaw operates. That separation prevents the model from modifying its own permissions during execution. Civic docs cover what Nexus enforces at the protocol level.
Get startedIf you run OpenClaw and connect it to real systems, Civic Nexus gives you a cleaner path to doing that safely. The setup we walked through takes less than two minutes and keeps credentials where they belong.
Start with the Civic Nexus for OpenClaw quickstart and join the conversation in the Civic Developers Slack. We'd like to hear what you're building and what you're connecting it to.
Civic has officially joined the Gelato Network’s Rollups-as-a-Service (RaaS) marketplace, enabling developers to seamlessly integrate privacy-focused user verification tools into their blockchain rollups. This collaboration aims to address the increasing challenges posed by bots and fake users in decentralized applications. Through Gelato’s marketplace, developers can now access Civic’s verification solutions i.e., the Civic Pass, with just one click.
The Civic Pass provides on-chain identity verification designed to combat Sybil attacks enhance user experience, and ensure compliance. Civic has verified 170,000+ unique users and issued nearly one million Civic Passes highlighting its expertise in reducing fraudulent activity across gaming, social networks, and blockchain-based communities. The strategic integration with Gelato allows developers to create compliance-gated rollups and leverage Civic’s user authentication tools to strengthen rollup security, scalability, and reliability.
Gelato’s Advanced Infrastructure for Scalable Rollup Solutions Gelato’s RaaS platform is intended to simplify the process of rollup deployment and management by offering developers tools that make the process manageable and repeatable. The platform provides services on the same servers as rollups, thus reducing latency and enhancing performance. Some of them are transaction automation, account abstraction, and on-chain randomness using Gelato Functions, Relayers, and VRF services.
The integration of Civic into the Gelato ecosystem enhances these features with effective user management. Through this integration, developers can eliminate the risks of bots and improve the reliability of their applications using Gelato’s scalable infrastructure.
Civic Offers Proven Solutions for Real-World Applications Civic has successfully partnered with several projects including Gitcoin Passport and PlayHoneyland to eliminate fraud and protect users. This partnership with Gelato just serves to strengthen the position of Civic as the go-to platform for user verification within the blockchain industry.
Thus, with the help of Civic’s advanced tools, Gelato helps the developers to overcome the existing compliance and security issues and innovate. The collaboration shows the possibilities of pooling resources in support of decentralized ecosystems and increasing the utilization of blockchain rollups.
AUTHOR
Crypto journalist with years of experience providing in-depth analysis and news on blockchain and decentralized finance. With a keen eye for detail, Shahzaib delivers insightful articles that explore the latest trends, market movements, and innovations within the crypto and blockchain ecosystem. His work focuses on educating readers while offering expert commentary on the evolving landscape of digital assets, DeFi protocols, and the broader impact of blockchain technology.
Bitcoin (BTC) has been incurring a significant amount of upwards momentum as of late that allowed it to put an end to the month-long bout of selling pressure it has faced over the past month, which has also allowed it gain significant dominance over the aggregated crypto market capitalization.
Furthermore, data shows that Bitcoin has been dominating trading volume on major exchanges like Coinbase, which signals that traders are not currently interested in altcoins and are primarily focused on pouring their capital into BTC.
Bitcoin Briefly Surges Past $12,000 as Dominance Rises to Nearly 70% At the time of writing, Bitcoin is trading down marginally at its current price of $11,700 and is up slightly from its daily lows of $11,600 that were set yesterday and revisited earlier today.
Last night, Bitcoin surged past the $12,000 region before facing a sharp increase in selling pressure that sent it reeling lower. This selling pressure proved that the cryptocurrency is not yet ready to journey into the $12,000 region and may signal that further losses are imminent.
At the time, most major altcoins have been facing a significant surge in selling pressure that has caused many of them to plummet against their BTC trading pairs, which has allowed Bitcoin’s market dominance to surge to nearly 70%
Currently, Bitcoin’s market dominance is at the highest it has been since mid-2017 and is nearing levels not seen since the years before 2017.
Other major cryptocurrencies, like Ethereum and XRP, have been seeing a continuous decline in their dominance over the market, and smaller cryptocurrencies have surrendered even more of their market cap to Bitcoin.
Bitcoin Dominates Trading Volume on Coinbase This surge in market dominance has come about as a result of significantly higher-than-average BTC trading volume on major exchanges like Coinbase.
Larry Cermak, the director of research at The Block, spoke about this increased trading volume in a recent tweet, explaining that Bitcoin alone was responsible for 72% of the trading volume on Coinbase over the past 24 hours, signaling that investors have little to no interest in smaller altcoins at the present.
“Coinbase volume breakdown in the last 24 hours: BTC – 72.0% LTC – 10.2% (outlier this week because of the halving) ETH – 8.8% BCH – 2.5% XRP – 2.5% Chainlink – 1.4%. The rest combined (EOS, XLM, BAT, ETC, REP, ZRX, ZEC, Decentraland, Golem, district0x, Loom, Civic) – 4%,” he noted.
Coinbase volume breakdown in the last 24 hours:
BTC – 72.0%
LTC – 10.2% (outlier this week because of the halving)
ETH – 8.8%
BCH – 2.5%
XRP – 2.5%
Chainlink – 1.4%
The rest combined (EOS, XLM, BAT, ETC, REP, ZRX, ZEC, Decentraland, Golem, district0x, Loom, Civic) – 4% pic.twitter.com/6vdEk304mt
— Larry Cermak (@lawmaster) August 6, 2019
Although it still remains unclear as to whether or not Bitcoin is currently in a full uptrend, it is clear that investors are not yet interested in altcoins, and the prophesized “altseason” may be a long way off.
