| Internet-Draft | draft-singh-apex-psi-05 | July 2026 |
| Singh | Expires 20 January 2027 | [Page] |
PSI-05 defines the royalty schedule that MAY be levied by a publishing foundation for commercial, litigation, regulatory, or AI-training reuse of PSI public ledger data above a threshold defined by the foundation's charter. It establishes a flat-rate per-row fee schedule, exemption categories, and an audit protocol.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 20 January 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.¶
Public ledgers under PSI-04 are free to read and cite. This document defines a royalty framework for commercial reuse tiers, ensuring the publishing foundation can sustain operations.¶
Tier | Annual Row Threshold | Per-Row Fee (AUD) -----+----------------------+------------------ A | <= 1,000 | Free B | 1,001 - 100,000 | $0.001 C | > 100,000 | $0.0001 (negotiable)¶
The following uses are always royalty-free: - Personal research and academic citation. - Journalism and public-interest reporting. - Regulatory compliance audits.¶
Any user may request a signed royalty statement from the foundation. The statement includes total rows served per entity and the fee calculation.¶
Royalty enforcement depends on honest self-reporting until a regulatory framework mandates audit.¶
None.¶
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997. [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017. [RFC8785] Rundgren, A., Jordan, B., and S. Erdtman, "JSON Canonicalization Scheme (JCS)", RFC 8785, DOI 10.17487/RFC8785, June 2020. Author's Address Kawaljeet Singh Apex Intelligence Empire Balaclava, Victoria, Australia Email: kawaljeet.singh3008@gmail.com URI: https://apex-infrastructure.com¶