Skip to content

Conversation

@tequdev
Copy link
Member

@tequdev tequdev commented Dec 17, 2025

High Level Overview of Change

require:

Context of Change

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (non-breaking change that only restructures code)
  • Tests (you added tests for code that already exists, or your new feature included in this PR)
  • Documentation update
  • Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
  • Release

API Impact

  • Public API: New feature (new methods and/or new fields)
  • Public API: Breaking change (in general, breaking changes should only impact the next api_version)
  • libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
  • Peer protocol change (must be backward compatible or bump the peer protocol version)

@tequdev tequdev added the ripple(d) sync Sync w/ RIpple(d) label Jan 6, 2026
testSTI("00101003", true);
// STI_UINT160
testSTI("01110000000000000000000000000000000000000000", true);
// STI_PATHSET
Copy link
Member Author

@tequdev tequdev Jan 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently, it is commented out, but STI_PATHSET has not been processed correctly from the beginning.

fixed

@tequdev tequdev changed the title Support new STIs for sto_* HookAPI [DO NOT MERGE] Support new STIs for sto_* HookAPI Jan 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ripple(d) sync Sync w/ RIpple(d)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants