Skip to content
Menu

blockparty

Analytics

Is this your project? Claim and verify →

A unified Python client for EVM Block Explorer APIs

What HEY knows

Building
Dormant: no ship for 88 daysDormant: 0 meaningful events in 30 days; latest ship on 2026-07-23. Evidence Source

Build Momentum 0How it is measured

Latest ship
v0.8.0 · · GitHub release

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts blockparty 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 blockparty’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
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.

HEY can answer 9 of the 11 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-07-23.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv0.8.0Code changes, week of 2026-07-20 – 2026-07-26 · at least 2 commitsv0.7.5+1 moreWhat 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, 0 of them context only.ReadRecordsv0.8.0Code changes, week of 2026-07-20 – 2026-07-26 · at least 2 commitsv0.7.5+2 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
LinksWebsiteGitHubSources

Latest ship

Checked

v0.8.0

GitHub releaseSource verified

Full Changelog: https://github.com/DefiDebauchery/blockparty/compare/v0.7.5...v0.8.0

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

View evidence ↗Post this ship on X

Builder activity

No meaningful, source-backed updates in the 8 weeks since HEY began reading this project’s sources; earlier weeks are not yet read.

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

Is blockparty still being built?
DerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-07-23. Evidence
What did blockparty ship last?
Factv0.8.0 — GitHub release, on 2026-07-23. Evidence
What does HEY not know about blockparty?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs. Details

Build timeline

  1. Code changes, week of 2026-07-20 – 2026-07-26 · at least 2 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in defidebauchery/blockparty.

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

    View evidence: Code changes, week of 2026-07-20 – 2026-07-26 · at least 2 commits (opens in a new tab)

  2. v0.7.5

    GitHub releaseSource verified

    Full Changelog: https://github.com/DefiDebauchery/blockparty/compare/v0.7.0...v0.7.5

    View evidence: v0.7.5 (opens in a new tab)

  3. 3 releases in defidebauchery/blockparty on 20 Mar

    GitHub release

    Show all 3 releases

    1. v0.7.1

      GitHub releaseSource verified

      Full Changelog: https://github.com/DefiDebauchery/blockparty/compare/v0.7.0...v0.7.1

      View evidence: v0.7.1 (opens in a new tab)

    2. v0.7.0

      GitHub releaseSource verified

      Full Changelog: https://github.com/DefiDebauchery/blockparty/compare/v0.6.0...v0.7.0

      View evidence: v0.7.0 (opens in a new tab)

    3. v0.6.0

      GitHub releaseSource verified

      Initial release

      View evidence: v0.6.0 (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 blockparty? 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 blockparty: 5 releases · 1 build pace change · 1 week of code pushed.

All 7 changes for blockparty →

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 9 of the 11 research questions that apply.

9 of 11 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 3d ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 2mo ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 2d ago.

Code and packages

  • Repository detailsMeasuredRead 9h ago.
  • Published packagesMeasuredRead 9m ago.
  • Package advisoriesMeasuredRead 9h ago.

Not applicable here: 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