Skip to content
HEY Research Lab
Menu

SyncNet

$SYNC

Contract 0x6368e007b9f0b941560ed1f3bceb20247f5eca37

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

Is this your project? Claim it →

SyncNet is building a synchronization layer for token economies on par. Most tokens launch alone. SyncNet introduces SYNs: tokens created around a connection between existing assets, communities and markets. At the center is $SYNC — the network asset and the first synchronization experiment, launched around NET and USDG. The idea is simple: instead of treating every token as an isolated market, SyncNet makes those relationships explicit and composable. $SYNCAT is the first live SYN, connecting the CASHCAT ecosystem with $SYNC and demonstrating the model in production. CASHCAT ← $SYNCAT → $SYNC NET ← $SYNC → USDG Trading activity can generate asset flows through par’s fee mechanics. Rewards depend on actual market activity and are not guaranteed. $SYNC launched with an initial supply of 1 billion tokens, has no mint function, and is deflationary, with supply reduced through permanent burns. One network. Multiple assets. New identities built from existing communities. Sync anything.

Read more

What HEY knows

Development

Last shipped 22 days agoActive: 1 counted ship in 30 days; latest ship 22 days ago. Evidence Source

Build Momentum 25How it is measured

Latest: Code changes, week of 2026-10-12 – 2026-10-18 · 2 commits

Token market · context

Launch pool only

Token check

Project names this contract
FollowCreate alertTerminal preview
Get updates

Get updates

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

No account? Email me SyncNet’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
Attention
Discovery Gap not measured — 24h volume under $1,000. What the Discovery Gap is
More detail
Product usage
Fact1 of 1 watched contract active · 66 calls in 7 days — all token transfers and approvals (ERC-20), which trading alone produces; none reached another function HEY watches.

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; no implementation or interface change recorded.
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Contract activity (partly measured). HEY read its website and found no link to docs.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule: 1 counted ship in the last 30 days, the newest 2026-10-15.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 2 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 33 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 53 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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.
Source3 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 2 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 33 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 53 commits+3 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.
Project names this contract.
Project names this contract: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedProject names this contract: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Launch pool only.
Launch pool only: the only pool is the launch pool holding the token’s own supply, and it traded in the last day.
Source9 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Launch pool only”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Discovery Gap: Not measured — 24h volume under $1,000.
Not measured — market too thin: the tracked token's market reads “Launch pool only”. A Discovery Gap is measured only on an active market that is more than a launch curve and trades at least $1,000 a day: a thin market's attention percentile sits near the floor, so its gap would measure the thinness, not the building.
SourceThe score row: the Build Momentum percentile and the market-attention percentile, both taken over the projects with a market reading.ReadWhat HEY derivedNot measured — market too thin.Not concludedIt compares building with market attention; it is not a prediction and not a reason to trade.
Research coverage: HEY can answer 16 of the 19 research questions that apply.
16 of 19 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 47d ago.

Building

  • Building activityMeasuredRead 5h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • 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 7d ago.

Code and packages

  • Repository detailsMeasuredRead 2d ago.
  • Published packagesMeasuredRead 2d ago.

Contracts

  • Contract creationMeasuredRead 17h ago.
  • Contract activityPartly measuredSome days’ events were decoded; on others only the calls could be read.
  • Published source codeMeasuredRead 6d ago.
  • Contract interfaceMeasuredRead 6d ago.

Market

  • Current marketMeasuredRead 59m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead yesterday.
  • LocksMeasuredRead 52m ago.
  • Market checksMeasured

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

Code changes, week of 2026-10-12 – 2026-10-18 · 2 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:

1 active day in syncnetcapital/syncnet.

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.

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

Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit 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-15; HEY first knew on 2026-10-15.
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)

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: 5 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-09-28 – 2026-10-04 · 33 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in syncnetcapital/syncnet.

    How HEY read this week

    This week HEY looked inside 3 of 33 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 · 33 commits (opens in a new tab)

  2. 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 syncnetcapital/syncnet.

    How HEY read this week

    This week HEY looked inside 3 of 53 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-21 – 2026-09-27 · 53 commits (opens in a new tab)

Other changes on HEY’s record

23 changes on HEY’s record for SyncNet: 1 new Verified Builder or owner proof · 19 market moves · 3 weeks of code pushed.

All 23 changes for SyncNet →

The full change record holds 5 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 0x6368e007B9F0B941560eD1f3bceb20247F5Eca37 on Robinhood Chain

0x6368…ca370x6368e007b9f0b941560ed1f3bceb20247f5eca37

Project names this contract.

Market context

Launch pool only · FDV (fully diluted) $5.7K · liquidity $4.2K (launch pool inventory, not a market) · reading under an hour old (DEX Screener).

Token

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

Market

24h volume
$33
Trades 24h
4 buys · 3 sells
Price 24h
up 0.7 percent over 24 hours· 6hunchanged over 6 hours

The pool still holds the token’s own supply, so its reported liquidity is not a depth figure; trades in the last 24 hours are what make this a market.

Market history, trading and checks →

Market integrity

Liquidity is 60% below the level it held two days running ($10.6K, 2026-09-22).

Market
Launch pool only
Last day with trading
2026-11-05

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-11-06 18:58 UTC · How HEY checks this

Sources

3 places HEY reads for SyncNet