Skip to content

Conversation

@0xakk0r0kamui
Copy link
Contributor

What are you adding?

  • Vendor/Protocol
  • Enterprise Use Case
  • Update to existing content
  • Other

Description

docs: update ERC-7573 DvP pattern with clearer explanations and operational detail

Checklist

  • I've checked this doesn't duplicate existing content
  • All links work
  • Info is accurate

- Asset side and payment side live on different networks (L1/L2 or sidechains).
avoid-when:
- You rely on HTLC timeouts or manual reconciliation.
- Both sides already settle on the same network with simple on-chain transfers.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here can be added:

  • You're searching for a production-ready solution (EIP not yet recommended)
  • You're searching for a fully trustless solution

- Asset side and payment side live on different networks (L1/L2 or sidechains).
avoid-when:
- You rely on HTLC timeouts or manual reconciliation.
- Both sides already settle on the same network with simple on-chain transfers.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here can be added:

  • You're searching for a production-ready solution (EIP not yet recommended)
  • You're searching for a fully trustless solution

maturity: pilot
works-best-when:
- Asset and cash legs live on different networks (L1/L2).
- Asset side and payment side live on different networks (L1/L2 or sidechains).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

leg is the term used in traditional finance; best if you can revert this change to be consistent. Also best to avoid the sidechain scenario.

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.

2 participants