v.11.2.0

• Added ability for wallets to create verifiable presentations (proofs) from identities and accounts.
  The entrypoint is VerificationRequestV1. This change does not include audit.
• Removed checked exception from AtomicStatement.canBeProvedBy()
• AtomicStatements now implement equals() and hashCode()
• Hash is now fully JSON and CBOR serializable

v.11.2.0-alpha.2

Update the version to 11.2.0-alpha.2

v.11.2.0-alpha.1

Update the version to 11.2.0-alpha.1

v.11.1.0

• Made TokenOperations deserializable from CBOR.
  TokenUpdate.builder().operationsSerialized() can be used for deserialization
• Added TaggedTokenHolderAccount.getAddress() returning the address in a convenient form

v.11.0.2

• Fixed always empty tokens in AccountInfo

v.11.0.1

• Made Android package compatible with 16 KB alignment requirement

v.11.0.0

• Support for Protocol 9
• Added ProtocolVersion.V9 corresponding to Protocol version 9
• Added tokens field to AccountInfo, containing list of related protocol level tokens
• Added new account transaction, TokenUpdate, used to execute protocol level tokens operations
• Added TokenOperation interface for protocol level tokens operations
• Added TransferTokenOperation implementing protocol level token transfer
• Added protocol level token transfer example, see SendTokenTransfer in concordium-sdk-examples
• Added tokenUpdate result to AccountTransactionDetails
• Added createPltUpdate authorization to AuthorizationsV1
• Added RejectReasonTokenUpdateTransactionFailed and RejectReasonNotExistentTokenId transaction reject reasons
• Added CborMapper singleton providing Jackson CBOR object mapper
• Fixed having the Lombok library transitive

v.10.0.1

• Added getPassiveDelegationInfo endpoint providing information about the passive delegators at the end of a given block
• Exposed Payload.calculateEnergyCost method
• Fixed base cost of ConfigureDelegation transaction being bigger than needed

v.10.0.0

It's a small release fixing one particular issue in ConfigureBaker transaction, yet the fix is not backward-compatible.

• Changed openForDelegation field in ConfigureBakerPayload from boolean to OpenStatus:
  what used to be false is now OpenStatus.OPEN_FOR_ALL,
  what used to be true is now OpenStatus.CLOSED_FOR_NEW,
  and it is now possible to set OpenStatus.CLOSED_FOR_ALL as well

If you missed the previous major release introducing Protocol 8 support, check out the corresponding release notes

v.9.0.0

• Support for Protocol 8
• Added ProtocolVersion.V8 corresponding to Protocol version 8
• Added BakerSuspended and BakerResumed transaction result events
• Added ValidatorSuspended and ValidatorPrimedForSuspension special outcomes
  for the GetBlockSpecialEvents endpoint
• Added ChainParametersV3 for Protocol version 8, adding ValidatorScoreParameters
• Added GetConsensusDetailedStatus endpoint for querying detailed consensus status information
• Added GetScheduledReleaseAccounts endpoint for querying the list of accounts that have scheduled releases
• Added GetCooldownAccounts, GetPreCooldownAccounts and GetPrePreCooldownAccounts
  endpoints for querying the lists of accounts that have pending cooldowns in protocol version 7 onwards
• Added parameter field to ContractInitializedResult containing the parameter passed to the init function
• Added isSuspended field to Baker and BakerPoolStatus which, since Protocol version 8,
  indicates whether the account is suspended and is not participating in the consensus algorithm
• Added missedRounds and isPrimedForSuspension fields to CurrentPaydayStatus
  which, since Protocol version 8, reflect validator score status
• Added suspended field to ConfigureBakerPayload which, since Protocol version 8,
  indicates whether the validator is suspended
• Added FinalizationCommitteeParameters and ValidatorScoreParameters entries of PendingUpdateType,
  therefore new possible update types in PendingUpdateV2
• Added validatorScoreParameters field to NextUpdateSequenceNumbers
  which corresponds to updates in ChainParametersV3.validatorScoreParameters