Skip to content
Quantix Security Labs

Quarrystone Payments research programme.

Merchant payments and pull-payment subscriptions in Sui Move. Research will focus on capability objects and shared invoice handling.
ScheduledOpens 16 November 2026

Programme scheduled. Opens on 16 November 2026, after the package upgrade that introduces subscription limits.

Programme overview

Protocol category
Payments
Ecosystems in scope
Sui
In-scope components
3 (3 contracts)
Languages
Move (Sui)

Focus areas

Where research is most wanted.

  • 01

    Capability leakage

  • 02

    Shared-object ordering

  • 03

    Subscription limit enforcement

  • 04

    Package upgrade version checks

Scope

In scope.

Identifiers belong to the programme’s research deployment. Test only on a local fork or the programme’s test environment.
ComponentTypeIdentifierNotes
invoice moduleSuiSmart contracts0x56c505d5c31609670a032acc93de826ceadcd7fa5b47511708aa1934d8137c0bShared invoice objects and settlement
subscription moduleSuiSmart contracts0xb23edc7459dc7410bfb6ad395d2fc233527d27f06a363f073a93f7067cc91cbdPull-payment capabilities with limits
merchant registrySuiSmart contracts0x949397a91f973a46a57de689784486da54943f3d740428e5089dbeeb3844cb2dMerchant identity and fee settings

Out of scope

  • Sui framework packages
  • Wallet applications
  • Issues already reported in the research assessment
  • Findings that require compromised keys or privileged access the attacker could not obtain

Severity

How findings in this programme are rated.

Examples specific to Quarrystone Payments. The full criteria are in the severity guidelines.
  • Critical
    • Pulling funds beyond a subscription limit
  • High
    • Settling an invoice to the wrong merchant
  • Medium
    • Blocking settlement of shared invoices
  • Low
    • Missing events on merchant updates

Rules of engagement

Research within these rules.

  1. 01Test only against a local fork or the programme’s test deployment. Never interact with production systems or other users’ funds.
  2. 02Do not run denial-of-service, spam or social-engineering tests, and do not access data that is not yours.
  3. 03Report privately through the submission form. Keep details confidential until a disclosure date is agreed.
  4. 04One finding per submission, with a reproducible proof of concept where code is involved.
  5. 05Issues already listed in the protocol’s research assessment as acknowledged or open are not eligible for recognition.

These rules, together with the disclosure policy, define what the programme authorises. Testing outside them is not authorised.

Recognition

Validated findings receive recognition. This programme offers no monetary reward.

  • Acknowledgement in the report

    Validated findings are credited in the protocol’s research assessment or advisory, by name or handle, with your consent.

  • Recognition ledger

    Each validated finding becomes a ledger entry recording programme, vulnerability class, severity and validation date. Entries are published only with the researcher’s consent.

  • Researcher standing

    Standing reflects validated findings over time: Contributor after the first, Recognised after three, Distinguished after a validated critical or high finding with a published write-up.

  • Research collaboration

    Researchers with standing are invited to closed challenge rounds and to co-author research on the vulnerability classes they reported.

This programme is not accepting submissions yet.

Opens on 16 November 2026, after the package upgrade that introduces subscription limits.