Ellison_

A robot paused in the wrong spot. Nothing happened. No damage, no injuries. And yet, it still triggered a full incident report. That’s when the paperwork avalanche hit. Not because anyone panicked, but because everyone knew what comes next: auditors, insurers, maybe even regulators. And the only question that mattered? Painful but simple: who signed off on that action?
Thinking more about it, I realized how complicated things get when autonomous robots and AI systems span multiple organizations. One team builds the model, another handles deployment, a third manages on-site overrides, and the safety team writes the “rules” without ever touching the code. The robot’s behavior ends up being the sum of all these pieces. Yet someone still has to be accountable. Responsibility needs a name, a signature, a trail. The law doesn’t accept “it just emerged from the system.”
This is why I keep coming back to @Fabric Foundation . To me, it’s not just another product it’s infrastructure that could change how accountability works. If approvals and changes can be verified across parties, the cost of disputes drops drastically. The first users will likely be regulated operators who already live with audits: hospitals, logistics fleets, public deployments, insurers. It can work if it’s cheaper and more reliable than the current scramble for evidence. But it falls apart if it’s optional or if participants refuse to treat the shared record as real when it works against them.
#ROBO $ROBO @FabricFND

@MidnightNetwork brings real Blockchain Utility and true Rational Privacy to developers and users. No longer must users have to choose between being private and a blockchain being useful. With Midnight Network users have full control of their data, and are able to choose what to reveal and what to keep private, while still benefiting from the on-chain proof required for a blockchain to be useful. Finally, real privacy for crypto.
So that’s Midnight. A concept based on the separation of public and private state for every transaction. In Midnight, contracts are written in a TinyTS (a tiny version of TypeScript) dialect that we call Compact. The contracts are run on the user’s local machine, and a zk-Proof of correctness is provided without releasing the private inputs. Transaction data and metadata is private by default in Midnight, but can be disclosed as required for business, regulatory or audit purposes. Recursive zk-SNARKs enable this functionality and as a developer you get to work on blockchain based applications as you would normally, but with the extra feature of privacy by default.
This is not theory, there are countless use cases that will solve a multitude of problems people and organizations encounter. Some examples include: Vote systems where the voter gets a proof of having voted in a way that does not reveal which vote. Decentralized identity apps that verify that a person is older than 18, that they completed a full Know Your Customer (KYC) process etc, while not having to disclose in full their passport or credit report. Dark-pool exchanges that keep all bids and prices confidential until after a trade is settled. Health care systems that verify a patient has given consent and is eligible for certain services without having to disclose the full health record. Supply chains where the origin and components of products can be verified in supplier contracts without having to disclose the full contents. Our partners, Midnames, Triple Play and Webisoft are already building Decentralized Identity apps, private credit scoring, and confidential exchanges using verifiable credentials and ZK predicates.
Who is behind this? Well the people behind Shielded Technologies are quite well known within the cryptocurrency space. Midnight is a long term project, one that has been in the works for many years. It’s based on a number of pieces of research that have been carried out internally by a team of researchers from Input Output Global. The same team of researchers that are behind the Cardano project. The chief scientist at Input Output Global, Professor Aggelos Kiayias, and other academics including Professor Elias Koutsoupias have been writing a number of papers on the subject of sidechains, private smart contracts and also Minotaur a consensus protocol. Shielded Technologies are carrying out the engineering work on Midnight and the Midnight Foundation will assist in the project’s journey to full decentralisation. Midnight is also one of the first official partner chains of Cardano, and as such, all the security of the Cardano network will be inherited as Midnight will be using merged staking.
We are fueled by NIGHT tokens, which were launched in December 2025 after a multiphase Glacier Drop in what is arguably one of the most fair token distributions in the history of crypto. Unshielded governance and capital reserve, NIGHT is not a fee bearing currency. By simply holding NIGHT in your wallet, you will also earn DUST our shielded transacting and smart contract executing currency, which acts as the rechargeable battery of the network. DUST burns down and cannot be transferred. Night supply is capped at 24B and all block producers are paid in NIGHT. Future on chain governance will allow Night holders to vote for treasury direction and protocol upgrades.
As things are, as far as the market price is concerned, NIGHT has somewhat recovered from the wild swings it saw during its initial launch. As of mid-March 2026, NIGHT is sitting at about $0.050, with a market cap of about $831 million, with 16.6 billion tokens in the market (out of 24 billion total) and with the daily trading volume being more than $140 million. Currently, it is ranked at about 80th place by market cap. It managed to reach an all-time high of $0.11 during its early days. Now it is time to look beyond the market price and to see if there is some real-world adoption.
The pace of progress on the roadmap remains strong and we have just finished the Hilo phase of the roadmap. This involved having NIGHT live on the Cardano blockchain to provide liquidity and to further test out the tokenomics. We are now moving into the Kūkolu phase of the roadmap, which will see the deployment of a federated mainnet with a set of trusted validators (including a couple of partners from Google Cloud) who will create the genesis block and deploy the first production privacy applications. The subsequent phases will see the addition of further validators, full decentralization and further cross-chain hybridization. We continue to deploy applications to testnet, and the Midnight Academy and new AI tools are having a significant impact on the productivity of our development team.
I’m quite bullish on Midnight’s prospects. A future where there is heavy regulation on cryptocurrencies and users want to remain anonymous is likely to have a need for a privacy-preserving, compliant, decentralized platform for tokenized assets, AI or enterprise dApps. Midnight does more than just add privacy to a system, it makes the privacy that is used in that system actual, auditable and in the control of the user what I call sovereign. With a solid research base, a fair token model and a community of passionate developers building real products, Midnight is poised to become the backend of choice for the next wave of blockchain innovations while finally delivering on the promise of cryptocurrency: freedom and privacy.
#night @MidnightNetwork $NIGHT

