Integritee RPC decision checklist
Before you point a wallet, indexer, or dApp at an Integritee node, confirm four things:
- Network status. Integritee announced that the network would shut down on November 11, 2025. If you are reading this after that date, assume public RPC endpoints are no longer maintained.
- Data availability. If you need historical blocks, check whether the node or provider keeps an archive. A pruned node only serves recent state.
- Protocol access. Substrate-based chains expose HTTP JSON-RPC and WebSocket endpoints. Make sure your client uses the right protocol for subscriptions.
- Exit plan. If your application still depends on Integritee, plan a migration path before the endpoint disappears. The rest of this article explains what to check and how to move forward.
What is Integritee?
Integritee is a blockchain network designed for privacy-preserving data processing. It combined the transparency of a public Substrate-based blockchain with the confidentiality of Trusted Execution Environments (TEEs), such as Intel SGX. The project launched on Kusama as a parachain and planned to expand on Polkadot.
At a high level, Integritee separates public consensus from confidential execution. The public chain handles balances, governance, and an on-chain registry of enclave attestations. A sidechain or off-chain execution environment processes application logic over private data. Results are anchored to the public chain so users can verify that a computation happened without exposing the inputs.
Developers used Integritee to build dApps that need to compute over sensitive data without revealing raw inputs. The main use cases included identity, health data, confidential analytics, and other applications where privacy is a feature. The network aimed to support GDPR-oriented workflows by making privacy-preserving data processing auditable.
The network’s token is TEER. Token holders participate in governance and staking. Because Integritee is built with the Polkadot SDK, its RPC interface follows the standard Substrate JSON-RPC conventions.
Integritee network status and the November 2025 shutdown
The official Integritee website announced that the network would shut down on November 11, 2025. That announcement has major implications for anyone who runs or uses Integritee RPC endpoints:
- Public endpoints may stop responding once the network winds down.
- Collator and validator operation may be discontinued.
- Applications that depend on TEER transactions may lose access to live state.
If a network is shutting down, verify the exact status from the project itself rather than relying on a third-party RPC page. An RPC endpoint may still answer a system_health request, but that does not mean the network will keep producing blocks or that token transfers will remain available.
This matters for a simple reason: a privacy network that is no longer producing blocks cannot provide the trust guarantees it was designed for. Even if a cached endpoint returns old data, new transactions will not settle, and the confidentiality model based on on-chain attestation loses its foundation.
Integritee RPC endpoint settings
Because Integritee uses the Polkadot SDK, a node exposes the same standard ports as many Substrate chains:
| Setting | Typical value |
|---|---|
| HTTP JSON-RPC | 9933 |
| WebSocket JSON-RPC | 9944 |
| P2P port | 30333 |
| Chain specification | Integritee mainnet |
If you run your own node, --rpc-port and --ws-port control the RPC ports. A managed provider typically gives you an HTTPS URL and a wss:// URL plus an API key.
A local node start command might look like this:
./integritee --chain mainnet --rpc-port 9933 --ws-port 9944 --port 30333
Note that if the Integritee binary is no longer actively maintained, it may not sync reliably after the shutdown. Check the official repository for the last release instead of assuming a stale binary will behave correctly.
When you use a remote endpoint, you usually append an API key or use a provider-specific path. Do not hardcode a known public endpoint in a production application unless you have confirmed that the provider still supports it.
How to query an Integritee RPC endpoint
The standard way to test any Substrate-based RPC endpoint is a JSON-RPC POST request. The system_health method reports whether the node is syncing, while chain_getBlockHash returns the hash of a block at a given height.
curl -sS -X POST 'https://<integritee-rpc-url>' -H 'Content-Type: application/json' -d '{"id":1,"jsonrpc":"2.0","method":"system_health","params":[]}'
A healthy response looks like this:
{"jsonrpc":"2.0","result":{"isSyncing":false,"peers":12,"shouldHavePeers":true},"id":1}
For WebSocket subscriptions, use a client that supports wss://. Here is a minimal Node.js subscription to new chain heads:
const WebSocket = require('ws');
const ws = new WebSocket('wss://<integritee-wss-url>');
ws.on('open', () => {
ws.send('{"id":1,"jsonrpc":"2.0","method":"chain_subscribeNewHeads","params":[]}');
});
ws.on('message', (data) => {
console.log(data.toString());
});
The same JSON-RPC pattern applies to other Substrate chains. If you are building a new integration on an active network, you can follow this pattern with the correct endpoint. OnFinality publishes the chain settings for supported networks on the supported RPC networks page, and you can compare RPC pricing before choosing a provider.
What to check before building on Integritee today
The table below summarizes the criteria that matter when you evaluate an RPC provider or decide whether to keep an Integritee dependency.
| Criterion | What to check | Why it matters |
|---|---|---|
| Network status | Official announcements and block explorer | An offline or frozen network makes RPC calls fail and may block token operations |
| RPC provider availability | Current endpoint URLs, key requirements, and maintenance notices | Public endpoints can disappear without warning during a shutdown |
| Archive data | Whether the provider stores historical state | Indexers and analytics need old blocks, not only recent head state |
| WebSocket support | WSS endpoint and subscription methods | Wallets and dApps rely on real-time event and new-head updates |
| Alternative chain | Privacy and TEE guarantees on other Substrate chains | Moving an application to a new chain requires matching confidentiality requirements |
Use this table as a starting point. If you are evaluating a provider for a production workload, check their documentation for rate limits, failover behavior, and whether they support both HTTPS and WSS. The criteria are especially important when the underlying network is changing status, as Integritee did.
Where to run RPC infrastructure as Integritee winds down
When a network is shutting down, new projects should not build on it. For existing projects, the priority is moving to a network with active development and a supported RPC ecosystem.
OnFinality provides both managed RPC endpoints and dedicated node infrastructure for a range of active networks. You can check current coverage on the supported RPC networks page. If you need predictable cost and a workload-specific setup, the RPC pricing page shows how plans are structured.
A managed provider is useful when you want:
- HTTPS and WSS endpoints with a stable URL.
- API keys that can be scoped per project.
- Monitoring and failover on the provider side.
- A way to test multiple networks without running nodes locally.
If you need full control, a dedicated node gives you direct access to a node that you can tune for archive data, WebSocket connections, or specialized monitoring. Always verify that your chosen provider explicitly lists the network you want; do not assume coverage.
You should also consider the operational side of a shutdown. If you ran an Integritee node yourself, evaluate whether the same hardware can be reused for a different chain. If you used a public RPC provider, export your configuration and replace the Integritee URLs before the service is decommissioned.
Migration checklist for existing Integritee applications
If you have a live Integritee application, work through this checklist before the shutdown makes changes harder:
- Export and back up state. Extract any application state, encrypted data, or keys that live outside the chain.
- Audit TEE assumptions. Integritee used enclaves to keep data private. Find out whether your data flow depends on a specific enclave implementation or remote attestation process.
- Choose an alternative network. If you need similar privacy, look at active Substrate or Polkadot-based chains that offer TEE, Zero-Knowledge, or other confidentiality tooling.
- Update RPC endpoints. Replace any hardcoded Integritee URLs in your client configuration with endpoints for the new network.
- Test subscriptions and batch calls. Confirm that the new provider supports the WebSocket methods and JSON-RPC batch calls your dApp uses.
- Notify users. If user funds or personal data are involved, give clear instructions about the network transition.
- Monitor after migration. Watch for sync gaps, failed extrinsics, and missing events during the first week.
By treating the migration as a separate workstream, you avoid the situation where a dApp is live but pointing at an endpoint that no longer exists.
Key takeaways
- Integritee is a Substrate-based privacy network that used Trusted Execution Environments for confidential data processing.
- The network announced it would shut down on November 11, 2025, so public RPC endpoints may no longer be reliable.
- Standard Substrate JSON-RPC methods apply, but you should verify the network status before sending any production traffic.
- When choosing RPC infrastructure, check current endpoint availability, archive data support, WebSocket access, and the provider’s published network list.
- For active networks, managed RPC services and dedicated nodes from OnFinality can simplify infrastructure. Check the supported RPC networks and RPC pricing pages for current details.
Frequently Asked Questions
Is Integritee still running?
The Integritee project announced that the network would shut down on November 11, 2025. If you rely on the network, verify its status from official sources before assuming that RPC endpoints will keep responding.
Can I still use Integritee RPC endpoints?
You can try the endpoint you already have, but public endpoints may stop after the shutdown. If you run your own node, check whether it is still syncing and producing blocks.
What should I use instead of Integritee?
It depends on your privacy and computation requirements. Look for an active network that provides the TEE, zero-knowledge, or data-protection features you need, then confirm that your chosen RPC provider supports it. OnFinality lists supported networks on its supported RPC networks page.
Related resources
Originally published at OnFinality.
Top comments (0)