TIBBIR Universe · Saved post receipt · 1955664675166720101

MopHandle

@MopHandel · Published: Wed Aug 13 16:16:07 +0000 2025

Original post on X · Full data receipt · Backup index

Saved archive render, not a screenshot of the original X page. Full captured content is retained below; capture gaps are stated explicitly. Video files are not stored.

Crossmint — Ribbit led the latest $23.6M round. Fireblocks — Ribbit co-led the $310M Series C. Razorpay — Ribbit is an early/ongoing backer (participated in multiple rounds). TechCrunch SafetyKit — Company lists Ribbit as an investor. Lightspark — Investor rosters include Ribbit (alongside a16z/Paradigm, etc.). Decagon - Ribbit Capital participated in Decagon's $131 million Series C funding round, which valued the company at $1.5 billion Stack fit: The companies @ribbita2012 keeps name-checking line up almost perfectly with the primitives $TIBBIR needs: Identity/credentials & tokenization: Crossmint/Forge, SafetyKit. Agent permissions & execution: 4337/session-key style ideas, policy/permit tokens. Institutional custody & controls: Fireblocks/MPC for agent-safe treasury ops. Payments/settlement rails: Lightspark/Razorpay for turning intents into money movement. Context provider/understanding: Decagon is a natural source of those claims. high-quality, machine-legible claims to verify as the "understanding & tokenization” layer Ribbit’s cap-table overlap: All of these are Ribbit portfolio bets, which makes an integrated “intent rails” play plausible from a go-to-market and BD standpoint. On-chain identity signal: The CryptoPunk purchase + promised SBT drop are narrative-consistent with “agents that can be someone, not just something.”
Saved post image or poster

Image source: https://pbs.twimg.com/profile_images/1982914236595527680/3PAKBt0g_200x200.jpg

Quoted and embedded posts — separate backups

Posts that embed this post

Provenance and integrity
{
  "path": "sources/community-deep-dive-2026-10-14/fx-1955664675166720101.json",
  "sha256": "75552d1f5eb49ee469d7cbff9c82b9a85c8a0d75415eceb92fd1a944fa17a815",
  "retrieved_at": null
}

Receipt generated: 2026-10-15T09:54:53.764902+00:00. Publication and retrieval dates are separate. SHA-256 hashes detect changes; they do not independently authenticate the publisher.