Set the rules. Review the impact. Prepare the community proposal.
Rule draft · unapproved
No approved rule version is connected. This planner creates drafts; it cannot move funds.
Loading programme snapshot…
Loading the observation time and active validator count.
Data source and block
Waiting for programme data.
Set the allocation rules
Equal distribution
Allocation criteria
1 Validator status
Running, non-jailed validators may qualify inside or outside the consensus set.
Being outside the set is not evidence of being offline.
V1 checks jail status and the archived participation criterion below. Current uptime
outside the set is not independently verified.
2 Voting power
Enter a factor from 1.0 to 2.0 in steps of 0.1.
The voting power limit will appear after data loads.
How the limit is calculated
Cap = min(30%, factor × 100% / active validator count).
All active validators count, including programme exclusions. The cap limits
projected total stake, including other delegators. There is no separate minimum or
maximum programme amount per validator.
3 Commission
Whole numbers from 0 to 100. Proposed default: 10%.
Enter a whole-number commission limit from 0 to 100.
4 Upgrade participation
Juno v31 participation within five hours
Archived participation is required. Missing or late evidence needs review; it does
not prove a late software installation.
Review the participation evidence
Loading the archived halt time and observation coverage.
Includes delegated and available JUNO, keeps at least 50 JUNO in reserve and rounds
down to whole hundreds.
Opens a prepared draft on our proposal page. After approval and execution, refresh
the data to include claimed rewards.
Currently delegated — JUNO
Current programme positions
Loading the active and inactive delegation breakdown.
Manual exclusions · none
Exclude a validator by name or address, with a public reason. This changes the rule
proposal.
No manual exclusions in this draft.
Not saved · unapproved
Planned criteria · V2
30-day uptime
Signed blocks during actual active participation, with measurement gaps visible.
Update responsiveness
Stricter deadlines and points for independently evidenced faster participation.
Testnet participation
A proposed fixed UNI-7 active-set bonus with .neta and verified operator linkage. No
extra uptime gate initially.
Governance participation
Own votes on completed proposals, treating every vote option equally and using a
fair historical denominator.
Public infrastructure
Attributed RPC/API and archive service, measured for availability, freshness,
latency and coverage from independent locations.
Community-approved scoring
Every weight or threshold needs a new rule approval. Missing evidence stays
unassessed; duplicate endpoints earn no extra points.
These criteria are not active. The governance window of 20 proposals and infrastructure
observation period of 30 days remain proposals. Relayer contribution is a later option
requiring attribution and useful transfer evidence. No automatic dApp, community or
special-agreement points.
Proposed allocation—JUNO
Receiving validators—— eligible ·
Active set pendingUnallocated funds—JUNO
Set the rules and simulate to see who would receive funds.
This is a target distribution, not an immediate redelegation transaction.
Why target amounts can differ
Targets are the total programme delegation after redistribution. Equal amounts are
reduced where a validator would exceed the projected voting power limit; the remainder
is redistributed. Other delegators’ stake counts towards the limit.
Existing programme delegations are removed before targets are added. Unallocated funds
do not count as bonded stake. Moving inactive positions into the active set can change
its total stake and each validator’s percentage.
Amounts below are rounded to two decimals; expand a validator for exact values.
Calculations and downloads retain all six decimals. Projected shares estimate voting
power for a fixed validator set.
Scroll horizontally to compare all six columns.
Current and proposed programme delegations. Rounded display; exact amounts and
eligibility evidence are available in each row.
Validator / reason
Current JUNO
Target JUNO
Change JUNO
Total JUNO after allocation All delegators
Stake share Current → projected
Set the rules and simulate to compare allocations.
The previous policy planned 15 million JUNO, distributed proportionally to
committee-assigned points across seven categories, up to 120 points. These historical
scores do not determine this simulation. Current balances are read from the chain.
Publish proposal opens the prepared draft on our proposal page for review. Nothing is
submitted automatically; on-chain approval and execution remain separate steps.
Later: update allocations under approved rules
An allocation update needs a verified on-chain rule version and a separate execution
proposal. Changed criteria or exclusions require new rule approval first.
Unavailable: on-chain approval verification, programme authority and transaction-level
redelegation checks are not connected yet.