DApp Connections
Sanke introduces a new way for wallets to connect to dApps — one that prioritizes privacy, minimizes metadata leakage, and removes unnecessary reliance on centralized RPC endpoints.
Traditional wallet connections expose far more information than users realize: IP address, wallet history, full transaction graph, and even behavioral metadata. Sanke eliminates these leaks by redesigning the connection layer around Kohaku’s privacy primitives.
Private P2P Connections
Instead of communicating through public RPC servers or centralized relays, Sanke uses peer-to-peer JSON-RPC messaging, a protocol developed within the Kohaku stack.
No centralized relayer mediating messages
No hidden metadata logged by gateways
No IP exposure to dApps
No RPC-level fingerprinting
Every connection originates locally from the device and reaches the dApp through a P2P channel, ensuring that nothing about the user or device is leaked during the handshake.
This is one of Kohaku’s core goals: enable private, server-less wallet ↔ dApp communication.
One Identity Per App
Sanke automatically generates a fresh, isolated account identity for every dApp you connect to.
This prevents third-party aggregators from correlating activity across multiple protocols:
Each dApp sees a different address
No cross-app transaction graph
No unified profile for tracking or deanonymization
Even if two dApps were compromised or colluding, they cannot link your identities without access to private wallet internals — which they never receive.
Your activity stays compartmentalized by design.
No RPC Dependency
Every dApp call performed through Sanke is validated locally using Kohaku’s light client & execution environment.
This means:
No centralized RPC can track your requests
No metadata logs
No RPC outages blocking transactions
No trust required in external infrastructure
Sanke simply does not rely on a third party to tell it what is happening on-chain. Verification happens on your device — not on someone’s server.
Last updated