Complete C#/.NET port of the Uniswap SDK monorepo (v2-v4, Universal Router, UniswapX, Permit2) - exact BigInteger/BigRational math, verified to the digit against upstream. 1,694 tests, on NuGet.
What HEY knows
Building
Last shipped 43 days agoActive: 0 meaningful events in 30 days; latest ship 43 days ago.Evidence →Source
Follow puts UniswapSharp on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
“Active” by the activity rule's longer window: 3 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-06, is more than 30 days old.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-08-31 – 2026-09-06 · 13 commitsv2.0.1v2.0.0+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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.
Source3 registered sources, 1 of them context only.ReadRecordsCode changes, week of 2026-08-31 – 2026-09-06 · 13 commitsv2.0.1v2.0.0+3 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
This week HEY looked inside 5 of 12 commits to see what changed: 1 changed code, 3 documentation or maintenance only, 1 could not be classified. One code change is enough for the week to count, so HEY stopped there. 1 automated commit (bot accounts or a repeating scripted message) not counted.
Record ship:411c70fb… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.
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: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.
Questions HEY can answer about UniswapSharp — as of 2026-10-19
Is UniswapSharp still being built?
DerivedActive: 0 meaningful events in 30 days; latest ship 43 days ago.Evidence →
What did UniswapSharp ship last?
FactCode changes, week of 2026-08-31 – 2026-09-06 · 13 commits — Code activity, 43 days ago.Evidence →
What does HEY not know about UniswapSharp?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.Details →
HEY keeps these on record as context. None counts toward the activity status or Build Momentum; each says why.
SDK releaseUniswapSharp 2.0.12026-09-06Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.
SDK releaseUniswapSharp 2.0.02026-09-04Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.
SDK releaseUniswapSharp 1.0.02026-07-13Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.
SDK releaseUniswapSharp 1.0.0-rc.22026-07-13Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.
SDK releaseUniswapSharp 1.0.0-rc.12026-07-12Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.
