AIE - Airdrop Integrity | Private Institutional Airdrop Analysis

Early Idea Discussion Sales Pitch by Service Providers
1

Good day.
Blockchain promised transparent rules, verifiable outcomes and accountable value movement. What should have remained clean, auditable and fair has too often been filled with hidden coordination, artificial participation and operational distortion.
AIE is releasing one of its private Web3 integrity systems for institutional use:
AIE - Airdrop Integrity
AIE - Airdrop Integrity is a buyer-controlled analytical system for reconstructing wallet relationships, identifying coordinated structures, separating alternative explanations and false-positive controls, and reviewing allocation evidence before an airdrop decision is finalized.
The visible chain rarely shows the complete structure. AIE works beneath that visible surface, turning fragmented activity into a reviewable map of relationships, routes, groups and evidence.
What the system does
AIE - Airdrop Integrity provides a complete workflow for:
reconstructing wallet relationships and coordinated structures;
identifying common funding, collection and route patterns;
separating hidden coordination from shared services and legitimate common behavior;
reviewing individual wallets inside discovered structures;
preserving the evidence path behind every cluster-level result;
comparing results against approved historical outcomes;
simulating allocation consequences before execution;
generating local reports, hashes, checkpoints and review records.
The system recovers signal from noise without converting every unusual pattern into an accusation.
Relationship evidence, allocation simulation and operator decisions remain separate layers.
Private deployment
Each deployment is designed for:
one organization;
one trusted operator;
one licensed Windows workstation;
unlimited local runs during the valid license period;
a fixed three-calendar-month license term;
buyer-controlled datasets, graphs, reports and evidence records;
readable static results after license expiry.
The operator uses a local browser interface while package verification, analysis, graphs, simulations, manual review and reporting remain inside the buyer-controlled environment.
The analytical core does not require RPC, external APIs, cloud upload, telemetry or outbound licensing calls.
Upstream data acquisition may be performed online or offline under buyer control. AIE Data Prep Gateway converts existing exports into a deterministic, signed and hash-addressed package. The Offline Engine accepts only packages that pass identity, schema, checksum, signature and provenance gates.
buyer-controlled acquisition → verified local package → Offline Engine → local evidence and reports
External data may enter the workflow. The analytical decision layer does not leave the buyer’s control.
Campaign-to-wallet analysis
AIE - Airdrop Integrity operates first at the distribution level.
It identifies coordinated structures across the complete campaign and shows where deeper examination is required.
Selected addresses can then be examined through the AIE Wallet Risk Analysis workflow for:
transaction paths;
exposure;
counterparties;
connected activity;
funding and collection routes;
mixer and hidden-flow interaction;
wallet-specific risk.
distribution-wide structural detection → selected-wallet examination
This creates a direct path from the hidden architecture of a campaign to the evidence attached to an individual wallet.
Managed analysis by request
Organizations may request a selected managed case without purchasing or receiving the software.
Available work includes:
airdrop integrity review;
wallet risk analysis;
transaction-path reconstruction;
mixer and hidden-flow route examination;
wallet incident reconstruction;
counterparty review;
settlement verification;
wallet recovery intelligence.
The client submits one agreed frozen evidence package. The analysis is performed inside the private AIE laboratory, and the client receives a structured result with supporting evidence.
Initial findings from 30 minutes. Complete delivery within 24 hours after a complete evidence package is accepted.
Requests are accepted by direct message.
Three forum-nominated verification cases
Following this release, AIE will open three public verification slots.
Forum participants may nominate any technically suitable case: a completed airdrop, an active campaign, a planned distribution, or another frozen dataset suitable for controlled analysis and comparison.
Three cases nominated through this forum will be accepted.
For each accepted case:
the scope and comparison point will be fixed before analysis;
the submitted dataset will be frozen;
the output will be frozen before comparison;
the result and supporting evidence will be published on this forum.
The cases will come from the forum rather than from an internally selected list.
After the third forum-nominated case is completed and released, allocation of the numbered AIE - Airdrop Integrity deployments will open.
Limited institutional release
Only 11 individually numbered copies of AIE - Airdrop Integrity will be issued.
Each copy is a closed institutional deployment for one organization, one trusted operator and one licensed workstation.
The release is finite and will not be replenished after the eleventh copy is allocated.
Pricing is not published. Deployment scope and institutional terms are discussed privately.
Completed evidence case - Hop Protocol
A completed blind analysis was performed on the full public Hop topology corpus.
The objective was to determine how much published structure could be recovered from a neutral relationship plane before the official baseline was opened.
Corpus
Official neutral universe: 43,058 addresses
Retained public relationship rows: 6,057,473
Source files: 183
Networks represented: Ethereum, Arbitrum, Optimism, Polygon and Gnosis
Both analytical outputs were hashed, frozen and receipted before the official Hop baseline was authorized or opened.
Run A - comparator-aligned neutral topology
Detected structures: 2,249
Detected addresses: 12,919
Official Hop exclusions recovered: 5,819 / 14,195
Official-exclusion recall: 40.993308%
Runtime: 1,514.500 seconds
Official groups with 100% member recall: 12 / 610
Exact full member-set recoveries: 7
Across all 610 official groups:
100% member recall: 12
90% to below 100%: 5
75% to below 90%: 18
50% to below 75%: 94
Below 50%: 341
Missed: 140
The result was substantial but partial. It recovered known structure from a reduced topology plane without treating that reduced plane as the full analytical depth of AIE.
Run B - raw-topology ablation
Run B is classified as:
VALID_RAW_TOPOLOGY_ABLATION_ONLY
It imported the same 43,058 addresses and 6,057,473 directed relationships, but deliberately removed transaction identity, real time, amount, asset, method, verified contract role and trace facts.
Run B recovered 0 / 14,195 official exclusions and produced one three-address structure.
It is an ablation result and is not presented as the complete native capability of AIE.
The contrast between Run A and Run B shows where the visible graph ends and where richer evidence families begin to matter.
Additional structures
An additional structure was defined as a deduplicated detected structure with zero member overlap with every official Hop group used in the published baseline.
Under that frozen definition:
Independently confirmed: 0
Topology-validated under preregistered criteria: 421
Unresolved: 579
Insufficient evidence: 2
Contradicted: 0
Separately, 1,248 Run A structures overlapped at least one official group and were excluded from the additional-structure count.
Topology-validated structures are not described as confirmed Sybil groups, confirmed abuse or proof of common control.
This separation preserves what the evidence shows while keeping unresolved structure visible rather than discarding it.
Independent acceptance
Two independent reviews recomputed:
the accepted 80/80 AIE core identity;
the blind chronology;
the complete address-level metrics;
all 610 group-recovery tiers;
the Run B ablation classification;
the additional-structure population rule.
They reported zero material metric mismatches.
No AIE rerun, threshold tuning, input change, baseline rewrite or external-data substitution occurred during acceptance and reconciliation.
Evidence availability
The complete frozen evidence package, manifests, receipts and independent review materials are available for direct examination on request.
No evidence file is attached to this forum post.
Reproducibility
The result can be recomputed from the frozen input hashes, output manifests, run receipts, official Hop baseline, published evaluation definitions and the frozen additional-structure rule.
A visible blockchain can still contain an invisible structure. AIE is built to recover that structure, preserve the evidence behind it and return analytical order to decisions that should remain clean, fair and verifiable.

AIE - Integrity Research
Private Web3 integrity systems for clean distributions, fair participation and verifiable on-chain decisions.

1 Like
2

Impressive work on the Hop case and the focus on frozen evidence and reproducibility. At the same time, for a public DAO like Arbitrum, relying on a private, scarce integrity tool raises questions around method transparency, access asymmetry, and clear appeal / review standards if its outputs inform exclusion decisions.

3

The relevant distinction is not “public tool versus private tool.” It is whether the decision surface remains inspectable, reproducible and contestable.

A public model can still produce an opaque exclusion. A proprietary analytical engine can still expose a fully reviewable evidentiary surface.

AIE separates three layers that should never be collapsed into one:

  1. the protected analytical kernel;
  2. the reviewable evidence produced by that kernel;
  3. the governance authority that decides policy, exclusion and appeal.

The analytical kernel may remain private. The decision-relevant evidence may not.

Any material conclusion produced by AIE must be traceable to frozen inputs, frozen outputs, address-level relationship paths, provenance, alternative explanations, false-positive controls and an explicit statement of what remains unresolved. A DAO is therefore not asked to trust a hidden score. It is given a structured evidentiary record that can be reviewed independently and challenged at the level of the underlying facts.

The scarcity of the software concerns deployment, not review rights. A participant does not need access to the engine in order to understand the evidence used in a decision, contest an incorrect relationship, introduce contrary evidence or request a second review. Appeal standards remain a governance decision and should be defined before any exclusion policy is applied.

