Make, Stake, Semble, Wave

V2.1, October 27, 2026. The clean copy of V2.0, ready to build from. The content is the same; the review marks are gone. Lines marked ◆ were added by Davara and Claude, and Davara's own lines carry her name. Everything else is August's. A name that is new in V2 is marked (proposed word).

This spec adds Dash stakes, Semble Seats paid in Dash, and funding to what's already live on Semble.CC and DashSupport.TEAM, and ties both to Waves.Fund and Dash Waves.

The whole loop: make something real, stake 3 Dash behind it, gather people who pay to be there, keep a promise every month, earn your wave, and plant the next seed.

◆ Davara · Opening

A door opens on a weeknight in Chicago.
Ten people pay at it in Dash and come in.
Each one signs that they were there.
Three Dash sit still at an address
where anyone can look and no platform can reach.
A builder says what she will do this month.
Next month she shows it to a room.
The people who saw it say so, and the date is kept.
She does it again, and again.
The chain pays once a month
for promises kept the month before.
The same day, the pool sends three Dash
to someone she believes in.
He opens a door on a weeknight.

Davara's lines are for this spec. Site copy stays August's.

Why this exists

People come first. Every rule here exists to protect the people who build, gather, and back each other.

Trust is the foundation. It grows in small steps, the TrustBase records every one, and only what really happened, in the room and on the chain, can prove it.

Bitcoin proved that money doesn't need a bank. Dash can prove something more: a network that pays its own builders. Its treasury pays out every month, which Bitcoin was never built to do. This model makes sure that money reaches the people who show up, keep their word, and back each other.

Crypto funding is known for easy money and big promises. Here, money follows proof: people who show up, pay, and keep coming back. The bar is high, and it's set by results, not by price.

◆ What the chain shows

The treasury's own record, read from every superblock since March 5, 2017 (block 631,408) on Symphonic Vision ONE's Whole Memory. One project can use several addresses, so these count payout addresses, not projects.

And this month:

• The treasury can pay 6,828 DASH a payday. On October 21 it paid 5,393 to 6 proposals. Every other payday this year paid 14 or 15.
• On the November 20 ballot (block 2,575,480), 5 proposals are on track, asking 5,193 together. About 1,635 DASH would go unclaimed, and budget nobody asks for is never created. Three of those five lines end with that payday.
• No DashSupport.TEAM or Semble.CC proposal is on chain yet.

What this means for the spec: the money is there every month. What has thinned is the flow of new builders reaching the ballot, and the share who come back with results. Make, Stake, Semble, Wave is built for both.

Semble Strong, Secure, Safe, and Sound

• Semble Strong. The bar is results, checked in person. Semble Seats need people in the room, revenue needs outside wallets, and a wave needs three straight months of kept promises. Before stewards confirm a wave, its builder presents it in person on The Stage.
• Semble Secure. No single person or group can move funds, and no one can buy their way into a vote. Payouts need three of five Trust Protectors, with keys kept offline. Payment addresses are watch-only, and every payout is announced before it moves.
• Semble Safe. No platform holds private keys or anyone's Dash, and support is a statement of conviction, never an investment. Names appear only with consent, and contact details stay private.
• Semble Sound. Every number can be rebuilt from public data: the chain and the check-in log. Every amount comes from one dated policy, every report comes before the next ask, and the rules change in the open when the numbers say they should.

◆ Real or policy. A control is real when an attacker would need a key or a cost they can't hold or pay. It's policy when it works only if people behave. Both have a place, and the spec should say which is which.

Promise	What enforces it	Real or policy
People in the room	The host confirms each check-in	Policy today, because the host is the builder (◆ Hardening 2)
Revenue from outside wallets	A wallet count and a funding flag	Policy: one hop through an exchange hides the source (◆ Hardening 1)
Three of five Trust Protectors	A multisignature address on chain	Real
No platform holds keys	Watch-only addresses	Real
Payouts announced first	A post on the Pulse	Policy
Names only with consent	A display rule	Policy, and a name beside a transaction opens that wallet's history (◆ Hardening 8)
Numbers rebuilt from public data	The chain and the check-in log	Real for the chain; the log becomes real once it's sealed (◆ The seal)

Semble Source

We build in the open by default, and we review the work in person.

• Open source. Builders share their code, and how their work runs, at Share.Waves.Fund when they're ready. Work funded by Semble Source Waves is always shared there, so anyone can learn from it, check it, and build on it.
• Open rules. This spec, every pool policy, and every dated amount are public, and they change in the open.
• In person first. The strongest review is a room. Sembles are where people learn and teach, and The Stage is where builders show their work to the people who'll hold them to it.
• Tested before it's coded. Every rule runs by hand in a real room before it's built into software, and it keeps changing as the numbers come in.

◆ Davara. Testing by hand before code is the right order. No line yet says which hand test has to pass before what gets coded, so ◆ The build order gives every step a done-when.

The platforms

Each one keeps one record, and they all link by project.

A project starts on Semble.CC, gets Verified on Dash Alive, and becomes a Wave. Its TrustBase follows it the whole way: every step dated, every Dash tied to its transaction.

◆ Where it stands, October 27, 2026

Everything in this spec rests on one thing that hasn't happened yet: a room that moves. The build order for Semble.CC starts there (◆ Step 0, after Three movements). Davara's read on the table: five platforms is a lot to keep in step before one room has moved, so Semble.CC's part comes first.

◆ Names, settled and open. The two core roles are Semble Stewards and Wave Guides (August, October 27). The $124 Stewards on Semble.CC and the stewards in this spec are one role: Semble Stewards. Semble Seats now say "paid in Dash" in the opening line, while seats on a Steward's Stage are still sold in US dollars through Stripe under the same name. Semble Certified and Verified are two marks (decided October 27). Semble Certified means the project passed the Semble step in a room: 10 checked-in seats, confirmed in person. Verified is Dash Alive's desk check: real, reachable, not a copy, and signed.

◆ Semble Citizen: the base of the climb

August's own rule, from The Emergent State: "You cannot buy your way in. To hold the passport of the Emergent State, you must participate in at least 2 Semble Sessions." Decided on October 27: show up twice, then $20 a month, the live Semble Citizen membership. (The Emergent State says $22; the live number, $20, is the one decided.)

