Repository navigation
Idea: a checked reference for takeaway-order inquiries #19
PerchAnton
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I maintain RefMint, a TypeScript library for public references with a type prefix and a Bech32m checksum.
Use case
OrderRestro handles orders, kitchen displays and local-network operation. For a later receipt inquiry, a customer could read a public reference while staff look up the original order locally.
Proposal
Discuss an optional RefMint receipt reference and input validator, leaving table numbers, kitchen ticket numbers and payment identifiers unchanged. This needs a receipt-length and operator-workflow check before implementation.
Trade-offs and current status
The first alpha is available as a GitHub package archive, not on npm. It targets Node 22+ and Web Crypto browsers, with no runtime dependencies. The format may change and adds six checksum characters. A checksum is not authorization. Keeping the current reference format is a valid alternative.
I checked the released package (generation, formatting, parsing and typo rejection); I have not tested an integration here or measured a benefit for your users. Would this optional workflow be useful, or is the current approach sufficient?
All reactions