Use AntGain only on devices and networks you are allowed to share. Keep normal security protections in place and avoid unnecessary network exposure when troubleshooting.
Permission first. Use only devices and networks you may share.
Check before changing. Start with what the device and network actually show.
Narrow changes. Do not weaken protections to appear online.
Illustration of owner control and safe network operation. This is not a security scan.
Safety principles
Start with permission, protection, and the smallest safe change.
Use only devices and networks you are allowed to share, preserve existing protections, and keep troubleshooting changes narrow and reversible.
Use only networks and devices you are allowed to share
Before enabling bandwidth sharing, confirm that you control the device and are permitted to use the connection for this purpose under the network provider, workplace, school, hosting or other applicable rules.
Do not weaken security just to make a node appear online
An offline indicator is not proof that inbound ports, UPnP, firewall exceptions or other exposure changes are required. Start with supported software, normal connectivity and authenticated device state.
Keep account and node details private
Keep account identifiers, node identifiers, IP addresses, tokens, balances, and traffic details private. Use your account for your node and account details.
Safe network use
Do not turn a network symptom into a security shortcut.
Device state and network topology can help with troubleshooting, but they do not guarantee compatibility, traffic, or earnings.
Network-use guidance
Online status means a node is available to AntGain. It does not guarantee traffic or earnings.
NAT type, public IPv4 availability, and IPv6 availability describe the network. They do not by themselves determine traffic or earnings.
Do not bypass network-provider controls, captive portals, access restrictions or security policy in order to operate a node.
Use the current AntGain release path for supported software rather than relying on old installers or instructions copied from third parties.
If a deployment model needs a network or security change, follow current product-specific documentation and keep the change as narrow as possible.
Availability is not an earnings promise
Traffic and earnings vary with demand and successfully recorded activity. Being online does not guarantee income.