Skip to content

Spec does not requires lengths to be canonical #60

Description

@stevenroose

The Crypto-Conditions spec does not mention anything about the used OER encoding to be either Basic OER or Canonical OER.

So these tests should be left out or the reference implementation:
https://github.com/interledgerjs/five-bells-condition/blob/master/test/fulfillmentSpec.js#L135

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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