Skip to content

feat(*): Enrich FullNode command-line-options#6397

Merged
kuny0707 merged 1 commit intotronprotocol:release_v4.8.1from
halibobo1205:feat/command_opt
Aug 13, 2025
Merged

feat(*): Enrich FullNode command-line-options#6397
kuny0707 merged 1 commit intotronprotocol:release_v4.8.1from
halibobo1205:feat/command_opt

Conversation

@halibobo1205
Copy link
Contributor

close #6218.

@kuny0707 kuny0707 moved this to In Review in java-tron Jul 11, 2025
@kuny0707 kuny0707 linked an issue Jul 11, 2025 that may be closed by this pull request
@halibobo1205
Copy link
Contributor Author

TODO: SolidityNode has been replaced by FullNode --solidity. CI testing scenarios(buildkite/interface-status-test-in-docker)need to be adapted accordingly.

logger.error("Trust node is not set.");
return;
}
parameter.setSolidityNode(true);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will remove this parameter.setSolidityNode(true); effect the respected http/rpc service start?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make sure you check all related sub-class not depend this value

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

parameter.setSolidityNode(true) is replaced by --solidity.

Image

@Sunny6889
Copy link
Contributor

I have a question:
In existing FullNode with config node.http.solidityEnable with default is true, HTTP API /walletsolidity/... will return solidity info. Same asnode.rpc.solidityEnable for RPC request with protocol.WalletSolidity.
It seems we don't need SolidityNode at all, it only confuses users. Thus I think we don't need to support SolidityNode related features.

@halibobo1205
Copy link
Contributor Author

@Sunny6889 Java-tron's support for SolidityNode is still quite valuable, particularly for accelerating historical synchronization. By configuring trusted nodes, SolidityNode can skip the computationally expensive signature verification process, resulting in roughly a 33% reduction in synchronization time.

@Sunny6889
Copy link
Contributor

@Sunny6889 Java-tron's support for SolidityNode is still quite valuable, particularly for accelerating historical synchronization. By configuring trusted nodes, SolidityNode can skip the computationally expensive signature verification process, resulting in roughly a 33% reduction in synchronization time.

@halibobo1205 For SolidityNode it only sync soliditied blocks? Could you share more about where the logic control it?

@halibobo1205 halibobo1205 changed the title feat(*): Consolidate SolidityNode into FullNode with --solidity feat(*): Enrich FullNode command-line-options Jul 17, 2025
- `--solidity`: SolidityNode → FullNode
- `--keystore`: KeystoreFactory → FullNode
- `db convert`: DBConvert → Toolkit
@halibobo1205
Copy link
Contributor Author

@Sunny6889 Java-tron's support for SolidityNode is still quite valuable, particularly for accelerating historical synchronization. By configuring trusted nodes, SolidityNode can skip the computationally expensive signature verification process, resulting in roughly a 33% reduction in synchronization time.

@halibobo1205 For SolidityNode it only sync soliditied blocks? Could you share more about where the logic control it?

@Sunny6889
image

@kuny0707 kuny0707 merged commit 9247853 into tronprotocol:release_v4.8.1 Aug 13, 2025
7 checks passed
@github-project-automation github-project-automation bot moved this from In Review to Done in java-tron Aug 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Enrich FullNode command-line-options

5 participants