chore(deps): update module go.sia.tech/core to v0.19.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
go.sia.tech/core	v0.14.1 → v0.19.0

---

Release Notes

SiaFoundation/core (go.sia.tech/core)

v0.19.0: 0.19.0 (2025-12-01)

Compare Source

Breaking Changes

• Changed rhp.BuildSectorProof to accept cached subtrees to reduce disk IO required for sector reads.

Fixes

• Parallelize sector root computation in ReaderRoot.

v0.18.1: 0.18.1 (2025-11-10)

Compare Source

Fixes

• Fix invalid MaxCollateral validation for partial contract refreshes.

v0.18.0: 0.18.0 (2025-09-23)

Compare Source

Breaking Changes

• Changed the encoding of rhp.Account to include the ed25519: prefix.

v0.17.5: 0.17.5 (2025-09-01)

Compare Source

Fixes

• Fix ProtocolVersion marshalling failing.

v0.17.4: 0.17.4 (2025-08-27)

Compare Source

Fixes

• Add compatibility for old protocol version JSON encoding

v0.17.3: 0.17.3 (2025-08-21)

Compare Source

Fixes

• Fix RPCSectorRoots not supporting MaxSectorBatchSize.

v0.17.2: 0.17.2 (2025-08-21)

Compare Source

Fixes

• Fix RPCAppendSectors not allowing up to MaxSectorBatchSize sectors.

v0.17.1: 0.17.1 (2025-08-18)

Compare Source

Features

• Add NonceFactor field to the HardforkASIC struct and use this as the return value for State.NonceFactor().

v0.17.0: 0.17.0 (2025-08-11)

Compare Source

Breaking Changes

• Add dedicated ProtocolVersion type for RHP version.

Fixes

• Increase RPCFreeSectorsRequest and RPCFreeSectorsResponse maxLengths to fix issue with large contracts failing to prune.

v0.16.0: 0.16.0 (2025-07-28)

Compare Source

Breaking Changes

Allow empty miner payout after FinalCut

A remnant of the old v1 types.Currency encoding persists in the Block.MinerPayouts field. In v2, only a single miner payout is allowed, so its value is fully determined by the sum of the block reward and miner fees. We can therefore omit the value entirely, eliminating a redundant source of truth. It was decided that requiring the value to be omitted was too onerous, as it would compel all miners to update. Making the omission optional allows us to enforce it as a hard requirement at some later time, after all miners have updated.

Add (State).PowTarget and deprecate v1 fields

The consensus.State type contains several redundant and unused PoW-related fields. However, since these fields were included in the Commitment hash, nodes still had to update them correctly. These fields are now zeroed after the hardfork height, so that the Commitment hash can hard-code them if desired.

Features

• Expose helper methods to compute the remaining allowance, collateral, risked collateral and risked revenue on the V2FileContract type.

Fixes

• Fixed issue with RPC validation functions not returning RPC errors.

v0.15.0: 0.15.0 (2025-07-25)

Compare Source

Breaking Changes

• Change Account.Token method to NewAccountToken function

Features

Added RPCRefreshPartial ID and RefreshContractPartialRollover helper

Previously, renters and hosts had to rollover all funds when refreshing a contract. With this change, renters can set their spendable allowance without forcing an increase and hosts only have to rollover their existing risked collateral and revenue. This change increases efficiency of refreshing without compromising the collateral guarantees of existing data or forcing hosts to lock additional collateral that won't be utilized.

v0.14.3: 0.14.3 (2025-07-17)

Compare Source

Features

• Fixed issues comparing RPCErrors.

v0.14.2: 0.14.2 (2025-07-07)

Compare Source

Features

Add RPCSendHeaders

#​330 by @​lukechampine

Also removes RPCSendBlocks and RPCSendBlk (made obsolete by RPCSendV2Blocks and RPCSendCheckpoint), as well as RPCRelayHeader and RPCSendTransactionSet (as no more v1 blocks or v1 transactions can be mined). I could maybe see an argument for keeping the latter two, if we wanted to run a v1 testnet, but... why would we want to run a v1 testnet?

consensus: Reject V1BlockSupplement after require height

#​329 by @​lukechampine

This is somewhat redundant since the chain.DBStore always returns an empty supplement after the require height, but it doesn't hurt to enforce it in core.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5028a6c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}