Skip to content

Remove the patent strategy doc, keep the grant it carried - #60

Merged
blocksifrdev merged 1 commit into
mainfrom
docs/patent-grant-to-notice
Sep 15, 2026
Merged

blocksifrdev merged 1 commit into
mainfrom
docs/patent-grant-to-notice

Conversation

@blocksifrdev

Copy link
Copy Markdown
Collaborator

docs/patent-strategy.md is gone. It opened by naming two methods as patent-pending — a poor first impression for a protocol asking people to implement it — and the strategy framing around it served BlockSiFr rather than the reader.

But over half of it wasn't strategy. It carried an explicit royalty-free grant and three long-term commitments, and those answer the first question any adopter's counsel asks: will we be sued for implementing this?

Deleting the file wholesale would have removed the assurance along with the disclosure — and a withdrawn promise reads worse than one never made, particularly in a public repo where the deletion shows up in the diff.

So the grant moved to NOTICE, in BlockSiFr's own words rather than rewritten:

  • The Apache 2.0 express patent grant covers implementing the spec — "if you implement what's in the spec, you're covered"
  • The five royalty-free permissions (implement the protocol, use the reference aggregation algorithm commercially, build competing Trust Authorities, deploy internally, fork the reference implementations)
  • The three commitments: never encumber the core spec, provide standards-body grants, flag new patent-pending mechanisms through the RFC process before they enter the normative spec

Also fixes two relative links left broken by the earlier docs move: protocol/spec.md../MVP.md and docs/README.md../COMMERCIAL_BOUNDARY.md.

🤖 Generated with Claude Code

docs/patent-strategy.md is gone. It opened by naming two methods as
patent-pending, which is a poor first impression for a protocol asking
people to implement it, and the strategy framing around it served
BlockSiFr rather than the reader.

More than half of it was not strategy though. It carried an explicit
royalty-free grant and three long-term commitments, and those answer the
first question any adopter's counsel asks: will we be sued for
implementing this. Deleting the file wholesale would have removed the
assurance along with the disclosure, and a withdrawn promise reads worse
than one never made — particularly in a public repository where the
deletion is visible in the diff.

So the grant moved to NOTICE, in BlockSiFr's own words rather than
rewritten: the Apache 2.0 express patent grant covers implementing the
spec, the five royalty-free permissions, and the commitments never to
encumber the core specification, to provide standards-body grants, and to
flag new patent-pending mechanisms through the RFC process before they
enter the normative spec.

Also fixes two relative links left broken by the earlier docs move:
protocol/spec.md pointed at ../MVP.md and docs/README.md at
../COMMERCIAL_BOUNDARY.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@blocksifrdev
blocksifrdev merged commit 4a850e1 into main Sep 15, 2026
4 checks passed
@blocksifrdev
blocksifrdev deleted the docs/patent-grant-to-notice branch September 15, 2026 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant