Skip to main content

Reactive Network

Reactive Network — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Reactive Network — an EVM‑compatible infrastructure and a set of concepts for event‑driven smart contracts; the project describes the migration from PARSIQ to Reactive Network and the REACT token (see Evidence).

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 network/infrastructure where smart contracts are described as “reactive” and can execute in response to events (per the project’s Tier‑1 blog).
  • Who it’s for: dApp developers and teams that need automation and event‑driven logic.
  • Why onchain/token: the REACT token is described as a utility token for the operation of the network (fees/staking/rewards; see Evidence).

How it works (very briefly)

  1. The user does: creates/deploys smart contracts and/or connects automation.
  2. The system does: executes the logic of reactive contracts in response to events (per the description in the Tier‑1 post).
  3. The user gets: automation/reaction to events without separate offchain infrastructure (as positioned in Tier‑1).
  4. Where the blockchain is: onchain execution/accounting, PoS validation (per Tier‑1).
  5. Token role (if any): REACT is described as gas/fees + staking/rewards + payment for event log processing (per Tier‑1).

Quick links: AI thesis fit

Project passport

Field Value
Project name Reactive Network
Also known as (aliases) PARSIQ; PRQ; REACT
Logo (logo) ../assets/333_parsiq_logo.jpg
Token symbol (ticker) REACT
Category AI/Other | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2025-03-05 (mainnet; claimed)
Project status (status) active
Token (standard) ERC-20
Token contract REACT (ERC‑20): 0x817162975186d4D53dBF5a7377dd45376e2D2fc5; PRQ (ERC‑20): 0x362bc847A3a9637d3af6624EeC853618a43ed7D2
Token model (token_type) utility (payments + staking)
Max supply 500,000,000 (REACT; as claimed)
Issuance burn (fees burned; as claimed)
Tokenomics (tokenomics, brief) PRQ→REACT migration 1:1; gas/staking/rewards (per Tier‑1)
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI applicability for AI agents/dApps
Use‑case (use_case) event-driven smart contracts
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 2 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

Reactive Network, per the Tier‑1 description, positions itself as a network and a set of technologies for event‑driven smart contracts, where contracts “observe” events and trigger actions. The same material describes the “From PARSIQ to Reactive Network” history and the transition of the PRQ token to REACT.

Within DecAIHub it is important to record: (1) AI here is claimed as an area of applicability (AI agents / AI‑powered dApps), (2) the onchain part is the network/contracts and PoS validators (as claimed), (3) the REACT token is a utility token for the operation of the network.

Features/modules

  • Event‑driven contracts: reactive contracts/automation by events (per the Tier‑1 description).
  • Cross‑chain automation: mentioned as a target scenario (per the Tier‑1 description).
  • ReactVM: mentioned as a key execution element (per the Tier‑1 description).

Typical scenarios

  • Scenario 1: a developer sets the conditions for reacting to an event → the contract executes the action automatically (per the description).
  • Scenario 2: the protocol reacts to an event in another network → performs the related step in its logic (per the description).

Getting started (wallet/network)

  • What you need: see the project’s website/docs.
  • Network/chain: the Tier‑1 material claims a mainnet launch date (2025‑03‑05); this card records the ERC‑20 contract of wrapped REACT on Ethereum.
  • Fees: network fees (as described for REACT in the Tier‑1 material).

Architecture/tech (non‑AI)

  • Components: ReactVM (as described), PoS validation, reactive contracts, the REACT token as a utility token (per the Tier‑1 material).

Token/economics (expanded, no forecasts)

  • REACT utility: fees/gas, validator rewards, fees for event log processing (per Tier‑1).
  • Staking: validators stake REACT (per Tier‑1).
  • Migration: a 1:1 PRQ→REACT migration is claimed (per Tier‑1).

Governance

  • Governance: specific governance mechanics are not recorded per Tier‑1 (a separate check against primary sources is needed).

Security and incidents

  • Audits/Bug bounty: links are claimed in links_*; details require a separate check against the primary source of the reports/terms.

Project status and timeline

  • Current status: the Tier‑1 material claims a mainnet launch on 2025‑03‑05.
  • Roadmap: see links_*.

Ecosystem/integrations

  • Ecosystem/cases: the Tier‑1 material lists areas of applicability (DeFi/AI/IoT, etc.); specific production cases require separate Tier‑1 confirmation.

