Candidate for 6.0.5 release by kushti · Pull Request #2416 · ergoplatform/ergo

kushti · 2026-07-08T21:15:27Z

Validate NiPoPoW proof parameters

Reject proofs whose header chain contains invalid Autolykos PoW before bootstrap headers are applied. Add regression coverage demonstrating that rejected proof headers are not inserted into history.

Restore the v6.0.5 node and integration-test builds under fatal unused-import warnings.

Validate NiPoPoW proof header PoW

Fix fee estimation bounds

Reject invalid inbound NiPoPoW parameters

Preserve asset issuance with token burn requests

Bound per-peer outbound buffering

…-cleanup Close all live connections for blacklisted IPs

Log method, relative URI, response status and elapsed time for every query served by the node's HTTP interface. Bodies are not logged: requests to this API carry secrets (mnemonic on /wallet/restore, password on /wallet/unlock). Logging goes through ScorexLogging rather than akka's LoggingAdapter, so no dependency is added and the node's HTTP verbosity is not tied to akka's global log level. It is off by default, as the root logger is at INFO, and costs nothing when off since log.debug is a macro guarded by isDebugEnabled. The directive wraps the route outside handleRejections, so rejected requests are logged too, with the status they were answered with. Closes #1909

Commented-out logger element so the switch is discoverable.

Attaches a logback ListAppender to the service logger and asserts on what is emitted: one line per served query with method, URI, status and duration; the query string included and unmatched paths logged with the status they were answered with; nothing logged below DEBUG; and the response body unchanged with logging on and off.

Log API queries at DEBUG level

jozanek

Reviewed the full branch against master, focused on protocol/wire compatibility, concurrency, DoS surface, and test coverage.

No protocol blockers: serializers untouched, stricter NiPoPoW validation is bootstrap-only with prover/verifier symmetry intact, FullBlockApplied.txIds never hits the wire, and the outbound buffer cap changes no message format. Test coverage is excellent — every fix ships a regression spec.

Findings below: 3 minor, 5 nit — release-note/visibility items, no code defects.

jozanek · 2026-08-11T17:54:04Z

  *
  */
-case class PoPowParams(m: Int, k: Int, continuous: Boolean)
+final class PoPowParams private (val m: Int, val k: Int, val continuous: Boolean, val minChainLength: Int)


MINOR: PoPowParams going from case class to a private-constructor class with apply returning Try is a source/binary break in ergo-core's public API (no more direct construction, copy, or unapply). Since ergo-core is the library SPV clients build against, this deserves an explicit entry in the 6.0.5 release notes.

jozanek · 2026-08-11T17:54:04Z