Must have been first thing in the morning, probably about 7 a.m. as I seem to have left my coffee undrunk next to the keyboard.
I have been giving some thought to trust in systems that are robotised. Everything is OK when robots are contained within the laboratory. When robots are placed in the wider environment of the public space with citizens, then this is no longer the case. I find myself asking a simple question: who in this scenario is the arbiter of truth?
As I went through the paper again I started to actually get what ROBO is talking about. The idea is actually very simple. Every robot will have its crypto-identity; like an passport. All the information about capabilities, rules and boundaries will be openly available as metadata and not locked behind some corporate wall.
The part that really struck me is how the activity of taking down the drones would be tracked. This information would not be stored on some internal system on the drone itself. Instead the task performed by the drone, the output of that task and the feedback received on the task would all be posted to an open system essentially the drone’s activity would be posted as a social update to a platform available for public scrutiny. No way to hide the drone activity later, it would all be out there for good.
The timing seems weird. Fabric’s 2026 roadmap has us starting off with concepts such as robot identity, the workflow of completing tasks, and collecting structured data. And about this time Binance had listed ROBO on March 4, bringing lots of new attention to it.
A better answer to the question I posed in my previous post might be that the hype surrounding Apple and other recent stock market advances is irrelevant to the core subject of my inquiry. But to be honest, the market excitement isn’t the part that interests me most.
What struck me was not the talk of the town, but the few things that were being done quietly behind the scenes. Example number one: the Global Robot Observatory, in which the behavior of robots would be open to human observation and scrutiny. Example number two: the ongoing effort to create a permanent record of ground truth. First-hand experience has shown me just how important that effort will be in the years ahead.
Personally this part of the project is more important to me than the usual marketing fluff. Real trust isn’t built by soaring prices, or market hype. It’s built on something more mundane. Something even more fundamental than mere code, or an architecture. It’s built on something simple, yet utterly vital. Boring stuff. Unremarkable facts that remain as they were written, unaltered and unchangeable over time. Facts that can’t be modified in the dead of night, or revised to suit a future agenda. Just unbending, unalterable records of the past.
#ROBO $ROBO @FabricFND

I was skimming a post on robot data rights. What had started out as what feels like a somewhat abstract argument was rapidly becoming a much more tangible one very relevant to many of the systems and topics I’m tracking. As I bounced from one related post to the next, one question kept coming up – who gets to decide what happens in any particular system at any particular time? While catching my breath and having a quick look at the Fabric Foundation as one example of a platform which might help answer that question, the whitepaper there gave me a fairly strong impression of how this type of system might be implemented and hence a better feel for what’s actually going on. Having read the whitepaper, I then went on to read Fabric’s 2026 roadmap which gives a fair amount of detail about what the Foundation has in mind for the future. Among many other things, this includes robot identity, task settlement, data collection and other items, with what feel like very reasonable additions such as verification of incentives for tasks that can be paid out.
This is an interesting timing, to say the least. Fabric’s paper on Fabric was published by Fabric in December, and the $ROBO token was launched in February, roughly around the time the EU Data Act has come into effect, and the AI Act is on track to be enforced in 2026. It feels to me that all these things are becoming from vague concepts to tangible things, and thus becoming real to the end user. One thing that I think has changed for good is that we went from having a vaguely permit given to data, to having the right to access that data being based on auditable terms of that permit. For a long time permissions have been based on trust, which more or less boils down to a “I trust you, go ahead and use this data” feeling, rather than on real permissions with well defined terms and conditions, which have been rarely if ever used as the basis for giving permission to access our data. What has changed is that the conversation has become a bit more real and I feel that having access to our data is just the beginning. Access to the data in our wallets or in our PCs is not enough to change the way we interact with permissions to access that data in an end to end fashion. Access should be auditable in terms of what has been granted to be eligible to get access, under which conditions such permission has been granted, and, most importantly, on what terms and how such access has been used.
#ROBO $ROBO @FabricFND

