@cardano-foundation/ledgerjs-hw-app-cardano
Advanced tools
Changelog
3.2.0 - [May 24th 2021]
Added support for signing pool registration certificates as operator, support for pool retirement certificates within the signTransaction()
call and added a new call for operational certificate signing - signOperationalCertificate()
.
TransactionSigningMode.POOL_REGISTRATION_AS_OPERATOR
to allow signing pool registration as operatorCertificateType.STAKE_POOL_RETIREMENT
signOperationalCertificate()
callPoolRegistrationParams.poolKey
has been changed from a string
to PoolKey
in order to support pool operator signing - poolKey
can now also be sent as a pathPoolRegistrationParams.rewardAccount
has been changed from a string
to PoolRewardAccount
in order to support pool operator signing - rewardAccount
can now also be sent as pathAssetGroup.tokens
and TxOutput.tokenBundle
are required to be in CBOR canonical orderChangelog
3.1.0 - [May 11th 2021]
Added support for Catalyst voting registration metadata creation within the signTransaction()
call, introduced in Ledger Cardano app version 2.3.2.
signTransaction()
call ttl
and validityIntervalStart
parameter to allow zero valueAddressParamsReward
now requires staking key path as the stakingPath
property instead of spendingPath
(which was misleading)Changelog
3.0.0 - [April 13th 2021]
Major release. Switched from flow to TypeScript.
src/Ada.ts
changes in https://github.com/vacuumlabs/ledgerjs-cardano-shelley/pull/61)AddressTypeNibble
enum renamed to AddressType
derive/showAddress
now take network
as an explicit parameter instead of networkIdOrProtocolMagic
field in AddressParams
Str
(e.g. feeStr
) are now without the suffix (i.e. fee
) and take a "bigint-like" argument which can be Number
(if it is small enough, i.e. <= Number.MAX_SAFE_INTEGER
), string, or native BigInt
. Non-native bigint implementations are not supported and should be converted to strings){type: SomeType.Variant, params: SomeTypeVariantParams}
typing. This unified previously mixed tagging with sometimes arbitrarily variant fields into the parent type. As part of this change
destination
specification.
DestinationType.ThirdParty
or DestinationType.DeviceOwned
to clarify what the device should signAddress
param typeAddress
is now tagged enum across different address types (Byron, Base, Enterprise, Pointer, Reward). Reward address still uses spendingPath
instead of stakingPath
to denote that this key can be used to spend funds*Request
/*Response
nomenclature{version, compatibility}
instead of version
where compatibility
describes overall set of features we support for the device. It should be responsibility of API users to check compatibility.isCompatible
flag and urge users to upgrade device to compatibility.recommendedVersion
if the device is not compatible.ErrorBase
from errors
sub-package. API now distinguishes between these error types
InvalidData
- you passed some wrong data to the API. We will not even try to communicate with the deviceDeviceUnsupported
- thrown when trying to use API with unsupported Ledger app version (or when using features not yet available for the app version)DeviceStatusError
- thrown when device rejects operation for some reason. Common reasons are found in DeviceStatusCodes
mapping.Changelog
2.2.0 - [February 8th 2021]
Works with Ledger Cardano app 2.2.0 and is backwards compatible with older versions down to 2.0.4/2.0.5*. Older versions of this js library do not support Ledger Cardano app 2.2.0, hence an update to this version of the library is required before Ledger Cardano app 2.2.0 is released.
Changelog
2.1.0 - [December 11th 2020]
Works with Ledger Cardano app 2.1.0 and is backwards compatible with 2.0.4/2.0.5 as well*. Older versions of this library do not support Ledger Cardano app 2.1.0, therefore an update to this version of the library is required before Ledger Cardano app 2.1.0 is released.
Changelog
[2.0.0] - [August 18th 2020]
First release with Shelley-era support, works with Ledger Cardano app version 2.0.4 (Nano S) and 2.0.5 (Nano X). Older versions of this library no longer work with the Cardano blockchain.
* backwards compatibility refers only to features supported by the respective app versions, unsupported features result in an error being thrown.