-
Notifications
You must be signed in to change notification settings - Fork 3
Roadmap
Adrian Boros edited this page Nov 29, 2024
·
4 revisions
This document will address the roadmap and release timeline for the PHP SDK library for Open Payments
Open Payments Php Library will follow the typescript implementation of the Interledger Open Payments library
We target the first release of the library by the end of the 2024 year.
- add Open API specs + generated code
- add http signature functionality
- add client and service to work with wallet server
- add Authenticated client logic
- add services and tests to implement Open Payments standard
| Milestone | Status | Target Due Date |
|---|---|---|
| Open API specs + generated Open API code | completed | |
| Unauthenticated Client read wallet server addresses | completed | |
| integrate http signature | completed | Nov 29 2024 |
| Authenticated Client setup | completed | Nov 29 2024 |
| Grant Service | completed | Nov 29 2024 |
| Token Service | TO DO | Dec 6 2024 |
| Incoming Payment Service | TO DO | Dec 6 2024 |
| Quote Service | TO DO | Dec 13 2024 |
| Outgoing Payment Service | TO DO | Dec 13 2024 |
- PHP 8.3+
- Sodium extension
- There are differences between nodejs and php in working with keys
- Node.js uses the crypto library and generates 32-byte private keys, which are essentially the seed for the Ed25519 algorithm.
- PHP's Sodium library expects a 64-byte private key, which includes:
- A 32-byte seed (private key).
- A 32-byte public key concatenated to the seed.
- The signature generated by sodium_crypto_sign_detached() in PHP is valid only if the private key is correctly constructed and compatible with the public key expected by Node.js.
- Open Payments Php 1.0.0 - target release Dec 20 2024
- Adrian Boros