Idea: Separate reference in the web order-support flow

[PerchAnton]

I maintain RefMint, a TypeScript library for public references with type prefixes and a Bech32m checksum.

Use case

An attendee asking about an order could read a public inquiry reference without exposing the ticket's admission credential.

Proposed change

Try a separate reference in the web order-support flow; preserve QR admission secrets, order numbering and server access rules.

Alternatives

Keeping the current identifiers and lookup flow, or using a simple local alias, are valid alternatives. The extra field is worthwhile only if manual lookup is a real need.

Compatibility and validation

v0.1.0-alpha.1 is a GitHub package archive, not an npm release. It targets Node 22+ and Web Crypto browsers, with no runtime dependencies. The format may change; the checksum adds six characters and does not provide authorization.

I checked generation, formatting, parsing and typo rejection in the released package. I have not tested an integration here or measured benefits for your users. Would this optional workflow be useful?