Uniswap v4 hook that defends LP pools through stock splits and dividends. The arb pays the LPs, not the bot.
robinhood
Joined September 2026
- Tweets63
- Following4
- Followers192
- Likes48
Pinned Tweet
$PARITY
CA: 0x0ac7de2c90d3fc6827256d4bbca47edb0f6519ff
Tokenized stocks split and pay dividends. The pool has no idea.
When the multiplier updates, the price inside the pool is stale for one block. The first arber takes the difference, and the LP pays for it.
Parity is a Uniswap v4 hook that prices the event before it lands.
useparity.tech
Parity retweeted
Have you joined?
Will post every update there ( including dev updates )
useparity.tech
Parity now has an official TG channel.
t.me/parityRH
Dex has been updated.
Website now also shows the TG channel button.
Parity retweeted
/watch is live on Parity.
Open connection, tells you when a feed crosses a threshold, a verdict flips, or a corporate action enters the horizon. Silent otherwise.
Watchlist stays in your browser. No account, nothing stored to breach.
Updates every 15 min when the cron commits. Not a millisecond tape.
useparity.tech/watch
/watch is live on Parity.
Open connection, tells you when a feed crosses a threshold, a verdict flips, or a corporate action enters the horizon. Silent otherwise.
Watchlist stays in your browser. No account, nothing stored to breach.
Updates every 15 min when the cron commits. Not a millisecond tape.
useparity.tech/watch
Have you joined?
Will post every update there ( including dev updates )
useparity.tech
Parity now has an official TG channel.
t.me/parityRH
Dex has been updated.
Website now also shows the TG channel button.
Parity now has an official TG channel.
t.me/parityRH
Dex has been updated.
Website now also shows the TG channel button.
Global chat is live on Parity. useparity.tech/chat
No accounts. Links are refused outright, because an anonymous room on a finance site is where a drainer link goes.
Last 200 messages persist. The site redeploys every 15 min, so without a volume the room would empty four times an hour.
Parity retweeted
Parity today
- Nav collapsed into a menu
- Parity now works on phone. Phone pass on all 13 pages (the home page was panning 20px sideways, tap targets down at 16px) & site adapted for all types of mobile devices.
-Latest audit has been done.
One of my scripts had a hardcoded path, so the Source page was publishing the build machine's directory layout. Fixed, rerun clean: 171 files, 68,416 lines, 12 of 12 checks.
An audit that never catches you is a badge, not an audit.
useparity.tech/audit
Parity today
- Nav collapsed into a menu
- Parity now works on phone. Phone pass on all 13 pages (the home page was panning 20px sideways, tap targets down at 16px) & site adapted for all types of mobile devices.
-Latest audit has been done.
One of my scripts had a hardcoded path, so the Source page was publishing the build machine's directory layout. Fixed, rerun clean: 171 files, 68,416 lines, 12 of 12 checks.
An audit that never catches you is a badge, not an audit.
useparity.tech/audit
Parity's Radar is live.
Every tokenized equity dashboard trusts a market data vendor for corporate actions.
The vendor is downstream. A dividend is real when the issuer files it with the SEC, not when a calendar endpoint publishes it.
So Parity now reads the filings directly. 23 tokens, 38 action-type 8-Ks in 90 days, cross-checked against what our own pipeline knew.
6 matched. That number is NOT an error rate and the page says so in bold: item 8.01 is a catch-all. MSTR alone files 15 of them, every one a bitcoin purchase, zero corporate actions.
It's a tripwire, not a grade. If the vendor ever drops a real dividend, the issuer's filing sits there unmatched and the weekly record shows the week it happened.
SPY is excluded by structure, not scored as clean. It's a trust, it files NPORT-P, and there is no declaration filing to check a calendar against.
First build of this said 2.6%. That was a bug in my own script, not a finding.
Fixed before shipping, because publishing it would have been a fake indictment of our upstream.
useparity.tech/radar
Small thing on the record page.
The very first Radar run says 1 match, not 6. That was not a swing in filings. That was my script guessing the wrong key when reading our own backtest, loading 0 of 81 historical events, and making the vendor look far worse than it is.
I caught it a minute later. The row is still there, flagged as a suspect build, with a note saying exactly what broke.
Deleting it would have been easier and the history would have looked cleaner. But a monitoring page you can quietly reset is not monitoring, and the first thing anyone should be able to check is whether I edit my own record.
useparity.tech/radar
We have a decently big update tomorrow.
Shipping will be live and for now, everything points at a “perfect” new update.
Meaning there’s been no mistakes/errors at all and it runs smoothly.
Parity.
Parity now audits itself in public: useparity.tech/audit
150 files, 36,992 lines, 10 credential patterns, no allowlist and no skipped extensions. The scanner scans itself too. 12 checks, 110 tests, 0 findings.
It reads clean because we found a live GitHub push token sitting in our own git remote and killed it. The remote is a plain HTTPS URL now and auth comes from the environment at push time.
We called 22 of 23 oracles bad at 12:15 UTC.
Wrong. The feeds were fine, our reference price was 48h old, and we scored them against it.
Fix shipped: live reference refresh before every scan, drift withheld whenever the reference is stale. Latest scan: 23/23 up, 0 bad, 10 within 25-50bps of live. useparity.tech/feeds
Also, reaching 200 followers is a great milestone achieved.
We're very thankful, and this is just the start.
Working into getting the best version of parity we're able to deliver, day and night, that's why maybe tweets are inconsistent but, we can assure your, we are working and putting our best into parity.
Make sure to leave any type of feedback under this post and ideas incase you wanna add to the site.
Ran the uptime sweep across 23 feeds. The good news: nothing is offline. The honest part: freshness has degraded hard. Median feed age 1.6h, worst is 16.2h, and 21 feeds sit past their fresh thresholds.
We are not hiding this behind a green dashboard. Feeds that are old are reported as old, not as healthy.
History is thin too: only 7 samples over the last 45.9h, so we are still building a real baseline. Until the sample count is meaningful, treat every age number as a snapshot, not a trend.
Watching the worst offenders, will surface the ones that stay stale across the next cycles.
useparity.tech
Today is wednesday.
If you've been following Parity, you know whats coming.
Hopefully it's all ready for today.
useparity.tech
In Parity, we've mixed multiple technologies together to make user's life easier.
We've been working day and night to bring you working legitimate features.
While being also fully open source.
Parity is just next up, thanks for all the support, we know who's been there since the start.
useparity.tech
Three things shipped on useparity.tech today.
Feed staleness now has a record, not just a snapshot.
23 Chainlink feeds, every scan appended, uptime counted over scans taken so a dead cron reads as a thin record instead of healthy silence.The watchtower is subscribable: feed.xml + feed.json.
It only emits when something is wrong. A feed that announces good news trains you to ignore it.And a redeem simulator that does the contract's arithmetic with the contract's inputs. USAR at $100k pays $99,022 right now.
That $978 is a feed 2.6 days old, and nothing on chain reverts on a stale oracle. Parity does not fix that. The hook prices corporate actions, it has no opinion about an oracle that stopped writing.Honest gap: the uptime page needs a few hundred scans before it can tell you whether all-stale is normal here. Roughly Wednesday.
If you want it shorter for reach, this version keeps the sting and drops the setup:
useparity.tech now prices a redeem the way the vault would: USAR at $100k pays $99,022.
The missing $978 is a Chainlink feed that hasn't written in 2.6 days.
Parity doesn't fix that. The hook prices corporate actions, it has no opinion about an oracle that stopped writing.
Wednesday will come with multiple updates about this feature.
On the meantime, we'll keep you updated with new inspiring news.
Three things shipped on useparity.tech today.
Feed staleness now has a record, not just a snapshot.
23 Chainlink feeds, every scan appended, uptime counted over scans taken so a dead cron reads as a thin record instead of healthy silence.The watchtower is subscribable: feed.xml + feed.json.
It only emits when something is wrong. A feed that announces good news trains you to ignore it.And a redeem simulator that does the contract's arithmetic with the contract's inputs. USAR at $100k pays $99,022 right now.
That $978 is a feed 2.6 days old, and nothing on chain reverts on a stale oracle. Parity does not fix that. The hook prices corporate actions, it has no opinion about an oracle that stopped writing.Honest gap: the uptime page needs a few hundred scans before it can tell you whether all-stale is normal here. Roughly Wednesday.
If you want it shorter for reach, this version keeps the sting and drops the setup:
useparity.tech now prices a redeem the way the vault would: USAR at $100k pays $99,022.
The missing $978 is a Chainlink feed that hasn't written in 2.6 days.
Parity doesn't fix that. The hook prices corporate actions, it has no opinion about an oracle that stopped writing.
Wednesday will come with multiple updates about this feature.
On the meantime, we'll keep you updated with new inspiring news.