Skip to main content

Ispolink

Ispolink — an AI/HR / Web3 jobs / GameFi project with AI matching of candidates and a Web3 ecosystem (ATS + “Ispoverse” and an AI agent per the website description). The project has a multi‑chain token, ISP (the website lists the Ethereum/BSC/Polygon networks; the ERC‑20 contract in this card is Ethereum).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a platform/ecosystem for Web3 job openings and hiring, where the system helps find suitable candidates and automate recruiting.
  • Who it’s for: Web3/IT employer companies and candidates/developers.
  • Why onchain/token: the ISP token is claimed as a means of payments/discounts/incentives and of participation in the ecosystem; the blockchain is used as the carrier of the token and (per the whitepaper) for payments/verifications.

How it works (very briefly)

  1. The user does: a company posts a job opening or a candidate fills in a profile/CV.
  2. The system does: applies AI/ML modules (CV parsing, matching by criteria, candidate recommendations) and helps run the selection process (per the whitepaper).
  3. The user gets: a list of relevant candidates/job openings and a faster recruiting process (per the description).
  4. Where the blockchain is: the ISP token (ERC‑20 on Ethereum and a bridge/versions on other networks per the website) and the claimed payment/incentive mechanics.
  5. Token role (if any): payments for services/discounts, staking/mining and governance/voting in the ecosystem (per the ISP Token page).

Quick links: AI thesis fit

Project passport

Field Value
Project name Ispolink
Also known as (aliases) ISP Token, Ispoverse
Logo (logo) ../assets/256_ispolink_logo.svg
Token symbol (ticker) ISP
Category AI/HR | Web3 jobs | GameFi
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) — (not found in the extracted Tier‑1)
Project status (status) active (website and whitepaper available)
Token (standard) ERC-20
Token contract 0xc8807f0f5ba3fa45ffbdc66928d71c5289249014
Token model (token_type) utility (governance)
Max supply 8,394,601,245.531574652509556763 ISP (per Etherscan max total supply)
Issuance fixed (based on the absence of mint in the published token code; a burn function is present)
Tokenomics (tokenomics, brief) the whitepaper describes sales (private/seed/strategic/public) and “unsold voided”; the website lists the utilities (governance, staking/mining, GameFi, metaverse services, purchase services).
Governance governance via the token is claimed (process details not disclosed in the extracted Tier‑1)
Admins/keys — (not found in the extracted Tier‑1)
Audit Tier‑2: CertiK (Skynet) indicates 1 audit available (PDF)
Bug bounty — (not found in the extracted Tier‑1)
Team (team) — (not found in the extracted Tier‑1)
Funding (investors/funding) — (not found in the extracted Tier‑1)
AI component (ai_component) CV parsing, ML matching, recommendations
Use‑case (use_case) Web3 talent + job matching
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 2 / 3
Last verified 2026-02-06

General project overview

In its whitepaper, Ispolink describes a “cross-chain platform for developers” and an ATS approach to hiring in Web3/IT: the project claims to be building a platform that connects companies and candidates, with the key differentiator being the use of AI/ML for CV parsing, a matching algorithm and candidate recommendations. On the website, the product is also described as a “GameFi AI-driven platform for Web3 developers” and as part of a broader ecosystem (including GameFi/metaverse and an AI agent).

Features/modules

  • AI matching of candidates: CV parsing, ML matching against the job description and candidate recommendations (per the whitepaper).
  • Recruiting ATS/workflow: management of selection stages via a dashboard, automation and an “instant feedback” mechanic (per the whitepaper).
  • ISP token economy and utility: payments/discounts/incentives, staking/mining, governance, GameFi and metaverse services (per the ISP Token page).
  • Ecosystem products: “Ispoverse” and “Friendly Giant AI Agent” (per the website).

Typical scenarios

  • Scenario 1: a company posts a job opening → the ML algorithm helps match candidates → hiring is accelerated (per the whitepaper).
  • Scenario 2: a candidate uploads a CV → the AI parses it and forms the data for the match rate → the candidate sees the relevance of job openings (per the whitepaper).
  • Scenario 3: a user uses ISP for access to services/discounts/participation in staking/governance in the ecosystem (per the ISP Token page).

Getting started (wallet/network)

  • What you need: an account/access to the app.ispolink.com web application (per the website). If the token is needed — an EVM wallet.
  • Network/chain: for the ISP token the website lists Ethereum/BSC/Polygon; the ERC‑20 contract in this card is Ethereum.
  • Fees: network fees (gas) for onchain operations with the token; within the product, payments for services with the token are possible (per the whitepaper and the ISP Token page).

