Welcome to the Dash Forum!

Please sign up to discuss the most innovative cryptocurrency!

OFFICIAL DASH ROADMAP - Version 2.1.1 // Delivery Milestones

Discussion in 'Official Announcements' started by tungfa, Jun 27, 2017.

  1. tungfa

    tungfa Administrator
    Dash Core Group Foundation Member Moderator

    Joined:
    Apr 9, 2014
    Messages:
    7,545
    Likes Received:
    5,995
    Trophy Points:
    1,283
    https://github.com/dashpay/dash-roadmap/blob/master/README.md

    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.

    Please see post 2 ....>
     
    • Winner Winner x 5
    • Useful Useful x 1
  2. tungfa

    tungfa Administrator
    Dash Core Group Foundation Member Moderator

    Joined:
    Apr 9, 2014
    Messages:
    7,545
    Likes Received:
    5,995
    Trophy Points:
    1,283
    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 22
    • Ethernet networking requirement 15
    • 1TB HDD / 128GB SSD Req 8 9
    • 64TX/SEC && 5.33MB blocks 16 20 21
    • Quorum-based DAPI implementation 4
    • Proof of service / Proof of blockchain
    • Governance object support for users, groups, accounts
    • Email-based invitation system 2
    • State transitions 6
    • Encryption of object data
    • Offices in Arizona, Europe (CORE), and Asia (Dash SW)
    • Age-based quorums 13
    • Friending system / Semaphore-based approval system 7
    • 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 17
    • GB Ethernet-handoff / Co-located level networking requirement
    • Ability to move money between public and private accounts 5
    • DashDrive v2 3
    • Governance objects for multi-user accounts (multisig)
    • Masternode redundancy planning 26
    • 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 27
    • Unofficial Evolution wallets with custom features 23
    • Evolution marketplace / Add-ons / Rating system 25
    • Hardened entropy-based wallet seeding system 18
    • 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 17
    • DashDrive sharding / 4TB HD / 512GB SSD
    • PCI-E hardware-based masternode peripheral 14
    • 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
     
    • Winner Winner x 5
    • Like Like x 1
    • Informative Informative x 1
    • Friendly Friendly x 1
  3. akhavr

    akhavr Active Member
    Masternode Owner/Operator

    Joined:
    Oct 11, 2014
    Messages:
    438
    Likes Received:
    251
    Trophy Points:
    133
    Won't that lead to risk of adversarial body (e.g. government agency) going forward such specialized colo facilities?
     
  4. TheSingleton

    TheSingleton Member
    Masternode Owner/Operator

    Joined:
    Mar 27, 2017
    Messages:
    98
    Likes Received:
    53
    Trophy Points:
    68
    Might happen but as long as we don't have all the nodes in 1 country that should be fine.
     
  5. akhavr

    akhavr Active Member
    Masternode Owner/Operator

    Joined:
    Oct 11, 2014
    Messages:
    438
    Likes Received:
    251
    Trophy Points:
    133
    Well, if all the nodes are in several countries, but all of them are in the FATF, that won't make much difference.
     
  6. jimbursch

    jimbursch Active Member

    Joined:
    Mar 5, 2017
    Messages:
    458
    Likes Received:
    258
    Trophy Points:
    133
    When does the CoPay wallet get released on LiveNet?

    Does this constitute a "hard fork" or a "spork" or simply a software update? Same question for 12.3 and 13.0
     
  7. UdjinM6

    UdjinM6 Official Dash Dev
    Core Developer Moderator

    Joined:
    May 20, 2014
    Messages:
    3,243
    Likes Received:
    3,220
    Trophy Points:
    1,183
    We are still working on details but it's probably going to be a combination SF-like signaling + HF + sporks
     
    • Like Like x 1
  8. bielie

    bielie Member

    Joined:
    May 13, 2017
    Messages:
    55
    Likes Received:
    19
    Trophy Points:
    48
    So when will collateralised mining be implemented? Two years?
     
    • Agree Agree x 1
  9. AndyDark

    AndyDark Official Dash Dev
    Core Developer

    Joined:
    Sep 10, 2014
    Messages:
    313
    Likes Received:
    633
    Trophy Points:
    163
    Should be late Sept or October
     
  10. AndyDark

    AndyDark Official Dash Dev
    Core Developer

    Joined:
    Sep 10, 2014
    Messages:
    313
    Likes Received:
    633
    Trophy Points:
    163
    Within 2 years I would say but yes after Evo V1 launch
     
  11. RichardAO

    RichardAO New Member

    Joined:
    Jan 17, 2017
    Messages:
    33
    Likes Received:
    8
    Trophy Points:
    8
    Dash Address:
    XmTSEYFTG5dF7N68mEZwtpVUQPAPQ
    Ive been proposing this for a while, Im glad this is part of the plan - even if I may not have inspired it :)
    How can I contribute/help?
     
  12. camosoul

    camosoul Well-known Member

    Joined:
    Sep 19, 2014
    Messages:
    1,557
    Likes Received:
    1,009
    Trophy Points:
    183
    It seems like the same old consolidation argument. And I agree...

    I understand the reasoning, and even the perceived need. But, sometimes, the sledge hammer has a certain advantage in it's defiant lack of refinement. The Samsung Galaxy 8 did not make the Sledge Hammer obsolete.

    I'd like to see a summary of what is to become of MNs and MNOs as we know them today. Just tell me what an MNO will become, what is expected of him/her, etc. As PoSe requirements go up, will we get a sort of load monitor tool to find out how we're dong, as opposed to the boolean fucked/fuckednot? Are we all moving to this savings account thing? Who's paying for this specialized hardware and hosting that I think is a really bad idea?
     
    • Agree Agree x 1
  13. camosoul

    camosoul Well-known Member

    Joined:
    Sep 19, 2014
    Messages:
    1,557
    Likes Received:
    1,009
    Trophy Points:
    183
    In case I wasn't clear.
    Specifically; this makes running a masternode more and more precarious.

    It exposes the operator to more liability, is easier to identify and target, and much less portable.

    I believe that the advantages spoken of in the above quoted block are insignificant when compared to what is lost. Especially in light of Moore's Law.

    I think the flexibility or remaining generic is far more valuable, and the ability to do so while and still attain service level is not in question. This appears to be a solution in search of a problem, with far more cons than pros.

    It makes sense to specialize mining hardware, but not masternodes. These matters should remain discreet, despite the efficiency gains possible. Efficiency is not the only metric of value.

    My MNs already run on an all SSD machine with 64 threads... Even if load increased by 2 full orders or magnitude, it wouldn't notice. If a machine of this capacity ran only one node... Not to mention that it's already 2 generations old...

    Dedicated MN hardware sounds cool, but the negatives far outweigh the positives, IMNSHO. It seems as if only one metric was considered in reaching the quoted opinion.

    ISPs already hate hashers. Are you suggesting that MNOs will abandon the datacenter and bring pipes home? Does this not defeat much of the advantage currently held? Isn't the fact that MNs can leverage external market factors for cost/benefit going to be lost to the same vertical market response that we have for any dedicated hardware? Just look a the "charge whatever we can" of the ASIC realm. If DASH really does go up to $10,000, which it would have to, to make this worth doing, do you think that the remaining 2% ROI after all these expenses, on top of all this hassle, would be worth it? Not to mention the exposure... USDT flexes more than that... Pretty much any investment would be lower maintenance and higher profit. From a simple math perspective, this would make DASH the worst place to put your money. And bust your ass for the privilege? May as well just get a job and pay the boss man for the privilege of doing his work for him.

    I think this sounds like super-nerd fun, but no actual need. A solution in search of a problem, that didn't bother to look at the peripheral values.

    It's incredibly cheap to shoot myself in the foot. I could do it millions of times. It's very cost effective, and I have some of the coolest hardware capable of doing it very efficiently. That doesn't make it a good idea.
     
    #13 camosoul, Jul 8, 2017
    Last edited: Jul 8, 2017
  14. GrandMasterDash

    GrandMasterDash Well-known Member
    Masternode Owner/Operator

    Joined:
    Jul 12, 2015
    Messages:
    1,430
    Likes Received:
    547
    Trophy Points:
    183
    I agree and disagree.

    It's true this brings a form of "centralisation", but this also sets dash apart from every other coin. In five years from now, the crypto ecosystem will look very different; there will be multiple top-tier coins but each one of them will have their own distinctive modus operandi with very little in the way of real competition. Everything else will be hobby coins. And this roadmap does exactly this; moves dash from hobby coin to serious contender... or at least try.

    I totally get that dash could of / should of gone in a different direction but this is the reality and this is a space that will be filled, if not dash then someone else.

    I always end up referring people to the same old book but I think it's highly relevant. I believe crypto is following a similar pattern to how the telephone went from "fully decentralized" to "centralized":
    The Master Switch: Rise and Fall of Information Empires by Tim Wu
     
  15. camosoul

    camosoul Well-known Member

    Joined:
    Sep 19, 2014
    Messages:
    1,557
    Likes Received:
    1,009
    Trophy Points:
    183
    Being set apart only matters is that which sets it apart is useful.

    The "centralization" worries me less than the bull's eye.

    For the moment, governments don't take crypto too seriously. A few flipped their lid at the idea, but backed off when they realized they were losing their shit over a silly nerd non-threat.

    The fact that it can't be taken seriously is what made it a non-threat. As you've observed, that "can't take it seriously" aspect is going to change.

    Having special hardware makes it really easy to shut down. Can't just rent a new server in another country and bring it all back online in an hour.

    Not to mention the exposure to the taxation vector. Even complete compliance will not save you from arbitrary and capricious re-interpretations, ignorant mis-interpretation, and plain old corruption... Avoiding this is not about avoiding taxation, but the fact that you'll get fucked even if you do everything by the letter. Pulling the plug on racks and racks of special MN hardware can't be good for the network.

    If more resources are needed, the better route would be... Yes, I'm about to say this; 500/250/125 DASH MN collateral. Most of the load will come from DAPI. More servers does solve this. More servers is more hard drives is more data shards is more redundancy is more quorum parallelization is more resiliency is more flexibility is more agility...

    Give me mntop...
     
    • Like Like x 3
    • Agree Agree x 1
  16. GrandMasterDash

    GrandMasterDash Well-known Member
    Masternode Owner/Operator

    Joined:
    Jul 12, 2015
    Messages:
    1,430
    Likes Received:
    547
    Trophy Points:
    183
    Clearly, dash has set sail on a path of "centralization" of sorts. Of course, I don't mean a single company or location, but this new rising empire is going to get a lot of people talking, and no doubt some powerful people will single out MNOs as Digital Mafioso (money launderers blah blah blah). So I am wondering if we can organise a one week full-on assault on the dash network. One week of all-out war, a compilation of stress tests using "hacked" sporks etc to take out half of the network. I mean, in an organised take down of, say, 25% MNOs might take down 50% of network capacity. Let's simulate that and make the network work really hard. We can use a proposal to compensate MNOs for their losses. What do people think?
     
  17. splawik21

    splawik21 Well-known Member
    Dash Core Group Foundation Member

    Joined:
    Apr 8, 2014
    Messages:
    1,978
    Likes Received:
    1,362
    Trophy Points:
    283
    ^^ don`t we have testnet for that?
     
    • Funny Funny x 1
  18. GrandMasterDash

    GrandMasterDash Well-known Member
    Masternode Owner/Operator

    Joined:
    Jul 12, 2015
    Messages:
    1,430
    Likes Received:
    547
    Trophy Points:
    183
    True, but I imagine testnet can only do so much. I've seen very little regarding stress tests, except a few DDoS attacks. How do we assess and work around things like some major exchange also going down at the same time? Or important core team members disappearing? I mean, if 400 MNOs are simultaneously arrested and charged, that would likely take out 1000+ nodes and quite possibly for a very long time (months)... assets frozen etc.
     
    • Agree Agree x 1
  19. Andras

    Andras New Member

    Joined:
    Mar 20, 2017
    Messages:
    25
    Likes Received:
    10
    Trophy Points:
    3
    I agree with @GrandMasterDash that the hard-testing of the MNs is a good idea. I think they should be tested regularly, simulating DDoS attacks or testing their current maximum transaction processing power. The hardware behind the masternode should be irrelevant for the network as long as it hits the expected transaction processing power limit and it is resilient to certain hacking attacks. This way everyone could decide if they wanted to invest in specialized hardware or if they need to move their server to a server farm with faster internet connection.

    It is hard to admit and I realize that this would mean less profit for the current masternode owners, but I also agree with @camesoul that lower barrier of entry as masternode should be a goal, since that would make Dash more robust.
     
    • Agree Agree x 2
  20. akhavr

    akhavr Active Member
    Masternode Owner/Operator

    Joined:
    Oct 11, 2014
    Messages:
    438
    Likes Received:
    251
    Trophy Points:
    133
    I'd better have an ability to use both specialized hardware and general purpose servers on MN network. Maybe in different tiers or whatever... The ability to bring up a node anytime on a notebook over 3g connection within minutes after the specialized node is shut down.. This can be live-instead-of-death moment for the dash network in case of coordinated attack.

    Have any specific ideas how to do it? Maybe start a new thread for this?
     
  21. jimbursch

    jimbursch Active Member

    Joined:
    Mar 5, 2017
    Messages:
    458
    Likes Received:
    258
    Trophy Points:
    133
    Soon the Dash bug bounty program will be up and running, first in private, then later open to the public. If there are any specific tests you would like the program to address, contact me and we can consider it.
     
  22. GrandMasterDash

    GrandMasterDash Well-known Member
    Masternode Owner/Operator

    Joined:
    Jul 12, 2015
    Messages:
    1,430
    Likes Received:
    547
    Trophy Points:
    183
    There is something I don't understand. The MN will be run on specialized hardware to keep up with transaction demand... so that means regular supporting nodes (non-MN) will be excluded simply because they won't be able to keep up with the network?

    Anyway, regarding livenet stress tests, hmmm, I'm not entirely sure how MNOs will be able to compensate if half the network drops off. On the face of it, @akhavr idea of running a backup node over 3g seems a bit too ambitious, though a home fibre connection might work? In any event, it seems to me, the performance tests that are placed upon MNs should be self-adapting... perhaps then, it could recognise that half the network has disappeared and compensate accordingly.

    When first responders are put through emergency simulations, one of the things they are being trained for, repeatedly, is to keep calm and follow procedure. Perhaps that's where we need to be. Is that over the top? - I don't think so because dash's reputation would be on the line and it's not like we are talking hobby.. we are supposedly transitioning to a more responsible position.
     
  23. TheSingleton

    TheSingleton Member
    Masternode Owner/Operator

    Joined:
    Mar 27, 2017
    Messages:
    98
    Likes Received:
    53
    Trophy Points:
    68
    Yes unless they spend the money to upgrade their node to the level of a MN they will likely not be able to keep up.
     
  24. Andras

    Andras New Member

    Joined:
    Mar 20, 2017
    Messages:
    25
    Likes Received:
    10
    Trophy Points:
    3
    My current understanding is that masternodes will take over the job of the miners in the long run.
    So, ideally if a non-MN, regular node can't meet the current requirements of the masternodes (collateral, static IP, maximum tx/second, DDoS stress-test, protocol version etc.) they will not get paid, but they would still act as a useful source of the blockchain data for example.

    The Dash bug bounty is great, and I think it's a very good way to find security holes.
    On another level of quality assurance, I could imagine that the masternodes occasionally switch to stress-test mode for a few minutes, and ask every other masternode/regular node to flood it with requests, simulating extreme traffic/DDoS attacks. The cooperating masternodes would report the target's ability to respond, measuring it's toughness. If this value is lower then the current requirement, the masternode temporarily would loose its status (and profit potential). It's just a raw idea, and it might be too expensive to accomplish in a fair way, I don't know... A decentralized self-testing mechanism would risk only one masternode at a time and it would also continuously monitor the network health.
     
    • Like Like x 1
  25. akhavr

    akhavr Active Member
    Masternode Owner/Operator

    Joined:
    Oct 11, 2014
    Messages:
    438
    Likes Received:
    251
    Trophy Points:
    133
    That was a stretch to get the idea across :)
     
  26. camosoul

    camosoul Well-known Member

    Joined:
    Sep 19, 2014
    Messages:
    1,557
    Likes Received:
    1,009
    Trophy Points:
    183
    After some though... I wanted to revise my statements regarding MN hardware.

    If special MN hardware were a PCIe card, and it were cheap enough I could fire-and-forget it... No concern for the loss... I could see the advantage.

    Hosts are not going to allow the CPU to do the privileged mining. But an ASIC on PCIe, that doesn't crank up the power bill... And includes a few other massively parallel enhancements to chain and DAPI processing... I could see that.

    But only if it's cheap enough that it's disposable.
     
    • Like Like x 1
    • Agree Agree x 1
  27. akhavr

    akhavr Active Member
    Masternode Owner/Operator

    Joined:
    Oct 11, 2014
    Messages:
    438
    Likes Received:
    251
    Trophy Points:
    133
    Cheap not just because of "disposable", but because some countries have braindead customs. And it's not the theft of 44% price that concerns me, but the issue that the "administration" of the import can easily eat workweeks. And, of course, you'll be flagged in "the database".
     
    • Agree Agree x 1
  28. camosoul

    camosoul Well-known Member

    Joined:
    Sep 19, 2014
    Messages:
    1,557
    Likes Received:
    1,009
    Trophy Points:
    183
    Another solid point.

    Special MN Hardware makes the matter of being an MNO exceptionally cumbersome. Well, we expect a lot of MNOs. Sure. But you can't expect every MNO to start a war with the State. It is fine to ask much of MNOs fiscally, resourcefully, technically...

    But, asking the impossible will only hurt DASH. You're essentially asking "MNOs need to find a solution to global government corruption or they don't get to run a masternode." This is a problem as old as the Earth... No one has ever solved this problem. If you make running a MN contingent upon it, there simply won't be any masternodes.

    Dodging government is about dodging it's corruption. There is nothing in all of recorded human history which existed, had government added to it, and was improved. DASH simply will not be able to function with that burden.

    I'm not seeing a balance on hardware that would be so cheap it would be disposable, but still be useful...

    I understand the notion, but I find another aspect of DASH that makes me wonder if the nerds in charge poke their heads out and look around at the real world anymore...

    Yeah, I'm going to bring it up: IX is STILL broken... I understand the delay in gearing up the major codebase transition for Evolution. I do. But, hamstringing real-world efforts during that delay was an obnoxiously bad move. There could have been parallel work going on, laying a foundation... But, nope... Leave IX broken for 2 years... I realize it wouldn't be efficient. Sometimes life is messy and you have to do shit the hard way, or you end up doing nothing at all... Doing nothing, and holding back everyone else, just because it's not perfect, or might result in a bit of re-work... I cannot overstate the absolute foolishness of the decision NOT to fix IX BEFORE the long delay...

    And we see this special hardware thing, again, not considering the real-world implications...

    We're way, way better off reducing collateral to increase node count. If collateral were 500, that would put DASH waayyy beyond even the weak "full node" argument. Of course, we really don't care about positioning against legacy crapcoins, but the argument would be moot on it's face and not able to distract... One must also consider that a lowered collateral would likely have a more than doubling effect, as all the whiners who talk about how unfair it is that they can't afford a money hose, would be able to run a money hose... After complaining at length about how they lack the technical qualifications and want the job dumbed down instead of improving their resume...

    I identify as a MasterNode Operator! You elitists stop oppressing me! The Usefularchy is keeping me down! I refuse to think! Run my MasterNode for me! I'm entitled!

    The only upside I see is that the notion of MN hardware is very, very far future-looking. It will be quite a long time before this bridge need be crossed. Decreasing collateral/increasing node count, could put that off until I die of old age and let my son worry about it.

    But, so was the budget/DGBB implementation, and a total crap version was instituted even though much better ideas were tabled...
     
    #28 camosoul, Jul 18, 2017
    Last edited: Jul 18, 2017
    • Agree Agree x 1
  29. moonknight

    moonknight New Member

    Joined:
    Jan 12, 2017
    Messages:
    5
    Likes Received:
    1
    Trophy Points:
    3
    Anything regarding Masternode hardware and other physical requirements should be done very gradually and cautiously. Imagine if all of a sudden there was a special hardware requirement -- a lot of MNOs might simply decide that's too much trouble and cash out their collateral. What would happen to Dash's price and marketcap if a mere one hundred MNOs (~2% of total) dumped their 100,000 Dash on the market?
     
    • Agree Agree x 1
  30. GrandMasterDash

    GrandMasterDash Well-known Member
    Masternode Owner/Operator

    Joined:
    Jul 12, 2015
    Messages:
    1,430
    Likes Received:
    547
    Trophy Points:
    183
    Evan said there would be a transition period. And besides, I think a few other coins will go down a similar route.
     

Share This Page