I’m now formalizing this as Public Verification Case 1/3 through an Arbitrum-native controlled reconstruction using two separate analytical systems.

AIE - Airdrop Integrity will reconstruct the campaign-level structure beneath the visible chain. Its output will then be frozen before a wallet panel is selected. That frozen panel will be examined separately through AIE - Wallet Risk Analysis.

The chronology is therefore:

frozen public inputs → campaign-level reconstruction → frozen structural output → frozen wallet panel → wallet-level examination → frozen wallet output → comparison and review

This sequence is designed precisely to prevent methodological leakage, retrospective tuning and the use of post-hoc evidence to justify an earlier result.

Once both outputs are frozen, we will publish the evidentiary boundaries, chronology, comparison and review surface here.

The objective is not to replace public governance with a private instrument. It is to reveal, with greater depth and precision, the underlying structure that public governance is already responsible for judging.

4

Public Verification Case 1/3 - Frozen Structural Result
The campaign-level stage of the Arbitrum-controlled reconstruction is complete and frozen.
Case classification:
EXTERNALLY_SEEDED_POST_SNAPSHOT_CONTROLLED_RECONSTRUCTION
The public issue population was known in advance and was treated as an external allegation, not as official Arbitrum ground truth. No allegation labels, known-Sybil labels, expected clusters, or post-hoc target values were injected into AIE.
Frozen evidentiary plane
The source layer consists of the complete paginated Blockscout address histories of the two disclosed central addresses, intersected with the frozen 1,656-address seed population.
Source verification:
1,290 / 1,290 manifest entries verified
0 hash mismatches
12,804 normalized direct relationships
5 pre-snapshot relationships
12,799 post-snapshot relationships
The independently recomputed relationship surface shows:
1,656 / 1,656 seed wallets directly linked to the first central address
1,608 / 1,656 directly linked to the second central address
1,608 / 1,656 directly linked to both
48 without a direct second-address relationship in this declared evidence plane
The first direct reaches from the first central address to the complete 1,656-wallet population span 22,691 seconds - 6 hours, 18 minutes, 11 seconds.
The densest inclusive six-hour window contains:
1,653 unique first-reached seed wallets
2,407 direct relationship rows
Accordingly, the concentrated distribution pattern is supported, but the exact public statements of 2,417 transactions inside six hours and a universal second-address relationship do not reproduce in the complete declared plane.
Frozen AIE result
AIE - Airdrop Integrity processed:
12,804 events
1,658 addresses
0 imported labels
0 expected clusters
unchanged accepted defaults
zero network access during analysis
The frozen native output produced:
157 graph structures
803 seed wallets assigned to native structures
853 seed wallets unresolved or not natively clustered
13,029 candidate edges
2,244 accepted edges
10,785 rejected edges
647 cluster-evidence records
467 group-evidence records
The native output reconstructed:
a common-funder relationship family spanning all 1,656 seed wallets through the first central address;
a common-sink relationship family spanning 1,608 seed wallets through the second central address.
No wallet reached the configured native high-risk threshold. All native wallet outcomes remained within Low or Moderate levels.
AIE therefore did not convert the visible central-address pattern into an automatic exclusion list. It preserved structure membership, rejected relationships, unresolved wallets, rarity and size penalties, and the distinction between evidence and final judgment.
What the evidence establishes
The frozen result supports a strong post-snapshot operational-coordination or coordinated-execution interpretation.
It does not, by itself, establish:
who controlled the wallets;
whether any wallet was compromised;
whether a sweeper, poisoning event, or delegated operator was involved;
whether the same control existed during pre-snapshot eligibility-generating activity;
eligibility counts or ARB allocation totals;
culpability.
The claim matrix therefore resolves as:
2 independently supported
2 partially supported
2 contradicted
3 not testable from this evidence plane
1 unresolved
Native structure membership is evidence for review, not a final culpability finding. Native non-membership is not exculpatory.
No automatic exclusion is recommended.
Frozen chronology
The sequence was fixed as:
source verification → independent fact recomputation → deterministic input freeze → AIE execution → complete output freeze → deterministic wallet-panel selection → panel freeze → comparison
The AIE output was frozen before either panel selection or comparison.
Frozen AIE output tree SHA-256:
1c0de5bced4904d066c37055c9cddaae0d1ed14e5d5d4e6f3650a4234927acc4
Frozen ten-wallet panel SHA-256:
df74a27d8e9c0393455a727018da76d56309705cab5e2807b43719a489696096
The panel contains the two disclosed central addresses together with eight wallets selected deterministically from frozen native fields: strongest included members, weakest included members, strongest unresolved members, and strongest internal-divergence cases.
No additional wallet history was inspected before that panel was frozen.
Decision surface
This frozen case makes the review boundary concrete.
The protected analytical kernel does not replace the evidentiary surface. The reviewable layer contains:
frozen source records;
a frozen analytical output;
accepted and rejected relationships;
address-level evidence paths;
unresolved populations;
provenance;
explicit scope boundaries;
deterministic panel selection;
reproducible hashes.
The DAO retains policy, exclusion, appeal, review, and final decision authority.
The wallet-level phase of Public Verification Case 1/3 will follow against the already frozen ten-wallet panel.

