Skip to content

Releases: GalaChain/sdk

v1.5.9

10 Dec 01:01
eb5ee87
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.5.8...v1.5.9

v1.5.8

09 Dec 19:22
560337d
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.5.7...v1.5.8

v2.0.0

26 Nov 09:31
207ceb8
Compare
Choose a tag to compare

GalaChain SDK 2.0.0 Release Notes

GalaChain SDK version 2.0.0 introduces several enhancements aimed at improving flexibility, security, and consistency for developers. While some changes may require updates to existing codebases, these updates provide significant benefits for building more robust and decentralized applications.

Note: Version 1.x.x will continue to receive issue fixes (no new features) until January 31, 2025.
For a detailed breakdown of required updates, refer to the Breaking Changes Documentation.

Notable features

1. Role-Based Access Control

This release introduces Role-Based Access Control (RBAC), replacing the organization-based authorization model (allowedOrgs) with a more flexible role-based system (allowedRoles).

  • Roles such as CURATOR, EVALUATE, and SUBMIT enable granular permission management.
  • Roles can be assigned using the PublicKeyContract:UpdateUserRoles method.
  • Deprecated allowedOrgs in decorators; replaced by allowedRoles.
  • Roles provide greater flexibility and are better suited to decentralized applications, allowing permissions to align with user roles rather than organizations.

2. Strict UserAlias and UserRef Validation

This release introduces stricter validation for user-related fields, enhancing reliability and consistency when working with user data.

  • UserAlias: A unique identifier for a user on the chain (e.g., client|abc or eth|<checksumed-addr>).
  • UserRef: A reference to the user, which can include multiple formats, such as Ethereum addresses (lower-cased or checksumed) or GalaChain uses aliases.
  • Utility methods like asValidUserAlias() and asValidUserRef() help validate or transform these fields.

3. Bidirectional Aliases

Bidirectional Aliases enhance how user-related fields are handled in DTOs, allowing for flexible input and automatic resolution of user identifiers.

  • Accept both GalaChain aliases (e.g., client|abc) and raw Ethereum addresses for user-related fields.
  • Automatic resolution of user references (UserRef) to registered aliases (UserAlias).
  • The resolveUserAlias() function available in the chaincode maps UserRef values (e.g., Ethereum addresses) to corresponding UserAlias identifiers stored on the chain.
  • It allows easier integration with GalaChain for applications that use external signing (like MetaMask), and do not have direct access to GalaChain user aliases.

4. REST API Access for Local Development

Local development is now easier with the introduction of the Operation API, a REST service that mirrors the public GalaChain Gateway API.

  • Interact with the Hyperledger Fabric network in local environments via REST API.
  • Streamlined transitions between local and production environments without code changes.
  • Simplified application testing with consistent API behavior.

5. Enforced Unique Keys for Transactions

Submit transactions now require a uniqueKey to enhance security and prevent replay attacks.

  • Validation ensures uniqueKey is present and not reused.
  • Utility methods, such as createValidSubmitDTO() and createUniqueKey(), simplify compliance.

6. Unified TokenBalance API

The TokenBalance chain object API has been refined for clarity and ease of use. Validation and mutation methods are now combined (e.g., addInstance() replaces ensureCanAddInstance().add()).

7. Improved Unit Testing

  • Test utilities now reflect the updated authorization model, requiring signed DTOs for transactions.
  • Simplified syntax for testing interactions, including getWrites() for observing chain state changes.

8. Enhanced Security:

Signature verification is enforced for all methods updating the chain. DER signatures without additional metadata (signer address or signer public key) are no longer supported.

Preparing for the Update

Version 2.0.0 introduces several changes that may require adjustments to existing projects. For a full list of updates, including migration steps and deprecations, refer to the Breaking Changes Documentation.

GalaChain SDK 2.0.0 is designed to provide a more flexible, secure, and developer-friendly experience. If you have questions or need support during the upgrade, consult our community forums or official documentation.

What's Changed

Full Changelog: https://github.com/GalaChain/sdk/pull/368/files

v1.5.7

13 Nov 18:52
9f3423d
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.5.6...v1.5.7

v1.5.6

13 Nov 03:56
dc9a281
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.5.5...v1.5.6

v1.5.5

08 Nov 00:55
a1540a2
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.5.4...v1.5.5

v1.5.4

06 Nov 19:47
0ed8758
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.5.3...v1.5.4

v1.5.3: finalize Oracle Cross-rate price assertions (#421)

04 Nov 22:51
a4f229c
Compare
Choose a tag to compare
support bridge out, destination chain fee transaction
calculations in tokens that aren't directly priced in
GALA, using a common cross-rate exchange rate denominated
in a widely used token.

v1.5.2

30 Oct 20:23
7be5569
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.5.1...v1.5.2

v1.5.1

30 Oct 16:24
34fd553
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.5.0...v1.5.1