• The door. Two Semble Sessions, checked in at Trust.Semble.CC, then the $20 membership.
• What a Citizen holds. Their own TrustBase: rooms, check-ins, promises kept, builders brought up, and what they confirmed for others. Their written citizenship, which Semble.CC already asks every Citizen for. And their Dash ID.
• The Dash ID, in two steps. Every Citizen gets a Semble.CC record when they show up the second time, and it can be recovered if they lose a phone. Any Citizen can claim a Dash Platform identity and username the same day. Every builder is walked through it at Stake, when they already hold a Dash address and sign with it. The person holds the keys; Semble.CC links the two records and never holds a key. Sponsors can fund a new Citizen's first top-up.
• What it does for the rest of the spec. One Citizen is one person, however many wallets they use. A Citizen from another project is the outside confirmer at a paid Semble (◆ Hardening 2). Citizens are the people behind Surge presses. A payer who is a Citizen shows on a TrustBase as a verified person; other payers show as payers.
• The climb. Citizen, then builder (Make), then Semble Steward or Wave Guide, the builder's choice.
• It travels. As a Dash Platform record, any Dash app can read it, and any community that runs Sembles by the same rule can make Citizens.
• Private by default. The public sees counts and whatever a Citizen chooses to show. Never their wallet.

The four steps

1. Make. List a project on Semble.CC with a link to something real: code, a site, or a demo. Open projects are public and can host free Semble Seshes.

2. Stake. The builder adds the project's own Dash address and proves it's theirs by signing a message with it, the same check Dash Alive uses. Anyone can send Dash to it: the builder, friends, or stewards. When the address holds 3 Dash, the project goes Live. The 3 Dash stays there until the wave, like a masternode's collateral, and after the wave it's free to use. If the balance drops below 3, the project goes back to Open until it's topped up. Support is a statement of conviction and trust, made in public on the chain. It's final, it isn't an investment, and it carries no promise of return. Backers show on the TrustBase, by name only if they choose.

Why: belief anyone can see on the chain, with no platform holding anyone's money.

3. Semble. A Live project can host paid Sembles and sell Semble Seats at Trust.Semble.CC, priced in Dash at or above the minimum Semble Seat price. Seat payments go to the project's sales address, a second address, so the stake can stay put. The bar is 10 Semble Seats bought by 10 different people and checked in at Trust.Semble.CC, confirmed by the host and counted across all of a project's Sembles. Seats count once the host settles Semble.CC's fee. Then the project lists on Dash Alive (2 DASH to the Pool, as today), passes the Verified review, and joins the next Semble Source Waves proposal.

Why: anyone can pay from ten wallets, but ten people confirmed in the same room is much harder to fake.

Semble Strong: Stand, Support, Steward, Structure, BASE. Five open building blocks inside every Semble. What each one means is for the community to work out together.

4. Wave. A Dash Alive project earns its wave with both of these:

• Three straight months of milestones. One milestone on its TrustBase each month that a second person can check. Miss a month and the count starts over.
• 25 Dash in revenue. Paid through Semble Seats and sales links, from at least 10 different payers, each paying through their own payment request. Payments from the builder, the project's backers, or the project's own addresses don't count.

Then its builder presents it in person on The Stage, and stewards vote to confirm it. The project becomes a Wave, gets its profile on Waves.Fund, and moves to the Dash Waves proposal. The builder chooses to become a Semble Steward or a Wave Guide, and their SWAY helps confirm the next waves.

From there, the Wave plants the next seed. Every wave grant carries one extra stake, 3 Dash today, which the pool sends straight to an Open project the builder believes in, never their own. It's the next builder's start, and the record of who backed whom stays on the TrustBase for good. Every Wave starts another.

Why: three months shows it lasts, and revenue from outside the builder's circle shows people want it.

◆ One number per step

How long one turn takes. Decided October 27: the three months of milestones count from the day a project is Verified on Dash Alive. At best, a first check-in reaches a new builder's first wave grant in 5 cycles, about 152 days. Cycle 0: check in, list, stake, fill a paid Semble to 10 seats (Semble Certified), then Dash Alive and Verified. Cycles 1 to 3: three months of milestones in Semble Source Waves, then The Stage and the vote. Cycle 4: the Dash Waves payout.

Example: Kamora

1. Make. Kamora, a Chicago builder, makes Avanti Black, a Dash-powered music platform. It sells concert tickets in Dash and lets bands and venues sign Dash Wave Contracts: performance agreements paid in Dash, with every term on the record before the first note. She built it to bring transparency and trust to live music. She lists it on Semble.CC with a link to a working demo, and it shows as Open.
2. Stake. She adds her project's address. Two musicians who use Avanti Black and a steward send Dash, and at 3 Dash the project goes Live. She leaves the stake in place.
3. Semble. She hosts a free Sesh for local musicians on getting paid in Dash, then two paid Sembles, one for bands and one for venue owners. Her first attendees pass the second Semble on, and it fills. Fourteen people buy Semble Seats and check in at Trust.Semble.CC. A drummer from her Sesh starts a project of his own, a merch shop that takes Dash. She settles Semble.CC's fee, lists on Dash Alive for 2 DASH, gets Verified, and joins the next Semble Source Waves proposal.
4. Wave. Over three months she promises and delivers, and people at her Sembles confirm each step in person: 5 shows ticketed in Dash, then 12 Dash Wave Contracts, then 30 shows. Venues and bands pay Avanti Black's fees through her sales link, passing 25 Dash from 31 wallets. She shares her contract templates and code at Share.Waves.Fund, presents on The Stage, and stewards confirm her wave. She sets her own ask in the next Dash Waves proposal, with her numbers beside it, plus 3 Dash to seed the next builder she believes in: the drummer from her Sesh. Three months later her people and revenue have both tripled, so her next ask triples too, and every masternode can see why.

◆ Davara. Kamora runs every rule once and shows lineage through the drummer. Her pace is the best the rules allow: about 5 cycles from a first check-in to a first wave grant.

The structure of a Dash Wave

Every Dash Wave shows three things at once:

1. The Story. What is being built on Dash, and why it matters.
2. The Next Move. What's needed now, and how anyone can help. Builders post it at Share.Waves.Fund each month.
3. The TrustBase. Everything that has happened, every step dated and every Dash tied to its transaction. Each entry says how it's known: self-reported, linked, confirmed in person, or verified on chain. Confirmed in person means people checked in at the same Semble confirmed it at Trust.Semble.CC.