AI component of the project

  • What is real AI here? In the Tier‑1 material, AI is indicated as an area of applicability: the network is positioned as infrastructure into which AI agents/dApps can be embedded; no confirmation of a “built‑in AI component of the protocol” is recorded.
  • What is truly onchain? Per the Tier‑1 description, the onchain part is the execution of reactive contracts and the PoS validation of the network.
  • Why is a token needed? Per the Tier‑1 description, REACT is needed for fees/gas, validator/staking rewards and payment for event log processing.
  • Red flags / what to double‑check: (1) where the boundary between “AI applicability” and “AI component” lies, (2) the public artifacts of the network (contracts/repository/docs) and their coherence, (3) the parameters of the PRQ→REACT migration and the supporting artifacts.

DecAI Fit flags (0/1) and calculation

  • AI: AI_0=1; AI_1=0; AI_2 (decision): 0; AI_3=0; AI_4=0 → ai_score=1
  • Onchain: OC_1=1; OC_2=1; OC_3=0 → onchain_score=2
  • Token: TK_0=0; TK_1=1; TK_2=1; TK_3=0; TK_4=0 → token_score=2
  • Evidence: E_AI_T1=1; E_OC_T1=1; E_TK_T1=1; E_only_T3=0 → evidence_score=3
  • Summary: S=8 → decai_fit_base=4 → AI cap=3 → DecAI Fit=3/6

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): in the Tier‑1 material, AI is explicitly indicated as an area of applicability (AI agents / AI‑powered dApps) for the network’s infrastructure.
  • Evidence: Tier‑1 — https://blog.reactive.network/what-is-reactive-network-and-react-token/
  • Why sufficient / why not (one line): this is Tier‑1 “intent/applicability”, but not proof of a built‑in AI component (AI_1..AI_4 remain 0).
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): no Tier‑1 description of a specific AI component in the protocol/network was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the presence of “AI use cases” in the description does not reveal a specific AI module/feature as part of the protocol.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no Tier‑1 demos/guides for AI features are recorded.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 demo/quickstart for the AI part, the flag is 0.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): AI quality metrics were not found (the AI component as a product is not confirmed).
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): no tech description of the AI architecture/versions was found per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without Tier‑1 tech docs about the AI part, the flag remains 0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Reactive Network (claimed as mainnet); wrapped REACT (ERC‑20) on Ethereum is also indicated.
  • Addresses/identifiers: wrapped REACT (ERC‑20): 0x817162975186d4D53dBF5a7377dd45376e2D2fc5
  • Evidence: Tier‑1 — https://blog.reactive.network/what-is-reactive-network-and-react-token/
  • Why sufficient / why not (one line): the Tier‑1 material publishes the wrapped REACT address and describes the launch/operation of the network.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: Tier‑1 describes onchain automation/execution of “reactive smart contracts” and event log processing as part of the network.
  • Evidence: Tier‑1 — https://blog.reactive.network/what-is-reactive-network-and-react-token/
  • Why sufficient / why not (one line): onchain logic of execution/reaction to events is described, not reducible to token issuance.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: this card has no Tier‑1 argument that without the blockchain a key property breaks down per the SSOT criteria.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 “blockchain‑critical” wording per the replacement test, the flag is 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the REACT token exists (and wrapped REACT on Ethereum); PRQ existed previously.
  • Evidence: Tier‑1 — https://blog.reactive.network/what-is-reactive-network-and-react-token/
  • Why sufficient / why not (one line): the Tier‑1 material describes REACT and the PRQ→REACT migration.
  • Conflict note (if any): —

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): REACT is described as gas/payment for transactions and event log processing.
  • Evidence: Tier‑1 — https://blog.reactive.network/what-is-reactive-network-and-react-token/
  • Why sufficient / why not (one line): Tier‑1 explicitly lists gas fees and processing fees as the token’s utility.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): validators stake REACT and receive rewards (staking and rewards).
  • Evidence: Tier‑1 — https://blog.reactive.network/what-is-reactive-network-and-react-token/
  • Why sufficient / why not (one line): Tier‑1 describes validator staking and rewards.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance use of the token is not recorded in the Tier‑1 material.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 description of governance mechanics, the flag remains 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): No Tier‑1 argument about the replaceability of the token was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 justification of replaceability/irreplaceability, we set 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://blog.reactive.network/what-is-reactive-network-and-react-token/ Description of Reactive Network, the mainnet launch date (claimed), PoS and architectural theses.
Tier‑1 https://blog.reactive.network/what-is-reactive-network-and-react-token/ It is described that REACT is a utility token (fees/staking/rewards/payment for event logs) and a 1:1 PRQ→REACT migration is claimed.
Tier‑1 https://etherscan.io/token/0x817162975186d4D53dBF5a7377dd45376e2D2fc5 Onchain fact: the wrapped REACT (ERC‑20) contract on Ethereum (the address is given in the Tier‑1 material).

No comments to display

Back to top