Skip to content
HEY Research Lab
Menu

IfSoFinance

$IFSO

Payments · Utility

Not named by the project: HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership. Token market

Contract 0x0cfa417ee7748a13de76389d861abd1307ae1fa2

HEY holds 39 other Robinhood Chain tokens with the ticker $IFSO. This page is only the contract above. See them

Is this your project? Claim it →

Conditional USDG payments on Robinhood Chain.

What HEY knows

Development

Shipping consistentlyShipping: 5 counted ships in 30 days; latest ship today. Evidence Source

Build Momentum 60How it is measured

Latest: Update 37: stable error codes and GET /v1/errors

Token market · context

Active marketTracked token: $11K fully diluted valuation

Token check

Not named by the project
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

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

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

Attention
Building ranks ahead, and the market already notices it, among comparable projects: its building is ahead of 98.4% of them, its market attention ahead of 69.1% (a gap of 29.4). What the Discovery Gap is

It compares building with market attention; it is not a prediction and not a reason to trade.

More detail
Product usage
Fact1 of 1 watched contract active · 34 calls to the contracts' own functions over the 3 of 7 days HEY holds; the other 12,261 of 12,295 calls were ERC-20 token transfers and approvals, which trading alone produces; the rest unknown, not zero.

Counted from the chain. Usage says the contracts are used, not that anyone is building.

Contracts
Fact1 contract on record for code changes, 1 with published source code; latest change today: Contract 0x0cfa…1fa2 source published on the explorer. Source
Not yet known
Unknown3 gaps: Official docs (not tied to the project yet), API description (not tied to the project yet), Official site changes (not tied to the project yet). Only docs others link to; none the project publishes itself.
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-10.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsUpdate 37: stable error codes and GET /v1/errorsUpdate 22: /examples commandCode changes this week (since Mon 9 Nov) · 74 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".
Verified Builder.
The quality gate found counted building from the project's own sources.
Source5 registered sources, 2 of them context only.ReadRecordsUpdate 37: stable error codes and GET /v1/errorsUpdate 22: /examples commandCode changes this week (since Mon 9 Nov) · 74 commits+4 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.
Not named by the project.
Not named by the project: HEY has not confirmed that the project stands behind this contract — HEY knows it from a launchpad record, and the site that record named does not name it.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedNot named by the project: HEY knows it from a launchpad record, and the site that record named does not name it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Active market.
Active market: the pool holds liquidity and the token traded in the last day.
Source7 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Active market”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Research coverage: HEY can answer 14 of the 17 research questions that apply.
14 of 17 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 1d ago.

Building

  • Building activityMeasuredRead 58m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1h ago.
  • TimelineMeasured

Official site

  • Official docsNot tied to the project yetOnly docs others link to; none the project publishes itself.
  • API descriptionNot tied to the project yetIts website is not yet confirmed as the project’s own.
  • Official site changesNot tied to the project yetIts website is not yet confirmed as the project’s own.

Contracts

  • Contract creationMeasuredRead 6h ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 10h ago.
  • Contract interfaceMeasuredRead 10h ago.

Market

  • Current marketMeasuredRead 7m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead today.
  • LocksMeasuredRead 1h ago.
  • Market checksMeasured

Not applicable here: Repository details, Published packages, Package advisories, 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 (context only) (opens in a new tab)GitHub (opens in a new tab)X (opens in a new tab)DEX Screener (opens in a new tab)RHTools (opens in a new tab)Sources

Latest ship

Checked

Update 37: stable error codes and GET /v1/errors

GitHub releaseSource-backed

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

stable error codes and GET /v1/errors

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

Release, read from the team’s GitHub · no deployment linked
What it names
The team’s release names it: “Update 37: stable error codes and GET /v1/errors” (update-37).
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. 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-10 14:02 UTC; HEY first knew on 2026-11-10.
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. 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

Shared change · Verified Builder

IfSoFinance is now a Verified Builder: HEY checked its builder sources.

5 meaningful development events were recorded in the last 30 days. Builder status: Shipping.

Observed by HEY on 2026-11-10Source: HEY’s research record

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: 9 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. 14 releases in ifsodev/ifso today

    GitHub release

    Show all 14 releases

    1. Update 36: GET /v1/limits

      GitHub releaseSource-backed

      GET /v1/limits

      View evidence: Update 36: GET /v1/limits (opens in a new tab)

    2. Update 35: persisted feed status with a reason

      GitHub releaseSource-backed

      persisted feed status with a reason

      View evidence: Update 35: persisted feed status with a reason (opens in a new tab)

    3. Update 34: team alias table

      GitHub releaseSource-backed

      team alias table

      View evidence: Update 34: team alias table (opens in a new tab)

    4. Update 33: cache and rate-limit headers on /v1

      GitHub releaseSource-backed

      cache and rate-limit headers on /v1

      View evidence: Update 33: cache and rate-limit headers on /v1 (opens in a new tab)

    5. Update 32: backup freshness monitor

      GitHub releaseSource-backed

      backup freshness monitor

      View evidence: Update 32: backup freshness monitor (opens in a new tab)

    6. Update 31: prune cached price rounds older than the live window

      GitHub releaseSource-backed

      prune cached price rounds older than the live window

      View evidence: Update 31: prune cached price rounds older than the live window (opens in a new tab)

    7. Update 30: amount suffixes and separators

      GitHub releaseSource-backed

      amount suffixes and separators

      View evidence: Update 30: amount suffixes and separators (opens in a new tab)

    8. Update 29: GET /v1/mine paged with state and role filters

      GitHub releaseSource-backed

      GET /v1/mine paged with state and role filters

      View evidence: Update 29: GET /v1/mine paged with state and role filters (opens in a new tab)

    9. Update 28: daily ops digest to the ops chat

      GitHub releaseSource-backed

      daily ops digest to the ops chat

      View evidence: Update 28: daily ops digest to the ops chat (opens in a new tab)

    10. Update 27: record transaction receipts and reconcile sent rows

      GitHub releaseSource-backed

      record transaction receipts and reconcile sent rows

      View evidence: Update 27: record transaction receipts and reconcile sent rows (opens in a new tab)

    11. Update 26: end-of-period and article dates

      GitHub releaseSource-backed

      end-of-period and article dates

      View evidence: Update 26: end-of-period and article dates (opens in a new tab)

    12. Update 25: Idempotency-Key on relayed build, submit, claim and accept

      GitHub releaseSource-backed

      Idempotency-Key on relayed build, submit, claim and accept

      View evidence: Update 25: Idempotency-Key on relayed build, submit, claim and accept (opens in a new tab)

    13. Update 24: RPC scoreboard in /v1/status

      GitHub releaseSource-backed

      RPC scoreboard in /v1/status

      View evidence: Update 24: RPC scoreboard in /v1/status (opens in a new tab)

    14. Update 23: keeper decision log table

      GitHub releaseSource-backed

      keeper decision log table

      View evidence: Update 23: keeper decision log table (opens in a new tab)

  2. 9 releases in ifsodev/ifso on 9 Nov

    GitHub release

    Show all 9 releases

    1. Update 22: /examples command

      GitHub releaseSource-backed

      /examples command

      View evidence: Update 22: /examples command (opens in a new tab)

    2. Update 21: GET /v1/contracts addresses and ABIs

      GitHub releaseSource-backed

      GET /v1/contracts addresses and ABIs

      View evidence: Update 21: GET /v1/contracts addresses and ABIs (opens in a new tab)

    3. Update 20: gas runway forecast for relayer, keeper and resolver

      GitHub releaseSource-backed

      gas runway forecast for relayer, keeper and resolver

      View evidence: Update 20: gas runway forecast for relayer, keeper and resolver (opens in a new tab)

    4. Update 19: gas guard for the keeper

      GitHub releaseSource-backed

      gas guard for the keeper

      View evidence: Update 19: gas guard for the keeper (opens in a new tab)

    5. Update 18: help by topic

      GitHub releaseSource-backed

      help by topic

      View evidence: Update 18: help by topic (opens in a new tab)

    6. Bonus update 14: Pay on delivery

      GitHub releaseSource-backed

      What changes · You can now make a pay-on-delivery payment on the website. Tick "Pay on delivery" when you make a v2 payment, pick when the recipient is paid (1 hour, 1 day, 3 days, 7 days or a date you pick) and name a referee. · The money goes to the recipient automatically… Show all
      • What changes
      • You can now make a pay-on-delivery payment on the website. Tick "Pay on delivery" when you make a v2 payment, pick when the recipient is paid (1 hour, 1 day, 3 days, 7 days or a date you pick) and name a referee.
      • The money goes to the recipient automatically when the time is up. Until then you can dispute from your dashboard. After a dispute the referee decides. If the referee does not decide, the money comes back to you, by default 2 days after the release time.
      • The review step shows…
      View evidence: Bonus update 14: Pay on delivery (opens in a new tab)

    7. Update 17: GET /v1/fees/quote

      GitHub releaseSource-backed

      GET /v1/fees/quote

      View evidence: Update 17: GET /v1/fees/quote (opens in a new tab)

    8. Bonus update 13: v2 claim links

      GitHub releaseSource-backed

      What changes · A v2 payment can now go to a claim link instead of a wallet address. Pick "A claim link" when you make the payment. Your browser makes a private key for the link, and only its public address goes to IFSO. After you fund it, you get the link with a copy button.… Show all
      • What changes
      • A v2 payment can now go to a claim link instead of a wallet address. Pick "A claim link" when you make the payment. Your browser makes a private key for the link, and only its public address goes to IFSO. After you fund it, you get the link with a copy button. Anyone who has the link can claim the money, so send it only to the person it is for.
      • Opening the link shows the amount, the asset, the condition in plain words and the expiry, read from the chain. The person picks a browser wallet…
      View evidence: Bonus update 13: v2 claim links (opens in a new tab)

    9. Update 16: alert severity tag and repeat count

      GitHub releaseSource-backed

      alert severity tag and repeat count

      View evidence: Update 16: alert severity tag and repeat count (opens in a new tab)

  3. Code changes this week (since Mon 9 Nov) · 74 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in ifsodev/ifso.

    How HEY read this week

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