A milestone is a promise kept: each month, the Next Move says what comes next, and the TrustBase shows whether it happened. In this spec, a month means one Dash budget cycle, about 30 days.

◆ Davara. The four kinds of knowing (self-reported, linked, confirmed in person, verified on chain) are the best information design in V1. A Next Move needs a date on it, or "kept" can't be graded.

How it grows

Nothing here is won with a pitch. Every project proves itself by moving, and every move feeds the next.

1. A Semble brings people into a room.
2. People pass it on, and the next rooms fill.
3. Some attendees start projects of their own and post their first moves at Share.Waves.Fund.
4. Those projects keep their promises, earn Dash, and become Waves.
5. Each Wave plants the next seed, and every month's numbers go public, so the treasury backs what works.

People are the engine. They're the one resource here that grows the more it's used. Every step lands on a builder's TrustBase and goes wherever they go: promises kept, rooms filled, builders brought up. Money stays the measure. A Semble Seat shows demand, revenue shows value, and every report shows what each treasury Dash did. The numbers are public and live, and they only move when real people do.

◆ The system, mapped (Davara)

What fills, what flows, and which loops run it. The loop names are hers, with each loop's numbers in her atlas.

What fills. Open and Live projects. Dash held at stake addresses. Checked-in Semble Seats per project, counted as distinct people. People who have checked in anywhere. Each project's kept-promise streak, in straight cycles. Outside revenue, in Dash and in distinct payers. Verified projects, Waves and stewards. SWAY. The two pools. TrustBase entries, each marked by how it's known. And masternode trust, counted in net yes votes (the line on November 20 is 332).

What flows. Sponsor Dash moves a project from Open to Live, and spending below 3 moves it back. Seat payments go to the sales address, and check-ins enter the seat count once the host settles the fee. Treasury Dash, up to 6,828 a payday, enters the pools and leaves to projects in two halves; whatever isn't released comes back as a smaller ask. Kept milestones build the streak, and one miss empties it. Waves become stewards, and each wave grant sends 3 Dash to someone else's Open project. Checked-in people become new builders.

The delays. A budget cycle is about 30.3 days. Numbers freeze 7 days before a proposal goes on chain. A wave takes at least 3 cycles. A grant's second half waits up to 1 cycle. A steward's vote pauses after 3 cycles without a milestone. Price adjustment lags 1 to 2 cycles. Founding stewards hold the vote until 10 Waves are active, and today there are none.

What binds today. Rooms that move. Every stock after the room fills only through a checked-in person, so all of them are empty, while the treasury has slack: about 1,635 DASH unclaimed on November 20. Reach sits inside the same constraint, since only web push reaches people on Semble.CC's production.

Where to push first. R1, rooms fill rooms. Every other loop starts from a checked-in person, and R2 to R6 sit behind delays of 3 cycles or more with nothing yet to carry. The handle is already live: Semble.CC credits who brought whom.

The network multiple, on real base rates (an estimate). Of 475 treasury payout addresses, 101 (21%) were paid on 4 or more paydays. If a similar share of Live projects reach a wave, each builder needs to bring about 4.7 new Live builders to hold the multiple at 1, and about 9.4 to reach 2. At the best pace a generation is 5 cycles, so a multiple of 2 grows Waves about fivefold in 12 months. Rooms and passes have to carry that.

Each V1 rule and the rung it pulls. Her leverage ladder runs from M12 (a number) up to M1 (the paradigm).

Davara's test for Movement 1. One paid Semble in Chicago, run by hand, with one person from outside the project confirming the room. Watch the checked-in Semble Seats, and how many people arrive through a pass. What would prove the plan wrong: ten people check in, and none of them passes it to someone who comes to the next room within one cycle. Then the constraint is the pass, and the lever moves there.

Semble Surge

A Surge is the network choosing one thing and moving on it together, for one month.

• One goal. Anyone can propose a Surge with one goal, one number to move, and one month to move it. For example: twenty Chicago venues taking Dash by the end of the month. Stewards can flag a Surge that breaks the rules, the same way they flag projects.
• Pressed together. Everyone who has checked in at a Semble or a Sesh gets one press per Surge, and no one gets more. When the presses pass the threshold, the Surge goes live. If they don't, nothing happens, and that's an honest answer too.
• One at a time. Only one Surge runs at once, so the whole network's attention lands in one place.
• Everyone moves. Everyone who pressed takes one action toward the goal: host a Sesh, pass it to someone new, show up, or build. The number moves live on Share.Waves.Fund.
• It ends with a Semble Synapse. When the month closes, the Surge's results go into the Semble Synapse: the monthly report and recap of every Dash Wave and every Surge, shaped and curated by the community. What moved lands on the TrustBase of everyone who took part. If a Surge needs Dash, it asks through the next proposal like everything else.

What it could become

The first Surges are small on purpose. Over time, the Dash DAO can decide what a Surge becomes: a signal any Dash community can call, from a city or a language group to the merchants of one street; an open record on Dash Platform that any Dash app can read and join; or a way to point the whole network's attention at one shared goal for one month. We start it, and the DAO shapes it.

◆ Davara. One goal for one month points the whole network at one place, which is rung M3, the goal. Presses come from check-ins, and free Sesh check-ins can be farmed, so the outside-confirmer fix (◆ Hardening 2) should cover presses too.

The Semble Stage

The Stage is where builders show their work in person, to the people who'll hold them to it. For now it has one job in this spec: before stewards confirm a wave, its builder presents there, and the people in the room can confirm what they saw at Trust.Semble.CC.

Everything else is an open building block for the Dash DAO and the community to shape:

• What a presentation includes, and how long it runs
• Who's in the room, and whether people elsewhere can watch
• How the room's confirmations count on the TrustBase
• How Stages run across cities, so a builder in one place can present to stewards in another

The first Stage happens in Chicago. The community defines the rest.

◆ Davara. Presenting in person is a cost a shell project can't easily pay. A Stage watched from another city keeps that cost only if a room stays in the rule.

Semble Sesh

A Semble Sesh is a free Semble: a hackathon, a Dash teach-in, a build night. Anyone can host one, with no stake and no tickets, and free Sembles keep working the way they do today. Attendees clock in at Trust.Semble.CC, so every Sesh builds a track record on the TrustBase. Sesh check-ins never count toward Semble Seats or grants, so the bar holds. A Sesh host can raise a stake anytime and start the climb.