5

Public Verification Case 1/3 - Part II: Frozen Wallet-Level Review
The wallet-level stage is complete.
The ten-wallet panel was fixed only after the AIE - Airdrop Integrity output had been frozen. No wallet was added, removed, replaced or reordered after deeper examination began.
Case classification:
EXTERNALLY_SEEDED_POST_SNAPSHOT_CONTROLLED_RECONSTRUCTION
Wallet-stage evidence classification:
FROZEN_LIMITED_CENTRAL_RELATIONSHIP_WALLET_REVIEW
This distinction is essential. The wallet stage uses the complete frozen central-address relationship plane captured for this case. It does not claim complete independent histories for the eight non-central panel wallets.
Accepted wallet-analysis boundary
A separate Arbitrum-compatible ingestion candidate was created without modifying the accepted analytical core.
Acceptance result:
154 / 154 tests passed
10 / 10 analytical/core files remained byte-identical
0 core additions
0 core removals
0 core mismatches
0 outbound network attempts
original accepted product unchanged
The ten-wallet input was built twice from clean state and was byte-identical.
WRA input tree SHA-256:
b96a09f238a7bb0be9add8bc2f477526a90f2569dfa760593d33bb8e7d468870
Frozen wallet-level result
The panel contains:
the two disclosed central addresses;
two strongest native structure members;
two weakest included structure members;
two strongest unresolved members;
two strongest internal-divergence cases.
Across the exact frozen panel:
10 / 10 wallets contain post-snapshot relationship evidence
0 / 10 contain a pre-snapshot relationship in the exact-panel subset
8 / 8 non-central seed wallets are directly linked to both disclosed central addresses
47 unique native transactions were reconstructed
3 token-transfer observations were retained as supplemental evidence
20 plane-specific runs reproduced deterministically
0 WRA risk scores were emitted
0 automatic-exclusion recommendations were produced
Complete WRA output tree SHA-256:
b196ff188bfea7113f1c020782f4e11f4772e4f01ffcd0bea962cae407c4e8ce
The absence of a wallet-level risk score is not an absence of analysis. It is a boundary result.
The accepted product did not convert unavailable receipts, traces, raw log topics, unrelated counterparties, ownership evidence or complete wallet histories into synthetic confidence. Missing evidence remained missing. The system preserved the observed relationship envelopes and refused to manufacture a stronger conclusion than the frozen plane could support.
Two systems, two different questions
AIE - Airdrop Integrity evaluated the campaign-level relationship structure and produced:
157 reviewable structures
803 structured members
6 panel wallets included in native structures
4 panel wallets unresolved or not natively clustered
AIE - Wallet Risk Analysis then examined the exact frozen panel at address level.
It reconstructed the native transaction envelopes available inside the declared evidence plane and preserved, for every material record:
wallet identity;
evidence plane;
direction;
value;
timing;
source page;
source-page SHA-256;
source item index;
exercised evidence classes;
unavailable evidence classes.
The first system answers:

