Skip to content
Quantix Security Labs

Quarrystone Payments

Merchant payments and subscriptions on Sui.

Merchants accept payments in stablecoins through shared invoice objects. Subscriptions are pre-authorised with capability objects that let a merchant pull bounded amounts per period.

Ecosystem
SUISui
Category
Payments
Languages
Move (Sui)
Launched
Feb 2026
81.9AModerate risk

Grade A · Moderate risk

Sound posture; some improvements recommended.

+0.9 since Feb 2026 · +0.9 since Jul 2026

Quantix Protocol Research · as of 24 Oct 2026 · About this data

Risk Index

How the score is built

Six weighted components, each scored 0–100 where higher means less risk. Points are the component value multiplied by its weight; the gap is what the component costs against a perfect score.
ComponentWeightValuePointsGap
Code Security30%8425.2−4.8
Operational Security20%8016.0−4.0
Governance Risk15%8212.3−2.7
Economic Security15%8412.6−2.4
Infrastructure Resilience10%787.8−2.2
Transparency10%808.0−2.0
Quantix Risk Index100%81.9−18.1
CodeOperationalGovernanceEconomicInfrastructureTransparencyQuarrystone Payments, Code: 84Quarrystone Payments, Operational: 80Quarrystone Payments, Governance: 82Quarrystone Payments, Economic: 84Quarrystone Payments, Infrastructure: 78Quarrystone Payments, Transparency: 80
Risk Index components: Quarrystone Payments Code 84, Operational 80, Governance 82, Economic 84, Infrastructure 78, Transparency 80
ComponentQuarrystone Payments
Code84
Operational80
Governance82
Economic84
Infrastructure78
Transparency80

Grade scale

  1. AAA90–100
  2. AA85–89.9
  3. A80–84.9
  4. BBB75–79.9
  5. BB70–74.9
  6. B65–69.9
  7. CCC60–64.9
  8. CC55–59.9
  9. C50–54.9
  10. D0–49.9

Score history

9 monthly snapshots

Each point is the Risk Index computed from that month’s component values. Markers below the chart show the events that moved a component; the history starts at launch in Feb 2026.
Quarrystone Payments Quantix Risk Index by month
PeriodQuantix Risk Index
Feb ’2681.0
Mar ’2681.0
Apr ’2681.0
May ’2681.0
Jun ’2681.0
Jul ’2681.0
Aug ’2681.9
Sep ’2681.9
Oct ’2681.9
  1. 11 Aug 2026

    Upgrade

    Subscription caps hardened

    Per-period caps enforced inside the capability.

    • Code Security+3

Risk factors

What keeps the score from being higher, most severe first.
  • MediumCode SecurityProfile analysis

    Missing version gating

    After an upgrade, old package functions may still mutate shared objects unless versions are checked.

  • LowInfrastructure ResilienceProfile analysis

    Shared-object contention

    High-volume merchants share invoice objects, which can delay settlement under load.

Recommendations

Each recommendation raises one component to a target value. The score effect is recomputed with the Risk Index model, holding every other component fixed.
  • Code Security: 84 → 89

    Version-gate shared objects

    Store a version field and reject calls from older packages.

    +1.5

    → 83.4

  • Infrastructure Resilience: 78 → 84

    Per-merchant invoice objects

    Shard invoices to reduce contention.

    +0.6

    → 82.5

Analysis

Contract, governance and operations

Contract analysis

Source
Verified
Upgradeability
Package UpgradeCap held by a multisig
Administrative control
Merchant registry admin (multisig)
Enforced delay
None identified
External dependencies
Stablecoin issuers; Merchant integrations
  • PassSource published. Move packages published.
  • PassPull-payment limits. Subscriptions bounded per period by capability objects.
  • CautionVersion checks. Shared objects do not yet check package version after upgrades.

Governance exposure

Low

Package upgrades and registry admin through a multisig.

Operational resilience

Strong

Merchants manage their own capabilities; revocation is immediate.

Monitoring

Monitoring history

1 recorded security events for Quarrystone Payments, most recent first.
  1. 2 Sept 2026InformationalPackage upgraded to version 4 with approved digestProxy Upgrade · subscription moduleResolved

Research assessment

No Quantix assessment of Quarrystone Payments has been published. Its security findings are represented by the contract-analysis signals above: 0 failed and 1 cautionary.

Continue with

Comparable protocols

    Compare side by side

    Research

    Relevant research

    Publications on the risks that matter most for a payments protocol on Sui.

    Architecture

    System components

    invoice module
    Shared invoice objects and settlement
    subscription module
    Pull-payment capabilities with limits
    merchant registry
    Merchant identity and fee settings

    Turn risk factors into a remediation plan.

    A research assessment traces each weakness to code, configuration or process, and verifies the fix before the score moves.