Power consolidation
Source page: https://philipp-payments.pages.dev/history/
Publication text export. Evidence dates and source links are retained below.

Skip to content [https://philipp-payments.pages.dev/history/#main-record] 

How Philipp consolidated power and resources

Record prepared 24 October 2026 Sources & method [https://philipp-payments.pages.dev/history/#method] Download evidence [https://philipp-payments.pages.dev/history/history-evidence.zip] 

01 2022–2023 

Community funding, fee income and control over pooled stake

Community money financed ERIS development. Users supplied the stake behind its delegation and governance influence.

After the rejected 450,000-LUNA request, the revised grant requested 312,500 LUNA to finish the ERIS product portfolio. Its stated budget was $350,000 for salaries, $100,000 for audits, $35,000 for marketing and $15,000 for infrastructure. The grant described a delegation and governance framework among the products the community was funding.

On 20 January 2023 , the 312,500 LUNA reached the grant’s 4-of-5 community multisig , worth $598,925.52 at receipt . The funding terms provided for staged release and vesting against milestones. The accompanying ERIS grant material also published a 10% community-revenue commitment. This was a funded commitment to deliver infrastructure for Terra.

Liquid staking added a second source of power: users’ pooled stake. The ERIS hub holds the native delegation. Its voting operator can cast the hub’s governance ballot, while its allocation decisions affect validators’ stake and commission income. Users retain the economic claim through the derivative token; the hub concentrates the native delegation and its voting route.

By the 24 October 2026 snapshot, the hub delegated 31,977,210.37 LUNA — approximately $1,344,261.58 at that snapshot’s historical reference price. The dated control map below identifies Philipp’s owner permission to change the voting operator and his separate administration over Prop Gauge. The combined position links a fee-generating business to voting weight and validator dependence.

The control is exercised over other people’s capital. The deposits make the hub a large native delegator; the owner decides eligible validators and can replace the voting operator. That gives the operator two different forms of leverage: a route to cast the pooled stake’s chain-governance vote, and discretion over which validators receive the delegation and its commission income.

Consequence 
Community funding supported development; users’ deposits supplied the principal. The operating structure concentrated fees, delegation decisions and the route through which that pooled stake votes.

Record details

The grant receipt, milestone terms, published revenue commitment and 24 October 2026 control snapshot have separate source records and dates.

Supporting records 
Revised grant [https://philipp-payments.pages.dev/history/#event=native-3796] 

Published revenue terms [https://philipp-payments.pages.dev/history/#event=eris-revenue-2023] 

ERIS control map [https://philipp-payments.pages.dev/history/#eris] 

Grant receipt and historical USD [https://philipp-payments.pages.dev/history/#event=receipt-63] 

02 July 2023 

Public liquidity deepened the market for ERIS products

The community supplied capital as well as a development grant.

Native proposal 4736 , submitted on 3 July 2023 and passed, proposed 5 million LUNA for ampLUNA–LUNA and bLUNA–LUNA liquidity: 2.5 million LUNA per liquid-staking product. The instruction amount was worth $3,264,957.03 at submission . The revised proposal explicitly replaced the earlier rejected submission.

For ERIS, deeper ampLUNA liquidity makes its liquid-staking product easier to enter and exit. More use of that product can enlarge the native stake pooled under its operating structure. The grant funded the product; public liquidity supported its market; deposits supplied the stake behind its voting and delegation power. 

Consequence 
Public capital supported infrastructure through which ERIS could earn fees and aggregate stake. The development award and the liquidity allocation served different parts of the same operating position.

Record details

The 5-million-LUNA figure is the passed allocation, valued at submission. It is not a personal payment to Philipp and is not added to the payment total.

Supporting records 
Passed liquidity proposal and value [https://philipp-payments.pages.dev/history/#event=native-4736] 

Earlier rejected submission [https://philipp-payments.pages.dev/history/#event=native-4735] 

03 June–October 2024 

Paid to build TLA, while keeping the keys

Philipp became both a funded developer and the holder of powers that could change the system the board was supposed to oversee.

The TLA development and audit award paid 384,615 LUNA on 7 June 2024 , worth $250,986.08 at receipt . On 9 August , the original ten TLA contracts were deployed with Philipp’s configuration wallet as administrator.

His 12 August 2024 launch proposal stated: “Contract Admin will be transferred to PD Stewardship after 1 month.” It separately stated: “Ownership transferred to PD Stewardship after 3 months.” Those terms described a time-limited developer position followed by institutional control.

On 2 September , administration of all ten contracts moved to Philipp’s wallet. Authority moved between his wallets; Stewardship did not receive it. In the 18 October 2026 inventory, the original ten contracts still named his administrator wallet.

The Treasury shows a separate, equally concrete sequence. On 7 October 2024 , its configuration role was assigned to the board. On 8 October , Philipp’s configuration wallet reassigned that role to itself. Normal board voting therefore coexisted with authority held outside that voting process.

The crucial retained power was the ability to replace contract code. Administration determines who can change the implementation; ownership determines who can exercise the contract’s privileged functions. A board may control routine proposals while another wallet can change the rules under which those proposals operate.

Consequence 
The published arrangement required a handover. The recorded result left Philipp with technical powers outside ordinary collective approval, including the power to change the software enforcing that approval.

Record details

The original ten-contract TLA commitment and the later Treasury are traced separately. The strict post-handover count uses 27 November 2024 as its conservative cutoff.

Supporting records 
Original handover terms [https://github.com/phoenix-directive/docs/blob/7cebbd26048f0e1568a2aed55177090b90788d8b/common_backup/2024-08-12_24385_launching-terra-liquidity-alliance.md#L144-L169] 

Deployments and transfers [https://philipp-payments.pages.dev/handover/] 

8 October Treasury change [https://chainsco.pe/terra2/tx/B71CF351EB8A85620E18821288C35A4C73DD6B43B9751C08E937C8AC9FCEAF2F] 

04 August–October 2024 onward 

PD added recurring inflation income and a second delegation system

Phoenix funding and TLA allocations gave the board influence over both projects and validators.

Proposal 4816 established the Phoenix Directive framework. 4817 introduced three TLA buckets with target reward weights of 10%, 5% and 5%. 4822 introduced a separate Phoenix Treasury Alliance weight of 14%, described in the proposal as allocating 10% of chain staking rewards to PD. 4823 replaced earlier chain/ampROAR allocations with a 5% single-asset bucket.

These are the origins of recurring resource-allocation power : who gets funded, which liquidity earns incentives, and which validators receive the Treasury’s and connectors’ synthetic Alliance delegations. The percentages are the proposal’s specified weights and descriptions, with different activation schedules; they are not amounts to add into a present-day personal ownership share.

ERIS’s pooled-stake voting route was used in that reform. On 10 October 2024 at 10:39:31 UTC , Philipp’s fee account submitted a YES instruction to Prop Gauge for proposal 4823. The successful transaction explicitly records the ERIS hub as voter with 100% YES . This connects the liquid-staking governance channel to the decision replacing earlier allocations with the new single-asset system.

The board used that allocation power. A4–A6, A20 and A21 set up virtual-token staking. Later redelegations include A61, A81–A82, A114–A115, A136, A194–A198 and A218 . A114 directed additional allocations to named validators; A115 explicitly removed all allocations from Strangelove.

By 22 October 2026 , the saved Openfields model estimated 94.75 million LUNA-equivalent of active synthetic staking weight directed through the Treasury and four TLA holders—about 31.7% of its bonded-weight denominator. Several validators depended on these allocations for most of their recorded weight. This is a second channel alongside ERIS’s native LUNA pool.

Ordinary delegation decisions belonged to the board. The power to replace that delegation-controller role remained with Philipp’s registry-owner wallet. His separate administrator wallet could replace the registry’s code. The board-controlled allocation layer therefore sat beneath a retained technical authority.

Consequence 
The same institutional structure could distribute grants and incentives, allocate validator weight, and sustain its own recurring funding. Philipp participated in its collective decisions while retaining separate authority over the implementation.

Record details

The synthetic amount is Alliance staking weight, not 94.75 million withdrawable LUNA. The validator table below preserves native and synthetic allocations in separate columns.

Supporting records 
Foundation framework [https://philipp-payments.pages.dev/history/#event=native-4816] 

TLA buckets [https://philipp-payments.pages.dev/history/#event=native-4817] 

Recurring Phoenix funding [https://philipp-payments.pages.dev/history/#event=native-4822] 

Single-asset reform [https://philipp-payments.pages.dev/history/#event=native-4823] 

Hub YES instruction and native ballot [https://philipp-payments.pages.dev/history/#event=hub-native-vote-58] 

Named allocation beneficiaries [https://philipp-payments.pages.dev/history/#event=board-114] 

Strangelove removal [https://philipp-payments.pages.dev/history/#event=board-115] 

Stake snapshot [https://philipp-payments.pages.dev/history/#event=power-stake-snapshot-20261022] 

Validator dependence table [https://philipp-payments.pages.dev/history/#validator-dependence] 

05 November 2024–March 2025 

Approving benefits for directors and setting conditions for others

Personal allocations, paid governance roles and control over participation developed within the same decision structure.

A43, proposed by Philipp on 5 November 2024, created four permanent locks of 20,750 ampLUNA each for stewardship members. Philipp and MB both voted YES. Philipp’s own allocation was worth $9,338.13 at receipt. A49, proposed by Philipp on 9 November, authorized payments for setting up PD, including 10,000 USDC to his wallet. Philipp and MB again voted YES.

These were beneficiary approvals: people receiving allocations also participated in authorizing them. The transactions identify the recipients and the ballots identify the approvers. The conflict is built into the decision, so the relevant records are the entitlement, disclosure and independent review for each payment.

After the handover period, Philipp’s retained owner authority was used on 18 December 2024 to admit ERIS arbLUNA to voting escrow. Later migrations changed the gauge and incentive manager. The developer retained the means to alter participation while his own products operated inside the system.

In February 2025 , his public statements linked incentive access to roadmaps, social activity, resharing and ecosystem alignment. He invoked PD’s powers to list, delist and change take rates. The WHALE dispute proceeded through an internal proposal, a native community vote and subsequent asset removals. The record therefore contains both the stated conditions and the decisions implementing exclusion.

The asymmetry matters: the same governance network approved benefits for insiders while setting the requirements other participants had to satisfy to keep economic support.

Grants also reached into governance of funded projects . On 20 November 2024 , Philipp explained that obtaining CAPA tokens in exchange for SOLID funding allowed PD to secure CAPA governance and provide liquidity. On 16 January 2025 , he listed the support PD could provide: development grants, audits, launch-token purchases, TLA listing, liquidity acquisition through TLA votes and chain-owned liquidity, integration help, marketing and validator delegations.

This is a package of dependencies. A project seeking funding could also need listing, integration, liquidity and delegation support from the same decision network. Acquiring project-governance tokens in the process extended influence beyond Phoenix’s own board.

Consequence 
Board position carried financial benefits and influence over eligibility. Participants seeking incentives depended on decisions from people who also held funded roles and product interests.

Record details

The WHALE suspension received a native community vote. The register preserves that authorization and the later implementation alongside the beneficiary allocations.

Supporting records 
Beneficiary locks [https://philipp-payments.pages.dev/history/#event=board-43] 

Compensation [https://philipp-payments.pages.dev/history/#event=board-49] 

Philipp on incentive conditions [https://philipp-payments.pages.dev/history/#event=statement-2319] 

Native vote [https://philipp-payments.pages.dev/history/#event=native-4832] 

Asset removal [https://philipp-payments.pages.dev/history/#event=board-121] 

CAPA governance acquired with funding [https://philipp-payments.pages.dev/history/#event=statement-1501] 

Philipp’s list of PD support channels [https://philipp-payments.pages.dev/history/#event=statement-2025] 

06 August–October 2025 

The same people approved payments to themselves

Commercial beneficiaries, governance allies and technical administrators overlapped in identifiable payment decisions.

On 4 August 2025 , Philipp proposed Superbolt P35, “Distribute Treasury” , described as payment of open invoices. He voted YES on his own proposal. The three YES voters were Philipp, MB and Rebel ; each was also a recipient in the distribution.

MB executed the payment on 5 August. It included 45,000 USDC to Philipp — $44,994.60 at execution — and three allocations of 15,000 USDC, approximately $14,998.20 each . The proposal, ballots and transfer are separately preserved. This establishes a commercial relationship among participants who also occupied governance, review or advocacy roles around Phoenix.

On 1 October 2025 , Philipp’s retained TLA registry-owner authority changed the incentive-creation fee recipient from Stewardship to the ERIS fee account . That is a recorded use of retained authority to change who receives a revenue stream. The reconciled stream contains 2,280 LUNA across 228 receipts, worth $159.95 at receipt-time prices .

The financial record also contains separately priced stewardship compensation, project grants, locked capital, invoice payments and protocol fees. These are linked to their actual recipients and approval records in the tables below. The same funds are tracked through each stage rather than counted again when paid onward.

Payments, ballots and retained keys belong in the same account of control. The people benefiting from funded work also participated in approvals, and Philipp retained a separate technical route for changing financial destinations.

Consequence 
The commercial relationship is recorded in transactions. It must be assessed alongside the pair’s governance alignment and the administrator’s power to alter payment rules.

Record details

Superbolt P35 is a company payment decision; the TLA fee-recipient change is a separate registry action. Both are identified by their own approvals and transactions.

Supporting records 
Superbolt P35 [https://philipp-payments.pages.dev/history/#event=beneficiary-approval-2] 

Fee-recipient change [https://chainsco.pe/terra2/tx/DC3118AA7A0A8BEC96AA7006074DF66A83321DEC0CEEDB2015B56AE83D80EB64] 

Payment evidence [https://philipp-payments.pages.dev/evidence/#payments] 

07 2025–2026 

Public funding and treasury positions reinforced Philipp’s products

Funding the software, supplying its capital and steering its rewards overlapped.

Votion received 50,000 USDC in Phoenix funding—$49,994.50 at the receipt times. Philipp had proposed funding ERIS to build a vote aggregator that would take deposits, vote for incentives and compound the proceeds. On 15 September 2025 , he said PF had deposited a majority of funds into Votion and described PF participation as up to 20% of TLA voting power. He subsequently described Votion as about 21% of TLA votes.

On 16 September , he explained that PF had chosen to steer through incentives paid to voters rather than manually voting its locked position. PF helped fund the voting product, supplied it with a treasury position, and also influenced the incentive budget to which it responded. That links software ownership, capital allocation and the reward market.

The investment is also on-chain. Philipp proposed Liquidity Alliance A16 on 21 August 2025 and voted YES. Rose and Vini supplied the other passing votes; MB executed on 25 August. A permanent locked position, originating from 199,999 LUNA converted into arbLUNA, entered Votion. The collective DAO received 107,365.102639 receipt shares . The captured pool configuration charges a 10% compounding fee .

This is a documented related-product investment: Philipp helped approve collective capital entering a product he developed and that charged protocol fees. The collective approvals and continuing collective ownership of receipt shares are part of the same transaction history.

In November 2025 , native proposal 4844 requested 30 million LUNA for protocol-owned liquidity in USDC–ampLUNA and LUNA–ampLUNA pools. It passed. The instruction amount was worth $2,198,802.09 at submission . Its stated purpose included deepening ampLUNA liquidity and strengthening validator alignment.

Creda received a further 210,000 USDC—$210,004.67 at receipt. Estima received its 45,000-USDC kickoff payment—$44,998.65—with another 80,000 USDC remaining conditional in the captured schedule. These grants, treasury deployments and recurring fees are separate economic flows. They show why business interests must be assessed alongside the decisions allocating community resources.

Consequence 
Public resources could support a product at several stages: development funding, deposited capital, liquidity and reward allocation. Each stage gave the product greater importance to the ecosystem and made its operator harder to replace.

Record details

TLA gauge votes allocate liquidity rewards. Native Terra governance votes decide chain proposals. The 20%/21% figures are Philipp’s September 2025 descriptions of the former, not a measurement of his share of native chain votes. Receipt values and proposed capital values are labelled separately.

Supporting records 
Votion grant [https://philipp-payments.pages.dev/history/#event=board-107] 

Proposed vote aggregator [https://philipp-payments.pages.dev/history/#event=statement-2167] 

PF deposits and voting power [https://philipp-payments.pages.dev/history/#event=statement-2973] 

21% statement [https://philipp-payments.pages.dev/history/#event=statement-2976] 

Steering through incentives [https://philipp-payments.pages.dev/history/#event=statement-3314] 

30-million-LUNA liquidity proposal [https://philipp-payments.pages.dev/history/#event=native-4844] 

Creda grant [https://philipp-payments.pages.dev/history/#event=board-190] 

Estima release [https://philipp-payments.pages.dev/history/#event=board-271] 

Actual capital deposit, votes and fee configuration [https://philipp-payments.pages.dev/history/#event=votion-collective-capital-A16] 

08 18 November 2025 

Delegation dependence was invoked against criticism

A financially connected governance participant made the pressure explicit in public.

At 07:00:17 UTC on 18 November 2025 , Rebel replied to a Lion DAO critic:
“Reflect upon the fact that LD validator gets the largest delegation from PF. Don’t bite the hand that feeds you.”
The surrounding exchange concerned PF communication, rewards and what Lion provided in return. Rebel had pointed to the date of Lion’s last repost of PF content and said the delegation should not be treated as free money. The immediate response objected to being held hostage over delegation.

The financial support itself became an argument for restraint in criticism and greater promotional support. This is directly recorded language, not a conclusion drawn from similar voting times. It belongs alongside Rebel’s paid communications role and shared commercial distributions with Philipp and MB.

Rebel also said he did not want Lion’s delegation reduced and did not speak for PF. Philipp later asked both sides to stop attacks. Those statements are preserved in the same extract. The exhibit establishes Rebel’s use of the dependency argument; no instruction from Philipp is assigned to it.

Consequence 
Delegation leverage can operate through intermediaries and public pressure as well as formal allocation decisions. Financially connected advocates can invoke the resources controlled by the governance network.

Record details

Nine native-export messages were rechecked for exact text and Unix timestamps. The public source link, warning, immediate objection and surrounding replies are preserved together.

Supporting records 
Original warning and preserved exchange [https://philipp-payments.pages.dev/history/#event=lion-delegation-pressure-95477] 

Shared Superbolt distribution [https://philipp-payments.pages.dev/history/#event=beneficiary-approval-2] 

Paid ERIS relationship [https://philipp-payments.pages.dev/evidence/#payments] 

09 September–October 2026 

Retained powers were used to restrict participation

Code changes, blacklists and delegation decisions turned control into concrete consequences for users, assets and validators.

On 22 September 2026 , migrations added asset-level incentive exclusion. The owner used the new list and changed the destination for excluded rewards to a PF operations wallet . Some broad exclusions were reversed later that afternoon. On 23 September , Treasury migration administration moved between Philipp’s two wallets .

On 3 October , code 4037 and then 4038 introduced sender-specific restrictions on staking, unstaking and reward claiming . The configured address remained listed until 18 October . Controlled execution of the deployed binary confirms those restrictions; the installation and add/remove transactions are preserved.

These were changes to what participants could do with the system. Removing a particular blacklist entry leaves the administrator’s ability to install or alter such rules in place. Restoring access for an address and surrendering the power to restrict access are different actions.

The separate ERIS delegation route was also exercised. On 9 October , Philipp’s owner wallet removed Ceres from the eligible validator list and rebalanced delegations . Those transactions show how operator discretion can change a validator’s allocation and associated income.

Across the strict original-TLA subset, the preserved record contains 31 operations in 19 successful transactions on seven contracts after the handover cutoff . This includes migrations, registry changes and participation restrictions. The retained powers were repeatedly used.

Consequence 
Philipp could influence the rules of participation through retained TLA authority and validator allocation through the separate ERIS owner role. Both created practical dependence on decisions he could make.

Record details

TLA code changes, Treasury administration and ERIS delegation are separate powers. Each operation is mapped to its contract, sender, timestamp and execution result.

Supporting records 
Exact-binary evidence and all 31 operations [https://philipp-payments.pages.dev/evidence/#authority] 

Treasury admin transfer [https://chainsco.pe/terra2/tx/5202CA47D1B467EA0C2441B3EDF1B40674D8633EC232C0E06F32C7DCC38BF3D3] 

Full dated history [https://philipp-payments.pages.dev/handover/#timeline] 

Ceres removal [https://philipp-payments.pages.dev/history/#event=eris-ceres-remove] 

Delegation rebalance [https://philipp-payments.pages.dev/history/#event=eris-ceres-rebalance] 

10 3–24 October 2026 

A272 would have made Philipp and MB sufficient authority alone

The proposed removal also changed the approval rule, eliminating the need for consent from anyone outside the pair.

Philipp’s A272, submitted on 3 October 2026, combined Vini’s removal with a threshold change from 75% to 60% . With four equal seats and a 75% threshold, Philipp and MB need a third vote. With three equal seats and a 60% threshold, their two votes are sufficient even when the third director votes NO .

Philipp and MB both voted YES. A272 failed. The attempted change is recorded in executable instructions, not inferred from rhetoric. It would have made an independent director’s agreement dispensable while leaving that person nominally on the board.

The pair’s existing relationship is relevant to that effect. In the A1–A289 record, MB voted YES on 251 of the 252 Philipp proposals on which he voted ; one ballot was NO. Of Philipp’s 288 proposals, 36 had no recorded MB ballot. The one NO was on A28 [https://chainsco.pe/terra2/tx/338EEF5869DF3B356439C7E6FF6DFFC1417ED91F309E54B863B95D66FFBD1B07] , which used the wrong contract; MB voted YES on corrected A29 [https://chainsco.pe/terra2/tx/1AD6A450B4B810BF245B3A8BBF0449E82F9A7D8D67B7BE81293A63CD7BCAD816] 5 minutes 10 seconds later. They also participated together in commercial distributions. Their proposed sufficiency must therefore be assessed as the sufficiency of a financially aligned voting bloc.

The later Emergency Supervisor thread continued the removal process. In post #5 , Philipp explicitly linked removal to two-of-three. In post #57 , he offered a temporary undertaking to vote only NO or ABSTAIN, with an exception for onboarding directors. That undertaking concerns his intended use of authority; it leaves the voting permissions in place and makes an exception for choosing the future board.

The structural question survives any finding against an individual director: what arrangement prevents the people who benefit from and implement decisions becoming sufficient authority to approve them without independent consent?

The surrounding payment sequence is exact: Philipp voted YES on A271 to release his Estima kickoff payment on 30 September 2026 . The 45,000 USDC payment occurred on 3 October at 14:47:41 UTC . He created A272 at 15:02:16 UTC , 14 minutes 35 seconds later. His proposed removal case invoked another director’s interested vote. The accountability test must cover his own beneficiary approvals as well as those he criticizes.

Consequence 
The attempted change would combine the pair’s financial and technical position with sufficient board votes. An independent third seat would remain present but lose its ability to require agreement.

Record details

The captured board remains four equal seats with a 75% threshold. A272’s failed status and the separate supervisor proposal are preserved in full.

Supporting records 
A272 and ballots [https://philipp-payments.pages.dev/history/#event=board-272] 

Explicit two-of-three explanation [https://philipp-payments.pages.dev/history/#event=forum-5] 

Temporary voting undertaking [https://philipp-payments.pages.dev/history/#event=forum-57] 

Current proposal text [https://philipp-payments.pages.dev/history/#event=forum-1] 

Estima release vote [https://philipp-payments.pages.dev/history/#event=board-271] 

11 9 October 2026 

Delegation discretion was exercised in an actual validator removal

The owner could change a validator’s economic position without a Phoenix board vote.

On 9 October 2026 , Philipp’s hub-owner wallet removed Ceres from the eligible validator list and then rebalanced native delegations. The recorded rebalance moved 1,680,127.496132 LUNA , worth $76,889.82 at that time. Ceres’s net reduction was 662,828.893153 LUNA—$30,333.88 . That reduction is part of the rebalance, not an additional amount.

This is a concrete use of the owner’s allocation power. A validator’s delegated principal supports its commission income and default governance weight. Eligibility and rebalancing decisions can therefore change both its business position and its role in chain governance.

Consequence 
Delegation is a continuing economic dependency. It can be changed by the controller, so influence over a validator is wider than the ballot cast on any one proposal.

Record details

The removal and rebalance are recorded actions. Private pressure reports are summarized separately.

Supporting records 
Eligible-list removal [https://philipp-payments.pages.dev/history/#event=eris-ceres-remove] 

Rebalance, amounts and USD values [https://philipp-payments.pages.dev/history/#event=eris-ceres-rebalance] 

12 19–24 October 2026 

The missed handover was defended as personal judgment

Philipp’s explanation made his confidence in the board the condition for transferring powers that had been subject to published deadlines.

In forum reply #55, dated 19 October 2026, Philipp said the TLA contracts remained under ERIS administration because ERIS continued to develop, maintain and operate them. He also said concerns about the board made transfer inappropriate in the ERIS team’s judgment.

The 2024 terms specified one month for administration and three months for ownership . His reply identifies no approving decision, authority or date replacing those deadlines with his continuing assessment of the board. The central accountability demand is therefore exact: produce the authorization for retaining and exercising the powers after the stated handover. 

A separate transfer proposal, Amplifier P9 , was recorded as passed on 24 October . Its executable payload contains two administrator changes, covering the hub and CW20-ICS20. At the captured blocks, the hub still named the existing administrator. The payload leaves hub configuration ownership, Prop Gauge administration, Treasury administration and TLA registry ownership outside that transfer.

The history therefore ends with a precise control question, not a title or assurance: which powers have actually moved, to which decision structure, and under what enforceable approval rule? A complete handover needs those authorities enumerated and its execution verified.

Consequence 
The published deadlines were displaced in practice by the administrator’s own judgment. Accountability requires the authorizing record, scrutiny of the uses made of those powers, and a completed transfer that removes the retained control routes.

Record details

P9’s status, two-message payload and contract administrators are recorded at the 24 October snapshot. Later changes can be compared against those preserved records.

Supporting records 
Explanation for withholding control [https://philipp-payments.pages.dev/history/#event=forum-55] 

Actual transfer payload [https://philipp-payments.pages.dev/history/#event=upgrade-proposal-9] 

Remaining voting controls [https://philipp-payments.pages.dev/history/#eris] 

Pressure and economic leverage

Validators report pressure over delegation and governance positions. Preserved evidence includes undelegation threats and threats to withdraw operational support. Reports also describe repeated threats following criticism and pressure to align with proposed governance changes.

| Form of pressure | Conduct reported or recorded

| Delegation | Threatened withdrawal of delegations and pressure on validator participation.

| Operational support | Threatened withdrawal of maintenance or services during governance disputes.

| Criticism and access | Demands to remove criticism, backed by threatened exclusion from interfaces or incentives.

| Governance alignment | Pressure on directors and participants over their positions, including repeated threats following criticism.

Economic dependence gives these threats force. Delegations, incentives, product access and essential services affect whether participants can challenge the people controlling those resources.

Supporting private records are retained. Reporting-source identities, dates, recipients, exact private wording and relay details are not published.

Supporting records [https://philipp-payments.pages.dev/evidence/#pressure] 

What he controlled, how it was used, and who depended on it

These powers reinforce one another. A grant recipient may also need liquidity, listing and integration; a validator may depend on delegation; a director may need the same signers to release legal funds. The table identifies the actual controller and the recorded use at each layer.

| Power or resource | Decision-maker | Mechanism | Recorded use / evidence | Consequence

| Community capital | Terra governance approves allocations; Philipp proposes and implements ERIS/TLA projects | Development awards, public liquidity and recurring Alliance rewards | ERIS grant [https://philipp-payments.pages.dev/history/#event=native-3796] ; 5m-LUNA liquidity allocation [https://philipp-payments.pages.dev/history/#event=native-4736] ; Phoenix recurring funding [https://philipp-payments.pages.dev/history/#event=native-4822] | Public resources finance infrastructure and capital positions around the operator.

| Native stake and chain votes | ERIS hub; owner Philipp; voting operator Prop Gauge | ~31.98m native LUNA in the 24 October snapshot; owner can replace vote operator | Actual hub ballot on Alliance reform [https://philipp-payments.pages.dev/history/#event=hub-native-vote-58] ; Owner/operator powers [https://philipp-payments.pages.dev/history/#eris] | The operator votes pooled native stake; derivative holders do not each have a separate native delegation.

| PD/TLA validator allocation | Board is the ordinary controller; Philipp owns and administers the role registry | ~94.75m active synthetic LUNA-equivalent in the 22 October model | Redistribute to named validators [https://philipp-payments.pages.dev/history/#event=board-114] ; Remove Strangelove [https://philipp-payments.pages.dev/history/#event=board-115] | Allocation affects validator income and weight; the registry owner can replace the allocation authority.

| Validator eligibility | Philipp’s ERIS hub-owner wallet | Eligible list, strategy, tuning and rebalance | Ceres removal [https://philipp-payments.pages.dev/history/#event=eris-ceres-remove] ; Actual rebalance [https://philipp-payments.pages.dev/history/#event=eris-ceres-rebalance] | A continuing source of economic leverage over validators, separate from a board seat.

| Grant and project selection | Phoenix board; Philipp originated 288 of A1–A289 | Approve grants, milestones and releases; finance projects that need integration or liquidity | Creda grant [https://philipp-payments.pages.dev/history/#event=board-190] ; Estima release [https://philipp-payments.pages.dev/history/#event=board-271] ; Support channels [https://philipp-payments.pages.dev/history/#event=statement-2025] | Strong influence over which builders receive resources and which products become established.

| Governance of funded projects | PD token holdings and linked governance products | Acquire project tokens with funding; place treasury voting positions into Votion | CAPA governance rationale [https://philipp-payments.pages.dev/history/#event=statement-1501] ; Collective capital deposited into Votion [https://philipp-payments.pages.dev/history/#event=votion-collective-capital-A16] | The effect of a grant can extend to project governance, not only payment for development.

| Reward distribution | PD eligibility decisions and TLA gauge/incentive mechanisms | List/delist assets, set take rates, place voting incentives and aggregate votes | Eligibility conditions [https://philipp-payments.pages.dev/history/#event=statement-2319] ; Steering through incentives [https://philipp-payments.pages.dev/history/#event=statement-3314] ; Asset removal [https://philipp-payments.pages.dev/history/#event=board-121] | A project’s access to recurring rewards depends on these decisions.

| Rule changes and participation restrictions | Philipp’s retained owner/admin wallets | Replace code; change role assignments; install asset and sender restrictions | 31 strict post-handover operations [https://philipp-payments.pages.dev/evidence/#authority] | Authority outside ordinary board voting can change the rules the board and users rely on.

| Fees and beneficiaries | Philipp as grant/fee recipient and participant in approvals | Receive project funds and compensation; re-route a fee recipient | Superbolt P35 [https://philipp-payments.pages.dev/history/#event=beneficiary-approval-2] ; Fee-recipient change [https://philipp-payments.pages.dev/evidence/#authority] | The same person can benefit financially and exercise implementation power.

| Aligned board votes and constitutional change | Philipp and MB | MB voted YES on 251 of 252 recorded ballots on Philipp proposals; the one NO concerned a wrong contract and was followed by YES on its correction; both supported A272 | A272 removal plus 60% threshold [https://philipp-payments.pages.dev/history/#event=board-272] | The proposed three-seat structure would let the pair approve despite the third director’s NO.

| Overlapping committees and wallets | Repeated signers across Stewardship, Liquidity Alliance, Delegation Program and Legal Contingency Fund | Separate wallet names, substantially the same approving group | Membership and approval records [https://philipp-payments.pages.dev/history/sources/power_20261022_openfields_pd_power.json] | Splitting functions among wallets does not create independent oversight when the decision-makers repeat.

| Paid communications and review relationships | Funded communications/ambassador roles; overlapping commercial recipients | Approve continuing communications payments and transact with advocates/review participants | Communications and ambassador funding [https://philipp-payments.pages.dev/history/#event=board-273] ; ERIS → Rebel invoice and shared distributions [https://philipp-payments.pages.dev/evidence/#payments] | Readers assessing independence need the financial relationship as well as the public argument.

| Interface access and criticism | ERIS interface operator | Threaten exclusion from interfaces in response to criticism | Unattributed pressure summary [https://philipp-payments.pages.dev/history/#event=pressure-interface-warning] | Operational access was invoked as a consequence of speech.

| Delegation used as pressure in public | Rebel, a communications participant and shared commercial beneficiary | Invoke PF delegation while criticizing a community’s response and publicity | Don’t bite the hand that feeds you [https://philipp-payments.pages.dev/history/#event=lion-delegation-pressure-95477] | The dependence was expressly used in argument. This is Rebel’s recorded conduct; the full exchange preserves his disclaimer and Philipp’s request to stop attacks.

| Community conduct and incentives | Philipp as proposer and PD decision participant | Threaten loss of incentive access in connection with criticism and community conduct | Unattributed pressure summary [https://philipp-payments.pages.dev/history/#event=pressure-incentive-warning] ; Subsequent narrower native vote [https://philipp-payments.pages.dev/history/#event=native-4832] | The cost of a dispute can extend from the speaker to a project and its liquidity users.

| Funding an independent challenge | Legal Contingency Fund uses the same four current board accounts | The recorded fund requires three approvals; two withholding approval can block a fund expenditure | Fund membership and threshold [https://philipp-payments.pages.dev/history/sources/power_20261022_openfields_pd_power.json] | Financial dependence can reach the cost of scrutiny itself. This is a fund-control capability; no specific blocked retainer is asserted here.

| Operational continuity | ERIS service operator and retained technical authorities | Threaten withdrawal of maintenance and operational services during governance disputes | Unattributed pressure summaries [https://philipp-payments.pages.dev/evidence/#pressure] | Dependence on the operator can pressure those responsible for supervising him.

| Forum administration and access | Philipp, Vini and Rose were all listed as administrators and moderators in the 17 October roster | Administrative control over the venue in which governance is debated | Public staff roster [https://philipp-payments.pages.dev/history/#event=forum-authority-20261017] ; Philipp on moderation and setting our own stage [https://philipp-payments.pages.dev/history/#event=statement-1239] | The venue itself is another control point. Philipp’s 10 October 2024 statement linked criticism and moderation to using a separate platform. The roster records shared powers; specific moderation acts require their own records.

| Information and the terms of the argument | Proposal author, operator and forum participant | Explain retained authority through personal confidence in the board; offer a later temporary voting undertaking | Withholding explanation [https://philipp-payments.pages.dev/history/#event=forum-55] ; Temporary arrangement [https://philipp-payments.pages.dev/history/#event=forum-57] | An authorization question becomes a claim about who deserves the operator’s confidence. The original transfer terms remain the benchmark.

The central accountability problem

The operator, beneficiary and decision-maker repeatedly overlap. Public funding builds the products; treasury capital and user deposits make them important; delegation and rewards make other participants dependent; retained keys preserve control over implementation. The proposed two-of-three board would then remove the need for consent from outside Philipp and MB’s pairing.

The pressure messages show why these connections matter: the powers were invoked over criticism, community conduct and the structure of oversight. Each episode must be judged by the authority held, the demand made, the consequence invoked and the action actually taken.

How much validators depended on these allocations

22 October 2026 snapshot. ERIS native delegations and PD/TLA synthetic allocations are shown separately. The percentages describe the allocated component relative to each validator’s recorded weight. These are economic exposures; actual votes must be checked separately.

Examples include Lion DAO: 94.7% PD/TLA ; ERIS: 53.8% PD/TLA and 45.1% ERIS-native ; Galactic Punks: 34.4% and 55.1% ; Smart Stake: 32.2% and 36.7% . The same transparency applies to dissenting directors’ validators: SCV: 83.5% PD/TLA , and cosmosrescue: 50.5% PD/TLA and 45.1% ERIS-native .

| Validator | PD/TLA synthetic LUNA-equivalent | PD/TLA share | ERIS native LUNA | ERIS-native share

| Node39.TOP | 2,105,227 | 99.9% | — | —

| owlstake | 2,105,227 | 99.7% | — | —

| 🦁 The Lion DAO | 7,816,998 | 94.7% | — | —

| Active Nodes | 4,544,766 | 88.8% | — | —

| 0base.vc | 3,272,232 | 84.6% | — | —

| SCV-Security | 3,676,813 | 83.5% | — | —

| SOLID | 3,635,449 | 79.9% | — | —

| Synergy Nodes | 4,544,766 | 74.1% | — | —

| Terrascope | 4,908,348 | 73.4% | — | —

| Stakely.io | 6,544,463 | 71.7% | — | —

| Pro-Nodes75 | 3,090,441 | 70.4% | — | —

| Lavender.Five Nodes 🐝 | 4,544,766 | 63.8% | — | —

| Orbital Command | 5,041,478 | 61.3% | 986,354 | 12.0%

| TdrSys | Auto-Compound | 2,181,488 | 53.8% | — | —

| ERIS ⚡️ Delegate for claimdrop | 4,622,279 | 53.8% | 3,878,960 | 45.1%

| WildSage 🧙 | 2,545,069 | 53.3% | — | —

| cosmosrescue | 4,202,072 | 50.5% | 3,749,579 | 45.1%

| Stakin by The Tie | 2,484,472 | 48.2% | — | —

| 01node | 2,545,069 | 43.7% | — | —

| HighStakes.ch | Stake for Airdrop | 3,453,671 | 42.8% | 3,254,064 | 40.3%

| polkachu.com | 5,090,138 | 39.0% | — | —

| Galactic Punks Validator | 4,908,348 | 34.4% | 7,862,461 | 55.1%

| Smart Stake | 6,885,018 | 32.2% | 7,862,461 | 36.7%

| Ceres Ventures | — | — | 695,349 | 25.0%

| BackBone Labs | Delegate for $SOUL Claim Drop | — | — | 3,343,826 | 74.5%

| closed inactive in snapshot | 3,635,800 | 99.9% | — | —

| [Shutting down] cosmostation please redelegate inactive in snapshot | 6,665,657 | 87.3% | — | —

Why it matters for votes: native validators supply default ballots, while direct native delegators can override their portions. The ERIS hub can vote its pooled stake through its operator. PD/TLA allocations separately affect the stake and income attached to recipient validators. A reform coalition therefore cannot count a validator’s headline weight without checking the underlying delegations and any overrides.

The PD/TLA column is the saved Openfields model, covering the Treasury and four connectors. Its 94.75m active total is synthetic staking weight, not a cash balance. ERIS uses preserved native-delegation responses. Sources were captured at nearby heights; columns are not combined into a single personal-control percentage. A dash means no allocation listed in that dataset.

Full calculations and definitions [https://philipp-payments.pages.dev/history/sources/stake-dependence.json] · Preserved indexer response [https://philipp-payments.pages.dev/history/sources/power_20261022_openfields_pd_power.json] · Native delegation response [https://philipp-payments.pages.dev/history/sources/power_20261022_amp_delegations.json] 

From pooled stake to voting and economic leverage

ERIS is a vehicle through which pooled user stake becomes concentrated delegation and governance influence. The critical permissions include changing who votes and changing the code of the contract that votes.

Holders deposit stake Economic ownership remains with users 
→
ERIS hub delegates 31.98m LUNA ≈ $1.34m at the snapshot price 
→
Two consequences Validator income + native governance weight 

The normal voting route

At the 24 October 2026 snapshot, Prop Gauge was the operator. A hub ballot is the vote of the native delegator. Holding ampLUNA alone is not the same as owning a direct native delegation with a separate override vote.

The separate control routes

The hub owner can replace the operator. The q0v administrator can replace Prop Gauge code. The hub’s weighted upgrade multisig protects a different layer.

| Channel | Recorded authority | Mechanism | Consequence

| Stake aggregation | ampLUNA hub holds native delegations | 31,977,210.366550 LUNA ≈ $1,344,261.58 at the 24 October query | The hub, rather than each derivative holder, is the direct native delegator. Evidence [https://philipp-payments.pages.dev/history/sources/hub_delegations.json] 

| Validator selection | Philipp’s kefa wallet (stored hub owner) | Add/remove eligible validators; configure strategy; tune/rebalance | Affects validator commission income and where default validator voting weight sits. Staking constraints still apply. Evidence [https://philipp-payments.pages.dev/history/sources/hub_config.json] 

| Native governance voting | Recorded operator: Prop Gauge contract | Hub vote / weighted-vote messages are operator-gated | The operator can submit the hub’s native ballot; this overrides the hub’s share of default validator votes. Evidence [https://philipp-payments.pages.dev/history/sources/hub_vote_operator.json] 

| Change the voting operator | Hub owner, through update_config | Owner can appoint a different vote operator | A holder-facing voting process remains changeable through a separate owner permission. Evidence [https://philipp-payments.pages.dev/history/sources/hub_execution_source.rs] 

| Change Prop Gauge code | Philipp’s q0v wallet | Prop Gauge migration administrator | The operator contract’s implementation is replaceable by a separate administrator. Evidence [https://philipp-payments.pages.dev/history/sources/gauge_info.json] 

| Change hub code | ERIS weighted multisig | 70 required out of 90; Philipp’s key has 50 | Requires other signers for this path; does not constrain the routine owner powers above. Evidence [https://philipp-payments.pages.dev/history/sources/hub_info.json] 

| Foundation / TLA delegations | Ordinary board controller; separate registry owner and code admin | Board directs normal allocation; registry can change role addresses | Board voting and retained technical authority must both be addressed. Evidence [https://philipp-payments.pages.dev/evidence/#current] 

| Revenue and participation | Fees, project awards, escrow eligibility and incentive rules | Fee routing, product eligibility and recipient decisions | Commercial benefit and power to shape participation can reinforce each other. Evidence [https://philipp-payments.pages.dev/evidence/#payments] 

Historical snapshot reference: $0.042038113 per LUNA, using the completed hour ending 17:00 UTC on 24 October 2026; query captured at 17:54 UTC. Price sources and calculation [https://philipp-payments.pages.dev/history/sources/historical-prices.json] .

An actual allocation change is recorded. On 9 October 2026, Philipp’s owner wallet removed Ceres from the eligible list and rebalanced delegations. The two transactions record the use of allocation power over validator income.

Removal transaction [https://philipp-payments.pages.dev/history/#event=eris-ceres-remove] · Rebalance transaction [https://philipp-payments.pages.dev/history/#event=eris-ceres-rebalance] 

The fresh contract and delegation queries were taken at nearby, separate heights, not one atomic block. The previous 22 October comparison placed the hub at roughly one tenth of bonded stake. No updated percentage is claimed here because the fresh pool query was rate-limited. Do not add the full voting power of recipient validators to the hub balance: that would double count overlapping stake.

Each form of control strengthens the others

01 · Agenda 
Frame the decisions

Philipp submitted 288 of the 289 captured board proposals. That is near-total authorship of the recorded board agenda.

02 · Votes 
Secure aligned approvals

Of 252 recorded MB ballots on Philipp’s proposals, 251 were YES. Philipp submitted 288 proposals; 36 had no recorded MB vote. The one NO was on A28, which used the wrong contract. MB voted YES on corrected A29 5 minutes 10 seconds later. Voting record and both transactions [https://philipp-payments.pages.dev/evidence/#votes] .

03 · Money 
Receive funded work and fees

Grants, milestone payments, compensation, fees and shared-business distributions create financial interests within the same decision network. Each payment remains linked to its recipient and approval.

04 · Implementation 
Keep authority outside the vote

Registry ownership and contract migration administration can change rules and permissions separately from normal board execution. A nominal board safeguard is incomplete when this route remains elsewhere.

05 · Dependence 
Influence who keeps support

Delegation, incentive eligibility, service maintenance and communications access can make participation depend on the same operator. Reports of pressure must be assessed against these actual powers.

06 · Oversight 
Seek fewer independent approvals

A272 would have made the aligned pair sufficient in a three-seat board. The attempted removal of this safeguard belongs at the end of the accumulated-control sequence, not in isolation.

The case for accountability

The record supports a serious concern about governance capture through overlapping financial, technical and voting authority . Its strongest basis is the documented structure and conduct: retained and used powers, beneficiary approvals, dependence on delegated stake, and an attempted reduction of independent consent.

The accountability question is how entrusted authority became a continuing source of personal discretion, financial benefit and power over participation. The retained keys, interested approvals, delegation leverage and proposed voting threshold must be examined together.

Who authorized departure from the handover terms, under what authority, and when? Who independently reviewed payments benefiting decision-makers? What enforceable arrangement prevents the financially aligned pair becoming sufficient authority alone? 

Follow each financial interest without counting it twice

The money register separates requests, approvals, project custody, reported awards and actual transfers. It includes ERIS’s original grant, TLA funding, Votion, Creda, Estima, migration work and shared Superbolt distributions. The 105-receipt schedule includes other associated participants so the commercial relationships can be examined.

Historical USD values for approvals are measured at the displayed proposal or voting-close date. Actual receipts are priced individually at receipt. The WHALE and MNTA figures remain unpriced because their settlement evidence and historical quotes have not been established. Future USDC milestones are nominal amounts; their future market prices are unknown.

The register identifies the recipient, approval, payment and purpose separately. It distinguishes project funding from personal receipts and prevents the same funds being counted again when paid onward.

Funding register [https://philipp-payments.pages.dev/history/sources/funding-register.json] · 105 receipts and valuation evidence [https://philipp-payments.pages.dev/evidence/exhibits/legacy/Zahlungen_105.json] · Existing payments page [https://philipp-payments.pages.dev/] 

Test the language against the powers and acts

| Dated statement or position | What must be compared

| 27 September 2024: compromise conditional on stopping division [https://philipp-payments.pages.dev/history/#event=statement-977] | An offer to change governance participation is tied to the opponent’s conduct. Compare the stated accountability claim with the retained key structure.

| 10 October 2024: unified alignment and “our own stage” [https://philipp-payments.pages.dev/history/#event=statement-1239] | The message rejects a communications candidate for competing-chain leadership and links moderation to where PD will hold discourse. Read the public counter-responses as well.

| 9 February 2025: “Code is law” and conditions of participation [https://philipp-payments.pages.dev/history/#event=statement-2319] | The statement identifies the power to list, delist and alter take rates, then attaches social and roadmap expectations. Native community approvals are separately recorded.

| 9 February 2025: “We don’t have control over the locks” [https://philipp-payments.pages.dev/history/#event=statement-2473] | Ordinary lock rules and retained code-replacement authority are different. The wording must be tested against both, rather than only the withdrawal interface.

| 31 August 2026: recusal and veto notification should occur [https://philipp-payments.pages.dev/history/#event=statement-4390] | Philipp identifies a process standard and a failure in one application. Apply that standard consistently to interested approvals.

| 19 October 2026: board confidence used to explain withholding control [https://philipp-payments.pages.dev/history/#event=forum-55] | The published terms specified time-based handovers. This response identifies personal judgment, but no amendment authorizing replacement of those terms.

| 19 October 2026: temporary vote restraint [https://philipp-payments.pages.dev/history/#event=forum-57] | A statement about intended voting does not disable the permission to approve, and the exception concerns appointment of future directors.

| 23 October 2026: milestone release described as a formality [https://philipp-payments.pages.dev/history/#event=forum-91] | Obtain the actual independent verification, contractual scope and conflicts record. A process label does not establish that these checks occurred.

Relevant public counter-context [https://philipp-payments.pages.dev/history/sources/statement-context.json] · Pressure and economic leverage [https://philipp-payments.pages.dev/evidence/#pressure] 

Funding, payments, capital and fees

The established payment ledger is included here so the control history can be read alongside the financial scale. Each USD figure uses the dated receipt prices, rather than today’s price. Shared-project funding and onward invoices overlap; these rows are not additive.

| Receipt category / dates | Token quantity | USD at receipt | What the amount represents

| Stewardship compensation 13 Nov 2024–17 Oct 2026 | 200,080 USDC | $200,060.30 | 23 recorded work-pay receipts, including 8,640 USDC claimed on 17 October 2026. Project grants and expenses are separate.

| Creda 2026-01-02; 2026-01-27 | 210,000 USDC | $210,004.67 | Component of Phoenix project grants.

| Votion 2025-02-19; 2025-08-25 | 50,000 USDC | $49,994.50 | Component of Phoenix project grants.

| Migration tool 2026-09-10 | 5,000 USDC | $4,999.50 | Component of Phoenix project grants.

| Estima kickoff 2026-10-03 | 45,000 USDC | $44,998.65 | Component of Phoenix project grants.

| Neutron project grants 8 Jul 2024–2 Jun 2025 | 100,000 USDC | $99,994.99 | Two 50,000-USDC awards. Subsequent transfers of 90,000 to Superbolt and 10,000 to another professional account are later uses of this funding.

| Superbolt invoice-labelled payment batches 2025-08-05–2026-03-17 | 55,975.5 USDC | $55,967.89 | Identified payments to Philipp. Kept outside the broad resource sum to avoid adding a downstream company payout to funding already counted upstream.

| Superbolt invoice 2024-002 2024-08-23 | 7,500 USDC | $7,498.05 | Identified payments to Philipp. Kept outside the broad resource sum to avoid adding a downstream company payout to funding already counted upstream.

| Voting incentives and rebases 2025-12-31–2026-09-23 | Multiple tokens | $1,043.54 | Recorded incentives/rebases. Includes rewards paid to or compounded for associated positions, not proof of a discretionary salary or pure profit.

| Expenses and reimbursements 19 Nov 2024–23 Jun 2025 | 10,450 USDC + 3,500 LUNA | $10,925.26 | Gross reimbursements received. The related expenses have not been reconciled into retained benefit.

| Permanent alignment allocation — A43 5 Nov 2024 | 20,750 ampLUNA · NFT 432 | $9,338.13 | Permanent locked capital allocation, assigned on 5 November 2024. This identifies the allocation precisely rather than calling it a generic bonus.

| Original Eris development grant 20 Jan 2023 | 312,500 LUNA | $598,925.52 | Received into the Eris grant custody structure. Predates Phoenix Foundation; includes development, audit, marketing and infrastructure budgets.

| TLA development and audit grant — proposal 4813 7 Jun 2024 | 384,615 LUNA | $250,986.08 | Project development and audit funding paid from the Terra community pool on 7 June 2024. The block-end transfer is verified; it has no ordinary transaction hash. Gross project funding, not personal net profit.

| Eris fees 30 May 2022–11 Oct 2026; coverage varies | Multiple tokens | $81,969.94 | Original product fees and network fee share; excludes later collector distributions.

| Eris validator commissions 2026-06-30–2026-10-06 | Multiple tokens | $4,475.82 | Gross recorded Eris validator commission withdrawals. Delegated principal and delegator rewards are excluded.

Full payment schedule [https://philipp-payments.pages.dev/data/payment-schedule.json] · Underlying receipt ledger and transactions [https://philipp-payments.pages.dev/data/complete-receipt-ledger.zip] · Open individual payment transactions [https://philipp-payments.pages.dev/payments/] 

Fee income over time

Captured original product fees and network fee share total $81,969.94 . Later collector distributions and reserve withdrawals are excluded. This comprises 48,243 receipt events; 576 lack a reliable historical price and are omitted from the USD subtotal.

| Year | Receipt-time USD | Coverage

| 2022 | $1,039.76 | 114 priced / 0 unpriced events

| 2023 | $8,581.63 | 3238 priced / 8 unpriced events

| 2024 | $22,122.46 | 20733 priced / 456 unpriced events

| 2025 | $18,211.83 | 9544 priced / 0 unpriced events

| 2026 | $32,014.25 | 14038 priced / 112 unpriced events

Coverage varies by product, beginning 30 May 2022 and ending 11 October 2026. These are gross protocol receipts, not personal retained profit. The separate 2,280-LUNA fee stream is excluded from the main total pending overlap reconciliation. Annual rows and the total are rounded separately from unrounded values; this produces a one-cent difference when adding the displayed annual figures.

Fee components, annual totals and exclusions [https://philipp-payments.pages.dev/data/fee-reconciliation.json] 

Timeline and evidence register

1,299 entries. The default selection shows the key sequence. Switch to the complete register for all captured board proposals, technical actions, payments and author statements. Entries can be different records about the same transaction; the entry count is not a count of offences or unique transactions.

ViewKey sequenceComplete registerLayerAll layersRecord typeAll record typesYearAll yearsFind evidenceOrderOldest firstNewest first

Loading the evidence register…

Download the complete CSV timeline [https://philipp-payments.pages.dev/history/events.csv] or JSON register [https://philipp-payments.pages.dev/history/events.json] . The numbered narrative above works without JavaScript.

The wider contract inventory

142 discovered contracts, captured 18 October 2026. Each row identifies the recorded administrator and contract. The original TLA subset and the current role checks are identified separately.
Filter contracts

Scope, preservation and checking

| Record set | Coverage and limits

| Board proposals | A1–A289; captured 23 October. Creation dates, ballots, vote transactions and executable payloads. A missing ballot is not an abstention.

| Technical actions | 181 collected successful actions by Philipp’s two owner/admin wallets. The strict original-TLA subset is 31 operations in 19 transactions on seven contracts after 27 November 2024. Other ERIS contracts are separate.

| Hub ballots | 58 contract-origin ballot events in 56 successful transactions on 13 native proposals, March 2023–October 2024. Event attribution and caller instructions retained; one explicit hub-voter field and 57 matching contract-event attributions. Multiple events can update one ballot.

| Native governance | 51 selected full-text proposals from a retained 124-record node inventory, through 5 October 2026. Proposal authorship and execution are identified in the corresponding records.

| Public chat | 566 non-forwarded Philipp messages from the supplied Phoenix Directive export, July 2024–October 2026. Extracts preserve source message IDs; collector/contact identifiers are redacted where marked. This is not a complete record of every channel or deleted revision.

| Forum | 22 Philipp posts from the visible 88-post thread snapshot retrieved 24 October; highest post number 93. Each extracted post records revision and update time. Available post numbers and revision metadata are preserved.

| Money | 105 selected receipt rows are individually priced; the wider payment and 48,243-event fee ledgers are linked separately. Executable instruction amounts are valued at proposal/event dates and are not summed as receipts. These amounts are not a lifetime personal-income total.

| Private reports | Summarized in the linked supporting records. Private source identities, correspondence and access details are excluded from this download.

| Integrity | The manifest records file sizes and SHA-256 hashes. It allows byte comparison; it does not independently certify authorship or timestamp the underlying events. Original chain links and existing third-party archival captures remain available.

Correction carried into this page: A258 and A266 have no recorded Philipp ballot. An earlier narrative described an abstention; the saved ballot bodies do not show one. A271 does record his YES. The dates in the register distinguish submission, creation, transaction, message and capture times.

Download this page and evidence [https://philipp-payments.pages.dev/history/history-evidence.zip] Timeline CSV [https://philipp-payments.pages.dev/history/events.csv] Historical USD values [https://philipp-payments.pages.dev/history/historical-usd.csv] Pricing evidence [https://philipp-payments.pages.dev/history/sources/historical-prices.json] Timeline JSON [https://philipp-payments.pages.dev/history/events.json] Primary-source index [https://philipp-payments.pages.dev/history/sources/source-index.json] Checksums [https://philipp-payments.pages.dev/history/SHA256SUMS.txt] Supporting records [https://philipp-payments.pages.dev/evidence/] Handover record [https://philipp-payments.pages.dev/handover/] Forum archives [https://philipp-payments.pages.dev/forum-records/] Original repository [https://github.com/phoenix-directive/docs] Independent repository mirror [https://github.com/terra2backup/Terra_Backup] 

Prepared 24 October 2026. Dates are UTC unless stated. The analysis links to the dated records supporting each finding. Individual source snapshots have their own dates and scope.