Skip to content
HEY Research Lab
Menu

TopWalllet

Integration record: HEY holds no Robinhood Chain evidence for this project (no token, contract or registry listing on the chain), so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim it →

What HEY knows

Development

Shipping consistentlyShipping: 6 counted ships in 30 days; latest ship yesterday. Evidence Source

Build Momentum 61How it is measured

Latest: Code changes this week (since Mon 26 Oct) · 5 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

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

Sign in to follow TopWalllet

No account? Email me TopWalllet’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.

View latest ship
Share
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 6 counted ships in the last 30 days, the newest 2026-10-28.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 26 Oct) · 5 commitsrelay-333464821Code changes, week of 2026-10-19 – 2026-10-25 · 2 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.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".
Research coverage: HEY can answer 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 54d ago.

Building

  • Building activityMeasuredRead 1h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 2d 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 2d ago.
  • Published packagesMeasuredRead 2d 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.

Market figures are context only and never change activity status. Methodology
LinksGitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes this week (since Mon 26 Oct) · 5 commits papatora/walletintel

Code activitySource-backed

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

What changed, in the repository’s own words:

2 active days in papatora/walletintel.

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

Record ship:439e1468… · HEY counts it as building; it does not judge the release’s quality.

Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 2 commits HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or a deployment: code is not a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it to the week of 2026-10-28; HEY first knew on 2026-10-27.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

View evidence ↗ (opens in a new tab)

Shared change · Development spike

TopWalllet: 3 meaningful ships were recorded in the latest 7 days, from 1 in the 7 days before.

Builder status: Shipping.

Dated 2026-10-27 by the sourceSource: HEY Signal

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.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. relay-333464821 papatora/walletintel

    GitHub releaseSource-backed

    View evidence: relay-333464821 (opens in a new tab)

  2. Code changes, week of 2026-10-19 – 2026-10-25 · 2 commits papatora/walletintel

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in papatora/walletintel.

    How HEY read this week

    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. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-10-19 – 2026-10-25 · 2 commits (opens in a new tab)

  3. Code changes, week of 2026-10-12 – 2026-10-18 · 10 commits papatora/walletintel

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in papatora/walletintel.

    How HEY read this week

    This week HEY looked inside 6 of 10 commits to see what changed: 1 changed code, 5 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there. 3 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 10 commits (opens in a new tab)

  4. Code changes, week of 2026-10-05 – 2026-10-11 · 16 commits papatora/walletintel

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in papatora/walletintel.

    How HEY read this week

    This week HEY looked inside 1 of 16 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 3 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 16 commits (opens in a new tab)

  5. Code changes, week of 2026-09-28 – 2026-10-04 · 13 commits papatora/topwalllet

    Code activitySource-backed

    What changed, in the repository’s own words:

    4 active days in papatora/topwalllet.

    How HEY read this week

    This week HEY looked inside 3 of 13 commits to see what changed: 1 changed code, 2 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there. 7 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 13 commits (opens in a new tab)

  6. Code changes, week of 2026-09-21 – 2026-09-27 · 73 commits papatora/topwalllet

    Code activitySource-backed

    What changed, in the repository’s own words:

    7 active days in papatora/topwalllet.

    How HEY read this week

    This week HEY looked inside 4 of 72 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 73 commits (opens in a new tab)

  7. Code changes, week of 2026-09-14 – 2026-09-20 · at least 74 commits papatora/topwalllet

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in papatora/topwalllet.

    How HEY read this week

    This week HEY looked inside 4 of 27 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 74 commits (opens in a new tab)

  8. Code changes, week of 2026-09-07 – 2026-09-13 · at least 53 commits papatora/topwalllet

    Code activitySource-backed

    What changed, in the repository’s own words:

    6 active days in papatora/TopWalllet.

    How HEY read this week

    This week HEY looked inside 4 of 53 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 8 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 53 commits (opens in a new tab)
Earlier ships (1)

  1. Code changes, week of 2026-08-31 – 2026-09-06 · at least 15 commits papatora/topwalllet

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in papatora/TopWalllet.

    How HEY read this week

    This week HEY looked inside 1 of 15 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 19 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 15 commits (opens in a new tab)

Other changes on HEY’s record

11 changes on HEY’s record for TopWalllet: 1 release · 1 build pace change · 9 weeks of code pushed.

All 11 changes for TopWalllet →

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

Questions HEY can answer about TopWalllet — as of 29 Oct

Show the answers
Is TopWalllet still being built?
DerivedShipping: 6 counted ships in 30 days; latest ship yesterday. Evidence
What did TopWalllet ship last?
FactCode changes this week (since Mon 26 Oct) · 5 commits — Code activity, yesterday. Evidence
What does HEY not know about TopWalllet?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

Sources

2 places HEY reads for TopWalllet