Nobody needs money to start. A builder with nothing can host Seshes, keep promises in public, and be seeded by a Wave that believes in them. And every project can end well: one that stops and writes an honest final report keeps its record, and that honesty counts in its builder's favor.

◆ Davara. Free rooms keep the attendee-to-builder loop open to anyone. Sesh check-ins still count for lineage and Surge presses, which is where cheap fakes would go (◆ Hardening 3).

The wave equation

Trust compounds one month at a time, so waves can too.

• Growth multiple. How many times over a Wave's people reached and outside revenue have grown since its last ask, counting whichever grew less, so both have to grow.
• Earned growth. A Dash Wave's next ask is shown beside its growth multiple. Numbers that doubled make a clear case for double the ask, and a Wave that keeps doubling can keep doubling. A first ask is the builder's own call.
• Reset the pace, not the record. After a missed promise, the next ask starts small again, and everything already earned stays on the TrustBase.
• The network's multiple. The network grows on its own when every builder brings up more than one new builder, through their rooms, their passes, and their seeds. At two each, it doubles every generation. Seeds per Wave is the dial: start at one, and raise it once seeded projects reliably earn their waves.

Masternodes see each ask beside its multiple, and they decide.

◆ Davara · The treasury ceiling. People and outside revenue can keep doubling. The treasury ask can only double a few times. A Wave that asks 20 DASH and doubles every cycle asks 2,560 at its 7th doubling, more than all of November 20's unclaimed budget, and 10,240 at its 9th, more than a whole 6,828 payday, about 273 days after its first ask (an example, not a forecast). Passing proposals are paid in order of net yes until the budget runs out, so a passing ask can still go unpaid. After about six doublings, outside revenue and outside capital pay for growth, or each ask is held to a share of the unclaimed budget read at the freeze. (The share is a proposed rule.)

Semble Source Waves and Dash Waves

DashSupport.TEAM submits two proposals to the Dash Treasury, on the same day each month. Semble Source Waves runs as a Tide Pool, the monthly pool that Dash Waves describes. Both proposals publish their full pool policy before taking any Dash, and any Wave can still go to the ballot on its own.

Good standing means a milestone every month and no open flags.

• Why one proposal. Up to 20 small projects share one fee and one clear vote, and masternode owners read one proposal instead of twenty.
• Results first. Numbers freeze and are published 7 days before each proposal goes on chain. Each proposal points home to a page with every project's TrustBase, numbers, and fixed amount.
• Results after. Before the next proposals, DashSupport.TEAM reports what every grant did, and that report opens the Semble Synapse on the Pulse. It leads with three numbers for masternode owners: people reached, new builders started, and outside revenue, each per treasury Dash. Miss a milestone and you sit out the next proposal.
• One project, one proposal. A project is in Semble Source Waves or Dash Waves, never both.
• If a proposal fails. Projects keep their standing and roll into the next month.

How the money moves:

• Each proposal pays into its own pool: a public multi-signature Dash address with a published policy.
• Three of five Trust Protectors sign every payout, with keys kept offline. No group holds more than two keys, and at least one belongs to a masternode owner.
• Half of each grant goes out when the superblock pays, and half when the project's next milestone lands.
• Every payout is announced on the Pulse before any Dash moves.
• Unreleased Dash rolls into the next proposal, which asks the treasury for that much less.

◆ Payments per proposal

Decided October 27. Semble Source Waves goes on chain as one proposal per monthly group, paying across three paydays, which matches its "up to three months". A climbing project rides one vote for its three months, and each month still brings one new group's proposal. Dash Waves stays monthly, because each Wave's ask changes with its growth multiple. Either way, half of each grant goes out on the payday and half on the next milestone, unreleased Dash comes back, and a missed milestone stops a project's releases. That keeps V1's two proposals on the same day each month.

◆ The monthly rhythm

Everything runs on the superblock: one every 16,616 blocks, about 30.3 days. Day 0 is the day a superblock pays. Block times drift, so the days are estimates and the block heights are exact.

(Proposed rule.) A month's milestone counts for that cycle when it's on the TrustBase before the freeze. That gives "a month" in this spec one edge everyone can see.

◆ The seal

V1 freezes the numbers 7 days before each proposal goes on chain. The seal makes that freeze provable.

• At the freeze, DashSupport.TEAM publishes the frozen numbers as one file: every project, its TrustBase link, its numbers, its fixed amount, and the team's budget line.
• The file's SHA-256 hash is its seal. It goes in the proposal's URL, for example https://www.dashsupport.team/waves/2026-12?seal=<hash>.
• A Dash proposal can't be edited once it's on chain, so the chain keeps the seal. Anyone can hash the published file and compare. Change one number and the hash no longer matches.
• After the payday, the grant report grades the sealed file: each project's promised milestone beside what landed, and each payout beside its transaction.

Symphonic Vision ONE's Superblock Scorecard already runs this loop, seal before and grade after, on the whole ballot every month (its seal for November 20 is 7ef3df2a4c0c2046). Its code is in Symphonic Vision ONE's public/api/_scorecard-lib.js, ready to reuse. The seal itself is a real control: a hash on chain that nobody can change. Publishing on time is policy.

SWAY

SWAY is the earned weight of a governance vote on Sembles and Waves. Dash held still is the other.

• Equal start. Every steward starts with the same SWAY.
• Earned, never bought. How SWAY grows is decided in the open. Our starting idea: it grows with the TrustBase, from kept promises and builders brought up, and Dash held or paid never adds to it.
• Capped. SWAY has a ceiling, set in the open, so no one can outweigh the room.

Sway Pay, a payments app built on the Dash blockchain and the open-source Dash Waves protocol, puts both in one place: paying in Dash, and voting with SWAY. Paying never adds SWAY. Details to be announced.

◆ Davara. "Dash held or paid never adds to it" cuts the right link. "Builders brought up" is cheap to fake early in the climb: one 3 DASH moved through ten addresses can take ten shell projects Live, one after another, for about 0.000025 DASH in network fees (an estimate), and a Sesh check-in is free. Proposed: a brought-up builder counts toward SWAY when they reach their wave, and toward lineage when their project reaches 10 seats.

Steward vote

Stewards vote to confirm a wave, after its builder presents it in person on The Stage. They also vote to clear a flag, to raise the bar, and to elect Trust Protectors. Any steward can also flag a project, and a flagged project sits out the next proposal until a vote clears it.

