Yeah we didn't optimize for size *at all* yet. Token encoding is purely client-side, cashuA... is base64, cashuB... will be binary.

Btw, you're the first person I've ever seen who managed to get a triple-nut token scanned. Since the problem can't be solved generally, the real solution is animated fountain QR codes.