+
+  def apply(m: Int, k: Int, continuous: Boolean): Try[PoPowParams] = Try {
+    require(isValid(m, k), s"Invalid NiPoPoW parameters: m=$m, k=$k")
+    new PoPowParams(m, k, continuous, m + k)


NIT: minChainLength is computed and stored but never read in production code (only one test asserts it). Either drop it or use it in prove's chain.lengthCompare(k + m) check so it earns its place.

jozanek · 2026-08-11T17:54:04Z


  private val mempoolCapacity = settings.nodeSettings.mempoolCapacity

+  private def withoutTransaction(id: ModifierId): TreeMap[WeightedTxId, UnconfirmedTransaction] = {


MINOR: the self-heal fallbacks (withoutTransaction's full filter, hasUnregisteredTransaction, currentTransaction's orElse scan) are O(n) per mutation once orderedTransactions.size != transactionsRegistry.size, so a corrupted pool under tx flood pays O(n) per admission until healed. The healthy path keeps O(log n) via the size-equality guard, so this is fine as a recovery path — but consider logging when the degraded path triggers, so pool corruption is visible in production instead of silently costing CPU.

logging added

jozanek · 2026-08-11T17:54:05Z

    val elapsed = System.currentTimeMillis() - stats.startMeasurement
-    if (stats.takenTxns != 0) {
-      elapsed * posInPool / stats.takenTxns
+    val cappedElapsed = math.max(0L, math.min(elapsed, MemPoolStatistics.measurementIntervalMsec.toLong))


NIT: MemPoolStatistics.measurementIntervalMsec = 60 * 1000 is commented "one hour" but is one minute. Pre-existing, but the new elapsed-time cap here now depends on this constant, so worth fixing the comment while in the area.

jozanek · 2026-08-11T17:54:05Z

+    MaxMessageSize.toLong + HeaderLength + ChecksumLength
+
+  // Independently bound collection overhead from small messages.
+  private[network] val MaxBufferedOutboundMessages: Int = 64


NIT: MaxBufferedOutboundMessages = 64 and the byte cap are hard-coded. If field tuning ever turns out to be needed (e.g. peers on high-latency links tripping the abort), exposing them under scorex.network would avoid a redeploy — fine to defer.

jozanek · 2026-08-11T17:54:05Z

  val modifierIdGet: Directive1[ModifierId] = parameters("id".as[String])
    .flatMap(handleModifierId)

+  private def parseModifierId(value: String): Try[ModifierId] =


MINOR: client-visible behavior change worth a release-note entry: modifier/box/token ids with wrong byte length and scan ids outside Short range now return 400 where they were previously accepted, silently truncated (scanIdInt.toShort querying the wrong scan!), or 500'd. Good hardening — just make sure API consumers hear about the stricter validation.

jozanek · 2026-08-11T17:54:05Z

-    } ~
-    (path("openapi.yaml") & get) {
-      getFromResource("api/openapi-ai.yaml", ContentTypes.`text/plain(UTF-8)`)
    }


NIT: removal of /openapi.yaml and /.well-known/ai-plugin.json is a deliberate feature removal, but anyone who scripted against those endpoints will notice — one line in the release notes would cover it.

jozanek · 2026-08-11T17:54:05Z

    .withFallback(nodeSeedConfigs.head)
    .withFallback(allowLocalConfig)

+  // `lazy` so the container is only started when a test actually touches `node`.


NIT: the lazy val change is right, but it documents that the only OpenAPI conformance test remains ignored (checker image gone) — so the openapi.yaml edits on this branch aren't machine-checked. Worth a tracking issue to restore an OpenAPI validation step.

jozanek

Review of the 6.0.5 release candidate

What "Request changes" means here: GitHub will show this PR as blocked on this review until it is re-reviewed or dismissed. I am using it because of one MAJOR functional finding — the extra indexer can stall permanently after the new catch-up deferral (inline below) — which should be fixed, or explicitly accepted, before the release is tagged. It is not a protocol or consensus objection.

Scope: the full PR diff against master — mempool duplicate-id fix, candidate-generator improvements, extra-indexer reorg handling, API input validation and openapi corrections, AI-plugin removal, NiPoPoW parameter/PoW validation, p2p outbound-buffer cap and blacklist cleanup, wallet burn-order fix, mempool fee/wait-time clamps, and the API query logger.

Protocol screen — why there are no blockers:

No serializer byte-format changes anywhere. The NiPoPoW hardening is verifier-side only: the deserializer still parses the same byte shapes (the new tests round-trip proofs with m = 0 and only isValid rejects them), and the tightened isValid (param sanity + per-header Autolykos PoW) only rejects proofs an honest prover never produces, so prover/verifier symmetry is retained.
LocalBlockApplied/RemoteBlockApplied gained a txIds field, but these are internal event-stream messages published by ErgoNodeViewHolder; they are never serialized to the network.
The appVersion = 6.0.5 handshake bump is the standard release procedure, and the openapi/do-release.sh version stamps are consistent with it.
The outbound-buffer cap and blacklist changes alter connection management only, not the wire format.

Also verified along the way: the removed openapi security annotations now match the code (only candidateWithTxs carries withAuth in MiningApiRoute; ScriptApiRoute has none), the old chainSlice range guard was dead code so the new check closes a real unbounded-request hole, and the scan-id .toShort truncation fix stops queries like 70000 from silently returning scan 4464's data.

Findings: 1 MAJOR, 5 MINOR, 3 NIT — all inline.

jozanek · 2026-08-11T18:30:40Z

+        context.become(receive.orElse(loaded(newState)))
+        self ! Index()
+      } else {
+        log.info("Deferring catch-up because the next header does not extend the indexed tip")


MAJOR The deferral branch stops the Index() self-loop without scheduling any retry, and while caughtUp = false the actor has no handler for FullBlockApplied (the handler at line 501 requires caughtUp), so the only signal that can resume indexing is a Rollback event.

Consider a near-tip headers-only fork that briefly becomes the best header chain but whose full blocks never win (the losing side of a miner race): the guard at line 481 sees a next header that does not extend the indexed tip and defers. If the original chain then outgrows the fork, the best header chain flips back — but no Rollback is ever published, because the full-block chain never switched. The indexer stays stalled until node restart, silently dropping every subsequent FullBlockApplied.

Suggestion: add case _: FullBlockApplied if !state.caughtUp && !state.rollbackInProgress => self ! Index() so every applied block re-evaluates the deferral condition (or re-schedule Index() with a short delay instead of only logging).

jozanek · 2026-08-11T18:30:40Z

-      if (modCount >= saveLimit) saveProgress(newState)
-      context.become(receive.orElse(loaded(newState)))
-      self ! Index()
+      val nextHeaderOpt = history.bestHeaderAtHeight(state.indexedHeight + 1)


MINOR During catch-up this adds a bestHeaderAtHeight(h + 1) (heightIds index read + full header fetch) per block, and index() then re-reads bestHeaderIdAtHeight(height) at line 381 because headerOpt is None on this path — two redundant storage reads per block on the full-reindex hot path, where they multiply across millions of blocks.

Suggestion: pass the already-fetched nextHeaderOpt into index(state.incrementIndexedHeight, nextHeaderOpt) so both the parent check and indexedHeaderId reuse a single read.

jozanek · 2026-08-11T18:30:40Z

      ))
    })