• Who votes. Every Semble Citizen, directly or through a Semble Steward or Wave Guide they delegate to. Until 10 waves are active, the DashSupport.TEAM founding stewards vote.
• Weighted by SWAY and Dash. Each vote carries its voter's SWAY and Dash weight, counted in the Semble house and the Waves house.
• Active means delivering. A steward's wave needs a milestone at least every three months, or their vote pauses until they deliver again.
• In public. Every vote is recorded with a one-line reason.
• Recusal. No one votes on a project they built, backed, seeded, or are paid by.
• Passing. A majority of the leading house's weight, with at least half of that weight voting. The other house can send it back for one cycle.

◆ Davara. Public reasons and recusal are real information. The arithmetic lets few decide: with 10 equal stewards, 5 make the quorum and 3 yes votes pass, so 30% can confirm a wave. Both are fixed as of October 27: Passing now takes a majority of the leading house's weight, and recusal covers seeds, so A can't seed B and then have B confirm A's next seed.

◆ Governance: two houses and the seasons (proposed)

Shaped with August on October 27. It builds on SWAY and the steward vote above and adds Dash weight, without letting money grade results. August changed his SWAY and Steward vote lines to match the same day.

Who votes. Semble Citizens only: two Semble Sessions, then $20 a month. A person can hold many wallets and is still one Citizen.

Two weights for every Citizen.

• SWAY, earned from kept promises, rooms filled and builders brought up. Capped.
• Dash, held still at the Citizen's own address and proved with a signed message. If it moves, the weight ends, the way a masternode's collateral works.
• Holding longer adds weight, from 1 times up to 3 times after a year.
• Dash earned through Semble Seats and sales links paid by Citizens counts double.
• Dash counts only while its holder has checked in at a Semble within the last three cycles.
• Capped per person.

Two houses, one vote. Every vote is counted in both houses.

• The rules, the bar, and the mixes themselves: both houses pass them, then Citizens ratify, one Citizen, one voice.
• Trust Protectors: elected by both houses.
• The month's one Surge and the Semble Synapse: Citizens, one voice each.
• Delegation: any Citizen can hand their SWAY, their Dash weight, or both to a Semble Steward or Wave Guide they trust, and take it back at any time. No one, delegations included, holds more than a set share of either house.

The seasons. A season is three budget cycles, about 91 days. Like Bitcoin's difficulty retarget, each house's mix moves toward what the system needs, in small, bounded steps.

1. The record shows the need. Rooms short of hosts lean the mix toward SWAY. Live builders short of backing for a whole season lean it toward Dash. Kept promises grade last season's calls in each house.
2. The Semble Synapse publishes a proposed step.
3. Citizens confirm it or hold.
4. A house moves at most 10 points a season and always counts between 20% and 80% of each weight. Over six seasons the houses can trade places, if the evidence keeps pointing that way.

Roles each season. A builder who earns a wave chooses Semble Steward or Wave Guide first, can switch each season, and writes what the role means to them, the way Citizens write their citizenship. Roles are jobs; weight comes from SWAY and Dash.

Crews and pools. Any crew, team or Wave pool can run its own mix for its own decisions, inside the network's bounds. The Synapse compares which mixes keep promises, and that evidence feeds the next season.

Sway Pay. Where each person sees their two weights, their role this season, their delegations and the season's proposed step, and votes. Its details stay August's.

What never moves without both houses and a Citizens supermajority. Only Citizens vote. Recusal: built, backed, seeded, or paid by. The caps. Every house counts both weights. Masternodes vote on every treasury proposal.

How it starts. The first season runs by hand at the starting mix. The retarget turns on once the record has rooms that moved to read.

Borrowed from what works. Two houses with a check: the Optimism Collective (Token House and Citizens' House) and Lido's dual governance. Lock longer, vote heavier, and delegation: Polkadot OpenGov. A capital vote over a treasury: Dash masternodes. A bounded retarget: Bitcoin's difficulty adjustment. Rules nested inside rules: Elinor Ostrom's work on commons.

August's lines, decided October 27. Changed to match: Semble Secure ("no one can buy their way into a vote"), SWAY's first line, Who votes, Weighted by SWAY and Dash, Passing, and the answer to "Can Dash buy a vote here?". Kept as written, because they stay true: "Dash held or paid never adds to it." and "Paying never adds SWAY." Dash adds its own weight, and SWAY itself is never bought.

Roles

Roles are jobs, not ranks, and no group moves money alone.

A mover's reward is a portion of what arrives through the pass, so routing your own Dash through it never pays.

◆ Trust Protectors, now and later. The first terms start at no more than two keys per group (August, October 27). The goal, as the community grows closer and better at deciding together: five or more groups, and no group holding more than one key. Each step toward it is a rule change, made in the open.

Price adjustment

Every Dash amount lives in one dated, published policy, the way Dash Alive's amounts do today, and a payment request keeps the amount it was created with. The policy moves in steps:

• When the 30-day average Dash price doubles from the launch baseline, every amount halves. When it halves, every amount doubles.
• New amounts start the next month.
• The bar moves up or down only through both houses and the Citizens, with the share of projects clearing it published beside every change.

This covers the stake, the minimum Semble Seat price, the listing fee, and the revenue bar. The bar stays the same in real-world terms, whatever Dash's price does.

◆ Which price. The dated policy should name its price source, so anyone can recompute the 30-day average: for example, the daily median of three named exchanges' DASH/USD closes. The halving and doubling steps then fire on a number everyone can check. (Proposed; the source is August's choice.)

◆ The language of the bar. The spec keeps saying "raise the bar": that's the stance (August, October 27). In practice the bar moves up or down with the world, through both houses and the Citizens.

◆ Davara. Between steps, the real cost of the 3 Dash stake can differ about 3.9 times (price at 1.99 against 0.51 of the baseline). Steps at 1.5 times, or a monthly recompute, would keep the bar steadier.

How we make money

Fees fund the platforms, and the Pool stays for builders. Nothing mixes, and every Dash is on a public ledger.

◆ Capital (Davara, checked against the chain)

Support stays a statement of conviction, never an investment. Every move here keeps that line.

