feat(*): Enrich FullNode command-line-options by halibobo1205 · Pull Request #6397 · tronprotocol/java-tron
| logger.error("Trust node is not set."); | ||
| return; | ||
| } | ||
| parameter.setSolidityNode(true); |
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?
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
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
@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 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
changed the title
feat(*): Consolidate SolidityNode into FullNode with --solidity
feat(*): Enrich FullNode command-line-options
- `--solidity`: SolidityNode → FullNode - `--keystore`: KeystoreFactory → FullNode - `db convert`: DBConvert → Toolkit
@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?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters

