InkHaven: A CKB-Native Publishing Platform Built for Global Writers

[InkHaven]

Continuing the discussion from /long-form-publishing-platform/9817

Hey community,

January 7, 2026

Yesterday we dropped that quick “hello world” tease just to let you know we were about to share something we’ve been building for a while. The response was awesome: lots of curiosity, questions, and encouragement. Thank you it means a lot.

Today, we’re delivering a much larger picture.

Meet InkHaven: a long-form publishing platform with CKB at its core for identity, monetization, and ownership proofs. Imagine Medium’s ease with true crypto ownership, that’s our vision.

Who We Are and Why This Exists

We’re builders, passionate about writing and strong supporters on Nervos. We’ve seen creators struggle on centralized platforms: sudden algorithm changes, unfair cuts, content deletions, or entire sites vanishing. Web3 promised fixes, but most options stayed niche due to high fees or complexity or pivoted away, like Mirror after its 2024 acquisition by Paragraph.

We built InkHaven to empower writers, putting CKB front and center. Its strengths, JoyID’s seamless onboarding, low on-chain fees (as low as 61 CKB min for transactions), and the cell model’s flexibility, make it ideal for a real-world creator app. Building on that foundation, here’s what we’ve created.

What We’ve Built

InkHaven mirrors the platforms writers love (Medium/Substack) but adds genuine crypto-native perks without the hassle.

Familiar Writing Flow Rich editor: headings, bold/italic, lists, tables, code blocks, image uploads with captions, embeds (YouTube, X, Spotify, etc.). Drafts auto-save; easy editing or unpublishing.

Easiest Onboarding in Web3 Wallet login via JoyID (mobile-first, biometric, no seed phrases). No emails or passwords. Publish your first piece in minutes.

Fair and Flexible Monetization All payments leverage CKB’s low costs for tips, purchases, and subs. Creators get up to 90% revenue share (premium authors) plus 50% referral share, the industry’s most generous.

Real Ownership and Permanence We designed a three-layer model so every writer can choose the level of protection that fits them:

• Free Basic Seal Your article’s content is hashed and cryptographically signed with your wallet. The signature is stored securely on InkHaven. This proves you are the author as long as the platform exists, no cost, instant, and available to everyone.
• Paid Blockchain Seal (one-time small fee) The hash + your signature are recorded permanently on the Nervos CKB blockchain (tiny transaction, low cost). The full article text and formatting are uploaded to Arweave using its proven endowment model (200+ years of storage, the network remains healthy and growing in 2026). The CKB transaction references the Arweave ID, creating an unbreakable link.

Why this matters With the paid seal, your work becomes completely independent:

• Anyone can verify authorship by checking the CKB blockchain record.

• Anyone can retrieve the exact original content from Arweave using the referenced ID.

• This survives forever, even if InkHaven shuts down, gets acquired, or changes terms. No trust in the platform required.

Global Reach Built In Full UI in English, Spanish, Portuguese, Simplified Chinese – tapping into Nervos’ thriving communities in Asia and Latin America.

Community Features Profiles, follows, likes, threaded comments, trending tags, engagement-based features, privacy-first analytics.

Polished and Ready 670+ tests passed, security/accessibility/performance audits cleared, GDPR compliant, moderation tools, push notifications. Launch-ready.

Near-term roadmap: off-chain payment explorations (potential Fiber integration) and did:ckb for portable identity.

For context, here’s how we stack up:

Feature	InkHaven	Medium	Substack	Mirror
Ownership	CKB + Arweave permanence	Platform-dependent	Platform-dependent	ETH + Arweave (high fees)
Revenue Share	Up to 90% + 50% referrals	Variable/opaque	90%	~97% but gas-heavy
Min Tx Cost	~$0.80	N/A	~$5	$5-50
Languages	4 (global focus)	Limited	Limited	English-only

Why This Can Matter for Nervos

