Skip to content

Standard library versions for different Simplicity integrations #16

Description

@schoen

Do we have a plan to have different versions of the standard library applicable to the different integrations of Simplicity (Elements, Bitcoin, Unchained)?

Because the underlying jets are different, the needs of developers may be slightly different in each case, and the available jets will be different. In one specific case (jet::total_fee), I believe the type signature of the jet will change. So standard library functions that use affected jets might need different implementations, or might not work in some integrations!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions