Cowrie Research

rhinestone-primary-sources-2026-04-22

4 min read

Rhinestone primary-source snapshot

Fetched: 2026-04-22 UTC

1) Official docs: what Rhinestone is

Source: https://docs.rhinestone.dev/home/introduction/what-is-rhinestone

Selected excerpts from the docs:

Rhinestone is a smart wallet SDK and crosschain intent API. It combines a modular smart account toolkit with an intent-based transaction engine, giving teams a single integration for deploying wallets and routing transactions across any supported chain.

Rhinestone offers three core services:

  • Modular Smart Account toolkit, compatible with all major embedded wallet signers
  • An Intent Engine (Warp) for single- and multi-chain transaction and swap routing
  • A Relayer Market that aggregates solver liquidity for intent execution

Additional signals from this page:

  • Docs emphasize passkeys, session keys, multisig, recovery, and embedded-wallet-provider compatibility
  • The Warp section claims universal gas sponsorship, multi-input intents, deterministic execution or rollback, and human-readable EIP-712 signatures
  • The page frames the product as signer-agnostic, modular, and usable via REST API even without the full SDK

2) Technical overview of Warp

Source: https://docs.rhinestone.dev/home/introduction/rhinestone-intents

Selected excerpts from the docs:

Warp is Rhinestone’s intent routing and execution engine. It aggregates crosschain settlement layers through a unified solver market and executes intents with sub-2-second confirmation times.

A Warp intent is a signed declaration of what the user wants to happen: which tokens to spend, on which chains, and what to execute at the destination. The user signs once — Warp handles the rest.

Origin chain settlement happens asynchronously after the destination fill. The user’s transaction is complete once the fill lands — they don’t wait for settlement finality.

Additional implementation notes from this page:

  • The Orchestrator indexes balances, finds routes, builds transactions, and broadcasts intent operations to the relayer market
  • Docs say settlement layers such as Across, Relay, and Eco are aggregated through direct onchain integrations rather than simple API aggregation
  • The system supports origin and destination executions inside one signed intent and uses a multi-chain EIP-712 structure intended to stay human-readable

3) Smart Sessions / delegated permissions

Source: https://docs.rhinestone.dev/smart-wallet/smart-sessions/overview

Selected excerpts from the docs:

Session keys are cryptographically signed keys generated by a user’s master key (passkey, ECDSA, or multisig). Smart Sessions enables session keys to be created and used with all major smart account implementations (via ERC-7579) and is fully compatible with Rhinestone’s Warp transaction infrastructure.

Key example use cases include:

  • Skipping confirmations: Store a session key locally for “one-click trading,” allowing seamless decentralized application (dapp) interactions without repeated signing prompts.
  • Automating transactions: Users share a scoped key for server-side execution…

Additional signals from this page:

  • Sessions are modeled around owners, actions, and policies
  • Supported policy types include spend limits, timeframe limits, usage limits, and call restrictions
  • Docs explicitly warn that smart-session support is experimental and note that permissive defaults should be restricted with relevant policies

4) Breadth of public docs and audit references

Sources:

Selected excerpts and signals:

Learn what chains our services are deployed on

Today, we support Across, Relay, and Eco.

Additional signals from the docs index and resources pages:

  • The docs index exposes API endpoints for account registration, intent submission, route discovery, supported chains/tokens, portfolio retrieval, deposits, withdrawals, sponsorship, widgets, and status tracking
  • Supported-chains docs list smart-account-infrastructure mainnet support on Ethereum, Base, Optimism, Arbitrum One, Polygon, Avalanche, Gnosis, Scroll, BNB Smart Chain, and ZKsync Era
  • Audit-reports docs link to public repositories and reports for the module registry, safe7579, core modules, Smart Sessions, WebAuthnValidator, and Nexus

Notes

  • This pass did not locate a classic whitepaper or litepaper from official Rhinestone sources.
  • The docs portal appears to be the primary source of truth, supplemented by public audit-report links and referenced repositories.
  • Because parts of the source set are product/docs pages, specific performance claims (for example sub-2-second fills) should be treated as official claims rather than independently verified measurements.

Graph View