What is Dash?

Learning objectives

By the end of this lesson, you will be able to:

• recognize what a blockchain gives you as a developer — a shared, tamper-evident record no single company owns;
• trace how value moves through transactions, keys, and addresses;
• explain why decentralization changes where you choose to build an app;
• describe what a masternode makes possible; and
• tell Dash Core apart from Dash Platform.

Dash is digital cash with a second job. Before either job makes sense, you need the one idea both are built on: a blockchain. This lesson starts there and then shows what makes Dash different.

A blockchain, in terms you already know

If you have worked with a database, a log file, or a Git history, you already understand the shape of a blockchain: an append-only log made of blocks, where each block is a batch of transactions the network has agreed to add.

Two properties follow from how the blocks are linked. First, each block carries the hash — a short, fixed-size fingerprint of its contents — of the block before it. Chaining blocks by hash makes the log tamper-evident: change anything in an earlier block and every later block's fingerprint no longer lines up, so rewriting the past means redoing everything after it. Second, no single computer owns the log. Copies live on many independent nodes around the world, and the network follows one set of rules to agree on which copy is correct, with no central administrator choosing winners.

From your side, it behaves like a database you can trust but nobody owns. The next section shows what actually moves through it.

Transactions, keys, and addresses

There is no account with a balance you add to and subtract from. Value is a chain of ownership. A transaction spends the outputs of earlier transactions and creates new outputs for the next one: each output records an amount and the condition for spending it later. An output can be spent exactly once — a second attempt to spend the same output is rejected as a double spend (two payments trying to use the same money).

Two related numbers let you spend an output:

• A private key — a secret 256-bit number that proves you may spend the output. Lose it and the money is gone; there is no password reset.
• A public key — a number derived from the private key, which others use to check your signature. The relationship is one-way: the public key comes from the private key, but the private key cannot be recovered from the public key.

You do not hand out the public key. You hand out an address: a short string derived from the public key (the usual form hashes it and adds a checksum). An address is enough for someone to pay you while revealing nothing about the private key that controls the money.

Dash's amount is measured the way dollars are: in whole units and their smallest subdivision. One DASH equals 100,000,000 duffs, the smallest unit — the same idea as cents in a dollar.

Why decentralization matters to a builder

Everything so far has a practical payoff. When you build an app on a centralized platform, you are renting someone else's infrastructure: their servers, their uptime policy, their approval. When you build on a decentralized network, the deal changes:

• No server to run or secure. The network already runs the storage. You write application code and talk to the network; you do not operate the database or its backups.
• No single point of failure. Because copies live on many independent nodes, one computer — or one company — going away does not take your app's data with it.
• Nobody can shut it down. There is no central account to freeze and no company that can pull the plug or censor a record.
• No single backend to depend on. The network is the backend. Your app keeps working as long as the network does, not as long as one vendor stays in business.

Decentralization is a trade-off, not a free lunch — it changes how you think about upgrades, privacy, and who is responsible for a mistake. But the reason builders choose it is the same in every case: the app belongs to its users, not to a host.

Dash as money

Dash is digital cash: a cryptocurrency built for payments. It began as a modification of Bitcoin's software, and it keeps Bitcoin's core idea — money that moves peer to peer with no bank in the middle — while adding the speed and services a payment network needs. Unlike fiat currency, no government issues it and no central bank backs it; the network itself issues and settles it.

A few numbers orient you. Dash's blocks arrive roughly every 2.6 minutes, and new coins are issued as a reward for proposing blocks. The network launched with no premine and no ICO — no founder stash and no presale.

Masternodes make the rest possible

Bitcoin's network is a single tier: every computer does roughly the same job. Dash adds a second tier of specially equipped servers called masternodes.

A masternode is a server that deposits 1,000 DASH as collateral and, in return, does extra work for the network. The collateral is the point: because an operator has real money at stake, the network can trust these servers with jobs that need more than blindly relaying transactions, and a misbehaving operator stands to lose more than they could gain.

That second tier is what makes the rest of Dash possible. Masternodes provide the extra services that turn "cryptocurrency" into "digital cash you can actually spend": near-instant payment confirmation, an extra layer of security for the chain, and the self-governing, self-funded process that pays for the network's own development.

Payments confirm in about a second

On most blockchains, "the payment went through" means "wait until enough blocks pile on top that reversing it becomes impractical." With Dash's 2.6-minute blocks, naive confirmation would mean waiting several minutes before you trust that money arrived.

Dash is different: a payment confirms in about a second. The masternode tier vouches for each transaction as soon as it is broadcast, so in roughly the time it takes to swipe a card, a seller can treat a Dash payment as settled instead of waiting for several blocks to be mined.

For a builder, that one-second difference is the difference between a usable checkout and a "please wait a few minutes" screen. You get cash-like speed — the way a banknote or a card payment feels instant — without a middleman holding the funds.

One network, two jobs

Everything so far describes money. But Dash runs two jobs on one network, and the second is why this course exists:

• Dash Core is the money layer — the layer-1 blockchain we have been describing. It settles Dash payments and carries the currency.
• Dash Platform is the application-data layer. Instead of just money, it stores and serves the data behind real applications, and it runs on the same masternode tier.

Platform has two main pieces you will meet throughout this course:

• Drive is Platform's storage. It keeps and validates the network's application data.
• DAPI is Platform's API. Your app reads and writes to Platform through it instead of running its own node.

The two jobs come together on the masternodes that run both. Evonodes are masternodes with a larger 4,000 DASH deposit that, in addition to Core's services, host Dash Platform. Regular masternodes serve Core only.

Checkpoint

Pass the quiz to complete the lesson.

What you accomplished

You can now read a blockchain the way you read any append-only, tamper-evident store — and see what makes Dash's version different: digital cash with about-a-second payment confirmation, enabled by a second tier of collateralized masternodes, and a second job, Dash Platform, that turns the same network into an application platform. The next lesson zooms in on that second job to show what you can actually build with it.