unicity-sphere/sphere-sdk-connect-example

Sphere SDK Connect Example is a collection of runnable code examples demonstrating how applications can integrate with a Sphere wallet using the Sphere...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 12 minutes ago
Added to GitGenius on September 1st, 2026
Created on February 14th, 2026
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 32
Total Stargazers: 9,618 (+0)
Total Subscribers: 23 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.7 hours
Mean response time: 34.8 days
90th percentile: 69.1 days
Tracked items: 2

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Sphere SDK Connect Example is a collection of runnable code examples demonstrating how applications can integrate with a Sphere wallet using the Sphere Connect protocol.

The project addresses the need for applications to interact with user wallets—reading balances, sending tokens, and signing messages—without ever accessing private keys. Sphere Connect is a typed RPC protocol where a dApp runs a ConnectClient and communicates with a wallet running a ConnectHost through a message transport. The examples show four distinct integration patterns: a browser-based dApp where users approve transactions in real time, a Node.js service that drives a user's wallet over WebSocket, a bot that operates its own wallet autonomously without approval prompts, and a backend service that authenticates users via signature verification without moving any funds.

Developers should choose an example based on two axes: whose wallet the application uses and what operations it needs to perform. Browser and Node.js examples suit applications that need to move a user's tokens with per-action approval. The bot example is appropriate for autonomous agents like tipping bots, faucets, or game NPCs that control their own funds. The backend-auth example is recommended for applications requiring authenticated user identity—such as games with leaderboards or ownership tracking—but no token movement or custody. The project notes that the bot example runs its own wallet directly rather than using Connect, and the backend example only verifies signatures rather than moving funds.

The project maintains strict SDK version requirements, enforcing a minimum dependency floor at the handshake stage to prevent incompatible clients from attempting connection. The examples are written in TypeScript and include detailed README files for each integration pattern, with specific guidance on testing configurations such as using an iframe path when testing against the hosted wallet rather than a local instance.