Skip to content

Releases: 3loop/loop-decoder

@3loop/transaction-interpreter@0.4.0

25 Aug 16:36
3eb5ee2
Compare
Choose a tag to compare

Minor Changes

  • 797da0f: Add more default interpreters and std functions
  • d1579f1: Add default interpreters for erc20, erc721 and erc1155 contracts

Patch Changes

  • Updated dependencies [1e55653]
  • Updated dependencies [68e2034]
  • Updated dependencies [102fda3]
    • @3loop/transaction-decoder@0.14.0

@3loop/transaction-decoder@0.14.0

25 Aug 16:36
3eb5ee2
Compare
Choose a tag to compare

Minor Changes

  • 1e55653: Add all interacted addresses metadata to decoded transaction
  • 68e2034: Use managed runtime inside vanilla api and allow passing a custom log level
  • 102fda3: Fix decoding of logs that do not have parameters or if we could not decode their params

@3loop/transaction-interpreter@0.3.0

21 Jul 18:57
5696972
Compare
Choose a tag to compare

Minor Changes

  • 215e045: Add a common data type to return it from all interpreters. Additionally added a couple of more examples of interpretators and a fallback interpretator.

Patch Changes

  • Updated dependencies [32af229]
    • @3loop/transaction-decoder@0.13.0

@3loop/transaction-decoder@0.13.0

21 Jul 18:57
5696972
Compare
Choose a tag to compare

Minor Changes

  • 32af229: Separate ABI resolvers into fragment and full address abi

@3loop/transaction-decoder@0.12.0

26 Jun 17:30
1bdd716
Compare
Choose a tag to compare

Minor Changes

  • fff83bc: Modify set in AbiStore to accept 2 parameters, key and value

@3loop/transaction-interpreter@0.2.1

25 Jun 18:31
7d1f663
Compare
Choose a tag to compare

Patch Changes

  • af5093d: Add otel tracing spans
  • Updated dependencies [d169992]
  • Updated dependencies [af5093d]
    • @3loop/transaction-decoder@0.11.0

@3loop/transaction-decoder@0.11.0

25 Jun 18:31
7d1f663
Compare
Choose a tag to compare

Minor Changes

  • d169992: Refactor stores to call set when the data is not found in strategies. This introduces new types for store values, to
    be able to differentiate between a missing value, and one that was never requested.

      1. Success - The data is found successfully in the store
      1. NotFound - The data is found in the store, but is missing the value
      1. MetaEmpty - The contract metadata is not found in the store

    This change requires the users of the library to persist the NotFound state. Having the NotFound state allows us
    to skip the strategy lookup, which is one of the most expensive operations when decoding transactions.

    We suggest to keep a timestamp for the NotFound state, and invalidate it after a certain period of time. This will
    ensure that the strategy lookup is not skipped indefinitely. Separately, users can upload their own data to the store.

Patch Changes

@3loop/transaction-interpreter@0.2.0

21 Jun 18:05
fd92e88
Compare
Choose a tag to compare

Minor Changes

  • 67b2286: Make interpreter layer scoped

@3loop/transaction-interpreter@0.1.0

19 Jun 16:23
d92cdd4
Compare
Choose a tag to compare

Minor Changes

  • 0589145: The initial release of the transaction interpreter with QuickJS.

Patch Changes

  • Updated dependencies [0589145]
    • @3loop/transaction-decoder@0.10.0

@3loop/transaction-decoder@0.10.0

19 Jun 16:23
d92cdd4
Compare
Choose a tag to compare

Minor Changes

  • 0589145: The initial release of the transaction interpreter with QuickJS.