docs: add Ecosystem section to README#23
Open
LORDBABUINO wants to merge 1 commit intomainfrom
Open
Conversation
LORDBABUINO
force-pushed
the
docs/readme-ecosystem-section
branch
from
947750e to
3d2db53
Compare
Surfaces active integration discussions (Liana #2107, BDK #429), external interest (am-i-exposed, Umbrel/Start9 packaging request), and the Freedom Tech Friday podcast feature, so new visitors and grant reviewers can find traction signals without digging through upstream issue trackers.
LORDBABUINO
force-pushed
the
docs/readme-ecosystem-section
branch
from
3d2db53 to
93ef045
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an
## Ecosystemsection to the top-level README, listing the active integration discussions and external signals that previously lived only in upstream issue trackers and grant drafts.Entries:
Why
New visitors and grant reviewers landing on the README can now see traction signals directly without digging through upstream issue trackers. The section is date-stamped (`Last updated: 2026-04-25`) so staleness is visible.
Maintenance contract
Update this section when state changes meaningfully (issue closed, new external party engages, integration ships) and bump the date stamp at the same time. Not every comment — meaningful state changes only.
Test plan