Architecture/tech (non‑AI)

  • Components: the ATS web platform (dashboard), offchain AI/ML services for the matching algorithms, the ISP token and the related smart contracts/bridges (per the website), as well as the payment flow (described in the whitepaper at a conceptual level).
  • Participant roles: employers, candidates, ISP holders/stakers, platform operators.
  • Where logic runs: AI/ML matching and UX — offchain; the token and onchain operations (transfers/staking/bridging) — onchain.
  • Dependencies: EVM networks (Ethereum/BSC/Polygon per the website), web infrastructure; specific oracles/DA are not described in the extracted Tier‑1.

Token/economics (expanded, no forecasts)

  • Token utility: the ISP Token page lists the utilities: token governance (voting/proposals), staking & mining (LP provision), GameFi/rewards for tasks/referrals, metaverse services (payments for rentals/events), purchase services (discounts/bonuses), NFTs.
  • Protocol necessity drivers: in the whitepaper the token is described as a medium of exchange within the platform (payments by employers/job seekers) and as incentives for contribution/activity; on the website the utilities are extended to staking/governance/GameFi.
  • Who pays fees: users pay network fees (gas) for onchain operations; the whitepaper describes the flow of paying for services with the token within the platform.
  • Where fees go: network fees — to the miners/validators of the respective networks; the platform’s internal commissions/fees and their distribution are not detailed in the extracted Tier‑1.
  • Issuance/burn: max total supply per Etherscan; the published token code has burn() (the possibility of burning) and there is no described inflationary issuance in the extracted sources.
  • Security/incentive mechanisms: staking/mining are claimed on the website; the whitepaper also describes incentives for activity (“social mining”, “mining” as payment for resources).
  • Distribution and token issuance schedule: the whitepaper specifies 4 sales (private/seed/strategic/public) and that unsold tokens are “voided”; the numerical distribution/release schedule parameters are not presented in the extracted PDF fragment.
  • Treasury: — (not found in the extracted Tier‑1)

Governance

  • Who makes decisions: —
  • How protocol parameters change: —
  • Where decisions are discussed/made: —
  • Keys/multisig: —

Security and incidents

  • Audits: — (if many — put a table below)
  • Bug bounty: —
  • Incidents: —
  • Threat model: —

Project status and timeline

  • Current status: —
  • Key releases/milestones: —
  • Roadmap: —

Ecosystem/integrations

  • Integrations: —
  • Partners: —
  • Where it’s actually used: —

AI component of the project

  • What is real AI here? the whitepaper describes AI modules: CV parsing, ML matching of candidates against the job description and recommendations of potential candidates; the website additionally mentions an AI agent (Friendly Giant) “powered by DeepSeek R1 model”.
  • What is truly onchain? the ISP token (ERC‑20 on Ethereum) and, per the website, versions/bridges on BSC/Polygon; the onchain part is token accounting and the related operations.
  • Why is a token needed? payment for services/access and incentive mechanics (whitepaper), as well as governance, staking/mining and ecosystem payments/discounts (ISP Token page).
  • Red flags (based on the information found): AI‑washing — the absence of quality/accuracy metrics for the matching algorithm in the extracted Tier‑1; onchain‑washing — the core ATS product can work without a blockchain; token‑washing — the utilities are listed broadly, it is important to check that they are actually enforced and used.

DecAI Fit component summary

  • DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity low 1
Token necessity medium 2
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 2.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI is used for CV parsing, ML matching of candidates against the job description and candidate recommendations.
  • Evidence: Tier‑1 — https://ispo-files.s3.eu-central-1.amazonaws.com/static/Ispolink_Whitepaper_v1.pdf
  • Why sufficient / why not (one line): the whitepaper lists specific AI use‑cases and the criteria of the matching model.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no public, replicable demo/case of the matching algorithm at work was found in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://ispolink.com/
  • Why sufficient / why not (one line): the website describes the product, but without verifiable demo steps/public results of AI matching in the extracted content.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: — (not found)
  • Context (version/date/how measured): — (not found)
  • Evidence: Tier‑1 — https://ispo-files.s3.eu-central-1.amazonaws.com/static/Ispolink_Whitepaper_v1.pdf
  • Why sufficient / why not (one line): the extracted Tier‑1 lack accuracy/conversion/matching quality metrics.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): the whitepaper describes AI use‑cases (CV parsing / ML matchmaking / suggestions) and an example of the criteria; the website mentions an AI agent (DeepSeek R1).
  • Evidence: Tier‑1 — https://ispo-files.s3.eu-central-1.amazonaws.com/static/Ispolink_Whitepaper_v1.pdf ; https://ispolink.com/
  • Why sufficient / why not (one line): there are descriptions of functions/approaches, but no detailed architecture of the model/datasets/versions.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Ethereum (ERC‑20)
  • Addresses/identifiers: 0xc8807f0f5ba3fa45ffbdc66928d71c5289249014
  • Evidence: Tier‑1 — https://etherscan.io/token/0xc8807f0f5ba3fa45ffbdc66928d71c5289249014 ; https://ispolink.com/isp-token
  • Why sufficient / why not (one line): Etherscan and the website confirm the token contract and the multi‑chain presence.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: in the extracted Tier‑1 there are no confirmed addresses/contracts of a “payment system” or onchain verifications, other than the token and links to the bridge/staking.
  • Evidence: Tier‑1 — https://ispolink.com/isp-token ; https://ispo-files.s3.eu-central-1.amazonaws.com/static/Ispolink_Whitepaper_v1.pdf
  • Why sufficient / why not (one line): the sources describe the onchain idea/utility, but without specific onchain protocol modules (other than the token) in the extracted form.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the core functionality of the ATS/talent matching can work without a blockchain; in the extracted Tier‑1 there is no proof of the irreplaceability of onchain.
  • Evidence: Tier‑1 — https://ispolink.com/ ; https://ispo-files.s3.eu-central-1.amazonaws.com/static/Ispolink_Whitepaper_v1.pdf
  • Why sufficient / why not (one line): onchain is used as an additional economy/utility, but it is not shown as a mandatory condition for the product to work.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, ISP (ERC‑20 on Ethereum), and versions on other networks (per the website).
  • Evidence: Tier‑1 — https://ispolink.com/isp-token ; https://etherscan.io/token/0xc8807f0f5ba3fa45ffbdc66928d71c5289249014
  • Why sufficient / why not (one line): the website and the explorer confirm the existence of the token.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): the whitepaper claims that employers pay ISP for access to job seekers, and job seekers spend ISP for access to employer profiles; the website states “purchase services / payment process”.
  • Evidence: Tier‑1 — https://ispo-files.s3.eu-central-1.amazonaws.com/static/Ispolink_Whitepaper_v1.pdf ; https://ispolink.com/isp-token
  • Why sufficient / why not (one line): the sources directly link ISP to paying for/purchasing platform services.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): the website claims staking/mining and GameFi rewards (for tasks/referrals); the whitepaper describes incentives for activity (“social mining”).
  • Evidence: Tier‑1 — https://ispolink.com/isp-token ; https://ispo-files.s3.eu-central-1.amazonaws.com/static/Ispolink_Whitepaper_v1.pdf
  • Why sufficient / why not (one line): incentives and staking are listed as token utilities in the official sources.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): the ISP Token page claims “Token Governance” (voting and proposals with ISP).
  • Evidence: Tier‑1 — https://ispolink.com/isp-token
  • Why sufficient / why not (one line): the governance utility is listed in the official description of the token.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): basic payments/access can be implemented without the token (fiat/classic subscriptions), so the token looks partially replaceable for the core ATS.
  • Evidence: Tier‑1 — https://ispolink.com/ ; https://ispo-files.s3.eu-central-1.amazonaws.com/static/Ispolink_Whitepaper_v1.pdf
  • Why sufficient / why not (one line): the extracted Tier‑1 do not show that the platform is inoperable without the token.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://ispo-files.s3.eu-central-1.amazonaws.com/static/Ispolink_Whitepaper_v1.pdf description of the product and the AI modules (CV parsing/ML matchmaking/suggestions) + the statement about the token as a utility for payments/incentives.
Tier‑1 https://ispolink.com/ description of the platform and the ecosystem; mention of the AI agent and the AI‑based matching engine.
Tier‑1 https://ispolink.com/isp-token ISP token utilities (governance, staking/mining, GameFi, metaverse services, purchase services) and the list of networks/contracts.
Tier‑1 https://etherscan.io/token/0xc8807f0f5ba3fa45ffbdc66928d71c5289249014 confirmation of the onchain existence of the ISP token and the max total supply.
Tier‑2 https://skynet.certik.com/projects/ispolink third‑party source: the existence of an audit (PDF) and security metadata (does not replace Tier‑1).

No comments to display

Back to top