White Paper

Plasticus (PLS) — White Paper

Status: Verified against the fleet state of record · 22 November 2026 Directory: https://xmarkets.ca/tokens/ Linked website: https://plasticus.ca/ Network: Avalanche C-Chain, according to the XMarkets directory. Verified contract address (Avalanche C-Chain): `0x2E4baa2318fbd86Ad5B1f9Ce9EA124b724Ca696A`.

Executive summary

Plasticus is listed in the XMarkets ecosystem as a token associated with plastics recovery and circular materials. This paper outlines a coherent product and accountability model for that purpose. It does not certify that all described workflows are deployed. The intended users are collectors, processors and buyers.

Problem and product

Sector work is often split across documents, messages and isolated applications. The proposed product gives authorized participants a shared operating record for material origin, collection, sorting, recycling and compliance. Each record should have an owner, timestamp, version history and permission boundary. An event should be considered verified only when the source evidence and reviewer decision can be inspected.

Token utility and access

The directory presents PLS as the sector token. A defensible access model would connect a wallet, verify its balance and apply permissions at the workspace and module level. Holding a token does not by itself convey ownership of an underlying asset, a claim on revenue, or decision rights. Access terms of record: the gate is a HOLD, never a spend — a wallet holds 1 PLS to enter the Plasticus ERP and 1 PLS per module across its 14 modules (15 PLS for the full suite). Held tokens are never spent, transferred or escrowed by the gate, and holding conveys no claim on revenue. Supply, mint authority and burn rules are as deployed in the verified contract above.

Operating workflow

  1. An organization creates an isolated workspace and assigns authorized users.
  2. A user creates or imports a record covering material origin, collection, sorting, recycling and compliance.
  3. A designated reviewer checks supporting evidence and records corrections without erasing the audit trail.
  4. The workspace reports status to the people entitled to see it; external participants see only their permitted subset.
  5. If blockchain anchoring is enabled, publish a hash or batch proof while protecting confidential source documents.

Governance, security and measurements

Publish the entity responsible for the service, treasury and contract upgrades. Separate administrators from reviewers and provide a process for correcting errors and revoking access. Monitor adoption by active organizations, completed workflows, validated evidence and dispute resolution, rather than by token price. Protect personal and commercial data with encryption, retention limits, access logs and incident response. Smart-contract claims should be backed by deployed code and an audit.

Site-specific findings and publication checks

The public directory establishes the sector positioning and linked website. Product features, token economics and rollout dates require issuer confirmation and direct testing before publication. The linked site was visited during this review; its marketing statements are not independent evidence that production workflows are complete.

Before an issuer-approved release, add the canonical token name and verified contract, issuer/legal entity, token supply and allocation, access fee schedule, custody and treasury controls, technical architecture, audit reports, operational status, roadmap with dates, and jurisdiction-specific risk disclosures. No return, liquidity or redemption is promised in this draft.

Sources

  1. XMarkets directory: https://xmarkets.ca/tokens/
  1. Project site: https://plasticus.ca/