TipLink

• Name: TipLink
• URL: https://tiplink.io/
• Category: link-wallet and asset-distribution company / campaign-and-dispenser operator / Solana onboarding and wallet-adapter company
• Tags: solana-ecosystem
• Summary: TipLink now belongs in companies/ as well as projects/ because the practical dependency is no longer only the link is the wallet product mechanic. The named TipLink operator now packages TipLink Wallet, TipLink Pro, Email TipLinks, and the TipLink Wallet Adapter under one brand, while controlling API-key issuance, client-ID issuance, campaign and dispenser tooling, Google-sign-in wallet onboarding, and email-delivery workflow. Public materials still expose a somewhat thin legal map — the docs currently surface both TipLink Corp and TipLink, Inc. language — but the branded company boundary is already real enough to matter analytically.
• What it does:
  • Operates the TipLink wallet product that turns a URL into a Solana-native asset handoff for SOL, SPL assets, NFTs, and SFTs
  • Packages TipLink Pro for large-scale distribution flows, including campaign creation, dispenser management, mint flows, analytics, and anti-abuse controls such as captcha and fingerprinting
  • Offers Email TipLinks as an API-gated delivery path routed through a secure-enclave design that the docs say prevents TipLink from seeing private keys directly
  • Offers the TipLink Wallet Adapter so third-party sites can embed TipLink’s Google-sign-in wallet experience behind a company-issued client ID
  • Controls the public developer and support admission path through contact@tiplink.io / Discord-based access requests for backend email APIs and wallet-adapter credentials
• Key claims:
  • The main site currently presents a three-part product shell — TipLink Wallet, TipLink Pro, and TipLink Wallet Adapter — which is the clearest signal that a company note is now warranted rather than keeping everything collapsed into one product note
  • The TipLink Pro API docs say the main class interfaces with campaigns and dispensers, and expose API-key-gated creation, pausing, refreshing, deletion, analytics, and premium-theme hooks, which makes TipLink a real distribution operator rather than just a wallet UX brand
  • The Email TipLinks docs say links travel through a secure enclave such that TipLink Corp never sees the private keys, but those same docs also say Email TipLinks require a backend API key requested from TipLink, which means the company controls who gets access to this delivery surface
  • The Wallet Adapter docs say integrators need a client ID from TipLink and describe a Google-sign-in self-custodial wallet flow for third-party sites, which makes TipLink the operator of an embedded onboarding surface rather than only a direct-to-user wallet app
  • The accessible public materials still provide a somewhat incomplete legal map, with TipLink Corp appearing in product docs and TipLink, Inc. appearing in docs-footer output observed during this pass, so the safest current framing is named company/operator boundary with imperfect public legal labeling
• Whitepaper: No standalone company whitepaper is the point here. The clearest current primary materials are the live site product cards and the product docs for TipLink Pro, Email TipLinks, and Wallet Adapter; see ../whitepapers/tiplink-company-boundary-primary-sources-2026-08-12.md.
• Sources:
  • https://tiplink.io/
  • https://docs.tiplink.io/docs/products/client
  • https://docs.tiplink.io/docs/products/email-tiplinks
  • https://docs.tiplink.io/docs/products/wallet-adapter
  • https://docs.tiplink.io/docs/getting-started/overview
  • https://docs.tiplink.io/sitemap.xml
  • https://github.com/TipLink

Internal linkages

• Product-layer note: tiplink.
• Useful wallet-and-onboarding operator comparisons: backpack, crossmint, and passkeys-foundation.
• Useful contrast where the product surface is smaller than the operator shell but still matters on its own: qr-wallet and qr-wallet.

Protocol / company boundary

• Keep tiplink on the product mechanics: URL-as-wallet behavior, Solana-only scope, public API primitives like TipLink.create() and TipLink.fromLink(...), and the user-facing claim / onboarding flow.
• Keep this company note on the named operator shell above that mechanic: TipLink Pro campaign tooling, dispenser management, anti-abuse controls, Email TipLinks access, Wallet Adapter client-ID issuance, and the company-run Google-sign-in onboarding path.
• That split matters because how does a TipLink work? and which company controls scaled distribution, embedded onboarding, credential issuance, and delivery policy around TipLink? are related but not identical questions.
• Until stronger primary legal materials surface, preserve the ambiguity explicitly instead of pretending the public entity map is already crisp.

Control surface

• Practical leverage sits in API-key issuance, client-ID issuance, campaign creation, dispenser lifecycle controls, captcha and fingerprinting defaults, email-delivery access, embedded-wallet rollout, and the branded onboarding path that lets users claim through Gmail instead of a preexisting Solana wallet.

• The sticky dependency is not only the wallet URL format. It is TipLink’s company-run distribution shell for mass campaigns, recipient delivery, anti-abuse policy, and embedded wallet access.

• TipLink’s self-custodial positioning reduces one class of custody risk, but it does not eliminate company power over who can industrialize the product, embed it, or rely on the higher-level distribution surfaces.

• Read TipLink as a company-run Solana onboarding and asset-distribution control plane, not just as a clever link wallet.

• Last reviewed: 2026-08-12 UTC