diff --git a/.gitignore b/.gitignore index 15511dc..2cb7b53 100644 --- a/.gitignore +++ b/.gitignore @@ -23,3 +23,8 @@ grant-application/TESTER_GUIDE.md grant-application/TEAM_UPDATE_EMAIL.md grant-application/DEMO_VIDEO_SCRIPT.md grant-application/OUTREACH_MESSAGES_JUL2026.md +# Outreach and call material naming individuals and private reply status — local only, shared with the grant team directly +grant-application/ECOSYSTEM_OUTREACH_SEP2026.md +grant-application/M3_DAO_ACQUISITION_PLAN.md +grant-application/BITFLOW_CALL_SCRIPT.md +grant-application/PITCH_DECK_COMMUNITY_CALL.md diff --git a/frontend/src/lib/constants.ts b/frontend/src/lib/constants.ts index c153a00..cb7e594 100644 --- a/frontend/src/lib/constants.ts +++ b/frontend/src/lib/constants.ts @@ -124,8 +124,8 @@ const MAINNET_TOKENS: readonly TokenConfig[] = [ symbol: "sBTC", name: "Stacks BTC", decimals: 8, - contractId: "SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.token-sbtc", - ftName: "sbtc", + contractId: "SM3VDXK3WZZSA84XXFKAFAF15NNZX32CTSG82JFQ4.sbtc-token", + ftName: "sbtc-token", icon: "/bitcoin.svg", description: "Native Bitcoin on Stacks — the flagship streaming token", }, @@ -143,7 +143,7 @@ const MAINNET_TOKENS: readonly TokenConfig[] = [ name: "ALEX", decimals: 8, contractId: "SP102V8P0F7JX67ARQ77WEA3D3CFB5XW39REDT0AM.token-alex", - ftName: "token-alex", + ftName: "alex", icon: "/alex.svg", description: "ALEX DeFi protocol token", }, @@ -184,7 +184,7 @@ export const SUPPORTED_TOKENS: readonly TokenConfig[] = IS_MAINNET export const DEFAULT_TOKEN = SUPPORTED_TOKENS[0]; /** - * Lookup a TokenConfig by its on-chain contract identifier (e.g. "SP3K8...token-sbtc"). + * Lookup a TokenConfig by its on-chain contract identifier (e.g. "SM3VDX...sbtc-token"). * Falls back to DEFAULT_TOKEN when not found so callers always get a non-null * record. Used by transaction builders to derive the ftName for post-conditions. */ diff --git a/frontend/src/lib/stacks.ts b/frontend/src/lib/stacks.ts index 47a0258..a3be0b3 100644 --- a/frontend/src/lib/stacks.ts +++ b/frontend/src/lib/stacks.ts @@ -220,7 +220,7 @@ export async function isRegisteredDao(admin: string): Promise { export function buildCreateStreamTx(params: { recipient: string; tokenContract: string; - /** Fungible token asset name inside the contract (e.g. "sbtc", "mock-sbtc", "usda") */ + /** Fungible token asset name inside the contract (e.g. "sbtc-token", "mock-sbtc", "usda") */ ftName: string; depositAmount: bigint; startBlock: number; @@ -380,7 +380,7 @@ export function buildCancelStreamTx(params: { export function buildTopUpStreamTx(params: { streamId: number; tokenContract: string; - /** Fungible token asset name inside the contract (e.g. "sbtc", "mock-sbtc", "usda") */ + /** Fungible token asset name inside the contract (e.g. "sbtc-token", "mock-sbtc", "usda") */ ftName: string; amount: bigint; senderAddress: string; @@ -473,7 +473,7 @@ export async function getCurrentBlockHeight(): Promise { export async function getTokenBalance( address: string, tokenContract: string, - /** Fungible token asset name inside the contract (e.g. "sbtc", "mock-sbtc", "usda") */ + /** Fungible token asset name inside the contract (e.g. "sbtc-token", "mock-sbtc", "usda") */ ftName: string ): Promise { if (!address) return 0n; diff --git a/grant-application/CONTENT_SCHEDULE.md b/grant-application/CONTENT_SCHEDULE.md index 88e96e4..90d8c0d 100644 --- a/grant-application/CONTENT_SCHEDULE.md +++ b/grant-application/CONTENT_SCHEDULE.md @@ -1,769 +1,1051 @@ -# StackStream Content Schedule — July 2026 (Jul 13 to Aug 11, 30 days) +# StackStream Content Schedule: Sep 14 to Oct 13, 2026 (30 days) -> Companion to `MARKETING_PLAN_V2.md`. Working draft, subject to team review. -> One narrative per day, rewritten for every channel that fires that day, in that channel's own voice. -> The June schedule this replaces lives in git history. - -**The job of this month:** move the north-star number. Baseline was 9 streams on Jul 8; the target is 40 by Aug 7 and every day below exists to onboard someone new or keep someone we already onboarded. Persuade, prove, remove friction, repeat. +> Same 30 days and day numbers as `DESIGNER_BRIEF_SEP2026.md`. Who gets a message, and the messages themselves: `ECOSYSTEM_OUTREACH_SEP2026.md` and `M3_DAO_ACQUISITION_PLAN.md`. Voice and settlement rules: `MARKETING_PLAN_V2.md`. --- -## The six channels and how each one sounds +## Where we stand -| Channel | Who is reading | Voice | +| Fact | Value | Source | |---|---|---| -| **Official X** (@Stackstream0X) | The wider ecosystem and newcomers | The brand. Clear, warm, confident. We. | -| **Personal X** (@dev_jayteee) | Builders who follow the founder | You, the founder. I. Honest, behind the scenes, real. | -| **LinkedIn** | Founders, operators, people with budgets | Professional and calm. A little longer. Value and credibility. | -| **Stacks Forum** | Stacks developers and ecosystem peers | Thoughtful, discussion-first. Honest about live vs roadmap. Used sparingly. | -| **Grantees Telegram** | Fellow grant recipients, peers | Builder to builder. Casual, supportive, feedback-seeking. Never salesy. | -| **WhatsApp (status)** | Close network, friends, early supporters | Like texting a friend. Very short. Soft. | +| Streams created on mainnet | **11** | `stackstream.xyz/api/stats`, Sep 21, 10:00 UTC | +| Organisations registered | **0** | same | +| Tests | **125, all passing**, across 2 test files, including property-based fuzz tests | `npx vitest run`, verified Sep 15 | +| Security | Independent paid bounty audit before mainnet. Zero critical findings, every real bug fixed in v1.0.0-rc2 | `audits/AUDIT_REPORT_v1.0.0.md` | +| Live | Stacks mainnet since May 2026 | `deployments/default.mainnet-plan.yaml` | --- -## The rules every post obeys +## What we are proving -**Voice:** talk to a person, lead with the feeling or problem, one idea per post, plain words, no jargon (no escrow, protocol, SIP-010 in social copy), clean punctuation, no em dashes. The line we repeat: **real-time money, settled on Bitcoin.** +**Internally**, the goal is the M3 target: 3 organisations registered and $10,000 streamed. It is never stated in public and never tied to a date. -**Settlement language:** never put the every-few-seconds rhythm and Bitcoin settlement in the same clause. The rhythm is how often the stream updates. Bitcoin finality comes when settlement anchors to Bitcoin, on Bitcoin's own schedule. Say "streams update in seconds; settlement inherits Bitcoin finality" for technical readers, or "your balance updates every few seconds, secured by Bitcoin" in social copy. Never say "settling on Bitcoin every few seconds" or "once it lands, it is final." +**Publicly**, every piece of content works toward two outcomes: **real proof of usage for the Stacks Endowment**, and **StackStream serving the ecosystem's payment needs efficiently**. -**North star:** every post is judged by one question, does it give someone a reason to open a stream? Pull the live number from **stackstream.xyz/api/stats** before every metrics post. Never estimate, never round up. +Four points every post can stand on: -**CTA:** every public post ends with exactly one destination, written as a full link on its own final line. Default **https://stackstream.xyz**. Use **https://t.me/dev_jaytee** when the ask is "talk to us". Forum and Grantees TG stay soft (one light link at most, never a pitch). +1. **It has a real audience.** DAOs, grant programmes, and contributors across Stacks pay and get paid by hand today. +2. **It is safe.** Independently audited, 125 passing tests, and funds sit in the contract, never with us. +3. **It is live.** On Stacks mainnet, works with any token on Stacks, no fee from us. +4. **Both sides benefit.** Recipients claim as they earn. Payers keep full control: pause, top up, or cancel, with unearned funds returned instantly. -**Selling points to keep warm:** 1) Settled on Bitcoin, final and irreversible once settled. 2) Real-time, balance moves every few seconds. 3) Any token on Stacks, sBTC, STX, USDA, ALEX, all of them. 4) The sender never loses control, pause, top up, cancel, reclaim. +**The public call:** real teams using StackStream is how it proves it serves the ecosystem, and shows the Stacks Endowment a product that grows natively, over time and space. --- -## The weekly rhythm +## Voice and length + +**Tone:** professional but light. Persuade with benefits and proof, never hype. + +| Format | Length | +|---|---| +| X post | One post, 280 characters or fewer including the link | +| WhatsApp status | One line | +| Grantees Telegram, Stacks Discord | 100 words or fewer | +| LinkedIn, Stacks Forum | 100 to 200 words | +| Outreach DM | 100 to 200 words, follow-ups under 60 | -| Slot | Format | Persuasion job | +| Channel | Voice | Asset ratio | |---|---|---| -| **Monday** | Metrics, the real number | Social proof that compounds. Nobody else posts verifiable numbers weekly. | -| **Tuesday** | Idea or feature | Teach one thing that makes streaming feel obvious. | -| **Wednesday** | Proof | Video, receipt, live clip. Seeing beats reading. | -| **Thursday** | Objection or friction killer | Answer the exact doubt that stops a signup. | -| **Friday** | Segment spotlight | One audience per week pictured using it: DAOs, freelancers, merchants, grants. | -| **Saturday** | Human note | Founder story, behind the scenes, warmth. Trust is the product. | -| **Sunday** | Educate or vision | Evergreen ideas travel on weekends. | +| Official X (@Stackstream0X) | We. Clear, warm, confident | 1:1 | +| Personal X (@dev_jayteee) | I. Honest, behind the scenes | 1:1, or none on human-note days | +| LinkedIn | Calm, professional, value-led | 4:5 | +| Stacks Forum | Discussion-first, precise terms allowed | 16:9 | +| Stacks Discord | Receipts and help, never announcements | 16:9, or none | +| Grantees Telegram | Builder to builder, never salesy | None | +| WhatsApp status | Like texting a friend | 9:16 | + +--- -LinkedIn fires about twice a week. Forum twice this month. Grantees TG five genuine touches. WhatsApp most days, one soft line. +## The four doors + +| Door | Who | What they get | Days | +|---|---|---|---| +| **1. DAOs and teams** | Bitflow, Zest, Stacking DAO, Velar, Taptive | Payroll set once, contributors claim anytime, full control kept | D5, D9, D23, D26 | +| **2. Grant and bounty programmes** | Stacks Endowment, DeGrants, PaySats, DeepStack | Funds release as work ships, unreleased funds stay with the funder, the payment is the report | D10, D12, D24 | +| **3. People being paid** | Contributors, freelancers, creators | Pay grows while they work, claimed anytime on the Earn page | D6, D11, D19 | +| **4. Subscriptions** | Listen only this run | Charges only while the service is used | D7 | + +**Distribution layer:** Xverse (Ken Liao), Stacks Labs (Alex Miller, Andre Serrano), and Muneeb Ali, held until a team registers. Their days: D14, D16, D17, D21, D24. + +**Private scoreboard, every Sunday:** per door, record conversations opened, replies, calls, organisations registered, streams funded by others, value streamed, and unprompted inbound. A registration or funded stream beats a call, and a call beats a reply. Day 30 names the door with the most pull. Value streamed stays on the scoreboard only. + +--- + +## Rules + +- **Numbers:** [N] streams and [D] organisations from `stackstream.xyz/api/stats` on the morning of posting. Never estimate. Any stream we open ourselves is labelled as ours. +- **Security claims:** say "independently audited" and "125 passing tests". Re-run the suite before Day 24 in case the count changed. +- **No deadlines anywhere. No target figures or amounts in public.** +- **Settlement:** never put the update rhythm and Bitcoin settlement in the same clause. Social: "your balance updates every few seconds, secured by Bitcoin". Technical: "streams update in seconds; settlement inherits Bitcoin finality". +- **No jargon** in social copy or on assets: escrow, protocol, primitive, SIP-010, vault. Forum posts and Days 10 and 24 may be precise. +- **Link:** every post ends with https://stackstream.xyz. Developer days may use the GitHub repo. Explorer links go in the first reply. Telegram only in DMs and replies. +- **Follow line:** every post carries a follow ask for the official page, placed just before the final link: "Follow @Stackstream0X for the weekly numbers." on X and LinkedIn, "Weekly numbers on X: @Stackstream0X." on Forum, Discord and Grantees Telegram, and "X: @Stackstream0X" appended to the WhatsApp line. The link still stays last. Effective from Day 3, Sep 16. +- **Handles:** @Stackstream0X, @dev_jayteee (three e's), t.me/dev_jaytee (two e's). +- **DMs** go from @dev_jayteee only. @Stackstream0X engages each target two to three days first. +- **No team named** without written permission, and nothing posted before the transaction confirms. +- **Style:** no em dashes. Personal says "I", Official says "we", never the same words. +- **Assets:** if one is late, post the words alone. Never stock imagery. + +--- + +## Weekly rhythm + +**Mon** the number (A) · **Tue** one idea (B) · **Wed** proof (H or C) · **Thu** one objection (D) · **Fri** one door (E) · **Sat** human note (F) · **Sun** a bigger idea. + +**A missed day is skipped, not reposted.** The calendar does not shift and no day carries two posts. Weekends count. LinkedIn about twice a week, Forum four times, Discord on Days 3, 10, 17 and 24, Grantees Telegram five touches, WhatsApp daily. + +--- + +## Outreach calendar + +Follow-ups at three and ten days, then stop. + +| Send | Person | Door | Follow-ups | +|---|---|---|---| +| Tue Sep 15 | **Bitflow**, via your existing thread with the Bitflow account, asking for Dylan Floyd | 1 | Sep 18, Sep 25 | +| Tue Sep 15 | **Rena Shah**, Stacks Endowment. Replied Sep 18: will try it after the Q3 TC meeting in Cayman | 2 | None. Check in after the meeting | +| Wed Sep 16 | **Grant Nissly**, Taptive and Stacks Labs. LinkedIn only, already connected, message directly | 1 | Sep 21 (slipped from Sep 19), email Sep 28 if silent | +| Wed Sep 23 | **Tycho Onnasch**, Zest and Stacking DAO. Followed Sep 21, message two days later | 1 | Sep 26, Oct 3 | +| Tue Sep 22 | **DeGrants stewards** via @zeroauthdao | 2 | Sep 25, Oct 2 | +| Wed Sep 23 | **Mithil Thakore**, Velar | 1 | Sep 26, Oct 3 | +| Fri Sep 25 | **PaySats and DeepStack**, fellow grantees | 2 | Oct 2 | +| Mon Sep 28 | **Alex Miller**, Stacks Labs | Distribution | Oct 1, Oct 8 | +| Tue Sep 29 | **Andre Serrano**, sBTC go-to-market | Distribution | Oct 2, Oct 9 | +| Wed Sep 30 | **Ken Liao**, Xverse | Distribution | Oct 3, Oct 10 | +| Fri Oct 2 | **Three content creators**, M3 Template E, only if Tycho is silent | 3 | Oct 5 | +| Hold | **Muneeb Ali**, until a team registers. One message, no follow-up | Distribution | None | --- ## Which channels fire each day -| Day | Narrative | Off. X | Pers. X | LinkedIn | Forum | Grantees TG | WhatsApp | -|---|---|:--:|:--:|:--:|:--:|:--:|:--:| -| Jul 13 | Day one: the counter starts | ✓ | ✓ | | | ✓ | ✓ | -| Jul 14 | The tap, not the bucket | ✓ | ✓ | | | | ✓ | -| Jul 15 | Demo video launch | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| Jul 16 | Your first five minutes | ✓ | ✓ | | | | ✓ | -| Jul 17 | Payday that runs itself (DAOs) | ✓ | ✓ | ✓ | | | ✓ | -| Jul 18 | Where the money actually sits | ✓ | ✓ | | | | ✓ | -| Jul 19 | Why Bitcoin | ✓ | ✓ | | | | ✓ | -| Jul 20 | Metrics, week 2 | ✓ | ✓ | | | | ✓ | -| Jul 21 | Ask the chain (OpenClaw) | ✓ | ✓ | | | | ✓ | -| Jul 22 | Show the receipt | ✓ | ✓ | | | ✓ | ✓ | -| Jul 23 | Any token you hold | ✓ | ✓ | | | | ✓ | -| Jul 24 | Paid as you work (freelancers) | ✓ | ✓ | ✓ | | | ✓ | -| Jul 25 | Three steps, one offer | ✓ | ✓ | | | | ✓ | -| Jul 26 | Subscriptions that feel fair | ✓ | ✓ | ✓ | | | ✓ | -| Jul 27 | Metrics, week 3 | ✓ | ✓ | | | | ✓ | -| Jul 28 | Life changes, streams adjust | ✓ | ✓ | | | | ✓ | -| Jul 29 | The assistant, on camera | ✓ | ✓ | | | | ✓ | -| Jul 30 | Fund in stages (grants) | ✓ | ✓ | ✓ | | ✓ | ✓ | -| Jul 31 | Meet a streamer (spotlight) | ✓ | ✓ | | | | ✓ | -| Aug 1 | The real cost of waiting | ✓ | ✓ | | | | ✓ | -| Aug 2 | Where this goes (cross-chain) | ✓ | ✓ | | ✓ | | ✓ | -| Aug 3 | Metrics, week 4 | ✓ | ✓ | | | | ✓ | -| Aug 4 | Your salary is personal (privacy) | ✓ | ✓ | | | | ✓ | -| Aug 5 | Watch a claim, start to finish | ✓ | ✓ | | | | ✓ | -| Aug 6 | Open code, tested funds | ✓ | ✓ | ✓ | | | ✓ | -| Aug 7 | Target day: the honest result | ✓ | ✓ | | | | ✓ | -| Aug 8 | You asked, we answer | ✓ | ✓ | | | | ✓ | -| Aug 9 | The money people trust most | ✓ | ✓ | | | | ✓ | -| Aug 10 | Metrics + the month in review | ✓ | ✓ | ✓ | | ✓ | ✓ | -| Aug 11 | The open invitation | ✓ | ✓ | | | | ✓ | - -**Before Jul 13:** shoot the 60 second demo (script in local ops docs), cut the three crops plus the 10 second loop and the receipt shot, and run the 30 minute June engagement review. If the review contradicts a format below, swap the content, keep the rhythm. - ---- - -## Week 1 — Make them believe (Jul 13 to Jul 19) - -### Jul 13 (Mon) — Day one: the counter starts - -> Pull [N] from stackstream.xyz/api/stats. Baseline was 9 on Jul 8. +| Day | Date | Narrative | Asset | Off. X | Pers. X | LinkedIn | Forum | Discord | TG | WhatsApp | +|---|---|---|---|:--:|:--:|:--:|:--:|:--:|:--:|:--:| +| 1 | Mon Sep 14 | The call to real teams (posted) | A | ✓ | ✓ | | | | ✓ | ✓ | +| 2 | Tue Sep 15 | The tap, not the bucket (posted) | B | ✓ | ✓ | ✓ | | | | ✓ | +| 3 | Wed Sep 16 | Watch it move (posted) | H | ✓ | ✓ | | | ✓ | | ✓ | +| 4 | Thu Sep 17 | Where the money actually sits (posted) | B, D | ✓ | ✓ | | | | | ✓ | +| 5 | Fri Sep 18 | Payday that runs itself (posted) | E | ✓ | ✓ | ✓ | | | | ✓ | +| 6 | Sat Sep 19 | Why I built this (skipped) | F | ✓ | ✓ | | | | | ✓ | +| 7 | Sun Sep 20 | Money that moves like water (skipped) | E | ✓ | ✓ | | | | | ✓ | +| 8 | Mon Sep 21 | The number, week 2 (posted) | A | ✓ | ✓ | | | | | ✓ | +| 9 | Tue Sep 22 | You are never locked in (posted) | B | ✓ | ✓ | | | | | ✓ | +| 10 | Wed Sep 23 | A real transaction | C | ✓ | ✓ | | | ✓ | ✓ | ✓ | +| 11 | Thu Sep 24 | What if nobody claims it? | D | ✓ | ✓ | | | | | ✓ | +| 12 | Fri Sep 25 | Grants that release as work ships | E, B | ✓ | ✓ | ✓ | | | ✓ | ✓ | +| 13 | Sat Sep 26 | The number nobody wants to post | F | ✓ | ✓ | | | | | ✓ | +| 14 | Sun Sep 27 | Nobody else can do this bit | G | ✓ | ✓ | ✓ | ✓ | | | ✓ | +| 15 | Mon Sep 28 | The number, week 3 | A | ✓ | ✓ | | | | | ✓ | +| 16 | Tue Sep 29 | Any token you actually hold | B | ✓ | ✓ | | | | | ✓ | +| 17 | Wed Sep 30 | Two minutes, start to finish | H, C | ✓ | ✓ | | | ✓ | | ✓ | +| 18 | Thu Oct 1 | What does it cost? | D | ✓ | ✓ | | | | | ✓ | +| 19 | Fri Oct 2 | Paid as you work | E | ✓ | ✓ | ✓ | | | | ✓ | +| 20 | Sat Oct 3 | Building this alone | F | ✓ | ✓ | | | | | ✓ | +| 21 | Sun Oct 4 | Bitcoin is the difference | B | ✓ | ✓ | ✓ | ✓ | | | ✓ | +| 22 | Mon Oct 5 | The number, week 4 | A | ✓ | ✓ | | | | | ✓ | +| 23 | Tue Oct 6 | Cancel it and see | B | ✓ | ✓ | | | | | ✓ | +| 24 | Wed Oct 7 | Open code, tested | C | ✓ | ✓ | | | ✓ | ✓ | ✓ | +| 25 | Thu Oct 8 | Is it safe? | D | ✓ | ✓ | | | | | ✓ | +| 26 | Fri Oct 9 | How teams pay people today | E, B | ✓ | ✓ | ✓ | | | | ✓ | +| 27 | Sat Oct 10 | What I got wrong | F | ✓ | ✓ | ✓ | | | | ✓ | +| 28 | Sun Oct 11 | Where this goes | B | ✓ | ✓ | | ✓ | | | ✓ | +| 29 | Mon Oct 12 | The number, week 5 | A | ✓ | ✓ | | | | | ✓ | +| 30 | Tue Oct 13 | Thirty days in the open | A, G | ✓ | ✓ | ✓ | ✓ | | ✓ | ✓ | -**Official X** -> Today we start something most projects avoid. -> Every Monday we post our real usage number, straight from the smart contract: [N] streams opened on mainnet so far. -> Anyone can verify it, any time, at stackstream.xyz/api/stats. -> Watch it grow. Better yet, be in it. +--- + +## Week 1: What streaming is (Sep 14 to Sep 20) + +### Day 1, Mon Sep 14: The call to real teams (posted) + +> Posted on all channels Sep 14. Kept as the record, not for reposting. + +**Official X** (thread) +> DAOs and teams on Stacks pay real people every month. That money should not have to wait for payday. +> StackStream is live on mainnet. Balances grow every few seconds, secured by Bitcoin. Recipients claim anytime. Senders stay in full control. +> ↳ What comes next is real teams using it. Every stream they open shows how well this serves the ecosystem, and shows the Stacks Endowment a product built to grow natively, over time and space. +> The first seats are open. See it working for yourself. > https://stackstream.xyz -**Personal X** -> New habit starting today. Every Monday, our real number, no dressing up: [N] streams on mainnet. -> It comes straight from the contract's own counter, so I could not fake it if I wanted to. -> When you open a stream, you literally move this number. +**Personal X** (thread) +> What StackStream needs next is not more code. It is real teams. +> DAOs and projects paying real contributors through it. That is how we prove it fits this ecosystem, and how the Stacks Endowment sees it grow natively, over time and space. +> ↳ We are early. The product is ready. See what we have built, then let me set up your team's first stream with you. > https://stackstream.xyz **Grantees Telegram** -> Starting weekly public metrics today, [N] streams on mainnet. Posting the real counter every Monday even when it is flat, and you all know how much courage that takes. If any of you want to test a stream between our projects this month, I will set it up personally. +> Starting a new push today, and this room is where I want to begin. StackStream is live and working. The next step is real teams using it, because that is what proves it serves Stacks and shows the Endowment it can grow natively. If your project pays anyone, I would love to set up one stream with you and hear what you honestly think. Gas only, no catch. stackstream.xyz -**WhatsApp (status)** -> From today: our real numbers, every Monday. [N] streams on Bitcoin so far. stackstream.xyz +**WhatsApp** +> StackStream is live and ready. Now it is time for real teams. stackstream.xyz --- -### Jul 14 (Tue) — The tap, not the bucket +### Day 2, Tue Sep 15: The tap, not the bucket (posted) + +> `SS_D02_tap-bucket` (B) · Outreach: Bitflow thread, Rena Shah **Official X** -> Every payment you have ever received was a bucket. You waited, then someone handed it over. -> A stream is a tap. Always on, your balance rising every few seconds, and you take what you have earned whenever you like. -> Turn the tap on once and payday stops being a date. +> Most pay arrives like a bucket: once a month, and late. +> StackStream works like a tap. Your balance grows every few seconds, and you take what you have earned anytime. +> Payroll, grants, freelance work. Same tap, live on Stacks. > https://stackstream.xyz **Personal X** -> How I explain StackStream to my family: stop thinking in buckets, start thinking in taps. -> Money that arrives while you work, not weeks after. You scoop out what is yours anytime. -> Once you see it, you cannot unsee it. See it live. +> How I explain StackStream: the bucket and the tap. +> Bucket: work all month, get paid in one lump. +> Tap: pay flows every few seconds as you work. Fill your glass (your wallet) anytime. The payer controls the tap. +> Audited, live on Stacks. +> https://stackstream.xyz + +**LinkedIn** +> Your team works every day. Why does it only get paid once a month? +> +> Most payments are built around a date, not around the work. +> Payroll lands at month end. Invoices wait 30 days. Grants release on sign-off. The value is created continuously, yet the money arrives in one late lump. +> StackStream changes that. An organisation opens a stream once, the recipient's balance grows every few seconds, and they claim whenever they choose. The payer keeps full control and can pause, top up, or cancel, with unearned funds returned instantly. +> It is live on Stacks mainnet, independently audited, and backed by 125 passing tests. It serves groups already active in the ecosystem: DAOs paying contributors, grant programmes releasing funds, and the builders who get paid. +> If your team pays people, I would be glad to show you how it works. > https://stackstream.xyz -**WhatsApp (status)** -> Money like a tap, not a bucket. That is the whole idea. stackstream.xyz +**WhatsApp** +> Money like a tap, not a bucket. Live on Stacks today. stackstream.xyz --- -### Jul 15 (Wed) — DEMO VIDEO LAUNCH +### Day 3, Wed Sep 16: Watch it move (posted) -> The anchor of the month. Pin on both X accounts. All channels fire. +> `SS_D03_ticking-balance` (H), pin on @Stackstream0X · Outreach: Grant Nissly · If the loop is late, cut 10 seconds from the July demo **Official X** -> This is money arriving every 5 seconds. -> A real stream, live on mainnet. Not sped up, not a mockup, and the on-chain receipt is at the end so you can check every detail yourself. -> Watch it work, then open yours in three steps. +> Watch it move. +> A real balance growing in real time, with nobody pressing anything. +> This is getting paid on StackStream: every few seconds, secured by Bitcoin, yours to claim anytime. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -> (attach the 60s video) **Personal X** -> I have wanted to show you this properly for months. -> A real balance ticking up on its own while nobody touches anything, then the receipt on-chain for anyone to verify. -> This is what we built. 60 seconds. +> Eight seconds that explain a year of building. +> A number rising on its own while someone gets on with their work. Audited, live on mainnet, and ready for real teams. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -> (attach the 60s video) -**LinkedIn** -> Sixty seconds that explain our product better than any deck could. -> A payment on StackStream is not a monthly event, it is a stream. Work starts, money starts. The person earning watches their balance grow in real time and claims whenever they like. The sender keeps full control throughout, and settlement inherits Bitcoin finality. -> If your team, DAO, or business still pays in lumps and waits, watch this. +**Stacks Discord** (#building-on-stacks) +> Hi all, Jethro here, founder of StackStream. A quick look rather than a long read: this loop is a real stream on mainnet. A team opens a stream, the recipient's balance grows every few seconds, and they claim anytime. The team can pause, top up, or cancel, with unearned funds returned instantly. Any token on Stacks, independently audited, 125 passing tests, no fee from us. +> If you pay people from a Stacks project, one honest answer would help: what would stop you trying this? +> Weekly numbers on X: @Stackstream0X. > https://stackstream.xyz -> (attach the 60s video) -**Stacks Forum** — thread: "60 second demo: a live stream accruing on mainnet" -> Recorded a short demo of a real mainnet stream for people who would rather see the accrual than read about it. Balance updates in seconds; settlement inherits Bitcoin finality. The create transaction appears in the clip so you can verify it in the explorer. Happy to answer anything about edge cases, pause, resume, cancel. Feedback genuinely welcome. -> App and demo: https://stackstream.xyz - -**Grantees Telegram** -> The demo video is out. Some of you told me the real-time feel had to be obvious in the first five seconds, so that is exactly how it opens. Honest reactions wanted: does it land? - -**WhatsApp (status)** -> Watch money arrive in real time. 60 seconds, no tricks. stackstream.xyz (clip) +**WhatsApp** +> Eight seconds of money arriving in real time. stackstream.xyz · X: @Stackstream0X --- -### Jul 16 (Thu) — Your first five minutes +### Day 4, Thu Sep 17: Where the money actually sits (posted) + +> `SS_D04_where-money-sits` (B, D) **Official X** -> Here is your entire onboarding. -> Minute 1: connect a Stacks wallet. Minute 2: pick who you are paying, the token, the amount, the length. Minute 3: open the stream. -> Minutes 4 and 5 are you watching the balance move. No forms, no approval queue. +> While money streams, who holds it? +> Not us. Funds sit in an audited contract. Recipients claim only what they have earned, and senders reclaim only what has not been earned yet. +> Safe by design, not by promise. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> The bar I set for us: if you can send a message, you can send a stream. -> Connect, choose, open. Three screens. And if you get stuck anywhere, message me and I will walk you through it myself. -> https://t.me/dev_jaytee +> The first question I get: where is the money while it streams? +> In a contract neither side controls, and not even I can touch it. The contracts were independently audited before mainnet. +> Follow @Stackstream0X for the weekly numbers. +> https://stackstream.xyz -**WhatsApp (status)** -> Five minutes from wallet to your first live stream. Try it today: stackstream.xyz +**WhatsApp** +> While money streams, it sits in an audited contract, never with us. stackstream.xyz · X: @Stackstream0X --- -### Jul 17 (Fri) — Payday that runs itself (DAOs) +### Day 5, Fri Sep 18: Payday that runs itself (posted) + +> `SS_D05_payday-runs-itself` (E) · Follow-ups: Bitflow, Rena · @Stackstream0X starts engaging Zest and Stacking DAO **Official X** -> DAO treasurers: count the hours you lost to last month's payday. Signers, spreadsheets, reminders. -> Open one stream per contributor instead. They earn as they work and claim when they want. You pause, top up, or stop anytime, and unearned funds return to the treasury. +> A team of five at month end: a spreadsheet, a signer asleep, someone missed. +> Or five streams, opened once and already running. People claim when they want, and you stay in control. > Payday that runs itself. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -> (attach the claim shot from the demo) **Personal X** -> I have watched small DAOs burn a full day every month just to pay people. It always felt backwards. -> One stream per contributor, set once, runs itself. Your treasury stays yours the whole time. -> I will personally onboard any DAO's first stream, no charge, no catch. -> https://t.me/dev_jaytee +> Small teams lose hours every month just paying people. Nobody's job, everybody's problem. +> Five streams, set once, and the ritual stops. I will set up your first one with you. +> Follow @Stackstream0X for the weekly numbers. +> https://stackstream.xyz **LinkedIn** -> For DAO operators and distributed teams: payroll should not be a monthly project. -> Streaming flips it. One stream per contributor, opened once. People are paid continuously as they work, the treasury keeps control, and every payment settles with Bitcoin behind it. Register your DAO once and every payment is on the record for members to see. -> Less admin, fewer mistakes, happier contributors. +> Five people, one spreadsheet, and someone always paid late. +> For founders and operators of small distributed teams, payroll should not be a monthly project. At five people the work is real, but nobody owns it. Amounts get checked twice, signers get chased across time zones, and someone is always paid late. +> With StackStream, each person gets one stream, opened once. Their balance grows as they work, and they claim whenever they choose. Your team keeps full control: pause, top up, or cancel, with unearned funds returned instantly. It works with any token on Stacks, including sBTC, and takes no fee. +> It is live on mainnet and independently audited, so the smallest trial is low risk: one stream, one person, one month. I will set it up with you. +> Follow @Stackstream0X on X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Payday that runs itself. If you run a team, this one is for you. stackstream.xyz +**WhatsApp** +> Payday that runs itself. If you run a team, this is for you. stackstream.xyz · X: @Stackstream0X --- -### Jul 18 (Sat) — Where the money actually sits +### Day 6, Sat Sep 19: Why I built this (skipped, not reposted) + +> `SS_D06_why-i-built-this` (F) · Follow-up: Grant **Official X** -> The question everyone should ask first: while money is streaming, who holds it? -> Answer: nobody. Funds sit in an on-chain vault that neither side can raid. The recipient can only claim what they have already earned. Everything else stays the sender's, always reclaimable. -> Safety by design, not by promise. +> Our founder on why StackStream exists: +> "I have been paid late. So has everyone I know." +> So we built pay that arrives as the work happens, secured by Bitcoin. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> The first question my mother asked about StackStream: "but where is the money while it streams?" -> Fair question. It sits on-chain where neither side can touch what is not theirs. You can only ever claim what you earned, and I can only reclaim what you have not. -> That design is why I sleep well. +> I have been paid late. So has everyone I know. +> Not dishonestly late, structurally late: the work is done, then weeks of waiting for money already earned. +> StackStream is my answer to that. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> While money streams, nobody holds it but the chain. That is the safest version of trust. stackstream.xyz +**WhatsApp** +> I have been paid late. So has everyone I know. That is why I built this. stackstream.xyz · X: @Stackstream0X --- -### Jul 19 (Sun) — Why Bitcoin +### Day 7, Sun Sep 20: Money that moves like water (skipped, not reposted) + +> `SS_D07_like-water` (E) · Tonight: first private scoreboard review **Official X** -> We could have built this somewhere cheaper. We chose Bitcoin. -> Because when a payment is final, both sides can relax. No reversals, no waiting to see if it sticks. -> The most trusted money in the world should also be the most useful. +> Work flows. Value flows. Pay still arrives in lumps. +> Streams change that for contributors, grantees, freelancers, and subscribers alike. +> Money that moves like water, live on Stacks. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> People ask why I did not build on a cheaper chain. -> Because trust is the entire point of money. Streams update in seconds, and settlement inherits Bitcoin finality. I would rather build slower on the foundation everyone already trusts. -> That choice is the product. +> Music, video, and news all became continuous. Pay is still a lump on a date. +> I think that changes, because waiting for money you have already earned was never a feature. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Built on the money people trust most. On purpose. stackstream.xyz +**WhatsApp** +> Money that moves like water, not in buckets. stackstream.xyz · X: @Stackstream0X --- -## Week 2 — Prove it and lower the bar (Jul 20 to Jul 26) +## Week 2: Proof and control (Sep 21 to Sep 27) + +### Day 8, Mon Sep 21: The number, week 2 (posted) -### Jul 20 (Mon) — Metrics, week 2 +> `SS_D08_metric-card` (A), live counts only · Outreach: Tycho Onnasch **Official X** -> Monday numbers. -> [N] streams on mainnet, [+X] since last week. Live counter, straight from the contract, at stackstream.xyz/api/stats. -> Every one of these is a person or team who chose to get paid in real time. Join them. +> Week 2, straight from the contract: 11 streams. 0 teams registered. +> That 0 is our favourite number. It is a seat saved for the first @Stacks team to stream its pay. +> The product is ready. The seat is warm. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> Week 2 of honest Mondays: [N] streams, [+X] new. -> [One true sentence about what worked or what did not this week.] -> Open a stream this week and you are in next Monday's number. +> Monday numbers: 11 streams, 0 teams. +> Built with @StacksEndowment backing. Audited, live, ready. But code cannot pick its own first team. +> That part belongs to this ecosystem. I will do the setup myself. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> [N] streams and counting. Real number, every Monday. stackstream.xyz +**WhatsApp** +> 11 streams, 0 teams, and one seat saved for the first. stackstream.xyz · X: @Stackstream0X --- -### Jul 21 (Tue) — Ask the chain (OpenClaw) +### Day 9, Tue Sep 22: You are never locked in (posted) + +> `SS_D09_never-locked-in` (B) · Outreach: DeGrants stewards **Official X** -> Meet OpenClaw, the assistant living inside StackStream. -> Type a stream ID, it answers from the chain: status, deposit, what is claimable this second. Paste an address, get every stream flowing in or out of it. -> No block explorer, no guesswork. It is in the dashboard. +> Four controls, and your money stays yours. +> Pause when work stalls. Resume when it restarts. Top up when it runs long. Cancel when it ends, and unearned funds return instantly. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> My favorite underrated feature: an assistant that reads the blockchain for you. -> Ask about any stream or address and it answers in a click, live from the chain. -> Most projects make you dig. We answer. +> The feature I refused to launch without: the exit. +> Cancel a stream and the earned part goes to the person who earned it, while the rest comes home in the same transaction. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Ask a question, get the answer straight from the blockchain. stackstream.xyz +**WhatsApp** +> Pause, resume, top up, or cancel. Your money stays yours. stackstream.xyz · X: @Stackstream0X --- -### Jul 22 (Wed) — Show the receipt +### Day 10, Wed Sep 23: A real transaction + +> `SS_D10_proof-card` (C), precise terms allowed · Outreach: Mithil Thakore · Use a real mainnet stream and label it if it is ours · Explorer link in the first reply **Official X** -> Here is a real stream from this week, and here is its receipt. -> Open the transaction, check the sender, the recipient, the amount, the timing. Nothing to take on faith. -> We like showing our work. Start yours today. +> A real transaction, nothing to take on faith. +> The hash, the block, the amount, confirmed on mainnet. Open it in the explorer and check every field. Receipt in the reply. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -> (include the explorer link to the transaction) **Personal X** -> I would rather show than tell. This week's stream, receipt and all, open for anyone to verify. -> Building in the open is slower and better. -> Check it yourself, then open your own. +> Proof over adjectives. One real stream, receipt in the reply. +> Better still: paste the stream ID into the assistant in our dashboard, and it reads the status and claimable balance straight from the chain. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -> (include the explorer link to the transaction) + +**Stacks Discord** +> Hi all, Jethro from StackStream. Today I am posting a receipt, not a promise. +> This is a real stream on mainnet: https://explorer.hiro.so/txid/0xe8367172fde244bb23b776fe6acda8afcb6cf9559ae67b7a2cd6f8dc5ca89148?chain=mainnet +> Stream 11. 1.2 USDA over 2,160 blocks. Created, then claimed. It runs between two of my own wallets, so I am saying that upfront. +> Open it. Check every field. Then paste the stream ID into the lookup on our dashboard and watch it read the balance straight from the chain. +> The infrastructure is ready. What it needs now is real teams. If your project pays anyone, try one stream. I will set it up with you. +> Weekly numbers on X: @Stackstream0X. **Grantees Telegram** -> Posting this week's stream receipt end to end, in case a real example helps your own build-in-public posts. And the standing offer: a test stream between our projects any time, I will set it up. +> Sharing a stream receipt end to end, in case it helps with your own milestone evidence. Everything checks out in the explorer, which saves a lot of "trust me" in grant reports. Standing offer: a test stream between our projects, and I will set it up. +> Weekly numbers on X: @Stackstream0X. -**WhatsApp (status)** -> Real stream, real receipt, on-chain. Check it yourself. stackstream.xyz +**WhatsApp** +> Real stream, real receipt. Check it yourself. stackstream.xyz · X: @Stackstream0X --- -### Jul 23 (Thu) — Any token you hold +### Day 11, Thu Sep 24: What if nobody claims it? + +> `SS_D11_nobody-claims` (D) · Follow-ups: Tycho, Bitflow, Rena **Official X** -> Some tools stream one token. We stream them all. -> sBTC, STX, USDA, ALEX, whatever your team actually holds. Pick it when you open the stream and get paid in what you actually use. -> One product, every asset on Stacks. +> What if the person you pay never claims? +> Nothing is lost. The balance keeps accruing and waits in the contract. Claim a little every day, or everything on the last day. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> A quiet superpower we do not talk about enough: you are not locked into one token. -> Pay in sBTC, get paid in USDA, run a grant in STX. Whatever you and the other side actually hold. -> Your money, your choice. +> A common question: what happens if nobody claims? +> Nothing dramatic. The earned balance simply waits until they want it. Claiming is a right, not a chore. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Stream any token you hold, not just one. stackstream.xyz +**WhatsApp** +> Forget to claim? Nothing is lost. It waits for you. stackstream.xyz · X: @Stackstream0X --- -### Jul 24 (Fri) — Paid as you work (freelancers) +### Day 12, Fri Sep 25: Grants that release as work ships + +> `SS_D12_grants-in-stages` (E, B) · Follow-ups: DeGrants, Rena · Outreach: PaySats and DeepStack **Official X** -> Freelancers: you finished the work. Why is the money still 30 days away? -> Share your address once. Watch your earnings grow live while you work. Pull them to your wallet whenever you want, in Bitcoin or any token you prefer. -> No invoice, no chasing. +> Funding builders should not mean choosing who carries the risk. +> Stream the grant instead. Funds release as work ships, pause if a milestone slips, and anything unreleased stays in your control. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> I freelanced for years. The work was never the hard part. The waiting was. -> Invoice, silence, follow-up, 30 days. We built the exact opposite: your pay grows in real time and you take it anytime. -> Send your next client this link instead of an invoice. +> Grant programmes already pay in stages. The money just moves by hand. +> A streamed grant does it automatically, and every payment is public, so the payment itself becomes the report. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **LinkedIn** -> If you hire freelancers, here is a retention tool nobody talks about: pay them as they work. -> A streamed engagement means your contractor watches their earnings grow while they build, claims anytime, and never chases an invoice. You stay in control and can pause or stop whenever scope changes. Both sides get certainty. -> The best people choose clients who pay like this. +> For grant, bounty, and ecosystem funding programmes. +> Milestone funding manages risk but creates admin. Someone checks the deliverable, approves the release, sends the transfer, and later writes up where the money went. +> A streamed grant keeps the milestone logic and removes most of the handling. Funds release continuously over the grant period, and the builder draws what has accrued when needed. If work stops, the programme pauses or cancels, and every unreleased dollar returns in the same transaction. Because each payment is on a public ledger, reporting becomes a by-product rather than a task. +> StackStream is live on Stacks mainnet and independently audited. We are looking for one programme to try this on one or two grants, with full control kept throughout. +> Follow @Stackstream0X on X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> For everyone still waiting on an invoice. There is a better way. stackstream.xyz +**Grantees Telegram** +> This one is for us. We are all paid in milestones, and many of us pass funds on to collaborators. If you want to run a sub-grant or bounty as a stream, releasing with the work while the rest stays with you, I will set it up with you. stackstream.xyz +> Weekly numbers on X: @Stackstream0X. + +**WhatsApp** +> Fund builders in stages, as the work happens. stackstream.xyz · X: @Stackstream0X --- -### Jul 25 (Sat) — Three steps, one offer +### Day 13, Sat Sep 26: The number nobody wants to post + +> `SS_D13_founder-note` (F) · Follow-ups: Grant, Mithil **Official X** -> The whole thing in three steps. -> 1. Pick who you are paying and how much. -> 2. Open the stream. -> 3. They claim anytime, you reclaim whatever is left. -> And this month, we will set up your first stream with you, step by step. -> https://t.me/dev_jaytee +> Why we publish small numbers every Monday: +> The one thing about us you can check in ten seconds should be the thing you trust most. +> Live counts, straight from the chain. +> Follow @Stackstream0X for the weekly numbers. +> https://stackstream.xyz **Personal X** -> Saturday offer, no catch: if you have been curious about streaming money, message me and I will personally walk you through your first stream this week. -> Ten minutes, your token, your terms. If it is not for you, you lose nothing. -> My DMs are open. -> https://t.me/dev_jaytee +> Every Monday I post numbers that make StackStream look small: [N] streams, [D] registered organisations. +> I keep posting them because anyone can verify them in seconds. Small and true beats big and dressed up. +> Follow @Stackstream0X for the weekly numbers. +> https://stackstream.xyz -**WhatsApp (status)** -> Free onboarding this month. I will set up your first stream with you. Message me: t.me/dev_jaytee +**WhatsApp** +> Posting our real numbers on purpose. True beats impressive. stackstream.xyz · X: @Stackstream0X --- -### Jul 26 (Sun) — Subscriptions that feel fair +### Day 14, Sun Sep 27: Nobody else can do this bit + +> `SS_D14_comparison` (G) · Match on four rows, differ on one, and never claim a row we do not win **Official X** -> Subscriptions, but fair to both sides. -> The payment streams in as the service is delivered. The customer stops, the payment stops. No chargebacks, no disputes, no awkward refunds. -> Honest by design. +> Real-time streams, any token, non-custodial, cancel anytime: Sablier has it, Streamflow has it, and so do we. +> The difference is the foundation. Theirs are Ethereum and Solana. Ours is secured by Bitcoin. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> Charging a year upfront and hoping the customer stays happy is not a business model, it is a standoff. -> Streaming fixes the incentives. Pay while you use it, stop anytime, both sides relax. -> Quietly, I think this is how subscriptions end up working. +> Streaming money is not our invention. Sablier proved it on Ethereum, with over $2B streamed. +> What did not exist was the same thing secured by Bitcoin. That gap is why I built StackStream. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **LinkedIn** -> A thought for subscription and service businesses. -> The upfront charge creates friction on both sides: customers fear commitment, you carry chargeback risk. A streamed payment flows in as you deliver, and if the customer stops, it stops. It builds more trust than any refund policy, and your suppliers can be paid the very same way. -> Worth a look if you bill recurring. +> Positioning honestly in a category that already exists. +> Payment streaming is proven. Sablier has streamed over $2 billion on Ethereum, and Streamflow serves Solana. Real-time accrual, multi-token support, non-custodial contracts, and cancellation are table stakes, and StackStream matches them. +> The difference is the foundation. StackStream runs on Stacks, where streams update in seconds and settlement inherits Bitcoin finality. For organisations that already hold Bitcoin, or want payroll on the most established settlement layer, that is the property the alternatives cannot offer. +> It is live on mainnet, independently audited, and backed by 125 passing tests. +> Competing on the one row that matters is more credible than claiming every row. +> Follow @Stackstream0X on X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Subscriptions that only charge while you actually use them. Fair both ways. stackstream.xyz +**Stacks Forum**, thread: "StackStream, Sablier, Streamflow: an honest comparison" +> Posting this because people ask, and accuracy matters more than flattery. +> Shared by all three: continuous accrual, token-agnostic streams (SIP-010 for us), non-custodial contracts, and sender cancellation with unearned funds returned. +> Where Sablier and Streamflow lead: scale, integrations, years in production, and features we deliberately deferred, such as cliffs, vesting schedules, and multi-recipient splits. +> Where StackStream differs: Clarity on Stacks, so streams update in seconds and settlement inherits Bitcoin finality, and sBTC means the streamed asset can be actual Bitcoin. Live on mainnet since May, audited through an independent bounty review, with 125 passing tests including property-based fuzzing. +> If anything here is wrong about either project, correct me and I will update the chart. +> Weekly numbers on X: @Stackstream0X. +> https://stackstream.xyz + +**WhatsApp** +> Others stream on Ethereum and Solana. We are secured by Bitcoin. stackstream.xyz · X: @Stackstream0X --- -## Week 3 — Handle doubts, widen the story (Jul 27 to Aug 2) +## Week 3: Who it is for (Sep 28 to Oct 4) -### Jul 27 (Mon) — Metrics, week 3 +### Day 15, Mon Sep 28: The number, week 3 + +> `SS_D15_metric-card` (A) · Outreach: Alex Miller **Official X** -> Monday numbers, week 3. -> [N] streams on mainnet, [+X] this week. Verify it live at stackstream.xyz/api/stats. -> Our public target is 40 by Aug 7. We are [on track / short, and here is what we are doing about it]. -> Help decide how this post reads next week. +> Week 3. [N] streams live on mainnet. [D] organisations registered. +> One product, three ways in: payroll that runs itself, grants that release as work ships, and pay that grows while you work. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> [N] streams, [+X] this week. Three straight weeks of posting the truth. -> The target I set publicly is 40 by Aug 7. [Honest one-liner about the gap or the momentum.] -> Every stream counts, including yours. +> Week 3: [N] streams, [D] organisations registered. +> The kind of team leaning in most so far: [DAOs and teams / grant programmes / builders]. [One true line on why.] +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Week 3: [N] streams. The counter does not lie. stackstream.xyz +**WhatsApp** +> Week 3: [N] streams, [D] teams. Built for Stacks. stackstream.xyz · X: @Stackstream0X --- -### Jul 28 (Tue) — Life changes, streams adjust +### Day 16, Tue Sep 29: Any token you actually hold + +> `SS_D16_any-token` (B) · Outreach: Andre Serrano **Official X** -> Plans change. Budgets change. People change. -> That is why every stream can be paused, topped up, or cancelled in one click, and whatever was not yet earned goes straight back to the sender. -> Commitment without the trap. +> Not an STX-only tool. +> Stream sBTC, STX, USDA, ALEX, or any token on Stacks. Pay in what your treasury holds, and get paid in what you actually want. +> Including real Bitcoin, through sBTC. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> The feature I insisted on from day one: the exit. -> Pause when a project stalls. Top up when it extends. Cancel and the unearned part comes home instantly. -> Nobody should need a lawyer to stop paying for something. +> The most common wrong assumption: "so it only streams STX?" +> No, any token on Stacks. My favourite is sBTC: someone paid in real Bitcoin, continuously, claiming it themselves. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Pause, top up, or stop anytime. Money with an undo button. stackstream.xyz +**WhatsApp** +> Stream any token you hold, even real Bitcoin. stackstream.xyz · X: @Stackstream0X --- -### Jul 29 (Wed) — The assistant, on camera +### Day 17, Wed Sep 30: Two minutes, start to finish + +> `SS_D17_two-minute-flow` (H, C), captioned, under 40 seconds · Outreach: Ken Liao **Official X** -> Watch our assistant answer from the blockchain in real time. -> A stream ID goes in, live on-chain data comes out: status, deposit, claimable right now. -> This is what "do not trust, verify" looks like when it is friendly. +> Wallet to live stream, start to finish, no cuts. +> Connect. Choose who, which token, how much, and how long. Confirm. Watch it start. +> Captioned, so it works on mute. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -> (attach the OpenClaw screen clip) **Personal X** -> Party trick I never get tired of: asking OpenClaw about a stream and watching it read the chain back in a second. -> No explorer tabs, no raw calls, just answers. -> It is sitting in the dashboard waiting for you. +> My bar for the product: if you can send a message, you can open a stream. +> Here is the full flow, recorded once with no edits. Try it yourself, and tell me where it could be smoother. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -> (attach the OpenClaw screen clip) -**WhatsApp (status)** -> Our assistant reads the blockchain so you do not have to. stackstream.xyz +**Stacks Discord** +> For anyone who wanted the real flow rather than a loop: a full recording of opening a stream on mainnet, from wallet to live stream, captioned. [clip] +> If you try it and anything breaks, especially in the wallet step, post it here or DM me. Reports from this room are the fastest way I find and fix issues. +> Weekly numbers on X: @Stackstream0X. + +**WhatsApp** +> Wallet to live stream in under two minutes. stackstream.xyz · X: @Stackstream0X --- -### Jul 30 (Thu) — Fund in stages (grants) +### Day 18, Thu Oct 1: What does it cost? + +> `SS_D18_cost` (D), asset copy "No fee from us" · Follow-ups: Alex, Tycho **Official X** -> If you fund builders, stream the grant instead of wiring a lump. -> Money flows as the work ships. Milestones slip, you pause. Whatever is not yet earned stays yours the entire time. -> We fund our own work exactly this way. +> What does it cost? +> No fee from us. You pay Stacks network gas, a few STX, and that is it. +> Price should never be the reason not to try. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> Grants force a bad choice: pay upfront and carry all the risk, or pay at the end and make the builder carry it. -> Streaming sits in the middle. The grant flows with the work and the unreleased part stays safe. -> We run StackStream's own funding like this, which is the best endorsement I can give. -> https://stackstream.xyz - -**LinkedIn** -> For grant and funding programs: lump sums put all the risk on one side of the table. -> A streamed grant flows in stages as work happens. Anything unreleased stays with the funder, milestones slipping means pausing rather than awkward clawback conversations, and the builder still gets paid continuously while shipping. We use this for our own funding. -> How it works, in sixty seconds. +> Budget quietly kills good tools, so I say it first: StackStream takes no fee. +> A one-person, one-month trial costs a few STX in gas and twenty minutes. I will do the setup. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**Grantees Telegram** -> This one is literally about us. If any project here wants to run a sub-grant or bounty as a stream, money flowing with the work and the rest staying safe, I will help you set it up and we can compare notes after. First one this week gets my full attention. - -**WhatsApp (status)** -> Fund builders in stages, as the work happens. The fair version of a grant. stackstream.xyz +**WhatsApp** +> No fee from us. Just a few STX in network gas. stackstream.xyz · X: @Stackstream0X --- -### Jul 31 (Fri) — Meet a streamer (spotlight) +### Day 19, Fri Oct 2: Paid as you work -> Only with the user's permission, tag them. If nobody is ready, run the story version: "picture a five person team that pays as it builds", and make converting a real spotlight the outreach goal of the week. +> `SS_D19_paid-as-you-work` (E) · Follow-ups: DeGrants, Andre · Outreach: creators, only if Tycho is silent **Official X** -> Meet one of the teams streaming with us. -> No more month-end scramble. Their people watch their pay grow as they build, and the treasury stays in control the whole time. -> This is exactly who we built StackStream for. Be next. +> For the person being paid. +> From the moment a stream opens, your balance grows while you work. Watch it on the Earn page and claim all or part anytime. +> No invoice. No chasing. No 30-day wait. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> Someone chose us for payroll this month. Seeing a team trust your product with something as personal as pay is a quiet, huge feeling. -> Thank you. We will keep earning it. -> If you want to be the next story here, my DMs are open. -> https://t.me/dev_jaytee +> I freelanced for years. The work was never the hard part; the waiting was. +> On StackStream, your pay grows in front of you and you take it when you want. Send this to whoever pays you. +> Follow @Stackstream0X for the weekly numbers. +> https://stackstream.xyz + +**LinkedIn** +> If you hire freelancers, contractors, or creators, here is an underrated retention tool: pay them as they work. +> With a streamed engagement, your contractor watches earnings grow while they deliver and claims anytime, without chasing an invoice. You keep control and can pause or stop if the scope changes. Both sides get certainty. +> StackStream makes this simple on Stacks. It is live on mainnet, independently audited, works with any token on Stacks including sBTC, and takes no fee. Setup takes a few minutes, and the person you pay needs nothing more than a Stacks wallet. +> The best people choose clients who pay like this. +> Follow @Stackstream0X on X for the weekly numbers. +> https://stackstream.xyz -**WhatsApp (status)** -> Real teams are streaming pay with us now. Come see why. stackstream.xyz +**WhatsApp** +> For everyone still waiting on an invoice, there is a better way. stackstream.xyz · X: @Stackstream0X --- -### Aug 1 (Sat) — The real cost of waiting +### Day 20, Sat Oct 3: Building this alone + +> `SS_D20_behind-the-scenes` (F) · Follow-ups: Mithil, Ken **Official X** -> Net 30 is not a payment term. It is a free loan you never agreed to give. -> Thirty days of your money sitting in someone else's account, every single invoice, forever. -> Streaming ends the loan. You earn it, you have it. +> Behind StackStream is one builder, many late nights, and a public counter that never gets dressed up. +> Small team, audited code, and every message answered. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> Did the math once on my freelance years: every net 30 invoice was me lending my client a month of my salary, interest free. -> Nobody calls it that, but that is what it is. -> I built the alternative. +> Building StackStream mostly alone is less romantic than it sounds. +> The upside: when you message about your stream, you reach the person who wrote the code. My DMs are open. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Net 30 is a free loan you never agreed to give. Stop giving it. stackstream.xyz +**WhatsApp** +> Building this mostly alone, and still answering every message. stackstream.xyz · X: @Stackstream0X --- -### Aug 2 (Sun) — Where this goes (cross-chain roadmap) +### Day 21, Sun Oct 4: Bitcoin is the difference + +> `SS_D21_two-clocks` (B), two separate timelines · Read the settlement rule aloud before posting **Official X** -> A glimpse of where this goes. -> One day you stream on Bitcoin, and the person you pay receives it on whatever chain they call home. We are building toward that through sBTC bridges. -> Not live yet, and we will not pretend otherwise. But we are getting ready. +> Two clocks, never mixed up. +> Clock one: your balance updates every few seconds. +> Clock two: settlement inherits Bitcoin finality, on Bitcoin's own schedule. +> Fast where you feel it. Final where it counts. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> Dreaming out loud on a Sunday: stream from Bitcoin, get paid wherever you already live, no friction. -> Not live yet, and I will always tell you the truth about timing. But every design choice we make today keeps that door open. -> Follow the build. +> The easiest mistake when describing StackStream is merging two speeds into one. +> The stream updates in seconds. Separately, settlement inherits Bitcoin finality. Precise beats impressive, especially with money. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**Stacks Forum** — thread: "Designing StackStream to be bridge ready" -> A roadmap note for the builders here. We keep our payment flows composable so that once sBTC cross-chain transfer is generally available, streaming payout to other ecosystems is an extension rather than a rewrite. Token transfer first, not arbitrary messaging, and we are scoping accordingly. Curious how others think about cross-chain payout patterns from Stacks. -> Project: https://stackstream.xyz +**LinkedIn** +> Why we built on Bitcoin, and why we describe it carefully. +> StackStream runs on Stacks. Since the Nakamoto upgrade, blocks arrive roughly every five seconds, so a stream's balance updates in near real time. That is the clock people feel. +> Separately, Stacks state anchors to Bitcoin, and settlement inherits Bitcoin finality on Bitcoin's own schedule. That is the clock that makes a payment final. +> We keep the two apart in everything we publish, because payment infrastructure should be described precisely. Together they give responsiveness where people experience it, and the most established finality where it counts. +> The contracts are live on mainnet and independently audited. +> Follow @Stackstream0X on X for the weekly numbers. +> https://stackstream.xyz -**WhatsApp (status)** -> Stream on Bitcoin, get paid wherever you live. Not yet, but we are building for it. stackstream.xyz +**Stacks Forum**, thread: "Two clocks: accrual cadence and Bitcoin finality in StackStream" +> A short technical note to keep descriptions of StackStream accurate. +> Accrual: the claimable balance is computed from elapsed Stacks blocks. Post-Nakamoto that gives roughly five-second granularity, so the UI and the on-chain claimable amount move in near real time. +> Finality: claims, top-ups, and cancellations are Stacks transactions. They confirm on Stacks quickly and inherit Bitcoin finality once the relevant state is anchored to Bitcoin, on Bitcoin's cadence rather than per Stacks block. +> "Updates in seconds" and "Bitcoin finality" are both true, and they describe different layers. If you ever see us merging them, flag it and we will fix it. +> Weekly numbers on X: @Stackstream0X. +> https://stackstream.xyz + +**WhatsApp** +> Updates in seconds. Secured by Bitcoin. stackstream.xyz · X: @Stackstream0X --- -## Week 4 — Close the month, cement the habit (Aug 3 to Aug 11) +## Week 4: Trust and depth (Oct 5 to Oct 11) -### Aug 3 (Mon) — Metrics, week 4 +### Day 22, Mon Oct 5: The number, week 4 + +> `SS_D22_metric-card` (A) · If a team registers this week, run the break-glass posts **Official X** -> Monday numbers, four weeks running. -> [N] streams on mainnet, [+X] this week, live at stackstream.xyz/api/stats. -> Four Mondays of verifiable truth. That is the whole marketing strategy. +> Week 4. [N] streams on mainnet. [D] organisations registered. +> Every team that streams here strengthens the case for payments on Stacks: real-time, verifiable, built to grow natively, over time and space. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> [N] streams, [+X] new. A month ago posting real numbers weekly felt risky. Now it feels like the only honest way to build. -> Target day is Thursday. [One line on where we stand.] -> There is still time to be in the final count. +> Week 4: [N] streams, [D] organisations registered. +> [One honest line on the gap between conversations and registrations, and what you are changing.] +> Still setting up every team's first stream myself. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Four Mondays of real numbers: [N] streams. Target day is Thursday. stackstream.xyz +**WhatsApp** +> Week 4: [N] streams, [D] teams. Still building, still open. stackstream.xyz · X: @Stackstream0X --- -### Aug 4 (Tue) — Your salary is personal (privacy roadmap) +### Day 23, Tue Oct 6: Cancel it and see + +> `SS_D23_cancel-split` (B), chart green and red **Official X** -> A quiet thought. -> Your salary is personal. Not everyone wants it visible to the whole internet. -> Private streams are on our roadmap, built carefully on Bitcoin. We are taking it slowly because getting privacy wrong helps nobody. -> The rest is live today. +> What happens when a stream is cancelled halfway? +> Earned funds go to the person who earned them. Unearned funds go back to the sender. Same transaction, no dispute. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> Something I think about a lot: open money is powerful, but a salary is a private thing. -> So private streams are on our roadmap. Slow and careful, because privacy done wrong is worse than no privacy. -> It is coming. Meanwhile, everything else works today. +> The moment I trust most in StackStream is cancel. +> Earned goes one way, unearned the other, in one transaction. No clawback emails, and no refund in five to seven business days. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Money can be open and still keep some things private. We are working on that. stackstream.xyz +**WhatsApp** +> Cancel a stream and it splits fairly, instantly. stackstream.xyz · X: @Stackstream0X --- -### Aug 5 (Wed) — Watch a claim, start to finish +### Day 24, Wed Oct 7: Open code, tested + +> `SS_D24_open-code` (C), precise terms allowed · Re-run `npx vitest run` first and update the count if it changed **Official X** -> From "I earned it" to "it is in my wallet" in one clip. -> Watch a recipient claim mid-stream: click, confirm, done. The stream keeps flowing behind them. -> No payday, no permission, no waiting. +> For developers. +> Open-source Clarity contracts, 125 passing tests including property-based fuzzing, and an independent audit before mainnet. Report in the repo. +> Read it, run it, then decide. +> Follow @Stackstream0X for the weekly numbers. +> https://github.com/jayteemoney/stackstream + +**Personal X** +> I would not move my salary through a contract I could not read, so you can read ours. +> 125 passing tests, including fuzz tests on the property that matters most: funds are always conserved. +> Follow @Stackstream0X for the weekly numbers. +> https://github.com/jayteemoney/stackstream + +**Stacks Discord** +> A developer-focused one. StackStream's contracts are open source: stream-manager and stream-factory in Clarity, with 125 passing tests on Clarinet, including property-based fuzz tests. The independent audit report and findings triage are in /audits, and every real bug found was fixed before mainnet. +> If you want to build on streams, or you spot something, open an issue or DM me. +> Weekly numbers on X: @Stackstream0X. +> https://github.com/jayteemoney/stackstream + +**Grantees Telegram** +> For anyone preparing security evidence for a milestone: our audit report and findings triage are public in the repo. Feel free to copy the format, as it made our own reporting far easier. +> Weekly numbers on X: @Stackstream0X. + +**WhatsApp** +> Open code, independent audit, 125 passing tests. stackstream.xyz · X: @Stackstream0X + +--- + +### Day 25, Thu Oct 8: Is it safe? + +> `SS_D25_is-it-safe` (D) · Follow-up: Alex + +**Official X** +> Is it safe? +> Funds sit in the contract, never with us. The contracts were independently audited before mainnet, and every real bug found was fixed. +> Code, tests, and report are public. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -> (attach the claim clip) **Personal X** -> The moment that converts people is never the pitch. It is watching someone claim their pay mid-week just because they felt like it. -> Click, confirm, money in wallet, stream still running. -> That freedom is the product. +> The question behind every question: can I trust it? +> My answer: do not trust it, check it. Audited contracts, 125 passing tests, and everything public in the repo. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -> (attach the claim clip) -**WhatsApp (status)** -> Claim your pay any moment you like. Watch how fast: stackstream.xyz +**WhatsApp** +> Your money sits in an audited contract, never with us. stackstream.xyz · X: @Stackstream0X --- -### Aug 6 (Thu) — Open code, tested funds +### Day 26, Fri Oct 9: How teams pay people today + +> `SS_D26_how-teams-pay` (E, B), the highest-converting asset · Follow-up: Andre · Pin on @dev_jayteee if a Door 1 conversation is open **Official X** -> Where your money flows should never be a mystery. -> Our contracts are open source, covered by a test suite that checks funds are always conserved, and hardened by independent security review. -> Read the code, run the tests, then stream with confidence. +> How a small team pays people today: a spreadsheet, a second check, signer chasing, a late payment, and someone missed. +> The same month with streams: set once, paid continuously, full control. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> We put our contracts through independent security review and a test suite that verifies every satoshi is conserved. Then we left it all public. -> Not because it is required. Because pay is too important for "trust me". -> The code is open. -> https://github.com/jayteemoney/stackstream +> The image maps every step of month-end payroll and every place it breaks. +> None of it is hard. It is just repeated forever. One stream, one person, one month is the easiest way to see the difference. +> Follow @Stackstream0X for the weekly numbers. +> https://stackstream.xyz **LinkedIn** -> A note on how we treat trust. -> StackStream's smart contracts are open source, independently reviewed, and covered by tests that verify funds are conserved in every scenario, pause, cancel, top up, claim. Anyone can read the code and re-run the checks. -> When software moves salaries, this should be table stakes. +> Mapping manual payroll honestly for a small distributed team. +> A spreadsheet at month end. A second check by whoever has time. A multi-signature proposal and a round of chasing signers across time zones. Payment somewhere in the first week of the next month, and almost always one person missed. +> None of it is difficult. It is hours of repeated work every month, and it leaves contributors unsure when they will be paid. +> StackStream turns it into a one-time setup. Each contributor gets a stream, pay accrues continuously, and they claim when they choose. The team keeps full control throughout. It is live on Stacks mainnet and independently audited. +> If this is your month end, try one stream with one person for one month. I will set it up with you. +> Follow @Stackstream0X on X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Open code, independent review, tested funds. Pay deserves nothing less. stackstream.xyz +**WhatsApp** +> Month-end payroll takes hours. It should take zero. stackstream.xyz · X: @Stackstream0X --- -### Aug 7 (Fri) — Target day: the honest result +### Day 27, Sat Oct 10: What I got wrong -> Whatever the number says, post it. Hitting builds momentum, missing builds trust. Both are worth having. +> `SS_D27_what-i-got-wrong` (F) · Follow-up: Ken · No target figures, no dates, no excuses **Official X** -> Thirty days ago we set a public target: 40 streams by today. -> The result: [N]. [If hit: "Target met, and every single one is verifiable on-chain." If missed: "Short of the target, and we said we would report honestly, so here it is. What we learned: ..."] -> The counter never stops, and the next target drops Monday. +> Our founder on the last three months, including what did not work. +> Short version: good contracts do not onboard teams. Conversations do. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> Result day. We aimed for 40 streams in 30 days and landed at [N]. -> [Two honest sentences: what worked, what did not, what changes.] -> Building in public means posting this either way. Thank you to everyone in the count. +> What I got wrong this year: I polished too long, pitched before I listened, and assumed a working product would sell itself. +> Now every conversation starts with a question. [One true line on the result.] +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Thirty days ago we set a public target. Today: the honest result. [N] streams. stackstream.xyz +**LinkedIn** +> Three lessons from trying to get organisations to adopt payment infrastructure. +> StackStream is live on mainnet, audited, and works well. Getting teams to register has been slower than I expected, and the product was not the reason. My approach was. +> First, I pitched before I listened. My early messages assumed how teams paid people, and a wrong premise makes any message read like a template. +> Second, being first is the real objection, not the technology. Nobody wants to be the first team to trust something new with pay. +> Third, publishing honest numbers built more credibility than anything I wrote about the product. +> Every conversation now starts with a question. [One true line on what that has changed.] +> Follow @Stackstream0X on X for the weekly numbers. +> https://stackstream.xyz + +**WhatsApp** +> Wrote about what I got wrong this year. The honest version. stackstream.xyz · X: @Stackstream0X --- -### Aug 8 (Sat) — You asked, we answer +### Day 28, Sun Oct 11: Where this goes + +> `SS_D28_roadmap` (B), every element marked "roadmap, not shipped" · Tonight: final scoreboard review, draft Day 30 **Official X** -> Real questions from this month, answered. -> Is my money safe mid-stream? It sits on-chain where neither side can take what is not theirs. -> Which tokens? Any token on Stacks. -> Can I stop? Anytime, and the unearned part returns instantly. -> More answers on the site. +> Where this goes. Roadmap, not shipped: +> Cross-chain payout, so recipients receive on the chain they use. +> Private streams, because a salary is personal. +> No dates. Everything else is live today. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> Spent the month collecting every question people asked me about StackStream. Put the honest answers in one place, the FAQ on our site. -> The question behind every question was the same: "can I trust it?" The answer we give is: do not trust it, verify it. -> Ask me anything, anytime. -> https://t.me/dev_jaytee +> Two things I am building toward, neither live yet: paying someone who receives on another chain, and streams where the amount stays private. +> No dates I cannot keep. Nothing shipped today closes either door. +> Follow @Stackstream0X for the weekly numbers. +> https://stackstream.xyz -**WhatsApp (status)** -> Every question you have about streaming money, answered honestly: stackstream.xyz +**Stacks Forum**, thread: "Roadmap note: cross-chain payout and private streams" +> Neither is shipped and neither has a date. Here are the constraints, so the discussion stays grounded. +> Cross-chain payout depends on sBTC cross-chain transfer being generally available. That bridge moves tokens, not arbitrary messages, so we are scoping payout as a token transfer at claim time rather than mirroring stream state across chains. +> Private streams depend on zero-knowledge verification inside Clarity. Recent ecosystem work suggests it is possible without network changes, but it needs serious cryptographic review before anyone's pay relies on it. +> Before either, the priority is teams using what is live. If you have views on either design, especially payout at claim versus at creation, I would like to hear them. +> Weekly numbers on X: @Stackstream0X. +> https://stackstream.xyz + +**WhatsApp** +> Where we are heading next. Roadmap, not promises. stackstream.xyz · X: @Stackstream0X --- -### Aug 9 (Sun) — The money people trust most +## Week 5: Closing (Oct 12 to Oct 13) + +### Day 29, Mon Oct 12: The number, week 5 + +> `SS_D29_metric-card` (A), with the five-Monday sparkline **Official X** -> Fifteen years, no bailouts, no rollbacks, no downtime that mattered. -> That is the settlement layer under every StackStream payment. -> When pay is on the line, build on the money people trust most. +> Week 5, the last card of this run. [N] streams live on mainnet. [D] organisations registered. +> All five Mondays in one line, every figure checkable on-chain. The door stays open. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> Sunday conviction post: fads rotate, Bitcoin settles. -> We anchored a payments product to it on purpose, because salaries deserve the most boring, most trusted foundation that exists. -> Boring foundations, exciting product. +> Five Mondays, five cards: [N] streams, [D] organisations registered. +> [One honest line on the shape of the sparkline.] +> Tomorrow: what this month taught us about who needs StackStream most. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz -**WhatsApp (status)** -> Built on the most trusted money there is. On purpose. stackstream.xyz +**WhatsApp** +> Five honest Mondays. [N] streams, [D] teams. stackstream.xyz · X: @Stackstream0X --- -### Aug 10 (Mon) — Metrics + the month in review +### Day 30, Tue Oct 13: Thirty days in the open + +> `SS_D30_thirty-days` (A, G), built to work whether numbers rose or barely moved · Name the door with the most pull from the scoreboard, or say plainly that none led **Official X** -> Five Mondays of real numbers. Here is the month: -> [N] total streams, up from 9. [Y] claimed without a single dispute. The demo passed [V] views. -> Every number verifiable, every week, at stackstream.xyz/api/stats. -> August target: [new target]. Hold us to it. +> Thirty days in the open. +> Sep 14: 11 streams, 0 organisations. Today: [N] streams, [D] organisations. +> The teams leaning in hardest: [door]. That is where the next month goes. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> One month of radical honesty, in numbers: 9 streams to [N]. A demo video, a public target, and a result posted either way. -> The biggest lesson: people join what they can verify. -> New month, new target, same honesty. +> 30 days of posting real numbers: 11 to [N] streams, 0 to [D] organisations. +> The biggest lesson: [door] needs this most. That is where I am heading next, and my DMs are open. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **LinkedIn** -> A month ago we committed to one metric and weekly public reporting. The result: [N] streams on mainnet, up from 9, every one verifiable against the contract itself. -> The lesson for anyone building in fintech: the most persuasive marketing asset we own is a number we cannot fake. -> The counter is public. +> Thirty days ago we started testing one question in public: which part of the Stacks ecosystem needs payment streaming most? +> StackStream serves teams paying contributors, grant programmes releasing funds, and individuals paid as they work. All three were live throughout, on mainnet, with audited contracts. We published usage every Monday, straight from the chain, and tracked every conversation by where it came from. +> Result: [N] streams and [D] organisations registered, from 11 and 0. The strongest pull came from [door], measured by [registrations, calls, inbound]. The weakest was [door]. +> Next: [one sentence]. +> The lesson for anyone seeking product-market fit: measure behaviour by segment, not interest overall. The total hides the segment already leaning in. +> Follow @Stackstream0X on X for the weekly numbers. +> https://stackstream.xyz + +**Stacks Forum**, thread: "StackStream, 30 days in the open" +> A retrospective for the ecosystem, posted the same day as the public numbers. +> Numbers: 11 to [N] streams and 0 to [D] organisations, all verifiable at stackstream.xyz/api/stats. Any streams we opened ourselves are labelled: [list or "none"]. +> Conversations: [count] opened across teams, grant programmes, contributors, and ecosystem partners. The strongest response came from [door], the weakest from [door]. +> Shipped this month: [list]. Changing next: [one or two lines]. +> The contracts remain open source, independently audited, live on mainnet, and backed by 125 passing tests. If your Stacks project pays people by hand, I will still set it up with you personally. +> Weekly numbers on X: @Stackstream0X. +> https://stackstream.xyz + +**Grantees Telegram** +> 30-day run done: [N] streams, [D] organisations, and the clearest signal is that [door] wants this most. Thank you to everyone here who answered my question about how you pay people; it shaped the whole month. Happy to share the scoreboard format, and the test-stream offer never expires. stackstream.xyz +> Weekly numbers on X: @Stackstream0X. + +**WhatsApp** +> Thirty days of showing our work. Thank you for watching. stackstream.xyz · X: @Stackstream0X + +--- + +## Extra post: an onboarding call with a fellow grantee + +> Post only with the team's written OK, the afternoon after the call, as an extra. That day's scheduled post still runs in the morning. Asset: none, or a plain card with both logos if they agree. Says "onboarding call", never "registered", until the transaction confirms. Once it does, the break-glass post below takes over. + +**Official X** +> First onboarding call done, with a fellow Stacks Endowment grantee. +> [Team name] builds [one line, in their words]. We walked through how a stream works from their own wallet. +> No claims yet. Just two builders getting a real team ready to use it. +> Follow @Stackstream0X for the weekly numbers. +> https://stackstream.xyz + +**Personal X** +> Had my first onboarding call this week, with [team name], another Endowment grantee. +> Builder to builder, wallet open, real questions. This is what "ready for use" looks like from the inside. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Grantees Telegram** -> Month one of public metrics done: 9 to [N] streams, target [hit/missed] and reported honestly either way. Happy to share what worked with anyone here thinking of doing the same. And the test-stream offer never expires. +> Did an onboarding call with [team name] this week. Took about twenty minutes, from their own wallet. Same offer stands for anyone here: I will set up your first stream with you. stackstream.xyz -**WhatsApp (status)** -> One month, five honest Mondays, [N] streams. Thank you for watching us build. stackstream.xyz +**WhatsApp** +> First onboarding call done. Real team, real wallet. stackstream.xyz · X: @Stackstream0X --- -### Aug 11 (Tue) — The open invitation +## Break-glass: the day a team registers + +> Post only after the registration confirms, and name the team only with written permission; otherwise use the bracketed unnamed version. Post the next afternoon as an extra. That day's schedule still runs. +> Asset: proof card (C) of the registration. Same day: send the held Muneeb Ali message and submit the event to Stacks Snacks. Record the door on the scoreboard. **Official X** -> If you made it through a month of our posts, you have seen it all: live demos, on-chain receipts, honest numbers, real teams. -> The only thing missing is your stream. -> Open it in five minutes, or let us set it up with you personally. +> [Team name / A Stacks team] just registered on StackStream and opened its first streams on mainnet. +> Its people are now paid continuously, with the team in full control. Receipt in the reply. +> Follow @Stackstream0X for the weekly numbers. > https://stackstream.xyz **Personal X** -> Closing the month the way I started it: with an open door. -> If anything this month made you curious, message me. I will set up your first stream with you, walk you through every step, and you keep full control the entire time. -> That is the offer, no catch. -> https://t.me/dev_jaytee +> A team just trusted something I built with how it pays its people. +> Thank you to [team name / them] for going first. It makes it easier for every team that follows. +> Follow @Stackstream0X for the weekly numbers. +> https://stackstream.xyz + +**LinkedIn** +> Milestone: the first organisation has registered on StackStream and is streaming payments on Stacks mainnet. +> [Team name / The team] now pays [contributors / grantees / collaborators] continuously. Recipients claim whenever they choose, and the organisation can pause, top up, or cancel at any point, with unearned funds returned instantly. +> This is the proof we set out to build: a real team using audited infrastructure to pay real people more efficiently. [D] organisations are now registered, and every payment is verifiable on-chain. +> If your organisation pays people by hand, you could be next, and I will set it up with you. +> Follow @Stackstream0X on X for the weekly numbers. +> https://stackstream.xyz + +**Stacks Discord** +> Follow-through rather than an announcement: the first team is registered and streaming on mainnet, [receipt link]. Thank you to this room for the sceptical questions that shaped the onboarding. Same offer for the next team: I will do the setup with you. +> Weekly numbers on X: @Stackstream0X. + +**Grantees Telegram** +> First team registered on StackStream this week. Onboarding took one registration transaction and about twenty minutes on a call. If anyone here wants the same, I will set it up with you. stackstream.xyz +> Weekly numbers on X: @Stackstream0X. -**WhatsApp (status)** -> A month of showing our work. Now it is your turn. Open your first stream: stackstream.xyz +**WhatsApp** +> The first team is streaming pay with us. stackstream.xyz · X: @Stackstream0X --- -## Notes before posting +## Before every post -- Brackets [N], [+X], [Y], [V] get real values on the morning of posting, from stackstream.xyz/api/stats and the platforms' own analytics. Never estimate, never round up. If a number is embarrassing, post it anyway, that is the strategy. -- Every public post ends with its CTA link on the final line. On X the bare link auto-embeds; if the preview card crowds a video post, keep the link and drop the media annotation, never the other way around. -- Personal X and Official X fire the same day but never with identical words. Personal is "I", Official is "we". -- Forum and Grantees TG are for substance and feedback, not announcements. Keep them rare and genuine. -- WhatsApp is one warm status line, not a broadcast blast. -- If the June engagement review or the team's DAO-focus decision contradicts anything here, the rhythm stays, the content flexes. Fridays re-weight toward DAOs the moment the team approves. -- The demo assets (60s cut, 10s loop, claim shot, receipt shot) come from one recording. Shoot it before Jul 13, script in the local ops docs. +- Numbers pulled that morning, and no `[N]` or `[D]` left in the copy or on the card. +- Asset filename matches the day number. +- X posts fit in one post of 280 characters or fewer. +- Settlement sentence read aloud. +- One link, on the last line, to https://stackstream.xyz. +- Follow line for @Stackstream0X present, just above the link. +- Reply to every reply within the hour. diff --git a/grant-application/DESIGNER_BRIEF_SEP2026.md b/grant-application/DESIGNER_BRIEF_SEP2026.md new file mode 100644 index 0000000..f8e5444 --- /dev/null +++ b/grant-application/DESIGNER_BRIEF_SEP2026.md @@ -0,0 +1,296 @@ +# StackStream, Brand Designer Brief +## 30 days of visual content: Monday Sep 14 to Tuesday Oct 13, 2026 + +**From:** Jethro Irmiya, founder +**To:** Brand designer +**Written:** Sep 9, 2026 +**First assets live:** Monday Sep 14 + +--- + +## 1. Read this first + +Everything we have published so far has been words. It has been honest and it has been consistent, and it has not been enough. People scroll past text. What we are missing is the thing that makes someone stop, understand in two seconds, and believe it. + +That is what you are being brought in to build, and this document is meant to give you everything you need so that you never have to guess or wait on me. + +**What StackStream is, in one sentence.** It is payment streaming on the Stacks blockchain: instead of paying someone once a month, an organisation opens a stream and the recipient's balance grows continuously, every few seconds, and they take what they have earned whenever they want. + +**Why anyone cares.** Everyone has been paid late, or waited a month for money they earned in week one. Streaming closes that gap. And this is the first time it has been built where the money settles on Bitcoin, which is the part nobody else can copy. + +**The single most important visual idea in this whole document.** A number going up, continuously, in real time. That is the product. If a person watches a balance tick upward for three seconds, they understand StackStream completely and no copy is needed. Every asset you make either shows that or supports it. + +**Where we honestly are.** Eleven streams created on mainnet, zero organisations registered, as of Sep 8. Small numbers. We publish them anyway, every week, because they come straight from the blockchain and anyone can check them. Do not treat this as a problem to design around. It is the most trustworthy thing about us and the metric card is a hero asset, not an embarrassment. + +--- + +## 2. What I owe you, by end of day today + +Nothing in this brief can start until you have these. If any are missing, message me and I will send them within the hour. + +| Item | Where | +|---|---| +| Logo, SVG and PNG | `logo.svg`, `logo-oval.png` | +| Bitcoin mark | `bitcoin.svg` | +| Live product to screenshot | https://stackstream.xyz | +| Live public numbers, refreshed on demand | https://stackstream.xyz/api/stats | +| The 60-second demo recording, for pulling frames | I will send the file | +| Existing content plans, for tone reference | `CONTENT_SCHEDULE.md`, `MARKETING_PLAN_V2.md` | +| Founder photos for the human-note posts | I will send a folder | + +--- + +## 3. Brand system, use these exact values + +The product is dark-first with Bitcoin orange as the accent. These are pulled directly from the live site's design tokens, so anything you make will sit correctly next to the actual product. + +**Brand orange** + +| Token | Hex | +|---|---| +| brand-50 | `#fff7ed` | +| brand-100 | `#ffedd5` | +| brand-200 | `#fed7aa` | +| brand-300 | `#fdba74` | +| brand-400 | `#fb923c` | +| brand-500 | `#f97316` | +| brand-600 | `#ea580c` | +| brand-700 | `#c2410c` | + +`brand-500` is the primary accent. `brand-400` for anything that needs to glow on dark. + +**Dark surfaces** + +| Token | Hex | Use | +|---|---|---| +| surface-0 | `#09090b` | Page background, the default canvas for every asset | +| surface-1 | `#0f0f13` | Cards sitting on the background | +| surface-2 | `#18181b` | Raised cards | +| surface-3 | `#1e1e23` | Higher still | +| surface-4 | `#27272a` | Highest, and the default border colour | + +**Text and lines** + +| Token | Hex | Use | +|---|---|---| +| foreground | `#fafafa` | Primary text | +| muted | `#a1a1aa` | Secondary text | +| muted-foreground | `#71717a` | Labels, captions, axis text | +| border | `#27272a` | Card borders, dividers | +| border-subtle | `#1e1e23` | Quiet dividers | + +**Type.** The product uses Geist Sans and Geist Mono. Use them. **Every number is set in Geist Mono, without exception**, because monospaced digits do not jitter when a value changes, and half of what we publish is numbers that change. + +**Colour discipline, and this matters more than it sounds.** Orange is the only accent. It marks exactly one thing per asset: the number, or the moment, that the asset exists to communicate. The moment a second accent colour appears, everything stops being emphatic and the whole system flattens. + +**Two exceptions, and only two.** Charts may use a green and a red for genuinely opposed quantities, such as earned versus unearned in a cancelled stream. Pick one green and one red, write the hex values into the style sheet in section 4, and never introduce a third. + +--- + +## 4. First deliverable: the style sheet + +**Due end of day Thursday Sep 10. This comes before any individual post asset.** + +One page, exported as PNG and as an editable source file, showing: + +1. The eight-step orange ramp and the five dark surfaces, labelled with hex values +2. Type scale: headline, subhead, body, caption, and the numeral treatment in Geist Mono, with the exact sizes you will use at 1080px wide +3. The chart green and chart red you have chosen, with hex values +4. Logo lockup: minimum size, clear space, and how it sits on `#09090b` +5. The eight asset templates from section 6, each shown once at 1:1 + +Once I approve this page, you never have to ask me a colour or type question again for the rest of the 30 days. That is the point of doing it first. + +--- + +## 5. Rules that cannot be broken + +Some of these will look pedantic. Each one exists because breaking it has cost us something real. + +**5.1 Never write "settles on Bitcoin every few seconds."** This is the most important line in this document. It is factually wrong and this audience will catch it and say so publicly. The balance *updates* every few seconds. Bitcoin *finality* is inherited when the state settles to Bitcoin, on Bitcoin's own schedule. These are two different things and they may never appear in the same clause. + +- Approved for social: **"Your balance updates every few seconds, secured by Bitcoin."** +- Approved for technical: **"Streams update in seconds. Settlement inherits Bitcoin finality."** +- Never: "settles on Bitcoin every few seconds", "final the instant it lands", or anything that fuses the two. + +**5.2 Never invent a number.** Not in a chart, not in a mockup, not as placeholder text that might survive to export. Every figure in every asset comes from `https://stackstream.xyz/api/stats` or from me directly. If you need a number and do not have it, leave the field as `[N]` in the layout and I will fill it before posting. A fabricated chart in this ecosystem is unrecoverable. + +**5.3 Every public asset has exactly one call to action, on its own final line, as a full link.** Default `stackstream.xyz`. Use `t.me/dev_jaytee` when the post's ask is "talk to us". Never two. + +**5.4 Our handles, exactly as written, never improvised.** + +| | | +|---|---| +| Website | `stackstream.xyz` | +| Official X | `@Stackstream0X` | +| Personal X | `@dev_jayteee` (three e's, this is the one people get wrong) | +| Telegram | `t.me/dev_jaytee` (two e's, and yes it differs from the X handle by one letter) | + +**5.5 No em dashes anywhere in copy on an asset.** Commas or full stops. + +**5.6 Text must survive a phone.** Assume the asset is viewed at 30% of the size you are designing it at. Smallest type on any 1080px asset is 28px. If a chart needs more than five labels to make sense, it is the wrong chart. + +**5.7 Everything is captioned and everything is readable muted.** Most people watch video with the sound off. Every motion asset carries burned-in captions. + +**5.8 No jargon on any asset.** Banned: escrow, protocol, primitive, SIP-010, vault, on-chain settlement layer. Say "the money sits in a contract", "a stream", "any token on Stacks". The only exception is the two technical explainers on Day 10 and Day 24, which are aimed at developers and may use precise terms. + +--- + +## 6. The eight templates + +Thirty days is only workable if it is eight reusable templates rather than thirty original designs. Build these once, in the style sheet, and then each day is a content swap rather than a new design. + +**Template A, the Metric Card.** Runs every Monday, five times. One enormous number in Geist Mono, orange, filling most of the frame. Small label under it. Two secondary figures below in muted grey. Bottom left, a timestamp and the words "read live from the contract". This is our most distinctive recurring asset because nobody else in the ecosystem publishes verifiable numbers weekly. Make it look like a readout, not a marketing graphic. + +**Template B, the Explainer Diagram.** Sender, contract, recipient, and the flow between them. Built once as a master diagram, then reused with different parts highlighted in orange depending on which idea that day's post is teaching. This is the workhorse. + +**Template C, the Proof Card.** A real transaction on the blockchain, framed and made legible. Cropped explorer screenshot, the hash, the block, the amount, a green confirmed marker. Deliberately plain. It should look like evidence rather than design, because the moment it looks designed it stops working as proof. + +**Template D, the Objection Card.** Two stacked panels. Top, the doubt, in muted grey on `surface-1`. Bottom, the answer, in white with the key phrase in orange, on `surface-2`. Used for every "yes but what if" post. + +**Template E, the Segment Scene.** A specific person or team pictured in their situation. Illustration or a strongly treated photograph, your call, but pick one approach in the style sheet and hold it for all 30 days. Never generic stock imagery. + +**Template F, the Human Note.** Founder photo, quiet treatment, a short handwritten-feeling line. Warmer and less produced than everything else. Slightly off-system on purpose. These are the posts that build trust, and over-designing them kills them. + +**Template G, the Comparison Chart.** Us against Sablier and Streamflow. Rows are properties, columns are the three products. One orange column, two muted. No animation, no gradient, no decoration. Let the single differentiating row do the work. + +**Template H, the Ticking Balance Loop.** The hero asset of the entire month, and the one to build first. A short seamless loop of a balance counting upward in Geist Mono, orange, on `#09090b`. Six to eight seconds, loops invisibly, works with no sound and no context. Deliver in 1:1, 9:16 and 16:9. **This one asset will be reused more than any other thing you make this month**, so it is worth spending disproportionate time on. If you deliver nothing else by Monday, deliver this. + +--- + +## 7. Formats, naming and delivery + +**Sizes. Every asset ships in all four unless the day's spec says otherwise.** + +| Ratio | Pixels | Used for | +|---|---|---| +| 1:1 | 1080 x 1080 | X, LinkedIn | +| 4:5 | 1080 x 1350 | LinkedIn, best feed real estate | +| 9:16 | 1080 x 1920 | WhatsApp status, stories | +| 16:9 | 1600 x 900 | Stacks Forum, blog headers, link previews | + +**Safe zone:** keep all text and key elements inside a 10% margin on every edge. The 9:16 crop loses the top and bottom in most viewers. + +**File naming, exactly this pattern, because I will be pulling files under time pressure:** + +`SS_D07_ticking-balance_1x1.png` + +Day number always two digits. Ratio as `1x1`, `4x5`, `9x16`, `16x9`. + +**Formats:** static as PNG, plus the editable source. Motion as MP4 (H.264) and a WebP or GIF fallback under 5MB. Anything with type also as SVG where possible. + +**Delivery:** one shared folder, one subfolder per week, `Week1` through `Week5`. Sources in a `_source` subfolder at the top level, not scattered. + +--- + +## 8. Production schedule + +We ship Monday Sep 14, which is five days from today. That is genuinely tight, so week one is deliberately the lightest week and leans hardest on templates. + +| Batch | Contains | Due | Notes | +|---|---|---|---| +| **Batch 0** | Style sheet (section 4) plus Template H, the ticking balance loop | **Thu Sep 10, end of day** | Approval on the style sheet unblocks everything else | +| **Batch 1** | Days 1 to 7 | **Sat Sep 12, end of day** | Two clear days of buffer before we post | +| **Batch 2** | Days 8 to 14 | Fri Sep 18 | | +| **Batch 3** | Days 15 to 21 | Fri Sep 25 | | +| **Batch 4** | Days 22 to 28 | Fri Oct 2 | | +| **Batch 5** | Days 29 to 30, plus any reshoots | Fri Oct 9 | | + +**If Batch 0 and Batch 1 cannot both land, prioritise in this order:** Template H, then the Day 1 metric card, then the Day 3 explainer diagram. Those three cover the first week on their own and the rest can follow midweek. + +**Review loop.** I review within four hours of delivery and give you one consolidated set of notes, not a trickle. Two revision rounds per asset are budgeted. If an asset needs a third round, the design is not the problem and we should talk instead of iterating. + +--- + +## 9. The 30 days + +The weekly rhythm is fixed and repeats, so you always know roughly what is coming: **Monday** is the real number, **Tuesday** teaches an idea, **Wednesday** shows proof, **Thursday** kills an objection, **Friday** pictures a specific kind of team, **Saturday** is a human note, **Sunday** is a bigger idea. + +Bracketed values like `[N]` are numbers I fill in on the morning of posting. Leave them as visible placeholder fields in the layout. + +### Week 1: Sep 14 to Sep 20, what streaming actually is + +| Day | Date | Post | Asset | Template | +|---|---|---|---|---| +| 1 | Mon Sep 14 | The number, week 1 | Metric card: `[N]` streams created, `[D]` organisations registered, timestamp, "read live from the contract" | A | +| 2 | Tue Sep 15 | The tap, not the bucket | Split infographic. Left, a bucket filled once a month, cold grey. Right, a tap running continuously, orange. The single clearest picture of what we do | B | +| 3 | Wed Sep 16 | Watch it move | **The ticking balance loop.** Six to eight seconds, seamless, no logo until the last frame. Cold open on the number | H | +| 4 | Thu Sep 17 | Where the money actually sits | Diagram answering "who is holding my funds". Sender, contract, recipient, with the contract highlighted and a lock. Copy: "It never touches us" | B, D | +| 5 | Fri Sep 18 | Payday that runs itself | Segment scene: a small team of five. Left panel, month-end chaos, spreadsheet, chasing signatures, someone missed. Right panel, five quiet streams already running | E | +| 6 | Sat Sep 19 | Why I built this | Founder photo, quiet. One line: "I have been paid late. So has everyone I know" | F | +| 7 | Sun Sep 20 | Money that moves like water | Wide conceptual piece. Streaming as continuous flow versus discrete lumps. The most artistic asset of the month, use the range | E | + +### Week 2: Sep 21 to Sep 27, proof and control + +| Day | Date | Post | Asset | Template | +|---|---|---|---|---| +| 8 | Mon Sep 21 | The number, week 2 | Metric card, same layout as Day 1. **Identical composition every Monday**, only the numbers change. The repetition is the point | A | +| 9 | Tue Sep 22 | You are never locked in | Four-icon strip: pause, resume, top up, cancel. Under cancel: "everything unearned comes straight back" | B | +| 10 | Wed Sep 23 | A real transaction | Proof card from an actual mainnet transaction. Hash, block, amount, confirmed. Plain and unglamorous on purpose | C | +| 11 | Thu Sep 24 | What if nobody claims it? | Objection card. Doubt on top. Answer below: "It keeps accruing. Nothing is lost. Claim all of it on the last day if you like" | D | +| 12 | Fri Sep 25 | Grants that release as work ships | Segment scene: a grant programme. A funding bar releasing in stages as milestones complete, unreleased portion clearly still inside the funder's control | E, B | +| 13 | Sat Sep 26 | The number nobody wants to post | Founder note about publishing eleven streams instead of hiding it. Quiet, honest, no chart | F | +| 14 | Sun Sep 27 | Nobody else can do this bit | Comparison chart. StackStream, Sablier, Streamflow. Rows: real-time, any token, non-custodial, cancellable, **settlement**. One orange cell carries the whole asset | G | + +### Week 3: Sep 28 to Oct 4, who it is for + +| Day | Date | Post | Asset | Template | +|---|---|---|---|---| +| 15 | Mon Sep 28 | The number, week 3 | Metric card | A | +| 16 | Tue Sep 29 | Any token you actually hold | Token strip: sBTC, STX, USDA, ALEX, all flowing through one stream. Kill the assumption that this is STX-only | B | +| 17 | Wed Sep 30 | Two minutes, start to finish | Screen-recorded flow: connect, create stream, watch it start. Captioned, muted-readable, under 40 seconds | H, C | +| 18 | Thu Oct 1 | What does it cost? | Objection card. Answer: "No protocol fee. Stacks gas only, a few STX." Make the number visually tiny, that is the message | D | +| 19 | Fri Oct 2 | Paid as you work | Segment scene: a contributor watching their balance grow while working. The recipient-side view, which we have under-served | E | +| 20 | Sat Oct 3 | Building this alone | Founder note, behind the scenes, warm and unpolished | F | +| 21 | Sun Oct 4 | Bitcoin is the difference | The settlement explainer, and **the single most language-sensitive asset of the month**. Two clearly separate timelines: stream updates in seconds, settlement inherits Bitcoin finality. Two tracks, visually distinct, never merged into one arrow. Re-read rule 5.1 before starting this one | B | + +### Week 4: Oct 5 to Oct 11, trust and depth + +| Day | Date | Post | Asset | Template | +|---|---|---|---|---| +| 22 | Mon Oct 5 | The number, week 4 | Metric card | A | +| 23 | Tue Oct 6 | Cancel it and see | Diagram of a cancelled stream splitting into two: earned to the recipient, unearned back to the sender, in the same transaction. Use the chart green and red here | B | +| 24 | Wed Oct 7 | Open code, tested | Developer-facing card. Contract line count, 125 passing tests including fuzz tests, independently audited, report in the repo. Terminal aesthetic, Geist Mono. Jargon is allowed on this one | C | +| 25 | Thu Oct 8 | Is it safe? | Objection card on custody and audit. Answer: "The funds sit in the contract. Never with us. Not at any point" | D | +| 26 | Fri Oct 9 | How teams pay people today | Segment scene: the manual month-end process drawn honestly, every step, every place it breaks. Then the same thing as one stream. This is the highest-converting asset in the set, give it the most time | E, B | +| 27 | Sat Oct 10 | What I got wrong | Founder note on lessons from the last three months. Vulnerable and specific | F | +| 28 | Sun Oct 11 | Where this goes | Roadmap piece: cross-chain payout and private streams. **Every element on this asset carries a visible "roadmap, not shipped" marker.** We do not promise dates and we do not let a viewer mistake a plan for a feature | B | + +### Week 5: Oct 12 to Oct 13, closing + +| Day | Date | Post | Asset | Template | +|---|---|---|---|---| +| 29 | Mon Oct 12 | The number, week 5 | Metric card, final one. Add a small sparkline of all five Mondays underneath, so 30 days of honesty is visible in one glance | A | +| 30 | Tue Oct 13 | Thirty days in the open | Summary infographic. Every weekly number, what shipped, what did not. **Design this to work whether the numbers went up a lot or barely moved.** If they barely moved we still post it, so it cannot be a victory graphic | A, G | + +--- + +## 10. Definition of done + +An asset is finished when all of these are true. Check them yourself before delivering, because I will check them before posting and a bounce costs us both a day. + +- [ ] Exported in all four ratios, unless the day's row says otherwise +- [ ] All text inside the 10% safe margin +- [ ] Smallest type is at least 28px at 1080 wide +- [ ] Every numeral is Geist Mono +- [ ] Exactly one accent colour is doing work +- [ ] Exactly one call to action, as a full link, on its own final line +- [ ] Handles spelled correctly: `@Stackstream0X`, `@dev_jayteee`, `t.me/dev_jaytee` +- [ ] Zero invented numbers. Unknown figures left as visible `[N]` fields +- [ ] Rule 5.1 checked by reading the copy out loud +- [ ] No em dashes +- [ ] Motion assets are captioned and readable with the sound off +- [ ] Filename follows `SS_D07_slug_1x1.png` +- [ ] Editable source is in `_source` + +--- + +## 11. How to reach me + +Telegram `t.me/dev_jaytee` is fastest and I will answer within the hour during working hours. If you are blocked on anything, ask immediately rather than guessing. A wrong assumption caught in five minutes costs nothing; the same assumption caught at delivery costs a day we do not have. + +**Two things to ask me about rather than decide alone:** any number that appears on an asset, and any wording change to a settlement claim. Everything else, including the visual direction, is yours. + +--- + +*Jethro Irmiya, Sep 9, 2026. Live figures quoted here were true on Sep 8, 2026 and are refreshed from https://stackstream.xyz/api/stats on the morning of each post.* diff --git a/grant-application/M3_EVIDENCE_PACKAGE.md b/grant-application/M3_EVIDENCE_PACKAGE.md new file mode 100644 index 0000000..26d4b6a --- /dev/null +++ b/grant-application/M3_EVIDENCE_PACKAGE.md @@ -0,0 +1,102 @@ +# StackStream, M3 Evidence Package (living document) + +**Milestone 3 target:** 3 organisations registered and $10,000 equivalent streamed on Stacks mainnet. +**Grant:** Stacks Endowment, Q1 2026, Payments, Getting Started track. +**Started:** Sep 14, 2026. **Updated:** Sep 23, 2026. Updated daily while the campaign runs; every row below is verifiable from a public link or from the contract. + +This package follows the shape of `M1_EVIDENCE_PACKAGE.md` and `M2_EVIDENCE_PACKAGE.md`. It records what was actually shipped, not what was planned. The plan lives in `CONTENT_SCHEDULE.md`; if a day in the plan was not shipped, it is marked here as skipped, never quietly dropped. + +--- + +## Section 1, On-chain metrics + +Read directly from the contract through `https://stackstream.xyz/api/stats` on the morning of each Monday post. Never estimated. + +| Date | Block | Streams created | Organisations registered | Note | +|---|---|---|---|---| +| Sep 14, 2026 | not recorded | 11 | 0 | Campaign baseline, read at 14:56 UTC | +| Sep 21, 2026 | 9,037,877 | 11 | 0 | Week 2 | +| Sep 28, 2026 | | | | Week 3 | +| Oct 5, 2026 | | | | Week 4 | +| Oct 12, 2026 | | | | Week 5 | + +Rule carried from M2: any stream between our own wallets is labelled as ours wherever it appears, and is never counted as adoption. + +--- + +## Section 2, Public content shipped + +One row per calendar day. A row is only filled in on the day it was posted. Post links are pasted the same day so the record is verifiable later. + +| Day | Date | Narrative | Channels posted | Asset | Post links | +|---|---|---|---|---|---| +| 1 | Sep 14 | The call to real teams | Official X, Personal X, Grantees TG, WhatsApp | A | | +| 2 | Sep 15 | The tap, not the bucket | Official X, Personal X, LinkedIn, WhatsApp | B | | +| 3 | Sep 16 | Watch it move | Official X (pinned), Personal X, Stacks Discord, WhatsApp | H | | +| 4 | Sep 17 | Where the money actually sits | Official X, Personal X, WhatsApp | B, D | | +| 5 | Sep 18 | Payday that runs itself | Official X, Personal X, LinkedIn, Grantees TG (link share), WhatsApp | E | | +| 6 | Sep 19 | Why I built this | **Skipped** | | | +| 7 | Sep 20 | Money that moves like water | **Skipped** | | | +| 8 | Sep 21 | The number, week 2 | Official X, Personal X, WhatsApp | A | | +| 9 | Sep 22 | You are never locked in | Official X, Personal X, WhatsApp | B | | +| 10 | Sep 23 | A real transaction (stream 11 receipt) | Official X, Personal X, Stacks Discord, Grantees TG, WhatsApp | C | | + +**Standing rules every post obeyed:** one link per post, the follow line for @Stackstream0X from Day 3 onward, live numbers only, no deadlines, and the settlement language rule from `MARKETING_PLAN_V2.md`. + +--- + +## Section 3, Outreach + +Reported in aggregate here. Individual names, message texts and reply status are tracked in a local working file and can be shared with the grant team privately on request. + +| Week | Messages sent | Replies | Calls held | Outcome | +|---|---|---|---|---| +| Sep 14 to Sep 20 | 3 | 1 | 0 | One senior ecosystem contact has committed to trying the product after a scheduled committee meeting | +| Sep 21 to Sep 27 | 3 so far (Sep 23) | 0 so far | 1 (Privara onboarding call, see Section 4) | | +| Sep 28 to Oct 4 | | | | | +| Oct 5 to Oct 11 | | | | | + +--- + +## Section 4, Organisations onboarded + +An organisation counts toward M3 only once its registration transaction confirms on mainnet. Calls and commitments are recorded here as leading evidence, clearly separated from registrations. + +### Onboarding calls held + +| Date | Organisation | What they build | Stage | Next step | +|---|---|---|---|---| +| Sep 2026 | **Privara** (useprivara.xyz) | Privacy-preserving payments on Stacks: one-time recipient addresses for sBTC, USDCx and STX. Contracts, web app, relayer and SDK live on mainnet. Fellow Stacks Endowment grantee | Onboarding call held | Registration and first stream, on a call, from their wallet | + +### Registrations confirmed on mainnet + +| Date | Organisation | Registration tx | First stream tx | Token | Amount | +|---|---|---|---|---|---| +| | | | | | | + +--- + +## Section 5, Assets produced + +Designed to `DESIGNER_BRIEF_SEP2026.md`. Filenames follow `SS_D##_slug_ratio`. + +| Day | Asset | Delivered | Used in | +|---|---|---|---| +| 1 | SS_D01 metric card | | | +| 2 | SS_D02 tap-bucket | | | +| 3 | SS_D03 ticking-balance loop | | | +| 4 | SS_D04 where-money-sits | | | +| 5 | SS_D05 payday-runs-itself | | | +| 8 | SS_D08 metric card | | | +| 9 | SS_D09 never-locked-in | | | +| 10 | SS_D10 proof-card | | | + +--- + +## Section 6, Verifiable references + +- Live app: https://stackstream.xyz +- Live stats: https://stackstream.xyz/api/stats +- Stream 11 receipt (our own wallets): https://explorer.hiro.so/txid/0xe8367172fde244bb23b776fe6acda8afcb6cf9559ae67b7a2cd6f8dc5ca89148?chain=mainnet +- Contracts and audit report: https://github.com/jayteemoney/stackstream +- Grant listing: https://grants.stacksendowment.co/