What the developer wrote
Authored by Pablo Greco
Log status of ELIP 203
What changed, and why it matters
This commit adds a single log message that records whether a network feature called ELIP 203 is active when the node starts. It does not change any rules, permissions, or behavior; it only prints a status line for operators to read.
No security action needed; this is an informational logging change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change inserts one LogPrintf() call in AppInitMain() that reports the boolean result of chainparams.GetAcceptUnlimitedIssuances(), which controls acceptance of unlimited issuances under ELIP 203. No logic, validation, or consensus code is modified.
Changed components
src/init.cppInspect captured patch +1 / −0
diff --git a/src/init.cpp b/src/init.cpp
index d8dd3dc..5bb74b4 100644
--- a/src/init.cpp
+++ b/src/init.cpp
@@ -1547,6 +1547,7 @@ bool AppInitMain(NodeContext& node, interfaces::BlockAndHeaderTipInfo* tip_info)
}
LogPrintf("* Using %.1f MiB for chain state database\n", cache_sizes.coins_db * (1.0 / 1024 / 1024));
LogPrintf("* Using %.1f MiB for in-memory UTXO set (plus up to %.1f MiB of unused mempool space)\n", cache_sizes.coins * (1.0 / 1024 / 1024), nMempoolSizeMax * (1.0 / 1024 / 1024));
+ LogPrintf("ELIP 203 is%s active\n", (chainparams.GetAcceptUnlimitedIssuances())?"":" not");
bool fLoaded = false;
while (!fLoaded && !ShutdownRequested()) {
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.