Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: iotaledger/iota
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: d69a4ea1d7500b7c15078fc67a540644db54a4ea
Choose a base ref
...
head repository: iotaledger/iota
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 310abc75b81339e0515692e1ef6bf121932768bf
Choose a head ref
  • 8 commits
  • 43 files changed
  • 2 contributors

Commits on Dec 2, 2025

  1. feat(consensus): Introduce Scoring metric store (#9178) 

    ```mermaid
---
config:
  gitGraph:
    {parallelCommits: true,
    mainBranchName: 'Feature',
    rotateCommitLabel: true}
---
gitGraph
   commit id: "Initial commit"
   commit id: "Old Scorer" tag: "PR8530"
   checkout Feature
      branch new-types
   commit id: "add ChangeEpochV4"
   checkout Feature
    branch misbehavior-reports
   commit id: "add MisbehaviorReports"
    checkout misbehavior-reports
    branch scoring-metrics
   commit id: "add ScoringMetrics"
    checkout scoring-metrics
   branch scorer
   commit id: "add Scorer"
    checkout scorer
   branch scoring-metrics-store
   commit id: "add ScoringMetricsStore"
checkout scorer
    merge scoring-metrics-store tag: "THIS PR"
```

Introduces the `ScoringMetricStore`, which holds the validator scoring
metrics to be updated by consensus

- [x] 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

- [x] Protocol: Introduce Scoring metric store
- [ ] Nodes (Validators and Full nodes):
- [ ] Indexer:
- [ ] JSON-RPC:
- [ ] GraphQL:
- [ ] CLI:
- [ ] Rust SDK:
- [ ] REST API:

remove unused code
    @oliviasaa @cyberphysic4l
    oliviasaa authored and cyberphysic4l committed Dec 2, 2025
    Configuration menu
    Copy the full SHA
    37d3d63 View commit details
    Browse the repository at this point in the history

  2. feat(iota-core): Add report validation logic (#9362) 

    We build on top of the other PRs of this feature branch to enable the
misbehavior reports validation logic.

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

- [x] Protocol: Enables misbehavior report validation
- [ ] Nodes (Validators and Full nodes):
- [ ] Indexer:
- [ ] JSON-RPC:
- [ ] GraphQL:
- [ ] CLI:
- [ ] Rust SDK:
- [ ] REST API:

---------

Co-authored-by: Olivia <[email protected]>
    @cyberphysic4l @oliviasaa
    cyberphysic4l and oliviasaa committed Dec 2, 2025
    Configuration menu
    Copy the full SHA
    5f354fe View commit details
    Browse the repository at this point in the history

  3. feat(iota-core, iota-types): Add scoring function (#9361) 

    We introduce the scoring formulas for the validator scoring mechanism

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

- [x] Protocol: Introduces new scoring formulas for the validator score mechanism
- [ ] Nodes (Validators and Full nodes):
- [ ] Indexer:
- [ ] JSON-RPC:
- [ ] GraphQL:
- [ ] CLI:
- [ ] Rust SDK:
- [ ] REST API:

---------

Co-authored-by: Olivia <[email protected]>
    @cyberphysic4l @oliviasaa
    cyberphysic4l and oliviasaa committed Dec 2, 2025
    Configuration menu
    Copy the full SHA
    22d653c View commit details
    Browse the repository at this point in the history

  4. feat(iota-core, iota-types): Enable misbehavior report creation (#9363) 

    # Description of change

This PR enables the creation of the MisbehaviorReport consensus message,
as their submission to consensus in order to disseminate it with the
rest of the committee.

## Links to any relevant issues

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

## How the change has been tested

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

### 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.

- [x] Protocol: Enables misbehavior report creation and dissemination.
- [ ] Nodes (Validators and Full nodes):
- [ ] Indexer:
- [ ] JSON-RPC:
- [ ] GraphQL:
- [ ] CLI:
- [ ] Rust SDK:
- [ ] REST API:

---------

Co-authored-by: Andrew <[email protected]>
    @oliviasaa @cyberphysic4l
    oliviasaa and cyberphysic4l committed Dec 2, 2025
    Configuration menu
    Copy the full SHA
    99c886f View commit details
    Browse the repository at this point in the history

  5. feat(iota-core, iota-types): Add advance epoch v4 (#9424) 

    Enables the creation of a new version of advance epoch transaction and
new advance epoch function in iota-framework to modify rewards based on
scores. The existing validator reporting system remains whereby rewards
can be slashed entirely when a validator is reported. Now we
additionally modulate the rewards with the score provided as an argument
to the new version of the advance epoch function.

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

- [x] Protocol: Enables the creation of a new version of advance epoch
transaction and new advance epoch function in iota-framework to modify
rewards based on scores.
- [ ] Nodes (Validators and Full nodes):
- [x] Indexer: Enables a new `ChangeEpochV4` system transaction which
may appear in checkpoints for networks where `score_based_rewards`
protocol config is enabled. Consequently **a dependency bump is
necessary for `iota_data_ingestion_core` library consumers (custom
indexers) to prevent outages**.
- [ ] JSON-RPC:
- [ ] GraphQL:
- [ ] CLI:
- [ ] Rust SDK:
- [ ] REST API:

---------

Co-authored-by: Andrew <[email protected]>
    @oliviasaa @cyberphysic4l
    oliviasaa and cyberphysic4l committed Dec 2, 2025
    Configuration menu
    Copy the full SHA
    2700087 View commit details
    Browse the repository at this point in the history

  6. compile move packages

    @cyberphysic4l
    cyberphysic4l committed Dec 2, 2025
    Configuration menu
    Copy the full SHA
    d5f5cc6 View commit details
    Browse the repository at this point in the history

  7. update protocol config and snapshots

    @cyberphysic4l
    cyberphysic4l committed Dec 2, 2025
    Configuration menu
    Copy the full SHA
    6afef5a View commit details
    Browse the repository at this point in the history

  8. add iota-framework snapshots

    @cyberphysic4l
    cyberphysic4l committed Dec 2, 2025
    Configuration menu
    Copy the full SHA
    310abc7 View commit details
    Browse the repository at this point in the history
Loading