Repository navigation
fix: remove unresolved Private DvP placeholder #203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
rymnc
merged 2 commits into
ethsystems:master
from
arunimshukla:fix/remove-private-dvp-placeholder
Oct 13, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think we can link to private stablecoins here
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’d use Private Repo instead of Private Stablecoins here.
private-repo.md is explicitly tagged
primary_domain: Trading.private-stablecoins.mdis taggedprimary_domain: Payments. So the repo’s own taxonomy already puts Repo in the exact domain this page represents.Private Repo is structurally closer to DvP because repo settlement is an asset-versus-cash transaction and the page already points to atomic settlement and DvP patterns.
Private Stablecoins are better understood as the cash part of a trade, not the trade use case itself. The stablecoin page supports settlement across multiple domains, especially Payments.
The Trading domain already has a separate “Related use cases” section. Stablecoins fit better there as supporting settlement infrastructure, while Repo fits naturally as a primary Trading use case.
Private Stablecoins are already a primary use case under Payments. Using it again as the main Trading entry weakens the taxonomy; using Private Repo keeps each domain anchored to a use case that actually belongs there.
If that makes sense, I’ll update the PR to link
Private Repohere.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree Repo seems to fit better than Stablecoins here. Note, however, that Private Stocks and Private Commodities are also
primary_domain: Trading, so all three should be listed rather than just Repo.Having said that, there's the underlying question of how accurate current tags are. There may be some drift wrt existing knowledge and understanding. In particular, "Private DvP" already appears in the map as
Approach: Atomic DvP Settlement(approaches/approach-dvp-atomic-settlement.md).MAybe an
Approachessection (like governance.md and identity-compliance.md) linking that approach and Private Trade Settlement can be interesting.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. I checked the current front matter and Trading has three primary use cases today:
so I’ll update the section to include all three.
I also checked the wider mapping and there does appear to be some taxonomy drift. Five use cases currently declare
secondary_domain: Trading, Private FX, Private Read, Private Messaging, Private Corporate Bonds, and Private Oracles, whiledomains/trading.mdcurrently lists only Private Bonds under its secondary section.private-bonds.mditself does not declare Trading as a secondary domain.I’ll keep this PR scoped to two concrete changes:
Align the primary use-case list with the existing frontmatter.
Add an Approaches section linking Atomic DvP Settlement and Private Trade Settlement, following the structure already used in
governance.mdandidentity-compliance.md.I can take the broader domain/use-case mapping as a separate follow-up once this is merged, rather than mixing a taxonomy cleanup into the current fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay, sounds good!