Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DO NOT MERGE] Changeset Release Preview - v2.23.0 #1

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Mar 26, 2025

This PR is a preview of the changes that will be included in the next release. Please do not merge this PR.

Changelog Chainlink Core

2.23.0 - PREVIEW

added

  • #16789 4ce1a16 - Support new report type 'evm_streamlined'. #added
    This new report type is designed to be as small and optimized as possible to minimize report size and calldata.
    Reports are encoded as such:
    (no FeedID specified in opts)

    <32 bits> channel ID
    <64 bits> unsigned report timestamp nanoseconds
    <bytes>   report data as packed ABI encoding
    

    (FeedID specified in opts)

    <256 bits> feed ID
    <64 bits> unsigned report timestamp nanoseconds
    <bytes>   report data as packed ABI encoding
    

    Report contexts are encoded as such:

    // Equivalent to abi.encodePacked(digest, len(report), report, len(sigs), sigs...)
    // bytes32 config digest
    // packed uint16 len report
    // packed bytes report
    // packed uint8 len sigs
    // packed bytes sigs
    

    See report_codec_evm_streamlined_test.go for examples.

  • #16825 390c02c - Implement support for TimestampedStreamValue data types in LLO (RWAs) #added
    Support encoding into evm_abi_unpacked or evm_streamlined report formats.
    ABI must specify how to encode both types, as such:

    // Encodes the timestamp as uint64 and data payload as int192
    {
      "abi": [[{ "type": "uint64" }, { "type": "int192" }]]
    }

    The first element of the array encodes the timestamp, the second encodes the data payload.
    Users may suppress one or the other entirely by using the special keyword "bytes0" e.g.

    // Encodes only the data payload
    {
      "abi": [[{ "type": "bytes0" }, { "type": "int192" }]]
    }

removed

updated

internal

  • #16704 fe50f92 - #internal Split EVM and SVM transmitter

  • #16704 fe50f92 - #internal: Added stop-gap solution enabling EVM->SOL transfers in CCIP contract transmitter

  • #16769 7f3e55b - #internal bump chainlink-common library to v0.5.1

  • #16785 abf6662 - #internal upgrade the mcms library to v0.14.0

  • #16754 f0bb88c - Adds message IDs and logging in capabilities server and client #internal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant