THE COMMUNITY ARCHIVE / COVERAGE-LIMITED EDITION
A chain is made
of people.
For Stackchain enjoyers and Stackchain Magazine readers: the people, forks, memes and moments behind the tip.
Browse a familiar name, follow a source, or bring a memory we’re missing. This is an independent community reading room—not a leaderboard or a complete history.
How to read this archive: documentary sources support specific claims; oral history records what a contributor remembers. Candidate portraits remain unverified. Open the evidence and its limits before treating a story as settled.
FROM THE RECORDINGS / BURNCHAIN
A little of the room, preserved.
A surviving conversation about Burnchain—not its original announcement. In Stackchain SJ Lottery, the host asks about a project already started; the respondent explains a block-by-block practice of burning Bitcoin and posting evidence.
Published January 30, 2023 · excerpt from 02:07.00–03:52.70 in the original recording
Download the excerpt (MP3)Original episode ↗Publisher description ↗
The excerpt retains the respondent’s uncertainty about whether sending to the genesis address actually burns coins. Technical speculation is not a verified Bitcoin claim. The publication date is not a verified recording date or Burnchain genesis date; the original announcement remains unfound.
Reading companion, source offsets & attribution
This is an editorial excerpt, not the full discussion. These listening notes summarize audio-derived evidence, not a verbatim or speaker-verified transcript. Times below refer to the original recording; the player starts at zero.
- About 02:16–02:18: the host asks about a burn chain already started.
- About 02:22–02:49: the respondent describes burning some Bitcoin, posting evidence and making the next block.
- About 02:57–03:23: discussion of unspendability, addresses and OP_RETURN.
- About 03:24–03:52.70: the respondent describes sending to the genesis address, then explicitly says they have not confirmed actual burning.
Publisher attribution: the episode description credits Skinner with the opening Burnchain discussion. This supports context, not independent identification of the exact voice. The host is not identified here.
Contributor oral history · not independently corroborated: Alexander Whitestone self-identifies as burntoshi, skinner, Rockachopa and bitcoin Squanto, and recalls introducing Burnchain in a Stackchain Space. Those statements do not independently establish ownership of a particular account or authorship of a particular post or voice.
Alexander credits a fellow Burnchainer, The 🪨, with creating the later burner address—not himself. This is a contributor’s address-creation attribution, separate from the earlier introduction story; it does not prove transaction authorship or unspendability. No further identity is inferred.
BEYOND THE PEOPLE
Many threads. An incomplete map.
#stackchain · #stackchaintip · #burnchain · #stackjoin
Absence here is not evidence of absence.
READ THE FINE PRINT
Evidence before mythology.
A contribution, not a biography
These 18 portraits describe public Stackchain activity. Selection favors concrete contributions, not fame, wealth, or an all-time ranking. Discovery is weighted toward Anthony’s Spaces and Alexander / Skinner’s archive. Other participants and chains are underrepresented.
Different records, different weight
Documentary-backed means a profile has documentary support—not that every claim in it is verified. Participant publications are attributed recollections. Public purchase posts are not independent audits of payments, donations, or holdings.
Candidates remain candidates
Five portraits rely on unverified machine-transcript candidates. ASR can hallucinate words and merge speakers. Presence on a stage is not voice attribution. Segment offsets are not word-level timings. The original portrait research did not add audio verification; earlier reviewed audio is labeled as inherited. The separate Burnchain listening feature adds a checked excerpt and audio-derived notes, without upgrading any portrait’s evidence tier.
What this edition cannot establish
The research read 31 base transcripts; 15 additional discovered Spaces lacked accessible metadata or replay. Some handles are historical. Mutable project documents do not prove when every line was written. Only explicit reply edges are evidence of ancestry; a full chain to genesis is not reconstructed.
The Burnchain listening notes separately label Alexander’s contributor oral history. It is not merged into the documentary record or used to upgrade profile evidence. Corrections should identify the profile, the claim, and a public source; use your existing contact with Alexander. This website has no submission endpoint. Source links open external websites only when you choose them.
A COMMUNITY PROJECT, BUILT WITH PERMISSION
Were you there? Add your side.
A missing meme, a remembered Space, a fork you helped build: start with one moment. Tell us what you recall, what you can source, and how you want to be credited.
Write a memory locally → Take the questionnaire with you ↓
This archive is being developed as a multi-contributor public history—not a private assistant opened to the public. Alexander is the initial publication editor. Participation is opt-in: offer your own recollections, public source links, dated recordings, or a specific correction. Public handles and chosen pseudonyms are enough.
Contribute, then review
Start with the questionnaire or browser worksheet below. Keep your original answers. If you choose to share them through your existing contact with Alexander, include attribution, permission scope, and any restrictions. Unanswered permission means research-only. Forwarding an interview is not consent to publish it.
Corrections stay attached to evidence
Identify the profile or history entry, the disputed wording, and supporting public sources. The editorial workflow calls for preserving originals separately, labeling testimony and uncertainty, reviewing a specific draft with its contributor when approval is required, and retaining a revision and correction trail. There is no automatic publication of submissions.
Group participation, outreach and Telegram interviews are planned, not connected here. Joining a group or allowing a bot does not authorize publication of every member’s words. A dedicated community service will require separate consent, privacy boundaries, retention rules and testing. This page has no multi-user backend, live Telegram bot or public access to a personal assistant. The browser interview export stays local until you choose to share the downloaded file.
Open the local interview worksheet ↓ADD YOUR SIDE OF THE STORY
Remember it in your own words.
Download the questionnaire or use the structured worksheet below. This is not generative chat. Live Timmy interviews are not connected. Answers stay in this tab until you download them; nothing is uploaded or automatically saved. Closing or reloading the page loses your answers.
Download interview questionnaire ↓
Do not include seed phrases, passwords, holdings, home addresses, private contacts, or other people’s private messages. Skip any story question. Exporting is not submission or publication.