-    } ~
-    (path(".well-known" / "ai-plugin.json") & get) {


MINOR Removing /openapi.yaml and /.well-known/ai-plugin.json is clearly intentional (ChatGPT-plugin retirement), but it is a breaking removal of public endpoints — anything still fetching them gets a 404 after upgrade. Worth an explicit line in the 6.0.5 release notes.

jozanek · 2026-08-11T18:30:40Z

+  // `lazy` so the container is only started when a test actually touches `node`.
+  // The single test below is currently `ignore`d (the openapi-checker image is gone),
+  // so without `lazy` we would start and tear down a node for nothing.
  lazy val node: Node = docker.startDevNetNode(offlineGeneratingPeer).get


MINOR The spec's only test remains ignored (the openapi-checker image is gone), so this suite passes CI while providing zero signal — the new comment documents the situation but keeps the dead spec. Consider deleting the spec or reviving the check with a maintained validator image.

jozanek · 2026-08-11T18:30:40Z

  *
  */
-case class PoPowParams(m: Int, k: Int, continuous: Boolean)
+final class PoPowParams private (val m: Int, val k: Int, val continuous: Boolean, val minChainLength: Int)


MINOR minChainLength is not read anywhere in production code — its only consumer is the assertion in PoPowAlgosSpec. If it is groundwork for the follow-up NiPoPoW parsing work (#2461), fine to keep, but then a short comment saying so would help; otherwise it is a dead field that suggests a validation which does not actually happen yet.

jozanek · 2026-08-11T18:30:40Z

      suffixHead.checkInterlinksProof()
  }

+  lazy val hasValidPow: Boolean = headersChain.forall(popowAlgos.hasValidPow)


MINOR Validating every header's Autolykos PoW is the right fix, but isValid is evaluated inside ErgoNodeViewSynchronizer's receive (case Success(proof) if proof.isValid around line 1085 of ErgoNodeViewSynchronizer.scala), so a proof chain of hundreds of headers now runs full PoW verification on the synchronizer's dispatcher thread, stalling its mailbox during nipopow bootstrap — and several proofs can arrive back-to-back from the p2pNipopows peers.

Suggestion: run the proof validation in a Future on a dedicated dispatcher and pipeTo the result back, keeping the synchronizer responsive.

jozanek · 2026-08-11T18:30:40Z

  private val mempoolCapacity = settings.nodeSettings.mempoolCapacity

+  private def withoutTransaction(id: ModifierId): TreeMap[WeightedTxId, UnconfirmedTransaction] = {
+    // Keep healthy mutations logarithmic; scan by ID only after cardinality diverges.


NIT The size-equality heuristic takes the fast path on compensating corruption — one duplicate key plus one orphaned entry leaves the sizes equal, so a duplicate would survive withoutTransaction. Fine as best-effort self-healing, but worth extending the comment to note that limitation.

jozanek · 2026-08-11T18:30:40Z

-    done.await()
+    awaitCondition(done)
    indexer ! GenerateBetterChainTip()
    lock.lock()


NIT awaitCondition fixes the lock discipline (the old pattern never unlocks after await()), but this test still uses bare lock.lock(); created.await() in two places. Worth finishing the migration to awaitCondition(created) here too.

jozanek · 2026-08-11T18:30:40Z


+  // Keep one maximum serialized frame per peer. Backpressured snapshot transfers
+  // retry instead of retaining their entire application-level in-flight window.
+  private[network] val MaxBufferedOutboundBytes: Long =


NIT Question on honest-path headroom: the byte cap is one max frame (~16.4 MB), which the tests show fits 4 in-flight snapshot chunks — but a peer that requested a large block batch can legitimately have several Modifiers responses (up to ~8.4 MB each) queued while its socket is stalled, and two of those already exceed the cap, aborting the connection. Reconnect makes this self-healing, so it may well be acceptable — but worth confirming the serving side never queues more than one large response per request round, or noting that connection churn under full-stall is the intended trade-off.

Clarify comment regarding state after headers-only fork.

Resume deferred ExtraIndexer catch-up without reindexing

odiseusme · 2026-08-21T21:35:23Z

Review of the 6.0.5 release candidate at 25ae315

Scope and method: the full diff against master at merge-base c313356 (35 files, +810/-381), read against the current master state, so items already merged to master since jozanek's review (ExtraIndexer catch-up retry, API id validation) are out of scope here. For every production change I traced callers and cleanup paths rather than reading hunks in isolation, and checked the dependency story against the upstream repos. CI state at 25ae315 is covered in finding 0.

Verdict: one MAJOR build finding, then no functional blockers. The functional fixes are correct and well-tested. Beyond finding 0 there are two confirm-items on the Aug 21 dependency bumps, two minors, and release-notes items.

MAJOR - the RC head does not build, on two independent dependency faults introduced by the Aug 21 bump commit (CI run 3758 fails at 25ae315; the immediately preceding commits passed). Both abort at resolution, before any compilation, so none of the Aug 21 changes (scrypto 3.1.1, sigma 6.0.6, circe 0.14.15, the ExtensionCandidate migration) have been compiled or exercised by any test yet.

Fault A, Scala 2.13 legs (wallet/ergo-core, from the wallet job log): sigma-state 6.0.6 is built with Scala 2.13.18 (its build.sbt pins scala213 = "2.13.18"), so its 2.13 artifact pulls scala-library 2.13.18 onto the classpath, and sbt's SIP-51 scalaInstance guard aborts against the build's pinned 2.13.16 ("Expected ergoWallet / scalaVersion to be 2.13.18 or later, but found 2.13.16"). Fix: bump scala213 from 2.13.16 to 2.13.18 in build.sbt:9, avldb/build.sbt:5, ergo-core/build.sbt:4, ergo-wallet/build.sbt:4, and the two ci.yml matrix lines (24, 67). allowUnsafeScalaLibUpgrade := true is the wrong choice for a release.

Fault B, Scala 2.12 legs (node/it-node, from the node job log): an early-semver eviction conflict. sigma-state 6.0.6 and ergo-core both now depend on circe 0.14.15, which is selected over the 0.9.1 that akka-http-circe 1.20.0 (build.sbt:339) declares, and sbt flags the pair as suspected binary-incompatible and aborts. Fix: either a libraryDependencySchemes entry declaring the circe modules early-semver (so 0.14.15 satisfies akka-http-circe's 0.9.1 requirement), or move off the abandoned heikoseeberger akka-http-circe onto a maintained JSON-marshalling path. evictionErrorLevel downgrade would silence it but ships an unverified binary-compat assumption.

Both faults must be fixed and CI must be green before tagging; right now the branch has never compiled with its own declared dependencies.

Verified correct, beyond reading the diff:

Wallet burn/issue fix (ErgoWalletSupport): outputs is built 1:1 from requestsWithoutBurnTokens via Traverse.sequence, so the old zip(requests) misaligned whenever a BurnTokensRequest preceded an AssetIssueRequest, misidentifying the issuance box and corrupting targetAssets. The fix aligns the zip, and the new "asset issuance should be independent of burn request order" property pins it.
Blacklisted rewrite (NetworkController): the old code was doubly wrong: it acted only on an exact socket-address key hit, and it dropped same-IP entries from the connections map without stopping their handlers, leaking live handlers. The new code closes every matching handler and relies on context.watch/Terminated cleanup, which I verified exists (L224-229). The two new NetworkControllerSpec properties cover both the multi-connection close and the inexact-socket case.
Outbound buffer cap (PeerConnectionHandler): byte and count accounting is exact, including the id-overwrite path and Ack idempotence (an Ack for an unknown id no longer corrupts the byte counter), and the abort path zeroes state before stopping. The three new properties cover the frame cap, the 64-message cap, and retry/ack accounting.
Mempool logging added in 5f0e92a: I checked all three callers of currentTransaction plus both degraded paths; the new warns fire only on genuine index divergence, never on the healthy path, so no log spam. The fee floor and elapsed clamp are right, comment fixed.
NiPoPoW parameter hardening end to end: invalid or overflowing m,k now surface as 400 with a message at /nipopow/proof (overflow test with Int.MaxValue present), PoPowParams construction is Try-gated, and isValid orders the cheap parameter check first and per-header PoW last.
Version stamps consistent (appVersion and openapi.yaml both 6.0.5). The query logger wraps outside handleRejections as documented, logs method/URI/status/elapsed only, so api_key headers and request bodies never reach the log, and it is macro-dead at INFO.

Findings:

VERIFIED, for the record - scrypto 2.3.0 -> 3.1.1 (avldb/build.sbt). Structurally this is the right move: the node excludes sigma's transitive scrypto and pins its own via avldb (which ergo-core and the root project depend on), and master has been running sigma 6.0.3 (built against scrypto 3.0.0) forced onto scrypto 2.3.0, a latent binary mismatch, while 3.1.1 is exactly what sigma 6.0.6 is built against. I traced the fork's v3.1.1 tag (70b3610): the duplicate-leaf Merkle fix (PR added travis configuration #5, merged 28839b0) is inside the tag, and its diff changes the proof layer only: proofByIndices now reads positional leafHashes instead of the old elementsHashIndex Map round-trip, which collapsed duplicate hashes and produced invalid multiproofs for any tree containing a duplicate leaf. calcTopNode and the leaf vector feeding it are untouched, so rootHash is byte-identical for every input: consensus-safe. The new MerkleTreeSpecification properties pin duplicate-leaf proofs against rootHash. This PR's own ExtensionCandidate change calls indexByElementHash and the no-arg proofByIndices, both of which exist only after that fix, so a green compile doubles as proof the published 3.1.1 artifact contains it (pending finding 0's resolution). Remaining ask: a one-liner on what the "slice fix" (scrypto mempool wait for the appearance of all transactions #2) hardens, for downstream users judging upgrade urgency.
CONFIRM - sigma 6.0.3 -> 6.0.6. The 6.0.5 step includes "reject negative-id vars in ContextExtension deserializer" (sigma Make a test for ErgoWalletActor.generateTransactionWithOutputs #1121). ContextExtension bytes ride inside transactions, so if a negative id was deserializable and mineable under 6.0.3, stricter parsing opens a divergence window against un-upgraded peers. My reading is that ids are unsigned on the wire so the rejected case should be unreachable in blocks, but I would like that confirmed explicitly, since it is the one behavior change in the bump chain that touches tx bytes.
MINOR - circe 0.13.0 -> 0.14.15. Core printing is stable across this line, but the node's JSON is consumed by the whole ecosystem (explorer, appkit, wallets). Worth one golden-output check on representative /info, /transactions and /blocks responses before tagging, and a release-notes line so client authors know the JSON stack moved.
MINOR - unresolved from jozanek's review: proof.isValid, which now includes per-header Autolykos PoW over the whole headers chain, still runs inline in ErgoNodeViewSynchronizer's receive (L1085). The nipopowProviders set bounds it to one proof per peer, which limits but does not remove the mailbox stall during bootstrap. Either a Future + pipeTo on a separate dispatcher, or an explicit "accepted for 6.0.5" so it does not silently carry into 6.0.6.
Release-notes checklist for tagging, consolidating this branch plus the already-merged master changes: PoPowParams case class removed from ergo-core's public API (source break for SPV client libs), scrypto moved to the ergoplatform fork and bumped 2.3.0 -> 3.1.1, sigma-state 6.0.3 -> 6.0.6, circe 0.13.0 -> 0.14.15, /openapi.yaml and /.well-known/ai-plugin.json removed, stricter 400s on malformed modifier/box/token/scan ids, and the new opt-in HTTP query logger with its logback switch.
NIT: with OpenApiSpec and ApiChecker deleted, nothing machine-checks openapi.yaml at all. Fine for 6.0.5, but a tracking issue for a maintained validator would stop the spec drifting.

tum231990 and others added 19 commits June 12, 2026 09:56

Validate NiPoPoW proof parameters

7b394cc

Address NiPoPoW params review feedback

21c327f

Stabilize fee estimation heuristics

a2ffb6e

6.0.5 version set

4777818

Merge pull request #2379 from a-shannon/fix/nipopow-proof-param-bounds

17f578a

Validate NiPoPoW proof parameters

Validate NiPoPoW proof header PoW

366a046

Reject proofs whose header chain contains invalid Autolykos PoW before bootstrap headers are applied. Add regression coverage demonstrating that rejected proof headers are not inserted into history.

Remove unused InfoApiRoute import

594eeb9

Restore the v6.0.5 node and integration-test builds under fatal unused-import warnings.

Merge pull request #2396 from a-shannon/fix/nipopow-validated-pow-levels

cdd89ce

Validate NiPoPoW proof header PoW

Merge pull request #2410 from a-shannon/fix/fee-estimation-stability

ce1dfac

Fix fee estimation bounds

Reject invalid inbound NiPoPoW parameters

706a916

refactor: reuse NiPoPoW parameter validation

3cc7f3c

Merge pull request #2417 from a-shannon/codex/fix-nipopow-inbound-params

28d644a

Reject invalid inbound NiPoPoW parameters

Bound per-peer outbound buffering

14e7e71

Close all live connections for blacklisted IPs

eaa7f1b

Preserve asset issuance with token burn requests

b7baa6c

Merge pull request #2430 from a-shannon/fix/burn-issue-output-matching

83b15cc

Preserve asset issuance with token burn requests

Test outbound retry accounting through ACK flow

514800b

Merge pull request #2426 from a-shannon/fix/p2p-outbound-buffer-limit

130518a

Bound per-peer outbound buffering

Merge pull request #2427 from a-shannon/fix/blacklisted-ip-connection…

84b1638

…-cleanup Close all live connections for blacklisted IPs

a-shannon mentioned this pull request Jul 17, 2026

Handle fragmented and coalesced handshakes #2436

Open

kushti and others added 5 commits July 30, 2026 22:54

Merge branch 'v6.0.4' of github.com:ergoplatform/ergo into v6.0.5

88fdaf7

Merge branch 'v6.0.5' of github.com:ergoplatform/ergo into v6.0.5

7589493

Document the API query logger in logback.xml

e5844b1

Commented-out logger element so the switch is discoverable.

a-shannon mentioned this pull request Aug 6, 2026

NiPoPoW: align proof construction, length-prefixed parsing, and validation #2461

Open

github-actions Bot mentioned this pull request Aug 7, 2026

Add info on refactor(api): establish Scala and RUST API families (#233): docs/roadmap.md ergoplatform/ergodocs#506

Closed

Merge pull request #2456 from Ergologica/feature/log-api-queries-1909

ea00db7

Log API queries at DEBUG level

jozanek reviewed Aug 11, 2026

View reviewed changes

jozanek requested changes Aug 11, 2026

View reviewed changes

This was referenced Aug 11, 2026

Candidate for 6.0.4 release #2293

Merged

Make ExtraIndexer checkpoints reorg-safe #2465

Closed

a-shannon and others added 25 commits August 18, 2026 22:38

Fix ExtraIndexer checkpoint recovery

4d93c8a

refactor: tighten extra indexer test seams

ed971fa

ci: rerun integration tests

ac26b44

fix: stop only ExtraIndexer on rollback failure

bcfe56b

Remove redundant block transaction filter

02cfd04

Retrigger CI after DeepRollBackSpec timeout

572ca8e

refactor: restore v6.0.5 ExtraIndexer history wiring

994e582

fix: keep deferred ExtraIndexer catch-up retry

93c9302

refactor: restore indexed contract template storage

e3178cb

refactor: restore indexed address storage

0f9862f

refactor: restore indexed token storage

5d434e4

refactor: restore v6.0.5 indexer state

12b247e

refactor: restore v6.0.5 history storage

eb4118a

refactor: restore v6.0.5 full block processor

077985c

test: restore non-AD history specification

02923ec

test: restore ExtraIndexer chain generator

8edecb1

test: keep deferred catch-up regression

a0e936e

test: keep deferred catch-up test seam

cfd6eae

test: restore history storage specification

af79298

test: clarify deferred catch-up fixture

458af20

Update comment for clarity on fork state

4130b6b

Clarify comment regarding state after headers-only fork.

Merge branch 'master' of github.com:ergoplatform/ergo into v6.0.5

4aa34ff

Merge pull request #2476 from a-shannon/fix/extra-indexer-catch-up-retry

fe8f2e4

Resume deferred ExtraIndexer catch-up without reindexing

adressing review comments

5f0e92a

scrypto updated to 3.1.1, sigmasdk to 6.0.6

25ae315

kushti added 2 commits August 25, 2026 00:01

scala 2.13 and http-circe versions update

211ca58

deprecation messages fix

4c43f0e


		private val mempoolCapacity = settings.nodeSettings.mempoolCapacity

		private def withoutTransaction(id: ModifierId): TreeMap[WeightedTxId, UnconfirmedTransaction] = {

Uh oh!

Conversation

kushti commented Jul 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jozanek left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jozanek left a comment

Choose a reason for hiding this comment

Review of the 6.0.5 release candidate

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

odiseusme commented Aug 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

kushti commented Jul 8, 2026 •

edited

Loading