by Wolf McNally and Christopher Allen
part of the crypto commons technology family
URDemo is an app to demonstrate sending and receiving of URs using URKit
This app is written in Swift using SwiftUI. It demonstrates the use of URKit to send and receive single-part and multi-part Uniform Resources (URs) via QR codes. Multi-part QR codes are generated using Luby Transform code (fountain codes).
Main screen. Either select the scenario for the message you want to send (messages are generated randomly), or tap the button at the bottom to receive a message.
Sending screen. A LifeHash displays a hash of the message being sent for easy recognition on the receiving side. The blue bar beneath the animated QR code shows the segments mixed into the currently displayed part. This is part of the fountain codes technique. The buttons below the QR code can be adjusted to show frames at a higher or lower rate.
You can use the circular arrow button in the upper-right to choose a new message and restart the transmission.
Receiving screen. You're seeing the sending device through the viewfinder. The blue bar beneath the viewfinder lights up in white to signify the complete parts of the message received so far, and also shows in light blue the fragments mixed in to the last received part. The progress bar at the very bottom shows an estimate of the expected completion percent.
You can use the circular arrow button in the upper-right to abort and restart the current receive, or start a new receive after the last one completes.
Proper distance and framing. For optimal transmission, you should try to make the sending QR code fill as much of the viewfinder as possible.
Acknowledgement screen. Appears on successfully receiving a message. The LifeHash displayed on the sending and receiving devices should match.
Explanation of the URDemo iOS application, which demonstrates Blockchain Commons research into transmitting different sizes of UR data, from small single QR codes to large animated fountain codes.
Video of Animated QR codes with test reference data for different sizes of UR data, from small single QR codes to large animated fountain codes.
URDemo is currently under active development and in the late alpha testing phase. It should not be used for production tasks until it has had further testing and auditing.
- Swift 5, iOS 13, and Xcode 11.5
- Open
URDemo.xcodeworkspace, wait for the dependencies to resolve, and build theURDemotarget for your iOS device.
Unless otherwise noted (either in this /README.md or in the file's header comments) the contents of this repository are Copyright © 2020 by Blockchain Commons, LLC, and are licensed under the spdx:BSD-2-Clause Plus Patent License.
In most cases, the authors, copyright, and license for each file reside in header comments in the source code. When it does not, we have attempted to attribute it accurately in the table below.
This table below also establishes provenance (repository of origin, permalink, and commit id) for files included from repositories that are outside of this repo. Contributors to these files are listed in the commit history for each repository, first with changes found in the commit history of this repo, then in changes in the commit history of their repo of their origin.
| File | From | Commit | Authors & Copyright (c) | License |
|---|
To build URDemo you'll need to use the following tools:
- Swift 5, iOS 13, and Xcode 11.5
This URDemo project is either derived from or was inspired by:
URDemo is a project of Blockchain Commons. We are proudly a "not-for-profit" social benefit corporation committed to open source & open development. Our work is funded entirely by donations and collaborative partnerships with people like you. Every contribution will be spent on building open tools, technologies, and techniques that sustain and advance blockchain and internet security infrastructure and promote an open web.
To financially support further development of $projectname and other projects, please consider becoming a Patron of Blockchain Commons through ongoing monthly patronage as a GitHub Sponsor. You can also support Blockchain Commons with bitcoins at our BTCPay Server.
We encourage public contributions through issues and pull requests! Please review CONTRIBUTING.md for details on our development process. All contributions to this repository require a GPG signed Contributor License Agreement.
The best place to talk about Blockchain Commons and its projects is in our GitHub Discussions areas.
Gordian Developer Community. For standards and open-source developers who want to talk about interoperable wallet specifications, please use the Discussions area of the Gordian Developer Community repo. This is where you talk about Gordian specifications such as Gordian Envelope, bc-shamir, Sharded Secret Key Reconstruction, and bc-ur as well as the larger Gordian Architecture, its Principles of independence, privacy, resilience, and openness, and its macro-architectural ideas such as functional partition (including airgapping, the original name of this community).
Blockchain Commons Discussions. For developers, interns, and patrons of Blockchain Commons, please use the discussions area of the Community repo to talk about general Blockchain Commons issues, the intern program, or topics other than those covered by the Gordian Developer Community or the Gordian User Community.### Other Questions & Problems
As an open-source, open-development community, Blockchain Commons does not have the resources to provide direct support of our projects. Please consider the discussions area as a locale where you might get answers to questions. Alternatively, please use this repository's issues feature. Unfortunately, we can not make any promises on response time.
If your company requires support to use our projects, please feel free to contact us directly about options. We may be able to offer you a contract for support from one of our contributors, or we might be able to point you to another entity who can offer the contractual support that you need.
The following people directly contributed to this repository. You can add your name here by getting involved. The first step is learning how to contribute from our CONTRIBUTING.md documentation.
| Name | Role | Github | GPG Fingerprint | |
|---|---|---|---|---|
| Christopher Allen | Principal Architect | @ChristopherA | <[email protected]> | FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED |
| Wolf McNally | Project Lead | @WolfMcNally | <[email protected]> | 9436 52EE 3844 1760 C3DC 3536 4B6C 2FCF 8947 80AE |
We want to keep all of our software safe for everyone. If you have discovered a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner. We are unfortunately not able to offer bug bounties at this time.
We do ask that you offer us good faith and use best efforts not to leak information or harm any user, their data, or our developer community. Please give us a reasonable amount of time to fix the issue before you publish it. Do not defraud our users or us in the process of discovery. We promise not to bring legal action against researchers who point out a problem provided they do their best to follow the these guidelines.
Please report suspected security vulnerabilities in private via email to [email protected] (do not use this email for support). Please do NOT create publicly viewable issues for suspected security vulnerabilities.
The following keys may be used to communicate sensitive information to developers:
| Name | Fingerprint |
|---|---|
| Christopher Allen | FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED |
You can import a key by running the following command with that individual’s fingerprint: gpg --recv-keys "<fingerprint>" Ensure that you put quotes around fingerprints that contain spaces.