Skip to content

Conversation

@oliviasaa
Copy link
Contributor

TO DO

Description of change

Please write a summary of your changes and why you made them.

Links to any relevant issues

Be sure to reference any related issues by adding fixes #(issue).

How the change has been tested

Describe the tests that you ran to verify your changes.

Make sure to provide instructions for the maintainer as well as any relevant configurations.

  • Basic tests (linting, compilation, formatting, unit/integration tests)
  • Patch-specific tests (correctness, functionality coverage)
  • I have added tests that prove my fix is effective or that my feature works
  • I have checked that new and existing unit tests pass locally with my changes

Change checklist

Tick the boxes that are relevant to your changes, and delete any items that are not.

  • I have followed the contribution guidelines for this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation

Release Notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.

For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

  • Protocol:
  • Nodes (Validators and Full nodes):
  • Indexer:
  • JSON-RPC:
  • GraphQL:
  • CLI:
  • Rust SDK:
  • REST API:

@vercel
Copy link

vercel bot commented Nov 20, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

6 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
apps-backend Skipped Skipped Nov 20, 2025 11:01am
apps-ui-kit Skipped Skipped Nov 20, 2025 11:01am
iota-evm-bridge Skipped Skipped Nov 20, 2025 11:01am
iota-multisig-toolkit Skipped Skipped Nov 20, 2025 11:01am
rebased-explorer Skipped Skipped Nov 20, 2025 11:01am
wallet-dashboard Skipped Skipped Nov 20, 2025 11:01am

@github-actions github-actions bot added the ts-sdk Issues related to the TS SDK label Nov 20, 2025
@oliviasaa oliviasaa changed the base branch from develop to protocol-research/feat/score-integration November 20, 2025 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core-protocol research ts-sdk Issues related to the TS SDK

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants