Learning Hive Projects in Public #2: Ecency (Current Understanding)
This post reflects my current understanding after researching public sources and chain/API data. I may still misunderstand parts of this system. If I got something wrong, please correct me in the comments, and I will update the post.
1) What this project is
Ecency is a Hive social client ecosystem (web + mobile, and historically desktop) focused on publishing, discovery, wallet interactions, and onboarding.
Verified: Ecency’s public repositories describe the web client (vision-next) and mobile app (React Native), and the app is distributed on iOS/Android.
2) History / timeline (publicly verifiable)
- 2016-11-03:
@esteemapp account created on Hive chain data.
- 2020-05-13:
@ecency account created on chain.
- 2020-06-10: post by
@esteemapp titled "From Esteem to Ecency" published.
- 2020-07-17: Ecency development update says official Ecency release target was 2020-07-22.
- 2020-2026: multiple DHF proposals under
@ecency (including current cycle proposal #336 through 2026-06-21).
3) Team / people (public only)
- Public Hive and GitHub activity strongly indicates leadership/development continuity around accounts including
Hive account@good-karma and 
Hive account@ecency.
- GitHub org
ecency shows a verified organization with active public repositories.
- Public GitHub member visibility is limited, so this is incomplete by design.
4) Problem it is solving
Ecency appears to be solving a practical user problem on Hive: making decentralized social posting + wallet actions feel app-like and accessible across devices.
My current read is that it is trying to bridge:
- blockchain-native ownership and composability
- mainstream UX expectations (mobile app reliability, notifications, clean publishing flow)
- identity/signing flows that work for both technical and non-technical users
5) Technology and architecture (current understanding)
Verified from public repo docs:
- Web stack: Next.js + TypeScript (
vision-next repo docs).
- Mobile stack: React Native (
ecency-mobile repo docs).
- Data fetching uses
@ecency/sdk, with web requests routed to /private-api/* and /search-api/*.
- Signing/broadcast paths mention posting key usage, Hivesigner token mode, and injected broadcasters (Keychain/HiveAuth/mobile).
- Ecency docs describe cache policy design using middleware + Cloudflare/Nginx behavior.
Informed inference (not fully verified end-to-end):
- Ecency likely runs a hybrid architecture: direct Hive RPC interactions plus managed/private service layers for performance, search, and UX-specific features.
Unknown / still investigating:
- Exact boundaries of what is fully open-source and self-hostable today versus what is effectively managed infrastructure for production experience.
6) Hive integration points
Confirmed / strongly evidenced:
- Standard Hive social and wallet operations are integrated via web and mobile clients.
- DHF funding history is visible on-chain via proposal records under
@ecency.
- Ecency mobile docs include Hive URI and transaction-signing flows.
Partially clear:
- Ecency points mechanics are referenced in docs (e.g., point transfer handling) but I still need a cleaner public map of accounting, issuance, and full lifecycle.
7) Strengths, tradeoffs, risks
What looks strong
- Multi-client coverage (web + mobile, with long-term continuity from eSteem era).
- Ongoing public development footprint and proposal accountability surface on-chain.
- Explicit attention to signing methods and user-facing UX.
Tradeoffs and risks
- Hybrid/private layers can improve UX but reduce outsider visibility into full internals.
- As with most Hive frontends, long-term resilience depends on sustained maintenance and funding support.
- Ecosystem users can underestimate operational complexity behind “simple” social UX.
8) Open Questions
- Which Ecency backend components are currently critical-path but not practically reproducible by third parties?
- How is Ecency points accounting implemented end-to-end, and what is the authoritative public specification?
- Which metrics does the Ecency team consider the best signal of product health right now (retention, posting velocity, active wallets, etc.)?
- How should users think about interoperability and migration risk between Hive frontends over multi-year timelines?
9) Sources
If you are close to this project, I would especially value corrections on architecture boundaries and Ecency points internals.
