DarkCoin(DASH) - POW/POS - X11





  • Dash Release long-awaited 12.1 version 

    https://github.com/dashpay/das...

    More Details:

    The new binaries, along with documentation, will be available in www.dash.org.

    Mining pools

    The information needed to the upgrade is available at https://dashpay.atlassian.net/wiki/display/DOC/Mining+pools

    Masternodes

    New hardware requirements and upgrade guides will be available at https://dashpay.atlassian.net/wiki/display/DOC/Masternode+Update

    Users / Exchanges

    Basic upgrade guide will be available upon release.

    Support about the update

    Should you have any question about the update, we recommend either:

    -#dash_support_desk channel at the Dash Nation Slack (public, cummunity-driven Slack, you can sign up here)

    -Official forum : https://www.dash.org/forum/top...

     

    The team and the community will be available to answer arising questions.

    Thanks



  • Bring Dash to your local ATM!

    “Dash is now supported on all GENERAL BYTES #bitcoin ATMs. Ask your local ATM operator to enable Dashpay today!http://thndr.me/zZnUM3

    Recently the GENERAL BYTES Bitcoin ATM models have been upgraded to support Dash, the 6th largest cryptocurrency in the world. You can do your part to help increase Dash adoption in the ATMs by supporting this Thunderclap event.

    We need a minimum of 100 people to support us in our goal. (*supporting us is free!) All it takes is a minute of your time and you will be able to support us using your Facebook, Twitter or Tumblr account. The Dash community will be grateful so what are you waiting for? Your favourite cryptocurrency needs you!

    https://www.thunderclap.it/pro...



  • New Exchange 

    Dash is listed on cryptxc

    https://cryptxc.com/markets/da...



  • Dash Core 0.12.1.1 Release

    About this Release

    Dash Core 0.12.1.1 is a maintenance release of the Dash Core 0.12.1.x series

    In this minor release only bugfixes have been included and we consider this a stable release.

    • improve govobj sync
    • fix Qt segfault on mixing
    • minor typos
    • improve rpc API

    Download:https://github.com/dashpay/das...

    Changelog

    0.12.1.1 changelog
    ===============
    - fixing strings and docs + instantsend.md
        --> https://github.com/dashpay/dash/pull/1354
    - [RFC] add ObjectType to first-level JSON result
        --> https://github.com/dashpay/dash/pull/1352
    - fix gov list filtering bug
        --> https://github.com/dashpay/dash/pull/1353
    - Add "enough data" stop conditions for gov sync
        --> https://github.com/dashpay/dash/pull/1350
    - fix verification network behaviour
        --> https://github.com/dashpay/dash/pull/1348
    - Update sendcoinsentry.ui
        --> https://github.com/dashpay/dash/pull/1349
    - fix watchdogs
        --> https://github.com/dashpay/dash/pull/1346
    - a bit more granular sync checks for mnpayment
        --> https://github.com/dashpay/dash/pull/1344
    - Gracefully not accept incoming connection
        --> https://github.com/dashpay/dash/pull/1342
    - Few networking fixes
        --> https://github.com/dashpay/dash/pull/1341
    - [Trivial] maxconnections parameter help text modified
        --> https://github.com/dashpay/dash/pull/1340
    - Fix: Broken download link
        --> https://github.com/dashpay/dash/pull/1335
    - Update for OpenSSL 1.1 API.
        --> https://github.com/dashpay/dash/pull/1336
    - Fix crash on initial mixing step:
        --> https://github.com/dashpay/dash/pull/1331
    - Fix locking issues in dash-qt masternodelist
        --> https://github.com/dashpay/dash/pull/1328
    - Fix rpc
        --> https://github.com/dashpay/dash/pull/1325
    - Fix some uninitialized variables in dash-qt
        --> https://github.com/dashpay/dash/pull/1324


  • New Exchnage:

    https://magneticexchange.com/i...

    For more Details about Magnetic Exchnage:http://cryptocentral.info/topi...



  • Dash New Exchange:

    https://coingi.com/

    More Details About Exchnage: http://www.cryptocentral.info/...



  • Dash Core 0.12.1.3 Release

    We are happy to announce the release of 0.12.1.3. This release includes binaries, which can be downloaded below.

    About this Release

    Dash Core 0.12.1.3 is a maintenance release of the Dash Core 0.12.1.x series

    In this minor release only bugfixes have been included and we consider this a stable release.

    On March 1st we have discovered a bug in IS/IX processing code which may cause a peer to crash under certain circumstances. Because of the nature of this bug and the impact on node stability we advice ALL users to update to 0.12.1.3 ASAP. All 24/7 nodes (mining pools, masternodes, exchanges, merchants etc) should consider this update as a MUST.

    • fixes a bug in IS/IX processing code which causes the peer to crash
    • improve sync
    • improve sendrawtransaction RPC
    • fix splash screen
    • fix protobuf 3.0 compilation on MacOS

    Changelog

    0.12.1.3 changelog
    ==================
    - Do not send outdated MNs on sync (#1373)
    - Do not force disconnect for stalled nodes on sync (#1374)
    - fix recently observed crash on IsValid (#1375)
    - fixed protobuf 3.0 (byteswap) issue on macOS (#1370)
    - make sendrawtransaction to accept 2nd optional (#1369)
    - Splashscreen now displays correctly (Fully) (#1367)
    Thanks to 
    @UdjinM6, @tgflynn, @spencerlievens, @chaeplin, @QuantumExplorer, @schinzelh

    Download :https://github.com/dashpay/das...



  • DashForce Bitfinex contest: 


    The Dash Biz Dev team has tasked DashForce with getting some traffic over to Bitfinex. They have just fired up Dash trading pairs again and need some liquidity on the buy side. 
    Here is how it will work, if you buy over $1000 in Dash you will get a 1 Dash tip, $500 and you get a 0.5 Dash tip. If you place an order that is higher than $250 you get a 0.25 tip.

    So, after you place your order take a screenshot of that. Then, once someone fills your order take a screenshot of that. Upload your screenshots in the #dash_force slack channel and we will send you your reward. Simple as that! 
    Our budget for this contest is ~$500, so get over there quick and don't Slack 
    Help us Make Bitfinex Great Again!  


    Bitfinex
    https://www.bitfinex.com/trading/DSHBTChttp://dash-nation-invite.herokuapp.com/

    #dash_force slack channel
    https://dashnation.slack.com/m...

    *This is not the major exchange that was announced last month, that is still in the works.



  • Dash Core Release v0.12.1.4


    Download:



  • The Dash Masternode Network: A Response to Critics






    Since its inception, the Dash Masternode network has received both substantial praise and strong criticism. This 2nd-tier network is the primary differentiation between Dash and Bitcoin, because the Masternode network is what makes possible Dash’s advanced features including InstantSend, PrivateSend, and the Dash Budget System. However, since the inception of the Masternode network almost two years ago a number of criticisms have cropped up. Here, I address the most common ones. “Masternode ownership is centralized” Like any cryptocurrency, Dash is intended to be decentralized. Critics have complained that the Masternode network is in fact centralized, claiming that only a few people own the 4,000 Masternodes currently running. The truth is, no one knows exactly how many people own those Masternodes — it’s all guesswork. Looking at the numbers from Dash Central and voting patterns from Dash Vote Tracker, I suspect it is far more distributed than some critics think. I would guess there are at least 1,000 different owners, and perhaps as many as 2,000. But again, no one knows, and all guesses include some level of speculation. More importantly, let’s step back and realize what centralization really is before we start attaching the label to the Masternode network. I would argue that to be centralized, three things must be true:

    1. There is a small group of people in charge.
    2. It is impossible or nearly so to become a member of, or influence, that small group.
    3. One is under significant obligation to use the centralized service.

    They are in control. A perfect example of centralization are most country’s governments. After all, they consist of a small, elite group in charge; for most people it is effectively impossible to become part of or influence that group; and citizens are forced to use the services of their government. Large industries such as banking are also often centralized. Only a small group of people control the banks; it is very difficult to influence those who control the banks; and in modern society, it is almost impossible to live without using the banking system (although cryptocurrencies are aiming to change that). Let’s look at Dash now. Is it centralized? If critics are correct, then a small number of people own the Dash Masternodes. So the first requirement — if true — is met. Is it impossible or nearly so to become a member of that small group? Not at all. For the past three years anyone with even limited funds could become a Masternode owner. Now, the price is higher, but it is only money that is a barrier. The last requirement is where claims of Dash’s “centralization” truly fail. No one is forced to use Dash, and, being open-source software, anyone can copy the code and create a new fork if they are unsatisfied with the direction Dash is taking (and someone has). That’s quite a lower hurdle than overthrowing a centralized government or taking on the banking establishment. “It’s too expensive to buy a Masternode” I’ve been hearing this one since Dash was $4; with the price recently topping $100, it’s just becoming more prevalent. As the price of a Masternode begins to reach and exceed the price of a nice house in many areas of the world, is a Masternode too expensive?

    Approximate current cost of a Masternode. We need to remember the purpose of the Masternode network — it’s not to enrich Masternode owners (although it may do that), it’s to provide a 2nd-tier network to execute the many features of Dash. The block rewards are simply to incentivize people to do the work of running a Masternode. Just as mining was not created to enrich miners, but to secure a blockchain network, so Masternodes were created to provide an important service to the network. The 1,000 Dash barrier to Masternode rewards is arbitrary and could be changed in the future. If, for example, the barrier to entry was such that not enough Masternodes were running to support Dash, then the collateral requirement could be reduced to 500 Dash, or even lower. But note the requirement won’t be reduced in order to allow more people to receive Masternode rewards; it will be reduced if the network is in need of more Masternodes to service it (again: remember the purpose of Masternodes). Further, one does not need 1,000 Dash to receive Masternode rewards. There are currently Masternode-sharing services in which as little as 25 Dash gets you a share of a Masternode. Right now these systems require you to trust a third-party, but in the future this may become a decentralized part of the Dash network itself. Sometimes running a Masternode has been marketed as an investment; I think that this is a mistake. Running a Masternode is a job, for which one receives compensation. And like any job, there are application requirements for those who wish to fill the position — in this case, the Masternode collateral and the ability to set up and manage a server (or hire someone to do so). “Only early adopters are Masternode owners” This criticism is related to the “Masternode ownership is centralized” complaint above. Now that a Masternode is out of reach for most people, some are complaining that only early adopters are Masternode owners. And, yes, in general, I’m willing to bet that most Masternode owners today are early adopters, in the sense that they got involved in Dash before the recent meteoric price rise. However, this is a good thing. Masternodes are the backbone of Dash, and as such, they need to be run by people committed to Dash. There are two primary ways someone is committed to Dash — ideologically or financially (these two can overlap, of course). An early adopter is typically ideologically committed to Dash — he believes in the project, and was willing to invest when everyone else either ignored or attacked it. Although he made a smaller monetary investment than would be required today, his risk of total loss was also higher — which also argues for his ideological commitment. Because of these factors, early adopters have been highly motivated to manage their Masternodes properly in order to keep Dash strong.

    Artist’s rendition of the first Masternode owner. Of course, at some point even the most committed Dash follower might want to cash out his Masternode collateral. In response, someone new to Dash might pay the high price of setting up a new Masternode. This person might not be as ideologically committed to Dash as the previous owner, but now she is financially committed. She will do everything she can to protect and grow her investment. In other words, she too will make a strong Masternode owner. As Dash evolves, incentives are properly aligned so that Masternode owners are always working for the overall betterment of the network. “Masternode owners are overcompensated for their service” The current payout for running a Masternode is valued at over $750/month, and the cost is currently about $5-$20/month plus a little sys admin work. Surely Masternode owners are overpaid, aren’t they?

    The approximate value of the first Masternode payment. This is a relatively new criticism, since a year ago a Masternode owner would only be paid about $40-$50/month (with comparable costs). So this complaint only sprang up when Dash’s price dramatically rose. But note that Masternode compensation hasn’t changed (other than the scheduled 7% deflation each year); it’s the value of that compensation that’s changed. A Masternode receives around 1.8 Dash approximately every 6–7 days for its service, exactly as scheduled years ago. The change in value, however, is because the market is giving a higher value to Dash itself. Just as this higher value is based mostly on the future potential of Dash, so likewise the higher value of Masternode compensation is based on the future demands to execute that potential. Further, as Dash’s value increases, the importance of the Masternode network increases, and thus compensation naturally increases. Dash can’t control the value of its currency; it can only control the level of compensation Masternodes receive. The rise in value of Masternode compensation is a direct consequence of market forces, not any internal machinations of the Dash team or Masternode owners. “Masternodes artificially suppress Dash’s money supply” Some argue that with 4,000+ Masternodes requiring more than 4 million Dash in collateral, the total supply of Dash is effectively reduced, which artificially suppresses the total supply of Dash available. Two points in response: First, so what? The available supply might be effectively lower, but a proper understanding of money will tell you that a money supply can be 1 and still be effective, as long as the currency can be denominated to smaller and smaller portions. It doesn’t really matter what the supply is (after all, 21 million isn’t a magic number), what matters is that it cannot be artificially inflated. Those who buy and sell Dash are well aware of the existence of Masternodes and their collateral requirements, so the price of Dash reflects the market’s determination of its value with that taken into consideration.

    Manipulating the money supply, one Masternode at a time. Second, and more importantly, one must remember that the Masternode collateral isn’t really “locked up” — at any time a Masternode owner can spend that 1,000 Dash with the click of a button. And at the right price, I’m sure some owners will do just that. So although in one sense the supply is suppressed, in another, more accurate sense, the full 7+ million Dash are available. “Masternodes can be easily Sybil-attacked” This is probably the oldest, and paradoxically the weakest, criticism of Masternodes. Because Masternode owners can remain anonymous, the argument goes that an organization can take over the network by setting up a majority of Masternodes.

    Taking over the world, er, Masternode network… If there were no collateral to run a Masternode, this might be possible. With the collateral requirement, this is effectively impossible for anyone but those with the deepest pockets. Consider this. There are currently 4,000 Masternodes. To “take over” the network, an organization (let’s call it “Sybil Corp.”) would need control of at least half of all Masternodes running (actually, it’s more than that, but we’ll keep it at half to make the example simple). Let’s say, for arguments sake, that for every Sybil Masternode set up, an existing one shuts down (unlikely, but let’s assume). So Sybil Corp. would need to purchase 2,000 Masternodes, which require 2 million Dash. At current prices, that’s almost $200 million needed. Scratch off the vast majority of potential bad actors at this point (most organizations who have that much funding would be smart enough to see the costs of executing this attack far outweigh the potential benefits). But in reality Sybil Corp. will be ecstatic if they only pay $200 million. Because once they start buying up Dash to fund their Masternodes, the price of Dash will shoot up, as demand for Dash will outweigh the current desire to sell. It’s impossible to say where the price will end up, but considering current Dash’s daily trading volume is around 400k Dash, and Sybil Corp wants to single-handedly buy up 2 million Dash (almost 30% of the total supply in existence!), I’m confident the price will quickly reach four digits and price out almost anyone except the U.S. Government. (And before the conspiracy theorists start talking about the U.S. Government as Sybil Corp., note that it has the virtually unlimited funds to take over any cryptocurrency — including Bitcoin — right now). “Future Masternode sell-offs will crash the market” Because so much of Dash’s money supply is currently being used to collateralize Masternodes (about 56%), some critics have argued that a sell-off by the Masternode owners would crash the market for Dash. Well, this criticism at least has an accurate understanding of market mechanics. If lots more people are selling an item than buying, the price will drop. Economics 101. If Satoshi were to come back and sell his purported 1 million Bitcoins, I can guarantee that the price of Bitcoin would drop precipitously, at least in the short-term. The same holds true if Dash Masternode owners did likewise en masse.

    When Masternode owners run amok. However, if a large segment of Dash Masternode owners were to sell off their Dash, it is likely that there is a significant reason — say, a critical and unfixable bug has been found in the Dash code. In such a situation, Dash’s price should drop. But there is no reason to believe it is more likely that hundreds of Dash Masternode owners would decide en masse to sell off their Masternodes than it is that many Bitcoin whales would do so. Compared to global currencies and commodities like gold or silver, cryptocurrencies are all top-heavy with a relatively small number of owners who could potentially manipulate the market. Bitcoin is bigger than Dash, but its price can still be manipulated if certain large stakeholders desire. The Masternode network, in fact, doesn’t make Dash more susceptible to a large sell-off; it makes it less so, because Masternode owners are incentivized to hold their considerable Dash. Large stakeholders in other cryptocurrencies simply hold their currency and hope it rises in value. Dash Masternode owners, however, receive block rewards if they hold their Dash and run a Masternode. If someone is heavily invested in Bitcoin but decides Ethereum has a better future, he can simply exchange his Bitcoin for ETH. But a Dash Masternode owner has to be convinced that a cryptocurrency will perform better not only than Dash, but better than Dash plus the 9–10% reward he receives every year for running a Masternode. Masternodes: The Future of Cryptocurrency The Masternode network used by Dash is an important innovation to cryptocurrencies. It both improves the existing network and aligns economic incentives to grow that network in the future. Dash’s Masternode network has weathered many criticisms over the years, but none of those criticisms have properly understood and appreciated the service Masternodes provide and the incentives in place to keep the network running. The design of the Masternode network makes it perfectly positioned to become the future of cryptocurrency.

    https:[email protected]..

    DashPay




  • Dash Electrum v 2.6.4 - Mac Release

    Latest Version : 2.6.4 Mac: https://electrum-dash.org/down...

    Windows: https://electrum-dash.org/down...

    Linux: under construction

    Electrum Wiki: https://dashpay.atlassian.net/...

    DashPay



  • Dash Scam Alert: Dash-wallet.com

    The dash-wallet.com scam has been a trap that has caught several newcomers to Dash over the years. A typical problem faced by several cryptocurrency users is the setting up various sites that try to steal from the naive and onlookers through devious means such as fake wallets, fake cloud mining contracts, fake exchanges, etc.

    The dash-wallet.com incidence has happened so often that there are several red flags raised all across community channels to possibly curb the situation which has been achieved to some extent while some still get scammed by the fakewallet site despite all these efforts.

    The site works fine and has no indications that scream spam at a first glance. The site works too perfectly well and goes to the extent of generating a working Dash address for deposits, during this process the wallet works flawlessly well not raising any suspicion. Deposits work well too, but when you try to conduct a transaction that send coins out of the wallet, tables suddenly turn. After entering your destination address and amount your transaction begins and takes forever to get confirmed.

    The bottom line is, you will not be able to send coins using the wallet causing your coins to disappear into thin air. It’s no fault of users who fall for this scam, apart from community channels there are no indications on the World Wide Web of the impending danger the site poses to users. When you enter search queries “Dash wallet”, “Dash web wallet” and “online Dash wallet” dash-wallet.com appears on the first page of search results at a very high rank.

    On their contact page they have a form for to reclaim the 1 Dash lost above we sent an email to see if we could recover the missing Dash but unfortunately there has been no response yet. Dash-wallet.com is definitely a scam and should under no circumstances be used to store Dash. You can read Wallets (DashCore, Electrum, Mobile,...) for alternatives. Have you encountered any other Dash scams or are you a victim? Leave your thoughts in the comment section.

    Please read read Scam Warning Listing !! and Ponzi Pyramid Scheme Scam Warning for “other” bad players in the Crypto Space !




  • Dash Core Release v0.12.1.5

    We are happy to announce the release of 0.12.1.5. This release includes binaries, which can be downloaded below.

    About this Release

    Dash Core 0.12.1.5 is a maintenance release of the Dash Core 0.12.1.x series

    In this minor release only bugfixes have been included and we consider this a stable release.

    This release fixes a issue with proper watchdog propagation which causes rare "watchdog_expired" spikes.

    We encourage all masternode and other full node operators (exchanges, pools, explorers) to update.

    Changelog

    0.12.1.5 changelog
    ==================
    - multiple wd rate check (#1426)
        * Modify MasternodeRateCheck to support updating buffers only on failure
        * Update rate check buffer only when fAddToSeen is true
    - multiple vote fix (#1425)
        * Avoid adding the same vote multiple times to the vote file
        * Cleanup multiple votes in vote file
    - Fix potential race condition in vote processing (#1424)
    - Fix ProcessVerifyBroadcast (#1423)
        * check if mn rank can be calculated
        * fix "is in top" condition
    - Reject payment vote if masternode rank can't be calculated (#1422)
    - Don't add non-current wd's to seen map (#1417)
    Thanks to 
    @udjinm6, @tgflynn, @schinzelh
    

    Downloads



  • Kraken opens Dash (DASH) trading

    Kraken is pleased to announce support for Dash (DASH). Dash is the fourth most valuable digital asset by market cap and recently experienced a huge surge in price (6x gain) and trading volume (10x gain). Dash has one of the fastest growing peer-to-peer networks and supports both “private” and “instant” payments. The open source Dash protocol is self-funded and self-governed, meaning that the Dash network funds its own development and anyone can present their idea to the network. Dash coin supply is limited to 22 million, with the current available supply at the time of writing around 7.22 million. “We’re excited to have Dash added to Kraken’s trading platform. As more people begin to take interest in our growth, we hope Dash rises to meet our expectations as one of the most highly traded cryptocurrencies on the platform, while simultaneously providing Kraken clients with the value they’re looking for.” - Dash Core Team Which DASH pairs will be available for trading? DASH/USD (Dash - US Dollar) DASH/BTC (Dash - Bitcoin) DASH/EUR (Dash - Euro) Margin Trading: possibly coming soon! How do I deposit DASH to my Kraken account? Go to Funding > Deposit > DASH and click “Generate New Address.” Then send DASH to this deposit address from any DASH wallet. Will DASH be available on the new trade platform? Yes! To trade DASH on Kraken’s new trade platform, go to Trade Kraken and click “Connect” to log into your Kraken account. Select the DASH/USD currency pair from the drop-down menu in the upper left of the screen below the Kraken logo. See our previous blog post for more information on getting started with the new trade platform. Which Dash payment types will Kraken support for withdrawal? Normal withdrawals (fee = 0.005 DASH) “Instant-Send” withdrawals (fee = 0.01 DASH) - Please note that while “Instant-Send” withdrawals may be faster than normal withdrawals, they will take several minutes at least to move through Kraken’s system and may take another 15 minutes after that if the destination doesn’t recognize “Instant-Send” payments. “Private-Send” withdrawals - NOT supported at launch.

    http://blog.kraken.com/post/15...

    DashPay



  • DASH TUTORIAL: How To Use Jaxx App On iPhone


    Author,

    Leah Stella Stephens

    writer, editor and artist. Contact me on Twitter if you must: https://twitter.com/stellabell...

    Today is a big day for Dash. iPhone users (I’m in this camp) now have a great digital currency wallet to use because Apple approved the Jaxx iOS app this morning. Dash Nation is celebrating big time because Apple hasn’t been too kind to Dash in the past. So, today is a huge leap forward for Dash and Apple. YAY!

    Today is also a big day for me personally, because I taught my mother how to use the Jaxx wallet on her iPhone. She also just got her very first Dash today. I paid her 1 Dash this morning to be my guinea pig. Her eyes lit up when I said she might be the oldest woman on the planet who is currently holding 1 Dash in her Jaxx iPhone wallet.

    If you’ve never used a digital currency wallet before and you have an iPhone, don’t worry, this tutorial is for you.

    STEP 1: DOWNLOAD JAXX IOS APP FROM THE APP STORE



    Here’s the link to the Jaxx iOS app: https://itunes.apple.com/us/app/jaxx-blockchain-wallet/id1084514516?mt=8

    I’ve already downloaded and sent two transactions (to my mom!), so I know it works just fine.

    STEP 2: CHOOSE WHICH DIGITAL CURRENCIES YOU WANT

    For now, I’m just using Dash the most, so I selected that currency. Jaxx makes a different wallet for each digital currency, so select the ones you use:


    STEP 3: CREATE NEW WALLET

    Select CREATE NEW WALLET and tap Continue:

    STEP 4: BACKUP YOUR WALLET [very important!]

    You’ll need to select “Yes, Backup wallet” after you select this. At this point, you’ll want to know what a backup recovery phrase is and how it works. Your backup recovery phrase is made up of 12 unique words in a certain order. These 12 words that are the keys to your money, all of it. Your backup phrase is the key to all of your digital assets, meaning all your Bitcoin, Dash, etc. This means that if you lose your recovery phrase, then you also lose all your digital coins in the event that your phone gets lost or broken. As long as you have your recovery phrase, you can regain control of your funds.

    Jaxx will display your unique 12 words to you at this point and you need to write them down with a pen on paper. DO NOT TAKE A SCREENSHOT OF YOUR RECOVERY PHRASE. Put your recovery phrase in a safe place. In the event that your phone is lost or stolen, as long as you have your recovery phrase, you will still have access to your money. This phrase enables you to set up a Jaxx wallet on different devices, like a desktop computer or other phones, etc.

    PLEASE PUT YOUR UNIQUE 12 WORD RECOVERY PHRASE IN A SAFE PLACE AND DO NOT STORE ONLINE OR IN ANY DIGITAL FORM.

    Tap on the menu in the upper right-hand corner:


    Select TOOLS from the menu:

    Choose BACKUP WALLET:

    STEP 5: Setup your PIN

    Your pin is a 4 digit code that is used whenever you send money to someone. Your pin is different from your recovery phrase. Your pin is used every time you send money to someone. Your backup recovery phrase is used when you’re setting up another digital wallet on a different device or if you lose a device.

    This additional security layer is to prevent others from sending your money from your phone. When you send money to an address, Jaxx will require you to input your pin number as the last step in the transaction process.

    To setup your pin, tap the menu icon in the upper right corner, and then select SETTINGS:

    Tap SETUP SECURITY PIN:

    Jaxx will require you to enter it twice to confirm it’s correct. Write down your PIN and keep it with your backup recovery phrase. Keep it in a safe place.

    To learn more about Jaxx, visit their official webiste: https://jaxx.io/

    Here’s a Dash Detailed video that gives you the backstory on how the Jaxx iOS app was finally approved by Apple:



  • Coinapult Integration + Dash Core Hires 12 Full-time Devs | DASH: Detailed

    movements, network stats, and more. Host Amanda B. Johnson brings you DASH: Detailed.

    TRANSCRIPT

    SHOW LINKS

    GET SOCIAL + LEARN MORE

    DashPay



  • $20 DASH for Every Viewer Who Helps Someone Open -FirstDashWallet


    Get paid Dash to spread Dash in this week’s #FirstDashWallet campaign. Take to Twitter or Facebook with your hashtag, payment address, and photo – and don’t forget to help your friend backup their new wallet.

    RULES FOR THIS CAMPAIGN:

    1. One paid post per person

    CONNECT:

    Amanda’s Twitter: http://twitter.com/amandab_joh...

    Amanda’s Facebook: http://facebook.com/dashingama...

    Dash-related online discussion: http://dashnation.com/chat

  • Dash homepage: http://dash.org
  • SUBSCRIBE:

    • Send an email to [email protected] with “subscribe” in the subject line

    DashPay

    Amanda B Johnson








  • OFFICIAL DASH ROADMAP Version 2.1.1

    Version 2.1.1 // Delivery Milestones

    • Evan Duffield / [email protected] / Dash Labs
    • Andy Freer / [email protected] / Dash Core CTO

    Dash Evolution will be the first user-friendly and scalable digital currency platform suitable for mass adoption. Because this is such an ambitious goal, we’ve created a detailed roadmap to guide development. Evolution will be launched in three stages. Each release will increase the processing power, ease of use, feature set, and scalability of the network.

    We intend to increase the user capacity of the network by an order of magnitude with each new stage of development. Furthermore, because of increases in the amount of available budget funding, we will be able to grow the development team rapidly. We plan to double the number of developers with each release, allowing us to accelerate the implementation of each phase.

    We intend to schedule releases of Dash Evolution in a way that produces a high-quality product and provides a user-friendly experience. In addition to emphasizing quality and user experience, we will use each incremental release as a robust framework for future development. The Dash Core Team believes that taking the time to create a high quality product will create the most value over the long term. A quick rush to market would likely result in an inferior product that causes temporary price growth but long-term stagnation or decline.

    Several new technologies are required to deliver such an excellent user experience. These technologies will expand the capabilities of the backbone infrastructure supporting the network and will ensure that it is capable of handling the transaction loads and data storage requirements of a mass-market user base.

    Masternodes will scale and be tested using a system called ”state transitions.” This system will provide a mathematically predictable way of determining the quality of service that masternodes provide. Full access to the blockchain will be required to perform proper state transitions of user objects, which will reference governance objects and blockchain transactions to perform quorum operations. Masternodes which fall under a threshold of activity will automatically be removed from the masternode list using a new system called “masternode blocks.”

    DashDrive will be implemented using software called IPFS, a user-friendly and popular P2P file system which will automatically handle most of the network’s sharing, redundancy and syncing operations. IPFS writes will utilize masternode quorums for security. DashDrive is an internal facing system that stores user objects within the network in a decentralized way. There is no public-facing system for storage of non-Dash related information. DashDrive is not a replacement for consumer and enterprise applications like Dropbox; it’s a mechanism to allow smooth functioning of the network.

    Network operations will scale using a targeted model to allow for exponential growth. Hardware requirements for masternodes will gradually increase to power a larger network that services more users with greater functionality. When the first phase of Evolution is deployed, masternodes will face new hard disk requirements. They will need both a solid state drive (for faster retrieval of blockchain data) and an ordinary hard disk with higher storage capacity. Eventually the network will finance the creation of masternode-specific hardware with custom requirements. Such hardware will allow massive parallelization of transaction processing, hashing, and other system functions. More powerful hardware will increase the throughput of the network significantly. This hardware will be entirely open source and non-exploitable and will connect to commodity hardware for additional storage capacity.

    Over the past few months we have been rapidly increasing the size of our development team in order to accelerate delivery of Evolution. In the meantime, a number of Core developers have been focused on delivering and implementing Dash 12.1. This update was absolutely vital, serving as a link between the existing Dash codebase and future Evolution releases. Now that 12.1 has been successfully rolled out, our entire development team is transitioning to work on Evolution.

    In order to create a quality product as quickly as possible, the team had to create a solid foundation. We had to carefully plan the project’s roadmap, create enormous amounts of documentation, and do significant research to ensure that we do not make time- and resource-wasting mistakes during the creation of Evolution. We will soon be opening a vast amount of private documentation to the community, ensuring complete transparency of our development work. This phase of the project is coming to a close, with the entire team now beginning to focus on creating the actual codebase for Evolution.

    We would also like to announce the creation of a new team to be centered in Hong Kong, called Dash Labs. This team will be the scientific arm of the project, focusing on research and the development of custom hardware. Evan Duffield and Andy Freer are heading up this team. Dash Labs aims to create the first open-source versions of many different types of hardware. Our goal is to help the digital currency space to remain open and transparent, while reducing the economic advantages of closed-source proprietary technology. For example, advanced open-source ASICs would eliminate most of the advantages of privately-developed ASICs. As a result, mining centralization could be significantly reduced. All economic actors will have a level playing field, at least with respect to hardware solutions.

    DashPay Wallet Alpha (September 2017)

    • Dash version of CoPay, pre-Evolution functions, on test-net
    • Will lead to full Evolution wallet (not merely a web wallet)
    • DashCore 12.2 Release (September 2017)
    • 2MB block size increase, activation in November 2017
    • 2MB / 5MB block research documentation
    • Launch of a read-only/view-only portal for project documentation which will be open to the entire community (to ensure transparency)
    • Launch a read-only/view-only portal to view current tickets, projects the teams are working on

    DashPay Evolution Wallet Testnet Release (November 2017)

    • User signup and friending process (Signup procedure for Evolution on testnet // reservation testnet)
    • Basic support for purchase agreements
    • Evolution Account Management (Create, Review, Update, Delete)
    • DAPI testnet release

    DashCore 12.3 Release (December 2017)

    • HD wallets, rehaul of networking code, etc etc (other Trac items)
    • Evolution Alpha Release to Partners (testnet, December 2017)
    • Integration partner testing
    • Merchant and app testing
    • API & SDK testing
    • Multi-stage escrow transactions
    • Support for user/merchant ratings via maintenance quorums

    DashPay Evolution Wallet Livenet Release (February 2018)

    • Signup and Friending Process Evolution on Livenet
    • Evolution Account Management on LiveNet
    • DAPI Livenet Release

    13.0 - Evolution v1 - Mainnet (June 2018)

    • Public DashPay, DAPI, DashDrive, DashCore v13.0 release
    • Fourth Hiring Wave - Full-time developers
    • 500K daily-users supported 2215
    • 1TB HDD / 128GB SSD Req 89
    • 64TX/SEC && 5.33MB blocks 1620 214
    • Proof of service / Proof of blockchain
    • Governance object support for users, groups, accounts
    • Email-based invitation system 26
    • Encryption of object data
    • Offices in Arizona, Europe (CORE), and Asia (Dash SW)
    • Age-based quorums 137
    • IPFS DashDrive implementation / Limited sharding ability
    • Official user-friendly Wallet
    • Masternode blocks 11

    14.0 - Evolution v2 (TBD)

    • Fifth Hiring Wave - Full-time developers
    • 5M daily-users supported
    • 2TB HDD / 256GB SSD / 16/32 Xeon processor
    • 128TX/SEC && 10.67MB blocks 175
    • DashDrive v2 326
    • Third-party add-ons for customer DAPI objects / wallet schema versioning
    • Automatic form filling for delivery addresses using encrypted blobs
    • External storage support to offload blob storage for payment request history and other information
    • Fiat / Credit card support from within wallet, seamless design 2723
    • Evolution marketplace / Add-ons / Rating system 2518
    • Collateralized mining 12

    15.0 - Evolution v3 (TBD)

    • Sixth Hiring Wave - Full-time developers
    • 50M daily-users supported
    • 10 GB Ethernet-handoff / Co-located networking requirement
    • 256TX/SEC && 21.34MB blocks 1714
    • Masternode shares via governance objects
    • Group-based masternode shares program 1
    • Group-based voting system for picking / dropping hosting providers on group owned masternode
    • Group-based voting for network proposals

    16+ - TBD

    • Complete end-to-end open source masternode hardware / with custom silicon for processing high volumes of payments and other information. Important for maintaining exploit free hardware systems.
    • Fully open source / ahead-of-curve solutions for ASIC creation, allowing fair distribution and removing proprietary individual investment which creates imbalances in mining hardware 19
    • v16 - 42.68MB 512TX/S
    • v17 - 85.36MB 1024TX/S
    • v18 - 170.72MB 2048TX/S
    • v19 - 341.45MB 4096TX/S

    Footnotes

    1: Group of savings accounts which correlate to single group-operated masternode 2: Sybil-proof system, where each user created has the ability to invite three others; invitee can’t invite anyone (only proper created accounts using default registration system) 3: Efficient propagation of sub-objects according to user-based quorum filtering 4: DAPI has no access to user’s addresses / only object updates besides the singular pubkey address which is the user’s publicly-visible, address-based identity in the system. 5: ADAPI (private Tor-routed DAPI implementation for PrivateSend) 6: Burn-based credit system for allowing users to update governance objects 7: Friending system has two objects which point to each other, inverting users into/from fields 8: Subject to change according to ASU research 9: HD (disk-based) storage used for DashDrive governance object storage 10: SSD storage used for blockchain-only storage / caches 11: Blockchain-based masternode quorum record / historic accounting of active masternodes at specific times 12: System of requiring collateral + mining hardware to create blocks on network. Each collateral allowed to mine block every specific amount of time. 13: All active masternodes will be sorted into four groups by age. The oldest 25% of the network will be in the first group, the next-oldest 25% will be in the next group, and so on. Masternode quorums will draw 25% of their quorum from each age group. 14: X11 hashing, quorum selection, sha/crypto transaction processing and other common functions available via custom hardware allowing for higher network security and higher transaction support 15: System requires highly interconnected second-tier network with co-located ethernet handoff. VPS co-location should be suffient for first evo release. 16: Upgrade to 5MB blocks doesn’t require specialized hardware. 17: Base two log-linear growth model, based on mathematically model of crypto-sphere economy and historical growth of the space. 18: Base two growth model of block sizes beyond this 19: Easy to remember way of seeding wallets 20: Internal budget-based investments to create low nanometer / high quality ASIC hardware which offers bleeding edge advantage to the market, cutting out any ability for private investment to gain large advantage over other miners. 21: State transitions are calculated to be (2007310)*500000/576 bytes, per block, increasing blocksize by 807291 bytes each block, 17% of the total blocksize. 22: Tier-2 conceptually is able to handle much larger block propagation, due to having much higher quality network connections. We plan on having large farms of co-located servers, eventually connected using ethernet hand-off. Masternodes located in the same facility can be used for local syncing, allowing more rapid propagation of blocks to catch new servers up. Tier-1 remains permissionless, but also becomes vastly more expensive. Processing of blocks uses custom hardware, allowing for us to process transaction/transition signatures in a parallelized way. 23: 868 transactions per block, if assumed 1 transaction per day, per user (lots of assumptions // we need more data). (5TX/SEC + 2TS/SEC) 24: Second-generation Evolution wallets are software based wallets which expand the object schema to allow internal wallet-to-wallet custom relationships for custom applications such as allowing businesses to have custom wallets for their application. This will allow streamlined applications with easy to use features within subsets of the whole dash economy. 25: DashDrive object writes require fees for each object written to the system. The system is designed to use an initial burn of coins, which create a small credit that is tracked in the system, debits are introduced for each operation that is done in relation to Evolution. 26: Using specialized state transition for maintenance functions Each component of masternode will run redundantly under a load balancer to allow for individual component failure without causing a cascade which creates an outage 27: Using third party API keys, allowing user to setup keys in settings then use from wallet seamlessly without ever leaving Dash. 28: By leveraging dapi and third party tools, we can deploy addons and a marketplace, which allows custom third party services to integrate directly in the wallet such as debit/credit cards and fiat bank account support

    DashPay

    Evan Duffield



  •  Dash Core Team Monthly Report June - 2017

    Dear Community members,

    It is my pleasure to give you a status report of the Dash Core Team
    activities. Below, you will find our report covering activities
    performed through the end of May, grouped by the four strategic areas of
    focus for 2017.

    Software Development

  • Dash core wallet - version 12.x (lead developer: UdjinM6)
  • Dash Evolution (lead developer: Nathan Marley; PM: Luba S.)
    1. Backend Pre-Alpha version was completed in time. Alpha version development started at the beginning of June and will be finished at the middle of August.
    2. DashDrive Pre-Alpha version was started (will be delivered in July).
    3. DashPay Android installation for internal team review was delivered, Chrome and iOS installation building was started.
    4. We continue to improve project planning: internal roadmap was updated, release plan for Evolution Frontend team was added.
    5. Evolution Project Charter and with high-level risks definition was created and reviewed by Robert.
    6. Description and requirements list for Backend Pre-Alpha and Alpha were added to Evolution Confluence space.
  • Dash Evolution Backend (lead developer: Alex Werner; PM: Luba S.)
    1. Completed researches:
      1. Insight-API(1) : Check the possibility to received ballot and vote from the Network.
      2. Find the most efficient way (proto, class, functional programming) to run DAPI. Research results were described in ‘DAPI Architecture Report’.
      3. Getting more insight on SubTX(2) Protocol and evaluate how much we could use that as a solution for our initial seeding process. Research results were described in ‘Seeding Evo initial SubTx Costs from the Network’ and ‘DIP 002: DASH EVOLUTION Subscription Transactions’ documents.
      4. Review ZMQ(3) POC(4) and look into other messaging alternatives (IPFS, Orbit, DeepStream).
      5. DAPI(5): Research on invite transactions.
      6. Mempool: Research on best way to save data.
      7. DashTrust(6): Eigentrust on Dash.
      8. OrbitDB: Bootstrap to external OrbitDB instances to sync DB's, Bootstrapping with IPFS binaries working but using js-ipfs ongoing, js-ipfs - bootstrap to external nodes to sync published data.
      9. Networking(bcoin, dashcore, socketio, zmq). Created POC with Socket.io, with ZMQ (exclusive pair), high-level lookup on networking between pairs (ZMQ, Socket.io, P2P, bitcoin, bcoin..) was done. Networking bootstrap process of bcoin was setuped. Research results were described in: ‘Networking Review’.
    2. DAPI - Network - P2P(7) Setup & Seeding:
      1. Setup of working branch for networking in DAPI was done.
      2. Setup of basic barebone from bcoin codebase + setup test cases (commits) + template for node in mempool was completed.
      3. ZMQ demo setup(including pairing and broadcasting) was done.
      4. Implemented update functionality: a node receiving an identity update the node data in mempool and broadcast the update across network.
    3. ZMQ:
      1. POC was created. It supports all major minimal required features (connecting, propagating messages on network, new nodes auto syncing with network state, handling dropped nodes).
      2. Handled connections to dropped nodes by binding to new live nodes.
      3. Implemented new method of finding open ports within defined range.
      4. Created service which keeps tracks of active nodes (in production this will be obtained from DashDrive).
      5. Added ability to run ZMQ on external machines/IP's.
      6. ZMQ POC was tested on multiple machines. Benchmarks/stress tests were done, some bottlenecks were identified.
    4. DAPI-SDK(8) code refactoring was done.
    5. Preparing of Evo Backend for DashPay(9) use:
      1. Implemented several missing Explorer routes.
      2. Refactored and tested BWS(10) code.
      3. Prepared README.md of DAPI-SDK for DashPay frontend team.
      4. InstaSend implementation to BWS was completed. Added upstream modification in: bitcore-mnemonic, bitcore-payment-protocol, bitcore-wallet-client.
    6. Insight-API: A bug on /tx/send was fixed.
    7. A compilation of many backend researches + work (POCs) was integrated inside a DAPI Github branch.
  • Dash Evolution DashDrive (lead developer: Nathan Marley; PM: Luba S.)
    1. Researches:
      1. Postgres JSON capabilities.
      2. Mnesia (Erlang distributed db).
      3. Using IPFS(11) for DashDrive.
      4. Quorum(12) for Dashdrive data verification and meeting breakdown.
      5. Storage Backends exploring: should we use a Graph database? What are the benefits of Graph vs other NoSQL DBs and traditional relational DBMS'es?
      6. Orbit-DB for metadata synchronization: (OrbitDb/NodeJS ipfs-api POC dockerized and developed, installed and tested orbit-db key value store, developed OrbitDB index, tested data writes).
    2. The first version of DashDrive data flow/sync design was created.
    3. Quorum interaction design started.
    4. Testing of DashDrive POC was started.
    5. Dockerized Insight-Dash, built out a VPC, subnets for hosting insight.
    6. DashDrive repository was cleaned up, outstanding PRs were merged.
    7. Implementation of DashDrive IPFS event adds:
      1. Implemented event writes (adds to IPFS, pins, indexing).
      2. Discovered issue w/connections using IPFS + docker-compose.
      3. IPFS mockup testing was done.
    8. Created mock events for loading DashDrive.
    9. A proposal for testing Sentinel proposal pruning was imported to testnet.
    10. DashDrive tests were cleaned up use py.test w/mock data.
  • Dash Evolution Frontend (lead developer: Chuck Williams; PM: Luba S.)
    1. IBN(contractors team) made connections from the front-end of DashPay Wallet to the backend DAPI.
    2. DashPay Android installation for internal team review was delivered.
    3. Work on Chrome and iOS DashPay installation was started.
    4. Dashpay Android installation was updated: removed conflicts with existing installs.
    5. Evolution & DashPay wallets are officially "split" projects. IBN & Dash will share resources for both projects, but IBN will mainly focus on DashPay Development with support to Evolution Design & Dash team will mainly focus on Evolution development with support to DashPay development.
    6. Account Setup UX Flow was updated after review.
    7. New full time frontend developer was assigned to Evolution - Joshua.
  • Dash wallet for iOS - updated features (lead developer: @QuantumExplorer)
    1. back in Review on iTunes
  • HBPay Android Based POS with DASH Payment Processor (TestNet Open)
    1. https://hbpay-testnet.hexabit.io
      1. Mycelium wallet updates - re-launch
    1. Business Development
      1. Dash - RUB now on https://exmo.com
      2. Dash now trading on (African Crypto Exchange): https://www.altcointrader.co.za/dash
      3. Dash launched on CoinBR - Brasil
      4. Dash - Blockcypher partnership work together to attract new applications to the Dash network.
      5. Dash starts conversations with Korean and Japanese exchanges.
    2. Project Organization
      1. Law firm selected for general counsel (e.g., reviewing contracts, drafting contractor agreements, etc)
      2. Hired Director of Human Resources
      3. Initiated recruiting for QA/testing and project management roles in United States and Europe
      4. Research on physical office locations started
      5. Internal Service Desk alpha release
      6. Formalization of Evolution development (work on project charter and documentation)
    3. Marketing and Communication
      1. OFFICIAL DASH ROADMAP - Version 2.1.1 // Delivery Milestones: https://github.com/dashpay/dash-roadmap/blob/master/README.md
    1. Interview with Erik Vorhees:
    2. BitCart Dumps Bitcoin, Goes Dash-Only : https://cointelegraph.com/news/bitcart-ditches-bitcoin-for-dash-user-uptake-soars
    3. Publication in Forbes: https://www.forbes.com/sites/lauras...ut-is-it-about-to-self-destruct/#2c855a79cb31 Dash’s Amanda B. Johnson Talks About the Future of the Cryptocurrency: http://www.financemagnates.com/cryp...amanda-b-johnson-talks-future-cryptocurrency/
    4. New Hampshire’s First Vending Machine to Offer DASH: http://freekeene.com/2017/06/13/new-hampshires-first-vending-machine-to-offer-dash/ An article on Dash in Ghana: https://salam.liberty.me/dash-crypt...e-set-to-eliminate-poverty-in-northern-ghana/
    5. EToro launches cryptocurrencies investment CopyFund ("Dash to be added in the near future"): https://www.finextra.com/pressarticle/69540/etoro-launches--cryptocurrencies-investment-copyfund
    6. Get your Dash at 9000 kiosks in Ukraine! https://www.dash.org/forum/threads/get-your-dash-at-9000-kiosks-in-ukraine.15268/
    7. Sao Paulo / Brazil 2nd Bitcoin Summit - 30th June 2017. Daniel Diaz from Dash attends the conference. https://blog.coinbr.net/bitcoin-summit-evento-2017/?rdst_srcid=756684
    8. Dash Payment Platform Evolution Aims to Undercut PayPal, Venmo From 2018: Altcoin’s Roadmap: https://cointelegraph.com/news/dash...ercut-paypal-venmo-from-2018-altcoins-roadmap
    9. How To Enable On-Chain Scaling: https:[email protected]/how-to-enable-on-chain-scaling-2ffab5997f8b
    1. Interview with Evan Duffield on Evolution's Roadmap:
    2. Dash sets out roadmap: https://www.finextra.com/pressarticle/69847/dash-sets-out-roadmap
    3. BitcoinNW Launches Third DASH Cryptocurency ATM in Oregon: http://www.razor-forex.com/2017/06/bitcoinnw-launches-third-dash.html
    4. Why On Earth Would A Merchant Drop Bitcoin For Dash? : http://news360.com/article/408264561
    5. Can Bitcoin’s First Felon Help Make Cryptocurrency a Trillion-Dollar Market? (Dash featured): http://fortune.com/2017/06/26/bitcoin-blockchain-cryptocurrency-market/
    6. Hong Kong | Dash Research and Planning by Evan Duffield: https:[email protected]/hong-kong-research-and-planning-4206e065aa9c
    7. Dash DAO Gives Away $50,000 in #FirstDashWallet Campaign: Insights From Amanda: https://medium.com/dash-for-newbies...et-campaign-insights-from-amanda-f319f8a3bf46
    8. Moshi Moshi from Dash Japan): http://cryptocurrencymagazine.com/dash-japanese-website
    9. Daniel Diaz - Dash at PanaFinTech - 15th June: https://www.dash.org/forum/threads/daniel-diaz-dash-at-panafintech-15th-june.15379/
    10. Dash Sponsored MMA Fighter Davis Dos Santos To Fight At TKO 39: https://www.dashforcenews.com/dash-sponsored-mma-fighter-davis-dos-santos-fight-tko-39/
    11. Venezuelans Are Seeking a Haven in Crypto Coins as Crisis Rages (Dash mentioned): https://www.bloomberg.com/news/arti...eking-a-haven-in-crypto-coins-as-crisis-rages

    Footnotes

    (1) Insight API is a REST API and
    WebSocket service based on Bitcore Node Dash in order to work with Dash
    Blockchain in a easiest way.

    (2) In Evolution, users create accounts by registering their
    subscription data directly on the Blockchain in the metadata of
    specially constructed transactions called Subscription Transactions that
    also burn a minimum amount of Dash via a provably unspendable null-data
    pubkey script in one of the transaction’s outputs.

    (3) ZMQ is a raw, high-performance async brokerless messaging library.
    We will use it to add a P2P Layer in DAPI. We choose ZMQ because Dashd
    already need it, so we already have this dependency, and because of it’s
    lightweight footprint.

    (4) Proof-of-concept

    (5) A decentralized API which allows third tier users to access the
    network securely and provide functionality for merchant payments.

    (6) A trusting system that will provide a value to each DAPI node given
    their quality of answer, but also performance or any technical
    information on health of the server and quality/trustiness of the data
    he sent.

    (7) Each DAPI node will be connected to another DAPI node in a P2P way,
    this will allow us to have a specific exchange of objects that we do not
    want to store in the blockchain (because of the temporality of theses
    data).

    (8) This module allows developers working with the DAPI on a Javascript landscape.

    (9) Wallet built on base of Copay open source code and compatible with
    the current Dash network. It will contains Androind, iOs and Chrome
    installations.

    (10) A bitcore-wallet-service compatible with DAPI.

    (11) DashDrive stores data in the InterPlanetary File System (IPFS), and
    replicates the data using the built-in DHT and network establish thru
    running an IPFS node. Since the DashDrive writes are immutable and make
    up an immutable data ledger (much like corporate accounting, or a
    blockchain, for example), IPFS is actually a perfect fit for the
    required data store and distribution system.

    (12) Each write to the database requires a pseudo-random set of
    masternodes, called a quorum, to agree and sign a message. If the
    majority of this quorum agrees, the write object will be wrapped in
    these masternode signatures and relayed internally to DashDrive. By
    using masternode quorums, we ensure that our network is sybil-proof. Any
    attempt to attack the network would require the attacker to control an
    enormous number of masternodes, which would be prohibitively expensive.

    [IMG]


    Log in to reply
     

    Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.