What structure exists across the campaign-level relationship plane?
The second answers:
What address-level evidence is actually available for the frozen wallets, and where does that evidence stop?
Neither system is permitted to transform a limited evidence plane into an ownership, culpability or automatic-exclusion verdict.
What the combined result supports
The combined frozen result supports:
a strong post-snapshot operational-coordination or coordinated-execution structure;
direct reproducible relationships between all eight selected seed wallets and both disclosed central addresses;
deterministic separation between structured and unresolved wallets;
address-level provenance for every wallet-stage relationship used;
a review path that does not depend on accepting a hidden score.
What it does not establish
This case does not, by itself, establish:
complete independent wallet histories;
all counterparties;
ownership or common control;
authorization or compromise;
operator identity;
culpability;
pre-snapshot eligibility-generating control;
the wider address populations or allocation totals asserted in the external issue;
a basis for automatic exclusion.
The external issue remains an externally supplied claim set, not official Arbitrum ground truth.
The frozen claim matrix resolves as:
2 independently supported
2 partially supported
1 unresolved
2 contradicted
3 not testable from the declared evidence plane
Review, contestability and appeal
The decision surface is now concrete.
A reviewer can:
trace every wallet-stage relationship to a frozen source page;
verify its SHA-256 and item index;
separate pre-snapshot from post-snapshot evidence;
identify which evidence classes were exercised;
identify which evidence classes were unavailable;
challenge an incorrect relationship;
introduce contrary evidence or an alternative explanation;
request re-evaluation without changing the frozen record.
This is the practical distinction between a protected analytical kernel and an opaque decision.
The kernel remains private.
The evidence used in a decision remains inspectable, reproducible and contestable.
Frozen chronology
previous-stage verification → local evidence recomputation → isolated compatibility candidate → compatibility acceptance → wallet-input freeze → WRA execution → complete WRA-output freeze → independent output acceptance → dual-system comparison
Comparison began only after the Wallet Risk Analysis output had been frozen and independently accepted.
Evidence hashes:
Source manifest:
c69a209d6b0a48f6acc7865c49c2ab03fe0e9bc775d6bc2ea898379e3e6bcc95
Airdrop Integrity output:
1c0de5bced4904d066c37055c9cddaae0d1ed14e5d5d4e6f3650a4234927acc4
Frozen wallet panel:
df74a27d8e9c0393455a727018da76d56309705cab5e2807b43719a489696096
Wallet Risk Analysis input:
b96a09f238a7bb0be9add8bc2f477526a90f2569dfa760593d33bb8e7d468870
Wallet Risk Analysis output:
b196ff188bfea7113f1c020782f4e11f4772e4f01ffcd0bea962cae407c4e8ce
AIE supplies reviewable evidence.
The DAO retains policy, exclusion, appeal, review and final decision authority.
Public Verification Case 1/3 is now complete at both campaign-structure and frozen wallet-review levels.