# Dash Waves

### The Wave Praxis, built on Dash

**Status:** Coming soon. A proposed direction from the Dash Support Team. Nothing here has launched, and no project named here has agreed to anything unless it says so.  
**Version:** 0.3, Dash edition, September 24, 2026  
**Grows from:** The Wave Praxis by Waves.Fund, v0.1  
**Core practice:** Trust People. And They Become Trustworthy.  
**Home:** [dashsupport.team/waves](https://dashsupport.team/waves)  
**Listen:** the whole praxis, narrated, at [dashsupport.team/waves](https://dashsupport.team/waves#praxis)

> A Wave begins with a person and a purpose. A Wave Guide helps give it form. Other people can carry it, challenge it, improve it, and help move it forward. The Wave keeps its home and its history as it grows.

On Dash, the tide comes every month, and it pays in DASH.

## 1. Two waves, one motion

The Dash Waves mark is two waves moving together. They are the two halves of this praxis.

**The first wave is the Wave Praxis:** a human way to build. A project gets one lasting home, a Wave Guide who helps give it form, people who carry it further, and a Journey that records what actually happened.

**The second wave is the Dash network:** digital cash that settles in about two seconds, a treasury that pays builders every month, masternode owners who vote on every proposal, ChainLocks that keep the record from being rewritten, and Dash Platform for identities and open data.

Dash has run a working treasury for about a decade. What it has never had is a common shape for the work around those payments: where a project lives, who is helping, what it needs next, and what the last payment achieved. The Wave Praxis is that shape, and on its own it has no treasury, no vote and no ledger it can trust. Dash Waves brings the two together.

A **Dash Wave** is a living, builder-owned home for work on Dash. A Wave Guide helps shape it and the community carries it. When the work needs treasury funding, the Wave goes to the ballot as a proposal, is paid in DASH at the superblock if masternode owners vote it through, and reports back before it asks again.

Anyone who meets a Dash Wave should see three things at once:

- **The story:** what is being built on Dash, and why it matters.
- **The next move:** what is needed now, and how to help.
- **The evidence:** what has happened so far, and how to check each claim, down to the transaction.

## 2. The statement

Dash already has the ocean and the tide. The ocean is digital cash that settles in seconds. The tide is the treasury, which rises out of the network every month and pays builders in DASH. What a builder needs is a Wave: a shape the tide can lift, carried by people who believe in it, leaving a wake every masternode owner can read.

When information moves with the money, the DAO learns every month. Donella Meadows called missing information flows one of the most common reasons systems fail, and restoring them one of the cheapest and strongest ways to change one. That is the leverage in Dash Waves. The tide stays the same size, and every month it lifts work the network can see.

This is also where the core practice becomes something you can see. *Trust People. And They Become Trustworthy.* On Dash, trust is extended in small steps: one pass, one month, one milestone at a time. The Journey records each step and whether it was kept. Over many tides, that record becomes a reputation anyone can check, and it travels with the builder wherever they go next.

| On the water | On Dash |
| --- | --- |
| The ocean | DASH itself: digital cash that settles in about two seconds |
| The tide | The superblock: about once a month the network pays the proposals it voted through |
| The shore | The vote: masternode owners decide what each tide carries |
| A tide pool | A Wave Pool: a public Dash address with a named steward and a published policy |
| The wake | The Journey: every step dated, every DASH tied to its transaction |
| The anchor | ChainLocks: once a block is locked, the record holds |

## 3. Where the two waves bind

Six places where the Wave Praxis and the Dash network lock together. Each one uses something Dash already runs, and each one closes a loop that is open today.

### Binding 1 · The proposal points home

A Dash proposal's on-chain record carries a name, a payment address, an amount, start and end dates, and a URL. Point that URL at the Wave's home (or link the Wave from the proposal's DashCentral page) and record the proposal's hash in the Wave. The chain object and the living record then lead to each other: a voter who finds the proposal finds its whole story, and anyone reading the Wave can check its ballot status on chain.

**The leverage:** a habit, with no new protocol, that ties every treasury payment to a record people can read.

### Binding 2 · The superblock is the heartbeat

The treasury pays about once a month, and votes stop counting 1,662 blocks, about three days, before it pays. A Dash Wave keeps the same beat. Its month report is published before the next vote cutoff, so masternode owners vote on last month's evidence as well as next month's promise.

**The leverage:** the delay between funding and feedback shrinks to a single cycle, and every vote is informed by the one before it.

### Binding 3 · The ledger explains itself

Every payment to a proposal's address is public on the chain, and so is every DASH that leaves it. A Dash Wave watches its addresses with a watch-only key and labels each movement: which superblock paid it, which budget line spent it, which piece of work it paid for. Anything unlabelled says so ("not yet classified"), the way the Dash Support Pool already does.

**The leverage:** the money on Dash is already public. The Wave adds what it meant.

### Binding 4 · Every pass gets its own addresses

When someone accepts a pass to carry a Wave, the Wave derives fresh receiving addresses for that pass from its watch-only key, the way Dash Alive already derives one address for every payment. DASH that arrives through the carrier's link lands at that pass's addresses and counts once InstantSend locks it. The carrier's path shows on the chain without cookies, tracking pixels or donor identities.

**The leverage:** the praxis asks for honest path attribution, and on Dash the ledger provides it.

### Binding 5 · The Journey is signed on Dash Platform

The Wave format can be published as a Dash Platform data contract with a handful of document types: the Wave, a Journey event, a pass, a pool and a report. The steward's Platform identity signs each event, and the contract can make Journey events immutable, so a correction is a new event that points to the old one. Anyone can read the contract. Private data never goes on chain.

**The leverage:** an open standard every Dash app can read on the day it ships, with tamper evidence built in.

### Binding 6 · Tide Pools for the missing middle

Many good projects are too small for a proposal: one translation, a merchant's first month, a single library release. A Tide Pool is a Wave Pool that the DAO refills by treasury proposal, one month at a time. Its steward pays small milestone rewards in DASH under a published policy, discloses every payment in the pool's Journey, and reports each month before asking for the next refill. Masternode owners fund one accountable pool instead of weighing fifty tiny proposals, and they can stop refilling it in any month.

**The leverage:** the treasury opens to small builders, and every DASH stays one vote away from the network.

Together the six bindings close one large loop. A Wave asks, the network pays, the work shows, and the next ask is easier to trust.

## 4. First principles, on Dash

The praxis rests on a few principles. On Dash, each one has a mechanism behind it.

1. **The builder owns the direction.** The builder or team controls the mission, the story, the permissions and the decisions. On Dash that includes the keys: the proposal's payment address and the Wave's receiving keys belong to the steward, and no Guide, host or carrier ever holds them.
2. **Human first, adaptive by design.** A Guide from the Dash community listens before choosing any tool. A Wave has a small common foundation and no required template.
3. **One home, many paths.** Every Wave has one lasting home. Proposals, posts, embeds and passes all point back to it.
4. **Movement is visible when people consent.** The Journey shows approved facts. Donor identities and private work stay private, even though amounts and txids are public on the chain.
5. **Credit follows evidence.** A feature is not an endorsement, a visit is not a contribution, and a pledge is not DASH received. A DASH payment proves that money arrived. It doesn't prove the work was done, so the Journey shows both, labelled.
6. **Support does not buy control.** DASH sent to a Wave is support. Only masternode owners allocate the treasury, and no payment buys a vote, a seat on the team or a say over the story.
7. **Portable means the builder can leave.** A Wave exports as plain JSON, and its public record lives in an open data contract, so it depends on no single host, channel or company, including us.
8. **Trust is practiced.** The month report comes before the next ask. A correction is a new event, never a silent edit. Every claim can be checked.
9. **Every Wave can end well.** When the work is done, or when it stops, the steward writes a final report, any pool follows its published rule for what is left, and the Journey stays as a public record. A Wave that ended honestly counts in its builder's favour.

## 5. What a Dash Wave is

A Dash Wave is a **living, builder-owned project object** with a lasting home, a story people can read, clear ways to act, a treasury layer, and a Journey that grows with consent. It can be shown differently in different places and still keep its identity and meaning.

The shared structure stays small. It answers six questions: **Who is building? Why does this matter? What is happening? What is needed now? How can someone help? What can be verified?** The Guide and the builder decide the rest.

| Layer | Every Dash Wave has | Built from on Dash |
| --- | --- | --- |
| Identity | A stable Wave ID, a home, a steward, created and updated dates | A Dash Platform identity and username for the steward; the Wave's document ID in the open data contract |
| Story | Purpose, current state, intended change, people affected | The Wave's home, and its DashCentral thread once it becomes a proposal |
| Action | The next moves, and who can take them | Support in DASH, carry the Wave, join the work; masternode owners vote |
| Evidence | Source, date and status for every public claim | Links and reports, plus transactions locked by InstantSend or ChainLocks |
| Treasury | Funding routes, amounts, status, who reports back | The proposal hash, the payment address, superblock payments, pool policies |
| Participation | Roles, permissions, consent and review rules | Set by the steward; the masternode vote stays the only treasury decision |
| Journey | Dated events with an actor, a type, a visibility and an evidence level | Signed Platform documents; any event involving DASH carries its txid |
| Portability | Exportable data and a versioned format | A JSON export and the open data contract |

**Optional modules** are added when the builder needs them, never to make a Wave look complete: a proposal kit (draft, budget lines, the vote cutoff), a Tide Pool, a team board, a merchant map, a translation queue, a research notebook, a public roadmap.

### Invariants for a Dash Wave

- Every Wave **must** name its steward and its home.
- Every DASH figure **must** link its txid or say that it is an estimate.
- Every public claim **must** say whether it is self-reported, linked, partner-confirmed or transaction-verified.
- A Wave on the ballot **must** link its proposal hash. A Wave that isn't on the ballot **must not** look like one.
- Receiving keys **must** stay with the steward. Nobody working on a Wave ever asks for a recovery phrase.
- A person **must** consent before their contribution or identity is made public.
- A pass **must** name its carrier, scope, duration and any paid placement, and the steward can revoke it.
- A correction **must** add a new event and keep the fact that the earlier version existed.
- A Wave that ends **must** say so, with a final report.
- An adapter **must** state what it can read or publish, and never imply a connection it doesn't have.
- A Wave **should** keep its proofs on Dash and its story portable, so it still reads and works when exported.

## 6. The Wave Guide on Dash

Every Wave starts with a conversation. The Guide helps a builder turn an intention into a working Wave. The builder keeps the agency; the Guide brings experience with Dash. Guides come from the community: Office Hours staff, people who have run proposals before, builders who have shipped on Dash Platform.

1. **Listen and map.** Learn the mission, the people, the stage, what already exists, what the work needs and what the builder does *not* want made public.
2. **Shape the Wave.** Write a brief together: story, audience, next move, evidence, modules, consent and what success looks like. Confirm scope and ownership before building anything.
3. **Build and connect.** Build the home and the tools. Set up receiving addresses from a watch-only key the builder holds. Connect channels only with the builder's approval, and keep an export and a record of decisions.
4. **Coordinate the journey.** Invite collaborators, review proposed changes, issue passes and help carriers share the Wave responsibly.
5. **Guide the funding route.** Choose between direct support, a Tide Pool and a treasury proposal. For a proposal: the payment address the builder controls, the 1 DASH fee (it is burned), the DashCentral thread, the vote cutoff three days before the superblock, and the month report after it.
6. **Evolve and hand over.** Review the month with the builder, improve the Wave and make sure the team can run it without depending on one Guide.

A Guide's time is paid in the open, from one of three places: the Wave's own funding, a Tide Pool set up to fund guidance for first-time builders, or nowhere at all, when a Guide volunteers. Whichever it is, the Wave shows it.

A Guide's profile can live on their Dash username: the Waves they served, the next moves those Waves completed, and DASH committed kept separate from DASH received (which is checkable on the chain). Guides disclose fees, referral relationships and conflicts on every Wave they touch.

## 7. A Wave's month on Dash

The treasury runs on a monthly beat, and a Wave moves with it.

1. **Form.** The builder and a Wave Guide shape the Wave: its story, next move, evidence and funding route.
2. **Carry.** People pass it on: creators, community channels in many languages, other builders. Every pass is invited, scoped and revocable.
3. **Propose.** When the work needs treasury funding, the owner submits a proposal on chain, pointing home, and opens the discussion on DashCentral. The Journey sits next to the pitch.
4. **Vote.** Masternode owners vote. A proposal needs net yes votes worth 10% of all possible votes and room in the month's budget. Votes stop counting about three days before the superblock.
5. **Tide.** The superblock pays every funded proposal in DASH, straight to its payment address. The payment enters the Journey with its txid.
6. **Report.** The Wave shows what the DASH did: what was delivered, the evidence and what is unfinished. The report is out before the next cutoff, and the next proposal is made with what the month taught.

The Dash Support Team's own first proposal follows this cycle on purpose: one month, one report, then a longer proposal shaped by what we learned. Small, kept promises, one tide at a time, are how trust compounds.

## 8. Pass the Wave

Passing a Wave is a permissioned invitation to carry its story somewhere new. The builder keeps the home. A carrier may add a perspective, propose an edit, publish a feature, make an introduction or invite support. The builder decides which changes become part of the Wave.

The talking stick is the ritual: *I have listened; I will carry this forward; I will show what I did.* Holding a Wave is a temporary role. It isn't ownership, and it grants no authority to make financial promises and no access to private data.

A pass moves through **invited → accepted → active → completed, declined, expired or revoked**. Its record names the carrier, the scope, the channel, the period and any paid placement. On Dash, an accepted pass also gets its own receiving addresses (Binding 4), so what arrives through that carrier's path is visible on the chain, and a pass never carries any payment address other than the Wave's own.

Carriers on Dash are the people who already move the network: community channels in many languages, creators, merchants, and masternode owners who share what they back.

## 9. The Journey and the evidence ladder

The Journey is a readable timeline of the Wave in motion: a Guide match, an update, a feature, an introduction, a proposal, a vote result, a superblock payment, a milestone, a correction. Each event has a date, a source, a visibility and an evidence level.

| Evidence level | What it means | On Dash |
| --- | --- | --- |
| Self-reported | The steward says so | A Journey event signed by the steward's identity |
| Linked | A public source backs it | The link and the date it was checked |
| Partner-confirmed | Someone accountable confirms it | A confirmation signed by the partner's identity |
| Transaction-verified | The DASH moved | InstantSend-locked or in a ChainLocked block, with its txid |

Every Wave also keeps a **tide ledger**: each DASH in (a superblock, direct support, a pool award) and each DASH out (to contributors, to budget lines), labelled with what it was for. The chain supplies the facts and the Wave supplies the meaning (Binding 3).

**Example.** A merchant circle in one city builds a Wave with a Guide. A local creator accepts a pass and publishes a video. Viewers follow the creator's link, and some send DASH, which lands at the pass's own addresses and shows as transaction-verified. Others offer to help new shops. The Journey shows the feature, the DASH that arrived through that path and the shops that joined. It shows path attribution, and never claims the creator caused every gift. The creator's disclosed carrier reward is paid after the month report, with its txid.

When a Wave ends, its Journey stays. The last entry is the final report, and the record keeps counting for the people who built it.

## 10. DASH, rewards and pools

Funding is one possible action within a Wave. A Wave may need people, knowledge, a customer, an introduction or time more than DASH. Its funding route always states the recipient, the purpose, the mechanism, any fees, the current status and who reports back.

### Four rules

- **Rewards follow delivered work.** A view, a like or a share earns nothing by itself. DASH is paid when the evidence for the work reaches the level agreed in advance.
- **Every reward is disclosed on the Wave:** the role, the reason, the amount and the txid. A person's name appears only with their consent.
- **Dash Waves holds no one's DASH.** Every pool is a public Dash address with a named steward and a published policy. Nothing is custodial.
- **Support is not an investment.** Nobody backs a Wave for a return, and no Wave may promise funding or returns. Any future investment layer would be a separate product built with qualified partners.

### Three ways DASH reaches a Wave

1. **Direct support.** Anyone can send DASH to a Wave's own single-use address, the way Dash Alive works today. It counts once it is InstantSend-locked or confirmed, and it appears in the Journey.
2. **Treasury proposals.** A Wave that needs more asks the DAO: one proposal, one superblock, paid in DASH. Start small, report, then ask for more.
3. **Wave Pools.** A pool gathers DASH for a shared goal, such as builder support, translations or the merchants of one city.

### Three ways a Wave grows

- **Milestone rewards.** A Wave can post a reward in DASH for a specific piece of work, such as a feature shipped, a translation merged or a merchant's first month of sales. It pays when the evidence arrives.
- **Carrier rewards.** A Wave may set aside a disclosed share of the DASH that arrives through a carrier's pass addresses, paid after the month report.
- **Growth pools.** Part of a proposal's budget can seed a pool for the Waves that come after it, so each tide lifts more builders than the last. In our own proposal, builder funds we don't spend roll forward to builders in the next round.

### Tide Pools

A Tide Pool (Binding 6) is refilled by a treasury proposal, one month at a time. Before it takes a single duff, every pool publishes its policy:

- who can contribute, and who controls the address;
- who decides allocations, and how;
- eligibility and conflicts of interest;
- how funds are released, and any fees;
- reporting and appeals;
- what happens if the goal fails, or the DAO stops refilling it;
- what is public.

A support signal, such as a DASH payment on Dash Alive, can inform a pool's decision. It never replaces the pool's published process, and it never replaces the masternode vote.

### Guarding the loop

Any reward can be gamed, so the rules are written with the people who would try in mind.

- A carrier's reward is a share of what arrives, so sending your own DASH through your own pass only ever costs you.
- A milestone reward pays for evidence a second person can check, never for a claim alone.
- Nobody approves a reward to themselves, and nobody reviews their own milestone.
- When a pattern looks wrong, the pass or the reward pauses, and the Journey says why.

Delivery builds trust, trust brings carriers and support, and support funds the next delivery. Rewards that pay only on evidence keep that loop honest, so a Wave grows through work the network can see.

## 11. The Wave as communication, coordination and growth

A Wave carries the story and the work. It gives someone a way to understand a mission, see its progress, choose a useful action and follow what happens next.

For the DAO, a Wave is also a better proposal: the pitch, the budget, the Journey and last month's report in one place, linked from DashCentral. For growth, it is the source every channel version comes from: a DashCentral post, a Telegram message, an X thread, a video, a translation. Those are **expressions of one Wave**, and paid placement is always labelled.

For coordination, it holds the next moves, their owners, the decisions and the updates. The same Wave can change its emphasis as the work moves from an idea to a first proposal to a project the network depends on.

## 12. The Wave as a Dash data contract

The Wave format should be published as an open, versioned specification after real Waves show what is truly common. On Dash, the natural form is a Dash Platform data contract. A first draft could hold five document types:

| Document | Holds | Signed by |
| --- | --- | --- |
| wave | ID, name, home URL, steward, status, proposal hash when there is one | The steward |
| journeyEvent | Date, type, summary, visibility, evidence level, link or txid | The steward, or a confirming partner |
| pass | Carrier, scope, channel, period, disclosure, state | The steward and the carrier |
| pool | Address, steward, policy version, policy link | The pool's steward |
| report | Period, delivered, evidence, unfinished, DASH in and out, and whether it is the final report | The steward |

Extensions stay namespaced and optional, so a custom Wave never has to fit one layout. Integration grows in levels:

| Level | Capability | On Dash |
| --- | --- | --- |
| 1. Share | A link to the home with an accurate preview | Posted on DashCentral, Telegram or X |
| 2. Render | A permissioned embed or channel version | An approved Wave card on a partner site |
| 3. Publish | An authorized account connection | A post the builder approves |
| 4. Exchange | An approved two-way data flow | Proposal status and votes read from the Dash network or DashCentral's public API |
| 5. Transact | A financial action completed and confirmed | DASH received at the Wave's own address, locked by InstantSend |

## 13. Ownership, safety and verification

The builder owns their content and receives their data, their exports and, as agreed before work starts, the source of anything custom built for them. Publishing the open format doesn't publish anyone's private content.

Keys stay with their owners. A Guide sets up watch-only receiving from a key the builder holds, and nobody working on a Wave ever asks for, stores or sees a recovery phrase.

Dash can prove that a payment happened and when. It can't prove that the work was good; that still takes accountable people, source evidence and honest labels. Anchor proofs on Dash and keep private data off chain. Label sponsorships and paid placements clearly. Give every metric a source and its limits, and never present an estimate, a pledge or a support signal as DASH received.

## 14. Founding Waves

### Wave 001 · DashSupport.Team

**Founding Wave, stewarded by the Dash Support Team.**

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

**The systemic problem:** builders on Dash, like builders across crypto, mostly work alone. Good projects stall on the same few questions, and the answers are scattered across docs, forums and chats.

**The Wave:** "Dash Supports" is a community-led support team for all builders building on Dash DAO. Office Hours every weekday, answers in our channels, Dasha AI at any hour, and a live registry of the projects building on Dash.

**Live today:** Dasha AI on the web and in Telegram · Office Hours, Monday to Friday, 1 to 4 PM Central · Dash Alive, the project registry · the Dash Support Pool and its policy · The Pulse, our public numbers.

**Next move:** one month on the ballot. 108 DASH for one superblock: 60 to three working leads, 20 to the Support Team, 20 to builder support and 8 to infrastructure and Dasha. Then a public month report, and a longer proposal shaped by it.

**Growth pool:** builder funds we don't spend roll forward to builders in the next round.

**Journey:**

- Jun 2026 · DashSupport.Team is live · linked
- Aug 2026 · Dash Alive and the Dash Support Pool open · linked
- Sep 23, 2026 · Office Hours begin, Monday to Friday · linked
- Sep 24, 2026 · The one-month proposal is prepared, 108 DASH · self-reported
- Next · On the ballot, then the superblock, then the month report · pending

### Wave 002 · DashCentral.org

**An invitation.** Written for DashCentral by the Dash Support Team, not by DashCentral. They haven't joined or endorsed Dash Waves. If they want this Wave, it is theirs to shape.

**The systemic problem:** DAOs vote once and then look away. Each month masternode owners judge new proposals mostly on promises, while the record of what earlier funding delivered is spread across threads, chats and the chain.

**The Wave:** proposal Journeys. DashCentral is where much of the Dash DAO already reads, discusses and votes on proposals. A Journey beside each funded proposal would show what was asked, what each superblock paid (with the txid), what was delivered, and how each claim is evidenced. The track record would sit next to the vote.

**Why it matters:** better information at the moment of the vote (Bindings 1 and 2). Owners who deliver would find their next proposal easier, and voters would spend less time digging.

**Next move:** a conversation with DashCentral's team.

**Journey:**

- Sep 24, 2026 · Invitation written · self-reported
- Next · DashCentral's reply · pending

### Wave 003 · Outlier.Systems

**Example Wave, stewarded by Outlier.Systems.** Strategic Systems Intelligence Agency.

> Solutions For The Data Backed World

**The systemic problem:** DAOs fund projects one at a time and rarely see the system they are funding. Nobody maps where DASH, people and information actually flow, so the places where a small change would help most go unseen.

**The Wave:** a living systems map of the Dash DAO. It traces the flows between the treasury, masternode owners, builders, merchants and users, draws in the feedback loops and delays, and marks the leverage points. It is built in public and handed to the DAO to challenge and improve.

**The offer:** Systems Intelligence Design (SID) available to teams and communities for coherence and aligned agency.

**Next move:** map one full budget cycle, from proposal to superblock to report, and publish it for the DAO.

**Journey:**

- Next · The first map of one budget cycle · pending

## 15. Sample Waves

Illustrations of what Dash Waves could carry. These projects don't exist yet, and every number in them is an example.

### Merchant Circles

**The systemic problem:** most crypto sits still. Coins wait in wallets and on exchanges, and the few shops that accept them are hard to find and often stop after the first month.

**The Wave:** one city's merchants who accept Dash, carried by the people who shop there. A live map, a local Guide who helps each shop through its first month, and a Tide Pool that pays that help in DASH.

**Reward:** a local helper earns DASH when a merchant they brought in reaches 30 InstantSend payments, counted with the merchant's consent.

### Keys Home

**The systemic problem:** when an exchange or custodian fails, people lose savings they never held the keys to, and they learn about self-custody too late.

**The Wave:** small self-custody circles. A Guide helps each person move their DASH into a wallet they control and back up the recovery phrase themselves, offline. Nobody else ever asks for it or sees it. Graduates carry the Wave by guiding the next circle.

**Reward:** a Guide earns DASH for each completed circle, confirmed by a signed message from each new wallet, so no balance is ever made public.

### The Keepers

**The systemic problem:** crypto runs on open-source code that everyone uses and few people maintain. When a maintainer burns out, wallets, libraries and explorers slowly decay.

**The Wave:** a Wave for the tools Dash builders depend on: SDKs, libraries, explorers and docs. The people who use them carry it, and the maintainers name what they need next.

**Reward:** a Tide Pool pays maintainers in DASH for each reviewed release, with the release and the payment linked in the Journey.

## 16. The honest path on Dash

**The first month: September 24 to October 24, 2026.** Listen before building. Talk with builders and masternode owners in Office Hours and on DashCentral, find the first Wave Guides, shape the founding Waves with the people they belong to, and publish what we learned.

**Pilot: prove usefulness.** Three founding Waves, each with a Guide, one permissioned pass, one real action and a readable Journey, each running across at least one superblock. Use existing, proven rails for DASH. Measure whether masternode owners found the Waves useful when they voted, and whether the builders completed their next move.

**Extract: publish what repeats.** Find the smallest structure all three shared. Publish a draft data contract, an export format and a reference implementation, and invite builders and Guides to challenge them.

**Connect: grow through consent.** Add embeds, channel versions and approved publishing. Offer proposal Journeys to DashCentral and other Dash apps, and connect only where the partner wants it.

**Expand: add accountable funding.** Propose the first Tide Pool to the DAO. Publish Guide standards and outcome profiles. Explore paying a Wave by its Dash username, so supporters never have to copy an address. Share actual results and limits before making large claims.

### Questions the Dash pilot must answer

- What is the smallest structure that helps every builder without flattening their story?
- What do masternode owners want to see in a Wave before they vote?
- Which Journey events belong on Dash Platform, and which should stay off chain?
- Who stewards the first Tide Pool, and who approves its releases?
- What share of a proposal, if any, should seed a growth pool?
- How do we reward carriers without paying for attention?
- How should a Wave end, and what should its final report hold?
- Which parts should be open, which belong to the builder, and which are a paid service?

## 17. What this means for the Dash DAO

- **For masternode owners:** the pitch, the budget and the record in one place before you vote, and the month report in the same place after.
- **For builders:** a home that outlives any one proposal, a Guide for the hard parts, people who carry your work, and a route to DASH that fits the size of the job.
- **For newcomers:** a way into Dash that starts with a person and a project, before anyone has to learn how governance works.
- **For the network:** more DASH moving to people doing work the DAO can see, a treasury that learns every month, and more projects that stay built.

## 18. The statement

**Raise Money In A New Way.**

A Wave is not finished when it is published. It grows when someone listens, acts, carries it onward, and gives the work back to its people with more clarity than they found it. The protocol should make that movement possible; the praxis should make it trustworthy.

On Dash, the tide comes every month. Dash Waves give it work worth lifting.

## Coming soon

Dash Waves isn't live yet. This is what works today:

- Shape your idea with Dasha AI at any hour: [dashsupport.team/dasha](https://dashsupport.team/dasha)
- Come to Office Hours, Monday to Friday, 1 to 4 PM Central, in the [Telegram group](https://t.me/TheDashSupportTEAM)
- List your project on Dash Alive: [dashsupport.team/Dash-Alive](https://dashsupport.team/Dash-Alive)

Want to shape one of the first Dash Waves? Tell us in Office Hours.

## Words used here

- **DASH:** the digital cash of the Dash network. A **duff** is its smallest unit, one hundred-millionth of a DASH.
- **Superblock:** the block, about once a month, that pays the proposals masternode owners voted through.
- **Masternode owners:** the people who run the network's masternodes and vote on every treasury proposal.
- **InstantSend:** Dash's lock that makes a payment final in about two seconds.
- **ChainLocks:** Dash's protection that keeps confirmed blocks from being rewritten.
- **Dash Platform:** the part of Dash that holds identities, usernames and open data contracts.
- **txid:** a transaction's public ID, which anyone can look up on the chain.
- **Wave:** a living, builder-owned home for work on Dash.
- **Wave Guide:** the person who helps a builder give a Wave its form.
- **Carrier and pass:** a carrier is someone invited to share a Wave; the pass is that invitation, with its scope and its own addresses.
- **Journey:** the dated, evidenced record of what happened.
- **Tide Pool:** a Wave Pool the DAO refills by proposal, one month at a time.

---

**References.** The Wave Praxis, Waves.Fund, v0.1, the source this edition grows from · [Dash documentation](https://docs.dash.org) for governance, InstantSend, ChainLocks and Dash Platform · [DashCentral](https://www.dashcentral.org) · Donella Meadows, [Leverage Points: Places to Intervene in a System](https://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/) · From the original praxis: [FTC guidance on creator relationships](https://www.ftc.gov/node/60343) and the [SEC guide to broker-dealer registration](https://www.sec.gov/about/divisions-offices/division-trading-markets/division-trading-markets-compliance-guides/guide-broker-dealer-registration). These references inform boundaries and possible integrations; they don't establish any partnership or approval.

*Dash Waves is a Dash Support Team initiative, grown from the Wave Praxis by Waves.Fund. Coming soon at [dashsupport.team/waves](https://dashsupport.team/waves).*