Skip to content
Menu

Pons Fork

RWA

Is this your project? Claim and verify →

Pons Fork — automated creator-fee engine on Robinhood Chain (buyback & burn, cashback, charity, RWA, LP). EVM deployment of the Rebate ecosystem. Monorepo of 12 services + site + backend.

What HEY knows

Building
Dormant: no ship for 71 daysDormant: 0 meaningful events in 30 days; latest ship on 2026-08-09. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-08-03 – 2026-08-09 · 4 commits · · Code activity

Why it matters: The first week of code changes HEY has recorded for this project.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts Pons Fork on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me Pons Fork’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

HEY can answer 7 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Dormant.
“Dormant” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-08-09.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-08-03 – 2026-08-09 · 4 commitsv0.5.0 — RWA Cashback and Fees to LPv0.9.0 — Pons Fork monorepoWhat HEY derivedHEY’s activity rule reads the counted events as “Dormant”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source2 registered sources, 1 of them context only.ReadRecordsCode changes, week of 2026-08-03 – 2026-08-09 · 4 commitsv0.5.0 — RWA Cashback and Fees to LPv0.9.0 — Pons Fork monorepo+1 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
LinksGitHubSources

Latest ship

Checked

Code changes, week of 2026-08-03 – 2026-08-09 · 4 commits

Code activitySource linked

What changed, in the repository’s own words:

1 active day in rebateprotocol/pons_fork.

This week HEY looked inside 2 of 4 commits to see what changed: 1 changed code, 1 could not be classified. One code change is enough for the week to count, so HEY stopped there.

Record ship:ae8553be… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Shared change · Release

Pons Fork shipped v0.5.0 — RWA Cashback and Fees to LP.

Builder status: Dormant.

Dated 2026-08-09 by the sourceSource: github

View evidence ↗Evidence receipt

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 3 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about Pons Fork — as of 2026-10-19

Is Pons Fork still being built?
DerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-08-09. Evidence
What did Pons Fork ship last?
FactCode changes, week of 2026-08-03 – 2026-08-09 · 4 commits — Code activity, on 2026-08-09. Evidence
What does HEY not know about Pons Fork?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record. Details

Build timeline

  1. 6 releases in rebateprotocol/pons_fork on 9 Aug

    GitHub release

    Show all 6 releases

    1. v0.5.0 — RWA Cashback and Fees to LP

      GitHub releaseSource linked

      2026-07-28. Protocols four and five. · RWA Cashback — swap fees into Robinhood tokenized stocks and pay holders the basket the deployer picked. · Fees to LP — add fees as liquidity, route the LP fees to the treasury. Also: the charity registry expanded to 27 verified… Show all
      • 2026-07-28. Protocols four and five.
      • RWA Cashback — swap fees into Robinhood tokenized stocks and pay holders the basket the deployer picked.
      • Fees to LP — add fees as liquidity, route the LP fees to the treasury. Also: the charity registry expanded to 27 verified organisations, and the holders API hardened for scale. Historical tag — the last pre-consolidation commit.
      View evidence: v0.5.0 — RWA Cashback and Fees to LP (opens in a new tab)

    2. v0.4.0 — the v2-ready port

      GitHub releaseSource linked

      2026-07-27. All three protocols re-implemented against the Pons v2 design — pull-based fee escrow, bonding curve to Uniswap v4 graduation — built and left dormant until v2 activates on mainnet. Historical tag, v2 lineage only.

      View evidence: v0.4.0 — the v2-ready port (opens in a new tab)

    3. v0.2.0 — ponsfork.com goes live

      GitHub releaseSource linked

      The public site, 2026-07-25: landing page, live token list read straight off Robinhood Chain, per-token pages with mode badges. Hand-written static HTML, no bundler, no build step. Historical tag, site lineage only.

      View evidence: v0.2.0 — ponsfork.com goes live (opens in a new tab)

    4. v0.3.0 — Charity, the third protocol

      GitHub releaseSource linked

      2026-07-26. Fees routed to real charities at a 0% service fee, with the deployer choosing the split via an on-chain memo transaction. Shipped alongside the Disperse batch-payout contract that makes paying hundreds of holders affordable. Historical tag, disperse lineage; the… Show all

      2026-07-26. Fees routed to real charities at a 0% service fee, with the deployer choosing the split via an on-chain memo transaction. Shipped alongside the Disperse batch-payout contract that makes paying hundreds of holders affordable. Historical tag, disperse lineage; the charity engine shipped the same day in its own repo.

      View evidence: v0.3.0 — Charity, the third protocol (opens in a new tab)

    5. v0.1.0 — the first two engines

      GitHub releaseSource linked

      The two protocols that started Pons Fork, ported from the Solana bots to Robinhood Chain in TypeScript/viem on 2026-07-20. · Agentic Mode — claim creator fees, buy the token back, burn it. · Cashback — claim creator fees, pay holders in ETH pro-rata. Historical tag. It predates… Show all
      • The two protocols that started Pons Fork, ported from the Solana bots to Robinhood Chain in TypeScript/viem on 2026-07-20.
      • Agentic Mode — claim creator fees, buy the token back, burn it.
      • Cashback — claim creator fees, pay holders in ETH pro-rata. Historical tag. It predates the monorepo, so it points into the agentic engine's own lineage; Cashback shipped the same day in a separate repo. Whole-project states begin at v0.9.0.
      View evidence: v0.1.0 — the first two engines (opens in a new tab)

    6. v0.9.0 — Pons Fork monorepo

      GitHub releaseSource verified

      Twelve separate repos folded into one npm workspace, full commit history preserved, no behaviour change to any live service. In this release · Five fee protocols as services: agentic (buyback & burn), cashback (ETH to holders), charity, rwa (tokenized stocks), lp (dormant).… Show all
      • Twelve separate repos folded into one npm workspace, full commit history preserved, no behaviour change to any live service. In this release
      • Five fee protocols as services: agentic (buyback & burn), cashback (ETH to holders), charity, rwa (tokenized stocks), lp (dormant).
      • The ops bots: alerts, notifier. The wallet↔X backend. The ponsfork.com static site. The Disperse contract. The GitBook docs. The dormant Pons v2 engine.
      • 10 systemd units under version control for the first time.
      • Conventional Commits enforced by a zero-dependency git hook. Live on mainnet: agentic, cashback…
      View evidence: v0.9.0 — Pons Fork monorepo (opens in a new tab)

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about Pons Fork? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

7 changes on HEY’s record for Pons Fork: 6 releases · 1 week of code pushed.

All 7 changes for Pons Fork →

The full change record holds 1 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 14h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 2mo ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 5h ago.
  • Published packagesMeasuredRead 5h ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources

  • Repository
    https://github.com/rebateprotocol/pons-fork-v2Context onlyContext only because HEY found this repository by its owner alone and nothing the project controls ties it to the project; it counts once a moderator accepts it, or once the project’s verified owner adds it and a GitHub claim names it, it names the token’s contract, it carries a Robinhood Chain dedication HEY matched to this project, or its homepage is the project’s own site (one the owner did not type in).
  • Repository
    https://github.com/rebateprotocol/pons_forkOfficial