This is a public recap of the second meeting in the proposal series. Unlike Meeting #1, the whole recording of this session is published: Shaka confirmed on 14 November 2026 that it may be transcribed and shared, and the participants gave a thumbs-up to recording at the opening. Even so, this page is a recap—not minutes, a membership registry, a treasury decision, or a claim that the Open Source Orchestra DAO has been adopted or deployed.
Who was in the circle
First names only, as spoken in the recording and as Shaka wrote them. Two 4Seas hosts say a brief hello at the very end. No other attendee data is published.
What actually happened
- Shaka opened by confirming everyone had agreed to be recorded, framed the call as the second DAO-proposal and Devcon 8 retrospective circle, and said plainly: there will be no token for OSO, and the main goal is simply to play more music together.
- He described the current state as he sees it: no on-chain activation beyond the ability to receive donations, with osoartist.eth subnames, own-wallet connection and agent-held x402 wallets “in the works” for tips to individual artists or the whole orchestra equally.
- Aakaash, Sha and Vipul introduced themselves and what Devcon 8 meant to them: a stage where coders came to decompress, where people sang in public for the first time, and where Ethereum showed itself as culture, not only code.
- Shaka screen-shared this virtual hall, the OG Circle and the orchestra’s history from Devcon Bogotá and Amsterdam through Bangkok, Buenos Aires and Mumbai, and pointed everyone to devcon.org/lisbon and opensourceorchestra.org.
- The call closed with gratitude, an open invitation to play at 4Seas in Chiang Mai, and a quick hello from the 4Seas hosts as their next session began.
What was proposed — not decided
- Every contribution equal: code, voice, sound engineering, logistics and hosting all count the same in whatever the OSO DAO becomes.
- Gift first, receipts after: musicians keep showing up voluntarily, as tourists and friends, never as employees; if grants ever arrive, the first proposals would be reimbursement requests with receipts for Devcon 8 travel—retroactive, not transactional up front.
- Pay it forward: a hope that more than half of participants would take no funds and vote their share toward shared needs for about three years—for example a permanent European backline for the road to Lisbon, building on instruments already living in Prague, Barcelona, Berlin and Chiang Mai.
- Sanctuary, not schedule: propose a Devcon 9 Lisbon music sanctuary where stewardship, not slots, shapes who plays.
- Sha’s ideas: record a shared Devcon 9 song remotely and play it live; donate any surplus to local music initiatives wherever the orchestra lands; connect with Portuguese musicians and their instruments; invite music-tech makers to lend new gear.
- Consent on a ledger: a wallet address or steward-protected subname as the way to say “I am in,” so retroactive thanks can find people; multi-sig treasuries and co-stewarded agents as later experiments.
- Copyright care: Vipul’s offer to help protect the orchestra’s music and watch for infringement in India.
None of these were voted on, funded, scheduled or signed. There is no treasury, no grant, no reimbursement, no backline purchase and no Lisbon venue.
Recording, notes, transcript, audio
A verified 56:47.709 recording was transcribed locally with faster-whisper; the media never went to a transcription service. The session was scheduled for 95 minutes, so the recording is the whole record we have.
Read the high-level notes → Ten themes with actual versus proposed clearly separated.
Read the full transcript → 24 speaker turns, 542 lines, about 9,200 words, with timestamps that seek the audio.
Listen → 27 MB mono MP3 with captions. Machine-readable state: status.json.
The path remains a proposal
- Listen: reconcile IN / LATER / NO equally across both time-zone circles; silence is never a yes.
- Practice: keep the community Git ledger, privately verified humans and equal off-chain signalling before any tool is adopted.
- Choose together: any retroactive-reimbursement protocol, backline fund or consent ledger is adopted only after the whole circle explicitly agrees, with privacy, recusal and appeal rules readable.
- Execute only if chosen: human-only signers and public receipts after rehearsal, legal/tax review and community approval. Agents never hold keys or votes.