Inside the Protocol
A deep dive into the decentralized architecture, cryptographic identity resolution, and high-performance infrastructure that powers Tagwise.
User App
Consumer Application
TIP Client
TipClient.resolve("@alice")
Fast API Resolution
HTTP GET /v1/resolve
Redis
(Memory)
Postgres
(Disk)
Direct On-Chain
RPC getAccountInfo
Applications Layer
CONSUMER UXWallets (Phantom, Solflare), dApps, DEXs, and widgets requesting resolution.
TIP Client SDK
npm: @tagwise/tip-sdkLightweight TypeScript library with local response caching and fallback RPC logic.
TIP Edge API
EDGE GATEWAYHigh-concurrency globally distributed edge workers providing REST & GraphQL.
Resolver Core
PROTOCOL ENGINECryptographic proof engine that verifies Anchor state signatures and proofs.
TIP Indexer
REAL-TIME SYNCEvent-driven indexer tracking on-chain Anchor account mutations and delegations.
TIP Registry Program
ANCHOR SMART CONTRACTOn-chain smart contract maintaining canonical tag-to-address bindings.
Solana Devnet
LAYER 1 STATEThe base settlement layer providing sub-second finality and cryptographic consensus.
Zero-Custody Guarantee: At no point in the 7-layer stack does Tagwise hold, custody, or intercept payment funds.
Architecture Comparison
TIP vs. SNS
Note: TIP and SNS serve complementary layers on Solana. SNS handles general Web3 naming and profiles, while TIP is optimized exclusively for instant financial checkout and merchant routing.