Skip to content

Revise ⚡ to Case Studies > Shared account #618

Closed

Description

@pavlenex
No description provided.

Activity

  1. added this to the Milestone 12 milestone on Jan 10, 2022
  2. sbddesign commented on Jan 12, 2022

    @sbddesign
    Collaborator

    Perhaps this page needs Lightning content?

    A common real-world use case for shared accounts are couples managing their monthly spending, with both parties being able to spend from the account ... The other person does not need to co-sign every transaction, but we might want a spending limit, above which both parties need to approve the transaction.

    So you could imagine a situation where the two people can make small daily purchases over Lightning on their own, but need to consult each other before making a larger payment.

    I'm not sure about having more than one private key responsible for one side of a Lightning channel. (Would it work? Has it been implemented?)

    Is this the kind of content we should save for a later date?

  3. GBKS commented on Jan 13, 2022

    @GBKS
    Contributor

    I don't think multi-sig on Lightning is possible, is it? @johnsBeharry do you maybe know?

  4. sbddesign commented on Jan 13, 2022

    @sbddesign
    Collaborator

    I think it's absolutely possible in a theoretical sense. Lightning signer lists "multi-party signing" in their project roadmap. But just being theoretically possible doesn't mean it's been implemented yet.

  5. moneyball commented on Jan 14, 2022

    @moneyball
    Contributor

    Once LN is upgraded to support taproot (Schnorr), then multi-sig will be possible in the sense that the tapscript used won't know if the single signature is 1 or more keys. If something like musig2 is used then N-of-N could be supported and something like FROST is used then K-of-N could be supported. Perhaps this is possible within a year...we'll see.

  6. GBKS commented on Jan 25, 2022

    @GBKS
    Contributor

    Created a PR for this with a single note that multi-key on Lightning is still in development. See #632.

  7. Repository owner moved this from Todo 📝 to Done ✅ in Bitcoin Design Guide Roadmap 🎨🎯on Jan 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CopyTask is about improving text.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions