Documentação Dash¶

Dash é uma criptomoeda peer-to-peer de código aberto com foco no setor de pagamentos. Dash oferece uma forma de dinheiro que é portátil, barata, divisível e rápida. Ele pode ser gasto on-line com segurança e pessoalmente, com taxas mínimas de transação. Baseado no projeto Bitcoin, o Dash pretende ser o sistema de pagamentos mais amigável e escalável do mundo. Além do conjunto de recursos do Bitcoin, o Dash atualmente também oferece transações instantâneas (InstantSend), transações privadas (PrivateSend) e opera um modelo autônomo e autofinanciado que permite que a rede Dash pague indivíduos e empresas para o trabalho que agrega valor à rede. Isto sistema descentralizado de governança e orçamentação faz dele uma das primeiras organizações autônomas descentralizadas (DAO).

Se você é novo em criptomoedas, a mudança mais importante para entender é que as transações ocorrem diretamente entre duas partes, sem qualquer autoridade central para facilitar a transação. Isso também significa que você é responsável por sua própria segurança - não há banco ou empresa de cartão de crédito para reverter uma transação se seus fundos forem roubados ou perdidos. Nesse sentido, é semelhante a dinheiro ou ouro, mas a criptomoeda pode ser gasta local e internacionalmente com a mesma facilidade, se você tiver certeza de que está enviando fundos para o destino certo. Por esses motivos, a documentação da Dash tem um forte foco na segurança e na compreensão dos conceitos e recursos que orientam o ecossistema Dash. Os vídeos, links e documentação abaixo podem ajudá-lo a começar ou usar o sumário à esquerda para encontrar um tópico específico de interesse.

Índice¶

O que é o Dash?¶

Dash aims to be the most user-friendly and scalable payments-focused cryptocurrency in the world. The Dash network features instant transaction confirmation, double spend protection, optional privacy equal to that of physical cash, a self-governing, self-funding model driven by incentivized full nodes and a clear roadmap for on-chain scaling to up to 400MB blocks using custom-developed open source hardware. While Dash is based on Bitcoin and compatible with many key components of the Bitcoin ecosystem, its two-tier network structure offers significant improvements in transaction speed, privacy and governance. This section of the documentation describes these and many more key features that set Dash apart in the blockchain economy.

Check out the official Dash website to learn how individuals and businesses can use Dash. The videos, links and documentation collected here can help you get started, or use the table of contents on the left to find a specific topic of interest. New users may be interested in getting started with an appropriate wallet, learning about how to buy Dash and where to spend Dash, learning about safety or joining one of the many Dash community sites.

Dash Videos¶

Escola Dash¶

Escola Dash é uma série de vídeos em seis partes produzida por Amanda B. Johnson. Ela explica Dash desde o nível de um iniciante até as descrições dos recursos mais avançados.

Dash 101¶

Dash 101 é uma série de vídeos de oito partes produzido por Aaron Koenig. Ele cobre recursos e funções exclusivas disponíveis apenas na rede do Dash e está disponível em Ingles, Frances, Alemão, Espanhol e Russo.

Whitepaper¶

O Whitepaper do Dash descreve a proposta de valor exclusiva e as principais inovações no Dash, de uma perspectiva acadêmica e teórica. É um documento vivo mantido como um wiki do GitHub, recebendo atualizações contínuas e traduções frequentes da comunidade, à medida que novos recursos são implementados. Vários outros documentos técnicos descrevendo características particulares com detalhes adicionais e (por razões históricas) o documento técnico original está disponível para download como arquivos PDF.

Cronograma¶

The Dash Roadmap sets out delivery milestones for future releases of Dash and includes specific technical details describing how the development team plans to realise each challenge.

Dash Roadmap

Características¶

Especificações¶

Primeiro bloco minerado às 23:00 horas EST, em 18 de janeiro de 2014
Sem premine
Algoritmo X11, mineração CPU/GPU/ASIC disponível
Tempo de bloco 2,6 minutos, blocos de 2MB, ~56 transações por segundo
Recompensa por bloco diminui em 7,14% ao ano
Algoritmo de ajuste de dificuldade Dark Gravity Wave
Entre 17,74M e 18,92M o fornecimento total de moedas
Rede descentralizada de masternode
Superior privacy using PrivateSend
Transações instantâneas usando o InstantSend
Protection against blockchain reorganization events (commonly called 51% attacks) using ChainLocks
Governança Descentralizada Por Blockchain permite que os proprietários de masternode votem em propostas de orçamento e decisões que afetam Dash

Masternodes¶

Além das recompensas tradicionais da Proof of Work (PoW) para o Dash de mineração, os usuários também são recompensados por executar e manter servidores especiais chamados de masternodes. Graças a essa inovadora rede de dois níveis, o Dash pode oferecer recursos inovadores de maneira confiável e descentralizada. Os Masternodes são usados para impulsionar o PrivateSend, o InstantSend e o sistema de governança e tesouraria. Os usuários são recompensados por executar masternodes; 45% da recompensa do bloco é alocada para pagar a rede do masternode. Você pode ver guias práticos sobre todos os tópicos relacionados a masternodes here.

Masternodes permitem os seguintes serviços:

InstantSend permite transações quase instantâneas. As transações do Dash InstantSend são totalmente confirmadas em dois segundos.
PrivateSend gives financial privacy through a decentralized implementation of CoinJoin.
ChainLocks, which protects the blockchain against 51% mining attacks by signing blocks as they are mined.
Governance and Treasury allows stakeholders in Dash to determine the direction of the project and devotes 10% of the block reward to development of the project and ecosystem.
O Dash Evolution tornará o uso da criptomoeda tão fácil quanto usar o PayPal.

Masternode owners must have possession of 1000 DASH, which they prove by signing a message included in a special transaction written to the blockchain. The Dash can be moved or spent at any time, but doing so will cause the masternode to fall out of queue and stop earning rewards. Masternode users are also given voting rights on proposals. Each masternode has one vote and this vote can be used on budget proposals or important decisions that affect Dash.

Masternodes cost money and effort to host so they are paid a percentage of the block reward as an incentive. Because only one masternode is paid in each block, the frequency of the payment can vary, as well as the value of the Dash paid out. This tool shows a live calculation of masternode earnings. These rewards decrease by 7% each year, together with the block reward. There is also the possibility for masternodes to earn money from fees in the future.

PrivateSend¶

PrivateSend gives you true financial privacy by obscuring the origins of your funds. All the Dash in your wallet is comprised of different «inputs», which you can think of as separate, discrete coins. PrivateSend uses an innovative process to mix your inputs with the inputs of at least two other people in a single transaction, so the value in Dash never leaves your wallet. You retain control of your money at all times.

Você pode ver um guia prático para usar o PrivateSend aqui.

O processo PrivateSend funciona assim:

PrivateSend begins by breaking your transaction inputs down into standard denominations. These denominations are 0.001, 0.01, 0.1, 1 and 10 DASH – much like the paper money you use every day.
Sua carteira envia solicitações para os nós especialmente configurados na rede, chamados «masternodes». Estes masternodes são informados então que você está interessado em misturar uma certa denominação. Nenhuma informação identificável é enviada para os masternodes, então eles nunca sabem «quem» você é.
Quando duas outras pessoas enviam mensagens semelhantes, indicando que desejam misturar a mesma denominação, começa uma sessão de mistura. Sua carteira paga essa denominação diretamente para si mesma, mas em um endereço diferente (chamado de endereço de alteração).
Your wallet must repeat this process a number of times with each denomination. Each time the process is completed, it’s called a «round». Each round of PrivateSend makes it exponentially more difficult to determine where your funds originated. The user may choose between 1-16 rounds of mixing.
This mixing process happens in the background without any intervention on your part. When you wish to make a private transaction, your funds will be ready to spend. No additional waiting is required.

Observe que as transações do PrivateSend serão arredondadas para que todas as entradas de transação sejam gastas. Qualquer excesso de Dash será gasto na taxa de transação.

IMPORTANTE: Sua carteira contém apenas 1000 desses «endereços de alteração». Toda vez que um evento de mixagem acontece, um de seus endereços é usado. Uma vez que o total deles seja usado, sua carteira deve criar mais endereços. Isso só pode ser feito, no entanto, se você tiver backups automáticos ativados. Consequentemente, os usuários que tiverem backups desativados também terão o PrivateSend desativado.

InstantSend¶

Criptomoedas descentralizadas devem esperar por um certo período de tempo para que blocos suficientes passem para garantir que uma transação seja irreversível e não uma tentativa de gasto duplo o dinheiro que já foi gasto em outro lugar. Esse processo é demorado e pode levar de 15 minutos a uma hora para que o número amplamente aceito de seis blocos se acumule. Outras criptomoedas atingem um tempo de confirmação de transação mais rápido centralizando a autoridade na rede em vários níveis.

Dash não sofre dessas limitações graças à sua rede de masternodes de segunda camada. O Masternodes pode ser chamado para formar quoruns de votação para verificar se uma transação enviada é válida ou não. Se for válido, os masternodes «bloquearão» as entradas da transação e transmitirão essas informações para a rede, prometendo efetivamente que a transação será incluída em blocos minerados subsequentemente e não permitindo nenhum outro gasto dessas entradas durante o período de confirmação.

A tecnologia InstantSend permitirá que moedas criptografadas, como o Dash, concorram com sistemas de transação quase instantâneos, como cartões de crédito para situações de ponto de venda, sem depender de uma autoridade centralizada. A aceitação generalizada por parte do fornecedor do Dash e do InstantSend poderá revolucionar a criptomoeda, encurtando o atraso na confirmação de transações de uma hora (com o Bitcoin) para apenas alguns segundos.

Você pode ver um guia prático para usar o InstantSend here. O InstantSend foi introduzido em um white paper chamado Transaction Locking e Masternode Consensus: um mecanismo para reduzir os ataques de gastos duplos.

Como o Dash “InstantSend” protege os comerciantes de duplos gastos, Dash Detailed de Amanda B. Johnson, 16 de setembro de 2016

ChainLocks¶

ChainLocks are a feature provided by the Dash Network which provides certainty when accepting payments. This technology, particularly when used in parallel with InstantSend, creates an environment in which payments can be accepted immediately and without the risk of “Blockchain Reorganization Events”.

The risk of blockchain reorganization is typically addressed by requiring multiple “confirmations” before a transaction can be safely accepted as payment. This type of indirect security is effective, but at a cost of time and user experience. ChainLocks are a solution for this problem.

ChainLocks Process Overview¶

Every twelve hours a new “LLMQ” (Long-Lasting Masternode Quorum) is formed using a “DKG” (Distributed Key Generation) process. All members of this Quorum are responsible for observing, and subsequently affirming, newly mined blocks:

Whenever a block is mined, Quorum Members will broadcast a signed message containing the observed block to the rest of the Quorum.

If 60% or more of the Quorum sees the same new block they will collectively form a “CLSIG” (ChainLock Signature) message which will be broadcast to the remainder of the network.

When a valid ChainLock Signature is received by a client on the network, it will reject all blocks at the same height that do not match the block specified in that message.

The result is a quick and unambiguous decision on the “correct” blockchain for integrated clients and wallets. From a security perspective, this also makes reorganizations prior to this block impossible. See DIP0008 ChainLocks for a full description of how ChainLocks work.

Sporks¶

Em resposta a problemas imprevistos com o lançamento da atualização «RC3» principal em junho de 2014, a equipe de desenvolvimento do Dash criou um mecanismo pelo qual o código atualizado é liberado para a rede, mas não imediatamente ativado («imposto»). Essa inovação permite transições muito mais suaves do que no paradigma do fork rígido tradicional, bem como a coleta de dados de teste no ambiente de rede ao vivo. Esse processo de forjamento em várias fases era originalmente chamado de «soft forking», mas a comunidade o apelidou carinhosamente de «the spork» e o nome ficou.

Novos recursos ou versões do Dash passam por testes extensivos no testnet antes de serem liberados para a rede principal. Quando um novo recurso ou versão do Dash é lançado na mainnet, a comunicação é enviada aos usuários informando sobre a alteração e a necessidade de atualizar seus clientes. Aqueles que atualizam seus clientes executam o novo código, mas ele não é ativado até que uma porcentagem suficiente de participantes da rede (geralmente 80%) chegue a um consenso sobre sua execução. No caso de ocorrerem erros com o novo código, os blocos do cliente não serão rejeitados pela rede e os forks indesejados serão evitados. Os dados sobre o erro podem então ser coletados e encaminhados para a equipe de desenvolvimento. Uma vez que a equipe de desenvolvimento esteja satisfeita com a estabilidade do novo código no ambiente mainnet - e uma vez atingido o consenso de rede aceitável - o cumprimento do código atualizado pode ser ativado remotamente por vários membros da equipe principal de desenvolvimento assinando uma mensagem de rede junto com seus respectivos parceiros privados. chaves. Caso ocorram problemas, o código pode ser desativado da mesma maneira, sem a necessidade de uma reversão em toda a rede ou de uma atualização do cliente. Para detalhes técnicos sobre sporks individuais, consulte here.

Hash Algoritimo X11¶

O X11 é um algoritmo de hash amplamente utilizado, criado pelo desenvolvedor do núcleo do Dash, Evan Duffield. O algoritmo de hashing encadeado do X11 utiliza uma sequência de onze algoritmos de hashing científico para a prova de trabalho. Isso é para que a distribuição do processamento seja justa e as moedas sejam distribuídas da mesma maneira que as do Bitcoin eram originalmente. O X11 pretendia tornar os ASICs muito mais difíceis de criar, dando à moeda muito tempo para se desenvolver antes que a centralização da mineração se tornasse uma ameaça. Esta abordagem foi amplamente bem sucedida; a partir do início de 2016, os ASICs para o X11 agora existem e compreendem uma porção significativa do hashrate da rede, mas não resultaram no nível de centralização presente no Bitcoin. Informações sobre mineração com X11 podem ser encontradas na seção Mining section of this documentation.

X11 é o nome do algoritmo de prova de trabalho (PoW) que foi introduzido no Dash (lançado em janeiro de 2014 como «Xcoin»). Foi parcialmente inspirado pela abordagem hashing encadeada de Quark, acrescentando mais «profundidade» e complexidade, aumentando o número de hashes, ainda difere de Quark em que as rodadas de hashes são determinadas a priori em vez de ter alguns hashes sendo escolhido aleatoriamente.

O algoritmo X11 usa várias rodadas de 11 hashes diferentes (blake, bmw, groestl, jh, keccak, meada, luffa, cubehash, shavite, simd, eco), tornando-o um dos hashes criptográficos mais seguros e sofisticados em uso pelos modernos criptomoedas. O nome X11 não está relacionado ao sistema de janelas X11 de código-fonte aberto comum em sistemas operacionais semelhantes a UNIX.

Vantagens do X11¶

A maior complexidade e sofisticação do algoritmo encadeado fornece níveis aprimorados de segurança e menos incerteza para uma moeda digital, em comparação com soluções de PoW com um único hash que não estão protegidas contra riscos de segurança, como SPOF (Single Point Of Failure). Por exemplo, um avanço de computação, mas não provável, que «quebra» o hash SHA256 poderia colocar em risco toda a rede Bitcoin até que a rede mude através de uma bifurcação para outro hash criptográfico.

No caso de uma descoberta de computação semelhante, uma moeda digital usando o X11 PoW continuaria a funcionar com segurança, a menos que todos os 11 hashes fossem quebrados simultaneamente. Mesmo se alguns dos 11 hashes se provassem não confiáveis, haveria um aviso adequado para uma moeda usando o X11 para tomar medidas e substituir os hashes problemáticos por outros algoritmos hash mais confiáveis.

Dada a natureza especulativa das moedas digitais e suas incertezas inerentes como um novo campo, o algoritmo X11 pode fornecer maior confiança para seus usuários e potenciais investidores que as abordagens single-hash não podem. Soluções de hashing encadeadas, como o X11, proporcionam maior segurança e longevidade para fins de armazenamento de riqueza, diversificação de investimentos e proteção contra riscos associados a moedas com hashing único afetadas por SPOF (Single Point Of Failure - Ponto Único de Falha).

Evan Duffield, o criador do Dash e do X11, escreveu em várias ocasiões que o X11 foi integrado ao Dash não com a intenção de impedir que os fabricantes de ASIC criem ASICs para o X11 no futuro, mas sim fornecer um caminho migratório similar. Bitcoin tinha (CPUs, GPUs, ASICs).

Dark Gravity Wave¶

DGW ou Dark Gravity Wave é um algoritmo de ajuste de dificuldade de código aberto para criptomoedas baseadas em Bitcoin que foi usado pela primeira vez no Dash e desde então apareceu em outras moedas digitais. DGW foi criado por Evan Duffield, o desenvolvedor e criador do Dash, como uma resposta a uma exploração temporal encontrada em Kimoto’s Gravity Well. No conceito, DGW é semelhante ao Kimoto Gravity Well, ajustando os níveis de dificuldade a cada bloco (em vez de cada Blocos de 2016 como o Bitcoin) com base em dados estatísticos de blocos encontrados recentemente. Isso possibilita a emissão de blocos com tempos relativamente consistentes, mesmo que o poder de hashing sofra grandes flutuações, sem sofrer com a exploração do tempo-warp.

A versão 2.0 do DGW foi implementada no Dash a partir do bloco 45.000 em diante, a fim de aliviar completamente a exploração do time-warp.
A versão 3.0 foi implementada em 14 de maio de 2014 para melhorar ainda mais a dificuldade de redirecionamento com transições mais suaves. Ele também corrige problemas com várias arquiteturas que tinham diferentes níveis de precisão de ponto flutuante por meio do uso de inteiros.

Taxa de emissão¶

Criptomoedas como Dash e Bitcoin são criadas através de um processo criptograficamente difícil conhecido como mineração. A mineração envolve a resolução repetida de algoritmos hash até uma solução válida para a atual dificuldade de mineração é descoberto. Uma vez descoberto, o minerador pode criar novas unidades da moeda. Isso é conhecido como a recompensa de bloco. Para garantir que a moeda não esteja sujeita à inflação sem fim, a recompensa em bloco é reduzida em intervalos regulares, como mostrado neste cálculo. A representação gráfica desses dados resulta em uma curva mostrando o total de moedas em circulação, conhecido como taxa de emissão de moedas.

Embora o Dash seja baseado no Bitcoin, ele modifica significativamente a taxa de emissão de moedas para oferecer uma redução mais suave na emissão de moedas ao longo do tempo. Enquanto Bitcoin reduz a taxa de emissão de moeda em 50% a cada 4 anos, Dash reduz a emissão em um décimo quarto (aprox. 7,14%) a cada 210240 blocos (aprox. 383,25 dias) .Pode ser visto que reduzir a recompensa de bloco por um montante menor a cada ano oferece uma transição mais suave para uma economia baseada em taxas do que o Bitcoin.

Taxa de emissão Bitcoin vs. Dash

Emissão total de moedas¶

Emissão total de moeda do Bitcoin pode ser calculado como a soma de uma série geométrica, com a emissão total se aproximando (mas nunca atingindo) 21.000.000 BTC. Isso continuará até 2140, mas a recompensa da mineração reduz tão rapidamente que 99% de todos os bitcoins estarão em circulação até 2036 e 99,9% até 2048.

Emissão total de moeda da Dash é também a soma de uma série geométrica, mas a emissão total final da moeda é incerta porque não se pode saber quanto da recompensa do bloco de 10% reservada para propostas do orçamento será alocada realmente, desde que esta depende do comportamento de votação futuro. Dash continuará a emitir moedas por aproximadamente 192 anos antes de um ano inteiro de mineração cria menos de 1 traço. Após 2209 apenas mais 14 traço será criado. O último Dash levará 231 anos para ser gerado, começando em 2246 e terminando quando a emissão pára completamente em 2477. Com base nesses números, uma oferta de moeda máxima e mínima possível no ano 2254 pode ser calculada entre:

17,742,696 DASH	Assumindo a alocação de tesouraria zero
18,921,005 DASH	Assumindo a alocação total de tesouraria

Alocação de recompensas de bloco¶

Ao contrário do Bitcoin, que aloca 100% da recompensa em bloco aos mineiros, Dash retém 10% da recompensa em bloco para uso no sistema descentralizado budget system. O restante do bloco, bem como quaisquer taxas de transação, são divididos 50/50 entre os mineiros e o masternode, que é deterministicamente selecionado de acordo com a lógica de pagamento. O Dash apresenta superblocos, que aparecem a cada 16616 blocos (aproximadamente 30,29 dias) e podem liberar até 10% do orçamento acumulado retido sobre período do ciclo orçamentário para as propostas vencedoras no sistema orçamentário. Dependendo da utilização do orçamento, isso resulta em uma alocação de recompensa aproximada de moedas ao longo de um ciclo orçamentário, como segue:

45%	Recompensa de Mineração
45%	Recompensa do Masternode para a Prova de Serviço
10%	Orçamento de Governança Descentralizada

Esta documentação é baseada em cálculos e posts de moocowmoo. Por favor, veja este post do reddit para mais detalhes, ou execute seus próprios cálculos de emissões usando esta ferramenta. Veja este site para dados ao vivo nas estatísticas atuais da rede.

Governança Descentralizada¶

Governança Descentralizada pela Blockchain, ou DGBB, é a tentativa de Dash de resolver dois problemas importantes em criptomoeda: governança e financiamento. A governança em um projeto descentralizado é difícil, porque, por definição, não há autoridades centrais para tomar decisões sobre o projeto. No Dash, tais decisões são tomadas pela rede, isto é, pelos donos dos masternodes. O sistema DGBB permite que cada masternode vote uma vez (sim / não / abstém) para cada proposta. Se uma proposta for aprovada, ela poderá ser implementada (ou não) pelos desenvolvedores do Dash. Um exemplo importante é no início de 2016, quando o Core Team do Dash submeteu uma proposta à rede perguntando se o tamanho do bloco deveria ser aumentado para 2 MB. Dentro de 24 horas, o consenso foi alcançado para aprovar essa mudança. Compare isso com Bitcoin, onde o debate sobre o tamanho do bloco tem durado por quase três anos.

O DGBB também fornece um meio para o Dash financiar seu próprio desenvolvimento. Enquanto outros projetos têm que depender de doações ou dotações pré-estabelecidas, Dash usa 10% da recompensa em bloco para financiar seu próprio desenvolvimento. Toda vez que um bloco é extraído, 45% da recompensa vai para o minerador, 45% vai para um masternode e os 10% restantes não são criados até o final do mês. Durante o mês, qualquer pessoa pode fazer uma proposta de orçamento para a rede. Se essa proposta receber aprovação líquida de pelo menos 10% da rede do masternode, no final do mês será criada uma série de «superblocos». As recompensas do bloco que não foram pagas (10% de cada bloco) serão usadas para financiar propostas aprovadas. A rede, portanto, se financia, reservando 10% da recompensa em bloco para projetos orçamentários.

Você pode ler mais sobre a governança do Dash na seção Governança desta documentação.

Sentinel¶

Introduced in Dash 0.12.1, Sentinel is an autonomous agent for persisting, processing and automating Dash governance objects and tasks. Sentinel is implemented as a Python application that binds to a local version dashd instance on each Dash masternode.

A Governance Object (or «govObject») is a generic structure introduced in Dash 0.12.1 to allow for the creation of Budget Proposals and Triggers. Class inheritance has been utilized to extend this generic object into a «Proposal» object to supplant the current Dash budget system.

Diagrama destacando a relação entre Dash Sentinel e Core

Taxas¶

Transactions on the Dash network are recorded in blocks on the blockchain. The size of each transaction is measured in bytes, but there is not necessarily a correlation between high value transactions and the number of bytes required to process the transaction. Instead, transaction size is affected by how many input and output addresses are involved, since more data must be written in the block to store this information. Each new block is generated by a miner, who is paid for completing the work to generate the block with a block reward. In order to prevent the network from being filled with spam transactions, the size of each block is artificially limited. As transaction volume increases, the space in each block becomes a scarce commodity. Because miners are not obliged to include any transaction in the blocks they produce, once blocks are full, a voluntary transaction fee can be included as an incentive to the miner to process the transaction. Most wallets include a small fee by default, although some miners will process transactions even if no fee is included.

The release of Dash 0.12.2.0 and activation of DIP0001 saw a simultaneous reduction of fees by a factor of 10, while the block size was increased from 1MB to 2MB to promote continued growth of low-cost transactions even as the cost of Dash rises. Dash also supports InstantSend and PrivateSend transactions, which operate on a different and mandatory fee schedule. Dash 0.13.0.0 introduced InstantSend autolocks, which causes masternodes to automatically attempt to lock any transaction with 4 or fewer inputs — which are referred to as “simple” transactions — and removes the additional fee for InstantSend. The current fee schedule for Dash is as follows:

Tipo de transação	Taxa recomendada	Por unidade
Transação padrão	.00001 DASH	Por kB de dados de transação
InstantSend autolock	.00001 DASH	Por kB de dados de transação
InstantSend	.0001 DASH	Por entrada de transação
PrivateSend	.001 DASH	Por 10 rodadas de mixagem (média)

As an example, a standard and relatively simple transaction on the Dash network with one input, one output and a possible change address typically fits in the range of 200 - 400 bytes. Assuming a price of US$100 per DASH, the fee falls in the range of $0.0002 - $0.0004, or 1/50th of a cent. Processing a simple transaction using InstantSend at the same price is free of charge, while more complex InstantSend transactions may cost around 1-2 cents per transaction, depending on the number of inputs. These fees apply regardless of the Dash or dollar value of the transaction itself.

PrivateSend works by creating denominations of 10, 1, 0.1, 0.01 and 0.001 DASH and then mixing these denominations with other users. Creation of the denominations is charged at the default fee for a standard transaction. Mixing is free, but to prevent spam attacks, an average of one in ten mixing transactions are charged a fee of 0.0001 DASH. Spending inputs mixed using PrivateSend incurs the usual standard or InstantSend fees, but to avoid creating a potentially identifiable change address, the fee is always rounded up to the lowest possible denomination. This is typically .001 DASH, so it is important to deduct the fee from the amount being sent if possible to minimise fees. Combining InstantSend and PrivateSend may be expensive due to this requirement and the fact that a PrivateSend transaction may require several inputs, while InstantSend charges a fee of 0.0001 DASH per input. Always check your fees before sending a transaction.

Evolution¶

Dash Evolution is the code name for a decentralized platform built on Dash blockchain technology. The goal is to provide simple access to the unique features and benefits of Dash to assist in the creation of decentralized technology. Dash introduces a tiered network design, which allows users to do various jobs for the network, along with decentralized API access and a decentralized file system.

Dash Evolution will be released in stages. Dash Core releases 0.12.1 through to 0.12.3 lay the groundwork for the decentralized features behind the scenes. Version 0.13 introduces the foundation of Evolution, specifically DIP2 Special Transactions and DIP3 Deterministic Masternode Lists. Version 0.14 establishes DIP6 Long Living Masternode Quorums. Expected in late 2019, Dash Core 1.0 will introduce key Evolution features such as username-based payments, the world’s first decentralized API (DAPI) and a decentralized data storage system (Drive) based on IPFS.

Incluído abaixo está o nosso trabalho atual no Evolution, que adiciona muitos componentes como:

Drive: A decentralized shared file system for user data that lives on the second tier network
DAPI: Uma API descentralizada que permite que usuários de terceira camada acessem a rede com segurança
DashPay Carteiras Descentralizadas: Essas carteiras são clientes leves conectados à rede via DAPI e executados em várias plataformas
Segunda Camada: A rede masternode, que fornece infraestrutura compensada para o projeto
Budgets: O segundo nível é dado o poder de voto para alocar fundos para projetos específicos na rede através do sistema de orçamento
Governanca: O segundo escalão tem poder de voto para governar a moeda e traçar o rumo que a moeda leva.
Deterministic Masternode Lists: This feature introduces an on-chain masternode list, which can be used to calculate past and present quorums
Social Wallet: We introduce a social wallet, which allows friends lists, grouping of users and shared multisig accounts

Evolution Previews¶

Os vídeos a seguir, com o Dash Founder Evan Duffield e o Chefe de Desenvolvimento UI/UX, Chuck Williams, descrevem o processo de desenvolvimento e os recursos futuros da plataforma Dash Evolution.

Evolution Demo #1 - O Primeiro Dash DAP, 16 Março 2018

Evolution Demo #2 - Mobile Evolution, 25 Abril2018

Evolution Demo #3 - Dashpay User Experience, 15 Maio2018

Chuck Williams on Evolution, Dash Conferencia em London, 14 Setembro de 2017

Evan Duffield on the Evolution Roadmap, Dash Force News, 28 Junho 2017

How To Buy¶

Dash can be purchased and sold in several ways, each with different advantages and disadvantages. The following options are available:

Exchanges are one of the most popular ways to trade cryptocurrency. A wide range of exchanges exist, each offering slightly different features. Some serve different markets, some are in direct competition, some have cheaper fees, and some are subject to more or less strict regulatory requirements. Most exchanges are centralized, meaning they are operated by a single company, which may be obliged by the laws of the jurisdiction in which it operates to collect data on its customers. Others are decentralized, but as a result have higher escrow requirements since you are dealing peer-to-peer instead of with a trusted entity. Exchanges can be broadly broken down into two categories: exchanges which accept national currency (fiat money) and exchanges which deal in cryptocurrencies only. For safety, exchanges should not be used as wallets. Exchanges are for trading, not for savings.
Instant exchanges perform a similar function to normal exchanges, but without the requirement to log in. They effectively convert one currency to another, with some limits on the amount to be exchanged and usually at a less advantageous rate. Others may even offer to sell cryptocurrency as a credit card purchase.
Over the counter exchanges have recently appeared to facilitate sale of Dash directly from a company to the individual at a specified price, or peer-to-peer between individuals at a negotiated price. Volume may be limited compared to exchanges, but these services are usually much easier to use. More advanced peer-to-peer sites offer escrow services for a fee to prevent cheating during the sale between two parties who have never met.
ATMs accepting card and cash payments in return for crypto are widely available. Mapping services can show the specific location of these machines, or you can even set one up at your own business and earn a percentage of sales.

DISCLAIMER: This list is provided for informational purposes only. Services listed here have not been evaluated or endorsed by Dash Core and no guarantees are made as to the accuracy of this information. Please exercise discretion when using third-party services.

Exchanges¶

Cryptocurrency exchanges exist to convert national currency, also known as fiat money, into cryptocurrency. Many exchanges do not accept fiat money, and exchange between various cryptocurrencies only. Trades are handled on markets, and trades are created between pairs of currencies, identified by their ticker codes. Dash is widely accepted on exchanges and many pairs exist against both fiat money and cryptocurrency. This means it is possible to exchange EUR for DASH, or DASH for BTC, for example. The volume traded on an exchange provides a good indication of how quickly a buy or sell order you place will be filled. This section introduces some of the most popular exchanges for trading Dash.

Marketplace comparison websites¶

Coinpaprika

https://coinpaprika.com

Coinpaprika lists hundreds of cryptocurrencies by their market capitalization, traded volume and recent price performance. A number of advanced features to research cryptocurrency projects and exchanges are also available.

Cryptoradar

https://cryptoradar.co

Cryptoradar is a real-time cryptocurrency marketplace price comparison and review platform. The website compares dozens of Dash markets based on prices, fees, payment methods, reviews and more.

CoinMarketCap

https://coinmarketcap.com

CoinMarketCap lists all cryptocurrencies by their market capitalization. Clicking one of these currencies allows you to view price charts, and clicking Markets allows you to view the markets available and the trading pairs they offer.

Dash.org markets¶

https://www.dash.org/exchanges

The official Dash website also provides a list of major exchanges offering Dash.

List of exchanges¶

Please see here for a detailed guide on how to buy Dash on an exchange. The exchanges listed here are for informational purposes only and do not indicate endorsement or affiliation with any particular platform.

Kraken

https://www.kraken.com

Kraken is a high-volume US-based exchange offering fiat currency deposits in EUR, USD, JPY and GBP. DASH can be traded against EUR, USD and BTC.

Coinbase Pro

https://pro.coinbase.com/

Coinbase Pro is a major cryptocurrency trading platform offering high Volume DASH trading pairs for USD and BTC. Coinbase Pro supports deposits and withdrawals in cryptocurrency as well as USD, GBP and EUR.

Poloniex

https://poloniex.com

Poloniex is a US-based cryptocurrency exchange operated by Circle offering high volume DASH pairs for BTC, USDC, USDT and XMR. Poloniex also supports deposits in USD by bank transfer and allows cryptocurrency purchases with debit and credit cards. Leveraged margin trading and lending is also available for DASH.

Bittrex

https://bittrex.com

Bittrex is a US exchange working with cryptocurrencies only, although USD wire transfers have been intermittently supported in the past. DASH trading pairs are available for BTC, ETH and USDT.

Bitfinex

https://www.bitfinex.com

Bitfinex is a cryptocurrency exchange based in Hong Kong offering high volume BTC and USD trading pairs for DASH, as well as leveraged trading.

Binance

https://www.binance.com

Binance is a high-volume exchange with a very wide range of trading pairs available. DASH is available for funding and can be traded against BTC, ETH, TUSD and BNB.

HitBTC

https://hitbtc.com

HitBTC offers facilities to major investors to credit USD, EUR and GBP, as well as BTC, ETH and USDT trading pairs against DASH for normal users.

Bithumb

https://www.bithumb.com

Bithumb is the largest cryptocurrency exchange in South Korea. It accepts fiat deposits in South Korean Won only, and offers high volumes of DASH trading.

Huobi

https://www.huobi.pro

Huobi is a major Chinese exchange offering high volume DASH trading against BTC. A native app is available for both iOS and Android.

BitKan

https://bitkan.com

Founded in 2012, BitKan offers a one-stop platform for smart trading, “K-Site” community, market data, industry news, a multi-cryptocurrency wallet and mining monitor for millions of global users. BitKan also features a Smart Trade platform to help users get the fastest trade at the best price by aggregating the liquidity of multiple exchanges.

CEX.IO

https://cex.io

CEX.IO is a UK-based exchange with over one million users and offers DASH exchange pairs for fiat currencies including GBP, EUR and USD.

DigiFinex

https://www.digifinex.com

Based in Singapore, DigiFinex offers Dash trading against USDT, BTC and ETH. DigiFinex supports InstantSend, with clear benefits for arbitrage traders and consumers.

YoBit

https://yobit.net

YoBit is an exchange focusing on Ethereum tokens, but also supports BTC, USD and RUB trading pairs for DASH.

Chaoex

https://www.chaoex.com

Based in Hong Kong and available in English and Traditional Chinese, Chaoex is a pure crypto exchange offering trading with a focus on new assets and supports mobile apps for both Android and iOS.

Bit-Z

https://www.bit-z.com

Bit-Z is a cryptocurrency exchange with a focus on offering OTC funding options to Chinese traders. DASH is available for trade against BTC.

Koineks

https://koineks.com

Koineks serves the Turkish market and offers trading pairs for DASH against the Turkish Lira and Bitcoin.

Bitci

https://bitci.com

Bitci offers DASH trading in Turkey against BTC, Turkish Lira (TRY) and CHFT.

Sistemkoin

https://sistemkoin.com

Sistemkoin serves the Turkish market and offers trading pairs for DASH against the Turkish Lira and Bitcoin.

Ovis

https://www.ovis.com.tr

Ovis serves the Turkish market and offers trading pairs for DASH against the Turkish Lira and Bitcoin.

Exmo

https://exmo.com

Exmo is a UK-registered exchange offering fiat deposits in USD, EUR, USD and UAH (Ukrainian Hryvnia). DASH trading pairs exist for BTC, USD and RUB.

Coinvest

https://coinve.st

Coinvest offers a range of products and research targeting both consumers and institutional investors, as well as a wallet built around smart contracts. DASH is available for trade against BTC, ETH, GUSD and COIN.

BitBay

https://bitbay.net

BitBay is based in Poland and accepts fiat deposits in EUR, USD and PLN. DASH can be traded against all three fiat currencies and BTC.

Livecoin

https://www.livecoin.net

Livecoin offers fiat deposits in EUR, USD and RUB, and DASH trading pairs for BTC, USD and some other low volume cryptocurrencies.

xBTCe

https://www.xbtce.com

xBTCe is an exchange based in St. Kitts and Nevis with a focus on providing fiat currency trading pairs. Various deposit methods are available for currencies including CNH (Chinese Offshore Yuan), EUR, GBP, JPY, IDR and RUB. DASH trading pairs include BTC, USD and CNH.

BitMax

https://bitmax.io

BitMax is a global operator of digital asset exchanges for a diverse groups of clients, from retail to institutions. The trading platform, architected by a group of Wall Street quant trading veterans, is designed for reliability and speed of trade execution, and ease of connectivity.

IDAX

https://www.idax.pro

Based in Mongolia, IDAX is a high volume exchange with a focus on the Chinese and Korean markets. Dash transactions support InstantSend, and trading is available for against BTC.

Upbit

https://upbit.com

UPbit is a Korean exchange allowing deposits in KRW and offering DASH trading pairs for KRW, ETH, BTC and USDT.

CoinEx

https://www.coinex.com

CoinEx is a Hong Kong based exchange with a focus on Bitcoin Cash trading. DASH is available for trading against both BCH and BTC.

Trade by Trade

https://tradebytrade.com

Trade By Trade is registered in Vanuatu and provides a trading platform for over 60 cryptocurrencies with a range of tools to manage your trades.

Bitinka

https://www.bitinka.com

Bitinka is the premiere exchange in Latin America, and offers BTC, LTC, ETH, XRP and DASH in exchange for over 10 national currencies from America and Europe.

eToro

https://www.etoro.com

With legal entities in the UK, Israel and Cyprus, eToro offers a social trading platform where you can copy top performing accounts. DASH and a number of other cryptocurrencies, forex and stocks are available.

Liqui

https://liqui.io

Liqui is headquartered in Ukraine and offers a modern interfaced for leveraged trading of many cryptocurrencies, including a DASH/BTC pair.

Bitbns

https://bitbns.com

Bitbns offers DASH trading against the Indian Rupee (INR) for Indian citizens with bank deposits supported from many major Indian banks.

Coinome

https://www.coinome.com

Coinome is an Indian exchange offering DASH trading against the Indian Rupee (INR).

Bitcoin.com

https://exchange.bitcoin.com/

Bitcoin.com allows you to buy, sell and store cryptocurrencies. DASH can be traded against BCH, BTC, ETH and USDT.

WazirX

https://wazirx.com

WazirX is an Indian exchange offering DASH trading against BTC and USDT, and funding in the Indian Rupee (INR).

Coinsquare

https://coinsquare.io

Coinsquare is a Canadian exchange offering DASH trading against BTC and CAD.

Lykke

https://www.lykke.com

Incorporated in Switzerland, Lykke is an open source exchange, online/mobile wallet service, idea accelerator and ICO platform. DASH is available for both trading and investment.

Liquid

https://www.liquid.com

Liquid serves the Asian market with funding support for HKD, AUD, CNY, INR, JPY, PHP, IDR, UDS, SGD and EUR, and trading against ETH, BTC, BCH and DASH.

BitcoinVN

https://bitcoinvn.io

BitcoinVN is a Vietnamese exchange offering BTC, BCH, LTC and DASH for trading against Vietnamese đồng.

Ginero

https://ginero.io

Ginero is a peer-to-peer exchange operating in Vietnam and offeringexchange offering BTC, BCH, LTC, ETH, GIN and DASH for trading against Vietnamese đồng.

ZB.com

https://www.zb.com

With a focus on the Chinese market, ZB.com offers trading from specialized applications for macOS, Windows, Android and iOS. Crypto deposits and DASH trading against QC, USDT and BTC.

Coinfield

https://www.coinfield.com

Coinfield is a Canadian exchange offering funding in CAD and quick market purchases or advanced trading against DASH.

Bitshares

https://bitshares.org

BitShares is a decentralized exchange (DEX) offering DASH trading pairs for BTC and BTS, as well as the bit assets bitUSD, bitCNY and bitBTC.

Cryptopia

https://www.cryptopia.co.nz

Cryptopia is a New Zealand cryptocurrency exchange with a reputation for supporting a large number of low-volume altcoins. It offers DASH trading pairs for BTC, LTC, DOGE and USDT.

ACX

https://acx.io

ACX is an Australian exchange accepting fiat deposits from Australian bank accounts. DASH is available to trade against BTC.

Jinanace

https://jinance.com.au

Jinance is an Australian exchange accepting fiat deposits from Australian bank accounts. DASH is available to trade against AUD.

OKEX

https://www.okex.com

OKEX, previously known as OKCoin, is an exchange focused on the Chinese market offering DASH trading pairs against BTC. Funding with CNY and futures trading is also available.

Bitexbook

https://bitexbook.com

Bitexbook promises the fastest possible deposit and withdrawal times and responsive customer support. Deposits are available in USD and RUB, and credit cards are supported.

MoneyPolo

https://moneypolo.com

MoneyPolo offers currency exchange and transfer, prepaid cards and the ability to hold accounts in a range of currencies. Deposits and withdrawals are available in DASH, BTC, ETH, LTC, BCH and BTG, and it is possible to transfer value to a prepaid card or any worldwide bank account.

Coinapult

https://coinapult.com

Coinapult is an asset exchange headquartered in Panama City and providing exchange services between BTC, DASH, USD, GBP and EUR, as well as gold and silver.

Panda.exchange

https://panda.exchange

Based in Latin America, Panda.exchange specializes in making digital assets such as Dash available in Latin America and, through a branch in Portugal, the EU market.

Cubobit

https://cubobit.com/

Cubobit allows you to exchange Dash and other cryptocurrencies against Mexican pesos.

Golix

https://golix.com

Based in Zimbabwe, Golix is a digital currency exchange that helps people in Sub-Saharan Africa buy and sell DASH and other cryptocurrencies.

Bisq

https://bisq.network

Bisq is a decentralized exchange running on the Tor network and offers complete privacy, but trades are manual, require escrow and must be settled between users.

Coincheck

https://coincheck.com

Coincheck is a Japanese exchange allowing deposits in JPY and USD for trading against DASH and other cryptocurrencies.

Coindeal

https://coindeal.com

Coindeal allows deposits in EUR and offers a range of trading pairs, including DASH. The exchange is focused on obtaining a FINMA license in Switzerland to be able to accept a broader range of fiat deposits.

BuyUcoin

https://www.buyucoin.com

BuyUcoin is a large Indian exchange offering DASH and many other cryptocurrencies in exchange for Indian Rupees (INR).

BitMEX

https://www.bitmex.com

BitMEX is a pure-crypto derivates exchange offering trading with up to 100x leverage. DASH is available to trade against BTC.

MBAex

https://mbaex.com

MBAex is a pure crypto exchange with a focus on the Chinese market. DASH can be traded against BTC, USDT and MDP.

KuCoin

https://www.kucoin.com

KuCoin is a pure crypto exchange with a focus on the Chinese market. DASH can be traded against BTC, USDT, ETH and KCS.

BTCC

https://www.btcc.com

Based in the UK Hong Kong and available in English and Chinese, BTCC offers DASH trading against BTC and USD.

Bibox

https://www.bibox.com

With a focus on the Asian market, Bibox offers DASH trading against BTC, ETH and USDT.

DigiFinex

https://www.digifinex.com

DigiFinex is a Chinese exchange allowing trading of DASH against USDT and BTC.

OOOBTC

https://www.ooobtc.com

OOOBTC offers DASH trading against BTC and ETH, with a user interface available in Russian, Arabic and many East Asian languages.

ExchangeAssets

https://exchange-assets.com

ExchangeAssets is available in Russian and English, and offers DASH trading against BTC.

ABCC

https://abcc.com

ABCC offers web and app-based trading of Dash against BTC, ETH and USDT.

Indodax

https://indodax.com

Indodax allows funding in IDR and offers a DASH/BTC trading pair.

ALFAcashier

https://www.alfacashier.com

ALFAcashier, incorporated in Belize, provides electronic exchange and fiat services. DASH trading pairs are available for BTC, XRP, XMR, XEM, ETH, LTC, BCH, USD, EUR, CNY, CAD and RUB.

CoinSuper

https://www.coinsuper.com

Registered in Hong Kong and with a focus on the Chinese market, CoinSuper allows fiat deposits in USD and offers DASH trading against BTC, ETH and USD.

Exrates

https://exrates.me

Exrates allows crypto and USD deposits, and offers DASH trading against BTC and USD.

Bleutrade

https://bleutrade.com

Registered in Brazil, Bleutrade offers DOGE and BTC trading pairs for DASH.

LBank

https://www.lbank.info

Available in English and Chinese, LBank has a focus on token trading. DASH is available to trade against BTC.

Coinroom

https://coinroom.com

Registered in Poland, Coinroom has a strong focus on trading against fiat currencies. Deposits are available in CHF, CZK, DKK, EUR, GBP, NOK, PLN and USD. DASH can be traded against USD, BTC, EUR, PLN and GBP.

CoinSpot

https://www.coinspot.com.au

CoinSpot is an Australian exchange offering DASH, BTC, LTC and ETH in exchange for AUD.

Holy Transaction

https://holytransaction.com

Holy Transaction offers DASH trading pairs for BTC, USD and EUR, as well as over ten other altcoins.

NovaDAX

https://www.novadax.com.br

NovaDAX offers BTC, USDT and BRL trading pairs for Dash, with rapid deposits and withdrawals in Brazilian real. Trading compeitions and OTC services are also available.

3xBit

https://3xbit.com.br

3xBit is a Brazil-based exchange offering many Dash pairs, as well as trading against BTC and the dollar-proxy CREDIT coin.

NegocieCoins

https://www.negociecoins.com.br

Based in Brazil, NegocieCoins offers deposits in Brazilian real and Dash trading pairs. A premium service with higher withdrawal limits is available.

XDEX

https://www.xdex.com.br

Based in Brazil, XDEX offers both simple purchase and sale of cryptocurrencies and an advanced trading platform with various order types. Dash and several other cryptocurrencies are available for trading against the Brazilian real.

Bitcointoyou

https://bitcointoyou.com

Based in Brazil, Bitcointoyou has been in operation since 2010 and offers trading of a number of cryptocurrencies, including Dash, against the Brazilian real.

Exscudo

https://exscudo.com

Exscudo offers an exchange trading Dash against BTC and EUR, as well as cash-settled merchant services and a wallet ecosystem based on the EON token, which allows users to seamlessly transmit money to one another in a chat environment.

LATOKEN

https://latoken.com

LATOKEN offers DASH trading against USDT and BTC.

BitOffer

https://bitoffer.com

BitOffer offers DASH trading against USDT, ETH and BTC.

BW

https://bw.com

BW exchange focuses on the Chinese and Korean market, with Dash available for exchange against USDT and the QC exchange token.

SatoWallet

https://satowallet.com

SatoWallet is a multi-coin crypto wallet with built-in exchange functionality. Dash is available for trade against Nigerian Naira (NGN), USD, BTC and ETH.

OmniTrade

https://omnitrade.io

Based in Brazil, OmniTrade accepts deposits in Brazilian real through a partnership with Neon Bank, which can then be traded against Dash.

Braziliex

https://braziliex.com

Based in Brazil, Brazilies accepts deposits in Brazilian real, and offers trading of real, Bitcoin and USDT against Dash.

WEX

https://wex.nz

WEX, previously known as BTC-e until it was shut down by authorities, has resumed business under a new name. DASH trading pairs exist for BTC, USD, RUB, EUR, LTC and ETH.

Ovis

https://www.ovis.com.tr

Ovis serves the Turkish market and offers trading pairs for DASH against the Turkish Lira and Bitcoin.

Lescovex

https://lescovex.com

Registered in Switzerland, Lescovex offers deposits and withdrawals in a wide range of fiat currencies (EUR, USD, CAD, GBP, CHF, SEK, RON) for trading against DASH and other cryptocurrencies. The platform is designed to assist in the creation of tokens and cryptographic contracts.

AvaTrade

https://www.avatrade.com

Headquartered in Ireland, with offices around the world and boasting over 200,000 registered customers globally, AvaTrade is committed to empowering people to invest and trade, with confidence, in an innovative and reliable environment. AvaTrade offers Dash trading as well as traditional Forex, CFD and options trading.

SouthXchange

https://www.southxchange.com

Based in Argentina, SouthXchange offers DASH for USD and BTC.

Coinrail

https://coinrail.co.kr

Coinrail is a Korean exchange offering DASH trading against KRW.

Cashierest

https://www.cashierest.com

Cashierest is a Korean exchange offering DASH trading against KRW, BTC and ETH.

Tidex

https://tidex.com

Tidex is an exchange focusing on tokens on the WAVES and Ethereum blockchains, but also offers trading against fiat currencies. DASH can be traded against ETH, BTC, WAVES and Waves pegged currencies.

LiteBit

https://www.litebit.eu

LiteBit is a service based in The Netherlands selling cryptocurrency including Dash for EUR.

Laissez Faire

https://lzf.com

Laissez Faire offers incentivized trading which includes DASH.

OceanEx

https://oceanex.pro

OceanEx offers DASH trading against VET and USDT.

BTC-Alpha

https://btc-alpha.com

BTC-Alpha is an exchange serving Russian-speakers and offering DASH trading pairs against BTC and USDT.

Instant exchanges¶

Changelly

https://changelly.com

Changelly is a broker service offering a range of cryptocurrency, including Dash, for instant exchange against other cryptocurrencies without needing to create an account. Be sure to check the fees and rates before purchasing.

ShapeShift

https://shapeshift.io

ShapeShift allows users to directly exchange one crypto asset for another, albeit with a higher markup than most exchanges. ShapeShift supports Dash and over 70 other cryptocurrencies.

ChangeHero

https://changehero.io

ChangeHero is a broker service and instant exchange with a clear fee structure, allowing users to quickly and efficiently exchange Dash for many other cryptocurrencies. It is also possible to purchase directly using a credit card.

SimpleSwap

https://www.simpleswap.io

SimpleSwap is a simple and easy-to-use platform for cryptocurrency exchanges that works without registration and limits. It is possible to exchange Dash with over 60 other cryptocurrencies.

AirTM

https://www.airtm.io

AirTM allows rapid exchanges between a range of cryptocurrencies, traditional banks and proprietary regional payment schemes such as Alipay, Western Union or Skrill.

Godex

https://godex.io

Godex allows users to directly exchange one crypto asset for another without creating any account, albeit with a higher markup than most exchanges. Godex supports Dash and over 120 other cryptocurrencies.

Flyp.me

https://flyp.me

Flyp.me is developed by the team at HolyTransaction, the first multicurrency web wallet. It offers instant exchange services between 18 different cryptocurrencies without creating an account.

OnePageX

https://onepagex.com

One Page Exchange is a single-page instant exchange allowing users to convert Dash into over 140 different cryptocurrencies without registration.

CoinSwitch

https://coinswitch.co

CoinSwitch is a crypto to crypto exchange aggregate with more than 300 different coins and tokens listed. Also offers purchases through credit/debit cards.

fox.exchange

https://fox.exchange

fox.exchange is a crypto to crypto exchange allowing instant exchange between DASH, BTC, LTC, BCH, BSV, ETH and BAT.

MorphToken

https://www.morphtoken.com

MorphToken is an instant exchange allowing users to instantly convert between Dash, Bitcoin, Bitcoin Cash, Ethereum, Litecoin and Monero. It is even possible to convert into more than one cryptocurrency in a single exchange.

changeNOW

https://changenow.io

changeNOW is a non-custodian exchange service based in the Netherlands, with low commissions and quick service. Offers crypto to crypto exchanges, as well as purchases through credit/debit cards.

Guarda

https://guarda.co

Guarda offers an entire blockchain ecosystem consisting of desktop, web and mobile wallets, OTC crypto sales and instant crypto exchange. Dash is supported throughout the ecosystem, making it an easy and convenient way for new users to get started.

BlockTrades

https://blocktrades.us

BlockTrades is a decentralized exchange designed to facilitate free movement between the Steemit, BitShares, Bitcoin and Dash blockchains. The system is designed to find the best possible instant conversion rate between any two given cryptocurrencies.

Over the Counter¶

Coinbase

https://www.coinbase.com

Coinbase is a large US-based cryptocurrency exchange with a focus on making it easy to buy, sell and manage your cryptocurrency portfolio. With trading allowed between any of the 17+ cryptocurrencies supported and many major fiat currencies including EUR, USD and GBP, Coinbase is a great place to buy your first cryptocurrency.

Uphold

https://uphold.com

Uphold accounts may be funded with over 30 national currencies by bank account or credit card to purchase and spend multiple cryptocurrencies including Dash.

Kriptomat

https://kriptomat.io

Kriptomat enables you to buy, sell and store cryptocurrencies in your local language - safe, simple and secure. Dash is available for exchange to and from EUR with bank accounts and credit cards.

Bitpanda

https://www.bitpanda.com https://www.bitpanda.com/togo

Bitpanda is a broker service offering Bitcoin, Ethereum, Litecoin and Dash both online and at over 400 Post branches and about 1300 Post partners throughout Austria. Pay with cash, credit card or bank transfer.

Bitnovo

https://www.bitnovo.com

Bitnovo is a broker service offering Bitcoin and Dash both on their website and at tens of thousands of physical locations throughout Europe. They also offer reloadable cards, vouchers and cryptocurrency wallets.

Cointree

https://www.cointree.com

Cointree offers services to buy, sell and trade Bitcoin, Dash and many other cryptocurrencies in Australia on a simple and attractive web platform. Cointree offers multiple payment methods, low fees, bill payment options and a range of learning materials to help get started with cryptocurrencies.

Voyager

https://www.investvoyager.com

Voyager is a crypto asset broker that connects to multiple exchanges commission-free. Dash can be traded and purchased directly with USD.

Crypto Voucher

https://cryptovoucher.io

Crypto Voucher allows you to instantly buy Dash and other cryptocurrencies using credit cards, SEPA transfers, giftcards and in offline stores. A number of online distributors are also supported.

Bitit

https://bitit.io

Bitit is a broker service offering Bitcoin, Dash and several other cryptocurrencies for sale online. Payment in a range of currencies is support using both direct banking, credit cards and vouchers.

RenrenBit

https://renrenbit.com

RenrenBit is a digital asset management platform offering 100% reserve. With its official launch in 2018, RenrenBit now provides financial services including wallet, trading markets and crypto asset loans.

buycrypto

https://buycrypto.gr

Buycrypto is a peer-to-peer cryptocurrency-fiat exchange geared towards giving Greeks easier access to economically sound money. Dash is available for purchase and sale against the Euro.

ChangeHero

https://changehero.io

ChangeHero is a broker service and instant exchange with a clear fee structure, allowing users to quickly and efficiently exchange Dash for many other cryptocurrencies. It is also possible to purchase directly using a credit card.

Kraken

https://www.kraken.com

Kraken offers private, personalized OTC service with deep liquidity to institutions and high net-worth individuals needing to fill orders in excess of $100,000. Simply send an email to otc@kraken.com to get started.

Koi Trading

https://koi.trade

Based in San Francisco with satellite offices in Hong Kong and Europe, Koi Trading offers a reliable, efficient, and compliant OTC pathway for institutions and high net-worth individuals to engage with cryptocurrency. Brokerages, exchanges, miners and funds worldwide trust Koi Trading for its professional, high-touch services and robust cryptocurrency liquidity.

Coinfinity

https://coinfinity.co

Coinfinity offers Dash and Bitcoin broker services in Austria and Germany, as well as through their coupon-based Bitcoinbon service.

Coinsave

https://coinsave.io

Coinsave is a Canadian OTC retailer offering DASH and other cryptocurrencies for CAD.

Coinrex

https://coinrex.io

Coinrex allows you to sell and buy Dash and other cryptocurrencies OTC with Mexican pesos.

Bitcoin Meester

https://www.bitcoinmeester.nl https://www.bitladon.com

Bitcoin Meester, and it’s international sister site Bitladon, allows you to buy and sell Dash (and other cryptocurrencies) OTC in exchange for Euro.

Coinvertit

https://www.coinvertit.com

Based in Romania, Coinvertit is an easy way to buy and sell Dash in exchange for BTC, LTC, BCH and Romanian Leu (RON).

eBitpoint

https://www.ebitpoint.com

eBitpoint is a secure online peer to peer platform with escrow service for buying, selling, storing Dash and other digital currencies at competitive exchange rates in Ghana.

eBitcoinics

http://www.ebitcoinics.com

eBitcoinics is a cryptocurrency exchange and education platform for the African market. Dash is available for exchange against Nigerian Naira (NGN) and Ghanaian Cedi (GHS).

Kurecoinhub

https://kurecoinhub.com

Kurecoinhub offers DASH and other cryptocurrencies for sale OTC for the Nigerian Naira. Dividend bearing bank deposits, loans against Dash collateral and merchant services are also available from this innovative platform.

Gredo E-currency

https://www.gredoe-currency.com

Gredo E-currency offers OTC sale of Dash and other cryptocurrencies for Nigerian Naira (NGN).

TruexGOLD

https://truexgold.com

TruexGOLD offers OTC sale of Dash in Nigeria for Nigeria Naira (NGN).

Cryptomate

https://cryptomate.co.uk

Cryptomate sells a range of cryptocurrencies, including Dash, for GBP. Cryptomate’s goal is to make buying and selling cryptocurrency as simple as possible for people who want a pain-free experience and the fastest transactions - coins can be in your wallet as soon as 5 minutes after ordering.

Easy Crypto

https://www.easycrypto.nz

Easy Crypto allows New Zealanders to buy and sell Dash and 45 other cryptocurrencies instantly, with fast and friendly service.

BitPrime

https://www.bitprime.co.nz

BitPrime operates a secure and compliant platform for easy retail trading in New Zealand. Dash is available OTC for both purchase and sale together with many other cryptocurrencies.

Mercury Cash

https://www.mercury.cash

Mercury Cash is an online/mobile wallet and licensed money transmitter with integration for merchant services. Balances can be held in both Ethereum and Dash, and deposited or withdrawn in local currencies through a number of methods, including credit cards.

Bitcoin.de

https://www.bitcoin.de

Bitcoin.de allows user to post offers to buy or sell Dash and Bitcoin within their region or country. The users then arrange the deal between themselves.

cryptomonster

https://www.cryptomonster.co.uk

cryptomonster have created an easy to use platform where you can buy DASH and other digital assets within minutes. All you need is a UK bank account and a wallet address. cryptomonster pride themselves on a next-level service and regard themseleves as the leading digital assets platform in the UK.

Changelly

https://changelly.com

Changelly is a popular instantaneous crypto to crypto exchange platform with more than 100 different coins and tokens listed. Also offers purchases via credit/debit cards.

Cryptobuyer

https://cryptobuyer.io

Cryptobuyer is a direct purchasing service with a focus on the Latin American market and Venezuela in particular. It can be linked with a bank account to purchase Dash, Litecoin and Bitcoin directly. The company also operates a network of ATMs and merchant integrations.

BasiChange

https://basichange.com

BasiChange offers exchange, trading and OTC crypto sales with a focus on Venezuela and Colombia.

Daexs

https://daexs.com

Daexs is a cryptocurrency exchange based in Colombia with Dash and Bitcoin markets trading against the Colombian Peso (COP).

CryptoWay

https://cryptoway.io

On CryptoWay, you can buy and sell Dash, Bitcoin, Ethereum, Litecoin and Doge peer-to-peer (P2P) with Venezuelan bolivars on a secure, fast and simple platform. You can also link your bank account for efficient processing of deposits and withdrawals.

Kamoney

https://www.kamoney.com.br

Kamoney is a Brazil-based cryptocurrency vendor offering services to buy and sell Dash, Bitcoin and Ethereum in exchange for Brazilian real, as well as payment services in Brazil.

BitJá

https://www.bitja.com.br

BitJá is a Brazil-based cryptocurrency vendor offering services to buy and sell Dash, Bitcoin and Ethereum in exchange for Brazilian real.

Stratum

https://stratum.hk

Stratum is a Brazil-based cryptocurrency company offering a variety of services including an exchange, mining, bill payment, point-of-sale, and more. Dash is available for purchase at over 13,000 locations around Brazil.

Wall of Coins

https://wallofcoins.com

Wall of Coins allows user to post offers to buy or sell Dash and Bitcoin within their region or country. The service, which is available in over 20 countries, then holds the coins in escrow while the buyer completes payment.

Liberalcoins

https://liberalcoins.com

Liberalcoins allows users to arrange trades to buy or sell Dash, Monero, Bitcoin and Litecoin directly with one another.

QCashPay

https://qcashpay.com

QCashPay is a Hong Kong company specialising in direct sale of cryptocurrency, including Dash, for USD and CNY using various bank and third party payment schemes.

MegaChange

https://www.megachange.is

MegaChange offers direct sale and exchange of various digital forms of currency in a simple market system. It supports Dash and multiple methods of adding fiat currency, including USD, RMB and RUB.

Magnetic Exchange

https://magneticexchange.com

Magnetic Exchange offers Bitcoin, Ethereum, Litecoin and Dash in exchange for USD or EUR through various payment services.

AnycoinDirect

https://anycoindirect.eu

AnycoinDirect.eu is a broker service offering 14 cryptocurrencies, including Dash, for sale online. Pay by bank transfer or various national instant payment schemes.

Dash Nearby

https://dashnearby.com

Dash Nearby allows users to arrange direct trades of cryptocurrency or local currency between one another.

Coindirect

https://www.coindirect.com

Coindirect offers OTC and P2P services to buy and sell many cryptocurrencies, including Dash. Verified users can create offers in their local currency to buy and sell with other users. Online wallets and exchange services are available for most currencies as well.

Graviex

https://graviex.net

Graviex is a part of the Gravio ecosystem, a blockchain-based communication platform. It offers extremely low rates and fees for trading. DASH can be traded against BTC, ETH, LTC and DOGE.

Bitqist

https://bitqist.com

Bitqist is a service based in The Netherlands offering over 140 for purchase and sale. While not strictly an exchange in the sense of offering order books, it is possible to buy and sell each currency at near the market price.

SlithEx

https://slithex.com

Based in Malaysia and funded by the Dash Treasury, SlithEx (and its payment processor, RocketPay) offer exchange, wallet and sale/trading of Dash against the Malaysian ringgit.

ATMs¶

ATMs are a popular method of buying cryptocurrency at businesses to encourage adoption and spending in these currencies. A number of ATMs support Dash, and the mapping services listed on this page can help you find one near you. It is also possible to operate your own ATM to sell Dash on-site at your business - simply contact the companies listed on this page.

General Bytes

https://www.generalbytes.com

General Bytes offers a range of two-way cash ATM and Point of Sale solutions integrating Dash.

Coin ATM Radar

https://coinatmradar.com

Various coin ATMs are available around world. Coin ATM Radar helps you find one close to you.

Lamassu

https://lamassu.is

Lamassu offers modular one-way and two-way cash ATMs integrating Dash.

CoinFlip

https://coinflip.tech

CoinFlip operates a network of ATMs across the USA and offers hosted ATMs for businesses.

Trovemat

https://trovemat.com

Focusing on the European market, Trovemat provides a risk-free solution to sell cryptocurrency from a physical device.

TigoCTM

https://tigoctm.com

TigoCTM offers simple ATM solutions integrated with a management blockchain.

Segurança¶

Se você é novo em criptomoedas, a mudança mais importante para entender em comparação com o sistema bancário tradicional é que as transações ocorrem diretamente entre duas partes, sem qualquer autoridade centra para facilitar a transação. Isso também significa que você é responsável por sua própria segurança - não há banco ou empresa de cartão de crédito para reverter uma transação se seus fundos forem roubados ou perdidos. Se esquecer ou perder o seu arquivo da carteira, a frase de recuperação ou o PIN, você perde permanentemente e irrevogavelmente o acesso aos seus fundos.

Dash é projetado desde o início para ser rápido, seguro, fungível e privado. Nesse sentido, é semelhante a dinheiro ou ouro, mas a criptomoeda pode ser gasta local e internacionalmente com a mesma facilidade, se você tiver certeza de que está enviando fundos para o destino certo. Por esses motivos, a documentação do Dash tem um forte foco na segurança e na compreensão dos conceitos e recursos que orientam ao ecossistema Dash.

Algumas diretrizes gerais de segurança:

Não confie em nenhum serviço online ou pessoa só porque eles soam ou parecem respeitáveis. Sempre use um serviço de custódia(escrow), se você estiver comprando peer-to-peer.
Guarde o seu Dash em um hardware wallet se possível. Se não, guarde suas moedas no oficial Carteira Dash Core ou o oficial Carteira Dash Electrum.
Não use exchanges como carteiras. As exchanges são para negociação, não para poupança.
Carteiras móveis devem ser usadas para compras do dia-a-dia, mas não mantenham grandes quantias de dinheiro nelas. Coloque os fundos conforme necessário.

Uma lista de fraudes conhecidas, carteiras falsas e esquemas Ponzi ou pirâmide pode ser vista abaixo. Não acredite neles.

Impersonation¶

Scammers may attempt to impersonate well-known community members and manipulate you into granting them access to your system or wallets. This is usually done via private messages on the forum, Discord or email. The attacks are often targeted against masternode owners. If you require technical assistance, it is best to ask in a public channel/forum or go to https://support.dash.org and open a ticket. If you engage in personal chat with a well-known community member, verify their identity by their chat history or through their publicly available cryptographic keys. All community members and Dash Core Group staff will be able to verify their identity using signed PGP messages. Identities can also be verified on Keybase:

Golpes¶

Há muitas páginas «falsas» de Dash/Darkcoin na Internet tentando enganar os usuários para que enviem Dash ou outras criptomoedas ou «abrir uma carteira». Outras fraudes incluem a venda de hardware de mineração falsa, Dash falso ou altcoins com um nome semelhante e esquemas Ponzi (veja abaixo). Por favor, tenha cuidado e não confie em terceiros listados aqui!

Lista de golpes conhecidos relacionados ao Dash:

dash-wallet dot com é uma farsa conhecida!
electrumdash dot org é um clone falso do site oficial!
dashcoinmining dot com não é afiliado com Dash!
dashcrypto dot info não é afiliado com Dash!
onclooud dot com não é afiliado com Dash!
as-shop dot su está vendendo mineradoras baikal fake!
minershop dot biz está vendendo mineradoras baikal fake!
dashcoinclub dot com é um esquema Ponzi não afiliado com Dash!
dash-coin dot net é uma carteira web falsa, não envie dinheiro!
coinvert dot io fake exchange!
dashcash dot io is not affiliated with Dash and may be distributing a compromised wallet!
dashdaowallet dot com is a mydashwallet clone and confirmed scam

Cuidado com as contas falsas do Twitter que se passam por Dash! A conta oficial do Twitter é: https://twitter.com/Dashpay

Por favor, denuncie estes e quaisquer outros golpes que você encontrar da seguinte forma:

Denunciar phishing e golpes ao Google: https://www.google.com/safebrowsing/report_phish
Procure o registro do domínio e envie uma reclamação: https://www.whois.com/whois
Reportar phishing para Netcraft: https://www.netcraft.com
Reportar golpes ao projeto BadBitcoin: http://www.badbitcoin.org
Em caso de dúvida, use o Crypto Scam Checker para ver se já reportou e relatar também: https://fried.com/crypto-scam-checker

Sinta-se livre para denunciar qualquer nova fraude que você encontrar no fórum em nosso tópico «equipe swat»: https://dashtalk.org/threads/www-dash-wallet-com-is-a-scam-website.8267

Esquemas Ponzi¶

Um Esquema Ponzi, Esquema em pirâmide o Marqueking Multi Nivel são operações de investimento fraudulentas em que a empresa gera retornos para investidores mais antigos por meio de receita paga por novos investidores. Mais e mais usuários devem constantemente aderir ao esquema para que ele continue sua operação, com um número cada vez maior de pessoas perdendo dinheiro para os criadores do esquema.

Se você encontrar um esquema Ponzi, siga as mesmas etapas de relatório acima para sites fraudulentos!

Lista de esquemas Ponzi conhecidos (há muitos mais - fique atento!):

OneCoin

SwissCoin

The Billion Coin

Sustaincoin

http://www.scamvoid.com/check/sustaincoin.com

E-Dinar

DasCoin

BitConnect

HashOcean

http://themerkle.com/bitcoin-scam-risk-warning-hashocean/

CryptoDouble

http://themerkle.com/bitcoin-hyip-ponzi-scheme-alert-coindouble/

Links and Information¶

Links¶

Community sites¶

Forums¶

Dash Forum: https://www.dash.org/forum
BitcoinTalk thread: https://bitcointalk.org/index.php?topic=421615.0
Cryptocurrencytalk.com: https://cryptocurrencytalk.com/forum/693-dash
巴比特 (8BTC) Forum: http://8btc.com/forum-115-1.html
百度贴吧达世币吧 (Baidu Tieba): https://tieba.baidu.com/f?kw=达世币
彩云比特达世币 (CYBTC Dash): http://www.cybtc.com/forum-123-1.html

Chat¶

Dash Nation Discord: https://discordapp.com/invite/9z8zX5j
Dash Talk Discord: https://discordapp.com/invite/PXbUxJB
Dash English Telegram: https://t.me/dash_chat
Dash Brasil Telegram: https://telegram.me/dashbrasil
Dash Russia Telegram: https://telegram.me/Dash_Ru
Dash en Español Telegram: http://unete.dashespanol.com
Dash Embassy D-A-CH auf Deutsch Telegram: https://t.me/dashembassydach
Dash Telegram News Bot: https://telegram.me/dashnews
QQ 达世币官方群 DASH.China: 419967021
Freenode IRC: #dashpay

Facebook¶

English (Official): https://www.facebook.com/DashPay
Dash News En Español: https://www.facebook.com/DashNewsEspanol
Dash Embassy Thailand: https://www.facebook.com/DashEmbassyThailand
Brazil: https://www.facebook.com/DashBrazil
Denmark: https://www.facebook.com/DashDenmark
Germany: https://www.facebook.com/dashgermany
Greece: https://www.facebook.com/DashGreece
Poland: https://www.facebook.com/Dash.Polska
Russia: https://www.facebook.com/Dash.Russia
Thailand: https://www.facebook.com/groups/1127359790623640
Venezuela: https://www.facebook.com/groups/DarkcoinVenezuela
Vietnam: https://www.facebook.com/dashvietnam

Twitter¶

Dash Official Account: https://twitter.com/dashpay
Ryan Taylor, CEO of Dash Core Group: https://twitter.com/RTaylor05
Dash Force News: https://twitter.com/DashForceNews
Joël Valenzuela, Chief Editor, Dash Force News: https://twitter.com/TheDesertLynx
Mark Mason, Director of Media & PR, Dash Force News: https://twitter.com/StayDashy
Amanda B. Johnson, Dash Superfan and DAO-funded contractor: https://twitter.com/AmandaB_Johnson
Tao of Satoshi, Dash Nation Founder and DAO-funded contractor: https://twitter.com/Dash_Nation
とみ三（Samurai33）, Dash Japan: https://twitter.com/samurai3311
Dash Vietnam: https://twitter.com/dashvietnam

News¶

Dash Force News: https://www.dashforcenews.com
Dash News En Español: https://dashnewsespanol.com
Dash News En Español (YouTube): https://www.youtube.com/channel/UCG6Cuh8Q2eUt4NlZu4K-u8g
Dash News Korea: https://dashnewskorea.com
Cointelegraph: https://cointelegraph.com/tags/dash
巴比特 (8BTC): http://www.8btc.com/dash
比特时代 (BTC38): http://www.btc38.com/altcoin/dash
Dash Embassy D-A-CH: http://www.dash-embassy.org/
Dash News Germany: https://dash-news.de
Dash Vietnam: https://dashvn.blogspot.com
Dash France: https://dashfrance.com/
Dash News China (Wechat): dashnews (or scan QR below)

Ferramentas¶

Block explorers, statistics and visualizations¶

Treasury tools¶

Masternode management¶

Price monitoring and statistics¶

Dash Community project¶

DarkNet pages¶

Dash (Mirror of Main Page): http://dashorg64cjvj4s3.onion
The Hidden Wiki: http://zqktlwi4fecvo6ri.onion/wiki/Dash_-_DigitalCash

Mobile Apps¶

iOS¶

Dash Wallet: https://itunes.apple.com/app/id1206647026
Edge Wallet: https://itunes.apple.com/app/id1344400091
Jaxx Wallet: https://itunes.apple.com/app/id1084514516
Coinomi Wallet: https://itunes.apple.com/app/id1333588809
Dashy: https://itunes.apple.com/app/id1033268631
CoinCap: https://itunes.apple.com/app/id1074052280
Blockfolio: https://itunes.apple.com/app/id1095564685
Cryptonaut: https://itunes.apple.com/app/id1312756405
Quoinex: https://itunes.apple.com/app/id1140955992
Abra: https://itunes.apple.com/app/id966301394
BitUniverse: https://itunes.apple.com/app/id1329338902

Android¶

Dash Wallet: https://play.google.com/store/apps/details?id=hashengineering.darkcoin.wallet
Edge Wallet: https://play.google.com/store/apps/details?id=co.edgesecure.app
Jaxx Wallet: https://play.google.com/store/apps/details?id=com.kryptokit.jaxx
Coinomi Wallet: https://play.google.com/store/apps/details?id=com.coinomi.wallet
Cryptonator Wallet: https://play.google.com/store/apps/details?id=com.aev.cryptonator
DashCentral: https://play.google.com/store/apps/details?id=net.paregov.android.dashcentral
CoinCap: https://play.google.com/store/apps/details?id=io.coinCap.coinCap
Blockfolio: https://play.google.com/store/apps/details?id=com.blockfolio.blockfolio
Cryptonaut: https://play.google.com/store/apps/details?id=org.cryptonaut.app
Quoinex: https://play.google.com/store/apps/details?id=mobi.quoine
Abra: https://play.google.com/store/apps/details?id=com.plutus.wallet
Bitcoin Ticker Widget: https://play.google.com/store/apps/details?id=st.brothas.mtgoxwidget
BitUniverse: https://play.google.com/store/apps/details?id=com.bituniverse.portfolio

Glossário¶

51% Attack

A condition in which more than half the computing power on a cryptocurrency network is controlled by a single miner or group of miners. That amount of power theoretically makes them the authority on the network. This means that every client on the network believes the attacker’s hashed transaction block.

Address

Um endereço Dash é usado para enviar / receber um pagamento na rede Dash. Ele contém uma cadeia de caracteres alfanuméricos, mas pode ser representado como um código QR. Um endereço Dash é também a chave pública do par de chaves utilizadas por titulares do Dash para assinar digitalmente transações (ver chave pública).

Algorithm

Em matemática e ciência da computação, um algoritmo é um passo-a-passo conjunto independente de operações a serem realizadas. Algoritmos de executar o cálculo, processamento de dados, e / ou tarefas de raciocínio.

Altcoin

Since Bitcoin was the first cryptocurrency and has the largest market capitalization, it is considered as the reference. An altcoin, or alternative coin, is any cryptocurrency other than Bitcoin.

AML

Técnicas de lavagem de dinheiro são usadas para impedir que as pessoas converta recursos obtidos ilegalmente, para parecer como se tivessem sido obtidos legalmente. mecanismos LMA pode ser legal ou de natureza técnica. Reguladores frequentemente aplica técnicas de AML para trocas.

API

Na programação de computadores, uma interface de programação de aplicações (API) é um conjunto de rotinas, protocolos e ferramentas para a construção de software e aplicações.

Uma API expressa um componente de software em termos de suas operações, entradas, saídas e tipos subjacentes, definindo funcionalidades que são independentes das respectivas implementações, o que permite definições e implementações para variar, sem comprometer a interface. Uma boa API torna mais fácil para desenvolver um programa, fornecendo todos os blocos de construção, que são então colocadas em conjunto pelo programador.

ASIC

Um circuito integrado de aplicação específica (ASIC) / eɪsɪk /, é um circuito integrado (IC) personalizado para um uso específico, em vez de ser utilizado para fins gerais. Por exemplo, um chip projetado para ser executado em um gravador de voz digital ou um Mining Dash de alta eficiência é um ASIC

ATM / BTM

A ATM Dash é uma máquina física que permite a uma pessoa comprar Dash com dinheiro. Existem muitos fabricantes, alguns dos quais permitem aos usuários vender Dash por dinheiro. Eles também são chamadas às vezes «BTMS “ou” Dash AVMS “. Dash é suportado por vários ATMs.

Backlog

Backlog generally refers to an accumulation over time of work waiting to be done or orders to be fulfilled.

Backup

O processo de fazer cópias de um arquivo de computador para garantir a sua integridade no caso de perda, roubo ou dano. Dash tem a característica única de permitir aos usuários fazer cópias de segurança de suas carteiras digitais. Isso protege contra a perda do dinheiro no caso de um computador travar ou perder um dispositivo móvel. Isso seria o equivalente a ser capaz de fazer o backup do dinheiro em sua carteira, de modo que se você perdeu, você pode restaurar o dinheiro em um backup.

Bitcoin 2.0

Este é um termo que explica o próximo novo nível de projetos Bitcoin que começou com um fork do Bitcoin, mas estenderam seu código para o próximo nível de Projetos Blockchain (Contratos inteligentes, descentralizada Votação, ….)

Blockchain

É um banco de dados distribuído que mantém uma lista crescente de registros de dados. Ele consiste em blocos de estrutura de dados que mantêm exclusivamente dados em implementações iniciais de blocos e dados e programas em algumas das implementações mais recentes - com cada bloco realizando lotes de transações individuais e os resultados de qualquer bloco executável. Cada bloco contém um timestamp e informação ligando-o a um bloco anterior.

Blocos

As transações no Blockchain são coletadas em blocos, blocos registro e confirmar quando e em que seqüência as transações entra e são registrados na cadeia de bloco. Os blocos são criados por usuários conhecidos como «mineradores» que usam software especializado ou equipamento projetado especificamente para criar blocos.

Budget System / DGBB

The development of Dash and the Dash ecosystem is self-funded by the network. Each time a block is discovered, 45% of the block reward goes to miners and 45% goes to masternodes. Ten percent is withheld by the network and used to fund projects that are approved by the masternode network. This process is known as Decentralized Governance by Blockchain (DGBB). For a fee, anybody can submit a proposal to the network, and will be paid directly by the blockchain if approved by the masternodes. The Budget System is sometimes called the Treasury System; the two terms are interchangeable.

ChainLock

Defined in DIP8, ChainLocks are a method of using an LLMQ to threshold sign a block immediately after it is propogated by the miner in order to enforce the first-seen rule. This is a powerful method of mitigating 51% mining attacks, which are associated with double spending.

Cloud Wallet

São terceiros que irá armazenar seus Dash em seus servidores para você, para que você “pode acessar seus Dashs a partir de qualquer dispositivo conectado à internet. Se o site é hackiado ou se os servidores estão danificados, você corre o risco de perder o seu Dash. Quaisquer carteiras on-line devem ser feita com frases-senhas fortes e 2FA. Você não pode fazer cópias de segurança de sua carteira on-line, porque você não tem acesso às chaves privadas.

Coinbase transaction

The first transaction in a block. Always created by a miner, it includes a single input which constitutes the block reward. This is split between the miner and a deterministically chosen masternode.

Cold Storage

Um método de gerar e armazenar chaves privadas completamente offline. Pode-se usar um computador desktop ou laptop desconectado da internet, um hardware wallet, um USB ou um carteira de papel.

Confirm(ed) Transaction

Quando uma transação é feita, um minerador deve verificar se a transação é válida. Quando as entradas e saídas são verificadas, a transação está incluída em um bloco no blockchain. A transação pode ser agora completa e irreversível. O número de confirmação aumenta à medida que mais blocos são adicionados ao blockchain.

Confirmation Number

O número de confirmações Dash para uma transação. Zero significa que as confirmações de transação não está confirmado. Uma confirmação significa que a transação está incluída no mais recente bloco no blockchain. Duas confirmações indica que a transação está incluído em dois blocos, a três quadras confirmações para três, e assim por diante. A probabilidade de uma transação ser revertida (duplo gasto) diminui exponencialmente com cada bloco e posterior confirmação.

Confirmed Transactions

Transactions that are processed by miners and considered irreversible, usually after six confirmations. In the case of InstantSend, funds can be considered irreversible after a few seconds, but must still be written to the blockchain (and thus «confirmed»).

CPU

A central processing unit (CPU) is the electronic circuitry within a computer that carries out the instructions of a computer program by performing the basic arithmetic, logical, control and input/output (I/O) operations specified by the instructions. The term has been used in the computer industry at least since the early 1960s. Traditionally, the term «CPU» refers to a processor, more specifically to its processing unit and control unit (CU), distinguishing these core elements of a computer from external components such as main memory and I/O circuitry.

Cryptocurrency

Uma criptomoeda (ou moeda criptográfica ou cripto-moeda) é um meio de troca usando criptografia para proteger as transações e controlar a criação de novas unidades.

Cryptography

Cryptography or cryptology (from Greek κρυπτός kryptós, «hidden, secret»; and γράφειν graphein, «writing,» or -λογία -logia, «study,» respectively) is the practice and study of techniques for secure communication in the presence of third parties called adversaries. More generally, cryptography is about constructing and analyzing protocols that prevent third parties or the public from reading private messages; various aspects in information security such as data confidentiality, data integrity, authentication, and non- repudiation are central to modern cryptography. Modern cryptography exists at the intersection of the disciplines of mathematics, computer science, and electrical engineering. Applications of cryptography include ATM cards, computer passwords, and electronic commerce.

DAP

Decentralized Application Protocol. This term describes an application running on top of the Dash DAPI platform.

DAP Client

An HTTP Client that connects to DAPI and enables Dash blockchain users to read and write data to their DAP Space.

DAP Schema

A Dash Schema document extending the Dash System Schema to define consensus data and rules within a DAP contract.

DAP Space

The part of a DAP State that is owned by a specific blockchain user. Data in a DAP Space can only be changed by the owner.

DAP State

The total set of data stored in a DAP. This data consists of user DAP Spaces.

DAPI

Decentralized Application Programming Interface. See above for a definition of API. DAPI will perform the same functions as an API, but with quorums of masternodes acting as the endpoints for API communication.

Dark Gravity Wave

No conceito, Dark Gravity Wave (DGW) é semelhante a Kimoto Gravity Well, ajustando os níveis de dificuldade de cada bloco (em vez de cada 2016 blocos como Bitcoin) usando dados estatísticos dos últimos blocos encontrados. Desta forma, os tempos de emissão de blocos podem permanecer consistentes, apesar das altas flutuações de hashpower. No entanto, ele não sofre com o tempo-warp explora.

Darkcoin

Dash foi lançado como XCoin e depois renomeado para Darkcoin.

Dash

Originally launched as Xcoin and later renamed to Darkcoin, the currency was later renamed «Dash» to avoid association with the darknet markets. Dash is a portmanteau of «Digital Cash.» Dash is an open source peer-to- peer cryptocurrency that solves many of Bitcoin’s problems. Dash’s features include PrivateSend, InstantSend, Decentralized Governance by Blockchain (DGBB), a 2nd tier network (referred to as the masternode network). See the Features page for a full list of Dash’s features.

DashDrive

Dash network data storage backend service used by masternodes for off-chain data relating to Evolution. DashDrive implements IPFS, a type of distributed file storage system.

Dash Client

Clientes Dash são programas de software usados para interagir com a rede Dash. Eles armazenam as chaves privadas necessárias para realizar transações Dash, bem como uma cópia de todo o bloco. Um cliente Dash se conecta à rede Dash e se torna um nó na rede. Um nó compartilha e propaga novas transações com o restante da rede criando uma infraestrutura robusta.

Carteira Dash Core

The Dash Core Wallet (known also as the QT wallet) is the «official» Dash wallet that is compiled by the Dash Core Team and allows both PrivateSend and InstantSend. The DashCore wallet will download the entire blockchain and serve it over the internet to any peers who request it.

Dash Evolution

This is a 3 tier network Dash developers are presently building. It will make Dash as easy to use as PayPal, while still remaining decentralized. See the Evolution page for more information.

Dash Schema

A JSON-based language specification for defining and validating consensus data in Evolution.

DDoS

Um ataque de negação de serviço distribuído usa um grande número de computadores sob o controle de um invasor para drenar os recursos de um alvo central. Eles muitas vezes enviam pequenas quantidades de tráfego de rede através da Internet para amarrar recursos de computação e largura de banda no destino, o que impede que ele forneça serviços a usuários legítimos. As exchange de Dash foram às vezes atingidos com ataques DDoS.

Decentralized

Decentralized computing is the allocation of resources, both hardware and software, to each individual workstation or office location. In contrast, centralized computing exists when the majority of functions are carried out or obtained from a remote centralized location. Decentralized computing is a trend in modern-day business environments. This is the opposite of centralized computing, which was prevalent during the early days of computers. A decentralized computer system has many benefits over a conventional centralized network. Desktop computers have advanced so rapidly that their potential performance far exceeds the requirements of most business applications. This results in most desktop computers remaining nearly idle most of the time. A decentralized system can use the potential of these systems to maximize efficiency. However, it is debatable whether these networks increase overall effectiveness.

Desktop Wallet

A wallet is a piece of software that stores your Dash. There are many different wallet options, but it is imperative to choose a secure one. We recommend any of the following: Dash Core Wallet / Dash Electrum Wallet / Hardware Wallets

Difficulty

Esse número determina a dificuldade de um novo bloco. Ele está relacionado com o número máximo permitido em uma determinada porção numérica do hash de um bloco de transação. Quanto menor o número, mais difícil é produzir um valor de hash que o ajuste. A dificuldade varia com base na quantidade de poder de computação usada pelos mineradores na rede Dash. Se um grande número de mineradores deixar uma rede, a dificuldade diminuiria. Até agora, no entanto, a popularidade crescente Dash tem atraído mais poder de computação para a rede, o que significa que a dificuldade aumentou.

Digital Wallet

See this link for full documentation on wallets.

A digital wallet is similar to a physical wallet except that it is used to hold digital currency. A Dash wallet holds your private keys, which allow you to spend your Dash. You are also able to make backups of your wallet in order to ensure that you never lose access to your Dash. Digital wallets can exist in many different forms and on many devices:

Desktop Wallet (Dash Electrum Wallet, Dash Core Wallet): Wallet programs that you install on a laptop or desktop computer. You are solely responsible for protecting the wallet file and the private keys it contains. Make backup copies of your wallet files to ensure that you don’t lose access to your funds.
Mobile Wallet (Android, iOS): These wallets can be downloaded through Google Play or Apple (iTunes) App Stores. Mobile wallets allow you to use Dash on-the-go by scanning a QR code to send payment. Make backup copies of your mobile wallet files to ensure that you don’t lose access to your funds. Due to security issues with mobile phones, it is advised that you don’t store large amounts of funds on these wallets.
Online/Cloud/Web Wallet (Exodus, MyDashWallet): Third parties that will store your Dash on their servers for you or provide an interface to access your Dash with you providing the keys, so that you can access your Dash from any device connected to the internet. If their website is hacked or if their servers are damaged, you run the risk of losing your Dash. Any online wallets should be secured with strong passphrases and 2FA. You cannot make backup copies of your online wallet, because you do not have access to the private keys. We strongly urge that you NEVER store large amounts of Dash in any online wallet or cryptocurrency exchange.
Hardware Wallets (Trezor, KeepKey, Ledger, Nano): A hardware wallet is a specialized, tamper-proof, hardware device that stores your private keys. This device is able to sign transactions with your private key without being connected to the internet. However, you must have an internet connection to send the transaction to the Dash network. This allows your private keys to be accessed easily while still keeping them securely protected. This is widely regarded to be the safest form of storage for your Dash.
Offline/Cold Storage (Paper wallet): A special wallet that is created offline and is never exposed to the internet. Accomplished by using software to generate a public and private key offline and then recording the generated keys. They keys can be printed out on paper or even laser-etched in metal. Copies can be made and stored in a personal safe or bank deposit box. This is an extremely secure way to store Dash. There is no risk of using software wallet files, which can become corrupt, or web wallets, which can be hacked. NOTE: USB sticks are not safe for long-term (multi-year) storage because they degrade over time.

DKG

Defined in DIP6, Distributed Key Generation (DKG) is a method of generating a BLS key pair for use in an LLMQ to perform threshold signing on network messages. It is based on BLS M-of-N Threshold Scheme and Distributed Key Generation, which is an implementation of Shamir’s Secret Sharing.

Digital Signature

Uma assinatura digital é um mecanismo matemático que permite a alguém provar sua identidade ou propriedade de um ativo digital. Quando sua carteira digital assina uma transação com a chave privada apropriada, toda a rede pode ver que a assinatura corresponde aos Dashs que estão sendo gastos, sem a necessidade de revelar a chave privada para a rede.

Electrum Wallet

Dash Electrum Wallet is a lightweight wallet that does not require you to download or sync the entire blockchain, making the wallet lighter and faster. However, it is missing certain features such as PrivateSend and InstantSend.

Encryption

In cryptography, encryption is the process of encoding messages or information in such a way that only authorized parties can read it. Encrypted messages which are intercepted by a third-party are indecipherable gibberish without the private key. In an encryption scheme, the plaintext message is encrypted using an encryption algorithm, generating ciphertext that can only be read if decrypted by the intended recipient. For technical reasons, an encryption scheme usually uses a pseudo-random encryption key generated by an algorithm. Increases in computing power have «broken» many past encryption algorithms, but a well-designed modern system such as AES-256 is considered essentially «uncrackable.»

Escrow Services

An escrow is:

a contractual arrangement in which a third party receives and disburses money or documents for the primary transacting parties, with the disbursement dependent on conditions agreed to by the transacting parties; or
an account established by a broker for holding funds on behalf of the broker’s principal or some other person until the consummation or termination of a transaction; or
a trust account held in the borrower’s name to pay obligations such as property taxes and insurance premiums.

A trusted escrow service is often used when purchasing cryptocurrency or other goods/services over the internet. Both the buyer and seller will choose a trusted third-party, the seller will send the item (or currency) to the escrow agent, and the buyer will send the purchasing funds to the escrow agent as well. Once the escrow agent is satisfied that both parties have satisfied the terms of the agreement, he/she will forward the funds and the product (or currency) being purchased to the appropriate party.

Evan Duffield

Founder and first Lead Developer of Dash. Inventor of X11, InstantSend and PrivateSend. Before creating Dash, Evan was a financial advisor and holds a Series 65 license.

Exchange

The current price of one Dash compared to the price of other currencies, like the US dollar, Yen, Euro, or Bitcoin. Because most trading volume takes place on the BTC/DASH markets, price is often quoted in fractions of a bitcoin. For instance, the price of one Dash at the end of March 2017 was 0.08 (bitcoins per Dash). An excellent site for following the exchange rate of Dash is CoinMarketCap. Businesses wishing to reduce the risk of holding a volatile digital currency can avoid that risk altogether by having a payment processor do an instant exchange at the time of each transaction.

Faucet

Faucets are a reward system, in the form of a website or app, that dispenses rewards in the form of a microdash or Duff, which is a hundredth of a millionth Dash, for visitors to claim in exchange for completing a captcha or task as described by the website.

Fiat Gateway

Fiat money has been defined variously as:

Any money declared by a government to be legal tender.
State-issued money which is neither convertible by law to any other thing, nor fixed in value in terms of any objective standard.
Intrinsically valueless money used as money because of government decree.

Examples include the US dollar, the Euro, the Yen, and so forth.

Fintech

Financial technology, also known as FinTech, is an economic industry composed of companies that use technology to make financial services more efficient. Financial technology companies are generally startups trying to make financial processes more efficient or eliminate middle- men. Recently many fintech companies have begun utilizing blockchain technology, which is the same technology that underpins Dash and Bitcoin.

Fork

When the blockchain diverges or splits, with some clients recognizing one version of the blockchain as valid, and other clients believing that a different version of the blockchain is valid. Most forks resolve themselves without causing any problems, because the longest blockchain is always considered to be valid. In time, one version of the blockchain will usually «win» and become universally recognized as valid. Forks can, however, be extremely dangerous and should be avoided if possible.

Forking is most likely to occur during software updates to the network. Dash uses a Multi-Phased Fork (“Spork”) system for greater flexibility and safety.

Full Nodes

Any Dash client that is serving a full version of the blockchain to peers. This can be a user running a Dash Core wallet on his/her desktop, or it could be a masternode. Full nodes promote decentralization by allowing any user to double check the validity of the blockchain.

Fungible

Cada unidade da moeda vale o mesmo que qualquer outra unidade.

Genesis Block

O primeiro bloco na cadeia de blocos.

GPU

A graphics processing unit (GPU), also occasionally called visual processing unit (VPU), is a specialized electronic circuit designed to rapidly manipulate and alter memory to accelerate the creation of images in a frame buffer intended for output to a display. GPUs are used in embedded systems, mobile phones, personal computers, workstations, and game consoles. Modern GPUs are very efficient at manipulating computer graphics and image processing, and their highly parallel structure makes them more efficient than general- purpose CPUs for algorithms where the processing of large blocks of data is done in parallel. In a personal computer, a GPU can be present on a video card, or it can be embedded on the motherboard or — in certain CPUs — on the CPU die. Certain cryptocurrencies use mining algorithms which are most efficiently run on GPUs.

Hardware Wallet

Hardware wallets are among the safest type of wallet for storing your Dash. Your private key is protected inside a piece of hardware, and is never exposed to the internet. You are still able to sign transactions as normal, making it both safe and convenient.

Hash

A mathematical process that takes a variable amount of data and produces a shorter, fixed-length output. A hashing function has two important characteristics. First, it is mathematically difficult to work out what the original input was by looking at the output. Second, changing even the tiniest part of the input will produce an entirely different output.

Hashrate

O número de hashes que pode ser executado por um minerador Dash em um determinado período de tempo (geralmente um segundo).

Insight

Blockchain information server used to power block explorers and respond to transaction queries.

InstantX

See InstantSend

InstantSend

InstantSend technology uses the masternode network to «lock» transaction inputs, preventing Dash from being double-spent. Unlike Bitcoin, where it takes an hour or longer for transactions to fully confirm, transactions using InstantSend are «locked» and irreversible after only a few seconds.

Liquidity

The ability to buy and sell an asset easily, with pricing that stays roughly similar between trades. A suitably large community of buyers and sellers is important for liquidity. The result of an illiquid market is price volatility, and the inability to easily determine the value of an asset.

LLMQ

Defined in DIP6, A Long- Living Masternode Quorum (LLMQ) is a deterministic subset of the global deterministic masternode list. Such a quorum is formed with the help of a distributed key generation (DKG) protocol and is supposed to be active for a long time (e.g. days). Multiple quorums are kept alive at the same time, allowing load balancing between these quorums. The main task of a LLMQ is to perform threshold signing of consensus related messages.

Masternode

A masternode is special type of full node that performs services for the network and is paid a portion of the block reward. Masternodes require proof of ownership of 1000 DASH.

Masternodes serve as the second tier of the Dash network, and power InstantSend, PrivateSend, the Budget System.

Mining

Miners process transactions on the Dash network and publish them on the blockchain. As a reward for doing this, miners are paid 45% of the block reward.

Mobile Wallet

Estes são carteiras disponíveis em telefones móveis (iPhone + Android).

MultiSig

Multi-signature addresses provide additional security by requiring multiple people to sign a transaction with their private key before the transaction can be sent. For example, in 2 of 3 multisig, two out of three possible signatories have to sign a transaction for it to be processed. Multi-signature addresses are commonly used by exchanges and other organizations that are in possession of large sums of cryptocurrency, since it makes theft much more difficult.

Node

A node is any device running Dash wallet software. Full nodes are software clients that have downloaded the entire blockchain and serve it to other clients on Dash’s peer-to-peer network.

OTC

Over the counter (OTC) trades are trades that occur off exchanges. In an OTC trade, a buyer and seller trade with each other directly, or through an intermediary. OTC trading is useful when a person wants to either buy or sell a large amount of cryptocurrency and is afraid that a large buy or sell order will move the price (called «slippage»).

P2P

Peer-to-peer. Decentralized interactions that happen between at least two parties in a highly interconnected network. An alternative system to a “hub-and-spoke” arrangement, in which all participants in a transaction deal with each other through a single mediation point.

Paper Wallet

Paper wallets are offline wallets, printed on paper for safety. If properly secured and stored they are considered the safest way to store cryptocurrency.

Privacy

Privacy is the ability of an individual or group to seclude themselves, or information about themselves, and thereby express themselves selectively. The boundaries and content of what is considered private differ among cultures and individuals, but share common themes. When something is private to a person, it usually means that something is inherently special or sensitive to them. The domain of privacy partially overlaps security (confidentiality), which can include the concepts of appropriate use, as well as protection of information. Dash includes PrivateSend, which allows users to maintain financial privacy.

Private Key

A private key is a long alphanumeric passcode that allows Dash to be spent. Every Dash wallet contains one or more private keys which are saved in the wallet file. The private keys are mathematically related to all Dash addresses generated for the wallet. Because the private key is the «ticket» that allows someone to spend Dash, it is important that these are kept secure and secret.

PrivateSend

PrivateSend obscures the source of funds in order to maintain financial privacy between users. It can be turned on or off at the users” discretion.

Proof of Service - PoSe

Consensus mechanism used in Dash to verify that a masternode has provided uninterrupted service meeting a minimum quality level to the network. Maintaining this service allows a masternode to enter and move up through the global list and eventually into the selection pool to receive payment.

Proof of Stake - PoS

Consensus mechanism that relies on ownership of a cryptocurrency to maintain the blockchain. In Proof of Stake systems, each owner of the currency can use their wallet to «stake,» and there’s a small chance that they will be chosen to create the next block and add it to the chain. In this way consensus is maintained across all nodes. Proof of Stake saves electricity and does not require specialized computer hardware. It does however suffer from several pitfalls, including the «nothing at stake» problem. Since no electricity is consumed, in the event of an attack it is actually beneficial for Proof of Stake nodes to «vote» to accept both the legitimate chain and the attacker’s chain.

Proof of Work - PoW

Consensus mechanism that keeps all nodes honest by requiring computational power to be expended in order to create new blocks. Miners must use expensive equipment and burn electricity to add blocks to the blockchain. Without a consensus mechanism of some sort, any node could add blocks to the chain and the network’s nodes would never agree on which chain was valid.

Public Key

The public key is derived from the private key but is not secret and can be revealed to anybody. When a private key is used to sign messages, the public key is used to verify that the signature is valid.

Pump and dump

Inflating the value of a financial asset that has been produced or acquired cheaply, often using aggressive publicity and misleading statements. The publicity causes others to acquire the asset, forcing up its value. When the value is high enough, the perpetrator sells their assets, cashing in and flooding the market, which causes the value to crash. This is particularly common in markets with low liquidity, such as some altcoins.

Quorum

Group of masternodes signing or voting on some action, with the formation of the group determined by some determiniation algorithm.

QR Code

A two-dimensional graphical block containing a monochromatic pattern representing a sequence of data. QR codes are designed to be scanned by cameras, including those found in mobile phones, and are frequently used to encode Dash addresses.

Satoshi Nakamoto

Satoshi Nakamoto is the name used by the person or people who designed Bitcoin and created its original reference implementation.

SDK

Software Development Kit. A set of tools, code and documentation used by developers to create apps targeting a specific hardware or software platform.

Signaling

An indication, flag, or signal of support for a feature or fork. The term signaling is most often used in the context of miners delivering this indication of support or agreement. The message is generally delivered through their adoption of updated software in support of a particular protocol and/or by setting a specific version bit within discovered blocks.

State View

The current state of all data objects once all changes from state transitions have been applied. Used in Evolution to determine what should be displayed in a given social wallet, for example.

Spork

The Dash development team created a mechanism known as a «spork» by which updated code is released to the network, but not immediately made active (or “enforced”). Communication is sent out to users informing them of the change and the need for them to update their clients. Those who update their clients run the new code, but in the event of errors occurring with that new code, the client’s blocks are not rejected by the network and unintended forks are avoided. Data about the error can then be collected and forwarded to the development team. Once the development team is satisfied with the new code’s stability in the mainnet environment – and once acceptable network consensus is attained – enforcement of the updated code can be activated remotely. Should problems arise, the code can be deactivated in the same manner, without the need for a network-wide rollback or client update.

Tainted Coins

Taint is a measure of correlation between two (wallet) addresses. It is only important if the user is trying to remain anonymous.

tDash

Test Dash, usado no Testnet.

Testnet

Testnet é uma rede apenas para testes (paralela à Rede Principal), Test QT Wallets, Test Coins, Test Masternodes, Test Miners e testadores (públicos) estão simulando Mainnet.

Tor

Um protocolo de roteamento anônimo, usado por pessoas que querem ocultar sua identidade on-line.

Transaction

Some movement of data on the distributed blockchain ledger. Transactions may be divided into classical and special transactions. Similar to Bitcoin, classical transactions move balances between addresses on the blockchain. Special transactions contain an extra payload in the format defined by DIP2, and can be used to manage blockchain users, for example.

Transaction Block

Uma coleção de transações na rede Dash, reunidas em um bloco que pode então ser hashed e adicionado ao blockchain.

Transaction Fee

Uma pequena taxa imposta em algumas transações enviadas através da rede Dash. A taxa de transação é concedida ao minerador que com êxito minero o bloco contendo a transação relevante.

Unconfirmed Transactions

Transactions that are not yet processed by miners or held via InstantSend are «unconfirmed on the blockchain.» Unconfirmed transactions can be reversed and should not be considered as «final.»

Vanity Address

Um endereço Dash com um padrão desejável, como um nome.

Virgin Dash

Recebeu como recompensa por explorar um bloco ou executar um Masternode. Estes ainda não foram gastos em qualquer lugar e são «Virgem».

Volatility

A mensuração dos movimentos de preços ao longo do tempo para um ativo financeiro negociado (incluindo Dash).

Wallet

Um método de armazenamento da Dash para uso posterior. Uma carteira contém as chaves privadas associadas aos endereços Dash. O blockchain é o registro dos valores de Dash associados a esses endereços.

Whitepaper

Um whitepaper é um relatório autoritativo ou guia que informa os leitores concisamente sobre uma questão complexa e apresenta a filosofia do organismo emissor sobre o assunto. Destina-se a ajudar os leitores a entender um problema, a resolver um problema ou a tomar uma decisão.

X11

X11 é um algoritmo hashing criado pelo desenvolvedor da Dash, Evan Duffield.

Zero Confirmations

This is a transaction without any confirmations from the blockchain. It is technically reversible (unless InstantSend was used).

vin

A transaction (tx) consists of one or more inputs and one or more outputs. The vin is the list of inputs to the transaction, and vout is the list of outputs. Masternodes require a 1000 DASH vin (exactly that amount) in order to work.

VMN

Virtual Masternode - a standalone masternode emulator in JavaScript that simulates Layer 1-3 Evolution functions for DAP design, development and testing.

Carteiras¶

Sempre que você estiver armazenando objetos com valor no mercado, a segurança é necessária. Isso se aplica a sistemas de troca, bem como economias usando moeda como meio de troca. Enquanto os bancos armazenam saldos em um livro particular, as criptomoedas armazenam saldos sob endereços únicos em um livro público distribuído. As chaves privadas criptográficas para acessar o saldo armazenado em cada endereço público são, portanto, o objeto de valor neste sistema. Esta seção da documentação discute diferentes métodos práticos de manter essas chaves seguras em carteiras, enquanto ainda permanece útil para as necessidades do dia-a-dia.

Por segurança, não é recomendável armazenar fundos significativos em exchanges ou carteiras de software. Se você está com criptomoedas que vale mais que o dispositivo que você usa para armazená-lo, você deve comprar uma carteira de hardware.

Carteira Dash Core¶

A Carteira Dash Core é o lançamento oficial completo do Dash e suporta todos os recursos do Dash à medida que são lançados, incluindo o InstantSend e o PrivateSend, além de um console de RPC e recursos de controle. A Carteira Dash Core (também conhecido como QT wallet, devido à estrutura de software QT usada no desenvolvimento) é uma carteira profissional ou pesada que baixa o blockchain completo (vários GB em tamanho) e pode operar como um nó completo ou masternode no rede. Devido ao requisito de manter uma cópia completa do blockchain, é necessário algum tempo para a sincronização ao iniciar a carteira. Feito isso, os saldos corretos serão exibidos e as funções na carteira podem ser usadas. A Carteira Dash Core está disponível para macOS, Linux, Raspberry Pi e Windows.

Características:

PrivateSend
InstantSend
Criptografar carteira
Controle de moedas e controle de taxas
Gerar QR code e livro de endereços
Comandos de Masternode e votação
backup automatico
Debug console

Documentação disponível:

Instalação¶

Instalar o Dash Core é tão simples quanto acessar https://www.dash.org/ e baixar o arquivo apropriado para o seu sistema, seguindo as etapas de instalação apropriadas para o seu sistema. Guias detalhados estão disponíveis para Linux, macOS e sistemas operacionais Windows abaixo.

Também é possível compilar o Dash Core a partir do código fonte.

Linux Installation Guide¶

This guide describes how to download, verify, install and encrypt the Dash Core wallet for Linux. The guide is written for Ubuntu 16.04 LTS, but the steps should be similar for other Linux distributions.

Downloading da Carteira Dash Core¶

Visit https://www.dash.org/downloads to download the latest Dash Core wallet. In most cases, the website will properly detect which version you need. Click Dash Core button to download the package directly.

O site detecta corretamente a carteira apropriada para o seu sistema

If detection does not work, you will need to manually choose your operating system and whether you need a 32 or 64 bit version. If you are unsure whether your version of Linux is 32 or 64 bit, you can check in Ubuntu under the System menu > About This Computer. For details on how to check this in other versions of Linux, see here.

Ubuntu System Overview. This is a 64 bit system.

Once you know which version you need, download Dash Core to your computer from https://www.dash.org/downloads and save the file you downloaded to your Downloads folder.

Verificando Dash Core¶

Essa etapa é opcional, mas é recomendável verificar a integridade do arquivo que você baixou. Isso é feito verificando o hash SHA256 com o hash publicado pela equipe de desenvolvimento do Core do Dash. Para visualizar o hash publicado, clique no botão Arquivo Hash na página de download da carteira.

Assim que o arquivo do Dash Core e o arquivo de hash tiverem sido baixados, clique duas vezes no arquivo de hash ou exiba-o no navegador e localize o valor de hash do arquivo do Core e e do Core que você baixou.

Visualizando o arquivo hash do Dash Core

This hash value should correspond with the hash value of the file you have downloaded to ensure it is authentic and was not corrupted during transit. To do this, open Terminal, browse to the location where you saved the file, and run the sha256sum command.

Gerando um hash SHA256 para o arquivo baixado

If the hashes match, then you have an authentic copy of Dash Core for Linux.

Extracting Dash Core¶

Dash Core for Linux is distributed as a compressed archive and not an installer. This is because this same archive also contains other files built for running a masternode on a server, for example. In this guide, we will extract the executable file with a graphical user interface (GUI) designed for use by end users as a wallet.

Begin by creating a folder for the Dash Core executable file on the Desktop. Browse to the Desktop (or the location of your choice) and create the folder.

Creating a folder on the Desktop

Renaming the folder to Dash

Next, open the archive by double-clicking on it. The Archive Manager will appear. Browse to the dashcore-0.14.0/bin/ folder and extract the dash-qt file to the Dash folder you created on the Desktop by drag and drop.

The dash-qt file in Archive Manager

The dash-qt file in the Dash folder on the Desktop

To run Dash Core for the first time, open Terminal and browse to the Dash folder on the Desktop, or where you chose to extract the file. Type ./dash-qt to run the file.

Running Dash Core from the Terminal

Na primeira vez que o programa for lançado, você terá a opção de escolher onde deseja armazenar seus dados de blockchain e carteira. Escolha um local com espaço livre suficiente, pois o blockchain pode atingir cerca de 30GB+. Recomenda-se usar a pasta de dados padrão, se possível.

Escolhendo a pasta de dados do Dash Core

O Dash Core será iniciado. Isso levará um pouco mais do que o normal na primeira vez que você executá-lo, já que o Dash Core precisa gerar dados criptográficos para proteger sua carteira.

Iniciando Dash Core

Sincronizando o Dash Core na rede do Dash¶

Depois que o Dash Core for instalado e iniciado com sucesso, você verá a tela de visão geral da carteira. Você notará que a carteira está «fora de sincronia» e a barra de status na parte inferior da janela mostrará o andamento da sincronização.

Dash Core começa a sincronizar com a rede do Dash

Durante esse processo, o Dash Core baixará uma cópia completa do blockchain de outros nós para o seu dispositivo. Dependendo da sua conexão com a internet, isso pode levar muito tempo. Se você vir a mensagem «Nenhuma fonte de bloqueio disponível», verifique sua conexão com a Internet. Quando a sincronização estiver concluída, você verá um pequeno sinal azul no canto inferior direito.

A sincronização do Dash Core está concluída

Agora você pode começar a usar sua carteira para enviar e receber fundos.

Criptografando sua carteira do Dash¶

Depois que sua carteira for sincronizada com a rede do Dash, é altamente recomendável criptografar a carteira com uma senha para impedir o acesso não autorizado. Você deve usar uma senha nova e forte que nunca usou em outro lugar. Anote sua senha e armazene-a em algum lugar seguro ou você será bloqueado fora de sua carteira e perderá acesso a seus fundos.

To encrypt your wallet, click Settings > Encrypt wallet.

Criptografar a carteira do Dash com uma senha

Você será solicitado a inserir e verificar uma senha.

Entering a password

Confirme que você deseja criptografar sua carteira

Quando o processo de criptografia estiver concluído, você verá um aviso de que os backups anteriores da sua carteira não serão mais utilizáveis e será solicitado a encerrar o Dash Core. Quando você reiniciar Dash Core, você verá uma pequena trava azul no canto inferior direito.

Carteira Dash Core totalmente criptografada e sincronizada

Using the Ubuntu Repository to install Dash Core¶

Ubuntu allows you to add third-party repositories to install and update software using the apt command line utility. Dash Core team maintains such a repository, although the software version included here may be older than what is available on the website. To install Dash Core from the repository, open the Terminal and enter the following commands:

sudo add-apt-repository ppa:dash.org/dash
sudo apt update
sudo apt install dashd dash-qt

Guia de instalação no macOS¶

Este guia descreve como baixar, instalar e criptografar a carteira do Dash Core para macOS. O guia foi escrito para o macOS Sierra, mas as etapas devem ser semelhantes para outras versões.

Downloading da Carteira Dash Core¶

Visit https://www.dash.org/downloads to download the latest Dash Core wallet. In most cases, the website will properly detect which version you need. Click Download Installer to download the installer directly.

O site detecta corretamente a carteira apropriada para o seu sistema

If detection does not work, you will need to manually choose your operating system. Go to https://www.dash.org/downloads and select the macOS tab, then click Download Installer. Save the file you downloaded to your Downloads folder.

Verificando Dash Core¶

Essa etapa é opcional, mas é recomendável verificar a integridade do arquivo que você baixou. Isso é feito verificando o hash SHA256 com o hash publicado pela equipe de desenvolvimento do Core do Dash. Para visualizar o hash publicado, clique no botão Arquivo Hash na página de download da carteira.

Assim que o arquivo do Dash Core e o arquivo de hash tiverem sido baixados, clique duas vezes no arquivo de hash ou exiba-o no navegador e localize o valor de hash do arquivo do Core e e do Core que você baixou.

Visualizando o arquivo hash do Dash Core

Esse valor de hash deve corresponder ao valor de hash do arquivo que você baixou para garantir que seja autêntico e não foi corrompido durante o trânsito. Para fazer isso, abra o Terminal, navegue até o local onde você salvou o arquivo e execute o seguinte comando, substituindo a versão pela versão específica do arquivo que você baixou:

shasum -a 256 dashcore-version-osx.dmg

Gerando um hash SHA256 para o arquivo baixado

Se os hashes coincidirem, você terá uma cópia autêntica da Carteira Dash para macOS.

Instalando o Dash Core¶

Abra o Finder e navegue até a pasta Downloads. Em seguida, clique duas vezes no arquivo .dmg que você baixou para descompactá-lo. Aparece uma janela mostrando o conteúdo do arquivo.

Abrindo o arquivo .dmg do Dash Core

Arraste o arquivo do aplicativo Dash Core para a pasta Aplicativos para instalar o Dash Core.

Instalando o Dash Core

Executando o Dash Core pela primeira vez¶

Para executar o Dash Core pela primeira vez, abra o Launchpad ou navegue até a pasta Aplicativos no Finder. Clique duas vezes em Dash Core ou Dash-Qt para iniciar o aplicativo. Você pode ver um aviso sobre a abertura de um aplicativo de um desenvolvedor não identificado. Para resolver esse problema, simplesmente clique com o controle no ícone do aplicativo e escolha Abrir no menu de atalho e clique novamente em Abrir na caixa de diálogo. O aplicativo é salvo como uma exceção às configurações de segurança, e você pode abri-lo no futuro clicando duas vezes nele, assim como em qualquer aplicativo registrado.

Desbloqueando o macOS para a execução do Dash Core

Na primeira vez que o programa for lançado, você terá a opção de escolher onde deseja armazenar seus dados de blockchain e carteira. Escolha um local com espaço livre suficiente, pois o blockchain pode atingir cerca de 30GB+. Recomenda-se usar a pasta de dados padrão, se possível.

Escolhendo a pasta de dados do Dash Core

O Dash Core será iniciado. Isso levará um pouco mais do que o normal na primeira vez que você executá-lo, já que o Dash Core precisa gerar dados criptográficos para proteger sua carteira.

Iniciando Dash Core

Sincronizando o Dash Core na rede do Dash¶

Depois que o Dash Core for instalado e iniciado com sucesso, você verá a tela de visão geral da carteira. Você notará que a carteira está «fora de sincronia» e a barra de status na parte inferior da janela mostrará o andamento da sincronização.

Dash Core começa a sincronizar com a rede do Dash

Durante esse processo, o Dash Core baixará uma cópia completa do blockchain de outros nós para o seu dispositivo. Dependendo da sua conexão com a internet, isso pode levar muito tempo. Se você vir a mensagem «Nenhuma fonte de bloqueio disponível», verifique sua conexão com a Internet. Quando a sincronização estiver concluída, você verá um pequeno sinal azul no canto inferior direito.

A sincronização do Dash Core está concluída

Agora você pode começar a usar sua carteira para enviar e receber fundos.

Criptografando sua carteira do Dash¶

Depois que sua carteira for sincronizada com a rede do Dash, é altamente recomendável criptografar a carteira com uma senha para impedir o acesso não autorizado. Você deve usar uma senha nova e forte que nunca usou em outro lugar. Anote sua senha e armazene-a em algum lugar seguro ou você será bloqueado fora de sua carteira e perderá acesso a seus fundos.

Para criptografar sua carteira, clique em Definições >Criptografar Carteira.

Criptografar a carteira do Dash com uma senha

Você será solicitado a inserir e verificar uma senha.

insira uma senha

Confirme que você deseja criptografar sua carteira

Quando o processo de criptografia estiver concluído, você verá um aviso de que os backups anteriores da sua carteira não serão mais utilizáveis e será solicitado a encerrar o Dash Core. Quando você reiniciar Dash Core, você verá uma pequena trava azul no canto inferior direito.

Carteira Dash Core totalmente criptografada e sincronizada

Agora você pode começar a usar sua carteira para enviar e receber fundos com segurança.

Guia de Instalação no Windows¶

Este guia descreve como baixar, instalar e criptografar a carteira do Dash Core para Windows. O guia foi escrito para o Windows 10, mas as etapas devem ser semelhantes para o Windows XP, Vista, 7 e 8.

Downloading da Carteira Dash Core¶

Visit https://www.dash.org/downloads to download the latest Dash Core wallet. In most cases, the website will properly detect which version you need. Click Download Installer to download the installer directly.

O site detecta corretamente a carteira apropriada para o seu sistema

Se a detecção não funcionar, você precisará escolher manualmente o sistema operacional e se precisa de uma versão de 32 ou 64 bits. Se não tiver certeza se sua versão do Windows é de 32 ou 64 bits, você pode fazer check-in no Windows 10, em Iniciar > Configurações > Sistema > Sobre. Para obter detalhes sobre como verificar isso em outras versões do Windows, consulte aqui.

Em Configurações do Windows, clique em Sistema.

Na seção Sistema, clique em Sobre para visualizar o tipo de sistema. Este é um sistema de 64 bits.

Once you know which version you need, download the Dash Core Installer to your computer from https://www.dash.org/downloads and save the file you downloaded to your Downloads folder.

Verificando Dash Core¶

Essa etapa é opcional, mas é recomendável verificar a integridade do arquivo que você baixou. Isso é feito verificando o hash SHA256 com o hash publicado pela equipe de desenvolvimento do Core do Dash. Para visualizar o hash publicado, clique no botão Arquivo Hash na página de download da carteira.

Baixando o arquivo hash do Dash Core assim que o arquivo do Core do Dash e o arquivo de hash forem baixados, abra o arquivo de hash em um editor de texto ou no navegador e localize o valor de hash do arquivo do Core que você baixou….

Visualizando o arquivo hash do Dash Core

Esse valor de hash deve corresponder ao valor de hash do arquivo que você baixou para garantir que seja autêntico e não foi corrompido durante o trânsito. Para fazer isso, abra o Prompt de Comando, navegue até o local onde você salvou o arquivo e execute o seguinte comando, substituindo a versão pela versão específica do arquivo que você baixou.

certutil -hashfile <dashcore-version-windows>.exe SHA256

Gerando um hash SHA256 para o arquivo baixado

Se os hashes coincidirem, você terá uma cópia autêntica do Dash Core para Windows.

Executando o instalador do Dash Core¶

Clique duas vezes no arquivo para iniciar a instalação do Dash Core.

O instalador do Dash Core na pasta Downloads

Neste momento, você pode ver um aviso do Windows SmartScreen que o aplicativo não é reconhecido. Você pode ignorar este aviso com segurança clicando em Mais informações e em Executar mesmo assim.

Ignorando o Windows SmartScreen para executar o aplicativo. Esse aviso é conhecido como «falso positivo».

O instalador irá guiá-lo através do processo de instalação.

A tela de boas-vindas do instalador do Dash Core

Clique nas telas a seguir. Todas as configurações podem ser deixadas com seus valores padrão, a menos que você tenha um motivo específico para alterar alguma coisa.

Selecione o local de instalação

Selecione a pasta do menu Iniciar

Dash Core está sendo instalado

A instalação está completa

Executando o Dash Core pela primeira vez¶

Quando a instalação estiver concluída, o Dash Core será iniciado imediatamente. Se isso não acontecer, clique em Iniciar > Core do Dash > Core do Dash para iniciar o aplicativo. Na primeira vez que o programa for lançado, você terá a opção de escolher onde deseja armazenar seus dados de blockchain e carteira. Escolha um local com espaço livre suficiente, pois o blockchain pode atingir cerca de 30GB+. Recomenda-se usar a pasta de dados padrão, se possível.

Escolhendo a pasta de dados do Dash Core

O Dash Core será iniciado. Isso levará um pouco mais do que o normal na primeira vez que você executá-lo, já que o Dash Core precisa gerar dados criptográficos para proteger sua carteira.

Iniciando Dash Core

Sincronizando o Dash Core na rede do Dash¶

Depois que o Dash Core for instalado e iniciado com sucesso, você verá a tela de visão geral da carteira. Você notará que a carteira está «fora de sincronia» e a barra de status na parte inferior da janela mostrará o andamento da sincronização.

Dash Core começa a sincronizar com a rede do Dash

Durante esse processo, o Dash Core baixará uma cópia completa do blockchain de outros nós para o seu dispositivo. Dependendo da sua conexão com a internet, isso pode levar muito tempo. Se você vir a mensagem «Nenhuma fonte de bloqueio disponível», verifique sua conexão com a Internet. Quando a sincronização estiver concluída, você verá um pequeno sinal azul no canto inferior direito.

A sincronização do Dash Core está concluída

Agora você pode começar a usar sua carteira para enviar e receber fundos.

Criptografando sua carteira do Dash¶

Depois que sua carteira for sincronizada com a rede do Dash, é altamente recomendável criptografar a carteira com uma senha para impedir o acesso não autorizado. Você deve usar uma senha nova e forte que nunca usou em outro lugar. Anote sua senha e armazene-a em algum lugar seguro ou você será bloqueado fora de sua carteira e perderá acesso a seus fundos.

Para criptografar sua carteira, clique em Definições >Criptografar Carteira.

Criptografar a carteira do Dash com uma senha

Você será solicitado a inserir e verificar uma senha.

insira uma senha

Confirme que você deseja criptografar sua carteira

Quando o processo de criptografia estiver concluído, você verá um aviso de que os backups anteriores da sua carteira não serão mais utilizáveis e será solicitado a encerrar o Dash Core. Quando você reiniciar Dash Core, você verá uma pequena trava azul no canto inferior direito.

Carteira Dash Core totalmente criptografada e sincronizada

Agora você pode começar a usar sua carteira para enviar e receber fundos com segurança.

Interface¶

A Carteira Dash Core é um aplicativo que roda no seu computador e permite que você faça transações na rede do Dash. A maioria das transações é para enviar ou receber Dash, mas também é possível criar mensagens assinadas ou controlar um masternode, por exemplo. A interface da Carteira Dash Core é descrita em detalhes nas seções a seguir.

A janela principal¶

A Carteira Dash Core

A janela do Dash Core está dividida em várias áreas:

Barra de menu
Barra de guias
A area principal
A bara de status

A barra de menu¶

A barra de menus fornece acesso a todas as funções do Dash Core. Existem quatro menus disponíveis:

Arquivo: O menu Arquivo é usado para gerenciar sua carteira, mensagens e endereços.
Configurações: O menu Configurações fornece acesso a opções de criptografia da carteira e configurações gerais de software.
Ferramentas: O menu Ferramentas fornece informações sobre a rede, permite modificar os arquivos de configuração do masternode e outras funções avançadas.
Ajuda: O menu Ajuda se conecta a documentação, guias e declarações legais relacionadas ao Dash Core.

A barra de tabalho¶

A barra de guias é usada para alternar rapidamente entre as principais áreas do Core do Dash. O conteúdo na área principal do Core do Dash muda dependendo de qual guia você selecionou. As seguintes abas estão disponíveis:

A guia Visão geral¶

A aba de visão geral oferece acesso rápido ao seu saldo e transações mais recentes, bem como o recurso PrivateSend e as opções de mistura das moedas.

A guia Visão geral do Dash Core

A parte esquerda da área principal é dividida em duas áreas. A área superior mostra seus saldos:

Disponível: Isso mostra seu saldo líquido atual. Esta é a quantia de Dash que você pode gastar agora.
Pendente: Isso mostra fundos aguardando a conclusão de uma transação.
Imaturo: Isso mostra fundos de pagamentos do masternode ou de mineração que ainda não atingiram o número necessário de confirmações.
Total: Isto é simplesmente os seus fundos disponíveis e pendentes adicionados em conjunto.

A área inferior mostra o status de PrivateSend e permite que você misture seus fundos usando o Dash Masternode Network.

A parte direita da tela mostra suas transações recentes. Estes são identificados por ícones da seguinte forma:

Transações de entrada recentes aparecem em preto, prefixadas por um sinal +
Transações de saída recentes aparecem em vermelho, prefixadas por um sinal -
Os pagamentos de mineração ou masternode recebidos também aparecem em preto

Para mais detalhes sobre o seu histórico de transações, consulte a guia Transações.

A guia Enviar¶

A guia Enviar permite que você envie fundos para outro endereço na rede do Dash. Ele contém campos para inserir o endereço do destinatário, um rótulo para o endereço e a quantia de Dash que você deseja enviar. Opções relacionadas à taxa de transação, InstantSend e PrivateSend também estão disponíveis. Uma visão rápida do seu saldo total também está disponível no canto inferior direito.

A guia Enviar

A guia Receber¶

A guia Receber permite que você crie endereços para receber o Dash. Você pode criar uma solicitação para uma quantia específica de Dash ou incluir uma mensagem específica e enviá-la para outro usuário como um link ou código QR.

A guia Receber

A guia Transações¶

A guia transações mostra todo o histórico de transações de todos os endereços associados à sua carteira. Isso aparece como uma tabela mostrando a hora, o tipo, o rótulo e a quantidade de Dash para cada transação. Você também pode exportar o histórico de transações como um arquivo CSV clicando no botão Exportar no canto inferior direito da janela.

Os ícones na coluna mais à esquerda indicam o status da transação. Uma marca indica que o número recomendado de confirmações foi ultrapassado, enquanto um relógio indica que a transação ainda não atingiu seis confirmações.

A guia Transações

A bara de status¶

A barra de status mostra uma barra de progresso de sincronização e uma linha de ícones de status que indicam o status de sua conexão com a rede do Dash.

A barra de sincronização¶

Esta barra mostra o status de sincronização do Dash Core com a rede do Dash. Toda vez que você abrir o Dash Core, ele começará a baixar os blocos que foram criados no blockchain no tempo desde a última vez que você abriu o aplicativo. Esses blocos são baixados de outros usuários do Dash e masternodes. Se você nunca abriu o aplicativo antes, isso pode significar que vários blocos de anos anteriores precisam ser baixados. Os seguintes status são possíveis:

Nenhuma fonte de bloco disponível: Isso ocorre se a conexão com a Internet estiver inativa ou se as portas exigidas pela Carteira forem bloqueadas por um firewall.
Sincronizando com rede: O Carteira Dash está baixando blocos da rede.
Sincronizando masternodes/pagamentos de masternode/objetos de controle: O Carteira está sincronizando outros dados com a rede da segunda camada.

Quando a sincronização estiver concluída, a barra de progresso desaparecerá e uma marcação aparecerá à direita da barra de status.

Os ícones de status¶

Os ícones de bloqueio indicam o status da sua carteira: bloqueados ou desbloqueados. Você precisa desbloquear sua carteira para enviar fundos ou executar outras ações.

Esses ícones indicam a qualidade de sua conexão com a rede do Dash. Se você não conseguir se conectar devido a problemas de rede, verá o ícone à esquerda. Mais barras indicam mais conexões com seus colegas na rede.

Esses ícones mostram o status de sincronização do Dash Core com a rede. Quando a sincronização estiver concluída, o ícone de atualização ficará azul.

Estes ícones indicam se a sua carteira está sendo executada no modo hierárquico determinístico (HD) ou no modo padrão.

A caixa de diálogo Opções¶

Esta documentação descreve a funcionalidade da caixa de diálogo Opções do Core do Dash, disponível no menu Configurações> Opções no Dash Core.

Aba principal¶

A guia Principal da caixa de diálogo Opções contém configurações relacionadas à inicialização e ao desempenho do aplicativo Dash Core.

A guia Principal da caixa de diálogo Opções da Carteira Dash

Inicie a Carteira Dash Core no login do sistema: Esta opção faz com que o Dash Core inicie automaticamente quando o usuário atual se conecta. Na maioria dos computadores, há apenas uma conta de usuário principal que é conectada automaticamente quando o computador é ligado, portanto, é a mesma coisa que iniciar o Dash Core junto com o sistema operacional.
Tamanho do cache do banco de dados: Esta opção especifica o tamanho do cache do banco de dados na memória. Um valor mais alto resultará em maior desempenho ao adicionar novos blocos ao custo de maior uso de memória. O valor padrão é 100 MB e não deve ser definido abaixo desse nível.
Número de encadeamentos de verificação de script: Esta opção define o número de threads de verificação de script, variando de -4 a 16. Verificação de script é o processo de seguir as instruções registradas no blockchain para garantir a transações são válidas. 0 significa automático e permitirá que a verificação de script seja dimensionada para o número de núcleos disponíveis em seu processador. Definir um número positivo especifica que o Dash Core deve usar esse número de núcleos de processador, enquanto a configuração de um número negativo deixará esse número de núcleos de processador livres.

Guia Carteira¶

A guia Carteira na caixa de diálogo Opções contém configurações relacionadas a como os endereços são gerenciados no aplicativo Dash Core. Na primeira vez que você executar o Dash Core, ele gerará uma nova carteira contendo 1000 endereços exclusivos do Dash. Essa guia permite configurar como esses endereços são usados como entradas com os recursos Coin Control, PrivateSend e Masternode.

A guia Carteira da caixa de diálogo Opções da Carteira Dash

Ativar recursos de controle de moedas: Seu saldo da carteira do Dash Core é, na verdade, a soma total de todos os endereços que contêm saldo associados à sua carteira. Quando você gasta Dash, a Carteira irá retirar quantas entradas forem necessárias para fazer a quantidade desejada de Dash para ser transferida. Esse comportamento pode ser indesejável se você quiser manter um certo equilíbrio em um endereço. O caso de uso mais comum é o requisito de manter o 1000 Dash em um único endereço como garantia para um masternode. A ativação desta opção adicionará um botão chamado Entradas na guia Enviar. Isso fornece acesso à caixa de diálogo Seleção de moeda, que pode ser usada para bloquear, desbloquear e priorizar diferentes endereços em sua carteira. Veja here para uma explicação mais detalhada sobre Coin Control.
Mostrar guia Masternodes: Ativar essa opção faz com que a Carteira exiba uma guia adicional do Masternodes à direita da guia Transações. Esta opção requer que você reinicie o aplicativo da Carteira. A aba Masternodes pode ser usada para gerenciar interações (iniciar, parar, verificar status, etc.) com masternodes controlados por essa carteira. Essa guia é um recurso avançado não exigido pelos usuários que não operam um masternode na rede do Dash.
Ativar interface avançada do PrivateSend: A ativação dessa opção altera a interface de mistura do PrivateSend na guia Visão geral da carteira do Dash Core para incluir mais opções, como o Try Mix e a porcentagem de conclusão. Veja here para uma explicação completa de como usar o PrivateSend.
Avisar se o PrivateSend estiver ficando sem chaves: Habilitar esta opção fará com que a Carteira exiba um aviso quando o conjunto original de 1000 endereços estiver acabando, o que pode afetar a mixagem do PrivateSend. Toda vez que um evento de mixagem acontece, até 9 de seus endereços são usados. Isso significa que esses 1000 endereços duram cerca de 100 eventos de mistura. Quando 900 deles são usados, sua carteira precisa criar mais endereços. Isso só pode ser feito, no entanto, se você tiver backups automáticos ativados. Consequentemente, os usuários que tiverem backups desativados também terão o PrivateSend desativado.
Ativar multi-sessão do PrivateSend: Normalmente, a mixagem do PrivateSend é concluída em várias rodadas consecutivas, cada uma usando um único masternode. Ativar essa opção permite multi-sessão, o que significa que você pode usar vários servidores masternode ao mesmo tempo, aumentando muito a velocidade do processo de mixagem ao custo de criar mais endereços e, portanto, exigindo backups de carteira mais frequentes. Esse recurso é experimental no Dash Core 12.1.5.
Gastar mudança não confirmada: Quando esta opção está ativada, a carteira do Dash Core permite que você gaste imediatamente as alterações de transações anteriores que foram transferidas internamente entre os endereços associados à mesma carteira. Isso é possível mesmo que a transação ainda não tenha sido confirmada, porque a carteira sabe que ela será confirmada, uma vez que criou a própria transação interna. Deixar essa opção ativada permite criar novas transações, mesmo se as transações anteriores ainda não tiverem sido confirmadas.
PrivateSend rodadas para usar: Use esta opção para controlar o número de rodadas de mixagem do PrivateSend a serem executadas para o saldo escolhido. Cada rodada de mixagem usa um novo masternode. Quanto maior o número de rodadas, mais difícil se torna rastrear o Dash até seu endereço original. Isso é à custa de mais tempo necessário para misturar e taxas potencialmente mais altas. Veja aqui uma explicação completa de como usar o PrivateSend.
Amount of Dash to keep mixed: This option allows you to specify how much Dash should be kept on balance in a ready-to-use mixed state, meaning it has already passed through the PrivateSend mixing process. If you do not have sufficient Dash available in your balance of unlocked inputs, the amount will be automatically reduced to the available balance and shown in red in the PrivateSend interface on the Overview tab.

Guia Rede¶

Essa guia inclui opções relacionadas a como sua conexão com a rede do Dash é feita.

A guia Rede da caixa de diálogo Opções do Core do Dash

Mapear porta usando o UPnP: Esta opção faz com que o Dash Core tente automaticamente abrir e mapear a porta do cliente no seu roteador usando o UPnP (Universal Plug and Play). Esse recurso é suportado pela maioria dos roteadores domésticos modernos e permite que você se conecte à rede do Dash sem fazer nenhuma configuração especial em seu roteador.
Permitir conexões de entrada: Esta opção faz com que seu cliente aceite conexões externas. Como o Dash é uma rede peer-to-peer e o Dash Core é considerado um cliente completo porque armazena uma cópia do blockchain no seu dispositivo, habilitar essa opção ajuda outros clientes a sincronizar o blockchain e a rede através de seu nó.
Conectar-se por meio do proxy SOCKS5 (proxy padrão): Essas opções permitem que os usuários em uma intranet solicitem que um proxy atinja a Internet mais ampla para especificar o endereço de seu servidor proxy para retransmitir solicitações para a Internet. Entre em contato com o administrador do sistema ou verifique as configurações de rede no seu navegador da Web se não conseguir conectar-se e suspeitar que um proxy possa ser a origem do problema.
Use o proxy SOCKS5 separado para alcançar os peers por meio de serviços ocultos do Tor: Essas opções permitem que você especifique um servidor proxy adicional projetado para ajudá-lo a se conectar a pontos na rede Tor. Esta é uma opção avançada para maior privacidade e requer um proxy Tor em sua rede. Para mais informações sobre o Tor, veja here.

Aba Window¶

Esta opção contém opções que regem o comportamento da janela do aplicativo Dash Core no Microsoft Windows.

A guia Window da caixa de diálogo Opções do Core do Dash

Ocultar ícone da bandeja: Quando esta opção está ativada, o Dash Core não exibe um ícone na bandeja do sistema. Esta opção não pode ser selecionada ao mesmo tempo que Minimize para a bandeja em vez da barra de tarefas.
Minimizar para a bandeja em vez da barra de tarefas: Quando esta opção está ativada e a janela do Dash Core é minimizada, ela não aparecerá mais na sua barra de tarefas como uma tarefa em execução. Em vez disso, o Dash Core continuará funcionando em segundo plano e poderá ser reaberto a partir do ícone do Dash na bandeja do sistema (a área ao lado do relógio do sistema). Esta opção não pode ser selecionada ao mesmo tempo que Ocultar ícone da bandeja.
Minimize na barra: Quando esta opção está ativada, clicar no botão X no canto superior direito da janela fará com que o Core do Dash minimize ao invés de fechar. Para fechar completamente o aplicativo, selecione Arquivo > Sair.

Guia de exibição¶

Essa guia contém opções relacionadas à aparência da janela da Carteira Dash.

A guia Exibir da caixa de diálogo Opções da Carteira Dash

Idioma de interface do usuário: Selecione seu idioma preferido neste menu suspenso. Alterar o idioma exige que você reinicie o aplicativo Dash Core.
Tema da interface do usuário: Você pode usar essa opção para selecionar um tema diferente que governa a aparência da janela do Core do Dash. Toda a funcionalidade é idêntica sob os diferentes temas, embora o tema padrão do Dash-light seja mais recente e com maior probabilidade de funcionar sem nenhum artefato de exibição.
Unidade para mostrar valores em: Isso permite que você altere a unidade padrão de moeda na Carteira Dash para mDASH, µDASH ou duffs. Cada unidade desloca o separador decimal três lugares para a direita. Os Duffs são a menor unidade na qual o Dash pode ser separado.
Dígitos decimais: Essa opção permite que você selecione quantos dígitos decimais serão exibidos na interface do usuário. Isso não afeta a contabilização interna de suas entradas e saldo.
URLs de transação de terceiros: Esta opção permite que você especifique e um site externo para inspecionar um determinado endereço ou transação no blockchain. Vários exploradores blockchain estão disponíveis para isso. Para usar este recurso, insira o URL do seu explorador blockchain favorito, substituindo %s pelo ID da transação. Você poderá então acessar este blockchain explorer diretamente do Dash Core usando o menu de contexto de qualquer transação.

A Ferramenta de Diálogo¶

Esta documentação descreve a funcionalidade da caixa de diálogo Ferramentas principais do Dash, disponível no menu Ferramentas na Carteira Dash Core.

Guia Informações¶

A guia Informações da caixa de diálogo Ferramentas principais do Dash

Geral: Esta seção exibe informações sobre o nome e a versão do cliente e do banco de dados e o local do diretório de dados do aplicativo atual.
Rede: Esta seção exibe informações e estatísticas sobre a rede à qual você está conectado.
Block chain: Esta seção mostra o status atual do blockchain.
Pool de memória: Esta seção mostra o status do pool de memória, que contém transações que ainda não puderam ser gravadas em um bloco. Isso inclui as transações criadas desde o último bloco e as transações que não puderam ser inseridas no último bloco porque estavam cheias.
Abra o arquivo de log de depuração: Este botão abre debug.log do diretório de dados do aplicativo. Este arquivo contém a saída do Dash Core, que pode ajudar a diagnosticar erros.

Guia Console¶

A guia Console fornece uma interface com o console Dash Core RPC (chamada de procedimento remoto). Isto é equivalente ao comando dash-cli nas versões headless do Dash, como dashd sendo executado em um masternode. Clique no ícone vermelho `` –`` para limpar o console, e veja a documentação detalhada dos comandos RPC para aprender sobre os possíveis comandos que você pode emitir.

A guia Console da caixa de diálogo ferramentas da Carteira Dash Core

Guia Tráfego de rede¶

A guia Tráfego de rede mostra um gráfico do tráfego enviado e recebido pelos colegas na rede ao longo do tempo. Você pode ajustar o período usando o controle deslizante ou Limpar o gráfico.

A guia Tráfego de Rede da caixa de diálogo Ferramentas da Carteira Dash

Guia Peers¶

A guia «Pares» mostra uma lista de outros nós completos conectados ao seu cliente do Dash Core. O endereço IP, versão e tempo de ping estão visíveis. A seleção de um par mostra informações adicionais sobre os dados trocados com esse peer.

A aba Peers da caixa de diálogo ferramentas da Carteira Dash Core

Guia de reparo da carteira¶

A guia Reparar Carteira oferece vários comandos de inicialização para restaurar uma carteira a um estado funcional. Selecionar qualquer um desses comandos reiniciará a Carteira Dash Core o com a opção de linha de comando especificada.

A aba de reparo da carteira da caixa de diálogo ferramentas da Carteira Dash Core

Carteira em Salvamento: A carteira de salvamento assume que o wallet.dat está corrompido e não pode ser lido. Ele faz uma cópia de wallet.dat para wallet.<date>.bak e o verifica para tentar recuperar qualquer chave privada. Verifique seu arquivo debug.log depois de executar a carteira de recuperação e procure as linhas que começam com «Salvage» para obter mais informações sobre as operações concluídas.
Rescanear arquivos da blockchain: Rescans o blockchain já baixado para quaisquer transações que afetem as contas contidas na carteira. Isso pode ser necessário se você substituir seu arquivo wallet.dat por uma carteira diferente ou um backup - a lógica da carteira não saberá sobre essas transações, portanto, uma nova verificação é necessária para determinar os saldos.
Recuperar transações: Os comandos de recuperação de transações podem ser usados para remover transações não confirmadas do conjunto de memórias. Sua carteira irá reiniciar e redigitalizar o blockchain, recuperando transações existentes e removendo transações não confirmadas. As transações podem ficar paradas em um estado não confirmado se houver um conflito nas versões do protocolo na rede durante a mixagem do PrivateSend, por exemplo, ou se uma transação for enviada com taxas insuficientes quando os blocos estiverem cheios.
Atualizar formato de carteira: Este comando está disponível para carteiras muito antigas, onde é necessária uma atualização para a versão de carteira, além de uma atualização para o software de carteira. Você pode ver sua versão atual da carteira executando o comando getwalletinfo no console.
Recontruir Indice: Descarta o blockchain atual e incorpora os índices (o banco de dados de saídas de transação não gastas) e o recria a partir dos arquivos de bloco existentes. Isso pode ser útil para recuperar saldos ausentes ou emperrados.

Enviando e recebendo¶

A sua carteira do Dash Core está associada a vários endereços exclusivos que podem ser usados para enviar e receber o Dash. Cada endereço possui seu próprio saldo e a soma de todos os seus saldos é o que aparece na guia Visão geral. Quando você envia o Dash, sua carteira transfere automaticamente fundos de quantos endereços forem necessários para o endereço de destino, que é controlado por outro usuário do Dash e associado à sua carteira. Você pode controlar quais endereços você usa usando o recurso Coin Control.

Quando você confirma uma transação, o Dash Core irá inserir a transação em um bloco, que será então adicionado ao blockchain para outros clientes confirmarem. Uma transação é geralmente considerada confirmada uma vez que seis blocos foram adicionados após o bloco contendo sua transação, embora os pagamentos de masternode e mineração sejam liberados somente após 101 blocos. Observe que um processo diferente é usado para transações InstantSend e PrivateSend.

Os endereços do Dash têm 34 caracteres e começam com um X maiúsculo.

Enviando Dash¶

Você pode usar o Dash Core para enviar o Dash da sua conta para outro usuário. O usuário que recebe lhe fornecerá um endereço do Dash para o qual você deverá enviar os fundos. Clique na guia Enviar na barra de guias e insira o endereço de destino no campo Pagar para.

A guia Envio do Dash Core

Você também pode usar os três ícones à direita do campo Pagar para para selecionar um endereço usado anteriormente, cole um endereço da área de transferência ou limpe o endereço atual. Se este for um novo endereço, você pode inserir um nome para o endereço no campo Etiqueta para ajudar a identificá-lo novamente mais tarde. Por fim, insira a quantia de Dash que você deseja transferir no campo Quantidade.

As outras opções estão relacionadas a taxas e PrivateSend/InstantSend. Você pode escolher se deseja pagar a taxa de rede além do valor enviado ou subtrai-la do valor enviado. Você também pode aumentar sua taxa para incentivar os nós na rede a priorizar sua transação. A escolha do InstantSend tem um efeito semelhante, mas na verdade depende de um mecanismo diferente na rede da segunda camada para acelerar o tempo de transação. A escolha do PrivateSend enviará o Dash de um endereço que tenha sido previamente misturado. Você pode descobrir mais sobre o PrivateSend e o InstantSend aqui.

Vamos tentar um exemplo. Digamos que você tenha recebido uma fatura que agora deseja pagar com o Dash. O escritor da fatura incluiu um endereço de Dash, que pode ser visto na seguinte janela começando com Xpa. A fatura é para 2.45 Dash, que você preenche no campo Valor.

A guia Enviar preenchida para uma transação

Depois de inserir o endereço de destino e o valor, clique no botão Enviar. Se você criptografou sua carteira, será necessário inserir sua senha para desbloquear a carteira.

Digitando a senha para desbloquear a carteira

Finalmente, você recebe uma confirmação final e a chance de cancelar sua transação de envio antes que o Dash Core processe a transação no blockchain.

Janela de confirmação final

Se você responder com Sim, sua transação será processada. Seu sistema operacional pode exibir uma notificação e a transação aparecerá na guia Transações, onde você poderá monitorar seu progresso.

O Windows 10 enviou notificação de confirmação de transação

Observe que o valor da transação aumentou em .000045 Dash. Esta é a taxa de transação. Na próxima seção, veremos como esse procedimento se parece no lado do recebimento.

Recebendo Dash¶

Para receber o Dash, primeiro você deve criar um endereço de recebimento para dar à parte de envio. Para fazer isso, clique em Arquivo > Recebendo Endereços. A janela Recebendo endereços é exibida.

A janela de endereços de recebimento

Copie um endereço existente clicando no endereço e, em seguida, no botão Copiar ou crie um novo endereço clicando no botão Novo. Você também pode editar um endereço existente clicando com o botão direito e selecionando Editar endereço no menu de contexto. Dê este endereço para a pessoa que lhe enviará o Dash. Sua carteira não precisa estar aberta para receber fundos, mas se estiver, você pode ver a transação chegar em tempo real. Isso ocorre porque sua carteira sempre procura novos blocos no blockchain quando ela está aberta e reconhece uma nova transação envolvendo seu endereço de recebimento quando ele ocorre.

O Windows 10 recebeu notificação de confirmação de transação

Depois de receber o pagamento, você poderá ver o saldo na guia Visão geral e na guia Transações.

A transação recebida

Como criar novos endereços de recebimento no DashQT

PrivateSend and InstantSend¶

PrivateSend¶

This documentation describes how to use Dash Core to send Dash privately. PrivateSend, released as DarkSend in RC4 of the DarkCoin client and rebranded to PrivateSend in May 2016, is a trustless method of running a sequence of transactions (known as «mixing») such that an external observer is unable to determine the source of funding when a PrivateSend transaction is created. This gives your Dash the same privacy properties as cash withdrawn from an ATM, for example. The mixing and denomination process is seamless, automatic, and requires no intervention on the part of the user. The current implementation of PrivateSend in the Dash Core wallet allows any amount of Dash to be mixed for later use in PrivateSend transactions. As of December 2018, PrivateSend is not currently available in other Dash wallets.

O conhecimento do número exato de rodadas de mistura do PrivateSend usado em qualquer transação do PrivateSend tem um efeito quantificável sobre a confiança que um adversário pode ter ao tentar adivinhar a origem de uma transação do PrivateSend. Por esse motivo, o número recomendado (e padrão) de rodadas de mistura do PrivateSend é definido como quatro.

Você pode ler mais sobre teoria e processos do PrivateSend aqui.

Configuração¶

Abra sua carteira do Dash Core, vá para Definições e selecione Opções. Vá para guia Carteira.
Next to PrivateSend rounds to use, enter a value between 1-16. Each round of PrivateSend performs one denominated fund mixing transaction. Higher numbers of rounds increase your overall level of privacy while decreasing the chance of detection via node collusion. 16 is the highest number of rounds currently available.

NOTE: To prevent system abuse, an average of one in ten rounds of masternode mixing incurs a fee of .0001 DASH.
Enter a target value for Amount of Dash to keep mixed. This value provides a lower boundary on the final amount of funds to be mixed. Depending on how the client splits your wallet balance, you may end up with denominated inputs whose sum total is greater than the target amount. In this case the client will use all existing denominated inputs in the PrivateSend process. The final mixed amount may be higher than your target, but should be close.
Clique em OK para salvar as configurações.
O PrivateSend é desativado por padrão quando você abre a carteira. Ele só será iniciado depois que você definir o número de rodadas e o número de Dashs para misturar nas configurações e clicar em Iniciar mixagem na guia Visão geral da sua carteira.

Iniciar Mixing¶

O processo PrivateSend é iniciado clicando no botão Iniciar mixagem na guia Visão geral da carteira do Dash Core. A mixagem é possível depois que as seguintes condições forem atendidas:

The wallet contains sufficient non-mixed funds to create the minimum required denominated values
O usuário não desativou o PrivateSend na caixa de diálogo Opções
The target value for mixed Funds in the Options dialog is greater than zero

Se a sua carteira estiver criptografada (altamente recomendada), você será solicitado a digitar sua senha da carteira. Ative a caixa de seleção Somente para mixagem via PrivateSend para desbloquear a carteira somente para mixagem.

Digitar uma senha somente para o PrivateSend

Isso desbloqueará sua carteira e o processo de mixagem do PrivateSend será iniciado. A carteira permanecerá desbloqueada até a conclusão da mixagem do PrivateSend, quando será bloqueada automaticamente.

Interface do PrivateSend depois de clicar no botão Iniciar mixagem. Observe que o status é ativado.

O PrivateSend começará a criar transações e seu saldo do PrivateSend aumentará gradualmente. Esse processo pode levar algum tempo, então seja paciente. Você pode monitorar o processo com mais detalhes, conforme descrito na seção a seguir.

Qualquer uma das seguintes ações interromperá o processo de mixagem. Como as transações são atômicas (elas ocorrem completamente ou não ocorrem), deve ser possível interromper com segurança a mixagem do PrivateSend a qualquer momento.

Clicando no botão Parar Mixagem na guia Visão Geral
Fechar o cliente antes da conclusão da mixagem do PrivateSend
Enviando fundos do PrivateSend da carteira antes que as rodadas do PrivateSend sejam concluídas
Desativando o PrivateSend antes que o processo seja concluído

Monitorando Mixagem¶

Se você quiser monitorar o PrivateSend com mais detalhes, é necessário ativar alguns recursos avançados da carteira. Vá para Definições, selecione Opções e vá para a guia Carteira. Marque as caixas ao lado das opções Ativar recursos de controle de moeda e Ativar interface avançada de PrivateSend.

Ativando opções avançadas para PrivateSend nas configurações da carteira do Dash Core

Isso permitirá que você monitore o progresso e veja quais operações individuais o PrivateSend está executando em segundo plano.

Monitorando o progresso do PrivateSend

Since PrivateSend mixing creates a lot of new address keys to send and receive the mixed denominations, you may receive a warning when the number of remaining keys runs low. This is nothing to be worried about, since the wallet will simply create more keys as necessary. However, these keys will not exist in any previous backups of your wallet. For this reason, it is important to backup your wallet again after mixing is complete.

Você também pode monitorar o progresso do PrivateSend visualizando as transações criadas pelo processo de mixagem na guia Transações.

Transações criadas pelo PrivateSend na guia Transações

A tabela a seguir descreve as transações relacionadas ao PrivateSend exibidas na coluna Tipo da guia Transações:

Tipo de transação PrivateSend	Descrição da transação
PrivateSend Faça Entradas Colaterais (Mixing)	Os fundos da carteira foram transferidos para entradas colaterais que serão utilizadas para efectuar pagamentos colaterais. Isso é feito para minimizar a rastreabilidade das garantias.
PrivateSend Cria Denominações (Mixing)	Os fundos da carteira foram divididos em denominações do PrivateSend (Passo 1 aqui)
PrivateSend Denominação (Mixing)	Uma transação foi enviada para um masternode para participar de uma sessão de mixagem (Passo 3 aqui)
Pagamento de garantia por parte do PrivateSend (Mixing)	A garantia da sessão de mistura foi reivindicada. Esta taxa é cobrada em ~10% das sessões de mixagem para evitar ataques de spam.
PrivateSend (Gastos)	Fundos mistos foram usados para enviar um pagamento para alguém. Nota: Ao contrário dos 4 tipos de transação anteriores, esta não é uma transação do processo de mixagem.

You can also use the coin control feature to view which addresses hold mixed denominations ready to be used for PrivateSend transactions. Go to the Send tab of your wallet and click Inputs to view the possible input addresses for your transactions. You can see how each address holds given denominations of mixed Dash, and how many rounds of mixing have been completed. This is to ensure that an efficient combination of addresses can be used as inputs in PrivateSend transactions without too much change, since amount in a PrivateSend transaction must be rounded up to completely spend all inputs. The current minimum balance for an input used in a PrivateSend transaction is 0.00100010 DASH.

Caixa de diálogo seleção de moedas mostrando os endereços que mantêm os saldos mistos do PrivateSend em diferentes denominações

Pagando com PrivateSend¶

You can only use PrivateSend for payments once you have mixed enough Dash to make up the amount you are trying to send. Because the mixing process takes time, it must be done in advance before you create the send transaction. A PrivateSend transaction is effectively the same as any other transaction on the blockchain, but it draws only from input addresses where the denomination has previously been mixed to ensure privacy of funds. Because several input addresses are usually required to make up the amount you are trying to send, a PrivateSend transaction will usually take up more space (in kilobytes) on the blockchain, and therefore will be charged a slightly higher fee.

To send a payment using PrivateSend, go to the Send tab of the Dash Core wallet and enable the PrivateSend option. The balance displayed will change to show your PrivateSend balance instead of the total balance. You can then enter the Pay To address, Label, Amount and click Send as usual. Your payment will be rounded up to completely spend the lowest possible denomination of mixed balance available (currently to the nearest 0.001 DASH). You will be prompted to enter your password and receive a detailed breakdown of the fee structure for PrivateSend before sending.

Dash Core pronto para enviar uma transação do PrivateSend. Observação O PrivateSend está ativado e o valor a ser enviado é menor que o saldo do PrivateSend disponível

InstantSend¶

introdução¶

Esta documentação descreve como usar o InstantSend para enviar instantaneamente fundos para qualquer outro usuário do Dash em todo o mundo. O Dash InstantSend é suportado por muitas carteiras e fornecedores, incluindo (mas não limitado a) o seguinte:

Carteira Dash Core
Carteira Dash Android
Carteira Dash iOS
Minha Carteira Dash
Kraken
Bitrefill
e muito mais…

Você pode ler mais sobre teoria e processos do InstantSend aqui.

Pagando com InstantSend¶

InstantSend functions by setting a flag on the transaction, causing deterministic selection of a quorum of 10 masternodes for each input spent in an InstantSend transaction. The masternodes examine the input, and if a majority determines it has at least six confirmations, they then accept the transaction. The input is then locked until the transaction has been confirmed in six mined blocks, at which point the output can be used as an input in another InstantSend transaction. This differs from inputs used in normal transactions, which can be spent after just one confirmation regardless of whether the Dash was received using InstantSend or not. A higher fee will be charged for InstantSend transactions with more than four inputs, according to the fee schedule. Note that the receiving wallet must also be aware of InstantSend in order to be able to immediately continue with the transaction or display an appropriate notification that the transaction should be considered locked. If the receiving wallet is not aware of InstantSend, it will simply appear as a normal transaction and you will need to wait for standard block confirmations.

Para pagar com o InstantSend, basta marcar a caixa de seleção relevante no seu aplicativo. As capturas de tela a seguir indicam onde essa configuração pode ser encontrada nas carteiras do Dash Core, iOS e Android.

Carteiras Dash mostrando a opção InstantSend

Backup e restauração de carteira¶

Backup¶

Esta documentação descreve como fazer o backup seguro do seu arquivo de carteira para armazenamento seguro, caso seu computador ou laptop seja danificado ou perdido. O Dash Core armazena todos os dados necessários para controlar seus endereços do Dash em um único arquivo chamado wallet.dat. Esta carteira está no formato Berkeley DB e armazena os pares de chaves criptográficas privadas/públicas usadas para gerenciar seus saldos no blockchain do Dash. O Dash Core torna transparente a maioria dessas operações e até gera backups automáticos do seu arquivo de carteira, caso esteja corrompido, mas o usuário é responsável por garantir que esses backups sejam armazenados em um local seguro. Se você perder o acesso ao seu arquivo da carteira, perderá permanentemente o acesso ao seu Dash.

É importante considerar que, se você não tiver criptografado sua carteira usando o item de menu Configurações> Criptografar Carteira, qualquer pessoa com acesso ao arquivo wallet.dat com backup terá acesso total ao seu Dash. Se você optar por criptografar sua carteira, não armazene a senha no mesmo local que o arquivo wallet.dat, especialmente se estiver salvando o backup na nuvem.

Backup do Dash Core¶

Em primeiro lugar, nunca copie o seu arquivo wallet.dat enquanto o Dash Core estiver aberto. Sempre use o menu Arquivo > Backup Wallet se a carteira estiver aberta. Quando você seleciona este item de menu, uma caixa de diálogo aparecerá para especificar onde o arquivo deve ser salvo. Digite um nome para o arquivo, selecione um local e clique em Salvar. O exemplo abaixo mostra como salvar o arquivo em um pendrive. Mantenha este arquivo em um local fisicamente separado para o seu computador.

Fazendo backup da carteira do Dash Core no menu Arquivo

Backup copiado wallet.dat¶

Se o Dash Core não estiver rodando, você também pode fazer o backup da sua carteira simplesmente copiando o arquivo wallet.dat para outro local. Este arquivo está localizado na pasta de dados DashCore. Você recebeu a opção de especificar o local dessa pasta durante a instalação, mas, por padrão, a pasta está nos seguintes locais em sistemas operacionais diferentes:

Windows
```
C:\Users\YourUserName\Appdata\Roaming\DashCore
```
Você pode acessar esta pasta diretamente precionando a tecla Windows + R e digitando %APPDATA%\DashCore
Linux
```
/home/YourUserName/.dashcore
```
Você pode acessar essa pasta diretamente digitando cd ~/.dashcore at the terminal or ~/.dashcore na barra de caminho usando o Ir > Endereço da Pasta… item do menu em arquivos
macOS
```
/Users/YourUserName/Library/Application Support/DashCore
```
Você pode acessar essa pasta diretamente digitando cd ~/Library/Application Support/DashCore no terminal ou ~/Library/Application Support/DashCore no diálogo no Ir > Ir Para Pastar

Assegure-se de que o Dash Core não esteja em execução e simplesmente copie o arquivo wallet.dat desta pasta para outra pasta da maneira normal para o seu sistema operacional. O exemplo abaixo mostra a cópia do arquivo em um pendrive USB usando o simples arrastar e soltar enquanto mantém pressionada a tecla Ctrl em um sistema Windows. Na maioria dos sistemas operacionais, você também pode clicar com o botão direito do mouse no arquivo e selecionar Copiar e, em seguida, selecione Colar na pasta de destino. Mantenha este arquivo em um local fisicamente separado para o seu computador.

Fazendo o backup do wallet.dat copiando para outra pasta

Backups Automatico¶

Toda vez que você abrir o Dash Core, ele criará automaticamente uma cópia de backup de wallet.dat na pasta dashcore/backups. Até 10 backups podem ser mantidos por padrão, e o backup mais antigo será excluído à medida que cada novo backup adicional é criado. Você pode modificar o número de backups mantidos usando o parâmetro -createwalletbackups = n na linha de comando ou no dash.conf. Definir esse valor como 0 desativa completamente os backups.

Você pode visualizar a pasta de backups automáticos navegando até a pasta DashCore no local especificado acima para wallet.dat e abrindo a pasta de backups ou selecionando Ferramentas> Mostrar backups automáticos no menu do Dash Core. Como esses arquivos não estão ativos quando o Dash Core está em execução, você pode copiá-los com segurança a qualquer momento. Eles também são um backup útil se os arquivos originais na pasta DashCore forem corrompidos devido ao desligamento incorreto do aplicativo Dash Core.

Restaurar¶

Para restaurar um backup, instale o Dash Core no sistema (ou pare-o, se já estiver instalado) e renomeie o arquivo wallet.dat existente na pasta DashCore.

Renomeia o arquivo wallet.dat antigo para wallet.old na pasta DashCore

Em seguida, copie o arquivo da carteira de backup para a pasta DashCore e verifique se ele está nomeado wallet.dat. Agora, quando você iniciar o Dash Core novamente, ele carregará a nova carteira. Não substitua wallet.dat enquanto o Core Core estiver em execução, pois isso ira corromper os dados!

Copiando o arquivo de backup para a pasta DashCore e renomeá-lo para wallet.dat

Considerações sobre armazenamento de backup¶

Qualquer backup depende, até certo ponto, da existência do software capaz de ler os dados em algum momento no futuro. Como tal, é recomendável armazenar uma cópia do software usado para criar o backup junto com o próprio arquivo de backup. Nesse caso, isso seria uma cópia da versão do Core do Dash que você usou para criar o backup.

O arquivo wallet.dat deve ser criptografado usando uma senha definida a partir do Configurações> Criptografar Carteira. No entanto, isso só impede que alguém com acesso ao arquivo crie transações, e não abra o arquivo. Você também pode armazenar o arquivo em outro local criptografado, como um dispositivo USB usando o BitLocker no Windows, LUKS no Linux ou FileVault no macOS. Também é possível criar imagens de disco ou arquivos zip com criptografia - Para mais informações sobre locais criptografados, veja aqui.

Você decide aonde armazenar este arquivo. Pode ser em sua casa, em um cofre em um banco, em um contêiner à prova d’água ou à prova de fogo ou em armazenamento na nuvem, como o Google Drive, o Dropbox ou o iCloud. Considere onde você armazenará as senhas necessárias para restaurar o acesso à carteira (em sua cabeça, em papel, em um gerenciador de senhas, etc.) e quem pode precisar acessar a senha no futuro.

Finalmente, é importante entender que wallet.dat em si é uma maneira relativamente perigosa de armazenar grandes quantidades de fundos - é simplesmente um arquivo de banco de dados que armazena chaves privadas. Embora a conveniência de armazenar um arquivo de carteira diretamente seja boa para holdings menores, é mais seguro armazenar grandes quantidades de Dash em um único endereço predefinido de modo que você tenha acesso garantido por meio de qualquer software que suporte o protocolo, em vez de um específico. Se estiver interessado, leia mais sobre carteiras de papel, onde a chave privada pode ser impressa diretamente ou também criptografada usando o BIP38 para armazenamento seguro.

Verificando backups¶

Não há procedimento fixo para verificar seu backup, mas você deve testá-lo pelo menos uma vez para ter certeza de que funciona. Se você tiver uma cópia simples do arquivo, tente restaurá-lo para a sua pasta atual DashCore e inicie o Dash Core para ter certeza de que ele será aberto sem erros. Se você decidiu armazenar o arquivo em um arquivo zip criptografado, certifique-se de descompactá-lo e abrir corretamente no Dash Core. Resumindo, certifique-se de que você (ou a pessoa em quem você confia eventualmente passar por esse processo para você) pode realmente reverter seu processo de backup para obter acesso ao seu Dash, em vez de confiar no fato de que esse processo deveria ser reversível teoricamente.

Arguments and commands¶

All command-line options (except for -datadir and -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file. The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the # character.

The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, dash-qt (or dashd) will look for a file named dash.conf in the dash data directory, but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments.

Plataforma

Caminho para a pasta de dados

Typical path to configuration file

Linux

~/

/home/username/.dashcore/dash.conf

macOS

~/Library/Application Support/

/Users/username/Library/Application Support/DashCore/dash.conf

Windows

%APPDATA%

(Vista-10) C:\Users\username\AppData\Roaming\DashCore\dash.conf

(2000-XP) C:\Documents and Settings\username\Application Data\DashCore\dash.conf

Note: if running Dash in testnet mode, the sub-folder testnet3 will be appended to the data directory automatically.

Command line arguments¶

These commands are accurate as of Dash Core version 0.13.0.0.

dashd
dash-qt
dash-cli
dash-tx

dashd¶

Dash Core Daemon

Usage¶

dashd [options]: Start Dash Core Daemon

Options¶

`--help`	Print this help message and exit
`--version`	Print version and exit
`--alerts`	Receive and display P2P network alerts (default: 1)
`--alertnotify=<cmd>`
	Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)
`--blocknotify=<cmd>`
	Execute command when the best block changes (%s in cmd is replaced by block hash)
`--assumevalid=<hex>`
	If this block is in the chain assume that it and its ancestors are valid and potentially skip their script verification (0 to verify all, default: 00000000000000b4181bbbdddbae464ce11fede5d0292fb63fdede1e7c8ab21c, testnet: 00000ce22113f3eb8636e225d6a1691e132fdd587aed993e1bc9b07a0235eea4)
`--conf=<file>`	Specify configuration file (default: dash.conf)
`--daemon`	Run in the background as a daemon and accept commands
`--datadir=<dir>`
	Specify data directory
`--dbcache=<n>`	Set database cache size in megabytes (4 to 16384, default: 100)
`--loadblock=<file>`
	Imports blocks from external blk000??.dat file on startup
`--maxorphantx=<n>`
	Keep at most <n> unconnectable transactions in memory (default: 100)
`--maxmempool=<n>`
	Keep the transaction memory pool below <n> megabytes (default: 300)
`--mempoolexpiry=<n>`
	Do not keep transactions in the mempool longer than <n> hours (default: 72)
`--blockreconstructionextratxn=<n>`
	Extra transactions to keep in memory for compact block reconstructions (default: 100)
`--par=<n>`	Set the number of script verification threads (-1 to 16, 0 = auto, <0 = leave that many cores free, default: 0)
`--pid=<file>`	Specify pid file (default: dashd.pid)
`--prune=<n>`	Reduce storage requirements by enabling pruning (deleting) of old blocks. This allows the pruneblockchain RPC to be called to delete specific blocks, and enables automatic pruning of old blocks if a target size in MiB is provided. This mode is incompatible with -txindex and -rescan. Warning: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, 1 = allow manual pruning via RPC, >945 = automatically prune block files to stay under the specified target size in MiB)
`--reindex-chainstate`
	Rebuild chain state from the currently indexed blocks
`--reindex`	Rebuild chain state and block index from the blk*.dat files on disk
`--sysperms`	Create new files with system default permissions, instead of umask 077 (only effective with disabled wallet functionality)
`--txindex`	Maintain a full transaction index, used by the getrawtransaction rpc call (default: 1)
`--addressindex`	Maintain a full address index, used to query for the balance, txids and unspent outputs for addresses (default: 0)
`--timestampindex`
	Maintain a timestamp index for block hashes, used to query blocks hashes by a range of timestamps (default: 0)
`--spentindex`	Maintain a full spent index, used to query the spending txid and input index for an outpoint (default: 0)

Connection options¶

`--addnode=<ip>`	Add a node to connect to and attempt to keep the connection open
`--allowprivatenet`
	Allow RFC1918 addresses to be relayed and connected to (default: 0)
`--banscore=<n>`	Threshold for disconnecting misbehaving peers (default: 100)
`--bantime=<n>`	Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
`--bind=<addr>`	Bind to given address and always listen on it. Use [host]:port notation for IPv6
`--connect=<ip>`	Connect only to the specified node(s); -noconnect or -connect=0 alone to disable automatic connections
`--discover`	Discover own IP addresses (default: 1 when listening and no -externalip or -proxy)
`--dns`	Allow DNS lookups for -addnode, -seednode and -connect (default: 1)
`--dnsseed`	Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect/-noconnect)
`--externalip=<ip>`
	Specify your own public address
`--forcednsseed`	Always query for peer addresses via DNS lookup (default: 0)
`--listen`	Accept connections from outside (default: 1 if no -proxy or -connect)
`--listenonion`	Automatically create Tor hidden service (default: 1)
`--maxconnections=<n>`
	Maintain at most <n> connections to peers (temporary service connections excluded) (default: 125)
`--maxreceivebuffer=<n>`
	Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000)
`--maxsendbuffer=<n>`
	Maximum per-connection send buffer, <n>*1000 bytes (default: 1000)
`--maxtimeadjustment`
	Maximum allowed median peer time offset adjustment. Local perspective of time may be influenced by peers forward or backward by this amount. (default: 4200 seconds)
`--onion=<ip:port>`
	Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: -proxy)
`--onlynet=<net>`
	Only connect to nodes in network <net> (ipv4, ipv6 or onion)
`--permitbaremultisig`
	Relay non-P2SH multisig (default: 1)
`--peerbloomfilters`
	Support filtering of blocks and transaction with bloom filters (default: 1)
`--port=<port>`	Listen for connections on <port> (default: 9999 or testnet: 19999)
`--proxy=<ip:port>`
	Connect through SOCKS5 proxy
`--proxyrandomize`
	Randomize credentials for every proxy connection. This enables Tor stream isolation (default: 1)
`--seednode=<ip>`
	Connect to a node to retrieve peer addresses, and disconnect
`--timeout=<n>`	Specify connection timeout in milliseconds (minimum: 1, default: 5000)
`--torcontrol=<ip:port>`
	Tor control port to use if onion listening enabled (default: 127.0.0.1:9051)
`--torpassword=<pass>`
	Tor control port password (default: empty)
`--upnp`	Use UPnP to map the listening port (default: 0)
`--whitebind=<addr>`
	Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
`--whitelist=<IP address or network>`
	Whitelist peers connecting from the given IP address (e.g. 1.2.3.4) or CIDR notated network (e.g. 1.2.3.0/24). Can be specified multiple times.
`--whitelistrelay`
	Accept relayed transactions received from whitelisted peers even when not relaying transactions (default: 1)
`--whitelistforcerelay`
	Force relay of transactions from whitelisted peers even if they violate local relay policy (default: 1)
`--maxuploadtarget=<n>`
	Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit (default: 0)

Wallet options¶

`--disablewallet`
	Do not load the wallet and disable wallet RPC calls
`--keypool=<n>`	Set key pool size to <n> (default: 1000)
`--fallbackfee=<amt>`
	A fee rate (in DASH/kB) that will be used when fee estimation has insufficient data (default: 0.00001)
`--mintxfee=<amt>`
	Fees (in DASH/kB) smaller than this are considered zero fee for transaction creation (default: 0.00001)
`--paytxfee=<amt>`
	Fee (in DASH/kB) to add to transactions you send (default: 0.00)
`--rescan`	Rescan the block chain for missing wallet transactions on startup
`--salvagewallet`
	Attempt to recover private keys from a corrupt wallet on startup
`--spendzeroconfchange`
	Spend unconfirmed change when sending transactions (default: 1)
`--txconfirmtarget=<n>`
	If paytxfee is not set, include enough fee so transactions begin confirmation on average within n blocks (default: 6)
`--usehd`	Use hierarchical deterministic key generation (HD) after BIP39/BIP44. Only has effect during wallet creation/first start (default: 0)
`--mnemonic`	User defined mnemonic for HD wallet (BIP39). Only has effect during wallet creation/first start (default: randomly generated)
`--mnemonicpassphrase`
	User defined mnemonic passphrase for HD wallet (BIP39). Only has effect during wallet creation/first start (default: empty string)
`--hdseed`	User defined seed for HD wallet (should be in hex). Only has effect during wallet creation/first start (default: randomly generated)
`--upgradewallet`
	Upgrade wallet to latest format on startup
`--wallet=<file>`
	Specify wallet file (within data directory) (default: wallet.dat)
`--walletbroadcast`
	Make the wallet broadcast transactions (default: 1)
`--walletnotify=<cmd>`
	Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)
`--zapwallettxes=<mode>`
	Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup (1 = keep tx meta data e.g. account owner and payment request information, 2 = drop tx meta data)
`--createwalletbackups=<n>`
	Number of automatic wallet backups (default: 10)
`--walletbackupsdir=<dir>`
	Specify full path to directory for automatic wallet backups (must exist)
`--keepass`	Use KeePass 2 integration using KeePassHttp plugin (default: 0)
`--keepassport=<port>`
	Connect to KeePassHttp on port <port> (default: 19455)
`--keepasskey=<key>`
	KeePassHttp key for AES encrypted communication with KeePass
`--keepassid=<name>`
	KeePassHttp id for the established association
`--keepassname=<name>`
	Name to construct url for KeePass entry that stores the wallet passphrase

ZeroMQ notification options¶

`--zmqpubhashblock=<address>`
	Enable publish hash block in <address>
`--zmqpubhashtx=<address>`
	Enable publish hash transaction in <address>
`--zmqpubhashtxlock=<address>`
	Enable publish hash transaction (locked via InstantSend) in <address>
`--zmqpubhashgovernancevote=<address>`
	Enable publish hash of governance votes in <address>
`--zmqpubhashgovernanceobject=<address>`
	Enable publish hash of governance objects (like proposals) in <address>
`--zmqpubhashinstantsenddoublespend=<address>`
	Enable publish transaction hashes of attempted InstantSend double spend in <address>
`--zmqpubrawblock=<address>`
	Enable publish raw block in <address>
`--zmqpubrawtx=<address>`
	Enable publish raw transaction in <address>
`--zmqpubrawtxlock=<address>`
	Enable publish raw transaction (locked via InstantSend) in <address>
`--zmqpubrawinstantsenddoublespend=<address>`
	Enable publish raw transactions of attempted InstantSend double spend in <address>

Debugging/Testing options¶

`--uacomment=<cmt>`
	Append comment to the user agent string
`--debug=<category>`
	Output debugging information (default: 0, supplying <category> is optional). If <category> is not supplied or if <category> = 1, output all debugging information.<category> can be: addrman, alert, bench, cmpctblock, coindb, db, http, leveldb, libevent, lock, mempool, mempoolrej, net, proxy, prune, rand, reindex, rpc, selectcoins, tor, zmq, dash (or specifically: gobject, instantsend, keepass, masternode, mnpayments, mnsync, privatesend, spork).
`--help-debug`	Show all debugging options (usage: –help -help-debug)
`--logips`	Include IP addresses in debug output (default: 0)
`--logtimestamps`
	Prepend debug output with timestamp (default: 1)
`--minrelaytxfee=<amt>`
	Fees (in DASH/kB) smaller than this are considered zero fee for relaying, mining and transaction creation (default: 0.00001)
`--maxtxfee=<amt>`
	Maximum total fees (in DASH) to use in a single wallet transaction or raw transaction; setting this too low may abort large transactions (default: 0.10)
`--printtoconsole`
	Send trace/debug info to console instead of debug.log file
`--printtodebuglog`
	Send trace/debug info to debug.log file (default: 1)
`--shrinkdebugfile`
	Shrink debug.log file on client startup (default: 1 when no -debug)

Chain selection options¶

`--testnet`	Use the test chain
`--devnet=<name>`
	Use devnet chain with provided name
`--litemode=<n>`	Disable all Dash specific functionality (Masternodes, PrivateSend, InstantSend, Governance) (0-1, default: 0)
`--sporkaddr=<hex>`
	Override spork address. Only useful for regtest and devnet. Using this on mainnet or testnet will ban you.
`--minsporkkeys=<n>`
	Overrides minimum spork signers to change spork value. Only useful for regtest and devnet. Using this on mainnet or testnet will ban you.

Masternode options¶

`--masternode=<n>`
	Enable the client to act as a masternode (0-1, default: 0)
`--mnconf=<file>`
	Specify masternode configuration file (default: masternode.conf)
`--mnconflock=<n>`
	Lock masternodes from masternode configuration file (default: 1)
`--masternodeprivkey=<n>`
	Set the masternode private key
`--masternodeblsprivkey=<hex>`
	Set the masternode BLS private key

PrivateSend options¶

`--enableprivatesend=<n>`
	Enable use of automated PrivateSend for funds stored in this wallet (0-1, default: 0)
`--privatesendmultisession=<n>`
	Enable multiple PrivateSend mixing sessions per block, experimental (0-1, default: 0)
`--privatesendsessions=<n>`
	Use N separate masternodes in parallel to mix funds (1-10, default: 4)
`--privatesendrounds=<n>`
	Use N separate masternodes for each denominated input to mix funds (2-16, default: 4)
`--privatesendamount=<n>`
	Keep N DASH mixed (2-21000000, default: 1000)
`--liquidityprovider=<n>`
	Provide liquidity to PrivateSend by infrequently mixing coins on a continual basis (0-100, default: 0, 1=very frequent, high fees, 100=very infrequent, low fees)

InstantSend options¶

`--enableinstantsend=<n>`
	Enable InstantSend, show confirmations for locked transactions (0-1, default: 1)
`--instantsendnotify=<cmd>`
	Execute command when a wallet InstantSend transaction is successfully locked (%s in cmd is replaced by TxID)

Node relay options¶

`--bytespersigop`
	Minimum bytes per sigop in transactions we relay and mine (default: 20)
`--datacarrier`	Relay and mine data carrier transactions (default: 1)
`--datacarriersize`
	Maximum size of data in data carrier transactions we relay and mine (default: 83)

Block creation options¶

`--blockmaxsize=<n>`
	Set maximum block size in bytes (default: 2000000)
`--blockprioritysize=<n>`
	Set maximum size of high-priority/low-fee transactions in bytes (default: 10000)
`--blockmintxfee=<amt>`
	Set lowest fee rate (in DASH/kB) for transactions to be included in block creation. (default: 0.00001)

RPC server options¶

`--server`	Accept command line and JSON-RPC commands
`--rest`	Accept public REST requests (default: 0)
`--rpcbind=<addr>`
	Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6. This option can be specified multiple times (default: bind to all interfaces)
`--rpccookiefile=<loc>`
	Location of the auth cookie (default: data dir)
`--rpcuser=<user>`
	Username for JSON-RPC connections
`--rpcpassword=<pw>`
	Password for JSON-RPC connections
`--rpcauth=<userpw>`
	Username and hashed password for JSON-RPC connections. The field <userpw> comes in the format: <USERNAME>:<SALT>$<HASH>. A canonical python script is included in share/rpcuser. The client then connects normally using the rpcuser=<USERNAME>/rpcpassword=<PASSWORD> pair of arguments. This option can be specified multiple times
`--rpcport=<port>`
	Listen for JSON-RPC connections on <port> (default: 9998 or testnet: 19998)
`--rpcallowip=<ip>`
	Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified multiple times
`--rpcthreads=<n>`
	Set the number of threads to service RPC calls (default: 4)

dash-qt¶

Dash Core QT GUI, use same command line options as dashd with additional options for UI as described below.

Usage¶

dash-qt [command-line options]: Start Dash Core QT GUI

Wallet options¶

`--windowtitle=<name>`
	Wallet window title

Debugging/Testing options¶

--debug=<category>

Output debugging information (default: 0, supplying <category> is optional). If <category> is not supplied or if <category> = 1, output all debugging information.<category> can be: addrman, alert, bench, cmpctblock, coindb, db, http, leveldb, libevent, lock, mempool, mempoolrej, net, proxy, prune, rand, reindex, rpc, selectcoins, tor, zmq, dash (or specifically: gobject, instantsend, keepass, masternode, mnpayments, mnsync, privatesend, spork), qt.

UI options¶

`--choosedatadir`
	Choose data directory on startup (default: 0)
`--lang=<lang>`	Set language, for example «de_DE» (default: system locale)
`--min`	Start minimized
`--rootcertificates=<file>`
	Set SSL root certificates for payment request (default: -system-)
`--splash`	Show splash screen on startup (default: 1)
`--resetguisettings`
	Reset all settings changed in the GUI

dash-cli¶

Dash Core RPC client

Usage¶

dash-cli [options] <command> [params]: Send command to Dash Core
dash-cli [options] help: List commands
dash-cli [options] help <command>: Get help for a command

Options¶

`--help`	This help message
`--conf=<file>`	Specify configuration file (default: dash.conf)
`--datadir=<dir>`
	Specify data directory

Chain selection options¶

`--testnet`	Use the test chain
`--devnet=<name>`
	Use devnet chain with provided name
`--regtest`	Enter regression test mode, which uses a special chain in which blocks can be solved instantly. This is intended for regression testing tools and app development.
`--named`	Pass named instead of positional arguments (default: false)
`--rpcconnect=<ip>`
	Send commands to node running on <ip> (default: 127.0.0.1)
`--rpcport=<port>`
	Connect to JSON-RPC on <port> (default: 9998 or testnet: 19998)
`--rpcwait`	Wait for RPC server to start
`--rpcuser=<user>`
	Username for JSON-RPC connections
`--rpcpassword=<pw>`
	Password for JSON-RPC connections
`--rpcclienttimeout=<n>`
	Timeout during HTTP requests (default: 900)
`--stdin`	Read extra arguments from standard input, one per line until EOF/Ctrl-D (recommended for sensitive information such as passphrases)

dash-tx¶

Dash Core dash-tx utility

Usage¶

dash-tx [options] <hex-tx> [commands]: Update hex-encoded dash transaction
dash-tx [options] -create [commands]: Create hex-encoded dash transaction

Options¶

`--help`	This help message
`--create`	Create new, empty TX.
`--json`	Select JSON output
`--txid`	Output only the hex-encoded transaction id of the resultant transaction.

Chain selection options¶

`--testnet`	Use the test chain
`--devnet=<name>`
	Use devnet chain with provided name
`--regtest`	Enter regression test mode, which uses a special chain in which blocks can be solved instantly. This is intended for regression testing tools and app development.

Commands¶

delin=N: Delete input N from TX
delout=N: Delete output N from TX
in=TXID:VOUT: Add input to TX
locktime=N: Set TX lock time to N
nversion=N: Set TX version to N
outaddr=VALUE:ADDRESS: Add address-based output to TX
outpubkey=VALUE:PUBKEY[:FLAGS]: Add pay-to-pubkey output to TX. Optionally add the «S» flag to wrap the output in a pay-to-script-hash.
outdata=[VALUE:]DATA: Add data-based output to TX
outscript=VALUE:SCRIPT[:FLAGS]: Add raw script output to TX. Optionally add the «S» flag to wrap the output in a pay-to-script-hash.
outmultisig=VALUE:REQUIRED:PUBKEYS:PUBKEY1:PUBKEY2:….[:FLAGS]: Add Pay To n-of-m Multi-sig output to TX. n = REQUIRED, m = PUBKEYS. Optionally add the «S» flag to wrap the output in a pay-to-script-hash.
sign=SIGHASH-FLAGS: Add zero or more signatures to transaction. This command requires JSON registers:prevtxs=JSON object, privatekeys=JSON object. See signrawtransaction docs for format of sighash flags, JSON objects.

Register Commands¶

load=NAME:FILENAME: Load JSON file FILENAME into register NAME
set=NAME:JSON-STRING: Set register NAME to given JSON-STRING

RPC commands¶

This documentation lists all available RPC commands as of Dash version 0.13.0.0, and limited documentation on what each command does. For full documentation of arguments, results and examples, type help ( «command» ) to view full details at the console. You can enter commands either from Tools > Debug console in the QT wallet, or using dash-cli for headless wallets and dashd.

Addressindex¶

getaddressbalance: Returns the balance for an address(es) (requires addressindex to be enabled).
getaddressdeltas: Returns all changes for an address (requires addressindex to be enabled).
getaddressmempool: Returns all mempool deltas for an address (requires addressindex to be enabled).
getaddresstxids: Returns the txids for an address(es) (requires addressindex to be enabled).
getaddressutxos: Returns all unspent outputs for an address (requires addressindex to be enabled).

Blockchain¶

getbestblockhash: Returns the hash of the best (tip) block in the longest blockchain.
getblock «blockhash» ( verbosity ): If verbosity is 0, returns a string that is serialized, hex-encoded data for block “hash”. If verbosity is 1, returns an Object with information about block <hash>. If verbosity is 2, returns an Object with information about block <hash> and information about each transaction.
getblockchaininfo: Returns an object containing various state info regarding blockchain processing.
getblockcount: Returns the number of blocks in the longest blockchain.
getblockhash height: Returns hash of block in best-block-chain at height provided.
getblockhashes timestamp: Returns array of hashes of blocks within the timestamp range provided.
getblockheader «hash» ( verbose ): If verbose is false, returns a string that is serialized, hex-encoded data for blockheader “hash”. If verbose is true, returns an Object with information about blockheader <hash>.
getblockheaders «hash» ( count verbose ): Returns an array of items with information about <count> blockheaders starting from <hash>. If verbose is false, each item is a string that is serialized, hex-encoded data for a single blockheader. If verbose is true, each item is an Object with information about a single blockheader.
getchaintips ( count branchlen ): Return information about all known tips in the block tree, including the main chain as well as orphaned branches.
getdifficulty: Returns the proof-of-work difficulty as a multiple of the minimum difficulty.
getmempoolancestors txid (verbose): If txid is in the mempool, returns all in-mempool ancestors.
getmempooldescendants txid (verbose): If txid is in the mempool, returns all in-mempool descendants.
getmempoolentry txid: Returns mempool data for given transaction.
getmempoolinfo: Returns details on the active state of the TX memory pool.
getrawmempool ( verbose ): Returns all transaction ids in memory pool as a json array of string transaction ids.
getspentinfo: Returns the txid and index where an output is spent.
gettxout «txid» n ( include_mempool ): Returns details about an unspent transaction output.
gettxoutproof [«txid»,…] ( blockhash ): Returns a hex-encoded proof that «txid» was included in a block.
gettxoutsetinfo: Returns statistics about the unspent transaction output set. Note this call may take some time.
preciousblock «blockhash»: Treats a block as if it were received before others with the same work. A later preciousblock call can override the effect of an earlier one. The effects of preciousblock are not retained across restarts.
pruneblockchain: Prune blockchain up to specified height or unix timestamp.
verifychain ( checklevel nblocks ): Verifies blockchain database.
verifytxoutproof «proof»: Verifies that a proof points to a transaction in a block, returning the transaction it commits to and throwing an RPC error if the block is not in our best chain.

Control¶

debug ( 0 | 1 | addrman | alert | bench | coindb | db | lock | rand | rpc | selectcoins | mempool | mempoolrej | net | proxy | prune | http | libevent | tor | zmq | dash | privatesend | instantsend | masternode | spork | keepass | mnpayments | gobject ): Change debug category on the fly. Specify single category or use “+” to specify many.
getinfo: DEPRECATED. Returns an object containing various state info.
getmemoryinfo: Returns an object containing information about memory usage
help ( «command» ) («subCommand»): List all commands, or get help for a specified comm
stop: Stop Dash Core server.

Dash¶

getgovernanceinfo

Returns an object containing governance parameters.

getpoolinfo

Returns an object containing mixing pool related information.

getsuperblockbudget index

Returns the absolute maximum sum of superblock payments allowed.

gobject «command»…

Manage governance objects. Available commands:

check

Validate governance object data (proposal only)

prepare

Prepare governance object by signing and creating tx

submit

Submit governance object to network

deserialize

Deserialize governance object from hex string to JSON

count

Count governance objects and votes (additional param: “json” or “all”, default: “json”)

get

Get governance object by hash

getvotes

Get all votes for a governance object hash (including old votes)

getcurrentvotes

Get only current (tallying) votes for a governance object hash (does not include old votes)

list

List governance objects (can be filtered by signal and/or object type)

diff

List differences since last diff

vote-alias

Vote on a governance object by masternode alias (using masternode.conf setup)

vote-conf

Vote on a governance object by masternode configured in dash.conf

vote-many

Vote on a governance object by all masternodes (using masternode.conf setup)

masternode «command»…

Set of commands to execute masternode related actions. Available commands:

check

Force check all masternodes and remove invalid ones

count

Get information about number of masternodes (DEPRECATED options: “total”, “ps”, “enabled”, “qualify”, “all”)

current

Print info on current masternode winner to be paid the next block (calculated locally)

genkey

Generate new masternodeprivkey, optional param: “compressed” (boolean, optional, default=false) generate compressed privkey

outputs

Print masternode compatible outputs

start-alias

Start single remote masternode by assigned alias configured in masternode.conf

start-<mode>

Start remote masternodes configured in masternode.conf (<mode>: “all”, “missing”, “disabled”)

status

Print masternode status information

list

Print list of all known masternodes (see masternodelist for more info)

list-conf

Print masternode.conf in JSON format

winner

Print info on next masternode winner to vote for

winners

Print list of masternode winners

masternodebroadcast «command»…

Set of commands to create and relay masternode broadcast messages. Available commands:

create-alias

Create single remote masternode broadcast message by assigned alias configured in masternode.conf

create-all

Create remote masternode broadcast messages for all masternodes configured in masternode.conf

decode

Decode masternode broadcast message

relay

Relay masternode broadcast message to the network

masternode list ( «mode» «filter» )

Get a list of masternodes in different modes. This call is identical to masternodelist call.

mnsync [status | next | reset]

Returns the sync status, updates to the next step or resets it entirely.

privatesend «command»

Available commands:

start

Start mixing

stop

Stop mixing

reset

Reset mixing

sentinelping version

Sentinel ping.

spork «command»

Shows information about current state of sporks. Available commands:

show

Show all current spork values

active

Show which sporks are active

voteraw <masternode-tx-hash> <masternode-tx-index> <governance-hash> <vote-signal> [yes | no | abstain] <time> <vote-sig>

Compile and relay a governance vote with provided external signature instead of signing vote internally

Evo¶

bls «command» …

Set of commands to execute BLS related actions. Available commands:

generate

Create a BLS secret/public key pair

protx «command» …

Set of commands to execute ProTx related actions. Available commands:

register

Create and send ProTx to network

register_fund

Fund, create and send ProTx to network

register_prepare

Create an unsigned ProTx

register_submit

Sign and submit a ProTx

list

List ProTxs

info

Return information about a ProTx

update_service

Create and send ProUpServTx to network

update_registrar

Create and send ProUpRegTx to network

revoke

Create and send ProUpRevTx to network

diff

Calculate a diff and a proof between two masternode lists

Generating¶

generate nblocks ( maxtries ): Mine up to nblocks blocks immediately (before the RPC call returns)
generatetoaddress nblocks address (maxtries): Mine blocks immediately to a specified address (before the RPC call returns)

Mining¶

getblocktemplate ( TemplateRequest ): If the request parameters include a “mode” key, that is used to explicitly select between the default “template” request or a “proposal”. It returns data needed to construct a block to work on.
getmininginfo: Returns a json object containing mining-related information.
getnetworkhashps ( nblocks height ): Returns the estimated network hashes per second based on the last n blocks. Pass in [blocks] to override # of blocks, -1 specifies since last difficulty change. Pass in [height] to estimate the network speed at the time when a certain block was found.
prioritisetransaction <txid> <priority delta> <fee delta>: Accepts the transaction into mined blocks at a higher (or lower) priority
submitblock «hexdata» ( «jsonparametersobject» ): Attempts to submit new block to network. The “jsonparametersobject” parameter is currently ignored. See https://en.bitcoin.it/wiki/BIP_0022 for full specification.

Network¶

addnode «node» «add | remove | onetry»: Attempts add or remove a node from the addnode list. Or try a connection to a node once.
clearbanned: Clear all banned IPs.
disconnectnode «address»: Immediately disconnects from the specified node.
getaddednodeinfo ( «node» ): Returns information about the given added node, or all added nodes (note that onetry addnodes are not listed here)
getconnectioncount: Returns the number of connections to other nodes.
getnettotals: Returns information about network traffic, including bytes in, bytes out, and current time.
getnetworkinfo: Returns an object containing various state info regarding P2P networking.
getpeerinfo: Returns data about each connected network node as a json array of objects.
listbanned: List all banned IPs/Subnets.
ping: Requests that a ping be sent to all other nodes, to measure ping time. Results provided in getpeerinfo, pingtime and pingwait fields are decimal seconds. Ping command is handled in queue with all other commands, so it measures processing backlog, not just network ping.
setban «subnet» «add | remove» (bantime) (absolute): Attempts add or remove a IP/Subnet from the banned list.
setnetworkactive true | false: Disable/enable all p2p network activity.

Rawtransactions¶

createrawtransaction [{«txid»:»id»,»vout»:n},…] {«address»:amount,»data»:»hex»,…} ( locktime ): Create a transaction spending the given inputs and creating new outputs. Outputs can be addresses or data. Returns hex-encoded raw transaction. Note that the transaction’s inputs are not signed, and it is not stored in the wallet or transmitted to the network.
decoderawtransaction «hexstring»: Return a JSON object representing the serialized, hex-encoded transaction.
decodescript «hexstring»: Decode a hex-encoded script.
fundrawtransaction «hexstring» ( options ): Add inputs to a transaction until it has enough in value to meet its out value. This will not modify existing inputs, and will add at most one change output to the outputs.
getrawtransaction «txid» ( verbose ): Return the raw transaction data. If verbose is “true”, returns an Object with information about “txid”. If verbose is “false” or omitted, returns a string that is serialized, hex-encoded data for “txid”.
sendrawtransaction «hexstring» ( allowhighfees instantsend bypasslimits): Submits raw transaction (serialized, hex-encoded) to local node and network. Also see createrawtransaction and signrawtransaction calls.
signrawtransaction «hexstring» ( [{«txid»:»id»,»vout»:n,»scriptPubKey»:»hex»,»redeemScript»:»hex»},…] [«privatekey1»,…] sighashtype ): Sign inputs for raw transaction (serialized, hex-encoded). The second optional argument (may be null) is an array of previous transaction outputs that this transaction depends on but may not yet be in the block chain. The third optional argument (may be null) is an array of base58-encoded private keys that, if given, will be the only keys used to sign the transaction.

Util¶

createmultisig nrequired [«key»,…]: Creates a multi-signature address with n signature of m keys required. It returns a json object with the address and redeemScript.
estimatefee nblocks: Estimates the approximate fee per kilobyte needed for a transaction to begin confirmation within nblocks blocks.
estimatepriority nblocks: DEPRECATED. Estimates the approximate priority a zero-fee transaction needs to begin confirmation within nblocks blocks.
estimatesmartfee nblocks: WARNING: This interface is unstable and may disappear or change! Estimates the approximate fee per kilobyte needed for a transaction to begin confirmation within nblocks blocks if possible and return the number of blocks for which the estimate is valid.
estimatesmartpriority nblocks: DEPRECATED. WARNING: This interface is unstable and may disappear or change! Estimates the approximate priority a zero-fee transaction needs to begin confirmation within nblocks blocks if possible and return the number of blocks for which the estimate is valid.
signmessagewithprivkey «privkey» «message»: Sign a message with the private key of an address
validateaddress «address»: Return information about the given dash address.
verifymessage «address» «signature» «message»: Verify a signed message

Wallet¶

abandontransaction «txid»: Mark in-wallet transaction <txid> as abandoned. This will mark this transaction and all its in-wallet descendants as abandoned which will allow for their inputs to be respent.
addmultisigaddress nrequired [«key»,…] ( «account» ): Add a nrequired-to-sign multisignature address to the wallet. Each key is a Dash address or hex-encoded public key. If “account” is specified (DEPRECATED), assign address to that account.
backupwallet «destination»: Safely copies current wallet file to destination, which can be a directory or a path with filename.
dumphdinfo: Returns an object containing sensitive private info about this HD wallet.
dumpprivkey «address»: Reveals the private key corresponding to “address”. Then the importprivkey can be used with this output
dumpwallet «filename»: Dumps all wallet keys in a human-readable format.
getaccount «address»: DEPRECATED. Returns the account associated with the given address.
getaccountaddress «account»: DEPRECATED. Returns the current Dash address for receiving payments to this account.
getaddressesbyaccount «account»: DEPRECATED. Returns the list of addresses for the given account.
getbalance ( «account» minconf addlocked include_watchonly ): If account is not specified, returns the server’s total available balance. If account is specified (DEPRECATED), returns the balance in the account. Note that the account «» is not the same as leaving the parameter out. The server total may be different to the balance in the default «» account.
getnewaddress ( «account» ): Returns a new Dash address for receiving payments. If “account” is specified (DEPRECATED), it is added to the address book so payments received with the address will be credited to “account”.
getrawchangeaddress: Returns a new Dash address, for receiving change. This is for use with raw transactions, NOT normal use.
getreceivedbyaccount «account» ( minconf addlocked ): DEPRECATED. Returns the total amount received by addresses with <account> in transactions with specified minimum number of confirmations.
getreceivedbyaddress «address» ( minconf addlocked ): Returns the total amount received by the given address in transactions with at least minconf confirmations.
getspecialtxes «blockhash» ( type count skip verbosity ): Returns an array of special transactions found in the specified block
gettransaction «txid» ( include_watchonly ): Get detailed information about in-wallet transaction <txid>
getunconfirmedbalance: Returns the server’s total unconfirmed balance
getwalletinfo: Returns an object containing various wallet state info.
importaddress «address» ( «label» rescan p2sh ): Adds a script (in hex) or address that can be watched as if it were in your wallet but cannot be used to spend.
importelectrumwallet «filename» index: Imports keys from an Electrum wallet export file (.csv or .json)
importmulti «requests» «options»: Import addresses/scripts (with private or public keys, redeem script (P2SH)), rescanning all addresses in one-shot-only (rescan can be disabled via options).
importprivkey «dashprivkey» ( «label» ) ( rescan ): Adds a private key (as returned by dumpprivkey) to your wallet.
importprunedfunds: Imports funds without rescan. Corresponding address or script must previously be included in wallet. Aimed towards pruned wallets. The end-user is responsible to import additional transactions that subsequently spend the imported outputs or rescan after the point in the blockchain the transaction is included.
importpubkey «pubkey» ( «label» rescan ): Adds a public key (in hex) that can be watched as if it were in your wallet but cannot be used to spend.
importwallet «filename»: Imports keys from a wallet dump file (see dumpwallet).
instantsendtoaddress «address» amount ( «comment» «comment-to» subtractfeefromamount ): Send an amount to a given address. The amount is a real and is rounded to the nearest 0.00000001
keepass <genkey | init | setpassphrase>: Keepass settings.
keypoolrefill ( newsize ): Fills the keypool. Requires wallet passphrase to be set with walletpassphrase call.
listaccounts ( minconf addlocked include_watchonly): DEPRECATED. Returns Object that has account names as keys, account balances as values.
listaddressbalances ( minamount ): Lists addresses of this wallet and their balances
listaddressgroupings: Lists groups of addresses which have had their common ownership made public by common use as inputs or as the resulting change in past transactions
listlockunspent: Returns list of temporarily unspendable outputs. See the lockunspent call to lock and unlock transactions for spending.
listreceivedbyaccount ( minconf addlocked include_empty include_watchonly): DEPRECATED. List incoming payments grouped by account.
listreceivedbyaddress ( minconf addlocked include_empty include_watchonly): List incoming payments grouped by receiving address.
listsinceblock ( «blockhash» target_confirmations include_watchonly): Get all transactions in blocks since block [blockhash], or all transactions if omitted
listtransactions ( «account» count skip include_watchonly): Returns up to “count” most recent transactions skipping the first “from” transactions for account “account”.
listunspent ( minconf maxconf [«addresses»,…] [include_unsafe] ): Returns array of unspent transaction outputs with between minconf and maxconf (inclusive) confirmations. Optionally filter to only include txouts paid to specified addresses.
lockunspent unlock ([{«txid»:»txid»,»vout»:n},…]): Updates list of temporarily unspendable outputs. Temporarily lock (unlock=false) or unlock (unlock=true) specified transaction outputs.
move «fromaccount» «toaccount» amount ( minconf «comment» ): DEPRECATED. Move a specified amount from one account in your wallet to another.
removeprunedfunds «txid»: Deletes the specified transaction from the wallet. Meant for use with pruned wallets and as a companion to importprunedfunds. This will effect wallet balances.
sendfrom «fromaccount» «toaddress» amount ( minconf addlocked «comment» «comment_to» ): DEPRECATED (use sendtoaddress). Sent an amount from an account to a dash address. Requires wallet passphrase to be set with walletpassphrase call.
sendmany «fromaccount» {«address»:amount,…} ( minconf addlocked «comment» [«address»,…] subtractfeefromamount use_is use_ps ): Send multiple times. Amounts are double-precision floating point numbers. Requires wallet passphrase to be set with walletpassphrase call.
sendtoaddress «address» amount ( «comment» «comment_to» subtractfeefromamount use_is use_ps ): Send an amount to a given address.
setaccount «address» «account»: DEPRECATED. Sets the account associated with the given address.
setprivatesendamount amount: Set the goal amount in DASH for PrivateSend mixing.
setprivatesendrounds rounds: Set the number of rounds for PrivateSend mixing.
settxfee amount: Set the transaction fee per kB. Overwrites the paytxfee parameter.
signmessage «address» «message»: Sign a message with the private key of an address Requires wallet passphrase to be set with walletpassphrase call.
walletlock: Removes the wallet encryption key from memory, locking the wallet. After calling this method, you will need to call walletpassphrase again before being able to call any methods which require the wallet to be unlocked.
walletpassphrase «passphrase» timeout ( mixingonly ): Stores the wallet decryption key in memory for “timeout” seconds. This is needed prior to performing transactions related to private keys such as sending dashs
walletpassphrasechange «oldpassphrase» «newpassphrase»: Changes the wallet passphrase from “oldpassphrase” to “newpassphrase”.

Advanced topics¶

Coin Control¶

Coin Control allows users of the Dash Core Wallet to specify which addresses and Unspent Transaction Outputs (UTXOs) should be used as inputs in transactions. This allows you to keep a specific balance on certain addresses in your wallet, while spending others freely. In Dash Core Wallet, click Settings > Options > Wallet > Enable coin control features. Now, when you go to the Send tab in your wallet, a new button labelled Inputs… will appear. Click this button to select which UTXOs can be used as input for any transactions you create. The following window appears:

Coin Selection window in Dash Core wallet, showing two masternodes (testnet)

Right click on the transaction(s) you do not want to spend, then select Lock unspent. A small lock will appear next to the transaction. You can click the Toggle lock state button to invert the locked/unlocked state of all UTXOs. When you are ready to continue, click OK. You can now safely create transactions with your remaining funds without affecting the locked UTXOs.

Locking UTXOs in Dash Core wallet

HD Wallets¶

Since version 0.12.2.0, Dash Core has included an implementation of BIP39/BIP44 compatible hierarchical deterministic (HD) key generation. This functionality is only available from the command line by specifying the usehd option when starting Dash Core for the first time. Use this function with care, since the mnemonic seed and keys will be stored in plain text until you specify a wallet passphrase. Note that the wallet passphrase is different to the mnemonic passphrase, which is often also referred to as the «25th word» or «extension word». The wallet passphrase encrypts the wallet file itself, while the mnemonic passphrase is used to specify different derivation branches from the same mnemonic seed.

We will use the Windows GUI wallet in this example, but the commands are similar if using dash-qt or dashd on other operating systems. Enter the following command to get started with a randomly generated HD wallet seed and no mnemonic passphrase:

dash-qt.exe --usehd=1

A new HD wallet will be generated and Dash Core will display a warning informing you that you must encrypt your wallet after verifying it works correctly. Open the console from Tools -> Debug console or issue the following RPC command from dash-cli to view the mnemonic seed:

dumphdinfo

Dash Core will display the HD seed in both hexadecimal and as a BIP39 mnemonic. To restore an existing HD wallet, or define your own separately generated mnemonic and/or passphrase, ensure no wallet.dat file exists in the datadir and enter the following command:

dash-qt.exe --usehd=1 --mnemonic="enter mnemonic" --mnemonicpassphrase="optional mnemonic passphrase"

The HD wallet will be restored and your balance will appear once sync is complete.

Multisignature¶

This section presents a worked example to demonstrate multisig functionality in Dash Core. While the transactions are no longer visible on the current testnet blockchain and some address formats or RPC responses may differ slightly from the version shown here, the principle and commands are the same. The example demonstrates how to set up a 2-of-3 multisig address and create a transaction. The example parties involved are a buyer, a seller and an arbiter. This example is based on:

Step 1: Create three addresses¶

Seller:

seller@testnet03:~$ ./dash-cli getnewaddress
n18cPEtj4ZfToPZxRszUz2XPts4eGsxiPk
seller@testnet03:~$ ./dash-cli validateaddress n18cPEtj4ZfToPZxRszUz2XPts4eGsxiPk
{
    "isvalid" : true,
    "address" : "n18cPEtj4ZfToPZxRszUz2XPts4eGsxiPk",
    "ismine" : true,
    "isscript" : false,
    "pubkey" : "02a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e",
    "iscompressed" : true,
    "account" : ""
}
seller@testnet03:~$ ./dash-cli dumpprivkey n18cPEtj4ZfToPZxRszUz2XPts4eGsxiPk
cVQVgBr8sW4FTPYz16BSCo1PcAfDhpJArgMPdLxKZQWcVFwMXRXx

Buyer:

buyer@testnet03:~$ ./dash-cli getnewaddress
mp5orHuaFaHCXFSCeYvUPL7H16JU8fKG6u
buyer@testnet03:~$ ./dash-cli validateaddress mp5orHuaFaHCXFSCeYvUPL7H16JU8fKG6u
{
    "isvalid" : true,
    "address" : "mp5orHuaFaHCXFSCeYvUPL7H16JU8fKG6u",
    "ismine" : true,
    "isscript" : false,
    "pubkey" : "0315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c",
    "iscompressed" : true,
    "account" : ""
}
buyer@testnet03:~$ ./dash-cli dumpprivkey mp5orHuaFaHCXFSCeYvUPL7H16JU8fKG6u
cP9DFmEDb11waWbQ8eG1YUoZCGe59BBxJF3kk95PTMXuG9HzcxnU

Arbiter:

arbiter@testnet03:~$ ./dash-cli getnewaddress
n1cZSyQXhach5rrj2tm5wg6JC7uZ3qPNiN
arbiter@testnet03:~$ ./dash-cli validateaddress n1cZSyQXhach5rrj2tm5wg6JC7uZ3qPNiN
{
    "isvalid" : true,
    "address" : "n1cZSyQXhach5rrj2tm5wg6JC7uZ3qPNiN",
    "ismine" : true,
    "isscript" : false,
    "pubkey" : "0287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce",
    "iscompressed" : true,
    "account" : ""
}
arbiter@testnet03:~$ ./dash-cli dumpprivkey n1cZSyQXhach5rrj2tm5wg6JC7uZ3qPNiN
cUbDFL81a2w6urAGZf7ecGbdzM82pdHLeCaPXdDp71s96SzDV49M

This results in three keypairs (public/private):

seller:    02a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e / cVQVgBr8sW4FTPYz16BSCo1PcAfDhpJArgMPdLxKZQWcVFwMXRXx
buyer:     0315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c / cP9DFmEDb11waWbQ8eG1YUoZCGe59BBxJF3kk95PTMXuG9HzcxnU
arbiter:   0287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce / cUbDFL81a2w6urAGZf7ecGbdzM82pdHLeCaPXdDp71s96SzDV49M

Step 2: Create multisig address¶

The createmultisig command takes as variables the number n signatures of m keys (supplied as json array) required. In this example, 2 of 3 keys are required to sign the transaction.

Note: The address can be created by anyone, as long as the public keys and their sequence are known (resulting address and redeemScript are identical, see below).

Seller:

seller@testnet03:~$ ./dash-cli createmultisig 2 '["02a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e","0315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c","0287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce"]'
{
    "address" : "2MuEQCZh7VB8pNrT4bj1CFZQh2oK7XZYLQf",
    "redeemScript" : "522102a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e210315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c210287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce53ae"
}

Buyer:

buyer@testnet03:~$ ./dash-cli createmultisig 2 '["02a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e","0315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c","0287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce"]'
{
    "address" : "2MuEQCZh7VB8pNrT4bj1CFZQh2oK7XZYLQf",
    "redeemScript" : "522102a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e210315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c210287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce53ae"
}

Arbiter:

arbiter@testnet03:~$ ./dash-cli createmultisig 2 '["02a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e","0315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c","0287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce"]'
{
    "address" : "2MuEQCZh7VB8pNrT4bj1CFZQh2oK7XZYLQf",
    "redeemScript" : "522102a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e210315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c210287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce53ae"
}

Step 3: Buyer funds the multisig address¶

This works the same as a usual transaction.

Buyer:

buyer@testnet03:~$ ./dash-cli sendtoaddress 2MuEQCZh7VB8pNrT4bj1CFZQh2oK7XZYLQf 777.77
a8b3bf5bcace91a8dbbddbf9b7eb027efb9bd001792f043ecf7b558aaa3cb951

The seller/arbiter can trace the transaction by its txid in the block explorer. Or from the console as follows.

Buyer:

seller@testnet03:~$ ./dash-cli getrawtransaction a8b3bf5bcace91a8dbbddbf9b7eb027efb9bd001792f043ecf7b558aaa3cb951 1
{
    "hex" : "010000001a2e514dd90f666e3de4cddd22682ae1ca7225988656369d98228c742482fee16b010000006b48304502200ea8dddd404aac644fd382d3089480f2c9a6ce753a3c4fc0b12ac81afe8ffa3b022100d88f698a0d9fefbbf76240790530fe7e23bf6b354a1feedb4effa99813405b00012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff3181c52614be8742c36665b6a287a2d6c7970494b0a341ff9595c1c9a8f23aa2010000006b483045022041ee176da4df13adc782c9ff2afdb24c4e1b61b450895486388431bf1a88b81f02210082be1b3bd20d3f121c971fb745cba52523f6b8093ec93df5987c9beb302c19ac012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff332356f7d5e4264302ca4cc0f38d2a75a9b4c1df4bc4f94044f8a8fab81b7e1b010000006b483045022100dc322074961ae5e2e8cb11828301b1e083eff9ed6078aa064c52ed70d52737410220776b99c8552bbc2e644c7450ef8502d3497c3de7196b176f1c49cca18d1ff09f012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff388b56a8a74338ce10e931dc198ed25fa4cb7213e0ea9905d32a3e902366661f010000006b48304502206d2cdfe9af498e9e46f88d0bd881746bf2dae182664d03f7a635ff599bdee84b022100bf3a7b88ed80b30d8915a2ae34d546defbc9a660ebf941afb4aa29461e0b4c95012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff44578d7579bef2a204359f8c878993480b306193d954ee735c53f8b3e076c3ea010000006c4930460221008a67da5764934392437fa9e05483e4b29204fd5d78dea01f744d4a23c403881b022100c77e58307f58953b578de568138659b4efd2fadaec51917c2270fab0bd4a57a6012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff4a3b7b666ce8f249ef4f253b7f718fb5cc2f21f899608d319bcc04c75ec47353010000006b48304502203ca5a0559647ee0d1790714296396ca0bca27a3ef3e68f76706c63da9cd3684f0221008c9529f7a54d89440f8dca89c1c47725821012670d05a70681b57f182b069a74012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff4ab5d98908e4424929bfdba3d6402e6b45db60a622b4df8c73da1b37bdb949a4010000006b48304502210094da4e007ba94cdb47a8c4805dab4b93dc475a44340a9b6f6d7956d49749e3d3022077b94861995ffe3f59429bf5b873914d3c1157f23f018697650bc3bd2dc2de1f012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff4cd58c1ad5b0ffd8556deff402854d94a79222799916be8e0f88d0cca3c38c85010000006b483045022030e72eec0386c83489efff8f3c71aed8eec0265565cddeb1492aab6644cc63220221008d6df06656dae12dae573b860d65045f088e4df5e2127902231d8edd4196ef1d012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff501ff2345fc47b9b7749afcc32e790fdbe5d22fd96b2c5d0522d4cad0cd5566f010000006a47304402204e9bc23796974fdf323c49399ca7db76e2238630add4c617631549f4595af4a80220658038b14884c1a0d730de79c7e2769d4d28135ed7896e7aff01ca94c8edf7bb012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff5020fe72d4c1038213cc3e1b99f5b313c4b2d57f1e0d9abba90860dc5c38630a010000006a473044022071b7cca6a7d72fef4b46ad425c23c37f28c72501e5e61821f00e022c4c8ef49502200d8ba406fe336d64a8ae909cad20d0ffe302cd977900013ea72b37c488550625012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff59f32023d4225cc193182e81444f00f6d95652a9458daa08f4324ab4bdac7bed010000006b4830450221009e0f701840c01c2c37e2baec0ea2c43d517126107ef874c3d68f32dfa2e4f05f02206d1306dee274267598d5ab8d7c4c26346d25d8118b30a6921b9b238307916d6e012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff05b5b8ecaf7bcbd5fdfc64fd7dbd6ebfee18dcaf57e00b6711ba0abe4329eb23010000006a47304402200515822e6d9641c72f1af7968ba63d47463caffeca03733750b0866ef123fe00022071fd40bac12aa1d36244fc5391162b70ec306a5ed2dffef3a3d4995524317a10012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff09cc372e4409bcbacd85adb17918ca5b20427dc280b44bd4f234fb698ac07fc6010000006b483045022051e5c430110e8b0d85693c421031f14abf89bee1a14702e6655a1eaa2663927c0221009a54781fddd4093032507f12fe8a97ce926a743851a1a56c2ca70026ce98b7e6012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff0963f2cc80666835ae8c5939ac3011d2962ae88e872cdc13257cfb0188f83c7a010000006b483045022032fd819b1cdb8f506e27f26b3e46330c498b965386c3e96c34dceeff2a517cf7022100a4c34d77ed25116dc05ca7d783bd6cb91c1e38db0541878dac72f2d63d4b7c11012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff14cff38ccbdd840ffc491614e9b5167edb6ad6b9eeaf8e3dc30feaeefa39d820010000006c493046022100f4d6dfce7778acee6bdcf9f2ec39dbf902b6ca977b8622c886eadddefa01bf5502210089b3c2d23b5fc5b03d2d6ea4bf28f04b98342b02dd7d2020a6466bddd85c3d50012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff63750bbce93657a59fe3472fce714eafa09791fcf7f687f30a923162f2ba5196010000006c493046022100bbbf84829fcc2ec70bc6d77cfc69f512c1a14359958eee46243001908dc2a0ab0221008f1fbda61fcfccb78fe6d4e6385e8f508035676ef82654425bb704727f1e59b4012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff6466da482404f4a719f7eb16798d05878af2c36ad7174e2b68964693f39e954b010000006a47304402204d57344da5a1a29ea800215d19ada89787b1026f7e47c2f2f1ea0ef82bec5b6d02203039bd98546843a99d9e6749819875a4d996a682c57a192d9e5cef9b694a028b012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff8b0b4a84522fded19446eef3fdd94cc0f7449c71b6e0080837d5f240c78ce03b010000006c493046022100c152177ec49bb572d70976b53c10d0c4be55584975d657c43e87fbaac8c081ec0221009dd150697257cf769c3e90afbde88fbbe5f95c17c561883546537644ed628f6f012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff8d7078622b75fc2c3ea1094d07099b0e460a7f7a4c53cf225d066f919f17daf6010000006b483045022100e440d404867748cfba792119faae12d286b265a185cec86215fe2737ec1e7ca402207770447154f81564f7022b375943c2b7eaf3d05a3281c6f5c70328b098423d7d012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff98c23cc59412943bfedba3b4a48bb2f97f58c119946e5c492031c43a36dd576e010000006c493046022100910cf6fb057269e5e02fa44fc2ba03925d9e0e3232d3d5a66aac440db9627f9f022100b656d982dec47000de616f21a331b1fb5e19d1ab312c5845f5f1538dac4dd301012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff9d4851f00e3c2fa22816adc55703fcb539ae0fe218f369f23af079964a6225fc020000006c4930460221009918ee137e4aead4760c79dbe940556ae1ecb7935a653543b486f4198f16cc6a022100f82e04cd970f2c5fd8dd48813e38f87c10ed8fa7b45eec1854562948f9d43a1b012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffffa13c3221f0e08289657208bccf7b466ea5795c591751065a20b16f00892bd598010000006b483045022073d9fed13def14a655fd423f5c4fa63e46eeea76668cdf8bb89d96630890760d022100f70edce3513c9cbc671f92dc0b4d97c5edc0d9d26f4e726bb2d66776a3b9e411012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffffcac4f229bd19c47cd15ee9355af8383531a960ba0e0f3e8e4fa0a607ab2000d9010000006b483045022100967624e60a7670e849eb7500cf185620fd65de10d1e5f7cef9131d3c6403cb5f022005182af16fba1b7dbdd27a8935205b439c6034d566c6f14950aba6bb328cbf79012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffffcbf8cb94ee2bcda1c9ceb54feaf6815441f722b70c4f7569525cc9dee7cbbdc2010000006b4830450221008cfcfdc62f0a398e2419ebd56cf067e2abadf8116936250939b9fa763dd428680220052c6d316189d5f7164d2423aae99e97d05165f3e5c7d138e2858f0adab4ebba012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffffdbad6da5900987f77e5bcf714c935889fbea2d3ff388586a331fe42e0a82efe0010000006c493046022100e80d73130bcd25faa73764f4ff6c05e1b401f3960b7ef30b4244daaf5fce953a022100b99a55caaaa312df54c7d743791052c3e8392725becf91d2aa886d2e8259af10012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689fffffffffdc2d56fd131ae16837fc86e3015c9e78077dd36b6a2591cf1d500c584bbcc6a010000006b483045022100d13e5a55a4a71e039603bd2d3d76a757c63b1d199bcf340e3f2eeb5bed10897c022046a43ecc6cd8295981bde38c34c29708e402db59fc93e657196fc3032858d967012103954bfa8b6b1b0f1f5624ea2925b18cd1477fde2087eada1a51323a6617172689ffffffff0240d6de1b1200000017a91415c85c2472f5941b60a49462a2cfd0d17ab49d1c87c02fdf67000000001976a914b8d899f7193a7b3278be037b006c8f08998ebef388ac00000000",
    "txid" : "a8b3bf5bcace91a8dbbddbf9b7eb027efb9bd001792f043ecf7b558aaa3cb951",
    "version" : 1,
    "locktime" : 0,
[...]
    "vout" : [
        {
            "value" : 777.77000000,
            "n" : 0,
            "scriptPubKey" : {
                "asm" : "OP_HASH160 15c85c2472f5941b60a49462a2cfd0d17ab49d1c OP_EQUAL",
                "hex" : "a91415c85c2472f5941b60a49462a2cfd0d17ab49d1c87",
                "reqSigs" : 1,
                "type" : "scripthash",
                "addresses" : [
                    "2MuEQCZh7VB8pNrT4bj1CFZQh2oK7XZYLQf"
                ]
            }
        },
[...]
    ],
    "blockhash" : "000000034def806f348cadf6a80660aed1cfc30ccbd1492a8ea87062800ea94d",
    "confirmations" : 3,
    "time" : 1409224896,
    "blocktime" : 1409224896
}

Step 4: Spending the multisig¶

Now we assume the deal is complete, the buyer got the goods and everyone is happy. Now the seller wants to get his Dash. As a 2-of-3 multisig was used, the transaction must be signed by 2 parties (seller + buyer or arbiter). The seller creates a transaction (we will reuse his public address from above).

Seller:

seller@testnet03:~$ ./dash-cli createrawtransaction '[{"txid":"a8b3bf5bcace91a8dbbddbf9b7eb027efb9bd001792f043ecf7b558aaa3cb951","vout":0}]' '{"n18cPEtj4ZfToPZxRszUz2XPts4eGsxiPk":777.77}'
010000000151b93caa8a557bcf3e042f7901d09bfb7e02ebb7f9dbbddba891ceca5bbfb3a80000000000ffffffff0140d6de1b120000001976a914d728be76cd74b5d148eba2a49246b80dac12f73e88ac00000000

And partially signs it, using the redeemScript, scriptPubKey and his private key

Seller:

seller@testnet03:~$ ./dash-cli signrawtransaction '010000000151b93caa8a557bcf3e042f7901d09bfb7e02ebb7f9dbbddba891ceca5bbfb3a80000000000ffffffff0140d6de1b120000001976a914d728be76cd74b5d148eba2a49246b80dac12f73e88ac00000000' '[{"txid":"a8b3bf5bcace91a8dbbddbf9b7eb027efb9bd001792f043ecf7b558aaa3cb951","vout":0,"scriptPubKey":"a91415c85c2472f5941b60a49462a2cfd0d17ab49d1c87","redeemScript":"522102a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e210315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c210287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce53ae"}]' '["cVQVgBr8sW4FTPYz16BSCo1PcAfDhpJArgMPdLxKZQWcVFwMXRXx"]'
{
    "hex" : "010000000151b93caa8a557bcf3e042f7901d09bfb7e02ebb7f9dbbddba891ceca5bbfb3a800000000b500483045022051a7f0e95a5066859ce37fe64a6e7ab6e30bfe9a68d9d3f1453064052eab5625022100c0067a33d2ee02478d89fc1a71f3a93c883db022e970886181c50ca9afc3dfa4014c69522102a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e210315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c210287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce53aeffffffff0140d6de1b120000001976a914d728be76cd74b5d148eba2a49246b80dac12f73e88ac00000000",
    "complete" : false
}

Note that the output hex is getting longer, but complete flag is «false» as the transaction needs another signature. So now either the buyer or the arbiter can complete the signature of the transaction, using the output from above and their private key. Let’s assume the buyer is completing the signature.

Buyer:

buyer@testnet03:~$ ./dash-cli signrawtransaction '010000000151b93caa8a557bcf3e042f7901d09bfb7e02ebb7f9dbbddba891ceca5bbfb3a800000000b500483045022051a7f0e95a5066859ce37fe64a6e7ab6e30bfe9a68d9d3f1453064052eab5625022100c0067a33d2ee02478d89fc1a71f3a93c883db022e970886181c50ca9afc3dfa4014c69522102a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e210315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c210287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce53aeffffffff0140d6de1b120000001976a914d728be76cd74b5d148eba2a49246b80dac12f73e88ac00000000' '[{"txid":"a8b3bf5bcace91a8dbbddbf9b7eb027efb9bd001792f043ecf7b558aaa3cb951","vout":0,"scriptPubKey":"a91415c85c2472f5941b60a49462a2cfd0d17ab49d1c87","redeemScript":"522102a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e210315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c210287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce53ae"}]' '["cP9DFmEDb11waWbQ8eG1YUoZCGe59BBxJF3kk95PTMXuG9HzcxnU"]'
{
    "hex" : "010000000151b93caa8a557bcf3e042f7901d09bfb7e02ebb7f9dbbddba891ceca5bbfb3a800000000fdff0000483045022051a7f0e95a5066859ce37fe64a6e7ab6e30bfe9a68d9d3f1453064052eab5625022100c0067a33d2ee02478d89fc1a71f3a93c883db022e970886181c50ca9afc3dfa401493046022100dc3f61fdb7b8ea7ec729682d355646c922f5512054c4985534e6b91040c5bd660221008b48c117ec95814f573d33bca981cb703fdd9fa6e52aa8fe67423e06cad87215014c69522102a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e210315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c210287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce53aeffffffff0140d6de1b120000001976a914d728be76cd74b5d148eba2a49246b80dac12f73e88ac00000000",
    "complete" : true
}

The signature is complete now, and either of the parties can transmit the transaction to the network.

Buyer:

buyer@testnet03:~$ ./dash-cli sendrawtransaction 010000000151b93caa8a557bcf3e042f7901d09bfb7e02ebb7f9dbbddba891ceca5bbfb3a800000000fdff0000483045022051a7f0e95a5066859ce37fe64a6e7ab6e30bfe9a68d9d3f1453064052eab5625022100c0067a33d2ee02478d89fc1a71f3a93c883db022e970886181c50ca9afc3dfa401493046022100dc3f61fdb7b8ea7ec729682d355646c922f5512054c4985534e6b91040c5bd660221008b48c117ec95814f573d33bca981cb703fdd9fa6e52aa8fe67423e06cad87215014c69522102a862b412ff9e3afd01a2873a02622897f6df92e3fc85597788b898309fec882e210315617694c9d93f0ce92769e050a6868ffc74d229077379c0af8bfb193c3d351c210287ce6cf69b85593ce7db801874c9a2fb1b653dbe5dd9ebfa73e98b710af9e9ce53aeffffffff0140d6de1b120000001976a914d728be76cd74b5d148eba2a49246b80dac12f73e88ac00000000
cf1a75672006a05b38d94acabb783f81976c9e83a8de4da9cbec0de711cf2d71

Again, this transaction can be traced in a block explorer. And the seller is happy to receive his coins at his public address as follows.

Seller:

seller@testnet03:~$ dash-cli listtransactions "" 1
[
    {
        "account" : "",
        "address" : "n18cPEtj4ZfToPZxRszUz2XPts4eGsxiPk",
        "category" : "receive",
        "amount" : 777.77000000,
        "confirmations" : 17,
        "blockhash" : "000000067a13e9bd5c1d5ff48cb4b9f8414a6adcc470656262731bfd013510dd",
        "blockindex" : 9,
        "blocktime" : 1409228449,
        "txid" : "cf1a75672006a05b38d94acabb783f81976c9e83a8de4da9cbec0de711cf2d71",
        "time" : 1409227887,
        "timereceived" : 1409227887
    }
]

Multiple wallets¶

It is possible to select between different Dash wallets when starting Dash Core by specifying the wallet argument, or even run multiple instances of Dash Core simultaneously by specifying separate data directories using the datadir argument.

To begin, install the Dash Core wallet for your system according to the installation instructions. When you get to the step Running Dash Core for the first time, you can decide whether you want to maintain separate wallet.dat files in the default location (simpler if you do not need to run the wallets simultaneously), or specify entirely separate data directories such as e.g. C:\Dash1 (simpler if you do want to run the wallets simultaneously).

Separate wallet.dat files¶

For this scenario, we will create two shortcuts on the desktop, each using a different wallet file. Navigate to the binary file used to start Dash Core (typically locatd at C:\Program Files\DashCore\dash-qt.exe or similar) and create two shortcuts on the desktop. Then open the Properties window for each of these shortcuts.

Creating desktop shortcuts using Windows 10

Modify the Target property of each shortcut to point to a different wallet file by specifying the wallet argument when starting the wallet. If you do not specify a wallet argument, wallet.dat will be used by default. The specified wallet file will be created if it does not exist. The following example demonstrates two wallets named workwallet.dat and homewallet.dat:

Wallet Target 1: "C:\Program Files\DashCore\dash-qt.exe" -wallet=workwallet.dat
Wallet Target 2: "C:\Program Files\DashCore\dash-qt.exe" -wallet=homewallet.dat

Specifying separate wallet files

You can now use the two icons to quickly and easily open different wallets from your desktop. Note that you cannot open both wallets simultaneously. To do this, you will need two separate data directories, as described below.

Separate data directories¶

Start Dash Core and allow it to synchronize with the network, then close Dash Core again. You can now create two directories at e.g. C:\Dash1 and C:\Dash2 and copy the blocks and chainstate directories from the synchronized data directory into the new directories. Each of these will serve as a separate data directory, allowing you to run two instances of Dash Core simultaneously. Create two (or more) shortcuts on your desktop as described above, then specify arguments for datadir as shown below:

Datadir Target 1: "C:\Program Files\DashCore\dash-qt.exe" -datadir=C:\Dash1 -listen=0
Datadir Target 2: "C:\Program Files\DashCore\dash-qt.exe" -datadir=C:\Dash2 -listen=0

Specifying separate datadirs

You can now use the two icons to quickly and easily open different wallets simultaneously from your desktop. Both wallets maintain separate and full copies of the blockchain, which may use a lot of drive space. For more efficient use of drive space, consider using an SPV or «light» wallet such as Dash Electrum to maintain multiple separate wallets without keeping a full copy of the blockchain.

Two instances of Dash Core running simultaneously

KeePass¶

Since version 0.11.0, Dash Core has supported integration with KeePass, the popular open source password manager. This guide describes how to configure the association between Dash Core and KeePass, and how to save a Dash Core wallet passphrase in KeePass using the integration. When this is done, KeePass can be used to unlock the wallet.

Instalação¶

You will need the following:

KeePass 2: http://keepass.info
KeePassHttp plugin: https://github.com/pfn/keepasshttp
Dash Core: https://www.dash.org

If not already installed, install these packages according to the instructions linked below:

KeePass: https://keepass.info/help/v2/setup.html
KeePassHttp: https://github.com/pfn/keepasshttp/blob/master/README.md
Dash Core: https://docs.dash.org/en/stable/wallets/dashcore/installation.html

Commands¶

The following KeePass RPC commands are available in the Dash Core client console or server:

keepass genkey: Generates a base64 encoded 256 bit AES key that can be used for communication with KeePassHttp. This is only necessary for manual configuration. Use init for automatic configuration.
keepass init: Sets up the association between Dash and KeePass by generating an AES key and sending an association message to KeePassHttp. This will trigger KeePass to ask for an ID for the association. Returns the association and the base64 encoded string for the AES key.
keepass setpassphrase: Updates the passphrase in KeePassHttp to a new value. This should match the passphrase you intend to use for the wallet. Please note that the standard RPC commands walletpassphrasechange and the wallet encryption from the QT GUI already send the updates to KeePassHttp, so this is only necessary for manual manipulation of the password.

The following new arguments are available for dashd and dash-qt:

keepass: Use KeePass 2 integration using KeePassHttp plugin (default: 0)
keepassport=<port>: Connect to KeePassHttp on port <port> (default: 19455)
keepasskey=<key>: KeePassHttp key for AES encrypted communication with KeePass
keepassid=<name>: KeePassHttp id for the established association
keepassname=<name>: Name to construct url for KeePass entry that stores the wallet passphrase

Carteira Dash Core

Carteira Dash Electrum¶

O Dash Electrum é uma carteira leve que usa poderosos servidores externos para indexar o blockchain, enquanto ainda protege as teclas do seu computador pessoal. As transações são verificadas no blockchain do Dash usando uma técnica chamada Verificação de Pagamento Seguro (Secure Payment Verification - SPV), que requer apenas os cabeçalhos de bloco e não o bloco inteiro. Isso significa que a inicialização da carteira é quase instantânea, mantendo os fundos seguros e móveis. Atualmente, não suporta recursos avançados do InstantSend e do PrivateSend.

O Dash Electrum é um fork da carteira Electrum para Bitcoin. Embora esta documentação se concentre no uso do Dash Electrum, a documentação completa de todos os recursos do Bitcoin Electrum (em sua maioria idênticos no Dash Electrum) está disponível no site de documentação oficial.

Instalação¶

Download¶

Você pode baixar o Dash Electrum no site oficial do Dash ou no minisite Dash Electrum.

Dash Electrum is developed by community member akhavr and is released through his GitHub account.

https://github.com/akhavr/electrum-dash/releases

You can optionally verify the integrity of your download by running the following commands (example for Linux):

wget https://github.com/akhavr/electrum-dash/releases/download/3.3.8.2/Dash-Electrum-3.3.8.2.tar.gz
wget https://github.com/akhavr/electrum-dash/releases/download/3.3.8.2/SHA256SUMS.txt.asc
sha256sum Dash-Electrum-3.3.8.2.tar.gz
cat SHA256SUMS.txt.asc

You can also optionally verify the authenticity of your download as an official release by akhavr. All releases of Dash Electrum are signed by akhavr using GPG with the key 64A3 BA82 2F44 9D50, verifiable here on Keybase. Import the key, download the ASC file for the current release of Dash Electrum and verify the signature as follows:

curl https://keybase.io/akhavr/pgp_keys.asc | gpg --import
gpg --verify SHA256SUMS.txt.asc

Linux¶

O Dash Electrum para Linux está disponível a partir de um PPA para o Ubuntu e Linux Mint e como um tarball de origem para outros sistemas. A partir da versão 3.0.6, requer que o Python 3 seja executado. Digite os seguintes comandos para instalar a partir do PPA:

sudo add-apt-repository ppa:akhavr/dash-electrum
sudo apt update
sudo apt install electrum-dash

Digite os seguintes comandos (alterando o número da versão para coincidir com a versão atual, conforme necessário) no terminal para instalar o Dash Electrum a partir do source de origem:

sudo apt install python3-pyqt5 python3-pip python3-setuptools
wget https://github.com/akhavr/electrum-dash/releases/download/3.3.8.2/Dash-Electrum-3.3.8.2.tar.gz
tar -zxvf Dash-Electrum-3.3.8.2.tar.gz
cd Dash-Electrum-3.3.8.2
sudo python3 setup.py install

You can then run electrum-dash from the terminal.

macOS¶

Basta baixar e executar o arquivo DMG. Talvez seja necessário conceder permissão para instalar, dependendo das configurações de segurança. Clique no assistente de instalação e execute o Dash Electrum na sua pasta Aplicativos quando estiver completo.

Windows¶

Basta baixar e executar o arquivo de instalação para configurar o Dash Electrum. Talvez seja necessário conceder permissão para instalar, dependendo das configurações de segurança. Clique no assistente de instalação e execute o Dash Electrum no menu Iniciar quando terminar.

Android¶

Faça o download e execute o arquivo APK em https://electrum.dash.org para configurar o Dash Electrum. Talvez seja necessário conceder permissão para instalar a partir de fontes desconhecidas, dependendo das configurações de segurança. Clique no assistente de instalação e execute o Dash Electrum quando terminar.

Criando uma nova carteira¶

O Dash Electrum reúne dados de configuração quando executado pela primeira vez. Para mais informações sobre os conceitos por trás deste processo, pule para as seções posteriores deste guia, discutindo backups, segurança e endereços. Ao configurar o Dash Electrum pela primeira vez, um assistente irá guiá-lo através do processo de criação de sua primeira carteira. A primeira tela pergunta como você gostaria de se conectar ao servidor remoto. Selecione Conexão automática e clique em Avançar para continuar. Você verá um aviso de que nenhuma carteira existe atualmente. Digite um nome para sua carteira (ou aceite o nome padrão) e clique em Avançar para criar sua carteira.

Selecionando o servidor e nomeando sua primeira carteira

Você será perguntado que tipo de carteira você quer criar. Escolha entre Carteira padrão, Carteira multi-assinatura e Endereços do painel de acompanhamento. Se não tiver certeza, selecione Carteira padrão e clique em Próximo para continuar. Você será perguntado como deseja armazenar/recuperar a semente. Se armazenado com segurança, uma semente pode ser usada para restaurar uma carteira perdida em outro computador. Escolha entre Crie uma nova semente, Eu já possuo uma nova semente, Utilizar chaves públicas ou privadas ou Utilizar um dispositivo de hardware. Se você estiver usando o Electrum Dash pela primeira vez e não estiver restaurando uma carteira existente, escolha Crie uma nova semente e clique em Avançar para continuar.

Selecionando o tipo de carteira e keystore

O Electrum Dash gerará sua carteira e exibirá a semente de recuperação. Escreva essa semente, idealmente em papel e não em formato eletrônico, e guarde-a em algum lugar seguro. Essa semente é a única maneira de recuperar sua carteira se você perder o acesso por qualquer motivo. Para ter certeza de que você salvou sua semente corretamente, a Electrum Dash pedirá que você a digite como uma confirmação. Digite as palavras na ordem correta e clique em Proximo para continuar.

Gerando e confirmando a semente de recuperação

Uma senha opcionalmente protege sua carteira contra acesso não autorizado. Adicionar uma senha forte e memorável melhora a segurança de sua carteira criptografando sua semente desde o início. Ignorar a criptografia neste ponto, ao não selecionar uma senha, arrisca um possível roubo de fundos posteriormente, por mais improvável que seja a ameaça. Digite e confirme uma senha, verifique se a caixa de seleção Criptografar arquivo da carteira está marcada e clique em Proximo para continuar.

Entrando e confirmando uma senha criptografica da carteira

Sua carteira Dash Electrum está agora pronta para uso.

O Dash Electrum após a conclusão da instalação

Enviando e recebendo¶

Você pode possuir o Dash armazenado em outra carteira de software, ou em uma bolsa como Bittrex ou Kraken, ou simplesmente desejar enviar ou receber fundos como uma transação salarial ou comercial. Os fundos podem ser transferidos entre essas fontes e a carteira Electrum usando os endereços do Dash. Sua carteira contém vários endereços e gerará novos endereços conforme necessário. Como o blockchain do Dash é transparente para o público, considera-se como prática recomendada usar um novo endereço para cada transação, a fim de manter sua privacidade.

Enviando¶

Clique na guia Enviar para efetuar um pagamento. Digite o endereço de destino no campo Pagar para, manualmente ou colando na área de transferência. Opcionalmente, insira uma Descrição para aparecer no seu histórico de transações, seguido pelo Quantidade a ser enviado. O valor total da transação é a soma do valor enviado e da taxa de transação, que é calculada automaticamente. A Dash Electrum emite um aviso se o valor total da transação exceder o saldo da carteira.

Transação pronta para enviar a carteira Dash Electrum

A carteira solicitará sua senha, então transmitirá a transação para a rede e exibirá uma caixa de diálogo de confirmação com o ID da transação.

Prompt de senha e confirmação de transação na carteira Dash Electrum

Recebendo¶

Você pode visualizar seus endereços de recebimento clicando na guia Receber. Clique duas vezes no Endereço de recebimento e copie-o para a área de transferência clicando no ícone Copiar para a área de transferência. Se você pretende usar o endereço repetidamente, também é possível inserir uma descrição. Clique em Salvar para armazenar o endereço na lista Solicitações. Clicar em um endereço na lista exibirá as informações armazenadas na área superior, junto com um código QR contendo as mesmas informações.

Transação pronta para enviar a carteira Dash Electrum

Digite este endereço no software enviando os fundos, envie-o para a pessoa que transfere fundos para você ou digitalize-o diretamente da sua carteira móvel. Quando a transação estiver concluída, o saldo aparecerá no canto inferior esquerdo de sua carteira, e o indicador na tabela Requisição mudará de Pendente para Pago.

Pagamento recebido com sucesso na carteira do Dash Electrum

Depois de usar um endereço, você pode continuar a usá-lo ou clicar em Nova para gerar um novo endereço.

Monitorando transações¶

A guia Histórico lista todas as transações atuais e pendentes. Uma transação para um endereço em sua carteira aparecerá na lista logo após ser feita. Inicialmente, esta transação será marcada como Não confirmada, seguida por um indicador de relógio à esquerda. Como a rede do Dash processa a transação, o status será atualizado na lista do histórico de transações. A rede confirma transações com um novo bloco aproximadamente a cada 2,5 minutos, e uma transação é considerada confirmada (e, portanto, utilizável) após seis confirmações. Essas transações processadas são indicadas com uma marca de seleção verde e o registro de data e hora em que a transação foi feita.

A guia Histórico da carteira do Dash Electrum imediatamente após o recebimento de uma transação e após a conclusão da confirmação

Para visualizar detalhes adicionais da transação, clique com o botão direito do mouse em uma transação na guia Histórico e selecione Detalhes no menu de contexto. Você também pode usar esse menu para copiar o ID da transação para a área de transferência (isso pode ser usado como prova de que uma transação ocorreu), editar a descrição da transação para seus registros ou visualizar a transação em um explorador de bloco externo.

Detalhes da transação na carteira Dash Electrum

Carteira Segura¶

Alterar senha¶

Para alterar a senha da carteira, selecione a opção Carteira > Senha no menu principal ou clique no ícone de bloqueio no canto inferior direito da janela principal. Digite e confirme uma nova senha segura. Se você esquecer a senha de sua carteira, nem tudo está perdido. Sua carteira pode ser restaurada em sua totalidade usando o procedimento de backup descrito aqui.

Backup¶

No Dash Electrum, uma semente é um backup completo de todos os endereços e transações. Acesse a semente da sua carteira através do ícone de semente no canto inferior direito da tela principal, ou a opção do menu principal Carteira > Semente. Quando solicitado, digite a senha segura que você escolheu ao configurar a carteira do Dash Electrum.

Exibindo a semente de recuperação de carteira no Dash Electrum

Faça uma cópia manual das doze palavras encontradas na caixa em um pedaço de papel e armazene-a em um local seguro. Lembre-se, qualquer um que encontrar sua semente pode gastar todos os fundos em sua carteira.

Visualizando a semente de recuperação

Como alternativa, um arquivo de backup pode ser salvo usando a opção do menu principal Arquivo > Salvar cópia. Este arquivo armazena a semente criptografada da carteira junto com os endereços importados. Restaurar este backup exigirá a senha da carteira.

Restaurar¶

A única coisa necessária para recuperar uma carteira Dash Electrum em outro computador é a sua semente. Você pode testar a recuperação da carteira com a sua instalação atual do Dash Electrum, selecionando o item de menu Arquivo > Novo/Restaurar. Uma caixa de diálogo aparecerá pedindo para você nomear sua nova carteira. Digite um nome, selecione Carteira padrão ** como o tipo de carteira e, em seguida, escolha **Eu já possuo uma semente.

Restaurando uma carteira de uma semente existente

Em seguida, copie a semente de doze palavras para o campo de texto.

Entrando na semente de recuperação

Se a sua semente foi inserida corretamente, a Dash Electrum lhe dá a opção de adicionar uma senha para sua carteira. Depois de restaurar sua carteira, a Dash Electrum listará todas as transações existentes nessa carteira. Esse processo pode demorar alguns minutos e as transações podem aparecer como Não verificado. Esse problema desaparece depois de reiniciar o programa.

Transações não verificadas após a recuperação

Para restaurar um arquivo de carteira sem usar a semente de recuperação, copie o arquivo para a pasta de dados do aplicativo de acordo com o sistema operacional:

Linux: Abrir arquivos, selecione Ir > Ir para a pasta, copie o caminho ~/.electrum-dash e cole-o na caixa de diálogo.
macOS: Abra o Finder, selecione Ir > Ir para pasta, copie o caminho ~/.electrum-dash e cole-o na caixa de diálogo.
Windows: Abra o Explorer, copie o caminho %APPDATA%\Electrum-DASH e cole-o na barra de endereço.

Frequently Asked Questions¶

How does Dash Electrum work?¶

Dash Electrum focuses on speed, low resource usage and providing a simple user experience for Dash. Startup times are instant because it operates in conjunction with high-performance servers that handle the most complicated parts of the Dash system.

Does Dash Electrum trust servers?¶

Not really; the Dash Electrum client never sends private keys to the servers. In addition, it verifies the information reported by servers using a technique called Simple Payment Verification.

What is the Seed?¶

The seed is a random phrase that is used to generate your private keys. Example:

constant forest adore false green weave stop guy fur freeze giggle clock

Your wallet can be entirely recovered from its seed. To do this, select the I already have a seed option during startup.

How secure is the seed?¶

The seed created by Dash Electrum has 128 bits of entropy. This means that it provides the same level of security as a Dash private key (of length 256 bits). Indeed, an elliptic curve key of length n provides n/2 bits of security.

What are change addresses?¶

The Dash Electrum wallet design and workflow are based on a concept called a “wallet generation seed”. This seed is a unique, randomly- selected list of twelve words. A Dash Electrum wallet uses its seed as a template for generating addresses.

To understand the problem that seeds solve, browse to the Electrum Receive tab. Next, open the collapsible entry marked Change.

Receiving and change addresses in Dash Electrum

Notice that the total balance does not only show the sum of all receiving addresses, but also the separately listed Change addresses. Where did these new change addresses come from and why does the first one now hold funds?

Dash is an electronic cash system, meaning that it shares much in common with the process of using paper banknotes. Although some cash payments involve exact change, many do not. You tend to “overpay” when using cash, and expect to receive the difference as change. Perhaps surprisingly, this is how Dash transactions work as well. If the entire balance of an address is not required for any given transaction, the remainder is sent to a new and unused address under control of the same wallet. This address is generated deterministically (rather than randomly) from the wallet seed, which means that any other wallet will also regenerate the change addresses in the same order from the same recovery seed, and have access to the balances.

Spending the entire balance and sending any remainder to a change address is considered good practice because it prevents the transaction recipient from linking transactions by browsing the blockchain, thus compromising your privacy. If privacy is not a concern, change addresses can be disabled via the Tools > Electrum preferences menu option.

How can I send the maximum available in my wallet?¶

Type an exclamation mark (!) in the Amount field or simply click the Max button. The fee will be automatically adjusted for that amount.

How can I send Dash without paying a transaction fee?¶

You can create a zero fee transaction in the GUI by following these steps:

Enable the Edit fees manually option
Enter 0 in the Fee field
Enter the amount in the Amount field

Note that transactions without fees might not be relayed by the Dash Electrum server, or by the Dash network.

Is there a way to enter amounts in USD in Dash Electrum?¶

Yes, go to Tools > Prefernce > Fiat and select a Fiat currency to display the current exchange rate from the chosen Source.

Entering values in fiat currency in Dash Electrum

What does it mean to “Freeze” an address in Dash Electrum?¶

When you freeze an address, the funds in that address will not be used for sending Dash. You cannot send Dash if you don’t have enough funds in your non-frozen addresses.

How is the wallet encrypted?¶

Dash Electrum uses two separate levels of encryption:

Your seed and private keys are encrypted using AES-256-CBC. The private keys are decrypted only briefly, when you need to sign a transaction; for this you need to enter your password. This is done in order to minimize the amount of time during which sensitive information is unencrypted in your computer’s memory.

In addition, your wallet file may be encrypted on disk. Note that the wallet information will remain unencrypted in the memory of your computer for the duration of your session. If a wallet is encrypted, then its password will be required in order to open it. Note that the password will not be kept in memory; Dash Electrum does not need it in order to save the wallet on disk, because it uses asymmetric encryption (ECIES).

Wallet file encryption is activated by default since version 2.8. It is intended to protect your privacy, but also to prevent you from requesting Dash on a wallet that you do not control.

I have forgotten my password but still have my seed. Is there any way I can recover my password?¶

It is not possible to recover your password. However, you can restore your wallet from its seed phrase and choose a new password. If you lose both your password and your seed, there is no way to recover your money. This is why we ask you to save your seed phrase on paper.

To restore your wallet from its seed phrase, create a new wallet, select the type, choose I already have a seed and proceed to input your seed phrase.

Does Dash Electrum support cold wallets?¶

Yes. See the cold storage section.

Can I import private keys from other Dash clients?¶

In Dash Electrum 2.0, you cannot import private keys in a wallet that has a seed. You should sweep them instead.

If you want to import private keys and not sweep them you need to create a special wallet that does not have a seed. For this, create a new wallet, select Use public or private keys, and instead of typing your seed, type a list of private keys, or a list of addresses if you want to create a watching-only wallet. A master public (xpub) or private (xprv) will also work to import a hierarchical deterministic series of keys. You will need to back up this wallet, because it cannot be recovered from seed.

Importing a list of private keys to create a wallet

Can I sweep private keys from other Dash clients?¶

Sweeping private keys means to send all the Dash they control to an existing address in your wallet. The private keys you sweep do not become a part of your wallet. Instead, all the Dash they control are sent to an address that has been deterministically generated from your wallet seed.

To sweep private keys go to Wallet > Private Keys > Sweep. Enter the private keys in the appropriate field. Leave the Address field unchanged. This is the destination address from your existing Dash Electrum wallet. Click on Sweep. Dash Electrum then takes you to the Send tab where you can set an appropriate fee and then click on Send to send the coins to your wallet.

Where is my wallet file located?¶

The default wallet file is called default_wallet and is created when you first run the application. It is located under the /wallets folder.

Linux: Open Files, select Go > Go to folder, copy the path ~/.electrum-dash and paste it into the dialog box
macOS: Open Finder, select Go > Go to Folder, copy the path ~/.electrum-dash and paste it into the dialog box
Windows: Open Explorer, copy the path %APPDATA%\Electrum-DASH and paste it in to the address bar

Can I do bulk payments with Dash Electrum?¶

You can create a transaction with several outputs. In the GUI, type each address and amount on a line, separated by a comma.

Creating a transaction with multiple outputs in Dash Electrum

Amounts are in the current unit set in the client. The total is shown in the GUI. You can also import a CSV file in the Pay to field by clicking on the folder icon.

Can Dash Electrum create and sign raw transactions?¶

Dash Electrum lets you create and sign raw transactions right from the user interface using a form.

Dash Electrum freezes when I try to send Dash¶

This might happen if you are trying to spend a large number of transactions outputs (for example, if you have collected hundreds of donations from a Dash faucet). When you send Dash, Dash Electrum looks for unspent coins that are in your wallet in order to create the new transaction. Unspent coins can have different values, much like physical coins and bills.

If this happens, you should consolidate your transaction inputs by sending smaller amounts of Dash to one of your wallet addresses; this would be the equivalent of exchanging a stack of nickels for a dollar bill.

What is the gap limit?¶

The gap limit is the maximum number of consecutive unused addresses in your deterministic sequence of addresses. Dash Electrum uses it in order to stop looking for addresses. In Dash Electrum 2.0, it is set to 20 by default, so the client will get all addresses until 20 unused addresses are found.

How can I pre-generate new addresses?¶

Dash Electrum will generate new addresses as you use them, until it hits the gap limit.

If you need to pre-generate more addresses, you can do so by typing wallet.create_new_address() in the console. This command will generate one new address. Note that the address will be shown with a red background in the address tab, to indicate that it is beyond the gap limit. The red color will remain until the gap is filled.

WARNING: Addresses beyond the gap limit will not automatically be recovered from seed. To recover them will require either increasing the client’s gap limit or generating new addresses until the used addresses are found.

If you wish to generate more than one address, you may use a ‘for’ loop. For example, if you wanted to generate 50 addresses, you could do this:

for x in range(0, 50):
  print wallet.create_new_address()

How to upgrade Dash Electrum?¶

Warning: always save your wallet seed on paper before doing an upgrade.

To upgrade Dash Electrum, just install the most recent version. The way to do this will depend on your OS. Note that your wallet files are stored separately from the software, so you can safely remove the old version of the software if your OS does not do it for you.

Some Dash Electrum upgrades will modify the format of your wallet files. For this reason, it is not recommended to downgrade Dash Electrum to an older version once you have opened your wallet file with the new version. The older version will not always be able to read the new wallet file.

The following issues should be considered when upgrading Dash Electrum 1.x wallets to Dash Electrum 2.x:

Dash Electrum 2.x will need to regenerate all of your addresses during the upgrade process. Please allow it time to complete, and expect it to take a little longer than usual for Dash Electrum to be ready.
The contents of your wallet file will be replaced with a Dash Electrum 2 wallet. This means Dash Electrum 1.x will no longer be able to use your wallet once the upgrade is complete.
The Addresses tab will not show any addresses the first time you launch Dash Electrum 2. This is expected behaviour. Restart Dash Electrum 2 after the upgrade is complete and your addresses will be available.
Offline copies of Dash Electrum will not show the addresses at all because it cannot synchronize with the network. You can force an offline generation of a few addresses by typing the following into the Console: wallet.synchronize(). When it’s complete, restart Dash Electrum and your addresses will once again be available.

Funções Avançadas¶

Dash Electrum is based on Electrum, a Bitcoin wallet. Most functions are identical, which means it is not necessary to reproduce the entirety of the Electrum documentation here. The following sections describe some frequently used advanced functions. For further details on other advanced functions in Electrum for both Bitcoin and Dash, please click the links below.

Masternodes in Dash Electrum¶

Dash Electrum supports masternode creation through an interface called the Masternode Manager. The functionality is available starting from the protocol version 70201.

Masternode Manager¶

The Masternode Manager can be accessed either from the Wallet > Masternodes menu or by pressing Ctrl+M. This manager displays the status of your masternode(s). A wallet with no masternodes will begin with a default masternode for which you can fill in the necessary information.

The manager displays the following data about each masternode you have set up:

The alias (name) of the masternode.
The status of the masternode (e.g. whether it has been activated).
The collateral payment of the masternode.
The private delegate key.
The IP address and port that your masternode can be reached at.
The protocol version that your masternode supports.

Masternode setup¶

A masternode requires a «delegate» key, which is known to both Dash Electrum and your masternode. Your masternode will use this key to sign messages, and the Dash network will know that you authorized it to. A delegate key can either be one of your Dash Electrum keys, or an imported key. Either way, your masternode and Dash Electrum will both need to know the private key.

To use one of your Dash Electrum keys as a delegate key, put its private key in the Masternode Private Key field of the View Masternode tab.

IP address and protocol version¶

Certain information about your masternode is required. The IP address and port that your masternode uses must be supplied. Also, the protocol version that your masternode supports is required. This information is filled in automatically if you import a «masternode.conf» file.

Entering IP and protocol information

Collateral¶

To start a masternode, you must have a 1000 DASH payment available in your wallet. You can scan your wallet for 1000 DASH payments in the Choose Collateral tab of the Masternode Manager.

After scanning, a list of available 1000 DASH collateral payments will be displayed. Selecting one of them will cause the selected masternode’s data to be filled in, though these changes won’t be saved until you click the Save button in the lower-right corner of the tab.

Entering IP and protocol information

Activating your masternode¶

After selecting a collateral payment and specifying a delegate key, you can activate your masternode. Do this by clicking Activate Masternode in the Activate Masternode tab of the Masternode Manager. If the Activate Masternode button cannot be clicked, look at the message in the Status bar. It will show you why your masternode cannot be activated.

Activation will require your password if your wallet is encrypted, because a message must be signed. After waiting for Dash Electrum to sign and broadcast your masternode announcement, you will be presented with a message detailing the result. The status of your masternode will be updated in the table and the View Masternode tab.

Entering IP and protocol information

Importing masternode.conf¶

You can import a masternode.conf file using the Masternode.conf tab of the Masternode Manager. This is the recommended way of setting up masternodes, as it allows you to configure masternodes for Dash Core and Dash Electrum in the same way. Importing a masternode.conf file will automatically set up one or more masternode configurations in the Masternode Manager.

Multisig wallets¶

This tutorial shows how to create a 2 of 2 multisig wallet. A 2 of 2 multisig consists of 2 separate wallets (usually on separate machines and potentially controlled by separate people) that have to be used in conjunction in order to access the funds. Both wallets have the same set of addresses.

A common use-case for this is if you want to collaboratively control funds: maybe you and your friend run a company together and certain funds should only be spendable if you both agree.
Another one is security: one of the wallets can be on your main machine, while the other one is on a offline machine. That way you make it very hard for an attacker or malware to steal your coins.

Create a pair of 2-of-2 wallets¶

Each cosigner needs to do this: In the menu select File > New, then select Multi-signature wallet. On the next screen, select 2 of 2.

Selecting x of y signatures for a multi-signature wallet

After generating and confirming your recovery seed, you will be shown the xpub address for this wallet.

xpub key of the first wallet

After generating a seed (keep it safely!) you will need to provide the master public key of the other wallet. Of course when you create the other wallet, you put the master public key of the first wallet.

Entering xpub from the second wallet in the first wallet

You will need to do this in parallel for the two wallets. Note that you can press cancel during this step, and reopen the file later.

Recebendo¶

Check that both wallets generate the same set of Addresses. You can now send to these Addresses (note they start with a “7”) with any wallet that can send to P2SH Addresses.

Enviando¶

To spend coins from a 2-of-2 wallet, two cosigners need to sign a transaction collaboratively. To accomplish this, create a transaction using one of the wallets (by filling out the form on the Send tab). After signing, a window is shown with the transaction details.

_images/faq-multisig-partially-signed.png

Partially signed 2-of-2 multisig transaction in Dash Electrum

The transaction now has to be sent to the second wallet. Several options are available for this:

You can transfer the file on a USB stick

You can save the partially signed transaction to a file (using the Save button), transfer that to the machine where the second wallet is running (via USB stick, for example) and load it there (using Tools > Load transaction > From file)
You can use QR codes

A button showing a QR code icon is also available. Clicking this button will display a QR code containing the transaction, which can be scanned into the second wallet (Tools > Load Transaction > From QR Code)

With both of the above methods, you can now add the second signature to the transaction (using the Sign button). It will then be broadcast to the network.

Fully signed 2-of-2 multisig transaction in Dash Electrum

Sweep a paper wallet¶

You may have received a paper wallet as a gift from another Dash user, or previously stored one in a safe deposit box. Funds are swept from a paper wallet into a live wallet by importing its private key, which is a long sequence of characters starting with the number «7» or the capital letter «X». The example below displays a private key (WIF format).

Public address and associated private key produced by Dash Paper Wallet Generator

Funds from paper wallets are swept into an Dash Electrum Wallet by creating a transaction using the private key and sending it to a new address from your wallet. This is necessary because it is not possible to add new public or private keys to an existing deterministic series of addresses derived from a seed phrase.

Begin by selecting the Wallet > Private Keys > Sweep menu item. The Sweep private keys dialog will appear, where you can paste your private key(s). An unused address controlled by your Dash Electrum wallet appears in the lower field, and can be changed by clicking the Address button. Once you have pasted your private key, click the Sweep button.

Entering the private key

Dash Electrum then prepares a transaction using the private key you just imported to derive the public address for the transaction input and the address from your wallet as the output, and signs the message. Click Broadcast to enter the transaction on the blockchain. The balance will then appear in your wallet under the specified address. The address you swept is left with zero balance.

Broadcasting the sweep transaction

Cold storage¶

This section shows how to create an offline wallet that holds your Dash and a watching-only online wallet that is used to view its history and to create transactions that have to be signed with the offline wallet before being broadcast on the online one.

Create an offline wallet¶

Create a wallet on an offline machine, as per the usual process (File > New). After creating the wallet, go to Wallet -> Master Public Keys.

Master Public Key of a new offline wallet

The Master Public Key of your wallet is the string shown in this popup window. Transfer that key to your online machine somehow.

Create a watching-only version of your wallet¶

On your online machine, open Dash Electrum and select File > New/Restore. Enter a name for the wallet and select Use public or private keys. Paste your master public key in the box. Click Next to complete the creation of your wallet. When you’re done, you should see a popup informing you that you are opening a watching-only wallet.

Master Public Key of a new offline wallet

The transaction history of your cold wallet should then appear.

Create an unsigned transaction¶

Go to the Send tab on your online watching-only wallet, input the transaction data and click Send. A window will appear to inform you that a transaction fee will be added. Continue. In the window that appears up, click Save and save the transaction file somewhere on your computer. Close the window and transfer the transaction file to your offline machine (e.g. with a USB stick).

Sign your transaction¶

On your offline wallet, select Tools > Load transaction -> From file in the menu and select the transaction file created in the previous step. Click Sign. Once the transaction is signed, the Transaction ID appears in its designated field. Click Save, store the file somewhere on your computer, and transfer it back to your online machine.

Broadcast your transaction¶

On your online machine, select Tools -> Load transaction -> From file from the menu. Select the signed transaction file. In the window that opens up, click Broadcast. The transaction will be broadcast over the Dash network.

Command line¶

Dash Electrum has a powerful command line available when running under Linux or macOS. This section will show you a few basic principles.

Using the inline help¶

To see the list of Dash Electrum commands, type:

electrum help

To see the documentation for a command, type:

electrum help <command>

Magic words¶

The arguments passed to commands may be one of the following magic words: ! ? : -.

The exclamation mark ! is a shortcut that means ‘the maximum amount available’. Note that the transaction fee will be computed and deducted from the amount. Example:

electrum payto Xtdw4fezqbSpC341vcr8u9HboiJMFa9gBq !

A question mark ? means that you want the parameter to be prompted. Example:

electrum signmessage Xtdw4fezqbSpC341vcr8u9HboiJMFa9gBq ?

Use a colon : if you want the prompted parameter to be hidden (not echoed in your terminal). Note that you will be prompted twice in this example, first for the private key, then for your wallet password:

electrum importprivkey :

A parameter replaced by a dash - will be read from standard input (in a pipe):

cat LICENCE | electrum signmessage Xtdw4fezqbSpC341vcr8u9HboiJMFa9gBq -

Aliases¶

You can use DNS aliases in place of bitcoin addresses, in most commands:

electrum payto ecdsa.net !

Formatting outputs using jq¶

Command outputs are either simple strings or json structured data. A very useful utility is the ‘jq’ program. Install it with:

sudo apt-get install jq

The following examples use it.

Sign and verify message¶

We may use a variable to store the signature, and verify it:

sig=$(cat LICENCE| electrum signmessage Xtdw4fezqbSpC341vcr8u9HboiJMFa9gBq -)

And:

cat LICENCE | electrum verifymessage Xtdw4fezqbSpC341vcr8u9HboiJMFa9gBq $sig -

Show the values of your unspents¶

The listunspent command returns a list of dict objects, with various fields. Suppose we want to extract the value field of each record. This can be achieved with the jq command:

electrum listunspent | jq 'map(.value)'

Select only incoming transactions from history¶

Incoming transactions have a positive ‘value’ field:

electrum history | jq '.[] | select(.value>0)'

Filter transactions by date¶

The following command selects transactions that were timestamped after a given date:

after=$(date -d '07/01/2015' +"%s")
electrum history | jq --arg after $after '.[] | select(.timestamp>($after|tonumber))'

Similarly, we may export transactions for a given time period:

before=$(date -d '08/01/2015' +"%s")
after=$(date -d '07/01/2015' +"%s")
electrum history | jq --arg before $before --arg after $after '.[] | select(.timestamp&gt;($after|tonumber) and .timestamp&lt;($before|tonumber))'

Encrypt and decrypt messages¶

First we need the public key of a wallet address:

pk=$(electrum getpubkeys Xtdw4fezqbSpC341vcr8u9HboiJMFa9gBq| jq -r '.[0]')

Encrypt:

cat | electrum encrypt $pk -

Decrypt:

electrum decrypt $pk ?

Note: this command will prompt for the encrypted message, then for the wallet password.

Export private keys and sweep coins¶

The following command will export the private keys of all wallet addresses that hold some Dash:

electrum listaddresses --funded | electrum getprivatekeys -

This will return a list of lists of private keys. In most cases, you want to get a simple list. This can be done by adding a jq filer, as follows:

electrum listaddresses --funded | electrum getprivatekeys - | jq 'map(.[0])'

Finally, let us use this list of private keys as input to the sweep command:

electrum listaddresses --funded | electrum getprivatekeys - | jq 'map(.[0])' | electrum sweep - [destination address]

Using cold storage with the command line¶

This section will show you how to sign a transaction with an offline Dash Electrum wallet using the command line.

Create an unsigned transaction¶

With your online (watching-only) wallet, create an unsigned transaction:

electrum payto Xtdw4fezqbSpC341vcr8u9HboiJMFa9gBq 0.1 --unsigned > unsigned.txn

The unsigned transaction is stored in a file named ‘unsigned.txn’. Note that the –unsigned option is not needed if you use a watching-only wallet.

You may view it using:

cat unsigned.txn | electrum deserialize -

Sign the transaction¶

The serialization format of Dash Electrum contains the master public key needed and key derivation used by the offline wallet to sign the transaction. Thus we only need to pass the serialized transaction to the offline wallet:

cat unsigned.txn | electrum signtransaction - > signed.txn

The command will ask for your password, and save the signed transaction in ‘signed.txn’.

Broadcast the transaction¶

Send your transaction to the Dash network, using broadcast:

cat signed.txn | electrum broadcast -

If successful, the command will return the ID of the transaction.

How to accept Dash on a website using Dash Electrum¶

This tutorial will show you how to accept dash on a website with SSL signed payment requests. It is updated for Dash Electrum 2.6.

Requirements¶

A webserver serving static HTML
A SSL certificate (signed by a CA)
Electrum version >= 2.6

Create a wallet¶

Create a wallet on your web server:

electrum create

You can also use a watching only wallet (restored from xpub), if you want to keep private keys off the server. Once your wallet is created, start Dash Electrum as a daemon:

electrum daemon start

Add your SSL certificate to your configuration¶

You should have a private key and a public certificate for your domain. Create a file that contains only the private key:

-----BEGIN PRIVATE KEY-----
your private key
-----BEGIN END KEY-----

Set the path to your the private key file with setconfig:

electrum setconfig ssl_privkey /path/to/ssl.key

Create another file that contains your certificate and the list of certificates it depends on, up to the root CA. Your certificate must be at the top of the list, and the root CA at the end:

-----BEGIN CERTIFICATE-----
your cert
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
intermediate cert
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
root cert
-----END CERTIFICATE-----

Set the ssl_chain path with setconfig:

electrum setconfig ssl_chain /path/to/ssl.chain

Configure a requests directory¶

This directory must be served by your webserver (eg Apache):

electrum setconfig requests_dir /var/www/r/

By default, Dash Electrum will display local URLs, starting with ‘file://‘ In order to display public URLs, we need to set another configuration variable, url_rewrite. For example:

electrum setconfig url_rewrite "['file:///var/www/','https://electrum.org/']"

Create a signed payment request¶

electrum addrequest 3.14 -m "this is a test"
{
   "URI": "dash:Xtdw4fezqbSpC341vcr8u9HboiJMFa9gBq?amount=3.14&r=https://electrum.org/r/7c2888541a",
   "address": "Xtdw4fezqbSpC341vcr8u9HboiJMFa9gBq",
   "amount": 314000000,
   "amount (DASH)": "3.14",
   "exp": 3600,
   "id": "7c2888541a",
   "index_url": "https://electrum.org/r/index.html?id=7c2888541a",
   "memo": "this is a test",
   "request_url": "https://electrum.org/r/7c2888541a",
   "status": "Pending",
   "time": 1450175741
}

This command returns a json object with two URLs:

request_url is the URL of the signed BIP70 request.
index_url is the URL of a webpage displaying the request.

Note that request_url and index_url use the domain name we defined in url_rewrite. You can view the current list of requests using the listrequests command.

Open the payment request page in your browser¶

Let us open index_url in a web browser.

Payment request page in a web browser

The page shows the payment request. You can open the dash: URI with a wallet, or scan the QR code. The bottom line displays the time remaining until the request expires.

Wallet awaiting payment

This page can already be used to receive payments. However, it will not detect that a request has been paid; for that we need to configure websockets.

Add web sockets support¶

Get SimpleWebSocketServer from here:

git clone https://github.com/ecdsa/simple-websocket-server.git

Set websocket_server and websocket_port in your config:

electrum setconfig websocket_server <FQDN of your server>
electrum setconfig websocket_port 9999

And restart the daemon:

electrum daemon stop
electrum daemon start

Now, the page is fully interactive: it will update itself when the payment is received. Please notice that higher ports might be blocked on some client’s firewalls, so it is more safe for example to reverse proxy websockets transmission using standard 443 port on an additional subdomain.

JSONRPC interface¶

Commands to the Dash Electrum daemon can be sent using JSONRPC. This is useful if you want to use Dash Electrum in a PHP script.

Note that the daemon uses a random port number by default. In order to use a stable port number, you need to set the rpcport configuration variable (and to restart the daemon):

electrum setconfig rpcport 7777

With this setting, we can perform queries using curl or PHP. Example:

curl --data-binary '{"id":"curltext","method":"getbalance","params":[]}' http://127.0.0.1:7777

Query with named parameters:

curl --data-binary '{"id":"curltext","method":"listaddresses","params":{"funded":true}}' http://127.0.0.1:7777

Create a payment request:

curl --data-binary '{"id":"curltext","method":"addrequest","params":{"amount":"3.14","memo":"test"}}' http://127.0.0.1:7777

Carteira Dash Electrum

Carteira Dash Android¶

O Dash oferece uma carteira autônoma para Android, com desenvolvimento suportado pelo orçamento do Dash. A Carteira Android do Dash suporta recursos avançados do Dash, incluindo gerenciamento de contatos e InstantSend. Você pode digitalizar e exibir QR Code para transferências rápidas, fazer backup e restaurar sua carteira, manter um livro de endereços usados com freqüência, pagar com NFC, varrer as carteiras de papel e muito mais.

Instalação¶

Google Play¶

A maneira mais fácil de instalar a Carteira Dash para Android é na Google Play Store.

Por APK¶

Alguns telefones Android não têm acesso à Google Play Store porque o software, o provedor de rede ou o país do telefone podem não permitir isso. Você pode instalar o aplicativo manualmente, primeiro habilitando a instalação de fontes externas (se ainda não o fez) e, em seguida, baixando e instalando um arquivo APK. Siga estas instruções:

Certifique-se de que sua versão do Android seja pelo menos 4.0.3 acessando Configurações → Sobre o telefone e verificando o número da versão.
Habilite fontes desconhecidas acessando Configurações → Segurança → Fontes desconhecidas. Leia e aceite o aviso.
Usando seu telefone, baixe a versão mais recente do APK a partir deste link.
Se você não puder usar seu telefone para ficar on-line, faça o download do APK usando o seu PC e copie-o para o seu telefone usando um cabo ou Bluetooth. Você pode precisar de um navegador de arquivos para encontrar o arquivo copiado.

Você também pode instalar um arquivo APK diretamente do seu computador usando o Android Debug Bridge (ADB). Siga estas instruções:

Certifique-se de que sua versão do Android seja pelo menos 4.0.3 acessando Configurações → Sobre o telefone e verificando o número da versão.
Certifique-se de ter uma cópia do ADB no seu PC. Isso está incluído no Android SDK Platform Tools para Mac, Windows ou Linux.
Habilite fontes desconhecidas acessando Configurações → Segurança → Fontes desconhecidas. Leia e aceite o aviso.
Ative a depuração USB acessando Configurações → Opções do desenvolvedor → Depuração USB. Se as Opções do desenvolvedor não estiverem disponíveis, vá para Sobre o telefone, role para baixo e toque no número da compilação sete vezes.
Usando o seu PC, baixe a versão mais recente do APK a partir deste link.
Conecte seu telefone ao PC, abra uma janela de prompt de comando/terminal e digite:
```
adb install <<path to .apk file>>
```

Da fonte¶

O código-fonte da carteira Android do Dash está disponível no GitHub. As instruções a seguir descrevem como compilar um APK a partir do código-fonte em uma instalação atualizada do Ubuntu 18.04 LTS com um único usuário não-root. Observe que a versão 12b do NDK é necessária, em vez de instalar a versão mais recente usando o sdkmanager. Comece instalando dependências e baixando as últimas ferramentas do Android SDKTools:

sudo apt install openjdk-8-jdk-headless unzip make
mkdir android-sdk-linux
cd android-sdk-linux
wget https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip
wget https://dl.google.com/android/repository/android-ndk-r12b-linux-x86_64.zip
unzip sdk-tools-linux-3859397.zip
unzip android-ndk-r12b-linux-x86_64.zip

Em seguida, atualize as Ferramentas do SDK e faça o download dos pacotes e dependências da plataforma do SDK necessários, depois adicione e carregue as variáveis de ambiente apropriadas:

./tools/bin/sdkmanager --update
./tools/bin/sdkmanager "platforms;android-15" "platforms;android-25" "build-tools;25.0.2"
echo 'export ANDROID_HOME=$HOME/android-sdk-linux' >> ~/.bashrc
echo 'export ANDROID_NDK_HOME=$ANDROID_HOME/android-ndk-r12b' >> ~/.bashrc
source ~/.bashrc
cd ~

Agora que o ambiente de construção está pronto, baixe e construa da fonte da Carteira Dash Android:

git clone https://github.com/HashEngineering/dash-wallet.git
cd dash-wallet
./gradlew clean build -x test

Os arquivos APK construídos estão agora disponíveis na pasta ~/dash-wallet/wallet/build/outputs/apk .

Começando¶

Criando uma nova carteira¶

Quando você inicia sua carteira do Dash, ela gera automaticamente uma nova carteira para você. Em seguida, ele solicitará que você insira um PIN para proteger os gastos da carteira. A primeira coisa que você deve fazer depois de definir um PIN é fazer o backup da carteira tocando no botão de menu no canto superior esquerdo e selecionando Segurança > Ver frase de recuperação. Você precisará dessa frase para recuperar os fundos posteriormente se perder ou danificar seu telefone ou precisar transferir a conta para outro dispositivo. Escreva a frase e guarde-a em um lugar seguro - se você perder isso, você também perderá o acesso aos seus fundos para sempre. Se preferir, você também pode fazer o backup de um arquivo de carteira protegido por senha, selecionando Segurança > Fazer back up da carteira.

Visualizando a frase de recuperação para uma nova carteira no Dash Wallet para Android

Restaurando a partir do backup¶

Se você já tiver uma carteira do Dash para Android, poderá restaurá-la nesse momento tocando no botão de menu no canto superior esquerdo e selecionando Segurança > Restaurar a partir da frase de recuperação. Introduza cuidadosamente a sua frase de recuperação e toque em Restaurar. Sua carteira pode reiniciar e levará algum tempo para que transações e saldos passados apareçam.

Restaurando uma carteira existente a partir da frase de recuperação no Dash Wallet para Android

Recebendo¶

Toque no botão Solicitar Dash no canto inferior esquerdo da tela para receber o Dash. A carteira irá gerar e exibir um código QR para o outro dispositivo para escanear, e você pode, opcionalmente, inserir o valor do Dash ou do dólar da transação para facilitar a pessoa que ira pagar. Você pode tocar no botão de menu no canto superior direito e selecionar Copiar endereço para copiá-lo e colá-lo em outro aplicativo para enviá-lo a uma pessoa que o pague remotamente. Você receberá uma notificação quando a transferência ocorrer e poderá visualizar o status de confirmação na tela principal e o saldo no canto superior direito. O Dash Wallet para Android considera uma transação utilizável após a confirmação de 1 bloco (aprox. 2,5 minutos) ou 6 confirmações de bloqueio se você quiser gerar transações InstantSend.

Recebendo Dash e visualizando suas transações e saldo na Carteira Dash para Android

Enviando¶

Toque no botão Enviar Dash no canto inferior direito da tela para enviar o Dash. Você será solicitado a digitar, colar ou digitalizar (tocando no botão redondo) um endereço de Dash, o valor a ser pago e se deseja usar o InstantSend. Observe que essas informações já podem estar incluídas se você estiver digitalizando um código QR. A taxa de rede determinada automaticamente é exibida. Toque em Enviar para concluir a transação.

Envio de Dash e visualização de suas transações e saldo na Carteira Dash para Android

Comprando¶

Desde a versão 6.1.0, foi possível vincular sua carteira Android ao Uphold para comprar o Dash usando os métodos de financiamento disponíveis no Uphold. Para começar, toque no botão de menu, selecione Conta Uphold e, em seguida, Vincular conta confirmada. Digite seu nome de usuário e senha e complete a autenticação de dois fatores (se habilitado para sua conta). Seu saldo restante será exibido. Toque em Comprar Dash para adicionar fundos e convertê-los para Dash usando Uphold. Toque em Transferir de Uphold insira o valor, toque em Transferir e confirme os detalhes da transação para transferir fundos do Uphold para sua carteira do Dash. Para mais informações sobre o uso do Uphold, veja a documentação do Uphold.

Efetuando login para confirmar e comprar Dash

Transferindo Dash do Uphold para sua carteira Dash no Android

Funções Avançadas¶

Address book¶

Your Android wallet allows you to manage frequently used addresses by adding a label to help you identify the owner. You can also label your own addresses in the wallet in order to keep track of regular incoming payments. You can access the address book by tapping the Menu button, then Address book. This will display a screen where you can swipe left and right between your own addresses and the addresses to which you frequently send Dash, such as family members for example. Tap the More options button to Paste from clipboard or to Scan address from a QR code, or tap an existing address to Send Dash or Edit the label.

Accessing the address book and adding an address

You can also add labels directly from the main transaction history screen by tapping the More options button for the transaction (three vertical dots) and selecting either Add label to your address, Edit label of your address, Add sending address or Edit label of sending address.

Adding and editing address labels in transaction view

Exchange rates¶

Dash Wallet for Android allows you to display the equivalent value of your Dash balance and in transactions by selecting a default fiat currency. To select a default currency, tap the Menu button, then Exchange rates. Find your preferred fiat currency, then tap the More options button for that currency and select Set as default. The exchange rate for this currency will appear when sending Dash, and you can also tap in the fiat currency field to enter the value in the fiat currency directly, instead of in Dash.

Selecting a fiat exchange rate and creating a transaction denominated in USD

Sweep paper wallet¶

Sweeping a paper wallet is a method of transferring the value stored on an address you may have received as a paper wallet or from an ATM into your own wallet. You must have access to the private key for an address to use this function. In this process, all Dash stored on the address will be sent to a new address that has been deterministically generated from your wallet seed. The private keys you sweep do not become a part of your wallet.

To sweep a paper wallet, tap the Menu button and select Sweep paper wallet. Tap the Scan button and scan the QR code from your paper wallet. Once the private key has been identified, tap Sweep to create the transaction moving the Dash into your own wallet. Once this transaction is confirmed, the paper is worthless and should be destroyed.

Sweeping a paper wallet with 0.10 DASH into the Android Wallet

Network monitor¶

The Dash Android Wallet is a light wallet and functions in SPV mode, meaning it does not download a full copy of the blockchain. The network monitor allows you to view details about the full nodes to which you are connected. You can also swipe left to view blocks as they are created on the blockchain.

Viewing peers and blocks to monitor network activity

Configurações¶

The Settings menu in Dash Android Wallet

The settings menu contains a range of options to control the behavior of the Dash Android Wallet. To access the settings, tap the Menu button, then Settings. You can then choose between Settings, Diagnostics and About, which displays wallet version, copyright, license and source code information.

Configurações¶

Denomination and precision: Select the number of decimal places to show for DASH denominations, or switch to mDASH or µDASH denominations
Own name: Enter a short name to be included in your QR codes when displaying to other users for scanning. The short name will then appear as a label in their wallet to verify the recipient and simplify address management.
Auto-close send coins dialog: Specify whether or not to close the send dialog once a payment is complete.
Connectivity indicator: Enables display of an indicator in the Android notification area to be able to quickly verify connectivity.
Trusted peer: Enter the IP address or hostname of a single peer to connect to.
Skip regular peer discovery: Enabling this option prevents automatic peer discovery and forces connection to the one specified trusted peer only.
Block explorer: Allows you to select which block explorer you want to use for functions linking to a block explorer.
Data usage: Links to the Android Data usage function to view and/or restrict data usage for the app.
Balance reminder: Enables an Android system notification to remind you of any unspent Dash if you don’t open the app in that time.
Enable InstantSend: Enables functionality to use InstantSend to send and receive Dash.
Enable Lite Mode: Enabling lite mode reduces bandwidth usage.
Show disclaimer: Enables or disables various disclaimers and warning messages in the app.
BIP70 for scan-to-pay: Enables use of the BIP70 payment protocol to add further verification and security features when scanning QR codes.
Look up wallet names: Enables use of DNSSEC to attempt to identify a wallet name when creating transactions.

Diagnostics¶

Report issue: Allows you to gather a range of information related to your wallet in order to send a bug report to developers for troubleshooting.
Show xpub: Displays the extended public key for the seed used to generate addresses in your wallet. Providing your xpub to a third party will allow them to view your entire transaction history, but not make new transactions.
Reset block chain: Resets data stored on your device relating to the blockchain. This data will need to be collected again from full nodes, similar to when setting up a new wallet. This process may take some time.

Carteira Dash Android

Carteira Dash iOS¶

Dash offers a standalone wallet for iOS, with development supported by the Dash budget. The official Dash Wallet supports advanced Dash features such as InstantSend sending and receiving. You can also scan and display QR codes for quick transfers and backup your wallet using a secure recovery phrase.

Instalação¶

App Store¶

The easiest way to install the Dash Wallet for iOS is from the App Store. While older versions of iOS are supported, you will need to be using iOS 10.0 or newer to use the latest version.

Compilando a partir da fonte¶

O código fonte da carteira está disponível aqui. As etapas a seguir descrevem como fazer o download e compilar a carteira a partir da fonte.

instalar Xcode da App Store. O download é de cerca de 5 GB, portanto, essa etapa pode levar algum tempo.
Abra o Xcode, concorde com os termos e condições e feche o aplicativo.

Abra o Terminal e digite os seguintes comandos:

cd ~/Documents
mkdir src
cd src
git clone https://github.com/QuantumExplorer/dashwallet.git

Abra o Xcode novamente e clique em Arquivo -> Abrir
Navegue até ~/Documents/src/dashwallet/DashWallet.xcodeproj` e clique em Open.
Clique em Produto > Executar para criar e executar o aplicativo no Simulator.

Carteira Dash iOS em execução no simulador depois de compilar no Xcode

Você também pode fazer modificações no código e transferir o aplicativo para o seu dispositivo iOS. Para detalhes, veja este post no Reddit.

Começando¶

Criando uma nova carteira¶

Quando você iniciar a sua carteira do Dash pela primeira vez, você será solicitado a escolher entre criar uma nova carteira ou recuperar uma carteira existente. Escolha Nova Carteira para criar uma nova carteira, a menos que você tenha fundos existentes armazenados em outra carteira usando uma frase de recuperação. Sua nova carteira será gerada e uma frase de recuperação aparecerá para que você possa recuperar os fundos posteriormente se perder ou danificar seu telefone ou precisar transferir a conta para outro dispositivo. Escreva a frase e guarde-a em um lugar seguro, se você perder isso, você também perderá o acesso aos seus fundos para sempre.

Criando uma nova carteira e gerando a frase de recuperação no iOS Dash Wallet

Você também pode ser solicitado a especificar um PIN ou vincular o aplicativo ao seu TouchID. Você pode tocar no logotipo do painel na parte superior do aplicativo para ver seu saldo. Você precisará desbloquear sua carteira para isso, bem como visualizar seu histórico de transações ou enviar o Dash.

Recebendo¶

Depois de ter configurado sua carteira, você terá duas telas disponíveis para enviar e receber Dash. Você pode deslizar para a esquerda e direita entre as telas. Para receber o Dash, o aplicativo irá gerar um endereço que aparece na parte inferior da tela. Você pode tocar para copiar e compartilhar ou escanear o código QR diretamente. Quando a transferência estiver concluída, você poderá ver seu saldo, histórico de transações e o status de qualquer transação pendente clicando no botão de menu no canto superior esquerdo.

Recebendo Dash e exibindo seu saldo na Carteira Dash no IOS

Enviando¶

The Send DASH screen gives you two options to enter the payment address: Scan QR Code or Pay Address From Clipboard. You can choose to use InstantSend for instant confirmation, or disable this to send a normal transaction which will require more time for confirmation. Depending on the code you are scanning, the amount of Dash requested may be included, or you can enter it yourself. A confirmation screen will appear to explain the fee structure and request your unlock code (PIN or TouchID). The transaction will then be sent.

Envio de Dash da iOS Dash Wallet

Funções Avançadas¶

URL Scheme¶

iOS allows apps to communicate with one another through URL schemes. The Dash Wallet for iOS implements the dashwallet:// scheme, allowing you to call the wallet to complete a transaction denominated in Dash. This page documents the methods available using the URL scheme.

Payment¶

Payment request URL format:

dashwallet://pay=<address>&amount=<amount>&(req-)IS=<0/1>&sender=<sender>

Notes:

sender is both your callback URL and the name of the app that you show to the user. This is to prevent 3rd party apps from phishing.
req- can be added before IS to force use of InstantSend for the transaction. If the user doesn’t have InstantSend enabled and doesn’t want to enable it, he will not be offered the option to send as a normal transaction.

The user will see something similar to this:

Payment request in iOS

If the user enters the correct passcode, then the transaction is sent and the user is returned to the sender app following the callback URL.

Callback URL format:

<sender>://callback=payack&address=<example:XiUsEXvLjqhuz1Gunbymtw7JUwtkQXQHaa>&txid=<example:09855ac1c57725d8be2c03b53f72d1cb00ecb7b927bc9e7f5aed95cb3a985d76>

Master public key¶

Master public key request format:

dashwallet://request=masterPublicKey&account=0&sender=<sender>

Note: account is optional and corresponds to BIP32/BIP44 account, most of the time this should be 0. If account is not specified, we use account 0. This will send back both the extended public key at 44’/5’/<account>’ and <account>’

Callback:

<sender>://callback=masterPublicKey&masterPublicKeyBIP32=<example:xpub68GSYNiJZ7k1beEHGmkMUjPsawFvhM7adhbXgnaY1zj5iucUgKPJNDh5iCB8KV2A9FFAGKcGZp5JtQ1XNmT7j2ErRnf8eb4Mt4wjLG6uRcN>&masterPublicKeyBIP44=<example:xpub6DTuSViCnkd1jcgoiQLcghtTAAntBX4zWhfwNMSsmcD94JATNaWZ1tC4NEv6bxcD1YA4474S2BzCDsBA97sM52jiJcmFPBiXcH9JzZSLQJm>&account=0&source=dashwallet

Get address for payment¶

dashwallet://request=address&sender=<sender>

Callback:

<sender>://callback=address&address=<example:XjkMY3GiK5aHwbpg9Uaw7QCPk3QE63Nh5i>&source=dashwallet

Carteira Dash iOS

Carteira de Papel Dash¶

O Gerador de Carteiras de Papel permite que você gere, criptografe e proteja as chaves para um único endereço do Dash em um computador, sem precisar se conectar à Internet. Perfeito para armazenamento seguro a longo prazo.

Introdução¶

A paper wallet is a method of storing a private key to access funds stored on a single address. It can be generated on a computer that has never been connected to the internet, and printed out for air-gapped offline storage. As such, they are suitable for storing large amounts of Dash, but care must be taken not to lose the private key, since there is no way of recovering funds if it is ever lost. To use the key, it must be imported or «swept» into an online wallet and should not be used again. Paper wallets are extremely secure but somewhat inconvenient for everyday use compared to hardware wallets, which also offer a high degree of security.

Paper wallets use random user and machine input to create a set of keys/addresses which you then print. You can never regenerate a paper wallet once you turn off the machine. What you print is all you get. For this reason, paper wallets are somewhat vulnerable and require special care because they can get damaged, lost, destroyed or stolen. Even if you encrypt them with BIP38 (which you should), a sufficiently motivated adversary (e.g. robbery/home invasion) could bypass this encryption using the proverbial «$5 wrench attack».

https://imgs.xkcd.com/comics/security.png

The $5 wrench attack. Credit: xkcd.com

Nevertheless, together with appropriate planning, paper wallets are a highly convenient and user-friendly way to store Dash long term.

Security¶

While you can create a paper wallet using a machine that is connected to the internet, wallets that will be used to store significant funds should be generated using an offline computer running a single-use operating system to ensure that all generated data will be permanently wiped from memory once the process is complete.

A simple method of doing this is to burn a live Linux CD. Ubuntu Desktop is recommended because it will have the most drivers and is simple to use, while Tails and Kali Linux are popular choices for extremely strong security. Booting from an actual CD is most secure since it is mounted read-only, but a USB stick is generally fine as well. Both laptops and desktops can be used if you can ensure that all networking hardware is disabled when you get to the stage of actually generating your keys.

Boot from the CD and download/install your tools (or download them ahead of time to a USB drive). Disconnect from the internet, generate your keys/addresses/printouts, and power off the machine. You are now the only person with access to these addresses.

Death plan¶

Whichever type of cold storage you choose, make a plan to pass on the necessary data to regenerate the keys to your loved ones in the event of an accident - it will happen to us all eventually. Write down your paper wallet BIP38 decryption password or brain wallet passphrase. Then write down instructions on how to use it, and keep them separate with a clear procedure on how they can be accessed when necessary.

Tools¶

A Dash paper wallet can be generated in several ways.

Using the generator at https://paper.dash.org
Using the generator at https://walletgenerator.net/?currency=Dash
Offline using the Dash Paper Wallet source code from GitHub at https://github.com/dashpay/paper.dash.org/releases/latest
Offline using the same code which powers both sites, by viewing the GitHub project or downloading directly

Since the source code for all three options is largely similar, this guide will use https://paper.dash.org as an example. The websites listed here run entirely in your web browser without sending any of the data generated to an external server, but the most secure option is to download the wallet generator and run it on a computer with a freshly installed operating system that is not connected to the internet.

This guide is based on the guide available from https://walletgenerator.net. Please donate if you find this project useful!

Address generation¶

Go to https://paper.dash.org in your web browser (or open index.html if you downloaded the wallet generator). Select your language and choose Dash as the currency if necessary. The following screen will appear:

The Dash Paper Wallet Generator at paper.dash.org

Some random data is required to ensure the generated address and key are unique. Move our mouse around and/or type random characters into the text box until the process reaches 100% and the following screen appears:

Generating randomness for the Dash Paper Wallet Generator

A Dash address and private key generated using Dash Paper Wallet Generator

Once your public address and private key (shown in Wallet Import Format or WIF) are visible on the Single Wallet tab, you should immediately click Print to print the data and store it securely. If you leave the page without somehow recording the dash address and private key, all data will be irretrievably lost, together with any funds you have sent to the address.

Encryption¶

The information shown on the Single Wallet tab does not have a passphrase and is not encrypted. You can print this paper wallet as it is and use it, but it is not protected from being stolen if someone finds it. You should keep it safe the same way you would jewels or cash.

If you decide that you need the additional security of a password for this address, click Paper Wallet. A different address/key pair will appear. To create an encrypted wallet, select BIP38 Encrypt? and enter a passphrase. Tick the box Hide Art? and change to 1 the field Addresses to Generate and then click on Generate. A new wallet will be generated where the private key (WIF) is encrypted using the password you specified, resulting in a BIP38 key. You now need both this BIP38 key and the password to control funds on the address, so be sure to click Print and store both safely. If you are unsure about how to use BIP38 encryption, it is highly recommended to test the workflow with a low amount of Dash before storing significant funds on an encrypted paper wallet. If you forget the password or lose the encrypted key, you will permanently lose access to your funds.

A Dash WIF address can be easily identified because it always begins with «7». A BIP38 format encrypted key can be identified because it always begins with «6P». See here to learn more about BIP38.

Encrypted paper wallet generated using Dash Paper Wallet Generator

Sending to a paper wallet and viewing the balance¶

You can send Dash to a paper wallet address in the same way as to any other Dash address. See the documentation for your wallet if you do not know how to do this. For this example, 0.05 Dash (minus transaction fee) has been sent to the paper wallet address. Anyone with knowledge of the public address is able to see the balance of the wallet using a block explorer, but only someone with knowledge of the private key can access the funds. You can make as many deposits and send as many coins to the same address as you’d like. Just make sure you test your wallet with small amounts first to learn how it works.

Viewing the balance of the paper wallet using the Dash Block Explorer at explorer.dash.org

Spending from a paper wallet¶

In order to access the funds stored on the paper wallet address, you will need the following:

The public address
The private key in WIF

If you encrypted the wallet, you will additionally need the following to convert the BIP38 key into the WIF key:

The encrypted private key in BIP38 format
The passphrase you used to encrypt the key

Optional: Decrypt BIP38 key to WIF¶

If you encrypted your paper wallet, you will first need to decrypt the BIP38 key. You can skip this step if your private key was not encrypted.

Go to the Wallet Details tab, enter the encrypted key in the Enter Private Key field and click View Details. You will be asked to Enter BIP38 Passphrase in the field. Enter the passphrase and click Decrypt BIP38. A range of information derived from the key will appear, the information required to access the funds on the public address appears under Private Key WIF. Copy the Private Key WIF and use it in the next step.

Dash Paper Wallet Generator displaying information derived from an encrypted private key

Importing the private key to your live wallet¶

When you are ready to spend the balance on the paper wallet, you will need to import the private key used to control the address printed on the wallet into another Dash wallet that is connected to the internet. We will use the Dash Core Wallet in this example, although Dash Electrum and mobile wallets are also supported. Open Dash Core Wallet, click Settings and Unlock Wallet. Enter your wallet passphrase. Then click Tools and select Debug Console. The console appears. Enter the following command:

importprivkey <your private key in WIF>

Dash Core Wallet importing a private key

This process requires rescanning the entire downloaded blockchain for transactions involving this address, and will therefore take some time. Be patient. Once the process is complete, any transactions involving the imported address will appear in your list of transactions. If you use Coin Control, you can also enable or disable the address for spending there.

Paper wallet address successfully imported into Dash Core Wallet from WIF private key

Since the paper wallet public address still holds the funds, it can also be imported again into a second wallet if it is not destroyed. It is recommended to transfer the balance from the paper wallet to an internal wallet address or another address where you have exclusive control over the private key. This will prevent a third party from obtaining unauthorised access to the same address from the paper wallet before you do. You can then spend your balance as usual.

Once the paper wallet is empty and you are sure it will not be receiving any further deposits, you can destroy the paper.

Carteira de Papel Dash

Carteiras Hardware¶

Uma carteira hardware é um tipo de dispositivo que armazena chaves privadas em um dispositivo de hardware seguro, em vez de em um arquivo de banco de dados como o wallet.dat usado com carteiras de software comuns. Isso oferece grandes vantagens de segurança em relação às carteiras de software, além de benefícios práticos em relação às carteiras de papel. Até o momento, não há evidências verificáveis de carteiras hardware sendo comprometidas por vírus, e elas também são imunes a ataques de keylogger que poderiam ser usados para roubar senhas para desbloquear as chaves privadas usadas com carteiras de software.

As carteiras de hardware funcionam armazenando suas chaves privadas em uma área protegida de um microcontrolador. É impossível para a chave privada deixar o dispositivo em texto simples - somente a saída assinada do hash criptográfico é transmitida ao dispositivo interagindo com o blockchain, como seu computador ou smartphone. A maioria das carteiras de hardware possui uma tela que permite que você confirme independentemente se o endereço para o qual você está enviando está correto.

Esta seção lista as carteiras hardware comerciais mais comuns que suportam o Dash, embora alguns outros projetos de entusiastas também possam estar disponíveis.

Introdução¶

As carteiras de hardware oferecem a segurança de armazenar suas chaves em um dispositivo seguro e, ao mesmo tempo, permitem que você faça transações simples por meio de uma interface Web. Três grandes fabricantes de carteiras de hardware atualmente existem, com o Dash sendo suportado em todos eles.

Trezor¶

Desenvolvido pela startup Czech SatoshiLabs <https://satoshilabs.com> _, o dispositivo custa $99 é essencialmente um dongle USB projetado para adicionar uma camada de autenticação extra a todas as transações de bitcoins. Trezor apoia o Dash desde janeiro de 2017 com o lançamento da versão de firmware 1.4.2.

Em virtude de seu design, o Trezor pode ser usado para assinar transações em computadores «inseguros» e é imune a keyloggers e muitos outros vetores de ataque, portanto, mesmo que seu PC host seja comprometido, o invasor não terá como obter sua chave privada. É também aí que o dispositivo recebe o seu nome, pois «trezor» se traduz em «cofre» na maioria das línguas eslavo, incluindo o tcheco. Uma espécie de “cofre” para a sua chave privada de bitcoin , a Trezor afirma usar uma série de truques inteligentes para manter a segurança mesmo em máquinas comprometidas e inseguras.

Site: https://trezor.io
Review: https://www.dashforcenews.com/trezor-hardware-wallet-review
Shop: https://shop.trezor.io
Carteira: https://wallet.trezor.io

Também é possível operar um masternode do Dash usando o seu Trezor. Veja aqui para detalhes.

Começando¶

Depois de ter comprado o seu Trezor em https://shop.trezor.io ou em um revendedor autorizado, você precisará de uma carteira para usá-lo. O Trezor suporta as seguintes carteiras do Dash:

Esta documentação descreve como começar a usar a carteira da Web oficial da Trezor em https://wallet.trezor.io. Confirme sempre se o URL está correto e se a criptografia SSL está ativada ao trabalhar com a Carteira Trezor. Siga estas etapas ao configurar seu Trezor pela primeira vez:

Inspecione a embalagem para adulteração. Deve haver dois selos e as abas devem ser coladas. Deve ser impossível remover o dispositivo sem destruir totalmente a embalagem.
Vá para https://trezor.io/start/ e assista ao vídeo para apresentar os conceitos de um layout de PIN de deslocamento e de uma seed de recuperação.
Vá para https://wallet.trezor.io/ para iniciar o processo de configuração.
Se ainda não estiver instalado, instale o aplicativo Trezor Bridge em https://wallet.trezor.io/#/bridge
Conecte o Trezor ao seu computador quando solicitado.
Se esta é a primeira vez que você conecta seu Trezor, você será solicitado a instalar o firmware. Clique no botão Instalar, aguarde o download e confirme no dispositivo.
Quando concluído, o dispositivo exibirá uma impressão digital. Verifique se isso corresponde à impressão digital mostrada na tela. Observe que isso é hexadecimal e, portanto, não faz distinção entre maiúsculas e minúsculas.
Após a conclusão da verificação, desconecte e reconecte seu dispositivo. Digite um rótulo de dispositivo na tela que aparece.
Digite e confirme um PIN clicando nos quadrados de acordo com o mapeamento mostrado no dispositivo.
Seu dispositivo Trezor agora exibirá uma sequência de 24 palavras na tela. Esta é a sua seed de recuperação. Escreva as palavras na ordem em que aparecem no cartão de recuperação. Nunca armazene sua semente de recuperação em qualquer formato digital, incluindo fotos ou texto.
Verifique a seed o que você escreveu e guarde-a em um lugar seguro.
Você será solicitado a digitar seu PIN novamente.
A Carteira Trezor aparecerá com uma mensagem de que seu dispositivo está pronto para uso. O nome do seu dispositivo aparecerá no dispositivo.
Mude para a carteira do Dash usando o menu no canto superior esquerdo. Agora você pode usar o seu Trezor para enviar e receber o Dash.

Carteira Trezor Web para Dash pronto para o primeiro uso

Recebendo Dash¶

Vamos agora criar um endereço de recebimento do Dash e tentar receber 1.0 DASH.

Na carteira do Trezor Dash, clique em Conta#1 e, em seguida, clique em Receber.
Um endereço de dash será exibido. Clique em Mostrar endereço completo para verificar o endereço no dispositivo Trezor.

Envie 1 DASH para este endereço usando uma exchange ou outra carteira.
Quando a transação for confirmada, ela aparecerá na guia Transações da sua Carteira Trezor.

Carteira Trezor Web depois de receber o Dash

Enviando Dash¶

Vamos agora enviar o dash (menos custos de transação) para um endereço externo.

Na carteira do Trezor Dash, clique em Conta#1 e, em seguida, clique em Enviar.
Digite o endereço e a quantia nos campos.

Digite seu PIN
Confirme o endereço no dispositivo e confirme a ação.

A transação será transmitida para a rede e o destinatário recebe os fundos.

Carteira Trezor Web após o envio do Dash

Funções avançadas¶

Alterando o PIN/Senha¶

Seu PIN é sua principal forma de segurança ao usar sua carteira de hardware. É considerado seguro porque o layout do teclado PIN muda cada vez que você o usa. Se você suspeitar que seu PIN foi comprometido, altere-o usando as instruções a seguir. Para maior segurança, ou se você acredita que pode estar sujeito à pressão em algum momento no futuro, você pode adicionar uma senha para revelar outras carteiras que só aparecem quando você insere sua frase-senha. Como a frase secreta atua como um sal criptográfico, não existe uma senha «correta» - uma carteira diferente será exibida para cada senha digitada. Esteja absolutamente certo de que você entende as senhas antes de usá-las. Para mais informações, veja aqui.

Alterando seu PIN¶

Você pode alterar o seu PIN Trezor em ambos Carteira Trezor e DMT.

Trezor: Vá para https://wallet.trezor.io e clique no ícone de engrenagem ao lado do seu nome de usuário. Em seguida, clique em Alterar PIN. Você precisará confirmar que deseja alterar seu PIN no dispositivo de hardware e, em seguida, insira o PIN existente e o novo PIN duas vezes.

DMT: Abra o DMT e clique em Ferramentas > Configuração do PIN/Senha do Hardware da Carteira. A seguinte janela irá aparecer. Clique em Alterar. Você precisará confirmar que deseja alterar seu PIN no dispositivo de hardware e, em seguida, insira o PIN existente e o novo PIN duas vezes.

Adicionando uma frase secreta¶

Você pode adicionar uma senha ao seu Trezor tanto da carteira Trezor quanto do DMT. Antes de adicionar uma frase secreta, você deve estar totalmente ciente de como ela funciona com «25ª palavra» para sua seed e os riscos de esquecer sua frase secreta. Note que você não precisa digitar uma frase secreta - o espaço em branco é perfeitamente aceitável e revelará sua carteira normal.

Trezor: Clique em ** Avançado ** para confirmar que você entende os riscos e clique em Ativar criptografia de frase secreta. Isso permite que insira uma senha toda vez que você usar seu Trezor.

DMT: Abra o DMT e clique em Ferramentas > Configuração do PIN/Senha do Hardware da Carteira. A seguinte janela irá aparecer. Clique em Ativar. Isso permite que insira uma senha toda vez que você usar seu Trezor.

Mudando a tela inicial¶

Seu Trezor permite que você altere a imagem da tela inicial do logotipo Trezor padrão. Uma gama de imagens existentes pode ser selecionada, você pode gerar um você mesmo usando o Editor Trezor Homescreen <https://trezor.github.io/homescreen-editor/>`_, ou você pode criar e carregar sua própria imagem em preto e branco de 128x64px. Para alterar sua imagem homescreen:

Va para https://wallet.trezor.io e abra sua carteira
Clique no pequeno ícone de engrenagem ao lado do nome do seu dispositivo
Clique na aba Homescreen
Selecione a nova tela inicial e clique no botão Definir como tela inicial na parte superior
Confirm the change on the Trezor device

Algumas imagens de amostra estão disponíveis para o Dash:

Sugestões de Armazenamento¶

Embora a perda de um Trezor não seja uma ameaça à segurança (a menos que alguém saiba o seu PIN/Senha), é um dispositivo de custo moderado que pode ser danificado por pressão ou água, por exemplo. Por esse motivo, o membro da comunidade do Dash, tungfa, compartilhou fotos de um caso Trezor feito sob medida. Os seguintes materiais são necessários:

Pelican Case 1010 Micro Case
Espuma
Trezor + Cabo
USB Stick (para arquivos wallet.dat + blockchains de todos os portfólios)
Notepad

KeepKey¶

A carteira de hardware KeepKey $129 possui uma tela grande e 100% de código aberto para garantir a segurança de suas chaves privadas. O KeepKey suporta o Dash desde a versão de firmware 4.2.10, lançada em 28 de março de 2017, e adicionou suporte para o InstantSend na versão de firmware 5.7.2, lançada em 5 de setembro de 2018. Siga estas instruções para começar a usar o Dash no dispositivo KeepKey.

Site: https://www.keepkey.com
Review: https://coincentral.com/keepkey-wallet-review
Shop: https://keepkey.myshopify.com/
Produção de video: https://vimeo.com/133811189

Também é possível operar um masternode do Dash usando o KeepKey. Veja aqui para detalhes.

Ledger¶

Fundada em 2014, startup francesa Ledger comercializa soluções de segurança blockchain para empresas e consumidores, incluindo €58 Ledger Nano S e próximo Ledger Blue. Ledger Nano S suporta o Dash desde novembro de 2016 e a versão de firmware 1.2. Siga estas instruções <https://support.ledger.com/hc/en-us/articles/115005308185-Dash-DASH->`_para adicionar suporte ao Dash ao dispositivo.

Site: https://www.ledger.com
Review: https://www.dashforcenews.com/ledger-nano-s-review
Shop: https://www.ledger.com/collections/all-products

Produção de video:

Também é possível operar um masternode do Dash usando o seu Ledger. Veja aqui para detalhes.

Carteira Trezor Web

Carteiras de Terceiros¶

Essas carteiras foram desenvolvidas por desenvolvedores externos para suportar o Dash. Muitas carteiras de terceiros suportam múltiplas criptomoedas ao mesmo tempo, ou integram trocas instantâneas de criptomoedas.

Introdução¶

The Dash protocol and many Dash products such as Dash Core and the mobile wallets are entirely open source, which makes it easy for third parties to integrate Dash with their existing cryptocurrency wallet solutions. This section describes some of the third party wallets available and the functions they offer. Please note that Dash does not provide support for any of these wallets, and any listing here should not be considered an endorsement or recommendation. Contact the software vendor for support.

Abra¶

https://www.abra.com

Abra is a multi-cryptocurrency wallet supporting Dash amongst other currencies. It is designed for investment and can be funded from your bank account, credit/debit card, cash (in the Philippines), Bitcoin, Bitcoin Cash, or Litecoin. Dash deposits and withdrawals are currently not supported.

Instalação¶

Documentation¶

VegaWallet maintains a FAQ and a Telegram group for support. The team also responds to support queries by email at support@vegawallet.com

VegaWallet wallet running on iOS

Carteira Edge

Carteiras Web¶

Carteiras da Web são serviços que mantêm um saldo do Dash para você, mantendo o controle das chaves privadas em seu nome. Qualquer Dash armazenado em exchanges se enquadra nesta categoria, mas também há alguns serviços capazes de armazenar Dash para você através de simples sistemas de login do Google/Facebook. Seja extremamente cuidadoso com o armazenamento na Web, pois o seu Dash é tão seguro quanto a reputação da empresa que o armazena para você. Uma exceção específica é o MyDashWallet.org, que fornece uma interface da Web segura ao blockchain do Dash, deixando você com controle total de suas chaves privadas.

MyDashWallet¶

MyDashWallet é uma interface web para o blockchain, inspirada por MyEtherWallet e criado por DeltaEngine.net. É explicitamente uma carteira on-line, o que significa que você mantém o controle sobre suas chaves privadas em todos os momentos. Ao contrário de muitas outras carteiras, o MyDashWallet também suporta recursos avançados do Dash, como InstantSend e PrivateSend. O projeto é sem fins lucrativos, de código aberto e livre para uso. Você pode carregar uma carteira e fazer transações em diversos formatos de carteira:

Carteira Keystore (baseada em arquivo)
Carteira Ledger Hardware
Carteira Trezor Hardware
Chave privada
BIP39/44 HD frase de recuperação (em breve)
BIP32 HD frase de recuperação (em breve)

Please note that web wallets may not be as secure as alternatives such as hardware wallets. Be aware of the risk of storing large amounts of Dash in keyfile wallets, since they are an easier target to attack than mobile or hardware wallets.

O MyDashWallet oferece documentação completa e detalhada para todas as funções.

Magnum Wallet¶

Magnum Wallet is a web wallet with support for 20+ cryptocurrencies, including Dash. The wallet stores encrypted private keys in a simple downloadable text file, which can only be decrypted with the users password. Hardware wallets are also supported, and in-wallet staking and exchange functionality is available. Magnum Wallet presents a clean and simple interface, allowing users to transact quickly and easily in Dash.

Please note that web wallets may not be as secure as alternatives such as hardware wallets. Be aware of the risk of storing large amounts of Dash in keyfile wallets, since they are an easier target to attack than mobile or hardware wallets.

Support for Magnum Wallet is available at support@magnumwallet.co.

Magnum Dash Wallet

Minha Carteira Dash

Carteiras de Texto¶

Carteiras de texto (ou carteiras SMS) permitem que usuários sem smartphones ou acesso à Internet realizem transações no Dash usando mensagens de texto em telefones com recursos simples. Códigos de acesso inovadores, geralmente em colaboração com provedores de serviços móveis nacionais, tornam relativamente simples criar transações para enviar e receber o Dash.

Introdução¶

As carteiras de mensagem de texto (SMS) permitem que você faça transações facilmente no Dash usando um telefone simples. Uma conexão com a internet não é necessária. Como as carteiras de texto exigem acesso a mensagens de texto, elas geralmente só suportam regiões específicas. Veja abaixo para detalhes.

CoinText¶

https://dash.cointext.io

O CoinText é um projeto para fins específicos que torna a criptomoeda fácil de usar para expandir a liberdade econômica em todo o mundo. Permite transacionar no Dash sem internet, apps, contas ou endereços complicados. O CoinText atualmente suporta transações do Dash nos EUA e no Canadá e tem como objetivo expandir para mais de 50 países nos próximos meses. É possível denominar o valor a ser enviado tanto no Dash quanto na moeda local e enviar o Dash para os números de telefone e os endereços do Dash.

Instruções¶

Basta digitar START para o número de telefone do CoinText da sua região. Para mais informações sobre a lista de regiões suportadas e instruções mais detalhadas sobre como enviar e receber pagamentos, consulte os links abaixo:

DashText¶

https://dashtext.io

DashText is a service available in Venezuela, Colombia and Spain to allow users to transact in Dash using text messages. The only fees are the cost of a standard SMS, incurred by the network operator. Users can send Dash to innovative shortcodes to securely confirm transactions.

Instruções¶

Basta digitar CREATE no número de telefone do DashText para começar. Outras instruções e links aparecerão aqui quando o projeto estiver pronto para o mercado de massa.

Dash CoinText

Guias de Carteiras¶

A documentação nesta seção descreve tarefas comuns e perguntas relacionadas a todas as carteiras.

Recuperar Carteira¶

Os usuários de longa data na criptomoeda às vezes encontram arquivos antigos da carteira em unidades USB ou armazenamento na nuvem de que se esqueceram. Outros podem ter um backup, mas não conseguem lembrar o software usado para criá-lo ou esqueceram a senha. Outros usuários podem ter uma versão antiga do Dash Core que não funciona mais porque a rede foi atualizada. Esta documentação destina-se a ajudar esses usuários a restaurar o acesso a seus fundos.

Determinando o formato do backup¶

O primeiro passo é determinar o formato do seu backup. Na maioria dos casos, isso será um arquivo, provavelmente chamado wallet.dat, ou uma frase de palavras. Em alguns casos, você pode ter armazenado a chave privada para um endereço Dash diretamente. A lista a seguir mostra as possibilidades e métodos para restaurar sua carteira em ordem de probabilidade.

Backup é armazenado em uma versão mais antiga do Dash Core que não funciona mais
- Siga as instruções para restaurar arquivos da carteira usando Dash Core
Backup é um arquivo
- Se o nome do arquivo for semelhante ao wallet.dat, tente restaurar usando Dash Core
- Se o nome do arquivo for semelhante a dash-wallet-backup ou incluir a palavra “mobile”, tente restaurar usando Carteira Dash para Android
Backup em uma frase de palavras
- Se tiver 12 palavras, tente restaurar usando Carteira Dash Electrum ou Carteira Dash para Android ou iOS, dependendo do que você usou para criar o backup
- Se tiver 13 palavras, tente restaurar usando Carteira Dash Electrum
- Se tiver 12, 18 ou 24 ou 25 palavras, tente restaurar com carteira de hardware usada para criar a frase de recuperação
Backup em uma longa seqüência de caracteres aleatórios ou um código QR
- Se tiver 34 caracteres e começar com X, esse é um endereço público e não pode ser usado para restaurar o acesso a fundos perdidos. Você precisa da chave privada.
Se tiver 51 caracteres e começar com 7, essa é uma chave privada em WIF, importar usando o Dash Core
Se tiver 58 caracteres e começar com 6P, esta é uma chave privada criptografada BIP38, descriptografar usando carteira de papel, em seguida, importar usando o Dash Core

Depois de determinar seu formato de backup, siga os links para visualizar o guia de restauração para esse formato.

Backups de arquivos¶

Dash Core¶

One of the most common wallet backup formats is a wallet.dat file from Dash Core wallet. Before you begin, make absolutely sure that you have a copy of this file stored somewhere safe in case the restore process accidentally corrupts your wallet file! In most cases, wallet.dat backups will also be protected by a password, which you will need to know to regain access to your Dash funds. If you already have Dash Core installed, first ensure it has been updated to the latest version by clicking Help > About Dash Core. Compare this with the latest available version of Dash Core on the website as follows:

Comparando a versão instalada do Dash Core com a versão mais recente disponível no site

Atualize o Dash Core para a versão mais recente de acordo com a instruções de instalação. Se você tiver apenas um arquivo de carteira e nenhuma instalação existente do Dash Core, basta instalar o Dash Core de acordo com as instruções de instalação e iniciá-lo uma vez para criar a pasta DashCore. Em seguida, feche o Dash Core e copie o arquivo wallet.dat que você deseja restaurar para a pasta DashCore no local especificado abaixo, substituindo ou renomeando o arquivo existente.

Plataforma	Caminho para a pasta de dados	Como navegar
Linux	~/	Vá para a sua pasta pessoal e pressione Ctrl + H para mostrar os arquivos ocultos, depois abra o `.dashcore`
macOS	~/Library/Application Support/	Press Shift + Command + G, type `~/Library/Application Support`, then open `DashCore`
Windows	%APPDATA%	Precionar Windows Key + R e digite `%APPDATA%`, então abra `DashCore`

Se a sua versão existente do Dash Core é mais antiga que v0.12.1.x, você pode precisar renomear sua pasta de dados de Dash para DashCore.

Para reparar uma instalação quebrada, navegue até a pasta DashCore e exclua todos os arquivos .log e .dat exceto wallet.dat. Os seguintes arquivos podem ser excluídos com segurança:

banlist.dat
budget.dat
db.log
debug.log
fee_estimates.dat
governance.dat
mncache.dat
mnpayments.dat
netfulfilled.dat
peers.dat

Deixar arquivos e pastas .conf (tal como``backups``, blocks, chainstate, etc.) intacto, pois eles ajudarão você a começar mais rapidamente, fornecendo uma cópia do blockchain e de suas configurações.

Agora abra o Dash Core e aguarde a conclusão da sincronização blockchain. Sua carteira será restaurada/atualizada e todos os saldos deverão ser exibidos. Certifique-se de ter a senha correta ao tentar desbloquear sua carteira em Definições> Desbloquear carteira para ter certeza de que você pode realmente criar transações usando seus saldos. Se você tiver algum problema com seu saldo não aparecer, tente forçar uma nova verificação do blockchain indo em Ferramentas > Reparar Carteira e selecionando Reprocessar ficheiros da cadeia de blocos. Reconstruir indexação também pode ajudar. O Core irá reiniciar e realizar uma varredura completa do blockchain.

Forçando o Dash Core a rescanear o blockchain

Neste estágio, a recuperação está completa e você deve fazer outro backup usando Arquivo > Backup Wallet ou seguindo as instruções aqui. Se você tiver mais problemas, tente perguntar no forum, Reddit ou o canal #dash-support-desk em Dash Nation Discord.

Dash Android¶

Semelhante à carteira do Dash Core, o Dash Wallet para Android pode fazer o backup de sua carteira em um arquivo. Para restaurar esta carteira em outro dispositivo, simplesmente copie o arquivo de backup para a pasta /Downloads do seu dispositivo usando um computador conectado por USB ou um aplicativo gerenciador de arquivos no dispositivo. Certifique-se de que sua carteira do Dash esteja totalmente atualizada na Play Store e abra o Dash. Se você tiver um saldo existente, faça outro backup ou transfira-o para um endereço externo, porque a restauração de uma carteira substituirá sua carteira existente!

Clique no botão de menu no canto superior esquerdo, selecione Segurança > Restaurar carteira e selecione o arquivo apropriado na lista. Digite sua senha e clique em Restaurar. Isso pode levar algum tempo e seu saldo será exibido quando concluído.

Restaurando um arquivo de backup usando o Carteira Dash para Android

Frases de Recuperação¶

Se você tiver uma frase de 12 palavras e tiver certeza de que seu backup foi feito em um dispositivo móvel iOS ou Android, siga estas instruções.

Frase de 12 palavras no Android¶

Certifique-se de que sua carteira do Dash esteja totalmente atualizada na Play Store e abra o Dash. Se você tiver um saldo existente, faça outro backup ou transfira-o para um endereço externo, porque a restauração de uma carteira substituirá sua carteira existente! Clique no botão de menu no canto superior esquerdo, selecione Segurança > Restaurar a partir da frase de recuperação e digite sua frase de 12 palavras.

Restaurando a partir de uma frase de recuperação de 12 palavras usando a carteira do Dash para Android

Frase de 12 palavras no iOS¶

Certifique-se de que sua carteira do Dash esteja totalmente atualizada na App Store e abra o Dash. Se esta for a primeira vez que você está abrindo o aplicativo, você pode inserir sua frase de recuperação diretamente, selecionando Recuperar carteira na tela inicial. Se você tiver um saldo existente, faça outro backup ou transfira-o para um endereço externo, porque a restauração de uma carteira substituirá sua carteira existente!

Clique no botão de menu no canto superior esquerdo, selecione Configurações > Iniciar/recuperar outra carteira. Digite sua frase atual de recuperação da carteira, o aplicativo será redefinido e você verá a opção Recuperar carteira novamente.

Restaurando a partir de uma frase de recuperação de 12 palavras usando a carteira do Dash para iOS

Frase de 12/13 palavras no Dash Electrum¶

Certifique-se de estar usando a versão mais recente do Dash Electrum de acordo com as instruções de instalação aqui. O Dash Electrum suporta múltiplas carteiras simultâneas, para que você possa restaurar com segurança um novo arquivo de carteira, sem perder sua carteira antiga. Clique em Arquivo > Novo/Restaurar e insira um nome de arquivo para armazenar sua nova carteira. Em seguida, selecione Eu já tenho uma seed e insira sua frase de recuperação de 12/13 palavras. Digite uma nova senha para sua carteira e clique em Próximo para recuperar seus endereços da frase de recuperação.

Restaurando a partir de uma frase de recuperação de 12 palavras usando o Dash Electrum

Frases de recuperação de carteiras hardware¶

Se a sua frase de recuperação de 12, 18 ou 24 palavras foi gerada por uma carteira de hardware, siga estas instruções:

Restaurando uma carteira do iOS no Dash Electrum¶

Você pode usar sua frase de recuperação Dash iOS com o Dash Electrum para recuperar fundos se perder o acesso ao seu dispositivo iOS por qualquer motivo. No entanto, como os caminhos de derivação de carteira não são idênticos, o processo só funciona em uma direção, o que significa que não é possível restaurar uma carteira Dash Electrum usando a carteira Dash iOS. Além disso, como o processo de importação usa uma chave xprv em vez da frase de recuperação diretamente, não será possível exibir a frase de recuperação no Dash Electrum. Recomenda-se, portanto, mover os fundos (para uma carteira padrão da Dash Electrum ou outra carteira) assim que a recuperação for bem-sucedida para garantir que os procedimentos de backup padrão funcionem conforme o esperado.

A recuperação ocorre em duas etapas. Primeiro, converteremos a frase de recuperação do Dash iOS em uma chave xprv. Na segunda etapa, importaremos a chave xprv para o Dash Electrum.

Recuperando a chave xprv do Dash iOS correta¶

Vá para a página BIP39 Mnemonic Code Converter <https://iancoleman.io/bip39/>`_page. Esta é uma ferramenta útil para manipular/exibir dados de semente BIP32/39. Se você não estiver confortável em realizar este procedimento on-line, uma versão off-line estará disponível fazendo o download do arquivo descrito em `estas instruções. Quando a ferramenta estiver carregada no navegador, conclua as etapas a seguir:

Digite sua frase com 12 palavras no campo BIP39 Mnemonic.
Deixe Passaprase BIP39 em branco.
Coloque a moeda no Dash.
Em Derivation Path, clique na guia BIP44.
Copie o valor mostrado em Chave privada estendida.

Importando a chave xprv para o Dash Electrum¶

Abra o Dash Electrum e clique em Arquivo -> Novo/Restaurar.
Digite um nome para sua carteira.
Selecione Carteira padrão.
Selecione Use chaves públicas ou privadas.
Cole o valor da Chave privada estendida da conta.
Opcionalmente, insira uma senha.

O Dash Electrum deve agora detectar o seu saldo do Dash iOS e você deve ter acesso completo aos seus fundos. A frase seed não estará disponível no Dash Electrum, então você só precisará seguir os passos acima novamente se quiser restaurar essa carteira a partir da frase de recuperação novamente. Recomenda-se enviar seus fundos para uma nova carteira Dash Electrum e seguir procedimentos de backup padrão.

Versões mais antigas da carteira do Dash iOS usavam o endereço BIP32 sob o caminho de derivação m/0'. A carteira deve migrar esses fundos para endereços BIP44 durante o uso normal, mas algum saldo residual pode estar sob esse caminho de derivação, então restaurar a Chave Privada Estendida BIP32 pode ser útil em algumas situações. Por favor, veja este tópico do fórum para uma discussão mais aprofundada sobre este assunto. processo.

Chaves Privadas¶

A maioria das carteiras oferece uma função para importar um endereço de uma chave privada, consulte a documentação da sua carteira para obter instruções específicas. Embora as chaves privadas possam ser armazenadas de várias maneiras, neste exemplo, trabalharemos no processo de restauração de uma chave privada a partir de uma carteira de papel usando o Dash Core. Se você tiver apenas um código QR e não a chave, use um aplicativo de leitura de código de barras (Android ou iOS) para ler o código primeiro.

Primeiro, inicie o Dash Core e desbloqueie sua carteira selecionando Definições> Desbloquear carteira. Digite sua senha e abra o console de depuração selecionando Ferramentas > Consola de Depuração. No console, digite o seguinte, substituindo a chave privada de exemplo pela sua chave:

importprivkey 7rPQWnMrh3oWLtZrzt1zLRSCVyuBbwnt7fRBXPp2EwcPhtzXSzp

Importando uma chave privada usando o console de depuração na carteira do Dash Core

O Dash Core irá fazer uma nova varredura do blockchain para transações envolvendo o endereço público dessa chave e inserir as transações e o saldo em sua carteira.

A chave privada deve estar no formato de importação de carteira (WIF). Se sua chave for criptografada usando BIP38 (a chave começa com 6P em vez de 7), primeiro você deve descriptografá-la para exibir a chave no WIF. Para fazer isso, acesse https://paper.dash.org/ e clique em Detalhes da Carteira. Digite a chave privada criptografada no campo e clique em Visualizar detalhes. Você será solicitado a fornecer a senha e suas chaves serão descriptografadas. Encontre a chave chamada Private Key WIF e importe-a para sua carteira.

Descriptografar uma chave criptografada BIP38 para WIF para importação na carteira do Dash Core

Senhas Esquecidas¶

Na maioria dos casos, se você selecionou uma senha forte e a esqueceu ou perdeu, praticamente não há esperança de recuperação. A criptografia usada pelas carteiras do Dash é extremamente forte pelo design, e uma senha bem escolhida deve anular a maioria das tentativas de quebra de força bruta. Se você puder lembrar alguns detalhes da senha, particularmente seu comprimento ou sequências de caracteres que podem ser incluídos, então vale a pena tentar técnicas de quebra de senha de força bruta. Vários serviços existem para fazer isso, ou você mesmo pode tentar. Como o Dash Core é baseado no Bitcoin Core, a maioria das abordagens para aplicar a força bruta para quebrar uma carteira Bitcoin também funcionará para as carteiras do Dash.

Signing and Verifying Messages¶

Dash wallets function by securely storing the private keys used to create transactions using publicly visible addresses on a distributed ledger called a blockchain. In some cases, it may be necessary to verify an address to demonstrate control of the funds that it holds, that you can receive using the address, or even to verify your identity to an exchange that has previously seen a transaction from that address. To avoid phishing attacks, take great care when sending signed messages to parties you do not trust, since ambiguously worded messages could be used to impersonate your identity.

Signing messages requires a private key. Verifying messages requires a public address. In this way, you can write an arbitrary message and generate a signature that could only have been created by a user with control of the private key for this address. Any user with the message, the public address and the signature can easily verify that only you could have created the signature. Messages are not stored on the blockchain. Instead, you must send these three text snippets (message, address and signature) to your intended recipient using another communication channel, such as email. As an example, you can test the following message and signature and verify that it was signed by the given address:

Message: Documentation test signature
Address: XwHihwiQzheVKbT76e7ZhPkujDCQGEZC6P
Signature: IKaEt7MTb4Y57WIde5TLUkm1vbVsjk/L9eG+TE2tdQhMeK9vGgTsqcVOTmXXQ6QA0/WQtxqPURH2qZG27YR2VE0=

Signing a Message¶

The following screenshots show how to sign a message using the Dash Core wallet (File > Sign message), Trezor web wallet (Sign & Verify > Sign message) and DMT (Tools > Sign message with HW for current masternode’s address):

Signing messages in Dash Core, Trezor web wallet and DMT

Verifying a Message¶

The following screenshots show how to verify a message using the Dash Core wallet (File > Sign message) and Trezor web wallet (Sign & Verify > Sign message):

Verifying messages in Dash Core and Trezor web wallet. Notice that the message verified by Dash Core was generated in Trezor, and vice versa

Earning and Spending¶

Dash is designed from the ground up to function as digital cash. This documentation discusses how and where Dash users can manage all of their personal finances using Dash.

Earning¶

A range of services and businesses are available to convert your wage to and from Dash as you receive it. It is of course easiest to receive payment from your employer in Dash directly, however this may not always be an option. Uphold allows you to instantly and automatically convert any received deposits to and from Dash. Building on this functionality, Bitwage allows you to invoice and receive payment from any employer, practically anywhere in the world, and have a percentage of your wage immediately converted to Dash. You can then withdraw your wage to any Dash wallet for spending or saving. For more information, see the following blog posts:

Bitwage: https://blog.bitwage.com/2018/03/12/get-dash

Uphold: https://uphold.com/en/blog/posts/uphold/bitwage-launches-support-of-dash-powered-by-uphold

Dash Force News: https://www.dashforcenews.com/can-get-salary-dash-right-now

Spending¶

Merchant Directory¶

Dash can be spent in hundreds of stores and services both online and in physical locations.

Discover Dash lists businesses around the world accepting Dash, sorted by category. It’s easy to add your business to the list, and also features a short introduction for new Dash users. The site is maintained by Dash Force, and has been featured on Dash Force News.

Debit Cards¶

Debit cards work by prepaying in Dash to load the account, then withdrawing cash from an ATM or spending online or anywhere debit/credit cards are supported. The Dash is either exchanged at the time of purchase or in advance. For an overview and review of all available and upcoming cards, including cards funded by the Dash budget system, see this article on Dash Force News.

The rapidly evolving approach to regulation of cryptocurrencies such as Dash and instant exchange solutions such as ShapeShift means that availability of debit cards cannot be guaranteed in any or all jurisdictions. Check with the following providers for updates on the availability of Dash debit cards.

Disclaimer: This list is provided for informational purposes only. Dash Core is not liable for any funds transmitted in error to these providers, or for the accuracy of information on this page.

Spend

https://www.spend.com

Spend offers Simple, Preferred and Black Visa cards accepted at over 40 million locations worldwide. Linked with the Spend Wallet, the system allows you to buy or deposit Dash, which is then converted to the appropriate local fiat currency and loaded on the Spend Visa Card for use in purchase and ATM withdrawals.

Crypto.com

https://www.crypto.com

In the Crypto.com Wallet & Card App, users can purchase DASH at true cost with no fees - with credit card and bank transfer both supported. Holders of Crypto.com’s MCO Visa card can also use DASH, making it easy to convert cryptocurrencies into fiat currencies and spend at over 40 million merchants globally.

Change

https://www.getchange.com

The Change Wallet & Card App allows you to convert instantly between all of your currencies and spend with your card worldwide. No commission fees for buying and selling cryptocurrency. Lock your card conveniently from the app in case it gets lost or stolen.

2gether

https://www.2gether.global

2gether is a next generation financial platform that works solely for the benefit of its customers, who are also its owners. A collaborative banking app and cryptocurrency debit card solution are currently available for Eurozone customers.

PolisPay

https://polispay.com

The PolisPay Card is one of the fastest, easiest ways to turn your Dash into fiat currency. You can use your PolisPay Card for online shopping and at any brick and mortar retailer that accepts MasterCard® debit cards. You can also withdraw cash at any MasterCard®-compatible ATM.

Bitsa

https://www.bitsacard.com

The new Bitsa prepaid card allows you to buy online or at any store. You can withdraw cash from any ATM, make transfers between cards or top it up with redeemable vouchers, bank card, transfer, cash or blockchain tokens. Bitsa is a prepaid card topped up using the app, and is not linked to any bank account.

FuzeX

https://fuzex.co

The FuzeX Card & FuzeX Wallet strive to offer an all in one payment solution that provides a smarter way to pay. The card offers real-time exchange of cryptocurrency at the time of purchase. The goal is to make paying with cryptocurrency secure, fast and a seamless process for everyday use.

Paycent

https://paycent.com

Paycent provides Android and iOS wallets that can be funded using both fiat and cryptocurrency. Users can transact with one another within the app, identified by their mobile numbers, or order physical debit cards to spend their balance. Dash is the preferred network partner of Paycent.

SpectroCoin

https://spectrocoin.com

Spectrocoin offers an exchange, wallet and POS service, with a physical card potentially available again soon. Dash, Bitcoin and Ethereum are supported, as well as over 20 major fiat currencies.

Bitwala

https://www.bitwala.com

Bitwala is currently preparing legal documentation to re-launch it’s card service in Europe, and has supported Dash in the past.

Tax¶

Taxation law is different depending on where you qualify as a resident for tax purposes. The following services are available to help you calculate your tax obligations.

Começando¶

O Dash acolhe novos comerciantes e suporta a integração através de um processo padronizado de integração. É fácil começar a aceitar pagamentos no Dash e aproveitar os seguintes benefícios:

Saldo em segundos e liberação em poucos minutos
Capacidade de aceitar pagamentos de qualquer lugar ao redor do mundo
Transações irreversíveis para evitar fraudes
Privacidade avançada para clientes e comerciantes
Taxas mais baixas do setor

A three-part course on why Dash is a popular choice for payments and how integration takes place is available in English and Spanish on DashAcademy.com. To get started with an integration in your sales system, simply select an online or point of sale payment solution from the lists below. If you are unsure, GoCoin is a popular choice due its support for InstantSend, while CoinPayments supports the largest range of online shop software. Anypay is an incredibly simple solution for retail stores, and also supports InstantSend. Larger integrations may require some customisation or cooperation with a specialist payment processor such as ePaymints. This documentation also describes the administrative and technical steps required to integrate various Dash services.

Any Dash received in payment can be automatically converted to the fiat currency of your choice using services such as Uphold. Simply select the card for the target currency and click Add funds -> With cryptocurrency. Any cryptocurrency deposited to this address will immediately be converted to the target fiat currency at the time of deposit.

Muitos grandes comerciantes aceitam Dash - confira Bitrefill ou CheapAir para exemplos de como a integração comercial pode parecer. Assim que estiver pronto para aceitar o Dash, considere adicionar sua empresa ao diretório mantido em Discover Dash para maior visibilidade.

Processadores de pagamento¶

Esta seção lista os processadores de pagamento conhecidos que suportam o Dash e as plataformas de negócios que eles suportam. Por favor, realize uma pesquisa completa antes de escolher um provedor de pagamento para garantir que suas necessidades sejam atendidas.

alt thirty six

https://www.alt36.com

Alt Thirty Six allows any business (including those involved in cannabis) to accept digital payments at the point of sale and online using Dash or USD.

Anypay

https://anypayinc.com

Anypay offers easy, professional tools for retail, as well as Dash rewards for users shopping at your store. Anypay is enjoys broad support from the Dash community, works to bring you new customers and is cheap and easy to set up.

BTCPay Server

https://btcpayserver.org

BTCPay Server is a free, self-hosted and fully open-source cryptocurrency payment processor designed with security, privacy and censorship-resistance at its core.

CDPay

https://www.cdpay.eu

CDPay offers API to accept Dash on your website, as well as an automated fiat exchange service to convert the payments you receive to EUR or CZK.

CoinGate

https://coingate.com

CoinGate offers point of sale apps, payment buttons, e-commerce plugins and an API to accept payments in Dash, with payouts in EUR, USD or Dash.

Coinify

https://coinify.com

Coinify offers a variety of two-way virtual currency services tailored to businesses and customers of different sizes and needs. A simple, secure and compliant solution that allows you to accept virtual currencies without having to hold any currencies yourself, and get payouts in your preferred local currencies.

CoinPayments

https://www.coinpayments.net

CoinPayments is an integrated payment gateway with a wide range of plugins available for popular webcarts, as well as fiat settlement in the US and Europe.

Coinremitter

https://coinremitter.com

Coinremitter is a secure and reliable payment gateway with no monthly fees. Features include built-in exchange, automatic withdrawals and no ID or bank account required.

CoinsPaid

https://coinspaid.com

Coinspaid offers a white label backoffice payments solution with on-the-fly Fiat (EUR) conversion and instant transaction confirmations.

CopPay

https://coppay.io

CopPay allows you to accept Dash and receive EUR, GBP and USD, eliminating volatility risks. CopPay is absolutely free with 0% transaction fee for merchants.

EletroPay

https://eletropay.com

EletroPay is a hardware point of sale device with an ePaper display and built-in receipt printer designed to bring businesses into the digital economy in style.

ePaymints

http://epaymints.com

ePaymints specializes in highly customized payment processing for high risk merchant accounts in industries challenged with high levels of chargebacks.

Festy

https://www.festy.ie

Festy is a data monetisation platform used for payments, ticketing and events. Festy allows you to accept cryptocurrencies at festivals using innovative card or NFC wristbands.

GB CortexPay

https://www.generalbytes.com/pos

Take the professional approach and start accepting Dash with a dedicated CortexPay terminal. his terminal can also be used to sell Dash to clients visiting your location.

GoCoin

https://gocoin.com

The GoCoin platform makes taking Dash as easy as installing a plugin in your webshop. Payment processing is already implemented for every major shopping platform.

GoURL

https://gourl.io

GoURL offers a range of plugins and APIs to accept Dash online. White label solutions to process payments with your logo and on your server are also available.

iQCashNow

https://www.iqcashnow.com

iQCashNow offers ATMs and mobile POS terminal systems that combine traditional payment methods and crypto-payments into a unique complete package of software, hardware and services.

NOWPayments

https://nowpayments.io

NOWPayments is an easy way to accept cryptocurrency payments with native integration into your platform or a neat widget. Auto coin conversion keeps you safe from any dramatic rate fluctuations.

Paybyte

https://paybyte.io

Paybyte allows you to accept cryptocurrency payments through an API or payment buttons for a flat monthly fee.

Paytomat

https://paytomat.com

Paytomat provides software for integration into existing merchant systems without the need to purchase additional hardware or install third-party software.

PumaPay

https://pumapay.io

PumaPay provides a fast, efficient and inexpensive alternative to credit cards to empower your digital customer. We provide the all the tools enabling you to start accepting cryptopayments today.

QR.cr

https://qr.cr

QR.cr is a popular and well-supported dynamic QR code system designed to provide multilingual content and payment services for businesses via mobile friendly landing pages.

Salamantex

https://www.salamantex.com

The Salamantex crypto payment service is available as a hardware terminal or software for installation on existing POS systems or mobile devices.

Spark

https://get-spark.com

Spark is simple, 100% open source software for accepting Dash payments. Designed from the ground up to be familiar and with wide community support, all keys and funds remain in your control at all times.

Xpay

https://xpay.cash

Xpay is a popular point of sale device in Venezuela and Colombia, allowing you to quickly accept Dash using QR codes.

Exemplos de instalação¶

Esta seção contém exemplos de como instalar, configurar e processar seu primeiro pagamento usando os processadores de pagamento listados nesta documentação.

WooCommerce e GoCoin¶

Se a sua loja on-line é construída sobre o WooCommerce, você pode simplesmente instalar o GoCoin como um gateway de pagamento adicional e imediatamente começar a aceitar o Dash. Este guia pressupõe que você já tenha Instalado o Wordpress, Instalado o WooCommerce e criado pelo menos um produto em sua loja.

Vá para a pagina gocoin-woocommerce GitHub Releases e faça o download de um arquivo zip da versão mais recente do plug-in, conforme mostrado abaixo. No seu backend de administração do WordPress, selecione Plugins -> Add Novo e depois clique Carregar Plugin. Click Escolher Arquivo selecione o arquivo que você acabou de baixar e clique em Instalar agora e Ativar Plugin.

Em seguida, vá para a página de inscrição de comerciante do GoCoin e crie uma conta. Quando estiver conectado, vá para Preferências, selecione Dash e clique em Adicionar Endereço DASH para adicionar um endereço de retirada de pagamento. Você receberá um email com um link para confirmar o endereço. Em seguida, acesse Desenvolvedores e copie o Comerciante ID em um arquivo de texto temporário. Em seguida, clique em Obter Chave para exibir uma chave de API válida. Copie essa chave em seu arquivo de texto temporário também. Por fim, opcionalmente, você pode adicionar um logotipo do painel ao seu checkout na seção Perfil e clicar em Logotipo -> Carregar.

De volta à seção de plugins do WordPress, clique no botão Configurações do plug-in WooCommerce e navegue até a seção Checkout -> GoCoin. Verifique se o plug-in GoCoin está ativado aqui e insira o Comerciante ID e API Key nos campos apropriados, conforme mostrado abaixo, modificando os outros campos conforme necessário. Clique em Salvar alterações quando estiver pronto.

Seus clientes verão agora uma opção para pagar com o Dash ao concluir o processo de check-out de um pedido. O pagamento será processado pela GoCoin e você receberá e-mails detalhando cada procedimento de compra. Você pode escolher com que frequência deseja retirar seus pagamentos, para qual endereço do painel e várias outras opções na seção de administração da GoCoin. Veja a GoCoin Documentação para mais informações.

Concluindo o pagamento através do processador de pagamento GoCoin

WooCommerce e CoinPayments.net¶

Se a sua loja on-line é construída sobre o WooCommerce, você pode simplesmente instalar o CoinPayments como um gateway de pagamento adicional e imediatamente começar a aceitar o Dash. Este guia assume que você já tenha instalado o Wordpress, instalado WooCommerce e criado pelo menos um produto em sua loja. Um video do processo para instalar o gateway de pagamento CoinPayments também está disponível.

No painel de administração do WordPress, selecione Plugins -> Add Novo e digite «coinpayments.net» na caixa de pesquisa. Um plugin chamado CoinPayments.net Payment Gateway for WooCommerce deve aparecer. Clique em Instalar agora para instalar o plug-in. Alternativamente, você pode baixar o Download do plugin do site WordPress como um arquivo zip e enviá-lo usando o botão Upload Plugin . Quando o plug-in estiver instalado, clique em Ativar para iniciar a configuração.

Instalando o plugin CoinPayments.net WooCommerce

Em seguida, vá para CoinPayments.net e inscreva-se para criar uma conta. Uma vez que você está logado, vá para Conta -> Configurações de Aceitação de Moedas e ative Dash, bem como, opcionalmente, inserir um endereço de retirada. Em seguida, acesse Conta -> Configurações da conta e copie Sua Id de Operador da área Configurações Basicas em um arquivo de texto. Em seguida, navegue até a seção Configurações do Operador e insira uma série longa e aleatória de caracteres para o segredo do IPN. Copie este código para o seu arquivo temporário também.

De volta à seção de plugins do WordPress, clique no botão Configurações do plug-in WooCommerce e navegue até a seção Checkout -> CoinPayments.net. Verifique se o plug-in CoinPayments está ativado aqui e insira o Codigo do Operador, IPN Secreto e Descrição nos campos apropriados, conforme mostrado abaixo. Clique em Salvar alterações quando estiver pronto.

Configurando o plugin CoinPayments.net WooCommerce

Seus clientes verão agora uma opção para pagar com o Dash ao concluir o processo de check-out de um pedido. O pagamento será processado pelo CoinPayments.net, e você receberá e-mails detalhando cada procedimento de compra. Você pode escolher com que frequência deseja retirar seus pagamentos, para qual endereço do painel e várias outras opções na seção de administração do CoinPayments. Veja a documentação do CoinPayments ou Ferramentas do Comerciante para mais informações.

Concluindo o pagamento através do gateway de pagamento CoinPayments.net

Ponto de venda com Anypay¶

Anypay.global permite que você comece a aceitar pagamentos em ponto de venda rapidamente no Dash em uma loja física. O serviço funciona como um site simples que você carrega em qualquer dispositivo conectado à Internet e ativado por toque, como um smartphone ou tablet.

Comece registrando uma conta no Anypay. Você será solicitado a especificar um endereço de e-mail e senha. Depois de fazer o login, você deve adicionar um endereço de retirada do pagamento do painel.

Configurando Anypay

Depois que isso for configurado, você poderá começar a processar os pagamentos imediatamente. Basta fazer login em https://pos.anypay.global ou tocar em Merchant Point of Sale App na área de administração usando seu dispositivo. Um teclado aparecerá. Insira o valor da fatura em USD ou DASH e pressione o botão COLLECT na parte inferior da tela. O aplicativo gerará um código QR para o seu cliente digitalizar. Assim que o pagamento estiver concluído, você poderá criar uma nova fatura tocando em Next Payment ou visualizar o status de suas faturas tocando no menu button no canto superior esquerdo do teclado ou verificando a seção Invoices do backend de administração. As retiradas são processadas para o endereço que você especificou logo após o pagamento ser concluído.

Ponto de Venda com Spark¶

Spark Payments allows you to quickly start accepting point-of-sale payments in Dash at a physical store. The system works as an app, and is available for Android, macOS, Windows and Linux, with an iOS progressive web app (PWA) in development.

O projeto é um aplicativo de terminal externo para processamento de pagamentos do Dash em lojas físicas. O comerciante digita o valor da venda na moeda local (94 moedas suportadas), o aplicativo gerará uma venda e código QR para a quantidade adequada de Dash para o cliente digitalizar. Em seguida, o terminal fornecerá feedback sobre o status do pagamento (recebido, expirado, parcial, instantado ou regular) e, se configurado, a conversão de fiat por uphold.com. Um guia sobre como configurar o Spark com Uphold para converter pagamentos em moeda fiduciária está disponível em Inglês e Alemão.

Para usar o Spark, abra o aplicativo no seu dispositivo. Se esta é a primeira vez que você está usando o aplicativo, você precisará especificar um endereço de Dash para receber pagamentos do sistema, bem como a moeda fiduciária escolhida. Você pode alterar essas informações a qualquer momento no menu. Para gerar uma fatura de pagamento, insira o valor em moeda fiduciária. O Spark gerará um código QR contendo seu endereço especificado e o valor solicitado, denominado em Dash. O cliente digitaliza o código QR e o aplicativo exibirá uma indicação visual quando o pagamento for concluído.

Configurando e recebendo pagamentos usando o Spark Payments

Sistemas de pagamento como Anypay e Spark podem ser integrados ao seu terminal existente e/ou software de contabilidade (como Square Register, registrando as vendas faturadas no Dash como um Outro tipo de pagamento no sistema. Isso permite que você acompanhe sua renda do Dash tão facilmente quanto se você estivesse aceitando dinheiro.

Administrative Processes¶

It’s easy to get started integrating Dash, but you will need to make some decisions about whether you plan to convert your income earned in Dash into your local fiat currency, or if you prefer to hold some or all of it in Dash. Most payment processors offer a range of fiat conversion options, although various fees and limits may be applicable.

Onboarding Process¶

New merchants typically go through the following steps when joining the Dash ecosystem:

Set up a Dash wallet
Identify an appropriate payment processor
Decide on how and when to convert funds
Implementation and testing
Release and marketing
Integration on DiscoverDash

Promoting Dash¶

A wide range of ready-to-go visual products are available to help you promote Dash as a payment method to your customers. This includes promotional graphics and stickers, fonts for consistent visual design and guidelines on how to use the Dash visual identity. See the Marketing section for more information.

The reduced fees may also offer an additional incentive for your customers to pay with Dash, particularly in businesses with high cash handling fees or where it is necessary to add a fee to process credit card transactions.

Currency Conversion¶

Cryptocurrency is a relatively recent development, and rapid development in the ecosystem coupled with various barriers to access and heavy trading mean that fiat-denominated value is subject to considerable fluctuation. As a merchant, you will need to make decisions about how much of your income taken in cryptocurrency should actually be held in cryptocurrency, and how much should be converted back to a fiat currency (such as USD) directly. Different payment processors offer different solutions to this problem.

Services such as GoCoin are able to convert a specified percentage of received payments into a range of fiat currencies for withdrawal. Others such as CoinPayments offer the ability to diversify your payments into a range of different cryptocurrencies, but require you to set up automatic withdrawals to an exchange for conversion to fiat currency. Finally, services such as Uphold allow you to convert your Dash payments between various currencies and commodities very easily, and even offer automated investment services.

Note that these listing are not endorsements, and you must complete your own due diligence and/or seek advice from a tax and investment specialist before investing.

Legal considerations¶

Tax, legal and regulatory considerations may be applicable in some jurisdictions.

Governança¶

Governança Descentralizada pela Blockchain, ou DGBB, é a tentativa de Dash de resolver dois problemas importantes em criptomoeda: governança e financiamento. A governança em um projeto descentralizado é difícil, porque, por definição, não há autoridades centrais para tomar decisões sobre o projeto. Em Dash, tais decisões são tomadas pela rede, isto é, pelos donos dos masternodes. O sistema DGBB permite que cada masternode vote uma vez (sim / não / abstém) para cada proposta. Se uma proposta for aprovada, ela poderá ser implementada (ou não) pelos desenvolvedores do Dash. Um exemplo importante é no início de 2016, quando o Core Team do Dash submeteu uma proposta à rede perguntando se o tamanho do bloco deveria ser aumentado para 2 MB. Dentro de 24 horas, o consenso foi alcançado para aprovar essa mudança. Compare isso com o Bitcoin, onde o debate sobre o tamanho do bloco tem durado por quase três anos e resultou em sérios desmembramentos dentro da comunidade e até mesmo se forçou na blockchain do Bitcoin.

O DGBB também fornece um meio para o Dash financiar seu próprio desenvolvimento. Enquanto outros projetos têm que depender de doações ou dotações pré-estabelecidas, Dash usa 10% da recompensa em bloco para financiar seu próprio desenvolvimento. Toda vez que um bloco é extraído, 45% da recompensa vai para o minerador, 45% vai para um masternode e os 10% restantes não são criados até o final do mês. Durante o mês, qualquer pessoa pode fazer uma proposta de orçamento para a rede. Se essa proposta receber aprovação líquida de pelo menos 10% da rede do masternode, no final do mês será criada uma série de «superblocos». As recompensas do bloco que não foram pagas (10% de cada bloco) serão usadas para financiar propostas aprovadas. A rede, portanto, se financia, reservando 10% da recompensa em bloco para projetos orçamentários.

No final de 2016, a IOHK preparou um relatório detalhado sobre a versão 0.12.1 do sistema de governança do Dash, incluindo análises formais de fraquezas e áreas para melhoria. Você pode ver o relatório aqui.

Você pode aprender mais sobre a Governança Dash nas seguintes seções:

Compreendendo a governança do Dash¶

Um dos maiores desafios da criação de uma plataforma de criptomoeda é garantir que você crie um sistema descentralizado de governança para gerenciar, financiar, manter e expandir o projeto. Este elemento-chave tem estado ausente em todas as principais divisas até à data, pelo que a resposta natural é criar uma fundação sem fins lucrativos que encarregue de manter o protocolo central e promover a moeda, mas não esteja realmente ligada aos detentores de moeda. qualquer maneira significativa. Essa abordagem tem algumas questões que foram evidenciadas a partir da experiência de plataformas de criptomoeda mais antigas.

As atuais fundações de criptografia não estão relacionadas à própria moeda por qualquer mecanismo incluído no protocolo e não são projetadas para sobreviver aos adotantes iniciais quando perdem o interesse. A fundação então luta para manter o financiamento até que ele imploda e o desenvolvimento central do protocolo seja deixado lutando por financiamento ou dependendo da caridade que não pode ser contada e não permite orçamento e planejamento adequados. As doações também são injustas para os doadores, porque há sempre free riders que se beneficiam do esforço feito por outros sem contribuir. Outros projetos se financiaram pela premiação de moedas ou pela execução de pré-vendas, o que não é uma ótima solução porque o controle dos fundos é centralizado e, nesse estágio, é impossível quantificar as necessidades futuras do projeto.

Através da rede de nós completos e do requisito de garantia, o Dash já tem uma rede descentralizada de operadores de masternodes que investem pesadamente no futuro da moeda e que, como um grupo, podem atuar como administradores do desenvolvimento e promoção do protocolo principal. Propomos um sistema de gestão descentralizado baseado no mecanismo de votação do masternode. Os operadores da Masternode não são os únicos interessados no sucesso do Dash, mas são os mais estáveis porque, ao contrário dos mineiros, eles não podem reutilizar seus ativos para nenhuma outra finalidade ou moeda.

No sistema orçamentário, parte da recompensa do bloco é mantida em depósito pela própria rede, em nome dos operadores, para ser executada no desenvolvimento e expansão do ecossistema de acordo com o voto dos masternodes em diferentes propostas orçamentárias. Estes fundos destinam-se a apoiar o desenvolvimento e a promoção da moeda. Os operadores da Masternode votam em orçamentos e projetos específicos a serem financiados, definindo assim a direção que a moeda está tomando. Isto é feito de uma forma completamente transparente através de um portal público onde novas iniciativas são propostas e os masternodes podem votar nelas. Funcionando como um Kickstarter ou Lighthouse descentralizado, o orçamento pode ser usado para qualquer coisa que crie valor dentro do ecossistema.

Este é um sistema 100% descentralizado alimentado pelos masternodes, onde os orçamentos são definidos e pagos diretamente do blockchain. A blockchain contrata desta forma os principais desenvolvedores e introduz um novo conceito de empreiteiros blockchain, onde as pessoas trabalham e são diretamente compensadas pela rede, através dos votos descentralizados de todos os operadores de masternode. Uma vantagem deste modelo é que ele pode sobreviver aos primeiros usuários. Se os primeiros operadores de masternode vendem suas moedas, o novo proprietário pode criar um masternode e com isso adquirir o direito de votar nos orçamentos e projetos. Isso garante que há um sistema de manutenção em funcionamento à medida que as pessoas vêm e vão, tornando a rede capaz de se sustentar sozinha, sem depender de atores específicos.

Observe que, se você não operar um masternode, ainda poderá votar nas propostas do DashBoost. Veja https://www.dashboost.org para mais informações.

Orçamentos e votação por masternode¶

O sistema funciona como um mecanismo de votação descentralizado estabelecido nas regras que regem o blockchain, onde os orçamentos para projetos específicos são propostos, então os masternodes como um todo votam neles. Cada projeto, se for aprovado, é adicionado ao orçamento total e pago diretamente do blockchain à pessoa que faz o trabalho. Isso permite que o Dash contrate desenvolvedores do núcleo e os pague diretamente após a aprovação do trabalho de forma descentralizada.

Um masternode vota uma proposta (tecnicamente um objeto de governança no blockchain) usando o comando de exemplo “masternode vote yes”, “masternode vote no” ou “masternode vote abstain”. Os votos então se propagam pela rede e são computados de acordo com as instruções seguidas pela própria rede. Orçamentos em discussão e progresso de votação podem ser visualizados usando o comando de exemplo “masternode budget show”.

Um sistema de governança descentralizado bem definido permite que uma rede de criptomoedas resista e sobreviva aos seus criadores originais. Dessa forma, gerações posteriores de operadores de masternodes têm uma maneira clara de suportar o sistema, conforme definido pelo próprio protocolo, aplicando a sabedoria das técnicas de crowd e o vínculo de confiança estabelecido pela garantia da masternode para criar um sistema de gerenciamento descentralizado. Isso cria um valor incrível dentro da moeda, o que nos permite ser mais ágeis e competir com outros sistemas de pagamento, como Bitcoin e cartões de crédito, em escala global.

À medida que o sistema se desenvolveu, uma forte equipe de empreiteiros produtivos pagos com recompensas de blockchain surgiu e se estabeleceu. Isso inclui a equipe principal de desenvolvimento, provedores de garantia, equipe de notícias e relatórios, laboratórios de desenvolvimento experimental, parcerias com universidades, contratação de empresas de marketing e RP e integrações com trocas de terceiros e plataformas de pagamento. O mercado reconhece o valor da estabilidade da rede como um todo e que a possibilidade de financiamento confiável e suficiente resulta em uma implementação mais rápida e mais coerente do roteiro Dash e dos serviços do painel central.

Planejamento de recompensa¶

Para garantir a sustentabilidade a longo prazo do blockchain, a rede mantém uma parte das recompensas do bloco de volta à medida que novos blocos são criados, com os operadores de masternode encarregados de atuar como administradores e investir na manutenção e expansão da rede através de votação. Isso resulta em desenvolvimento e promoção mais rápidos, criando um ciclo virtuoso que beneficia todos os atores, incluindo mineiros, operadores de masternodes, investidores e usuários. Mais importante, isso dá ao blockchain um mecanismo de autopreservação que está além do controle de qualquer indivíduo.

Recompensa de mineração para Prova-de-Trabalho	45%
Recompensa do Masternode para a Prova-de-Serviço	45%
Orçamento de Governança Descentralizada	10%

Masternodes e mineradores recebem 45% da recompensa de mineração, no momento em que são criados. Os 10% restantes são desembolsados mensalmente pelos operadores da masternode, uma vez computados os resultados de seus votos, criando a primeira plataforma descentralizada de criptomoedas auto-sustentável organizada como Organização Autônoma Descentralizada (DAO). Os operadores de masternode estabelecem um contrato social com a rede da qual eles se beneficiam e são obrigados a atuar como cuidadores, dedicando seu tempo, o trabalho de due diligence e uma parte das recompensas da rede para promover o ecossistema. Isso tem um efeito cascata que beneficia todas as partes envolvidas - especialmente os usuários finais.

Espera-se que o valor gerado pelo trabalho realizado na implementação de propostas seja maior do que alocar 100% de recompensas à mineração, porque a rede tem necessidades além de garantir apenas criptograficamente o blockchain. O resultado esperado é maior benefício líquido não apenas para os vencedores das propostas, mas também para operadores de masternode, mineiros e usuários normais. De fato, a própria introdução do orçamento de governança descentralizada foi decidida por um voto de masternode, tornando a primeira decisão distribuída a criação real do sistema, semelhante ao estabelecimento de uma constituição.

Esta abordagem de distribuir a recompensa de bloco normal de uma maneira que considere todos os elementos críticos que uma criptomoeda necessita para a sua viabilidade a longo prazo, e. mineração, nós completos, desenvolvimento e promoção, é revolucionário como é feito sem alterar a emissão ou criar qualquer inflação adicional para os investidores. A rede simplesmente distribui os recursos disponíveis de uma forma que é de maior benefício líquido para todas as partes.

Empreiteiros e propostas¶

Os empreiteiros do blockchain podem ser desenvolvedores, profissionais de extensão, líderes de equipe, advogados ou mesmo pessoas nomeadas para realizar tarefas específicas. As propostas geralmente começam a vida como simples postagens no fórum de pré-proposta no Dash Forum, onde comentários e sugestões são solicitado da comunidade geral. Quando o proprietário da proposta decide que tem uma chance razoável de aprovar a proposta, ela é criada como um objeto de controle no blockchain. Uma taxa de 5 DASH está associada a essa ação para evitar spam e garantir que apenas propostas sérias cheguem até esse estágio. Existem várias ferramentas para permitir que os operadores de masternode revisem e votem confortavelmente nas propostas. O total líquido de votos sim deve exceder 10% da contagem total de masternode no momento em que os votos são computados para passar. Se houver mais propostas aprovadas do que o bloco disponível que a recompensa pode fornecer, as propostas com o maior número de votos sim passarão primeiro, criando um ponto de corte para propostas menos populares. O mesmo processo é então repetido todo mês, e a quantia total de Dash disponível para propostas diminui em aproximadamente 7,14% ao ano, junto com a recompensa geral do bloco.

O vídeo a seguir, de Tao of Satoshi, inclui conselhos para que os proprietários de propostas apresentem propostas durante períodos de alta competição para os fundos orçamentários disponíveis:

Websites de Proposta¶

A comunidade se reuniu em torno do DashCentral como um site para facilitar a discussão e votação de propostas formalmente inseridas no blockchain do Dash. Outros sites, como o Dash Ninja e o Dash Nexus, estão disponíveis para monitorar o progresso ao longo do tempo e coletar estatísticas mais detalhadas. A ferramenta Dash Masternode também permite a votação sem a necessidade de compartilhar chaves privadas masternode com um serviço de terceiros.

Uma visão típica da discussão e votação da proposta no Dash Central

Cada proposta inclui uma descrição dos objetivos da proposta, detalhes sobre o trabalho que será realizado e um detalhamento do orçamento solicitado. Muitas propostas também têm links para seu próprio website ou para a discussão pré-proposta ou incluem um vídeo para validar a identidade e a sinceridade do proprietário da proposta. A discussão sobre o Dash Central ocorre abaixo dessas informações, e os proprietários do masternode têm a opção de verificar a propriedade de um masternode e a capacidade de votar, assinando uma mensagem a partir do endereço do colateral do masternode. O Masternodes pode votar a qualquer momento e também mudar seu voto a qualquer momento até que o bloco de corte seja extraído e a votação seja interrompida. Isso ocorre 1662 blocos antes do superbloco. Após o término da votação, o blockchain executa uma contagem descentralizada e valida todos os votos. Quando o consenso é alcançado, os resultados são transmitidos e o orçamento é alocado logo após em um superbloco.

Detalhes da proposta e botões de votação no Dash Central

Uma vez aprovadas, as propostas podem reportar-se à rede no Dash Forum ou através de canais públicos publicados e mídia social. Como é possível criar propostas que pagam ao longo de vários meses, também é possível revogar o financiamento de um projeto alterando a votação se o desenvolvimento ou o gasto de fundos já alocados for insatisfatório. Isso incentiva os proprietários da proposta a trabalhar de forma honesta e diligente para conquistar a confiança e a aprovação da rede. Discussão contínua e melhoria gradual ao longo do tempo resultam em um vínculo estreito entre a rede e aqueles que trabalham para a rede em papéis de apoio.

Voting on proposals is updated in real time via P2P messages and stored by Dash in cache files, so current winning proposals and the total allocation of the available budget are always open and visible to everyone. Dash Nexus is a popular site used for to view progress on proposal voting.

Monitorando a alocação do orçamento no Dash Nexus

Finalmente, o Dash Watch (que foi financiado por meio de uma proposta orçamentária) existe para monitorar a capacidade dos empreiteiros blockchain cumprirem suas promessas com relação às datas de entrega e aos montantes totais do orçamento. alocados em períodos de votação múltipla. Uma equipe de funcionários dedicados interage rotineiramente com os proprietários de propostas para acompanhar o progresso dos vários projetos e fornecer relatórios aos masternodes de votação em um único local. Embora o fornecimento de dados sobre o desempenho de sua proposta para o Dash Watch seja opcional, muitos proprietários de masternodes aproveitam os dados que disponibilizam para tomar suas decisões de voto. A equipe do Dash Watch pode ser contatada no endereço de e-mail team@dashwatch.org ou através do website.

Monitoramento de propostas no Dash Watch

Alocação de verba¶

O orçamento total da rede pode ser calculado levando 10% da recompensa ao longo do período de tempo entre dois superblocks, que ocorrem a cada 16616 blocos ou aproximadamente 30,29 dias. O corte da votação ocorre 1662 blocos antes do superbloco, e os votos finais são computados neste momento. Uma proposta deve satisfazer a condição (votos SIM - votos NÃO) > (Número total de Masternodes / 10) para ser considerada aprovada. Então, no superbloco, as propostas vencedoras são concedidas na ordem da margem pela qual elas estão passando até que todo o orçamento seja alocado ou não haja mais propostas aprovadas. Isso permite a alocação completamente irremediável e descentralizada do orçamento.

Se uma proposta ultrapassar o limite de votos, mas ainda não houver fundos suficientes para pagar o valor total solicitado, ela não receberá financiamento parcial. Em vez disso, quaisquer propostas menores que também tenham ultrapassado o limite que caberá no orçamento serão financiadas, mesmo que tenham uma aprovação líquida menor do que a proposta maior. Propostas que solicitem pagamento durante vários períodos orçamentários permanecerão no sistema de tesouraria pelo período de validade, mesmo que não passem do limite de votos, e mesmo que orçamento insuficiente esteja disponível para financiamento, conforme descrito acima. Qualquer orçamento não alocado simplesmente nunca é criado no superbloco, reduzindo a inflação desnecessária.

Devido à natureza descentralizada do sistema masternode, às vezes é necessário formar organizações financiadas, como comitês ou empresas, para serem responsáveis por algum projeto ou tarefa. Estes são apresentados da mesma forma, mas o próprio comitê recebe os fundos. Outra alternativa é colocar os serviços de garantia fidedignos entre o evento de alocação de orçamento e o remetente real da proposta para garantir que o trabalho seja pago em etapas, à medida que é entregue. Alguns supervisores sobre empreiteiros blockchain são às vezes necessários. Cada item orçado requer um gerente de equipe ou um comitê responsável pela implementação do trabalho. Periodicamente, espera-se que esse gerente relate as despesas orçamentárias e conclua o trabalho para mostrar o valor criado a partir dos recursos alocados. Isso permite que os remetentes de propostas repetidas criem uma reputação e ganhem a confiança da comunidade. As propostas que não fornecerem relatórios regulares e não puderem responder a perguntas sobre sua alocação orçamentária serão em breve invalidadas se fizerem parte de um ciclo regular de propostas mensais. O resultado é um tipo de sistema de autopoliciando.

Escala e usos futuros¶

À medida que o número de contratados de blockchain aumenta, chega-se a um ponto em que os operadores de masternode não podem ser realisticamente esperados para avaliar o volume de propostas. Neste ponto, organizações de financiamento podem ser criadas para atuar como contratadas para a distribuição de fundos para muitos projetos descentralizados menores, de acordo com as necessidades atuais. O Dash Core Group, Inc. é um exemplo de tal organização.

A existência do sistema de orçamento descentralizado coloca o poder de determinar onde o Dash vai no futuro nas mãos da própria rede de masternode. Todo o desenvolvimento central e vários desenvolvedores de periféricos já são financiados pelo orçamento, e outros projetos nem concebíveis neste momento provavelmente surgirão no futuro. Isso dissocia a sobrevivência e o valor do blockchain da atual base de usuários e desenvolvedores, tornando Dash o primeiro blockchain projetado para sobreviver aos usuários originais, uma rede de criptomoedas descentralizada auto-sustentável que ainda pode operar de forma coesa e trazer serviços de valor agregado aos usuários finais de forma consistente. a caminho.

Conclusão¶

Cada operador de masternode estabelece um vínculo de confiança e um contrato social com a rede, no qual ela é obrigada a contribuir para o desenvolvimento e a manutenção do ecossistema do qual ela se beneficia. De acordo com esse modelo, uma parte dos fundos que o operador está obrigado a receber, em certo sentido, está alocada em custódia, não em propriedade, e é mantida em depósito pela rede para ser executada pelos operadores em benefício do ecossistema. Todos contribuem de forma igual e proporcional aos benefícios que estão recebendo e aos riscos que estão assumindo, não há privilégios nem brechas. Isso é complementado pelo mecanismo de votação total do Nó, que permite que um grupo distribuído vote continuamente em questões práticas sem a necessidade de perder seu direito de decidir a outros, em intervalos de alguns anos, como ocorre com governos tradicionais ou corporações cooperativas.

Vislumbramos um futuro em que esse modelo de contribuição transparente, inquebrável e verificável para o bem comum, em combinação com a participação contínua da multidão por meio de votação ativa, seja utilizado para gerenciar organizações pertencentes ou operadas conjuntamente por seus membros, que compartilham benefícios e responsabilidades desses coletivos, como governos, corporações cooperativas, sindicatos, DAOs, criptomoedas, etc. Chamamos esse modelo de governança descentralizada por blockchain.

Using Dash Governance¶

Dash’s Decentralized Governance by Blockchain (DGBB) is a novel voting and funding platform. This documentation introduces and details the theory and practice to use the system.

Understanding the process¶

introdução¶

DGBB consists of three components: Proposals, Votes, and Budgets
Anyone can submit a proposal for a small fee
Each valid masternode can vote for, against or abstain on proposals
Approved proposals become budgets
Budgets are paid directly from the blockchain to the proposal owner

Proposals¶

Proposals are a request to receive funds
Proposals can be submitted by anyone for a fee of 5 Dash. The proposal fee is irreversibly destroyed on submission.
Proposals cannot be altered once submitted

Votes¶

Votes are cast using the registered voting address
The voting address can be delegated to a third party
Votes can be changed at any time
Votes are counted every 16616 blocks (approx. 30.29 days)

Budgets¶

Budgets are proposals which receive a net total of yes votes equal to or greater than 10% of the total possible votes (for example over 448 out of 4480)
Budgets can be nullified at any time if vote totals (cast or re-cast) fall below the approval threshold
Budgets are processed (paid) in order of yes minus no votes. More popular budgets get payment priority.
Approximately 6176 dash (in 2018) are available for each budget cycle, decreasing by 7.14% every 210240 blocks (approx. 383.25 days).

Object structure¶

The following information is required to create a proposal:

proposal-name: a unique label, 20 characters or less
url: a proposer-created webpage or forum post containing detailed proposal information
payment-count: how many cycles the proposal is requesting payment
block-start: the requested start of proposal payments
dash-address: the address to receive proposal payments
monthly-payment-dash: the requested payment amount

Persistence¶

Proposals become active one day after submission
Proposals will remain visible on the network until they are either disapproved or the proposal’s last payment-cycle is reached
Approval occurs when yes votes minus no votes equals 10% or more of the total available votes.
Disapproval occurs when no votes minus yes votes equals 10% or more of the total available votes.
The total available votes is the count of online and responding masternodes and can be seen by running the command masternode count in the Dash Core wallet debug window. A graph of the total masternode count can be found here

Templates¶

The following two Microsoft Word templates are available from Dash Core Group to help facilitate standardized proposal submission and updates. Usage is recommended, but not required.

Budget cycles¶

When preparing a proposal, be aware of when the next cycle will occur and plan accordingly. It is recommended to choose your proposal payment start block at least one cycle in the future to allow time for discussion and gathering support and votes. Note that votes will no longer be tallied 1662 blocks (approximately 3 days) prior to the superblock.

Block height	Approximate date
1212968	Thu Jan 30 02:38:52 UTC 2020
1229584	Sat Feb 29 09:43:54 UTC 2020
1246200	Mon Mar 30 16:48:56 UTC 2020
1262816	Wed Apr 29 23:53:58 UTC 2020
1279432	Sat May 30 06:59:00 UTC 2020
1296048	Mon Jun 29 14:04:02 UTC 2020
1312664	Wed Jul 29 21:09:04 UTC 2020
1329280	Sat Aug 29 04:14:06 UTC 2020
1345896	Mon Sep 28 11:19:08 UTC 2020
1362512	Wed Oct 28 18:24:10 UTC 2020
1379128	Sat Nov 28 01:29:12 UTC 2020
1395744	Mon Dec 28 08:34:14 UTC 2020

You can view the source code for this calculation at this GitHub gist

Creating proposals¶

Once you have prepared the text of your proposal and set up a website or forum post, it is time to submit your proposal to the blockchain for voting. While all tasks involved with creating a budget proposal can be executed from the Dash Core wallet console, several tools providing a user interface have been developed to simplify this procedure.

Dash Budget Proposal Generator¶

https://proposal.dash.org

The Dash Budget Proposal Generator supports creating budget proposals on both mainnet and testnet. In the first step, you must enter a short, clear and unique name for the proposal as it will appear on the blockchain. Proposal names are limited to 40 characters. You can then provide a link to the forum or DashCentral where your proposal is described in more detail (use a URL shortening service if necessary), as well as select the amount of payment you are requesting, how often the payment should occur, and the superblock date on which you are requesting payment. This allows you to control in which budget period your proposal will appear, and gives you enough time to build support for your proposal by familiarising voters with your project. Note that the payment amount is fixed and cannot be modified after it has been submitted to the blockchain.

Steps 1 & 2: Creating your proposal and preparing the command

Next, the proposal generator will provide you with a command to run from the console of your Dash Core wallet to prepare your budget proposal governance object. Running this command will cost you 5 DASH, which will be «burnt» or permanently removed from circulation. This one-time fee protects the governance system from becoming overwhelmed by spam, poorly thought out proposals or users not acting in good faith. A small transaction fee is charged as well, so make sure slightly more than 5 DASH is available in your wallet. Many budget proposals request reimbursement of the 5 DASH fee.

First unlock your wallet by clicking Settings > Unlock wallet, then open the console by clicking Tools > Debug console and paste the generated command. The transaction ID will appear. Copy and paste this into the proposal generator response window. As soon as you do this, the system will show a progress bar as it waits for 6 confirmations as follows:

Step 3: Creating the proposal transaction and waiting for 6 confirmations of the transaction ID

Once 6 block confirmations exist, another command will appear to submit the prepared governance object to the network for voting. Copy and paste this command, and your governance object ID will appear as follows:

Step 4: Submitting the governance object to the network

You can use this ID to track voting on the proposal until the budget closes and you receive your payout. You can also submit the ID to DashCentral to claim your proposal and enable simplified voting for masternodes using DashCentral voting services.

DashCentral Proposal Generator¶

https://www.dashcentral.org/budget/create

DashCentral also includes a tool to create budget proposals, or claim existing proposals so you can add a description on DashCentral and begin discussion with the community. The steps to be taken are almost identical to the procedure described above, and documentation is available here.

Voting on proposals¶

You must vote at least three days before the superblock is created or your vote will not be counted. The exact deadline is 1662 blocks before the superblock.

Observe que, se você não operar um masternode, ainda poderá votar nas propostas do DashBoost. Veja https://www.dashboost.org para mais informações.

Voting on DGBB proposals is an important part of operating a masternode. Since masternodes are heavily invested in Dash, they are expected to critically appraise proposals each month and vote in a manner they perceive to be consistent with the best interests of the network. Each masternode may vote once on each proposal, and the vote can be changed at any time before the voting deadline. The following sites and tools are available to view and manage proposals and voting:

For information on how to create a proposal, see here.

DashCentral¶

Many masternode operators store their password-protected masternode private key on DashCentral to enable simple voting with a user-friendly interface. The popularity of this site has made it a common place for discussion of the proposals after they are submitted to the governance system. To vote from the DashCentral web interface, first add your masternode private key to your account according to the instructions here. Note that the masternode private key is not the same as the private key controlling the 1000 DASH collateral, so there is no risk of losing your collateral. A separate password is required to unlock the masternode private key for voting, so the risk of the site operator voting in your name is minimal.

When you are ready to vote, go to the budget proposals page. Simply click to view the proposals, then click either Vote YES, Vote ABSTAIN or Vote NO.

Voting interface on DashCentral

Dash Masternode Tool (DMT)¶

If you started your masternode from a hardware wallet using DMT, you can also use the tool to cast votes. Click Tools > Proposals and wait for the list of proposals to load. You can easily see the voting status of each proposal, and selecting a proposal shows details on the Details tab in the lower half of the window. Switch to the Vote tab to Vote Yes, Vote No or Vote Abstain directly from DMT.

Voting interface in DMT

Dash Core wallet or masternode¶

If you started your masternode using the Dash Core Wallet (not recommended), you can vote manually from Tools > Debug console, or directly from your masternode via SSH using dash-cli. First click on the proposal you want to vote on at either DashCentral or Dash Ninja. You will see a command for manual voting below the proposal description. Copy and paste the command and modify it as necessary. As an example, take this proposal from Dash Ninja (or DashCentral). The voting code for Dash Core Wallet is as follows:

gobject vote-many 6ed7418455e07f4b30b99f0d4a24a2b83282e12b26fe3415673ecbea04ff6c9d funding yes
gobject vote-many 6ed7418455e07f4b30b99f0d4a24a2b83282e12b26fe3415673ecbea04ff6c9d funding no
gobject vote-many 6ed7418455e07f4b30b99f0d4a24a2b83282e12b26fe3415673ecbea04ff6c9d funding abstain

Note that to vote from your masternode directly, you need to prefix the command with dash-cli, which is usually found in the .dashcore folder. The command should be similar to the following:

~/.dashcore/dash-cli gobject vote-many 6ed7418455e07f4b30b99f0d4a24a2b83282e12b26fe3415673ecbea04ff6c9d funding yes
~/.dashcore/dash-cli gobject vote-many 6ed7418455e07f4b30b99f0d4a24a2b83282e12b26fe3415673ecbea04ff6c9d funding no
~/.dashcore/dash-cli gobject vote-many 6ed7418455e07f4b30b99f0d4a24a2b83282e12b26fe3415673ecbea04ff6c9d funding abstain

Note this command will trigger a vote from all masternodes configured in dash.conf. If you have multiple masternodes each with its own .conf file, or if you want to vote with only some of your masternodes, you must change the command from vote-many to vote. If your vote was successful, you should see a confirmation message reading Voted successfully.

Voting from the debug console in Dash Core Wallet

You can also view a list of proposals in JSON format from the console to copy and paste the proposal hash for voting as follows:

gobject list

Delegating votes¶

DIP003 masternodes feature a separate voting key, which makes it possible to delegate your vote to a representative. Simply enter a Dash address provided by the delegate when registering your masternode, or update your masternode registration to delegate the vote of a running masternode. The wallet controlling the private key to this address will then cast votes on behalf of this masternode owner simply by following the Dash Core voting procedure described above. No further configuration is required.

8 etapas para uma proposta bem sucedida¶

As propostas no sistema de governança estão sujeitas a votação pelos masternodes. Então, como qualquer votação, você precisa convencer os eleitores de que sua proposta deve ser aprovada. Aqui estão alguns pontos importantes a serem considerados em todas as propostas:

Mantenha sua proposta clara: Sua proposta deve ter um título claro, seguido por uma descrição curta e objetivos simples. Explicar no início da sua proposta exatamente como isso beneficiará a rede do Dash, quanto Dash você está solicitando, como chegou a esse valor e, finalmente, quem você é e como planeja fazer o trabalho. Os Masternodes deve ser capaz de ter uma idéia do que você está propondo desde as primeiras linhas da sua proposta.
Executar uma discussão de pré-proposta: Obtenha feedback da comunidade antes de postar sua proposta no blockchain. Um período de discussão de cerca de duas semanas ajudará você a descobrir se alguém propôs algo semelhante no passado e se foi bem-sucedido ou não. Existem canais de pré-proposta no fórum e Dash Nation Discord, e Reddit Também atrai muitos pontos de vista - considere a discussão sobre esses canais como a fase de pesquisa de sua proposta. Posteriormente, você pode postar um link para a discussão no fórum quando sua proposta for publicada para mostrar que você está incluindo o feedback da comunidade em seu trabalho.
Gerenciar sua identidade e reputação: A comunidade Dash é um dos recursos mais fortes da rede e os novatos são sempre bem-vindos. No entanto, devido ao modo como as propostas funcionam, é necessário que haja confiança razoável de que o trabalho prometido na proposta será concluído se for aprovado. Se você é novo, considere começar com uma proposta menor primeiro para provar sua capacidade de entregar dentro do prazo e do orçamento. Anexando seu nome real ou Keybase Identidade para uma proposta também ajuda a construir confiança. Se você estiver fazendo uma grande proposta, junte uma equipe e nomeie (ou contrate) uma pessoa para atuar como contato com a comunidade, já que a postagem de várias contas pode ser confusa.
Faça uma campanha entusiasmada para sua proposta: Propostas com um vídeo ou site têm uma chance muito maior de sucesso! Fazer upload de um vídeo dá à sua proposta um toque humano e uma chance de transmitir seu entusiasmo de uma forma que nem sempre é possível no texto. Publique seu vídeo no forum e DashCentral, Torne-se um usuario regular no Discord ou faça um webinar para explicar a proposta e responder a perguntas. Ponha um pouco de trabalho antes de pedir fundos para demonstrar seu envolvimento com o Dash - mas não seja irritante e não envie spam para muitos canais pedindo votos.
Demonstrar seu compromisso com a rede: Se você está pedindo financiamento significativo para iniciar ou expandir um negócio com fins lucrativos baseado em Dash, é necessário explicar por que e por quanto tempo esse financiamento é necessário e o que você está oferecendo em troca. Pode ser muito útil mostrar que você tem interesse no jogo combinando a contribuição fornecida no Dash com fundos de sua própria empresa ou investidores. Acordos de capital próprio ou de exclusividade podem ser alcançados com Dash Core Group, Inc., mas deve ser esclarecido por escrito antes que a proposta seja publicada.
Publique sua proposta com antecedência e fique à disposição para perguntas: A janela de votação fecha 1662 blocos (ou pouco menos de 3 dias) antes do superbloco. Para dar aos operadores de masternode tempo suficiente para considerar, discutir e votar em sua proposta, você deve publicá-la bem antes do prazo de votação - é melhor esperar pelo próximo superbloco do que correr! A maioria dos masternodes verá sua proposta pela primeira vez, uma vez que apareça no blockchain ou quando você a reivindicar no DashCentral. As primeiras horas de discussão entre os proprietários de masternodes normalmente trazem muitas perguntas e podem ser críticas para influenciar a opinião e a votação, portanto, fique disponível durante esse período.
Mantenha a comunidade atualizada quando sua proposta passar: Sua proposta deve incluir detalhes de como você planeja manter a comunidade e a rede informadas sobre seu trabalho. Cumpra seus compromissos e publique relatórios regulares para que sua saída seja clara e fique disponível nos canais sociais para responder a perguntas. Lembre-se de que sua capacidade de transmitir propostas futuras depende da sua capacidade demonstrada de fornecer e se comunicar.
Considere providências para pedidos grandes: Se você está solicitando uma quantidade significativa de financiamento, existe uma preocupação compreensível de que você cumprirá suas promessas à rede. Entre em contato com intermediários confiáveis, como Dash Core Group, Inc. ou Green Candle, Inc. antecipadamente para aconselhamento sobre depósito e tornar as condições para liberação de custódia públicas e parte da proposta. Se sua proposta for tão grande que use uma porcentagem significativa do orçamento, haverá um risco de que a aprovação de sua proposta colida com propostas menores fora do orçamento. Considere dividir sua proposta em pagamentos mensais menores.

Veja está documentação para instruções específicas sobre como criar uma proposta quando estiver pronto. Boa sorte!

Para um exemplo de boa reportagem, gerenciamento de reputação e uso de um vídeo para solicitar financiamento em uma pré-proposta, veja este vídeo da extremamente popular série de Amanda B. Johnson. DASH: Detailed proposal:

Alguns pontos adicionais:

Atualmente, não é possível pagar uma proposta de orçamento para um endereço multisig ou alterar o endereço de pagamento após a publicação da proposta no blockchain.
Para evitar acusações de favoritismo e negociação interna, a Dash Core não pode promover sua proposta para você. Se a sua proposta é uma integração, entre em contato com a equipe de desenvolvimento de negócios com antecedência. Uma vez que seu produto estiver ativo, pode ser possível anunciar isso dos canais do Dash Core.
Se a sua proposta é para notícias, promoção ou marketing, certifique-se de sincronizar seus esforços com as principais organizações existentes, como o Dash Force News ou empresas de marketing contratadas pelo Dash Core.
Você é responsável pelo seu próprio planejamento para se proteger contra a volatilidade dos preços. Se a sua proposta envolver pagamentos significativos a terceiros em moeda fiduciária, entre em contato com Dash Core Group, Inc. ou Green Candle, Inc. para aconselhamento sobre custódia, manutenção de preços, conversão de moedas e cobertura contra a volatilidade.
Pela mesma razão, não é recomendado solicitar financiamento por período superior a três meses. Os Masternodes não quer ver e votar na mesma proposta sem atualizações por vários meses seguidos, e a volatilidade dos preços faz dela uma proposta arriscada para a rede e para você mesmo.
Antes de inserir sua proposta de orçamento no blockchain, verifique quantas propostas já existem para o atual ciclo orçamentário. Se é provável que fique muito lotado ou se algumas propostas estão solicitando uma parcela significativa do orçamento, o voto provavelmente será muito competitivo, com projetos mais fracos sendo forçados a sair do orçamento, mesmo que eles colham votos suficientes para ultrapassar o limite de 10%. . Veja aqui para mais detalhes.

Masternodes¶

Dash is best known as the first cryptocurrency with a focus on user-friendly payments and transaction speed. What many people do not know is that these features are implemented on top of a network of dedicated servers known as masternodes, which gives rise to many exciting features not available on conventional blockchains. These features include instant and private transactions, as well as governance of the development of the Dash network through a monthly budget and voting. This in itself is a first in the crypto world, and the masternodes are necessary to achieve the privacy and speed that Dash offers.

Essa documentação se concentra na compreensão dos serviços que os masternodes fornecem à rede, mas também inclui guias sobre como executar um masternode, usando um provedor de hospedagem ou configurando e mantendo seu próprio serviço de hospedagem. O principal requisito para executar um masternode na rede do Dash é de 1000 DASH. Isso é conhecido como garantia e não pode ser gasto sem interromper a operação do masternode. O segundo requisito é o servidor real executando o software Masternode do Dash.

Opção 1: masternode hospedado

Como a operação de seu próprio servidor requer um certo nível de conhecimento sobre blockchains e sistemas operacionais de servidores Linux, vários membros da comunidade oferecem soluções de hospedagem dedicadas por uma taxa. Aproveitar esses serviços significa que o usuário só precisa fornecer a garantia do masternode e pagar a taxa de hospedagem para receber o pagamento da recompensa do bloco. Veja estas páginas para obter informações sobre como configurar um masternode hospedado.

Opção 2: auto-operando o masternode

Usuários com uma compreensão mais profunda (ou curiosidade) sobre o funcionamento interno da rede do Dash podem optar por operar seu próprio masternode em seu próprio servidor host. Várias etapas são necessárias e o usuário deve assumir a responsabilidade de configurar, proteger e manter o servidor e a garantia. Veja estas páginas para obter informações sobre como configurar um masternode auto-operado.

Entendendo os Masternodes¶

Os Masternodes, antes exclusivos da rede Dash, estão se tornando populares à medida que a tecnologia é colocada em outros blockchains. Esta seção da documentação descreve os princípios e mecanismos dos masternodes e os serviços que eles fornecem especificamente para a rede do Dash.

Simply put, a masternode is a server with a full copy of the Dash blockchain, which guarantees a certain minimum level of performance and functionality to perform certain tasks related to block validation, as well as PrivateSend and InstantSend, as the privacy and instant transaction features in Dash are called. The masternodes are paid for this service, using a concept known as Proof of Service. This is in addition to the Proof of Work done by miners to secure the blockchain. Masternodes are also allowed to vote on governance and funding proposals, with each masternode receiving one vote (yes/no/abstain) on each proposal submitted to the system.

Qualquer um pode executar um masternode. O objetivo é ter descentralização suficiente para garantir que nenhuma pessoa individual controle uma fração significativa dos masternodes. No entanto, para evitar o inchaço da rede com masternodes desnecessários ou incentivar os operadores imprudentes, há uma condição que precisa ser cumprida: prova de propriedade de 1000 Dash. As moedas não precisam estar no masternode, mas precisam ser mantidas de uma maneira que seja transparente para toda a rede. Se o proprietário move ou gasta essas moedas, o masternode pára de funcionar e o pagamento é interrompido.

Masternodes are paid by the network for the PrivateSend, InstantSend and governance services they provide. 45% of the block reward is paid out to the masternodes, 45% to miners and 10% to the budget. In practice, half of the reward from a normal block goes to the miner and half to the masternode. Then, every 16,616 blocks (approximately 30.29 days), a superblock is created that contains the entire 10% payout to the budget proposal winners. Masternodes are selected for payment in each block (approximately every 2.6 minutes) from a deterministic masternode list, and moved to the back of the list after payment. As more masternodes are created, the duration between payments increases. If the collateral behind a masternode is spent, or if a masternode stops providing services to the network for more than one hour, it is removed from the list until normal service resumes. In this way, masternodes are given incentive to provide efficient and reliable services to the network.

Ter tantos servidores mantendo uma cópia completa do blockchain e trabalhando para a moeda pode ser extremamente útil. Graças ao sistema de recompensas, não há risco de não ter masternodes suficientes, e os desenvolvedores podem contar com eles rapidamente implementando qualquer novo recurso descentralizado que desejarem implementar. É aí que reside a verdadeira força do Dash - um sistema incentivado de milhares de servidores distribuídos trabalhando 24x7 significa que o Dash pode escalar com mais eficiência e implantar serviços mais rapidamente do que um blockchain executado inteiramente por voluntários não remunerados. Quanto mais masternodes, melhor e mais segura a rede do Dash.

As of November 2018, the Dash network has over 5000 masternodes located in over 45 countries and hosted on over 140 ISPs. The block reward is approximately 3.34 Dash, so the selected masternode receives 1.67 Dash per payment or approximately 6 Dash per month. The block reward decreases by 7.14% approximately once per year, so the annual earnings for a masternode owner is approximately 7% of the collateral, and will decrease over time as calculated here. See this tool to calculate real-time payment rates, and this site for various real-time statistics on the masternode network.

DIP003 Masternode Changes¶

Dash 0.13.0 implements DIP003, which introduces several changes to how a Dash masternode is set up and operated. A list of available documentation appears below:

Important concepts and changes:

It is possible to upgrade an existing masternode in-place without starting a new server and without moving your 1000 DASH collateral.
A masternode was previously «started» using the masternode start-alias command based on a masternode.conf file. Under DIP003, this file is no longer used, and masternodes are «registered» instead of «started». Masternodes begin offering services when a ProRegTx special transaction containing a particular key is written to the blockchain.
As before in masternode.conf, the ProRegTx references the transaction id (txid) and index holding the collateral. The IP address and port of the masternode are also defined in this transaction.
The ProRegTx contains 2 Dash addresses (also called public keys) and one BLS public key, which represent 3 different roles in the masternode and define update and voting rights. The keys are:
1. ownerKeyAddr: This is a Dash address (public key) controlled by the masternode owner. It is different from the address used for the collateral. Because the owner uses the private key associated with this address to issue ProUpRegTx transactions, it must be unique for each masternode.
2. operatorPubKey: This is the BLS public key of the masternode operator. Only the operator is allowed to issue ProUpServTx transactions. Because the operator key is used during live masternode operation to sign masternode-related P2P messages, quorum-related messages and governance trigger votes, the BLS key must be unique for each masternode.
3. votingKeyAddr: This is a Dash address (public key) used for proposal voting. Votes signed with the corresponding private key are valid while the masternode is in the registered set.
Masternode payments were previously sent to the address holding the collateral. Under DIP003, the owner should specify a different address to receive payments in the ProRegTx. The owner may optionally specify a non-zero percentage as payment to a separate masternode operator, if applicable.
The masternode configuration can later be updated using ProUpServTx, ProUpRegTx and ProUpRevTx transactions. See Updating Masternode Information in DIP003 and Updating Masternode Information in this documentation for more details.
All functions related to DIP003 will only take effect once Spork 15 is enabled on the network. Until then, it is necessary to set up the masternode following the old process and then work through the upgrade procedure. In this state, the masternode will continue to function in compatibility mode, and all DIP003 related functions, such as payments to a separate address or percentage payments to operators, will not yet have any effect. The ownerKeyAddr and votingKeyAddr must also be identical until Spork 15 is enabled.

The process of setting up or upgrading a masternode is as follows:

Set up your server and operating system
Install the Dash software and synchronize the blockchain
Generate a BLS key pair and enter the private key on the masternode
Prepare a ProRegTx transaction
Sign the ProRegTx transaction
Submit the signed ProRegTx transaction

Step 1 can be omitted if you have an existing server. Steps 2 and 3 require direct access to the masternode. Steps 3 and 4 require access to a Dash Wallet (or DMT). Step 5 requires access to the wallet actually holding the collateral. Step 6 requires a Dash balance to pay the transaction fee.

Masternodes vs. mineração¶

Dash, como o Bitcoin e a maioria das outras criptomoedas, é baseado em um registro descentralizado de todas as transações, conhecido como blockchain. Este blockchain é garantido através de um mecanismo de consenso; no caso do Dash e do Bitcoin, o mecanismo de consenso é o Proof of Work (PoW). Mineração tentam resolver problemas difíceis com computadores especializados e, quando resolvem o problema, recebem o direito de adicionar um novo bloco ao blockchain. Se todas as outras pessoas que executam o software concordarem que o problema foi resolvido corretamente, o bloco é adicionado ao blockchain e o minerador é recompensado.

O Dash funciona um pouco diferente do Bitcoin, porque tem uma rede de dois níveis. A segunda camada é acionada por masternodes (Full Nodes), que permitem a privacidade financeira (PrivateSend), transações instantâneas (InstantSend) e o sistema descentralizado de governança e orçamento. Como esse segundo nível é tão importante, os masternodes também são recompensados quando os mineiros descobrem novos blocos. A distribuição é a seguinte: 45% da recompensa em bloco vai para a mineradora, 45% para os masternodes e 10% para o sistema de orçamento (criado por superblocos todos os meses).

O sistema masternode é referido como Prova de Serviço (PoSe), uma vez que os masternodes fornecem serviços cruciais para a rede. De fato, toda a rede é supervisionada pelos masternodes, que têm o poder de rejeitar os blocos mal formados dos mineiros. Se um mineiro tentasse levar a recompensa do bloco inteiro para si ou tentasse executar uma versão antiga do software Dash, a rede masternode ficaria órfã desse bloco, e não seria adicionado ao blockchain.

Em suma, os mineradores tem poder a primeira camada, que é o básico de envio e o recebimento de fundos e prevenção de doublespending. Masternodes tem poder da segunda camada, que fornecem os recursos adicionais que tornam a Dash diferente de outros criptomoedas. E computadores de mineração não podem servir como masternodes. Além disso, cada masternode é «protegido» por 1000 DASH. Essas DASH permaneçam sob o controle exclusivo de seu proprietário em todos os momentos e ainda pode ser gasto livremente. Os fundos não são bloqueados de forma alguma. No entanto, se os fundos são movidos ou gasto, o dono do masternode vai ficar off-line e parar de receber recompensas.

Lógica de pagamento¶

Masternode payments in Dash version 0.13.0 are entirely deterministic and based on a simple list sort algorithm. For documentation of version 0.12.0 payment logic, see the legacy masternode payment documentation. Dash version 0.13.0 implements DIP003 and defines two sets of masternodes.

The full set, which contains all registered masternodes that have not spent their collateral funding transactions.
The valid set, a subset of the full set which contains all masternodes which are not marked as Proof of Service (PoSe) banned.

Each masternode in the set of valid masternodes, identified by its registration transaction ID, is associated with the block at which it was last paid. If it has never received payment or was banned for failing to meet the PoSe requirements, then the block at which it was first registered or at which service was restored is used instead. The list is sorted in ascending order by this block height and ProRegTx hash (as a tie breaker in case two masternodes were registered in the same block), and the first entry is selected for payment.

Proof of Service¶

Proof of Service (PoSe) is a scoring system used to determine if a masternode is providing network services in good faith. A number of metrics are involved in the calculation, so it is not possible to game the system by causing masternodes to be PoSe banned for failing to respond to ping requests by e.g. a DDoS attack just prior to payment. Each failure to provide service results in an increase in the PoSe score relative to the maximum score, which is equal to the number of registered masternodes. If the score reaches the number of registered masternodes, a PoSe ban is enacted and the masternode must be repaired to ensure it provides reliable service and registered in the list again using a ProUpServTx. The current scoring rules as of Dash 0.14 are:

Failure to participate in DKG= 66% punishment
Each subsequent block reduces PoSe score by 1

Seleção de quórum¶

In past versions of Dash, quorums of 10 masternodes were formed spontaneously to lock InstantSend transactions. As of Dash 0.14, quorums are deterministically formed, contain more masternodes and remain alive for a longer period of time. While they remain responsible for InstantSend transactions, the locking mechanism has changed to automatically attempt locks on most network transactions according to the requirements described here. Masternodes are now also responsible for more network consensus functions, such as ChainLocks. Masternode quorums are formed through a process of distributed key generation. Failure to participate in DKG will eventually result in a PoSe ban as described above.

Requisitos de Masternode¶

1000 Dash: Indiscutivelmente a parte mais difícil. Dash pode ser obtido em trocas como Poloniex, Bittrex, Kraken e LiveCoin. O serviço da Shapeshift também é um excelente caminho.
A server or VPS running Linux: Most recent guides use Ubuntu 18.04 LTS. We recommend VPS services such as Vultr and DigitalOcean, although any decent provider will do. Generally an instance with low to average specifications will do, although performance requirements will increase according to this roadmap.
Um endereço IP dedicado: Estes geralmente vêm com o VPS/servidor.
Um pouco de tempo e (coração): Masternodes costumava exigir uma configuração complexa, mas ferramentas como o Dashman agora simplificam bastante o processo.

In addition to the 1000 Dash held in collateral, masternodes also have minimum hardware requirements. For Dash versions 0.14 and higher, these requirements are as follows:

	Mínimo	Recomendado
CPU	1x 1 GHz	1x 2 GHz
RAM	2 GB + 2 GB swap	4 GB + 2 GB swap
Disco	40 GB	60 GB
Network	400 GB/mth	1 TB/mth

O uso de largura de banda da Masternode varia entre 300 e 500 GB por mês e crescerá conforme a rede.

Dash Evolution¶

The exact hardware requirements for Dash Evolution masternodes have yet to be determined, although some pointers can be taken from the roadmap and this blog post. It should be possible to run Dash masternodes on normal VPS servers until the block size reaches approximately 20 MB, after which custom hardware such as GPUs and eventually ASICs may be required.

Hosting Services¶

Several Dash community members offer masternode hosting services. This service can be realized securely without the customer ever giving up control of the 1000 DASH required for collateral. For security reasons, it is highly recommended to keep the collateral on a hardware wallet when taking advantage of a hosting service. A list of currently available masternode hosting services is available below.

List of hosting services¶

Disclaimer: Dash Core may be affiliated with these community members, but is not involved in the provision of any of these services.

CrowdNode¶

https://crowdnode.io

Operated by: CrowdNode ApS
Services: Hosting, Shares
Cost: 15% of masternode payments
Site
Email

SID Hosting Service¶

https://dashmasternode.io

Operated by: splawik21 (Dash Core team member)
Services: Hosting
Cost: €25/month, paid in Dash
Site
Email

Allnodes¶

https://www.allnodes.com

Operated by: Sephiroth
Services: Monitoring, Hosting
Cost: $5/month (free during beta)
Site
Email
Twitter
Telegram
Discord

Node40¶

https://node40.com

Operated by: Perry Woodin
Services: Hosting, Voting, Tax Compliance
0.34 Dash/month (variable, discounts available)
Site
Email
Forum
Review

Masternodehosting¶

https://masternodehosting.com

Operated by: flare (Dash Core team member)
Services: Hosting
Cost: €18/month
Site
Email
Forum

NodeHub.io¶

https://nodehub.io

Operated by: NodeHub.io Platform
Services: Hosting, Governance, Stats
Cost: $9.90/month (charged daily at $0.33)
Site
Email
Twitter
Discord

Gentarium¶

https://mn.gtmcoin.io

Operated by: Gentarium International OÜ
Services: Hosting, Shares
Cost: $3.99/month (charged daily at $0.15)
Site
Email
Twitter
Discord

Registering a hosted masternode¶

Dash 0.13.0 implements DIP003, which introduces several changes to how a Dash masternode is set up and operated. A list of available documentation appears below:

It is highly recommended to first read at least the list of changes before continuing in order to familiarize yourself with the new concepts in DIP003.

Registering a hosted masternode is done in several steps:

Send 1000 DASH to an address you control in a single transaction and wait for 15 confirmations
Correspond with your hosting provider to determine who will generate the operator BLS keys, whether their fee will be paid by an operator reward percentage or according to a separate contract, and whether the masternode will be set up before or after the registration transaction
Prepare, sign and broadcast the registration transaction using Dash Core or DMT

It is highly recommended to store the keys to your masternode collateral on a hardware wallet for added security against hackers. Since the hardware wallet is only used to sign a transaction, there is no need to ever connect this wallet to the internet. However, a Dash Core wallet with balance (for the transaction fee) is required to submit the registration transaction. The masternode registration process closely follows the setup guide, beginning from the registration step.

Operator transactions¶

This documentation is intended for operators managing nodes on behalf of owners. If you provide an IP address and port of a synchronized full node with your masternodeblsprivkey entered in the dash.conf file as descibed here to the masternode owner, it will appear in the DIP003 valid set immediately after they submit the protx register_submit command as described above. If the full node is not running, or if the owner submits 0 for the ipAndPort, then the node will be registered in a PoSe-banned state. In this case, the operator will need to issue a ProUpServTx transaction to update the service features and register the masternode.

The ProRegTx submitted by the owner also specifies the percentage reward for the operator. It does not specify the operator’s reward address, so a ProUpServTx is also required to claim this reward by specifying a Dash address. If the reward is not claimed, it will be paid to the owner in full.

Setup¶

Setting up a masternode requires a basic understanding of Linux and blockchain technology, as well as an ability to follow instructions closely. It also requires regular maintenance and careful security, particularly if you are not storing your Dash on a hardware wallet. There are some decisions to be made along the way, and optional extra steps to take for increased security.

Commercial masternode hosting services are available if you prefer to delegate day-to-day operation of your masternode to a professional operator. When using these hosting services, you retain full control of the 1000 DASH collateral and pay an agreed percentage of your reward to the operator. It is also possible to delegate your voting keys to a representative, see the governance documentation for more information.

Before you begin¶

This guide assumes you are setting up a single mainnet masternode for the first time. If you are updating a masternode, see here instead. You will need:

1000 Dash
A wallet to store your Dash, preferably a hardware wallet, although Dash Core wallet is also supported
A Linux server, preferably a Virtual Private Server (VPS)

Dash 0.13.0 and later implement DIP003, which introduces several changes to how a Dash masternode is set up and operated. While this network upgrade was completed in early 2019, a list of available documentation appears below:

This documentation describes the commands as if they were entered in the Dash Core GUI by opening the console from Tools > Debug console, but the same result can be achieved on a masternode by entering the same commands and adding the prefix ~/.dashcore/dash-cli to each command.

Set up your VPS¶

A VPS, more commonly known as a cloud server, is fully functional installation of an operating system (usually Linux) operating within a virtual machine. The virtual machine allows the VPS provider to run multiple systems on one physical server, making it more efficient and much cheaper than having a single operating system running on the «bare metal» of each server. A VPS is ideal for hosting a Dash masternode because they typically offer guaranteed uptime, redundancy in the case of hardware failure and a static IP address that is required to ensure you remain in the masternode payment queue. While running a masternode from home on a desktop computer is technically possible, it will most likely not work reliably because most ISPs allocate dynamic IP addresses to home users.

We will use Vultr hosting as an example of a VPS, although DigitalOcean, Amazon EC2, Google Cloud, Choopa and OVH are also popular choices. First create an account and add credit. Then go to the Servers menu item on the left and click + to add a new server. Select a location for your new server on the following screen:

Vultr server location selection screen

Select Ubuntu 18.04 x64 as the server type. We use this LTS release of Ubuntu instead of the latest version because LTS releases are supported with security updates for 5 years, instead of the usual 9 months.

Vultr server type selection screen

Select a server size offering at least 2GB of memory.

Vultr server size selection screen

Enter a hostname and label for your server. In this example we will use dashmn1 as the hostname.

Vultr server hostname & label selection screen

Vultr will now install your server. This process may take a few minutes.

Vultr server installation screen

Click Manage when installation is complete and take note of the IP address, username and password.

Vultr server management screen

Set up your operating system¶

We will begin by connecting to your newly provisioned server. On Windows, we will first download an app called PuTTY to connect to the server. Go to the PuTTY download page and select the appropriate MSI installer for your system. On Mac or Linux you can ssh directly from the terminal - simply type ssh root@<server_ip> and enter your password when prompted.

PuTTY download page

Double-click the downloaded file to install PuTTY, then run the app from your Start menu. Enter the IP address of the server in the Host Name field and click Open. You may see a certificate warning, since this is the first time you are connecting to this server. You can safely click Yes to trust this server in the future.

PuTTY security alert when connecting to a new server

You are now connected to your server and should see a terminal window. Begin by logging in to your server with the user root and password supplied by your hosting provider.

Password challenge when connecting to your VPS for the first time

You should immediately change the root password and store it in a safe place for security. You can copy and paste any of the following commands by selecting them in your browser, pressing Ctrl + C, then switching to the PuTTY window and right-clicking in the window. The text will paste at the current cursor location:

passwd root

Enter and confirm a new password (preferably long and randomly generated). Next we will create a new user with the following command, replacing <username> with a username of your choice:

adduser <username>

You will be prompted for a password. Enter and confirm using a new password (different to your root password) and store it in a safe place. You will also see prompts for user information, but this can be left blank. Once the user has been created, we will add them to the sudo group so they can perform commands as root:

usermod -aG sudo <username>

Now, while still as root, we will update the system from the Ubuntu package repository:

apt update
apt upgrade

The system will show a list of upgradable packages. Press Y and Enter to install the packages. We will now install a firewall (and some other packages we will use later), add swap memory and reboot the server to apply any necessary kernel updates, and then login to our newly secured environment as the new user:

apt install ufw python virtualenv git unzip pv

(press Y and Enter to confirm)

ufw allow ssh/tcp
ufw limit ssh/tcp
ufw allow 9999/tcp
ufw logging on
ufw enable

(press Y and Enter to confirm)

fallocate -l 4G /swapfile
chmod 600 /swapfile
mkswap /swapfile
swapon /swapfile
nano /etc/fstab

Add the following line at the end of the file (press tab to separate each word/number), then press Ctrl + X to close the editor, then Y and Enter save the file.

/swapfile none swap sw 0 0

Finally, in order to prevent brute force password hacking attacks, we will install fail2ban and disable root login over ssh. These steps are optional, but highly recommended. Start with fail2ban:

apt install fail2ban

Create a new configuration file:

nano /etc/fail2ban/jail.local

And paste in the following configuration:

[sshd]
enabled = true
port = 22
filter = sshd
logpath = /var/log/auth.log
maxretry = 3

Then press Ctrl + X to close the editor, then Y and Enter save the file. Retart and enable the fail2ban service:

systemctl restart fail2ban
systemctl enable fail2ban

Next, open the SSH configuration file to disable root login over SSH:

nano /etc/ssh/sshd_config

Locate the line that reads PermitRootLogin yes and set it to PermitRootLogin no. Directly below this, add a line which reads AllowUsers <username>, replacing <username> with the username you selected above. Then press Ctrl + X to close the editor, then Y and Enter save the file.

Then reboot the server:

reboot now

PuTTY will disconnect when the server reboots.

While this setup includes basic steps to protect your server against attacks, much more can be done. In particular, authenticating with a public key instead of a username/password combination and enabling automatic security updates is advisable. More tips are available here. However, since the masternode does not actually store the keys to any Dash, these steps are considered beyond the scope of this guide.

Send the collateral¶

A Dash address with a single unspent transaction output (UTXO) of exactly 1000 DASH is required to operate a masternode. Once it has been sent, various keys regarding the transaction must be extracted for later entry in a configuration file and registration transaction as proof to write the configuration to the blockchain so the masternode can be included in the deterministic list. A masternode can be registered from a hardware wallet or the official Dash Core wallet, although a hardware wallet is highly recommended to enhance security and protect yourself against hacking. This guide will describe the steps for both hardware wallets and Dash Core.

Option 1: Sending from a hardware wallet¶

Set up your Trezor using the Trezor wallet at https://wallet.trezor.io/ and send a test transaction to verify that it is working properly. For help on this, see this guide - you may also choose to (carefully!) add a passphrase to your Trezor to further protect your collateral. Create a new account in your Trezor wallet by clicking Add account. Then click the Receive tab and send exactly 1000 DASH to the address displayed. If you are setting up multiple masternodes, send 1000 DASH to consecutive addresses within the same new account. You should see the transaction as soon as the first confirmation arrives, usually within a few minutes.

Trezor Wallet Receive tab showing successfully received collateral of 1000 DASH

Once the transaction appears, click the QR code on the right to view the transaction on the blockchain. Keep this window open as we complete the following steps, since we will soon need to confirm that 15 confirmations exist, as shown in the following screenshot.

Trezor blockchain explorer showing 15 confirmations for collateral transfer

While we are waiting for 15 confirmations, download the latest version of the Dash Masternode Tool (DMT) from the GitHub releases page here. Unzip and run the file. The following window appears.

Dash Masternode Tool startup screen

Click the third button from the left Check Dash Network Connection in the top left corner of the main window to verify that the connection is working. Then connect your Trezor device and click the next button Test Hardware Wallet Connection to verify the Trezor connection is working.

Dash Masternode Tool successful connection confirmations

We will now use DMT to enter some basic information about the masternode and extract the transaction ID. Carry out the following sequence of steps as shown in this screenshot:

Dash Masternode Tool configuration steps

Click the New button.
Enter a name for your masternode. The host name you specified for your VPS above is a good choice.
Enter the IP address of your masternode. This was given to you by the VPS provider when you set up the server. Then enter the TCP port number. This should be 9999.
Click Locate collateral to view unused collateral funding transactions available on the connected hardware wallet. Select the address to which you sent 1000 Dash and click Apply. The Collateral address, path, Collateral TX hash and index fields should be filled automatically.

Dash Masternode Tool with masternode configuration

Leave DMT open and continue with the next step: installing Dash Core on your VPS.

Option 2: Sending from Dash Core wallet¶

Open Dash Core wallet and wait for it to synchronize with the network. It should look like this when ready:

Fully synchronized Dash Core wallet

Click Tools > Debug console to open the console. Type the following command into the console to generate a new Dash address for the collateral:

getnewaddress
yiFfzbwiN9oneftd7cEfr3kQLRwQ4kp7ue

Take note of the collateral address, since we will need it later. The next step is to secure your wallet (if you have not already done so). First, encrypt the wallet by selecting Settings > Encrypt wallet. You should use a strong, new password that you have never used somewhere else. Take note of your password and store it somewhere safe or you will be permanently locked out of your wallet and lose access to your funds. Next, back up your wallet file by selecting File > Backup Wallet. Save the file to a secure location physically separate to your computer, since this will be the only way you can access our funds if anything happens to your computer. For more details on these steps, see here.

Now send exactly 1000 DASH in a single transaction to the new address you generated in the previous step. This may be sent from another wallet, or from funds already held in your current wallet. Once the transaction is complete, view the transaction in a blockchain explorer by searching for the address. You will need 15 confirmations before you can register the masternode, but you can continue with the next step at this point already: generating your masternode operator key.

Trezor blockchain explorer showing 15 confirmations for collateral transfer

Install Dash Core¶

Dash Core is the software behind both the Dash Core GUI wallet and Dash masternodes. If not displaying a GUI, it runs as a daemon on your VPS (dashd), controlled by a simple command interface (dash-cli).

Open PuTTY or a console again and connect using the username and password you just created for your new, non-root user. There are two options to install Dash Core, an automated option using a script utility called dashman, and a more complicated option which will allow you to understand all of the key steps involved in preparing your masternode.

Option 1: Automated installation using dashman¶

To install Dash using dashman, enter the following commands after logging in:

cd ~
git clone https://github.com/moocowmoo/dashman
~/dashman/dashman install

(press Y and Enter to confirm)

dashman will download the latest version of Dash Core for your system, as well as an initial snapshot of the blockchain to speed up the bootstrapping process. Next download and install Sentinel, which is required for masternodes at version 0.12.1 or higher:

~/dashman/dashman install sentinel

Your system is now running as a standard Dash node, and is busy completing synchronisation with the blockchain. Since dashman does not automatically restart your masternode in the event of a system error, add a check function to crontab to make sure it checks every minute to ensure your masternode is still running:

crontab -e

Choose nano as your editor and enter the following line at the end of the file, after the line for sentinel:

* * * * * { pidof dashd || ~/.dashcore/dashd;} >/dev/null 2>&1

Press enter to make sure there is a blank line at the end of the file, then press Ctrl + X to close the editor and Y and Enter save the file. Check the sync status and wait until all blockchain synchronisation and the 15 confirmations for the collateral transaction are complete:

~/dashman/dashman status

dashman status output showing masternode ready to be registered

Continue with the next step to register your masternode.

Option 2: Manual installation¶

To manually download and install the components of your Dash masternode, visit the GitHub releases page and copy the link to the latest x86_64-linux-gnu version. Go back to your terminal window and enter the following command, pasting in the address to the latest version of Dash Core by right clicking or pressing Ctrl + V:

cd /tmp
wget https://github.com/dashpay/dash/releases/download/v0.15.0.0/dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz

Verify the integrity of your download by running the following command and comparing the output against the value for the file as shown in the SHA256SUMS.asc file:

wget https://github.com/dashpay/dash/releases/download/v0.15.0.0/SHA256SUMS.asc
sha256sum dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz
cat SHA256SUMS.asc

You can also optionally verify the authenticity of your download as an official release by Dash Core Team. All releases of Dash are signed using GPG by Alexander Block (codablock) with the key 63A9 6B40 6102 E091, verifiable here on Keybase. Import the key, download the ASC file for the current release of Dash and verify the signature as follows:

curl https://keybase.io/codablock/pgp_keys.asc | gpg --import
gpg --verify SHA256SUMS.asc

Downloading the PGP key and verifying the signed binary

Create a working directory for Dash, extract the compressed archive and copy the necessary files to the directory:

mkdir ~/.dashcore
tar xfv dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz
cp -f dashcore-0.15.0/bin/dashd ~/.dashcore/
cp -f dashcore-0.15.0/bin/dash-cli ~/.dashcore/

Create a configuration file using the following command:

nano ~/.dashcore/dash.conf

An editor window will appear. We now need to create a configuration file specifying several variables. Copy and paste the following text to get started, then replace the variables specific to your configuration as follows:

#----
rpcuser=XXXXXXXXXXXXX
rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
rpcallowip=127.0.0.1
#----
listen=1
server=1
daemon=1
#----
#masternode=1
#masternodeblsprivkey=
externalip=XXX.XXX.XXX.XXX
#----

Replace the fields marked with XXXXXXX as follows:

rpcuser: enter any string of numbers or letters, no special characters allowed
rpcpassword: enter any string of numbers or letters, no special characters allowed
externalip: this is the IP address of your VPS

Leave the masternode and masternodeblsprivkey fields commented out for now. The result should look something like this:

Entering key data in dash.conf on the masternode

Press Ctrl + X to close the editor and Y and Enter save the file. You can now start running Dash on the masternode to begin synchronization with the blockchain:

~/.dashcore/dashd

You will see a message reading Dash Core server starting. We will now install Sentinel, a piece of software which operates as a watchdog to communicate to the network that your node is working properly:

cd ~/.dashcore
git clone https://github.com/dashpay/sentinel.git
cd sentinel
virtualenv venv
venv/bin/pip install -r requirements.txt
venv/bin/python bin/sentinel.py

You will see a message reading dashd not synced with network! Awaiting full sync before running Sentinel. Add dashd and sentinel to crontab to make sure it runs every minute to check on your masternode:

crontab -e

Choose nano as your editor and enter the following lines at the end of the file:

* * * * * cd ~/.dashcore/sentinel && ./venv/bin/python bin/sentinel.py 2>&1 >> sentinel-cron.log
* * * * * pidof dashd || ~/.dashcore/dashd

Press enter to make sure there is a blank line at the end of the file, then press Ctrl + X to close the editor and Y and Enter save the file. We now need to wait for 15 confirmations of the collateral transaction to complete, and wait for the blockchain to finish synchronizing on the masternode. You can use the following commands to monitor progress:

~/.dashcore/dash-cli mnsync status

When synchronisation is complete, you should see the following response:

{
  "AssetID": 999,
  "AssetName": "MASTERNODE_SYNC_FINISHED",
  "AssetStartTime": 1558596597,
  "Attempt": 0,
  "IsBlockchainSynced": true,
  "IsSynced": true,
  "IsFailed": false
}

Continue with the next step to construct the ProTx transaction required to enable your masternode.

Register your masternode¶

DIP003 introduced several changes to how a masternode is set up and operated. These changes and the three keys required for the different masternode roles are described briefly under DIP003 Masternode Changes in this documentation.

Option 1: Registering from a hardware wallet¶

Go back to DMT and ensure that all fields from the previous step are still filled out correctly. Click Generate new for the three private keys required for a DIP003 deterministic masternode:

Owner private key
Operator private key
Voting private key

Dash Masternode Tool ready to register a new masternode

Then click Register masternode. Optionally specify a different Payout address and/or Operator reward, then click Continue. Select Remote Dash RPC Node (automatic method). (See here for documentation on using your own local RPC node.) and confirm the following two messages:

Dash Masternode Tool confirmation dialogs to register a masternode

The BLS private key must be entered in the dash.conf file on the masternode. This allows the masternode to watch the blockchain for relevant Pro*Tx transactions, and will cause it to start serving as a masternode when the signed ProRegTx is broadcast by the owner, as we just did above. Log in to your masternode using ssh or PuTTY and edit the configuration file as follows:

nano ~/.dashcore/dash.conf

The editor appears with the existing masternode configuration. Add or uncomment these lines in the file, replacing the key with your BLS private key generated above:

masternode=1
masternodeblsprivkey=24c1fa3c22c6ea6b1cc68a37be18acb51042b19465fe0a26301c8717bf939805

Press enter to make sure there is a blank line at the end of the file, then press Ctrl + X to close the editor and Y and Enter save the file. We now need to restart the masternode for this change to take effect. Enter the following commands, waiting a few seconds in between to give Dash Core time to shut down:

~/.dashcore/dash-cli stop
sleep 15
~/.dashcore/dashd

At this point you can monitor your masternode using ~/dashman/dashman status, by entering ~/.dashcore/dash-cli masternode status or using the Get status function in DMT. The final result should appear as follows:

dash-cli masternode status output showing successfully registered masternode

At this point you can safely log out of your server by typing exit. Congratulations! Your masternode is now running.

Option 2: Registering from Dash Core wallet¶

Identify the funding transaction¶

If you used an address in Dash Core wallet for your collateral transaction, you now need to find the txid of the transaction. Click Tools > Debug console and enter the following command:

masternode outputs

This should return a string of characters similar to the following:

{
"16347a28f4e5edf39f4dceac60e2327931a25fdee1fb4b94b63eeacf0d5879e3" : "1",
}

The first long string is your collateralHash, while the last number is the collateralIndex.

Generate a BLS key pair¶

A public/private BLS key pair is required to operate a masternode. The private key is specified on the masternode itself, and allows it to be included in the deterministic masternode list once a provider registration transaction with the corresponding public key has been created.

If you are using a hosting service, they may provide you with their public key, and you can skip this step. If you are hosting your own masternode or have agreed to provide your host with the BLS private key, generate a BLS public/private keypair in Dash Core by clicking Tools > Debug console and entering the following command:

bls generate

{
  "secret": "395555d67d884364f9e37e7e1b29536519b74af2e5ff7b62122e62c2fffab35e",
  "public": "99f20ed1538e28259ff80044982372519a2e6e4cdedb01c96f8f22e755b2b3124fbeebdf6de3587189cf44b3c6e7670e"
}

These keys are NOT stored by the wallet and must be kept secure, similar to the value provided in the past by the masternode genkey command.

Add the private key to your masternode configuration¶

The public key will be used in following steps. The private key must be entered in the dash.conf file on the masternode. This allows the masternode to watch the blockchain for relevant Pro*Tx transactions, and will cause it to start serving as a masternode when the signed ProRegTx is broadcast by the owner (final step below). Log in to your masternode using ssh or PuTTY and edit the configuration file as follows:

nano ~/.dashcore/dash.conf

The editor appears with the existing masternode configuration. Add or uncomment these lines in the file, replacing the key with your BLS private key generated above:

masternode=1
masternodeblsprivkey=395555d67d884364f9e37e7e1b29536519b74af2e5ff7b62122e62c2fffab35e

Press enter to make sure there is a blank line at the end of the file, then press Ctrl + X to close the editor and Y and Enter save the file. We now need to restart the masternode for this change to take effect. Enter the following commands, waiting a few seconds in between to give Dash Core time to shut down:

~/.dashcore/dash-cli stop
sleep 15
~/.dashcore/dashd

We will now prepare the transaction used to register the masternode on the network.

Prepare a ProRegTx transaction¶

A pair of BLS keys for the operator were already generated above, and the private key was entered on the masternode. The public key is used in this transaction as the operatorPubKey.

First, we need to get a new, unused address from the wallet to serve as the owner key address (ownerKeyAddr). This is not the same as the collateral address holding 1000 Dash. Generate a new address as follows:

getnewaddress

yfgxFhqrdDG15ZWKJAN6dQvn6dZdgBPAip

This address can also be used as the voting key address (votingKeyAddr). Alternatively, you can specify an address provided to you by your chosen voting delegate, or simply generate a new voting key address as follows:

getnewaddress

yfRaZN8c3Erpqj9iKnmQ9QDBeUuRhWV3Mg

Then either generate or choose an existing address to receive the owner’s masternode payouts (payoutAddress). It is also possible to use an address external to the wallet:

getnewaddress

yjZVt49WsQd6XSrPVAUGXtJccxviH9ZQpN

You can also optionally generate and fund another address as the transaction fee source (feeSourceAddress). If you selected an external payout address, you must specify a fee source address. Either the payout address or fee source address must have enough balance to pay the transaction fee, or the final register_submit transaction will fail.

The private keys to the owner and fee source addresses must exist in the wallet submitting the transaction to the network. If your wallet is protected by a password, it must now be unlocked to perform the following commands. Unlock your wallet for 5 minutes:

walletpassphrase yourSecretPassword 300

We will now prepare an unsigned ProRegTx special transaction using the protx register_prepare command. This command has the following syntax:

protx register_prepare collateralHash collateralIndex ipAndPort ownerKeyAddr
  operatorPubKey votingKeyAddr operatorReward payoutAddress (feeSourceAddress)

Open a text editor such as notepad to prepare this command. Replace each argument to the command as follows:

collateralHash: The txid of the 1000 Dash collateral funding transaction
collateralIndex: The output index of the 1000 Dash funding transaction
ipAndPort: Masternode IP address and port, in the format x.x.x.x:yyyy
ownerKeyAddr: The new Dash address generated above for the owner/voting address
operatorPubKey: The BLS public key generated above (or provided by your hosting service)
votingKeyAddr: The new Dash address generated above, or the address of a delegate, used for proposal voting
operatorReward: The percentage of the block reward allocated to the operator as payment
payoutAddress: A new or existing Dash address to receive the owner’s masternode rewards
feeSourceAddress: An (optional) address used to fund ProTx fee. payoutAddress will be used if not specified.

Note that the operator is responsible for specifying their own reward address in a separate update_service transaction if you specify a non-zero operatorReward. The owner of the masternode collateral does not specify the operator’s payout address.

Example (remove line breaks if copying):

protx register_prepare
  16347a28f4e5edf39f4dceac60e2327931a25fdee1fb4b94b63eeacf0d5879e3
  1
  45.76.230.239:19999
  yfgxFhqrdDG15ZWKJAN6dQvn6dZdgBPAip
  99f20ed1538e28259ff80044982372519a2e6e4cdedb01c96f8f22e755b2b3124fbeebdf6de3587189cf44b3c6e7670e
  yfRaZN8c3Erpqj9iKnmQ9QDBeUuRhWV3Mg
  0
  yjZVt49WsQd6XSrPVAUGXtJccxviH9ZQpN
  yR83WsikBaBaNusTnHZf28kAcL8oVmp1TE

Output:

{
  "tx": "030001000175c9d23c2710798ef0788e6a4d609460586a20e91a15f2097f56fc6e007c4f8e0000000000feffffff01a1949800000000001976a91434b09363474b14d02739a327fe76e6ea12deecad88ac00000000d1010000000000e379580dcfea3eb6944bfbe1de5fa2317932e260acce4d9ff3ede5f4287a34160100000000000000000000000000ffff2d4ce6ef4e1fd47babdb9092489c82426623299dde76b9c72d9799f20ed1538e28259ff80044982372519a2e6e4cdedb01c96f8f22e755b2b3124fbeebdf6de3587189cf44b3c6e7670ed1935246865dce1accce6c8691c8466bd67ebf1200001976a914fef33f56f709ba6b08d073932f925afedaa3700488acfdb281e134504145b5f8c7bd7b47fd241f3b7ea1f97ebf382249f601a0187f5300",
  "collateralAddress": "yjSPYvgUiAQ9AFj5tKFA8thFLoLBUxQERb",
  "signMessage": "yjZVt49WsQd6XSrPVAUGXtJccxviH9ZQpN|0|yfgxFhqrdDG15ZWKJAN6dQvn6dZdgBPAip|yfRaZN8c3Erpqj9iKnmQ9QDBeUuRhWV3Mg|ad5f82257bd00a5a1cb5da1a44a6eb8899cf096d3748d68b8ea6d6b10046a28e"
}

Next we will use the collateralAddress and signMessage fields to sign the transaction, and the output of the tx field to submit the transaction.

Sign the ProRegTx transaction¶

We will now sign the content of the signMessage field using the private key for the collateral address as specified in collateralAddress. Note that no internet connection is required for this step, meaning that the wallet can remain disconnected from the internet in cold storage to sign the message. In this example we will again use Dash Core, but it is equally possible to use the signing function of a hardware wallet. The command takes the following syntax:

signmessage collateralAddress signMessage

Example:

signmessage yjSPYvgUiAQ9AFj5tKFA8thFLoLBUxQERb yjZVt49WsQd6XSrPVAUGXtJccxviH9ZQpN|0|yfgxFhqrdDG15ZWKJAN6dQvn6dZdgBPAip|yfRaZN8c3Erpqj9iKnmQ9QDBeUuRhWV3Mg|ad5f82257bd00a5a1cb5da1a44a6eb8899cf096d3748d68b8ea6d6b10046a28e

Output:

II8JvEBMj6I3Ws8wqxh0bXVds6Ny+7h5HAQhqmd5r/0lWBCpsxMJHJT3KBcZ23oUZtsa6gjgISf+a8GzJg1BfEg=

Submit the signed message¶

We will now submit the ProRegTx special transaction to the blockchain to register the masternode. This command must be sent from a Dash Core wallet holding a balance on either the feeSourceAddress or payoutAddress, since a standard transaction fee is involved. The command takes the following syntax:

protx register_submit tx sig

Where:

tx: The serialized transaction previously returned in the tx output field from the protx register_prepare command
sig: The message signed with the collateral key from the signmessage command

Example:

protx register_submit 030001000175c9d23c2710798ef0788e6a4d609460586a20e91a15f2097f56fc6e007c4f8e0000000000feffffff01a1949800000000001976a91434b09363474b14d02739a327fe76e6ea12deecad88ac00000000d1010000000000e379580dcfea3eb6944bfbe1de5fa2317932e260acce4d9ff3ede5f4287a34160100000000000000000000000000ffff2d4ce6ef4e1fd47babdb9092489c82426623299dde76b9c72d9799f20ed1538e28259ff80044982372519a2e6e4cdedb01c96f8f22e755b2b3124fbeebdf6de3587189cf44b3c6e7670ed1935246865dce1accce6c8691c8466bd67ebf1200001976a914fef33f56f709ba6b08d073932f925afedaa3700488acfdb281e134504145b5f8c7bd7b47fd241f3b7ea1f97ebf382249f601a0187f5300 II8JvEBMj6I3Ws8wqxh0bXVds6Ny+7h5HAQhqmd5r/0lWBCpsxMJHJT3KBcZ23oUZtsa6gjgISf+a8GzJg1BfEg=

Output:

aba8c22f8992d78fd4ff0c94cb19a5c30e62e7587ee43d5285296a4e6e5af062

Your masternode is now registered and will appear on the Deterministic Masternode List after the transaction is mined to a block. You can view this list on the Masternodes -> DIP3 Masternodes tab of the Dash Core wallet, or in the console using the command protx list valid, where the txid of the final protx register_submit transaction identifies your masternode.

At this point you can go back to your terminal window and monitor your masternode using ~/dashman/dashman status, by entering ~/.dashcore/dash-cli masternode status or using the Get status function in DMT. The final result should appear as follows:

dashman status output showing successfully registered masternode

At this point you can safely log out of your server by typing exit. Congratulations! Your masternode is now running.

Maintenance¶

Masternodes require regular maintenance to ensure you do not drop off the payment queue. This includes promptly installing updates to Dash, as well as maintaining the security and performance of the server. In addition, masternodes should vote on proposals and perform other tasks in the interest of the network and the value of the Dash they hold.

Masternode Software Update¶

The Dash Core software requires regular updates in order to remain consistent with the current network consensus. Depending on whether you installed Dash manually or using dashman, you must follow the procedure appropriate for your masternode, as described below.

Option 1: Updating from dashman¶

To update Dash using dashman, log in to your server and enter the following commands:

~/dashman/dashman sync update -y

Check the status of your masternode:

~/dashman/dashman status

The Dash software on the masternode is now updated.

Option 2: Manual update¶

To update Dash manually, log in to your server using ssh or PuTTY. If your crontab contains an entry to automatically restart dashd, invoke crontab -e and comment out the appropriate line by adding the # character. It should look something like this:

# * * * * * pidof dashd || ~/.dashcore/dashd

Then stop Dash running:

~/.dashcore/dash-cli stop

Visit the GitHub releases page and copy the link to the latest x86_64-linux-gnu version. Go back to your terminal window and enter the following command, pasting in the address to the latest version of Dash Core by right clicking or pressing Ctrl + V:

cd /tmp
wget https://github.com/dashpay/dash/releases/download/v0.15.0.0/dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz

Verify the integrity of your download by running the following command and comparing the output against the value for the file as shown in the SHA256SUMS.asc file:

sha256sum dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz

Extract the compressed archive and copy the new files to the directory:

tar xfv dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz
cp -f dashcore-0.15.0/bin/dashd ~/.dashcore/
cp -f dashcore-0.15.0/bin/dash-cli ~/.dashcore/

Restart Dash:

~/.dashcore/dashd

You will see a message reading «Dash Core server starting». We will now update Sentinel:

cd ~/.dashcore/sentinel/
git checkout master
git pull

Finally, uncomment the line to automatically restart Dash in your crontab by invoking crontab -e again and deleting the # character.

The Dash software on the masternode is now updated.

Updating Masternode Information¶

Periodically, it may be necessary to update masternode information if any information relating to the owner or operator changes. Examples may include a change in IP address, change in owner/operator payout address or changes to the nominated voting/operator keys. It is also possible to revoke a masternode’s registered status (in the event of a security breach, for example) to force both owner and operator to update their details.

Configuration changes which affect the provision of service to the network, such as the BLS operator key and IP address, will reset your position in the payment queue. Changes to the voting or various payout addresses will not reset your position in the payment queue.

ProUpServTx¶

A Provider Update Service Transaction (ProUpServTx) is used to update information relating to the operator. An operator can update the IP address and port fields of a masternode entry. If a non-zero operatorReward was set in the initial ProRegTx, the operator may also set the operatorPayoutAddress field in the ProUpServTx. If operatorPayoutAddress is not set and operatorReward is non-zero, the owner gets the full masternode reward. A ProUpServTx can be created from DMT by clicking the Update service button, or from Dash Core using the following syntax:

protx update_service proTxHash ipAndPort operatorKey (operatorPayoutAddress feeSourceAddress)

Where:

proTxHash: The hash of the initial ProRegTx
ipAndPort: IP and port in the form «ip:port»
operatorKey: The operator BLS private key associated with the registered operator public key
operatorPayoutAddress (optional): The address used for operator reward payments. Only allowed when the ProRegTx had a non-zero operatorReward value. Enter "" to use the last on-chain operator payout address.
feeSourceAddress (optional): An address used to fund ProTx fee. operatorPayoutAddress will be used if not specified.

Example:

protx update_service d6ec9a03e1251ac8c34178f47b6d763dc4ea6d96fd6eddb3c7aae2359e0f474a 140.82.59.51:10002 4308daa8de099d3d5f81694f6b618381e04311b9e0345b4f8b025392c33b0696 yf6Cj6VcCfDxU5yweAT3NKKvm278rVbkhu

fad61c5f21cf3c0832f782c1444d3d2e2a8dbff39c5925c38033730e64ecc598

The masternode is now removed from the PoSe-banned list, and the IP:port and operator reward addresses are updated.

ProUpRegTx¶

A Provider Update Registrar Transaction (ProUpRegTx) is used to update information relating to the owner. An owner can update the operator’s BLS public key (e.g. to nominate a new operator), the voting address and their own payout address. A ProUpRegTx can be created from DMT by clicking the Update operator key, Update voting key or Update payout addr. buttons, or from Dash Core using the following syntax:

protx update_registrar proTxHash operatorKeyAddr votingKeyAddr payoutAddress (feeSourceAddress)

Where:

proTxHash: The transaction id of the initial ProRegTx
operatorKeyAddr: An updated BLS public key, or "" to use the last on-chain operator key
votingKeyAddr: An updated voting key address, or "" to use the last on-chain voting key
payoutAddress: An updated Dash address for owner payments, or "" to use the last on-chain operator key
feeSourceAddress (optional): An address used to fund ProTx fee. PayoutAddress will be used if not specified.

Example to update payout address:

protx update_registrar cedce432ebabc9366f5eb1e3abc219558de9fbd2530a13589b698e4bf917b8ae "" "" yi5kVoPQQ8xaVoriytJFzpvKomAQxg6zea

ProUpRevTx¶

A Provider Update Revocation Transaction (ProUpRevTx) is used by the operator to terminate service or signal the owner that a new BLS key is required. It will immediately put the masternode in the PoSe-banned state. The owner must then issue a ProUpRegTx to set a new operator key. After the ProUpRegTx is mined to a block, the new operator must issue a ProUpServTx to update the service-related metadata and clear the PoSe- banned state (revive the masternode). A ProUpRevTx can be created from DMT by clicking the Revoke operator button, or from Dash Core using the following syntax:

protx revoke proTxHash operatorKey reason (feeSourceAddress)

Where:

proTxHash: The transaction id of the initial ProRegTx
operatorKey: The operator BLS private key associated with the registered operator public key
reason: Integer value indicating the revocation reason
feeSourceAddress (optional): An address used to fund ProTx fee. operatorPayoutAddress will be used if not specified.

Example:

protx revoke 9f5ec7540baeefc4b7581d88d236792851f26b4b754684a31ee35d09bdfb7fb6 565950700d7bdc6a9dbc9963920bc756551b02de6e4711eff9ba6d4af59c0101 0

Proof of Service Bans¶

If your masternode fails to provide service to the network in accordance with the current consensus rules, it will receive a Proof of Service Ban. If your masternode is in the POSE_BANNED status, you should check the following settings are configured correctly:

Ensure you are running the latest version of Dash
Ensure your masternode has sufficient memory, swap, processing power and hard drive space
Ensure you are fully synced to the correct blockheight, and that you are on the correct chain and not forked off
Ensure that a BLS private key is specified using the masternodeblsprivkey option in the masternode’s dash.conf file
Ensure that the BLS private key on the masternode is unique on the network and not shared with any other masternodes
Ensure that the BLS private key on the masternode corresponds to the BLS public key registered on the blockchain in the ProRegTx or ProUpRegTx
Ensure that the externalip (and port if using testnet) are specified correctly and not blocked by a firewall or port forwarding service
Ensure that Sentinel is installed, updated, not exiting with an error and is entered in your crontab to run every 1-2 minutes

Once you are certain these settings are correct, you can update your service status on the network and return to the valid set of masternodes by creating a ProUpServTx. Monitor your masternode closely using masternode status and/or the debug.log file after restoring service. This information can help you pinpoint the specific misconfiguration that is causing the masternode to be banned. The masternode will be banned again if it continues to fail to provide service.

DashCentral voting, verification and monitoring¶

DashCentral is a community-supported website managed by community member Rango. It has become a de facto site for discussion of budget proposals and to facilitate voting from a graphical user interface, but also offers functions to monitor masternodes.

Adding your masternode to DashCentral¶

Dashcentral allows you to vote on proposals from the comfort of your browser. After completing registration, go to the masternodes page and click the Add masternode now button. Enter your collateral address on the following screen:

_images/maintenance-dc-add-masternode.png

Adding a masternode to DashCentral

Click Add masternode. Your masternode has now been added to DashCentral.

Enabling voting from DashCentral¶

Click Edit under Voting privkeys to enter your masternode private key to enable voting through the DashCentral web interface. Enter a voting passphrase (not the same as your login password, but equally important to remember!) and enter the private key (the same key you used in the dash.conf file on your masternode) on the following screen:

Adding voting privkeys to DashCentral

It is important to note that the private key to start your masternode is unrelated to the private keys to the collateral address storing your 1000 DASH. These keys can be used to issue commands on behalf of the masternode, such as voting, but cannot be used to access the collateral. The keys are encrypted on your device and never stored as plain text on DashCentral servers. Once you have entered the key, click Store encrypted voting privkeys on server. You can now vote on proposals from the DashCentral web interface.

Verifying ownership¶

You can also issue a message from your address to verify ownership of your masternode to DashCentral. Click Unverified under Ownership and the following screen will appear:

Verifying ownership of your masternode to DashCentral

Instructions on how to sign your collateral address using a software wallet appear. If you are using a hardware wallet other than Trezor, you will need to use the DMT app to sign the address. If you are using the Trezor hardware wallet, go to your Trezor wallet, copy the collateral address and click Sign & Verify. The following screen will appear, where you can enter the message provided by DashCentral and the address you wish to sign:

Signing a message from the Trezor Wallet

Click Sign, confirm on your Trezor device and enter your PIN to sign the message. A message signature will appear in the Signature box. Copy this signature and paste it into the box on DashCentral and click Verify ownership. Verification is now complete.

Masternode ownership has been successfully verified

Installing the DashCentral monitoring script¶

DashCentral offers a service to monitor your masternode, automatically restart dashd in the event of a crash and send email in the event of an error. Go to the Account settings page and generate a new API key, adding a PIN to your account if necessary. Scroll to the following screen:

Setting up the DashCentral monitoring script

Copy the link to the current version of the dashcentral script by right- click and selecting Copy link address. Open PuTTY and connect to your masternode, then type:

wget https://www.dashcentral.org/downloads/dashcentral-updater-v6.tgz

Replace the link with the current version of dashcentral-updater as necessary. Decompress the archive using the following command:

tar xvzf dashcentral-updater-v6.tgz

View your masternode configuration details by typing:

cat .dashcore/dash.conf

Copy the values for rpcuser and rpcpassword. Then edit the dashcentral configuration by typing:

nano dashcentral-updater/dashcentral.conf

Replace the values for api_key, your masternode collateral address, rpc_user, rpc_password, daemon_binary and daemon_datadir according to your system. A common configuration, where lwhite is the name of the Linux user, may look like this:

_images/maintenance-dc-update-config.png

DashCentral updater configuration file

################
# dashcentral-updater configuration
################

our %settings = (
    # Enter your DashCentral api key here
    'api_key' => 'api_key_from_dashcentral'
);

our %masternodes = (
    'masternode_collateral_address' => {
        'rpc_host'           => 'localhost',
        'rpc_port'           => 9998,
        'rpc_user'           => 'rpc_user_from_dash.conf',
        'rpc_password'       => 'rpc_password_from_dash.conf',
        'daemon_autorestart' => 'enabled',
        'daemon_binary'      => '/home/<username>/.dashcore/dashd',
        'daemon_datadir'     => '/home/<username>/.dashcore'
    }
);

Press Ctrl + X to exit, confirm you want save with Y and press Enter. Test your configuration by running the dashcentral script, then check the website. If it was successful, you will see that an update has been sent:

dashcentral-updater/dcupdater

Manually testing the DashCentral updater

DashCentral updater has successfully sent data to the DashCentral site

Once you have verified your configuration is working, we can edit the crontab on your system to schedule the dcupdater script to run every 2 minutes. This allows the system to give you early warning in the event of a fault and will even restart the dashd daemon if it hangs or crashes. This is an effective way to make sure you do not drop off the payment queue. Type the following command:

crontab -e

Select an editor if necessary and add the following line to your crontab after the line for sentinel, replacing lwhite with your username on your system:

*/2 * * * * /home/lwhite/dashcentral-updater/dcupdater

Editing crontab to run the DashCentral updater automatically

Press Ctrl + X to exit, confirm you want save with Y and press Enter. The dcupdater script will now run every two minutes, restart dashd whenever necessary and email you in the event of an error.

Masternode monitoring tools¶

Several sites operated by community members are available to monitor key information and statistics relating to the masternode network.

Block Explorers¶

Since Dash is a public blockchain, it is possible to use block explorers to view the balances of any Dash public address, as well as examine the transactions entered in any given block. Each unique transaction is also searchable by its txid. A number of block explorers are available for the Dash network.

Blockchair offers a block explorer with detailed visualizations to analyse the Dash blockchain.
CryptoID offers a Dash blockchain explorer and a function to view and map Dash masternodes.
BitInfoCharts offers a page of price statistics and information and a blockchain explorer.
CoinCheckup offers a range of statistics and data on most blockchains, including Dash.
CoinPayments offers a simple Dash blockchain explorer.
Dash.org includes two blockchain explorers at explorer.dash.org and insight.dash.org.
Trezor operates a blockchain explorer powered by a Dash fork of insight, an advanced blockchain API tool

Dash Masternode Tool¶

https://github.com/Bertrand256/dash-masternode-tool

Written and maintained by community member Bertrand256, Dash Masternode Tool (DMT) allows you to start a masternode from all major hardware wallets such as Trezor, Ledger and KeepKey. It also supports functions to vote on proposals and withdraw masternode payments without affecting the collateral transaction.

DASH Ninja¶

https://www.dashninja.pl

DASH Ninja, operated by forum member and Dash Core developer elbereth, offers key statistics on the adoption of different versions of Dash across the masternode network. Several features to monitor governance of the Dash, the masternode payment schedule and the geographic distribution of masternodes are also available, as well as a simple blockchain explorer.

DashCentral¶

https://www.dashcentral.org

DashCentral, operated by forum member rango, offers an advanced service to monitor masternodes and vote on budget proposals through an advanced web interface. An Android app is also available.

Masternode.me¶

https://stats.masternode.me

Masternode.me, operated by Dash community member moocowmoo, offers sequential reports on the price, generation rate, blockchain information and some information on masternodes.

Dash Masternode Information¶

http://178.254.23.111/~pub/Dash/Dash_Info.html

This site, operated by forum member and Dash Core developer crowning, offers a visual representation of many key statistics of the Dash masternode network, including graphs of the total masternode count over time, price information and network distribution.

Advanced Topics¶

Installing Dash on Fedora Linux¶

Dash developer t0dd has developed packages and written an excellent guide on installing and running Dash as a node, masternode or on testnet.

https://github.com/taw00/dashcore-rpm

Installing Dash on Ubuntu Linux¶

Dash binaries are under development for distribution through the Ubuntu Linux Launchpad repository system. Check back here for details once a release announcement is made.

Mining¶

Mining in the context of cryptocurrency such as Dash refers to the process of searching for solutions to cryptographically difficult problems as a method of securing blocks on the blockchain. The process of mining creates new currency tokens as a reward to the miner. Mining is possible on a range of hardware. Dash implements an algorithm known as X11, which the miner must solve in order to earn rewards.

The simplest and most general hardware available for mining is the general purpose CPU present in every computer. A CPU is designed to be versatile but offers less efficiency than a GPU, which is designed to rapidly calculate millions of vectors in parallel. While specific CPU instruction enhancements related to cryptography such as AES or AVX can provide a decent boost, GPUs offer a significant performance increase due to their multiple pipelines capable of processing the predictably repetitive calculations associated with cryptocurrency mining. Finally, ASICs are relatively inflexible and can only process the specific function(s) for which they were designed, but at an even faster rate than the more general purpose GPUs and CPUs. A number of X11 ASICs are now available on the market, which have quickly made CPU and GPU mining uneconomic due to the increased difficulty of hashing arising from the rapidly increasing hash rate. The result is a currency which is more secure against brute force attacks on the Dash blockchain.

The profitability of mining is determined by the hashrate of your mining device, the current network difficulty and the costs of your hardware and electricity. The following links provide up to date information:

Minerar vs. Masternode¶

Dash, como Bitcoin e a maioria das outras criptomoedas, é baseado em um livro de contabilidade descentralizado de todas as transações, conhecido como um blockchain. Este blockchain é protegido através de um mecanismo de consenso; no caso tanto o Dash e o Bitcoin, o mecanismo de consenso é prova de trabalho (PoW). Mineradores tentam resolver problemas difíceis com computadores especializados, e quando eles resolvem o problema, que recebem o direito de adicionar um novo bloco para o blockchain. Se todas as outras pessoas que executam o software concordam que o problema foi resolvido corretamente, o bloco é adicionado para o blockchain e o minerador é recompensado.

Dash funciona um pouco diferente do Bitcoin, no entanto, porque ele tem uma rede de duas camadas. A segunda camada é alimentada por masternodes (Full Nodes), que permitem privacidade financeira (PrivateSend), transações instantâneas (InstantSend) e o sistema de governança e orçamento descentralizado. Porque este segundo nível é tão importante, masternodes também são recompensados quando os mineradores descobre novos blocos. A repartição é a seguinte: 45% da recompensa de bloco vai para o minerador, 45% vai para o masternodes, e 10% é reservado para o sistema de orçamento (criado por superblocos todos os meses).

O sistema masternode é referido como Prova de Serviço (PoSe), uma vez que os masternodes fornecem serviços cruciais para a rede. De fato, toda a rede é supervisionada pelos masternodes, que têm o poder de rejeitar os blocos mal formados dos mineiros. Se um mineiro tentasse levar a recompensa do bloco inteiro para si ou tentasse executar uma versão antiga do software Dash, a rede masternode ficaria órfã desse bloco, e não seria adicionado ao blockchain.

Em suma, os mineradores tem poder a primeira camada, que é o básico de envio e o recebimento de fundos e prevenção de doublespending. Masternodes tem poder da segunda camada, que fornecem os recursos adicionais que tornam a Dash diferente de outros criptomoedas. E computadores de mineração não podem servir como masternodes. Além disso, cada masternode é «protegido» por 1000 DASH. Essas DASH permaneçam sob o controle exclusivo de seu proprietário em todos os momentos e ainda pode ser gasto livremente. Os fundos não são bloqueados de forma alguma. No entanto, se os fundos são movidos ou gasto, o dono do masternode vai ficar off-line e parar de receber recompensas.

Mining Pools¶

Mining Dash in pools is more likely to generate rewards than solo mining directly on the blockchain. Mining dash using P2Pool is strongly encouraged, since it is a good way to distribute, rather than centralize, the hashing power. The following site lists Dash P2Pool mining pools near you, simply choose a pool with favourable fees and ping time and enter your Dash payment address as username and anything as password.

http://www.p2poolmining.us/p2poolnodes/

If you would like to set up your own P2Pool, documentation of the process is available here and the code for p2pool-dash is available on GitHub.

Other pools are also available and may be advantageous for different reasons such as ping latency, uptime, fee, users, etc.:

DISCLAIMER: This list is provided for informational purposes only. Services listed here have not been evaluated or endorsed by the Dash developers and no guarantees are made as to the accuracy of this information. Please exercise discretion when using third-party services. If you’d like to be added to this list please reach out to leon.white@dash.org

In addition to joining a pool, you will also need to create a Dash address to receive your payout. To do this in Dash Core wallet, see here.

Dash P2Pool Node Setup¶

This guide describes how to set up a Dash P2Pool node to manage a pool of miners. Unlike centralized mining pools, P2Pool is based on the same peer-2-peer (P2P) model as Dash, making the pool as a whole highly resistant to malicious attacks, and preserving and protecting the decentralized nature of Dash. When you launch a P2Pool node, it seeks out, connects with, and shares data with a decentralized network of other P2Pool nodes (also known as peers). P2Pool nodes share a cryptographic chain of data representing value, similar to Dash’s blockchain. The P2Pool version is called the sharechain. The decentralized and fair nature of this mining model means mining with P2Pool is strongly encouraged. P2Pool for Dash uses the p2pool-dash software on GitHub, which is a fork of p2pool for Bitcoin. For more information, see here.

Because of the way P2Pool manages difficulty adjustments on the sharechain, it is important to maintain low latency between the miners and the P2Pool node to avoid miners submitting shares too late to enter the sharechain. When setting up your node, you need to consider its physical and network location relative to the miners you intend to connect to the node. If you operate a mining farm, your P2Pool node should probably be a physical machine on the same local network as your miners. If you plan to operate a public node, it may be best to set up your P2Pool node as a virtual machine in a data center with a high speed connection so geographically close miners can mine to your pool with relatively low latency.

This following section describes the steps to setup an Ubuntu Server running P2Pool for Dash. It has been tested with Ubuntu 18.04 LTS and Dash 0.13.1.0. While a reasonable effort will be made to keep it up to date, it should be possible to modify the instructions slightly to support different versions or operating systems as necessary.

Setting up the host server¶

Download a copy of Ubuntu Server LTS from https://www.ubuntu.com/download/server and install it on your system according to the steps described here. If you are using a VPS such as Vultr or AWS, your provider will most likely provide an option to install this system during provisioning. Ensure you enable OpenSSH server during setup so you can control your server from a remote console. Once you have access to your server, create a new non-root user if you have not already done so using the following command, replacing <username> with a username of your choice:

adduser <username>

You will be prompted for a password. Enter and confirm using a new password (different to your root password) and store it in a safe place. You will also see prompts for user information, but this can be left blank. Once the user has been created, we will add them to the sudo group so they can perform commands as root:

usermod -aG sudo <username>

Reboot your server and log in as the new user. At this point it is recommended to connect remotely using PuTTY (for Windows) or ssh (for Linux and macOS) if you have not already done so.

Setting up port forwarding¶

If you are on a private network behind a router, you will need to set up port forwarding for at least port 8999 (UDP/TCP) for access to the sharechain, as well as port 7903 (UDP/TCP) if you want your node to be accessible to the public. How this is done depends on your particular network router and is therefore beyond the scope of this documentation. An example from the popular DD-WRT open source router distribution is shown below. Guides to setting up port forwarding can be found here and here.

Take note of your IP address either from your router management interface or by visiting https://www.whatismyip.com

Setting up port forwarding under DD-WRT

Option 1: Automated script setup¶

Dash community member dracocephalum has generously donated a script to automatically deploy everything required to run a p2pool-dash node under Ubuntu Server 16.04 and higher. For more details, see this forum post, or simply follow these instructions to get the script. To get fetch the script and get started, type:

sudo apt install git
git clone https://github.com/strophy/p2pool-dash-deploy

The files will be created in the p2pool-dash-deploy folder. We now need to configure a few variables specific to your system:

nano ./p2pool-dash-deploy/p2pool.deploy.sh

Scroll down to the section labeled #Variables and enter the following information, replacing the <xxx> placeholders after the = sign. Note that it may also be necessary to update the DASH_WALLET_URL, DASH_WALLET_ZIP and DASH_WALLET_LOCAL values if they do not match the current version of Dash:

PUBLIC_IP = your public IP address from the previous step
EMAIL = your email address
PAYOUT_ADDRESS = your DASH wallet address to receive fees
USER_NAME = linux user name
RPCUSER = enter a random alphanumeric rpc user name
RPCPASSWORD = enter a random alphanumeric rpc password

Press Ctrl + X to close the editor and Y and Enter save the file. Then run the script:

bash ./p2pool-dash-deploy/p2pool.deploy.sh

The script will carry out all steps necessary to set up P2pool on Ubuntu Server and start dashd synchronisation. When setup is complete, you should see a message reading Installation Completed. You can now run a second script to start p2pool-dash:

bash ~/p2pool.start.sh

Your P2Pool node is now running. If you see errors similar to Error getting work from dashd or -10 Dash Core is downloading blocks… then you must wait until Dash finishes synchronisation. Once this is done, you can point your miners to <ip_address>:7903 to begin mining.

Example configuration showing a single Bitmain Antminer D3 connected to a p2pool-dash node on the local network

Option 2: Manual setup¶

First update your operating system as follows:

sudo apt update
sudo apt upgrade

Setting up dashd¶

P2Pool requires a full Dash node to be running to get block and transaction data. To download and install Dash, visit https://www.dash.org/downloads on your computer to find the link to the latest Dash Core wallet. Click Linux, then right-click on Download TGZ for Dash Core x64 and select Copy link address. Go back to your terminal window and enter the following command, pasting in the address to the latest version of Dash Core by right clicking or pressing Ctrl + V:

cd ~
wget https://github.com/dashpay/dash/releases/download/v0.15.0.0/dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz

Verify the integrity of your download by running the following command and comparing the output against the value for the file as shown on the Dash website under Hash File:

sha256sum dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz

Link to the hash file to verify download integrity

Create a working directory for Dash, extract the compressed archive, copy the necessary files to the directory and set them as executable:

mkdir .dashcore
tar xfvz dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz
cp dashcore-0.15.0/bin/dashd .dashcore/
cp dashcore-0.15.0/bin/dash-cli .dashcore/

Clean up unneeded files:

rm dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz
rm -r dashcore-0.15.0/

Create a configuration file using the following command:

nano ~/.dashcore/dash.conf

An editor window will appear. We now need to create a configuration file specifying several variables. Copy and paste the following text to get started, then replace the variables specific to your configuration as follows:

#----
rpcuser=XXXXXXXXXXXXX
rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
rpcallowip=127.0.0.1
#----
listen=1
server=1
daemon=1
maxconnections=64
#----

Replace the fields marked with XXXXXXX as follows:

rpcuser: enter any string of numbers or letters, no special characters allowed
rpcpassword: enter any string of numbers or letters, no special characters allowed

The result should look something like this:

Entering key data in dash.conf on the P2Pool node

Press Ctrl + X to close the editor and Y and Enter save the file. You can now start running Dash on the masternode to begin synchronization with the blockchain:

~/.dashcore/dashd

You will see a message reading Dash Core server starting. You can continue with the following steps and check synchronization periodically using the following command. Synchronization is complete when the number of blocks is equal to the current number of blocks in the Dash blockchain, as can be seen from any synchronized Dash wallet or block explorer:

~/.dashcore/dash-cli getblockcount

Setting up P2Pool¶

We will now set up the P2Pool software and its dependencies. Begin with the dependencies:

sudo apt install python-zope.interface python-twisted python-twisted-web python-dev gcc g++ git

Create working directories and set up p2pool-dash:

mkdir git
cd git
git clone https://github.com/dashpay/p2pool-dash
cd p2pool-dash
git submodule init
git submodule update
cd dash_hash
python setup.py install --user

We will add some optional extra interfaces to the control panel:

cd ..
mv web-static web-static.old
git clone https://github.com/justino/p2pool-ui-punchy web-static
mv web-static.old web-static/legacy
cd web-static
git clone https://github.com/hardcpp/P2PoolExtendedFrontEnd ext

You can now start p2pool and optionally specify the payout address, external IP (if necessary), fee and donation as follows:

python ~/git/p2pool-dash/run_p2pool.py --external-ip <public_ip> -f <fee> --give-author <donation> -a <payout_address>

You can then monitor your node by browsing to the following addresses, replacing <ip_address> with the IP address of your P2Pool node:

Punchy interface: http://ip_address:7903/static
Legacy interface: http://ip_address:7903/static/legacy
Status interface: http://ip_address:7903/static/status
Extended interface: http://ip_address:7903/static/ext

Example configuration showing a single Bitmain Antminer D3 connected to a p2pool-dash node on the local network

CPU Mining¶

This documentation describes how to mine Dash under the Windows operating system using just the CPU in your computer. Please note that the prevalence of GPU and ASIC miners mean that unless you have free electricity, this is highly unlikely to be profitable! Since this is the case, the software in this guide has not been updated in several years, and is intended for experimental purposes and testnet only.

This is a fairly simple procedure and examples will be given in order to achieve the fastest possible hash rate for your CPU, but remember that more optimized miners do exist, so we advise you to keep an eye out on mining sites such as these in order to keep up with the latest information and releases.

Mining software¶

The first step is to download appropriate mining software. A good basic miner for modern CPUs can be found here:

https://github.com/elmad/darkcoin-cpuminer-1.3-avx-aes

This software depends on your CPU supporting the AES-NI and AVX instruction sets. You can use CPU-Z to check if this is the case for your CPU:

CPU-Z showing details for an Intel i7 Haswell CPU

If your CPU does not support AES-NI and AVX, then you can try more generalized software which does not require specific instruction sets, such as these:

Our goal here is to choose mining software that supports the maximum possible instruction sets available on your CPU, and then try to increase the hash speed. Once you have made your choice, click Releases and download and extract the zip file. The different *.exe files indicate which specific processor optimizations they support. The folder should look something like this:

Executable CPU miners for Dash

Configuração¶

Begin by selecting a mining pool and generating a Dash address as described in the Mining Pools section above. Keep all your mining files in a single folder. In this example we will work from the Desktop. The node selected for this example is from the p2poolming.us list and is located in China:

http://118.184.180.43:7903/static/

Next, open Notepad and type in on one line the command we will use to start the miner, followed by pause on the second line. The general format is as follows:

<minerd> -a <algorithm> -o <url> -u <username> -p <password> -t <threads>
pause

Where:

minerd = the executable miner daemon file you choose to use
a = algorithm, which is X11 for Dash
o = URL of your mining pool, including the protocol and port
u = username, usually the Dash receiving address of your wallet or worker
p = password, can often be set to x
t = number of threads used
pause = keeps the window open in the case of errors

For the CPU in the example above, the command may be:

minerd-avx-aes-sse2-sss3.exe -a X11 -o stratum+tcp://118.184.180.43:7903 -u XwZRjo1f6gmq3LCv7X1Hi5h3NkvDMHvu8G -p x -t 8
pause

Notepad file showing an example command to start a CPU miner

Click File, then Save As. Change Save as type to All Files, then type the file name as startminer.bat and save it in the same folder as the unzipped minerd files.

Testing¶

You are now ready to start! Keep an eye on your CPU usage in Task Manager (right click the taskbar to open this) and be careful that the CPU temperature does not exceed your maximum rating (around 64°C). If you have temperature or desktop stability problems, reduce t to ~2 threads and try that first. If t is left out, the machine will default to the maximum number of threads. After running the miner for a while, take a look at the hash speed and payouts in your mining pool. You can identify your miner by the wallet address on the page.

Example of CPU mining using DarkCoin CPUMiner 1.3 on Intel Core i7

Tips¶

Reduce the number of threads for added desktop usability and heat reduction. If the CPU temperature is too high, consider fitting a new fan and check that the heat sink thermal paste on the CPU is adequate. Tweak the processor clock speed for added performance using a motherboard controller like AI Suite for Asus motherboards. Reduction of CPU core voltage will result in lower temperature but increased instability.

Try to select a pool that is nearby to reduce network latency. If the node appears slow, switch to another location. Please distribute the hashing power globally to different pools to avoid forking.

GPU Mining¶

This guide consolidates several other guides on how to use your GPU (the processor on your graphics card) to mine Dash using the X11 algorithm on Windows. Please note that the growing market for ASIC miners means that this if probably not going to be profitable! A lot of the software and binaries described here also have not been updated for several years, so this guide should be used for experimental purposes only.

This guide will cover the process of downloading and configuring the mining software, followed by some suggestions for optimizations. This technology can change rapidly, so we advise you to keep an eye out on mining sites such as these in order to keep up with the latest information and releases.

Mining software¶

As for CPU mining, a range of mining software is available for GPU mining. Most of it based on sgminer compiled with different optimizations specific to different hardware. A good approach is to identify your graphics hardware, then choose an appropriate build of sgminer. You can use GPU-Z to identify your GPU hardware:

GPU-Z showing details for AMD Radeon Turks and NVIDIA Quadro GK104 class GPUs

Next, download the mining software. Most of these are based on the original sgminer, but this is not suitable for the X11 algorithm, offers no compiled binaries and hasn’t been updated in years. We will describe using pre-compiled binary software maintained by newer developers only.

AMD

https://github.com/nicehash/sgminer/releases

NVIDIA

https://github.com/tpruvot/ccminer/releases (focus on core application)
https://github.com/sp-hash/ccminer/releases (sp-mod, optimized CUDA kernels for Windows)
https://github.com/KlausT/ccminer/releases (similar to SP version, more clean)

Download your chosen release and extract the zip file to a known location. The folder should look something like this:

Executable GPU miners for Dash

The sgminer file is the executable file, while the various files with .cl extensions define the various algorithms supported by sgminer. In this case, we are interested in the darkcoin.cl and darkcoin-mod.cl implementations of X11. Note that the name of the executable file may be different for miners with different optimizations, for example ccminer for NVIDIA cards.

Configuração¶

Begin by selecting a mining pool and generating a Dash address as described in the Mining Pools section above. Keep all your mining files in a single folder. In this example we will work from the Desktop. The node selected for this example is from the p2poolming.us list and is located in China:

http://118.184.180.43:7903/static/

Next, open Notepad and create the basic configuration. The general format is as follows:

{
  "pools" : [
    {
      "url" : "stratum+tcp://pooladdress:7903",
      "user" : "walletaddress",
      "pass" : "x",
      "algorithm":"darkcoin"
    }
  ]
}

Where:

pools = defines a list of pools (in this case, only one) towards which the hashing power is directed
url = URL of your mining pool, including the protocol and port
user = username, usually the Dash receiving address of your wallet or worker
pass = password, can often be set to x
algorithm = hashing algorithm to use, in this case darkcoin (for historic reasons) or darkcoin-mod

For the pool above, the configuration may be:

Configuration file for a Dash GPU miner

Click File, then Save As. Change Save as type to All Files, then type the file name as sgminer.conf and save it in the same folder as the unzipped sgminer files.

Testing¶

Double click your sgminer.exe and a Command Prompt window should appear immediately. If it disappears too quickly, check your configuration for missing commas, unclosed brackets or incorrect file name. The program will compile a special binary specific to your GPU and store it in the folder, then begin hashing.

Example of GPU mining using sgminer 5.6.1-nicehash-51 on Intel HD Graphics 4600

ASIC Mining¶

ASIC stands for Application-Specific Integrated Circuit and describes a type of processor that is designed for one purpose only. ASICs are a popular choice for mining cryptocurrency because they can offer a higher efficiency than CPU or GPU miners, resulting in higher profit.

Please note that the information on this page may become obsolete very quickly due to the rapidly changing market and difficulty of mining Dash. You are responsible for carrying out your own research and any listing on this page should not be considered an endorsement of any particular product. A good place to begin your research is the mining section of the Dash Forums.

The following X11 ASIC miners are available on the market today, click the product name to visit the manufacturer’s website:

Nome	Hash rate	Power	Weight	Dimensions (mm)	Price
Bitmain Antminer D5	119 GH/s ±5%	1566 W	7.5 kg	486 x 265 x 388	$1,180
iBelink DM56G	56 GH/s ±5%	2100 W	17 kg	490 x 390 x 180	$1,800
Innosilicon A5	32 GH/s ±8%	750 W	3.1 kg	400 x 135 x 158	$990
Spondoolies SPx36	540 GH/s ±10%	4400 W	19.5 kg	640 X 525 X 185	$7,000

The following ASIC miners are either no longer easily available or obsolete due to the increase in difficulty on the network.

Nome	Hash rate	Power	Weight	Dimensions (mm)
Baikal BK-X	10 GH/s ±5%	800 W	3.8 kg	312 x 125 x 130
Baikal Mini	150 MH/s ±10%	40 W	.475 kg	140 x 100 x 95
Baikal Giant+ A2000	2000 MH/s ±10%	430 W	3 kg	300 x 140 x 125
Baikal Giant A900	900 MH/s ±5%	217 W	2.5 kg	300 x 123 x 123
Baikal Quad Cube	1200 MH/s ±10%	300 W	3 kg	135 x 135 x 425
Bitmain Antminer D3	17 GH/s ±5%	970 W	6.5 kg	320 x 130 x 190
iBelink DM384M	384 MH/s ±10%	715 W	21 kg	490 x 350 x 180
iBelink DM11G	11 GH/s ±5%	810 W	22 kg	490 x 350 x 180
iBelink DM22G	22 GH/s ±5%	810 W	19 kg	490 x 350 x 180
Pinidea DR-1	500 MH/s ±10%	320 W	4.5 kg	290 x 130 x 150
Pinidea DR-2	450 MH/s ±5%	335 W	4.5 kg	200 x 165 x 135
Pinidea DR-3	600 MH/s ±5%	345 W	4.5 kg	200 x 165 x 135
Pinidea DU-1	9 MH/s ±5%	7 W		50 x 50 x 30
Pinidea DRX-Kuznetsov	900 MH/s ±5%	650 W		280 x 180 x 150
Pinidea DRX-Varyag	1200 MH/s ±5%	850 W		280 x 180 x 150

Desenvolvedores¶

O Dash Core publicou um extenso Guia do desenvolvedor para ajudar os novos desenvolvedores a começarem com a base de códigos do Dash e como uma referência para desenvolvedores experientes. Este guia pode ser aproveitado para integrar de forma rápida e eficiente aplicativos externos ao ecossistema Dash. Qualquer pessoa pode contribuir com o guia enviando um problema ou solicitando solicitação no GitHub. A documentação está disponível em: https://dash-docs.github.io/en/

A Equipe Core do Dash também mantém o Roadmap do Dash, que define marcos de entrega para versões futuras do Dash e inclui detalhes técnicos específicos que descrevem como a equipe de desenvolvimento planeja realizar cada desafio. O Roteiro do Dash é complementado pelo Dash propostas de melhoria, que contêm explicações técnicas detalhadas das alterações propostas para o protocolo Dash.

As seções restantes disponíveis abaixo descrevem as etapas práticas para executar tarefas comuns de desenvolvimento no Dash.

Integration Overview¶

This documentation is also available as a PDF.

Dash Core is a “fork” of Bitcoin Core and shares many common functionalities. Key differences relate to existing JSON-RPC commands which have been customized to support unique functionalities such as InstantSend.

General Information: Dash is a “Proof of Work” network and is similar to Bitcoin.
1. Block Time: ~2.6 Minutes per Block
2. Github Source: https://github.com/dashpay/dash
3. Latest Release: https://github.com/dashpay/dash/releases
JSON-RPC Interface: The majority of commands are unchanged from Bitcoin making integration into existing systems relatively straightforward. Note that the following commands have been modified to support InstantSend:
Block Hashing Algorithm: Dash uses the “X11” algorithm in place of SHA256 used in Bitcoin. It’s important to note, however, that this only affects the hashing of the Block itself. All other internals utilize SHA256 hashes (transactions, merkle root, etc) which allows for most existing libraries to work in the Dash ecosystem.
Special Transactions: Dash Core v0.13.x introduces the concept of “Special Transactions”. Please see the Transaction Type Integration Guide for more information.

Special Transactions¶

This documentation is also available as a PDF.

Dash 0.13.0 and higher implement DIP002 Special Transactions, which form a basis for new transaction types that provide on-chain metadata to assist various consensus mechanisms. The following special transaction types exist:

Release	Version	Type	Payload Size	Payload	Payload JSON	Transaction Purpose
v0.13.0	3	0	n/a	n/a	n/a	Standard Transaction
v0.13.0	3	1	<variable int>	<hex>	proRegTx	Masternode Registration
v0.13.0	3	2	<variable int>	<hex>	proUpServTx	Update Masternode Service
v0.13.0	3	3	<variable int>	<hex>	proUpRegTx	Update Masternode Operator
v0.13.0	3	4	<variable int>	<hex>	proUpRevTx	Masternode Revocation
v0.13.0	3	5	<variable int>	<hex>	cbTx	Masternode List Merkle Proof
v0.13.0	3	6	<variable int>	<hex>	qcTx	Quorum Commitment

Integration notes:

DIP002 Special Transactions are a foundational component of Dash Core v0.13.0 and introduce a new Transaction Version and related “Payload” to the network.
Integrated Systems must be able to serialize and deserialize these new Transaction Types in order to accurately encode and decode Raw Transaction data.
From a backwards compatibility perspective, the 4 byte (32-bit) version field included in Legacy Transactions has been split into two fields: version and type (each consisting of 2 bytes).
Refer to the Special Transactions section of the dash developer reference for additional detail on these data types, e.g. <variable int>.
InstantSend status and Payload JSON (e.g. proRegTx) is included in the JSON-RPC response, please note that this data is not part of the calculated hash and is provided for convenience.

See the v0.13.0 transaction types integration documentation (PDF) for worked examples of each transaction type.

InstantSend¶

This documentation is also available as a PDF.

InstantSend is a feature provided by the Dash network that allows for zero-confirmation transactions to be safely accepted and re-spent. The network attempts to lock the inputs of every valid transaction when it is broadcast to the network. Every secured transaction is included in a following block in accordance with standard blockchain principles.

InstantSend is enabled by the Masternode Network which comprises approximately 5,000 masternode servers. These nodes are differentiated from standard nodes by having proven ownership of 1,000 Dash, making the network highly resistant to Sybil attacks. Masternodes form Long-Living Masternode Quorums (LLMQs), which are responsible for providing near instant certainty to the transaction participants that the transaction inputs cannot be respent, and that the transaction will be included in a following block instead of a conflicting transaction.

This concept works as an extension to Nakamoto Consensus. InstantSend enables transacted funds to be immediately and securely respent by the recipient, even before the transaction is included in a block.

Receiving InstantSend Transactions¶

Receiving an InstantSend Transaction introduces two requirements:

The ability to determine the “InstantSend Status” of a given transaction.
The ability to adjust “Confirmation Status” independently of block confirmation.

InstantSend Status is typically determined through direct connection with the dash daemon, ZMQ notification, or through the usage of an external wallet notification script.

Direct Connection: InstantSend Status can be identified through direct connection with the Dash daemon using JSON-RPC protocol. The “instantlock” attribute of the JSON response reflects the status of the transaction and is included in the following commands:

ZMQ Notification: Whenever a transaction enters the mempool and whenever a transaction is locked in the mempool, ZMQ notifications can be broadcast by the node. A list of possible ZMQ notifications can be found here.

The following notifications are relevant for recognizing transactions and their corresponding instantlocks:

zmqpubhashtx
zmqpubhashtxlock
zmqpubrawtx
zmqpubrawtxlock

Wallet Notification: The Dash Core Daemon can be configured to execute an external script whenever an InstantSend transaction relating to that wallet is observed. This is configured by adding the following line to the dash.conf file:

instantsendnotify=/path/to/concurrent/safe/handler %s

This is typically used with a wallet that has been populated with watch-only addresses.

Broadcasting InstantSend Transactions¶

Since Dash v0.14.0 established LLMQs on the Dash network, quorums will now attempt to lock every valid transaction by default without any additional fee or action by the sending wallet or user. A transaction is eligible for InstantSend when each of its inputs is considered confirmed. This is the case when at least one of the following circumstances is true:

the previous transaction referred to by the input is confirmed with 6 blocks
the previous transaction is confirmed through an older InstantSend lock
the block containing the previous transaction is ChainLocked

When checking the previous transaction for an InstantSend lock, it is important to also do this on mempool (non-mined) transactions. This allows chained InstantSend locking.

Additional Resources¶

The following resources provide additional information about InstantSend and are intended to help provide a more complete understanding of the underlying technologies.

API Services¶

This documentation is also available as a PDF.

Several API services exist to facilitate quick and easy integration with the Dash network for services including:

Transaction broadcasting
Exchange rates
Currency conversion
Invoice generation

API Services are typically leveraged to eliminate that requirement of running your own infrastructure to support blockchain interactions. This includes mechanisms such as:

Forming and Broadcasting a Transaction to the network.
Address generation using HD Wallets.
Payment Processing using WebHooks.

There are a variety of options for supporting these methods, with the key differentiator being the pricing model included and supported features. The following list of API Providers attempts to outline these key features/differentiators and also includes a link to related documentation.

Insight¶

https://github.com/dashevo/insight-api

The open-source Insight REST API provides you with a convenient, powerful and simple way to read data from the Dash network and build your own services with it. A practical guide to getting started with the Insight API and Insight UI block explorer is available here.

Features: Transaction Broadcast, WebSocket Notifications.
Pricing Model: Free / Open Source
Documentation: https://github.com/dashevo/insight-api

BlockCypher¶

https://www.blockcypher.com

BlockCypher is a simple, mostly RESTful JSON API for interacting with blockchains, accessed over HTTP or HTTPS from the api.blockcypher.com domain.

Features: Transaction Broadcast, HD Wallet / Address Generation, WebSocket and WebHook Callbacks as well as Payment Forwarding. BlockCypher does not handle Private Keys.
Pricing Model: Per API Call, 5000 Requests -> $85.00 per month (https://accounts.blockcypher.com/plans)
Documentation: https://www.blockcypher.com/dev/dash/

BitGo¶

https://www.bitgo.com

BitGo provides a simple and robust RESTful API and client SDK to integrate digital currency wallets with your application. Support for Dash InstantSend is available.

Features: Multi-Signature HD Wallets, Wallet Operations, WebSocket and WebHook Notifications, Custody Solutions
Pricing Model: Per API Call
Documentation: https://www.bitgo.com/api/v2/

ChainRider¶

https://www.chainrider.io

ChainRider is a cloud service providing a set of REST APIs for digital currency management and exploration.

Features: Blockchain queries, Event Notifications, Transaction Broadcast, Payment Processing, etc.
Pricing Model: Free trial, pay per API call
Documentation: https://www.chainrider.io/docs/dash

GoCoin¶

https://gocoin.com

The GoCoin platform makes taking Dash as easy as installing a plugin. Payment processing is already implemented for every major shopping platform. GoCoin is focused on helping merchants in privacy-related niches and specific industries, and handles all transaction risk for all payments from your customers.

Features: Invoicing, Exchange Rates, WebHook Callbacks. GoCoin holds Private Keys on their server allowing the merchant to withdraw funds in Cryptocurrency or convert to Fiat.
Integrations: WooCommerce, Magento, Prestashop, VirtueMart, ZenCart, OpenCart, OSCommerce, UberCart, nopCommerce, WHMCS, NATS4, Shopify.
Pricing Model: 1% Processing Fee (https://gocoin.com/fees)
Documentation: https://gocoin.com/docs

CoinPayments¶

https://www.coinpayments.net

CoinPayments is an integrated payment gateway for cryptocurrencies such as Dash. Shopping cart plugins are available for all popular webcarts used today. CoinPayments can help you set up a new checkout, or integrate with your pre-existing checkout.

Features: Invoicing, Exchange Rates, WebHook Callbacks. CoinPayments holds Private Keys on their server allowing merchant to withdraw funds in Cryptocurrency or convert to Fiat.
Integrations: aMember Pro, Arastta, Blesta, BoxBilling, Drupal, Ecwid, Hikashop, Magento, OpenCart, OSCommerce, PrestaShop, Tomato Cart, WooCommerce, Ubercart, XCart, ZenCart
Pricing Model: 0.5% Processing Fee (https://www.coinpayments.net/help-fees)
Documentation: https://www.coinpayments.net/apidoc

SDK Resources¶

This documentation is also available as a PDF.

SDKs (Software Development Kits) are used to accelerate the design and development of a product for the Dash Network. These resources can either be used to interface with an API provider or for the creation of standalone applications by forming transactions and/or performing various wallet functions.

Dash Developer Guide¶

https://dash-docs.github.io/en/developer-guide

The Dash Developer Guide aims to provide the information you need to understand Dash and start building Dash-based applications. To make the best use of this documentation, you may want to install the current version of Dash Core, either from source or from a pre-compiled executable.

Documentation: https://dash-docs.github.io/en/developer-guide

NodeJS/JavaScript: Dashcore¶

https://bitcore.io

Dashcore is a fork of Bitcore and operates as a full Dash node — your apps run directly on the peer-to-peer network. For wallet application development, additional indexes have been added into Dash for querying address balances, transaction history, and unspent outputs.

Platform: NodeJS / Javascript
Documentation: https://bitcore.io/api/lib
Repository lib: https://github.com/dashevo/dashcore-lib
Repository node: https://github.com/dashevo/dashcore-node
See also: Insight API

PHP: Bitcoin-PHP¶

https://github.com/snogcel/bitcoin-php

Bitcoin-PHP is an implementation of Bitcoin with support for Dash using mostly pure PHP.

Platform: PHP
Documentation: https://github.com/Bit-Wasp/bitcoin-php/blob/master/doc/Introduction.md
Repository: https://github.com/snogcel/bitcoin-php

Python: PyCoin¶

https://github.com/DeltaEngine/pycoin

PyCoin is an implementation of a bunch of utility routines that may be useful when dealing with Bitcoin and Dash. It has been tested with Python 2.7, 3.6 and 3.7.

Platform: Python
Documentation: https://pycoin.readthedocs.io/en/latest/
Repository: https://github.com/DeltaEngine/pycoin
See also: JSON-RPC Utilities

Java: DashJ¶

https://github.com/HashEngineering/dashj

DashJ is a library for working with the Dash protocol. It can maintain a wallet, send/receive transactions (including InstantSend) without needing a local copy of Dash Core, and has many other advanced features. It’s implemented in Java but can be used from any JVM compatible language: examples in Python and JavaScript are included.

Platform: Java
Documentation: https://bitcoinj.github.io/getting-started
Repository: https://github.com/HashEngineering/dashj
Example application: https://github.com/tomasz-ludek/pocket-of-dash

Objective-C: Dash-Sync¶

https://github.com/dashevo/dashsync-iOS

Dash-Sync is an Objective-C Dash blockchain framework for iOS. It implements all most relevant Bitcoin Improvement Proposals (BIPs) and Dash Improvement Proposals (DIPs).

Platform: iOS
Repository: https://github.com/dashevo/dashsync-iOS

.NET: NBitcoin¶

https://github.com/MetacoSA/NBitcoin

NBitcoin is the most complete Bitcoin library for the .NET platform, and has been patched to include support for Dash. It implements all most relevant Bitcoin Improvement Proposals (BIPs) and Dash Improvement Proposals (DIPs). It also provides low level access to Dash primitives so you can easily build your application on top of it.

Platform: .NET
Documentation: https://programmingblockchain.gitbooks.io/programmingblockchain/content/
Repository: https://github.com/MetacoSA/NBitcoin
See also: JSON-RPC Utilities

BlockCypher¶

https://www.blockcypher.com

BlockCypher also offers client SDKs.

Platform: Ruby, Python, Java, PHP, Go, NodeJS
Repositories: https://www.blockcypher.com/dev/dash/#blockcypher-supported-language-sdks

GoCoin¶

https://gocoin.com

Platform: JavaScript, PHP, Java, Ruby, .NET, Python
Repositories: https://gocoin.com/docs

Vending Machines¶

Community member moocowmoo has released code to help merchants build their own vending machine and set it up to receive Dash InstantSend payments. The Dashvend software can also be used to create any sort of payment system, including point-of-sale systems, that can accept InstantSend payments.

Price Tickers¶

You can add a simple price ticker widget to your website using the simple code snippet generator from CoinGecko.

Similar widgets with different designs are available from CoinLib, WorldCoinIndex and Cryptonator, while an API providing similar information is available from DashCentral.

QR Codes¶

Many wallets are capable of generating QR codes which can be scanned to simplify entry of the Dash address. Printing these codes or posting the on your website makes it easy to receive payment and tips in Dash, both online and offline.

In Dash Core, go to the Receive tab, generate an address if necessary, and double-click it to display a QR code. Right click on the QR code and select Save Image to save a PNG file.
In Dash for Android, tap Request Coins and then tap the QR code to display a larger image. You can screenshot this to save an image.
In Dash for iOS, swipe to the left to display the Receive Dash screen. A QR code and address will appear. You can screenshot this to save an image.
To generate a QR code from any Dash address, visit CWA QR Code Generator and simply paste your Dash address to generate an image.

Dash 0.13 Upgrade Information¶

Official binaries are available at https://github.com/dashpay/dash/releases/tag/v0.13.3.0

Dash Core v0.13.0 is intended to serve as the foundation for Dash Evolution, a broadly scoped update to our network intended to facilitate and enable new payment methods and technologies. Please see the Dash Core v0.13.0 Product Brief for an overview of new features, and complete this 3 question survey to help us assess the impact of this upgrade. The upgrade will take place in phases, as shown in the following diagram:

Installation notes¶

Dash Core v0.13.0.0 will automatically activate DIP002, DIP003 and DIP004 once 80% of the network has upgraded. Mining pools must mine an upgraded block and pay an upgraded masternode to successfully signal the upgrade in a block, and 80% of blocks in a window must signal in order to lock in the upgrade. Please confirm the status of network uptake before proceeding as the upgrade path differs slightly depending on on your timing.

Activation status can be tracked in the image below or at this site.

http://178.254.23.111/~pub/13_adoption.png

Dash v0.13.0.0 adoption by miners

Masternode upgrade status can be tracked at Dash Ninja
If you are updating to Dash Core v0.13.0.0 prior to this 80% threshold you should be able to simply shut down the daemon and replace it with the updated binary.
If you are updating to Dash Core v0.13.0.0 after this 80% threshold is reached please note that you will need to re-index the chainstate using the “-reindex-chainstate” command.

Dependencies¶

Please note that Dash Core v0.13.0.0 requires a one-time upgrade to all related software and libraries to ensure continued compatibility.

DIP002: Special Transactions contains more information on backwards compatibility.
Please refer to the Transaction Type Integration Guide for information on the implementation of Special Transactions and for examples of this new format.
Contact the Support Desk with any compatibility questions or for help upgrading.

Please see the official Release Notes for a complete listing of RPC improvements, in summary:

Mining: getBlockTemplate now returns an array for masternode payments instead of a single object.
InstantSend: instantlock status is now included in getrawmempool, getmempoolancestors, getmempooldescendants, getmempoolentry, getrawtransaction, decoderawtransaction, gettransaction, listtransactions, listsinceblock.

Libraries and APIs¶

The following lists the current upgrade status for libraries:

Nome	Plataforma	Upgraded?
DashJ	Android
Dash-Sync	iOS	✓
Dashcore-Lib	JavaScript / NodeJS	✓
NBitcoin	.Net	✓
Bitcoin-PHP	PHP
PyCoin	Python	✓

Dash 0.14 Upgrade Information¶

Official binaries are available at https://github.com/dashpay/dash/releases/tag/v0.14.0.5

Dash Core v0.14.0 is intended to serve as the foundation for Dash Evolution, a broadly scoped update to our network intended to facilitate and enable new payment methods and technologies. Please see the Dash Core v0.14.0 Product Brief for an overview of new features. The upgrade will take place in phases, as shown in the following diagram:

Installation notes¶

Dash Core v0.14.0.0 will automatically activate DIP0008 once 80% of the network has upgraded. Mining pools must mine an upgraded block to successfully signal the upgrade in a block, and 80% of blocks in a window must signal in order to lock in the upgrade.

Activation status can be tracked in the image below or at this site.

http://178.254.23.111/~pub/14_adoption.png

Dash v0.14.0.0 adoption by miners

Masternode upgrade status can be tracked at Dash Ninja
If you are updating to Dash Core v0.14.0.0 from version 0.13.x you should be able to simply shut down the daemon and replace it with the updated binary.
If you are updating to Dash Core v0.14.0.0 from version < 0.13 please note that you will also need to re-index the chainstate using the “-reindex-chainstate” command.

Dependencies¶

DIP0006: Long-Living Masternode Quorums contains more information on Long-Living Masternode Quorums.
DIP0007: LLMQ Signing Requests / Sessions contains more information on the signing request / session process that supports the use of LLMQs.
DIP0008: ChainLocks contains more information on ChainLocks.
DIP0010: LLMQ InstantSend contains more information on the updated LLMQ-based InstantSend system.
Please refer to the ChainLocks Integration Guide for information on the implementation of ChainLocks and for examples of this new format.
Contact the Support Desk with any compatibility questions or for help upgrading.

Please see the official Release Notes for a complete listing of RPC improvements, in summary:

ChainLocks: chainlock status is now included in getrawtransaction, decoderawtransaction, gettransaction, listtransactions, listsinceblock. getblock

Translating Dash¶

Translations of all Dash products are managed courtesy of Transifex, which offers its own detailed documentation of all functions and features. Within Transifex, Dash maintains an organization which contains multiple projects and one team of translators assigned to all of the projects. Each project is assigned with one or more target languages for translation by the project maintainer. When a translator joins the team, they are able to choose the languages they feel able to translate. They can then work on any projects specifying this language as a target language.

In general, languages with minimal regional variation are to be translated into the common language (rather than regional) target. Portuguese, for example, is simply translated into the pt target language, rather than two separate target languages pt_BR and pt_PT, for Portuguese as spoken in Brazil and Portugal, respectively. As Dash grows, these languages may be separated out into their regional variants by proofreaders, depending on demand. Exceptions to this rule apply where the same spoken language is written differently, such as zh_CN and zh_TW for Simplified Chinese and Traditional Chinese.

Keeping translations consistent over time as multiple translators work on each target language is a very important part of delivering a quality user experience. For this reason, if you come across any Dash-specific terminology such as masternodes, you should use the Concordance search function to see how the term has been translated in the past. Transifex will also provide Suggestions and History if it recognizes a similar string in the database of past translations. Stay consistent with past language use, but also ensure your terminology is up to date with current use!

The following documentation describes the various projects and any special features specific to the programming language in which the product is written.

Dash Core¶

https://www.transifex.com/dash/dash/

This project contains a file named dash_en.ts, which is an export of all translatable user-facing content in the Dash Core Wallet. Languages with 80% or more of the translations complete will be integrated in the next release. Note that the software will often replace placeholders in the text with actual numbers, addresses or usernames. If you see a placeholder in the source text, it must also appear in the target text. If it does not, your translation cannot be used. The Copy source string button can help you copy everything over, so all you need to do is replace the English words surrounding the placeholders. You can change the order of the placeholders as necessary, according to the grammar of your target language.

Placeholders

Source: E&xit

Target: &Beenden

Note that the & character is placeholder used to indicate a keyboard shortcut in a program menu, and must appear next to the appropriate character in your target language with no adjacent space. Placeholders such as %1 or %s will be replaced by the software as it is running to indicate a name or number of something relating to the message. You must insert these placeholders in the grammatically appropriate position in your target text.

Punctuation

Source: change from %1 (%2)

Target: Wechselgeld von %1 (%2)

Note that any brackets () and punctuation such as full stops . at the end of a sentence must also exist in the target text.

Dash Docs¶

https://www.transifex.com/dash/dash-docs

This project contains all content from the Dash Documentation hosted at https://docs.dash.org (probably the site you are reading now). Each .html page in the documentation appears as a file in the resources section, named according to the navigation steps required to open the page. The Dash Documentation is written in a documentation language called reStructuredText and built using the open-source Sphinx Documentation Generator. To simplify layout, most of the text has no markup or code marks at all, but hyperlinks and certain formatting must be reproduced in the target language as follows:

Inline literals

Source: Type ``./dash-qt`` to run the file.

Target: Escriba ``./dash-qt`` para correr el archivo.

Note that two backticks `` before and after a word or phrase will cause that text to appear as an inline literal. This is commonly used to highlight code or commands to be typed by the user.

Bold and italic

Source: To encrypt your wallet, click **Settings** > **Encrypt** wallet.

Target: Para encriptar su billetera, haga click en **Settings** > **Encrypt** billetera.

A single * before and after a word or phrase will render it in an italic font, while a double ** will render it in bold.

Internal hyperlinks

Source: See :ref:`here <sporks>` for a brief introduction to sporks.

Target: Ver :ref:`aquí <sporks>` para una breve introducción a sporks

An internal hyperlink consists of the phrase :ref:, followed by a single backtick `, followed by some text which must be translated, followed by angle brackets with the link target < >, followed by another backtick `. Translate the text, but do not translate the text inside the angle brackets.

External hyperlinks

Source: The `official Dash website <https://www.dash.org>`_ also provides a list of major exchanges offering Dash.

Target: El `sitio web oficial de Dash <https://www.dash.org>`_ también proporciona una lista de las principales Casas de cambio o Exchanges que ofrecen Dash.

An external hyperlink consists of a single backtick `, followed by some text which must be translated, followed by angle brackets with the link target < >, followed by another backtick and a single or double underscore: `_ or `__. Translate the text, but do not translate the hyperlink (unless you want to link to a version of the page in the target language).

Dash Graphics¶

https://www.transifex.com/dash/dash-graphics

Dash visual products such as infographics, flyers and conference handouts are produced using Adobe InDesign, Adobe Illustrator or Microsoft Word and are available for use in the Marketing section of the Dash Documentation. It is important to view the finished English layout during translation in order to understand the context of the text you are translating. For example, many words should be translated differently depending if they are a heading, a sentence or an item in a diagram.

Because these proprietary file formats are not easily handled by Transifex, the language content is exported to a text or Microsoft Excel file and uploaded to Transifex for processing. If you translate Dash Graphics, please send an email to leon.white@dash.org or @strophy on Discord when you are finished to request layout in the visual design.

Carteira Dash iOS¶

https://www.transifex.com/dash/dash-ios-wallet

All language content from the Dash iOS Wallet are available for translation in this project. Please have a device running the iOS wallet available during translation to understand the context of the text you are translating. Note that any placeholders in the source text segment must also appear in the target language, similar to the instructions above for Dash Core Wallet.

Carteira Dash Android¶

https://www.transifex.com/dash/dash-wallet

All language content from the Dash Android Wallet are available for translation in this project. Please have a device running the Android wallet available during translation to understand the context of the text you are translating. Note that any placeholders in the source text segment must also appear in the target language, similar to the instructions above for Dash Core Wallet.

Dash Videos¶

https://www.transifex.com/dash/dash-videos

This section primarily contains language content from Amanda B. Johnson’s popular Dash School video series. Please translate with the videos open in YouTube to properly understand the context of the source text. Once your translation is complete, please send an email to leon.white@dash.org or @strophy on Discord to request inclusion of the subtitles on YouTube.

Dash Website¶

https://www.transifex.com/dash/dash-website

The Dash website at https://www.dash.org is available for translation in Transifex. Please have the website open while you translate to correctly understand the context of the source text. Once your translation is complete, please send an email to leon.white@dash.org or @strophy on Discord to request a build of your translation onto the website.

Compilando Dash Core¶

While Dash offers stable binary builds on the website and on GitHub, and development builds using GitLab CI, many users will also be interested in building Dash binaries for themselves. This process has been greatly simplified with the release of Dash Core 0.13.0, and users who do not required deterministic builds can typically follow the generic build notes available on GitHub to compile or cross-compile Dash for any platform.

The instructions to build Dash Core 0.12.3 or older are available here on a previous version of this page.

Gitian¶

Gitian is the deterministic build process that is used to build the Dash Core executables. It provides a way to be reasonably sure that the executables are really built from the source on GitHub. It also makes sure that the same, tested dependencies are used and statically built into the executable. Multiple developers build the source code by following a specific descriptor («recipe»), cryptographically sign the result, and upload the resulting signature. These results are compared and only if they match, the build is accepted and uploaded to dash.org.

Instructions on how to build Dash Core 0.13.0 will appear here once the Docker build system for Gitian is available. Instructions to create deterministic builds of Dash Core 0.12.3 or older are available here on a previous version of this page.

Testnet and devnets¶

Testnet is a fully functioning Dash blockchain with the one key exception that because the Dash on the network can be created freely, it has no value. This currency, known as tDASH, can be requested from a faucet to help developers test new versions of Dash, as well as test network operations using identical versions of the software before they are carried out on the mainnet. There are a few other key differences:

Testnet operates on port 19999 (instead of 9999)
Testnet addresses start with «y» instead of «X», ADDRESSVERSION is 140 (instead of 76)
Testnet balances are denominated in tDASH (instead of DASH)
Protocol message header bytes are 0xcee2caff (instead of 0xbf0c6bbd)
Bootstrapping uses different DNS seeds: test.dnsseed.masternode.io, testnet-seed.darkcoin.qa, testnet-seed.dashpay.io
Launching Dash Core in testnet mode shows an orange splash screen

To start Dash Core in testnet mode, find your dash.conf file and enter the following line:

testnet = 1

With the release of Dash Core 12.3, Dash added support for a great new feature — named devnets. Devnets are developer networks that combine some aspects of testnet (the global and public testing network) and some aspects of regtest (the local-only regression testing mode that provides controlled block generation). Unlike testnet, multiple independent devnets can be created and coexist without interference. For practical documentation on how to use devnets, see the developer documentation or this blog post.

Tools and links¶

The links below were collected from various community sources and may not necessarily be online or functioning at any given time. Please join Dash Nation Discord or the Dash Forum if you have a question relating to a specific service.

Test builds: https://gitlab.com/dashpay/dash/pipelines
Bugtracker: https://github.com/dashpay/dash/issues/new
Discussion and help: https://www.dash.org/forum/topic/testing.53/
Masternode tools: https://test.dashninja.pl/masternodes.html
Android wallet: https://www.dash.org/forum/threads/dash-wallet-for-android-v5-testnet.14775/
Testnet for Bitcoin: https://en.bitcoin.it/wiki/Testnet

Faucets¶

http://test.faucet.masternode.io - by coingun
http://faucet.test.dash.crowdnode.io - by ndrezza
https://test.faucet.dashninja.pl - by elbereth

Explorers¶

Pools¶

https://test.pool.dash.org [stratum+tcp://test.stratum.dash.org] - by flare
http://test.p2pool.dash.siampm.com [stratum+tcp://test.p2pool.dash.siampm.com:17903] by thelazier
http://p2pool.dashninja.pl:17903/static - by elbereth
http://test.p2pool.masternode.io:18998/static - by coingun

Masternodes¶

Installing a masternode under testnet generally follows the same steps as the mainnet masternode installation guide, but with a few key differences:

You will probably be running a development version of Dash instead of the stable release. See here for a list of builds, then choose the latest successful develop build and click Artifacts to view a list of binaries.
When opening the firewall, port 19999 must be opened instead of (or in addition to) 9999. Use this command: ufw allow 19999/tcp
Your desktop wallet must be running in testnet mode. Add the following line to dash.conf: testnet = 1
When sending the collateral, you can get the 1000 tDASH for free from a faucet (see above)
You cannot use dashman to install development versions of Dash. See the link to downloadable builds above.
Your masternode configuration file must also specify testnet mode. Add the following line when setting up dash.conf on the masternode: testnet = 1
As for mainnet masternodes, the RPC username and password must contain alphanumeric characters only
When cloning sentinel, you may need to clone the development branch using the -b option, for example: git clone -b develop https://github.com/dashpay/sentinel.git
Once sentinel is installed, modify ~/.dashcore/sentinel/sentinel.conf, comment the mainnet line and uncomment: network=testnet
The wallet holding the masternode collateral will expect to find the masternode.conf file in ~/.dashcore/testnet3/masternode.conf instead of ~/.dashcore/masternode.conf.

Testnet 0.15.0¶

In December 2019, the Dash team announced the start of testing of the upcoming Dash 0.15.0 release. Extensive internal testing has already been done on the 0.15.0 code, but there are numerous bugs that can only be revealed with actual use by real people. The Dash team invites anybody who is interested to download the software and become active on testnet. This release includes:

Bitcoin 0.15 backports
Removal of legacy code

Discussion:

Testnet announcement: https://www.dash.org/forum/threads/v15-0-testing.49140/
Product brief:
Testnet tools: https://docs.dash.org/en/stable/developers/testnet.html
Issue tracking: https://github.com/dashpay/dash/issues/new

Latest test binaries:

https://github.com/dashpay/dash/tree/v0.15.0.0-rc1

Testnet 0.14.0¶

In March 2019, the Dash team announced the start of testing of the upcoming Dash 0.14.0 release. Extensive internal testing has already been done on the 0.14.0 code, but there are numerous bugs that can only be revealed with actual use by real people. The Dash team invites anybody who is interested to download the software and become active on testnet. This release includes:

LLMQ DKGs
LLMQ based ChainLocks
LLMQ based InstantSend

Discussion:

Testnet announcement: https://www.dash.org/forum/threads/v14-0-testing.44047/
Product brief: https://blog.dash.org/product-brief-dash-core-release-v0-14-0-now-on-testnet-8f5f4ad45c96
Testnet tools: https://docs.dash.org/en/stable/developers/testnet.html
Issue tracking: https://github.com/dashpay/dash/issues/new

Latest test binaries:

https://github.com/dashpay/dash/releases/tag/v0.14.0.0-rc6

Testnet 0.13.0¶

In November 2018, the Dash team announced the start of testing of the upcoming Dash 0.13.0 release. Extensive internal testing has already been done on the 0.13.0 code, but there are numerous bugs that can only be revealed with actual use by real people. The Dash team invites anybody who is interested to download the software and become active on testnet. This release includes:

Automatic InstantSend for Simple Transactions
Deterministic Masternode List
3 Masternode Keys: Owner, Operator and Voting
Special Transactions
PrivateSend Improvements

Discussion:

Testnet announcement: https://www.dash.org/forum/threads/v13-0-testing.41945/
Product brief: https://blog.dash.org/product-brief-dash-core-release-v0-13-0-5d7fddffb7ef
Testnet tools: https://docs.dash.org/en/stable/developers/testnet.html
Issue tracking: https://github.com/dashpay/dash/issues/new

Latest test binaries:

https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc11

Testnet 0.12.3¶

In June 2018, the Dash team announced the start of testing of the upcoming Dash 0.12.3 release. Extensive internal testing has already been done on the 0.12.2 code, but there are numerous bugs that can only be revealed with actual use by real people. The Dash team invites anybody who is interested to download the software and become active on testnet. This release includes:

Named Devnets, to help developers quickly create multiple independent devnets
New format of network message signatures
Governance system improvements
PrivateSend improvements
Additional indexes cover P2PK now
Support for pruned nodes in Lite Mode
New Masternode Information Dialog

Discussion:

https://www.dash.org/forum/threads/v12-3-testing.38475
Testnet tools: https://docs.dash.org/en/stable/developers/testnet.html
Issue tracking: https://github.com/dashpay/dash/issues/new

Latest test binaries:

https://github.com/dashpay/dash/releases/tag/v0.12.3.0-rc3

Testnet 0.12.2¶

In October 2017, the Dash team announced the launch of a testnet for public testing of the upcoming 0.12.2 release of the Dash software. Extensive internal testing has already been done on the 0.12.2 code, but there are numerous bugs that can only be revealed with actual use by real people. The Dash team invites anybody who is interested to download the software and become active on testnet. This release includes:

DIP0001 implementation https://github.com/dashpay/dips/blob/master/dip-0001.md
10x transaction fee reduction (including InstantSend fee)
InstantSend vulnerability fix
Lots of other bug fixes and performance improvements
Experimental BIP39/BIP44 complaint HD wallet (disabled by default, should be fully functional but there is no GUI yet)

Discussion:

Testnet 12.2 discussion: https://www.dash.org/forum/threads/v12-2-testing.17412/
Testnet tools: https://www.dash.org/forum/threads/testnet-tools-resources.1768/
Issue tracking: https://github.com/dashpay/dash/issues/new

Latest successfully built develop branch binaries:

Dash Core: https://gitlab.com/dashpay/dash/pipelines
Sentinel: https://github.com/dashpay/sentinel/tree/develop

Insight API Installation¶

The open-source Dash Insight REST API provides you with a convenient, powerful and simple way to read data from the Dash network and build your own services with it. Simple HTTP endpoints exist for all common operations on the Dash blockchain familiar from the Bitcore Insight API, as well as Dash-specific features such as InstantSend transactions, budget proposals, sporks and the masternode list. This documentation describes how to set up the Dash Insight API server and (optionally) the Dash Insight UI block explorer.

A standard installation of Ubuntu Linux 18.04 LTS will be used as an environment for the server. We assume you are running as a user with sudo permissions. First update all packages and install some tools and dependencies:

sudo apt update
sudo apt upgrade
sudo apt install npm build-essential libzmq3-dev

Download and extract the latest version of Dash Core:

cd ~
wget https://github.com/dashpay/dash/releases/download/v0.15.0.0/dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz
tar -xvzf dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz
rm dashcore-0.15.0.0-x86_64-linux-gnu.tar.gz

Install Dashcore Node and create your configuration:

sudo npm install -g @dashevo/dashcore-node
dashcore-node create mynode

Install the Insight API service and (optionally) Insight UI:

cd mynode
dashcore-node install @dashevo/insight-api
dashcore-node install @dashevo/insight-ui

Change paths in the configuration file as follows:

nano dashcore-node.json

Change the value of datadir to ../.dashcore
Change the value of exec to ../dashcore-0.14.0/bin/dashd
Optionally change the value of network to testnet if you want to run Insight on testnet

Run it:

dashcore-node start

Your Insight API node will start up and begin to sync. Progress will be displayed on stdout. Once sync is complete, the API endpoints listed in the documentation will be available at:

https://<ip-address>:3001/insight-api/<endpoint>/

The Insight UI block explorer will be available at:

http://<ip-address>:3001/insight/

Sporks¶

Um fork multifásico, popularmente conhecido como «spork», é um mecanismo exclusivo do Dash usado para implantar com segurança novos recursos na rede por meio de variáveis de nível de rede para evitar o risco de bifurcação indesejada de rede durante as atualizações. Também pode ser usado para desabilitar determinados recursos se uma vulnerabilidade de segurança for descoberta - veja aqui para uma breve introdução aos sporks. Esta documentação descreve o significado de cada spork existente atualmente na rede e como verificar seus respectivos status.

Spork funções¶

Sporks são definidos usando valores inteiros. Muitos sporks podem ser definidos para uma data específica (número de segundos decorridos desde 1º de janeiro de 1970) para especificar a hora em que eles serão ativados. Os sporks ativados estão definidos como 0 (segundos até a ativação). Esta função é freqüentemente usada para definir uma data de ativação do spork até o futuro no futuro, que é efetivamente desativada até ser alterada. Os seguintes sporks existem atualmente na rede e servem funções conforme descrito abaixo:

SPORK_2_INSTANTSEND_ENABLED: Governa a capacidade dos clientes do Dash de usar a funcionalidade InstantSend.
SPORK_3_INSTANTSEND_BLOCK_FILTERING: Se ativado, os masternodes rejeitarão os blocos que contêm transações em conflito com transações InstantSend bloqueadas mas não confirmadas.
SPORK_5_INSTANTSEND_MAX_VALUE: Aplica o valor máximo no Dash que pode ser incluído em uma transação do InstantSend.
SPORK_6_NEW_SIGS: Ativa um novo formato de assinatura para mensagens de rede específicas do Dash, introduzidas no Dash 12.3. Para mais informações, veja aqui e aqui.
SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT: Se habilitado, os mineiros devem pagar 50% da recompensa em bloco para um masternode atualmente pendente de seleção ou o bloqueio será considerado inválido.
SPORK_9_SUPERBLOCKS_ENABLED: Se ativado, os superblocos são verificados e emitidos para pagar os vencedores das propostas.
SPORK_10_MASTERNODE_PAY_UPDATED_NODES: Controla se os masternodes que executam uma versão de protocolo mais antiga são considerados elegíveis para pagamento. Isso pode ser usado como um incentivo para incentivar os masternodes a serem atualizados.
SPORK_12_RECONSIDER_BLOCKS: Força a reindexação de um número especificado de blocos para se recuperar de garfos de rede não intencionais.
SPORK_13_OLD_SUPERBLOCK_FLAG: Descontinuada. Nenhuma função de rede desde o bloco 614820.
SPORK_14_REQUIRE_SENTINEL_FLAG: Alterna se os masternodes com status são elegíveis para pagamento se o status for WATCHDOG_EXPIRED, i.e. O Sentinel não está funcionando corretamente.
SPORK_15_DETERMINISTIC_MNS_ENABLED: Controla se deterministic masternodes é requerido. Quando ativada, a lógica da lista de masternodes herdada não será mais executada e os masternodes não atualizados não estarão qualificados para pagamento.
SPORK_16_INSTANTSEND_AUTOLOCKS: Permite o bloqueio automático de transações para transações com menos de um número especificado de entradas e remove a taxa do InstantSend herdado. Permite que qualquer nó solicite o bloqueio de transação, não apenas o nó de envio.
SPORK_17_QUORUM_DKG_ENABLED: Enables the DKG process to create LLMQ quorums. This spork will be turned on once 80% masternodes are upgraded to v0.14, which will enable DKG and DKG-based PoSe.
SPORK_19_CHAINLOCKS_ENABLED: Enables ChainLocks, a mechanism of preventing the risk to payments introduced by blockchain reorganization events. ChainLocks are described in DIP0008 ChainLocks.
SPORK_20_INSTANTSEND_LLMQ_BASED: When enabled, legacy InstantSend is superseded by LLMQ-based InstantSend, as described in DIP0010 LLMQ-based InstantSend.

Visualizar o status do spork¶

Os comandos spork show e spork active emitidos na janela de depuração (ou a partir de dash-cli em um masternode) permitem que você interaja com sporks. Você pode abrir a janela de depuração selecionando Ferramentas > Console de depuração.

spork show e spork active output no console de depuração do Dash Core

Histórico de versões¶

Notas de lançamento completas e o histórico de versões do Dash estão disponíveis aqui:

https://github.com/dashpay/dash/blob/master/doc/release-notes.md

Marketing¶

This page includes downloads of various templates and designs intended for use as office stationary and presentations. For a visual overview of existing web and sticker designs, please see the following links.

Dash uses the following color scheme to promote a consistent visual identity.

Color	RGB	CMYK	Hex	Pantone
Dash Blue	0,141,228	76,38,0,0	#008de4	2925c
Deep Blue	1,32,96	100,94,31,29	#012060	534c
Midnight Blue	11,15,59	100,96,41,53	#0b0f3b	5255c
White	255,255,255	0,0,0,0	#ffffff	-
Grey	120,120,120	54,46,45,11	#787878	Cool Gray 9 C
Black	17,25,33	82,71,59,75	#111921	Black 6 C

Design Materials¶

Brochures¶

An attractive brochure about Dash, designed for handing out at conferences and events. Prepared by community member Essra in 2018 following proposal sponsorship for the German Dash Embassy D-A-CH.

This design can be translated into your language at Transifex here. For more information on translating Dash products on Transifex, see here. Please contact leon.white@dash.org once translation is complete to request layout of the completed translation.

Language	Download
English	PDF
Dutch	PDF
French	PDF
German	PDF
Spanish	PDF
Thai	PDF
Vietnamese	PDF

Flyers¶

An attractive flyer about Dash, designed to be folded in half and placed on flat surfaces at conferences and events. Prepared by community member Essra in 2018 following proposal sponsorship for the German Dash Embassy D-A-CH.

This design can be translated into your language at Transifex here. For more information on translating Dash products on Transifex, see here. Please contact leon.white@dash.org once translation is complete to request layout of the completed translation.

Language	Download
English	PDF
Arabic	PDF
Chinese (Traditional)	PDF
Dutch	PDF
French	PDF
German	PDF
Spanish	PDF
Thai	PDF
Turkish	PDF
Vietnamese	PDF

Handouts¶

This handout is ideal for dual-sided printing as a handout for conferences. The current version is v3.1; previous versions are available below.

This design can be translated into your language at Transifex here. For more information on translating Dash products on Transifex, see here. Please contact leon.white@dash.org once translation is complete to request layout of the completed translation.

Language	Download
English	PDF DOCX
Arabic	PDF DOCX
Czech	PDF DOCX
Dutch	PDF DOCX
German	PDF DOCX
Russian	PDF DOCX
Slovak	PDF DOCX
Thai	PDF DOCX
Vietnamese	PDF DOCX

Previous versions (English only):

Version	Download
2.0	PDF DOCX
1.0	PDF DOCX

Infographics¶

The Dash Difference¶

This engaging infographic details the improvements the Dash network has delivered by building on the Bitcoin code base. Based on an original design by community member J. Arroyo.

This design can be translated into your language at Transifex here. For more information on translating Dash products on Transifex, see here. Please contact leon.white@dash.org once translation is complete to request layout of the completed translation.

Language	Download
English	PDF PNG
Arabic	PDF PNG
Bulgarian	PDF PNG
Chinese (Simplified)	PDF PNG
Chinese (Traditional)	PDF PNG
Czech	PDF PNG
French	PDF PNG
German	PDF PNG
Greek	PDF PNG
Italian	PDF PNG
Polish	PDF PNG
Russian	PDF PNG
Slovak	PDF PNG
Spanish	PDF PNG
Vietnamese	PDF PNG

Ten Misconceptions About Dash¶

This infographic refutes many common yet uninformed arguments made against Dash. Based on an original design by community member DashDude.

This design can be translated into your language at Transifex here. For more information on translating Dash products on Transifex, see here. Please contact leon.white@dash.org once translation is complete to request layout of the completed translation.

Language	Download
English	PDF PNG
Arabic	PDF PNG
Bulgarian	PDF PNG
Chinese (Traditional)	PDF PNG
Czech	PDF PNG
French	PDF PNG
German	PDF PNG
Greek	PDF PNG
Polish	PDF PNG
Russian	PDF PNG
Slovak	PDF PNG
Spanish	PDF PNG
Thai	PDF PNG
Vietnamese	PDF PNG

Presentations¶

Dash Meetup¶

An attractive presentation about Dash, designed to guide the audience through the basics of cryptocurrency and advantages of Dash. Prepared by community member Essra in 2018 following proposal sponsorship for the German Dash Embassy D-A-CH.

Language	Download
English	PPTX PDF
German	PPTX PDF

Simple presentation¶

A simple presentation about Dash, available in 5 languages, 3 aspect ratios and 2 formats. Simply click the links to download. Note that the Noto Sans UI font must be installed if using the PowerPoint files.

Browse all files on Dropbox

Language	Format	Download
English	PDF	16:9 4:3 A4
English	PPTX	16:9 4:3 A4
Chinese (Simplified)	PDF	16:9 4:3 A4
Chinese (Simplified)	PPTX	16:9 4:3 A4
Portuguese	PDF	16:9 4:3 A4
Portuguese	PPTX	16:9 4:3 A4
Russian	PDF	16:9 4:3 A4
Russian	PPTX	16:9 4:3 A4
Spanish	PDF	16:9 4:3 A4
Spanish	PPTX	16:9 4:3 A4

Dash 101 Presentation¶

Prepared by community member Essra in 2017 following proposal sponsorship for the German Dash Embassy D-A-CH.

Language	Download
English	PPTX
French	PPTX
German	PPTX
Spanish	PPTX

Business Templates¶

Document templates¶

Official Dash document templates.

Nome	Download
Word document with cover page and paragraph styles	DOCX
Word template with blue watermark	DOTX
Word template with grey watermark	DOTX

Presentation templates¶

Official Dash presentation templates. We strongly recommend using predefined presentation slide layouts (check here for instructions).

Nome	Download
PowerPoint template with simple blue and white slides	POTX
PowerPoint template with sample layouts, styles and shapes	POTX
Presentation icons	PPTX

Cards¶

High resolution cards for printing. Great for use as the back of business cards, or to hand out to explain and promote Dash.

Nome	Download version
Handout Card	English
	Arabic
	Chinese (Simplified)
	Czech
	French
	Polish
	Portuguese
	Russian
	Spanish

Fonts¶

Nome	Download version
Montserrat	7.20
Open Sans	1.10
Roboto Condensed	2.137

Legal¶

How the Law Applies to Dash¶

The purpose of the Dash DAO is to promote, protect and standardize Dash. In the course of our mission, we have received inquiries into how some aspects of Dash are treated under United States law. The purpose of this document is to address the most common of these inquiries and explain how we believe the laws apply to Dash. This is not meant as a legal opinion, and you should consult your own attorneys before relying upon it. However, it is meant to state our position on the law, and how the law should be properly interpreted.

One of the most common questions we receive is How are masternode operators treated under the US tax laws?

Tax Treatment¶

Block rewards¶

As many already know, block rewards are paid to masternode operators in exchange for validating transactions on the Dash network. The IRS has stated unequivocally that “when a taxpayer successfully ‘mines’ virtual currency, the fair market value of the virtual currency as of the date of receipt is includible in gross income.” To be sure, masternodes do not “mine”, but the IRS considers using computer resources to validate Bitcoin transactions and maintain the public Bitcoin transaction ledger to constitute “mining”. By analogy, a masternode operator should also treat as regular income the fair market value of the block reward.

Dash Collateral¶

A Dash user may demonstrate to the network his or her control over 1,000 DASH in order to run a masternode. These tokens never leave the user’s control. If at any point during the user’s tenure as a masternode operator, the user disposes of any or all of the 1,000 DASH, the network automatically strips the user of his or her status as a masternode. Under the US Internal Revenue Code, gain or loss is realized only on the “sale or exchange” of property. The term “sale” generally means the transfer of all right, title, and interest in the property transferred. A number of factors typically are considered to determine whether a sale has occurred, the most important being whether the benefits and burdens of ownership of the transferred property have passed from the transferor to the transferee. In Dash, the masternode operator retains control of the 1,000 DASH and simply demonstrates that control to the network. Therefore, the holding of the 1,000 DASH for purposes of qualifying as a masternode operator should not cause a taxable event to occur because the user has not transferred any of the benefits and burdens of ownership.

Capital Gains¶

Assuming that the 1,000 DASH are sold, whether that Dash is a “capital asset” will determine the tax treatment of the sale. Stocks, bonds and other investment property for example, are generally treated as capital assets. Inventory, depreciable property, and stock in trade, though, are not. Assuming the masternode operator held the 1,000 DASH either for investment purposes or for purposes of qualifying as a masternode operator, the IRS would likely treat gain or loss on the sale of those Dash tokens as capital in nature. Therefore, Dash held for a long enough period of time could be subject to the lower “long term capital gains” tax rate.

Legal Liability¶

As with cash or any other currency system, users may use Dash in connection with illegal activity. A common question we receive is whether masternode operators can also be liable for criminal activity, simply by relaying transactions related to that activity. The fundamental legal requirement of mens rea makes criminal liability unlikely for masternode operators.

Primary Liability¶

Almost all crimes require that a defendant have a defined mens rea at the time of an offense. Mens rea is a mental state like purposefulness, knowledge, recklessness or negligence. For example, to act with “purpose” is commonly understood as desiring as your “conscious object” the result of a crime. “Knowledge” is a less culpable mindset than “purpose” – acting with “knowledge” requires general awareness that your actions will bring about a particular crime. “Recklessness” requires disregard of a substantial risk. Finally, a person acts “negligently” if they should have been aware of a substantial and unjustifiable risk of a particular consequence of their actions, but were not.

Most masternodes have no awareness, while relaying Dash transactions, of the identity of the users involved, the ultimate destination of users’ funds, or any other circumstances of Dash transactions. As such, it would be difficult for a prosecutor to demonstrate that a masternode operator who facilitated an illegal transaction merely by relaying the transaction would have a culpable mens rea.

Secondary Liability¶

Even if someone is not the principal actor in the commission of a crime, that person can be secondarily liable for their involvement in it. As such, we are sometimes asked whether masternode operators, by their involvement in relaying Dash transactions, could be “aiding and abetting” or “conspiring” to commit a crime that might involve Dash. Generally speaking, aiding and abetting requires that the defendant (i) seek by his action to make the crime succeed and (ii) act with the same mens rea as required for the principal offense.

No matter the requisite mens rea of a particular principal offense committed by a Dash user, it is unlikely that a mere masternode operator, without more, could be found to have “aided and abetted.» To be sure, the masternodes do provide assistance in the principal offense – in that masternode action is required to process all Dash transactions. However, the masternodes would not have the requisite mens rea to satisfy the requirements of aiding and abetting liability. Masternode operators have no readily available information about the purpose or consequences of users’ Dash transactions, or even the originating identity of the sender of funds. As such, so long as a sufficient diversity of non-criminal transactions occur on the Dash network, they would not harbor even the least culpable mens rea (i.e. negligence) with respect to a user relaying or receiving Dash in furtherance of a particular crime.

“Conspiracy” liability is even less likely. Conspiracy generally requires i) an agreement to commit a crime, ii) knowledge of the unlawful purpose of the agreement, iii) intent to further the unlawful purpose, and iv) an act in furtherance of the conspiracy. None of these requirements are met by mere masternode operators.

Exchange Liability¶

Exchanges have asked whether they can be held liable for criminal activity connected with Dash PrivateSend transactions.

The Bank Secrecy Act (BSA) is the law that primarily governs exchanges in the United States. The BSA does not contain any prohibition on supporting Dash transactions. Indeed, the BSA take a flexible, risk- based approach to regulation and contemplate that financial institutions will enter into lines of business with new risks. This risk-based approach requires, at the outset, an independent risk assessment. By and large, the risks faced by exchanges who begin to support Dash will be similar to the risks associated with other virtual currencies. One significant difference concerns PrivateSend transactions, and we focus on this difference below:

PrivateSend transactions obfuscate the source and destination addresses of funds, thus blockchain forensic techniques like clustering analysis may be less effective. To the extent that exchanges rely on such blockchain forensics tools for their information collection, reporting and reporting obligations under the BSA, they should consider alternative means.
PrivateSend transactions are used for legitimate purposes and are often required to achieve personal or commercial privacy for sensitive transactions. The use of PrivateSend transactions is not inherently suspicious. Combination with other factors, including those identified in the exchange’s own risk assessment, may raise PrivateSend transactions to the level of suspicious activity.
Exchanges should consider revising their risk assessments and AML policies to account for the unique characteristics of Dash. For example, including blockchain addresses in Suspicious Activity Reports (SARs) will be less descriptive and effective for investigations based on such addresses. Exchanges might consider adding additional context and explanation in SARs.
When conducting Enhanced Due Diligence on customers and transactions, exchanges should account for the presence of PrivateSend transactions and update their AML policies accordingly. For example, identifying counterparties to a PrivateSend transaction may be more difficult than identifying counterparties to transactions in other virtual currencies when relying on blockchain forensics.

PrivateSend Legal Position¶

Dash’s transaction rules are identical to Bitcoin, and therefore for regulatory and compliance purposes Dash can and should be treated identically to Bitcoin. BlockchainIntel and Coinfirm are KYC/AML service providers that offer services covering the Dash blockchain.

This PDF document offers a full overview of the Dash PrivateSend Legal Position.

ATM & Fiat Compliance¶

introdução¶

An aspect that required legal research is what are the compliance requirements to facilitate Dash-fiat exchange. This can be in the form of running ATM kiosks or using other mechanisms to personally offer Dash to fiat exchange services.

For this purpose we hired Cogent Law, who have a lot of experience working in compliance for digital money services. They have put together a compliance program that will be shared with anyone launching a Dash service if they require it. This includes:

A finCEN BSA compliant written Principal MSB/KYC AML Program designed to prevent the Principal MSB from being used to facilitate money laundering and the financing of terrorist activities
A comprehensive risk based assessment by a third party compliance consultant expert

Our lawyer for this project is Adella Toulon-Foerster who has extensive experience in this field including:

Banking Secrecy Act (BSA), Anti-Money Laundering (AML), and Know Your Customer (KYC) regulations
FinCEN requirements and guidance
Written and on-going AML compliance programs
State-by-state money transmitter laws and licensure requirements

We now have full documentation of the program from Cogent Law, the package includes:

BSA AML Compliance training
KYC CDD Policy
AML Program
Risk Assessment
Surveillance and Monitoring Policy
Different Reports to file in different situations

The documents have a format as if they were created for the fictional company “Initech” and then the interested Dash entrepreneur would have to replace it with their real corporation. We believe that some counsel would still be advisable for an investor launching a service but this will help provide a solid understanding of the requirements and get them 80% of the way. This should also be highly educational and help the Dash investor be more at ease as it enlightens a typically obscure topic for most crypto enthusiasts.

This program is directed at Dash investors that are interested in running a compliant service in regulated markets. If some users prefer to run services without a compliance program or don’t need one, we completely respect that too.

Dash ATM Compliance Program¶

Please first read the Quick Guide To Operating a Virtual Currency Kiosk. This guide will guide you through the initial steps of registering as an MSB. It is crucial you start here.
Listen to the Audio Guides on BSA AML and read the BSA AML Training Manual
Get familiar with the documentation you will need by looking at the following templates
Get familiar with some of the reports you may need to file as part of operations. In the Quick Guide in Step 1, we go through registration on the E - BSA filing system. This step also provides example CTR (Currency Transaction Report) and SAR (Suspicious Activity Report) report samples. Dash operators should be familiar with these as they may need to file them as part of operations. Sample reports:
- Currency Transaction Report
- Suspicious Activity Report
If you would now like to move forward with your project, we recommend getting in contact with Cogent Law, our recommended legal counsel. Preferential rates are available for Dash users. Please email: atoulon@cogentlaw.co

Documentação Dash¶

Índice¶

O que é o Dash?¶

Dash Videos¶

Escola Dash¶

Dash 101¶

Whitepaper¶

Cronograma¶

Características¶

Especificações¶

Masternodes¶

PrivateSend¶

InstantSend¶

ChainLocks¶

ChainLocks Process Overview¶

Sporks¶

Hash Algoritimo X11¶

Vantagens do X11¶

Dark Gravity Wave¶

Taxa de emissão¶

Emissão total de moedas¶

Alocação de recompensas de bloco¶

Governança Descentralizada¶

Sentinel¶

Taxas¶

Evolution¶

Evolution Previews¶

How To Buy¶

Exchanges¶

Marketplace comparison websites¶

Dash.org markets¶

List of exchanges¶

Instant exchanges¶

Over the Counter¶

ATMs¶

Segurança¶

Impersonation¶

Golpes¶

Esquemas Ponzi¶

Links and Information¶

Links¶

Official sites¶

Community sites¶

Forums¶

Chat¶

Social media¶

Facebook¶

Twitter¶

News¶

Blogs¶

Wikipedia¶

Inactive¶

Ferramentas¶

Block explorers, statistics and visualizations¶

Treasury tools¶

Masternode management¶

Price monitoring and statistics¶

Dash Community project¶

DarkNet pages¶

Mobile Apps¶

iOS¶

Android¶

Glossário¶

Carteiras¶

Carteira Dash Core¶

Instalação¶

Linux Installation Guide¶

Guia de instalação no macOS¶

Guia de Instalação no Windows¶

Interface¶

A janela principal¶

A caixa de diálogo Opções¶

A Ferramenta de Diálogo¶

Enviando e recebendo¶

Enviando Dash¶

Recebendo Dash¶

PrivateSend and InstantSend¶

PrivateSend¶

InstantSend¶

Backup e restauração de carteira¶