Dependencies

INTU maintains a minimal set of dependencies to ensure reliability and flexibility. Our primary dependencies are Nostr for decentralized communication and RPC endpoints for blockchain interactions. The only paid service INTU relies on is for blockchain indexers, which we use for speed and performance in the INTU protocol.

Blockchain Indexers (Service)

For blockchain indexing, INTU currently uses Envio as our primary indexer, with Goldsky as a backup. In the future, INTU will have the ability to fall back to traditional RPC endpoints if the indexers are down or unavailable.

Reliability and Risks

Envio and Goldsky are our sole third-party service dependencies. We will always tie in more index service providers if needed. INTU commits to maintaining at least two operational indexers for redundancy. Ideally, INTU would provide a public facing indexer that other users can signal and support (TheGraph being one example).

Nostr (Open Source Communication)

Nostr is an open-source protocol for decentralized social networking and communication. INTU uses Nostr to enable users to connect via their own NOSTR relay or a public one if they choose.

Reliability and Risks

Nostr is open source, so it cannot go dark in the traditional sense. However, if it becomes unmaintained, it might stop working with modern technology at some point in the future. Nostr is only used for the facilitation/creation of NEW accounts, so any old accounts would not be affected in it's absense. And, there are other open source communication protocols INTU can use in the future if needed.

RPC Endpoints (Blockchain Interaction)

RPC endpoints serve as our primary method for pushing data to chain.

Reliability and Risks

INTU relies on a combiniation of public and private RPC endpoints to push blockchain interactions and transactions to chain. We also allow the end user to use their own RPC endpoint if they so choose.