This isn’t just a writing tool, it’s ecosystem rocket fuel. Each writer brings audiences (e.g., even 0.1% of Medium’s 100M+ users = massive exposure), onboarding JoyID wallets organically. Expect sustained on-chain volume from tips/patrons/subs. It’s a consumer app showcasing CKB to non-crypto folks, with multi-language content amplifying Nervos stories worldwide.

As writers ourselves, we built this to fix what frustrated us most: losing control.

The Real Talk: Challenges Ahead

We’re clear-eyed, platforms are tough:

• Chicken-and-egg: Great content draws readers; readers draw writers.
• Crypto curve: JoyID eases it, but education is key.
• Hybrid debate: Arweave complements CKB perfectly, but purists might question.
• Giant competition: We focus on niches like global/ownership-focused creators.

Our Starting Plan

To overcome hurdles, we’ll seed from within: inviting partners like Nervapes, JoyID, EcoFund etc. to use it as their go-to for in-depth tutorials, ecosystem analyses, RGB++ deep-dives, making it the source of truth for sharing polished work. Early momentum starts here, be part of it!

Let’s Hear From You

This is community-first. Share your honest thoughts:

• Can this platform boost Nervos’ and growth?
• Is the CKB-hybrid balance right?
• What features/integrations would excite you?
• How can we serve at launch (e.g., beta access)?

We’re investing everything to align InkHaven with Nervos’ vision. Now, let’s perfect it together.

Thanks for reading, can’t wait for your input!

InkHaven

---

InkHaven：一个为作家和 Nervos 生态量身打造的 CKB 原生发布平台

2026年1月7日
嘿，社区的朋友们，

昨天我们发布了那个简短的“hello world”预告，只是想让大家知道我们即将分享一个我们已经构建了一段时间的项目。反响非常棒：充满了好奇、问题和鼓励。非常感谢，这对我们意义重大。

今天，我们将呈现一个更全面的图景。

欢迎来到 InkHaven：一个以 CKB 为核心的长文发布平台，用于身份验证、变现和所有权证明。想象一下 Medium 的易用性加上真正的加密所有权，这就是我们的愿景。

我们是谁，以及为什么要做这个

我们是构建者，对写作充满热情，同时也是 Nervos 的坚定支持者。我们看到创作者在中心化平台上挣扎：算法突然变化、不公平的分成、内容被删除，或者整个网站消失。Web3 承诺了解决方案，但大多数选项由于高费用或复杂性而保持小众，或者像 Mirror 在 2024 年被 Paragraph 收购后转向其他方向。

我们构建 InkHaven 是为了赋能作家，将 CKB 置于核心位置。它的优势——JoyID 的无缝 onboarding、低链上费用（交易最低仅需 61 CKB）、以及细胞模型的灵活性——使其成为真实世界创作者应用的理想选择。在这个基础上，我们创造了以下内容。

我们构建了什么

InkHaven 模仿了作家们喜爱的平台（Medium/Substack），但添加了真正的加密原生优势，而无需繁琐操作。

熟悉的写作流程 丰富的编辑器：支持标题、粗体/斜体、列表、表格、代码块、带说明的图片上传、嵌入（YouTube、X、Spotify 等）。草稿自动保存；轻松编辑或取消发布。

Web3 中最简单的 onboarding 通过 JoyID 钱包登录（移动优先、生物识别、无种子短语）。无需邮箱或密码。几分钟内即可发布你的第一篇文章。

公平且灵活的变现 所有支付利用 CKB 的低成本，支持打赏、购买和订阅。创作者最高可获得 90% 收入分成（高级作者）加上 50% 推荐分成，这是行业中最慷慨的。

真正的所有权和永久性 我们设计了一个三层模型，让每位作家都能选择适合自己的保护级别：

• 免费基本密封 你的文章内容被哈希并用你的钱包进行加密签名。签名安全存储在 InkHaven 上。只要平台存在，这就能证明你是作者，无成本、即时，且对所有人开放。

• 付费区块链密封（一次性小额费用）哈希 + 你的签名永久记录在 Nervos CKB 区块链上（微小交易、低成本）。完整文章文本和格式上传到 Arweave，使用其成熟的捐赠模型（200+ 年存储，网络在 2026 年仍健康且在增长）。CKB 交易引用 Arweave ID，创建不可破坏的链接。

