The Logic Of Gas Payment Triggering Contract Task Execution

MMMBSC Management

Administrator
Staff member
πŸ—£Flow triggered by interaction between PH donation order server information and the smart contract:

πŸ‘‰1: The user PH creates an order request to trigger server data synchronization to the contract.
This operation instruction triggers the system GAS address to pay the fee.
(If there are not enough 2% Mavro funds and points, order creation will not succeed)

πŸ‘‰2: Prepayment matching order: After the system pays GAS, the general contract creates a sub-contract and matches the order.

If the network is congested at this time, the GAS payment transaction will be postponed indefinitely, and the completion of the contract will be postponed. The order will not be matched as scheduled.
If the GAS transaction fails, PH order creation will be marked X. There is no deduction of 2% of funds and points (the logic is optimized on June 22). Users recreate PH donation orders.

πŸ‘‰2: Matching order for the final payment:
The server sends a request to make the system pay for GAS. After the system pays the GAS, the general contract creates a sub-contract and matches the order. If the network is congested at this time, the GAS payment transaction will be postponed indefinitely, and the completion of the contract will be postponed. The order will not be matched as scheduled.

The only difference between the final payment and the prepayment: if the GAS transaction fails, the server automatically submits the request to enter the GAS payment queue. It loops indefinitely until the GAS payment successfully triggers the contract execution task. The order will not be matched as scheduled.

πŸ‘‰3: User pays for matching orders: After payment to the sub-contract is completed, click to confirm payment
(After the sub-contract receives the funds, the system allows the user to click the confirm payment button)
The user's request to confirm the payment triggers the system GAS address to pay the fee.
After the system pays GAS, the sub-contract funds are transferred to the 8508 general contract, and the user order is completed. At this point, the contract code starts accounting and calculates the user's revenue and bonus.

If the network is congested at this time, the GAS payment transaction will be postponed indefinitely, and the completion of the contract will be postponed. The order cannot be confirmed on schedule.
If the GAS transaction fails, the server automatically submits the request to enter the GAS payment queue. It loops indefinitely until the GAS payment successfully triggers the contract execution task. The order cannot be confirmed on schedule.

πŸ‘‰4: The PH order expires and unfreezes: The server requests information to trigger the system to pay GAS. The completion of payment of GAS triggers the contract to release the order.

If the network is congested at this time, the GAS payment transaction will be postponed indefinitely, and the completion of the contract will be postponed. The order cannot be released as scheduled.
If the GAS transaction fails, the server automatically submits the request to enter the GAS payment queue. It loops indefinitely until the GAS payment successfully triggers the contract execution task. The order cannot be released as scheduled.


πŸ—£ FLOW TRIGGERED BY INTERACTION BETWEEN GH WITHDRAWAL ORDER SERVER INFORMATION AND CONTRACT:

πŸ‘‰1: User GH creates an order request to trigger server data synchronization to the contract.
This operation instruction triggers the system GAS address to pay the fee.
(If there is not enough 1:1 linked funds, the order creation will not succeed)

πŸ‘‰2: GH withdrawal matching order: After the system pays GAS, the general contract creates a sub-contract and matches the order (1:1 matching funds are deducted when matching the order, if the related funds are insufficient at this time, the order cannot be matched successfully and marked X)

If the network is congested at this time, the GAS payment transaction will be postponed indefinitely, and the completion of the contract will be postponed. The order will not be matched as scheduled.
If the GAS transaction fails, the server automatically submits the request to enter the GAS payment queue. It loops indefinitely until the GAS payment successfully triggers the contract execution task. The order will not be matched as scheduled.

πŸ‘‰3: 8508 contract payment funds: After the GH order matching is completed, the system triggers the GAS payment, and the GAS completion triggers 8508 payment funds to reach the sub-contract. The subcontract automatically transfers funds to the user's address.

If the network is congested at this time, the GAS payment transaction will be postponed indefinitely, and the completion of the contract will be postponed. The order will not be paid as scheduled.
If the GAS transaction fails, the server automatically submits the request to enter the GAS payment queue. It loops indefinitely until the GAS payment successfully triggers the contract execution task. The order will not be paid as scheduled.
 
At first it was congestion of etheteum network which we were ask to increase our minimum PH order to $100 instead $10 to resolve the conjestion problem.instead of informing early that the delay in transaction execution was as a result of low gas fee .now they are talking of low gas fee .this people are just playing with us.they have gone .how come uptill no update concerning the so called technicians working on the system
 
Top