Skip to content
HEY Research Lab
Menu

Wayfinder Paths SDK

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: 5 counted ships in 30 days; latest ship 2 days ago. Evidence Source

Build Momentum 51How it is measured

Latest: v0.11.2

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Wayfinder Paths SDK 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 Wayfinder Paths SDK

No account? Email me Wayfinder Paths SDK’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.

More detail
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: 5 counted ships in the last 30 days, the newest 2026-11-12.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv0.11.2Code changes this week (since Mon 9 Nov) · 8 commitsCode changes, week of 2026-11-02 – 2026-11-08 · 4 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 45d ago.

Building

  • Building activityMeasuredRead 21m 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 3d ago.
  • Published packagesMeasuredRead 3d ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, 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

v0.11.2

GitHub releaseSource-backed

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

Published to PyPI on 2026-11-12: Everything merged from #784 through #867 since v0.11.1. Path publishing needs this release: review rejects skill exports built by 0.11.1. Added 1. Onchain token orders via Definitive Flash: DefinitiveAdapter and the onchain_place_order… Show all

Published to PyPI on 2026-11-12: https://pypi.org/project/wayfinder-paths/0.11.2/ Everything merged from #784 through #867 since v0.11.1. Path publishing needs this release: review rejects skill exports built by 0.11.1. Added 1. Onchain token orders via Definitive Flash: DefinitiveAdapter and the onchain_place_order / onchain_cancel_order / onchain_list_orders MCP tools rest limit, stop-loss, take-profit, breakout-buy, trailing-stop and TP + SL orders on EVM tokens through the Wayfinder relay. Tokens stay in the wallet until fill; the adapter checks Definitive's EIP-712 order…

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

Release, read from the team’s GitHub · no deployment linked
What it names
The team’s release names it: “v0.11.2”.
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
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 established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to 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 2026-11-12 20:25 UTC; HEY first knew on 2026-11-12.
Not known
  • HEY does not hold the commit the release was cut from.
  • HEY has not observed a deployment of this change.
  • Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.

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)Post this ship on X

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. Code changes this week (since Mon 9 Nov) · 8 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in wayfinderfoundation/wayfinder-paths-sdk.

    How HEY read this week

    This week HEY looked inside 1 of 8 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 this week (since Mon 9 Nov) · 8 commits (opens in a new tab)

  2. Code changes, week of 2026-11-02 – 2026-11-08 · 4 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in wayfinderfoundation/wayfinder-paths-sdk.

    How HEY read this week

    This week HEY looked inside 1 of 4 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-11-02 – 2026-11-08 · 4 commits (opens in a new tab)

  3. Code changes, week of 2026-10-26 – 2026-11-01 · 5 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in wayfinderfoundation/wayfinder-paths-sdk.

    How HEY read this week

    This week HEY looked inside 1 of 5 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-10-26 – 2026-11-01 · 5 commits (opens in a new tab)

  4. Code changes, week of 2026-10-19 – 2026-10-25 · 1 commit

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in wayfinderfoundation/wayfinder-paths-sdk.

    How HEY read this week

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

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

  5. Code changes, week of 2026-09-28 – 2026-10-04 · 2 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in wayfinderfoundation/wayfinder-paths-sdk.

    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.

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

  6. Code changes, week of 2026-09-14 – 2026-09-20 · 2 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in wayfinderfoundation/wayfinder-paths-sdk.

    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.

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

  7. v0.11.1

    GitHub releaseSource-backed

    First PyPI release since 0.11.0. Contains everything merged from #445 through #782. Added 1. Solana support (#521, #522, #524, #525, #530, #532, #534, #549, #553, #554, #574, #576, #584): Wallets are now EVM+SVM rings — create returns both addresses, reads come from the ring… Show all

    First PyPI release since 0.11.0. Contains everything merged from #445 through #782. Added 1. Solana support (#521, #522, #524, #525, #530, #532, #534, #549, #553, #554, #574, #576, #584): Wallets are now EVM+SVM rings — create returns both addresses, reads come from the ring endpoint, and core_get_wallets includes SOL/SPL balances. Solana signing + broadcast with priority-fee fan-out across RPCs, base58 mint resolution in token lookups, Solana branches in onchain_swap/onchain_send, cross-chain swaps signed with the source-chain leg and paid to the destination-chain leg, and core…

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

Other changes on HEY’s record

10 changes on HEY’s record for Wayfinder Paths SDK: 2 releases · 1 new Verified Builder or owner proof · 1 new project on HEY · 6 weeks of code pushed.

All 10 changes for Wayfinder Paths SDK →

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

Sources

1 place HEY reads for Wayfinder Paths SDK