为什么这很重要 通过付费密封，你的作品变得完全独立：

• 任何人可以通过检查 CKB 区块链记录来验证作者身份。

• 任何人可以使用引用的 ID 从 Arweave 检索精确的原始内容。

• 这将永久存在，即使 InkHaven 关闭、被收购或更改条款，也无需信任平台。

内置全球覆盖 完整 UI 支持英语、西班牙语、葡萄牙语、简体中文——深入 Nervos 在亚洲和拉丁美洲的活跃社区。

社区功能 个人资料、关注、点赞、线程评论、热门标签、基于互动的功能、隐私优先的分析。

精致且准备就绪 通过 670+ 测试、安全/可访问性/性能审计、GDPR 合规、审核工具、推送通知。已准备好推出。

短期路线图：探索链下支付（潜在 Fiber 集成）和 did:ckb 用于可移植身份。

作为参考，以下是我们与其他平台的比较：

功能	InkHaven	Medium	Substack	Mirror
所有权	CKB + Arweave 永久性	依赖平台	依赖平台	ETH + Arweave（高费用）
收入分成	最高 90% + 50% 推荐	不固定/不透明	90%	~97% 但 gas 费用高
最低交易成本	~$0.80	不适用	~$5	$5-50
语言支持	4 种（全球焦点）	有限	有限	仅英语

为什么这对 Nervos 很重要

这不仅仅是一个写作工具——它是生态系统的火箭燃料。每位作家都会带来受众（例如，即使 Medium 1亿+ 用户的 0.1% = 海量曝光），有机地 onboarding JoyID 钱包。预计打赏/赞助/订阅将带来持续的链上交易量。这是一个向非加密用户展示 CKB 的消费级应用，多语言内容将放大 Nervos 在全球的故事。

“作为作家，我们构建这个是为了解决最让我们沮丧的问题：失去控制。”

实话实说：未来的挑战

我们清醒地认识到，平台建设很艰难：

• 鸡生蛋蛋生鸡：优秀内容吸引读者；读者吸引作家。

• 加密学习曲线：JoyID 缓解了，但教育仍是关键。

• 混合模式争议：Arweave 完美补充 CKB，但纯粹主义者可能质疑。

• 巨头竞争：我们专注于全球/注重所有权的创作者细分市场。

重要的是，InkHaven 补充 Nervos Talk，而不是取代。它不适合短形式聊天或论坛。Nervos Talk 处理社区新闻/快速交流；我们处理精致的长文和变现。

我们的启动计划

为了克服障碍，我们将从内部开始：邀请合作伙伴如 Nervapes、JoyID 和 EcoFund 将其作为深度教程、生态分析、RGB++ 深度探讨的首选平台，使其成为分享精致作品的权威来源。早期势头从这里开始，一起参与吧！

听听你们的意见

这是社区优先。分享你们的真实想法：

• 这能提升 Nervos 的增长吗？

• CKB 混合模式的平衡合适吗？

• 哪些功能/集成会让你们兴奋？

• 我们如何在推出时更好地服务（例如，beta 访问）？

我们投入一切来让 InkHaven 与 Nervos 的愿景一致。现在，让我们一起完善它。

感谢阅读，期待你们的反馈！

InkHaven

[InkHaven]

Unfortunatly we were not allowed to add images nor links to the body preventing a more polished presentation. Can we ask if this is by design to an admin? Possibly related to being a new account.

[matt_ckb]

please try again on the images.

regarding suitability for CKB I want to put on your radar that you could eventually just use a single cell and continue to add proofs of authorship to it. This will drive transaction costs for your users toward 0 while not impacting the ability to monetize (simply by using CKB more efficiently and targeting more infrastructure toward witness instead of cell data)

Stay tuned for more info on what this would look like. Because of CKB’s economic model, we always have to consider the impact of storing data on-chain. Users wanting to store state will increase demand for CKB, which could increase the cost of storing data on CKB, which would slow down the flywheel of adoption.

