Our proposal to the Dash DAO

Our Commitment:
High Quality Support
For All Builders Building With DASH.

Community-led. Built first. Verifiable.

What the lights mean

The team. Support and Build are lit because this proposal funds them. Dash Waves and Design wait as seeds for later.

The decision, in brief

128 DASH, for one month.

Amount128 DASH
TermOne superblock, about one month
Allocation72 core leadership (three working leads, 24 each) · 24 Support Team · 24 Build Team · 8 infrastructure & Dasha
Core serviceOffice Hours, Monday–Friday, 1–4 PM Central
Working hoursDST Active Hours — each lead logs ≥3 h/day, Mon–Fri, posted publicly on Discord & Telegram
After the monthA public report to the community, then a longer proposal built on what we learned
Coming soonDash Waves and The Dash Design Team, not funded by this proposal
Funded byThe Dash DAO treasury — no token sale, no strings
Proposal fee1 DASH, burned when the proposal is submitted, paid by us, not the treasury
StatusPre-proposal, for November’s round · current proposals on DashCentral

Why one month. We want to earn the DAO’s trust and bring energy to it by doing the work well, in the open, before asking for more. When the month ends we report back to the community: what we did, what it cost, what worked and what didn’t. Then we submit a longer proposal shaped by what we learned.

The treasury stays in the driver's seat. This proposal pays once, if masternodes vote it through. Anything after it is a new proposal and a new vote.

The film · choose your length · sound on

The Anchor Holds. Thirty seconds, or ten minutes.

Thirty seconds · the brief
Ten minutes · the whole plan

Chapters and every word are on the film’s page. The trailer, 2:52, is on the Support page.

The builder problem

Building on a blockchain can be hard.
It's even harder to set off and build alone.

Builders on Dash run into the same walls: a wallet or InstantSend question, a Platform data contract that won’t validate, a proposal they don’t know how to write. Right now the answer depends on who happens to be around. This proposal pays for a few people to be there reliably, at set hours, in public, with Dasha covering the rest of the day.

We built before we asked

Already live. Already working.

Months of unpaid build hours went into these before this proposal: built first, asked second. Each one is usable today.

Live

Dasha AI

Answers on the web and in Telegram, grounded in the Dash docs, with live governance and chain tools. Replies on X are paused while its API credits are topped up. Try her · her mind on GitHub

Live

Dash Alive

A public list of the projects building on Dash, the live DAO ballot, and the Pool, with every payment on the chain. Open it

Live

The Pulse

Public numbers: answers counted, Dasha’s public record, and her heartbeat. We count what fires, never what is said. See it

Scheduled

Office Hours

Monday to Friday, 1 to 4 PM Central, in the Telegram group, for any project or builder on Dash. Join the group

The month’s deliverables

What we’ll deliver, and how to check it.

Each one has an owner, a rhythm, a place to check it, and a line for done. We’re not setting adoption targets for the first month: the report sets the baseline the next proposal is measured against.

DeliverableOwnerHow oftenWhere to checkDone means
Office HoursSupport Team Lead, with the other leadsEvery weekday, 1–4 PM CentralThe Telegram group, the reportHeld on every weekday of the month, or the gap and its reason in the report
Logged hoursEach leadEvery weekdayPosted in the Telegram group, totals on the PulseAt least 3 hours each weekday per lead, as logged
Answers in our channelsCommunity Engagement LeadDailyThe Telegram group, email, the PulseQuestions answered or handed to the right person; the count and any left open in the report
Listing reviews on Dash AliveSupport Team Lead, with the Security Lead for the checksAs listings arriveEach listing’s status on Dash AliveEvery listing received in the month reviewed: Verified, or told why not
The public answer baseCommunity Engagement LeadWeeklyGitHubStarted in public, with the month’s useful answers in it
A builder onboarding pathSupport Team LeadOnceLinked from the Support pageOne guided path for new builders, published
The month reportDirectorOnce, when the month endsThe Pulse and the Telegram groupHours, sessions, answers, reviews, every DASH spent with its transaction, what slipped, what’s next

The answer base, the guides and what contributors write belong to the Dash community.

Where every Dash goes

What 128 DASH buys, for one month.

Every Dash maps to a named team, a published role, or a logged hour.

72DASH
Core leadership — three working leads

24 DASH per lead for the month, for at least 3 logged hours every weekday: direction, community engagement, and cyber & AI security. Hours posted publicly, every week.

