RustMinerSystem

Documentation

Inside Fee Configuration

Configure inside fee rules for different coins from the Edit Fee Rate dialog in Service Management, including hot updates, historical version activation, and customer network checks.

Inside Fee Configuration

Inside fee configuration is managed from Service Management - Actions - Edit Fee Rate. Operators can maintain inside fee rules by custom-build CID and coin, so different coins can use different fee-routing settings.

Entry Point

  1. Open Service Management.
  2. Find the target custom service.
  3. Click Actions on that row.
  4. Open Edit Fee Rate.
  5. Select the target coin, then add or edit the inside fee configuration.

Before saving, confirm the target CID, custom name, and coin so the configuration is not applied to the wrong custom build.

How It Takes Effect

After the inside fee configuration is saved, running custom RustMiner clients will hot-update their fee configuration. In normal cases, RustMiner does not need to be stopped, and the customer’s running miners do not need to be restarted.

In other words, miners already running at the customer site should not be interrupted by the backend fee adjustment. RustMiner continues working after syncing the updated fee configuration.

Historical Versions

Pay special attention to version scope: newly saved inside fee configuration applies to the latest version by default.

If the customer is running an older RustMiner version, saving the configuration in Edit Fee Rate is not enough. Use Apply to Historical Versions from the corresponding service’s Actions menu in Service Management, select the historical version the customer is using, and submit it so that older clients use this configuration.

Recommended flow:

  1. Finish the inside fee configuration for the latest version in Edit Fee Rate.
  2. Confirm the RustMiner version currently used by the customer.
  3. If the customer runs an older version, open Apply to Historical Versions.
  4. Select the matching historical version and submit.
  5. Then observe the client behavior and the customer’s upstream pool side to confirm the result.

Network Environment Checks

When adding or editing inside fee configuration, do not only check whether the ratio is correct. You must also consider whether the configuration can actually work in the customer’s network environment.

Check these items carefully:

Check Description
Pool address Whether the customer server can reach the configured pool domain or IP.
Port and protocol Whether the customer’s network, firewall, or hosting policy allows the selected port and TCP/SSL protocol.
DNS resolution If a domain is used, whether DNS resolution is stable in the customer’s environment.
Regional limits Whether the customer’s region has access restrictions, route blocking, or abnormal latency.
Existing customer setup Whether the new inside fee configuration conflicts with the customer’s existing pool, proxy, or network policy.

If the configured target cannot be reached from the customer’s network, the backend may save successfully while the actual inside fee routing still does not work as expected.

Operational Advice

  • Confirm the customer’s RustMiner version before adding or editing inside fee configuration.
  • For older-version customers, remember to run Apply to Historical Versions.
  • Before changing ratio, pool address, port, or protocol, evaluate whether the customer’s network supports it.
  • For important customers or complex network environments, validate the configuration on a small scope before expanding it to all devices.
  • If the customer reports that the configuration did not take effect, first check version activation, network reachability, protocol, and port blocking.