Also you could accept payment through Fiber, this will reduce transaction costs as well. Currently CKB transaction fees are basically zero because of low chain utilization but in the future we can expect this to change (that’s why we’re all here!).

Your project sounds like a great development, really good to see

[Yeti]

@InkHaven

This is community-first. Share your honest thoughts:

• Can this platform boost Nervos’ and growth?

Whether or not this boosts CKB usage is totally dependent on the success of your business model.

The fact that your using CKB means absolutely nothing at the moment, because this whole thing is going to depend on if you can get people to use your platform first of all, which is going to be the real challenge, no matter which blockchain you use.

So I’d like to see more of your plans about how your going to steal current and new users from Medium and those other platforms, because the benefits to CKB only come after InkHaven is a success in its own right. Web2, Web3, doesn’t matter, this type of thing is just a business first and foremost.

@InkHaven

• Is the CKB-hybrid balance right?
• What features/integrations would excite you?

The hybrid approach if fine, CKB can’t do everything perfectly, so if you need to integrate other crypto platforms for the best user experience, then that’s definitely the best way.

I would also be making sure that readers can make payments in any token they like (big chain native tokens etc, not day old meme coins obviously).

You can’t expect non-CKB holders to buy CKB to make payments, so if that’s the game plan, then you need to redesign things.

The writers also need to be able to transact in other crypto and even credit card, Paypal etc and you need to act as the Paymaster using your own holding of CKB for the CKB specific transactions and storage requirements.

CKB might be perfect as the backend platform, but you need to hide the fact that it’s built on CKB.

And I’m not saying that in a way that you should be ashamed about it being built on CKB, I’m saying it because both the writers and the readers don’t care where it’s built, they want the best experience.

[matt_ckb]

@Yeti

CKB might be perfect as the backend platform, but you need to hide the fact that it’s built on CKB.

There are 2 approaches here. 1) Hide 2) Amplify

They are completely different paths but want to highlight that there is the option of maximizing use in our corner of the world.

[Yeti]

Maybe hide isn’t the best choice of words, it’s ok to make it known it’s built on CKB, but if we can do that at the same time as making sure that the users don’t need to also make the CKB token a big part of their life, then this is the best way.

edit: Just another thing, I think this is more important to things like InkHaven, which isn’t really a ‘crypto’ specific app, as they can reach outside crypto, but just use the things that crypto is good at and designed for.

[matt_ckb]

I think there’s some misunderstanding here, I agree with you on “hide”, there’s no reason a user would have to know or care about underlying tech.

What I’m saying is there is a second path, where we maximize for the existing community. In this case, paying in CKB is no problem, it’s like early BTC community, using CKB grows in our community.

This path seems more short-lived while the one you’re describing is more medium-long term kind of thinking.

I think it’s perfectly reasonable to say “hide” I’m just trying to get across another possible option here. Hat tip to @janx for opening my mind to this path.

[Yeti]

Ok, I think I get you and I’m all for current CKB holders to spend their tokens on CKB apps, we need this to happen as mush as possible.

I think this has actually been one of our biggest problems over the years, most CKB holders treat the token like it’s a family heirloom and can’t be spent.

This is what Bitcoin is like now and it deserves to be treated like it’s too special to spend, but like your saying, it wasn’t always like that, people were throwing it around like confetti at one stage and that’s really what we need to do with our CKB.

Spend CKB on CKB and then go to Binance and replace it.

But just to clarify, I definately wasn’t saying that we should hide the option for people to spend CKB directly if they already hold it, I want this!…I was just meaning that we should do what we can to allow people outside of CKB to use our apps without forcing them to become CKB holders.

[InkHaven]

Thanks @matt_ckb ! Actually, we’ve already implemented a pure witness-based seal system that does exactly this, but it’s still under testing. With this approach , out authorship seals will use witnesses instead of cell data, which eliminates capacity lock-up costs entirely. Seals are them encoded with magic bytes (INKHAVEN) + version byte + JSON payload.
The JSON includes: articleId, contentHash, authorAddress, timestamp, and optional Arweave backup reference.
This reduces the cost of blockchain sealing down to just transaction fees (<$0.01).
An examole would look something like this:
INKHAVEN\x01{“t”:“seal”,“v”:1,“a”:5,“h”:“5debc08b…”,“w”:“ckt1qr…”,“ts”:“2026-01-07T22:27:54Z”}

