Building upon #812, #948, #1334, #1477 and #1625, this proposal requests funding for the continuation of ReactiveDOT, along with its related projects: DOTConnect and, to a lesser extent, DOTConsole.

Project goals

ReactiveDOT is a library designed to:

• Simplify development: Provide intuitive front‑end functions and utilities for Substrate chain interactions, making development accessible for developers of all skill levels.
• Enhance developer experience: Reduce boilerplate and the complexity of integrating DApps with Substrate chains so teams can focus on product.
• Promote adoption: Lower the entry barrier through improved tooling and familiar patterns, encouraging wider adoption of Polkadot.

Previous major milestones

Solidity contract support

Full Solidity contract support without single‑chain or single‑account limitations.

• Announcement: https://x.com/tiennguyenk/status/1972456977340195161
• Pull request: https://github.com/buffed-labs/reactive-dot/pull/853
• Documentation: https://reactivedot.dev/react/smart-contract/solidity

Advanced async handling

Cementing ReactiveDOT (and by extension Polkadot) as the most cutting‑edge Web3 front‑end toolkit.

• Announcement: https://x.com/TienNguyenK/status/1981316461395312684
• Forum post: https://forum.polkadot.network/t/reactivedot-react-19-native-concurrency-for-polkadot-uis/15658
• Pull request: https://github.com/buffed-labs/reactive-dot/pull/968
• Documentation: https://reactivedot.dev/react/guides/async

Granular cache manipulation

Zero guess‑work bulk refresh/re‑render, fully compatible with React's transition.

• Pull request: https://github.com/buffed-labs/reactive-dot/pull/940
• Documentation: https://reactivedot.dev/react/guides/bulk-refresh

Incremental loading for a single query

• Pull request: https://github.com/buffed-labs/reactive-dot/pull/864
• Documentation: https://reactivedot.dev/react/guides/incremental-loading#defer

Miscellaneous contributions

Beyond my own projects, I contribute to various efforts in the Polkadot ecosystem whenever possible. Recent activity: https://github.com/tien?tab=overview

Current adoption

Noteworthy projects that I am aware of:

• create-polkadot-dapp
• inkathon
• Mentatminds
• Multix
• Polkadot-UI
• Delegit
• pop-wallet-signing-portal
• And possibly more

Weekly downloads: https://www.npmjs.com/package/@reactive-dot/core

Proposed works

As the feature set has now reached a stage where it meets the level of quality and completeness I personally set out to achieve, I'll be shifting my effort more toward increasing adoption and taking on DevRel.

This means a part‑time commitment of approximately 3 hours per day. During that time I will:

• refine and improve documentation and onboarding materials;
• assist projects integrating ReactiveDOT and related tools;
• stay responsive to community questions and fix issues promptly;
• maintain CI/CD pipelines and general upkeep.
• and of course develop any features on request

This schedule allows me to use my remaining time to explore other areas of contribution within the Polkadot ecosystem while maintaining the same high standard that I have in previous proposals: I always aim to push boundaries, not replicate or create busywork.

It will also help me gradually reduce dependency on the Treasury, sentiment is currently low, while still staying within Polkadot. Ultimately, I will wait for developments around Polkadot Hub before deciding on the most viable paths forward.

Requested budget

Milestones

November (already delivered)

Beside maintenance, support & onboarding, the following were also achieved

Contract event listener for both Solidity (eip-712) & Ink

Pull-requests:

• https://github.com/buffed-labs/reactive-dot/pull/996
• https://github.com/buffed-labs/reactive-dot/pull/997

Docs:

• https://reactivedot.dev/react/smart-contract/ink#listening-to-contract-events
• https://reactivedot.dev/react/smart-contract/solidity#listening-to-contract-events

Polkadot Vault support

ReactiveDOT:

• https://github.com/buffed-labs/reactive-dot/pull/1014
• https://github.com/buffed-labs/reactive-dot/pull/1018
• https://github.com/buffed-labs/reactive-dot/pull/1020

DOTConnect:

• https://github.com/buffed-labs/dot-connect/pull/418
• https://github.com/buffed-labs/dot-connect/pull/419
• https://github.com/buffed-labs/dot-connect/pull/421

Readonly Wallet & miscellaneous wallet related refactors

ReactiveDOT:

• https://github.com/buffed-labs/reactive-dot/pull/1022
• https://github.com/buffed-labs/reactive-dot/pull/1025
• https://github.com/buffed-labs/reactive-dot/pull/1028
• https://github.com/buffed-labs/reactive-dot/pull/1034
• https://github.com/buffed-labs/reactive-dot/pull/1038
• https://github.com/buffed-labs/reactive-dot/pull/1043

DOTConnect:

• https://github.com/buffed-labs/dot-connect/pull/424
• https://github.com/buffed-labs/dot-connect/pull/426

Popover wallet connection dialog, utilising native HTML Popover & CSS Anchor APIs

https://github.com/buffed-labs/dot-connect/pull/412

And many more, I don't want to be overly pedantic

• https://github.com/buffed-labs/reactive-dot/commits/main/
• https://github.com/buffed-labs/dot-connect/commits/main/
• https://github.com/tien?tab=overview&from=2025-11-01&to=2025-11-30

December & January

As discussed with W3F, success metrics for this period will be determined based on “alignment with DevEx teams from Parity, the W3F Tech Ed team, and ecosystem DevRel teams”, with progress reviewed on a monthly basis by W3F or an equivalent entity. The focus will be on measurable improvements in developer experience and adoption, while maintaining responsiveness to the needs of teams building on Polkadot.

Beyond DevRel activities, I currently plan to work on the following areas (Split between the two months when time allow), while remaining flexible to ecosystem priorities as they emerge:

• Expose a limited set of framework-agnostic primitives, including account utilities, wallet discovery/connection helpers, and contract interaction helpers. These capabilities are already achievable through internal building blocks, but formalising them into stable, public-facing APIs requires careful design. The goal is to provide a reliable, minimal, and predictable core layer that developers can use regardless of their stack.
• Add improvements and provide better documentation for DotConnect’s native Web Component capabilities, with emphasis on demonstrating usage across any front-end framework (React, Vue, Svelte, Angular, Solid, etc) as well as vanilla environments.
  This includes producing concise examples, integration patterns, and guidance on how to embed DotConnect seamlessly in existing applications without requiring a full rewrite or adoption of a specific toolchain.