1. Ask small, inside the room, with the call sealed. November 20 has about 1,635 DASH unclaimed and no proposal from DashSupport.TEAM or Semble.CC. The drafted DashSupportTeam-Nov2026 asks 128, 7.8% of that room, against a line of 332 net yes and a 1 DASH fee. When to submit is August's call.
2. Lead every report with new builders per treasury Dash. New payout addresses fell from 135 in 2018 to 19 a year from 2023 to 2025, and 20 in 2026 to October, down 86%. A pool that brought 20 new builders a year would match the treasury's whole recent yearly intake (an estimate, since an address isn't a project).
3. Fund the months where lines stop. 38% of payout addresses were paid once, and 79% on three paydays or fewer. Semble Source Waves funds "up to three months", the same stretch where most lines have ended.
4. Bring outside Dash in as purchases. Seats, sales links, Ensembles, and fees from venues and bands are outside capital arriving as payment. That money keeps growing after the treasury ceiling binds.
5. Let Sponsors fund more seeds, in public, with no return. A published pool policy could take Sponsor Dash for extra seeds to Open projects, raising the seed dial without treasury Dash. It's final, carries no promise of return, and stays apart from Wave Shares in every record.
6. One record for both kinds of capital. Semble's investor prospectus asks for the same evidence before any investor conversation: invitations, attendance, repeat meetings, paid renewal. A TrustBase anyone can rebuild from the chain is that evidence, for a masternode and for an investor alike.

Under all of it is one base rate: ten addresses received 66% of all treasury DASH. Under a ranked budget, lines that already win tend to keep winning. One proposal carrying 20 small projects is how builders who couldn't win alone get in.

Wave Shares

Support stays a statement of conviction, never an investment. Wave Shares are a separate, future layer for equity in Waves.

• MyWaveShares (MWS). The building blocks of equity in one Wave: who holds how much of it, and how they earned it.
• DashWaveShares (DWS). A future proposal to the Dash DAO for one shared way to measure and store Wave equity on Dash, whether as a token, a variable, or another building block.

Our first thoughts, offered to the community to shape:

• Every share points to the TrustBase, so anyone can see how it was earned.
• Shares live in an open format any Dash app can read, such as a Dash Platform data contract.
• Equity is regulated, so this layer is built with qualified legal partners before any share is issued.
• The structure, the format, and the foundation are decided with the whole Dash DAO, in the open.

Questions to bring to the Dash DAO:

• Should DWS be a token, a Dash Platform record, or something else?
• Who can hold Wave Shares, and how are they earned?
• How should they sit beside support, which is never an investment?

◆ Davara. Keeping equity as its own layer, with lawyers first, protects the support line. Any hint that a stake turns into shares later would break it.

What the Dash community will ask

