What happened to AWZF?

01 — Setup and quantum job

Bishop connects the AI to OpenQuantum

The recording begins before the coin exists. It shows Bishop setting up an AI workflow, connecting it to OpenQuantum, testing the process, and running job 96344213-6661-410b-926e-817308be2913. The job returns 128 bits, which the workflow turns into the name DOCHLY, the ticker AWZF, and the pixel character.

Source account: Bishop on X (@bschizojew)

• The video shows the OpenQuantum job that produced the 128 ones and zeroes used in the creation process. The job sits inside Bishop's OpenQuantum organization and is visible during the recording.
• We repeated that conversion and the result matches the published name, ticker, and image.

Quantum + AI creation clip — Oct 9

The first video shows Bishop running the OpenQuantum job and using its output to create the ticker and coin identity with AI. It appears to be a clip from a longer stream rather than a recording of the entire token launch. The accompanying voice updates and X Space record Bishop presenting the project.

02 — From bits to AWZF

The AI turns the result into a token

After the quantum step, the workflow uses the 128-bit result to create the name, ticker, and artwork. With the AI's help, Bishop then prepares the site and token and launches AWZF on pump.fun. The blockchain records the creation at 06:54:05 UTC on Oct 9, 2026, fourteen minutes after the quoted quantum-job time.

• AWZF was created at 2026-10-09T06:54:05Z. Open the creation transaction.
• The creator wallet was 6b3FGSxT...NLkfd. Its current token balance is zero.
• No one can create extra AWZF or freeze tokens in holders' wallets. Both controls are disabled on-chain. Supply: 975,136,533.55.
• The creator wallet briefly received and forwarded SOL, but did not retain AWZF supply. The transfer record is saved in export_transfer_6b3F...csv.

03 — The following day

The AWZF payment demonstration

About twelve hours after the Oct 9 launch stream, Bishop returned on Oct 10 and demonstrated the payment system he had built. In a 146-second continuous take, he spent AWZF to launch a quantum job. The amounts, SOL received, memos, and timestamps match the blockchain.

Funding link ON-CHAIN: treasury 5DvXH4cL9iwhPN2vTDF4gDyaFu6P282cDiqzDwMoJvw1 sent 1,000,000 AWZF to demo wallet 8pyDEk9iGSCLLm8a8AsuQbgaYquYZcMt1EUDoMjFBrAu at 09:24:59Z (cicEfTcN...). Demo wallet then sold 498,546 + 94,369 + 79,975 = 672,890, leaving 327,110 — exactly the screenshot balance. File: export_transfer_DqY1...csv + export_transfer_8pyD...csv.

Recordings from the demonstration — Oct 10

04 — After the second stream

QUANTY appears, then the promises disappear

After sleeping and returning for a second stream, Bishop worked on a simpler way for crypto users to buy quantum-computing jobs with AWZF. A few hours later, he posted a second contract, QUANTY, through Telegram and described it as the other half of an ecosystem with AWZF. Most AWZF holders had not been told a second coin was coming. Bishop later deleted the ecosystem posts and usequanty.com went offline.

Open Bishop's X post from this stage

The coin

