Goal
Qualify three independently controlled operators for one bounded seven-day
validator pilot. Five is the broader cohort target and ten is the recruitment
target. Multiple nodes under one person's control count once.
Current Status: September 13, 2026
Preview.20 combines the versioned token-limit correction and reliable delivery
of completed empty responses. In an app on .17 or newer, use Check for updates,
then Update and restart. Older binaries need one manual upgrade. Keep your
configuration, pending evidence and existing node identity; do not re-enroll.
App updates do not replace externally managed systemd services or Docker
containers.
Production Core is d606e4d8 / Alembic 0042. The 05:12 UTC snapshot showed
nine fresh heartbeats: three .20, four .13, one .15 and one .18. There were zero
finalized independent-operator approvals. This is a dated snapshot, not a live
count or a claim that every operator is controlled by AIPG. Check the
network page for current aggregate status.
The .20 release passed four-platform builds, clean installs and exact-source
artifact/provenance verification. All three owned services upgraded in place.
Fresh ordinary, token-limit v2 and empty-visible-response reports passed
independent signature, assignment and commitment checks with no economic rows.
Failed worker verdicts were preserved. These tests prove delivery, not exact
model identity or independent operator control. The public download page now
serves .20.
The evidence lane remains unpaid and non-punitive. The maintainer approved a
revised first-pilot budget of at most 100,000 AIPG over seven days, capped at
25,000 AIPG per reviewed independent operator, on September 13. This replaces
the earlier 4,000/1,000 budget; it is not an additional pool. These are token caps,
not guaranteed individual payments or dollar returns.
Revised budget and allocator change.
The matching allocator update still requires CI review and deployment.
The earning period has not started. No campaign is active. We still need
three qualified independent operators on the selected release, frozen membership
and published start/end dates. Recipient consent and verified transfers remain
required before payment. Existing participation is not retroactively covered by
this budget. Correctly reporting failed tasks can be useful compensated work;
majority agreement alone is not the acceptance criterion. Evidence does not
change worker routing, payouts or penalties.
Already Running?
Keep your existing configuration and val_* ID. Do not re-enroll, delete keys,
or restart qualification to troubleshoot. Core preserves the observed history
when a first maintainer review is attached. Older comments describing a mandatory
fresh clock after intake no longer describe the current implementation.
If you already supplied your ID, platform, region and operating details, do not
send them again. We will reuse them and ask only for missing control information.
An independence declaration is an intake claim; confirming control of the node
and checking shared practical control are separate review steps.
The public status page distinguishes online state, accepted evidence, time and
coverage gates, and maintainer review. An offline node needs connection recovery,
not a replacement identity. After its recent-heartbeat collection matures, the
coverage calculation uses a rolling 72-hour window so an old outage does not
require indefinite catch-up. Missed samples are not fabricated or backfilled.
New Operators
No GPU, Google/GitHub login, wallet extension, funds or pasted private key is
needed. After your confirmation, setup creates a dedicated local signing identity
and obtains a validator-only API key. Never use a funded wallet's private key.
Follow the quickstart for your platform. On Windows, extract the verified ZIP,
double-click aipg-validator.exe, choose 8. Open local operator app, and use
Set up node. If already configured, use Start validator. Check acknowledged
registration and heartbeat, then accepted evidence; normal assignment cooldowns
do not mean setup failed. No PowerShell is required for this menu/app path.
Windows remains unsigned and macOS is not notarized. Verify the exact release
checksums and GitHub provenance and follow the documented platform warnings.
Stop stops the app-managed runtime without deleting identity. Closing only
the browser tab does not stop it. Avoid starting duplicate copies.
Intake
For a first contact, share only:
- Public
val_* ID, if already running.
- Community handle, platform and broad region.
- Residential/datacenter/cloud hosting class and expected online hours.
- Whether you independently control the host, signing identity and operating
decisions, including any control shared with AIPG or another validator.
Send shared-control details privately to the sole project maintainer through
Discord. Never post API/private keys, seed phrases,
configuration files, account IDs, wallet addresses, signatures, IPs, private
local-app URLs, prompts, responses or unredacted diagnostics.
Qualification And Pilot
- Confirm control of the existing node without sharing credentials and review
practical independence. The documented signed control check is coordinated
with the maintainer; registration alone is not independence proof.
- Reuse the existing observed window: at least 72 hours, at least 80% sampled
heartbeat coverage, a fresh heartbeat, completed work and accepted signed
evidence in the applicable window. Review delays do not reset that history.
- Finalize the existing candidate through Core's fresh, digest-bound review.
Incomplete gates remain incomplete; do not weaken them or restart the clock.
- With three qualified independent operators, freeze one seven-day pilot's
membership, release policy, acceptance criteria, start and end. Publish its
pass/fail/inconclusive result instead of repeatedly extending it.
The three first-party services share an operator and hypervisor and cannot fill
independent seats. The approved compensation budget pays reviewed useful
participation once the pilot starts, not majority agreement or accusations.
Increasing its limits requires another explicit budget decision.
This broader cohort issue closes when at least five recently participating,
verified-independent groups are present and shared probe groups obtain at least
three reviewed independent votes. The initial supported-beta milestone remains
three operators and the bounded pilot, not five registrations.
Goal
Qualify three independently controlled operators for one bounded seven-day
validator pilot. Five is the broader cohort target and ten is the recruitment
target. Multiple nodes under one person's control count once.
Current Status: September 13, 2026
ghcr.io/aipowergrid/validator:v0.1.0-preview.20(x64/ARM64).Preview.20 combines the versioned token-limit correction and reliable delivery
of completed empty responses. In an app on .17 or newer, use Check for updates,
then Update and restart. Older binaries need one manual upgrade. Keep your
configuration, pending evidence and existing node identity; do not re-enroll.
App updates do not replace externally managed systemd services or Docker
containers.
Production Core is
d606e4d8/ Alembic0042. The 05:12 UTC snapshot showednine fresh heartbeats: three .20, four .13, one .15 and one .18. There were zero
finalized independent-operator approvals. This is a dated snapshot, not a live
count or a claim that every operator is controlled by AIPG. Check the
network page for current aggregate status.
The .20 release passed four-platform builds, clean installs and exact-source
artifact/provenance verification. All three owned services upgraded in place.
Fresh ordinary, token-limit v2 and empty-visible-response reports passed
independent signature, assignment and commitment checks with no economic rows.
Failed worker verdicts were preserved. These tests prove delivery, not exact
model identity or independent operator control. The public download page now
serves .20.
The evidence lane remains unpaid and non-punitive. The maintainer approved a
revised first-pilot budget of at most 100,000 AIPG over seven days, capped at
25,000 AIPG per reviewed independent operator, on September 13. This replaces
the earlier 4,000/1,000 budget; it is not an additional pool. These are token caps,
not guaranteed individual payments or dollar returns.
Revised budget and allocator change.
The matching allocator update still requires CI review and deployment.
The earning period has not started. No campaign is active. We still need
three qualified independent operators on the selected release, frozen membership
and published start/end dates. Recipient consent and verified transfers remain
required before payment. Existing participation is not retroactively covered by
this budget. Correctly reporting failed tasks can be useful compensated work;
majority agreement alone is not the acceptance criterion. Evidence does not
change worker routing, payouts or penalties.
Already Running?
Keep your existing configuration and
val_*ID. Do not re-enroll, delete keys,or restart qualification to troubleshoot. Core preserves the observed history
when a first maintainer review is attached. Older comments describing a mandatory
fresh clock after intake no longer describe the current implementation.
If you already supplied your ID, platform, region and operating details, do not
send them again. We will reuse them and ask only for missing control information.
An independence declaration is an intake claim; confirming control of the node
and checking shared practical control are separate review steps.
The public status page distinguishes online state, accepted evidence, time and
coverage gates, and maintainer review. An offline node needs connection recovery,
not a replacement identity. After its recent-heartbeat collection matures, the
coverage calculation uses a rolling 72-hour window so an old outage does not
require indefinite catch-up. Missed samples are not fabricated or backfilled.
New Operators
No GPU, Google/GitHub login, wallet extension, funds or pasted private key is
needed. After your confirmation, setup creates a dedicated local signing identity
and obtains a validator-only API key. Never use a funded wallet's private key.
Follow the quickstart for your platform. On Windows, extract the verified ZIP,
double-click
aipg-validator.exe, choose 8. Open local operator app, and useSet up node. If already configured, use Start validator. Check acknowledged
registration and heartbeat, then accepted evidence; normal assignment cooldowns
do not mean setup failed. No PowerShell is required for this menu/app path.
Windows remains unsigned and macOS is not notarized. Verify the exact release
checksums and GitHub provenance and follow the documented platform warnings.
Stop stops the app-managed runtime without deleting identity. Closing only
the browser tab does not stop it. Avoid starting duplicate copies.
Intake
For a first contact, share only:
val_*ID, if already running.decisions, including any control shared with AIPG or another validator.
Send shared-control details privately to the sole project maintainer through
Discord. Never post API/private keys, seed phrases,
configuration files, account IDs, wallet addresses, signatures, IPs, private
local-app URLs, prompts, responses or unredacted diagnostics.
Qualification And Pilot
practical independence. The documented signed control check is coordinated
with the maintainer; registration alone is not independence proof.
heartbeat coverage, a fresh heartbeat, completed work and accepted signed
evidence in the applicable window. Review delays do not reset that history.
Incomplete gates remain incomplete; do not weaken them or restart the clock.
membership, release policy, acceptance criteria, start and end. Publish its
pass/fail/inconclusive result instead of repeatedly extending it.
The three first-party services share an operator and hypervisor and cannot fill
independent seats. The approved compensation budget pays reviewed useful
participation once the pilot starts, not majority agreement or accusations.
Increasing its limits requires another explicit budget decision.
This broader cohort issue closes when at least five recently participating,
verified-independent groups are present and shared probe groups obtain at least
three reviewed independent votes. The initial supported-beta milestone remains
three operators and the bounded pilot, not five registrations.