Last week, the team released a range of updates in some ArcBlock's most-used kits - Pages Kit, Discuss Kit and Payment Kit. Read below to give a quick summary for each update.
1 — Discuss Kit: From Conversation Tool to Content Hub #
Theme | What Changed | Why It Matters |
|---|---|---|
User-owned content | Store posts, blogs, and bookmarks directly in your personal DID Space; preview them in-place | You control the data, not the platform — keeping the “decentralized” promise real |
Real-time feeds | A live activity stream rolls up every post, comment, bookmark and blog | No more jumping across threads to see what’s new |
Link & doc previews | OG embeds + blocklet previews + markdown tables | Rich context; less click-chasing |
Mobile polish | Better sidebar, bookmark UX, concise push notifications | Usable on small screens instead of “just tolerable” |
House-cleaning | Deleted / private items hidden; dozens of bug fixes | Cleaner signal, fewer surprises |
*Bottom line — Discuss Kit now feels like a fully fledged, DID-centric knowledge base for any community.*
2 — Pages Kit: Layout Control Without the CSS Headache #
- Custom page width & padding let teams dial in responsive layouts without touching code.
- Upgraded Markdown renderer keeps headings, lists, and quotes visually consistent with the rest of your theme.
- Mobile logo and nested-component bugs are stamped out; dependency bumps tighten security.
Takeaway: Pages Kit was already the quickest way to launch a static Web3 site. Now it finally behaves like a modern page builder, rather than a markdown viewer tied to a blockchain.
3 — Payment Kit: Less Friction, More Control #
Upgrade | Impact |
|---|---|
Batch subscription checkout | Pay for multiple subs in one shot — crucial for agencies and multi-product vendors |
Aggregated renewal emails | One digest per month instead of inbox spam |
Direct pay, no staking required | Opens pay-as-you-go tiers to non-crypto-native users |
Centralized billing dashboard | Users see balances, history, top-ups in one place |
Hot-to-cold auto-transfer (“Vault Wallet”) | Service operators cut custodial risk without manual sweeps |
Automatic retry on failed payments | Revenue leakage plugged; fewer angry tickets |
*If you sell anything recurring through ArcBlock, these tweaks remove the last excuses for churn.
Why This Release Cycle Matters #
ArcBlock’s kits used to feel like independent tools. With this round of updates, the seams are disappearing:
- DID Space integration ties identity, content and payments together.
- Real-time UX improvements surface the right data at the right moment.
- Batch actions (feeds, subscription bundles) respect users’ time — a subtle but critical shift from Web2 paradigms where the platform’s convenience trumped the user’s.
Expect future updates to push even harder on interoperability: imagine a Pages Kit widget that auto-generates paywalled content via Payment Kit, surfaced inside Discuss Kit feeds. That’s where this is headed.
What to Do Next #
- Check for updates — the gains are immediate.
- Test DID Space workflows for your moderators or power users.
- Audit your subscription SKUs; merge where possible to leverage batch checkout.
- Measure engagement: The new feed and notifications should improve time-on-site. Prove it with data.
- Plan cross-kit experiments — e.g., gated doc previews with micro-payments.
Continuous, user-controlled, interoperable: that’s it. If you’re building decentralized communities or services there's never been a better time to get started. Visit www.arcblock.io to get started.
Listen to the Podcast#
ArcBlock’s latest “Deep Dive” audio briefing condenses three separate product releases into a single, fast-moving conversation. Below is your TLDR so you can scan the essentials while listening in.