Skip to content

[requires fork] Elements should have a jet to access input asset ID for reissuances #327

@apoelstra

Description

@apoelstra

Elements has some annying logic for reissuances in which you are required to spend a confidential output containing a reissuance token, but you must reveal the blinding factor, in order to do a reissuance.

This is crazy but requires a hardfork to fix.

Meanwhile, for contracts to assert on the input type of a reissuance token, they need to reimplement the unblinding logic in Simplicity. (Or hack the crypto by doing ugly/inflexible/poorly-supported-by-wallets things like enforcing that an output asset have exactly the same commitment as an input asset.)

Anyway we ought to have a jet to do this work. Unsure where the best place to post "jet wishlist" issues is.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions