@Bedrock , the project that made serious waves on Binance Alpha. Chances are, you’ve traded it before, right?
I recently started spending more time looking into Bedrock 2.0. Not really because of yield or the BTCfi narrative. It started from a strange feeling I couldn’t ignore: there were moments when I’d finish using it and suddenly realize… wait, I barely had to think as much as I used to.
At first, I thought it was just better UX. Fewer steps. Fewer things to double-check. But the more I looked at how Bedrock 2.0 is building around uniBTC and BTCfi, the more it felt like something else was happening. It didn’t feel like DeFi was becoming simpler.
If anything, it felt like Bedrock was becoming smarter underneath.
Back then, using BTC in DeFi often meant becoming an operator for your own assets. Which wrapped version made sense. Where liquidity lived. Which staking layer worked best. Sometimes it felt like solving a small operational puzzle before pressing the button.
Bedrock 2.0 feels oddly different.
uniBTC doesn’t feel like just another wrapped asset to make BTC more productive. It feels closer to Bedrock trying to coordinate the growing complexity of BTCfi itself. Instead of asking users to manually navigate staking layers, liquidity paths, and BTC utility across protocols, more of that orchestration seems to be happening underneath. Users see fewer decisions, but the system itself is quietly handling more of them.
Crypto often misunderstands UX.Making things simpler doesn’t mean removing complexity. Sometimes the harder thing is keeping complexity exactly where it belongs. It reminds me of the internet.
Back then, getting online meant understanding modems and network settings. Today, you just open an app and use it. Not because the internet became simpler, but because the infrastructure underneath became dramatically smarter.
Maybe that’s what makes Bedrock 2.0 interesting, not simpler DeFi. Just a system smart enough to carry more complexity, so users no longer have to carry all of it themselves. @Bedrock $BR #Bedrock $LAB
There was a moment when I realized vibecoding in @OpenLedger was no longer just about making strategies faster. It was changing what “strategy” itself means. Before, a strategy was a clear object you could write down and attach attribution to. But vibecoding blurs that. A strategy no longer holds its shape long enough to stay fixed, because it gets translated through multiple layers while forming.
An idea like “reducing risk during high volatility” used to become a concrete strategy. Now it moves through intent understanding, routing, and liquidity-driven execution, with no single point that can be called its origin.
OpenLedger was built to answer: who contributed to this. But when vibecoding enters, “this” no longer stays still long enough to point at.
I once saw this in an execution. The same intent ran twice, almost identical, but outcomes differed. The attribution graph showed both runs were explained by different contributors. None had enough authority to be called the origin.
A strategy is no longer an object, but a flow of transformations with no original version to anchor to, reshaping itself in a real-time market loop depending on interpretation.
In OpenLedger, attribution is no longer about who created the strategy. It becomes a trace of layers: prompt, model, routing, execution, and market feedback.
There is no central author anymore. Everything is traceable, but there is no origin point. OctoClaw translates intent into market behavior through optimization layers. This strips strategy of a fixed shape. Only temporary states remain.
Sometimes OpenLedger returns two valid attribution graphs for nearly the same intent, with no single reference point for what is “more real.” The question then shifts from who created the strategy to who decides what shape it is allowed to take at each moment. It sounds similar, but it isn’t.
OpenLedger no longer records “strategies.” It records the ability to generate temporary forms of strategies. And vibecoding removes the idea that a strategy ever had an original version. $OPEN #OpenLedger
When the market fluctuates, OpenLedger doesn't change the data but changes how the system reads the data.
There's one thing I really started to see clearly after going through enough cycles in @OpenLedger especially during times when the market begins to run unstable. It's not that the system is broken. It's not that the logic is wrong. It's the same thing, but it feels like it's being 'read' in a different way. In OpenLedger, the initial attribution seems pretty straightforward. Which input generates what contribution, which agent does what, and which flow leads to which output. Everything feels like it can be logged in a clear manner. But the longer I look, the more I realize the issue isn't with 'what happens', but with 'the system deciding what to call a contribution'.
There was a moment when I swapped inside @GeniusOfficial . Not a large trade or anything dramatic, but enough that I had to pause for a few seconds. I picked a route, confirmed it, and when I looked back, the path had already changed before execution finished. No warning, no sense of “which pool I went through” just the outcome appearing.
I used to think liquidity lived inside protocols as if there were pools with TVL and incentives that I simply entered to withdraw from. But after using Genius more, that idea stopped holding up, because it no longer feels like I’m entering any real “pool” at all.
It’s like using a ride-hailing app. You don’t care where the car is parked or who the driver is. You just set a destination, and the system pulls a car that appears when needed.
Once I tried manually changing the route to see how the system would respond. It didn’t reselect liquidity - it rewrote it during execution, collapsing A and B into a single temporary routing point.
Liquidity in Genius doesn’t sit inside any protocol. It gets pulled at the exact moment routing needs it, assembled into a temporary path, then returns to a distributed state.
The protocol is no longer where liquidity is held. It’s just a temporary appearance point in execution. If routing selects it, it shows up; if not, it doesn’t exist in that flow.
I tried tracking which pool was used, but stopped seeing “selected pools” altogether. All I saw was “optimized routes,” and those two no longer overlap the way DeFi used to describe them.
So liquidity is no longer inside protocols. It lives in routing behavior in how the system pulls it out at each moment. Before intent, it’s dormant. After intent, it only exists during execution.
TVL is still there, protocols are intact, but the sense of owning liquidity in the old way has almost disappeared. It’s no longer “inside the system”, it’s “called by the system when needed.”
And I’m not sure whether this is just better UX, or a shift DeFi hasn’t fully named yet. $GENIUS #genius
There’s something I’ve started noticing when looking at @OpenLedger moving into enterprise AI through OpenLedger. It’s not about transparency, but the fact that an output no longer belongs to a single source, yet systems still treat it that way.
In early enterprise AI, things were simple. If the model improved, the system improved. If data was cleaner, results got better. Like thinking a good dish is just about a good chef. As long as KPI looked good, everything was fine.
But at scale, that breaks. Outputs come from multiple layers—model, data, retrieval, routing. Like a restaurant where the dish depends on prep, coordination, and timing. But everything is still compressed into one performance number.
I once saw two teams explain the same pipeline differently. One said model tuning, the other said data filtering and retrieval shifts. Both were right, but no one knew what mattered most.
This is where OpenLedger shifts things. Not just tracing data, but asking where influence comes from. It’s no longer “what’s in the pipeline,” but “what produces the output.” It breaks the idea that every component contributes equally.
Small components can drive most of the result, while “important” layers just pass information. Like prep work mattering more than the chef.
Previously, all of this was one idea: the system is performing well. But OpenLedger forces it into traceable influence layers. The system doesn’t slow down it just loses the illusion that everything contributes equally.
The question becomes whether a system is still efficient if efficiency has always come from a structure of influence it was never forced to name. @OpenLedger $OPEN #OpenLedger
Cheap compute is pushing attribution to become the most expensive cost in OpenLedger
After just a week diving into @OpenLedger I’m starting to realize that it’s not as straightforward as I thought; this time it’s not from the whitepaper or any narrative ‘attribution layer’, but from something very down-to-earth: compute is now so cheap that you don’t even feel it’s being used anymore. It's like opening an app and everything responds instantly. So fast that you don't even think about how much it takes to run behind the scenes. And just when that feeling fades away, another thing disappears too: the awareness that the output had a history to exist.
What made me start seeing @GeniusOfficial differently wasn’t the idea that this terminal helps people trade faster. It’s more that I’ve started noticing crypto becoming a bit less “exhausting” in places where that exhaustion was just considered normal.
Crypto has always had platforms promising better routing and execution, but Genius’s focus on execution quality, programmable signing, and private execution suggests something more fundamental that’s rarely stated openly.
a lot of people don’t lose because they make the wrong decision, but because execution doesn’t keep up with that decision.
It sounds simple, but the market isn’t. Even when people correctly read the narrative, pick the right asset, and time it well, outcomes can still be distorted by inefficient routing, shifting liquidity, execution delays, or the market reacting to intent too early.
The positive part is that crypto has long accepted this as normal. As if participating means you must also understand every layer underneath it. As if investing isn’t just about decisions, but also about operating the infrastructure behind them. And this is where Genius starts to feel different.
The more I look at how they are building the terminal, the more I feel they are reducing the execution work users need to think about. Not by removing control, but by shifting focus from infrastructure to decisions.
It’s like you still choose where to go, but you’re no longer forced to figure out every route, transfer, or technical step no one really wants to deal with. I feel like Genius is pulling trading closer to a simpler experience: You decide what you want. And how it gets executed on-chain is handled more in the background.
Better execution. Less friction. Less unnecessary loss around the edges of a decision. And maybe the most interesting thing about Genius isn’t that it makes traders smarter. It’s that it makes participating in crypto feel less like fighting the system and more like actually focusing on what you intended to do.
There’s a perspective on @OpenLedger that I find quite important, yet it’s rarely explained simply. People usually talk about the AI economy, data marketplaces, or the idea that “whoever contributes gets paid.” It sounds reasonable, but it still sits at an older layer: whoever puts data into the system gets acknowledged.
What OpenLedger is trying to do goes a step further. Instead of focusing on data or models, it focuses on the exact moment an AI generates an answer. The question shifts from “who did it learn from?” to “what is shaping its response right now?”
A single AI response is not decided by one thing. It’s multiple forces working together: data from datanets, retrieval signals, routing decisions, and other context inputs. It’s not one voice, but many small forces pushing the answer in a direction.
The key point is: OpenLedger doesn’t just acknowledge these exist. They try to measure how much each one changes the output. From there, a different idea of ownership emerges: it’s no longer about owning data or models, but owning the degree of influence in the AI’s reasoning process.
A simple analogy: in a group discussion, each person adds something different, and the final answer reflects different influence levels. OpenLedger is trying to make that influence measurable and distributable.
This is a shift. In traditional AI, ownership is static: you contribute once and it’s recorded. In inference-time systems, ownership becomes dynamic: the same data can have different influence depending on context.
There is also a hard question here. It’s not always clear how much a factor influences an output. Sometimes it’s direct, sometimes it flows through layers. So how do we define “impact”, and where is the boundary?
If it works, AI is no longer just producing answers, but something you can trace backward: who shaped each response, and how. And that is the bet OpenLedger is making: not ownership of data, but ownership of real influence at the moment an AI decides. $OPEN #OpenLedger
When invisible labor starts to prove its existence in OpenLedger
Today, I started to view OpenLedger in a different light, not because of any specific feature, but because of how it redefines 'contribution.' It’s no longer just about data, models, or compute. Everything that can influence the output can be traced back. It sounds like a layer of transparency, but the first impression is: this system doesn’t forget anything. In most AI systems, there's a very familiar area that few notice, known as the part where everything gets erased. Data cleaning, preprocessing, filtering, alignment… it all sits there. No one sees it, but without it, the system can’t run. OpenLedger doesn’t disrupt that zone, but it starts to flip the script: if this part has an impact, why isn’t it part of the system’s economy?
When people are busy talking about which terminal has better routes, better quotes, or execution a few milliseconds faster, I keep getting stuck on one small detail about @GeniusOfficial .
It’s not multi-chain or UX. It’s how they mention stealth execution, private execution infrastructure, and execution quality. At first I thought it was just narrative every project claims better execution.
But the more I look at it, the more it feels off. If it’s only about better routes, why emphasize “stealth”? Best quote should be enough. I start to feel Genius isn’t just solving execution, but something behind execution itself.
The more I trade onchain, the more I notice something small. Trades still go through, prices are fine, slippage isn’t bad. But sometimes it feels like the market reacts too early, as if it already inferred my intent before execution finished.
Not clear, but enough to think: “it feels like I got read.” People talk about MEV in bots, searchers, builders. Very technical. But if you strip it away, it feels more human.
Like walking into a store and before you speak, the seller already knows what you’ll buy. No one is doing anything wrong. It’s just that your signal moves faster than your intention.
And that’s where I connect it back to Genius. If execution is only routing, the story ends at best price. But with stealth execution, I think they’re optimizing another variable: how fast intent becomes readable on-chain.
Not “is the trade cheaper”, but “how quickly does the market infer your intent”. That sounds backwards in DeFi, but it makes sense.
Because the more predictable your execution path is, the faster you get priced in before settlement finishes. At that point, you become a pattern. That’s when stealth execution shifts meaning.
Not hiding users from the market, but slowing how fast intent is observed and priced. Not invisible, just not decoded too early. And maybe Genius isn’t competing on better routes, but on keeping a small delay between intent and what the market can infer. $GENIUS #genius
There’s a hard-to-name feeling when you start vibecoding inside a system like @OpenLedger . You think you’re creating something, but the feeling of “creation” appears and disappears before it can settle. What remains no longer feels like creation in the traditional sense.
It’s like telling a familiar mechanic, “just tweak it so it runs better.” But the system doesn’t treat it as a request; it treats it as a signal to reshape how it operates around it.
And this is the first deviation: you think you’re creating, but in reality you’re triggering. Vibecoding starts by nudging a system into a self-propelling direction. Agency is still there, but it’s no longer tied to the outcome.
You adjust a small detail in an agent flow, just changing data prioritization. Nothing significant at the time. But days later, downstream behavior shifts: the agent starts skipping sources that were always prioritized.
No one rewrote the logic. No commit recorded it. It appears without a clear origin. In OpenLedger, execution is no longer a linear input → output chain. It’s a network of overlapping influences. A trace looks clean, but it’s a flattened slice.
When you overlay attribution, the structure fractures. Old datasets reappear in new contexts. Rules inside OctoClaw trigger repeatedly. Other users’ behavior affects the current flow without explicit introduction.
There is no clear origin. Only layered influence. Vibecoding is no longer creation. It’s adjusting the tilt of a system already running. You don’t control execution; you slightly change initial conditions so the system drifts differently.
Like pushing a table in a crowded room. No one is controlled, but movement shifts in a way no one can pinpoint.
Deeper in OpenLedger, attribution doesn’t clarify things. Outputs are intersections of influences. There is no traditional creator. Only a network that legitimizes its outputs. $OPEN #OpenLedger
Intermediate steps are not just important - they are where AI distorts the original question.
Finally, I've discovered something distinctly different about the essence of @OpenLedger compared to other AI projects. I used to think AI agents were pretty straightforward: input goes in, output comes out, and the stuff in between was just a technical pipeline to keep the system running smoothly. If the result is right, then we're good to go; if it's wrong, we tweak the model or the prompt. That perspective made everything look like a straight line, easy to understand and easy to manage. But I was wrong. After examining how a system like OpenLedger operates, that 'straight line' feeling disappears pretty quickly. It's not that the model is more complex, but rather that what determines the output lies in a series of intermediate steps: retrieval, rerank, context selection, tool routing, inference path. And the frustrating part is that none of those steps seem significant enough when viewed in isolation.
I still remember the first time I turned on delegation in @GeniusOfficial . But this time felt different. It wasn’t hesitation about handing control to a system anymore. It felt like accepting that there are market moments where I shouldn’t be participating through emotion.
What I find interesting about Genius is that they don’t soften the idea of “delegation.” They don’t call it an assistant. They don’t say AI is just supporting decisions. They state it plainly: once delegation is enabled, the agent can act without asking again. No confirmation. No extra approval.
That clarity creates a strange feeling. But it’s also one of the rare cases where a system doesn’t avoid the fact that it is receiving real power from the user.
From an execution perspective, it shifts decision-making earlier in the flow. Before doubt kicks in. Before emotion interferes. In fast-moving markets, this isn’t just optimization it removes human latency from the reaction loop.
A lot of strategies don’t fail because the direction is wrong. They fail because humans intervene too late, or change their mind too often.
What’s notable is that Genius doesn’t force this behavior. Delegation is optional. It can be scoped. It can be turned off. There’s no feeling of a black box. At the setup stage, responsibility still clearly sits with the user.
But there’s still tension. When things work well, delegation feels reasonable. When the market moves against you, the choice collapses into either revoking everything or continuing to trust. Not everyone is comfortable with that binary decision.
Maybe this is the hardest part of AI trading not execution itself, but holding responsibility when execution no longer matches expectations.
Still, I understand why this direction exists. If systems are not allowed to act for real, AI remains just a suggestion layer. At that point, it’s not very different from tools we already had years ago.
Delegation isn’t for everyone. It’s for people who understand what part of the decision they are stepping away from. $GENIUS #genius
I’ve been looking at @OpenLedger and noticed something clear: if “Proof of Attribution” works as designed, data spam doesn’t need to be cleaned up anymore it simply loses its place in the economy.
In the past, AI data felt like an open reservoir. Anyone could pour things into it: crawled text, labels, feedback, generated content. And because most reward systems are tied to volume, spam isn’t a “bug” it’s just rational optimization.
What changed my view was how OpenLedger ties rewards to inference-time impact. It’s not about how much you contribute to a dataset, but whether your contribution actually shows up in the model’s output. Data isn’t paid for because it’s included, but because it’s used.
This clicked when I looked back at a dataset I worked with: hundreds of thousands of rows that looked useful, but only a small fraction actually influenced outputs. The rest just sat in storage. Spam emerges naturally when there’s no way to trace impact.
A simple example: if a class is graded by number of submissions, students optimize for quantity. If grading is based on how much your work helps others solve problems, “doing more” stops mattering.
Same with reviews: if all reviews have equal weight, spam floods in. If only reviews that actually influence decisions count, spam loses its value.
OpenLedger doesn’t improve spam filters it redefines data value. From “what you contributed” to “what changed the output.” A small shift in wording, but a big shift in incentives.
Of course, there will always be “intelligent spam” that mimics impact. But the key change is this: spam is no longer a volume game.
In the end, data starts carrying an economic footprint inside AI systems. And when rewards follow that footprint, spam doesn’t get filtered out it simply loses its path to revenue. $OPEN #OpenLedger
OpenLedger and the Real Issue with AI: the Invisible Source of Intelligence
I've noticed something pretty funny but all too common: we usually only start paying attention to the source of quality when that quality dips. You’ve been using an app that runs smoothly for a whole year, then one day it suddenly feels sluggish, and you have no idea why. You used to follow a creator you really liked, but at some point, their content just doesn't have the same vibe anymore. The strange thing is, most of the time, what changes isn't on the surface. The surface often stays the same; it's just what's behind the scenes that quietly shifts without anyone noticing.
A crypto swap usually looks very simple. You click a button, wait a few seconds, and it’s done. But behind a transaction, there are often many possible choices, while the UI makes it look like only one path ever existed.
That’s where @GeniusOfficial begins. It doesn’t try to make the interface prettier. It starts from a simple assumption: what users see is only a condensed version of a more complex execution process happening behind the scenes.
In reality, a swap has never been just about “exchanging A for B.” Behind it are multiple decisions: which route makes more sense, which liquidity pool to use, whether to split the order, or whether to prioritize price or speed. But most crypto UIs pre-select one option and present the result as if:
“This is the only way this could have happened.”
Genius shifts the way swaps are understood, from “action” to “intent.” A swap is no longer: “Execute this order.”Instead, it becomes:“I want to exchange A for B.”
It sounds like a small difference, but the logic changes completely. Once it becomes an “intent,” the system can no longer assume there is only one correct path. It has to evaluate multiple execution paths, weigh trade-offs, and decide based on market conditions.
The UI changes roles too. It no longer silently decides on behalf of the user. It becomes the place that explains what just happened.Instead of simply showing: “Done.”
It becomes closer to: “There were a few ways to execute this. I chose this one because it offers a better balance between price, speed, and execution quality.”
Think of it like ordering food late at night. Normally, you order, the food arrives, and that’s it. But imagine the owner says:
“The kitchen’s busy tonight, so I made it this way because it’ll be faster. The other way might taste better, but you’d have to wait longer.”
Genius doesn’t make crypto feel easier by hiding complexity. It simply refuses to pretend there was only one way things could have happened. $GENIUS #genius
I used to think @OpenLedger was a pretty easy project to figure out.
If AI lacks data, then you build a data layer. That was the market narrative, the timeline kept repeating it, and I naturally went along with it: probably just another story about “AI needing more data.”
But the deeper I looked, the more I felt OpenLedger may not actually be solving AI’s data shortage the way people assume. What they seem to be touching feels way more uncomfortable: the smarter AI gets, the harder it becomes to know how much we should trust it.
I think anyone who uses AI a lot has probably felt this. It answers fast, sounds reasonable, sometimes even like it understands things better than you do. I’ve asked it work questions before and almost followed it without thinking twice.
Then this tiny thought suddenly showed up: “Okay! but where is this actually coming from?”
At some point, it stopped being about whether the answer was right or wrong. I started paying attention to something else: why do I trust this answer in the first place?
That was when OpenLedger started feeling different from how the market frames it. Reading more about attribution and inference, it felt like they’re not just trying to make AI smarter. They’re trying to make intelligence feel less like a black box.
The way I see it is simple: if AI gives you a conclusion, there should be a way to trace what that conclusion is standing on. What knowledge shaped it most, what data contributed to the output, and who created value when the model generated an answer, not just during training.
Because if AI eventually starts touching real money, real decisions, real jobs… then the key question may not be how smart it is.
It becomes this: when AI sounds incredibly confident, do we actually know where that confidence is coming from?
Maybe this is what OpenLedger is really aiming at.
Not exactly “AI needs more data,” but something much more uncomfortable:
AI keeps becoming more convincing ..while humans are getting less certain about why they trust it in the first place.
OpenLedger is tackling a tougher problem: intelligence needs to be seen before it can be valued.
I used to see @OpenLedger as just your typical AI project. But now I’m starting to feel a bit off as I read more about it. It’s not really about whether this 'project' is solid or how long the AI narrative can keep running, since those debates are always going on in the market. What’s keeping me hooked is a rather unsettling feeling: the more I delve into OpenLedger, the more I see folks are looking at it through the wrong lenses. It’s like standing at a train station arguing about which train is the fastest, when maybe the real question is who’s running the entire network.
One day I went back and reread about @GeniusOfficial , and I suddenly thought: if it actually does what it claims, then crypto might have a little less “technical drama.”
Trading in crypto feels like ordering the same dish everywhere, but each place cooks it differently spicy, too salty, or delayed. Execution is not wrong, just unpredictable.
If Genius creates an “execution standard,” it would be like having a system where you order anywhere, the process stays consistent, and delivery time is almost the same everywhere. Sounds amazing. Especially for anyone who has been hurt by slippage.
But life isn’t that simple. Because once everything becomes standardized, people don’t become more well-behaved. They just become more systematic at bending things.
I once saw a rewards app that worked well at first, until users figured out how to chain actions to get more points. The system still functioned, but its original intent quietly changed.
If an execution standard works, it will reduce friction. No more guessing whether the chain is congested or whether the route will fail.
But the other side is always there: when everything is standardized, people find ways to go around the “standard” in more optimized ways.
Crypto has always lived on deviation: price gaps, liquidity gaps, timing mismatches. Those inefficiencies create opportunity. If Genius does this well, some of those opportunities will get flattened.
But that doesn’t mean it’s bad. If you’ve ever waited for a transaction to fail at 2 a.m., you know why “flattening the system” can feel appealing.
When things become more predictable, the market looks for new areas that are less predictable.
Like when a main road is built, people still take side streets not because they like risk, but because sometimes they’re faster when they know them.
I’m not sure whether Genius makes crypto better or just more uniform. But if execution becomes a standard, the interesting parts of the market won’t disappear. They’ll just move somewhere else. @GeniusOfficial $GENIUS #genius
There’s something I’ve started noticing from a question the system keeps avoiding: if intelligence creates value, why has the internet never had a native “payment rail” for it?
It sounds like infrastructure, but @OpenLedger and Payable AI make it feel like a gap that was allowed to exist. AI is paid for compute, APIs, and subscriptions, not for the impact its output has after leaving the model.
It’s like paying for the microphone, but not the sentence that shifts a room.
OpenLedger calls it Proof of Attribution. But it’s not just tracking data. It’s preserving traces of value in a system designed to blur them for scale. Once attribution becomes visible, something uncomfortable appears: value and payment have been disconnected for a long time.
A familiar pattern in viral content: creators make value, but money flows through platforms, algorithms, and ads. AI sharpens this because outputs don’t just get seen—they drive action.
Payable AI is not “AI getting paid.” It’s pricing intelligence at the point it changes system state, not where it is produced. Stripe made internet commerce usable, but it never had to price cognition, where value lives after output, not inside it.
The internet relies on proxies like clicks, impressions, engagement. But as OpenLedger pushes toward attribution and state change, these are incomplete.
If intelligence is priced on post-output impact, then most value capture is approximation. And approximation distorts: some capture too much, some value never returns.
Maybe the internet isn’t missing a payment rail for intelligence. Maybe it already runs through attention, distribution, and platform incentives.
OpenLedger isn’t just building payment for AI. It’s reopening a question the internet postponed: if value lives in impact, where does pricing actually beginand where does it stop?
And if state change is the real unit of intelligence, what happens when it doesn’t stop, but flows into states the system can no longer see? $OPEN #OpenLedger