• QUANTY mint 2RSbQ1CWutt5VqUtaARtGDsHLEm4CgEv4zLpZC3Fpump — RugCheck: creator BdiiKF1i6P9qx6Qng5wDjadTxzwcSfsbiCTEPEiLeERQ (different wallet from AWZF creator), balance 0, mint/freeze null, supply ~999.9M, holders 206, liq ~$2,730, rugged:false flag (low-liq, not LP-pull per scanner).
• Ecosystem promise (screenshot ev08_ecosystem-posts.png, now deleted — fxtwitter API returns 404 for all 5 status IDs 2108939779/218217/488490/983026/146108): “creator fees of $AWZF will burn $QUANTY”, “50/50 — 50% to lower computation price, 50% to buy and burn Quanty”.
• Chat screenshots attributed to Telegram user @bishop show a hostile disagreement with community members, followed by the account saying it was leaving. Because direct message links are unavailable, this remains CLAIMED.
• The blockchain shows sales rather than a liquidity withdrawal. Bishop's full 5% QUANTY allocation moved through the project treasury and was sold; the same treasury was the largest identified AWZF seller. The transaction sequence appears in §07.
• usequanty.com recovery: live domain dead (NXDOMAIN both apex + www), archive.ph 404, Wayback throttled, Common Crawl impossible (latest crawl Sept 17, site launched ~Oct 10). Local trace: Brave history shows 2 visits to usequanty.com/ at 14:36:07Z + 14:36:09Z Oct 10 (~8 min after QUANTY creation), but cache holds 0 bytes (evicted). Surviving artifacts in QUANTY_archive/: token metadata (“Spend $QUANTY, get jobs done on a quantum computer. No sign up. No credit card…”, website + twitter links), quanty_logo.png (pixel-Q, 460 KB), @UseQuanty profile (19 followers, 8 tweets, verified, website http://usequanty.com). Homepage screenshot filed as ev12_usequanty-homepage.png (“Quantum Computing made easy”, one-line job box, Run/How/Get buttons) — copy matches metadata verbatim. Full HTML unrecoverable.

The deployer wallet

• QUANTY deployer wallet BdiiKF1... export filed as export_transfer_BdiiKF1i6P9qx6Qng5wDjadTxzwcSfsbiCTEPEiLeERQ_1791662829448.csv: creation 14:28:30Z (50M to self), 50M → treasury 5DvXH... at 15:42:09Z, creator-fee harvests 13:58–15:47Z (0.5–93 SOL each via pump.fun program). Matches crawlscan dev-bought-5% row.

What remains of the promises

Independent record of the deletions

Frontrun Pro independently tracks coins announced by @bschizojew, including deleted announcements. Its counters corroborate this archive and quantify the deletions.

• Files ev10_frontrun-early-posts.png / ev11_frontrun-ecosystem.png — Frontrun Pro “CA History for bschizojew” (powered by @frontrunpro): 27 Active / 29 Deleted, filters All 53 / SOL 38 / BSC 1 / BASE 0 / RH 14.
• Active entries corroborate our post archive: Oct 9 first-coin post (68 likes / 18 RTs / 48 replies), Oct 10 spend claim (26 / 9 / 9), GM post, and both ecosystem mints 2RSbQ...pump + DqY1...V1Xt.
• The 29 deleted entries independently support the conclusion that posts were published and later removed. Deleted posts alone do not establish why they were removed; the wallet sales are evaluated separately in §07.

05 — Saved records

Posts and recordings that were preserved

Bishop told the story through @bschizojew on X on Oct 9–10, then began deleting posts. The posts were captured in order, and the launch video and both Spaces recordings were saved. Third-party archives corroborate the deletions.

• Earliest proof: ev01_first-coin-post_oct9.png — @bschizojew Oct 9, 2026 2:01 PM, 15.3K views. Job ID + CA + DOCHLY/AWZF + 8:54 video. Status 2108452664723882189 (48 replies, 18 RTs, 69 likes). Full text + author JSON archived via fxtwitter.
• Quantum + AI creation clip: 2108452664723882189_launch_video_720p.mp4 (19.7 MB, 1280x720, 550s) shows the ticker/identity-generation process and appears to be excerpted from a longer stream. The matching audio-only file is 1548_2108452664723882189_launch_video_720p.mp3 (8.4 MB).
• Voice + Spaces: Vid_10_1548/ (3-part voice 90.0 + 87.8 + 7.0 MB + Oct 9 space audio mp3 269.7 MB) and Vid2_10_1450/ (2-part voice 88.8 + 77.1 MB + Oct 10 space audio mp3 324.2 MB). Oct 9 gap closed.
• Telegram QUANTY note archived as ev09_telegram-quanty-note.png (“this is looking good. idk who made it tho… professional work”, 52 views 9:33 PM).

06 — Who bought first

What the earliest buyers did

Independent scanners found no single-entity bundle. But the complete early-buyer records show every first-second buyer exited within hours, with some of the same wallets active in both launches.

Was the launch secretly controlled by one buyer?

• AWZF: report — status no_bundle, bundled 0%, dev bought 0%, first-second 4.1%, risk low, insiders hold 0%. Dev 6b3F..., 1 launch in 7d. launchedAt 1791528845 = 2026-10-09T06:54:05Z (matches creation tx).
• QUANTY: report — status no_bundle, bundled 0%, dev bought 5%, first-second 5%. Dev BdiiKF1..., 1 launch in 7d.
• Conclusion: the scanners found no evidence that one operator secretly bought a coordinated block of either coin at launch. The later wallet sales are a separate issue covered in §07.

Shared wallets across both launches

• Launch-wallet lists (pasted from isitbundled reports, filed as launch_wallets_awzf.txt (41) + launch_wallets_quanty.txt (62), overlap in launch_wallets_overlap.txt): 3 wallets in BOTH launches — 5BRh7o6n7r3opLpwppohh6WUqnPW1HA81vZLhPTzkcPW, GTfHPpyyoC6X4uxmhLBWzovQCsSMZ8cfckPt8dcxeKcq, ssssswdk4RR8HqkE3uwUWzDbd6mXFTTPjcXBKNzQ57E. Treasury 5DvXH... in QUANTY list; demo wallet 8pyD... in neither (later buyer, funded 09:24:59Z).

What happened to the first 20 buyers?

• Full tables: crawlscan_early_buyers_awzf.csv + crawlscan_early_buyers_quanty.csv.
• Bubblemaps (InsightX Atlas is JS-only — server fetch returns empty, screenshot them): AWZF launch map (~07:00Z Oct 9) · QUANTY map (~16:58Z Oct 10).
• AWZF's first 20 buyers acquired 37.2% of the supply within two seconds. All 20 later sold their complete positions. One of those wallets also appeared in QUANTY's launch list. Open the AWZF report.
• QUANTY's first 20 buyers acquired 43.4% within one second, and all 20 later sold everything. Buyer #1 was the developer wallet, which received 5% and later moved it to the project treasury. Two early wallets also appeared in AWZF's launch list. This shows highly speculative early trading, but does not prove that all the wallets had one owner. Open the QUANTY report.

Proxima.Tools context

Bishop's public Telegram profile advertises Proxima.Tools and a referral code for it. Proxima is a token-launch service. A separate tutorial in which Bishop reportedly demonstrates its bundling and wallet-management features still needs to be linked here. Until that source is added, this page does not treat familiarity with the tool as proof that Bishop controlled any unattributed wallet.

07 — Wallet sales

What the developer-linked wallets sold

The records show large sales from the same project treasury across both coins. For QUANTY, the developer's entire 5% allocation moved through that treasury and was sold. For AWZF, the treasury was the largest identified seller.

QUANTY — the developer's 5% was sold within 74 minutes

1. Dev BdiiKF1... takes 50M (5%, buyer #1) at creation, 14:28:30Z Oct 10 — crawlscan + isitbundled devBoughtPct: 5 agree.
2. Dev → treasury 5DvXH..., 50,000,000, 15:42:09Z — 8XwCAvtn....
3. Treasury → pool, 50,000,000, 15:42:20Z — 11 seconds later — 64d4UTUV.... Treasury is the #8 QUANTY seller; dev never sold directly — it routed the whole allocation through treasury first.

AWZF — the project treasury was the largest identified seller

• 15:42:35Z, 26,564,224 — EP9EoB2C...
• 15:45:41Z, 23,610,057 — 5nQeMWPu...
• 11:40:22Z, 20,431,227 — 31KcBA9z...
• Four smaller morning sells 08:29–08:58Z (~2.2M total). 7 sells, 72,769,743 total, net sold 22.6M after pool rebuys. (Export window starts Oct 10 08:28Z; pre-window fills aren't covered. Creator 6b3F... never held supply — SOL pass-through only, balance 0.)

The largest sales happened together

QUANTY's final 50 million were sold at 15:42:20 UTC. Fifteen seconds later, the same treasury sold 26.6 million AWZF, followed by another 23.6 million AWZF three minutes later. The largest sales in both coins therefore occurred within the same four-minute period.

Wallets we cannot safely attribute

• Biggest QUANTY sellers (106M/83M/82M) bought from the pool first: no dev link, could be snipers. Unattributed.
• QUANTY holder #2 (ArTaDh..., 39M) is a net buyer, not a dumper.
• ARu4n5mF... dumped both coins (66.6M QUANTY + 52.3M AWZF): same operator, unattributed.

08 — Community takeover

Community takeover

AWZF is no longer Bishop's project. After he left and the linked project promises disappeared, holders organized a community takeover. The community is preserving the evidence, the story, and the original idea of making quantum computing easier for ordinary crypto users. Follow the verified CTO account on X for official updates.

• If you have watched a promising project disappear after its creator moved on, you can help by preserving evidence, sharing the archive, and following @AWZF_Coin.