We are also implementing this for co-authorship verification.

[InkHaven]

@Yeti, We’re not under any illusion that “built on CKB” is a selling point for mainstream users. The platform has to work as a product first. Our strategy isn’t to compete head-to-head with industry giants. Instead, we’re starting with niches where crypto-native monetization actually matters: writers in regions with limited payment infrastructure, creators who’ve been burned by platform censorship, and communities that already understand the value of owning their identity and content.

The Nervos community is our first testbed, if we can’t convince the people who already understand CKB to use it, we have no business going mainstream.

On payment flexibility:

We hear you on multi-token payments and that is something that can be addressed in many different ways. There are fiat and Fiber Network integration already on our roadmap for exactly this reason. The goal is to let readers pay with whatever they’re comfortable with while writers can choose how they want to receive funds.

On “hiding the blockchain”:

This is where we respectfully see things a bit differently. For mainstream users, yes, the blockchain infrastructure can be made “invisible” . But for our initial community, the CKB connection IS the value proposition. They’re not just users, they’re collaborators who understand what we’re building and why.

The end goal is to build abstraction layers that feels like regular login, one-click tipping, etc.) but we’re not hiding where we come from. When we’re ready for mainstream, those abstractions will be in place. For now, we’re proud to build in the open with the community that will help us get there.

[matt.eth]

对于长文写作平台，我觉得重点可能需要放在内容运营上，AI时代，内容供给泛滥，我们需要一个能过滤垃圾降低时代信噪比、提供深度洞察、并能让作者和读者产生真实情感连接的高审美社区。第一性原理，写作平台，作者更需要好的流量，读者需要好的内容。所有权可以锦上添花，但作为核心卖点我怀疑它有足够的吸引力让一个项目成功商业化，它和web2已有的所有权选项区别真的那么大吗？substack也可以导出订阅者邮件列表。我觉得web3可能适合作为技术选项，但只作为隐形的基础设施就好。

运营的借鉴上我能想到当年的牛博网+现在的小宇宙（策展与分发）。我希望能有一个文章搬运机制，鼓励大家把看到的好文章搬运到这个平台，平台首页是编辑精选文章，基于一定的审美品味解析出一批忠实用户。

总之，我觉得最好先基于内容把流量搞起来，再基于实际需求调整平台技术架构和收益分配。

[janx]

I’m excited to see something like this in the works—thanks for all your efforts! Even though there are many writing tools out there and new ones appear every day, there’s always room for innovation, and InkHaven is definitely one of those opportunities.

I believe the most important question is who the first 1,000 users—the initial target audience—will be. In my understanding InkHaven aims to attract writers who (1) are dissatisfied with Web2 platforms’ revenue cuts and seek higher returns, (2) want their work to be permanently showcased, and (3) value more direct connections with readers. If so the challenge turns to find users who fit this profile, which may be the hardest part and where skilled growth experts could make a difference.

If the initial goal is to reach certain kind of 1,000 users, it’s better to focus on this small group and trim some features meant for mass adoption—we’ll get there eventually, just not today. For example, is credit card payment necessary? is on-chain data “compression” necessary? etc.

@InkHaven

Paid Blockchain Seal (one-time small fee) The hash + your signature are recorded permanently on the Nervos CKB blockchain (tiny transaction, low cost). The full article text and formatting are uploaded to Arweave using its proven endowment model (200+ years of storage, the network remains healthy and growing in 2026). The CKB transaction references the Arweave ID, creating an unbreakable link.

I’m not sure whether the record is compatible with CKB token standards such as UDT, DOB, Spore, or RGB++. This matters because standard compatibility enables on-chain seals/publications to be “liquid” and circulate throughout the ecosystem—for example, combining with Nervape or RGB+±leaping to Bitcoin. It also forms the foundation for more advanced tokenomic designs, such as DOBs for fan clubs or UDT/DOB-based curator and recommendation models.

