SUNPHI — NODE OPERATOR RULES V1
Policy identifier: wander-owner-admission-v1

Admission is controlled by the network owner. The owner reviews identity, authority,
contact and common control before approving an operator. Approval is not a promise
of payment, voting allocation, independence from the owner or financial return.

An operator must be a named individual or identifiable company, provide truthful
information and consent to publication of its name and aggregate node/gateway counts.
All servers under common control must use the same operator group. Companies
cannot obtain extra independent-operator status by submitting additional machines.
Identity review reduces impersonation; it cannot guarantee absence of collusion.

Public registry: owner name and aggregate registered node/gateway counts, with
removed nodes distinguished when applicable. Initial owner label: SunPhy.
The public registry does not expose node addresses, device names, hosting providers,
physical locations, individual node keys or placement. Placement remains in the
owner's authenticated administration. Registry privacy does not make public gateway
endpoints or network routing information inherently secret.
Private review: country, company registration details, contact, website, node key,
verification contact, review notes and evidence references. Do not upload
passports, biometric data, passwords, wallet backups or any private signing keys.

The operator protects its keys and durable journal, uses an approved compatible
release, avoids cloning a live signer, accurately declares physical failure domains,
reports compromise and cooperates with investigation. Ordinary offline periods,
retry delivery, client errors and unproven complaints are not proof of bad intent.

An approval prepares a restricted connection. The node must verify certified history
and prove possession of its own key. Certified registration initially means standby.
Active voting assignment requires a separate certified membership transition.

The owner may reject or revoke admission with a recorded reason. A revocation
decision takes effect for future approval immediately; removal of active voting
authority must be finalized by the existing membership protocol. If required quorum
or replacement capacity is missing, the result remains pending/blocked. The owner
cannot label a pending removal complete or lower safety checks to force it through.
Revocation does not confiscate tokens or give the owner wallet signing keys.

The operator can seek review through its verification contact and agent@sun-phi.com.
Status and audit records distinguish owner decisions from actual network execution.
For current rollout limits see https://network.sun-phi.com/#network-status .