Sentinel has announced that it is working toward a migration from its current Cosmos-based chain to Solana and rewriting parts of its decentralized VPN protocol in Rust. This is important news for the Indigitus CasaNode project, because the inherited CasaNode software currently connects to Sentinel’s Cosmos-based network.
It does not mean our work has stopped. It does mean we need to keep the device modular and avoid building new production features against details that Sentinel has not finalized yet.
What Sentinel has confirmed
In its official announcements, Sentinel says that:
- work is underway to move the protocol layer toward Solana;
- the decentralized VPN protocol is being restructured and rewritten in Rust;
- preserving decentralized node discovery remains an objective; and
- more detailed milestones and instructions will be published as development progresses.
Sentinel has also described two possible approaches for moving the P2P token: a phased burn-and-mint process, or a snapshot followed by a Merkle-based claim. Both remain under consideration. The final migration process, production architecture, dates, and any required action for token holders have not yet been published as a completed specification.
The currently released Sentinel node documentation still describes the existing Cosmos-based network and its current node software. That remains the compatibility baseline we can verify today.
Does this delay the Indigitus CasaNode launch?
It changes part of the launch sequence, but it does not block the entire project.
We can continue the work that does not depend on a particular blockchain:
- making the CasaNode boot reliably and recover safely;
- building an outbound-only support and update path;
- improving signed updates, rollback, privacy, and device security;
- handling real household networking conditions such as carrier NAT;
- connecting the CasaNode’s private local status to the GFAVIP display; and
- validating the Raspberry Pi and ESP32 together on physical hardware.
These are necessary for a dependable device whether Sentinel ultimately runs on Cosmos, Solana, or another supported protocol adapter.
What we will not finalize yet is the production layer that depends on Sentinel’s future chain design. That includes new wallet handling, token migration, node registration, blockchain discovery, sessions, payments, rewards, staking, and earning claims.
Our initial local and managed CasaNode pilot can therefore continue. A broader public launch promising Sentinel provider earnings will wait until Sentinel publishes versioned specifications and released software that we can test and support responsibly.
How we are protecting the project from disruption
We are treating Sentinel as a replaceable integration module rather than embedding one blockchain throughout the device.
The CasaNode’s basic health status, secure management channel, update and rollback system, and GFAVIP display contract will remain chain-neutral. Sentinel-specific logic will sit behind its own adapter. This gives us a clear place to support the current Cosmos implementation and, later, a released Solana implementation without redesigning the whole device.
It also means that a blockchain interruption should not prevent the CasaNode from booting, reporting local health, receiving an authorized maintenance update, or showing non-chain GFAVIP content.
What current P2P holders should know
Indigitus is not issuing token-migration instructions at this stage. Community members should rely only on Sentinel’s official channels for future dates and claim procedures.
Please do not share a wallet seed phrase or private key with anyone offering to perform an early migration. A current Cosmos address or mnemonic should not be assumed to map automatically to a future Solana account. We will not build an automatic wallet conversion into CasaNode software based on announcements alone.
Our next milestones
The next CasaNode work remains practical and hardware-focused:
- finish the controlled review of our cleaned and reproducible CasaNode API package;
- continue image hardening and rollback preparation;
- validate the outbound device-management boundary without adding a remote shell;
- complete a supervised CasaNode and GFAVIP ESP32 physical pilot; and
- track Sentinel’s released specifications before authorizing a new chain adapter.
We are encouraged by Sentinel’s continued investment in decentralized VPN infrastructure, and we will follow the migration closely. Our responsibility is to turn that direction into a reliable product only when the interfaces, software, security assumptions, and recovery path can be verified.
We will publish another community update when Sentinel releases implementation details or when our next physical CasaNode milestone is complete.