Skip to content
HEY Research Lab
Menu

AlabaamaFi

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 →

AlabaamaFi is a Web3 DeFi platform built on Arc Network, bringing essential onchain tools into one seamless experience. Users can connect their wallets, send and manage assets, swap tokens, bridge assets, check wallet balances and activities, and explore onchain transactions all through a simple, fast, and user-friendly interface.

Read more

What HEY knows

Development

Shipping consistentlyShipping: 4 counted ships in 30 days; latest ship 7 days ago. Evidence Source

Build Momentum 46How it is measured

Latest: Code changes, week of 2026-10-26 – 2026-11-01 · 88 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts AlabaamaFi 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 AlabaamaFi

No account? Email me AlabaamaFi’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
More detail
Not yet known
Unknown2 gaps: API description (source unavailable), Official site changes (source unavailable). Its website did not answer.
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: 4 counted ships in the last 30 days, the newest 2026-10-29.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-26 – 2026-11-01 · 88 commitsCode changes, week of 2026-10-19 – 2026-10-25 · 116 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 131 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 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 27m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 8h ago.
  • API descriptionSource unavailableIts website did not answer.
  • Official site changesSource unavailableIts website did not answer.

Code and packages

  • Repository detailsMeasuredRead 18h ago.
  • Published packagesMeasuredRead 18h 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
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)X account @alabaama_fi not found, checked 2026-10-28.Sources

Latest ship

Checked

Code changes, week of 2026-10-26 – 2026-11-01 · 88 commits

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:

4 active days in xidilshan/alabaamafi.

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

Record ship:5bf77838… · 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
3 of 6 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-29; HEY first knew on 2026-10-26.
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 · Official source change

AlabaamaFi's official site changed.

Links the official site declares changed: 2 added, 0 removed. Added docs link….

Observed by HEY on 2026-10-27Source: Project’s official site

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: 4 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, week of 2026-10-19 – 2026-10-25 · 116 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    7 active days in xidilshan/alabaamafi.

    How HEY read this week

    This week HEY looked inside 3 of 116 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

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

  2. Code changes, week of 2026-10-12 – 2026-10-18 · 131 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    7 active days in xidilshan/alabaamafi.

    How HEY read this week

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

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

  3. Code changes, week of 2026-10-05 – 2026-10-11 · 52 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    6 active days in xidilshan/alabaamafi.

    How HEY read this week

    This week HEY looked inside 5 of 52 commits to see what changed: 3 changed code, 2 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-10-05 – 2026-10-11 · 52 commits (opens in a new tab)

  4. Code changes, week of 2026-09-28 – 2026-10-04 · 26 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in xidilshan/alabaamafi.

    How HEY read this week

    This week HEY looked inside 3 of 26 commits to see what changed: 3 changed code. 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-28 – 2026-10-04 · 26 commits (opens in a new tab)

  5. Code changes, week of 2026-09-21 – 2026-09-27 · 53 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    4 active days in xidilshan/alabaamafi.

    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.

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

  6. Code changes, week of 2026-09-14 – 2026-09-20 · at least 99 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    at least 3 active days in xidilshan/alabaamafi since 2026-09-18; the count stops at the newest 100 commits listed.

    How HEY read this week

    This week HEY looked inside 3 of 47 commits to see what changed: 3 changed code. 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 99 commits (opens in a new tab)

Other changes on HEY’s record

9 changes on HEY’s record for AlabaamaFi: 1 new Verified Builder or owner proof · 1 official source change · 7 weeks of code pushed.

All 9 changes for AlabaamaFi →

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

Sources

4 places HEY reads for AlabaamaFi