24DASH
The Dash Support Team

Office Hours every weekday, daily coverage in our channels, the public answer base, and contributor hours for community members answering alongside the leads. The engine room.

24DASH
The Dash Build Team

Developer support hours, onboarding paths, and bounties for community devs who unblock real Dash builders, plus Dash Alive listing reviews and Verified checks.

8DASH
Infrastructure & Dasha

Her minds, hosting, the Pulse, the commons: deliberately lean, and open source.

Dash Waves and The Dash Design Team are coming soon and draw nothing from this budget. Unspent builder funds roll forward to builders in the next round, not to the team. Every hour, role and payment is reported on the Pulse.

The hours, plainly
  • Office Hours: 15 staffed hours a week, 1 to 4 PM Central, Monday to Friday.
  • Lead hours: at least 3 hours every weekday per lead. That’s 15 a week each and 45 a week combined, and Office Hours count toward them.
  • Over the month: a month is about 4.3 weeks, so about 65 hours per lead and about 195 combined. Those are estimates; the report gives the hours actually logged.
  • Who’s paid from which line: each lead is paid from the 72 DASH leadership line only. The Support and Build lines pay community contributors and bounties, so no hour is paid twice.
  • Holidays and absences: if a lead is away, the others cover Office Hours, and the report says so.
The people on the hook

The Dash Support Core Team.

August James Domanchuk

August James Domanchuk

Director · Support Team Lead

August.Dash — builder, designer, systems thinker. Built Dasha AI and this entire platform before asking the DAO for anything. Directs the team and manages all payments until the Operations Lead and DST Accountant stand up.

@BuiltByAugustGitHub

“It is always the right time for the right work.”

NM

Natalie Mitchell

Community Engagement Team Lead

A background in data science and content writing — reading the signal honestly, writing the words that bring people in. Natalie leads how the team shows up, every day.

ES

Ember Seoni

Cyber Security & AI Security Team Lead

Deep cyber security skillset, now completing her studies in AI and AI Security. Team lead of SystemsBench — open-source benchmarking of AI models’ long-horizon systems thinking.

Where this role evolves: Dash AI Agent Security Team Lead — a security-and-integrity role for the agentic era, building safe and secure Dash AI agent foundations for the whole DAO.

Not in this proposal: an Operations Lead and a DST Accountant may join in a later one, if the work calls for them.

After the month

Report, learn, then propose again.

1

Report

When the month ends we publish the report on the Pulse and in the Telegram group: hours logged, sessions held, questions answered, listings reviewed, every DASH spent with its transaction, and what slipped.

2

Listen

We ask builders, the community and masternode owners what to keep, cut or change, in the open.

3

Propose again

We submit a longer proposal with that in hand. It’s a new proposal and a new vote, and the report is its evidence.

Ideas for later proposals, not funded by this one: an Operations Lead and a DST Accountant, a support desk for masternode operators, and Dash Waves and the Dash Design Team.

The honest ledger

What a yes vote costs.
And what it buys.

What the network risks

  • 128 DASH, paid once, if the vote passes. Nothing more is paid without a new proposal and a new vote.
  • Limited hours. Three leads, each working at least 3 hours a weekday. People are there in Office Hours; outside them Dasha answers and the team follows up.
  • Price moves. The proposal is paid in DASH, so its dollar value moves with the price.
  • Outside dependencies. Dasha relies on outside AI model providers, and the site runs on Vercel and GitHub. August holds the domains, accounts and hosting for now. The code is public on GitHub.
  • If something goes wrong, the report says so, with what we’ll change.

What the network gains

  • Staffed help in Telegram and on the web, so a builder gets an answer before they leave for another chain.
  • Dasha AI, answering around the clock in many languages. She’s live now.
  • Office Hours every weekday, 1–4 PM Central: a place any builder on Dash can bring a question, a bug or a proposal draft.
  • The Dash Alive DAO Project Registry: one live, public list of the projects building on Dash, already running.
  • A public answer base and public metrics anyone can read.
  • A month of evidence, reported in public, to judge the next proposal by.

Under promise.
Over deliver.

Trust is the foundation and cornerstone of the Dash DAO. We intend to earn it every single superblock.

Pre-proposal, for November’s round.

Current Proposals On DashCentral Talk To Us First
Chat with Dasha AI