Pre-auditThree days of senior audit time for $1,500, credited in full toward your Zealynx audit.3 audit days, credited toward your auditSee how →
Plunid · Smart Contract Security AssessmentPlunid Client Hub

EURP Smart Contracts

Zealynx reviewed Plunid's permissioned EURP token, profile and field management, privileged roles, and deployment scripts. The audit identified 12 findings: two Medium, seven Low, and three Informational. The mitigation review verified eight source-level fixes; two purpose-code findings were superseded by a policy change, and two findings were acknowledged. The review did not verify deployed bytecode, off-chain identity or payout operations, or fiat reserves.

PolygonSoliditySmart Contract Code Review2026-11-18Zealynx methodology
Total findings
12
8 fixed · 2 superseded · 2 acknowledged
Critical
00
High
00
Medium
02
Low + Info
10
02

Scope

9 files
Initial commit
4c37ce69136b
Final commit
469d39681948
Platform
Polygon · Solidity
Methodology
Out of scope
Web portal and external databases, Fiat reserves and reward disbursement, Actual KYC operations, deployment execution, and legal compliance
File
contracts/PlunidAccounts.sol
contracts/FieldManagement.sol
contracts/ProfileManagement.sol
contracts/Eurp.sol
contracts/ERC20Interface.sol
contracts/Migrations.sol
migrations/1_initial_migration.js
migrations/2_deploy_contracts.js
migrations/3_deploy_eurp.js
03

Findings

click any row for the full write-up
04

Review and mitigation

The initial source review covered the frozen audit revision from 9 to 13 November 2026. The mitigation review examined the separate fixes revision through 18 November. The reported statuses describe that source-level review, not a production deployment.

05

Boundaries

Identity checks, confidential records, fiat backing, and actual PURP payments depend on off-chain processes outside the contract audit. The committed contract suite compiled, but three tests still assumed removed purpose-code or earlier allowance behavior: 12 of 15 passed. Focused mitigation checks passed. Integrations need to account for the revised purpose-code policy and event ABI.

06

Security strengths

The design starts profiles in a restricted state, separates activation and currency permission, uses explicit privileged roles and matching votes for superadmin recovery, and limits mint and burn authority to Treasury. These controls were evaluated alongside the findings, and do not establish the security of excluded operations.

07

Team & approval

Lead Auditor
Carlos (Bloqarl)
08

Disclaimer

This audit is not an endorsement and does not constitute investment advice. Zealynx reviewed the codebase at the commits listed in section 02 over the engagement window. Findings are limited to issues identified within that scope and do not preclude the existence of other vulnerabilities. Subsequent code changes are not covered by this report unless the engagement is explicitly extended.

Download PDF (25p)
ZEALYNX SECURITY · published 2026-11-18
12 findings · Solidity