And the tier-ed storage model is cool. Not sure if you consider provide more on-chain tiers in future. For example, a hash+signature seal tier, a DOB tier, a Bitcoin on RGB++ tier, so users can choose different benefits/costs package themselves. More tiers will incur higher cognition burden and development complexity though.

The tiered storage model is great. Are you considering adding more on-chain tiers in the future? For example, a hash + signature seal tier, a DOB tier, or Bitcoin/RGB++ tier, so users can choose their preferred balance of benefits and costs. However, adding more tiers would increase cognitive load and development complexity.

@InkHaven

• Can this platform boost Nervos’ and growth?

Yes if it finds the 1000 first users and converts them to Nervos users.

@InkHaven

• Is the CKB-hybrid balance right?

It’s fine. Arweave is a practical choice for permanence. I think a project’s “CKB-native score” mainly depends on how deeply and broadly it integrates with the CKB ecosystem (such as UDT/DOB composability), rather than on the number of non-CKB integrations it has.

One final suggestion concerns its name (as noted in this comment): sharing the same name as another product in the same category causes unnecessary confusion and, in my opinion, has more drawbacks than benefits.

I’m really excited to see all the ideas and effort that went into this. Can’t wait for the launch!

[Yeti]

@InkHaven

The Nervos community is our first testbed, if we can’t convince the people who already understand CKB to use it, we have no business going mainstream.

But for our initial community, the CKB connection IS the value proposition. They’re not just users, they’re collaborators who understand what we’re building and why.

Hi @InkHaven I just want to say first that I know it looks like I’m being negative here for the hell of it, but I’m just trying to give you some advise from what I’ve seen after a very long time in the community.

I want to see CKB succeed more than anyone and I still fully believe that it will, but we need to be honest here and understand that the current CKB community is very small and of that very small community only a very small number of those are people are even interested in using the blockchain.

If your plan is to keep fighting until this becomes a successful business and you want to leave something meaningful on CKB, then that’s great and I will fully support you all the way, even if it’s not something I’m personally interested in.

But we have seen time and time again that apps get developed on CKB and when the CKB community doesn’t show up to use the app, the project just throws their hands up in the air like they can’t believe what’s happened and then just walk away.

What I’m getting at is, you can’t rely on us, as a group we most likely won’t help you.

So don’t be surprised when what I’m saying happens, because it almost certainly will, but this doesn’t mean you’ve failed, the reality is we are just too small and too passive a group to carry any project ourselves, you need to know this going in.

Build something on CKB because you need CKB for something it does uniquely, but you need to look outside for your users, so do everything you can to make it easy for them come here.

But luckily CKB is actually built for this exact purpose, with things like CCC and Joyid you’ve got nearly everything you need.

[AIIA]

很赞成，有没有什么办法，把ckb变成所有链的结算层，看起来很多应用在其他公链或者应用链上面，但是都会要走向ckb

[Ophiuchus]

This is a really interesting thread because it shows that the real question isn’t “hide CKB or not”, but when, for whom, and at which layer.

In the early phase, it makes total sense to lean into the CKB-native angle : Crypto-aware users, contributors who understand why ownership, permanence and censorship resistance matter, and who are willing to interact with CKB directly. That’s not a weakness, it’s a strength ! And probably the only realistic way to bootstrap meaningful usage.

At the same time, the long-term path is clearly abstraction. Mainstream users don’t care what chain is underneath, and they shouldn’t have to. Payments, login, UX … All of that needs to feel invisible eventually.

What I find compelling here is that these two approaches aren’t contradictory, they’re sequential. And CKB feels particularly well-suited for that kind of phased strategy : Strong infra and guarantees at the base layer, with the flexibility to progressively abstract things away as the product matures.

InkHaven feels like a good example of “build something that needs CKB for what it does uniquely, but doesn’t force CKB into the user’s face before it makes sense.”

