NUT for Discreet Log Contract support #122

Open
opened 2024-05-20 02:02:34 +00:00 by conduition · 1 comment
conduition commented 2024-05-20 02:02:34 +00:00 (Migrated from github.com)

Today I published a first-draft of an idea for discreet log contract integration for Chaumian Ecash mints.

https://conduition.io/cryptography/ecash-dlc/ [Pull request link]

Before I go to the trouble of writing up a NUT submission, is this even the right place for such an idea? Or would DLCs be outside the scope of Cashu?

Naturally I don't think DLC support should be mandatory for any cashu implementation. But DLCs could be a highly desirable feature for ECash... something which might incentivize non ecash users to take the plunge. DLCs could offer a sort of programmable functionality on top of Ecash, outside of simple unconditional payments, without adding much complexity to the mint itself.

Today I published a first-draft of an idea for [discreet log contract](https://bitcoinops.org/en/topics/discreet-log-contracts/) integration for Chaumian Ecash mints. https://conduition.io/cryptography/ecash-dlc/ [[Pull request link](https://github.com/conduition/conduition.io/pull/6)] Before I go to the trouble of writing up a NUT submission, is this even the right place for such an idea? Or would DLCs be outside the scope of Cashu? Naturally I don't think DLC support should be mandatory for any cashu implementation. But DLCs could be a highly desirable feature for ECash... something which might incentivize non ecash users to take the plunge. DLCs could offer a sort of programmable functionality on top of Ecash, outside of simple unconditional payments, without adding much complexity to the mint itself.
AngusP commented 2024-05-20 14:55:55 +00:00 (Migrated from github.com)

There are already NUTs for DLEQ Proofs, P2PK and HTLCs, so yeah I think it's nut-worthy and fine to have optional specs

There are already NUTs for [DLEQ Proofs](https://github.com/cashubtc/nuts/blob/main/12.md), [P2PK](https://github.com/cashubtc/nuts/blob/main/11.md) and [HTLCs](https://github.com/cashubtc/nuts/blob/main/14.md), so yeah I think it's nut-worthy and fine to have optional specs
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo-admin/nuts#122
No description provided.