◆ Hardening: what stops what (Davara's red team)

A defense is real when the attacker needs a key or a cost they can't hold or pay. It's policy when it works only if people behave. V1's answer "Faking is costly" holds for check-ins once a second confirmer exists. Every fix below is proposed; none changes a V1 line until August says so. Network fees are estimates, at 0.00001 DASH per kB.

1. Fake outside revenue. Hits "from at least 10 different wallets." Today: policy. The flag catches a payer funded straight from the project's addresses, and one hop through an exchange hides it. Cost to fake: sending 25 DASH from 10 fresh wallets to your own sales address costs about 0.00005 DASH in fees, because the 25 comes back. Sales links carry no fee. Through Semble Seats the 5% fee makes it 1.25 DASH. The same rule also miscounts honest buyers: ten people paying from one exchange can show as one address. Fix: count payers by payment request, and count toward the 25 only payers who checked in at a Semble or signed a Dash Wave Contract.
2. Relayed check-ins. Hits "confirmed by the host." Today: policy, because the host is the builder. Cost to fake: the seat money comes back to the faker's sales address, so ten fake seats cost the 5% fee, which is half of one seat price. Fix: seats count only when one person from outside the project, checked in at the same Semble, also confirms the room.
3. Shell builders on a rented stake. Hits lineage at "takes a project Live" and SWAY from "builders brought up." Today: policy, because Live is read at one moment. Cost to fake: one 3 DASH moved through ten addresses takes ten shells Live, one after another, for about 0.000025 DASH, and a Sesh check-in is free. Fix: Live means the lowest balance over 7 days was 3 or more; lineage counts at 10 seats; SWAY counts a brought-up builder at their wave.
4. Steward capture. Hits "A simple majority of SWAY, with at least half of active stewards voting." Today: policy, with public records. Cost to fake: with 10 equal stewards, 3 yes votes can pass. Fix: done on October 27. Passing takes a majority of the leading house's weight, and recusal covers seeds.
5. Ladder pulling. Hit "Stewards can vote to raise the bar, never to lower it." Those who climbed at the old bar could raise it behind them with one vote. Fixed October 27: the bar now moves up or down only through both houses and the Citizens, with the share of projects clearing it published beside every change.
6. The treasury ceiling. Hits "Each Wave's own ask." Today: real information, no guarantee. A passing ask goes unpaid when proposals with more net yes fill the 6,828 first. October paid 6 proposals where every other 2026 payday paid 14 or 15, so the room moves month to month. Fix: read the unclaimed budget at the freeze, keep both asks inside it, and seal the call (◆ The seal).
7. Vote fatigue. Hits two proposals "on the same day each month." Partly fixed October 27: a Semble Source Waves group now rides one vote for three paydays (◆ Payments per proposal). Before that: no defense. Each must reach the line every month (332 on November 20), and the most-voted proposal this cycle drew 1,153 net yes. Three long lines end on November 20. Fix: proposals with 2 or 3 payments, since masternodes can withdraw a yes in any month a report fails.
8. Linking names to wallets. Hits "every Dash tied to its transaction", beside named backers and dated check-ins. Today: policy. A consented name beside one transaction opens that person's address history and balance, and a check-in adds where they were and when. "A wallet counts once per project" means the platform holds a map of people to addresses. Fix: publish transactions and counts, never a person beside a transaction, and run the once-per-project check on a private salted hash.
9. Lost keys. Hits "Three of five Trust Protectors." Today: real. Two lost keys are survivable; a third freezes the pool. A builder who loses a project key loses the stake. Fix: each Trust Protector signs a dated message on the Pulse every cycle, so a lost key shows within 30 days, and each new term moves the pool to a fresh multisignature address.
10. Price shocks. Hits Price adjustment's halving and doubling. Today: partly real, since "a payment request keeps the amount it was created with." Cost: between steps, the stake's real cost can differ about 3.9 times, and a fall makes stakes and faked revenue cheaper. Fix: steps at 1.5 times, or a monthly recompute.

Three movements

Each movement builds on what's already live.

Movement 1: Semble Seats and check-in (build now)

Seed it by hand first. Run one paid Semble in Chicago with a Dash QR code at the door and a paper check-in list, and post its TrustBase by hand. It's also Semble.CC's own next move as a founding Dash Wave. Then build only what that first night proves you need.

• Project Dash addresses and sales addresses, with ownership proved by a signed message.
• The stake: read the project's address from the chain, showing Open below 3 Dash and Live at 3 or more. Warn builders that spending from it can drop it below 3, because most wallets send change to a new address.
• Trust.Semble.CC, the door: one payment request per Semble Seat, with a unique exact amount paid to the sales address, valid for 30 minutes and counted once InstantSend locks it. At the Semble, each attendee clocks in with their seat's signed, single-use code, and the host confirms. Sesh attendees clock in the same way, without paying. A payer counts once per project. Reuse Dash Alive's chain-reading code.
• In-person confirmations: people checked in at a Semble can confirm a milestone they saw shown there, and it lands on the TrustBase as confirmed in person.
• Semble.CC's fee: after each Semble, the host settles it in one payment, and those seats count.
• Sales links that count toward revenue, with an automatic flag when a payer was funded from the project's own addresses.
• The TrustBase: status, stake, Semble Seats, check-ins, revenue, and milestones, dated and public.
• A button to list on Dash Alive that carries the project's record to DashSupport.TEAM.
• Lineage: when someone who checked in at a Semble later takes a project Live, both TrustBases show it, and it counts as a new builder.

Movement 2: Funding on DashSupport.TEAM

• The Semble Source Waves proposal and its Tide Pool policy: eligibility, frozen numbers, the proposal itself, and its report in the Semble Synapse.
• Steward votes weighted by SWAY, flags, and wave presentations on The Stage.
• Trust Protectors and the pools, with milestone releases.
• Passes for Sembles and projects, with mover rewards paid when the host or builder settles.
• The dated amounts policy, with price adjustment.
• The Semble Synapse: the monthly report and recap of every Dash Wave and every Surge, opened by the grant report and curated with the community.

Movement 3: Waves on Waves.Fund

• Wave profiles built from the Story, the Next Move, and the TrustBase, linked with the Dash Waves page on DashSupport.TEAM.
• Share.Waves.Fund, for posting each Next Move, new Sembles, and Semble Source code.
• The Dash Waves proposal and the wave equation.
• Opening the DashWaveShares conversation with the Dash DAO.
• Semble Surge: proposals, presses, and the live counter on Share.Waves.Fund.

◆ The build order for Semble.CC

Semble.CC applies this spec first. The order follows V1's own rule: seed it by hand, then build only what the first night proves you need. Each step ends with a check that says it's done.

Step 0: a room moves. Semble.CC's own one number is rooms that moved, per week, and no Dash feature helps until it's above zero.

• Decide whether new rooms move at 3 or 5 while the city is young (Semble's docs/NEXT.md, decision 2). The first room asked for 5.
• Put a text or email key on production, so people hear when their room moves.
• Run one room a week at one time and place, using Again next week.
• Done when one room has moved in public and its record shows who was there.

Step 1: the first paid Semble, by hand. Movement 1's first paragraph: a Dash QR code at the door, a paper check-in list, the TrustBase posted by hand. Add Davara's test: one person from outside the project confirms the room. Write down everything that was slow or confusing at the door. That list decides what gets built next.

• Done when one paid Semble's TrustBase is public, with every payment tied to its transaction.

Step 2: the project record. Today a project is a link on a Semble. Movement 1 needs a project of its own: name, link, builder, status (Open, Live, Dash Alive, Wave), stake address, and sales address. Ownership of each address is proved with a signed message, using Dash Alive's verifier. Store it the way Semble.CC stores everything: create-only keys in Vercel Blob, a versioned document (doc/project/<id>/<seq>.json), and facts as key names.

• Done when a builder can list a project, add both addresses, sign for both, and see Open.

Step 3: the stake, read from the chain. Open below 3 Dash, Live at 3 or more, read with Dash Alive's chain-reading code. Read it again before anything that depends on it: a seat sale, a listing, a wave. If August takes Hardening 3, Live reads the lowest balance over 7 days. Show the warning about wallet change addresses before a builder spends.

• Done when, on a preview, 3 Dash sent to a test address turns it Live and moving it out turns it Open.

Step 4: Trust.Semble.CC, the door. One payment request per seat: a unique exact amount to the sales address, valid for 30 minutes, counted once InstantSend locks it. Each seat gets a signed, single-use code, shown as a QR code on the attendee's phone, and the host confirms. Sesh attendees clock in the same way without paying. A wallet counts once per project.

• Done when, on a preview, ten test seats are paid, locked and checked in once each, and a second use of any code is refused.

Step 5: the TrustBase page. Status, stake, seats, check-ins, revenue and milestones, each dated, each Dash linked to its transaction, and each entry marked self-reported, linked, confirmed in person, or verified on chain. Each Next Move carries a date, so "kept" can be graded. Semble Certified shows once the 10 seats are confirmed in person; Verified shows once Dash Alive's review passes.

• Done when every number on the page can be rebuilt from the chain and the check-in log by a script anyone can run.

Step 6: carry it to Dash Alive. The button that lists the project on Dash Alive with its record.

What holds the whole way:

• No private key, seed or extended private key ever touches Semble.CC. Every address is watch-only.
• A person's name never appears beside a wallet address or a transaction unless that person chose it, and the choice says plainly that it links their name to that wallet on a public chain.
• Semble.CC's place privacy rules (docs/PLACE-PRIVACY.md) hold for paid Sembles exactly as for free ones.
• No visitor counting. Every count on a TrustBase is something a person did on purpose: paid, checked in, confirmed.
• Every name on screen comes from this spec or from August. Where a screen needs a sentence, the builder leaves the slot empty and says it's waiting for him.
• Each step gets a check in Semble.CC's suites: CORE on previews, and read-only SMOKE checks on live. Nothing that writes runs against production.
• When Insight answers with a challenge page, never work around it. Read the chain another way (a node or DAPI).

Design

Clean, modern sans-serif type only: Geist, Sora, Inter, or IBM Plex. Every project shows the four steps as a progress bar, with one clear line on what it needs next.

◆ On Semble.CC. Semble.CC already uses three of these faces, each with a job (docs/DESIGN.md): Sora for titles, Geist for reading, and IBM Plex Mono for labels, counts and addresses. Dash amounts, addresses and transaction ids belong in Plex Mono. The four-step bar follows the same design doc: squircles, one lit press per page, and nothing that competes with the room. Davara adds: the bar should show the streak too, since a reset matters most.

Open decisions

• The minimum Semble Seat price
• Semble.CC's fee on each Semble Seat (suggested 5%)
• DashSupport.TEAM's budget line per proposal (suggested 10%)
• The Semble Source Waves grant size, and the cap per proposal (suggested 20 projects)
• The founding stewards, the first five Trust Protectors, and their terms
• SWAY: how it's earned, and its cap
• The baseline Dash price (suggested: the 30-day average on launch day)
• The Dash Alive listing fee: keep today's 2 DASH, or raise it to 5 as discussed
• A lawyer's review of the support terms, fees, payouts, and Wave Shares before launch
• The date, place, and project for the first Semble
• Seeds per Wave (one to start)
• Mover rewards
• MyWaveShares and DashWaveShares, shaped with the Dash DAO
• Semble Surge: the threshold, how often Surges can run, and what the Dash DAO builds it into
• The Semble Stage: its format and how it grows, shaped with the Dash DAO
• The Semble Synapse: who curates it, and how the community shapes it
• Semble Strong: what Stand, Support, Steward, Structure, and BASE each mean, defined with the community

◆ More open decisions, from V2

Davara's read: the date and place of the first paid Semble outranks everything below.

• Whether new rooms move at 3 or 5 while the city is young
• A text or email key on Semble.CC's production
• The names still open: Semble Seats on a Stage (dollars) beside Semble Seats at a paid Semble (Dash), and Semble Certified beside Verified
• The governance numbers: the starting mixes, the 1 to 3 times holding ladder, the caps, and the step size (◆ Governance)
• When a month's milestone counts (proposed: on the TrustBase before the freeze)
• The outside confirmer at a paid Semble (proposed: a Semble Citizen from another project)
• The price source, and the size of the price step
• The seal in each proposal's URL
• Each fix in ◆ Hardening

◆ Close in view

• November 20, block 2,575,480. Votes close about November 17. DashSupportTeam-Nov2026 is drafted and still off chain, and August decides in the next few days whether it goes in this cycle. A proposal counts votes from about a day after it's on chain, so submitting by about November 3 leaves roughly two weeks of votes against a line of 332 net yes, in a month with about 1,635 DASH of room.
• About December 20, block 2,592,096. The first payday a proposal submitted right after November 20 can reach. Three of November's five lines end on November 20, so December's room depends on who renews.
• The second room. The first room's record offers Try it again a week on.
• Semble.CC on Dash Alive. The listing reads best with a room that moved behind it.
• Dash Platform. V1 already points there for the Surge record and DashWaveShares. The TrustBase can follow as a data contract once its shape settles. (Proposed.)

◆ For August

Decided on October 27

Quoted lines are August's. Each change below is made in V2; nothing else of his was touched.

1. The opening line: yes. "Semble Seats" became "Semble Seats paid in Dash", because Semble.CC already sells Semble Seats in US dollars on a Steward's Stage.
2. "Wave Steward": no. August: there are two core roles, Semble Stewards and Wave Guides. No Wave Stewards, no Semble Guides. The $124 Stewards on Semble.CC and the stewards here are one role.
3. When stewards vote: yes. "Stewards vote at one point in the climb" now names all four votes: confirming a wave, clearing a flag, raising the bar, and electing Trust Protectors.
4. Trust Protector groups: two per group, for now. Roles now reads "no more than two from any one group", matching How the money moves. The goal is five or more groups with one key each (◆ Trust Protectors, now and later).
5. Wallets: payers. August left it to Claude. Revenue counts payers, each paying through their own payment request, and "A payer counts once per project." Nobody is stopped from using many wallets; Semble Citizenship is where one person counts as one.
6. Recusal: seeded is added. August left it to Claude. "No one votes on a project they built, backed, seeded, or are paid by." Without it, seeds could form vote rings.
7. Semble Strong, used twice: kept as written. August: these are frames and mindsets, and the community will shape them over time.
8. After a wave: the builder chooses. "The builder becomes a steward who confirms the next waves" now reads "The builder chooses to become a Semble Steward or a Wave Guide, and their SWAY helps confirm the next waves."

Also decided: Semble Citizenship is two Semble Sessions, then $20 a month, and the Dash ID comes in two steps (◆ Semble Citizen). The seasons design is written in as a proposed section, with Dash earned from Citizens counting double (◆ Governance).

1. The governance lines. Changed to match the two houses: Semble Secure ("no one can buy their way into a vote"), SWAY's first line, Who votes, Weighted by SWAY and Dash, Passing, and the answer to "Can Dash buy a vote here?". Kept as written: "Dash held or paid never adds to it."

The open questions, answered on October 27

1. Semble Certified and Verified: two marks. Semble Certified is the Semble step passed in a room (10 checked-in seats, confirmed in person). Verified is Dash Alive's desk check.
2. The bar moves both ways. "Stewards can vote to raise the bar, never to lower it." now reads "The bar moves up or down only through both houses and the Citizens, with the share of projects clearing it published beside every change." The spec's language stays "raise the bar".
3. The three months count from Dash Alive. One turn is about 5 cycles, about 152 days.
4. Payments per proposal: split. Semble Source Waves runs one 3-payment proposal per monthly group; Dash Waves stays monthly (◆ Payments per proposal).
5. Davara's lines stay in the spec, marked as hers and never site copy.

Still open

1. Whether DashSupportTeam-Nov2026 goes on chain for November 20. August decides in the next few days. Submitting by about November 3 leaves roughly two weeks of votes before they close around November 17; otherwise it goes in right after November 20 for the December 20 payday.
2. The governance numbers: the starting mixes, the 1 to 3 times holding ladder, the caps, and the step size (◆ Governance).

Show up. Keep your word. Carry It On.

#BuildStrong #BuildBRAVE #MoveWAVES #SembleWAVES #DashBRAVE