This is the problem that motivated me to read about @MidnightNetwork . Every blockchain follows a dictum that we call “don’t be evil” and that is “everything must be open”. The open nature of blockchains was a core tenet of many of the first crypto projects, and there is a solid base for this idea. But with openness comes a set of new issues that become roadblocks for any businesses trying to operate. Midnight Network is a project that aims to reach a better balance in the openness of a blockchain.
Our latest project, Midnight, is a privacy blockchain that will be used as the companion chain to Cardano. Instead of being yet another competing blockchain, Midnight aims to create a completely new use case where participants are able to share encrypted and sensitive information in a private manner but with the data still being auditable and on-chain. To achieve this Midnight will be leveraging advanced cryptographic techniques such as zero-knowledge proofs, which enables one to prove that some statement is true without necessarily revealing any information about how such proof was constructed. Using zero-knowledge proofs as an example, users can demonstrate to a bank that they have all of the qualifications and characteristics required to receive a loan, for example, without having to show any personal ID or priiate documents.
The thing that I find very interesting about Midnight is the programmable privacy. All the other privacy coins obfuscate all transactions, and that’s the core promise that most users are used to. In the case of Midnight, as a developer, you can choose at different points in the transaction flow, what is private and what you choose to reveal at a given time, which is a concept that we are calling rational privacy. Where something is private by default but then at a later stage in time it could be disclosed to a specific auditor, or set of auditors or even to the regulators.
Zero knowledge cryptography in the form of zk-SNARKs is used for privacy-preserving smart contract interactions and transactions on the network. This means that complex computations can be made on sensitive local data without ever revealing the data itself. Instead of publishing sensitive information to the blockchain, only a cryptographically verifiable “proof” that the smart contract rules have been followed is published, allowing sensitive information to remain private while still being verifiable, decentralized and secure.
One alternative design path for Midnight is the economic design. The NIGHT token will be the token of the NIGHT ecosystem: the governance and capital token of the network. Locking it will reward the user with DUST, an independent resource used for personal transaction and execution purposes. This trade-off is not something you would see in a traditional blockchain design. It is a design choice that is heavily influenced by the fact that having governance value in the unlocking mechanism of a primitive as well as having costly transaction fees is a bad way to leak sensitive metadata.
Privacy in blockchains, which is something that I think Midnight is quite pivoting to. A lot of projects think of privacy as a layer on top of a base layer blockchain, but I think Midnight and the Tardigrade protocol that it is built on is positioning privacy more as a infrastructure layer that can be programmed in. So, if this works, there’s loads of applications in finance, for identity, for healthcare and for business where you want to keep information private but you also want it to be available in such a way that it can be seen and verified on the blockchain. I think the privacy/visibility trade-off is the key to getting blockchain out of the early days of “proof of concept” and into some more real-world use cases.
#night $NIGHT @MidnightNetwork

One thing immediately stood out to me. It doesn’t approach robot development the way most people imagine, where everything happens quietly inside a closed lab and upgrades appear out of nowhere. Fabric seems to view robot progress as something that can happen in a more open and coordinated environment. From what I understood while going through the whitepaper, the idea is to build a network where general purpose robots can be created, governed, and gradually improved with the help of a public ledger. Data, computing power, and oversight are all part of the same system. What made this interesting to me is that better robot decisions don’t really come from raw data alone. Real progress usually happens when the whole process around it such as training, validation, skill upgrades, and responsibility is visible and aligned so the people involved actually have the right incentives.

Another part that really caught my attention was how Fabric treats robots as modular systems instead of fixed machines. The idea of adding or improving abilities through “skill chips” made the evolution process feel more collaborative rather than static. It gives the sense that robots can slowly expand what they are capable of instead of being redesigned every time something new is needed. Then when I looked at how $ROBO fits into the ecosystem through fees, verification, and governance, it started to make more sense to me. The system naturally creates a way to coordinate who contributes, who verifies the work, and how improvements are recognized. For me, that structure is what makes the model feel durable over time, not just an ambitious concept written in a document.
#ROBO $ROBO @FabricFND