Repository navigation
Releases: ex-money/digital_token
Release list
Digital Token version 2.1.0
Bug Fixes
-
Short name and long name lookups resolve the same token on every OTP release. An ambiguous name resolves by token type (native first), then curated symbol, then ascending token identifier, and
DigitalToken.search/1returns the candidates in that order, winner first. -
DigitalToken.symbol/2returns the curated symbol forETH,BCHandEOSagain. The bundled symbol data is regenerated and keyed to Ethereum Ether, Bitcoin Cash and EOS rather than to layer-two deployments of them.
Enhancements
-
Adds the standard GitHub Actions CI workflow (Elixir 1.17–1.20 across OTP 26–29, with formatting and dialyzer on the lint row).
-
DigitalToken.validate_token/2andDigitalToken.get_token/1document how an ambiguous name resolves, and the README gains a section on ambiguous short names.
Digital Token version 2.0.0
Breaking Changes
- dtif.org has moved to a paywall model requiring several thousand euros a year to access the full registry data. Fortunately they do maintain a publically available extract which is enough to support this library. However even that data is not accessible programmatically. Therefore the data is only updated when a maintainer downloads it manually. As a result, the data is tied to the package release which is not a good long time solution. Like the Localize solution, the next release of digital_token will generate an .etf file of the content we need and store in in R2.
Digital Token version 1.0.0
Bug Fixes
- Fix parsing error on some tokens from the updated registry.
Enhancements
- Use the erlang
:jsonmodule as a candidate JSON decoder if the underlying OTP release supports it (>= OTP 27). This support also requires at leastcldr_utilsversion 2.28.2.
Digital Token version 0.5.0
Enhancements
- Make the JSON library configurable. Like
ex_cldrit will also attempt to use the JSON library configured forex_cldr,ecto,phoenixor if otherwise configuredJasonorPoison.
Digital Token version 0.4.0
Enhancements
- Parse and structure the downloaded digital token registry and digital token symbols at download time rather than compile time. This reduces the compile time significantly.