ttp-protocol/NOTICE at main · BlockSiFr/ttp-protocol · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
Trust Transfer Protocol (TTP) and PCTR
Copyright 2026 BlockSiFr

This product includes software developed at BlockSiFr (https://blocksifr.com).

Licensed under the Apache License, Version 2.0. The full, unmodified license text
is in LICENSE.

BlockSiFr's commercial offerings — managed enforcement, hosted control plane,
KMS/HSM signing, enterprise integrations and support — are separate products built
on this protocol. They are not covered by, and place no additional conditions on,
the Apache 2.0 grant above. See docs/COMMERCIAL_BOUNDARY.md.

"BlockSiFr", "TTP" and "PCTR" are trademarks of BlockSiFr. Trademark use is
governed by docs/TRADEMARKS.md and, per section 6 of the License, no trademark
rights are granted by the License itself.

--------------------------------------------------------------------------------
PATENT GRANT AND IMPLEMENTATION ASSURANCE
--------------------------------------------------------------------------------

TTP is released under the Apache License 2.0 and is intended to remain a
permanently open protocol. BlockSiFr's commercial interests are in managed
services and enterprise tooling built on top of the protocol -- not in
controlling the protocol itself.

The Apache 2.0 license's express patent grant covers any patents BlockSiFr
holds that are necessarily infringed by implementing the protocol
specification as published in this repository.

In plain language: if you implement what's in the spec, you're covered.

You may, royalty-free:

  - Implement the TTP protocol as described in the specification.
  - Use the reference aggregation algorithm from protocol/aggregation-spec.md
    in any product, commercial or otherwise.
  - Build competing Trust Authority services, SDKs, issuers, or verifiers that
    conform to the protocol.
  - Deploy TTP for internal enterprise use without paying BlockSiFr anything.
  - Fork and modify the reference implementations under Apache 2.0.

BlockSiFr commits that:

  1. The core TTP specification will never be made patent-encumbered in a way
     that blocks royalty-free implementation.

  2. If TTP is submitted to a standards body (IETF, W3C, etc.), BlockSiFr will
     provide the patent grants required by that body's IP policy.

  3. Any protocol change that introduces a new patent-pending mechanism will be
     clearly flagged in the RFC process, and the patent grant will be updated
     before the change is accepted into the normative specification.

None of BlockSiFr's commercial offerings gate access to the open protocol.
Alternative Trust Authority implementations are possible and encouraged.

For questions about IP or licensing: hello@blocksifr.com