MB VOTING EVIDENCE — 23 OCTOBER 2026

Start with MB_voting_record_2026-10-23.xlsx or findings.txt. The CSV provides the complete sortable 289-row record. The JSON adds exact primary-source references and hashes. No message or publication was made in preparing this packet.

Scope: the main Phoenix Stewardship board's proposal module A, every proposal A1–A289, including unsuccessful and open proposals. The current module inventory listed only A and its count was 289. This packet does not claim to cover other DAO bodies, native Terra governance, separate companies or private/off-chain decisions. A285 remained open at capture.

Answer: across both professionally associated MB wallets, 252 YES / 1 NO / 0 ABSTAIN and 36 proposals with no recorded MB ballot. The earlier wallet contributed 117 YES / 1 NO; the current wallet 135 YES. The one NO was A28 on 24 October 2024. Philipp had already submitted corrected A29 explaining the wrong contract and asking A28 be vetoed. MB voted YES on A29 five minutes and ten seconds after his NO. Include that correction context with the literal NO count.

The complete comparison with Philipp is 235 matching and 5 different ballots among 240 proposals on which both recorded a vote. A284 is a newer current-wallet difference: MB YES, Philipp ABSTAIN. The older 119/119 shared-YES statistic ends at A283 and must not be represented as the current complete result.

Wallet association: the pinned archived Phoenix Directive Terra Recovery Proposal explicitly names MB aejir (OC/PD) with the earlier address. The executed A125 member substitution replaced it with the current address on 27 March 2025 at 23:41:42 UTC. This is a professional account association and seat-continuity record, not proof of exclusive key custody.

Method: all 283 historical primary ballot files were reopened/hash-checked; the six subsequent ballot files and all 289 current proposal records were retrieved; every named ballot sum was reconciled to the refreshed proposal tally; every proposal disallows revoting. All 253 recorded MB ballots were matched to exactly one successful transaction. An independent check reached the same totals. Capture metadata preserves exact retrieval times/heights. Vote timestamps are block timestamps, not signing/submission times.

Contents:
- Workbook, CSV, findings and JSON: readable and structured record.
- raw/: all 289 named ballot bodies, full current proposal pages, current module/count/config records, current delta and capture metadata.
- sources/blocks/: prior proposal-creation block responses used for exact dates.
- sources/vote_transactions/: the nine preserved full vote-query response pages used to verify historical transactions.
- sources/prior/: the prior proposal page containing A125's decoded account replacement.
- sources/exceptions/: pinned public wallet-attribution document, A125 execution response and capture metadata.
- mb_vote_transactions.json: exact extracted transactions/responses for the 253 recorded MB votes with parent-file pointers.
- verification.json and independent_check.txt: checks and important historical-cutoff distinctions.
- source_manifest.json and SHA256SUMS.txt: sizes and hashes for verification.

Privacy and source handling: this shareable copy contains public blockchain proposal content, wallet addresses, transaction records and the named public institutional attribution document. The full raw blockchain .body files are byte-for-byte copies of the preserved sources. Some contain unrelated public transactions in the same blocks/query pages. Derived JSON/text/capture references have been changed to relative paths. No local user account path, private Telegram material, email account, credentials, scripts or private identity sheet is included. Original full-provenance working files were retained separately.

A missing ballot is not an explicit NO, ABSTAIN, consent or proof of recusal. Proposer means the on-chain submitting address, not proven authorship of every idea. Votes alone do not establish coordination or motivation.

To verify: calculate SHA-256 for the files listed in SHA256SUMS.txt. Primary .body hashes also appear in the derived records. The manifest itself is excluded from its own digest list. Public source/query and individual transaction URLs remain in the dataset.
