This project is supported by the EnAccess Foundation (https://enaccess.org/)
Hardware implementation with generic C version + Arduino + schematics: https://github.com/EnAccess/OpenPAYGO-HW
-
Have a look at the general documentation: https://github.com/EnAccess/OpenPAYGO/blob/master/documentation/general_documentation.pdf
-
The source code of the example implementation into a device (including an example for begginers implemented on Arduino): https://github.com/EnAccess/OpenPAYGO-HW
-
The guide for the example, including a quick test to see if you have implemented the code properly into your system: https://github.com/EnAccess/OpenPAYGO/blob/master/documentation/example_implementation_documentation.pdf
If you have pulled or downloaded this implementation before the official OpenPAYGO Token release on the 10th of October 2019, please make sure to update to the latest version before using in production.
2019-11-15: v2.1 release
- Added documentation about how to allow entry of slightly older tokens on device (unordered token entry)
- Added an example of unordered token entry (with test scenario) on the Python implementation
- Ensured compatibility of the Python code with Python v2.7+ (in addition to Python 3+ already supported).
Note: This version is fully retro-compatible with the v2.0, the tokens themselves do not change. Changes can be implemented on devices that wish to support unordered token entry but are not required. No change is required on servers.
2019-10-10: v2.0 release
- Improved the test suite
- Added an extra example in the implementation documentation
- Bugfix in the example server implementation leading to count not always being updated correctly
- Bugfix in the update of count in the python device simulator
2019-09-27:
- Added signed independent security audit
- Added documentation as PDF
2019-09-06: v2.0 rc1
- Added extended token example implementation
2019-08-28: v2.0 beta
- Fully functional version with all v2.0 features
2019-07-19: v2.0 alpha
- First functional pre-release version
Note: The v1.0 version was only provided to a few partners for a limited beta test and to gather feedback useful to make the v2.0, it is not published here, is not compatible with the v2.0 and should not be used in production.