Skip to content
Menu

PaliSadeScan by Virtuals

$PALISADE

AI Agents

Is this your project? Claim and verify →

PaliSade is a read-only onchain security scanner. It checks tokens and wallets across Robinhood Chain, Ethereum, Polygon, Arbitrum, and Solana for rugpulls, honeypots, and dangerous approvals. It never signs, holds keys, or moves funds — six independent signals combine into one verdict: buy or don't.

Read more

What HEY knows

Building
Dormant: no ship for 78 daysDerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-07-30. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-07-27 – 2026-08-02 · 9 commits · · Code activity

Why it matters: The first week of code changes HEY has recorded for this project.

Latest change
DerivedMarket event 2 days ago: Liquidity $13K → $6K in a week. Context, not building. Evidence
FollowCreate alertTerminal previewView latest ship
Share

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

No account? Email me PaliSadeScan by Virtuals’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.

Product usage
UnknownThe project has a contract, but HEY does not count its calls yet: a token joins the watch once it takes calls in a thirty-day window, and any contract the project’s own sources name is watched. Unknown, not zero.
Contracts
Fact1 contract on record for code changes, 1 with verified source; no implementation or interface change recorded.
Token market · context
Trading inactiveToken unverified
Not yet known
Unknown4 gaps: Official docs (no source), API description (not tied to the project yet), Official site changes (not tied to the project yet), Supply distribution (not enough yet). HEY read its website and found no link to docs.

HEY can answer 15 of the 19 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Dormant.
“Dormant” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-07-30.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-07-27 – 2026-08-02 · 9 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Dormant”.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 verified building evidence from the project's own sources.
Source3 registered sources, 1 of them context only.ReadWhat 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.
Token unverified.
Token unverified: HEY found the token through a launch record or a market listing, and nothing the project published names it.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedToken unverified: HEY knows it from a launchpad record, and the project’s site 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.
Trading inactive.
Trading inactive: the only pool is the launch pool holding the token’s own supply, and nothing traded in it in the last day.
Source5 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Trading inactive”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Market figures are context only and never change activity status. Methodology
LinksWebsite (context only)GitHubXdefined.fiRHToolsSources

Latest ship

Checked

Code changes, week of 2026-07-27 – 2026-08-02 · 9 commits

Code activitySource linked

What changed, in the repository’s own words:

4 active days in palisadescan/palisade.

This week HEY looked inside 1 of 9 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

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

View evidence ↗

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.

Questions HEY can answer about PaliSadeScan by Virtuals — as of 2026-10-16

Is PaliSadeScan by Virtuals still being built?
DerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-07-30. Evidence
What did PaliSadeScan by Virtuals ship last?
FactCode changes, week of 2026-07-27 – 2026-08-02 · 9 commits — Code activity, on 2026-07-30. Evidence
Is 0x492e5Eb3BE8f2E046F7b096071e923c3B865a868 PaliSadeScan by Virtuals’s own contract?
UnknownToken unverified: HEY found this token through a launchpad record. The declared site does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership. Details
What does HEY not know about PaliSadeScan by Virtuals?
Unknown4 gaps: Official docs (no source), API description (not tied to the project yet), Official site changes (not tied to the project yet), +1 more. HEY read its website and found no link to docs. Details

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about PaliSadeScan by Virtuals? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

9 changes on HEY’s record for PaliSadeScan by Virtuals: 1 market check · 1 build pace change · 6 market moves · 1 week of code pushed.

All 9 changes for PaliSadeScan by Virtuals →

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

Research coverage

HEY can answer 15 of the 19 research questions that apply.

15 of 19 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 3d ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • 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.

Code and packages

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

Contracts

  • Contract creationMeasuredRead 6d ago.
  • Contract activityMeasuredRead 6d ago.
  • Verified sourceMeasuredRead 1d ago.
  • Contract interfaceMeasuredRead 1d ago.

Market

  • Current marketMeasuredRead 3h ago.
  • Market historyMeasuredRead today.
  • Supply distributionNot enough yetNo balance changed in the window HEY reads.
  • LocksMeasuredRead 56m 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.

Sources

Contract
0x492e…a8680x492e5eb3be8f2e046f7b096071e923c3b865a868