Other changes on HEY’s record

53 changes on HEY’s record for IfSoFinance: 46 releases · 1 new Verified Builder or owner proof · 1 new project on HEY · 1 contract change · 4 other changes in 2 more kinds.

All 53 changes for IfSoFinance →

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)

The token’s market, checks, locks and stamps below are context only: none of it changes activity status or Build Momentum.

Contract 0x0cfA417ee7748a13dE76389D861Abd1307AE1Fa2 on Robinhood Chain

0x0cfa…1fa20x0cfa417ee7748a13de76389d861abd1307ae1fa2

Not named by the project.

Market context

Active market · FDV (fully diluted) $10.8K · current liquidity $9.1K · reading under an hour old (DEX Screener).

Token

Launch stage
Trading in a DEX pool
Pair age
1d ago

Market

24h volume
$17K
Trades 24h
124 buys · 189 sells
Price 24h
down 42.7 percent over 24 hours· 6hdown 21.3 percent over 6 hours· 1hdown 4.7 percent over 1 hour

The tracked token has liquidity, and trading volume was read for it within a day of its newest market reading — in that reading, or in HEY’s record of on-chain trades.

Market history, trading and checks →

Sources

5 places HEY reads for IfSoFinance
  • Website
    https://ifso.tech/Context onlyContext only because HEY reached this site through a launch record or a listing and nothing yet ties it to this token; it counts once the site names the token’s contract, a GitHub claim names one of the project’s repositories, or a moderator confirms one of them.
  • Docs
    https://ifso.tech/how-it-worksContext onlyThe same reason as the row above that explains it.
  • Repository
    https://github.com/ifsodev/ifsoFrom a launch or market listing
  • X
    https://x.com/IfSoFinance@IfSoFinance links back to ifso.tech — checked 2026-11-10.From a launch or market listing
  • Telegram
    https://t.me/IFSOonhoodFrom a launch or market listing