triggerConstantContract

[Mihail-source-arch]

Good afternoon, friends. Could you please tell me if it is possible to run "triggerConstantContract" on multiple transactions at the same time? I need to run the first transaction, which will change the data in the smart contracts, and then, in the same thread, take into account all the changes made by the previous transaction, and get the new values by sending another transaction. I understand that this is not possible in the standard API. Could someone please tell me which file in the java-tron source code handles and calculates "triggerConstantContract"? I'll try to dig around myself, and maybe I can rewrite this function to suit my needs. Thanks everyone, and sorry if I'm asking a silly question.

[halibobo1205]

Hi there,
Here's what you need to know:

About triggerConstantContract:
triggerConstantContract is a read-only call that simulates contract execution without broadcasting to the network. It doesn't actually modify the on-chain state, which is why you can't chain multiple state-changing operations this way.

Regarding the source code:
In the java-tron repository, look for:

• org.tron.core.services.http.TriggerConstantContractServlet - handles HTTP requests
• org.tron.core.actuator.VMActuator - contract execution actuator

Hope this helps! Feel free to ask if you need more specific guidance.

[yanghang8612]

Requests to triggerconstantcontract via HTTP or gRPC will ultimately invoke the triggerConstantContract method in the Wallet, located at Wallet.java#L3038.

We strongly discourage you from modifying and deploying java-tron code without thorough verification, as this may lead to potential problems, potentially affecting node operation or even data corruption.

If you insist on making custom modifications, please conduct a thorough code review and testing.

If you have any questions about the code, we are happy to provide assistance.

[Mihail-source-arch]

Hi there, Here's what you need to know:

About triggerConstantContract: triggerConstantContract is a read-only call that simulates contract execution without broadcasting to the network. It doesn't actually modify the on-chain state, which is why you can't chain multiple state-changing operations this way.

Regarding the source code: In the java-tron repository, look for:

• org.tron.core.services.http.TriggerConstantContractServlet - handles HTTP requests
• org.tron.core.actuator.VMActuator - contract execution actuator

Hope this helps! Feel free to ask if you need more specific guidance.

Thank you so much for the information.

[Mihail-source-arch]

Requests to triggerconstantcontract via HTTP or gRPC will ultimately invoke the triggerConstantContract method in the Wallet, located at Wallet.java#L3038.

We strongly discourage you from modifying and deploying java-tron code without thorough verification, as this may lead to potential problems, potentially affecting node operation or even data corruption.

If you insist on making custom modifications, please conduct a thorough code review and testing.

If you have any questions about the code, we are happy to provide assistance.

Thank you, I will keep this in mind.

[halibobo1205]

By the way, @Mihail-source-arch , in what scenario would you need this kind of operation?

[Mihail-source-arch]

By the way, @Mihail-source-arch , in what scenario would you need this kind of operation?

Good afternoon, I'm afraid it will be difficult to describe this in a few sentences. However, it is very important to me to implement this. I would greatly appreciate any assistance in this matter. Thank you.

[halibobo1205]

@Mihail-source-arch, hi, any updates on this issue?

[Mihail-source-arch]

@Mihail-source-arch, привет, есть ли какие-нибудь новости по этому вопросу?

Good day to you. I'm still working on this issue, and there are no results yet. Unfortunately, I don't have any experience in Java development, so the process is taking longer as I'm learning on the fly. If I achieve success, I will definitely let you know.

[Mihail-source-arch]

Привет, вот что вам нужно знать:

О triggerConstantContract: triggerConstantContract это вызов, доступный только для чтения, который имитирует выполнение контракта без трансляции в сеть. Он фактически не изменяет состояние в цепочке, поэтому таким образом невозможно объединить несколько операций по изменению состояния в цепочку.

Что касается исходного кода: в репозитории java-tron найдите:

• org.tron.core.services.http.TriggerConstantContractServlet- обрабатывает HTTP-запросы
• org.tron.core.actuator.VMActuator- исполнительный механизм исполнения контракта

Надеюсь, это поможет! Не стесняйтесь обращаться, если вам нужны более конкретные рекомендации.

Hi there, Here's what you need to know:

About triggerConstantContract: triggerConstantContract is a read-only call that simulates contract execution without broadcasting to the network. It doesn't actually modify the on-chain state, which is why you can't chain multiple state-changing operations this way.

Regarding the source code: In the java-tron repository, look for:

• org.tron.core.services.http.TriggerConstantContractServlet - handles HTTP requests
• org.tron.core.actuator.VMActuator - contract execution actuator

Hope this helps! Feel free to ask if you need more specific guidance.

Good day to you. Once again I want to thank you for the answers to my question. If possible, please help me with this issue.
For example, in a contract, you can perform multiple internal transactions, and each of them can make changes to the network state. If you simulate the call to such a contract, "triggerConstantContract," it will work correctly, and the intermediate network state between each internal transaction will be saved. Based on this, I conclude that it is theoretically possible to simulate multiple transactions in a single thread to analyze changes in the network. Is this correct? I also understand that "VM.java" is responsible for executing transactions in the "play" function, right? Please let me know if you have any thoughts on this. Thank you very much.

[yanghang8612]

The internal transactions you mentioned are essentially a mechanism that allows a contract to call a method of another contract during execution, which may result in state changes.

Yes, simulating multiple transactions within an independent thread is theoretically possible, but it requires analysis in conjunction with the relevant specific mechanisms. Additionally, it's important to note that nodes are still synchronizing, and completing this task without disrupting normal synchronization poses significant challenges.

The entry point for smart contract transaction execution resides in VMActuator.java, while VM.java handles the interpretation and execution of bytecode.

[Mihail-source-arch]

The internal transactions you mentioned are essentially a mechanism that allows a contract to call a method of another contract during execution, which may result in state changes.

Yes, simulating multiple transactions within an independent thread is theoretically possible, but it requires analysis in conjunction with the relevant specific mechanisms. Additionally, it's important to note that nodes are still synchronizing, and completing this task without disrupting normal synchronization poses significant challenges.

The entry point for smart contract transaction execution resides in VMActuator.java, while VM.java handles the interpretation and execution of bytecode.

Thank you so much for your help with my question. If you can, please tell me if I understand correctly that the network state is stored in "BlockCapsule". If this is not the case, please let me know where the network state is stored.

[halibobo1205]

@Mihail-source-arch Could you clarify what network state means in this context? Are you referring to the state of P2P nodes, or the state data itself?

[Mihail-source-arch]

@Mihail-source-arch Could you clarify what network state means in this context? Are you referring to the state of P2P nodes, or the state data itself?

Good afternoon. I was referring to the status data itself. In other words, when a smart contract transaction is executed in the VMActuator.java file, what variable stores the current network state?