Building upon [#812](https://polkadot.subsquare.io/referenda/812), [#948](https://polkadot.subsquare.io/referenda/948), [#1334](https://polkadot.subsquare.io/referenda/1334), [#1477](https://polkadot.subsquare.io/referenda/1477) and [#1625](https://polkadot.subsquare.io/referenda/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/1959061585508671931](https://x.com/TienNguyenK/status/1959061585508671931)
- Pull request: [https://github.com/buffed-labs/reactive-dot/pull/853](https://github.com/buffed-labs/reactive-dot/pull/853)
- Documentation: [https://reactivedot.dev/react/smart-contract/solidity](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](https://react.dev/reference/react/useTransition).

- 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](https://github.com/paritytech/create-polkadot-dapp)
- [inkathon](https://inkathon.xyz/)
- [Mentatminds](https://mentatminds.com/)
- [Multix](https://multix.cloud/)
- [Polkadot-UI](https://polkadot-ui.com/)
- [Delegit](https://delegit.xyz/)
- [pop-wallet-signing-portal](https://github.com/r0gue-io/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

<table>
  <caption>3 months duration: November to January 2025</caption>
  <thead>
    <tr>
      <th>Personnel</th>
      <th>Rate</th>
      <th>Tasks</th>
      <th>Time</th>
      <th>Cost</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="6">Tien (myself)</td>
      <td rowspan="6">$125/hour</td>
      <td>Development based on feature requests</td>
      <td rowspan="6">198 hours</td>
      <td rowspan="6">$24,750</td>
    </tr>
    <tr>
      <td>Bug fixes</td>
    </tr>
    <tr>
      <td>Improve documentation & onboarding materials</td>
    </tr>
    <tr>
      <td>CI/CD maintenance</td>
    </tr>
    <tr>
      <td>Support via GitHub issues, DMs & dedicated Matrix channel</td>
    </tr>
    <tr>
      <td>Outreach & promotion</td>
    </tr>
  </tbody>
</table>


#1779 Funding for ReactiveDOT & related developments