Everything worth asking

For traffic your device actually carries and completes, metered per MB at 10 points per MB. Uptime alone earns nothing — a device that is switched on but never receives a connection earns zero points that day. The running total for the day is shown as "Today" on the app's overview screen.

Traffic carried between 19:00 and 21:00 counts double, at 20 points per MB. The rest of the day is a flat 10 points per MB. The same volume of traffic is worth twice as much inside that window, so it pays to be online and stable through those two hours.

No. Scheduling allocates traffic per exit IP. Devices behind the same broadband line or the same SIM share that IP's allocation, and the total is split between them rather than multiplied. Scaling up means a second line or a second SIM — not more handsets on the same network.

Usually one of two reasons. Either the device is new and still ramping up — low or zero connection counts over the first few days are normal, so give it one to three days online — or the exit network is not on the eligibility list (datacentre or public-cloud IPs, overseas ISPs, or lines whose ownership cannot be resolved), in which case the device stays online but is never selected. Home broadband and mobile data are far more likely to be scheduled.

Scheduled volume ramps up gradually rather than starting at full allocation. Low connection counts and earnings in the first few days are expected. Keep the device online, on mains power and on a stable network during that period, and avoid reinstalling the app or switching networks back and forth.

In hourly windows. Traffic lands in the current hour's settlement window; once that window closes, a scheduled job on the control plane totals it up and writes it to the settlement ledger. That is why traffic you just carried does not show up in your balance until the hour is over.

It is a runtime setting rather than a fixed number published here; check the rate shown on the app's withdrawal screen at the moment you submit a request. The converted amount is paid out by Alipay transfer — the full flow is on the earnings page.

Any Android handset on 7.0 or later, any brand. No root and no custom ROM required. iOS is not supported, so an iPhone cannot take part. Xiaomi, Huawei and similar Chinese ROMs need their background restrictions relaxed — see the next answer.

Two kinds. First, the overlay permission, used for the small status window: tap "Enable" on the app's settings screen, allow it in system settings, then come back. Second, autostart plus a battery-optimisation exemption, so the OS does not kill the app in the background. On Xiaomi: Settings → Apps → Manage apps → Tianqing → enable Autostart and set the battery saver policy to "No restrictions". On Huawei: Settings → Apps → App launch → Tianqing → turn off "Manage automatically", then allow auto-launch, secondary launch and background activity. Until the checklist is complete, the Start button stays disabled and a red note at the bottom says how many items are outstanding.

Yes — both Wi-Fi and mobile data are supported. But the mobile-data switch is off by default; turn on "Allow running on mobile data" in the app's settings screen. Once enabled it will keep consuming data, and the cost is yours to bear. If you are unsure how much allowance is left, leave it off.

It is strongly recommended, along with turning off battery saver. A flat battery, or a power-saving policy killing the app in the background, drops the connection and cuts off any traffic in flight — and no points accrue while it is offline.

Emulators, cloud phones and devices on datacentre networks are explicitly prohibited: they are never scheduled and earn nothing. Public-cloud IPs, overseas ISPs and lines whose ownership cannot be resolved are likewise kept out of the dispatch pool.

Almost always carrier eligibility. Only exits on China Telecom, China Unicom, China Mobile, China Broadnet (CBN) or CERNET enter the dispatch pool. Datacentre IPs (cloud servers), overseas ISPs and unidentifiable lines are excluded, and the device is flagged isp_error — which looks exactly like "online but never selected". Move it to home broadband or mobile data and the policy converges through gateway heartbeats within roughly 15 seconds.

A bound phone number and completed identity verification. Until both are done the withdrawal entry is only a prompt telling you what is missing. You also need to enter an Alipay receiving account and the payee's real name. Verification attaches to the phone account, not to a device.

By Alipay transfer to the receiving account you bound. A new request starts as awaiting review (pending), moves to paying out (paying) once an administrator approves it, and becomes paid (success) when Alipay confirms the transfer.

Alipay checks the name and refuses a mismatch outright. The request ends as a failed payout and the frozen points are returned in full. Enter the name exactly as it appears on the ID document — a wrong name is not caught at submission, it is rejected at payout time.

Straight back to your balance. Points are frozen when you submit. Once an administrator rejects the request (rejected) or Alipay explicitly reports a failure (failed), the frozen amount is returned in full and you can correct the details and submit again. The refund is idempotent per request, so it can neither double up nor go missing.

That is deliberate. When the network times out or Alipay has not returned a conclusive result, the request stays on "paying out" until an authoritative answer arrives, and only then resolves to success or failure. The system never guesses, and never pays twice because it was unsure. Each request maps to exactly one merchant transfer order number, and retries reuse that same number, so a double payment is not possible. The reviewer, the transfer order number, the final state and any failure reason all go into the audit log and can be traced request by request.

Alipay transfers have a floor of CNY 0.1 per transaction, so anything below that cannot be paid out. Your withdrawable balance is the settled balance minus anything in flight (awaiting review plus paying out) minus what has already been paid.

As an exit carrying proxy traffic for customers. Outbound requests are matched against a domain blocklist in real time at the gateway; a match is refused on the spot — the client receives TARGET_DENIED and the request is not retried on another device. The blocklist is maintained centrally and broadcast to the gateways, so a new rule takes effect immediately. The first batch of 101 rules is already live.

Not to run a node, but yes to withdraw. Verification attaches to the phone account rather than to a device, so doing it once covers every device under that account.

We do not record the destinations or contents of the traffic relayed through your device. To pay you, the system meters how many MB your device carried and writes that into hourly settlement windows — what is stored is volume and time range, so earnings can be reconciled, not a list of sites. The domain blocklist works by matching and refusing at the gateway in real time, which likewise does not depend on keeping access records.

On servers inside mainland China. Device state changes, blocks, blocklist edits, eligibility-policy changes, legal-document releases, and withdrawal review and payout all go into the audit log and can be traced item by item.

They are the User Agreement, the Privacy Policy and the Network Exit Authorisation. Together they form a mandatory consent gate on first launch — the app cannot be used without accepting them. Each document is hashed server-side as content_sha256 and verified for integrity by the client. A new release takes effect immediately, and devices that have not accepted the current version receive CONSENT_REQUIRED and must confirm again before they can keep running.

Yes. The app runs in the background with just a small floating status window on screen. Carrying traffic does consume upstream bandwidth continuously, though, so gaming or video calls on the same network may suffer — which is why a spare handset on spare bandwidth is the right setup.

Tap Stop in the app and confirm. The device disconnects, stops accepting new connections and pauses its running statistics; you can start again at any time. Points already settled are unaffected.

Live connections are cut, and the device rejoins scheduling under its new exit IP once it comes back. The new network has to pass carrier eligibility too — move onto a datacentre or public-cloud network and it will stop being selected. The policy is not broadcast; gateways re-read it on heartbeat, converging within roughly 15 seconds.

Sign in on every device with the same phone number — earnings are aggregated by phone number, so even a multi-device setup needs only one account. Devices without a bound number still run, but the overview screen then counts only that handset; once bound it shows the combined total across all your devices. Remember that devices sharing one exit IP split the earnings rather than adding them up.