That balance is hard, but this discussion shows the right questions are being asked.

[Thinker]

非常有趣的现象，社区似乎从劝亲朋好友来开发走到了“劝阻”阶段，前几天就看到有人劝WarSpore · Saga项目最好不要打着CKB来，想法用BTC链游来宣发，无论说的对与不对，项目方听与不听，至少是反应了社区的一些心态

[fishell]

喜欢这种清醒。以前一些项目总是指望在ckb社区捞用户，根本不可能有什么发展。不如看清现实，一起往外面去捞用户

[Yeti]

I disagree that anyone’s discouraging development ON CKB, I highly encourage that, but you could say that I personally am discouraging development FOR CKB.

The evidence is crystal clear, we’ve proven ourselves to be unable to help ourselves.

There’s no harm in admitting this, in fact refusing to see it is way more damaging, we just need to understand it and stop kidding ourselves going forward.

But the solution is also crystal clear - build cool stuff that other crypto users who haven’t already tied themselves to one blockchain or another will want to use and then we entice them here.

I’m not saying I know exactly how to do this, but it is the way forward for sure.

[InkHaven]

We completely understand where you’re coming from, and we truly appreciate the honest advice. It’s coming from a place of experience, and we respect that.

We’re not expecting any miracles here. We know the community well, and history clearly shows that adoption hasn’t come from within. It almost always starts from outside efforts pulling new users in. So we’re fully aware that the early users will likely have to come from our own outreach rather than the existing community showing up in large numbers. But we still need to reach out to OGs.

That said, our goal is to build something genuinely compelling. A consumer app with great features that stands on its own merits and sparks curiosity in people outside the current circle, drawing them in to explore it.

Failure is inevitable along the way, but we believe success is built on learning from those failures.

Thank you for the heads-up about not relying on the community to carry the project. It’s a fair warning, and we’ll try to plan accordingly by focusing on making it as accessible as possible for newcomers. We’re already leveraging tools like CCC and JoyID to lower those barriers significantly.

This isn’t just about what CKB enables uniquely. It’s about creating a solid consumer app with standout features. And rest assured, we won’t abandon it. If things ever shift in a way that we can’t continue, we’ll make the full code open source to ensure continuity for anyone who wants to carry it forward.

We’re in this with eyes wide open, and your support means a lot, even if it’s not your personal cup of tea.

[InkHaven]

We really appreciate this nuanced take. It perfectly frames the strategic question we’ve been wrestling with internally.

You’re spot on that it’s not about hiding CKB versus promoting it, but about deliberate phasing: who we’re speaking to, at what stage, and through which interface.

Right now, we’re very intentionally starting with the CKB-native angle because those early users aren’t just downloads. They’re the ones who deeply understand and can meaningfully stress-test the core value proposition around true ownership, content permanence, and censorship resistance. Their feedback will shape the product in ways casual users couldn’t. So leaning into the tech at this stage isn’t a compromise. It’s essential for building something that actually delivers on promises.

For mainstream adoption, we’ve designed the experience so that almost everything feels like a normal consumer app. Reading, browsing, commenting, following authors, and most daily interactions require zero blockchain knowledge. The only moments where users encounter signing are the ones that truly matter for sovereignty and permanence: initial login (via JoyID, quick, passwordless, like email or social signup with biometric support), publishing or “sealing” a post (free basic seal or paid blockchain + Arweave seal), adding digital signatures, and monetization actions like tipping or setting up patron tiers/subscriptions.

Payments are fully CKB-native today (tips, subscriptions, and patron contributions all happen wallet-to-wallet with no custody), which keeps the strongest ownership guarantees in the ecosystem. That said, we’re actively planning to add support for stable assets like USDi and, longer-term, smoother fiat on-ramps to make those features feel as frictionless as any traditional platform.

What excites us most is that CKB’s tools, especially JoyID and the CCC connector let us keep crypto exposure minimal while preserving real user sovereignty in a way few chains can match.

Thanks for articulating this so clearly. Discussions like this confirm we’re asking the right questions and keep us motivated to execute well.