Add TKQR1: Animated-QR Air-Gap Transport for Arbitrary Payloads#178
Open
RexStarBSV wants to merge 1 commit into
Open
Add TKQR1: Animated-QR Air-Gap Transport for Arbitrary Payloads#178RexStarBSV wants to merge 1 commit into
RexStarBSV wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request:
Proposes a new standard by creating a new markdown file in the appropriate directory and requests discussion and assignment of a BRC number
Summary
This proposes TKQR1, a text framing that carries an arbitrary byte string across an optical air gap as a sequence of QR codes and reassembles it with integrity and set-consistency checks. Each frame is one line of US-ASCII: a fixed prefix, a 64-bit truncated SHA-256 payload tag, a sequence number, a frame total, and a base64url slice of the payload. The shared tag binds every frame to one payload, so a collector rejects frames from a different or stale stream, refuses to emit until the set is complete, and re-verifies the full payload hash before returning bytes. BSV currently has no standard for animated-QR transport; the closest prior art is BC-UR on BTC, which shares no wire format. The spec is grounded in a working reference implementation, two byte-compatible ports validated against a shared vector file, and is written so a second implementer can build an interoperable version from the Specification and Test Vectors alone.
Validation