Blocks
Lens Blocks blocks: 7 sections with preview
All 7 blocks published by Lens Blocks, with categories, file counts and licence. The table lists the biggest sections and links to each preview.
Key points
- 7 blocks in 17 files, all tied to Lens Protocol.
- MIT licence, but canary dependencies and a required wallet.
- Unmaintained since December 2025: verify the code before use.
Lens Blocks publishes 7 blocks in 17 files, all for Lens Protocol. Lens Post alone takes nine files; the rest are dialogs and account components for the social protocol.
Blocks with the most files
| Block | Registry | Files | Category |
|---|---|---|---|
| Lens Post | Lens Blocks | 9 | lens |
| Lens Account Hover Card | Lens Blocks | 2 | lens |
| Lens Login | Lens Blocks | 2 | lens |
| Lens Account Chooser | Lens Blocks | 1 | lens |
| Lens Collect Post Dialog | Lens Blocks | 1 | lens |
| Lens Quote Post Dialog | Lens Blocks | 1 | lens |
| Lens Tip Dialog | Lens Blocks | 1 | lens |
What this source contains
- Repository: iPaulPro/lens-blocks
- Site: https://lensblocks.com
- Licence: MIT (LICENSE file in the iPaulPro/lens-blocks repository)
- Categories: taken from the publisher manifest, not invented.
When to use it
It pays off when you are building a Lens client and want parts already wired to the social graph: post, quote, collect, tip. It does not suit a generic social app: half the catalogue assumes a wallet and Lens sessions.
Lens Protocol: when the block is only the surface
Lens Post opens nine files because it does more than draw a card: it handles metadata, actions, counters and protocol loading states. The other blocks are smaller but share the same data layer: accounts, followers, post context.
Dependencies explain the real cost. @lens-protocol/react and @lens-protocol/client sit on a dated canary version, wagmi and viem handle the connection, connectkit opens the wallet, react-virtuoso carries long lists. Installing a block means adopting this stack, not just the markup.
The catalogue has been still since December 2025 and has seven stars: a personal project, not a maintained product. The MIT licence helps, but the canary dependency versions are the real risk: a protocol update can break a block without the repository changing.
curl "https://ui.eneawork.it/api/blocks?source=ipaulpro-lens-blocks&limit=8"Three examples from the table: Lens Post, Lens Account Hover Card, Lens Login; the full inventory is at /blocks. For the counting method read how the block catalogue is built, for the copy-versus-compose comparison read the economics of sections, and for heroes read the shadcn hero guide.
Frequently asked questions
How many blocks does Lens Blocks have?
Seven blocks in seventeen files, measured on 1 November 2026. Lens Post alone takes nine, more than half the catalogue.
What licence does Lens Blocks use?
MIT in the iPaulPro/lens-blocks repository. The code is permissive, but Lens Protocol and its dependencies carry their own terms.
Do the blocks need a wallet?
Yes, for social actions. wagmi, viem and connectkit handle the connection, so a static preview cannot prove the flow.
Why are the Lens dependencies on canary versions?
The publisher pinned canary versions dated August 2025. They are unstable by definition and may drift from the current protocol.
Is the project still maintained?
The last GitHub push was in December 2025 and the repository has seven stars. Treat it as sample code to verify, not a living library.